Helm repository is not available anymore

We used to use the Helm repository located at https://bloomberg.github.io/solr-operator/charts, but it seems not to be available anymore.
Is there a new location? The documentation still mentions the old location.

I don't know when it happened, but since solr-operator is now an apache project, it makes sense that the chart isn't hosted on bloombergs github page anymore. I'm looking for an alternative as well.

I don't know when it happened, but since solr-operator is now an apache project, it makes sense that the chart isn't hosted on bloombergs github page anymore. I'm looking for an alternative as well.

@bsankara any news on this? thanks

@bsankara any news on this? thanks

Hey everyone, sorry about this. I'll try to have it available as soon as possible.
Unfortunately the repo was moved to apache/lucene-solr-operator instead of apache/solr-operator. So it will have to be moved again. But I will try to make it work in the meantime. I'll post an update here and on the slack channel when it should be available.

Hey everyone, sorry about this. I'll try to have it available as soon as possible.
Unfortunately the repo was moved to apache/lucene-solr-operator instead of apache/solr-operator. So it will have to be moved again. But I will try to make it work in the meantime. I'll post an update here and on the slack channel when it should be available.

In the meantime, you should be able to use this instead: (Just a fix until the real changes have been made)
helm repo add solr-operator https://raw.githubusercontent.com/apache/lucene-solr-operator/master/docs/charts

In the meantime, you should be able to use this instead: (Just a fix until the real changes have been made)
helm repo add solr-operator https://raw.githubusercontent.com/apache/lucene-solr-operator/master/docs/charts

But, as you said, will the Git project and Helm repo eventually move to apache/solr-operator instead of apache/lucene-solr-operator?

But, as you said, will the Git project and Helm repo eventually move to apache/solr-operator instead of apache/lucene-solr-operator?

Great question, I should have addressed it.
It looks like we will unfortunately not be able to move to apache/solr-operator for a while. It will eventually move there, but I cant give a timeline. We will definitely be more vocal about the change beforehand next time and try to make the transition smoothless.

Great question, I should have addressed it.
It looks like we will unfortunately not be able to move to apache/solr-operator for a while. It will eventually move there, but I cant give a timeline. We will definitely be more vocal about the change beforehand next time and try to make the transition smoothless.

Okay, great, thanks a lot.

Okay, great, thanks a lot.

Just to be clear, @HoustonPutman meant 'smooth' 😄

Just to be clear, @HoustonPutman meant 'smooth' 😄

Did you ask INFRA if they can rename the repo to solr-operator for us? They will understand why...

Did you ask INFRA if they can rename the repo to solr-operator for us? They will understand why...

Yeah, I did. They do permissioning based off of apache project name prefix. So since Solr isn't a TLP yet, there are no user groups called "solr", so no one would have permissions for the "solr-operator". Since the group is called "lucene", we are able to have permissions for "lucene-solr-operator". We will be able to migrate once the "solr" TLP user groups are created, irrespective of when the Solr code actually splits.
It is frustrating, but it should be an easy enough move whenever the TLP gets created. (hopefully sooner rather than later)

Yeah, I did. They do permissioning based off of apache project name prefix. So since Solr isn't a TLP yet, there are no user groups called "solr", so no one would have permissions for the "solr-operator". Since the group is called "lucene", we are able to have permissions for "lucene-solr-operator". We will be able to migrate once the "solr" TLP user groups are created, irrespective of when the Solr code actually splits.
It is frustrating, but it should be an easy enough move whenever the TLP gets created. (hopefully sooner rather than later)


Unintuitive behavior when both features and package are specified

If I have a workspace:
Cargo.toml
foo/Cargo.toml

and run in the root of the workspace:
cargo build -p foo --features=bar

Cargo fails with an error #7742:

error: --features is not allowed in the root of a virtual workspace

while
cd foo
cargo build --features=bar

is accepted. It's surprising that specifying -p is not equivalent to building in that package's directory.
I expected that when -p points to a specific package, Cargo wouldn't try to use non-existent features from the root manifest (#4942), but instead look for the features in that package's own manifest.

There is a solution for this implemented via -Zpackage-features (#5364).  cargo build -p foo --features bar -Zpackage-features should work.

Perfect! Thank you.


Fixes/spelling

Hi Kevin, I found a few spelling errors. Not sure if you want to fix them all because it will make some files unreadable.

hold on, this is merging into the wrong branch!


deprecated Player prop methods to pluralize them

It's setting only one prop at a time so pluralizing the method name makes no sense.


DispatchSignedRequest || Hyper 0.12 || Struggle with Migration

Hello there,
I'm kind a struggle regarding the migration Rusoto 0.31.0 to 0.32.0
My program have an Option of StaticProvider
and before the migration I used to load DispatchSignedRequest with default_tls_client().unwrap()
Migration mention simple but as I can understand, it was replace by new and new_with are the oldest implementation regarding the PR #1077 for hyper 0.12.
I've seen comment of @srijs https://github.com/rusoto/rusoto/issues/1066#issuecomment-396156924
But don't know how implement DispatchSignedRequest the right way.
use rusoto_core::{Region};
use rusoto_logs::{
    CloudWatchLogs,
    CloudWatchLogsClient,
};
use hyper::Client;

fn get_client(region: Region, credentials_file: Option<String>) -> Box<CloudWatchLogs> {
    return match credentials::parse(credentials_file) {
        None => {
            Box::new(CloudWatchLogsClient::new(region))
        },
        Some(credentials) => {
            let client = Client::new();
            Box::new(CloudWatchLogsClient::new_with(
                client,
                credentials,
                region
            ))
        },
    }
}

Thanks.

Can you share the code you're having an issue with? Could be easier to help figure out the migration. 😄

Hi @matthewkmayer
Thanks for helping.
Here is the branch of repo and the PR concerned
https://github.com/Pierozi/awatchlog/blob/feat/metadata/src/awatchlog.rs#L99-L114
https://github.com/Pierozi/awatchlog/pull/14/files#diff-9494cf29ddb04424c9fcc7ae43bf3868R99

Looks like the issue was around creation of the clients CloudWatchLogsClient::new_with() required. Here's what I changed to get it to work.
Latest published version of Rusoto and friends in Cargo.toml:
-rusoto_core = "0.33.0"
-rusoto_logs = "0.33.0"
-rusoto_credential = "0.12.0"
+rusoto_core = "0.34"
+rusoto_logs = "0.34"
+rusoto_credential = "0.13"

git diff src/awatchlog.rs gives:
 use std::thread;
-use rusoto_core::{Region, DispatchSignedRequest, HttpClient};
+use rusoto_core::{Region, DispatchSignedRequest, HttpClient, DefaultCredentialsProvider};
 use rusoto_logs::{
     CloudWatchLogs,
     CloudWatchLogsClient,
@@ -102,13 +102,14 @@ fn get_client(region: Region, credentials_file: Option<String>) -> Box<CloudWatc
             Box::new(CloudWatchLogsClient::new(region))
         },
         Some(_credentials) => {
-            Box::new(CloudWatchLogsClient::new(region))
-            /*let client = HttpClient::Future;
+            let client = HttpClient::new().expect("failed to create request dispatcher");
+            // TODO: point it at credentials file
+            let credentials = DefaultCredentialsProvider::new().expect("Couldn't make a new credential provider");
             Box::new(CloudWatchLogsClient::new_with(
                 client,
                 credentials,
                 region
-            ))*/
-        },
+            ))
+        }
     }
 }

The function in non-diff form:

fn get_client(region: Region, credentials_file: Option<String>) -> Box<CloudWatchLogs> {
    return match credentials::parse(credentials_file) {
        None => {
            Box::new(CloudWatchLogsClient::new(region))
        },
        Some(_credentials) => {
            let client = HttpClient::new().expect("failed to create request dispatcher");
            // TODO: point it at credentials file
            let credentials = DefaultCredentialsProvider::new().expect("Couldn't make a new credential provider");
            Box::new(CloudWatchLogsClient::new_with(
                client,
                credentials,
                region
            ))
        }
    }
}

To read the credentials from a file, you can use the ProfileProvider.
Hope this helps! 😄

Hello @matthewkmayer,
Thanks for your input, don't know what change with v34 but it's work like a charm!
Yes, I should add too ProfileProvider as the third choice of credentials input.
Credentials and MetaData are the priority for now.


One NPE in ConfigValidationUtils.java

Hello,
Our static analyzer found a following potential NPE. We have checked the feasibility of this execution trace. It is necessary to defend this vulnerability to improve the code quality.
This issue has a similar bug trace as the one in #8194

Return null to caller
https://github.com/apache/dubbo/blob/f26ba91b67f642148a10d3b197502e29928b77bf/dubbo-common/src/main/java/org/apache/dubbo/common/utils/UrlUtils.java#L69

Function parseURL executes and returns
https://github.com/apache/dubbo/blob/f26ba91b67f642148a10d3b197502e29928b77bf/dubbo-common/src/main/java/org/apache/dubbo/common/utils/UrlUtils.java#L174

Function add executes and registries can contains null value
https://github.com/apache/dubbo/blob/f26ba91b67f642148a10d3b197502e29928b77bf/dubbo-common/src/main/java/org/apache/dubbo/common/utils/UrlUtils.java#L174

Program reaches the return point, and registries is the return value, which contains null value
https://github.com/apache/dubbo/blob/f26ba91b67f642148a10d3b197502e29928b77bf/dubbo-common/src/main/java/org/apache/dubbo/common/utils/UrlUtils.java#L176

Function parseURLs executes and returns
https://github.com/apache/dubbo/blob/f26ba91b67f642148a10d3b197502e29928b77bf/dubbo-config/dubbo-config-api/src/main/java/org/apache/dubbo/config/utils/ConfigValidationUtils.java#L206

Function next executes and returns null value
https://github.com/apache/dubbo/blob/f26ba91b67f642148a10d3b197502e29928b77bf/dubbo-config/dubbo-config-api/src/main/java/org/apache/dubbo/config/utils/ConfigValidationUtils.java#L208

The return value of function next is passed as the this pointer to function getProtocol (the return value of function next can be null), which will leak to null pointer dereference
https://github.com/apache/dubbo/blob/f26ba91b67f642148a10d3b197502e29928b77bf/dubbo-config/dubbo-config-api/src/main/java/org/apache/dubbo/config/utils/ConfigValidationUtils.java#L211

Commit: f26ba91b67f642148a10d3b197502e29928b77bf
ContainerAnalyzer

I will fix it.

I will fix it

Is there any progresss on this issue? @fangliji

it fixed by #8208


Add new API

[x] svd
[x] Pseudo inv, pinv - Moore-Penrose pseudoinverse of matrix.
[x] Gaussian elimination (backward subs) (inv)

[ ] Qr decomposition
[ ] Cholesky
[ ] Eigen values/vectors (less frequent)
[ ] LU Decomp
[ ] LDL Decomp
[ ] Matrix exponentiation (depends on SVD for A>=0, or on Eig for general matrices)
[ ] Gaussian Elimination for triangular matrices (should be trivial, but as long as it's there)
[ ] OLS (i.e., just QR then Pinv for triangular bit)
[ ] allowDestroy

[ ] Pure diagonal matrixes
[ ] Special routines for special matrices - Triangular (U or L), Diagonal (i.e., trivial stuff), Block Diagonal (much trickier), Banded and Tri-diagonal, Permutation matrices, Toeplitz

[ ] MMult,
[ ] Pinv (e.g., gaussian elim)
[ ] Schur Complement for block diagonal

[x] FFT - std.numeric for now
[ ] Matrix Creation

[x] Easy to stack matrices (Hstack and Vstack). See mir.ndslice.concatenation
[x] FlipUD, FlipLR (oops, got in the wrong order) reversed!0/reversed!1
[ ] special kind of B=P*A for P=permute

Hi @firoozye, what API Gaussian elimination should have? Does Matlab's \ / mldivide solves this problem?
ping @080993

Just a question, would it be possible to use operator overloading, so that
v_1 = v * M ; can be written directly? Instead of vec_1 = vec.mtimes(matrix);
During my studies of math, I used a C++-lib (written from my tutor) allowing to write this kind of code with an underlaid Fortran lib, if I remember right.
On the other side we did a lot with PVM / MPI for solving large linear equations on as many CPUs in the network. The network was very slow, 10 Mbit coax, but avoiding swapping to disk brought an over linear speedup. My task was to calculate the eigen-frequencies of an a clamped sheet and compare the result with the known of the squared sheet.
Any work in this parallelization direction?

Just a question, would it be possible to use operator overloading, so that
v_1 = v * M ; can be written directly?

A special matrix type is required. Current API uses ndslice.

4 decompositions was added


Make OPTIONS rendering clearer

We render the OPTIONS response via Not Found error handling, so to make this clearer, rename the render method to renderPlainOptionsMessage.

Coverage remained the same at 93.191% when pulling e3558a8c681d5af362e929a928e8c757ba4cf6a4 on akrabat:rename-options-rendering into afef745e9f425309f571b107b857fdb3b7374e7a on slimphp:3.x.

Not to be a ... stickler but I see that there is no test for this method ;)

@geggleto Test is here
This is just a rename of the method to make it clearer what it does.


Unable to link LEAN with fxcm

For a few days now, I am unable to link LEAN with fxcm. It was working until about a week ago.

Hey @hn2, just sanity tested it and it's working correctly for me in QC cloud. Mind providing more details?

20210211 23:30:02.366 Trace:: Config.GetValue(): debug-mode - Using default value: False
20210211 23:30:02.371 Trace:: Config.Get(): Configuration key not found. Key: results-destination-folder - Using default value:
20210211 23:30:02.372 Trace:: Config.Get(): Configuration key not found. Key: plugin-directory - Using default value:
20210211 23:30:02.373 Trace:: Config.Get(): Configuration key not found. Key: composer-dll-directory - Using default value: C:\QuantConnect\trade-fxcm-d1
20210211 23:30:02.477 Trace:: Config.Get(): Configuration key not found. Key: data-directory - Using default value: ../../../Data/
20210211 23:30:02.478 Trace:: Config.Get(): Configuration key not found. Key: version-id - Using default value:
20210211 23:30:02.478 Trace:: Config.Get(): Configuration key not found. Key: cache-location - Using default value: ../Data/
20210211 23:30:02.478 Trace:: Python for .NET Assembly: Python.Runtime, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null
20210211 23:30:02.478 Trace:: Engine.Main(): LEAN ALGORITHMIC TRADING ENGINE v<IP_ADDRESS> Mode: DEBUG (64bit)
20210211 23:30:02.479 Trace:: Engine.Main(): Started 11:30 PM
20210211 23:30:02.480 Trace:: Config.GetValue(): job-project-id - Using default value: 0
20210211 23:30:02.481 Trace:: Config.GetValue(): regression-update-statistics - Using default value: False
20210211 23:30:02.481 Trace:: Config.Get(): Configuration key not found. Key: lean-manager-type - Using default value: LocalLeanManager
20210211 23:30:02.483 Trace:: Config.Get(): Configuration key not found. Key: cloud-api-url - Using default value: https://www.quantconnect.com/api/v2/
20210211 23:30:02.496 Trace:: JobQueue.NextJob(): Selected ../my-algos/drl-forex/trade-fxcm-d1.py
20210211 23:30:02.511 Trace:: Python for .NET Assembly: nPython, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null
20210211 23:30:02.582 Trace:: Config.GetValue(): scheduled-event-leaky-bucket-capacity - Using default value: 120
20210211 23:30:02.583 Trace:: Config.GetValue(): scheduled-event-leaky-bucket-refill-amount - Using default value: 18
20210211 23:30:02.583 Trace:: Config.GetValue(): scheduled-event-leaky-bucket-time-interval-minutes - Using default value: 1440
20210211 23:30:02.585 Trace:: Config.Get(): Configuration key not found. Key: algorithm-id - Using default value: trade-fxcm-d1
20210211 23:30:02.585 Trace:: Config.GetValue(): scheduled-event-leaky-bucket-capacity - Using default value: 120
20210211 23:30:02.586 Trace:: Config.GetValue(): scheduled-event-leaky-bucket-refill-amount - Using default value: 18
20210211 23:30:02.586 Trace:: Config.GetValue(): scheduled-event-leaky-bucket-time-interval-minutes - Using default value: 1440
20210211 23:30:05.324 Trace:: Config.Get(): Configuration key not found. Key: data-permission-manager - Using default value: DataPermissionManager
20210211 23:30:05.325 Trace:: Config.Get(): Configuration key not found. Key: results-destination-folder - Using default value: C:\QuantConnect\trade-fxcm-d1
20210211 23:30:05.326 Trace:: Config.GetValue(): streamed-chart-limit - Using default value: 12
20210211 23:30:05.326 Trace:: Config.GetValue(): streamed-chart-group-size - Using default value: 3
20210211 23:30:05.330 Trace:: Config.Get(): Configuration key not found. Key: object-store-root - Using default value: ./storage
20210211 23:30:05.331 Trace:: Config.GetValue(): ignore-version-checks - Using default value: False
20210211 23:30:05.332 Trace:: AlgorithmManager.CreateTokenBucket(): Initializing LeakyBucket: Capacity: 120 RefillAmount: 18 TimeInterval: 1440
20210211 23:30:05.334 Trace:: Config.GetValue(): algorithm-manager-time-loop-maximum - Using default value: 20
20210211 23:30:05.341 Trace:: Config.GetValue(): consumer-batching-timeout-ms - Using default value: 0
20210211 23:30:05.596 Trace:: PythonInitializer.Initialize(): start...
PythonEngine.Initialize(): Runtime.Initialize()...
Runtime.Initialize(): Py_Initialize...
Runtime.Initialize(): PyEval_InitThreads...
Runtime.Initialize(): Initialize types...
Runtime.Initialize(): Initialize types end.
Runtime.Initialize(): AssemblyManager.Initialize()...
Runtime.Initialize(): AssemblyManager.UpdatePath()...
PythonEngine.Initialize(): register atexit callback...
PythonEngine.Initialize(): GetCLRModule()...
PythonEngine.Initialize(): clr GetManifestResourceStream...
20210211 23:30:05.856 Trace:: PythonInitializer.Initialize(): ended
20210211 23:30:05.859 Trace:: AlgorithmPythonWrapper(): Python version 3.6.8 |Anaconda, Inc.| (default, Feb 21 2019, 18:30:04) [MSC v.1916 64 bit (AMD64)]: Importing python module trade-fxcm-d1
20210211 23:30:07.673 Trace:: AlgorithmPythonWrapper(): Creating IAlgorithm instance.
20210211 23:30:07.727 Trace:: Config.GetValue(): mute-python-library-logging - Using default value: True
20210211 23:30:07.774 Trace:: Config.Get(): Configuration key not found. Key: results-destination-folder - Using default value: C:\QuantConnect\trade-fxcm-d1
20210211 23:30:07.775 Trace:: LocalObjectStore.Initialize(): Storage Root: C:\QuantConnect\trade-fxcm-d1\storage\QCAlgorithm
20210211 23:30:07.776 Trace:: LiveTradingDataFeed.GetDataChannelProvider(): will use DataChannelProvider
20210211 23:30:07.781 Trace:: Config.Get(): Configuration key not found. Key: data-aggregator - Using default value: QuantConnect.Lean.Engine.DataFeeds.AggregationManager
20210211 23:30:07.802 Trace:: LiveTradingDataFeed.GetDataQueueHandler(): will use FxcmBrokerage
20210211 23:30:07.803 Trace:: BaseDataExchange(CustomDataExchange) Starting...
20210211 23:30:07.806 Trace:: FxcmBrokerage.Connect()
log4j:WARN No appenders could be found for logger (com.fxcm.messaging.ConnectionManagerEx).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
20210211 23:30:08.507 ERROR:: LiveTradingResultHandler.Update(): Algorithm not yet initialized.
20210211 23:30:18.583 Trace:: LiveTradingResultHandler.SendStatusUpdate(): status: 'LoggingIn'.  Logging into brokerage...
20210211 23:30:18.584 Trace:: BrokerageSetupHandler.Setup(): Connecting to brokerage...
20210211 23:30:18.584 Trace:: BrokerageSetupHandler.Setup(): FXCM Brokerage account base currency: USD
20210211 23:30:18.584 Trace:: BrokerageSetupHandler.Setup(): Initializing algorithm...
20210211 23:30:18.584 Trace:: LiveTradingResultHandler.SendStatusUpdate(): status: 'Initializing'.  Initializing algorithm...
20210211 23:30:18.587 Trace:: Config.Get(): Configuration key not found. Key: security-data-feeds - Using default value:
20210211 23:31:18.642 Trace:: Isolator.ExecuteWithTimeLimit(): Used: 66, Sample: 72, App: 3634, CurrentTimeStepElapsed: 00:00.000
20210211 23:32:18.682 Trace:: Isolator.ExecuteWithTimeLimit(): Used: 88, Sample: 71, App: 3634, CurrentTimeStepElapsed: 00:00.000
20210211 23:33:18.695 Trace:: Isolator.ExecuteWithTimeLimit(): Used: 95, Sample: 113, App: 3658, CurrentTimeStepElapsed: 00:00.000
20210211 23:34:18.758 Trace:: Isolator.ExecuteWithTimeLimit(): Used: 103, Sample: 118, App: 3673, CurrentTimeStepElapsed: 00:00.000
20210211 23:35:18.619 Trace:: Isolator.ExecuteWithTimeLimit(): Execution Security Error: Operation timed out - 5 minutes max. Check for recursive loops.
20210211 23:35:18.623 ERROR:: Security.ExecuteWithTimeLimit(): Execution Security Error: Operation timed out - 5 minutes max. Check for recursive loops.
20210211 23:35:18.665 ERROR:: Engine.Run(): During the algorithm initialization, the following exception has occurred: System.TimeoutException: Execution Security Error: Operation timed out - 5 minutes max. Check for recursive loops.
at QuantConnect.Isolator.MonitorTask(Task task, TimeSpan timeSpan, Func1 withinCustomLimits, Int64 memoryCap, Int32 sleepIntervalMillis) in C:\Users\hanna\Source\Repos\Lean\Common\Isolator.cs:line 186    at QuantConnect.Isolator.ExecuteWithTimeLimit(TimeSpan timeSpan, Func1 withinCustomLimits, Action codeBlock, Int64 memoryCap, Int32 sleepIntervalMillis, WorkerThread workerThread) in C:\Users\hanna\Source\Repos\Lean\Common\Isolator.cs:line 95
at QuantConnect.Isolator.ExecuteWithTimeLimit(TimeSpan timeSpan, Action codeBlock, Int64 memoryCap, Int32 sleepIntervalMillis, WorkerThread workerThread) in C:\Users\hanna\Source\Repos\Lean\Common\Isolator.cs:line 201
at QuantConnect.Lean.Engine.Setup.BrokerageSetupHandler.Setup(SetupHandlerParameters parameters) in C:\Users\hanna\Source\Repos\Lean\Engine\Setup\BrokerageSetupHandler.cs:line 216Execution Security Error: Operation timed out - 5 minutes max. Check for recursive loops.
20210211 23:35:18.666 Trace:: JOB HANDLERS:
20210211 23:35:18.666 Trace::          DataFeed:     QuantConnect.Lean.Engine.DataFeeds.LiveTradingDataFeed
20210211 23:35:18.666 Trace::          Setup:        QuantConnect.Lean.Engine.Setup.BrokerageSetupHandler
20210211 23:35:18.666 Trace::          RealTime:     QuantConnect.Lean.Engine.RealTime.LiveTradingRealTimeHandler
20210211 23:35:18.667 Trace::          Results:      QuantConnect.Lean.Engine.Results.LiveTradingResultHandler
20210211 23:35:18.667 Trace::          Transactions: QuantConnect.Lean.Engine.TransactionHandlers.BrokerageTransactionHandler
20210211 23:35:18.667 Trace::          Alpha:        QuantConnect.Lean.Engine.Alphas.DefaultAlphaHandler
20210211 23:35:18.667 Trace::          ObjectStore:  QuantConnect.Lean.Engine.Storage.LocalObjectStore
20210211 23:35:18.667 Trace::          History Provider:     QuantConnect.Lean.Engine.HistoricalData.BrokerageHistoryProvider
20210211 23:35:18.668 Trace::          Brokerage:      QuantConnect.Brokerages.Fxcm.FxcmBrokerage
20210211 23:35:18.668 Trace:: LiveTradingDataFeed.Exit(): Start. Setting cancellation token...
20210211 23:35:18.668 Trace:: BaseDataExchange(CustomDataExchange) Stopping...
20210211 23:35:18.669 Trace:: LiveTradingDataFeed.Exit(): Exit Finished.
20210211 23:35:18.669 Trace:: DefaultAlphaHandler.Exit(): Exiting...
20210211 23:35:18.673 Trace:: DefaultAlphaHandler.Exit(): Ended
20210211 23:35:18.679 Trace:: BaseDataExchange(CustomDataExchange).ConsumeQueue(): Cancellation requested.  Exiting...
20210211 23:35:18.679 ERROR:: LiveTradingResultHandler.Update(): Algorithm not yet initialized.
20210211 23:35:18.679 ERROR:: During the algorithm initialization, the following exception has occurred: System.TimeoutException: Execution Security Error: Operation timed out - 5 minutes max. Check for recursive loops.
at QuantConnect.Isolator.MonitorTask(Task task, TimeSpan timeSpan, Func1 withinCustomLimits, Int64 memoryCap, Int32 sleepIntervalMillis) in C:\Users\hanna\Source\Repos\Lean\Common\Isolator.cs:line 186    at QuantConnect.Isolator.ExecuteWithTimeLimit(TimeSpan timeSpan, Func1 withinCustomLimits, Action codeBlock, Int64 memoryCap, Int32 sleepIntervalMillis, WorkerThread workerThread) in C:\Users\hanna\Source\Repos\Lean\Common\Isolator.cs:line 95
at QuantConnect.Isolator.ExecuteWithTimeLimit(TimeSpan timeSpan, Action codeBlock, Int64 memoryCap, Int32 sleepIntervalMillis, WorkerThread workerThread) in C:\Users\hanna\Source\Repos\Lean\Common\Isolator.cs:line 201
at QuantConnect.Lean.Engine.Setup.BrokerageSetupHandler.Setup(SetupHandlerParameters parameters) in C:\Users\hanna\Source\Repos\Lean\Engine\Setup\BrokerageSetupHandler.cs:line 216Execution Security Error: Operation timed out - 5 minutes max. Check for recursive loops.
20210211 23:35:18.681 ERROR:: LiveTradingResultHandler.Update(): Algorithm not yet initialized.
20210211 23:35:18.681 Trace:: Debug: FXCM Brokerage account base currency: USD
['EURUSD', 'USDJPY', 'GBPUSD', 'AUDUSD', 'USDCAD', 'USDCHF', 'NZDUSD']
[0.0001, 0.01, 0.0001, 0.0001, 0.0001, 0.0001, 0.0001]
[3, 3, 3, 3, 3, 3, 3]
oanda
4
24
td3
long_and_short
all
[log_returns]
['EURUSD', 'USDJPY', 'GBPUSD', 'AUDUSD', 'USDCAD', 'USDCHF', 'NZDUSD']
['spawn']
12
24
124
20210211 23:35:18.689 Trace:: StopSafely(): waiting for 'Result Thread' thread to stop...
20210211 23:35:18.784 Trace:: LiveTradingResultHandler.Run(): Ending Thread...
20210211 23:35:18.785 Trace:: LiveTradingResultHandler.SendFinalResult(): Starting...
20210211 23:35:53.858 Trace:: LiveTradingResultHandler.SendFinalResult(): Finished storing results. Start sending...
20210211 23:35:53.858 Trace:: LiveTradingResultHandler.SendFinalResult(): Ended
20210211 23:35:53.859 Trace:: Engine.Run(): Disconnecting from brokerage...
20210211 23:35:53.861 Trace:: FxcmBrokerage.Disconnect()
20210211 23:35:56.779 Trace:: Engine.Run(): Disposing of setup handler...
20210211 23:35:56.784 Trace:: BrokerageSetupHandler.Setup(): Found data queue handler to dispose: QuantConnect.Brokerages.Fxcm.FxcmBrokerage
20210211 23:35:56.797 Trace:: Engine.Main(): Analysis Completed and Results Posted.
Engine.Main(): Analysis Complete.
20210211 23:35:56.799 Trace:: Config.GetValue(): close-automatically - Using default value: False
Engine.Main(): Press any key to continue.
20210211 23:35:58.673 Trace:: FxcmBrokerage.GetHistory(): Maximum attempts reached for: GBPUSD

I am running the exact same script with oanda and it is working fine.

Hey @hn2, this issue is not happening in the cloud I believe, I see those logs are from a local deployment. From the logs FxcmBrokerage.GetHistory(): Maximum attempts reached for: GBPUSD, seems FXCM is timing out/failing in the history request, curious what mono version are you using?

I believe the latest one.

It throws this error:
mono_gdb_render_native_backtraces not supported on this platform, unable to find gdb or lldb
What mono version are you using in the cloud?

I believe the latest one.

See https://github.com/QuantConnect/Lean/blob/master/DockerfileLeanFoundation#L38, we are using 5.12. Suggest using quantconnect dockerhub images, at https://hub.docker.com/repository/docker/quantconnect/lean, to avoid these kinds of issues, closing this issue since it's not a Lean issue.

I was trying your code to install mono 5.12 but it keeps installing the latest version instead.
Even if I deleted old version, deleted and recreated mono-xamarin.list or even on a fresh new server, it keeps installing the latest version. What could be the problem?


Enemies not spawning

I am trying to do som missions but the Tech Wings and doom drones aren't spawning in Genius Grove.

Also when I enter Fusion Mayor's lair the quest doesn't update and nothing spawns

The dev team is currently working on placing mobs in the overworld. Once they're done with that, they will move on to fusion lairs.

Is there somewhere I can follow for news and updates?

Any updates will be posted on the discord server.

Gotcha!


Set up integration test framework

At a minimum we should have a way to create a temp dir on disk and populate it with a pnpm/yarn/npm workspaces setup matching some given config object, then returning a link to the dir to use in tests, along with setting up the workspace root and automating cleanup logic.
Maybe something like
function runTestInProject(config, async (dir) => {
  // do the test logic
})

Look at wireit for possible prior art.

I'm refactoring some parts of the CLI now, and integration tests of the commands would've been great to confirm I didn't break anything :) I think we should be able to use jest for this type of fs setup and cleanup, though I'm not sure how easy it would be to implement. Do you have any other ideas for the integration tests framework?

Sure, no worries! Sorry for the poor phrasing. I didn't mean to point out the absence of some tests ❤
It was more of a side note under this issue for us.


random action generation does not respect action limits

It looks like the line I am referencing generates random actions in the [0,1) interval, however action limits may be custom defined by algorithm parameters min_action and max_action. I have not been able to locate a part where the range is normalized to [min_action, max_action) range and the function has been consistently returning values between [0,1) for epsilon=1.0 (purely uniformly sampled at random).
https://github.com/AgileRL/AgileRL/blob/7496ebc31b9005b441ad4d0567454af0c5714e90/agilerl/algorithms/maddpg.py#L357
I am only referencing to MADDPG but I believe MATD3 also has the same characteristics.
EDIT: The generated values are clipped for tighter constraints fine but a larger action range such as [-1.0,1.0] does not work as expected.

Will get an update out shortly with better controls over action scaling across all algorithms.

Fixed and implemented better scaling options with support for asymmetrical min/max actions.


[v5] Require context if specified

Fixes #583

Merging this in since the relevant parts of the change were reviewed/resolved


Support Continue on Error in CSV Reader

Describe the bug
Attempting to read malformed CSV records where the number of columns doesn't match the schema leads to an out-of-memory error.
To Reproduce
See minimal example Rust code below.
arrow_bug.txt
Expected behavior
The CSV reader should start re-start reading from the first newline/delimiter after the malformed row is encountered.

Suggestion #1: if the reader encounters an unrecoverable error, it should be marked internally as being in an unrecoverable state and any attempts to continue reading should panic with an explicit message. Diagnosis of the panic would be easier than trying to work out where a silent out-of-memory error originates.
Suggestion #2: on encountering a schema mismatch, the reader should seek forward to the next unquoted delimiter and attempt to continue reading from there. If the delimiter is a newline character, the unquoted newline is only likely to be a problem if it occurs in a record which is already a schema mismatch; the reader would attempt to read forward from a non-terminal newline and the subsequent fields would also be mismatched to the schema.... at which point it's probably OK to fall back on the behaviour in suggestion #1. Would that be workable?

silent out-of-memory error

I think I am missing something here, the reader returns an error and should then no longer be used. I don't see how this is silent?

Well, it appeared silent to me. :)  I first encountered the OOM error after upgrading from an earlier version of the Arrow crate where the CSV reader would continue after encountering an error. I assumed the reader would continue to work in the same way after the upgrade, and found that my code would spin its wheels for a while and then exit with a "failed to allocate" memory error. The application gives no indication of where the error has arisen; hence I'd call that a silent error.
Yes, you could argue that I should have read the documentation more carefully. :) But a panic when I tried to use the failed reader would have made it explicit that I was trying to do something unwise.


[bug] "Input.is_action_pressed" method has a reproducible bug

Godot version:

3.1.1  &  3.2.dev.custom_build (current head)
OS/device including version:

tested on Windows 10 64 bit and Windows 7 64bit
Issue description:

Input.is_action_pressed() has a bug that can be easily reproduced.
If it occurs, is_action_pressed returns false even if the action is pressed.
You can test with the 2D Platformer  demo.
Steps to reproduce:

Open 2D Platformer demo
In this demo's InputMap there is an action called move_left.
　Left key of keyboard and left key of D-pad are set as events in this InputMap.

3.Let's Play the demo.
4. First, press and hold the left key of the D-pad.
robi will start walking.
5.In that state, press and release the left key on the keyboard.
After that, robi will stop even if you keep pressing the D-pad.
This is because is_action_pressed returns false.
You may think that there is no problem in real use cases, but there are problems in certain situations.
In most action games you can move with both D-pad and analog input.(Hollow Knight, Dead Cells, Bloodstained etc...)
To do this, suppose you assigned a D-pad and an analog input to the move action.
This bug occurs even with very weak analog inputs, so if the user (player) prefers to use a D-pad, the problem will occur.
Analog inputs can produce weak outputs even when not touched.
Even in this case, movement stops even if the player keeps pressing the D pad.
I actually tried it with the ps4 controller.
The dead zone remains at the default of 0.5.
Also, even if weak analog output occurs(some kind of noise), the character will not move without operation.
Even in this condition, when moving character with d-pad, the character sometimes stops due to this bug.
This bug seems to occur regardless of the dead zone setting.
That's all.
Thank you.

Duplicate of #23749


855 refactor dataGenerator

Description
refactor dataGenerator to make it easier to understand
Changes
split partitioning and dataBag generation logic into their own methods
Additional notes
no longer uses multiplexing dataBagSource, which was just a wrapper around combinationStrategy
Issue
Related to #855

Codecov Report

Merging #907 into master will increase coverage by 0.03%.
The diff coverage is 100%.

Impacted Files
Coverage Δ
Complexity Δ

...enerator/generation/DecisionTreeDataGenerator.java
100% <100%> (ø)
6 <5> (+1)
:arrow_up:

...nerator/walker/iterator/RouteDecisionIterator.java
100% <0%> (+4%)
10% <0%> (+1%)
:arrow_up:

...trictions/NoStringsPossibleStringRestrictions.java
85.71% <0%> (+28.57%)
4% <0%> (+2%)
:arrow_up:


Add localization

Resolves #129
Brief description
Add localization utilizing next-intl.
Checklist

[ ] I have built this pull request locally
[ ] I have ran the unit tests locally
[ ] I have manually tested this pull request
[ ] I have reviewed my pull request
[ ] I have added any relevant tests

Demonstration

The drop down code should be the same code used elsewhere to prevent issues like the ones shown.


Kubernetes Job yml manifest changes

What happened
When we deploy job.yml for kubernetes cluster we are facing kube-hunter.py file not found error. Need to change the job.yml file changes.
Expected behavior
Please use the followin yml file for kubernetes cluster.

apiVersion: batch/v1
kind: Job
metadata:
name: kube-hunter
spec:
template:
spec:
containers:
- name: kube-hunter
image: aquasec/kube-hunter
command: ["kube-hunter"]
args: ["--pod"]
restartPolicy: Never
backoffLimit: 4

I ran into this too with Pod deployment.
Job manifest Used
apiVersion: batch/v1
kind: Job
metadata:
  name: kube-hunter
spec:
  template:
    spec:
      containers:
      - name: kube-hunter
        image: aquasec/kube-hunter
        command: ["python", "kube-hunter.py"]
        args: ["--pod"]
      restartPolicy: Never
  backoffLimit: 4

Error seen with pods scheduled
$ kcl logs kube-hunter-2m5xb
python: can't open file 'kube-hunter.py': [Errno 2] No such file or directory

It's probably a dirty hack, but it worked as a simple workaround until the bug will get fixed
I replaced kube-hunber.py on the command to /usr/local/bin/kube-hunter and it fixed the problem
so the Job manifest
apiVersion: batch/v1
kind: Job
metadata:
  name: kube-hunter
spec:
  template:
    spec:
      containers:
      - name: kube-hunter
        image: aquasec/kube-hunter
        command: ["python", "/usr/local/bin/kube-hunter"]
        args: ["--pod"]
      restartPolicy: Never
  backoffLimit: 4

Had the same issue here and @ramakuka's new Job manifest suggestion worked fine here! You can probably submit this as the fix. Cheers!

When we consider the docker file we have to use as I added in the job.yml
file. Thanks Mgno for checking this.
On Thu, Sep 3, 2020 at 12:24 AM Magno Logan<EMAIL_ADDRESS>wrote:

Had the same issue here and @ramakuka https://github.com/ramakuka's new
Job manifest suggestion worked fine here! You can probably submit this as
the fix. Cheers!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aquasecurity/kube-hunter/issues/366#issuecomment-685932137,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJNXG6YERGUOIUEMR5TPCJLSD2IFPANCNFSM4QJHPTSQ
.

Should be fixed by #367

@lizrice @danielsagi job.yaml documented stopped working only recently. I understand #367 will work, but is that the right fix ?

@brathina-spectro can you please provide more info? what version of KH, how do you run it, what is the error you are getting? thanks

@brathina-spectro https://github.com/brathina-spectro . Yes this is the
correct fix. I was able to work with this fix without an issue. Pls provide
more info.
Sanka Sathyaji
On Fri, Sep 4, 2020 at 2:23 AM brathina-spectro<EMAIL_ADDRESS>wrote:

@lizrice https://github.com/lizrice @danielsagi
https://github.com/danielsagi job.yaml documented stopped working only
recently. I understand #367
https://github.com/aquasecurity/kube-hunter/pull/367 will work, but is
that the right fix ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aquasecurity/kube-hunter/issues/366#issuecomment-686758976,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJNXG62GZGYV4NMHV66SV7DSD7625ANCNFSM4QJHPTSQ
.


Could not resolve Maven dependencies ++ spark-salesforce-wave_2.10

Hi -
The Maven is not able to resolve and add artifact for spark-salesforce-wave_2.10 in the project.
Please help and confirm if the jar is available and correct Maven parameter.
Images of error attached.
Thanks,
Vineet

Hi Vineet,
Could you please use the latest version from maven repository?
Below is the maven dependency to be added in pom.xml

com.springml
spark-salesforce-wave_2.10
1.0.6

Thanks,
Sam.

Thanks. The Mavens details sorted it out.
Regards,
Vineet


ADX: expose DIPlus, DIMinus

May we expose DIPlus, DIMinus related to ADX ?

Hi @novecento ,
You can access to DIPlus and DIMinus using the class method related.
Example:
indicator = ADXIndicator(high=df[high], low=df[low], close=df[close], n=14, fillna=False)
df['trend_adx'] = indicator.adx()
df['trend_adx_pos'] = indicator.adx_pos()
df['trend_adx_neg'] = indicator.adx_neg()

Best,
Dario

Thanks Dario! Awesome awesome work.

Hi @novecento,
I have written the docstring documentation to every method of the class-based indicators. Now, you can check the documentation to get the information.
Best,
Dario


feat(addJudgePage) create Add Judge Page

Description
Designed the Add Judges Page using Figma
Fixes #14
Type of Change
Delete options that do not apply:

New feature (non-breaking change which adds functionality)

Is this a breaking change?

[ ] Yes
[x] No

@thetechie7 I added the endpoints u need:

POST /api/judge/csv - Content-Type=multipart/form-data with a single csv field that contains the CSV file uploaded
POST /api/judge/add - Content-Type=json - with 3 fields:

{
    "name": "name of judge",
    "email": "email of judge",
    "notes": "additional notes"
}

The errors don't clear when you upload new files.

oh no let me fix that


Fix remote builds with build.py

This has two changes to make building and using the uncompressed version of scratch blocks work, when doing a remote build:

get rid of a check for node_modules that was unnecessary and always set dir wrong
correctly check for the remote compiler

The second one is the same as #1512 with a long line broken apart.
I need this so that I can add workspace comments, because I need to be able to build and test them as I add new classes.

Changes look okay to me. Any idea why the build is failing on travis?

Oh no, tests pass locally but not on Travis :(


added missing translations; added polish language

Thanks for the PR. Adding languages should be done over at the potree repository: https://github.com/potree/potree/pull/735
since the PotreeConverter contains Potree as a dependency.

Should I rewrite it to potree/potree repo or it will be merget there from this commit?


Getting a MqttClient struct before server is reachable.

As far as I could tell, the only way to get a MqttClient struct is its start() method, but it fails if the server is not accessible.
This seems reasonable at first blush except it's inconsistent with the fact that rumqtt handles reconnection itself and can apparently stack pending publish() until connection succeeded. Mobile devices often have a flaky connection; rumqtt should handle connection issues at startup like it does at runtime.

Can I know which version you are using? master or v3? v3 has reconnection options to always retry. But it's still in development.

I'm using master, though I saw that a lot of work is happening in v3. Should I be trying v3 instead ? I'm still in the initial stage of mqtt support, I haven't settled on a particular lib yet, I might even go for a codec-only lib and handle the network myself (using actix).
Master does reconnect at runtime and eventually honors the publish() that was failing while the server was down. It's the initial start() that doesn't handle an unreachable server.
I can work around this, but this forces me to sprinkle initialisation code throughout the runtime codepaths, which is very inelegant. And I can't afford to stall initialisation until the server is up.

v3 is around 90% complete. Few more bugs to squash. It would also help me understand people's usecases. I would suggest you to please try v3 and give me a sample code of what's not working/ergonomic for you

I've switched to the v3 branch.
I was going to say that my issue was still there, but I eventually figured out that I needed to set_reconnect_opts(ReconnectOptions::Always(_)). Maybe the start() function could document that ?
Also, I wonder if some connection errors could be identified as permanent errors (like "host not found" as opposed to "connection timeout") and considered fatal anyway ? Maybe this is too much policy to put in rumqtt, and we should instead get APIs to query the number of connection attempts and/or the last error ?

Maybe the start() function could document that

I'll document these. Eventually :). Priority is to fix these issues to release v3.

Maybe this is too much policy to put in rumqtt, and we should instead get APIs to query the number of connection attempts and/or the last error ?

Yeah. We can revisit these once the core is stabilised

Maybe this is too much policy to put in rumqtt, and we should instead get APIs to query the number of connection attempts and/or the last error ?

Yeah. This might be a diminished return for the effort and increase learning curve for users to understand the cases where rumqtt won't reconnect (even with AlwayReconnect options).


Epic 6: Tree Details Page with functional builds, boots and tests

Sprint Goal: navigate to Tree Listing page Tree Details page and show case all the features. Focus on lists of builds, boots and tests and respective details page.
Demo: user uses dashboard to investigate problems with a tree. Dashboard is used to easily grasp build, boot and test errors. Tree Details Page is used for filtering data and identifying the root cause.
History Chart

[x] #151  (p1)
[ ] ~show commit message (p2)~

Status Changes

[ ] make sure all stats match (builds, boots, tests) (p1): #159 , #203
[ ] #232
[x] #233
[ ] #249
[ ] #250
[ ] #251
[ ] #252
[ ] #253

Tree Listing Page

[x] #227
[ ] #228
[x] #225
[x] #226
[x] #224

Tree Details Page

[ ] #229
[ ] #222
[ ] #230

Left Menu

[x] #94
[ ] #223

Comments from @padovan:

Add datetime (on hover) on the history graph
git describe seems to be missing on the per build pages, not sure if that's just the data not going into the database or not.
tree view: commit/tag should be wider
tree view:  Build status should be pass/fail, not valid/invalid.
tree view: git url could be trimmed
history graph: Success/fail instead of valid/invalid

Helen:

[ ] add url to search field
[ ] move search field to URL
[ ] Tree Listing Page: order by tree, branch, date

Comments from @padovan:
Tree Listing Page

[ ] remove Tree URL column and turn it into hoover
[ ] date columns: add time in a hover

Build Status

Success
Failed
Inconclusive (Unknown)

Boots/Test Status

Success (PASS)

Failed (FAIL)

Inconclusive (ERROR, MISS, SKIP, DONE)

Add datetime (on hover) on the history graph

git describe seems to be missing on the per build pages, not sure if that's just the data not going into the database or not.

tree view: commit/tag should be wider

tree view:  Build status should be pass/fail, not valid/invalid.

tree view: git url could be trimmed

history graph: Success/fail instead of valid/invalid

It seems execution list does not filter by current commit

Improve grouping of builds/boots/tests and navigation. @padovan , I think we need extra info to be able to work on that.

Add platform data to Test Details Page (from misc field, works only for maestro)

Show last time a test passed (in Test Details Page). We need more info here. For a specific build? @padovan

Add a build link in the Test Details Page.

Add pagination to the Tree Listing Page url

On Tree Listing Page, navigate to Builds/Boots/Tests tab depending on where the user clicked.

Filters does not affect the History Chart, but it should.

Add "under development" message to Tree Listing Page (p0)

Right-click to open in a new window/tab.


Record nav version

Does the tesla api export the version of navigation data?
If so could this be recorded in the same way as firmware versions.

I don't think the API provides that info.

You can find out what data the API provides here: https://tesla-api.timdorr.com/vehicle/state/data


Effective canister id in URL orcis-3qaaa-aaaad-qaaaa-cai does not match requested canister id: zsumk-yqaaa-aaaad-p34ya-cai.)

Saving me a lot of work! Unfortunately I haven't gotten the script to progress beyond just getting the canister ranges for each subnet.
I keep getting these types of errors:
HttpError(Http Error: status 400 Bad Request, content type "application/cbor", content: Effective canister id in URL orcis-3qaaa-aaaad-qaaaa-cai does not match requested canister id: zsumk-yqaaa-aaaad-p34ya-cai.)

I wonder if this effective canister id requirement changed recently? I can't even get the unmodified script to return the canister controllers and module hashes because of these errors.

I'm not sure how this batching is supposed to work if the effective canister id has to match the canister id in each path...

Unfortunately this tool does not work anymore because of the condition that effective canister id in the URL has to match all canister ids in every path. This condition has been in the specification for a long time, but it was not enforced by the implementation. Recently the condition started to be enforced by the nodes and this made my tool stop working.

Ah...too bad, I was afraid of that

So how do you check for canister metadata now?
I tried requesting the path /canister/<canister_id>/module_hash and got the same error...
I'm trying to iterate through all canisters to collect some data, cannot find any working example


Domain Adaptation with nematus

Hi folks,
I have trained a translation model with a dataset. After 510000th iteration, I have killed the training, and started a new training with a new dataset, by using the last 510000th model I had. For this reason, I have created a new models folder, and copied model.iter510000.npz as model.npz, and model.iter510000.npz.gradinfo.npz as model.npz.gradinfo.npz. But I forgot to copy model.iter510000.progress.json to my new models file.
Theoretically, it shouldn't effect the fact that I continue training from 510000th iteration, right? Because since I have not copied progress.json file, the output of the code shows like I have started from 0.

Yes, deleting the *.progress.json only resets the counter to 0, but
doesn't affect the learned weights.
best wishes,
Rico
On 03/06/17 04:59, saitarslanboun wrote:

Hi folks,
I have trained a translation model with a dataset. After 510000th
iteration, I have killed the training, and started a new training with
a new dataset, by using the last 510000th model I had. For this
reason, I have created a new models folder, and copied
model.iter510000.npz as model.npz, and
model.iter510000.npz.gradinfo.npz as model.npz.gradinfo.npz. But I
forgot to copy model.iter510000.progress.json to my new models file.
Theoretically, it shouldn't effect the fact that I continue training
from 510000th iteration, right? Because since I have not copied
progress.json file, the output of the code shows like I have started
from 0.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/rsennrich/nematus/issues/41, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAYry31cVsS6p4iTkDHeT3C51hR03Hx7ks5sANoigaJpZM4Nu9zH.


Broken link at README.md

At https://github.com/winstonjs/winston#querying-logs See Loggly Search API points to http://wiki.loggly.com/retrieve_events#optional, however it is 404 now.
I found this: https://www.loggly.com/docs/api-retrieving-data, but i believe that will not work for winston.

This was updated to the link you suggested. Thanks!


Can't able to call after update

@LichKing-2234
we have used same code for two different apps to communicate and its works on react-native-agora @alpha before it got depreciated,
know we have updated to the latest but video enables in one app only, in another app nothing is happen only shows a warning
Error: request to join channel is rejected
when tried twice,
need your help to fix this

pls provide the SDK log.

"react-native-agora": "^3.5.2",
"react": "17.0.2",
"react-native": "0.66.4",
@LichKing-2234

I mean our SDK log file, you can refer to the comments of setLogFile method to get more information.

Sorry I won't get properly what you asking exactly @LichKing-2234

Just know get that agora won't supporting in android version more than 10


Setting custom LB name

Great project. Very much enjoy using it!
Is it possible to set the Load Balancers Name as it appears in the AWS Console as part of the manifests? We produce several of these LB's using Helm charts, the ingress names and namespaces are identical in each cluster, making it inconvenient to determine which LB is on which cluster. We're currently using the tags to find the right cluster but it would make things marginally easier.

Currently this is not possible. There is a controller parameter where you can set alb prefix: https://github.com/kubernetes-sigs/aws-alb-ingress-controller/blob/e5c5d6e293e2b81167791ca9b2cea39fc5af7078/internal/ingress/controller/config/config.go#L75
..but it's not really useful in case where you need to find the ALB programmatically.
I'm thinking of trying to take a stab at this, as the workarounds are not that nice. Would be good to get a confirmation from the maintainers that they'd accept the PR.

@M00nF1sh could you kindly chip in your opinion?

@M00nF1sh could you kindly chime in?

I've been wondering about this too, is there a way the controller can write to the ingress status:
1.- ALB name.
2.- ALB arn.
maybe target group arn?
It will improve the UX, in our case we have large multi tenant clusters, our users don't have access to the AWS accounts, every time they need the ALB name or ARN they have to contact us.
If this is a desirable approach I might be able to submit a PR if @M00nF1sh doesn't beat me to :).
Thanks!

IMO it could be as simple as removing the prefix. The prefix is already an empty string by default. I think the code should avoid generating a prefix if it is by default not provided.
With "namespace" + "ingressName" + md5sum, it is already quite sufficient to avoid collision. Though I assume the reason to have a prefix is exactly to avoid a collision.. so maybe we will need to have some collision handling code.

/remove-lifecycle stale

This also has the potential to make consuming ALB logs and metrics way easier.
The whole problem boils down to a scenario that might be pretty common:

One AWS account
Multiple clusters per environment (staging, production, development)
Same namespace and ingress name in each cluster
Folks struggling to figure out what cluster's a load balancer tied to. Including all the resources related to it (metrics, logs).

Hi guys,
with the new v2.0.0 controller, we have applied AWS tags to resources, which will allow to track resources.
Also, we removed support for name prefix and used a general pattern for load balancer name: "k8s-namespace-ingName-hash".
We'll add support to customize ALB name soon, tracking it at https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/1483
@jescarri we'll add ALB ARN into Ingress annotations, tracking it at https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/1573
closing this issue.

Thank @M00nF1sh 😄


For some reason I am unable to start stream with location filter.

When I use this code I get stream no problem.

Auth.SetUserCredentials("consumerKey", "consumerSecret", "accessToken", "accesTokenSecret");
var stream = Stream.CreateFilteredStream();
stream.AddTrack("twitter");
stream.MatchingTweetReceived += (sender, args) =>
{
Console.WriteLine(args.Tweet);
};
stream.StartStreamMatchingAllConditions();

But whenever I add location filter to stream.

Auth.SetUserCredentials("consumerKey", "consumerSecret", "accessToken", "accesTokenSecret");
var stream = Stream.CreateFilteredStream();
stream.AddTrack("twitter");
stream.AddLocation(new Coordinates(-74, 40), new Coordinates(-73, 41));
stream.MatchingTweetReceived += (sender, args) =>
{
Console.WriteLine(args.Tweet);
};
stream.StartStreamMatchingAllConditions();

I get no response. No exception or anything.

Sorry for not replying earlier. Have you been able to solve your problem?

Yes problem is resolved. I had fiddler installed on my system it was interfering with traffic. Stream is working fine :)


feat: add linter to istio/proxy to check CEL expressions for validity

Describe the feature request
Add a linter to istio/proxy that prevents typos and misconfigurations around CEL expressions. These are hard to catch during human review of code.
Example: https://github.com/istio/proxy/pull/3076
[ X ] Extensions and Telemetry
Additional context
/cc @gargnupur @kyessenov @bianpengyuan

I would like to give this issue a try!


Wrong framework version targeted

I've followed the instructions on how to set target framework for upgrade assistant: https://github.com/episerver/upgrade-assistant-extensions#using-the-extension
But I can see from log files that .NET 6 sdk is being used....
Setting env variable does not seem to work.

It will always use the latest version of msbuild because the tool is written in dotnet 6.  However it should set the correct version when updating the project file framework version,

@marijorg
If you have multiple versions of SDK installed and want to build with specific .NET5 SDK, you'll need to build your own version of upgrade-assistant instead. Please refer to Johan's blog post with more details.
https://world.optimizely.com/blogs/Johan-Bjornfot/Dates1/2022/1/upgrade-to-cms-12-updates-to-upgrade-assistant-extensions/

Ok, closing issue.


intermittent error when trying to provision/ssh EC2 boxes

Any idea what might be causing the following intermittent error when trying to ssh into or provision an EC2 box (popped up a day or two ago)? Something to do with the excon and/or fog gems? Sometimes the commands work fine, sometimes the error is thrown.
Thanks
/Users/troyshu/.vagrant.d/gems/gems/excon-0.44.4/lib/excon/middlewares/expects.rb:6:in `response_call': Expected(200) <=> Actual(0 Unknown) (Excon::Errors::HTTPStatusError)
excon.error.response
  :body          => "[a long amazon response]"
  :headers       => {
    "Content-Type" => "text/xml;charset=UTF-8"
    "Date"         => "Wed, 12 Aug 2015 22:52:38 GMT"
    "Server"       => "AmazonEC2"
    "Vary"         => "Accept-Encoding"
  }
  :local_address => "<IP_ADDRESS>"
  :local_port    => 63241
  :reason_phrase => "K"
  :remote_ip     => "[some ip]"
  :status        => 0
	from /Users/troyshu/.vagrant.d/gems/gems/excon-0.44.4/lib/excon/middlewares/response_parser.rb:8:in `response_call'
	from /Users/troyshu/.vagrant.d/gems/gems/excon-0.44.4/lib/excon/connection.rb:372:in `response'
	from /Users/troyshu/.vagrant.d/gems/gems/excon-0.44.4/lib/excon/connection.rb:236:in `request'
	from /Users/troyshu/.vagrant.d/gems/gems/excon-0.44.4/lib/excon/middlewares/idempotent.rb:26:in `error_call'
	from /Users/troyshu/.vagrant.d/gems/gems/excon-0.44.4/lib/excon/middlewares/base.rb:10:in `error_call'
	from /Users/troyshu/.vagrant.d/gems/gems/excon-0.44.4/lib/excon/middlewares/base.rb:10:in `error_call'
	from /Users/troyshu/.vagrant.d/gems/gems/excon-0.44.4/lib/excon/connection.rb:256:in `rescue in request'
	from /Users/troyshu/.vagrant.d/gems/gems/excon-0.44.4/lib/excon/connection.rb:204:in `request'
	from /Users/troyshu/.vagrant.d/gems/gems/excon-0.44.4/lib/excon/middlewares/idempotent.rb:26:in `error_call'
	from /Users/troyshu/.vagrant.d/gems/gems/excon-0.44.4/lib/excon/middlewares/base.rb:10:in `error_call'
	from /Users/troyshu/.vagrant.d/gems/gems/excon-0.44.4/lib/excon/middlewares/base.rb:10:in `error_call'
	from /Users/troyshu/.vagrant.d/gems/gems/excon-0.44.4/lib/excon/connection.rb:256:in `rescue in request'
	from /Users/troyshu/.vagrant.d/gems/gems/excon-0.44.4/lib/excon/connection.rb:204:in `request'
	from /Users/troyshu/.vagrant.d/gems/gems/excon-0.44.4/lib/excon/middlewares/idempotent.rb:26:in `error_call'
	from /Users/troyshu/.vagrant.d/gems/gems/excon-0.44.4/lib/excon/middlewares/base.rb:10:in `error_call'
	from /Users/troyshu/.vagrant.d/gems/gems/excon-0.44.4/lib/excon/middlewares/base.rb:10:in `error_call'
	from /Users/troyshu/.vagrant.d/gems/gems/excon-0.44.4/lib/excon/connection.rb:256:in `rescue in request'
	from /Users/troyshu/.vagrant.d/gems/gems/excon-0.44.4/lib/excon/connection.rb:204:in `request'
	from /Users/troyshu/.vagrant.d/gems/gems/fog-xml-0.1.1/lib/fog/xml/sax_parser_connection.rb:37:in `request'
	from /Users/troyshu/.vagrant.d/gems/gems/fog-xml-0.1.1/lib/fog/xml/connection.rb:7:in `request'
	from /Users/troyshu/.vagrant.d/gems/gems/fog-aws-0.1.1/lib/fog/aws/compute.rb:528:in `_request'
	from /Users/troyshu/.vagrant.d/gems/gems/fog-aws-0.1.1/lib/fog/aws/compute.rb:523:in `request'
	from /Users/troyshu/.vagrant.d/gems/gems/fog-aws-0.1.1/lib/fog/aws/requests/compute/describe_instances.rb:81:in `describe_instances'
	from /Users/troyshu/.vagrant.d/gems/gems/fog-aws-0.1.1/lib/fog/aws/models/compute/servers.rb:63:in `all'
	from /Users/troyshu/.vagrant.d/gems/gems/fog-aws-0.1.1/lib/fog/aws/models/compute/servers.rb:150:in `get'
	from /Users/troyshu/.vagrant.d/gems/gems/vagrant-aws-0.6.0/lib/vagrant-aws/action/read_ssh_info.rb:24:in `read_ssh_info'
	from /Users/troyshu/.vagrant.d/gems/gems/vagrant-aws-0.6.0/lib/vagrant-aws/action/read_ssh_info.rb:15:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
	from /Users/troyshu/.vagrant.d/gems/gems/vagrant-aws-0.6.0/lib/vagrant-aws/action/connect_aws.rb:43:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builder.rb:116:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `block in run'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/util/busy.rb:19:in `busy'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `run'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:214:in `action_raw'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:191:in `block in action'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/environment.rb:516:in `lock'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:178:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:178:in `action'
	from /Users/troyshu/.vagrant.d/gems/gems/vagrant-aws-0.6.0/lib/vagrant-aws/provider.rb:24:in `ssh_info'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:415:in `ssh_info'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/ssh_exec.rb:26:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builder.rb:116:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `block in run'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/util/busy.rb:19:in `busy'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `run'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/call.rb:53:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builder.rb:116:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `block in run'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/util/busy.rb:19:in `busy'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `run'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:214:in `action_raw'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:191:in `block in action'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:174:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:174:in `block in action'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:178:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:178:in `action'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh/command.rb:59:in `block in execute'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/plugin/v2/command.rb:226:in `block in with_target_vms'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/plugin/v2/command.rb:220:in `each'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/plugin/v2/command.rb:220:in `with_target_vms'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh/command.rb:41:in `execute'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/cli.rb:42:in `execute'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/environment.rb:301:in `cli'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/bin/vagrant:174:in `<main>'

doesn't seem to be happening any more... maybe Amazon fixed something on their side

Sorry, this seems to be happening again. A few days ago, provisioning and ssh was working perfectly fine... Any ideas?

I am also having the problem. I have been using knife ec2 server create to successfully provision EC2s for a long time, and it randomly stopped working in us-east-1 last week. Others I've found online seem to be having the same problem. I think the problem is on Amazon's side and I just created a support ticket.
@troyshu are you using us-east-1?

@xtinagodwin @troyshu same issue here when using fog, seems to be related to something wonky in us-east-1. Are you using IAM?

@daanemanz yes I am using IAM

I'm opening a ticket with AWS to investigate -- it seems to be an issue related to the metadata service.
Approximate times of errors:

Aug 11 16:00 UTC - Aug 13 1:00 UTC
Aug 14 12:30 UTC - present

Update -- this seems to be related to the excon gem. @troyshu I see that whatever version of vagrant-aws you're using, uses excon-0.44.4 which is very likely due to the use of an older version of fog (version 1.22, see here).
This issue was fixed in https://github.com/excon/excon/pull/494. After updating the excon gem, I indeed started getting the expected result.

@daanemanz This fixed the problem for me as well! Thanks!!!

Thank you - updating to excon-0.45.4 fixed the issue for me too.

Thanks @daanemanz! https://github.com/mitchellh/vagrant-aws/issues/406#issuecomment-131919977

I actually did not touch my gems, and the error stopped appearing about a week or so; things are now working consistently. Maybe Amazon did something on their side. Will close this for now...


Fix exception thrown when database is null in config

What does this PR do?
Fixes a type check error:
error: sqlserver:6342f67680de647e | (sqlserver.py:316) | Initialization exception 'NoneType' object has no attribute 'lower'
Traceback (most recent call last):
  File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/sqlserver/sqlserver.py", line 289, in initialize_connection
    db_exists, context = self.connection.check_database()
  File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/sqlserver/connection.py", line 261, in check_database
    db_exists, context = self._check_db_exists()
  File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/sqlserver/connection.py", line 397, in _check_db_exists
    if database.lower() in self.existing_databases:
AttributeError: 'NoneType' object has no attribute 'lower'

Motivation

Additional Notes

Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached

We could also add a test to validate this fix


#494 Resolve issue with not showing messages of loglevel INFO

Fixed the issue with not showing messages of log-level INFO and not formatting the ones from level WARNING and above by overwriting uvicorn's default logging config.
resolves #494

@asynchroza we should be good to go

@asynchroza we should be good to go

FYI @IvanObreshkov you can rerequest a review by clicking the icon next to my handle:

Amazing job on this one :raketa:. I feel like this ticket turned out to be more beneficial than expected :kriskobeats:

Thank you mate!

@IvanObreshkov one last note - can you update the description of the PR since it doesn't really reflect what you actually did.


Fix #374: Add admin UI for timezone config

Also fix a bug that scrape.py doesn't support input type="number".

Thanks! Merged.


[APP-887] Users are getting prompted to verify email too often

We have it at once a week right now. In hindsight I think that was the wrong call, because some people simply won't want to verify and nagging them endlessly won't fix that. I'm going to modify it to ask once, and store than in device storage. That'll still lead to multiple prompts (switching devices, account storage clearing) but it'll be better.
APP-887

Another downside to this approach to be aware of is that you won't get prompted when you create a second account. We'll ultimately want to move this server-side.


rx.js error prevents me from scafolfding

I've a systematic error after having reinstalled yo today. I didn't get the error a few weeks ago on the same env.
> yo gruntplugin
undefined
For more information about Grunt plugin best practices,
please see the docs at http://gruntjs.com/creating-plugins
? Plugin Name grunt-foodfacts

/home/bertrand/.nvm/versions/node/v5.10.1/lib/node_modules/yo/node_modules/rx/dist/rx.js:77
    throw e;
    ^
grunt-foodfacts

I've indtalled<EMAIL_ADDRESS>the last version of the generator-gruntplugin
node 5.10.1, npm 3.9.0

I've retried from a fresh install :
nvm install v6.1.0
npm install -g yo generator-gruntplugin

And the result is the same :
➜  grunt-foodfact yo gruntplugin
(node:9751) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
undefined
For more information about Grunt plugin best practices,
please see the docs at http://gruntjs.com/creating-plugins
? Plugin Name grunt-food

/home/bertrand/.nvm/versions/node/v6.1.0/lib/node_modules/yo/node_modules/rx/dist/rx.js:77
    throw e;
    ^
grunt-food

➜  grunt-foodfact yo --version && echo $PATH $NODE_PATH && node -e 'console.log(process.platform, process.versions)'
1.8.1
/home/bertrand/.nvm/versions/node/v6.1.0/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
linux { http_parser: '2.7.0',
  node: '6.1.0',
  v8: '<IP_ADDRESS>',
  uv: '1.9.0',
  zlib: '1.2.8',
  ares: '1.10.1-DEV',
  icu: '56.1',
  modules: '48',
  openssl: '1.0.2h' }

It seems to be related to the generator only : https://github.com/yeoman/generator-gruntplugin/issues/32

encountered the same error with https://github.com/Dica-Developer/generator-node-webkit in rx.js:77

Same error while scaffolding with https://github.com/Dica-Developer/generator-node-webkit in rx.js:77


Airflow fails dag with no visible reason after executing only first task when dag_timeout is used

Full environment is at https://github.com/kretes/docker-airflow/tree/airflow-scheduler-hang-up
A. code
from datetime import datetime, timedelta

from airflow import DAG
from airflow.operators import BashOperator, DummyOperator

dag = DAG("MYDAG",
          default_args={"owner" : "me",
                        "start_date":datetime.now() - timedelta(minutes=100)},
          schedule_interval='*/3 * * * *',
          concurrency=6,
          dagrun_timeout=timedelta(minutes=4)
          )

def command():
    return "echo {{ params.myparam }} {{ (execution_date - macros.timedelta(hours = 1)).strftime('%Y/%m/%d %H %M') }} 2>&1 >> /tmp/logs"

run_this_last = DummyOperator(task_id='run_this_last', dag=dag)

firstTask = BashOperator(
        task_id='first',
        bash_command=command(),
        params= {"myparam":"1"},
        dag=dag)
secondTask = BashOperator(
        task_id='second',
        bash_command=command(),
        params= {"myparam":"2"},
        dag=dag)

firstTask.set_downstream(secondTask)
secondTask.set_downstream(run_this_last)

B. DAG:

C. I start airflow (whole environment with docker)
D. after some time scheduler stops executing full dag:

logs from the first 'error' run:
scheduler_1 | [2016-02-11 08:09:03,024] {jobs.py:507} INFO - Prioritizing 0 queued jobs
scheduler_1 | [2016-02-11 08:09:03,031] {models.py:197} INFO - Importing /usr/local/airflow/dags/thourly.py
scheduler_1 | [2016-02-11 08:09:03,034] {models.py:284} INFO - Loaded DAG <DAG: MYDAG>
scheduler_1 | [2016-02-11 08:09:03,063] {models.py:2156} INFO - Checking state for <DagRun MYDAG @ 2016-02-11 08:06:00: scheduled__2016-02-11T08:06:00, externally triggered: False>
scheduler_1 | [2016-02-11 08:09:03,065] {jobs.py:455} INFO - Getting list of tasks to skip for active runs.
scheduler_1 | [2016-02-11 08:09:03,067] {jobs.py:470} INFO - Checking dependencies on 3 tasks instances, minus 0 skippable ones
scheduler_1 | [2016-02-11 08:09:03,077] {base_executor.py:34} INFO - Adding to queue: airflow run MYDAG first 2016-02-11T08:06:00 --local -sd DAGS_FOLDER/thourly.py
scheduler_1 | [2016-02-11 08:09:03,109] {jobs.py:633} INFO - Done queuing tasks, calling the executor's heartbeat
scheduler_1 | [2016-02-11 08:09:03,110] {jobs.py:636} INFO - Loop took: 0.088226 seconds
scheduler_1 | [2016-02-11 08:09:03,111] {models.py:222} INFO - Finding 'running' jobs without a recent heartbeat
scheduler_1 | [2016-02-11 08:09:03,111] {models.py:228} INFO - Failing jobs without heartbeat after 2016-02-11 08:06:48.111842
scheduler_1 | [2016-02-11 08:09:03,115] {celery_executor.py:62} INFO - [celery] queuing ('MYDAG', 'first', datetime.datetime(2016, 2, 11, 8, 6)) through celery, queue=default
worker_1    | [2016-02-11 08:09:03,424] {__init__.py:36} INFO - Using executor CeleryExecutor
worker_1    | [2016-02-11 08:09:03,962] {__init__.py:36} INFO - Using executor CeleryExecutor
scheduler_1 | [2016-02-11 08:09:08,031] {jobs.py:507} INFO - Prioritizing 0 queued jobs
scheduler_1 | [2016-02-11 08:09:08,036] {models.py:197} INFO - Importing /usr/local/airflow/dags/thourly.py
scheduler_1 | [2016-02-11 08:09:08,038] {models.py:284} INFO - Loaded DAG <DAG: MYDAG>
scheduler_1 | [2016-02-11 08:09:08,088] {jobs.py:455} INFO - Getting list of tasks to skip for active runs.
scheduler_1 | [2016-02-11 08:09:08,088] {jobs.py:470} INFO - Checking dependencies on 0 tasks instances, minus 0 skippable ones
worker_1    | Logging into: /usr/local/airflow/logs/MYDAG/first/2016-02-11T08:06:00
scheduler_1 | [2016-02-11 08:09:08,115] {jobs.py:633} INFO - Done queuing tasks, calling the executor's heartbeat
scheduler_1 | [2016-02-11 08:09:08,115] {jobs.py:636} INFO - Loop took: 0.091296 seconds
scheduler_1 | [2016-02-11 08:09:08,116] {models.py:222} INFO - Finding 'running' jobs without a recent heartbeat
scheduler_1 | [2016-02-11 08:09:08,116] {models.py:228} INFO - Failing jobs without heartbeat after 2016-02-11 08:06:53.116813
scheduler_1 | [2016-02-11 08:09:13,022] {jobs.py:507} INFO - Prioritizing 0 queued jobs
scheduler_1 | [2016-02-11 08:09:13,029] {models.py:197} INFO - Importing /usr/local/airflow/dags/thourly.py
scheduler_1 | [2016-02-11 08:09:13,031] {models.py:284} INFO - Loaded DAG <DAG: MYDAG>
scheduler_1 | [2016-02-11 08:09:13,062] {jobs.py:455} INFO - Getting list of tasks to skip for active runs.
scheduler_1 | [2016-02-11 08:09:13,062] {jobs.py:470} INFO - Checking dependencies on 0 tasks instances, minus 0 skippable ones
scheduler_1 | [2016-02-11 08:09:13,085] {jobs.py:633} INFO - Done queuing tasks, calling the executor's heartbeat
scheduler_1 | [2016-02-11 08:09:13,085] {jobs.py:636} INFO - Loop took: 0.06762 seconds
scheduler_1 | [2016-02-11 08:09:13,086] {models.py:222} INFO - Finding 'running' jobs without a recent heartbeat
scheduler_1 | [2016-02-11 08:09:13,087] {models.py:228} INFO - Failing jobs without heartbeat after 2016-02-11 08:06:58.087064

Airflow marks DAG as 'failed' with no information in logs nor in UI

One possible reason for that *might be in https://github.com/airbnb/airflow/blob/master/airflow/jobs.py#L373  where dag is being failed - but is that code ok? In my case there was no actual timeout
There should be at least some logging about the reason of failing the DAG stored in the 'DagRun' object to be viewed in the GUI. and of course in logs.

I think I can add more to this hypothesis.
Doing 'select * from dag_run;' on this environment I can see all dag_runs' start_dates are the same - calculated when the dag file was first parsed.
This makes code for timeout verification notice timeout and the dag is failed...
Does this reasoning make sense?

I have your code running locally against sqllite and sequential executor.
I modified command to print out the execution date (not the hour before the execution date):
def command():
    return "echo {{ params.myparam }} {{ (execution_date).strftime('%Y/%m/%d %H %M') }} 2>&1 >> /tmp/logs_1"

The output looks normal.
sid-as-mbp:dags siddharth$ tail -f /tmp/logs_1
1 2016/02/11 11 58
1 2016/02/11 12 00
1 2016/02/11 12 03
2 2016/02/11 11 58
1 2016/02/11 12 06
2 2016/02/11 12 00
1 2016/02/11 12 09
2 2016/02/11 12 03
1 2016/02/11 12 12
2 2016/02/11 12 06
1 2016/02/11 12 15
2 2016/02/11 12 09

Wait.. I might be seeing an issue.  Can you restart your webserver and tell me if this goes away?
I'm seeing the following on the webserver...
[2016-02-11 14:25:30,595] {models.py:295} INFO - Loaded DAG <DAG: test_regex_1>
[2016-02-11 14:25:30,595] {models.py:204} INFO - Importing /Users/siddharth/Projects/airflow/dags/test_s3_sensor.py
[2016-02-11 14:25:30,615] {models.py:295} INFO - Loaded DAG <DAG: test_s3_sensor>
[2016-02-11 14:25:30,616] {models.py:204} INFO - Importing /Users/siddharth/Projects/airflow/dags/testdruid.py
[2016-02-11 14:25:30,616] {models.py:295} INFO - Loaded DAG <DAG: test_druid>
[2016-02-11 15:12:31 -0800] [77157] [CRITICAL] WORKER TIMEOUT (pid:80323)
[2016-02-11 15:12:31 -0800] [77157] [CRITICAL] WORKER TIMEOUT (pid:80308)
[2016-02-11 15:12:31 -0800] [77157] [CRITICAL] WORKER TIMEOUT (pid:80309)
[2016-02-11 15:12:31 -0800] [77157] [CRITICAL] WORKER TIMEOUT (pid:80310)
[2016-02-11 15:12:31 -0800] [80323] [INFO] Worker exiting (pid: 80323)
[2016-02-11 15:12:31 -0800] [80308] [INFO] Worker exiting (pid: 80308)
[2016-02-11 15:12:31 -0800] [80309] [INFO] Worker exiting (pid: 80309)
[2016-02-11 15:12:31 -0800] [80310] [INFO] Worker exiting (pid: 80310)
[2016-02-11 15:12:31 -0800] [80986] [INFO] Booting worker with pid: 80986
[2016-02-11 15:12:31 -0800] [80987] [INFO] Booting worker with pid: 80987
[2016-02-11 15:12:31 -0800] [80988] [INFO] Booting worker with pid: 80988
[2016-02-11 15:12:31 -0800] [81006] [INFO] Booting worker with pid: 81006
[2016-02-11 15:12:31,828] {__init__.py:36} INFO - Using executor SequentialExecutor
[2016-02-11 15:12:31,838] {__init__.py:36} INFO - Using executor SequentialExecutor
[2016-02-11 15:12:31,881] {__init__.py:36} INFO - Using executor SequentialExecutor
[2016-02-11 15:12:31,965] {__init__.py:36} INFO - Using executor SequentialExecutor
[2016-02-11 15:12:32,605] {models.py:126} INFO - Filling up the DagBag from /Users/siddharth/Projects/airflow/dags

and
usr/local/lib/python2.7/site-packages/sqlalchemy/sql/compiler.py:572: SAWarning: Can't resolve label reference 'execution_date desc'; converting to text() (this warning may be suppressed after 10 occurrences)
  util.ellipses_string(element.element))

I think I saw the tree view frozen. When I restarted the webserver, it refreshed as all green.

Also, BTW, I don't use the dag_timeout, but the logic you pointed me is suspicious indeed.
-s

@r39132 the webserver didn;t have any hiccup here, so we didn't try to mess with him. Furthermore the problem looks deeply inside scheduler, the logs from scheduler say the same.
and yes the dag_timeout is necessary to reproduce the issue - we removed this param on production and everything goes well since then.

Hi @kretes,
Ok. So, can you confirm a few things for me, since I am unable to reproduce this issue. Are you getting the error because your tasks are taking longer than 4 minutes to run? I don't use celery and am wondering if the combined times of running and some necessary heart beating is exceeding the 4 minutes you have set as a timeout.

@r39132 no the tasks are simple echos they complete in a few seconds including scheduling overhead.
I think the problem comes from the place in the code I pointed out. It would be good to add some better status for dag fail 'timeouted' instead of a general 'failed' to be sure, though.
When doing 'select * from dag_run'
I see entries that have start date set to the moment I first 'deployed' this DAG. Therefore the dag run will be timeouted.
Did you try to reproduce the issue by cloning the repo I prepared and running docker-compose there?

I switched executor to 'local' and the same happens.
First a few dag runs go well but then they freeze (it first happens when dag run ends after a specified dag timeout added to a first start_date of first dag run. see the example when dag timeout was set to 1 minute:

Are you running in UTC everywhere?

I ran your code and reproduced it on the LocalExecutor. Interestingly, I was not able to reproduce it on the SequentialExecutor....

I didn't try with the SequentialExecutor,
I'm really happy that you were able to reproduce this issue finally ;-)

If you can find and fix the bug, I'd be happy to review a PR.

Here is what I have found.
I have a modified piece of code (modified from what @kretes) provided. Here is the code :
from datetime import datetime, timedelta

from airflow import DAG
from airflow.operators import BashOperator, DummyOperator

dag = DAG("MYDAG_5",
          default_args={"owner" : "me",
                        "start_date":datetime.now()},
          schedule_interval='*/1 * * * *',
          dagrun_timeout=timedelta(minutes=4)
          )

def command():
    return "echo {{ params.myparam }} {{ (execution_date).strftime('%Y/%m/%d %H %M') }} 2>&1 >> /tmp/logs"

run_this_last = DummyOperator(task_id='run_this_last', dag=dag)

firstTask = BashOperator(
        task_id='first',
        bash_command=command(),
        params= {"myparam":"1"},
        dag=dag)
secondTask = BashOperator(
        task_id='second',
        bash_command=command(),
        params= {"myparam":"2"},
        dag=dag)

firstTask.set_downstream(secondTask)
secondTask.set_downstream(run_this_last)

I loaded this new DAG around 02-17T03:22:47.319562
When the DAG starts, it fails due to the DAGRUN_TIMEOUT!

Looking at the DAG run view, I see the following :

As you can see, it has failed almost immediately after starting. Each and every run fails!
Looking at the DAG run table, I see the following :

It looks like the problem is that the start date is set 8 hours behind the execution date!
I loaded the DAG 02-17T03:22:47.319562 and my schedule is minutely, but the start_dates are set to '2016-02-16 19:23:02.289377', which is 8 hours behind the current datetime and also behind the execution_date.
I am running everything in UTC, except the database! My database is running in PST.
sid-as-mbp:r39132_airflow siddharth$ !psql
psql -h localhost -U siddharth airflow
psql (9.4.1)
Type "help" for help.

airflow=# select CURRENT_TIMESTAMP;
             now
------------------------------
 2016-02-16 19:34:40.06475-08
(1 row)

So, it looks like start_date is set based on the DB TZ, while the execution_date is set using TZ where airflow is executing

I've confirmed and fixed this. Our stage and prod envs are on UTC, but my laptop used to be on PST. It's now also on GMT/UTC, and now so is my local postgresql instance.
After changing my DB TZ and restarting scheduler and webserver, it works.

@kretes I suspect this is also happening to you. Closing for now. If this is not the issue, then ping me to reopen.
If you use Postgres 9.4, you can change the TZ by
airflow=# ALTER DATABASE airflow  SET timezone TO 'Etc/GMT';
The logout of the DB and relogin:
airflow=# select CURRENT_TIMESTAMP;
              now
-------------------------------
 2016-02-17 03:59:46.934656+00
(1 row)

From my point of view having an implicit requirement of run in UTC, and introducing weird bugs when it is not running like that instead of 'forcing' this as this is internal DB configuration is a bug.
I see https://github.com/airbnb/airflow/issues/1015 is tracked so hopefully it will be solved

Agreed. It's a bug. We are looking for contributors as well, so feel free to pick issues off the list.

Also, we need to make running in UTC an explicit requirement until we can fix the code to not care.


"npm install firebase angularfire2 --save" throwing exception Ionic 2 version > beta.11

Ionic 2 version > beta.11
How to reproduce:
Within your ionic project directory > type > npm install firebase angularfire2 --save
Exception:
npm WARN peerDependencies The peer dependency<EMAIL_ADDRESS>included from angularfire2 will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm ERR! Darwin 15.6.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "angularfire2" "firebase" "--save"
npm ERR! node v4.4.7
npm ERR! npm  v2.15.8
npm ERR! code EPEERINVALID
npm ERR! peerinvalid The package<EMAIL_ADDRESS>does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>

As it states, ionic@beta is using angular2-rc4 and angularfire2 is using released version of angular2. That's why this issue belongs to ionic2's GitHub page, not here.

I suggest you use an older angularfire2 beta version until Ionic2 moves to Angular2 Final. I would suggest:
"angularfire2": "2.0.0-beta.2",
"firebase": "3.3.0"

@appplumbr What @alwaysprep is true. @dmastag's answer will help you as well.

@all - updated > Expected release for ionic beta12 this week that will fix this issue


Parker becomes a multitool for many object detection use cases

Then should it not be renamed to something more generic like 'objectrr'? ;-)


cannot load such file -- cucumber/ast/scenario

error that I get
cannot load such file -- cucumber/ast/scenario
Error creating formatter: PrettyFace::Formatter::Html (LoadError)
/Users/dennisdem/.rvm/gems/ruby-2.2.1/gems/pretty_face-0.10.3/lib/pretty_face/formatter/html.rb:5:in require' /Users/dennisdem/.rvm/gems/ruby-2.2.1/gems/pretty_face-0.10.3/lib/pretty_face/formatter/html.rb:5:in<top (required)>'
/Users/dennisdem/.rvm/gems/ruby-2.2.1/gems/cucumber-2.0.0/lib/cucumber/constantize.rb:17:in require' /Users/dennisdem/.rvm/gems/ruby-2.2.1/gems/cucumber-2.0.0/lib/cucumber/constantize.rb:17:inrescue in constantize'
/Users/dennisdem/.rvm/gems/ruby-2.2.1/gems/cucumber-2.0.0/lib/cucumber/constantize.rb:6:in constantize' /Users/dennisdem/.rvm/gems/ruby-2.2.1/gems/cucumber-2.0.0/lib/cucumber/cli/configuration.rb:73:informatter_class'
/Users/dennisdem/.rvm/gems/ruby-2.2.1/gems/cucumber-2.0.0/lib/cucumber/cli/configuration.rb:172:in block in formatter_factories' /Users/dennisdem/.rvm/gems/ruby-2.2.1/gems/cucumber-2.0.0/lib/cucumber/cli/configuration.rb:168:inmap'
/Users/dennisdem/.rvm/gems/ruby-2.2.1/gems/cucumber-2.0.0/lib/cucumber/cli/configuration.rb:168:in formatter_factories' /Users/dennisdem/.rvm/gems/ruby-2.2.1/gems/cucumber-2.0.0/lib/cucumber/runtime.rb:193:informatters'
/Users/dennisdem/.rvm/gems/ruby-2.2.1/gems/cucumber-2.0.0/lib/cucumber/runtime.rb:185:in report' /Users/dennisdem/.rvm/gems/ruby-2.2.1/gems/cucumber-2.0.0/lib/cucumber/runtime.rb:67:inrun!'
/Users/dennisdem/.rvm/gems/ruby-2.2.1/gems/cucumber-2.0.0/lib/cucumber/cli/main.rb:38:in execute!' /Users/dennisdem/.rvm/gems/ruby-2.2.1/gems/cucumber-2.0.0/bin/cucumber:9:in<top (required)>'
/Users/dennisdem/.rvm/gems/ruby-2.2.1/bin/cucumber:23:in load' /Users/dennisdem/.rvm/gems/ruby-2.2.1/bin/cucumber:23:in<top (required)>'
-e:1:in load' -e:1:in'
Running Rubymine
Using cucumber 2.0.0
Using pretty_face 0.10.3
Using rspec 3.2.0
Using selenium-webdriver 2.46.2

I'm also getting the same error, did anybody find a solution to this?

any update on this issue?

I think it need's to be reliased

I am working on pretty_face update right now.  I hope to have a functioning release out soon.

On Nov 10, 2015, at 7:06 AM, vveliev<EMAIL_ADDRESS>wrote:
I think it need's to be reliased
—
Reply to this email directly or view it on GitHub https://github.com/cheezy/pretty_face/issues/41#issuecomment-155445469.

Thanks @cheezy thats a great news..!!

I am having the issue also.

after this is fixed it might be a good time for a new release

any updates on this one?

any news sir @cheezy ?

Hi all , any updates/work arounds on this issue ? I have looked into options : 1 downgrade cucumber 2. Allure  3. reportbuilder . Any more  suggestions .

I am also facing same issue.Did anybody find any solution ?

could you take me off the list?

On Dec 28, 2016, at 8:41 PM, ktyagi<EMAIL_ADDRESS>wrote:
I am also facing same issue.Did anybody find any solution ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/cheezy/pretty_face/issues/41#issuecomment-269569142, or mute the thread https://github.com/notifications/unsubscribe-auth/AA98D0Rb2wsPFsU6uU7pRm59RS9K92NBks5rMw_ggaJpZM4E9Mzr.

Has anyone been able to find a solution to the issue with pretty face :+1:
cannot load such file -- cucumber/ast/scenario (LoadError)
C:/Ruby22-x64/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:121:in require' C:/Ruby22-x64/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:121:in require'
C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/pretty_face-0.10.3/lib/pretty_face/formatter/html.rb:5:i
C:/Ruby22-x64/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:69:in require' C:/Ruby22-x64/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:69:in require'
C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/pretty_face-0.10.3/lib/pretty_face.rb:2:in <top (requir C:/Ruby22-x64/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:128:in require'
C:/Ruby22-x64/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:128:in rescue in require' C:/Ruby22-x64/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:39:in require'
C:/Work/FMS-Automation/features/support/hooks.rb:2:in <top (required)>' C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/cucumber-2.4.0/lib/cucumber/rb_support/rb_language.rb:96 C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/cucumber-2.4.0/lib/cucumber/rb_support/rb_language.rb:96 C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/cucumber-2.4.0/lib/cucumber/runtime/support_code.rb:142: C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/cucumber-2.4.0/lib/cucumber/runtime/support_code.rb:84:i C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/cucumber-2.4.0/lib/cucumber/runtime/support_code.rb:83:i C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/cucumber-2.4.0/lib/cucumber/runtime/support_code.rb:83:i C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/cucumber-2.4.0/lib/cucumber/runtime.rb:253:in load_step
C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/cucumber-2.4.0/lib/cucumber/runtime.rb:61:in run!' C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/cucumber-2.4.0/lib/cucumber/cli/main.rb:32:in execute!'
C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/cucumber-2.4.0/bin/cucumber:8:in `<top (required)>'

I guess this has been left for dead and to rot..

Guess after 2 years it won't get fixed...time to move on...
has been unusable for years for me now

Tried to use this gem. Had to remove it because this issue makes it unusable.


Use async/await in Deploy Client

I was seeing some inconsistent errors around the HttpClient calls with cancelled tasks, so I adjusted the code to use async/await for those calls, and that appeared to address the issue.
I also did some minor cleanup and enhanced error logging in this PR.

After some more usage, I think the issue here is that the timeout in the HttpClient is being shortened to 25 seconds, instead of the default of 100 seconds, and this is causing errors (if the site needs to start up initially, or restart after the install).  Do y'all remember the reason that the timeout was specified at 25 seconds?

@bdukes No, but I think using the default of 100 seconds is a good precaution. We've been having issues with timeouts too.
I can make the change if you like.

👍 thanks @can-martin-kennish


Update the website withe 0.10.0-alpha.

Fixed by #1358. (Why didn't this close automatically?)

Probably b/c the change was merged into gh-pages instead of master.


Uncaught TypeError: ace.define is not a function

I am not using RequireJS, but using the src to load ace and we are loading it in this order in our html.
	<script src="../scripts/aceSrc/ace.js" type="text/javascript" charset="utf-8"></script>
	<script src="../scripts/aceSrc/ext-language_tools.js" type="text/javascript" charset="utf-8"></script>
	<script src="../scripts/aceSrc/ext-modelist.js" type="text/javascript" charset="utf-8"></script>

	<script src="../scripts/webIntellisense/webintellisense.js"></script>
	<script src="../scripts/webIntellisense/webintellisense-ace.js"></script>
	<link href="../styles/webIntellisense/webintellisense.css" rel="stylesheet" />

However right away we get an error
Uncaught TypeError: ace.define is not a function(anonymous function) @ webintellisense-ace.js:1
I checked and in the ace.js file line 49 var define =  is present so I am not sure why we are getting this error.
We have a working ACE Editor in the page, and are trying to add the intellisense but have not added in any of the JS yet in to the page to implement webIntellisense.

https://github.com/ajaxorg/ace-builds/issues/78
this was explained in this issue in ace


Update base.html.twig

More w3 validation fixes.

Bad value 100% for attribute width on element img: Expected a digit but saw % instead.
Bad value auto for attribute height on element img: Expected a digit but saw a instead.
The width attribute is already in the CSS styling and the height attribute does nothing as its read incorrectly anyway
Added alt description to featured image, search engines do not like empty alt tags

Well yes I'm not sure what I was trying to accomplish here.
In fast there is just the max-height attribut on the a tag


[SPARK-50398][CORE] Use ExitCode 0 for --help usage in Spark scripts

What changes were proposed in this pull request?
This PR aims to use 0 as the exit code for --help usage in Spark scripts consistently to provide better and consistent UX from Apache Spark 4.0.0.
Why are the changes needed?
Initially, Apache Spark was designed to exit with 0 when --help is given because --help argument is not a error case.
SparkSubmit
https://github.com/apache/spark/blob/d5da49d56d7dec5f8a96c5252384d865f7efd4d9/core/src/main/scala/org/apache/spark/deploy/SparkSubmitArguments.scala#L458-L459
Spark Master
https://github.com/apache/spark/blob/d5da49d56d7dec5f8a96c5252384d865f7efd4d9/core/src/main/scala/org/apache/spark/deploy/master/MasterArguments.scala#L88-L89
Spark Worker
https://github.com/apache/spark/blob/d5da49d56d7dec5f8a96c5252384d865f7efd4d9/core/src/main/scala/org/apache/spark/deploy/worker/WorkerArguments.scala#L107-L108
Spark History Server
https://github.com/apache/spark/blob/d5da49d56d7dec5f8a96c5252384d865f7efd4d9/core/src/main/scala/org/apache/spark/deploy/history/HistoryServerArguments.scala#L39-L40
In addition, all scripts under bin/* return 0 consistently like the following. This PR changes sbin/* scripts additionally for consistency.

Command
Before
After

bin/spark-class --help
0
0

bin/spark-shell --help
0
0

bin/pyspark --help
0
0

bin/spark-sql --help
0
0

bin/beeline --help
0
0

bin/sparkR --help
0
0

bin/docker-image-tool.sh --help
0
0

sbin/start-master.sh --help
1
0

sbin/start-worker.sh --help
1
0

sbin/start-history-server.sh --help
1
0

sbin/start-thriftserver.sh --help
1
0

sbin/start-connect-server.sh --help
1
0

Does this PR introduce any user-facing change?
Yes, but this is a exit status code for --help or -h.
How was this patch tested?
Manual review.
Was this patch authored or co-authored using generative AI tooling?
No.

+1, LGTM. Merging to master.
Thank you, @dongjoon-hyun.

Thank you, @MaxGekk .


Autologin ipadress needs to be set for autologin to work .... (Auto-login IP Address (Optional):)

If this configuration field is not set - autologin does not work with DNN9
Seems like the implementation/logic also is weak - should be able to define ipnet with mask.
Now it just converts your IP to a long and checks if its equal to one of the ipadresses in the list(converted to long) or greater/less than the adresses(converted to long) in the provided range.
Set to <IP_ADDRESS>-<IP_ADDRESS> autologin works ....

@Audun1555
Are you suggesting that for range we add the ability to enter something such as: <IP_ADDRESS>/32 instead of <IP_ADDRESS>-<IP_ADDRESS>?
Even with this implementation, will still need to check if local IP is within range after masking.  This feature will just clean up the ranges a bit and in some cases make adding ranges a little simpler.  Is this correct?
Trying to clarify before making code change.  Thanks for your input @Audun1555!

Hi, that was my initial thought - a more network/tcpip like approach ...
Maybe IPv6 should also be taken into account?
A few hints here on how this can be implemented:
https://stackoverflow.com/questions/2138706/how-to-check-a-input-ip-fall-in-a-specific-ip-range
On short term the most important thing to fix is to make autologin work if the configuration is left blank. (as stated in the documentation this should autologin everyone - guess many people give up in trying to set it up now - when autologin does not work without a defined IP range that the clients local ip is in the range)
//Audun

Release 6.1.2 has an added feature to enable/disable auto login and the auto-login ip address field is only used if auto login is enabled.  When enabled and ip address field is left blank, everyone is automatically logged on.
I will add a separate feature request for ip address mask.


Realtime messaging data channel example

I have successfully sent json data from the esp32 to the webrtc website but i dont know how we can send data from website to the esp32. is there any receive handler on the esp32 libpeer side?

I pushed the code that have some event callback for ESP32. You can try it
https://github.com/sepfy/libpeer/blob/main/examples/esp32/main/app_main.c#L57

woah thats fast thank you, I'll test it


Update README.md with easy-to-read US time.

Adding PST for easy conversion for US.
Signed-off-by: Catblade<EMAIL_ADDRESS>

#34 resolves