WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
There seem to be some performance regressions in compile time of NTuple in 1.0. Note, for example,

1.0:

using StaticArrays
julia> @time @SMatrix rand(16,16)
11.440824 seconds (1.41 M allocations: 85.987 MiB, 0.24% gc time)

0.6.4:

using StaticArrays
julia> @time @SMatrix rand(16,16);
1.330479 seconds (356.50 k allocations: 13.710 MiB)

We were speculating that this is due to #27398. While it doesn't seem unreasonable that the compiler really has to think about 256 type long signatures, we believe that the compiler may not know that all the types are guaranteed to be the same since (as far as I know) NTuple is nothing more than an alias.

Am I getting the story here correct? Would it be possible to make the compiler know that NTuple is promised to be homogeneous, but otherwise retain the current behavior?

I apologize if this is somehow duplicating or echoing existing issues, I wasn't able to find anything that addressed this directly.

(Thanks to @ChrisRackauckas for useful discussion on this.)

Issue 2:
I'd expect to be able to import with a depwarn, but get an error instead:

julia> import Base.Test: record
WARNING: Base.Test is deprecated, run `using Test` instead.
likely near no file:0
ERROR: invalid import path: "Test" does not name a module
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.0

Operating System version: windows

Java version: 1.8

zookeeper version: 3.4.6

Steps to reproduce this issue

使用zookeeper作为注册中心，开启ipv6的情况下，服务消费者始终找不到服务提供者，能帮忙给解决一下吗？

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 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.7.0

Operating System version: Windows7

Java version: jdk8

Steps to reproduce this issue

stop dubbo service

dubbo client set checked = true. do get cudbbo client for times.

the size of list field [urls] in ReferenceConfig wil increase

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

(project)[https://github.com/vio-lin/incubator-dubbo/tree/error-situation]

run java file

incubator-dubbo\dubbo-demo\dubbo-demo-xml\dubbo-demo-xml-consumer\src\main\java\org\apache\dubbo\demo\consumer\Application.java

Expected Result

the [urls] in ReferenceConfig will be updated.

Actual Result

the avalidable registery urls be add to [urls] in ReferenceConfig
Issue 1:
As you can see the CI was passing correctly before.

https://github.com/UltiRequiem/eloquent-javascript/commits/main

But since UltiRequiem/eloquent-javascript@a5f766e

While creating code coverage I'm getting this errors:

deno test --coverage=./cov

This step works as expected

deno coverage --unstable --lcov ./cov > cov.lcov

============================================================
Deno has panicked. This is a bug in Deno. Please report this
at https://github.com/denoland/deno/issues/new.
If you can reliably reproduce this panic, include the
reproduction steps and re-run with the RUST_BACKTRACE=1 env
var set and include the backtrace in your report.

Platform: linux x8[6](https://github.com/UltiRequiem/eloquent-javascript/runs/6168539434?check_suite_focus=true#step:8:6)_64
Version: 1.21.0
Args: ["deno", "coverage", "--unstable", "--lcov", "./cov"]

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: BadJson(Error("invalid unicode code point", line: 1, column: 2043))', cli/tools/coverage/mod.rs:1[7](https://github.com/UltiRequiem/eloquent-javascript/runs/6168539434?check_suite_focus=true#step:8:7)5:57
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

But as far I can see on UltiRequiem/eloquent-javascript@a5f766e there isn't any invalid unicode?

You can see it here too 👇🏽

https://github.com/UltiRequiem/eloquent-javascript/runs/6168539434?check_suite_focus=true

Issue 2:
Hi, I am having an issue where the output of deno coverage appears inaccurate. I was able to narrow it down to a minimal example; instructions below. I hope it is reproducible. The problem goes away if the emojis or the unused function h are removed. Removing a single emoji removes line 2 from the coverage report, but still inaccurately keeps line 3. I have not tested it with other emojis ☺️

This is the mod.ts file:

export default function () {
return "📣❓";
}

function h() {}

This is the mod_test.ts file:

import f from "./mod.ts";

Deno.test("test", () => {
f()
});

These are the shell commands:

deno test --coverage=.cov
deno coverage .cov
rm -rf .cov

This is the output of deno coverage. As far as I understand it, line 2 and 3 should be covered:

cover file:///home/mod.ts ... 25.000% (1/4)
2 | return "📣❓";
3 | }
-----|-----
5 | function h() {}

This is the output of deno --version:

deno 1.11.0 (release, x86_64-unknown-linux-gnu)
v8 9.1.269.35
typescript 4.3.2
Issue 1:
I want mymacro!(bar) to expand to fn foo_bar() { }.

#[feature(macro_rules)];

macro_rules! mymacro( ($x:ident) => (
fn concat_idents!(foo_, $x)() { }
))

mymacro!(bar)

fn main() {
foo_bar();
}

gives

foo.rs:4:21: 4:22 error: expected `(` but found `!`
foo.rs:4 fn concat_idents!(foo_, $x)() { }

on

rustc 0.9 (d3b3c66 2014-01-12 19:44:26 -0700)
host: x86_64-unknown-linux-gnu

Issue 2:
All of the examples below fail to compile with an error similar to the following:

test.rs:1:16: 1:17 error: expected ( but found !

test.rs:1 fn concat_idents!(foo, bar) () {}

^

fn concat_idents!(foo, bar) () {}

trait concat_idents!(foo, bar) {}

mod concat_idents!(foo, bar) {}

let concat_idents!(foo, bar) = 0;
Issue 1:
Directions say :Let's try this again, but with margin this time. Use Clockwise Notation to give an element a margin of 40 pixels on its top and left side, but only 20 pixels on its bottom and right side.

But criteria say

Your green-box class should give the top of elements 20px of margin.

Your green-box class should give the left of elements 40px of margin.

Your green-box class should give the bottom of elements 20px of margin.

Your green-box class should give the right of elements 20px of margin.

Accepts

margin:40px 20px 20px 40px;

So just need to correct the px in the criteria for match to 40px on top.

Cheers!

Issue 2:
In the instructions for the margin, you have the pixel setting for "Top" to 20px instead of 40px.
Issue 1:
Currently, any container runtime has to be linked into the kubelet. This makes experimentation difficult, and prevents users from landing an alternate container runtime without landing code in core kubernetes.

To facilitate experimentation and to enable user choice, we should add a client/server implementation of the container runtime interface.

This implementation will simply encode the requests, send them to a server where they will be decoded and sent into an instance of the container runtime interface.

However, this enables container runtime implementations to be built and maintained outside of the core kubernetes tree.

@dchen1107 @smarterclayton

@kubernetes/goog-node

Issue 2:
@smarterclayton raised this issue in #199: how should Kubernetes support non-load-balanced and/or stateful services? Specifically, Zookeeper was the example.

Zookeeper (or etcd) exhibits 3 common problems:

Identification of the instance(s) clients should contact

Identification of peers

Stateful instances

And it enables master election for other replicated services, which typically share the same problems, and probably need to advertise the elected master to clients.
Issue 1:
package main

type X *[10]Y
type Y X

func main() {
}

//--------------------------------------------------------------
Compiler says:
test.go:3: invalid recursive type Y

Compiler version: cd89452cfea3 weekly/weekly.2011-04-04

I think these recursive types are perfectly valid, because X's size doesn't depend on
Y's size.

Issue 2:
by jonas.p:

What steps will reproduce the problem?

try to get Subject Alternative Name URIs in the same way you can access DNSNames,
EmailAddresses and IPAddresses

http://play.golang.org/p/by0PoVfPyd

What is the expected output?
URIs returns the subject alternative name URIs of a certificate

What do you see instead?
URIs is not available

Which version are you using? (run 'go version')
go version devel +eec7eca4b11a Mon Jun 17 14:56:45 2013 -0700 linux/amd64

Please provide any additional information below.
possible implementation:
https://golang.org/cl/7501043/
Issue 1:
If an async op is not listed in the OP_DETAILS map in 40_testing.js, you can get the following exception:

TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator))
at asyncOpSanitizer (deno:runtime/js/40_testing.js:177:32)
at async resourceSanitizer (deno:runtime/js/40_testing.js:369:7)
at async Object.exitSanitizer [as fn] (deno:runtime/js/40_testing.js:426:9)
at async runTest (deno:runtime/js/40_testing.js:786:7)
at async Object.runTests (deno:runtime/js/40_testing.js:984:22)

Presumably some fallback message should show up in these cases, in case a new op is mistakenly left out, and for ease of development.

Additionally, some async ops related to resources (op_read, op_write, op_shutdown) and workers (op_host_recv_ctrl, op_host_recv_message) are currently missing.

Issue 2:
I don't have a clear reproduction path for this issue but I dug into the 40_testing.js code and I believe I found the cause of the issue. A user of my test_suite module opened an issue saying they were getting an error when upgrading to the newest version that uses the test step API. The user reported they are using Deno 1.19. Looking at the error message, it appeared to actually be an issue with Deno's test runner.

The Deno.metrics().ops object has 281 keys. The OP_DETAILS object in 40_testing.js only has 67 of those keys.

In the asyncOpSanitizer, if there is a difference in ops dispatched and completed, it will try getting hint information from the OP_DETAILS here using destructuring assignment (shown below). If there isn't a hint in OP_DETAILS for the key, then the value returned from OP_DETAILS[key] is going to return undefined and you can't destructure undefined.

const [name, hint] = OP_DETAILS[key];

If the key happens to be one that is undefined, this will throw the following error.

TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator))
at asyncOpSanitizer (deno:runtime/js/40_testing.js:176:32)
Issue 1:
Logs and details after the comment here #1118 (comment)

Test code: https://gist.github.com/ionelmc/4259997

Issue 2:
I am using Celery version 3.0.19 from pypi (upgraded and tested today). Here are my steps to reproduce:

app.py:

from time import sleep
from celery import Celery

celery = Celery(broker="amqp://")
celery.conf.update(
CELERYD_CONCURRENCY=1,
CELERYD_MAX_TASKS_PER_CHILD=1,
)

@celery.task
def accept_argument(argument):
sleep(5)

script.py:

from app import accept_argument

big_data = "A" * 1024 * 1024 * 8

accept_argument.delay(big_data)
accept_argument.delay(big_data)

Run the worker:

$ celery worker --app=app -l info

Crash the worker:

$ python script.py

Expected result:

Both tasks are run, in sequence.

The worker (sub)process restarts at the 5 second mark after the first task completes (MAX_TASKS_PER_CHILD=1 reached)

The worker process restarts at the 10 second mark after the second task.

Actual result:

The first task runs.

The first worker process goes into a zombie state.

The worker main process hangs in Modules/_billiard/socket_connection.c

Observe by attaching gdb to the running process.

Presumably the main process is writing the second task to the zombie original worker, but should be writing it to a new worker process.

I strongly suspect that this is the same problem as issue #957, but that was closed-presumed-fixed as of version 3.0.13 and I am using a later version of Celery.

EDIT: tweaking reproduction code.
Issue 1:
Migrated issue, originally created by Fayaz Khan (@fayaz)

In this specific scenario, query.count() & len(query.all()) do not match:

from sqlalchemy import create_engine, Column, ForeignKey, Integer, Table
from sqlalchemy.ext.declarative import declarative_base
from sqlalchemy.orm import relationship, sessionmaker

Base = declarative_base()
promo_like_association = Table(
'promo_like_association', Base.metadata,
Column('promo_id', ForeignKey('promo.id'), primary_key=True),
Column('like_id', ForeignKey('like.id'), primary_key=True))
user_like_association = Table(
'user_like_association', Base.metadata,
Column('user_id', ForeignKey('user.id'), primary_key=True),
Column('like_id', ForeignKey('like.id'), primary_key=True))

class Like(Base):
__tablename__ = 'like'
id = Column(Integer, primary_key=True)
users = relationship(
'User', secondary=user_like_association, backref='likes')

class Promo(Base):
__tablename__ = 'promo'
id = Column(Integer, primary_key=True)
likes = relationship(Like, secondary=promo_like_association)

class User(Base):
__tablename__ = 'user'
id = Column(Integer, primary_key=True)

def main():
database_uri = 'sqlite:///'
engine = create_engine(database_uri)
Session = sessionmaker(bind=engine)
session = Session()
Base.metadata.create_all(engine)
user = User(likes=[Like()])
session.add(user)
session.add(Promo())
check(session, Like.users.any(id=user.id))
check(session, Like.users.contains(user))
user.likes.append(Like())
check(session, Like.users.any(id=user.id))
check(session, Like.users.contains(user)) # Fails

def check(session, condition):
# query tries to fetch promos for user with common likes
# or promos that have no specific likes at all.
query = (session.query(Promo).outerjoin(Promo.likes)
.filter(condition | ~Promo.likes.any()))
assert query.count() == len(query.all()) == 1

if __name__ == '__main__':
main()

This will fail with:

Traceback (most recent call last):
File "test_sqla_contains.py", line 60, in <module>
main()
File "test_sqla_contains.py", line 48, in main
check(session, Like.users.contains(user)) # Fails
File "test_sqla_contains.py", line 56, in check
assert query.count() == len(query.all()) == 1
AssertionError

I'm working around the issue using any(id=...) instead of contains().

Issue 2:
Migrated issue, originally created by Anonymous

Currently it throws error at

File "C:\Python26\lib\site-packages\sqlalchemy-0.7.6-py2.6-win32.egg\sqlalchemy\sql\compiler.py", line 927, in visit_table

hinttext = self.get_from_hint_text(table, fromhintstable)

TypeError: get_from_hint_text() takes exactly 2 arguments (3 given)

the problem is that signature in mssql dialect is

def get_from_hint_text(self, text):

return text

Hence we should change the either the signature by adding table as argument or remove table parameter from sqlalchemy\sql\compiler.py", line 927
Issue 1:
Greetings,

continuation from this problem #12134

thanks brendan, after the update, nodes were restarted and all containers started without problems, but there is one thing I am really afraid of my mongodb instances.

I'm using this yaml file, just cut the container list.

apiVersion: v1
kind: ReplicationController
metadata:
name: mongodb-shard1-controller
spec:
replicas: 2
selector:
name: mongodb-shard1-controller
version: v0
template:
metadata:
labels:
name: mongodb-shard1-controller
version: v0
spec:
containers:
- name: mongodb-node1
image: gcr.io/app/mongodb3.0.4
ports:
- containerPort: 27017
hostPort: 27031
env:
- name: REPL_SET
value: kube_shard1
volumeMounts:
- mountPath: /data/db
name: db-path
volumes:
- name: db-path
source:
emptyDir: {}

it may not be the best, but I am using it in production. after the nodes restarted, all replica sets of mongodb instances, could not connect on to each other, and other than that, databases are gone. and I could not get it back up w/databases. i don't know where is /data/db gone?

I'm using GCP, what is the best practice for database storages?

Issue 2:
There are currently two different ways of determining request information: https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/apiserver/handlers.go#L264 and the system of record: https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/apiserver/api_installer.go#L97 that actually dispatches the calls.

Having two mechanisms for determining what verb/namespace/resource/subresource/etc information on the request means that the authorizer can end up out of sync with reality. Collapsing the determination of request information to a single spot with a separate authorize call is one way to eliminate the duplication and avoid false authorization matches due to out of sync request information parsing.

@smarterclayton I think this would address the problem we're having with subresource policy determinations.
Issue 1:
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

In Hybrid mode (when bootstrapped using upgradeAdatper.bootstrap()), the <ng-content select ='' > attribute on the downgraded ng2 component is not honored. it seems that select='' expression is ignored completely and all the light DOM child elements are included.

Expected/desired behavior

In Hybrid mode, the <ng-content select=''> attribute should be honored and should include only those DOM element matching the 'select' criteria.

Reproduction of the problem

Here is the plunker https://plnkr.co/edit/L7Flah?p=preview

What is the expected behavior?

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

It breaks the desired ng2 component behavior in hybrid mode.

Please tell us about your environment:

Angular version: 2.0.0-rc.1

Browser: [Chrome XX ]

Tested in Chrome Version 51.0.2704.103 m

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

https://code.angularjs.org/tools/typescript.js

Issue 2:
Bug Report

Angular version: 2.0.0-beta.11

Browser: [all]

Language: [Typescript]

Description

When downgrading an Angular 2 component to use in an Angular 1 application, the downgraded directive crashes if the original component uses multi-projection with more than 1 slot, for instance:

<ng-content select=".foo"></ng-content>
<ng-content select=".bar"></ng-content>

The error thrown is Error: The component {XXX} has {N} <ng-content> elements, but only 1 slots were provided.

Reproduce

See this plunker for a minimal example that reproduces the bug.

Thanks.
Issue 1:
Hi,

(demo)

async function test( { a } = { } ) {
alert( a );
alert( arguments );
}

test( { a : 10 } );

Babel will alert undefined, because the destructuring parameters are evaluated inside the regenerator wrapper, which doesn't preserve the arguments variable. Actually, any use of arguments inside the body of an async function will fail.

Issue 2:
Here's the code snippet:

const x = ({ a = 1 } = {}) => a

console.log(x()) // 1
console.log(x({})) // 1
console.log(x({ a: 5 })) // 5

const y = async ({ a = 1 } = {}) => a

async () => {
console.log(await y()) // 1
console.log(await y({})) // 1
console.log(await y({ a: 5 })) // 1 (expected 5)
}()

Using Babel 4.7.12 (experimental mode).

Works without the = {}, but then it don't allow passing no argument to the function.

The above snippet was compiled as (for just the y function):

var y = function callee$0$0() {
var _ref, _ref$a, a;

return _regeneratorRuntime.async(function callee$0$0$(context$1$0) {
while (1) switch (context$1$0.prev = context$1$0.next) {
case 0:
_ref = arguments[0] === undefined ? {} : arguments[0];
_ref$a = _ref.a;
a = _ref$a === undefined ? 1 : _ref$a;
return context$1$0.abrupt("return", a);

case 4:
case "end":
return context$1$0.stop();
}
}, null, _this);
};

Looks like there's a problem using arguments in a generator function; here arguments[0] === context$1$0. I think the arguments destructuring should be just after var _ref, _ref$a, a;. I achieved this by moving regenerator around in babel/transformation/transformers/index.js (just before default parameters):

diff --git a/index.old.js b/index.new.js
index 70cd878..f304e6f 100644
--- a/index.old.js
+++ b/index.new.js
@@ -61,6 +61,8 @@ module.exports = {
// needs to be after `es6.parameters.rest` as we use `toArray` and avoid turning an already known arr
ay into one
"es6.spread": require("./es6/spread"),

+ regenerator: require("./other/regenerator"),
+
// needs to be before `es6.blockScoping` as default parameters have a TDZ
"es6.parameters.default": require("./es6/parameters.default"),

@@ -78,8 +80,6 @@ module.exports = {
// identifiers in parameters and variable declarators
"es6.tailCall": require("./es6/tail-call"),

- regenerator: require("./other/regenerator"),
-
// needs to be after `regenerator` due to needing `regeneratorRuntime` references
// needs to be after `es6.forOf` due to needing `Symbol.iterator` references
// needs to be before `es6.modules` due to dynamic imports
Issue 1:
Feature request

Currently, only the following meta tags can be duplicate as per the next/head logic

var ALLOWED_DUPLICATES = ['article:tag', 'og:image', 'og:image:alt', 'og:image:width', 'og:image:height', 'og:image:type', 'og:image:secure_url', 'og:image:url'];

So, it is not allowing me to render multiple og:see_also tag in meta using next/head.

It would be great if these ALLOWED_DUPLICATES can be configured/override using web-pack config/environment variable/nextconfig.

Please suggest.

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

Looking at this repo — https://github.com/dargue3/nextjs-v5-object-context — this line of code (in pages/index.js used to return the names of all the functions belonging to a React component class before upgrading to next v5.

Object.getOwnPropertyNames(Object.getPrototypeOf(context))

Expected Behavior

It should print out ["constructor", "onClick", "otherFunction", "render", "componentDidMount", "componentWillUnmount"]

Current Behavior

It prints out ["constructor", "render", "componentWillReceiveProps", "componentWillUpdate"]

Steps to reproduce

Fire up the repo I pasted above and load localhost:3000. While rendering on the server, this works as expected. You can see the custom functions belonging to the class printing to the terminal. On the client however, any custom functions that you add to the React component will not show up. If you'd like to verify that this is related to v5, downgrade to v4.2.2 and you should see the print statement showing up correct on both server and client.

Your Environment

Tech
Version

next
v5.0.0

node
v8.6.0

I can't really speak to whether or not this is a bug (or how the version of Next is even related to this change in expected behavior). Could someone shed some light on what changes to v5 could have caused this?