WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
On macOS, typing option-shift-9 in the REPL (this types the interpunct character ·, see also #25157) gives an error:

julia> ERROR: MethodError: no method matching position(::Base.Terminals.TTYTerminal)
Closest candidates are:
position(::Base.Filesystem.File) at filesystem.jl:222
position(::Base.Libc.FILE) at libc.jl:94
position(::IOStream) at iostream.jl:188
...
Stacktrace:
[1] mark(::Base.Terminals.TTYTerminal) at ./io.jl:861
[2] peek at ./iostream.jl:462 [inlined]
[3] read(::Base.Terminals.TTYTerminal, ::Type{Char}) at ./io.jl:608
[4] match_input(::Dict{Char,Any}, ::Base.LineEdit.MIState, ::Base.Terminals.TTYTerminal, ::Array{Char,1}, ::Dict{Char,Any}) at ./repl/LineEdit.jl:1288
[5] match_input at ./repl/LineEdit.jl:1287 [inlined]
[6] prompt!(::Base.Terminals.TTYTerminal, ::Base.LineEdit.ModalInterface, ::Base.LineEdit.MIState) at ./repl/LineEdit.jl:2314
[7] run_interface(::Base.Terminals.TTYTerminal, ::Base.LineEdit.ModalInterface, ::Base.LineEdit.MIState) at ./repl/LineEdit.jl:2223
[8] run_frontend(::Base.REPL.LineEditREPL, ::Base.REPL.REPLBackendRef) at ./repl/REPL.jl:1024
[9] run_repl(::Base.REPL.LineEditREPL, ::getfield(Base, Symbol("##605#607"))) at ./repl/REPL.jl:183
[10] _start() at ./client.jl:420

It worked fine in 0.6.

Issue 2:
I found by accident this issue, in master Julia. Whenever I try to type "·" (U+00b7) in the REPL, Julia crashes. This doesn't happen in v0.6.2. On the other hand, I can type \cdotp [TAB] to avoid the issue.

Note that the middot is typed as SHIFT+3 in the spanish keyboard layout, and I don't have direct access to the other middot (U+22c5) apart from typing \cdot [TAB]. I would prefer to make them equivalent for the whole Julia, since it is easy to type in my case.

Here it is the version information

Julia Version 0.7.0-DEV.2959
Commit df2616e (2017-12-14 14:05 UTC)
Platform Info:
OS: Linux (x86_64-redhat-linux)
CPU: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz
WORD_SIZE: 64
BLAS: libopenblas (USE64BITINT NO_AFFINITY HASWELL)
LAPACK: libopenblas64_
LIBM: libopenlibm
LLVM: libLLVM-3.9.1 (ORCJIT, skylake)
Environment:

the error message

ERROR: MethodError: no method matching position(::Base.Terminals.TTYTerminal)

and the stacktrace

Stacktrace:
[1] ·mark(::Base.Terminals.TTYTerminal) at ./io.jl:847
[2] peek at ./iostream.jl:462 [inlined]
[3] read(::Base.Terminals.TTYTerminal, ::Type{Char}) at ./io.jl:594
[4] match_input(::Dict{Char,Any}, ::Base.LineEdit.MIState, ::Base.Terminals.TTYTerminal, ::Array{Char,1}, ::Dict{Char,Any}) at ./repl/LineEdit.jl:1288
[5] match_input at ./repl/LineEdit.jl:1287 [inlined]
[6] prompt!(::Base.Terminals.TTYTerminal, ::Base.LineEdit.ModalInterface, ::Base.LineEdit.MIState) at ./repl/LineEdit.jl:2314
[7] run_interface(::Base.Terminals.TTYTerminal, ::Base.LineEdit.ModalInterface, ::Base.LineEdit.MIState) at ./repl/LineEdit.jl:2223
[8] run_frontend(::Base.REPL.LineEditREPL, ::Base.REPL.REPLBackendRef) at ./repl/REPL.jl:1025
[9] run_repl(::Base.REPL.LineEditREPL, ::getfield(Base, Symbol("##602#603"))) at ./repl/REPL.jl:183
[10] _start() at ./client.jl:426

Thanks!

Interpunct, interpoint, middle dot, middot, centered dot, centred dot
Issue 1:
I am trying to make nextjs works together with firebase cloud functions.

When i am testing locally, there is no problem my app works perfectly.

However when i am deploying there is an error related to this line

const app = next({ dev : false })

When i put this line, my functions cannot be deployed and i get this message

Deploy Error: Function load error: Error: cannot communicate with function.

I don't understand because i don't have this issue in local testing.

Then when i comment this line. It's okay i can deploy my functions. However there is no possibility to use next.js . So this is the problem.

I have this error even without using any nextjs stuff in my functions. Just the fact to declare the line

const app = next({ dev : false }) prevent my app to deploy

any suggestions ?

Issue 2:
Firebase recently introduced the feature for server side rendering using cloud functions. ANy guide of how to implement next with it Next +redux progressive web app?
Issue 1:
Describe the feature:

We would like to be able to link slow queries back to the user or application which caused the slow query.

Therefore we recommend adding a "logData" parameter to the search API which is simply copied from the request directly into the slow query log. We can then put identifiers (user ID, application ID, query ID, etc.) and what-not into this field to provide the linkages necessary to perform traceback to the application / systems which caused the slow query.

We realize that we could possibly do this with the "stats" parameter (stats groups), but we are concerned that there may be many IDs (thousands, millions) and that the stats-groups structure may not support such a large number of groups (i.e. it would likely use up memory maintaining stats for millions of entries).

Thank you.

Paul

Issue 2:
This is same problem with #15520.

Cause of this problem is that behavior of killproc is different between RHEL 6 and 7.

Line 129 of /etc/init.d/elasticsearch:

killproc -p $pidfile -d 86400 $prog

In RHEL 6, killproc execute "sleep $delay" if target process does not stop within 1sec. So, "/etc/init.d/elasticsearch stop" often takes 86400 seconds, even if elasticsearch is stopped.
Issue 1:
ISSUE TYPE

Bug Report

Documentation Report

COMPONENT NAME

variables

ANSIBLE VERSION

ansible 2.5.0.32862.2cdf31d3a2
config file = /etc/ansible/ansible.cfg
configured module search path = [u'~/.ansible/plugins/modules',u'/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python2.7/site-packages/ansible
executable location = /usr/bin/ansible
python version = 2.7.14 (default, Sep 20 2017, 01:25:59) [GCC 7.2.0]

CONFIGURATION

N/A

OS / ENVIRONMENT

N/A

SUMMARY

When multiple roles are pulled into a playbook, earlier roles can reference default variables from later roles, i.e., variables can be used before they are defined.

Even after scouring the documentation I can only conclude that this is surprising behaviour.

It has been stated elsewhere that defaults belong to the global scope. But this issue is tangential. It refers to ordering of roles when it comes to defaults.

This is a duplicate of #13814 which has never been solved.

STEPS TO REPRODUCE

The example https://github.com/mrdrogdrog/ansible-var-default contains two roles which just print a var to debug output.

The role first hasn't a default definition.

The role second sets the default value of var to "second"

Playbook:

---
- hosts: local
roles:
- role: first
- role: second

EXPECTED RESULTS

The playbook shouldn't compile because first expects a value for var which is not set.

ACTUAL RESULTS

The playbook compiles and prints

second
second

to debug output

Issue 2:
Example code has been simplified to clearly demonstrate the variable scoping issue that occurs when a dependent role is activated.

This is a duplicate of issue #4528 - which I've added after reading advice from: https://groups.google.com/forum/#!msg/ansible-project/BPnZPe_Ixhg/aDU9dkvrUjcJ

The scoping issue is a major showstopper for us; and I'd like to at least get confirmation that this is a bug with intent to fix vs. desirable behavior.

Summary:

https://github.com/briceburg/ansible-variable-scoping/tree/master/simple
Issue 1:
What version of Go are you using (go version)? go1.6

What operating system and processor architecture are you using (go env)? linux/amd64

What did you do? http://play.golang.org/p/1MigDGnopS (unfortunately this cannot execute because of cgo)

What did you expect to see? One line printed to standard output containing text "test" (edit: as is output by this very similar, working example http://play.golang.org/p/eX1pSIjmo4)

What did you see instead?

panic: runtime error: cgo argument has Go pointer to Go pointer

goroutine 1 [running]:
panic(0x474d20, 0xc82000a210)
/usr/lib/go/src/runtime/panic.go:464 +0x3e6
main._cgoCheckPointer0(0x4697e0, 0xc820054094, 0x0, 0x0, 0x0, 0x0)
github.com/bmatsuo/lmdb-go/tmp/_obj/_cgo_gotypes.go:42 +0x4d
main.main()
/home/b/src/github.com/bmatsuo/lmdb-go/tmp/cgopanic.go:24 +0x153

I'm creating this issue to track a problem I brought up in #14210 (comment) but for which the cause/fix was different. I took some time before filing the issue to collect more information about the problem and the fix for my own understanding. My apologies for the delay. But it didn't look like a duplicate has been filed since.

I was also told to replace my code that looked like the above example with code which takes the address of a []byte at the actual cgo call site to help the tool figure out which memory region I was referring to. I have done so, and it works, but I have found the result to be significantly slower that before I made this change (both benchmarks takes from a stock go1.6 build -- no flags).

The changes I made to work around the above panic in my actual project can be found here: bmatsuo/lmdb-go@40ebaca

And the performance comparison against master can be seen in my pull request: bmatsuo/lmdb-go#57 (comment)

My benchmarks, unfortunately, have more noise than I would like but there is a definite pattern that shows this change having a real impact on call times (especially for some functions which should execute be extremely quickly). The relevant benchmarks show a 7-43% performance penalty from this change (100ns+ per affected C call).

Issue 2:
---------- Forwarded message ----------
From: james4k <sslice@gmail.com>
Date: Mon, Aug 12, 2013 at 5:30 PM
Subject: [golang-dev] cgo and guessKind() on darwin (10.8)
To: golang-dev@googlegroups.com

Hello,

On tip I am receiving a cgo error on the package github.com/go-gl/gl, while it works
fine on 1.1; the output is "gcc produced no output". This error comes from the
guessKind() method in src/cmd/cgo/gcc.go and appears to have started when clang was made
the default CC for darwin. Testing this with CC=gcc seems to confirm this (builds
successfully). I have not tested this with any other versions of clang or on linux, but
it looks like guessKind() is a very GCC specific routine that will need to be adapted to
support other compilers like clang, but I have limited knowledge on this.

Not sure whether or not to submit an actual issue as non-gcc support seemed to be a work
in progress, but posted here for your awareness.

$ clang -v
Apple LLVM version 4.2 (clang-425.0.28) (based on LLVM 3.2svn)
Target: x86_64-apple-darwin12.4.0
Thread model: posix
Issue 1:
Please consider generating wheel for faster installs

http://pythonwheels.com/

Issue 2:
I'm building a flask app that would benefit from being able to spawn some subprocesses via python's standard multiprocessing module.

However, spawning just one leads to an endless loop where an infinite number of processes are spawned. Yikes! It only happens when debug=True is passed to app.run. So it's not a problem in production, but it makes debugging hard.

This problem doesn't happen with the threading module, interestingly enough.

Code to reproduce (Python version 2.7.3 on Windows 7 x64) follows:

import time
from multiprocessing import Process
from flask import Flask

app = Flask(__name__)

def testFun():
print 'Starting'
time.sleep(3)
print '3 Seconds Later'
backProc = Process(target=testFun, args=())
backProc.start()

@app.route('/')
def root():
return 'Root'

if __name__ == '__main__':
app.run(debug=True)
Issue 1:
I have a form with the following code:

$form = $this->factory->create('Symfony\Component\Form\Extension\Core\Type\ChoiceType', null, array(
'multiple' => false,
'expanded' => false,
'choices' => array(
'label a' => false,
'label b' => true,
),
'choices_as_values' => true,
));

When submitting the form, none of the two radio buttons are selected, i.e. the values are lost.

I've written a unit test for it in imphil@71a59b7

Currently it fails with

There were 2 failures:

1) Symfony\Component\Form\Tests\Extension\Core\Type\ChoiceTypeTest::testSubmitSingleExpandedBooleanValueFalse
Failed asserting that false is identical to '0'.

/home/philipp/src/symfony/src/Symfony/Component/Form/Tests/Extension/Core/Type/ChoiceTypeTest.php:354

2) Symfony\Component\Form\Tests\Extension\Core\Type\ChoiceTypeTest::testSubmitSingleExpandedBooleanValueTrue
Failed asserting that true is identical to '1'.

/home/philipp/src/symfony/src/Symfony/Component/Form/Tests/Extension/Core/Type/ChoiceTypeTest.php:373

The problem only happens with boolean values and expanded=true. It seems that a proper conversion to the view data is missing. Unfortunately I have no idea about the inner workings of Symfony -- maybe someone with a bit more experience can have a look?

(This seems to be similar to #14877, but maybe not exactly the same, so I didn't want to hijack that issue.)

Issue 2:
Hi,

I'm currently updating my code to symfony 2.7 and I saw a weird behavior with choice field form with boolean value.

Here is my form class:

<?php
namespace Icap\DropzoneBundle\Form;

use Symfony\Component\Form\AbstractType;
use Symfony\Component\Form\FormBuilderInterface;
use Symfony\Component\OptionsResolver\OptionsResolver;

class DropzoneCommonType extends AbstractType
{
public function buildForm(FormBuilderInterface $builder, array $options)
{
$builder
->add('peerReview', 'choice', array(
'required' => true,
'choices' => array(
'Standard evaluation' => false,
'Peer review evaluation' => true
),
'choices_as_values' => true,
'expanded' => true,
'multiple' => false
));

}

public function getName()
{
return 'icap_dropzone_common_form';
}

public function configureOptions(OptionsResolver $resolver)
{
$resolver->setDefaults(
array(
'data_class' => 'Icap\DropzoneBundle\Entity\Dropzone',
'language' => 'en',
'translation_domain' => 'icap_dropzone',
'date_format' => DateType::HTML5_FORMAT,
)
);
}
}

And how the field is displayed, pretty classic:

{{ form_row(form.peerReview, {'label_attr': {'style': 'display: none;'}}) }}

But at the display of the form the field doesn't have its value checked, the radio button here.

The radio button is checked at the display of the form only after submitting it.

I checked in the debug bar to see what was in the form and I found what I think it's an error.

Before submitting the form the value, and the data, of the field peerReview is 1, and after submitting the value, and the data to, is true. I checked in my object and the attribute is a boolean with true as value.

After submitting the value is boolean, what I expect it to be, but before submission it's an integer.

Is it a bug or am I missing something?
Issue 1:
The following:

function resolve({a, b}, c) {
return resolve();
}

results in:

"use strict";

function f(_x, _x2) {
var _again = true;

_function: while (_again) {
var a = _ref.a;
var b = _ref.b;
_again = false;
var _ref = _x,
c = _x2;
a = b = undefined;
_again = true;
continue _function;
}
}

This obviously breaks, as _ref is accessed before being declared.

It only seems to happen, if the function is named (and recurses by calling itself by that name) and takes more than one argument.

The above example is the smallest I could narrow it down to. I realise it would create an endless loop, but the problem still exists, if you make the recursing conditional.

I hope this issue is not a duplicate of anything and I did not accidentally miss another issue.

Tested with babel@4.7.16, straight from npm.

Issue 2:
I looked at the resulting code and was curious if the _extends that gets created also gets renamed if I create an identifier with the same name, it works when it's all on the root level, but inside a function it seems to fail.

it('', () => {
const _extends = {};
const obj = {...obj};
});

transpiles to this

var _extends = 'lots of code ....';

it('', function () {
var _extends = {};
var obj = _extends({}, obj);
});

which would use my _extends, which I think is not intended, right?

see example repl
Issue 1:
I've been porting over some debugging code into Deno 1.0.0 and discovered that the file path in stack traces can be suppressed under certain scenarios.

I have simplified the test scenario to the following code:

// Place this code in /tmp/deno_test as path_test.ts
// % cd /tmp/deno_test
// % deno run path_test.ts
// Exception contains full path
// % cd /tmp
// % deno run deno_test/path_test.ts
// Exception does not contain full path!!

import * as path from "https://deno.land/std/path/mod.ts";

function f1(){ throw new Error("damn") }

try {
f1()
}catch(e){
console.log(e)
}

Here the output from my Ubuntu 20.04 with Deno 1.0.0:

/tmp/deno_test$ deno run path_test.ts
Compile file:///tmp/deno_test/path_test.ts
Error: damn
at f1 (file:///tmp/deno_test/path_test.ts:11:22)
at file:///tmp/deno_test/path_test.ts:14:3
/tmp/deno_test$ cd ../
/tmp$ deno run deno_test/path_test.ts
Compile file:///tmp/deno_test/path_test.ts
Error: damn
at f1 (path_test.ts:11:22)
at path_test.ts:14:3

When the line import * as path from "https://deno.land/std/path/mod.ts" is commented out the issue goes away on my machine.

Issue 2:
When I import any deno module (for ex, the parse module), the error message show only the file name instead of the full path of the source file. That avoid the vscode from creating a link where I can click and jump to the line of the error.

Without importing anything, the full path of the file is shown as expected.
Issue 1:
I successfully created a ground foliage system using instanced buffer geometry. Setting up the instancing wasn’t nearly as bad as I though it would be, however one aspect was just downright tedious.

What I’m referring to is recreating the Lambert shader manually and then adding in the custom orientation / position adjustments. This was necessary for the foliage material to respect scene lighting / shadows etc. Rebuilding the Lambert Material into a ShaderMaterial was not fun.

Would it not be easier to have a few for example: ShaderChunks[‘Instancing’]? If I’m not overlooking anything, it would just require a few chunks, an instancing_pars chunk which could contain the instancing attributes and applyQuaternionToVector function (from three.js dev instancing examples), and one right after the ‘begin_vertex’ chunk to alter the vec3 transformed variable using the function.

Would this not be much more user friendly? If a user wants to take advantage of instancing (who wouldn't), they simply have to set instancing: true on the material and of course set up the needed buffer attributes. They would no longer have to manually reconstruct an entire materials shader.

I've seen more complex examples of trying to ease usage of instancing, perhaps we should start with something a little more simple like this?

I’d be more than happy to make a PR, if this is desirable.

Issue 2:
Hello,

i am interested in creating a HUD in webgl. I know html can be used to overlay over the scene, but having the UI accelerated on the card can have some mighty advantages, mostly integration with the rest of the app, 3D transforms/transparency and shader special effects.

I was wondering if there was a way to dual render a scene and blend/overlay it. For example to render a a first time with a perspective camera, and then render a second HUD layer on top with an orthographic camera and blend it with the first.

thanks
Issue 1:
Version 1.7.1 is failing to compile and install via brew on an older iMac. The iMac is running macOS High Sierra.

==> Installing deno
==> python build/gen.py
==> ninja -C out
==> cargo install -vv
Last 15 lines from /Users/justin/Library/Logs/Homebrew/deno/03.cargo:
[rusty_v8 0.16.0] See //build/toolchain/mac/BUILD.gn:15:1: whence it was imported.
[rusty_v8 0.16.0] import("//build/config/mac/mac_sdk.gni")
[rusty_v8 0.16.0] ^--------------------------------------
[rusty_v8 0.16.0] See //BUILD.gn:4:1: which caused the file to be included.
[rusty_v8 0.16.0] static_library("rusty_v8") {
[rusty_v8 0.16.0] ^---------------------------
[rusty_v8 0.16.0] thread 'main' panicked at '
[rusty_v8 0.16.0] command did not execute successfully, got: exit code: 1
[rusty_v8 0.16.0]
[rusty_v8 0.16.0] build script failed, must exit now', /Users/justin/Library/Caches/Homebrew/cargo_cache/registry/src/github.com-1ecc6299db9ec823/cargo_gn-0.0.15/src/lib.rs:203:3
[rusty_v8 0.16.0] note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: failed to compile `deno v1.7.1 (/private/tmp/deno-20210204-79091-yndwd1/deno/cli)`, intermediate artifacts can be found at `/private/tmp/deno-20210204-79091-yndwd1/deno/target`

Caused by:
build failed

Do not report this issue to Homebrew/brew or Homebrew/core!

Issue 2:
We struggled with updating deno at Homebrew for a while (cf. Homebrew/homebrew-core#66920) and it seems that part of the reason is that the build is non-deterministic. The exact same build configuration can succeed now and fail (edit: with the same version!) later and vice-versa.

This is partly summarized in the table at Homebrew/homebrew-core#66920 (comment). These are all attempts at building deno 1.7.0.

In particular, note that the build configuration is the same between Homebrew/homebrew-core@54c027e and Homebrew/homebrew-core@77e4ad8 (the first two commits in the table), but the two commits have starkly different build outcomes.

The last three commits in that table are also the same, with differing results.
Issue 1:
Challenge http://www.freecodecamp.com/challenges/waypoint-remove-classes-from-an-element-with-jquery has an issue.

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

If you just type this:

$("button").removeClass();

without the "btn-default" as a parameter for the removeClass function, the "Go to my next challenge" already gets enabled.

Issue 2:
Challenge http://freecodecamp.com/challenges/waypoint-remove-classes-from-an-element-with-jquery has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

.

It has to control if the user has really removed the btn-default class. You can in the screenshot that it accepts the code even though i have not inserted btn-default in the removeClass() function