WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
when finding a Yaml date, the parser currently returns it as a unix timestamp.

A flag to return it as a DateTime would be great.

If we handle them as DateTime, the dumper should accept DateTime objects and dump them as Yaml dates though

Issue 2:
Hi,

I'm not sure if this issue is a duplicate, because i couldn't find any other that specifically points to this.

I am rendering two controllers into the view like this:

{{ render(controller('WebBundle:Task:navTask')) }}
{{ render(controller('WebBundle:Notification:navNotification')) }}

Everything works out fine, but for each render i get 1 or 2 errors in the console:

GET http://example.dev/_wdt/98002d 404 (Not Found)

Here's content of controller action:

public function navTaskAction()
{
return $this->render('WebBundle:Task:navTask.html.twig', [
'navTasks' => 2
]);
}

And view:

<div class="tasks">
{{ navTasks }}
</div>

When I remove those, errors are gone.

It didn't bother me at first, but when i wanted to add 3rd render, it started to throw 404 alert for profiler, because it exceeds 5 calls.

Probably the problem exists because token is not passed to the subrequests, which then throws 404 error. Just a guess. Is there a way to fix this, or am I doing something wrong?
Issue 1:
Check this : http://twitter.github.com/bootstrap/javascript.html#tooltips

The data-placement doesn't work ... tooltips always opens on top

Issue 2:
congrats on releasing 2.3.0!

I was checking out some of the docs and saw that tooltips data-placement is not working correctly. I think its because of the one pull request that makes options set in javascript override the options that were set in the html but I'm not sure..
Issue 1:
A couple weeks ago we discussed being able to 'chain' task spawn options, which would be much more fun to write than the current builder interface.

I envision:

fn unlinked() -> builder { ... }
fn notify_chan() -> builder { ... }
fn spawn() { ... }

impl for builder {
fn unlinked() -> builder {
{ link: false with builder }
}
fn notify_chan(chan) -> builder
...
fn spawn() ...
}

With the functions at the top level returning a default set. Then you'll never need to type "builder" - all of these will be valid:

do task::spawn { ... }
do task::unlinked().notify_chan(c).spawn { ... }
do task::notify_chan(c).unlinked().spawn { ... }
let t = task::unlinked();
do t.spawn { ... }
do t.notify_chan(c).spawn { ... }

One problem is noncopyability of certain things that might get put in builder - like wrappers and notify ports (or future stuff...? not entirely clear on that).

Move mode on self can solve that; until then, we could perhaps make it a runtime error by doing the standard option dance. (When move mode on self appears, we can make it a build error without changing the interface.)

type builder = ~mut option<{...record...}>
impl for builder {
fn set_noncopyable_thing() -> builder {
let mut result = none;
result <-> *self;
}
}

An attempt to use a builder with none in it would fail at runtime.

Issue 2:
I didn't find any duplicate issue, but this problem has probably been there for a long time.

The code panic!("{}", 7) compiles and prints thread <main> panicked at "7", ...

The code panic!("{} {}", 7) doesn't compile as an argument is missing

The code panic!("{}") does compile and prints thread <main> panicked at "{}", ...

The last one doesn't detect potential mistakes, and is inconsistent with println!("{}") which doesn't compile.
Issue 1:
ISSUE TYPE

Documentation Report

COMPONENT NAME

core

ANSIBLE VERSION

ansible 2.0.1.0
config file = /root/.ansible.cfg
configured module search path = Default w/o overrides

CONFIGURATION

OS / ENVIRONMENT

Running ansible on CentOS Linux release 7.2.1511 (Core)

Managing a system on CentOS release 5.5 (Final)

SUMMARY

wait_for will not accept both port and path. The documentation should note that restriction

STEPS TO REPRODUCE

Construct a playbook similar to the following. seths_46 is one of my test VM systems. When duplicating this bug, use one of your test systems instead.

---
- hosts: seths_46
gather_facts: false
strategy: free
tasks:
- wait_for: host={{ inventory_hostname }} path="/adp/etc/rc2.d/s099upwrapup" port=22 delay=1 timeout=1800

EXPECTED RESULTS

I wanted Ansible to wait for the port to be open and then for the filename in the path to exist. If Ansible cannot do that, then the documentation should say so.

ACTUAL RESULTS

TASK [wait_for] ****************************************************************
fatal: [<ip address deleted>]: FAILED! => {"changed": false, "failed": true, "msg": "port and path parameter can not both be passed to wait_for"}

Issue 2:
ISSUE TYPE

Bug Report

ANSIBLE VERSION

ansible 1.9.5
configured module search path = None

ansible 2.0.1.0
config file = /dev/null
configured module search path = Default w/o overrides

# from git: d78ba34cf000cc7d5ff57e8f99b679d03d064540
ansible 2.1.0
config file = /dev/null
configured module search path = Default w/o overrides

CONFIGURATION

export ANSIBLE_CONFIG=/dev/null

OS / ENVIRONMENT

OSX 10.11.4
python 2.7.11 (homebrew)

SUMMARY

While migrating some playbooks to Ansible 2.0 i found some inconsistencies between different ansible versions, and most importantly in the same version depending of the syntax chosen.

Attached you while find a complete example with variations over the same theme, running the same role multiple times.

STEPS TO REPRODUCE

# the example code is attached
cd example
ansible-playbook -i inventory test1.yml
ansible-playbook -i inventory test2.yml
ansible-playbook -i inventory test3.yml

example.zip

EXPECTED RESULTS

All three playbooks should return the same result.

ACTUAL RESULTS

Each ansible version tested return different results for playbooks that should be equivalent.
Issue 1:
Is it possible to keep a reference on a scene's object ?

When we do :

this.scene.add(meshObject);

When I make it, my object is add in the scene and it is "lost" in the property "children" which is an array.

I must search the object in the scene's property "children" to modify the object that I display.

I would like keep a link on this object and when I modify my object through this link I would modify directly the contents of the scene.

Like a say precedently I remarked that objects which are displayed are in scene's children property. isn't it possible to have a tree on this property to classify object.

By example I have several objects, some of them are cubes other are circles, and I would like classify them in the scene.

Like you can see on the following picture :

http://img526.imageshack.us/img526/893/treero.jpg

In this way I could apply a modification on all cubes easily without run all array's member. If I try to set it, the scene will be able to display objects or not ?

Issue 2:
Names of nodes are user-specified, and not guaranteed to be unique within a glTF file. But because THREE.PropertyBinding relies on track names to target animation, having two nodes with the same name will cause animation to affect the wrong part of a model. We should de-duplicate node names on import, to ensure that every node ends up with a unique name.

Filing to follow up on https://discourse.threejs.org/t/gltf-animation-bug-or-wrong-usage/4536/2.
Issue 1:
Preflight Checklist

I have read the Contributing Guidelines for this project.

I agree to follow the Code of Conduct that this project adheres to.

I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Problem Description

The current ipcRenderer API appears to be similar to the NodeJS EventEmitter API. However, the ipcRenderer docs list neither an addListener() method nor a off() method. The NodeJS EventEmitter API supports both addListener() and removeListener(), as well as respective on() and off() methods which act as aliases.

Furthermore, the methods addListener() and off() appear to be callable on ipcRenderer despite being undocumented, and no not throw any errors, leading to additional confusion.

Proposed Solution

If the addListener() and/or off() methods are already implemented on ipcRenderer, The ipcRenderer documentation should be updated to reflect this. If they are not implemented, they should either be implemented, or alternatively, some warning should be given to developer that they are either not implemented or are deprecated (e.g. via a message in the console).

Finally, although it could be argued that the presence of aliased functions in the NodeJS EventEmitter class causes confusion for developers, I would argue that having one function for adding listeners in one style (on) and one function for removing listeners in another style (removeListener) in Electron without clear documentation makes for a far less desirable developer experience.

Alternatives Considered

If there is really no desire to implement additional/aliased functions (assuming they do not already exist but are undocumented) in the ipcRenderer API, the API should at least be made consistent by implementing either on and off OR addListener and removeListener and not both, and deprecating the function to be removed from the different style with accompanying notices made available to developers.

Additional Information

I came across this issue/request while trying to debug a weird issue with React and Electron ipcRenderer events. The confusion between styles for adding/removing event listeners has exacerbated time spent debugging this other problem. For more info, see: https://stackoverflow.com/questions/60158863/spooky-action-at-a-distance-electron-react-useeffect-unable-to-unsubscribe

Issue 2:
Preflight Checklist

I have read the Contributing Guidelines for this project.

I agree to follow the Code of Conduct that this project adheres to.

I have searched the issue tracker for an issue that matches the one I want to file, without success.

Issue Details

Electron Version:

8.0.3

Operating System:

Win 7

Last Known Working Electron version:

unknown

Expected Behavior

Relative windows should not been closed when main window is closed.

Actual Behavior

Relative windows will be closed when main window is closed.

To Reproduce

Load a page in main window.

Click a link or use js window.open to open a new window.

Close the main window. The new popup window will be closed immediately.
Issue 1:
System information (version)

OpenCV => 3.1

Operating System / Platform => Linux Mint

https://www.virustotal.com/de/file/24bda432eaace9e992322dcc3d30144cefa5314c2424d4aa02e5fe3fa9dd17bd/analysis/1535208210/

Why u is there a trojan downloader ?! I do not appreciate it!

Detailed description

Avast: JS:Downloader-DZB [Trj]

AVG : JS:Downloader-DZB [Trj]

cyren : ZIP/Trojan.JDGB-6

Qihoo360 : Script/Trojan.Downloader.3f1

Steps to reproduce

Issue 2:
System information (version)

OpenCV => 3.2

Operating System / Platform => Windows

Compiler => -

Detailed description

Avast detects JS: Downloader-DZB [Trj] virus in OpenCV 3 (.exe file).

Steps to reproduce

I downloaded the OpenCV for Windows file (version 3.2) from http://opencv.org/downloads.html -> https://sourceforge.net/projects/opencvlibrary/files/opencv-win/3.2.0/opencv-3.2.0-vc14.exe/download

File: open-cv-3.2.0-vc14.exe.

I ran Avast Antivirus on the downloaded file and received a virus report: JS: Downloader-DZB [Trj] Specifically found in: open-cv-3.2.0-vc14.exe>opencv\sources\modules\ts\src\ts_gtest.cpp
Issue 1:
Bug report

Describe the bug

I have a monorepo usecase, where I want to share code between the next app and other modules that are located outside of the app folder.

It will end up with this error:

{ Error: (client) ../foo.ts 1:0
Module parse failed: The keyword 'interface' is reserved (1:0)
You may need an appropriate loader to handle this file type.
> interface Foo {
| prop: string;
| }
@ ./pages/index.tsx 4:0-28 8:5-8
@ multi ./pages/index.tsx

To Reproduce

I have set up a simple repo here, based on the next-typescript example:

https://github.com/Swatinem/next-monorepo/tree/master

Expected behavior

Whatever I import should be transpiled like everything else, period.

System information

OS: linux

Version of Next.js: next@7.0.2

Additional context

Related issue (possibly a duplicate?): vercel/next-plugins#234

Also related maybe:

#706

#3018

Issue 2:
Now some of us ships NPM packages (specially components) written in ES2015 without transpiling them.

That's a pretty good thing specially if they are gonna used in a project like Next.js or CRA (which does transpiling). They offer benefits like:

No need to transpile before shipping to NPM

Get the benefit of Webpack 2's tree-shaking

But we can't do this now we exclude everything inside node_modules from babel transpiling.

So, here's the proposed solution.

We have an entry in next.config.js to include modules which needs to go through babel. See:

module.exports = {
transpileModules: [
"my-component",
"redux/src"
]
}
Issue 1:
I tried to implement React Helmet for our project and noticed a bug when running in production mode.

React Helmet doesn't initialize on the very first request after starting the application. But it initializes correctly on each subsequent request (SSR & CSR).

I cloned the minimal with-react-helmet example and I can confirm that the issue appears there, too.

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

Expected Behavior

React Helmet should initialize correctly on the first request that was made.

Current Behavior

As described above, React Helmet doesn't initialize correctly on the very first request.

Steps to Reproduce (for bugs)

Clone with-react-helmet

npm install

npm run build

npm start

Check the DOM/page source

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

I need to support some older browsers, so I would like to always include some polyfills (Intl, Object.assign and Promise) in the app bundle and just execute them if need (I've tried to do it conditionally, but it fails in a lot of situations), but I can't figure out the way to do it. Has anybody did this o has an idea on how can I do it?
Issue 1:
For per-1.0 version, linear progress component has a consistent API with circle progress component, where the range of the progress can be set with 'max' and 'min' props. These APIs have been removed in 1.0, but it wasn't explicitly stated, and it was only implied in the examples that the value props linear progress now takes should be between 0 and 100. This causes a little confusing and unnecessary digging for those who migrated from pre 1.0 or new users who try to use both progress components.

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

Expected Behavior

Linear Progress and Circle Progress to have a consistent API implementation (with or without 'max/min' props')

Current Behavior

Linear Progress only takes value prop, while Circle Progress accepts max/min.

Steps to Reproduce (for bugs)

Use a simple component like this one below.

<LinearProgress mode='determinate' max={totalSeconds} min={0} value={totalSeconds - timePassed} />

If I start with a total seconds > 100, I would not see the linear progress bar moving until the last two minutes.

Context

I am trying to give user different views that use different progress bars.

Your Environment

Tech
Version

Material-UI
1.0.0-beta.18

React
16

browser

etc

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

Expected Behavior

LinearProgress and CircularProgress should accept min, max and value props.

When mode is 'determinate', the progress is calculated based on value between a scale of min to max.

If min and max are not supplied, they default to 0 and 100 respectively (original behavior).

inlineStyles.primary.transform = 'scaleX(' + ((value - min) / (max - min)) + ')';

Current Behavior

LinearProgress and CircularProgress accepts value prop.

When mode is 'determinate', the progress is calculated based on value between a scale of 0 to 100.

inlineStyles.primary.transform = 'scaleX(' + value / 100 + ')';

Context

This would simplify components that utilize LinearProgress and CircularProgress as parent components would no longer be responsible for scaling values between 0 and 100. I find it's pretty rare to have data already suitable for the progress components because it's not normally between 0 and 100.

Your Environment

Tech
Version

Material-UI
1.0.0-beta.18

React
16.0.0
Issue 1:
Yesterday, there was a file, server.ts that existed.

Today, it doesn't exist.

https://deno.land/std@v1.0.0-rc2/http/server.ts

Navigating to this URL makes it seem like there is a file server.ts

https://deno.land/std@v1.0.0-rc2/http/

It looks like all files are returning 404s.

What is wrong?

Issue 2:
Steps to reproduce

Delete ~/.cache/deno

Clone https://github.com/KSXGitHub/deno-args

Run deno cache --unstable **/*.ts

Expected behavior

It runs without error

Actual behavior

404 Not Found.
Issue 1:
Bug report

What is the current behavior?

Assume we have two projects with only index.js files in them, which are having same content:

and this webpack config:

module.exports = {
mode: 'production',
cache: {
type: 'filesystem'
},
infrastructureLogging: {
level: 'info',
debug: /webpack\.cache.*/,
},
entry: `./${process.env.SRC_DIR}/index.js`,
plugins: [
new MiniCssExtractPlugin({ filename:'styles.[chunkhash].css' })
],
output: {
pathinfo: false,
},
module: {
rules: [{
test: /\.(js|jsx)$/,
loader: 'babel-loader',
options: {
"plugins": [
"syntax-dynamic-import",
"@babel/plugin-proposal-class-properties"
],
"presets": [
[
"@babel/preset-env",
{
"modules": false
}
],
"@babel/preset-react"
]
}
}]
},

optimization: {
minimizer: [new TerserPlugin({

})],
}
}

After cache warmup with webpack5-1 repo we build first webpack5-1 and then - webpack5-2

warmup time:

webpack 5 - 1 (warmup) : 5.05401289999485 seconds

Full compilation time with cache is then following:

webpack 5 - 1: 0.8312232999801635 seconds
webpack 5 - 2: 1.4813145999908448 seconds

After that, if we not delete .cache folder and again build webpack5-1 and then - webpack5-2 then builds aree took almost the same time

webpack 5 - 1: 0.8569822000265122 seconds
webpack 5 - 2: 0.9038357999920845 seconds

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

Reproducing steps in readme section of repo https://github.com/SkReD/webpack5-performance-issue/tree/cache-share-problem

What is the expected behavior?

Expect compilation time to be almost the same for both webpack5-1 and webpack5-2 with cache from the first one.

Other relevant information:

webpack version: 5.38.1

Node.js version: 14.17.0

Operating System: windows 10 x64

Additional tools:

Issue 2:
Feature request

What is the expected behavior?

right now cache writes absolute paths

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

if all paths will be relative to cache folder it will allow to share cache

How should this be implemented in your opinion?

Did not investigate this, yet

Are you willing to work on this yourself?

Yes
Issue 1:
Migrated issue, originally created by Anonymous

inserting multiple rows using single list of row values doesn't work, ex.

conn.execute("insert into users (user_id, user_name) values (?, ?)", [(10,"donkey")]((9,"barney"),))

or

conn.execute("insert into users (user_id, user_name) values (%s, %s)", [[4,"ed"]([4,"ed"), [5,"horse"](5,"horse")])

Attached patch fixes this.

Issue 2:
I have a specific model configuration where queries using limit() on a relationship are not returning the expected number of rows.

In this example, staff is defined as a relationship on the School model as such:

staff = db.relationship( 'User', secondary='grant', primaryjoin='School.id==Grant.school_staff_target_id', secondaryjoin='Grant.user_id==User.id', lazy='dynamic', backref='schools_staff' )

Getting all rows with this query returns two rows, as expected:

staff = School.query.filter_by(id='5d2ab3bb1f28426f8148e47543b1cbee').one()\ .staff.filter_by(deleted=False).all()

This query, using limit(2), only returns one row:

staff = School.query.filter_by(id='5d2ab3bb1f28426f8148e47543b1cbee').one()\ .staff.filter_by(deleted=False).limit(2).all()

Whereas this query, using limit(3), returns both rows (expected):

staff = School.query.filter_by(id='5d2ab3bb1f28426f8148e47543b1cbee').one()\ .staff.filter_by(deleted=False).limit(3).all()
Issue 1:
To completely fix #1587 TypeScript should also support:

function repro(message: Object | Object[]) {
if (message instanceof Array) {
message = message.filter; // error
}
}

Currently it results in Property 'entries' does not exist on type 'Object | Object[]'. It seems message on the RHS switches from Array back to Object | Object[] prematurely.

Workaround:

function workaround(message: Object | Object[]) {
var theMessage = message;
if (theMessage instanceof Array) {
message = theMessage.filter;
}
}

Issue 2:
TS 1.4

Type guard fails to narrow the union type when returning early.

function foo(x: number | string) {
if (typeof x === 'string') {
return;
}
// x should now be a number
if (2 % x !== 0) {
// do something
}
}

Unfortunately, I get the following compiler error:

The right-hand side of an arithmetic operation must be of type 'any', 'number' or an enum type.

Clearly, the compiler should know at this point that it can't possibly be dealing with a string, as that scenario has already been returned.
Issue 1:
Vue.js version

2.0.3

Reproduction Link

https://jsbin.com/lurayuxofo/edit?html,js,console,output

Steps to reproduce

Include inline SVG with some styles within a Vue instance

Init vue instance

What is Expected?

SVG to be styled according to the style element

What is actually happening?

Vue is giving a warning "[Vue warn]: Templates should only be responsible for mapping the state to the UI. Avoid placing tags with side-effects in your templates, such as <style>. " and also stripping the style element so the SVG is appearing with no style.

Issue 2:
What problem does this feature solve?

From compiling template error message:

Component template should contain exactly one root element. If you are using v-if on multiple elements, use v-else-if to chain them instead.

But Cannot use as component root element because it may contain multiple nodes.

So I can't use <template> as component root element even if it contains only one node.

What does the proposed API look like?

Allow the following code as component root.

<template v-if="conditionA">
<div v-if="conditionC"></div>
<div v-else-if="conditionD"></div>
<div v-else></div>
</template>
<template v-else>
<div></div>
</template>

Do not allow the following code as component root.

<template>
<div v-if="conditionA"></div>
<div v-if="conditionB"></div>
</template>
Issue 1:
Migrated issue, originally created by Elliot Cameron (@3noch)

I'm using PostgreSQL and trying to build an array aggregate of tuples by selecting a column like this:

sa.func.array_agg(sa.func.row(User.id, User.name))

This parses as an ugly list of characters.

Putting the "row" on the outside works.

sa.func.row(sa.func.array_agg(User.id), sa.func.array_agg(User.name))

Maybe I'm missing something.

Issue 2:
Migrated issue, originally created by Michael Bayer (@zzzeek)

that is, all the functions in http://www.postgresql.org/docs/9.4/static/functions-json.html need to be possible without building subclasses of functions.