WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
I am trying to run an LSTM built with the Python API, exported to to protobuf, and evaluated in Java. After I updated my python scripts to use tf.contrib.rnn.LSTMBlockCell, LSTMBlockFusedCell, etc cell implementations, the Java portion stopped working and started throwing:

org.tensorflow.TensorFlowException: org.tensorflow.TensorFlowException: Op type not registered 'BlockLSTM' in binary running on xubuntu. Make sure the Op and Kernel are registered in the binary running in this process.

and

org.tensorflow.TensorFlowException: org.tensorflow.TensorFlowException: Op type not registered 'LSTMBlockCell' in binary running on xubuntu. Make sure the Op and Kernel are registered in the binary running in this process.

Evaluating the graph in Python works swimmingly. I didn't see anything on stack overflow. There are a couple tickets on github which might be related: #11847 and #12566

TF Version (Java and python): 1.3.0

Python Version: 2.7

Issue 2:
System information

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

TensorFlow installed from (source or binary): Binary

TensorFlow version (use command below): Tried with both 1.1.0 and 1.2.0-rc1

CUDA/cuDNN version: Running on CPU

I have SavedModel using TensorForestEstimator (RandomForest) by using export_savedmodel() it was saved successfully and able to load from SavedModel-cli too. But when trying to load using

val SAVED_MODEL_PATH =
"/Users/Documents/tensordata/1496652787";
val bundle = SavedModelBundle.load(SAVED_MODEL_PATH, "serve");

It's giving following error -:

Exception in thread "main" org.tensorflow.TensorFlowException: Op type not registered 'TreePredictions'
at org.tensorflow.SavedModelBundle.load(Native Method)
at org.tensorflow.SavedModelBundle.load(SavedModelBundle.java:38)
at ai.tenten.ml.ClassifyITCase$.main(ClassifyITCase.scala:59)

I am able to load Other saved models like HalfPlusTwo Regression and mnist dense Predict model successfully. Only in RandomForest It's giving error I thing some op is missing from build or Java API is not updated.
Issue 1:
We are currently running on superset 0.22.1 with python 2.7 on Ubuntu 16.04 LTS.

We are planning to upgrade superset to 0.35.0 version with python 3.6.9 on Ubuntu 18.04.3 LTS.

Can you kindly let us know whether we can use old superset 0.22.1 dashboards after upgrading to superset 0.35.0 ?

OR

Should we build all the superset dashboards from scratch after upgrading to 0.35.0 version ?

Environment

OS: Ubuntu 16.04 LTS

superset version: 0.22.1

python version: 2.7

Issue 2:
How to reproduce the bug

Go to explore view of time-series chart,

change time range.

from browser console you will see when you updated the time picker, new query is triggered.

but this trigger won't update chart, there is an overlay on top of chart.

user has to click on run query button on overlay to trigger another query.

Environment

latest master

cc @junlincc @zhaoyongjie
Issue 1:
I am getting duplicate debugViews.ts in recently opened. Both point to the same file, however they seem to have a different editors associated with them - eg selections are different.

Not sure how I got in this state, but I this is the first time I get duplicate entires. So my suspicion is that at a point of time the workbench created an additional editor for a file that was already open

Issue 2:
VSCode Version: 1.2.0-alpha

OS Version: Windows 10

Steps to Reproduce:

Open integrated terminal

Type git clone

Right click just to the right of the typing cursor

Paste https://github.com/Microsoft/vscode-smoketest-express.git

After scrolling back using the left arrow on the keypad, you cant get all the way back:
Issue 1:
It would be interesting to have the ability to define different word wrap values for different languages, specially if you use Code for editing normal programming languages like JavaScript, Pascal and non programming languages, like Markdown.

I tend to respect the word wrap values defined in the main IDE for a particular language (if exists/is used), and turn off word wrap for for Markdown/Log/Text files. But today, in Code I only have settings for the Editor (editor.wrappingColumn and editor.wrappingIndent).

Thanks in advance

Issue 2:
In our project we have a number of files where tabs are strictly required (a format we do not control). However, we want to normalize tabs to spaces throughout the rest of the project.

For now, I just ask that people don't edit those files in VSCode. I even considered adding them to the ignore list for VSCode itself. But it's not uncommon to have file-specific settings, so I thought it would be nice if VSCode allowed for more complex patterns - much like files.exclude, perhaps something like:

"editor.insertSpaces": true,
"diffEditor.ignoreTrimWhitespace": true,
"files.settings": {
"**/*.idt": {
"editor.insertSpaces": false,
"diffEditor.ignoreTrimWhitespace": false
}
}
Issue 1:
Playwright version

1.13.0

Operating system

Windows

What browsers are you seeing the problem on?

No response

Other information

Playwright inspector

What happened? / Describe the bug

When running playwright code generator chromium page was open but playwright inspector was opened but cant able to see in the screen. But when we are using laptop with more screen we can able to view it.

For your reference: video url

https://user-images.githubusercontent.com/61179075/126861280-159115f1-3b4d-4d4a-8c9e-4b980b58ad19.mp4

And expectation was it should support for laptop with small screen also. Thank you in advance

Code snippet to reproduce your bug

No response

Relevant log output

No response

Issue 2:
Context:

Playwright Version: 1.9.0

Operating System: Windows10

Node.js version: v12.18.2

Browser: Chromium

Extra: laptop with 13,3" screen, 1920 x 1080 (FullHD) resolution, scaled to 150%, setup with external monitor placed above laptop screen

Example script

const { chromium } = require('playwright');
(async () => {
const browser = await chromium.launch();
const page = await browser.newPage();
})().then(() => console.log('finished'));

When trying to debug script (set PWDEBUG=1) Playwright Inspector window is opened by Playwright outside of visible screen space - it is opened past the right border of the screen.

in

src\server\supplements\recorder\recorderApp.ts RecorderApp.open

there is a definitions of arguments for opening the window

const args = [

'--app=data:text/html,',

'--window-size=600,600',

'--window-position=1280,10',

];

when 1280 is changed to say 700 then Playwright Inspector windows is visible after it is first opened by Playwright.
Issue 1:
Edit: I'm guessing this is known and just unavoidable without some extra working around using the resolution of the promise returned from dock.show()?

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: 7.1.9

Operating System: macOS 10.13.6

Last Known Working Electron version: `Unk

Expected Behavior

Duplicate app icons shouldn't be possible.

Actual Behavior

Duplicate icons can accumulate. After quitting the application the extra icons remain and cannot be quit or force quit to get rid of them. Oddly, simply left-clicking them does get them to go away.

To Reproduce

remote.app.dock.show();
setTimeout(remote.app.dock.hide, 50);
setTimeout(remote.app.dock.show, 100);
setTimeout(remote.app.dock.hide, 150);
setTimeout(remote.app.dock.show, 200);
setTimeout(remote.app.dock.hide, 250);

Note: remote not required, just easier

Additional Information

If a user tries to force quit a zombie icon, macOS will prevent re-opening the app without the user acknowledging that it crashed last time, as it would if you actually force quit the app.

This should be easy enough for users to workaround, but I assume this isn't the intended behavior.

Edit: Simply checking for !dock.isVisible() before calling dock.show() is insufficient to prevent this behavior. The bug persists

The real world situation for this is an application that hides/shows with a global hotkey - a user may hit the hotkey by accident and then again to hide it, but they may end up with duplicated dock icons because of this quick action. I toggle back and forth 3x in the repro code above to ensure reproduction, but it can be reproduced with less.

Issue 2:
Output of node_modules/.bin/electron --version: 3.0.0

Operating System (Platform and Version): Debian GNU/Linux 9 (stretch)

Output of node_modules/.bin/electron --version on last known working Electron version (if applicable): (will check and update)

Expected Behavior

Should load the index.html page as per the documentation for getting started with electron.

Actual behavior

Shows a transparent application with screenshot of the background.

To Reproduce

Follow the exact steps for electron-quick-start

You can fork electron-quick-start and include a link to the branch with your changes.

If you provide a URL, please list the commands required to clone/setup/run your repo e.g.

Screenshots

Additional Information

On an related or unrelated note, npm install -g electron fails with even sudo during creation of folder '.electron' in the '/usr/lib/node_modules/electron'.
Issue 1:
See repro below:

import pandas as pd
df_with_ts = pd.DataFrame(data=[['BL', pd.Timestamp('2015-02-01')], ['TH', pd.Timestamp('2015-02-02')]], columns=['item', 'date'])
res = df_with_ts.groupby(['date']).apply(lambda x: pd.Series(x['item'].unique()[0]))
In []: res
Out[]:
0
date
2015-02-01 NaT
2015-02-02 2015-02-17

In []: res.dtypes
Out[]:
0 datetime64[ns]
dtype: object

It looks like this is happening because pd.Timestamp('TH') is valid and results in no exceptions. If you replace the string 'TH' with something else then the resulting column's dtype is object, as expected. The order of columns in the above example does not matter.

For comparison, this case works as expected:

df = pd.DataFrame(data=[['BL', '2015-02-01'], ['TH', '2015-02-02']], columns=['item', 'date'])
res = df.groupby(['date']).apply(lambda x: pd.Series(x['item'].unique()[0]))

In []: res
Out[]:
0
date
2015-02-01 BL
2015-02-02 TH

In []: res.dtypes
Out[]:
0 object
dtype: object

output of show_versions() below (using Miniconda):

In []: from pandas.util.print_versions import show_versions

In []: show_versions()

INSTALLED VERSIONS
------------------
commit: None
python: 2.7.9.final.0
python-bits: 64
OS: Windows
OS-release: 7
machine: AMD64
processor: Intel64 Family 6 Model 60 Stepping 3, GenuineIntel
byteorder: little
LC_ALL: None
LANG: None

pandas: 0.15.2
nose: 1.3.4
Cython: 0.21.2
numpy: 1.8.2
scipy: 0.14.0
statsmodels: 0.5.0
IPython: 2.3.0
sphinx: 1.2.3
patsy: 0.2.1
dateutil: 2.2
pytz: 2014.9
bottleneck: 0.8.0
tables: 3.1.1
numexpr: 2.3.1
matplotlib: 1.4.0
openpyxl: 2.0.2
xlrd: 0.9.3
xlwt: 0.7.5
xlsxwriter: 0.6.6
lxml: 3.4.1
bs4: 4.3.2
html5lib: 0.999
httplib2: None
apiclient: None
rpy2: None
sqlalchemy: 0.9.8
pymysql: None
psycopg2: None

Issue 2:
The .apply on DataFrame is converting my string to a date. I have posted this on StackOverflow:

http://stackoverflow.com/questions/28487105/pandas-on-apply-passing-wrong-value

I'm not sure if I'm doing something wrong or it is a bug, but it seems quite strange behavior.

Example here

In [8]: df = pd.DataFrame({'wing1':wing1, 'wing2':wing2, 'mat':mat}, index=belly)

In [9]: df
Out[9]:
mat wing1 wing2
216 2016-01-22 2T15 416
3T19 2019-09-07 4H19 4T20

In [17]: df.loc['3T19']
Out[17]:
mat 2019-09-07 00:00:00
wing1 2015-02-16 04:19:00
wing2 2015-04-20 00:00:00
Name: 3T19, dtype: datetime64[ns]

In [18]: df.loc['216']
Out[18]:
mat 2016-01-22 00:00:00
wing1 2T15
wing2 416
Name: 216, dtype: object
Issue 1:
Describe the bug

AxiosError: unexpected end of file

at AxiosError.from (C:\Users\samqw\Documents\scrapping\sense\node_modules\axios\dist\node\axios.cjs:785:14)

at BrotliDecompress.handleStreamError (C:\Users\samqw\Documents\scrapping\sense\node_modules\axios\dist\node\axios.cjs:2696:29)

at BrotliDecompress.emit (node:events:525:35)

at emitErrorNT (node:internal/streams/destroy:151:8)

at emitErrorCloseNT (node:internal/streams/destroy:116:3)

at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {

code: 'Z_BUF_ERROR',

errno: -5,

config: {

transitional: {

silentJSONParsing: true,

forcedJSONParsing: true,

clarifyTimeoutError: false

},

adapter: [ 'xhr', 'http' ],

transformRequest: [ [Function: transformRequest] ],

transformResponse: [ [Function: transformResponse] ],

timeout: 0,

xsrfCookieName: 'XSRF-TOKEN',

xsrfHeaderName: 'X-XSRF-TOKEN',

maxContentLength: -1,

maxBodyLength: -1,

env: { FormData: [Function], Blob: [class Blob] },

validateStatus: [Function: validateStatus],

headers: AxiosHeaders {

Accept: 'application/json, text/plain, /',

'User-Agent': 'axios/1.2.1',

'Accept-Encoding': 'gzip, compress, deflate, br'

},

method: 'get',

url: 'https://www.sense.com.tr/kaban-469',

data: undefined

},

To Reproduce

const response = await axios.get("https://www.sense.com.tr/kaban-469");

const outerhtml = response.data;

Code snippet

No response

Expected behavior

this snippet code above was working perfectly on "axios": "^0.21.0", before upgrading to "axios": "^1.2.1"

Axios Version

No response

Adapter Version

No response

Browser

No response

Browser Version

No response

Node.js Version

No response

OS

No response

Additional Library Versions

No response

Additional context/Screenshots

No response

Issue 2:
It seem axios simply concats the headers into a single string separated by comma rather than returning them in an array, this is problematic if a header value contains a comma.

Example server:

import * as http from 'http';

//Lets define a port we want to listen to
const PORT = 8080;

//Create a server
const server = http.createServer((request, response) => {
response.setHeader('x-warning', ['a', 'b']);
response.end('It Works!! Path Hit: ' + request.url);
});

//Lets start our server
server.listen(PORT, () => {
console.log("Server listening on: http://localhost:%s", PORT);
});

Result:

> void(axios = require('axios'))
undefined
> axios.get('http://localhost:8080').then(r=>console.log(r.headers))
Promise { <pending> }
> { 'x-warning': 'a, b',
date: 'Fri, 06 Jan 2017 19:06:02 GMT',
connection: 'close',
'content-length': '22' }

Curl for sanity:

curl localhost:8080 -vvv
* Rebuilt URL to: localhost:8080/
* Trying ::1...
* TCP_NODELAY set
* Connected to localhost (::1) port 8080 (#0)
> GET / HTTP/1.1
> Host: localhost:8080
> User-Agent: curl/7.51.0
> Accept: */*
>
< HTTP/1.1 200 OK
< x-warning: a
< x-warning: b
< Date: Fri, 06 Jan 2017 19:04:49 GMT
< Connection: keep-alive
< Content-Length: 22
<
* Curl_http_done: called premature == 0
* Connection #0 to host localhost left intact
It Works!! Path Hit: /%
Issue 1:
I'm fairly sure this is unrelated to #5389

Returning a non-Promise custom type from an async function causes the compiler to crash.

Given this tsconfig

{
"compilerOptions": {
"experimentalAsyncFunctions": true,
"target": "ES6"
}
}

and this code

type SomeType = {
someValue: string
}

async function someFunction(): SomeType {
return {
someValue: ''
}
}

tsc will crash with the following

TypeError: Cannot read property 'flags' of undefined
at isKnownProperty (/Users/andrewsmith/.nvm/versions/node/v0.12.6/lib/node_modules/typescript/lib/tsc.js:14041:25)
at hasExcessProperties (/Users/andrewsmith/.nvm/versions/node/v0.12.6/lib/node_modules/typescript/lib/tsc.js:14063:26)
at isRelatedTo (/Users/andrewsmith/.nvm/versions/node/v0.12.6/lib/node_modules/typescript/lib/tsc.js:13955:25)
at checkTypeRelatedTo (/Users/andrewsmith/.nvm/versions/node/v0.12.6/lib/node_modules/typescript/lib/tsc.js:13903:26)
at checkTypeAssignableTo (/Users/andrewsmith/.nvm/versions/node/v0.12.6/lib/node_modules/typescript/lib/tsc.js:13886:20)
at checkReturnStatement (/Users/andrewsmith/.nvm/versions/node/v0.12.6/lib/node_modules/typescript/lib/tsc.js:19460:29)
at checkSourceElement (/Users/andrewsmith/.nvm/versions/node/v0.12.6/lib/node_modules/typescript/lib/tsc.js:20461:28)
at Object.forEach (/Users/andrewsmith/.nvm/versions/node/v0.12.6/lib/node_modules/typescript/lib/tsc.js:90:30)
at checkBlock (/Users/andrewsmith/.nvm/versions/node/v0.12.6/lib/node_modules/typescript/lib/tsc.js:18973:16)
at checkSourceElement (/Users/andrewsmith/.nvm/versions/node/v0.12.6/lib/node_modules/typescript/lib/tsc.js:20440:28)

tsc -v returns message TS6029: Version 1.6.2

Issue 2:
/usr/local/lib/node_modules/typescript/lib/tsc.js:29825

async function abc():number{
return 123;
}

/usr/local/lib/node_modules/typescript/lib/tsc.js:29825
throw e;
^
TypeError: Cannot read property 'flags' of undefined
at isRelatedTo (/usr/local/lib/node_modules/typescript/lib/tsc.js:13951:56)
Issue 1:
Tim Chen opened SPR-3180 and commented

I have a PropertyPlaceholderConfigurer that is prefixed with #{

I can use it for any spring definition except those that are using namespaces.

For example:

Code:

<tx:advice id="txAdvice" transaction-manager="jtaTxManager">
<tx:attributes>
<tx:method name="*" propagation="REQUIRED" timeout="#{operational:jtaTimeout}"/>
</tx:attributes>
</tx:advice>

It wont process the value and I get exceptions that the value must be an integer.

How can I use PropertyPlaceholderConfigurer with namespaces?

The forum link is http://forum.springframework.org/showthread.php?p=101823#post101823

Affects: 2.0.2

Issue Links:

#9523 PropertyPlaceholderConfigurer doesn't work on beans defined in own schema e.g. tx:* ("is duplicated by")

3 votes, 11 watchers

Issue 2:
John Baker opened SPR-6052 and commented

The following exception has been noted when the WL JMS drivers failed to connect:

Exception in thread "jms.jobs.messageListenerContainer.SRUpdateFromSiebel-1" java.lang.NullPointerException

at java.lang.String.indexOf(String.java:1564)

at java.lang.String.indexOf(String.java:1546)

at org.springframework.jms.support.JmsUtils.buildExceptionMessage(JmsUtils.java:255)

at org.springframework.jms.listener.DefaultMessageListenerContainer.handleListenerSetupFailure(DefaultMessageListenerContainer.java:745)

at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:897)

at java.lang.Thread.run(Thread.java:595)

The problem is this line of code in JmsUtils.buildException:

if (linkedEx != null && message.indexOf(linkedEx.getMessage()) == -1) {

linkedEx may not be null, but the message can be null, so it simply need to be:

if (linkedEx != null && linkedEx.getMessage() != null && message.indexOf(linkedEx.getMessage()) == -1) {

Affects: 2.5.6

Issue Links:

#9948 JmsUtils.buildExceptionMessage throws NPE if the linked exception doesn't have a message ("duplicates")
Issue 1:
Feature request

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

My development setup consists of multiple Docker containers:

Next.js application running in development mode

Mock API

Proxy that is used in front of Next.js application and mock API containers so one host is used for accessing both the application and API.

Next.js 8.0 has introduced WebSockets based ping approach. This in turn uses randomly assigned port for WebSocket connection and makes it impossible for me to specify which port to open in proxy container to proxy to the application container. This results in refresh of the page every 5 seconds after WebSocket connection fails.

Describe the solution you'd like

Possibility to configure WebSocket ping port will solve this issue since that specific port can be opened and proxied in the proxy container.

Describe alternatives you've considered

Solution described above is desired and probably absolutely doable. As an alternative I would consider possibility to specify ping approach: either fetch based or WebSocket based.

Issue 2:
Bug report

Describe the bug

We can't use nextjs v8 in dev mode with docker because it reload the DOM every 5 seconds.

He can't access to the websocket port. I can open this port in my Dockerfile but it change every time I launch next

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

Just start next v8 with docker in dev mode

Screenshots

on-demand-entries-client.js:136 WebSocket connection to 'ws://0.0.0.0:41861/' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED

System information

OS: macOS

Version of Next.js: 8.0.0
Issue 1:
by jim@superluckycasino.com:

Before filing a bug, please check whether it has been fixed since the
latest release. Search the issue tracker and check that you're running the
latest version of Go:

Run "go version" and compare against
http://golang.org/doc/devel/release.html If a newer version of Go exists,
install it and retry what you did to reproduce the problem.

Thanks.

What steps will reproduce the problem?
If possible, include a link to a program on play.golang.org.
1. Download go1.1.2.darwin-amd64.pkg
2. Run installer
3. Installer fails with no explanation; some go files appear to be installed.

What is the expected output?
Successful installation.

What do you see instead?
Failed installation. Seriously. If you're going to fail, say why, or at least point to a
log file.

Which compiler are you using (5g, 6g, 8g, gccgo)?
I don't know how to determine this.

Which operating system are you using?
Mac OSX 10.8.4

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

Please provide any additional information below.

Issue 2:
by supermighty:

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

Using play.golang.org, fmt.Println out a time formatted using time.RFC822 and
time.RFC822Z.

What is the expected output?
It is expected that they will be different.
- time.RFC822 should output the alpha time zone (EST)
- time.RFC822Z should output the numeric time zone (-0500)

What do you see instead?
They will be the same.

Which compiler are you using (5g, 6g, 8g, gccgo)?
This uses the current play.golang.org compiler

Which operating system are you using?
play.golang.org

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

Please provide any additional information below.

I ran this test locally too. (Debian wheezy, go 1.0.2) and it worked as expected.

This seems to be an issue with play.golang.org

Thank you for all your hard work and freely giving me Go.

Ukiah
Issue 1:
After updating Symfony I thought I could see the effect of #14601 but it doesn't happen because there is two translations folders into the security component.

I updated Security/Resources/translations/security.fr.xlf but Security/Core/Resources/translations/security.fr.xlf is used.

I don't know if it's legit but now that translations have diverged I think something must be done.

Issue 2:
PHP 7

Using Symfony\Component\Validator\Constraints\Collection;

I'm using Symfony 3.1 and I hope I'm not doing something wrong. When I validate a field, it doesn't stop after the first violation. Example :

$errors = $val->validate(
$info,
new \Symfony\Component\Validator\Constraints\Collection([
'fields' => array(
'specialKey' => array(
new NotBlank(),
new Length(['min' => 8,'max' => 20]),
new Regex(['value' => "/^[A-Za-z]*$/"]),
)
),
'allowExtraFields' => true,
])
);

I'm getting :

'This value is too short. It should have 8 characters or more.'
'This value is not valid.'

I found a walk-around for those who are interested :

$errors = $val->validate(
$info,
new \Symfony\Component\Validator\Constraints\Collection([
'fields' => array(
'specialKey' => array(
new NotBlank(['groups' => 'groupe1']),
new Length(['min' => 8,'max' => 20,'groups' => 'groupe2']),
new Regex(['value' => "/^[A-Za-z]*$/",'groups' => 'groupe3']),
)
),
'allowExtraFields' => true,
]),
new GroupSequence(array('Default','groupe1','groupe2','groupe3'))
);