WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Q
A

Bug report?
yes

Feature request?
no

BC Break report?
no

RFC?
no

Symfony version
3.4.6

This is the symfony/standard-edition with the reproducible error.

Am I misunderstanding #23239, or is supposed that autowired controllers should call setContainer()?

$ ./vendor/bin/simple-phpunit --filter OtherControllerTest
PHPUnit 6.5.7 by Sebastian Bergmann and contributors.

Testing Project Test Suite
E 1 / 1 (100%)

Time: 350 ms, Memory: 14.00MB

There was 1 error:

1) Tests\AppBundle\Controller\OtherControllerTest::testOther
Error: Call to a member function getParameter() on null

vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Controller/Controller.php:40
src/AppBundle/Controller/DefaultController.php:18
src/AppBundle/Controller/OtherController.php:16
vendor/symfony/symfony/src/Symfony/Component/HttpKernel/HttpKernel.php:151
vendor/symfony/symfony/src/Symfony/Component/HttpKernel/HttpKernel.php:68
vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php:202
vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Client.php:68
vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Client.php:131
vendor/symfony/symfony/src/Symfony/Component/BrowserKit/Client.php:312
tests/AppBundle/Controller/OtherControllerTest.php:13

Issue 2:
I'm on symfony 2.3.3 and I have a big problem with form embedded.

I followed http://symfony.com/doc/current/cookbook/form/form_collections.html and,

the calling of {{ form_widget(form.tags.vars.prototype)|e }} return an empty string and if I debug form.tags.vars.prototype, I have a FormView object.

could somebody help ?
Issue 1:
Example here: http://is.gd/LKsPyZ

enum Foo {
Bar(u8)
}

fn main() {
let x = Foo::Bar as u32;
println!("{:?}", x);
}

In rust 1.0.0 stable, rustc prints "LLVM ERROR: expected relocatable expression"

In nightly, it currently compiles and when run, the application prints "3964760960"

Issue 2:
rustc 0.13.0-dev (222ae8b 2014-10-18 00:47:22 +0000)

enum Tag {
Dynamic,
Inline(u8),
Static,
}

#[test]
fn f() {
assert_eq!(Inline as uint, 1);
}

compiles and produces

task 'f' failed at 'assertion failed: `(left == right) && (right == left)` (left: `140041300628448`, right: `1`)', foo.rs:9

I think it's casting the constructor function itself as a function pointer? But this is super confusing behavior (caused a segfault in unsafe code) when I just refactored an enum to be not C-like and I want to get rid of remaining occurrences of as uint.

Also it doesn't warn for as u8, even though it's too small for a function pointer.
Issue 1:
For example, the following code currently doesn't work.

<div id="ticket">
<select v-model="chosenTicket" options="ticketOptions">
<option value="">Choose...</option>
</select>
<button v-attr="disabled: !chosenTicket" v-on="click: resetTicket">Clear</button>
<p v-if="chosenTicket">You have choosen <b>{{chosenTicket.name}}</b>(${{chosenTicket.price}})</p>
</div>

new Vue({
el: "#ticket",
data: {
tickets: [
{ name: "Economy", price: 199.95 },
{ name: "Business", price: 449.22 },
{ name: "First Class", price: 1199.99 }
],
chosenTicket: null
},
computed: {
ticketOptions: function() {
return this.tickets.map(function(ticket){
return {text: ticket.name, value: ticket};
});
}
},
methods: {
resetTicket: function() {
this.chosenTicket = null;
}
}
});

knockout.js supports this and it is extremely useful for data binding of cascading dropdowns.

Like http://knockoutjs.com/examples/cartEditor.html

Issue 2:
When using the {text:'', value:''} format for dynamic <select> options it becomes complex to get the text back out again for display since the v-model binds the value. One must then run a computed property and filter the options again and... you get the point.

Would it be possible to to support a syntax like this?

options: [
{this: 'This One'},
{that: 'That One'}
]

Which would then let us get that value back out like this.options[this.selected]. Just an idea. Feel free to say nay.
Issue 1:
Hey,

I hope that I did not made major flaws but I can not find a mistake. The output of argrelextrema() is always an empty numpy array.

import numpy as np
from scipy.signal import argrelextrema

dat = np.genfromtxt("numbers.dat")
print argrelextrema(dat[:], np.greater, order=6)

(array([], dtype=int64),)

numbers.dat contains a list of 50 testvalues containing a maximum. I also tested several values for the order parameter

78.75
81.0
83.25
85.5
87.75
89.25
91.5
93.0
94.5
96.75
98.25
99.75
101.25
102.0
103.5
104.25
105.75
106.5
107.25
108.0
108.75
108.75
109.5
109.5
109.5
109.5
109.5
109.5
109.5
108.75
108.75
108.0
107.25
106.5
105.75
105.0
104.25
102.75
102.0
100.5
99.0
97.5
96.0
94.5
93.0
90.75
89.25
87.0
84.75
82.5

Thanks for any comments!

Stephan

Issue 2:
Scipy documentation lists scipy.sparse.dok_matrix as having three methods that return iterators:

iteritems()

iterkeys()

itervalues()

None of these seem to exist. Example:

from scipy import sparse
A = np.random.rand(100,100)
As = sparse.dok_matrix(A)
As.iteritems() #<------ This raises an AttributeError: iteritems not found.
Issue 1:
Starting in julia 1.4, the Warning disappeared from Profile when you've overrun the profile buffer:

On 1.3:

julia> using Profile

julia> Profile.init(n=10, delay=0.000001) # Definitely going to run out of buffer

julia> @profile for _ in 1:10 peakflops() end

julia> Profile.print()
┌ Warning: The profile data buffer is full; profiling probably terminated
│ before your program finished. To profile for longer runs, call
│ `Profile.init()` with a larger buffer and/or larger delay.
└ @ Profile /Users/julia/buildbot/worker/package_macos64/build/usr/share/julia/stdlib/v1.3/Profile/src/Profile.jl:312
┌ Warning: There were no samples collected. Run your program longer (perhaps by
│ running it multiple times), or adjust the delay between samples with
│ `Profile.init()`.
└ @ Profile /Users/julia/buildbot/worker/package_macos64/build/usr/share/julia/stdlib/v1.3/Profile/src/Profile.jl:667

On 1.4:

julia> using Profile

julia> Profile.init(n=10, delay=0.000001) # Definitely going to run out of buffer

julia> @profile for _ in 1:10 peakflops() end

julia> Profile.print()
┌ Warning: There were no samples collected. Run your program longer (perhaps by
│ running it multiple times), or adjust the delay between samples with
│ `Profile.init()`.
└ @ Profile /Users/julia/buildbot/worker/package_macos64/build/usr/share/julia/stdlib/v1.4/Profile/src/Profile.jl:851

Obviously the above is a silly example, but this has definitely led to some wasted time in practice trying to understand a profile that doesn't make sense, only to eventually realize that the buffer must not have been big enough!

Can we add this Warning back to the package? It is very useful and should be cheap to perform.

Even better, can we also add a runtime check to print such a Warning as soon as the buffer fills up, during profiling? This way we can know to kill our profiling process and adjust the buffer, and re-run, shortening the developer loop.

I've been meaning to file an issue about this for a long time. I'm sorry it took me so long to do! :) Thanks for all your hard work and these very useful tools! ❤️ !

Issue 2:
The Regex docs provide indexing with Symbol, where the symbol is the name of the capture group.

What is lacking is a way to retrieve the capture group names from either a Match or just the Regex itself (from the docs).

s = "aaa bbb ccc"
r = r"(?<a>.*) (?<b>.*) (?<c>.*)"
m = match(r, s) # I don't think there is a way to retrieve the symbols [:a, :b, :c] from this or `r`

One has to know about Base.PCRE.capture_names(m.regex.regex).

The context in which this arose was wanting to easily construct a DataFrame from a Vector{RegexMatch} where the capture group names become the column names. Thanks to @pdeffebach for finding the capture_names function for me.

This should be a simple PR to add a line to https://docs.julialang.org/en/v1/manual/strings/#Regular-Expressions mentioning it.

I may get to it, I may not xd
Issue 1:
I have a DaemonSet configured as follows:

daemonset.yaml

apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
name: bugreport-daemonset
spec:
template:
metadata:
labels:
app: bugreport
spec:
containers:
- name: bugreport-container
image: gcr.io/bug-project/testcontainer:tag0
imagePullPolicy: Always
ports:
- containerPort: 80

When I run kubectl apply -f daemonset.yaml i can see the pods running on each node.

But if I change the image to gcr.io/bug-project/testcontainer:tag1 and then run kubectl apply -f daemonset.yaml again, the pods are never updated with the new container image.

Issue 2:
Hi,

Sorry for doing it in the wrong order as mentioned here : https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md#contributing-a-patch

I did #22439 to address this problem (on kubectl side)

The need is to be able to update a daemon set in a single command line.

Basically it is equivalent to do :

kubectl delete -f dsfile --cascade=false
kubectl create -f dsfile
for pod in pods
kubectl delete pod
wait for delete

EDIT : @bgrant0607 suggested to update the ds instead of delte / recreate
Issue 1:
What / Why

npm keeps creating its cache directory in my $HOME. I keep very few directories in my $HOME to keep things findable, and its very annoying when apps start littering stuff there.

When

Any time I run things like npm install blah.

Where

$ uname -srmo
Linux 5.7.2-arch1-1 x86_64 GNU/Linux

How

Current Behavior

A directory is creted in $HOME and cache data stored in there.

Steps to Reproduce

Run rm -rf .cache to delete your existing cache.

Navigate to a directory with an existing package.json.

Run npm install.

Expected Behavior

The cache directory should be in $XDG_CACHE_HOME on Linux. Specifically, it should be $XDG_CACHE_HOME/npm. $XDG_CACHE_HOME should default to .cache if undefined.

I believe on macOS there's a different spec for default locations, and things like cache are stored in a different place. I don't know the name of the spec so can't easily link in here.

Who

n/a

References

XDG Base Directory Specification

Issue 2:
Is there an existing issue for this?

I have searched the existing issues

Current Behavior

I'm trying to link 2 packages and I know this worked at some point in the past. The current process is running the following commands one after another

npm link guidemaker
npm link guidemaker-default-template

after the first link guidemaker is linked correctly, but after you run the second link it removes the link to guidemaker and only has the link to guidemaker-ember-template

while I was writing this section I wondered if the problem was running them "one after another" and I tried

npm link guidemaker guidemaker-default-template

which happened to work 🙈

Expected Behavior

I expect that running link twice with two different packages should just link both those packages. It's nice to have the workaround that I described above but this is quite confusing for people.

I know that there are existing issues around running npm install removing links but that isn't related to the expected behaviour that I have for this feature.

Steps To Reproduce

checkout and run npm link in guidemaker (or any npm package)

checkout and run npm link in guidemaker-default-template

go to a new node project with a package.json (ember app in my case)

run npm link guidemaker

run npm link guidemaker-default-template

Environment

OS: macOS 11.4

npm: '7.20.0',

node: '12.18.1',
Issue 1:
When using the conventional webpack 2+ dynamic imports, everything works great in dev but breaks in production (with builds).

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

Expected Behavior

Current Behavior

A bug: dynamic imports should work in production as well as they do in development.

Steps to Reproduce (for bugs)

Pull down this example nextjs app to reproduce

yarn dev to see it working in dev

yarn build then yarn start to spin up the production build

Context

I am trying to code-split my app and some of my dynamic imports are NOT components. So using next/dynamic is not appropriate...

Your Environment

Tech
Version

next
5.1.0 (latest)

node
9.7.1

OS
mac

browser
chrome

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

my config (tidied)

// next.config.js
import HtmlWebpackPlugin from 'html-webpack-plugin';
import FaviconsWebpackPlugin from 'favicons-webpack-plugin';

module.exports = {
webpack: (config, { dev }) => {
config.plugins.push(
new FaviconsWebpackPlugin({
logo: './static/assets/images/favicon.png',
inject: true,
}),
new HtmlWebpackPlugin(),
);

return config;
},
};

// pages/_document.js
import React from 'react';
import Document, { Head, Main, NextScript } from 'next/document';

export default class SmediaDocument extends Document {
render() {
return (
<html lang="en">
<Head>
<meta charSet="utf-8" />
<meta content="IE=edge" httpEquiv="X-UA-Compatible" />
<meta content="width=device-width,initial-scale=1" name="viewport" />
<title>Schoenwald.media</title>
<meta name="description" content="Thoughts on CSS, JS, and overall clean code." />
</Head>
<body>
<Main />
<NextScript />
</body>
</html>
);
}
}

I'd expect that the favicons-webpack-plugin generates the icons, and the html-webpack-plugin inject it in the <head/> of the page. Which it doesn't.

Steps to Reproduce

Checkout https://github.com/schoenwaldnils/blog

Set up .envfile with

HOST=localhost
PORT=3000

docker-compose up

Environment

Tech
Version

next
~4.0.0-beta.4

html-webpack-plugin
~2.30.1

favicons-webpack-plugin
0.0.7

node
8.4.0

OS
mhart/alpine-node:8.4.0
Issue 1:
I'm writing a new PowerShell script, and I want to make use of unicode emojies, which are now supported by the new Windows Terminal Preview. However, for a user running "legacy" PowerShell that doesn't support it, I do not wish to show the unrecognized characters, and instead I would like to show him some other text/sign.

To be more simple - I would like to know when my PS script is running in the new Terminal and show one thing and show something else for other PS terminals.

I have tried using $env:TERM_PROGRAM. If I use is inside the vscode PS terminal it returns "vscode", but under normal PS terminal or new terminal it returns nothing.

Any ideas?

Issue 2:
Summary of the new feature/enhancement

Maybe this is as simple as an environment variable like VSCode uses for its terminal e.g. TERM_PROGRAM=WindowsTerminal / TERM_PROGRAM_VERSION=0.0.1.0.

Proposed technical implementation details (optional)

Start by creating the environment variables above so those of us using PowerShell can adapt our user experience (via PowerShell profiles) to Windows Terminal.
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

<meta charset="utf-8"> should be the first element in the <head>

Current Behavior

<NextScript /> prepends the preloadDynamicChunks in the head.

https://github.com/zeit/next.js/blob/canary/server/document.js#L87

Context

https://sonarwhal.com/docs/user-guide/rules/meta-charset-utf-8/

Your Environment

Tech
Version

next
4.1.3

node
8.4.0

Issue 2:
Bug report

Describe the bug

When using experimental.publicDirectory and dynamic routing with the following setup

/pages
[slug].js
/public
robots.txt

If you hit /robots.txt:

On dev server it resolves to the [slug].js page

On build server it resolves to the robots.txt file

To Reproduce

Described above

Expected behavior

I would expect dev-server to also resolve that route to the robots.txt file.

System information

OS: macOS

Version of Next.js: 9.0.2
Issue 1:
Bug report

Describe the bug

Some Link components stops working in development and production

To Reproduce

here is a live example https://frontend-e4m1qf1rc.now.sh/ (note: there is popup ads, i hope you have an adblock)

1- Click on any news article, if you click on the home Link or the Logo link in the header, everything works as expected.

but when clicking on a news article, and refresh the page, and clicking on the home Link, the Link freezes and it's not routing to the proper route

2- This also occurs when going directly to a news article from a full url(domaine.com/news/some-slug)

Expected behavior

for the Link components to route to the desired route without freezing

Screenshots

this is how i use Link for those non-working routes:

<Link href="/" prefetch>
<a className={classes.homeLink} title="home">
home
</a>
</Link>

System information

Browser: chrome 75.0.3770.100 64bit

Version of Next.js: 9.0.2

Issue 2:
In my app, I have a series of QueryRenderers (some nested inside each other) that are pulling data. When I disable javascript in my browser, I expect it to render the full page properly on the server, and give it to me, however, this does not happen.

Posted here, since I think this is a problem centric to the server-side render, and not specifically relay.

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

Expected Behavior

Server side should render the full app, after all the QueryRenderer calls complete.

Current Behavior

It appears that after the fetch, the QueryRenderer#render prop is not called again on the server.

Steps to Reproduce (for bugs)

Add relay and a working query renderer to your app

Have the result just output the result as text

Disable javascript in your browser

Reload the page, you won't see the result text.

Context

Your Environment

Tech
Version

next
5.0.0

node
8.9.4

OS
osx sierra 10.12.6

browser
Chrome Version 66.0.3359.117 (Official Build) (64-bit)
Issue 1:
The bug #9362 is available.

ISSUE TYPE

Bug Report

COMPONENT NAME

templar

ANSIBLE VERSION

Ansible: 2.4.3.0

python version = 3.6.2 |Anaconda custom (64-bit)| (default, Jul 20 2017, 13:14:59) [GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.57)]

STEPS TO REPRODUCE

x: 0
a:
b: 1
s:
t:
u: 2

ACTUAL RESULTS

TASK [debug] ********************************************************************************************************************************
ok: [local] => {
"x": 0
}

TASK [debug] ********************************************************************************************************************************
ok: [local] => {
"a.b": "1"
}

TASK [debug] ********************************************************************************************************************************
ok: [local] => {
"s.t.u": "2"
}

CONFIGURATION

OS / ENVIRONMENT

SUMMARY

EXPECTED RESULTS

Issue 2:
Issue Type: Bug Report

Ansible Version: 1.9.0.1

Environment: Ubuntu 14.04

Summary:

When 2 roles using the same transitive dependency (more than 1 level deep) are applied to a single host, the transitive dependency is applied only once.

Steps To Reproduce:

I have 4 roles:

postgresql_third_party : from Ansible Galaxy, install and configure an instance of PostgreSQL

roles/postgresql_commons/meta/main.yml : commons settings for my projects

# allow_duplicates: yes
dependencies:
- postgresql_third_party

roles/postgresql_db1/meta/main.yml: creates a database named DB1

# allow_duplicates: yes
dependencies:
- { role: postgresql_commons, db_name: DB1 }

roles/postgresql_db2/meta/main.yml: creates a database named DB2

# allow_duplicates: yes
dependencies:
- { role: postgresql_commons, db_name: DB2 }

Enabling or disabling allow_duplicate does not change anything when executing the playbook:

- name : Install multiple DB on a single instance of PostgreSQL
hosts: db
sudo: true
roles:
- postgresql_db1
- postgresql_db2

Expected Results:

I would expect that the third party role is executed twice, once for DB1 and the other for DB2. The end result would be the creation of the 2 databases.

Actual Results:

The role is applied only once. Only the first database is created.
Issue 1:
When long pressing the windows key using Power tools to display the Shortcut Guide, a few of shortcuts are missing.

Windows C = Cortana

Windows F = Feedback Hub

Windows P = Presentation mode choices

Windows V = Clipboard History

Could these be added please.

Issue 2:
##Move/copy queue

Moving or copying files/folders from multiple locations to the same location gets slower and slower for each source added. It would be great to have a queue that you can add more sources to and prioritize the order in.

If you'd like to see this feature implemented, add a 👍 reaction to this post.
Issue 1:
At present, the draw order order in 3D plots is determined exclusively by sorting the values returned by calling do_3d_projection() in each collection/patch:

matplotlib/lib/mpl_toolkits/mplot3d/axes3d.py

Lines 294 to 307
in
40583b0

# Calculate projection of collections and patches and zorder them.

# Make sure they are drawn above the grids.

zorder_offset = max(axis.get_zorder()

for axis in self._get_axis_list()) + 1

for i, col in enumerate(

sorted(self.collections,

key=lambda col: col.do_3d_projection(renderer),

reverse=True)):

col.zorder = zorder_offset + i

for i, patch in enumerate(

sorted(self.patches,

key=lambda patch: patch.do_3d_projection(renderer),

reverse=True)):

patch.zorder = zorder_offset + i

However, this sorting is not always ideal and a common issue reported by users. I'd propose adding a "force_zorder" optional parameter to Axes3D (defaulting to False) that would ignore the above calculation and instead use the zorder already stored in each collection/patch, i.e.

if self.force_zorder:
for col in self.collections:
col.zorder = zorder_offset + col.zorder
for patch in self.patches:
patch.zorder = zorder_offset + patch.zorder
else:
# current code

This keeps existing behavior as default, but allows users to override that behavior. This does allow users to specify duplicate or negative zorders, as they can in 2D plots, but that hasn't generated errors in my testing.

However, not being at all familiar with the deeper workings, I'd rather get comments/concerns from the matplotlib maintainers and contributors before setting off to produce a full pull request.

Thanks!

Issue 2:
Bug report

Bug summary

ImageGrid seems to be broken on 3.0.0?

Code for reproduction

f = plt.figure()
grid = ImageGrid(f, 111,
nrows_ncols=(2, 2),
direction='column',
label_mode="L",
cbar_location="right",
cbar_mode="single",
cbar_size="5%",
cbar_pad="3%"
)
axarr = np.array(grid).reshape(2, 2)
for ax in axarr.flatten():
m = ax.imshow(np.random.random(15**2).reshape((15, 15))+0.5,
norm=LogNorm(vmax=2, vmin=0.5), cmap='coolwarm')
plt.colorbar(m, cax=grid.cbar_axes[0], format=FormatStrFormatter('%.2f'))

Actual outcome

Expected outcome

From 2.2.2

Note: if I remove all colorbar-related code, it again looks weird, but in a different way:

f = plt.figure()
grid = ImageGrid(f, 111,
nrows_ncols=(2, 2),
direction='column',
label_mode="L",
)
axarr = np.array(grid).reshape(2, 2)
for ax in axarr.flatten():
m = ax.imshow(np.random.random(15**2).reshape((15, 15))+0.5,
norm=LogNorm(vmax=2, vmin=0.5), cmap='coolwarm')

Seems like maybe all axes take up the whole figure, and so cover the rest?.. Just a guess.

Matplotlib version

Operating system: Ubuntu 16.04

Matplotlib version: 3.0.0

Matplotlib backend (print(matplotlib.get_backend())): inline

Python version: 3.5.2

Jupyter version (if applicable): Jupyter Lab 0.33.6
Issue 1:
JavaScript file at https://deno.land/x/once/index.js has a Triple-Slash Directive that define location of TypeScript definition:

/// <reference types="./index.d.ts" />

When I run deno fetch --reload https://deno.land/x/once/index.js, I expect Deno to also fetch index.d.ts but it does not.

This issue was suspected to be the cause of https://github.com/axetroy/vscode-deno/issues/102.

Issue 2:
$ deno fetch https://cdn.pika.dev/date-fns
Download https://cdn.pika.dev/date-fns
Download https://cdn.pika.dev/-/date-fns@v2.9.0-si0G7GvbRjRynVZsHhan/dist=es2019/date-fns.js

$ deno run mod.ts
Compile file:///Users/name/gpm/github.com/axetroy/deno_dnx/mod.ts
Download https://cdn.pika.dev/date-fns
Download https://cdn.pika.dev/-/date-fns@v2.9.0-si0G7GvbRjRynVZsHhan/dist=es2019/date-fns.js
Download https://cdn.pika.dev/-/date-fns@v2.9.0-si0G7GvbRjRynVZsHhan/dist=es2019/types/index.d.ts
Download https://cdn.pika.dev/-/date-fns@v2.9.0-si0G7GvbRjRynVZsHhan/dist=es2019/types/index.d.ts