WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
by raul.san@sent.com:

When it's used a certificate with signature algorithm RMD160 (created with OpenSSL), the
error message is:

x509: certificate signed by unknown authority

It should show a error message according to the real problem.

Issue 2:
If a certificate is signed with a hash function that wasn't compiled in the error
message isn't bad, but could be better:

x509: certificate signed by unknown authority (possibly because of "x509: cannot
verify signature: algorithm unimplemented" while trying to verify candidate
authority certificate "CA Cert Signing Authority")
Issue 1:
Description of the problem

To reproduce this issue

Create PlaneGeometry

Upload any non-power of 2 texture eg 1600 x 1200

When mipmaping is disabled:

material.map.minFilter = THREE.LinearFilter;

material.map.magFilter = THREE.LinearFilter;

texture is displayed properly.

When mipmapping is enabled (default) , looking close up (first mipmap) is looks ok, with angel, distance texture looks wrong, mipmaps are scaled, stretched.

Textures 1024 x 1024 are working properly.

As far as we can see problem occurs only on Windows 7 64bit and Chrome. In Internet Explorer works fine.

Tested in latest version of Three.js editor r85 but issue is present in other versions (tested r77).

Disabled mipmaps

Enabled mipmaps (default)

Three.js version

Dev

r85

r77

Browser

All of them

Chrome

Firefox

Internet Explorer

OS

All of them

Windows 7 64 bit

macOS

Linux

Android

iOS

Hardware Requirements (graphics card, VR Device, ...)

Intel Core i7 , Nvidia 1080 GTX

Chrome Version 58.0.3029.110 (64-bit)

Issue 2:
Description of the problem

When texture in not power of two, it generates wrong mipmaps (I suppose) after resize of texture. When mipmaps are not generated 2D texture displays correctly.

Inside "WebGLTextures.js" there is a function "makePowerOfTwo" where image is resized. I have made quick workaround to achive correct rendering on Windows 7:

after line: context.drawImage( image, 0, 0, canvas.width, canvas.height );

I add: context.getImageData(0, 0, canvas.width, canvas.height);

and it seems to be resised properly to generate proper mipmaps, but I'm not sure why and if calling getImageData is proper way...

On Firefox it looks fine but got console message Error: WebGL warning: texImage2D: Conversion requires pixel reformatting

Three.js version

Dev

r85

...

Browser

All of them

Chrome

Firefox

Internet Explorer

OS

All of them

Windows

macOS

Linux

Android

iOS

Hardware Requirements (graphics card, VR Device, ...)

Windows 7 32-bit, SP1, CPU i7 2600S
Issue 1:
I tried using the @types/sinon package and had problems.

I tried using the latest stable version of tsc. https://www.npmjs.com/package/typescript

Authors: @MrBigDog2U @rationull @lumaxis @nicojs @43081j

Is there a reason why the createStubInstance is not defined?

Conforming http://sinonjs.org/releases/v4.1.2/sandbox/ it should exist.

Issue 2:
I tried using the @types/xxxx package and had problems.

I tried using the latest stable version of tsc. https://www.npmjs.com/package/typescript

Mention the authors (see Definitions by: in index.d.ts) so they can respond.

Authors: @MrBigDog2U , @rationull , @lumaxis , @nicojs , @43081j

according to sinonjs/sinon#1602

there is a new method for Sandbox:

createStubInstance()

From type perspective it should be the same as the global createStubInstance method I guess.
Issue 1:
Such a function is often need i think...could be great to have an Util for this ..?

Issue 2:
Hello,

I have a problem with guessing maxlength attribute if field definition has attr option. Please see below:

$builder
->add(
'title',
null,
[
'attr' =>
[
'autocomplete' => 'off',
'data-display' => true,
],
]
);
.......

/**
* Title
*
* @var string
*
* @ORM\Column(type="string", length=255, nullable=false)
* @Assert\NotNull(groups={})
* @Assert\Length(max=255, groups={})
*/
private $title;

In this case I don't see maxlength attribute in html output, but if I declare field like this (without attr option):

$builder
->add(
'title',
null,
[
]
);

maxlength attribute appears in html output.

Could you please clarify this behavior.

Thanks in advance
Issue 1:
System info

Playwright Version: [v1.33.0]

Operating System: [Multiple]

Browser: [Chromium]

Other info: PW runs under docker official image, tried mcr.microsoft.com/playwright:v1.33.0 and mcr.microsoft.com/playwright:v1.32.0-focal - same result

Env: Node.js 17

This may be important: I use PW browser remote connection, PW and Chromium are in PW's image docker container and another docker container based on node:17-alpine image connects to it and performs RPA actions

Source code (partial)

const closeModalButtonLocator: Locator = page.locator('[data-automation-id="ModalDialog"] [aria-label="Close"]');
if (await closeModalButtonLocator.isVisible()) {
const notShowButtonLocator: Locator = page.locator(
'[data-automation-id="ModalDialog"] button >> text=Don\'t show me this again'
);
if (await notShowButtonLocator.isVisible()) {
await notShowButtonLocator.click({ force: true, timeout: this.config.longActionTimeout });
} else {
await closeModalButtonLocator.click({ force: true, timeout: this.config.longActionTimeout });
}
}

Expected

await locator.isVisible() should return boolean value immediately

Actual

await locator.isVisible() throws exception Timeout 5000ms exceeded, but it shouldn't wait for anything and should just return element is visible or not. it sometimes happens in different places where isVisible are used, regardless of element actually visible or not

P.S can't publish all source code or full trace, but last error action screenshot from trace viewer is representative, i suppose

Issue 2:
I have a similar issue as in #20928 where I have an SVG image in a react project when I hide the SVG get the error TypeError: Cannot read properties of undefined (reading 'includes').

Se reproduction below.

System info

Playwright Version: v1.33.0

Operating System: All

Browser: Chromium

Other info:

Source code

I provided exact source code that allows reproducing the issue locally.

Link to the GitHub repository with the repro

https://github.com/jonaskello/playwright-bug-repro

Steps

See the readme in repo above

Expected

No errors

Actual

Error:

t (in promise) TypeError: Cannot read properties of undefined (reading 'includes')
at parseSelectorString (<anonymous>:1422:17)
at parseSelector (<anonymous>:1322:18)
at InjectedScript.parseSelector (<anonymous>:4440:20)
at makeStrict (eval at extend (localhost/:4673:40), <anonymous>:1017:43)
at cssFallback (eval at extend (localhost/:4673:40), <anonymous>:1061:10)
at generateSelector (eval at extend (localhost/:4673:40), <anonymous>:826:40)
at Recorder._updateModelForHoveredElement (eval at extend (localhost/:4673:40), <anonymous>:3404:36)
at Recorder._onFocus (eval at extend (localhost/:4673:40), <anonymous>:3395:10)
at Recorder._performAction (eval at extend (localhost/:4673:40), <anonymous>:3531:10)
parseSelectorSt
Issue 1:
Waypoint: Bring your JavaScript Slot Machine to Life

I added the following code to Basic Javascript Waypoint 39:

$( $ )

The page froze and I could not interact with it. I tried refreshing and it would freeze once the page loaded because my code was still there. I don't know how to clear out the code so I can start the Waypoint over and complete it.

Issue 2:
Challenge http://freecodecamp.com/challenges/waypoint-bring-your-javascript-slot-machine-to-life has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

In typing this suggested code to solve the challenge, the automatic closing of parentheses leads the student to type

$($)

which immediately causes the script to become unresponsive. This is on Firefox for Mac v39.0.3
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

I am not sure if this is the requested behavior, but this behavior does not seem logical to me.

Current behavior

When using Reactive Forms, a formGroup containing FormControls which are invalid is shown as invalid which is normal, but it does not contain any errors.

Expected behavior

We should be able to get all the errors from FormControls | FormGroups | FormArrays inside their containing FormGroup.

Reproduction of the problem

http://plnkr.co/edit/OMnHZkHRIc75RRQM9XRz?p=preview

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

I have a form with required inputs. I fill in some input but not all of them.

So some input are in the pristine and also invalid. (like in the example of the tutorial for template driven forms): http://plnkr.co/edit/rzQfRbufDDRmDtGFbPIy?p=preview).

I decide to click on the submit button, but I have errors, so I want to show all the inputs with errors that the user has missed.

Please tell us about your environment:

OS X 10.11, Visual Studio Code

Angular version: 2.0.0-rc.6

Browser: [all ]

Language: [TypeScript 2.0.0]

Node (for AoT issues): node --version = v6.5.0

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

[ ] bug report
[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 there are errors in a form group, the formGroup.status is 'INVALID' but the formGroup.errors property is null.

ex.

formGroup.controls.username.errors: {invalidEmail: true}
formGroup.errors: null

Expected/desired behavior

When the validity of a FormControl changes, have the parent FormGroup.errors merged with the errors from the controls. This is similar to how the angularjs formController.$error property works.

https://docs.angularjs.org/api/ng/type/form.FormController

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

This would be helpful because I prefer to only disable a submit button when specific errors are on a form, such as required. With this I could drive that attribute off the formControl.errors value instead of formControl.status.

ex.

From:
<button [disabled]="myForm.status !== 'VALID'">Submit</button>

To:
<button [disabled]="myForm.errors.required">Submit</button>
Issue 1:
Description:

The signature of the following methods changed from (0.21.4)

post<T = any, R = AxiosResponse<T>>(url: string, data?: any, config?: AxiosRequestConfig): Promise<R>;
put<T = any, R = AxiosResponse<T>>(url: string, data?: any, config?: AxiosRequestConfig): Promise<R>;
patch<T = any, R = AxiosResponse<T>>(url: string, data?: any, config?: AxiosRequestConfig): Promise<R>;

to (0.22.0)

post<T = never, R = AxiosResponse<T>>(url: string, data?: T, config?: AxiosRequestConfig<T>): Promise<R>;
put<T = never, R = AxiosResponse<T>>(url: string, data?: T, config?: AxiosRequestConfig<T>): Promise<R>;
patch<T = never, R = AxiosResponse<T>>(url: string, data?: T, config?: AxiosRequestConfig<T>): Promise<R>;

breaking every usage of the method, when using generics, e.g.:

type RequestData = {
input: string;
};

type ResponseData = {
value: string;
};

async function test(): Promise<void> {
const requestData: RequestData = { input: "input" }
const {data} = await axios.post<ResponseData>("https://some-endpoint.com/v1/endpoint", requestData);
console.log(data.value);
}

The new generics will now cause compile errors, since RequestData and ResponseData are not the same type.

The following workaround helps:

async function test(): Promise<void> {
const requestData: RequestData = { input: "input" }
const {data} = await axios.post<RequestData, AxiosReponse<ResponseData>>("https://some-endpoint.com/v1/endpoint", requestData);
console.log(data.value);
}

These changes seem arbitrary, and possibly done by mistake, as it is very unlikely, that a Post-Request has exactly the same type for its payload, as it has for its response.

Issue 2:
when doing react.js project with isomorphic this message will appear when using axios on the server side.
Issue 1:
Bug report

What is the current behavior?

<w> [webpack.cache.PackFileCacheStrategy] Caching failed for pack: Error: Can't resolve 'url' in '/Users/keenwon/Test/webpack-test'
<w> while resolving 'url' in /Users/keenwon/Test/webpack-test as file
<w> at resolve esm file url
<w> at file dependencies /Users/keenwon/Test/webpack-test/webpack.config.mjs
<w> at file /Users/keenwon/Test/webpack-test/webpack.config.mjs
<w> at resolve commonjs /Users/keenwon/Test/webpack-test/webpack.config.mjs

If the current behavior is a bug, please provide the steps to reproduce.

works fine, no warnings

What is the expected behavior?

Other relevant information:

webpack version: 5.70.0

Node.js version: v14.19.0

Operating System: macOS 12.3

Additional tools:

demo

repo https://github.com/keenwon/webpack-test, switch to node-prefix branch

node: doesn't work either

Issue 2:
Hey,

I'm trying to pack https://github.com/ded/klass and webpack isn't impressed with it:

> webpack node_modules/klass/klass.js klass.packed.js

Hash: 214a480310b53c1a2c79305e8fbc6cf7
Compile Time: 124ms
Chunks: 1
Modules: 1
Modules including duplicates: 1
Modules first chunk: 1
main klass.packed.js: 893 chars/bytes

<id> <size> <filename>
klass.packed.js
0 ./~/klass/klass.js
ERROR: Entry module failed!
Error: File "/Users/rainerdreyer/Workspace/PipeDream/node_modules/klass/klass.js" parsing failed: TypeError: Cannot call method 'push' of undefined
@ ./klass.js

But there is no call to push in the klass source code as far as I can see. Could you check why webpack can't handle this? Unfortunately most of my code uses inheritance with klass, so the packaging of everything fails.

Thanks!
Issue 1:
Problem description

When using TypeScript and upgrading to 1.0.0-beta.7, I get the following type error:

Failed to compile.

/Users/wcandillon/tmp/fitspace/node_modules/material-ui/styles/withTheme.d.ts
(1,23): error TS2307: Cannot find module './theme'.

This error seems to make sense since ./theme doesn't exists in node_modules/material-ui/styles.

Steps to reproduce

Here is a simple app example

import * as React from "react";
import * as ReactDOM from "react-dom";

import { MuiThemeProvider, createMuiTheme, createTypography, createPalette } from "material-ui/styles";
import { FontStyle } from "material-ui/styles/typography";
import { Palette } from "material-ui/styles/palette";

const palette: Palette = createPalette({});

const fontStyle: FontStyle = {
fontFamily: "Lato, Roboto, Helvetica, Arial, sans-serif",
fontSize: "14px",
fontWeightLight: 300,
fontWeightRegular: "normal",
fontWeightMedium: "bold"
};

const theme = createMuiTheme({
typography: createTypography(palette, fontStyle)
});

ReactDOM.render(
<MuiThemeProvider {...{theme}}>
<div>Hello</div>
</MuiThemeProvider>,
document.getElementById("root") as HTMLElement
);

Versions

Material-UI: 1.0.0-beta.7

React: 15.6.1

Browser: Any

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

Expected Behavior

I expect the tests to run without a problem.

Current Behavior

I get an error:

TypeError: parentInstance.children.indexOf is not a function

I think this is due to portals not working properly in combination with jest snapshots.

Steps to Reproduce (for bugs)

import React from 'react';
import { storiesOf } from '@storybook/react';
import AlertDialog from './AlertDialog';

storiesOf('AlertDialog', module)
.add('basic', () => <AlertDialog bodyKey="test" onClick={() => {}} titleKey="test" open />);

Where <AlertDialog /> is a boring wrapper around <Dialog />.

I'm sorry for not including a code snippet. I don't know how to set up the tests to illustrate the issue, but I tried my best to provide as much relevant information as possible.

Context

I'm using storybooks with storysnaps (jest snapshots), and our tests are failing. I'm pretty sure it has something to do with enzymejs/enzyme#1150 and potentially reactjs/react-modal#553 could benefit from a solution as well.

Your Environment

Tech
Version

Material-UI
1.0.0-beta.21

React
16.0.0

browser
N/A

Additional

I have a feeling this is something that could be caught in storyshots but I'm not experienced enough with the material at hand. Any pointers, or better yet solutions would be greatly appreciated.

I'm not against fixing it and contributing either (if I get the right pointers to help me out).
Issue 1:
Migrated issue, originally created by Anonymous

Although the select, when evaluated directly, is correct, when nested in a query via the in_ function, with very circularly interconnected tables with joined table inheritance, it repeats a from clause element, which is sufficient to cause most databases not to execute the command.

See the attached code for an example...

Attachments: bug_test.py

Issue 2:
Migrated issue, originally created by Michael Bayer (@zzzeek)

diff --git a/lib/sqlalchemy/engine/default.py b/lib/sqlalchemy/engine/default.py
index 3e5f339..9f845e7 100644
--- a/lib/sqlalchemy/engine/default.py
+++ b/lib/sqlalchemy/engine/default.py
@@ -474,6 +474,23 @@ class DefaultDialect(interfaces.Dialect):
self.set_isolation_level(dbapi_conn, self.default_isolation_level)

+class StrCompileDialect(DefaultDialect):
+
+ statement_compiler = compiler.StrSQLCompiler
+ ddl_compiler = compiler.DDLCompiler
+ type_compiler = compiler.StrSQLTypeCompiler
+ preparer = compiler.IdentifierPreparer
+
+ supports_sequences = True
+ sequences_optional = True
+ preexecute_autoincrement_sequences = False
+ implicit_returning = False
+
+ supports_native_boolean = True
+
+ supports_simple_order_by_label = True
+
+
class DefaultExecutionContext(interfaces.ExecutionContext):
isinsert = False
isupdate = False
diff --git a/lib/sqlalchemy/sql/compiler.py b/lib/sqlalchemy/sql/compiler.py
index c5f87cc..076ae53 100644
--- a/lib/sqlalchemy/sql/compiler.py
+++ b/lib/sqlalchemy/sql/compiler.py
@@ -2118,6 +2118,30 @@ class SQLCompiler(Compiled):
self.preparer.format_savepoint(savepoint_stmt)

+class StrSQLCompiler(SQLCompiler):
+ """"a compiler subclass with a few non-standard SQL features allowed.
+
+ Used for stringification of SQL statements when a real dialect is not
+ available.
+
+ """
+
+ def visit_getitem_binary(self, binary, operator, **kw):
+ return "%s[%s]" % (
+ self.process(binary.left, **kw),
+ self.process(binary.right, **kw)
+ )
+
+ def returning_clause(self, stmt, returning_cols):
+
+ columns = [
+ self._label_select_column(None, c, True, False, {})
+ for c in elements._select_iterables(returning_cols)
+ ]
+
+ return 'RETURNING ' + ', '.join(columns)
+
+
class DDLCompiler(Compiled):

@util.memoized_property
@@ -2640,6 +2664,17 @@ class GenericTypeCompiler(TypeCompiler):
return type_.get_col_spec(**kw)

+class StrSQLTypeCompiler(GenericTypeCompiler):
+ def __getattr__(self, key):
+ if key.startswith("visit_"):
+ return self._visit_unknown
+ else:
+ raise AttributeError(key)
+
+ def _visit_unknown(self, type_, **kw):
+ return "%s" % type_.__class__.__name__
+
+
class IdentifierPreparer(object):

"""Handle quoting and case-folding of identifiers based on options."""
diff --git a/lib/sqlalchemy/sql/elements.py b/lib/sqlalchemy/sql/elements.py
index de17aab..fe2fecc 100644
--- a/lib/sqlalchemy/sql/elements.py
+++ b/lib/sqlalchemy/sql/elements.py
@@ -429,7 +429,7 @@ class ClauseElement(Visitable):
dialect = self.bind.dialect
bind = self.bind
else:
- dialect = default.DefaultDialect()
+ dialect = default.StrCompileDialect()
return self._compiler(dialect, bind=bind, **kw)

def _compiler(self, dialect, **kw):
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:

7.1.11

Operating System: MacOS 10.15.4

MacOS 10.15.4

Last Known Working Electron version:

unknown

Expected Behavior

When opening a dialog, such as About, VoiceOver should be able to read and interact with it and its controls.

Actual Behavior

VoiceOver does not see dialog contents in many cases.

To Reproduce

Download and install Visual Studio code.

Start VoiceOver, then Code.

Go to Visual Studio Code/About, and press Enter.

Try interacting with the dialog and read the contents, or navigate to the OK and Copy buttons using VoiceOver commands.

Screenshots

Additional Information

VoiceOver will track the focus somewhat, but not reliably, when using the Tab key to navigate. But VoiceOver commands such as CTRL+Option+Arrow keys don't work, VoiceOver only sees the Close, Minimize, and Zoom buttons.

This looks similar to #17207, only that this pertains to dialogs, not web content.

Issue 2:
Issue Details

Electron Version:

greater equal 6.0.0

greater equal 7.0.0-beta.1

Operating System:

Windows 10 17763 x64

Last Known Working Electron version:

lesser equal 5.0.11

lesser equal 6.0.0-beta.12

Expected Behavior

Closing the created window should not let the creator window freeze.

Actual Behavior

The creator window freezes.

To Reproduce

Create a window (this is the creator window) with following webPreferences set:

preload: some preload file which at least requires the electron remote module

nativeWindowOpen: true

sandbox: true (can be false when nodeIntegrationInSubFrames is true)

nodeIntegrationInSubFrames: true (can be false when sandbox is true)

When at least one of sandbox or nodeIntegrationInSubFrames is set to true the problem occours.

Load a website which opens a new window on a click (I used https://www.w3schools.com/jsref/tryit.asp?filename=tryjsref_win_open3).

Open a new window by clicking a link which should open a new window.

Close the new window.

Try to select some text in the creator window, when the problem occours any interaction should not be possible.
Issue 1:
seriously, each tsconfig.json has to have its own folder in order to be referenced with --project parameter

What if I need 2 projects based on the same set of files?

Issue 2:
This would allow you to specify a tsconfig.json that has a different name.

If you specify a directory, it should first try to resolve tsconfig.json. If it can't find it, it should find the first tsconfig*.json file

References: #2868 (comment)
Issue 1:
My main issue is with the character "$", currently when trying to select $myVar the double click only select myVar.

This is uber annoying since i'm used to call my variable like this.

Moreover when editing php scripts it gets more difficult to avoid this issue.

Overall, the double click selection should stick to the variable name pattern of the current language if possible, or accept the $ in the word, at least.

Issue 2:
Now that Language Specific Configuration Settings, have landed, should we consider removing $ from nonWordCharacters? How often does one want to select only the text of a variable name, and not the dollar sign too?