WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
I'm currently using babelify to transform my source code + global shimming babel-core/browser-polyfill.js through a vendor file.

I noticed redefinitions of _createClass [et al] and the docs mentioned to use { optional: 'runtime' }, but this has the unfortunate side effect of also including regenerator/core-js, extending the dev build time.

It would be nice if I can define { optional: 'runtime.helpers' } and have it include only the helpers.

Issue 2:
As far as I can tell the runtime transform is all-or-nothing, all I'm interested in is getting rid of the redundant helpers inlined into every module, but it seems I can't have that without also the "risk" of getting dependencies on the other runtimes (notably core-js).

Have I missed something or would it not make sense to have a separate transform for just this? They seem to have rather separate concerns from my perspective (avoid redundant helper code vs add dependencies for optional features).
Issue 1:
marc schipperheyn opened SPR-9538 and commented

When you Cache a Collection of elements, you are caching the entire collection as an entry.

The underlying elements can also be part of other @Cacheable entries, leading to duplicates and unnecessary memory consumption. Let's take the scenario of a Facebook Wall where a WallPost can be shared across hundreds of Walls with each Wall being a different collection of elements. Caching each collection would quickly become impossible or inefficient with high memory use and high numbers of cache refreshes.

If the item to be cached is a collection, it could be considered to cache each individual element separately and cache the collection as a collection of references to the individual entries.

EhCache supports this with the putAll method.

Ideally you should be able to configure this so that the following @Cacheable methods

mgr.getItem(Long id);

mgr.getItems();

mgr.getItems(Long userId);

all take their items from the same pool.

When a collection requests items that are not available in the pool, even more ideally, a dao request would be made for the missing items.

Affects: 3.1.1

Issue Links:

#17326 Caching strategy ("duplicates")

Issue 2:
Martin Vanek opened SPR-9000 and commented

In xml configuration I often use bean with parent="true" to set default values in parent context and multiple nonabstract beans in several child contexts with mandatory but always different dependency.

Because abstract bean concept is missing in @Bean code configuration this leads to lots of duplication

For example I have abstract LocalContainerEntityManagerFactoryBean bean in parent "platform" context preconfigured with jpaVendorAdapter and jpaPropertyMap, but dataSource is specified in child "dbmodel" context

Affects: 3.1 GA
Issue 1:
Continuing conversation started here: https://discuss.elastic.co/t/coerce-object-to-string/56748/3

Description of the problem including expected versus actual behavior:

Would like to be able to treat an object field as String given the following mapping:

"properties": {
"severity": {
"index": "not_analyzed",
"type": "string"
},
"metadata": {
"type": "string"
"coerce": true
}
}

Indexing the following document:

{
"severity": "ERROR",
"metadata": {
"someKey": "someValue",
"someKey": {
"some nested key": "some nested value"
}
}
}

should store the document under metadata as a searchable String.

Right now, it is not possible to coerce anything to a String.

Issue 2:
Describe the feature:

There are cases where complex objects need to be passed to tokenizers. I am writing a new feature that will allow a mapping to specify that a property of type string may coerce an object within that property to a string.

PUT /test
{
"mappings": {
"test": {
"properties": {
"a": {
"type": "string",
"coerce": true
}
}
}
}
}

PUT /test/test/1
{
"a": {
"b":"2",
"c":"3"
}
}

In this example, the tokenizer will be passed "{"b":"2","c":"3"}". It will be up to the tokenizer to decide how to treat that. The default tokenizer returns the tokens "b", "2", "c" and "3".

This situation occurs frequently in library data. Complex objects have been created and the values of some of the properties effect how the other properties are treated. A simple example occurs with book titles. There is a piece of data that specifies how many leading characters should be stripped from the title to use it as a sort key.

So far, the changes have been restricted to StringFieldMapper and TokenCountFieldMapper. I am making the changes in version 2.1.0 and expect to merge them into all subsequent versions.

I expect to be able to use the copy_to parameter, but don't know exactly how that will work yet.
Issue 1:
One limitation of the functional approach is discoverability: which functions can be applied to a given type? This is not necessary however: We (should) know all the functions which take an object of given type as first argument. This leads to the possibility of code completion:

abstract type Animal end
struct Cat <: Animal end
struct Fish <: Animal end
swims(Cat)=false
swims(Fish)=true
pussy=Cat()
pussy.swims() # <--- NEW syntax, same as swims(pussy), but discoverable via <tab>

The important point is that it doesn't change the fundamentals of the language at all**, it's just syntactic sugar with the huge benefit of discoverability in the REPL. It might also hugely increase adoption.

Corollary: An inverse 'methods' function which lists all the methods for a given type (can be huge).

(** I've read https://discourse.julialang.org/t/psa-julia-is-not-at-that-stage-of-development-anymore/44872 )

Issue 2:
Since Julia is struct oriented, this could be a nice way make the language more ergonomic for methods

https://en.wikipedia.org/wiki/Uniform_Function_Call_Syntax

Assume

struct Blah
...
end

foo(b::Blah,i::Int32)
...
end

b = Blah(..)

In addition to this syntax

foo(b,123)

this would also be acceptable if a function signature existed with Blah as first parameter type

b.foo(123)

Edited: fixed function name to be idiomatic
Issue 1:
Recently, I've been developing fast permutation tests that can make use of numpy/scipy matrix operations.

So far, I have developed 3 permutation tests: a mean test, a t-test and a pearson correlation test.

To get an idea for the timings, I've benchmarked the mean test to a naive implementation on a 60x60 table and with 1000 permutations. Below are the timings

Naive time [s]: 1.91008838018

Numpy time [s]: 0.0174480279287

If you guys are down, I can start committing these algorithms into scipy. In the near future, I plan on implementing ANOVA tests such as an F-test and a Krustal-Wallis test.

Issue 2:
Apparently these two functions do exactly the same but there are no links between them in the documentation. Is there a reason to keep the two? If so, perhaps it's worth adding to the docs.

https://github.com/scipy/scipy/blob/master/scipy/linalg/decomp_lu.py#L17
Issue 1:
I'm opening this to discuss possible options:

I've been scrutinizing ES indexing performance on the NYC taxi data set (1.2 B taxi rides, numerics heavy: http://www.nyc.gov/html/tlc/html/about/trip_record_data.shtml).

These documents are small (24 fields, though a bit sparse with ~23% cells missing) and are almost entirely numbers (indexed as points + doc values).

As a "ceiling" for indexing performance I also indexed the same data set using Lucene's "thin wrapper" demo server (http://github.com/mikemccand/luceneserver), indexing the same documents as efficiently as I know how (see indexTaxis.py).

The demo Lucene server has many differences vs. ES: it has no transaction log (does not periodically fsync), uses addDocuments not updateDocument, can index from a more compact documents source (190 GB CSV file, vs 512 GB json file for ES), does not add a costly _uid field (nor _version, _type) , uses a streaming bulk API, etc. I disabled _all and _source in ES, but net/net ES is substantially slower than the demo Lucene server.

So, one big thing I noticed that is maybe a lowish hanging fruit is that ES loses a lot of its indexing buffer to LiveVersionMap: if I give ES 1 GB indexing buffer, and index into only 1 shard, and disable refresh, the version map is taking ~2/3 of that buffer, leaving only ~1/3 for Lucene's IndexWriter:

node0: [2016-08-03 09:39:07,557][DEBUG][index.engine ] [node0] [taxis][0] use refresh to write indexing buffer (heap size=[313.7mb]), to also clear version map (heap size=[730.3mb])

This also means ES is necessarily doing periodic refresh when I didn't ask it to.

This is quite frustrating because I don't need optimistic concurrency here, nor real-time gets, nor refreshes. However, I fear the version map might be required during recovery, to ensure when playing back indexing operations from the transaction log that they do not incorrectly overwrite newer indexing operations? But then, this use case is also append-only, so maybe during recovery we could safely skip that, if the user turns on this new setting.

The version map makes an entry in a HashMap for each document indexed, and the entry stores non-trivial information, creating at least 4 new objects, holding longs/ints, etc. If we can't make it turn-off-able maybe we should instead try to reduce its per-indexing-op overhead...

Issue 2:
the node level TTL Purger thread fires up bulk delete request that might trigger auto_create_index if the purger thread runs a bulk after the index has been deleted.
Issue 1:
ISSUE TYPE

Bug Report

ANSIBLE VERSION

All recent releases

CONFIGURATION

N/A

OS / ENVIRONMENT

Ubuntu 16.04 4.4.0-24

SUMMARY

An error prevents from building the debian package from git sources.

STEPS TO REPRODUCE

release_number=$(your call)

build_date=$(date --rfc-2822)
echo --------
echo Cleaning
echo --------
cd git-ansible
git reset --hard
git clean -fxd :/
git fetch --progress --prune origin
git checkout v${release_number}

echo -------------------------------------------------------
echo "Copying Debian control folder in the expected location"
echo -------------------------------------------------------
rsync -av --delete packaging/debian .

echo --------------------------------------------------------------------------
echo "Modifying debian/changelog with current release & date"
echo ---------------------------------------------------------------------------
sed -i 1,6d debian/changelog
sed -i "1s/^/ansible (${release_number}) unstable; urgency=low\n\n * ${release_number}\n\n -- Jean-Christophe Manciot <manciot.jeanchristophe@gmail.com> $build_date\n\n/" debian/changelog

echo --------
echo Building
echo --------
dpkg-buildpackage -b -m"Jean-Christophe Manciot <manciot.jeanchristophe@gmail.com>"

ACTUAL RESULTS

...
dh_install -pansible
dh_install: Cannot find (any matches for) "docs/man/man1/*.1" (tried in ".")
dh_install: ansible missing files: docs/man/man1/*.1
dh_install: missing files, aborting
/usr/share/cdbs/1/rules/debhelper.mk:213: recipe for target 'binary-install/ansible' failed
make: *** [binary-install/ansible] Error 255
dpkg-buildpackage: error: debian/rules binary gave error exit status 2

Full log with 2.1.1.0-0.1.rc1:

Cannot find any matches for docs-man-man1-*.1.txt

Issue 2:
ansible_sudo=True/False

in inventory.

[krb5]
localhost
s8webera ansible_ssh_user=root ansible_sudo=False ansible_python_interpreter=/usr/bin/python2.7

This is important on mixed environment where some system dont have sudo installed.

Here is a current working solution that im using in production.

This was programmed as a hack.. So please could a project maintainer develop this fix correctly.

file:///home/s8weber/srv/ansible/lib/ansible/runner/init.py

def _executor_internal(self, host):
''' executes any module one or more times '''

host_variables = self.inventory.get_variables(host)

if host_variables.get('ansible_sudo', None):
self.sudo = host_variables.get('ansible_sudo', None) == 'True'

....
Issue 1:
Electron version: 1.2.5

Operating system: Mac OS X el capitan

When sending IPC messages between the renderer and the main process, I think we sometimes get duplicate messages.

What kind of reliability is ensured by Electron? Should we handle de-duplication ourselves in the case of the same messages being re-sent?

I don't know if that's the right place for that question but I tried to post it on the discussion forum of Electron a few days ago and nobody answered so I am trying here.

Thanks

Issue 2:
After creating a notification and passing a tag, then subsequent notifications with the same tag don't show up for the entire lifespan of the app.

Electron version: 1.8.1

Operating system: Windows 7 x64

Expected behavior

New notifications should open after the last one has closed.

Actual behavior

Nothing happens

How to reproduce

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

$ npm install

$ npm start

Then in the app open dev tools and paste this in the console:

new Notification("test", { tag: "test" });

Wait for the notification to disappear and paste it again, observe nothingness.
Issue 1:
We have a library of components for angular that we are currently migrating to Angular 2. We have a container that injects content using ng-content. We would like to have a child component that injects the parent if you nest it inside of the parent, like so:

<parent>
<child></child>
</parent>

This works beautifully in angular 2. However, since are in the process of migration, we would like to use the ngUpgrade adapter for this. The dependency injection seems to fail if the parent and child are specified in an angular 1 context. Any insights on this issue? Is this something that is going to be supported in the ngUpgrade adapter?

I have a working plunker that illustrates the problem:

http://plnkr.co/edit/9qb6ZK9SpJyrWoJDEFEj?p=preview

In both cases, the template includes a parent with the child transcluded/projected into it. The child tries to inject the parent and then calls a function on it when you press the button. The ng2 example works, but not the ng1/ngUpgrade one.

Issue 2:
According to the docs, making a directive that listens for events on the host element is like so:

@Directive({
selector: 'input',
hostListeners: {
'change': 'onChange($event)',
'window:resize': 'onResize($event)'
}
})
class InputDirective {
onChange(event:Event) {}
onResize(event:Event) {}
}

This seems like it could be streamlined:

The listeners are registered far away from where the handlers are defined

The registration duplicates a) the method names and b) arguments.

The registration uses strings which makes obfuscation and refactoring more difficult.

You can listen for global events, too (seems odd that the hostListener object lets you do this)

Listening for global events depends on a magic string prefix of "window:" (or "document:" or "body:", implied by the docs)

Here's a possible alternative:

@Directive({
selector: 'input'
})
class InputDirective {
@HostListener('change')
onChange(event: Event) {}

@WindowListener('resize')
onResize(event: Event) {}
}

This doesn't suffer from any of the problems listed above.

You can imagine a similar streamlining for properties. Currently you write:

@Directive({
selector: '[dependency]',
properties: {
'id':'dependency'
}
})
class Dependency {
id:string;
}

But using decorators you could write:

@Directive({
selector: '[dependency]',
})
class Dependency {
@Property('dependency')
id:string;
}

I find it a whole lot easier to understand this, not needing to remember constantly what the left and right hand side of the configuration means. E.g. for { 'id': 'dependency' } I cannot tell easily which one of 'id' or 'dependency' is the JS class property and which is the DOM element property. I constantly get this confused in Angular 1, too, with the scope config. Hopefully we can eliminate this rough edge in Angular 2...
Issue 1:
ISSUE TYPE

Bug Report

COMPONENT NAME

modules/cloud/google/gce.py

ANSIBLE VERSION

ansible 2.0.1.0
config file =
configured module search path = Default w/o overrides

CONFIGURATION

Python 2.7.10 from virtualenv and using apache-libcloud==1.5.0

OS / ENVIRONMENT

OS X 10.10.5

SUMMARY

Attempting to duplicate instance creation from example at http://docs.ansible.com/ansible/guide_gce.html.

STEPS TO REPRODUCE

Please note I am able to interact with google cloud using apache-libcloud with same credentials.

<---hosts file--->

localhost ansible_connection=local

<---playbook.yml--->

---
- name: Create instance(s)
hosts: localhost
connection: local
gather_facts: no

vars:
service_account_email: ...@developer.gserviceaccount.com
credentials_file: /Users...json
project_id: ...238
machine_type: n1-standard-1
image: debian-7

tasks:

- name: Launch instances
gce:
instance_names: dev
machine_type: "{{ machine_type }}"
image: "{{ image }}"
service_account_email: "{{ service_account_email }}"
credentials_file: "{{ credentials_file }}"
project_id: "{{ project_id }}"

Command is: ansible-playbook -i hosts playbook.yml -vvvv

EXPECTED RESULTS

Something indicating success; undocumented!

ACTUAL RESULTS

PLAY [Create instance(s)] ******************************************************

TASK [Launch instances] ********************************************************
task path: /Users/me/ansible/me/guide_gce/as_of_010617.yml:16
ESTABLISH LOCAL CONNECTION FOR USER: me
localhost EXEC /bin/sh -c '( umask 22 && mkdir -p "` echo $HOME/.ansible/tmp/ansible-tmp-1483722674.82-53534914954591 `" && echo "` echo $HOME/.ansible/tmp/ansible-tmp-1483722674.82-53534914954591 `" )'
localhost PUT /var/folders/h1/bg76tk196rz065b81p1d28ch0000gn/T/tmpp7fYZZ TO /Users/me/.ansible/tmp/ansible-tmp-1483722674.82-53534914954591/gce
localhost EXEC /bin/sh -c 'LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8 /usr/bin/python /Users/me/.ansible/tmp/ansible-tmp-1483722674.82-53534914954591/gce; rm -rf "/Users/me/.ansible/tmp/ansible-tmp-1483722674.82-53534914954591/" > /dev/null 2>&1'
fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "invocation": {"module_args": <OMITTED>
"module_name": "gce"}, "msg": "unsupported parameter for module: credentials_file"}

NO MORE HOSTS LEFT *************************************************************
to retry, use: --limit @as_of_010617.retry

PLAY RECAP *********************************************************************
localhost : ok=0 changed=0 unreachable=0 failed=1

Issue 2:
Documentation of the copy module suggests in the example that owner, group, and mode can be specified, even though these options aren't explicitly mentioned.

Looking through the source of library/copy suggests they aren't supported.

I feel they ought to be.
Issue 1:
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

Currently there is no equivalent to history.replaceState in the router API. The only way to redirect seems to be the redirectTo option in RouterConfig.

Expected/desired behavior

I'd like to be able to redirect the user dynamically in my application.

Please tell us about your environment:

Angular version: 2.0.0-rc.3

Browser: [all ]

Language: [all ]

Issue 2:
This issue is related to the new-new router:

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

There is not currently any way to navigate through an application while skipping the browser history.

Expected/desired behavior

In the router-deprecated there was a second parameter on the navigateByUrl method that allowed us to skipLocationChange. It would be nice if the navigate method allowed this too.

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

I have a specific use case where we have a 'loader' component that does a service call and essentially decides where to route you. I would like to be able to navigate to this loader component without including it in the back button history so that the browser doesn't get stuck in an infinite loop of going back to the loader only to get redirected.

Please tell us about your environment:

Angular version: 2.0.0-rc.3

Router version: alpha.7

Browser: [all]

Language: [all]
Issue 1:
I found a bug with the responsive behavior of the nav-justified element, on chrome.

When browser window is scaled down, the menu changes as it should, eventually turning into a vertical menu. but when window is scaled back up, it doesn't go back to the way it should be. When repeated, the problem increases.

check it out on:

http://getbootstrap.com/examples/justified-nav/

Issue 2:
The justified nav example (http://getbootstrap.com/examples/justified-nav) collapses perfectly when the screen is narrowed, but when the screen is expanded it get wonky.

expanded
Issue 1:
Apache Airflow version

2.3.3

What happened

I have multiple dags running regularly. Dags fail randomly for no reason. When I look at the grid view, one task is in skipped state due to dag timeout. But that task did not get executed during the entire period until timeout.

This happens randomly to any dag, to any task, at any time.

What you think should happen instead

No response

How to reproduce

No response

Operating System

Ubuntu 20.04.3 LTS

Versions of Apache Airflow Providers

No response

Deployment

Virtualenv installation

Deployment details

No response

Anything else

No response

Are you willing to submit PR?

Yes I am willing to submit a PR!

Code of Conduct

I agree to follow this project's Code of Conduct

Issue 2:
Apache Airflow version

2.2.2

What happened

We are using celery executor with Redis as broker.

We are using default settings for celery.

We are trying to test below case.

What happens when Redis or Worker Pod goes down?

Observations:

We tried killing Redis Pod when one task was in queued state.

We observed that task which was in queued state stays in queued state even after Redis Pod comes up.

From Airflow UI we tried clearing task and run again. But still it was getting stuck at queued state only.

Task message was received at celery worker . But worker is not starting executing the task.

Let us know if we can try changing any celery or airflow config to avoid this issue.

Also what is best practice to handle such cases.

Please help here to avoid this case. As this is very critical if this happens in production.

What you think should happen instead

Task must not get stuck at queued state and it should start executing.

How to reproduce

While task is in queued state. Kill the Redis pod.

Operating System

k8s

Versions of Apache Airflow Providers

No response

Deployment

Official Helm chart

Deployment details

No response

Anything else

No response

Are you willing to submit PR?

Yes I am willing to submit a PR!

Code of Conduct

I agree to follow this project's Code of Conduct