sched: rm nxsched_remove_readytorun

Summary
In the scenario of active waiting, context switching is inevitable, and we can eliminate redundant judgments.
code size
before
size nuttx
text    data     bss     dec     hex filename
262848   49985   63893  376726   5bf96 nuttx
after
size nuttx
text    data     bss     dec     hex filename
263324   49985   63893  377202   5c172 nuttx
reduce code size by  -476
Configuring NuttX and compile:
$ ./tools/configure.sh -l qemu-armv8a:nsh_smp
$ make
Running with qemu
$ qemu-system-aarch64 -cpu cortex-a53 -smp 4 -nographic
-machine virt,virtualization=on,gic-version=3
-net none -chardev stdio,id=con,mux=on -serial chardev:con
-mon chardev=con,mode=readline -kernel ./nuttx
Impact
Testing

The previous function nxsched_remove_readytorun suffered from being overly complex in its logic judgments due to its comprehensive functionality,
which also made it inconsistent with its name. By splitting this function into multiple, more specific functions for different scenarios,
we can significantly reduce the complexity of the code.
For instance, the intricate implementation of the TLIST_HEAD macro was once a necessity to be invoked frequently,
but now it's only required in certain scenarios, leading to a decrease in its frequency of use.
There are similar implementations that have undergone similar optimizations.
After these optimizations, we tested nxsem_wait and observed an approximate 10% performance gain in terms of cycles.

nxsched_add_readytorun()/nxsched_remove_readytorun() are paired functions. If you feel the logic is not clear enough, you could separate the requirements according to the task status and merge list, but do not expose it to kernel developers, which will reduce the readability of the code and increase the maintenance cost.
Abort newly added interface in this PR, there are special requirements for thread status and list merging, but in nxsched_remove_readytorun(), there will only be a few more conditional branches(if). If you want to optimize, we could add parameters to nxsched_remove_readytorun instead of using inexplicable interfaces to confuse developers.
nxsched_remove()? did not you think the function naming is weird?

Kernel interfaces are as reusable as possible. We need to balance some performance (if), which does improve code readability and avoids many low-level errors. I don't want to see all interfaces in the future like freertos (****_FromISR)

nxsched_add_readytorun()/nxsched_remove_readytorun() are paired functions. If you feel the logic is not clear enough, you could separate the requirements according to the task status and merge list, but do not expose it to kernel developers, which will reduce the readability of the code and increase the maintenance cost.
About newly added interface in this PR, there are special requirements for thread status and list merging, but in nxsched_remove_readytorun(), there will only be a few more conditional branches(if). If you want to optimize, we could add parameters to nxsched_remove_readytorun instead of using inexplicable interfaces to confuse developers.
nxsched_remove()? did not you think the function naming is weird?

Kernel interfaces are as reusable as possible. We need to balance some performance (if), which does improve code readability and avoids many rookie errors. I don't want to see all interfaces in the future like freertos (****_FromISR)

i update patch just add one interface nxsched_remove_self


Test frameworks

What do we want to use for testing? Mocha, jest, I dunno...
I've had decent results testing the modules using mocha, maybe we could stick with that for the redux stuff and then do some view layer tests with Jest?
The last time I tried to set up Jest on react native, it was super busted. Allegedly, they're supporting it now.

FWIW, I've seen a lot of support being poured into Jest. Also, the whole mocha ecosystem feels weird since you need so many deps just to make an assertion.

There's Enzyme as well.

Here's a maybe nice blog post<EMAIL_ADDRESS>


Chibuzo- Develop Landing page with TailwindCSS

Using Tailwind CSS to develop the landing page.

@Domicaren1 what's the update with this ticket? Are you having any issue?


Update yweather.py

Map clear-night string to 31 value.
Description:
It maps 31 value to "clear-night" string.
Related issue (if applicable): fixes #
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>
Example entry for configuration.yaml (if applicable):

Checklist:

[x] The code change is tested and works locally.
[ ] Local tests pass with tox. Your PR cannot be merged unless tests pass

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

Hi @wiuwiu,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!


Hint about your message: MSBUILD : error MSB1009: Project file does not exist.

MSBuild version 17.9.5+33de0b227 for .NET Framework
MSBUILD : error MSB1009: Project file does not exist.
Switch: MyLittleAxmolGameDemo-main.vcxproj

You have renamed the folder:   MyGameDemo to  MyLittleAxmolGameDemo
works here:

Oh... Thank you again
I got It


Master to DEV

- Summary

- Test plan

- Description for the changelog

**- To make the DEV and Master file aligned

👷 Deploy Preview for theentrepreneurialhour processing.

Name
Link

🔨 Latest commit
aa789279fc13981928341098f39c0593250e1215

🔍 Latest deploy log
https://app.netlify.com/sites/theentrepreneurialhour/deploys/64f69e6de0db950008cde243


SSL_CONF_cmd() doesn't recognize cmd but should as per documentation

Hi,
I have a SSL server implementation for which I have to increase backward compatibility for clients with older TLS version support.
For that I found, that if I edit the openssl.cnf statement MinProtocol, the backward compatibility improves.
However, the goal is not to bother with this configuration file but to achieve the same through the OpenSSL library.
I found this documentation where the above described should be possible.
However as you can see the demonstration program below, it's not working.
$ gcc `pkg-config --cflags --libs openssl` -o ssl-conf ssl-conf.c
$ ./ssl-conf
OpenSSL Version: OpenSSL 1.1.1d  10 Sep 2019
SSL_CONF_cmd() returned -2
$ cat ssl-conf.c

#include <stdio.h>
#include <openssl/ssl.h>

int main(void)
{
   int ret;
   SSL_CTX *ctx;
   SSL_CONF_CTX *ssl_conf;

   SSL_library_init();

   ctx = SSL_CTX_new(TLS_server_method());
   ssl_conf = SSL_CONF_CTX_new();

   ret = SSL_CONF_cmd(ssl_conf, "MinProtocol", "TLSv1");

   printf("OpenSSL Version: %s\n", OPENSSL_VERSION_TEXT);
   printf("SSL_CONF_cmd() returned %d\n", ret);

   return 0;
}

To me it seems to be a bug as it's documented that in the version I've installed it should be supported, but it returns with -2 which means that MinProtocol is not recognized.
Could you please check?
Thank you in advance.

Debugging led me to the realization, that the flags need to be set. Re-reading the documentation,  I see now the slight mentioning about the flag implication.
Maybe a more definitive sentence like "flags need to be set using the SSL_CONF_CTX_set_flags() function" would have led me to this conclusion earlier with less effort.
However it still means this issue is invalid. Sorry for bothering.
Closing....


getPassMasked fails on windows in git bash

when using running getPassMasked on windows terminal emulators like git bash and Cmder, the password it not masked and is printed after it is submitted.
I am running on golang version 1.9

I haven't taken a look at this in a while but based on my memory I don't think there is a very feasible way to get this to work.
The masking happens by making syscalls to change the cmdline behavior and if you are using a program that ignores syscalls there isnt a standard way to know what to do.
Effectively each terminal emulator would need to have a hook to specify how to modify its own behavior and gopass would have to know which to call or just call them all.
I ran into issues with the same root cause when trying to do stdlib go stuff + cygwin terminal.

Same as #34 effectively.

Is there a solution now

I think the readme says it best at this point:

You should probably just use terminal.

A lot has been developed for the go stdlib terminal package since this was originally developed and I dont know if it has much to offer at this point. Lots of examples to find in other repos of its use too.
Good luck

No longer maintained.


[DO NOT INTEGRATE] ISPN-10373 non blocking spi temporary

This PR is here solely to test CI for the changes in another branch.

Is this ready to merge? :stuck_out_tongue_winking_eye:

Looks like the SHA-1 is confusing CI. The actual run is https://ci.infinispan.org/job/Infinispan/view/change-requests/job/PR-8349/1/

org.infinispan.persistence.jdbc.stringbased.NonStringKeyPreloadTest.ThreadLeakChecker has failed here too :cry:


Model for prediction of survival

In this issue, I detail the work done to get a model predicting death using code model_training/survival_model
Let's first describe the data used in this case:

Input data: 181 subjects, 138 features
Target data: 181 subjects, 1 target

Here is the distribution of length of survival, since the end of the treatment (column ='date_fin'). We considered that those who died before the end of the treatment had a survival of 0. The ones who didn't die are not displayed in this following graph.

For this work, 3 models were trained:

Death prediction (without any timeframe)
This first model was trained on the entirety of data. In this case, we don't take into account the date of death. The data contains 56 subjects which died (out of 181).
The data is split into training (80% = 144 subjects) and testing (20% = 37 subjects)
The results are the following:

ROC AUC Score: 0.7966666666666666
Brier score:0.13994517546675272
Average precision: 0.8
Average Recall: 0.6666666666666666
Accuracy Score: 0.8378378378378378
AUC-PR score: 0.7873873873873873

Death prediction within 1 year
In this case, we consider that all those who died after 1 year (365 days) are considered as Negatives.
The data split is the same.  Number of subjects that died within 1 year:  12 (train: 10/ test: 2)
The result of the model are the following:

ROC AUC Score:  0.7285714285714286
Brier score  0.05123339930604174
Average precision 0.0
Average Recall 0.0
Accuracy Score:  0.9459459459459459
AUC-PR score   0.527027027027027
It seems that this model basically always predicts 0 (no death).

Death prediction within 3 year
In this case, we consider that all those who died after 3 year (1095 days) are considered as Negatives.
The data split is the same.  Number of subjects that died within 3 year:  40 (train: 32/ test: 8)
The result of the model are the following:

ROC AUC Score:  0.6163793103448276
Brier score  0.1856659172388495
Average precision 0.5
Average Recall 0.125
Accuracy Score:  0.7837837837837838
AUC-PR score   0.4070945945945946

I am currently working on the averaging the data across nodules for each patient.
I found the following things to investigate, some patients have varying values across nodules for:

score_charlson
centrale
tabac_PA
etalement
tabac
histo
delai_fin_DC
tabac_sevre
dose_tot
BED_10
OMS

Currently, asking clarifications on this.

Here are the new results after averaging across nodules for each subject.
First, we can look at the distribution of survival length (for those who died)

Then we can look at the performances of the 3 models:

Model for predicting death without any timeframe
Number of subjects which died: 47
Number of subject for training: 130
Number of subject for testing: 33
Model performance:

ROC AUC Score: 0.6944444444444444
Brier score: 0.23960448548378224
Average precision: 0.4444444444444444
Average Recall: 0.4444444444444444
Accuracy Score: 0.696969696969697
AUC-PR score: 0.5202020202020202

Model for predicting death within 1 year
Number of subjects that died within 1 year: 10
Number of subjects that died within 1 year (train): 9
Number of subjects that died within 1 year (test): 1
Model performance on the deadline of 1 year

ROC AUC Score: 0.34375
Brier score: 0.0782352770988001
Average precision: 0.0
Average Recall: 0.0
Accuracy Score: 0.8787878787878788
AUC-PR score: 0.015151515151515152

Model for predicting death within 3 year
Number of subjects that died within 3 year (train): 26
Number of subjects that died within 3 year (test): 7
Model performance on the deadline of 3 year

ROC AUC Score: 0.6758241758241759
Brier score: 0.21007829077560772
Average precision: 0.4
Average Recall: 0.5714285714285714
Accuracy Score: 0.7272727272727273
AUC-PR score: 0.5311688311688312

This is done without hyper-parameter fine-tuning.
Which model should be chosen for the study ?

I did some parameter finetuning using Bayesian optimisation and I was very surprised to obtain decreasing model performance. Here is an explication of why that is: Empirically has been observed to perform poorly on high dimensional objective functions (i.e. higher than 20 dimensions)

I also explored GridSearch which was inconclusive as well. Future explorations could be to remove some of the features. Is this something we want to be doing ?
Also considering the model results above, it seems that for the purpose of our study, selecting the model for prediction of death within 3 years makes the most sense.

I added the three following steps:

train/test split is done using the sites (test: site starting with "V" ; train: the rest)
feature selection based on variance thresholding, inter-feature correlation and correlation with the target features.
Bayesian hyperparameter optimisation

The file output is the following:

Feature data shape: (163, 139)
Target data shape: (163, 2)
Number of subjects which died: 47

Number of subject for training: 136
Number of subject for testing: 27

Model performance without any occurence deadline
ROC AUC Score:  0.6973684210526316
Brier score: 0.21620211765857958
Average precision: 0.6
Average Recall: 0.375
Accuracy Score:  0.7407407407407407
AUC-PR score: 0.5800925925925926

Number of subjects that died within 1 year: 10
Number of subjects that died within 1 year (train): 7
Number of subjects that died within 1 year (test): 3
Model performance on the deadline of 1 year
ROC AUC Score: 0.4861111111111111
Brier score: 0.08916433409898136
Average precision: 1.0
Average Recall: 0.3333333333333333
Accuracy Score: 0.9259259259259259
AUC-PR score: 0.7037037037037037

Number of subjects that died within 3 year: 33

Number of subjects that died within 3 year (train): 27
Number of subjects that died within 3 year (test): 6
Model performance on the deadline of 3 year
ROC AUC Score: 0.48412698412698413
Brier score: 0.21957430331287112
Average precision: 0.0
Average Recall: 0.0
Accuracy Score: 0.7407407407407407
AUC-PR score: 0.1111111111111111

Initial number of features: 28
Number of subject for training: 136
Number of subject for testing: 27

Model performance without any occurence deadline
ROC AUC Score:  0.736842105263158
Brier score: 0.2419225098071141
Average precision: 0.4
Average Recall: 0.25
Accuracy Score:  0.6666666666666666
AUC-PR score: 0.4361111111111111

Number of features after variance thresholding: 26
Number of features removed by variance thresholding: 2

Model performance after variance thresholding
ROC AUC Score:  0.6973684210526316
Brier score: 0.26179091772987256
Average precision: 0.5
Average Recall: 0.375
Accuracy Score:  0.7037037037037037
AUC-PR score: 0.5300925925925926

Number of features after correlation thresholding: 22
Number of features removed by correlation thresholding: 4

Model performance after feature selection based on correlation
ROC AUC Score:  0.5789473684210527
Brier score: 0.2260969131269171
Average precision: 1.0
Average Recall: 0.25
Accuracy Score:  0.7777777777777778
AUC-PR score: 0.7361111111111112

Number of features after correlation with target thresholding: 16
Number of features removed by correlation with target thresholding: 6

Model performance after feature selection based on correlation with target
ROC AUC Score:  0.7039473684210525
Brier score: 0.27357019660843984
Average precision: 0.2857142857142857
Average Recall: 0.25
Accuracy Score:  0.5925925925925926
AUC-PR score: 0.37896825396825395

Model parameters after hyperparameter tuning:
OrderedDict([('colsample_bytree', 0.01), ('gamma', 0.479917457783544), ('learning_rate', 0.5), ('max_depth', 10), ('min_child_weight', 1), ('n_estimators', 50), ('reg_alpha', 0.4265448487839457), ('reg_lambda', 1.0), ('subsample', 0.8001997191867042)])

Model performance after hyperparameter tuning
ROC AUC Score:  0.6973684210526316
Brier score: 0.24018803547750853
Average precision: 0.5
Average Recall: 0.625
Accuracy Score:  0.7037037037037037
AUC-PR score: 0.6180555555555556

After changing the test site (we now select site 'L' for testing), we obtain the following output:

Feature data shape: (163, 139)
Target data shape: (163, 2)
Number of subjects which died: 47

Number of subject for training: 142
Number of subject for testing: 21

Model performance without any occurence deadline
ROC AUC Score:  0.7777777777777779
Brier score: 0.21704406181336877
Average precision: 0.875
Average Recall: 0.5833333333333334
Accuracy Score:  0.7142857142857143
AUC-PR score: 0.8482142857142857

Number of subjects that died within 1 year: 10
Number of subjects that died within 1 year (train): 8
Number of subjects that died within 1 year (test): 2
Model performance on the deadline of 1 year
ROC AUC Score: 0.5526315789473685
Brier score: 0.0905243453278062
Average precision: 0.0
Average Recall: 0.0
Accuracy Score: 0.9047619047619048
AUC-PR score: 0.5476190476190477

Number of subjects that died within 3 year: 33

Number of subjects that died within 3 year (train): 26
Number of subjects that died within 3 year (test): 7
Model performance on the deadline of 3 year
ROC AUC Score: 0.5816326530612245
Brier score: 0.2912115012240408
Average precision: 0.0
Average Recall: 0.0
Accuracy Score: 0.6190476190476191
AUC-PR score: 0.16666666666666666

Initial number of features: 28
Number of subject for training: 142
Number of subject for testing: 21

Model performance without any occurence deadline (no deadline)
ROC AUC Score:  0.7037037037037037
Brier score: 0.248025119329143
Average precision: 0.6923076923076923
Average Recall: 0.75
Accuracy Score:  0.6666666666666666
AUC-PR score: 0.7925824175824175

Number of features after variance thresholding: 26
Number of features removed by variance thresholding: 2

Model performance after variance thresholding (no deadline)
ROC AUC Score:  0.7222222222222223
Brier score: 0.2345131046589517
Average precision: 0.6666666666666666
Average Recall: 0.6666666666666666
Accuracy Score:  0.6190476190476191
AUC-PR score: 0.7619047619047619

Number of features after correlation thresholding: 22
Number of features removed by correlation thresholding: 4

Model performance after feature selection based on correlation (no deadline)
ROC AUC Score:  0.7314814814814815
Brier score: 0.233313720673983
Average precision: 0.8181818181818182
Average Recall: 0.75
Accuracy Score:  0.7619047619047619
AUC-PR score: 0.8555194805194806

Number of features after correlation with target thresholding: 14
Number of features removed by correlation with target thresholding: 8

Final features of the model:
['sexe', 'BMI', 'score_charlson', 'tabac_sevre', 'dose_tot', 'BED_10', 'INTENSITY-BASED_MeanIntensity', 'INTENSITY-BASED_IntensitySkewness', 'INTENSITY-BASED_IntensityKurtosis', 'INTENSITY-BASED_AreaUnderCurveCIVH', 'INTENSITY-BASED_RootMeanSquareIntensity', 'INTENSITY-HISTOGRAM_IntensityHistogramMean', 'INTENSITY-HISTOGRAM_IntensityHistogramVariance', 'NGTDM_Strength']

Model performance after feature selection based on correlation with target (no deadline)
ROC AUC Score:  0.8148148148148148
Brier score: 0.17676625147768166
Average precision: 0.7333333333333333
Average Recall: 0.9166666666666666
Accuracy Score:  0.7619047619047619
AUC-PR score: 0.8488095238095238
Confusion matrix:
[[ 5  4]
 [ 1 11]]

Model performance with the hyperparameter found with Bayesian Optimisation  (no deadline)
ROC AUC Score:  0.8611111111111112
Brier score: 0.18067224640382637
Average precision: 1.0
Average Recall: 0.6666666666666666
Accuracy Score:  0.8095238095238095
AUC-PR score: 0.9285714285714286

Number of subjects that died within 1 year: 10
Number of subjects that died within 1 year (train): 8
Number of subjects that died within 1 year (test): 2

Model performance with fewer features with 1 year deadline
ROC AUC Score:  0.2894736842105263
Brier score: 0.10999299786953731
Average precision: 0.0
Average Recall: 0.0
Accuracy Score:  0.9047619047619048
AUC-PR score: 0.5476190476190477
Confusion matrix:
[[19  0]
 [ 2  0]]

Model performance with the hyperparameter found with Bayesian Optimisation (fewer features with 1 year deadline)
ROC AUC Score:  0.5921052631578947
Brier score: 0.08684877219570905
Average precision: 0.0
Average Recall: 0.0
Accuracy Score:  0.9047619047619048
AUC-PR score: 0.5476190476190477
Confusion matrix:
[[19  0]
 [ 2  0]]

My recommendation would be to go for the model with fewer features, optimized parameters and no deadline. It seems to be functioning rather efficiently.
On the other hand, the model with fewer features, optimised parameters and the 1 year deadline seems to miss the only 2 positive cases (which a model which always says 0 would be able to do).

The last model trained predicts 3 year survival, it has fewer features and the hyperparameters have been optimised.
These are the results of the model:
Model performance with the hyperparameter found with Bayesian Optimisation (fewer features with 3 year deadline)
ROC AUC Score:  0.7346938775510204
Brier score: 0.18810136954732778
Average precision: 0.5
Average Recall: 0.14285714285714285
Accuracy Score:  0.6666666666666666
AUC-PR score: 0.4642857142857143
Confusion matrix:
TN: 13
FP: 1
FN: 6
TP: 1

I wrote a script to only show the output of the final model chosen.
This is the output of the script :

Feature data shape: (163, 139)
Target data shape: (163, 2)
Number of subjects which died: 47

Number of subject for training: 142
Number of subject for testing: 21

Number of features: 14
Selected features: Index(['sexe', 'BMI', 'score_charlson', 'tabac_sevre', 'dose_tot', 'BED_10',
       'INTENSITY-BASED_MeanIntensity', 'INTENSITY-BASED_IntensitySkewness',
       'INTENSITY-BASED_IntensityKurtosis',
       'INTENSITY-BASED_AreaUnderCurveCIVH',
       'INTENSITY-BASED_RootMeanSquareIntensity',
       'INTENSITY-HISTOGRAM_IntensityHistogramMean',
       'INTENSITY-HISTOGRAM_IntensityHistogramVariance', 'NGTDM_Strength'],
      dtype='object')

Number of subjects that died within 3 year: 33
Number of subjects that died within 3 year (train): 26
Number of subjects that died within 3 year (test): 7

------------------------------------
Training the model to predict survival within 3 years with only 14 features
------------------------------------

Final model performance on the training set
ROC AUC Score:  0.8093501326259946
Brier score: 0.1133619189415632
Average precision: 0.75
Average Recall: 0.34615384615384615
Accuracy Score:  0.8591549295774648
AUC-PR score: 0.6079360780065005
Confusion matrix:
TN: 113
FP: 3
FN: 17
TP: 9

Final model performance on the testing set
ROC AUC Score:  0.7346938775510204
Brier score: 0.18810136954732778
Average precision: 0.5
Average Recall: 0.14285714285714285
Accuracy Score:  0.6666666666666666
AUC-PR score: 0.4642857142857143
Confusion matrix:
TN: 13
FP: 1
FN: 6
TP: 1

With the following figures as well:

Display of feature importance:

Updated above graphs with new feature names:

I added calibration to the training of the final_survival_model.py.
Here is the output:
Feature data shape: (163, 140)
Target data shape: (163, 2)
Number of subjects which died: 47

Number of subject for training: 142
Number of subject for testing: 21

Number of features: 14
Selected features: Index(['sexe', 'BMI', 'score_charlson', 'tabac_sevre', 'dose_tot', 'BED_10',
       'INTENSITY-BASED_MeanIntensity', 'INTENSITY-BASED_IntensitySkewness',
       'INTENSITY-BASED_IntensityKurtosis',
       'INTENSITY-BASED_AreaUnderCurveCIVH',
       'INTENSITY-BASED_RootMeanSquareIntensity',
       'INTENSITY-HISTOGRAM_IntensityHistogramMean',
       'INTENSITY-HISTOGRAM_IntensityHistogramVariance', 'NGTDM_Strength'],
      dtype='object')

Number of subjects that died within 3 year: 33
Number of subjects that died within 3 year (train): 26
Number of subjects that died within 3 year (test): 7

------------------------------------
Training the model to predict survival within 3 years with only 14 features
------------------------------------

Final model performance on the training set
ROC AUC Score:  0.8093501326259946
Brier score: 0.1133619189415632
Average precision: 0.75
Average Recall: 0.34615384615384615
Accuracy Score:  0.8591549295774648
AUC-PR score: 0.6079360780065005
Confusion matrix:
TN: 113
FP: 3
FN: 17
TP: 9

Final model performance on the testing set
ROC AUC Score:  0.7346938775510204
Brier score: 0.18810136954732778
Average precision: 0.5
Average Recall: 0.14285714285714285
Accuracy Score:  0.6666666666666666
AUC-PR score: 0.4642857142857143
Confusion matrix:
TN: 13
FP: 1
FN: 6
TP: 1

Final model performance on the testing set after calibration
ROC AUC Score:  0.8010204081632654
Brier score: 0.16524398564180856
Average precision: 1.0
Average Recall: 0.14285714285714285
Accuracy Score:  0.7142857142857143
AUC-PR score: 0.7142857142857142
Confusion matrix:
TN: 14
FP: 0
FN: 6
TP: 1

Here are the associated figures of the training and testing of the model:


Added logic for handling 'about:blank' to download()

It could be placed somewhere else perhaps, if you want, but this is where made sense to me.
Basically I've been dealing with some pages that are peppered with iframes that start out pointing to 'about:blank' and it's breaking things.

Thanks for this contribution! Do you happen to have the url for one of those page so I could test this on my end?

@hbregalad I'm not too sure why this was closed, but I just wanted to let you know that I have updated TkinterWeb to add support for about:blank pages. I modified your code a bit to add more general support for about: pages (making it easier to add new ones if needed). Simply update TkinterWeb and your issues with about:blank frames should be resolved. As always, feel free to let me know if you have any other suggestions or if you notice any bugs!

Thanks!
On Tue, Apr 12, 2022, 14:02 Andereoo @.***> wrote:

@hbregalad https://github.com/hbregalad I'm not too sure why this was
closed, but I just wanted to let you know that I have updated TkinterWeb to
add support for about:blank pages. I modified your code a bit to add more
general support for about: pages (making it easier to add new ones if
needed). Simply update TkinterWeb and your issues with about:blank frames
should be resolved. As always, feel free to let me know if you have any
other suggestions or if you notice any bugs!
—
Reply to this email directly, view it on GitHub
https://github.com/Andereoo/TkinterWeb/pull/34#issuecomment-1097030083,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACDO23GXUNFEYKGTNR6AZXDVEW3EVANCNFSM5SUG4RUA
.
You are receiving this because you were mentioned.Message ID:
@.***>


/prepare.sh cannot create as Directory is nonexistent

Please paste the output of the following command here: sudo edit-chroot -all

name: kali-rolling
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/kali-rolling...
crouton: version 1-20181001133934~master:38012fdf
release: kali-rolling
architecture: amd64
targets: core,audio,xfce
host: version 11151.11.0 (Official Build) dev-channel eve
kernel: Linux localhost 4.4.159-15334-g388c74685442 #1 SMP PREEMPT Wed Oct 24 02:07:35 PDT 2018 x86_64 GNU/Linux
freon: yes
Unmounting /mnt/stateful_partition/crouton/chroots/kali-rolling...
Please describe your issue:
I get the following error:
Compiling CRAS (native)...
Installing CRAS...
/prepare.sh: 1166: /prepare.sh: cannot create /usr/share/alsa/alsa.conf.d/10-cras.conf: Directory nonexistent
Failed to complete chroot setup.
Unmounting /mnt/stateful_partition/crouton/chroots/kali-rolling...
If known, describe the steps to reproduce the issue:
I just ran:
sudo sh -e ~/Downloads/crouton -r kali-rolling -u -t core,audio,xfc

I have tried other targets, even just core, and this keeps coming up.  Can you assist?  Thank you!

Me too.
$ sudo edit-chroot -all
name: kali
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/kali...
crouton: version 1-20181001133934~master:38012fdf
release: kali-rolling
architecture: amd64
targets: xiwi,cli-extra,keyboard,xfce,extension
host: version 11021.56.0 (Official Build) stable-channel peppy
kernel: Linux localhost 3.8.11 #1 SMP Mon Oct 22 23:38:25 PDT 2018 x86_64 GNU/Linux
freon: yes
Unmounting /mnt/stateful_partition/crouton/chroots/kali...

I did
sudo sh ~/Downloads/crouton -t xiwi,cli-extra,keyboard,xfce,extension -n kali -r kali-rolling

and got
...
Installing CRAS...
/prepare.sh: 1166: /prepare.sh: cannot create /usr/share/alsa/alsa.conf.d/10-cras.conf: Directory nonexistent
Failed to complete chroot setup.

I even made the directory, but I think it's in the chroot, not the chromeOS.  Not sure where to go from here...

I even made the directory, but I think it's in the chroot, not the chromeOS. Not sure where to go from here...

Could you try making it in /mnt/stateful_partition/crouton/chroots/kali-rolling/usr/share/alsa/ ?
This seems to have worked for me for debian buster:
sudo mkdir /mnt/stateful_partition/crouton/chroots/buster/usr/share/alsa/alsa.conf.d

@SamuelClyde that did it!  I can't thank you enough.  I am running kali-rolling in a KDE.  Thanks again!

Looks like the alsa configuration location has changed in Buster (and thus kali):
$ diff /usr/share/alsa/alsa.conf.old /usr/share/alsa/alsa.conf.new
11,17c11
<                       {
<                               @func concat
<                               strings [
<                                       { @func datadir }
<                                       "/alsa.conf.d/"
<                               ]
<                       }
---
>                       "/etc/alsa/conf.d"

That suggests two things:

Your workaround makes the installer finish, but I suspect audio won't work.
On systems with no /usr/share/alsa/alsa.conf.d, we should be writing the cras config to /etc/alsa/conf.d

I can confirm I am getting this on the latest ChromeOS running the above command for crouton (latest)
Installing CRAS...
/prepare.sh: 1166: /prepare.sh: cannot create /usr/share/alsa/alsa.conf.d/10-cras.conf: Directory nonexistent
Failed to complete chroot setup.
Unmounting /mnt/stateful_partition/crouton/chroots/kali-rolling...
chronos@localhost / $

Trying to mkdir with sudo says Cannot create directory no such file or directory exists.

Same problem as OP, adding the directory manually solved it
@carsenk You made sure to change 'buster' to 'kali-rolling' in the mkdir command?
For kali-rolling it would be this instead:
sudo mkdir /mnt/stateful_partition/crouton/chroots/kali-rolling/usr/share/alsa/alsa.conf.d
                                                       🡑

Thanks everyone.  I made the directory and voila, no problems.

That is odd. How did you test sound? I usually just do aplay /usr/share/sounds/alsa/Front_Left.wav.

Ah, my bad. I tried playing a video on Firefox, and Battle for Wesnoth, neither of which worked - but you're right, aplay does. I'll investigate those.
Thank you.

I have this issue (fails to install)- however when I manually add the directory I get the error 'UID 1000 not found in Kali" (named chroot since I have a couple)

I tried, and then I tried to run it again.

I'm having the same issue as knightlycat. I'm on a Samsung Chromebook3
The following packages were automatically installed and are no longer required:
libasound2-dev:i386 libc6-dev:i386 libspeex-dev:i386 libspeex1:i386 libspeexdsp-dev:i386 linux-libc-dev:i386
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Compiling CRAS (native)...
Installing CRAS...
/prepare.sh: 1166: /prepare.sh: cannot create /usr/share/alsa/alsa.conf.d/10-cras.conf: Directory nonexistent
Failed to complete chroot setup.
Unmounting /mnt/stateful_partition/crouton/chroots/kali-rolling...
Any ideas on how to fix?

Installed kali linux finally!
After power wash and re-entering developer mode, was able to
sudo mkdir /mnt/stateful_partition/crouton/chroots/kali-rolling/usr/share/alsa/alsa.conf.d
Then entered:
sudo sh -e ~/Downloads/crouton -r kali-rolling -t xfce

How? I had to go back and make all the directories from kali-rolling and up, and after trying to execute the command, It wouldn't let me because there were things already in it. power washing it..?
I'll try to update it when I finish making it, though I feel like there will be the same consequence..


run notebook on Azure Databricks get error

Description
als_movie_o16n.ipynb on databricks  I get error when execute codes below:
client = get_client_from_cli_profile(azure.mgmt.cosmosdb.CosmosDB,                                     subscription_id=subscription_id)

Error Stack:
CLIError                                  Traceback (most recent call last)
 in ()
----> 1 client = get_client_from_cli_profile(azure.mgmt.cosmosdb.CosmosDB)
2
3 async_cosmosdb_create = client.database_accounts.create_or_update(
4     resource_group,
5     account_name,
/databricks/python/lib/python3.5/site-packages/azure/common/client_factory.py in get_client_from_cli_profile(client_class, **kwargs)
77         resource, _ = _client_resource(client_class, cloud)
78         credentials, subscription_id, tenant_id = get_azure_cli_credentials(resource=resource,
---> 79                                                                             with_tenant=True)
80         parameters.update({
81             'credentials': kwargs.get('credentials', credentials),
/databricks/python/lib/python3.5/site-packages/azure/common/credentials.py in get_azure_cli_credentials(resource, with_tenant)
46     """
47     profile = get_cli_profile()
---> 48     cred, subscription_id, tenant_id = profile.get_login_credentials(resource=resource)
49     if with_tenant:
50         return cred, subscription_id, tenant_id
/databricks/python/lib/python3.5/site-packages/azure/cli/core/_profile.py in get_login_credentials(self, resource, subscription_id, aux_subscriptions)
488
489     def get_login_credentials(self, resource=None, subscription_id=None, aux_subscriptions=None):
--> 490         account = self.get_subscription(subscription_id)
491         user_type = account[_USER_ENTITY][_USER_TYPE]
492         username_or_sp_id = account[_USER_ENTITY][_USER_NAME]
/databricks/python/lib/python3.5/site-packages/azure/cli/core/_profile.py in get_subscription(self, subscription)
450         subscriptions = self.load_cached_subscriptions()
451         if not subscriptions:
--> 452             raise CLIError("Please run 'az login' to setup account.")
453
454         result = [x for x in subscriptions if (
CLIError: Please run 'az login' to setup account.

In which platform does it happen?

Azure Databricks.

How do we replicate the issue?
Other Comments
@jdhuntington @sverrejoh @bgianfo

Looks like the error shows that you have not authenticate your workspace? See https://docs.microsoft.com/en-us/python/azure/python-sdk-azure-authenticate?view=azure-python#mgmt-auth-cli if it helps.

We're investigating this. For now you can manually log in on the head node of Databricks by adding a cell with the following code:
%sh
pip install azure-cli
az login

This issue is caused by a new method of authentication within the azureml-sdk. As of version 1.0.10 of the sdk, it uses a different authentication method. So, the workspace.create() call authenticates for the azureml-sdk, but not the other azure modules. The scripts/prepare_databricks_for_o16n.sh script pins the version of the azureml-sdk to version 1.0.8 for this reason.
Solutions:

Update the setup.md to use the pinned version of the azureml-sdk so that you don't have to log in twice.
Update the notebook to install azure-cli on the head node.

Thoughts on which approach?

FYI, I was hit by this today as well. Seems pretty important to resolve, since anyone will be blocked running this notebook. Another solution to consider (that worked for me): create an AAD registered app, grant it access to my newly created AML workspace, then instantiate a ServicePrincipalCredentials object in the notebook and use it to authenticate. I used the portal for much of this, probably could/should be converted to az CLI equivalents. My notebook code looks like:
from azure.common.credentials import ServicePrincipalCredentials
credentials = ServicePrincipalCredentials(
client_id = app_id,
secret = app_key,
tenant = tenant_id
)
client = get_client_from_cli_profile(azure.mgmt.cosmosdb.CosmosDB, credentials=credentials, subscription_id=subscription_id)

We're investigating this. For now you can manually log in on the head node of Databricks by adding a cell with the following code:
%sh
pip install azure-cli
az login

Thanks

This issue is caused by a new method of authentication within the azureml-sdk. As of version 1.0.10 of the sdk, it uses a different authentication method. So, the workspace.create() call authenticates for the azureml-sdk, but not the other azure modules. The scripts/prepare_databricks_for_o16n.sh script pins the version of the azureml-sdk to version 1.0.8 for this reason.
Solutions:

Update the setup.md to use the pinned version of the azureml-sdk so that you don't have to log in twice.
Update the notebook to install azure-cli on the head node.

Thoughts on which approach?

Thanks , that  worked


[Bug]: Python schema generated types cannot be pickled

What happened?
The NamedTuple types we generate in apache_beam.typehints.schemas confound pickle libraries. We work around this in many places (e.g. GeneratedClassRowTypeConstraint #22679). We should see if we can find a way to make these types picklable, and clean up the workarounds.
Making the types work with cloudpickle should be the priority.
Issue Priority
Priority: 2
Issue Component
Component: sdk-py-core

Have we tried pickling these types with CloudPickle?

This is technically still an issue since dill can't pickle the types.


"scroll" and anchor links within an iFrame on iOS

Hello there,
I'm currently working on a project that will be rendered inside an iFrame.
I've decided to use velocity to make scroll animation when it comes to anchor links within my pages.
It works perfectly in iFrames when using Chrome for Android and for PC. But when it comes to iOS, it just won't work at all. I've been working on two iPad to test my project, using iOS8 and iOS9.
You can use the following codePen to see a simple reproduction of the bug :
http://codepen.io/Agentrouble/pen/ONWpKB
As you can see, trying to click on a link will result in the whole iFrame bugging out and flickering.
It's worth mentionning, that my code is working out perfectly out of an iFrame.  I've been looking for an alternative to workaround this issue, and it is not possible for me to avoid iFrames on this one.
Have a good day

Sadly I'm going to make a very unhelpful comment here - iFrames on iOS are some of the most annoying things around - I've had quite a few projects in the past that have had to use them, and the end result is always work-arounds and sidestepping the bug that is Safari - there's quite a lot of helpful posts on StackOverflow - but generally you need to treat an iFrame on iOS as a black box that doesn't behave properly - don't try to scroll it - scroll outside or inside, but not the window within the iFrame itself :-/

.Yeah I'm realising the hard way that iFrame are really tough to deal with.
Fortunately, I found a workaround just now by testing out different things. It works both for iOS8 and iOS9.
The codepen http://codepen.io/Agentrouble/pen/ONWpKB contains what is necessary.
The "container" option must be filled with the direct parent of our anchor elements.
This container must have a defined height, width, overflow-x, overflow-y and a position (like it's specified in the doc).
I'm leaving this open up until I'm sure everything is working out perfectly.

Hopefully this will help someone else - an iOS workaround for something relating to iFrames ;-)


High battery usage

The CPU is constantly running even when the app is in the background leading to battery drain.

Seems to have gone away on its own


change name of input field to "handleOrEmail"

Codeforces recently changed the name of a input field of the login page from
<input id="handle" style="width: 15em;" name="handle" value=""/>

to:
<input id="handleOrEmail" style="width: 15em;" name="handleOrEmail" value=""/>

Therefore it is now impossible to submit using the plugin.
This pull-request changes the parameter in the curl call accordingly and fixes the problem.

Thank you for maintaining this! I haven't been competing on CF, so it is great that you send such PRs.


Negotiate protocol versioning and ConnectionID split

Backport the Negotiate versioning and ConnectionID split

[x] SignalR Negotiate protocol versioning https://github.com/aspnet/AspNetCore/pull/13389
[x] SignalR ConnectionToken/ConnectionAddress feature https://github.com/aspnet/AspNetCore/pull/13773
[x] Add support for negotiateVersion query string parameter https://github.com/aspnet/AspNetCore/pull/13880
[x] [TS] Add support for negotiateVersion and connectionToken https://github.com/aspnet/AspNetCore/pull/14157
[x] C# and Java client negotiateVersion cleanup https://github.com/aspnet/AspNetCore/pull/14196

Manual Testing:

[x] 3.0 JS client + 3.1 server
[x] 3.0 Java client + 3.1 server
[x] 3.0 C# client + 3.1 server
[x] 3.1 JS client + 3.0 server
[x] 3.1 Java client + 3.0 server
[x] 3.1 C# client + 3.0 server
[x] 2.1 JS client + 3.1 server
[x] 2.1 C# client + 3.1 server
[x] 2.2 JS client + 3.1 server
[x] 2.2 Java client + 3.1 server
[x] 2.2 C# client + 3.1 server
[x] 3.1 client + 3.1 server + SignalR Service
[x] 3.0 client + 3.1 server + SignalR Service

This feature work is approved for 3.1 (internal tracking item: https://devdiv.visualstudio.com/DevDiv/_workitems/edit/984226/) and can be merged (when all the usual reviews/builds/etc. are complete).

Ready for review. I've got the core scenarios tested and I'll work on completing the rest.

@aspnet-hello triage https://dev.azure.com/dnceng/public/_build/results?buildId=372086&view=logs

This comment was made automatically. If there is a problem contact<EMAIL_ADDRESS>I've triaged the above build. I've created/commented on the following issue(s)
https://github.com/aspnet/AspNetCore-Internal/issues/3173

@aspnet-hello triage https://dev.azure.com/dnceng/public/_build/results?buildId=372087

This comment was made automatically. If there is a problem contact<EMAIL_ADDRESS>I've triaged the above build. I've created/commented on the following issue(s)
https://github.com/aspnet/AspNetCore-Internal/issues/3184


Hotword example Language

Hello,
is there a way to change the language in the hotword example?

Did you try --lang [language] behind the command? So for example: --lang ja-JP for Japanese and --lang de-DE for German.

@Simonx22 the hotword code is not structured to define the language. did you open the hotword.py file?

@Enzoinventor oh you're right. I thought it has that too like textinput.py does.  I heard that it's possible to change settings in the Google Home app, but I'm not sure how.

@Simonx22
You can change the language/devicename in the App, but without any effect :/

There was an issue where the hotword sample didn't set the client_type correctly during device registration.
We published a new release:
https://pypi.python.org/pypi/google-assistant-sdk/0.4.1
Can you give it another try?

@proppy yes, it worked for me.
ps: grpc takes about one hour for building on my single board PC (Orange Pi Zero)

@pratesbh there should be arm7 wheels for the 1.7.0 version:
https://pypi.python.org/pypi/grpcio/1.7.0

The hotword example now works with other languages, but I still have to pronounce "Ok Google" in english to trigger it

I don't have access to the google assistant app since i only have an ios device and the google assistant app is not available in the Swiss ios app store. Is it possible to change the language of the hotword example without the app?

@sergio-daniels no and in my opinion here they were not very correct. they cut out several users. (please solve)

For the Assistant SDK Library, you will need to change language using the app. If you are interested in programmatically changing the language in the library, please refer to #150.
For the Assistant Service, you can programmatically change the language in the API.
I'll close this issue as the primary question has been answered.

hello everyone I followed step by step your guide but I can not see the device on the app assistant, I ran:
(env) pi@raspberrypi:~ $ googlesamples-assistant-devicetool list --device
Device Instance Id: *****************
Nickname: Assistant SDK light
Model: Home
(env) pi@raspberrypi:~ $ googlesamples-assistant-devicetool list --model
Device Model Id: Home
Project Id: composite-****-*****
Device Type: action.devices.types.LIGHT
Trait action.devices.traits.OnOff
I have in my phone android 6.0.1 and on assistant language settings I only see the phone between the devices.
How can I solve?
Thanks to everyone in advance

Have you made sure the device and your phone are on the same Google account? Can you check again?

yes, I certainly used the same account.
a user on a forum wrote that:
This is because Google has limited the developer package that is available for installing on the Raspberry pi.
it's true?

@proppy ,
I tried the new release:
https://pypi.python.org/pypi/google-assistant-sdk/0.4.3
I registered my device and  changed the language to Japanese in the Google Assistant app.
But the hotword is still talking in english, nothing changed!
I tried the AIY assistant_library_demo.py too, the results were same, Japanese didn't work!
However, the pushtotalk can talk in Japanese with the parameter --lang ja-Jp.

@tei-chino the 「OK Google」 hotword model is only available in en-US for now. But you should be able to set the conversation language in Japanese by updating the language in the settings of Google Assistant App for the device your registered.

@proppy , I have set the device's language to Japanese using the Google Assistant App, but  the Assistant  still talks english.
It seems that the App language settings had no any affects.

@tei-chino can you double check that you switched the language for the right device.
I was able to successfully switch the assistant from english to japanese while it was running:
tmp 🍡  env/bin/googlesamples-assistant-hotword --device_model_id my-model --project_id my-project-id
device_model_id: my-model
device_id: my-device-id

https://embeddedassistant.googleapis.com/v1alpha2/projects/my-project-id/devices/my-device-id 200
ON_MUTED_CHANGED:
  {'is_muted': False}
ON_START_FINISHED

ON_CONVERSATION_TURN_STARTED
ON_END_OF_UTTERANCE
ON_RECOGNIZING_SPEECH_FINISHED:
  {'text': 'what time is it'}
ON_RESPONDING_STARTED:
  {'is_error_response': False}
ON_RESPONDING_FINISHED
ON_CONVERSATION_TURN_FINISHED:
  {'with_follow_on_turn': False}

// - Go to the Assistant Settings
// - Switch the language to Japanese for the device with "device-model-id"

ON_CONVERSATION_TURN_STARTED
ON_END_OF_UTTERANCE
ON_RECOGNIZING_SPEECH_FINISHED:
  {'text': '今何時ですか'}
ON_RESPONDING_STARTED:
  {'is_error_response': False}
ON_RESPONDING_FINISHED
ON_CONVERSATION_TURN_FINISHED:
  {'with_follow_on_turn': False}

Hope that helps.

@proppy , thanks for your advise.
I followed your instruction to switch the language from English to Japanese while running, but it still didn't work.
Maybe there are some things wrong with me, but I have no any ideas.

I apologize if I ask for your help again but I can not solve the problem of making the device appear on the app assistant.
I formatted the sd installed again noobs desktop and made all the updates, I followed the official guide https://developers.google.com/assistant/sdk/guides/library/python/
by wire and by sign and I created a new json key to be sure not to create conflicts, I then enabled the bee copied the code on the raspberry and I registered my device, I ran the hotword file without problems and I got the id that I entered in googlesamples-assistant-devicetool register-device --client-type LIBRARY
--model my-model --device my-device-id
the model and the device appear correctly if I interrupt the server but on the assistant app no device seen besides the phone.
Any suggestions?
thank you all in advance

@Fleker leker
gentlemen, I discovered the problem
for those who live in Italy, you have to change the language in English and set it in English, just by opening the app assistant and going to settings you can view the registered devices.
However, the problem remains that the Italian language is not yet available.
I will open a new report. @

@tei-chino
Hi, I can give you a suggestion:
make sure you have updated the library to the version: https: //pypi.python.org/pypi/google-assistant-sdk/0.4.3
run in the terminal:
source env / bin / activate
googlesamples-assistant-devicetool list --model
check that you do not have too many templates at most one by one with:
googlesamples-assistant-devicetool delete --model MODEL_ID
also run:
googlesamples-assistant-devicetool list --device
check that you do not have too many devices at most one by one with:
googlesamples-assistant-devicetool delete --device DEVICE_ID
and also from the app assistant it eliminates all the devices you see recorded.
Then register a new model and then execute:
googlesamples-assistant-devicetool register-device --client-type LIBRARY
--model my-model --device my-device-id
the device id you get it by running the file hotword.py as it showed proppy in the picture.
Let me know.

@aandroide, Thanks for your valuable advice. I followed your suggestion, tried the assistant again.
Please let me tell you the results.
a. Deleted all models and devices in my project.
b. Registered a new model  as SDK readme:
googlesamples-assistant-devicetool register-model --manufacturer "Assistant SDK developer" - product-name "Assistant SDK light" --type LIGHT --model test-model-1111
c. Registered a new device as your suggestion: (I notice that you set the  client_type = LIBRARY)
googlesamples-assistant-devicetool register-device --client-type LIBRARY --model test-model-1111 --device test-device-1111.
d. The new device showed on my Assistant App. I set the language to Japanese.
e. I run hotword using the new device:
googlesamples-assistant-hotword --device-model-id test-model-1111 -project_id my-project-4116-196212
f. I found another new device was shown on my Assistant App. I check it using "googlesamples-assistant-devicetool list --device". the model of the 2nd device is same with the 1st one, and it has been set to Japanese although I never do any things.
g. During first seconds,  the hotword didn't reacted my dialogue, then it began to recognize my Japanese as  proppy did, though recongnizing is not well done everytime:
ON_CONVERSATION_TURN_STARTED
ON_END_OF_UTTERANCE
ON_RECOGNIZING_SPEECH_FINISHED:
{'text': 'こんにちは'}
ON_CONVERSATION_TURN_TIMEOUT
However, no any replies ! The Assistant understood what I said, but didn't answer me.
Ahthough, I could not fix the problem at all . Anyway, I did  some progress.
By the way, I notice that the client type is set to  LIBRARY in  your suggestion, , however I found that the AIY project sample code and SDK readme set to SDK_SERVICE. Maybe, this caused the problem of Japanese.

@tei-chino
@proppy
I ask the experts, but sdk-service is only for pushbutton.py that uses api grpc
we await their confirmation

@aandroide
The following is from AIY-projects-python device-helps.py
`    device_id = "%s-%s" % (model_id, uuid.uuid4())
# We can hardcode client_type as SDK_SERVICE, because the Assistant Library
# creates its own device_id.

payload = {
        "id": device_id,
        "model_id": model_id,
        "client_type": "SDK_SERVICE",
}`

By the way, I have tried the AIY-projects-python, I can set the language to Japanese, but no any effects.

@aandroide
@proppy
I checked "My Actions" in my Assitant App, I found the logs of conversation with the Assistant.
It is very curious that my voice such as "今何時ですか？ (What time is it now?)" has been recognized on the RPi terminal, but  all of them recorded in my actions were "unknown voice commands".
These can explain why the Assistant didn't reply my voice in Japanese. The Assistant can recognize the voice Japanese words only, but could not understant the meanings. Why?
By the way, I got only one reply from the Assistant in Japanese. When I saiy "Ok Google, こんにちは (hello)", the Assistant talked a piece of news to me in Japanese. But when I tried again, it didn't work any more.

Hi everybody,
I am running hotword.py on my raspberry pi 3.
I got the same issue in changing the local settings to ITA.
I am unable to understand what do you mean when you say change the language in the APP. Do you mean in an Android phone?
Can you please tell me in which path of the phone is possible to setting the locale?
Which is the relationship among the Android APP and the code running on Raspberry?
Thanks & Regards

The Google Assistant app on a phone has settings for the Google Assistant on all registered devices. The Raspberry Pi, which is authenticated as you, should appear in your device list and have settings for changing the language.

In Android don't work


http-server with simple username & password options

Thanks for sharing this 'simple' awesome app. Is there a plan to add username/password options to it e.g. basic-auth? I don't intend to run it 24/7 with basic-auth but it prevent preying-eyes, just a piece of mind.

Hey, I also wanted something simple like this. Something easy like, --auth user:pass. Any input or guidance would be well appreciated.

+1

Fixed in #245

I have tried the command,

http-server --username "test" --password "testing"
but it just never prompt a username & password input dialog.

Am I doing right with this command?

@vic1106 are you trying that on v0.11.1, or when installed from the master branch? This feature is not yet released to npm.

oh I just realise that.
I was using npm version which suppose not having this feature.
Then, I tried with master branch with this command.
npm start --username "test" --password "testing"
Not seeing the prompt too.


using -> import to safe lock

Using import for more stability for future updates of the package.

Welcome to Codecov :tada:
Once merged to your default branch, Codecov will compare your coverage reports and display the results in this comment.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


Waiting for secure connection - Can't share

I've enjoyed using Justa.ml for a couple of years now but suddenly it doesn't work any longer.
When trying to connect w/ my Android phone I see a "Establishing encrypted connection..." message but can't receive text.
Note I just found that I can Start on Android and then Connect on PC, just not the other way around
Steps:

Click [Start] on Justa.ml on PC
Click [Connect] on Justa.ml on Android phone
Enter PIN on Android
Justa.ml shows "Establishing encrypted connection..." and "greys out" the screen on Android
Enter text on PC and click [Send]
New item appears on Android but says "Encrypted" and is greyed-out and not clickable

BTW: Grey area on Android covers entire Justa.ml web page but if you scroll, bottom of page is uncovered/not-grey.
All of this has worked well many times in the past but makes Just.ml unusable for me now.
Note: I just tried starting on my Android and connecting from my PC and it works just fine. So, it only fails going the other way. That's just always how I've used Justa.ml.
Thanks for your very useful tool.
Regards,
Stephen Jones
Chicagoland, USA
<EMAIL_ADDRESS>

Thank you for reporting this. I had to find a few android phones to understand if it affects just a specific browser and was able to replicate this issue once as my Pixel phone (firefox and chrome) works. What phone and browser were you using? until I can reliably reproduce this, I will keep this issue open.

The phone is an LG K30 running Android 8.1.0 and Chrome 79.034.
However, I just tried to reproduce it and couldn't (even though I reproduced it multiple times before submitting the bug). Go figure. Maybe a Chrome or Android update fixed it.
Thanks for looking into it. I'll close the issue.


TSDuck at IBC 2018

Hi,
For TSDuck users who will be at IBC 2018 in Amsterdam next September, I will make a very short presentation at the EBU Open Source Meetup. Several open source projects are presented every year. There won't be much time for each project, so you won't probably learn anything. For users who are already familiar with TSDuck, let's just use the event as an opportunity to meet and share ideas and experiences.
EBU is the European Broadcasting Union. Its Open Source Meetup will take place Saturday Sept. the 15th, 16:00-17:00 at the EBU stand 10.F20. If you plan to meet here before or immediately afterwards, please leave a message here or send an email to contact @ tsduck.io.

Thanks to TSDuck users who attended the presentation. It is always refreshing to meet users.


Not compatible with rupa/z

@fdaciuk pointed this out, let's fix!
Problem is that Antibody loads only .plugin.zsh file, and rupa/z doesn't have one...

:+1:


Xiaomi Smart Camera C200 Camera Control does not show stream in Home Assistant

chuangmi.camera.046c04
access_token: ************************************* model_name: chuangmi.camera.046c04 brand: chuangmi frontend_stream_type: hls model: chuangmi.camera.046c04 lan_ip: ********** mac_address: ********** entity_class: MiotCameraEntity miot_type: urn:miot-spec-v2:device:camera:0000A01C:chuangmi-046c04:1 miot_action_result:  did: '*********' miid: 0 siid: 7 aiid: 1 code: -706010002 description: 'remote error code : -4' exe_time: 0 withLatency: 0  miot_action_error: -706010002 Service does not exist stream_address:  expire_at: 2023-09-16 17:33:01.249514 camera_control.on: true camera_control.image_rollover: 0 camera_control.night_shot: 2 camera_control.wdr_mode: true glimmer_full_color-2-6: true camera_control.recording_mode: 0 camera_control.motion_tracking: false camera_control.local_storage: true lock_region.lock_region_attr: {"lock_region":0,"legal_status":0} stream_status-8-9: 1 stream_status-7-9: 1 motion_detection: true motion_detection.alarm_interval: 10 detection_sensitivity-5-3: 0 motion_detection_start_time-5-4: 00:00:00 motion_detection_end_time-5-5: 23:59:00 memory_card_management.status: 0 storage_total_space-4-2: 31144016 storage_free_space-4-3: 30957792 storage_used_space-4-4: 186224 indicator_light.on: false state_updater: cloud sub_entities: indicator_light-3, camera_control-2.on-1, motion_event motion_video_time: 2023-09-16 17:27:59 motion_video_type: ObjectMotion motion_video_latest:  startDuration: 0 cut: false offset: 0 isCloud: false isRead: false videoStoreId: >-   CAMERA_VIDEO_******************************* eventType: ObjectMotion expireTime:<PHONE_NUMBER>520 isAlarm: true isShowImg: true imgStoreId: >-   CAMERA_IMG_********************************** fileId: '96632501899822464' extraInfo: '{"ver":"1.0.0","alarmStart":true,"eventType":"ObjectMotion"}'  entity_picture: /api/camera_proxy/camera.chuangmi_046c04_c7a9_camera_control?token=************************************* friendly_name: Xiaomi Smart Camera C200 Camera Control supported_features: 3 keep_streaming: true video_attribute: 1
--

I have same issue
Logger: homeassistant.components.camera
Source: components/camera/init.py:846
Integration: Camera (documentation, issues)
First occurred: 22:45:45 (5 occurrences)
Last logged: 22:50:23
Error requesting stream: camera.chuangmi_046c04_xxxx_camera_control does not support play stream service

same error. Do you plan to fix it ?

I have the same problem with C200, but no problem with C300.
Could you please fix it?

Some news about this?

same problem, still not able to find a solution. Any workaround like onvif protocol or RTSP for Xiaomi C200?

same here with C200 : `miot_action_result:
did: '1029817025'
miid: 0
siid: 7
aiid: 1
code: -704220025
exe_time: 0
withLatency: 0
stream_address:
expire_at: 2024-10-14 15:50:01.510170
miot_action_error: -704220025 The number of action parameters does not match`

Hi!
Same issue here
any solution?

Hi
Any news on this topic. Do you plan to fix it or someone can provide a workaround ?
Thanks in advance

Still wait

Hi, I'm waiting too

Video  streams  are  not  supported.


Peers

"msg": "Missing external BGP Peering elements: [{'msg': 'Cannot find specified element', 'type': 'single_fw,fw_cluster', 'name': 'PEER_NC1_to_Store13'}, {'msg': 'Cannot find specified element', 'type': 'single_fw,fw_cluster', 'name': 'PEER_NC2_to_Store13'}]"
            "bgp_peering": [
                {
                    "engine": "PEER_NC1_to_Store13",
                    "interface_id": "1013",
                    "name": "Store13_to_phmbun1fmuta"
                },
                {
                    "engine": "PEER_NC2_to_Store13",
                    "interface_id": "2013",
                    "name": "Store13_to_phmbun2fmuta"
                }
            ],

How can i create a new Peer Element ?

same error after crearing PEER object manually

The error is related to the configuration - there are two peer types that you can specify 'engine' or 'external_bgp_peer'. In your example above you are using 'engine' which is expecting the name of a firewall engine. Change this to look like:
            "bgp_peering": [
                {
                    "external_bgp_peer": "PEER_NC1_to_Store13",
                    "interface_id": "1013",
                    "name": "Store13_to_phmbun1fmuta"
                },
                {
                    "external_bgp_peer": "PEER_NC2_to_Store13",
                    "interface_id": "2013",
                    "name": "Store13_to_phmbun2fmuta"
                }
            ],

I just grab with engine_facts and changed to create a new node.
Le 16 mars 2018 12:32:37 GMT+01:00, David LePage<EMAIL_ADDRESS>a écrit :

The error is related to the configuration - there are two peer types
that you can specify 'engine' or 'external_bgp_peer'. In your example
above you are using 'engine' which is expecting the name of a firewall
engine. Change this to look like:
           "bgp_peering": [
               {
                   "external_bgp_peer": "PEER_NC1_to_Store13",
                   "interface_id": "1013",
                   "name": "Store13_to_phmbun1fmuta"
               },
               {
                   "external_bgp_peer": "PEER_NC2_to_Store13",
                   "interface_id": "2013",
                   "name": "Store13_to_phmbun2fmuta"
               }
           ],

--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/gabstopper/ansible-stonesoft/issues/9#issuecomment-373687039

--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.

Goal is also to create the external_bgp_peer but impossible to specify the destination Ip of the peer ... and  comment as well ;)
Le 16 mars 2018 12:32:37 GMT+01:00, David LePage<EMAIL_ADDRESS>a écrit :

The error is related to the configuration - there are two peer types
that you can specify 'engine' or 'external_bgp_peer'. In your example
above you are using 'engine' which is expecting the name of a firewall
engine. Change this to look like:
           "bgp_peering": [
               {
                   "external_bgp_peer": "PEER_NC1_to_Store13",
                   "interface_id": "1013",
                   "name": "Store13_to_phmbun1fmuta"
               },
               {
                   "external_bgp_peer": "PEER_NC2_to_Store13",
                   "interface_id": "2013",
                   "name": "Store13_to_phmbun2fmuta"
               }
           ],

--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/gabstopper/ansible-stonesoft/issues/9#issuecomment-373687039

--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.

so the bug is in Engine_facts (engine instead of external_bgp_peer)

I just tried the latest posted engine_facts.yml and it appears to display the output properly:

Here is the yaml:
bgp_peering:
-   external_bgp_peer: bgppeer
interface_id: '21.21'
name: bgppeering
network: <IP_ADDRESS>/24
-   engine: jackson
interface_id: '67'
name: bgppeering
network: <IP_ADDRESS>/24
Can you confirm you have the latest engine_facts?
Understood on creating the BGP Peer. I will add this capability to simplify this.

Wow that one is pretty different of mine
i have no interface, no ip
i confirm, i did update on both pack this morning
Le 16/03/2018 à 17:54, David LePage a écrit :

I just tried the latest posted engine_facts.yml and it appears to
display the output properly:
image
https://user-images.githubusercontent.com/14811349/37533698-9607817c-2910-11e8-90a6-d37b087883c0.png
Here is the yaml:
bgp_peering:

external_bgp_peer: bgppeer
interface_id: '21.21'
name: bgppeering
network: <IP_ADDRESS>/24
engine: jackson
interface_id: '67'
name: bgppeering
network: <IP_ADDRESS>/24

Can you confirm you have the latest engine_facts?
Understood on creating the BGP Peer. I will add this capability to
simplify this.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/gabstopper/ansible-stonesoft/issues/9#issuecomment-373776947,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEEKjDyC7feW3XsIcjWOYoGbr7dxC7xgks5te-5HgaJpZM4Std01.

What about bgp elements like routemap ip prefix external bgp peer. Is it possiblr to have example to create ?
RÉMY
Le 16 mars 2018 17:54:31 GMT+01:00, David LePage<EMAIL_ADDRESS>a écrit :

I just tried the latest posted engine_facts.yml and it appears to
display the output properly:

Here is the yaml:
bgp_peering:
-   external_bgp_peer: bgppeer
interface_id: '21.21'
name: bgppeering
network: <IP_ADDRESS>/24
-   engine: jackson
interface_id: '67'
name: bgppeering
network: <IP_ADDRESS>/24
Can you confirm you have the latest engine_facts?
Understood on creating the BGP Peer. I will add this capability to
simplify this.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/gabstopper/ansible-stonesoft/issues/9#issuecomment-373776947

--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.

-rw-r--r--.  1 adminappli users    6207 Mar 16 18:06 l3fw_cluster.yml

      bgp_peering:
      -   engine: PEER_NC1
          interface_id: '1014'
          name: XXXX
      -   engine: PEER_NC2
          interface_id: '2014'
          name: XXXX
      bgp_profile: Default BGP Profile
      enabled: true
      router_id: null

PEER_NC1 & PEER_NC2 are external_bgp_peer object
version is latest downloaded this morning from master branch

Do you have the latest engine_facts.yml?
https://github.com/gabstopper/ansible-stonesoft/blob/master/library/engine_facts.py
Also, which version of SMC are you using? Just want to verify, i'm suspecting maybe the SMC version might be slightly older and the routing element type is not in that version. If you can verify I can adjust on my end if necessary.

ok, I have fixed this issue, it appears you may be using an older (i.e. SMC < 6.3.x) version. This will be part of next commit.

Yes im using 6.2.2 right now
Le 18 mars 2018 00:53:04 GMT+01:00, David LePage<EMAIL_ADDRESS>a écrit :

ok, I have fixed this issue, it appears you may be using an older (i.e.
SMC < 6.3.x) version. This will be part of next commit.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/gabstopper/ansible-stonesoft/issues/9#issuecomment-373961484

--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.

Ok. This is resolved in the latest commit. There was an attribute in earlier versions that was not supported so the default behavior was to interpret as engine.
For peers, i've almost finished a module that allows you to create all bgp elements, this will be complete and posted Monday.

Hi
Very good ! Let me know when its posted.
RÉMY POUCHAIN.
Le 19 mars 2018 04:36:18 GMT+01:00, David LePage<EMAIL_ADDRESS>a écrit :

Ok. This is resolved in the latest commit. There was an attribute in
earlier versions that was not supported so the default behavior was to
interpret as engine.
For peers, i've almost finished a module that allows you to create all
bgp elements, this will be complete and posted Monday.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/gabstopper/ansible-stonesoft/issues/9#issuecomment-374092011

--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.

Hi Remy,
I have bgp_element posted, along with an example yaml file.
I haven't finished the docs quite yet but those along with bgp_element_facts will be coming shortly.
This module will allow you to create all bgp element types.
See this yaml for an example for each of the element types:
https://github.com/gabstopper/ansible-stonesoft/blob/master/playbooks/bgp_element.yml
You will also need to update smc-python as well. I will complete the bgp_element_facts and docs soon so I can start the interface schema changes.

For ip prefix list best is also to select an object to avoid create static object.
Need to specify route-map in bgppeering and connection profile
Minimum mask length in prefix is not a mandatory field in SMC should the same on Maximum.
RÉMY POUCHAIN.
Le 20 mars 2018 06:30:55 GMT+01:00, David LePage<EMAIL_ADDRESS>a écrit :

Hi Remy,
I have bgp_element posted, along with an example yaml file.
I haven't finished the docs quite yet but those along with
bgp_element_facts will be coming shortly.
This module will allow you to create all bgp element types.
See this yaml for an example for each of the element types:
https://github.com/gabstopper/ansible-stonesoft/blob/master/playbooks/bgp_element.yml
You will also need to update smc-python as well. I will complete the
bgp_element_facts and docs soon so I can start the interface schema
changes.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/gabstopper/ansible-stonesoft/issues/9#issuecomment-374481094

--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.

"module_stderr": "Traceback (most recent call last):\n  File \"/tmp/ansible_fuCzMq/ansible_module_bgp_element.py\", line 229, in <module>\n    main()\n  File \"/tmp/ansible_fuCzMq/ansible_module_bgp_element.py\", line 226, in main\n    StonesoftBGPElement()\n  File \"/tmp/ansible_fuCzMq/ansible_module_bgp_element.py\", line 54, in __init__\n    super(StonesoftBGPElement, self).__init__(self.module_args, supports_check_mode=True)\n  File \"/tmp/ansible_fuCzMq/ansible_modlib.zip/ansible/module_utils/stonesoft_util.py\", line 367, in __init__\n  File \"/tmp/ansible_fuCzMq/ansible_module_bgp_element.py\", line 73, in exec_module\n    if self.create_or_update_element(element):\n  File \"/tmp/ansible_fuCzMq/ansible_module_bgp_element.py\", line 114, in create_or_update_element\n    with_status=True, **values)\n  File \"/usr/lib/python2.7/site-packages/smc_python-0.6.1_dev.201802262117-py2.7.egg/smc/routing/access_list.py\", line 131, in update_or_create\n    print(\"Class view: %s not in: %s\" % cls._view(**entry))\nTypeError: not all arguments converted during string formatting\n",
"module_stdout": "Entry: {'action': 'permit', 'subnet': 'XX.XX.XX.XX/23', 'max_prefix_length': 32, 'min_prefix_length': 24}\n",
"msg": "MODULE FAILURE",

  - ip_prefix_list:
        name: PREFIX_LIST_FW13 <== this name does not work (accepted by SMC)
        entries:
          - subnet: <IP_ADDRESS>/23
            min_prefix_length: 24 <== i don't want to specify this and need to be greater than mask (not mandatory in SMC)
            max_prefix_length: 32
            action: permit
          - subnet:  <IP_ADDRESS>/23
            min_prefix_length: 24 <== i don't want to specify this and need to be greater than mask
            max_prefix_length: 32
            action: permit

Ahh, I didn't realize the prefix mask lengths were optional. I just verified that indeed they are. I will fix this and the errant print bug real quick so you can continue.

I just verified, I already support not using those fields in the smc-python API so will make an adjustment to current bgp_element mod. Posting back shortly.

And a little support for group instead of subnet will be appreciated ;)
Le 20 mars 2018 13:44:02 GMT+01:00, David LePage<EMAIL_ADDRESS>a écrit :

Ahh, I didn't realize the prefix mask lengths were optional. I just
verified that indeed they are. I will fix this and the errant print bug
real quick so you can continue.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/gabstopper/ansible-stonesoft/issues/9#issuecomment-374583889

--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.

Hi Remy,
I will put that feature request in to the SMC team (i.e. adding groups as the subject of a access list entry).

Ok latest ansible commit @c863422 posted. That will remove the ip prefix list check for min/max prefixes. Latest smc-python removes the errant print in the new update_or_create access list function. This will all be rolled up into an official smc-python release once I work through the interface schema next.

Hi Remy,
One other thing you might notice, I am adding a better 'state' description when making an ansible run. For example, when you play the bgp_element task, you should see output from the state attribute like the following:
"state": [
        {
            "action": "created",
            "name": "PREFIX_LIST_FW13",
            "type": "ip_prefix_list"
        },
        {
            "action": "created",
            "name": "myservice2",
            "type": "ip_access_list"
        },
        {
            "action": "created",
            "name": "aprefix",
            "type": "ip_prefix_list"
        },

Or if a change was made:
"state": [
        {
            "action": "modified",
            "name": "aprefix",
            "type": "ip_prefix_list"
        }
    ]

Or if deleting (delete by setting state: absent and defining at least the bgp_element type and name:
{'ip_access_list': {'name'}}
 "state": [
        {
            "action": "deleted",
            "name": "PREFIX_LIST_FW13",
            "type": "ip_prefix_list"
        },

Some time i have database error. Did you already see this issue ?
RÉMY POUCHAIN
Le 20 mars 2018 17:18:22 GMT+01:00, David LePage<EMAIL_ADDRESS>a écrit :

Hi Remy,
One other thing you might notice, I am adding a better 'state'
description when making an ansible run. For example, when you play the
bgp_element task, you should see output from the state attribute like
the following:
"state": [
       {
           "action": "created",
           "name": "PREFIX_LIST_FW13",
           "type": "ip_prefix_list"
       },
       {
           "action": "created",
           "name": "myservice2",
           "type": "ip_access_list"
       },
       {
           "action": "created",
           "name": "aprefix",
           "type": "ip_prefix_list"
       },

Or if a change was made:
"state": [
       {
           "action": "modified",
           "name": "aprefix",
           "type": "ip_prefix_list"
       }
   ]

Or if deleting (delete by setting state: absent and defining at least
the bgp_element type and name:
{'ip_access_list': {'name'}}
"state": [
       {
           "action": "deleted",
           "name": "PREFIX_LIST_FW13",
           "type": "ip_prefix_list"
       },

--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/gabstopper/ansible-stonesoft/issues/9#issuecomment-374659974

--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.

I have seen this before - that message would be coming from the SMC API itself. It usually has to do with some sort of invalid input. Is it reproducible with a specific playbook? i.e. if you re-run the same playbook that causes the error, can you send me the smc.log output?
Also, is it related to a specific configuration area (i.e. your running route VPN modifications, etc).

I can send the smc-log but i have to anonymize stuff
Le 21 mars 2018 02:17:27 GMT+01:00, David LePage<EMAIL_ADDRESS>a écrit :

I have seen this before - that message would be coming from the SMC API
itself. It usually has to do with some sort of invalid input. Is it
reproducible with a specific playbook? i.e. if you re-run the same
playbook that causes the error, can you send me the smc.log output?
Also, is it related to a specific configuration area (i.e. your running
route VPN modifications, etc).
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/gabstopper/ansible-stonesoft/issues/9#issuecomment-374809653

--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.

I have this issue when i try to create a lot of elements (>10) And if a task is in error ... scenario still continue (why?)...
Le 21 mars 2018 02:17:27 GMT+01:00, David LePage<EMAIL_ADDRESS>a écrit :

I have seen this before - that message would be coming from the SMC API
itself. It usually has to do with some sort of invalid input. Is it
reproducible with a specific playbook? i.e. if you re-run the same
playbook that causes the error, can you send me the smc.log output?
Also, is it related to a specific configuration area (i.e. your running
route VPN modifications, etc).
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/gabstopper/ansible-stonesoft/issues/9#issuecomment-374809653

--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.

Not sure without seeing the audits. We may have to open a support case on it also. When i've seen this issue occur, it has almost always been due to an issue with the SMC side. If you can send me the task you are running and a snippet of the last payload from smc.log I can try to duplicate on my end.

You know i will update you with a full playbook of bgp runnig config ;)
But anyway i can provide you my playbook for objects created. I have so many firewalls and objects in the smc thats why we have some issue.
My question is regarding the result on SMC ... normally a failed status of a task will stop the full scenario. Maybe something is missing for ansible regarding the task status.
RÉMY POUCHAIN.
Le 21 mars 2018 13:12:06 GMT+01:00, David LePage<EMAIL_ADDRESS>a écrit :

Not sure without seeing the audits. We may have to open a support case
on it also. When i've seen this issue occur, it has almost always been
due to an issue with the SMC side. If you can send me the task you are
running and a snippet of the last payload from smc.log I can try to
duplicate on my end.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/gabstopper/ansible-stonesoft/issues/9#issuecomment-374916391

--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.

Ok so far so good. I will update you quickly with error log.
Right now I tested ip prefix list (you have already features needed), external peer ok, bgp peering ok, asn ok, route map (a check rule needed to avoid duplicate) ok.
I cant test access list community list and ipv6 cause i have nothing about this in my config.
RÉMY POUCHAIN
Le 21 mars 2018 14:46:40 GMT+01:00, David LePage<EMAIL_ADDRESS>a écrit :

You are correct, there is an exception handler in every ansible module
that would stop the task if an SMC error occurred. It should also print
the task status in a msg attribute. If you run with -vvv you will see
that message indicated. I can check to see without -vvv what the result
looks like. Also, making progress on the new interface schema. Should
have that ready soon.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/gabstopper/ansible-stonesoft/issues/9#issuecomment-374941840

--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.

ok thanks Remy! I have tested all and now have a solid framework for unittest before I publish these out. I will push bgp_element_facts soon.

And have you any task for monitoring ... validate tunnels works etc etc ;)
Or do a sh ip bgp sum or sh ip route bgp with filter to check redistribute on quagga ...
RÉMY POUCHAIN
Le 22 mars 2018 14:20:55 GMT+01:00, David LePage<EMAIL_ADDRESS>a écrit :

ok thanks Remy! I have tested all and now have a solid framework for
unittest before I publish these out. I will push bgp_element_facts
soon.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/gabstopper/ansible-stonesoft/issues/9#issuecomment-375303142

--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.

route_facts should dump the routing table (same that you see when going into SMC->monitoring->routing). On your SMC does this show the BGP routing details?

For routing table in BGP not sure because its manage by quagga :(
Routing table will show the static table but anyway i will ask stonesoft if its in api.
Monitoring could be interesting to have a good view about vpn tunnels up or not before starting others checks.
RÉMY POUCHAIN.
Le 22 mars 2018 20:44:10 GMT+01:00, David LePage<EMAIL_ADDRESS>a écrit :

routing_facts should dump the routing table (same that you see when
going into SMC->monitoring->routing). On your SMC does this show the
BGP routing details?
Here is an example:
https://github.com/gabstopper/ansible-stonesoft/blob/master/playbooks/routing_facts.yml
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/gabstopper/ansible-stonesoft/issues/9#issuecomment-375433330

--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.

It will show routing entries created by BGP also from Monitoring->Routing but likely not exactly the same level of detail as quagga. I'd have to test. Also, another option (since we're using Ansible) is a library to make the connection directly to the engine and execute the relevant quagga commands if the API doesn't provide what we need.
Also, I have a package smc-python-monitoring that does allow you to query the VPN tunnels as shown from Monitoring->VPN SA's. Maybe that would be adequate?

Yes right thats what i do for quagga for peering status and  route as well.
Smc monitoring should be a better view yes. Just to check.
RÉMY POUCHAIN
Le 22 mars 2018 23:31:50 GMT+01:00, David LePage<EMAIL_ADDRESS>a écrit :

It will show routing entries created by BGP also from
Monitoring->Routing but likely not exactly the same level of detail as
quagga. I'd have to test. Also, another option (since we're using
Ansible) is a library to make the connection directly to the engine and
execute the relevant quagga commands if the API doesn't provide what we
need.
Also, I have a package smc-python-monitoring that does allow you to
query the VPN tunnels as shown from Monitoring->VPN SA's. Maybe that
would be adequate?
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/gabstopper/ansible-stonesoft/issues/9#issuecomment-375479034

--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.

Hi Remy,
Following up on this one. Do you still need a solution for retrieving routes? Did you see the routing_facts module? There is an example called routing_facts.yml that allows you to query the SMC which will pull all routes as you see in SMC under Monitoring->Routing.


Muting issue

The app recognises when ads play(notification pops up), but doesn't mute them. I'm running on Android 10 on an Oppo device.

Do you have any tips? Where should i start?

Has it ever worked on this device on previous versions of either OS, spotify or adfree?
In any case, you can debug why the mute of stream music does not mute playback. The issue seems device specific.
See here
https://github.com/abertschi/ad-free/blob/master/app/src/main/java/ch/abertschi/adfree/AudioController.kt


term-image to respect XDG Base Directories Specification

Is your feature request related to a problem? Please describe.
Currently term-image stores and writes configuration files to $HOME/.term_image/
Describe the solution you'd like
If the system has XDG_CONFIG_HOME set,  please place configurations there (there may be other considerations, see XDG Base Directories Specification)
Describe alternatives you've considered
Thought about a symlink, but that still leaves another line of output when listing the home directory

Finally putting this to rest. :smiley:
I've updated every aspect of the tool that used ~/.term_image to now use XDG Base Directories (or system/user-specific directories in the case of temporary files).
I'm sorry it took so long.


Compatibility of Xray on Openshift platform

Missing documentation on Supported Openshift platform versions for Xray installation
Tested: Xray v2.5.1 installs on Openshift platform v3.9.x
Xray v2.6.0 throws error on Openshift platform v3.9.x

Updates: Xray v2.6.3 installs on Openshift platform v3.10.83

@eldada It requires to update OS templates as our installer has evolved.

This integration is deprecated.


Interesting flake on TestAccDeleteBeforeCreate

Interesting flake on TestAccDeleteBeforeCreate:
  	* Retrieving AWS account details: validating provider credentials: retrieving caller identity from STS:
  	operation error STS: GetCallerIdentity, https response error
        StatusCode: 403, RequestID: 8b1a26fa-db29-43dd-b705-869eadafa74c,
        api error ExpiredToken: The security token included in the request is expired

https://github.com/pulumi/pulumi-aws/issues/3655

Possibly a misconfiguration on our part?
SO troubleshooting topicwith similar issues
But the region is set globally for our tests.
This cron  is flaking on the STS GetCallerIdentity credentials verification:
 Retrieving AWS account details: validating provider credentials: retrieving caller identity from STS: operation error STS: GetCallerIdentity, https response error StatusCode: 403, RequestID: <redacted>, api error ExpiredToken: The security token included in the request is expired

This is the same error throughout on the flakes
What is interesting is that this test never flakes on master.
I deleted the EC2 instance that failed to be deleted in our last run.
I wonder if it's an expiration issue since node tests take just a little over an hour to run?

UPDATE: this is now flaking on pull requests as well.

Flakes on master in https://github.com/pulumi/pulumi-aws/issues/3636 fwiw.. Not sure what's going on here.

Waiting on a runner is what is eating up most of the authenticated time:
2024-03-20T18:07:34.4133831Z Requested labels: ubuntu-latest
2024-03-20T18:07:34.4134259Z Job defined at: pulumi/pulumi-aws/.github/workflows/run-acceptance-tests.yml@refs/pull/3664/merge
2024-03-20T18:07:34.4134450Z Waiting for a runner to pick up this job...
2024-03-20T18:07:34.7221118Z Job is waiting for a hosted runner to come online.
2024-03-20T18:07:39.3277658Z Job is about to start running on the hosted runner: GitHub Actions 12 (hosted)

(the above is output from a running job after ~15 minutes)

Fixed via #3666

https://github.com/pulumi/pulumi-aws/actions/runs/8438448044 another instance

https://github.com/pulumi/ci-mgmt/pull/863 I think ultimately fixed it by doubling the timeout window.