WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
followup to #17165 / #18738, cc @kshyatt

right now the base tests are printing both old as-you-go info, in addition to a new table so it looks like

* dsp maxrss 3501.18 MB
* examples maxrss 3501.18 MB
* compile maxrss 3501.18 MB

Test Summary: | Pass Broken Total
Overall | 22171317 28 22171345
Test: | Total time (s): | GC time (s): | Percent in gc: | Allocated (MB): | RSS (MB):
linalg/triangular | 546.77 | 11.92 | 2.18 | 8420.77 | 680.38
linalg/qr | 89.66 | 1.85 | 2.06 | 2312.61 | 751.55

I propose we get rid of the old style and attempt to make the table just print new rows as they come in, if that's possible. The maxrss numbers are the same so it's duplicated information.

Additional printing-related followup from #17165 (comment), printing of @test true or @test 1==1 should be adjusted to not bother showing Expression: nothing now that passing tests don't save the input expressions any more.

Issue 2:
As per discussion in https://groups.google.com/forum/#!topic/julia-users/alavN8tRdyI :

Let e.g.

Array{<:Real}

act like RArray given by

typealias RArray{T<:Real} Array{T}

This convenient shortcut should go a long way in those cases where people would want covariant types.

The type parameter of Array{<:Real} might become anonymous or hidden; it probably doesn't matter so much since you would rarely re-provide it, e.g. Array{<:Real}{Int}.
Issue 1:
What problem does this feature solve?

Actually we use :bool-prop="false". What would be the chances of implementing !bool-prop?

What does the proposed API look like?

Instead of

<button :ripple="false">Download</button>

Would be

<button !ripple>Download</button>

Think of several props in the same element.

Issue 2:
What problem does this feature solve?

我有一个类似于qq聊天的窗体，聊天框需要缓存用户行为（滚动条位置、输入框内容等），keepalive渲染的组件都是同一个，只是加了不同的key，用keepalive可以实现我的需求的，当我关闭某个用户的聊天窗口时，配置include时缓存是没法清除；

我的组件结构如下：

<keep-alive :include="included">
<chat v-if="_interlocutor.Key===interlocutor" :interlocutor="_interlocutor"
:key="_interlocutor.Key" v-for="_interlocutor in interlocutors"/>
</keep-alive>

现在只能通过_vnode.componentInstance获取到keys,和cache，在程序中自己来处理。处理起来比较麻烦。

What does the proposed API look like?

看代码发现include和exclude的配置都是判断的组件name，能否增加include和exclude对key的支持。
Issue 1:
Currently gradients can only be computed manually in C++ or automatically in Python with tf.gradients. Work on registering C++ implemented gradients for all the OPs has started. However, there is currently no easy way to automatically use those gradients to generate a graph. The C-api also does not have gradient creation calls yet.

This supercedes the gradient part of #476, since the rest of #476's issue was addressed.

Issue 2:
I have started porting Tensorflow to Node.js and was wondering about the status of gradients support in the C and C++ APIs:

https://www.tensorflow.org/versions/r0.12/how_tos/language_bindings/index.html

https://github.com/tensorflow/tensorflow/blob/master/tensorflow/g3doc/resources/roadmap.md

Could I ask for some help and / or offer some assistance? A couple of ideas:

I would be happy to test the work-in-progress API in Node.js using either of both C or C++. I have tried both APIs and would be happy to maintain both as a test case.

I would be happy to receive some guidance from someone on the tensorflow team on how to implement gradients / training without an official API. I see from this issue (#4473) that it might be possible, but it has been hard to study the Python and OCAML code to understand what to do. Some pseudocode or links to existing code that would need to replicated could be enough.

Something else? For example, I could help move the gradient API forward by working with someone on the tensorflow team.

Let me know if you have any suggestions for a path forward. Thank you!
Issue 1:
OpenCV uses some ffmpeg APIs that have been removed in the just released ffmpeg 5.0 and makes some assumptions about ffmpeg structs that are no longer true (primarily trying to access the "codec" member in an AVStream).

This causes the build to fail.

Issue 2:
related:

https://forum.opencv.org/t/error-avstream-aka-struct-avstream-has-no-member-named-codec/3506

ffmpeg changed its AVStream structure. in ffmpeg v3.1 (~2016) the codecpar member was introduced to replace codec member. codec has been deprecated since then. it is still available in ffmpeg v4.4 but not in the master branch.

availability is modulated by #define FF_API_LAVF_AVCTX (LIBAVFORMAT_VERSION_MAJOR < 59)

this version was bumped to 59 a month ago in FFmpeg/FFmpeg@85ba17f

OpenCV v4.5.2/master still assumes the existence of the codec member:

opencv/modules/videoio/src/cap_ffmpeg_impl.hpp

Line 606
in
ae4cc40

avcodec_close( video_st->codec );

I've checked issues and pull requests for mentions of codecpar and it seems this hasn't been reported yet.
Issue 1:
VSCode Version: 0.10.11

OS Version: Ubuntu 15.10 x64

Steps to Reproduce:

Define a variable in a Javascript/Typescript file and assign a multi-line string value, using the "" (backslash) character to join lines. e.g.

var mlString = "The is my long multi-line string which I am using a backslash \
to join over these lines."

In the vscode editor only the first line of the string is correctly color-coded as a string-type. See screenshot attached.

Issue 2:
From @KevinSCreative on December 30, 2015 18:13

After the first line, multi-line strings in JavaScript don't get string color. In the following example, only "Hello World" has the string color, and the obj variable declaration is all one color. In the default theme, 'var' is supposed to be blue. I would also expect the rest of the string to be orange in the default theme, not just the first line.

I am running VSC 0.10.6 and I have no extensions installed.

var test = 'Hello World!\
<div>\
<p>Testing</p>\
</div>\
';
var obj = $(test);

Copied from original issue: microsoft/vscode#1716
Issue 1:
i think package.json shouldn't be deprecated, but changed: the current proposal suggest full urls in the imports; i suggest the full urls will reside on the package.json, along with the version, and have a semantic short-name for the imported package, so it would be easier to refer to it from the multitudes of projects files... Also, i'd suggest an option to provide a repository short-name in the package.json, so make the more readable.

example:

{
repositories: {
kuku: 'https://www.github.com/kuku/'
},
dependencies: {
matrices: '@kuku/matrix-utils@~2.0.0'
}
}

the usage is simple:

my-code.ts:

import {multiply} from 'matrices' // or perhaps import {multiply} from '@matrices'
...
...

Issue 2:
Very interesting project! I love the web-compatibility goal.

One thing that would help there is support for bare module specifiers via package name maps: https://github.com/domenic/package-name-maps

This would allow for imports like:

import * as _ from 'lodash';

Without any requirements on a specific package manager. It's our hope that npm, yarn and others will produce package-name maps during installation, giving you a bridge there. We have a reference implementation in progress here: WICG/import-maps#37
Issue 1:
by jht5945:

1. What is a short input program that triggers the error?
{{{
package main

import "fmt"

func GetValue(val bool) string {
if val {
return "true"
} else {
return "false"
}
}

func main() {
fmt.Println(GetValue(true))
}
}}}

2. What is the full compiler output?
`prog.go:5: function ends without a return statement`

3. What version of the compiler are you using? (Run it with the -V flag.)
`go version go1.0.2`

Issue 2:
12156:8086095a2f8e tip
Build with AddressSanitizer
(http://code.google.com/p/address-sanitizer/wiki/AddressSanitizer):
CC="clang -faddress-sanitizer -g -fno-omit-frame-pointer" ./make.bash

ERROR: AddressSanitizer global-buffer-overflow on address
0x0000006e7ebe at pc 0x46ab3e bp 0x7fff80741d00 sp 0x7fff80741cf8
READ of size 1 at 0x0000006e7ebe thread T0
#0 0x47643e in typ src/cmd/cc/sub.c:159
#1 0x45a620 in fnproto1 src/cmd/cc/dcl.c:899
#2 0x4546c7 in dodecl src/cmd/cc/dcl.c:77
#3 0x485106 in yyparse src/cc.y:145
#4 0x46798e in compile src/cmd/cc/lex.c:284
#5 0x465ed5 in p9main src/cmd/cc/lex.c:156
#6 0x494329 in main src/lib9/main.c:36
0x0000006e7ebe is located 10 bytes to the right of global variable
'ewidth (src/cmd/6c/txt.c)' (0x6e7ea0) of size 20
Issue 1:
Environment

Windows build number: 10.0.18990.0
Windows Terminal version (if applicable): v0.6 on commit [71debc1](https://github.com/microsoft/terminal/commit/71debc158b6d90106a2dfc26b9029429499dfb29)

Any other software?

Steps to reproduce

Drag the tabs around

Expected behavior

I should be able to see the tab while dragging

Actual behavior

No tab until I drop :(

Issue 2:
Environment

Windows build number: Microsoft Windows [Version 10.0.18963.1000]
Windows Terminal version (if applicable): 0.5.2762.0

Steps to reproduce

Launch WSL terminal

Use other applications like a web browser

Go back to the WSL terminal

Expected behavior

See a working terminal with all the past text output

Actual behavior

The area where you would expect to see the terminal output is completely blank (black). Not sure how to reproduce this consistently, seems to happen at random. Looks like it can go back to normal after a bit (a minute?) of waiting.

Might be @2733
Issue 1:
Electron version: v1.2.4

Operating system: Ubuntu LTS 14.04

If there is an existing Electron issue for this, please link it here:

https://github.com/atom/electron/issues

Describe your problem:

Electron won't open at all. I ran the command to install electron-prebuilt. Nothing happens when I run electron afterward. I am using the code found on the website under Quick Start and it won't open so it's not the code as far as I am concerned. There have been other issues regarding electron not opening but those have been with errors popping up when trying to run electron. Mine is simple: electron doesn't do anything. I don't really know why this is happening but I need it to work asap and after having spent four hours of trying to get it to work I am running out of options

Issue 2:
Electron version: 1.2.4

Operating system: Linux xxx 4.2.0-38-generic #45~14.04.1-Ubuntu SMP Thu Jun 9 09:27:51 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

I was trying to set 1.2.2 - 1.2.3 versions and works fine. When updating to 1.2.4 app.on('ready'...) never works. No errors output on console.

Trying "Quick start" from electron. https://github.com/electron/electron-quick-start
Issue 1:
Feature request

Is your feature request related to a problem? Please describe.

Currently when deploying to now 2.0 we force all dependencies to be devDependencies, the reason for this is creating the smallest possible lambda.

This however introduces some issues:

When everything is a devDependency, how are my pages requiring these modules?

answer: next build --lambdas bundles imported modules and no longer uses externals for this reason.

When the user has a next.config.js that uses any module, most commonly a Next.js plugin like @zeit/next-css loading next.config.js in production will fail because of the module not being there. However this opens up the question: why is next-css being loaded on cold start in production.

Describe the solution you'd like

One solution is forcing phases to be used, documentation can be found here: https://github.com/zeit/next.js#custom-configuration

However there are alternatives, for example:

bundling the configuration (would also allow for next.config.ts or similar. At first glance this seems like a solution, however it doesn't solve the build-time modules being loaded in production mode.

No longer allowing a "runtime" next.config.js, this would be a breaking change but it would make a lot of sense since this forces applications to optimize at build and not have runtime values being passed for convenience. However we'd still need a way to allow publicRuntimeConfig and assetPrefix (which does work at runtime), which is for example used by Trulia's appshell.

Describe alternatives you've considered

I'd love to know how people are using next.config.js currently. From what I've seen the vast majority looks like the equivalent of:

const thePlugin = require('theplugin')
module.exports = thePlugin({})

Additional context

Issue reference for Now 2.0: #5750

For now this issue is just a writeup of one issue regarding serverless execution, I don't have a definitive opinion about this yet, but I wanted to write down my thoughts on the subject so that we can get the community involved and work towards a solution 👍

Issue 2:
Feature request

Support assetPrefix with next/link component.

Describe the solution you'd like

Provide assetPrefix props for next/link component.

Additional context

This feature is needed in case we have multiple NextJS apps on the same domain with different assetPrefix .

Note that, even page urls are on the same domain, assetPrefix might be on different CDN host.
Issue 1:
Version

2.7.4

Reproduction link

sfc.vuejs.org/

Steps to reproduce

Step1. create the project with @vue/cli 5.0.8; vue create vue27-ts-mini,

? Please pick a preset: Manually select features
? Check the features needed for your project: Babel, TS, Router, Vuex, CSS Pre-processors, Linter
? Choose a version of Vue.js that you want to start the project with 2.x
? Use class-style component syntax? Yes
? Use Babel alongside TypeScript (required for modern mode, auto-detected polyfills, transpiling JSX)?
Yes
? Use history mode for router? (Requires proper server setup for index fallback in production) Yes
? Pick a CSS pre-processor (PostCSS, Autoprefixer and CSS Modules are supported by default): Less
? Pick a linter / formatter config: Prettier
? Pick additional lint features: Lint on save
? Where do you prefer placing config for Babel, ESLint, etc.? In dedicated config files

Step2. mkdir types && mv src/*.d.ts types/ && pnpm i

Step3. edit shims-tsx.d.ts, add interface to global

import Vue, { VNode } from "vue";

declare global {
namespace JSX {
interface Element extends VNode { }
interface ElementClass extends Vue { }
interface IntrinsicElements {
[elem: string]: any;
}
}

interface IHttpResponse<T> {
Result: number
Reason?: string
ErrCode?: number
// ErrCode?:number
data?: T

}

}

Step4. edit .eslintrc.js add "prettier/prettier": 0, to rules section

Step5. add this code to main.ts and src/views/HomeView.vue

const zz: IHttpResponse<string> = {
Result: 0,
data: 'sdfsdf',
};
console.log('zz', zz);

What is expected?

No Warning

What is actually happening?

the main.ts does not has any error.

the src/views/HomeView.vue has an no-undef warning:

[{

"resource": "/D:/Playground/vue2.7-ts/vue2.7-ts/src/views/HomeView.vue",

"owner": "eslint",

"code": {

"value": "no-undef",

"target": {

"$mid": 1,

"external": "https://eslint.org/docs/rules/no-undef",

"path": "/docs/rules/no-undef",

"scheme": "https",

"authority": "eslint.org"

}

},

"severity": 8,

"message": "'IHttpResponse' is not defined.",

"source": "eslint",

"startLineNumber": 11,

"startColumn": 11,

"endLineNumber": 11,

"endColumn": 24

}]

Issue 2:
The <slot> functionality is really useful, however I wonder if having a vm.$slots instance property could be useful. Much like this thread, I'd like to show/hide parts of a component depending on whether a particular named slot was passed through. Although the thread was answered, I think having an instance property could make things much cleaner.

I don't really know much about Vue's internals, but it looks like a list is already compiled as vm._slotContents here. Perhaps this was purposefully not exposed as a public API, but being able to perform actions based on whether certain slots were provided seems quite useful to me.

I imagine it'd be similar to vm.$els, where each key is the slot's name and each value is its element.

Let me know what you think. Thanks!
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

I am trying to override the Grid item style, specifically the padding, using the classes prop.

Current Behavior

They way the object key is generated for the grid item padding it makes it very difficult to override it.

Context

I want to use the grid system to generate 2 rows AppBar. The padding of the Grid item makes the AppBar not resize in height as the standard AppBar would do when the width changes.

Your Environment

Tech
Version

Material-UI
beta13

React
15.6.2

browser
Chrome

etc

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

Expected Behavior

When using the Input component with multiline={true} and fullWidth={true}, the generated MuiTextarea-rootcomponent should have awidthof100%`.

Current Behavior

When using the Input component with multiline={true} and fullWidth={true}, the generated MuiTextarea-root doesn't have a width set up.

Steps to Reproduce (for bugs)

set up a div container with an arbitrary width, insert an Input component with properties fullWidth={true} and multiline={true} and a defaultValue that is big enough.

you will see that the text doesn't stretch to the width of the container.

Context

This problem happens because width: 100% is applied to MuiInput-root only, and not its descendant MuiTextarea-root.

Your Environment

Tech
Version

Material-UI
latest

React
latest

browser
chrome
Issue 1:
Currently, the env var in .env or .flaskenv will not override existing value. However, if a user installed python-dotenv and created a .flaskenv, he will expect the variables in .flaskenv override the old values. It's inconvenience when you develop multiple applications at the same time.

Issue 2:
I want to start by apologizing in advance if I make any mistakes in this bug report, I'm new to development and any mistakes are unintentional. That being said I appreciate any input as to how I can improve.

The issue:

Creating a class that inherits from FlaskForm causes an error with the following traceback

Error: While importing 'app', an ImportError was raised:

Traceback (most recent call last):
File "/home/rburd/.local/share/virtualenvs/d5-9RMvys9g/lib/python3.11/site-packages/flask/cli.py", line 218, in locate_app
__import__(module_name)
File "/home/rburd/academy/Mod-6/w18/d5/app/__init__.py", line 2, in <module>
from .form import Tweet
File "/home/rburd/academy/Mod-6/w18/d5/app/form.py", line 1, in <module>
from flask_wtf import FlaskForm
File "/home/rburd/.local/share/virtualenvs/d5-9RMvys9g/lib/python3.11/site-packages/flask_wtf/__init__.py", line 4, in <module>
from .recaptcha import Recaptcha
File "/home/rburd/.local/share/virtualenvs/d5-9RMvys9g/lib/python3.11/site-packages/flask_wtf/recaptcha/__init__.py", line 1, in <module>
from .fields import RecaptchaField
File "/home/rburd/.local/share/virtualenvs/d5-9RMvys9g/lib/python3.11/site-packages/flask_wtf/recaptcha/fields.py", line 3, in <module>
from . import widgets
File "/home/rburd/.local/share/virtualenvs/d5-9RMvys9g/lib/python3.11/site-packages/flask_wtf/recaptcha/widgets.py", line 2, in <module>
from flask import Markup
ImportError: cannot import name 'Markup' from 'flask' (/home/rburd/.local/share/virtualenvs/d5-9RMvys9g/lib/python3.11/site-packages/flask/__init__.py)

If I switch to flask ver. 2.2.3 I receive no such error

How to reproduce:

Start a new project in an empty directory using the command pipenv install flask flask-wtf python-dotenv

Create a subfolder named 'app' with the following files

# /app/__init__.py
from flask import Flask
from .form import Tweet

app = Flask(__name__)

and

# /app/form.py
from flask_wtf import FlaskForm
from wtforms import StringField, SubmitField

class Tweet(FlaskForm):
author = StringField("Author")
submit = SubmitField("Create New Tweet")

Create a .flaskenv file with the following contents:

FLASK_APP=app

Finally try to start the app with the command pipenv run flask run

What I Expected:

When the flask run command is given no error should occur, which is the behavior observed when using flask ver. 2.2.3

Environment:

Python version: 3.11.3

Flask version: 2.3.0
Issue 1:
The new explain API for detailing heap usage can be a huge help in debugging large Elasticsearch systems - for performance or crashes

Obviously if you can add the ES's structures to this functionality , all the better

https://issues.apache.org/jira/browse/LUCENE-5949

Issue 2:
A primary shard was stuck in RELOCATION state. Recovery API shows that all files have completed at 100%. The stage shows that it is TRANSLOG. But it has been sitting there for > 15 hours.

{
"id": 0,
"type": "RELOCATION",
"stage": "TRANSLOG",
"primary": true,
"start_time": "16443.3d",
"start_time_in_millis": 1420704589802,
"stop_time": "0s",
"stop_time_in_millis": 0,
"total_time": "15.1h",
"total_time_in_millis": 54706836,
"source": {
"id": "0eltfic0RdmC9v-Yb17Wzw",
"host": "elasticsearch1.localdomain",
"transport_address": "inet[/IP:9300]",
"ip": "127.0.1.1",
"name": "elasticsearch1.localdomain"
},
"target": {
"id": "ctCRm_huQsSBoTobhmqJdg",
"host": "elasticsearch8.localdomain",
"transport_address": "inet[/IP:9300]",
"ip": "127.0.1.1",
"name": "elasticsearch8.localdomain"
},
"index": {
"files": {
"total": 318,
"reused": 0,
"recovered": 318,
"percent": "100.0%",
"details": [
... list of files
]
},
"bytes": {
"total": 58111147927,
"reused": 0,
"recovered": 58111147927,
"percent": "100.0%"
},
"total_time": "0s",
"total_time_in_millis": 0
},
"translog": {
"recovered": 24685532,
"total_time": "0s",
"total_time_in_millis": 0
},
"start": {
"check_index_time": "0s",
"check_index_time_in_millis": 0,
"total_time": "0s",
"total_time_in_millis": 0
}
}

Running a reroute command with no post body got it to unstuck:

curl -XPOST 'localhost:9200/_cluster/reroute?pretty&explain=true'

Not sure how it got into this state (no log entries related to recovery of this shard in the data or master logs) and why we have to run an empty reroute request to get it unstuck.
Issue 1:
Vue.js version

2.0.1

Reproduction Link

I have written an example in jsfiddle

https://jsfiddle.net/yreenchan/vfxtb7ps/1/

Steps to reproduce

var vm = new Vue({ el: '#app', data: { isShow: 0, second: 1 } });

:style="{opacity: isShow}", the default value of isShow is 0, and the dom is hidden;

change the value of another property 'second'

What is Expected?

Don't effect the :style renderer results when it's value is not changed.

What is actually happening?

when after i change the value of another property 'second', the hidden dom show again.

Issue 2:
Version

2.6.11

Reproduction link

https://jsfiddle.net/0vxoaz75/

Steps to reproduce

Click on the "Unset" radiobutton.

What is expected?

The checked radiobutton (top row) should be unchecked.

What is actually happening?

Nothing.

Vue DevTools are showing me that the value is actually being set to null. But the view isn't updated.

If I do the value change inside DevTools(i.e. without clicking), it works as expected.

Or when I remove the name from the "Unset" radiobutton, it works too.

Or when I remove .prevent, it works too. From my understanding, .prevent in this case should only prevent the clicked radiobutton from getting checked; not prevent the others from being unchecked.