WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Bug report

What is the current behavior?

When creating a new ModuleFederationPlugin with shared libraries, if one of the packages has a configuration of singleton: true, requiredVersion: false, it will produce a remote entry file that uses the "loadFallback" function to try and get the package. This can lead to package duplication if a newer version of the library is provided by this module (or another module).

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

Sample repo: https://github.com/colacadstink/WebpackModuleFederationBug

The dist directory is created from the standard webpack.config.js, and the workingDist directory from the webpack.working.config.js file. The only differences between these files are the output directories and the requiredVersion of lodash.

Note the differences between dist/remoteEntry.js and workingDist/remoteEntry.js, specifically on line 380:

The dist copy of the file is using the loadFallback function, which will always return the highest version number available, regardless of if another instance has already been created; this can lead to situations where more than one instance is constructed, breaking the singleton flag.

The workingDist copy uses the loadSingletonVersionCheckFallback function with a version argument of [0]. This will let us use whatever version of the package is currently loaded, regardless of version, which is the same behavior I'd expected with the requiredVersion being false.

What is the expected behavior?

I feel as if this should be acting similarly to what happens if the requiredVersion is set to '*', which causes the method used in the remote entry file to be "loadStrictSingletonVersionCheckFallback" with a version argument of [0] (which does work as expected).

Other relevant information:

webpack version: v5.64.2

Node.js version: Tested on v12.16.1 and v12.20.1

Operating System: n/a, but definitely there on Windows

Additional tools: I used Lodash for demonstration purposes, but there's nothing special about it.

Issue 2:
Now when webpack is well typed and provides 12000+ lines of typescript code, it would be great to have a type for the main configuration function - the one which is exported.

Here is a question I asked a few days ago on StackOverflow: https://stackoverflow.com/questions/69584268/what-is-the-type-of-the-webpack-config-function-when-it-comes-to-typescript

Let me repeat it here:

Currently when one exports an object from the config-file, the Configuration type can be used:

const config: Configuration = {
mode: 'production',
// ...
}

But what is the type for exporting the function? E.g.

export default (...): ... => {
return {
mode: 'production'
// ...
}
}

Surprisingly, but I couldn't find the proper type among a bunch of the types provided for webpack in https://github.com/webpack/webpack/blob/main/types.d.ts

If you followed the SO line above, you'd see the answer from Igor: https://stackoverflow.com/a/69608855/1223483

Basically he makes this job: implementing missed types.

But how could they be missed?
Issue 1:
Hi everyone!

I upgraded the application from RC4 to RC5 and was working just fine. It was also working fine when i modified the bootstrap to the latest root module method. Then i converted one section of the application using NgModule approach. This Module is pulled in using routing.

So the issue is i have two components (Nav, header) which are being used in different components. When i put them in the declarations part of the Featured Module i get a warning in my browser console that its declared in two places, AppModule and CatalogModule (even though i have not explicitly declared it in AppModule.

After some research i found out that RC5 automatically pulls in all declarations to avoid breaking changes for developers using previous versions. So i Added the components explicitly in the declarations of the AppModule (root Module) and removed it from the CatalogModule (feature module). There are no compiler/browser errors now but the components are not loaded in that route. The header and Nav is simply missing.

For other components its working which belong to AppModule.

Can anyone please shine some light on what i could be doing wrong ?

Issue 2:
Before integrating the definitions to the package directly including those into a ASP.NET 4 project that uses SystemJS was really easy: Just put the file from DefinitelyTyped into the project, do an import * as ng from 'angular2/angular2' in a TypeScript file and everything worked fine. This doesn't fit anymore (in my case), since there is no single .d.ts file with all definitions.

When I was using the import statement above, the 'angular2/angular2' (path and JS file) was resolved by SystemJS and Visual Studio knew about it because of the definition file that was declaring a module. How do I achieve that Visual Studio will know about that again? I tried many hours without success, except using the old Alpha stage .d.ts file and changing it slightly to declare it as angular2/core.

How can this problem be resolved without using the new project system of ASP.NET 5?
Issue 1:
Is there a way to observe alt key press state change while displaying application menus?

I would like to update the menu items (which I am not sure is possible either) while the menu is displayed and the user is toggling the alt key.

This behavior can be seen in the OS X Finder app for instance.

Issue 2:
A dynamic menu item is a command that changes when the user presses a modifier key.

https://developer.apple.com/library/mac/documentation/UserExperience/Conceptual/OSXHIGuidelines/MenuChanging.html

Operating system: OS X
Issue 1:
React version:

17.0.2

eslint-plugin-react-hooks version:

4.2.0

Steps To Reproduce

import useEfect from react library

type useEfect(

Link to code example:

https://github.com/LeonardoRick/podcastr

The current behavior

output:

[Error - 16:40:28] ESLint stack trace:
[Error - 16:40:28] TypeError: Cannot read property 'type' of undefined
Occurred while linting D:\GIT\podcastr\src\Components\Player\index.tsx:16
at visitCallExpression (D:\GIT\podcastr\node_modules\eslint-plugin-react-hooks\cjs\eslint-plugin-react-hooks.development.js:1736:24)
at D:\GIT\podcastr\node_modules\eslint\lib\linter\safe-emitter.js:45:58
at Array.forEach (<anonymous>)
at Object.emit (D:\GIT\podcastr\node_modules\eslint\lib\linter\safe-emitter.js:45:38)
at NodeEventGenerator.applySelector (D:\GIT\podcastr\node_modules\eslint\lib\linter\node-event-generator.js:256:26)
at NodeEventGenerator.applySelectors (D:\GIT\podcastr\node_modules\eslint\lib\linter\node-event-generator.js:285:22)
at NodeEventGenerator.enterNode (D:\GIT\podcastr\node_modules\eslint\lib\linter\node-event-generator.js:299:14)
at CodePathAnalyzer.enterNode (D:\GIT\podcastr\node_modules\eslint\lib\linter\code-path-analysis\code-path-analyzer.js:711:23)
at D:\GIT\podcastr\node_modules\eslint\lib\linter\linter.js:954:32
at Array.forEach (<anonymous>)

error line:

// eslint-plugin-react-hooks\cjs\eslint-plugin-react-hooks.development.js:1736:24:
switch (callback.type) {

The expected behavior

No errors showing, since I'm currently typing the code

Issue 2:
eslint-plugin-react-hooks version: 4.2.0

Steps To Reproduce

I know it shouldn't exist in production code, but it's annoying while editing some files.

import React, { useEffect } from "react";

const App = () => {
useEffect(); // <-
return null;
};

export default App;

Link to code example: https://codesandbox.io/s/polished-sun-3wr27?file=/src/App.js

The current behavior

ESLint crashed.

TypeError: Cannot read property 'type' of undefined

The expected behavior

ESLint doesn't crash but reports an error instead.
Issue 1:
Tested in VSCode 1.2 and in the playground

class A {
method(): this {
return this;
}
}

class B extends A {}

const c = new B().method();

c's type is B (correctly). However, if I call super.method() from B, its return type is A instead of B:

class A {
method(): this {
return this;
}
}

class B extends A {
method(): this {
return super.method(); // Type 'A' is not assignable to type 'this'.
}
}

Issue 2:
TypeScript Version:

nightly with "node.d.ts" from typings

We recently add thisin to es5.d.ts

Expected behavior:

No error

Actual behavior:

Duplicate Identifier with the same property defined in "node.d.ts"
Issue 1:
At http://scikit-learn.org/stable/modules/classes.html#module-sklearn.utils (and in the deprecated section too), the signature of functions that take *args, **kwargs (e.g. utils.resample) appear with spurious backslashes, e.g.

utils.resample(\*arrays, \*\*options)	Resample arrays or sparse matrices in a consistent way

Issue 2:
Description

Not sure why this is happening, but if you look at the pipeline docs or any other module that uses * in their methods, the asterisks show up as \*. Perhaps something to have to do with escaping characters?

Expected Results

There are no \ before the asterisks.
Issue 1:
Issue Type:

Bug Report

Ansible Version:

ansible 1.8 (devel 6180d9a) last updated 2014/08/18 17:03:49 (GMT +1100)

Environment:

Bug discovered with Debian x86_64, confirmed and bisected with Gentoo x86_64.

Summary:

When using group_by to create a group on the fly (e.g. group_by: key="{{ ansible_os_family }}"), the group_vars fail to override vars in group_vars/all.

I bisected this to f6a55a3.

Steps To Reproduce:

site.yml:

---
- hosts: all
tasks:
- group_by: key={{ ansible_os_family }}
- fail: msg="testvar = {{ testvar }}"
when: testvar != "override OK"

group_vars/all:

---
testvar: override FAIL

group_vars/Gentoo (where "Gentoo" is whatever your ansible_os_family actually resolves to):

---
testvar: override OK

Expected Results:

PLAY [all] ********************************************************************

GATHERING FACTS ***************************************************************
ok: [127.0.0.1]

TASK: [group_by key={{ ansible_os_family }}] **********************************
changed: [127.0.0.1]

TASK: [fail msg="testvar = {{ testvar }}"] ************************************
skipping: [127.0.0.1]

PLAY RECAP ********************************************************************
127.0.0.1 : ok=2 changed=1 unreachable=0 failed=0

Actual Results:

PLAY [all] ********************************************************************

GATHERING FACTS ***************************************************************
ok: [127.0.0.1]

TASK: [group_by key={{ansible_os_family}}] ************************************
changed: [127.0.0.1]

TASK: [fail msg="testvar = {{testvar}}"] **************************************
failed: [127.0.0.1] => {"failed": true}
msg: testvar = override FAIL

FATAL: all hosts have already failed -- aborting

PLAY RECAP ********************************************************************
to retry, use: --limit @/home/direvus/site.retry

127.0.0.1 : ok=2 changed=1 unreachable=0 failed=1

Issue 2:
Issue Type: Bug Report

Ansible Version: 1.6.2 - 1.7.1

Environment: any

Summary:

Playbook level variable are ignored when we use vars_files with filename defined with {{ansible_os_family}}

If we import variable file with static name (RedHat.yml for example) - no issue

Steps To Reproduce:

Test playbook

---

- name: 'Test Precedence'
hosts: vagrantcentos
user: vagrant
sudo: yes

vars:
some_var: "foo"

vars_files:
- vars/{{ ansible_os_family }}.yml
#- vars/RedHat.yml
- vars/other_vars.yml

tasks:
- debug: msg={{some_var}}
tags:
- test

and additional files

group_vars/all

some_var: "bar"

vars/RedHat.yml

useless_var: "oops"

vars/other_vars.yml

other_var: "woot"

Expected Results:

debug message should be

"msg": "foo"

this result returned when I comment

- vars/{{ ansible_os_family }}.yml line

Actual Results:

Unexpectedly we got:

"msg": "bar"
Issue 1:
The SciPy autopower spectrum psd has a crosspower spectrum csd counterpart, so it would make sense if the autopower spectrogram had a crosspower equivalent.

Our group has a prototype that is just a wrapper around _spectral_helper. This seems cleaner than the alternative of iterating csd on a per-time-window basis.

Issue 2:
Hi,

As I was looking for a way to generate random rotation matrices uniformly, I found these two methods:

scipy.stats.special_ortho_group

scipy.spatial.transform.Rotation.random

As far as I understand Rotation.random is just a special case of stats.special_ortho_group where dim=3.

Am I right or am I missing something? If correct, should these functions be refactored?

Thanks !
Issue 1:
Just bringing attention to this particular issue since all the @ mentions are getting no response there. See FriendsOfSymfony/FOSUserBundle#747. If there is a better way to bring stuff like this to attention, then it would be good to know.

Quoting @stof:

The remember me services are private so they are removed from the container when optimizing it. This means that the has checks in the LoginManager will return false even when the remember me is activated for the firewall.

Issue 2:
This is common pattern when user clicks confirmation token.

I'm unable to set remember me in clean way.
Issue 1:
Version:

go version devel +4ffa5eb Sun Mar 27 05:31:54 2016 +0000 linux/amd64

Env:

GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/shaharko/gopath"
GORACE=""
GOROOT="/home/shaharko/src/go_master"
GOTOOLDIR="/home/shaharko/src/go_master/pkg/tool/linux_amd64"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build742740600=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"

$ go tool nm pkg/linux_amd64/io.a | grep gclocals | awk '{ print $3 }' | wc -l
142 # total gclocals
$ go tool nm pkg/linux_amd64/io.a | grep gclocals | awk '{ print $3 }' | uniq | wc -l
38 # unique gclocals

The symbol duplication factor is ~3.5x.

Issue 2:
http://play.golang.org/p/VMk-h3Js4z

produces the following output:

6 2 5 3 4 1

which appears to initialize the variables a to f in the order they are mentioned in the
composite literal in makeOrder.

However, the spec says ( http://tip.golang.org/ref/spec#Program_execution ):

"If the initializer of A depends on B, A will be set after B. Dependency analysis
does not depend on the actual values of the items being initialized, only on their
appearance in the source. A depends on B if the value of A contains a mention of B,
contains a value whose initializer mentions B, or mentions a function that mentions B,
recursively. It is an error if such dependencies form a cycle. If two items are not
interdependent, they will be initialized in the order they appear in the source,
possibly in multiple files, as presented to the compiler."

- dependency only depends on the appearance in the source: makeOrder depends on a...f
because it contains a mention of a...f. It doesn't say it depends on the order of those
mentions.

- not interdependent items are initialized in the order they appear in the source: a...f
are not interdependent, so they should be initialized in the order they appear: a, b, c,
d, e, f

Therefore the correct result should be:

1 2 3 4 5 6

gccgo produces this correct order.
Issue 1:
In issue #13133 for AngularJS it becomes clear that AngularJS doesn't work well with AMD. But AMD or CommonJS seem to become the default loading technique for TypeScript.

Will Angular v2 cope with this problem and work with AMD/CommonJS loaders, like RequireJS?

Issue 2:
Most developer workflows are based around CJS (Browserify or WebPack) and not System.js. Since System.js can consume cjs bundles, I suggest we replace our System.register bundle with a CJS bundle. In this case, developers that use Browserify or WebPack will be able to use it, and it should still work with System.

Notes:

System.register has a lot of overhead comparing to CJS. My naive measurements showed the difference is about 18%.

When using a CJS bundle, you cannot important submodudles, only "angular2/angular2". I think this is an advantage cause it prevents users from depending on private API.

Finally, once we produce a CJS bundle, I think we should change our Getting Started guide to use WebPack instead of System.js. The reason is WebPack provides a lot better experience out of the box (including TypeScript and Babel).

The WebPack config for an Angular 2 project written with TypeScript is about 10 lines long:

module.exports = {
resolve: {
root: __dirname,
extensions: ['.ts', '.js']
},
entry: ["webpackapp"],
output: {filename: "webappapp_bundle.js"},
externals: {'angular2/angular2': "angular2"},
devtool: 'source-map',
module: {
loaders: [
{ test: /\.ts$/, loader: 'ts-loader' }
]
}
}

You get source maps, dev server with live reload, production/dev modes -- a very good first impression and a clear path to production setting.

/cc @IgorMinar @mhevery @rkirov @jeffbcross
Issue 1:
Compiled from getbootstrap.com:

.modal-backdrop.fade {opacity:0;}

.modal-backdrop.in {opacity:0.5;}

The result is a solid black backdrop with opacity:1;

These declarations are of equal specificity and cancel each other out.

the declaration for "in" should read:

.modal-backdrop.fade.in{opacity:0.5;}

Issue 2:
Hi!

I just generated a customized version and the modal background is totally black (I also generated a version without any change to be sure it wasn't me that caused that):

The download link on the home page does have transparency:
Issue 1:
System info

Playwright Version: [v1.32.3]

Operating System: [All, Windows 11, Ubuntu 20, macOS 13.2, etc.]

Browser: [All, Chromium, Firefox, WebKit]

I am coming over to this project from webdriverio to evaluate this.

In Selenium and webdriverio we would just call waitForEnabled() or waitForEnabled({ reverse: true }) but I see only

waitFor("attached"|"detached"|"visible"|"hidden")

I see that isEnabled has timeout option but that does not work for me to really know when it will be. Is there a polling or something that we can tap into and if so how would one go about ?

Issue 2:
System info

Playwright Version: [v1.33]

Operating System: [Windows 11]

Browser: [WebKit]

i set userAgent in browsercontext using launchPersistentContext as

Mozilla/5.0 (iPhone; CPU iPhone OS 16_1_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.1 Mobile/15E148 Safari/604.1

but when opening new window and checking in webkits console its showing as

Mozilla/5.0 (Windows NT 6.2; Win64; x64) AppleWebKit/605.1.15 (KHTML, like Gecko)

below code used for test

Source code

const { webkit } = require('playwright');

(async () => {
const context = await webkit.launchPersistentContext('my-data', {
userAgent: 'Mozilla/5.0 (iPhone; CPU iPhone OS 16_1_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.1 Mobile/15E148 Safari/604',
headless: false
});
const page = await context.newPage();
page.goto('https://www.whatismybrowser.com/detect/what-is-my-user-agent/');
})();
Issue 1:
Update:

If anyone ends up needing this functionality, I've released it as vue-nonreactive with the appropriate admonitions and everything.

We have some non-plain models where we need to disable Vue's observation and walking. An example is a resource model that has access to a cache so that it can lookup related resources. This causes all of the objects in the cache to become watched (probably inefficient), as well as some additional interactions with other code. Currently, we get around this by setting a dummy Observer on the cache. Something similar to...

import get from 'http';
import Resource from 'resource';

new Vue({
data: { instance: {}, },
ready() { this.fetch(); },

methods: {
fetch() {
const Observer = Object.getPrototypeOf(this.instance.__ob__).constructor;

get('/api/frobs')
.then(function(data) {
// initialize Resource w/ JSON document
const resource = new Resource(data);

// Protect cache with dummy observer
resource.cache.__ob__ = new Observer({});

this.instance = resource;
});
},
},
});

This does work, but

relies on vue's internals

requires an already observed object since we cannot import the Observer class directly.

Proposal:

Add an official method for explicitly disabling Vue's observation/walking. eg, something like...

const someThing = {
nestedThing: {},
};

// make entire object non-reactive
Vue.nonreactive(someThing);

// make nested object non-reactive
Vue.nonreactive(someThing.nestedThing);
vm.$set('key.path', someThing);

Considerations:

What should happen if a user set a reactive key path to an non-reactive object? Should vue warn the user? eg,

vm.$set('a', Vue.nonreactive({});

// different from..
vm.$set('a', {
someKey: Vue.nonreactive({}),
});

Should an already reactive object warn the user if attempted to be made non-reactive? eg,

// error
Vue.nonreactive(vm.$data.a)

// valid
Vue.nonreactive(_.clone(vm.$data.a));

Issue 2:
What problem does this feature solve?

for example,there is a row component which includes some cols,i wanna the cols have transition effect,and give row some props.But ,the props i wrote does no effect on the row component.and if i use 'row > transtion-group' combination, some css will lose there effect

What does the proposed API look like?

<transtion-group type=row :option={row's props}>
Issue 1:
When adding a node to a load balance with state=present, it throws an error on subsequent ansible runs with:

"Duplicate nodes detected. One or more nodes already configured on load balancer."

I would assume "present" should just be a changed=False noop if it's already in the LB.

Issue 2:
ISSUE TYPE

Bug Report

COMPONENT NAME

ios_config, iosxr_config, nxos_config

Any config module with before and after

ANSIBLE VERSION

$ ansible --version
ansible 2.2.1.0
config file = /home/jmighion/git/blank-ansible-repo/ansible.cfg
configured module search path = Default w/o overrides

CONFIGURATION

inventory = inventory

forks = 1400

roles_path = roles

retry_files_enabled = False

OS / ENVIRONMENT

N/A

SUMMARY

Any commands in before: or after: in any network config module that has those params will not be added to the command stack if you're using a template. Not sure why the before or after commands cannot be added after the template is rendered or added into the template before rendering so the commands.

STEPS TO REPRODUCE

- name: Configure NTP
ios_config:
before: default ntp
src: ios.j2
save: yes
provider: "{{ cli }}"

ios.j2:

ntp authentication-key 1 md5 {{ ntp_peering_key }}
ntp authenticate
ntp trusted-key 1
ntp source {{ ntp_source }}
ntp server {{ npt_service_ipv4 }} key 1

EXPECTED RESULTS

default ntp
ntp authentication-key 1 md5 {{ ntp_peering_key }}
ntp authenticate
ntp trusted-key 1
ntp source {{ ntp_source }}
ntp server {{ npt_service_ipv4 }} key 1

ACTUAL RESULTS

"backup_path": "/home/jmighion/git/blank-ansible-repo/roles/config_ntp/backup/host_config.2017-03-16@17:35:09",
"changed": true,
"invocation": {
"module_args": {
"after": null,
"auth_pass": null,
"authorize": false,
"backup": true,
"before": [
"default ntp"
],
"config": null,
"defaults": false,
"force": false,
"host": "test_host",
"lines": null,
"match": "line",
"parents": null,
"password": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER",
"port": null,
"provider": {
"host": "test_host",
"password": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER",
"username": "test_user"
},
"replace": "line",
"save": true,
"src": "ntp authentication-key 1 md5 stuff!\nntp authenticate\nntp trusted-key 1\nntp source Vlan0\nntp server ip.ip.ip.ip key 1\n",
"ssh_keyfile": null,
"timeout": 10,
"transport": null,
"use_ssl": true,
"username": "test_user",
"validate_certs": true
}
},
"warnings": []