text:
issue #698 : Remove shared test directory for elastic search tests

This PR addresses GitHub issue: #698 .
Briefly describe the changes proposed in this PR:

Fix the use of shared directories across all elastic search tests
Add a global semaphore to ensure that JUnit never runs multiple tests through at once, given the use of global JVM state by the ElasticSearch libraries
Use try-finally to reliably attempt to clean up resources

Signed-off-by: Peter Ansell p_ansell@yahoo.com

Hold off on merging this, I customised the names for the indexes for each test using UUID's. That fixed the two tests that were breaking. However, it caused 2 others to break on command line, and an additional to start breaking in Eclipse (3 breaking in eclipse). Looking into what the underlying causes are.

It appears to be working for me again now. However, there are lots of exceptions being printed to the console about files not being found:
Running org.eclipse.rdf4j.sail.elasticsearch.ElasticsearchSailTupleFunctionTest
15:59:28.881 [elasticsearch[Arides][listener][T#1]] WARN  [Arides] failed to update master on updated mapping for index [rdf4j-es-testindex-28], indexUUID [8_HyRPJzQEeTAeDYogf-ZA], type [resource] and source [{"resource":{"_all":{"enabled":false},"properties":{"_geopoint_http://www.opengis.net/ont/geosparql#asWKT":{"type":"geo_point"},"context":{"type":"string","index":"not_analyzed"},"http://www.w3.org/2000/01/rdf-schema#label":{"type":"string"},"text":{"type":"string"},"uri":{"type":"string","index":"not_analyzed"},"urn:test.org/onto#number":{"type":"string"}}}}]
org.elasticsearch.transport.TransportException: transport stopped, action: internal:cluster/mapping_updated
	at org.elasticsearch.transport.TransportService$2.run(TransportService.java:178) ~[elasticsearch-1.7.0.jar:na]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_111]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_111]
	at java.lang.Thread.run(Thread.java:745) [na:1.8.0_111]
15:59:28.885 [elasticsearch[Arides][local_transport][T#2]] WARN  [Arides] Transport response handler not found of id [6]
15:59:29.086 [elasticsearch[Tri-Man][generic][T#1]] WARN  [Tri-Man] [rdf4j-es-testindex-26][0] failed to flush shard post recovery
org.elasticsearch.index.engine.FlushFailedEngineException: [rdf4j-es-testindex-26][0] Flush failed
	at org.elasticsearch.index.engine.InternalEngine.flush(InternalEngine.java:680) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.index.engine.InternalEngine.flush(InternalEngine.java:631) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.index.engine.InternalEngine.flush(InternalEngine.java:626) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.index.engine.FlushingRecoveryCounter.endRecovery(FlushingRecoveryCounter.java:50) ~[elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.index.engine.RecoveryCounter.close(RecoveryCounter.java:64) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.common.lease.Releasables.close(Releasables.java:45) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.common.lease.Releasables.close(Releasables.java:60) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.common.lease.Releasables.close(Releasables.java:81) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.common.lease.Releasables.close(Releasables.java:89) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.index.engine.InternalEngine.recover(InternalEngine.java:920) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.index.shard.IndexShard.recover(IndexShard.java:780) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.indices.recovery.RecoverySource.recover(RecoverySource.java:125) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.indices.recovery.RecoverySource.access$200(RecoverySource.java:49) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.indices.recovery.RecoverySource$StartRecoveryTransportRequestHandler.messageReceived(RecoverySource.java:146) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.indices.recovery.RecoverySource$StartRecoveryTransportRequestHandler.messageReceived(RecoverySource.java:132) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.transport.local.LocalTransport$2.doRun(LocalTransport.java:279) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:36) [elasticsearch-1.7.0.jar:na]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_111]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_111]
	at java.lang.Thread.run(Thread.java:745) [na:1.8.0_111]
Caused by: org.elasticsearch.index.translog.TranslogException: [rdf4j-es-testindex-26][0] failed to create new translog file
	at org.elasticsearch.index.translog.fs.FsTranslog.newTransientTranslog(FsTranslog.java:287) ~[elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.index.engine.InternalEngine.flush(InternalEngine.java:667) [elasticsearch-1.7.0.jar:na]
	... 19 common frames omitted
Caused by: java.io.FileNotFoundException: /tmp/junit2619868263578165536/es-ss-test/sail_test/nodes/0/indices/rdf4j-es-testindex-26/0/translog/translog-1482209963941 (No such file or directory)
	at java.io.RandomAccessFile.open0(Native Method) ~[na:1.8.0_111]
	at java.io.RandomAccessFile.open(RandomAccessFile.java:316) ~[na:1.8.0_111]
	at java.io.RandomAccessFile.<init>(RandomAccessFile.java:243) ~[na:1.8.0_111]
	at org.elasticsearch.index.translog.fs.RafReference.<init>(RafReference.java:49) ~[elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.index.translog.fs.FsTranslog.newTransientTranslog(FsTranslog.java:285) ~[elasticsearch-1.7.0.jar:na]
	... 20 common frames omitted
15:59:29.373 [elasticsearch[Northstar][generic][T#2]] WARN  [Northstar] [rdf4j-es-testindex-25][0] failed to flush shard post recovery
org.elasticsearch.index.engine.FlushFailedEngineException: [rdf4j-es-testindex-25][0] Flush failed
	at org.elasticsearch.index.engine.InternalEngine.flush(InternalEngine.java:680) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.index.engine.InternalEngine.flush(InternalEngine.java:631) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.index.engine.InternalEngine.flush(InternalEngine.java:626) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.index.engine.FlushingRecoveryCounter.endRecovery(FlushingRecoveryCounter.java:50) ~[elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.index.engine.RecoveryCounter.close(RecoveryCounter.java:64) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.common.lease.Releasables.close(Releasables.java:45) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.common.lease.Releasables.close(Releasables.java:60) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.common.lease.Releasables.close(Releasables.java:81) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.common.lease.Releasables.close(Releasables.java:89) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.index.engine.InternalEngine.recover(InternalEngine.java:920) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.index.shard.IndexShard.recover(IndexShard.java:780) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.indices.recovery.RecoverySource.recover(RecoverySource.java:125) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.indices.recovery.RecoverySource.access$200(RecoverySource.java:49) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.indices.recovery.RecoverySource$StartRecoveryTransportRequestHandler.messageReceived(RecoverySource.java:146) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.indices.recovery.RecoverySource$StartRecoveryTransportRequestHandler.messageReceived(RecoverySource.java:132) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.transport.local.LocalTransport$2.doRun(LocalTransport.java:279) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:36) [elasticsearch-1.7.0.jar:na]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_111]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_111]
	at java.lang.Thread.run(Thread.java:745) [na:1.8.0_111]
Caused by: org.elasticsearch.index.translog.TranslogException: [rdf4j-es-testindex-25][0] failed to create new translog file
	at org.elasticsearch.index.translog.fs.FsTranslog.newTransientTranslog(FsTranslog.java:287) ~[elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.index.engine.InternalEngine.flush(InternalEngine.java:667) [elasticsearch-1.7.0.jar:na]
	... 19 common frames omitted
Caused by: java.io.FileNotFoundException: /tmp/junit5328382935679970367/es-ss-test/sail_test/nodes/0/indices/rdf4j-es-testindex-25/0/translog/translog-1482209961254 (No such file or directory)
	at java.io.RandomAccessFile.open0(Native Method) ~[na:1.8.0_111]
	at java.io.RandomAccessFile.open(RandomAccessFile.java:316) ~[na:1.8.0_111]
	at java.io.RandomAccessFile.<init>(RandomAccessFile.java:243) ~[na:1.8.0_111]
	at org.elasticsearch.index.translog.fs.RafReference.<init>(RafReference.java:49) ~[elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.index.translog.fs.FsTranslog.newTransientTranslog(FsTranslog.java:285) ~[elasticsearch-1.7.0.jar:na]
	... 20 common frames omitted
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.091 sec - in org.eclipse.rdf4j.sail.elasticsearch.ElasticsearchSailTupleFunctionTest
Running org.eclipse.rdf4j.sail.elasticsearch.ElasticsearchIndexTest
15:59:30.907 [elasticsearch[Starfox][generic][T#3]] WARN  [Starfox] [rdf4j-es-testindex-27][0] failed to flush shard post recovery
org.elasticsearch.index.engine.FlushFailedEngineException: [rdf4j-es-testindex-27][0] Flush failed
	at org.elasticsearch.index.engine.InternalEngine.flush(InternalEngine.java:680) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.index.engine.InternalEngine.flush(InternalEngine.java:631) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.index.engine.InternalEngine.flush(InternalEngine.java:626) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.index.engine.FlushingRecoveryCounter.endRecovery(FlushingRecoveryCounter.java:50) ~[elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.index.engine.RecoveryCounter.close(RecoveryCounter.java:64) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.common.lease.Releasables.close(Releasables.java:45) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.common.lease.Releasables.close(Releasables.java:60) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.common.lease.Releasables.close(Releasables.java:81) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.common.lease.Releasables.close(Releasables.java:89) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.index.engine.InternalEngine.recover(InternalEngine.java:920) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.index.shard.IndexShard.recover(IndexShard.java:780) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.indices.recovery.RecoverySource.recover(RecoverySource.java:125) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.indices.recovery.RecoverySource.access$200(RecoverySource.java:49) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.indices.recovery.RecoverySource$StartRecoveryTransportRequestHandler.messageReceived(RecoverySource.java:146) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.indices.recovery.RecoverySource$StartRecoveryTransportRequestHandler.messageReceived(RecoverySource.java:132) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.transport.local.LocalTransport$2.doRun(LocalTransport.java:279) [elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:36) [elasticsearch-1.7.0.jar:na]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_111]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_111]
	at java.lang.Thread.run(Thread.java:745) [na:1.8.0_111]
Caused by: org.elasticsearch.index.translog.TranslogException: [rdf4j-es-testindex-27][0] failed to create new translog file
	at org.elasticsearch.index.translog.fs.FsTranslog.newTransientTranslog(FsTranslog.java:287) ~[elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.index.engine.InternalEngine.flush(InternalEngine.java:667) [elasticsearch-1.7.0.jar:na]
	... 19 common frames omitted
Caused by: java.io.FileNotFoundException: /tmp/junit297822125442591449/es-ss-test/sail_test/nodes/0/indices/rdf4j-es-testindex-27/0/translog/translog-1482209966550 (No such file or directory)
	at java.io.RandomAccessFile.open0(Native Method) ~[na:1.8.0_111]
	at java.io.RandomAccessFile.open(RandomAccessFile.java:316) ~[na:1.8.0_111]
	at java.io.RandomAccessFile.<init>(RandomAccessFile.java:243) ~[na:1.8.0_111]
	at org.elasticsearch.index.translog.fs.RafReference.<init>(RafReference.java:49) ~[elasticsearch-1.7.0.jar:na]
	at org.elasticsearch.index.translog.fs.FsTranslog.newTransientTranslog(FsTranslog.java:285) ~[elasticsearch-1.7.0.jar:na]
	... 20 common frames omitted
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.521 sec - in org.eclipse.rdf4j.sail.elasticsearch.ElasticsearchIndexTest

There is a single elasticsearch.yml file for the tests that defines a common cluster name for all invocations, but I am not sure how to replace it right now. The common cluster name is the "sail_test" that is showing up in the file errors above.
At minimum, it may be useful to run this pull request code through Hudson to see if it still complains or fails in new interesting ways.

hudson build running: https://hudson.eclipse.org/rdf4j/job/rdf4j-verify-pr/46/

Hudson build succeeds. Do you want to look into this further (or perhaps @pulquero does), or are you happy for this to be merged?

I would still like to know why it started to fail intermittently, and it is throwing some new error messages to the console, but it can be merged now to greenline Hudson builds and further investigation can be done separately.

Noticed one problem, AbstractLuceneSailSpinTest.populate doesnt have a searchIndex.begin()/searchIndex.commit() around the for loop of addStatement. cf ElasticsearchIndexTest.

I don't quite understand why SearchIndex is being populated using a custom API. Could you explain why the RepositoryConnection.add command (which works without begin/commit) isn't populating the search index?

Fixed the issue for me, including the warnings. The SPIN test, unlike the other tests, is hooking directly into SearchIndex without using LuceneSail. This means that both begin/commit need to be manually called on the SearchIndex in populate, and shutdown needs to be called on SearchIndex in tearDown.

The querytuplefunction means I can search in spin but doesn't answer the question of how to get stuff in the index in the first place. Spin has no sort of hook for doing things like that. Also the lucenesail and spinsail don't play nice together.

authors: ansell jeenbroekstra pulquero


text:
Android Text Select bar misplaced

when you select text in Android inputs, the selected text bar pushes the main tabris navbar down.

Thanks for catching this issue. Will be addressed in the next release.

The issue has been solved for the upcoming 1.2 release.

source: gharchive/issue

authors: bFlood mpost

repo: eclipsesource/tabris-js

license_type: permissive

license_source: bigquery


text:
pem file error

Hi I get: The key is not a file or a string PEM format private key
but the pem file have in headers:
-----BEGIN RSA PRIVATE KEY-----
What could be the problem?

How are you writing the path to the file? Or.. are you  passing the file contents? Can you give us a code example please?

That was the problem it was that the path was wrong without "file:/"
it's fixed now.

Nice! Let me close this issue after add some documentation about this missuse, I think is the second time it happened.

license: mit


text:
Long test failure

What happened?
I get a failure when I run long tests, and I noticed that none of the tests affected by the PRs I've submitted run on GitHub.
If that's not done on purpose, it looks like the unit-tests and integration-tests actions do the same thing, perhaps the integration tests could use the -E long flag.
What are the steps to reproduce the bug?
git clone git@github.com:ecmwf/earthkit-data.git
mamba env create -n earthkit-data -f tests/environment-unit-tests.yml
conda activate earthkit-data
pip install -e .
python -m pytest -vv -m 'not notebook and not no_cache_init' --cov=. --cov-report=$(COV_REPORT) -E long

Version
0.4.1.dev27+g7a11635
Platform (OS and architecture)
Darwin MacBook-Pro-3.local 22.6.0 Darwin Kernel Version 22.6.0: Wed Jul  5 22:21:56 PDT 2023; root:xnu-8796.141.3~6/RELEASE_X86_64 x86_64
Relevant log output
FAILED tests/sources/test_cds.py::test_cds_non_observation_csv_file_to_pandas_xarray - Exception: the request you have submitted is not valid. There is no data matching your request. Check that you have specified the correct fields and values..

Accompanying data
No response
Organisation
B-Open / CADS-EQC

This test is now disabled in the develop branch.

hmm, this is because the data provider has broken the dataset on the CDS. I'll change it to a static dataset, i.e. one without automatic upates which could potentially break in the future, and report the dataset issue to Eduardo

Got it, thanks.
I have a related question: How does the cache deal with dynamic datasets?

Got it, thanks. I have a related question: How does the cache deal with dynamic datasets?

Good question, I suspect it doesn't, I'll get back to you on this.
Did cads-toolbox+cachelote have anything in place to handle this? I don't see a way of implementing it without additional knowledge of the source you are accessing. TBH, this is a new (undoubtly long) ticket!

Nothing has been implemented for cads-toolbox, but the cache accepts settings such as tags and expirations that are used to clean/invalidate specific cache entries. It does require knowledge of the source if dynamic datatasets do not have public tags/metadata, but it should allow to deal with those datasets.

authors: EddyCMWF malmans2 sandorkertesz

repo: ecmwf/earthkit-data

license_source: github-api


text:
Pie图的标签能否自定义

问题简述 (One-line summary)
Pie图的标签样式现在不是很好，在页面中不是很好布局，影响美观。
比如我想把所有标签的视觉引导线都朝向左边，或者右边，而不是现在的360度方向，朝向一个方向对页面布局很有好处，且美观。
还有，标签文字和值能不能在视觉线的上下，这样可以节省空间。
如下图
谢谢
版本及环境 (Version & Environment)

ECharts 版本 (ECharts version):3
浏览器类型和版本 (Browser version):
操作系统类型和版本 (OS Version):

重现步骤 (Steps to reproduce)

期望结果 (Expected behaviour)
可能哪里有问题 (What went wrong)
ECharts配置项 (ECharts option)

option = {

}

其他信息 (Other comments)

暂时不行

authors: pissang visgoods

repo: ecomfe/echarts


text:
Graph 图,edgeLabel设置标签formatter失效

One-line summary [问题简述]
在option里面的设置edgeLabel.normal.formatter='{c}'，并不会把link（edge）的value显示出来，只能在json里面设置才可以
Version & Environment [版本及环境]

ECharts version [ECharts 版本]: 3.3.2
Browser version [浏览器类型和版本]: chrome52
OS Version [操作系统类型和版本]: Windows 10

Expected behaviour [期望结果]
edgeLabel.normal.formatter 的设置会对边的文字显示有效果
ECharts option [ECharts配置项]

option = {

    "legend": {
        "data": [
            "a"
        ]
    },
    "series": [
        {
            "type": "graph",
            "layout": "force",
            "animation": false,
            "draggable": true,
            "data": [
                {
                    "category": 0,
                    "name": "aa1",
                    "value": 1,
                    "id": 0
                },
                {
                    "category": 0,
                    "name": "aa2",
                    "value": 1,
                    "id": 1
                },
                {
                    "category": 0,
                    "name": "aa3",
                    "value": 1,
                    "id": 2
                }
            ],
            "categories": [
                {
                    "base": "aaa",
                    "name": "a",
                    "keyword": {}
                }
            ],
            "symbolSize": 30,
            "edgeSymbol": [
                "none",
                "arrow"
            ],
            "edgeSymbolSize": 20,
            "force": {
                "edgeLength": 100,
                "repulsion": 2000,
                "gravity": 0.2
            },
            "edgeLabel": {
                "normal": {
                    "show": true,
                    "textStyle": {
                        "fontSize": 20
                    },
                    "formatter": "{c}"
                }
            },
            "label": {
                "normal": {
                    "show": true,
                    "position": "right",
                    "textStyle": {
                        "fontSize": 18
                    },
                    "formatter": "{b}"
                }
            },
            "edges": [
                {
                    "source": 0,
                    "target": 1,
                    "value": "skaf",
                    "label": {
                        "normal": {
                            "formatter": "{c}",
                            "show": true
                        }
                    }
                },
                {
                    "source": 2,
                    "target": 1,
                    "value": "asfas"
                }
            ]
        }
    ]
}

Other comments [其他信息]

新版本修复这个问题

authors: JunLuo pissang


text:
WIP Renames X and pmf

See #1156 and #1051
To be merged after #1156

[ ] Tests for new functionality/models or Tests to reproduce the bug-fix in code.
[ ] Updated documentation of features that add new functionality.
[ ] Update CHANGELOG.md with major/minor changes.

Given the complexity of the other PR, it might be better to make this change before the xarray work.
I.e., we should settle on interface design choices for the (discrete) distributions, and then later worry about how to implement them.

source: gharchive/pull-request

repo: econ-ark/HARK


text:
Angular Django Tutorial

How about adding Angular Django tutorial? I can help you in that.

Hey @milapbhojak -
The new coder tutorials are just Python-based (my language of choice). A Django tutorial would definitely fit, but I'm unsure of the Angular part.  Partly because I'm not a JS dev, and partly because it's outside the scope of the site.
If you'd like to write up a complete Angular + Django tutorial, please feel free!  I'll create a separate portion of the site that points to equally awesome tutorials.

authors: econchick milapbhojak

repo: econchick/new-coder

license: Zlib


text:
Is this broken?

When I run it it does claim to have saved a csv file, but the csv-file is empty. Trying -corpus=eng_2019 also throws an error. Can somebody check whether this works for them? Thanks.

The code from pull request 18 works

The code from pull request 18 works

I am facing the exact same issue, the code runs but the resulting csvs are always empty even for the basic commands from the Github Publication. The code from pull request 18 yields errors for me. Could you please provide a solution?

I modified the script as the pull request 18 did. But it still doesn't work. It says "An error occured". I don't know whether the API went wrong.

authors: Nikolanoske ennoheese sdspieg yeshengjun333

repo: econpy/google-ngrams


text:
Event callbacks not firing when app is killed: Sending onExit with no listeners registered.

Awesome library, but trying to get it work when app is killed.
It actually starts app on boundary change, but I have Sending onExit with no listeners registered.
Is it supposed to work when app is killed? I'm using ios.

Hey @ValentinBlokhin, what version of the lib are you using?

Hey @eddieowens , I've been using 1.1.0 version.

@ValentinBlokhin Can you post the relevant code block?

Is there something special I need to do to get it to work when the app is killed? I can't find any documentation about it

I am having similar issues when killed. Could it be that the event listeners is bound in such a way that when the app is waked up on geofencing-events that registration of listeners is simply not run (or run after the event is emitted). I have little experience around what code actually gets called when wake up happens in a react-native context. Does anyone know or have a good resource around the topic?

Same here. Everything works perfect on Android and iOS, but when the app os Killed on iOS, if some transition is detected, when i open the app it show's this warning:

My code looks exactly like the repository example.
import {NativeEventEmitter, NativeModules, AppRegistry} from 'react-native';

const {RNBoundary} = NativeModules;

const TAG = "RNBoundary";

const boundaryEventEmitter = new NativeEventEmitter(RNBoundary);

const Events = {
  EXIT: "onExit",
  ENTER: "onEnter",
};

export { Events }

const HeadlessBoundaryEventTask = async ({event, ids}) => {
  console.log(event, ids);
  boundaryEventEmitter.emit(event, ids)
};

AppRegistry.registerHeadlessTask('OnBoundaryEvent', () => HeadlessBoundaryEventTask);

export default {
  add: boundary => {
    if (!boundary || (boundary.constructor !== Array && typeof boundary !== 'object')) {
      throw TAG + ': a boundary must be an array or non-null object';
    }
    return new Promise((resolve, reject) => {
      if (typeof boundary === 'object' && !boundary.id) {
        reject(TAG + ': an id is required')
      }

      RNBoundary.add(boundary)
        .then(id => resolve(id))
        .catch(e => reject(e))
    })
  },

  on: (event, callback) => {
    if (typeof callback !== 'function') {
      throw TAG + ': callback function must be provided';
    }
    if (!Object.values(Events).find(e => e === event)) {
      throw TAG + ': invalid event';
    }

    return boundaryEventEmitter.addListener(event, callback);
  },

  off: (event) => {
    if (!Object.values(Events).find(e => e === event)) {
      throw TAG + ': invalid event';
    }

    return boundaryEventEmitter.removeAllListeners(event);
  },

  removeAll: () => {
    return RNBoundary.removeAll();
  },

  remove: id => {
    if (!id || (id.constructor !== Array && typeof id !== 'string')) {
      throw TAG + ': id must be a string';
    }

    return RNBoundary.remove(id);
  }
}

For iOS, According to this, I believe we need allowsBackgroundLocationUpdates to be set to true: https://developer.apple.com/documentation/corelocation/handling_location_updates_in_the_background?language=objc

authors: ValentinBlokhin chrisspankroy eddieowens gusilveiramp mikaelengstrom paulrostorp

repo: eddieowens/react-native-boundary


text:
Swagger有误

在go version go1.12.9 windows/amd64、swag version v1.6.3的环境下使用swag init会报错：ParseComment error in file routers\api\v1\article.go :can not find schema type: "v1.json"，查询了相关的文章后应该将// @Success 200  {string} json "{"code":200,"data":{},"msg":"ok"}"修改为// @Success 200  {string} string "{"code":200,"data":{},"msg":"ok"}"

是这样的。遇到了同样的问题

The same error occur to me.

url := ginSwagger.URL("http://localhost:8090/swagger/doc.json") // The url pointing to API definition
r.GET("/swagger/*any", ginSwagger.WrapHandler(swaggerFiles.Handler, url))
这么使用 就可以

@zyeking @lpzhi @lyr1994  都是 swag v1.6.3 版本吗？

version: swag version v1.6.3.
err:

ParseComment error in file routers\api\v1\article.go :can not find schema type: "v1.json"

@easonlin404 What component version might be causing this?

@zyeking @lpzhi @lyr1994 都是 swag v1.6.3 版本吗？

是的

@zyeking 你这个问题之前已经修复了，目前 go-gin-example 并不存在相关的代码，若还是存在，请附上相应链接，感谢。

2020/06/24 17:39:18 ParseComment error in file routers/api/v1/tag.go :can not find schema type: "v1.json"
按照文档写仍然存在这个问题

请问一下这个报错是是你们意思呢？

repo: eddycjy/go-gin-example

license: MIT


text:
Close button doesn't close dialog on mobile devices

When the modal is open and i tap the close button.
Expected: The dialog closes
Actual: Dialog remains open, close button has focus styling

Edit:
Recreated in:

Chrome 58 on android 7, One+ 3T
Firefox 52 on android, One+ 3T
Chrome 55 on android, Samsung Galaxy S7 edge
Safari 10.3 on ios, iPhone 6+

Hello.
I cannot reproduce this problem. Could you please show me the code you are using?

It's very likely related to something I did locally. I'll create a stand alone example when I'm back at work. I already threw everything I knew at it, so I'm down to guessing and just trying to remove stuff. I couldn't get any event listener on click, touchstart or touchend to work on any device, bt it worked find on mobile emulators. When I figure it out I'll report back, or report back with an example that shows the problem. Hopefully this can result in a note in the docs about what not to do

Alright, let me know when you have something to show me. :)

Ok, this was definitely my own fault. Nothing to do with the library.
I was absolutely positioning the modal, the overlay, the content. But I was both using z-indexes to get the overlay and content above a sticky header, and also adding transforms for animations, which creates new stacking contexts.
Long story short, adding a z-index higher than the content and overlay made the button clickable.
Now, why on earth this is not happening on a desktop in mobile mode or a desktop mobile emulator I have no clue. Similarly, why I can see the close button, click it and see it get focus, when it's apparently behind something else is also beyond me.
Anyway, be careful with your z-indexes!

Alright. :)

authors: HugoGiraudel Munter


text:
Feature request: Detect Leaky Vessels runtime vulnerability (CVE-2024-21626)

Should be able to detect based on runc version
runc versions 1.1.11 and below, as used by containerization technologies such as Docker engine and Kubernetes, are vulnerable to an arbitrary file write vulnerability. Due to a file descriptor leak it is possible to mount the host file system with the permissions of runc (typically root). Successfully tested on Ubuntu 22.04 with runc 1.1.7-0ubuntu1~22.04.1 using Docker build.

Unfortunately, we can't find reliable evidence in a container environment with runc 1.1.11, because of the nature of the vulnerability.  In essence, it uses WORKDIR to glitch the view of the filesystem so that the new container namespace's filesystem never gets fully entered.  We can't see any side effect of WORKDIR by the time the tool runs.

authors: jedsalazar kaniini

repo: edera-dev/am-i-isolated


text:
Readme edgarpruebas

Hola @edgarbenz , aqui te paso una sugerencia para mejorar el contenido del README de tu repositorio del curso de Git

Muchas gracias por tus cambios , los he aceptado , saludos @edgarbenz

authors: edgarbenz edgarpruebas

repo: edgarbenz/youtube-git


text:
Fix the inconsistent use of the DROP keyword in DDL

Currently, we use DROP in DDL somewhat inconsistently and confusingly to:

Revert to the default or inherited value  (DROP default).
In specific cases, like DROP REQUIRED, to set the field to a falsy value.
To actually delete a schema object, such as DROP PROPERTY.

To fix this we:

Introduce the RESET <field> syntax instead of DROP <field> to revert
the field to the default or inherited value.

Replace uses like DROP REQURIED with appropriate SET syntax using a
complement, specifically:

DROP ABSTRACT replaced with SET CONCRETE
DROP FINAL replaced with SET NONFINAL
DROP DELEGATED replaced with SET NONDELEGATED
DROP OWNED replaced with SET INHERITED

The remaining use of DROP denoting an object deletion is thus consistent
and unambiguous.
Fixes: #2031

DROP ABSTRACT replaced with SET CONCRETE
DROP FINAL replaced with SET NONFINAL
DROP DELEGATED replaced with SET NONDELEGATED
DROP OWNED replaced with SET INHERITED

Maybe instead of CONCRETE / NONFINAL / NONDELEGATED we use NOT ABSTRACT, NOT FINAL, and NOT DELEGATED?
I know it's less "english-like", but it's also fewer unreserved keywords and things to remember.

Maybe instead of CONCRETE / NONFINAL / NONDELEGATED we use NOT ABSTRACT, NOT FINAL, and NOT DELEGATED?

Yeah, that works too.

The trio of SET REQUIRED, SET OPTIONAL and RESET REQUIREDseems odd. Why RESET REQUIRED as opposed to RESET OPTIONAL? It seems that this kind of situation should be more like SET REQUIRED := True, SET REQUIRED := False and RESET REQUIRED. I think that this would be ultimately less confusing and easier to understand and remember.
DDL is a low level language, but it's still something a regular user might need to look at when inspecting proposed migration steps for SDL migrations. So seeing SET OPTIONAL vs RESET REQUIRED may be more confusing than SET REQUIRED := False vs. RESET REQUIRED.

The trio of SET REQUIRED, SET OPTIONAL and RESET REQUIREDseems odd. Why RESET REQUIRED as opposed to RESET OPTIONAL

There's no reason not to offer RESET OPTIONAL too.

It seems that this kind of situation should be more like SET REQUIRED := True

Which makes ALTER inconsistent with CREATE, where qualifiers are specified as keywords as opposed to SET <field> := <value>.
Fundamentally, qualifiers are essentially a bitmask.  SET <bit> and RESET <bit> make sense.  Yes, some of the bits are complementary to each other and "reset" the other bit, and I don't see a problem with this.

There's no reason not to offer RESET OPTIONAL too.

Well, ease of reading would be a good reason. Also parsing and then code-genning user DLL. Are we actually going to keep 2 separate AST nodes for RESET REQUIRED and RESET OPTIONAL? This is even more confusing... remember that this is already a bit of obscure DDL and what we're doing is creating a distinction without a difference which will make end-users wonder whether there's some subtle effect of RESET REQUIRED that's different from RESET OPTIONAL.
This just seems like an invitation to write less consistent DDL for no actual benefit, but also making it slightly harder to read/skim.
Regarding consistency, I think comparing SET REQUIRED/OPTIONAL and RESET REQUIRED should really be compared to whatever the equivalent of those 3 is going to be for default as you mentioned on the call. These 2 have the benefit of being in the same category that needs those 3 options: set value, set explicit "nothing", set to inherited. On the other hand the data type is different and default normally appears with a :=, so re-using it in the SET/RESET scenario is not so great. My point is that if syntactic consistency is what we're after we should make sure that the syntax rules work well enough for both required and default as good representatives of the kinds of fields that we need to tinker with.

Are we actually going to keep 2 separate AST nodes for RESET REQUIRED and RESET OPTIONAL?

No.  In fact, the production is RESET <ident>, and there's only one AST node for everything.

but also making it slightly harder to read/skim.

Hm.  So you think the inconsistency between CREATE REQUIRED LINK and ALTER LINK SET OPTIONALITY := false doesn't make it harder to read DDL?

Are we actually going to keep 2 separate AST nodes for RESET REQUIRED and RESET OPTIONAL?

No. In fact, the production is RESET <ident>, and there's only one AST node for everything.

Perhaps I worded it wrong, but what I mean is whether we would generate different ASTs (with different values) for these two: RESET REQUIRED and RESET OPTIONAL.
If yes, then this seems like begging for more compiler hacks (or duplication) that still needs to treat them exactly identically.
If no, then user says: RESET OPTIONAL you potentially echo RESET REQUIRED in your migration commands and this is ever so slightly confusing. Not much, but this is not user brainpower well-spent.

but also making it slightly harder to read/skim.

Hm. So you think the inconsistency between CREATE REQUIRED LINK and ALTER LINK SET OPTIONALITY := false doesn't make it harder to read DDL?

Not quite. Since REQUIRED is the non-default keyword I would go with:
CREATE REQUIRED LINK and ALTER LINK SET REQUIRED := true. I do understand that it also means that I'm OK with this: CREATE OPTIONAL LINK and ALTER LINK SET REQUIRED := false
But I do think this is less confusing than having:
CREATE TYPE Foo {CREATE REQUIRED PROPERTY bar -> str};
CREATE TYPE Bar {CREATE OPTIONAL PROPERTY baz -> str};
...
ALTER TYPE Foo {ALTER PROPERTY bar {RESET REQUIRED}};
ALTER TYPE Bar {ALTER PROPERTY baz {RESET OPTIONAL}};

...and weirder still, someone could also write
ALTER TYPE Foo {ALTER PROPERTY bar {RESET OPTIONAL}};
ALTER TYPE Bar {ALTER PROPERTY baz {RESET REQUIRED}};

And it would have the same effect but be a bit confusing when reading. Did the person forget? Did they mean a different type? Is this outdated?
I'm basically putting myself in the shoes of a user who doesn't do DDL very often, so they might view DDL commands once in a while, perhaps to track some other issue. It seems that making it possible to write RESET REQUIRED/OPTIONAL both ways will just make the task of looking though the DDL a bit harder.

How would you go about cardinality in your approach?  SET MULTI := false?

How would you go about cardinality in your approach? SET MULTI := false?

Either that or even using the enum we have. So either SET MULTI := false or SET CARDINALITY := <schema::Cardinality>'One'. I realize that we drifted to where we are now in part while trying to get away from the bulky cardinality cast expression, so I'm not a big fan of the cast.

I've updated the PR to use the NOT <FOO> keywords and done a few more cleanups and generalizations.

authors: 1st1 elprans vpetrovykh

repo: edgedb/edgedb


text:
Add testing for security service of edgeX.

Signed-off-by: Tingyu Zeng tingyu.zeng@rsa.com

@tingyuz why is this PR closed?

@tingyuz why is this PR closed?

I pushed master to my feature branch by accident so Git closed the PR automatically as they are exactly same. Please use PR #160 instead.

repo: edgexfoundry/blackbox-testing


text:
Update restGetAddressableByAddress to use operator

Fix #1473
Update the restGetAddressableByAddress function to leverage the new
operator pattern which will allow for easier testing.
Add tests to cover the new operator.
Signed-off-by: Anthony M. Bonafide AnthonyMBonafide@gmail.com

Codecov Report

Merging #1477 into master will increase coverage by 0.05%.
The diff coverage is 75%.

@@            Coverage Diff             @@
##           master    #1477      +/-   ##
==========================================
+ Coverage   17.96%   18.01%   +0.05%
==========================================
  Files          81       82       +1
  Lines        8774     8781       +7
==========================================
+ Hits         1576     1582       +6
- Misses       7047     7048       +1
  Partials      151      151

Impacted Files
Coverage Δ

internal/core/metadata/rest_addressable.go
0% <0%> (ø)
:arrow_up:

...nternal/core/metadata/operators/addressable/get.go
100% <100%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 19d0599...34cb94b. Read the comment docs.

After taking a second look, I had my interface names mixed up and had to do a little bit of renaming.

authors: AnthonyMBonafide codecov-io

repo: edgexfoundry/edgex-go


text:
feat(notifications): Add secret creation API

Close: #3333
PR Checklist
Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/master/.github/Contributing.md.
What is the current behavior?

Issue Number: #3333
What is the new behavior?
Add secret creation API for storing EdgeX service exclusive secret to the Secret Store.
Does this PR introduce a breaking change?

[ ] Yes
[x] No

New Imports

[ ] Yes
[x] No

Specific Instructions
Are there any specific instructions or things that should be known prior to reviewing?
Other information

Codecov Report

Merging #3510 (7646f62) into master (8e84e87) will increase coverage by 0.03%.
The diff coverage is 78.57%.

@@            Coverage Diff             @@
##           master    #3510      +/-   ##
==========================================
+ Coverage   40.41%   40.44%   +0.03%
==========================================
  Files         204      206       +2
  Lines       16790    16846      +56
==========================================
+ Hits         6786     6814      +28
- Misses       9527     9552      +25
- Partials      477      480       +3

Impacted Files
Coverage Δ

internal/pkg/v2/controller/http/secret.go
78.57% <78.57%> (ø)

internal/pkg/v2/controller/http/common.go
40.47% <0.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8e84e87...7646f62. Read the comment docs.


text:
🛑 Xcodehoster server 4 is down

In 179b253, Xcodehoster server 4 (https://serverjogja.securityhub.id/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Xcodehoster server 4 is back up in 77a2702 after 10 minutes.

repo: edoaurahman/check-web-uptime


text:
0.4版本有发布时间预期吗

0.4版本计划接入Rest Api数据源，请问下大概有时间预估何时可以发布吗？

同问  0.4版本发布时间

开发中，预计6月底吧

authors: fmx0717 scottsut xingguangsixian


text:
fix(Widget): remove 600 data limit

#1715

#1964


text:
Support for custom Icons

See #2.

Also, if possible, please rebase your fork to get rid of the merge conflict.

Thanks for documentation! You still haven't rebased on top of changes from edward-shen/master, so there are still merge conflicts.
Do the following:
git remote add upstream git@github.com:edward-shen/MMM-page-indicator.git
git fetch upstream
git rebase upstream/master

I think we might be better off nuking this PR and adding my changes to a fresh branch

I'm inclined to agree.
If I were you, I'd make another branch that's equal to upstream/master, and then cherry pick your commits from your master onto the branch. Then make a PR to merge that branch with upstream/master.
I'll leave this PR open until you request another PR.

Try now, if not I'll nuke this and start again.

You need to make a new branch and request a PR on that branch--this PR is based on your master branch, and will attempt to pull in 14 commits.

Closing due to age.

authors: edward-shen stephenjgray

repo: edward-shen/MMM-page-indicator


text:
The page to make a Survey does not appear, being the frame to make reload in the release 2.13.2

Hello,
I'm running a release version, which corresponds to 2.13.2, with the version of xcode 9.2.
During the execution of the project, this problem occurs to me, which consists of a certain user clicking on a course, and trying to respond to a certain survey, and when I try to enter the same the page is done reload, and does not advance to the survey
The following image shows the problem, previous.
Can someone help me solve this problem?

Thank you

Hello @saeedbashir ,
Sorry for the inconvenience, but I'm not really able to solve this problem, in this release and the one I'm using.
However I've been testing on other releases and it's the same.
Could you give me a possible solution to this problem?
Thank you

@latinosamuel Could you please share your sandbox details and test user credentials so that I can see exactly what is breaking.

Hello @saeedbashir ,
I do not know if this is what you want. The following image demonstrates the Output of the Application.
And what does the image demonstrate? Or when it refers to "sandbox details", it refers to the data in the default_config folder of the config.yaml file.

@latinosamuel I need default_config data.

Hello @saeedbashir ,
API_HOST_URL: 'https://apdcdigitalacademy.bridgelk.com'
ENVIRONMENT_DISPLAY_NAME: 'APDCDigitalAcademy'
FEEDBACK_EMAIL_ADDRESS: 'servicedesk@bridgelk.com'
OAUTH_CLIENT_ID: '3b7ac86e311e5f64bf4e'

Could you please credentials of a test user as well?

Hello @saeedbashir ,
Email: sdfl-1@sapo.pt
pass: latino

@latinosamuel It seems your server is not properly configured for oauth2. Your server is not allowed to create a session for the mobile web. This URL is being used for creating a session.

Hello @saeedbashir ,
Could you give me a possible solution to this problem?

@latinosamuel I don't know much about server but maybe this wiki document will help you out.

Ok

@latinosamuel Can I close this issue?

authors: latinosamuel saeedbashir

repo: edx/edx-app-ios


text:
Please create for swift 3.0

This code will get deprecated in the next version of  Xcode.
We need to start building on Swift 3.0 NOW.

@edx  Just create a Swift 3.0 port for the same... we will start contributing. we can have it working in 1 week time.

Hey @lovebug1988. We have this at our roadmap but currently busy with some high priority tasks. It would be great if you can open an OSPR. If you need any assistance, we are here to help you.

Thanks for the response... I don't have much knowledge(Don't even know what is OSPR)... If you can provide me a starting point (Non compiling code would also be fine to start with.) That would be great.

Sorry I was't clear. OSPR means "Open Source Pull Request". I was saying if you want to contribute for porting of current edX code to swift 3.0, you have to create a new branch from master and then need to make all necessary changes. After porting your branch to swift 3.0, you can create a pull request.

NVM, I tried a lot... there is so much to learn from this code... You/Your devs are superb...  What a code quality/complexity. Oh WOW!! It is not easy to understand the code. Today a 3 year exp iOS dev is feeling like going back to primary school of coding. Please close issue. Will better wait till it rolls out.


text:
Course ware content scrolling improvements

Description
LEARNER-5801
I'm not sure this PR will fix the crash or not because the crash is not reproducible, but it will fix an issue that blocked user to interact with course content.
Notes
How to test this PR

@saeedbashir please take a look into failed test cases.

@saeedbashir please take a look into failed test cases.

@salman2013 It was a travis glitch and tests were passed on restart.

@saeedbashir you tag the wrong ticket with this PR. The correct ticket is https://openedx.atlassian.net/browse/LEARNER-6400

@salman2013 I worked on this story under LEARNER-5801 thats why I added this story into the description. Somehow both stories linked with earch other and LEARNER-6400 seems the root cause of LEARNER-5801 but I'm not sure about this because both of stories are not reporducible.


text:
Move more global state to local state

This shouldn't affect the logic of login, just where the state variables
live.

@jotiram @abhra-clarice This continues my improvements to remove unnecessary global state.
cc @rohan-dhamal-clarice @nasthagiri

Looks good!

Landed in master.

authors: aleffert rohan-dhamal-clarice


text:
Use LoggedIn User Details for New Response/Comment

Description
MA-2762

@salman2013 Ready for review.


text:
Python module

Add test script and plugins

Merge by cherry-pick

authors: EyelynSu eeliu

repo: eeliu/pinpoint-c-agent


text:
rprompt do not appear

I'm submitting a ...

[ ] bug report
[ ] feature request
[x] support request

Do you want to request a feature or report a bug?
bug

What is the current behavior?
right prompt is never show on a specific machine

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
Use my dotfiles https://gitlab.com/gnumoksha/dotfiles

What is the expected behavior?
alien-minimal show a right prompt

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

Please tell us about your environment:

Plugin Manager: [antigen | zplug | oh-my-zsh | ... ] none
ZSH Version: zsh 5.7.1 (x86_64-debian-linux-gnu)

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, etc)

Could you please share your .zshrc file?

if you are not using any plugin manager. you can follow below steps:
cd ~
git clone https://github.com/eendroroy/alien-minimal.git
cd alien-minimal
git submodule update --init --recursive

Then set source ~/alien-minimal/alien-minimal.zsh in the ~/.zshrc file.

if you are not using any plugin manager. you can follow below steps:
cd ~
git clone https://github.com/eendroroy/alien-minimal.git
cd alien-minimal
git submodule update --init --recursive

Then set source ~/alien-minimal/alien-minimal.zsh in the ~/.zshrc file.

Did you try it?

if you are not using any plugin manager. you can follow below steps:
cd ~
git clone https://github.com/eendroroy/alien-minimal.git
cd alien-minimal
git submodule update --init --recursive

Then set source ~/alien-minimal/alien-minimal.zsh in the ~/.zshrc file.

Did you try it? @gnumoksha

Yes, and it didn't work. I've used a minimal .zshrc containing only source ~/alien-minimal/alien-minimal.zsh and the rprompt is still empty. Also, all my environment vars are printed on each prompt rendered.
My .zshrc is located here https://gitlab.com/gnumoksha/dotfiles/tree/master/cli/home/config/zsh but alien-minimal does work on one machine with this exact configuration. The problem is with another machine only. How can I debug?

Which commit are you on?
Could you please try deleting the folder and cloning againg?

Steps
$ git clone https://github.com/eendroroy/alien-minimal.git /tmp/alien-minimal
$ cd /tmp/alien-minimal
$ git log -1
commit fcaf3c67025b5c4e0992a8311d4534a443906b70 (HEAD -> master, tag: 1.4.4, origin/master, origin/HEAD)
Author: indrajit <eendroroy@gmail.com>
Date:   2019-09-03 21:20:39 +0600

    update readme
$ git submodule update --init --recursive
$ echo 'source /tmp/alien-minimal/alien-minimal.zsh' > ~/.zshrc

Results
After close the shell, opening a new one and cd /tmp/alien-minimal:

left prompt is [S] alien-minimal
right prompt is empty
every new prompt shows all my environment variables (like in https://github.com/eendroroy/alien-minimal/issues/24)

rprompt also does not appear to me when I am using the current master branch

What Os you are using?

$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 10 (buster)
Release:        10
Codename:       buster
$ uname -a
Linux bombadil 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5 (2019-06-19) x86_64 GNU/Linux
$ zsh --version
zsh 5.7.1 (x86_64-debian-linux-gnu)

I have made some changes. Please checkout to latest master. Let me know if it resolves the issue.

head is now 5f60f560d0ce7bcfc7b471e705163f4e4b53038b and environment variables are no longer show. rprompt is still empty.

I have updated to master and everything is working great for me.
`No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.3 LTS
Release:	18.04
Codename:	bionic
Linux radix-gs1 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
zsh 5.4.2 (x86_64-ubuntu-linux-gnu)`

$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 10 (buster)
Release:        10
Codename:       buster
$ uname -a
Linux bombadil 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5 (2019-06-19) x86_64 GNU/Linux
$ zsh --version
zsh 5.7.1 (x86_64-debian-linux-gnu)

I have tried in a vagrant box. Seems to be working fine.

With below .zshrc
if [ -d ~/.zplug ]; then
  source ~/.zplug/init.zsh

  zplug "eendroroy/alien-minimal"

  # Install plugins if there are plugins that have not been installed
  if ! zplug check --verbose; then
    zplug install
  fi
  zplug load
fi

@eendroroy I've two machines: home and work. At home, alien-minimal works fine, but at work, it does not show rprompt. I know I've some problem but I can't figure out how to debug it.

https://github.com/eendroroy/alien-minimal/blob/25fa6df7049a03a5b2d633e9495f36b5251b0b47/alien-minimal.zsh#L51
change the above line to:
am_r_prompt_render "${PWD}" "${__AM_ENVS}" "${AM_VERSIONS_PROMPT}"

then you can use echo in any of the files to check if any command is throwing any error.

Using echo am_r_prompt_render "${PWD}" "${__AM_ENVS}" "${AM_VERSIONS_PROMPT}" results in the following:

Any ideas?

Try using the below:
echo $(am_r_prompt_render "${PWD}" "${__AM_ENVS}" "${AM_VERSIONS_PROMPT}")

echo \"$(am_r_prompt_render "${PWD}" "${__AM_ENVS}" "${AM_VERSIONS_PROMPT}")\"

prints " " on non-git directories and " %F{248}:%f%B%F{78}master%f%b %F{244}[4W]%f %F{248}66fc7eb%f %F{208}%f %F{208}%f " otherwise

RPROMPT value generation seems perfect. Probably the problem is printing it (or reseting zle)

Ok. Thank you.

authors: eendroroy gnumoksha sibblegp

repo: eendroroy/alien-minimal


text:
liquid-if can't add a row to a table

I am trying to toggle a hidden table row using liquid-if. However the toggled row becomes a div on top of the
 element.
I created a jsbin : http://emberjs.jsbin.com/daxav/2/edit
<button {{action 'toggleHiddenRow'}}>Click Me</button>

      Animated Table

      Visible Row

    {{#liquid-if isRowActive}}

          Hidded Row

    {{/liquid-if}}

App = Ember.Application.create();

App.ApplicationController = Ember.Controller.extend({
  isRowActive: false,
  toggleHiddenRow: function(){
    this.set('isRowActive', !this.get('isRowActive'));
  }
});

LiquidFire.map(function(){
  this.transition(
    this.toModel(true),
    this.use('crossFade', {duration: 1000}),
    this.reverse('fade', {duration: 500})
  );

});

Any work on supporting tagName? Would really love to see this work with tables.

:+1: Bumping up against this too.

authors: fsoumare jreading sprockow


text:
🛑 Nodo Monte Castro is down

In 50c3216, Nodo Monte Castro (https://nodomontecastro.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nodo Monte Castro is back up in 3a475ef after 19 minutes.

repo: efecear/upptime


text:
🛑 Almacén BioPandora is down

In b6177b5, Almacén BioPandora (https://www.biopandora.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Almacén BioPandora is back up in c99d5cc.


text:
🛑 La Semilla Que Crece is down

In 4fc6d70, La Semilla Que Crece (https://www.lasemillaquecrece.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: La Semilla Que Crece is back up in b468e8d.


text:
Create Repository: There is no longer a "native browser" menu item

There is no longer a "native browser" menu when right-clicking on a in Artifactory. Describe how to get the URL from the artifact and simply open it in a browser of your choise (chrome, curl...)
https://github.com/praqma-training/artifactory-katas/tree/master/create_repository#look-at-them-through-the-native-browser

There is now again the native browser menu with the latest JFrog Cloud artifactory ( I suppose 7.something ) as well as 6.23.7.
Getting the URL is added to gradle_intro where the url is picked from the repository, see PR #83

authors: michaelin mtavi

repo: eficode-academy/artifactory-katas


text:
Create sample data for database

Create scripts to insert sample data to database

@minhtridn2001
Complete!!!

repo: efode-intership/VTS


text:
🛑 CDN-Mikrotik-2 is down

In 0883e49, CDN-Mikrotik-2 (http://118.179.50.70) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CDN-Mikrotik-2 is back up in 7018c53 after 23 minutes.


text:
🛑 CDN-Mikrotik-2 is down

In 2ac4a5a, CDN-Mikrotik-2 (http://118.179.50.70) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CDN-Mikrotik-2 is back up in 24b97b9 after 38 minutes.


text:
[Service] Add a slower/waiter http plugin to slow down the http requests according to Google rate limits

It would be nice to be able to slow down http requests sent automatically according to Google rate limits. This would allow to:

Request Google services as much faster as we can.
Don't rely on sleep or usleep in users code or even internally in the tests suite which actually degrade performance as they are not optimized in most cases...
Reduce the number of OVER_QUERY_LIMIT responses.

Since Google species that even when following there rate limit rules, it is possible to get an OVER_QUERY_LIMIT, it would also be nice to introduce a Google Error plugin which would convert such response (and other errored reponses) to exception which then can be retried by the buit-in Httplug retry plugin.

Closing as it is not the way I will go for this feature.

repo: egeloen/ivory-google-map


text:
Improve scanning speed

Scanning GCP resources takes a lot of time. Scanning would be faster if performed in multiple threads.
Have to keep in mind note on google api library

This has been implemented in #13 and in #14
Scanning of each resource for each project allows to use multiple threads which increases overall speed.

repo: egnyte/cloudimized


text:
Protected Branches: Cannot create a new rule for non-existing branches

using the below in common_settings.branches and seeing as below
P.S: Branches with name release/* or release-* does NOT exists in the testproject
config.yaml has the below
common_settings:
  branches:
    "release/*":
      protected: true
      developers_can_push: false
      developers_can_merge: false
    "release-*":
      protected: true
      developers_can_push: false
      developers_can_merge: false

Error:
gitlabform.gitlab.core.UnexpectedResponseException: Request url='https://gitlab.com/api/v4/projects/testGroup%2FtestSubGroup%2Ftestproject/repository/branches/release-%2A/protect', method=PUT, data='{'id': 'testGroup/testSubGroup/testproject', 'branch': 'release-*', 'developers_can_push': False, 'developers_can_merge': False}' failed - expected code(s) [200, 201], got code 400 & body: 'b'{"message":"The branch refname is invalid"}''

Hi @yashwanth-l !
I think that the problem is that you are mixing usage of the old and the new API for branches protection. If you are passing patterns instead of plain branch names then please use the new syntax, as shown below this line:

Sorry for closing, misclick! 😅 Please feel free to reopen if you still have issues!

@gdubicki can you share an example for the same?

authors: gdubicki yashwanth-l

repo: egnyte/gitlabform


text:
tx power calibration implementation suggested as on ijv firmware

please take into account an implementation of tx power calibrations read from eeprom like in the original or ijv firmware. each band has sepatared tx calibration kept in the eeprom. for instance tx level can be different between uhf and vhf bands . The issue can be easily investigated when ijv firmware is used, Low, med, high levels are changed and eeprom is dumped. Of course calibration cannot be edited on original fw, ijv allows it.

use chirp to change calibration values

you do not understood. Every L M H setting has own value in the eeprom. You can set eg. 0,5W for Low power on 2m band. You have to try ivj. Chirp has nothing common with this issue

You don't understand, use calibration section in the chirp

Sadly I see here same regres like with 1of11

What regres? Did check out the chirp driver or not? I guess not.

Battery calibration is a different thing, it is one option and not gezilion different options like in the sql, or txp. Battery is easy. For TXP you need power meter and you need to know what youre doing, if someone whants to mess with that you have that option. I'm not adding that to the menu

authors: egzumer pawol


text:
switch to libtpu-nightly

Draft, wip

Getting this error when trying libtpu-nightly:
I1009 10:05:43.587473 8309755712 docker.py:89] #24 9.814 INFO: pip is looking at multiple versions of axlearn[core,tpu] to
 determine which version is compatible with other requirements. This could take a while.
I1009 10:05:43.789101 8309755712 docker.py:89] #24 9.841 ERROR: Ignored the following yanked versions: 0.0.1
I1009 10:05:43.789452 8309755712 docker.py:89] #24 9.841 ERROR: Ignored the following versions that require a different py
thon version: 0.23.0 Requires-Python >=3.6, <3.10; 1.6.2 Requires-Python >=3.7,<3.10; 1.6.3 Requires-Python >=3.7,<3.10; 1
.7.0 Requires-Python >=3.7,<3.10; 1.7.1 Requires-Python >=3.7,<3.10

repo: ehorning/axlearn


text:
Update the game over message

testUpdate the game over message so people know how to play again!

done


text:
Filter by max file size and with-height of image

Additionally to minimum file size and with-height filter sometimes needed also filter by max file size and with-height. Can you add it too, if this is not so hard?

Instead of large images, you need smaller ones?

I need middle - not small, not large :)
вт, 21 мая 2019 г., 8:35 eight notifications@github.com:

Instead of large images, you need smaller ones?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/eight04/image-picka/issues/196?email_source=notifications&email_token=AACSGFQGB6E46RMKJKGOXO3PWOC2BA5CNFSM4HOHMER2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV2ZTFY#issuecomment-494246295,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACSGFVBQGEMQFYWFN7FD7DPWOC2BANCNFSM4HOHMERQ
.


text:
editor创建plane预制体报错

复现步骤：
1.运行editor
2.点击Create->Geometry->plane
报错log:
[2024-05-15 14:00:37.85][ERROR]( ant.window|window ) `read `/pkg/ant.resources.binary/meshes/base/plane.glb/meshes/Plane_P1.meshbin` failed.
stack traceback:
        ( service:6 )
        D:/cpp20/ant/pkg/ant.io/main.lua:7: in upvalue 'readall'
        D:/cpp20/ant/pkg/ant.io/main.lua:12: in field 'readall'
        D:/cpp20/ant/pkg/ant.serialize/main.lua:29: in field 'load'
        D:/cpp20/ant/pkg/ant.asset/ext_meshbin.lua:123: in field 'loader'
        D:/cpp20/ant/pkg/ant.asset/main.lua:25: in field 'resource'
        D:/cpp20/ant/pkg/ant.render/render_system/render_system.lua:160: in local 'f'
        D:/cpp20/ant/pkg/ant.world/main.lua:475: in field '_pipeline_entity_init'
        D:/cpp20/ant/pkg/ant.world/main.lua:60: in method '_flush_entity_queue'
        D:/cpp20/ant/pkg/ant.world/entity_system.lua:63: in local 'func'
        D:/cpp20/ant/pkg/ant.world/main.lua:378: in upvalue 'update_func'
        D:/cpp20/ant/pkg/ant.world/main.lua:403: in field '_pipeline_update'
        D:/cpp20/ant/pkg/ant.world/main.lua:587: in method 'pipeline_update'
        D:/cpp20/ant/pkg/ant.window/service/window.lua:76: in upvalue '

原因：\pkg\ant.resources.binary\meshes\base\Plane.glb 文件名应改成小写。

cc @aimoonchen

@liuping1997 更新最新的引擎和子模块就好了

不报错了。
但整个项目搜索下相关引用，在tools\editor\pkg\tools.editor\resource\plane.prefab 第7、8行还有没改全的。
material: /pkg/ant.resources.binary/meshes/base/Plane.glb/materials/Material.001.material
mesh: /pkg/ant.resources.binary/meshes/base/Plane.glb/meshes/Plane_P1.meshbin

在更新一下引擎和子模块，应该好了

authors: aimoonchen cloudwu liuping1997

repo: ejoy/ant


text:
Fixes #366 - Allows options to be passed to mergeStreams

Fixes #366
mergeStreams now works with options passed in, which allows objectMode to be set to true, allowing an interesting use case where a SitemapStream uses an existing source file stream and another stream that allows more items to be added without having to hydrate and maintain the entire map in memory

@ekalinin - Are you available to review?  Thanks!


text:
SIGSEGV error

Getting a SIGSEGV error when aws-nuke is printing resource IDs before nuke confirmation in version 3.2.0. See stacktrace:

Well that's not what you want to see. Let me take a look.

@Petersoj I see the problem. I'll get patch up here shortly.

@Petersoj what OS are you on? I'll cut you a build for testing.

@ekristen I'm using Docker on macOS ARM.

I was able to duplicate. Just working on getting the fix in fully now.

:tada: This issue has been resolved in version 3.2.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

Time between release cut and builds can be about 5-10 minutes, give it a few and it'll show up with all the artifacts and docker images.

Excellent! The patch release works great. Thank you!

authors: Petersoj ekristen

repo: ekristen/aws-nuke


text:
fix(cognito-userpool): include user attribute update settings

Resolves #477

:tada: This PR is included in version 3.38.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


text:
Logo

Create a nice app logo

Closed via #88

repo: ekumenlabs/tangobot


text:
Add licence file header to all files

/*
 * Copyright (C) 2017 Open Source Robotics Foundation
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *     http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 *
 */

Closed in #199

repo: ekumenlabs/terminus


text:
Entities default naming pattern and issues with Device renaming

Currently, the default pattern for entity names  is prefixed by $brand $appliance -
It prevents HA from automatically shortening names on Device View. Making their names unreadable

If the beginning of entity name equals Device name, the prefix is stripped out.
Now question: what part of the system is responsible for renaming entities while renaming the device? I though that by renaming the device to match entity prefixes, I will clean up the Device page. Unfortunatelly it ended up with even bigger mess:

During renaming of the device from Susicka to Bosch Susicka, HA informed me, that no (out of 49 or so) entities will be renamed
Something opposite happened
All (most) entities have been renamed
a). Some some remained untouched (seems a few unavailable ones)
After some few forth-back attempts of device renaming I ended up with more prefixes of those entities: Bosch Bosch Susicka, Bosch Susicka, Bosch Susicka Bosch

Just wonder if should I raise an issue to HA Core, or if the renaming is done by the component, with the issue in applying the predefined pattern.

I see. It is a quite long time I have renamed it, but I think I have reinstalled the integration.

Thank you.
Good to know that it's enough to wait.
I have an impression that Reload didn't make the job (to any of the entities).

Neither reloading nor restart helped.
I had to remove the integrated devices/entities (see screenshot) and re-add it afterwards

The problem with such approach is, that a user has no option to select the entity naming pattern before adding entities. And tbh at that step the new user has no idea about how device and entity names and their relationship.
BTW I found that user may want to change device name - the integration doesn't provide such option during adding the device. It uses name provided by API.
Fortunatelly (for me), after adding devices (thus their entities too) I changed the pattern, and it did work this time, renaming already existing entities. So I'm happy right now I achieved cleaner view.
Now I'm really confused, why changing had effect on entity names this time, just after adding them, while it wasn't working before. (btw hyphen in name pattern prevents HA from automatic prefix removal)
And let me ask again for device renaming process. If a user uses a device rename option, is it HA core code which renames entities, or it's integration code? Why changing a device name results in renaming entities leading to the mess described in the OP?  I just wanted to change device name to match prefix of already existing entity names.
The message which pops up, that no entity will be renamed is even more confusing.
with regards

As I mentioned, once you rename entities using the HA UI it takes over the names and they will be managed by HA, which will most likely create the kind of mess you experienced. Changing the name template through the integration's "configure" UI will take effect without requiring removing and re-adding the integration.

I didn't rename any entity using HA GUI. I tried to change either the device name, or the template.
It gave messy results.
I don't know if the integration or HA is responsible for what happened. Maybe using non-ascii characters in the appliance name was causing the problem?
On top of that I suppose that the initial template should not contain a hyphen character, which might prevent the HA from shortening prefixes.
Since I managed to resolve that by removing and re-adding the appliance and renaming with use ascii-only names it works to me as expected.

How did you change the device name if not through the GUI?
Non-ascii is not a problem, everything is Unicode anyway.
Bottom line is that this feature exists for a very long time and I didn't get reports about problems with it, unless the names were changed manually in the GUI, in which case HA will override the name offered by the integration.
Since it's working for you and as you suggested I'll close the issue now and reopen if I get additional complaints about it.

authors: ekutner michalk-k z-vrba

repo: ekutner/home-connect-hass


text:
Reduce Particle Use in Spells

Since Mojang is apparently satisfied with the incredible drop in particle performance in 1.13, we will need to reduce our use of particles. Shame.
Mob < Serious lag
Smite
Wither on max lvl when it shoots 3 skulls < Serious lag
Arrow rain < Significant lag
Blast
Kill < Significant lag
Harden
Wave
Sandblast
Earthquake
Meteor shower
Railgun
Tornado
Singularity < Serious lag
Nuke
Dragon ball < Significant lag

@GottaSlay I will have all of these reduced in the next dev build, except for Dragon Ball. The odd/interesting thing about that one is I'm not using any custom effects. What appears on the ground there are the vanilla effects for the dragon's fireball, the same as you'd get fighting the dragon in the end. So I'm not sure what to do about that one.

Well that's great news regardless!
On Tue, 24 Sep 2019 at 19:31, Nathan Wolf notifications@github.com wrote:

@GottaSlay https://github.com/GottaSlay I will have all of these
reduced in the next dev build, except for Dragon Ball. The odd/interesting
thing about that one is I'm not using any custom effects. What appears on
the ground there are the vanilla effects for the dragon's fireball, the
same as you'd get fighting the dragon in the end. So I'm not sure what to
do about that one.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/elBukkit/MagicPlugin/issues/582?email_source=notifications&email_token=AKMF5VKB7QKUZNJK3AE3JT3QLI6EHA5CNFSM4IZV3XUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7O7FDY#issuecomment-534639247,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKMF5VM4RTRBM4F4GDIVAC3QLI6EHANCNFSM4IZV3XUA
.

Released in 7.7.5

authors: GottaSlay NathanWolf

repo: elBukkit/MagicPlugin


text:
scheduled ProjenUpgrade failed

Hi @eladb
Looks like the scheduled ProjenUpgrade will need to update the yarn.lock but --frozen-lockfile was passed.
https://github.com/pahud/cdk-spot-one/runs/987656093?check_suite_focus=true
Any comments on this ?

It doesn't seem like this is a result of the update but rather a result of the repo bootstrapping.
Try to run projen locally and commit the updated lockfile and let me know if this persists.

authors: eladb pahud

repo: eladb/projen


text:
Type issue for Button

Documentation states that color is optional for Button but type file defines it to be mandatory.
See
color: '#22BC66', // Optional action button color
And type definition
interface Button {         color: string;         text: string;         link: string; }

Hi @bussedesigngb,
Thanks so much for reporting this issue.
This has now been resolved in https://github.com/eladnava/mailgen/commit/65e098812761b79fef6c7511056f8857c5261b64 and published to npm in version 2.0.24.

authors: bussedesigngb eladnava

repo: eladnava/mailgen


text:
Inconsistent Dashboard/Manage section

Does it make sense to eliminate the Manage grouping in the profile menu?
The inconsistencies:

If you click Manage, you will be sent to Dashboard.
MyPage is not part of Manage

Record Video links to an external site

Maybe group it like that instead:

Or with Record video in a separate section:

Instead of:

Thanks for digging this up. Cf. https://github.com/elan-ev/tobira/pull/896 to see where this might lead.
Seriously though:

"MyPage is not part of Manage" You mean because it's not under /~manage like "My videos" and "Upload video"?
I agree "Manage" in the profile menu doesn't bring you to a space where there's more than what you had in the original profile menu (My page, My videos, Upload video, Record video).
I also agree the second option you present might correctly disply that My page and Record videos are different to the other two.

repo: elan-ev/tobira


text:
docs: copy paste docs

Summary
This PR adds ecs-logging-ruby docs. Shared content is included from the ecs-logging repo.
To test this PR, you'll need an up-to-date copy of both elastic/docs and elastic/ecs-logging. Then run the following command, where $GIT_HOME is the path to your local repos:
$GIT_HOME/docs/build_docs --doc $GIT_HOME/ecs-logging-ruby/docs/index.asciidoc --resource=$GIT_HOME/ecs-logging/docs/ --chunk 1 --open

Follow-ups

[ ] Open PR in elastic/docs to add to the build
[ ] Open infra ticket to add the docs check to this repo
[ ] Add webhook for docs check
[ ] Remove content from readme and link to docs

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Build Cause: Pull request #7 opened

Start Time: 2020-12-14T22:41:23.320+0000

Duration: 14 min 15 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
224

Skipped
0

Total
224

No prob! Opened https://github.com/elastic/ecs-logging-ruby/issues/8 to track the follow-ups.

repo: elastic/ecs-logging-ruby


text:
allow per-doc metadata to be specified at runtime

Libraries with API-driven support (like Spark) could support passing the metadata as a pair beside the document. This facilitates computational environments where things like id or the timestamp are created on the fly and are not part of the doc itself.

Related to #255

@costin Will this include the _version metadata as well?

Fixed in master. Closing the issue.

@costin I don't know if you saw my comment from above but I was wondering how to fetch the metadata while reading documents?

@mgreene For questions, please use the forum. The issue is about writing (not reading) documents (see the reference commits).
Thanks,

authors: costin mgreene

repo: elastic/elasticsearch-hadoop


text:
Sort failing due to serialization error

When I apply a sort, the response is throwing an error when trying to convert the hits back to concrete types.
After looking into the code, it appears that the _score is null when a sort is applied.  However, it fails to convert and throws an error.  If I set TrackScores to true, it works correctly (_score comes back as 0 in this case).  This happens on line 125 in https://github.com/elastic/elasticsearch-net/blob/master/src/Nest/CommonAbstractions/SerializationBehavior/StatefulDeserialization/ConcreteTypeConverter.cs
Here is the exception:
Microsoft.CSharp.RuntimeBinder.RuntimeBinderException was unhandled by user code
HResult=-2146233088
Message=Cannot implicitly convert type 'Newtonsoft.Json.Linq.JValue' to 'double'. An explicit conversion exists (are you missing a cast?)
Source=Anonymously Hosted DynamicMethods Assembly
StackTrace:
at CallSite.Target(Closure , CallSite , Object )
at Nest.ConcreteTypeConverter.GetConcreteTypeUsingSelector[T](JsonSerializer serializer, ConcreteTypeConverter1 realConcreteConverter, JObject jObject) in c:\code\elasticsearch-net\src\Nest\CommonAbstractions\SerializationBehavior\StatefulDeserialization\ConcreteTypeConverter.cs:line 125        at Nest.ConcreteTypeConverter.GetUsingConcreteTypeConverter[T](JsonReader reader, JsonSerializer serializer, ConcreteTypeConverter1 realConcreteConverter) in c:\code\elasticsearch-net\src\Nest\CommonAbstractions\SerializationBehavior\StatefulDeserialization\ConcreteTypeConverter.cs:line 83
at Nest.ConcreteTypeConverter`1.ReadJson(JsonReader reader, Type objectType, Object existingValue, JsonSerializer serializer) in c:\code\elasticsearch-net\src\Nest\CommonAbstractions\SerializationBehavior\StatefulDeserialization\ConcreteTypeConverter.cs:line 62
at Nest.DefaultHitJsonConverter.ReadJson(JsonReader reader, Type objectType, Object existingValue, JsonSerializer serializer) in c:\code\elasticsearch-net\src\Nest\CommonAbstractions\SerializationBehavior\StatefulDeserialization\ConcreteTypeConverter.cs:line 24
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.DeserializeConvertable(JsonConverter converter, JsonReader reader, Type objectType, Object existingValue)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateList(IList list, JsonReader reader, JsonArrayContract contract, JsonProperty containerProperty, String id)
InnerException:

@curtismbeard What version of NEST are you using, 2.x?

This should reproduce the error I think.
`
public interface IThing
{
    int Int { get; set; }
    string String { get; set; }
}

class ThingA : IThing
{
    public int Int { get; set; }
    public string String { get; set; }
    public string A { get; set; }
}

class ThingB : IThing
{
    public int Int { get; set; }
    public string String { get; set; }
    public string B { get; set; }
}
class ThingC : IThing
{
    public int Int { get; set; }
    public string String { get; set; }
    public string C { get; set; }
}

class Program
{
    static void Main(string[] args)
    {
       var client = new ElasticClient(settings);

        if (!client.IndexExists(new IndexExistsRequest("multitype")).Exists)
        {
            client.CreateIndex("multitype");
            var response = client.Map<ThingA>(m => m.Index("multitype").AutoMap());
            if (!response.IsValid)
            {
                throw new Exception(response.DebugInformation);
            }
            response = client.Map<ThingB>(m => m.Index("multitype").AutoMap());
            if (!response.IsValid)
            {
                throw new Exception(response.DebugInformation);
            }
            response = client.Map<ThingC>(m => m.Index("multitype").AutoMap());
            if (!response.IsValid)
            {
                throw new Exception(response.DebugInformation);
            }
        }

        client.Index(new ThingA {A = "Somthing for A", Int = 1, String = "thinga"});
        client.Index(new ThingA {A = "Somthing for A", Int = 2, String = "thinga"});
        client.Index(new ThingB {B = "Somthing for B", Int = 3, String = "thingb"});

        var searchResponse = client.Search<IThing>(
            s =>
                s.Index<ThingA>()//search correct index
                    .Type("thinga,thingb,thingc")
                    .ConcreteTypeSelector((v, y) =>
                    {
                        switch (y.Type)
                        {
                            case "thinga":
                                return typeof (ThingA);
                            case "thingb":
                                return typeof (ThingB);
                            case "thingc":
                                return typeof (ThingC);
                            default:
                                throw new Exception(y.Type);
                        }
                    })
                    .Query(x => x.Term(trm => trm.String, "thingb"))
                    .Sort(srt => srt.Ascending(fld => fld.Int))
                    .Skip(0)
                    .Take(10));}}`

I will work on a simple example that reproduces the issue.  I am using 2.0.2.

I ran into this issue last night. This is definitely an issue with sorting results that need to serialize to different POC types. When you remove the sorting it returns results without an error. There is a ticket from yesterday that has a good example to reproduce the issue. I hope this is helpful, please let me know if there is anything I can do to help further troubleshoot.
https://github.com/elastic/elasticsearch-net/issues/1929

Thank you all for reporting this.  It'll be fixed in the next release.

authors: RTroywest curtismbeard gmarz russcam tbrooks007

repo: elastic/elasticsearch-net


text:
Added overload to DismaxQueryDescriptor's Queries method to take QueryContainer[]

This allows it to act like other descriptors that get formatted into an array, such as Bool Query's Should, if you've already composed your QueryContainers elsewhere.

LGTM.  Thanks @xueye !

authors: gmarz xueye


text:
How can I use proxy to connect to elasticsearch ?

I am trying to connect elasticsearch cluster when I am behind a corporate proxy maybe something like
from elasticsearch import Elasticsearch, RequestsHttpConnection

class MyConnection(RequestsHttpConnection):
    def __init__(self, *args, **kwargs):
        proxies = kwargs.pop("proxies", {})
        super(MyConnection, self).__init__(*args, **kwargs)
        self.session.proxies = proxies

es = Elasticsearch(
    ["https://url_to_elasticsearch"],
    connection_class=MyConnection,
    proxies=proxies,
    use_ssl=True,
    http_auth=("username", "password"),
)

@RatanShreshtha thanks for the issue.
Unfortuantly using urllib3 we don't support proxies yet, so as a work around you can use the requests library, similar to what you're suggesting.
for more reference please see:

https://github.com/elastic/elasticsearch-py/issues/860
https://github.com/elastic/elasticsearch-py/issues/357
https://github.com/elastic/elasticsearch-py/issues/275#issuecomment-143682556

I am not sure how can I use the above code snippet for elasticsearch-py-async as here the aiohttp lib is used.

Since we won't be adding new features to this library I'll be closing this. See https://github.com/elastic/elasticsearch-py-async/issues/81 for more information. You can use a transparent HTTP proxy (as opposed to forwarding/tunnel) which should work fine with any client.

AsyncElasticsearch cannot recognize http_proxy
Windows 10
ES 7.10

authors: RatanShreshtha fxdgear qbit-git sethmlarson

repo: elastic/elasticsearch-py-async


text:
Make security.get_privileges 'name' parameter accept list of names

Hah, @delvedor beat me to this one, my local branch was out of date. Closing as not necessary!

repo: elastic/elasticsearch-specification


text:
include filesystem type?

It would be great if the output could include the type of filesystem (e.g. ext2, nfs, whatever).
A long-term solution is to add this information (comes from java7 FileStore api) to ES stats, but as a start, maybe we could include the output from df -k + mount or similar?

If there are command line utils that show this it's not a huge deal to add.

authors: nemonster rmuir


text:
Add filesystem type support on Windows

Not entirely sure if go generate is supposed to generate that many changes. I ran it on the beats Windows 2019 Vagrant VM.
Adds some of the functionality necessary for https://github.com/elastic/beats/issues/22501 -- as an example, returns ntfs as SysTypeName on the Vagrant box.

ping @elastic/integrations-services @elastic/security-external-integrations

anyone against cutting a release so we can update beats?

SGTM. It looks like there were two other changes that will get released. Any issue with those being released @fearful-symmetry?
And can you please change the PR/issue references to be actual links in the changelog when you release it.

Yah, that should be fine. I'd like to get a new release of this cut.

authors: andresrc andrewkroh andrewstucki fearful-symmetry

repo: elastic/gosigar


text:
fix: security.yaml is 404

fix: security.yaml is 404

[ ] Chart version not bumped (the versions are all bumped and released at the same time)
[ ] README.md updated with any new values or changes
[ ] Updated template tests in ${CHART}/tests/*.py
[ ] Updated integration tests in ${CHART}/examples/*/test/goss.yaml

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

cla/check

authors: daniel-hutao elasticmachine jmlrt

repo: elastic/helm-charts


text:
Version lock in metadata.json prevents from upgrading ceritsc-yum module

Module version: latest 0.13.2
Puppet version: 3.8.7
OS and version: CentOS 7.2 (1511)

Bug description
Version lock in metadata.json prevents from upgrading ceritsc-yum module
{"name":"ceritsc/yum","version_requirement":">= 0.9.6 < 1.0.0"},
proposed change
 {"name":"ceritsc/yum","version_requirement":">= 0.9.6"},

Based upon what I found in their github repo and the puppet forge, there is no 1.x release - am I mistaken/is there a release somewhere you can point me to? Reason being that we'd need to test the module against that version to ensure there's no breakage, but I can't find that version anywhere.

Hi,
ceritsc-yum was replaced by puppet-yum (which is not suitable yet), but in my case ceritsc is forked and maitained internally by me. Adding new features causes to increment version (leaving old name intact), which conflicts with elasticsearch module.
I would like to propose to remove < 1.0.0 version from requirements.

Guys, it's not a revolutionary change - simple unlock 'below'. I don't want to do this manually on every server I have, but since yum class is forked and available in version higher than 1.0.0, it would be nice to have status green.

Thanks!

authors: marcinbojko tylerjl

repo: elastic/puppet-elasticsearch


text:
Update Debian based install for 2.0.0 apt module

include_src was removed and now defaults to false
key_server renamed to server as a parameter of key
key now requires the parameter id is using a hash

you have to adapt the spec tests, too.

Hi,
I'm not planning to only support the 2.0 apt module since older PE versions are possibly pinned down to older apt module versions.
I'll be pinning the module to use apt < 2.0

K. I'll just use my fork. Thanks for the reply!

authors: bsparrow435 electrical igalic

repo: elastic/puppet-logstash


text:
[WIP] Refactor of rake tasks

Working in progress for refactoring of the devutils publish and vendor rake tasks.

this has been done differently, closing..

repo: elasticsearch/logstash-devutils


text:
Upgrade kube-prometheus-stack chart to v66.1.1

[!warning]
This is a public repository, ensure not to disclose:

[x] personal data beyond what is necessary for interacting with this pull request, nor
[x] business confidential information, such as customer names.

What kind of PR is this?
Required: Mark one of the following that is applicable:

[ ] kind/feature
[x] kind/improvement
[ ] kind/deprecation
[ ] kind/documentation
[ ] kind/clean-up
[ ] kind/bug
[ ] kind/other

Optional: Mark one or more of the following that are applicable:

[!important]
Breaking changes should be marked kind/admin-change or kind/dev-change depending on type
Critical security fixes should be marked with kind/security

[ ] kind/admin-change
[ ] kind/dev-change
[ ] kind/security
[ ] kind/adr

What does this PR do / why do we need this PR?

Noticed that the kube-prometheus-stack was falling behind a bit, this PR upgrades the Helm chart to v66.1.1.
This fixes some ARP metrics and a log issue caused by this in the node-exporter (this is mentioned in the linked issue).
Alertmanager in the Mangement cluster is not upgraded, instead the image version is fixed to previous v0.26.0 due to v0.27.0 deprecating the v1 API endpoint, which is still used by Thanos. Once we upgrade Thanos to v0.35 or higher, the v2 endpoint will be default (see related upstream issue).

Fixes #2166

Information to reviewers

Since this PR changes a lot of files, I recommend simply testing out the migration script in a dev environment, i.e. deploy previous version of kube-prometheus-stack and then run:
CK8S_CLUSTER=both ./migration/v0.43/apply/11-kube-prometheus-stack.sh execute

Run tests and check that metrics looks fine.
Checklist

[x] Proper commit message prefix on all commits

Change checks:

[ ] The change is transparent
[ ] The change is disruptive
[ ] The change requires no migration steps
[x] The change requires migration steps
[x] The change upgrades CRDs
[ ] The change updates the config and the schema

Documentation checks:

[ ] The public documentation required no updates
[ ] The public documentation required an update - [link to change](set-me)

Metrics checks:

[x] The metrics are still exposed and present in Grafana after the change
[ ] The metrics names didn't change (Grafana dashboards and Prometheus alerts are not affected)
[ ] The metrics names did change (Grafana dashboards and Prometheus alerts were fixed)

Logs checks:

[x] The logs do not show any errors after the change

Pod Security Policy checks:

[ ] Any changed pod is covered by Pod Security Admission
[ ] Any changed pod is covered by Gatekeeper Pod Security Policies
[x] The change does not cause any pods to be blocked by Pod Security Admission or Policies

Network Policy checks:

[ ] Any changed pod is covered by Network Policies
[x] The change does not cause any dropped packets in the NetworkPolicy Dashboard

Audit checks:

[x] The change does not cause any unnecessary Kubernetes audit events
[ ] The change requires changes to Kubernetes audit policy

Falco checks:

[x] The change does not cause any alerts to be generated by Falco

Bug checks:

[ ] The bug fix is covered by regression tests

I tried out this in a dev cluster. Grafana and metrics etc looks good, but (as expected?) Thanos has trouble.
Should this wait for a Thanos update?

Hmm maybe, I will test and check it again, I know I had issues with the newer alertmanager version and Thanos, but that should have been fixed by keeping the alertmanager version we used previously... Are you getting any particular alerts for Thanos?

Are you getting any particular alerts for Thanos?

Many of the Thanos pods were crashlooping. I'll have to take another look, could be a misconfiguration of my cluster.

Many of the Thanos pods were crashlooping. I'll have to take another look, could be a misconfiguration of my cluster.

Hmm when I tried upgrading to the new version I did not have any issues with Thanos.
I will try do a clean install from this version as well and test later.

Just tried a clean install and thanos seems to be running fine, did you manage to investigate why they were crashing for you @Zash ?

I will close this PR in favor of https://github.com/elastisys/compliantkubernetes-apps/pull/2381 to upgrade Prometheus to v3.

authors: Zash anders-elastisys

repo: elastisys/compliantkubernetes-apps


text:
Add kubecolor support to ck8s ops

What this PR does / why we need it:
Adds support for kubecolor in the ops script
Which issue this PR fixes (use the format fixes #<issue number>(, fixes #<issue_number>, ...) to automatically close the issue when PR gets merged): fixes #
Public facing documentation PR (if applicable)

Special notes for reviewer:
Add a screenshot or an example to illustrate the proposed solution:
Checklist:

[ ] Added relevant notes to WIP-CHANGELOG.md
[x] Proper commit message prefix on all commits
[ ] Updated the public facing documentation
Is this changeset backwards compatible for existing clusters? Applying:

[x] is completely transparent, will not impact the workload in any way.
[ ] requires running a migration script.
[ ] will create noticeable cluster degradation.
E.g. logs or metrics are not being collected or Kubernetes API server
will not be responding while upgrading.
[ ] requires draining and/or replacing nodes.
[ ] will change any APIs.
E.g. removes or changes any CK8S config options or Kubernetes APIs.
[ ] will break the cluster.
I.e. full cluster migration is required.

Chart checklist (pick exactly one):

[x] I upgraded no Chart.
[ ] I upgraded a Chart and determined that no migration steps are needed.
[ ] I upgraded a Chart and added migration steps.

Pipeline config (if applicable)
If you change some config options (e.g. add/rename variable or change the default value) you may need to update the config used by the pipeline in pipeline/config.

Broken PR


text:
searched list populates on profile page, css changes, handlebars styl…

…ing, attempted fix on displaying the user name but not functioning

This all looks great. The problem with the name showing up looks like it has to do with the handlebars variable in profile.handlebars. I think the “.name” needs to be removed from where it is in the pic I’m attaching.

repo: elcaine/FindIt


text:
Support tables without PKs and changing PKs on a row.

Current protocol assumes an unchanging identity by associating a key with each change. Since we're intent on keeping the key, we must split up an UPDATE change that affects a PK (entire row in case of PK-less tables, since entire row is the key at that point) into a DELETE + INSERT pair representing the update each with an individual key. The pair must be still tied in some way by additional metadata for a client to be able to reconstruct the update if it wants to

Closed by https://github.com/electric-sql/electric-next/pull/182 https://github.com/electric-sql/electric-next/issues/181

authors: balegas icehaunter

repo: electric-sql/electric


text:
MidiHandler buffers MIDI messages from UART

I was playing with the Midi example and hit a frustrating bug. After connecting a MIDI controller over UART (the MIDI jack on the POD), the messages were not available from the MidiHandler immediately but needed to get "pushed", i.e. a NoteOn was only getting processed after its NoteOff was sent by the controller.
I think that the delay is caused by the size of DMA buffer set at https://github.com/electro-smith/libDaisy/blob/72827e1b9f3f75031f5320ec5c8ee8a78ba95c78/src/hid_midi.cpp#L34 The only callback that hid_midi.cpp sets is triggered when the transfer is complete, and the regular MIDI messages have 2 and 3 bytes only. I think that this means a single message sits in the buffer until full 6 bytes are received.
Adjusting the DMA buffer size from 6 to 1 solves my problem and the MIDI messages are now available to my program immediately. I suspect that it's introducing a risk of losing incoming data and the correct approach would be to rely on the HAL_UART_RxHalfCpltCallback callback while setting the data transfer to 2 or 3 bytes but I'm not knowledgeable enough.

Good catch, you're absolutely correct. The UART buffer should be at most 3, here. But keeping 2-byte messages in mind, it should probably just be one. I'm sure there's a way to deal with this a bit more efficiently. I can get this fixed here this week.

authors: stephenhensley trisiak

repo: electro-smith/libDaisy


text:
Error when running project after installing opencv4nodejs

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

Please describe your issue:
When adding opencv4nodejs to my fresh forge installation (webpack template), I am getting following error on start:
✔ Checking your system
✔ Locating Application
✔ Preparing native dependencies: 1 / 1
✔ Compiling Main Process Code
✔ Launch Dev Servers
✔ Compiling Preload Scripts
✔ Launching Application

An unhandled rejection has occurred inside Forge:
TypeError: Cannot set property 'native_modules/opencv/build/lib/libopencv_plot.3.4.dylib' of undefined
    at Promise.all.files.map (/Users/steph/Documents/workspace/electron-opencv-test/node_modules/@marshallofsound/webpack-asset-relocator-loader/dist/index.js:14689:98)

Electron Forge was terminated. Location:
{}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! electron-opencv-test@1.0.0 start: `electron-forge start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the electron-opencv-test@1.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

What command line arguments are you passing?
npm start
What does your config.forge data in package.json look like?
"config": {
    "forge": {
      "packagerConfig": {},
      "makers": [
        {
          "name": "@electron-forge/maker-squirrel",
          "config": {
            "name": "electron_opencv_test"
          }
        },
        {
          "name": "@electron-forge/maker-zip",
          "platforms": [
            "darwin"
          ]
        },
        {
          "name": "@electron-forge/maker-deb",
          "config": {}
        },
        {
          "name": "@electron-forge/maker-rpm",
          "config": {}
        }
      ],
      "plugins": [
        [
          "@electron-forge/plugin-webpack",
          {
            "mainConfig": "./webpack.main.config.js",
            "renderer": {
              "config": "./webpack.renderer.config.js",
              "entryPoints": [
                {
                  "html": "./src/index.html",
                  "js": "./src/renderer.js",
                  "name": "main_window"
                }
              ]
            }
          }
        ]
      ]
    }
  },

Here is the repo:
https://github.com/stoefln/electron-opencv-test

We took a look at the code in opencv4nodejs and it seems that there's some weird code in there trying to detect Electron + Webpack:
https://github.com/justadudewhohacks/opencv4nodejs/blob/5d02be9b541c29b7e78061e8e5d82772f2f422cf/lib/opencv4nodejs.js#L4-L11
If that special case gets removed, it'll probably "just work".
Closing since it's very unlikely to be specifically an Electron Forge bug.

@malept I have created a small sample app showing the problem.
https://github.com/gallagherrchris/opencv4nodejs-electron-test
I added in some code to force the logic you highlighted above (should return true and force the first code path).  I am still having the issue with the module not being found and it hasn't "just work"™

authors: gallagherrchris malept stoefln

repo: electron-userland/electron-forge


text:
Include link to new Electron Discord in our Contributing docs

As an open source community, we want folks contributing to Electron to have access to help when they need it. To help them find those resources, we want to include a link to our new Electron Community Discord in our Contributing docs: https://github.com/electron/electron/blob/master/CONTRIBUTING.md
Acceptance Criteria:

Includes link to Discord: https://discord.gg/H6uTh7m
Briefly describes why a user may want to go to Electron's Discord
Spelling/grammar looks good 👍

The CONTRIBUTING.md link provided points to the CONTRIBUTING.md of electron repo and not electronjs.org repo. Where should it be added, exactly?

Please check and merge PR #4593

authors: MalwarePerseus VerteDinde the-bose


text:
Fix patches/086-backport-f0c82253.patch

Fixes regression introduced in https://github.com/electron/libchromiumcontent/pull/558
The patch relies on changes introduced in https://chromium.googlesource.com/chromium/src/+/c5045f3a803a8375502ab153ce61bc6944c0ee28, which I've missed before.

/trop run backport-to electron-1-8-x

authors: MarshallOfSound miniak

repo: electron/libchromiumcontent