WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Installed TF 1.4 with pip install --ignore-installed --upgrade https://storage.googleapis.com/tensorflow/linux/gpu/tensorflow_gpu-1.4.0-cp36-cp36m-linux_x86_64.whl

Gives me this error on import:

/home/tom/anaconda3/envs/tf4/lib/python3.6/importlib/_bootstrap.py:219: RuntimeWarning: compiletime version 3.5 of module 'tensorflow.python.framework.fast_tensor_util' does not match runtime version 3.6

return f(*args, **kwds)

Similar error reported form Tensorboard:

/home/tom/anaconda3/envs/tf4/lib/python3.6/importlib/_bootstrap.py:219: RuntimeWarning: compiletime version 3.5 of module 'tensorflow.python.framework.fast_tensor_util' does not match runtime version 3.6

return f(*args, **kwds)

TensorBoard 0.4.0rc2 at http://tomServal:6006 (Press CTRL+C to quit)

Issue 2:
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 14.04

TensorFlow installed from (source or binary): Source

TensorFlow version (use command below):

Python version: Python3.6

Bazel version (if compiling from source):

GCC/Compiler version (if compiling from source): -NA-

CUDA/cuDNN version: -NA-

GPU model and memory: -NA-

Exact command to reproduce: import tensorflow as tf

Environment capture text:

https://github.com/tensorflow/tensorflow/tree/master/tools/tf_env_collect.sh

tf_env.txt

You can obtain the TensorFlow version with

python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"

This command also results in the same error.

/home/raju/anaconda3/lib/python3.6/importlib/_bootstrap.py:219: RuntimeWarning: compiletime version 3.5 of module 'tensorflow.python.framework.fast_tensor_util' does not match runtime version 3.6

return f(*args, **kwds)

Describe the problem

When importing tensorflow , I get this error. I found some information on "Feature request: nightly build for python 3.6 #12935" --"Yes, we unfortunately copy the 3.5 binary for 3.6 I'll look into creating a specific 3.6 binary for Linux."

Source code / logs

$import tensorflow as tf

result is

/home/raju/anaconda3/lib/python3.6/importlib/_bootstrap.py:219: RuntimeWarning: compiletime version 3.5 of module 'tensorflow.python.framework.fast_tensor_util' does not match runtime version 3.6

return f(*args, **kwds)
Issue 1:
Multiply only works when called directly or when inverted (len * 3.0).

#[deriving(Copy, Show)]
pub struct Len(f64);

impl Mul<Len, Len> for f64 {
fn mul(self, r: Len) -> Len {
let Len(right) = r;

Len(self * right)
}
}

fn main() {
let len = Len(12.0);

// works
println!("{}", 3.0.mul(len));
// doesn't
println!("{}", 3.0 * len);
}

Issue 2:
STR

Given the proper (commutative) Add/Mul implementations. (See this playpen link)

const I: Complex<f32> = Complex { re: 0., im: 1. };

let z = I * 3.; // OK
let z = I + 3.; // OK
let z = 3. * I; // Err
let z = 3. + I; // Err

Output

error: mismatched types: expected `_`, found `Complex<f32>` (expected floating-point variable, found struct Complex)

@nikomatsakis Could this work in the future? It would be great if could type 3. + 4. * I instead of I * 4. + 3., the former feels more natural.
Issue 1:
I'm doing a demo with Nex.js, I got a problem with the path.

First of all, I know there are "assetsPrefix", and i have no problem with static content, images, CSS or js. The problem is about the Link

import Link from 'next/link'
<Link href="/about"}>.....</Link>

Everything is fine when i run the site in development mode via npm run dev, but the Link is go wrong when I export via npm run export.

For example, I have set the assetsPrefix in the next.config.js like the following

const isProd = process.env.NODE_ENV === 'production'
{
assetPrefix: isProd ? 'http://localhost:8888/nextjs/demo' : null
}

In development mode, the link becomes http://localhost:3000/about that fine.

In Exported static HTML, the link becomes /about/, after i click the link, the page url is changed to http://localhost:8888/about, actually I prefer http://localhost:8888/next/demo/about.

That means the Link base URL is not controlled by "assetPrefix", doesn't it?

Issue 2:
Feature request

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

Multi zones is a great feature which allows to run multiple next.js apps on the same domain, but it doesn't allow to define a basepath which will be accepted by all parts of next.js. Since we are not able to namespace apps right now it is not possible to have the same names for pages in various apps.

Describe the solution you'd like

I want to be able to configure a basepath in the next.config.js file. Thanks to this configuration all parts of next.js (Router, Link, Static assets etc.) will be aware of the basepath and will automatically generate and match to the correct paths.

Describe alternatives you've considered

One alternative is to nest all desired pages into a folder which matches the basepath. This solves just one small issue with routing and is quite ugly because most of the my basepaths are not one level paths.

The second alterantive is to configure a proxy in a way where the basepath is automatically removed before the request arrives into a next.js app and also implement a custom Link component which automatically adds basepath to all links. I just don't want to maintain custom fork of next.js. It doesn't make sense in my opinion.

Additional context

The assetPrefix solution allows us to define a different prefix for each app. But as fair as I know it works only with different hosts.

with-zones example

module.exports = {
assetPrefix: NOW_URL ? `https://${alias}` : 'http://localhost:4000'
}

If I add a basepath to it everything fails

module.exports = {
assetPrefix: NOW_URL ? `https://${alias}/account` : 'http://localhost:4000/account'
}

In my opinion we should split it into 2 variables:

module.exports = {
assetPrefix: NOW_URL ? `https://${alias}` : 'http://localhost:4000',
basepath: '/account'
}

Related issues

#2072

#257

#2289

#4969

#4146
Issue 1:
Terminal 0.6.2951.0, Windows 10.0.18908.0.

Steps to reproduce

Open terminal (I;m using pwsh as that's default) and hit 'Win .'

Expected behavior

Emoji picker is shown.

Actual behavior

Nothing happens.

Issue 2:
Environment

Microsoft Windows [版本 10.0.18362.267]
Windows Terminal version (if applicable):0.3.2142.0

Steps to reproduce

Open the terminal.

Switching CJK input methods.(doesn't work)

Typing.

Expected behavior

Show phrase candidate boxes.

Actual behavior

Directly entered English.
Issue 1:
Preflight Checklist

I have read the Contributing Guidelines for this project.

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

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

Issue Details

Electron Version:

5.0.6

Node Version:

8.16.0

Operating System:

Ubuntu 18.04 x64

Last Known Working Electron version:

4.2.6

Expected Behavior

It starts the electron app smoothly

Actual Behavior

npm ERR! Linux 4.18.0-25-generic

npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "start"

npm ERR! node v8.10.0

npm ERR! npm v3.5.2

npm ERR! code ELIFECYCLE

npm ERR! electron-test-sdk@1.0.0 start: electron .

npm ERR! Exit status 1

npm ERR!

npm ERR! Failed at the electron-test-sdk@1.0.0 start script 'electron .'.

npm ERR! Make sure you have the latest version of node.js and npm installed.

npm ERR! If you do, this is most likely a problem with the electron-test-sdk package,

npm ERR! not with npm itself.

npm ERR! Tell the author that this fails on your system:

npm ERR! electron .

npm ERR! You can get information on how to open an issue for this project with:

npm ERR! npm bugs electron-test-sdk

npm ERR! Or if that isn't available, you can get their info via:

npm ERR! npm owner ls electron-test-sdk

npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:

npm ERR! /home/taghive/Programming/Code/electron-test-sdk/npm-debug.log

To Reproduce

https://github.com/electron/electron-quick-start

sudo npm start (with above configuration)

Issue 2:
Preflight Checklist

I have read the Contributing Guidelines for this project.

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

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

Issue Details

Electron Version:

6.0.0-beta.5, 5.0.2

Operating System:

Linux - Ubuntu 18.04 x64

Last Known Working Electron version:

4.2.3

Expected Behavior

Electron should warn root users that Running as root without --no-sandbox is not supported., even if ELECTRON_ENABLE_LOGGING is not set

Actual Behavior

Running Electron as root fails silently, unless the user sets the environment variable ELECTRON_ENABLE_LOGGING=true. When ELECTRON_ENABLE_LOGGING=true, the console displays the message:

Running as root without --no-sandbox is not supported.

This behaviour is really confusing as causes people to think Electron doesn't work on their platform (eg see #18350) We should provide more context here.

To Reproduce

As root run:

$ git clone https://github.com/electron/electron-quick-start.git
$ npm install
$ npm start

No output.

Again as root run:

$ export ELECTRON_ENABLE_LOGGING=true
$ npm start

Warning message appears

Screenshots

Additional Information
Issue 1:
Currently, when invoking GET indexname/_mapping one gets a long list of the fields that can be expected in the index. All these have the form:

"feed": {
"type": "string",
"index": "not_analyzed"
}

For an end user, who normally cannot see the configuration, the name of the field and its properties might not be enough to understand what the field actually holds. Therefore, it would be very helpful to allow a comment field inside the object above. Here is an example:

"feed": {
"type": "string",
"index": "not_analyzed"
"comment": "feed holds the name of the feed as provided by the client side"
}

Issue 2:
Transaction logs are being persisted wrongly to the shared gateway storage, causing the full translog to be persisted each time (and not the delta), causing both wrong data stored in the gateway, and possible duplicates created when recovering.
Issue 1:
Description

I need to support several query parameters with same name in GET route. Typical request looks like this:

http://localhost/item?num=1&num=2

I configured a route

@app.get("/item", content_type=UJSONResponse)
async def get_part(num: list):
found = False
for i in num:
if i in some_data:
found = True
break
return {"found": found}

The idea is, that I can pass several numbers to check, if they exist in some_data. In my opinion, it is not a good idea to get numbers from body here, because it is a simple GET request, but in current version application expects argument "num" in body, so on my request (written above) I receive a response

{"detail":[{"loc":["body","num"],"msg":"field required","type":"value_error.missing"}]}

As I know, it is not restricted to pass several query parameters with the same name in an HTTP request by any specifications, so I would like to ask, is it possible to configure a route in FastAPI, which will be able to parse several query parameters with the same name?

Issue 2:
First Check

I added a very descriptive title to this issue.

I used the GitHub search to find a similar issue and didn't find it.

I searched the FastAPI documentation, with the integrated search.

I already searched in Google "How to X in FastAPI" and didn't find any information.

I already read and followed all the tutorial in the docs and didn't find an answer.

I already checked if it is not related to FastAPI but to Pydantic.

I already checked if it is not related to FastAPI but to Swagger UI.

I already checked if it is not related to FastAPI but to ReDoc.

Commit to Help

I commit to help with one of those options 👆

Example Code

from fastapi import FastAPI
from pydantic import BaseModel

app = FastAPI()

class ModelNoneWithUncommonDefaults(BaseModel):
x: Optional[str] = ...
y: Optional[str] = "y"

@app.get(
"/exclude_none_with_uncommon_defaults",
response_model=ModelNoneWithUncommonDefaults,
response_model_exclude_none=True,
)
def get_exclude_none_with_uncommon_defaults() -> ModelNoneWithUncommonDefaults:
return ModelNoneWithUncommonDefaults(x=None, y=None)

Description

This should return {}

Actually will raise a ValidationError

If no error would have been thrown it would return {"y": "y"} although y was set to None

See #4647 for a fix.

Operating System

macOS

Operating System Details

Current Monterey with M1 Pro chip - OS should not have any impact.

FastAPI Version

0.74.1 (git master)

Python Version

3.9.10

Additional Context

I already created a PR for this, but was not sure if this is enough. If this now is a duplicate, sorry I will do this another way the next time around.

The problem occurs as FastAPI will use exclude_none twice and by this manipulate the result data. Actually the current code only works for Optional[...] field types with a default value of None.
Issue 1:
What steps will reproduce the problem?

Don't know quite how to reproduce this but it seems to happen when deflating a tarball
we are creating using archive/tar to contain about 6 log files each of about 500 MB in
size. Maybe we are hitting some kind of 2 GB limit somewhere?

What do you see instead?

top of stack:

compress/flate.(*compressor).findMatch(0xf84153f0b0, 0x7fd87fff0000aa57, 0x55a900000002,
0x2, 0x0, ...)
go/src/pkg/compress/flate/deflate.go:157 +0x10e
compress/flate.(*compressor).deflate(0xf84153f0b0, 0xf8b5181e00)
go/src/pkg/compress/flate/deflate.go:266 +0x413
compress/flate.(*compressor).write(0xf84153f0b0, 0xf8b5189e00, 0x199a51a5199a51a5,
0xf81d25afa5, 0x0, ...)
go/src/pkg/compress/flate/deflate.go:359 +0xa0
compress/flate.(*Writer).Write(0xf84153f0b0, 0xf8b18d4000, 0x1d25afa51d25afa5,
0xf91d25afa5, 0x0, ...)
go/src/pkg/compress/flate/deflate.go:469 +0x54
compress/gzip.(*Writer).Write(0xf840112f20, 0xf8b18d4000, 0x1d25afa51d25afa5,
0xf929745094, 0x16c00000007, ...)
go/src/pkg/compress/gzip/gzip.go:190 +0x56c
archive/tar.(*Writer).Write(0xf8400a3f80, 0xf8b18d4000, 0x1d25afa51d25afa5, 0x0, 0x0,
...)
go/src/pkg/archive/tar/writer.go:184 +0xc7

Which compiler are you using (5g, 6g, 8g, gccgo)?

6g

Which operating system are you using?

linux

Which version are you using? (run 'go version')

revision 8db1b9223486

Please provide any additional information below.

Issue 2:
Now that we have internal packages we should make the go tool use an internal copy of the vcs package from the tools repo, so that we can keep the two in sync.
Issue 1:
在yml中dubbo.protocol.port的配置，修改端口号后还是取的默认的

在application.properties中配置就没事

Issue 2:
spring-boot-version : 1.5.9.RELEASE

dubbo.version : 2.6.0

bug 出现场景：

1、使用了@EnableDubbo 注解

2、配置文件使用的是 “.yml” 格式的文件

bug出现原因：

在yml 文件中，值是有数据类型的区分的，如果直接这样判断，会导致有些值被忽略
Issue 1:
Demonstrated at http://jsfiddle.net/xnhzvdoa/1/; open the error console and you should see this:

Uncaught Error: Invariant Violation: addComponentAsRefTo(...): Only a ReactOwner can have refs. This usually means that you're trying to add a ref to a component that doesn't have an owner (that is, was not created inside of another component's `render` method). Try rendering this component inside of a new top-level component which will hold the ref.

var Bug = React.createClass({
render: function() {
var html = React.renderToStaticMarkup(React.DOM.img());
return React.DOM.div({ ref: 'ref' }, html);
}
});
Bug = React.createFactory(Bug);

React.render(Bug(), document.body);

Issue 2:
Idea (that I'm pretty sure I saw elsewhere, react-native maybe?)…

We should transform our invariant calls to a conditional wrapping the call. We have to check the condition anyway and this would reduce the no-op function calls.

In otherwords

function doSomething(someArg) {
invariant(someArg !== undefined, 'hey doofus, don't pass undefined');
}

becomes

function doSomething(someArg) {
if (!(someArg !== undefined)) {
invariant(false);
}
}

Hell, we could replace the invariant(false) with throw new Error('whatevs') and get rid of the function call entirely, though it really doesn't matter much since we're going to throw (plus we'd duplicate the default string).

This might end up be a meaningless optimization…
Issue 1:
I'm submitting a ... (check one with "x")

[x] bug report => search github for a similar issue or PR before submitting
[ ] 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

When running ng-xi18n -p src/tsconfig.app.json --i18nFormat xlf and one of the node_modules includes translatable strings, the full path of that context is written to the messages.xlf file:

<trans-unit id="cedd5f9cee5d6a1681605d996cf45ab5398fabcd” datatype="html">
<source>Source Language</source>
<target/>
<context-group purpose="location">
<context context-type="sourcefile”>/Users/my_user/my_project/node_modules/my_dependency/index.ts</context>
<context context-type="linenumber">42</context>
</context-group>
</trans-unit>

Expected behavior

I'd expect something along the lines of

<trans-unit id="cedd5f9cee5d6a1681605d996cf45ab5398fabcd” datatype="html">
<source>Source Language</source>
<target/>
<context-group purpose="location">
<context context-type="sourcefile”>node_modules/my_dependency/index.ts</context>
<context context-type="linenumber">42</context>
</context-group>
</trans-unit>

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

On a team other committers will generate different output, conflicting when checking in.

I don't want to leak my internal file structure.

Please tell us about your environment:

$ npm --version
4.2.0
$ cat package.json | grep '"@angular/compiler-cli"'
"@angular/compiler-cli": "^4.1.3",

Issue 2:
I'm submitting a ... (check one with "x")

[ ] bug report => search github for a similar issue or PR before submitting
[x] 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

When ng-i18n extract strings it adds source element that contains the source code and line where the strings was extracted. This is very good.

However the extracted source code file is absolute.

<msg id="1238358838717941284"><source>D:/Source/Angular/Escape/src/app/app.component.ts:2</source>Sample</msg>

Would be better to have relative to the project root

<msg id="1238358838717941284"><source>src/app/app.component.ts:2</source>Sample</msg>

This would make it easier to move the project into different location. It might also be the different developers or localization enginerrs have different local directory structures.

Expected behavior

Use relative path.

<msg id="1238358838717941284"><source>src/app/app.component.ts:2</source>Sample</msg>

In addition it would be better to store source into an attribute instead of source element inside the string playload.

<msg id="1238358838717941284" source="src/app/app.component.ts:2">Sample</msg>

Minimal reproduction of the problem with instructions

Extract any template

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

Make localization easier.

Please tell us about your environment:

Windows 10, VS code 1.12.1

Angular version: 4.0.X

Browser: all
Issue 1:
Description of the new feature/enhancement

This FR would solve having to manually setup my workspace on every new launch. I always start with the same 3 tabs, it would be nice to launch these all in the default.

"globals": {

"defaultProfile": ["GUID1", "GUID2", "MULTI-PROFILE-GUID1", ...]

}

...

"profiles": [

{

"guid": "multi-profile guid",

"launchProfiles": ["other profile guid1", "other profile guid 2", ...]

}

]

Proposed technical implementation details (optional)

Change existing launch code into a for loop and the defaultProfile backing as a array.

Either new profile type could be introduced or the detection of launchProfiles for each profile configuration would signal needing to launch other profiles. Recursive?

Support the launching of multiple profiles in any launch action. Should be self explanitory.

Issue 2:
Environment

Windows build number: Microsoft Windows [Version 10.0.18362.175]

Windows Terminal version (if applicable): built using d82eab4

Steps to reproduce

open terminal with following profile:

{
"globals" :
{
"alwaysShowTabs" : false,
"defaultProfile" : "{9d2406b9-7e40-4e2b-a20d-82dc61c4cc24}",
"initialCols" : 80,
"initialRows" : 60,
"requestedTheme" : "dark",
"showTabsInTitlebar" : true,
"showTerminalTitleInTitlebar" : false
},
"profiles" :
[
{
"acrylicOpacity" : 0.80000001192092896,
"closeOnExit" : true,
"colorScheme" : "Solarized Dark",
"commandline" : "cmd.exe",
"cursorColor" : "#FFFFFF",
"cursorShape" : "bar",
"fontFace" : "Consolas",
"fontSize" : 10,
"guid" : "{9d2406b9-7e40-4e2b-a20d-82dc61c4cc24}",
"historySize" : 9001,
"name" : "cmd",
"padding" : "0, 0, 0, 0",
"snapOnInput" : true,
"startingDirectory" : "%USERPROFILE%",
"useAcrylic" : true
}
]
}

input characters until the line wraps, backspace once, and enter an additional character

Expected behavior

Cursor should return to the previous position following the last character on the previous line after hitting backspace.

Additional input character (sent after backspace) should show up after the last character on the previous line.

Actual behavior

Cursor returns to previous line, but with a whitespace between the last character input and the cursor position

Additional input character does not show up in terminal, although it is recognized

'..789ab' is received as input in the example below, even though it is not shown:
Issue 1:
When using hidden-* and visible-* classes, when the element is not hidden, it renders as "display: block". This won't work for inline elements (like hiding a span), so I ended up needing to create hidden-inline-*. I suppose I could add display: inline to each instance i need it, but I think that somewhat defeats the purpose of these helper classes.

Issue 2:
related to issues #8500 , #7808 , #4929 ; using .hidden-sm to hide span within .nav > li > a . Because class is display: block above -sm then text wraps to new line. Would you consider .hidden-* classes to be display: inline-block instead ?

Here's a jsfiddle of the two cases - but the repercussions could be greater outside of this situation so probably needs more consideration... http://jsfiddle.net/jholl/P86yf/