BCGov Theme: Footer component doesn't wrap the content properly

Specifications
@button-inc/bcgov-theme v1.0.1
Describe the bug
The Footer component wraps the content, but the container stays with a fixed height when the page gets narrow, which causes a rendering issue
How to reproduce
Use the Footer component with more than just a few items, and narrow the browser window down until the footer content wraps.
The documentation exhibits that behaviour when narrowing down just before it wraps the left-hand menu:
https://button-inc.github.io/service-development-toolkit/@button-inc/bcgov-theme/index.html?path=/docs/components-footer--default
Expected behavior
The container for the Footer component changes its height to fit its content
or
Some of the content is not displayed, and a menu appears
or
...?
Additional context

Acceptance Criteria

Given
When
Then
Pass/Fail

In order to fix the issue, the footer menu font size should be reduced (from 16 px to 14px) (we need to consider a smaller font size if we are considering mobile users as well?) and the space between menu items also needs to be minimized. So that when the window gets narrowed the whole footer menu is still available for the user to interact with.![Footer menu fixed .png]


Error with BarcodeReader when StartCameraAutomatically is true

Setup: NET 7, Blazor Server-side (use the project BarcodeReaderIssue.zip)
Steps to reproduce:

Refresh the page with reload button or press F5
Scan a QR code

Expected results: No error should occur on receiving barcode text
Actual results: An error occurs on StateHasChanged() at the callback function: The current thread is not associated with the Dispatcher. (see the video https://user-images.githubusercontent.com/76152571/218969612-6a2f57c3-0587-4134-b1d5-e61e178ce117.mp4)

Are you able to get a barcode to read?  I am only able to get a QR Code to read.

Are you able to get a barcode to read? I am only able to get a QR Code to read.

Yes, I get the QR code but then it throws an exception on the StateHasChanged() call.

I'm using the tool to read only QR codes, no barcodes.

Ok.  Well, I am not having your issue.  It seems to work just fine for me with scanning QR codes and the camera turning on automatically.  Maybe it's a camera/driver issue?  Any chance you could test to see if you can read a barcode and let me know if it works for you?

I tested with a barcode and I got the same error. I don't think is a camera issue because I hosted the website publicly (https://barcodereaderissue.azurewebsites.net/) and I tested with the camera on my smartphone, and I have the same problem. I think initially the issue is coming after the page is reloaded and I have the following exception:
System.NullReferenceException: Object reference not set to an instance of an object.
at BlazorBarcodeScanner.ZXing.JS.BarcodeReader.StopDecoding()
at BlazorBarcodeScanner.ZXing.JS.BarcodeReader.Dispose()
at Microsoft.AspNetCore.Components.RenderTree.Renderer.Dispose(Boolean disposing)
--- End of stack trace from previous location ---
at Microsoft.AspNetCore.Components.RenderTree.Renderer.Dispose(Boolean disposing)
at Microsoft.AspNetCore.Components.Rendering.RendererSynchronizationContext.<>c.b__8_0(Object state)
--- End of stack trace from previous location ---
at Microsoft.AspNetCore.Components.RenderTree.Renderer.DisposeAsync()
at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.g__Await|22_0(Int32 i, ValueTask vt, List1 toDispose)    at Microsoft.AspNetCore.Http.Features.RequestServicesFeature.<DisposeAsync>g__Awaited|9_0(RequestServicesFeature servicesFeature, ValueTask vt)    at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.<FireOnCompleted>g__ProcessEvents|242_0(HttpProtocol protocol, Stack1 events)

Tested your code with a webcam and it worked fine with qr codes.

Did you reload the page before scanning? Do you see any error in the Visual Studio Output window after the reload?

Probably shouldn't be calling StateHasChanged() while Disposing which is currently being done via StopDecoding()
Ref
        public void Dispose()
        {
            StopDecoding();
        }
...
...
...
        public void StopDecoding()
        {
            BarcodeReaderInterop.OnBarcodeReceived(string.Empty);
            _backend?.StopDecoding();
            IsDecoding = false;
            StateHasChanged();
        }

Hi @diegorod , thank you for your comment. Yes, the issue is calling StateHasChanged() while disposing and I think this should be fixed in the next version.
Now I realized that we have a similar error on calling await OnBarcodeReceived.InvokeAsync(args) at method ReceivedErrorMessage(ErrorReceivedEventArgs args):
System.InvalidOperationException: The current thread is not associated with the Dispatcher. Use InvokeAsync() to switch execution to the Dispatcher when triggering rendering or component state.
at Microsoft.AspNetCore.Components.Dispatcher.AssertAccess()
at Microsoft.AspNetCore.Components.RenderTree.Renderer.AddToRenderQueue(Int32 componentId, RenderFragment renderFragment)
at Microsoft.AspNetCore.Components.ComponentBase.StateHasChanged()
at Microsoft.AspNetCore.Components.ComponentBase.Microsoft.AspNetCore.Components.IHandleEvent.HandleEventAsync(EventCallbackWorkItem callback, Object arg)
at BlazorBarcodeScanner.ZXing.JS.BarcodeReader.ReceivedBarcodeText(BarcodeReceivedEventArgs args)
at System.Threading.Tasks.Task.<>c.b__128_0(Object state)
at Microsoft.AspNetCore.Components.Rendering.RendererSynchronizationContext.ExecuteSynchronously(TaskCompletionSource completion, SendOrPostCallback d, Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at Microsoft.AspNetCore.Components.Rendering.RendererSynchronizationContext.ExecuteBackground(WorkItem item)
And I'm not quite sure if this is only a local issue.

This is more of a JS interop problem use this instead to avoid that :
private async Task LocalReceivedBarcodeText(BarcodeReceivedEventArgs args)         {             await InvokeAsync(() => {                 this.LocalBarcodeText = args.BarcodeText;                 StateHasChanged();             });         }


[Java Core] Fixed a bug in deserialization of nested collections.

@sigansky,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Matlab crash while glmnetMex.mexmaci64 was running

I am trying to run the SINGE_Example.m in MATLABR2020a on macOS Catalina.

ver -support

MATLAB Version: <IP_ADDRESS>3465 (R2020a) Update 8
MATLAB License Number: 40707400
Operating System: Mac OS X  Version: 10.15.7 Build: 19H1824
Java Version: Java 1.8.0_202-b08 with Oracle Corporation Java HotSpot(TM) 64-Bit Server VM mixed mode
MATLAB                                                Version 9.8         (R2020a)      License 40707400

I get the following Warning message:
Warning: from glmnet Fortran code (error code -5); Convergence for 5th lambda value not reached
after maxit=10000 iterations; solutions for larger lambdas returned

In elnet (line 33)
In glmnet (line 443)
In iLasso_for_SINGE (line 111)
In run_iLasso_row (line 27)
In SINGE_GLG_Test (line 79)
In SINGE (line 20)
In SINGE_Example (line 16)

After several iterations MATLAB crashes.
According to MathWorks technical support, the crash was detected while the MEX-file glmnetMex.mexmaci64 was running.
Any suggestion to solve this issue?

Thanks for letting us know @ElenaMerinoTejero.  Can you please tell us which version glmnet you are using?  I see that https://hastie.su.domains/glmnet_matlab/download.html now lists glmnet_matlab.zip as well as glmnet_matlab_new.zip.

Thanks for bringing this to our notice @ElenaMerinoTejero.
Could you please share also more details of the hyperparameters file you are using to run SINGE as well as the size of the data matrix in number of genes and cells?
There is an ongoing issue with a potential memory leak in the glmnetMex code which causes the crashes for larger datasets. We also noticed that this issue is more frequent with the "poisson" distribution option compared to the "gaussian" distribution.
The following general strategies may help, but based on additional information, I could give you more targeted suggestions.

Reducing the number of potential regulators to make the glmnet input size. This can be achieved either by retaining only the important genes in the dataset, or using the regix argument where you specify the indices of the genes to be tested as regulators (please see https://github.com/gitter-lab/SINGE/blob/master/data1/X_regix_test.mat for an example).
Increasing the values of --prob-zero-removal 0 --prob-remove-sample 0.2 to also reduce the glmnet input size. Especially for sparse data sets, we observed that prob-zero-removal do not impact SINGE performance greatly.

Thanks for letting us know @ElenaMerinoTejero. Can you please tell us which version glmnet you are using? I see that https://hastie.su.domains/glmnet_matlab/download.html now lists glmnet_matlab.zip as well as glmnet_matlab_new.zip.

Thanks to you for the fast reply! I am using the updated glmnet version. I think that is the glmnet_matlab_new.zip.

Thanks for bringing this to our notice @ElenaMerinoTejero.
Could you please share also more details of the hyperparameters file you are using to run SINGE as well as the size of the data matrix in number of genes and cells? If you have access to docker, can you also try and run SINGE from its docker implementation? There is an ongoing issue with a potential memory leak in the glmnetMex code which causes the crashes for larger datasets. We also noticed that this issue is more frequent with the "poisson" distribution option compared to the "gaussian" distribution. The following general strategies may help, but based on additional information, I could give you more targeted suggestions.

Reducing the number of potential regulators to make the glmnet input size. This can be achieved either by retaining only the important genes in the dataset, or using the regix argument where you specify the indices of the genes to be tested as regulators (please see https://github.com/gitter-lab/SINGE/blob/master/data1/X_regix_test.mat for an example).
Increasing the values of --prob-zero-removal 0 --prob-remove-sample 0.2 to also reduce the glmnet input size. Especially for sparse data sets, we observed that prob-zero-removal do not impact SINGE performance greatly.

Thanks to you too, for your fast replying.
For now I am trying to running the SINGE_Example.m which takes as hyperparameters those in 'default_hyperparameters.txt', as data 'data1/X_SCODE_data.mat' (with 356 cells) and as gene list 'data1/gene_list.mat' (with 100 genes). Furthermore, the "gaussian" distribution is used in the example.
default_hyperparameters.txt
Nevertheless, I am planning to run SINGE with a larger dataset (33694 genes and 737280 single cells) so I could use your suggestions then, thanks.

That's actually one of the most stable test cases we have run. Would it be possible for you to test the docker implementation at https://hub.docker.com/r/agitter/singe?
This would remove the OS and the Matlab version as variables and help us better diagnose if the problem still persists.
Regarding the larger dataset: I would strongly advise on limiting the genes to a much smaller number, and potentially also subsampling the cells at a much higher rate. I understand you are currently trying SINGE out on a personal computing device, but for the larger datasets, you would also want to use a high throughput computing server to speed up the analysis.

Thanks for the suggestion! I am running the docker implementation and it doesn't crash now and produces output files. Nevertheless, the Warning message persists. I am unsure if it affects the output. Is there a way to compare my output with the expected one for the SINGE_Example?
In any case, I will take your advice about reducing the data set and trying it out on a server for higher speed.

We have formal test cases you can use to confirm the SINGE_Example output matches the expected output. However, they use a smaller set of hyperparameters so that they run quickly on GitHub Actions.  You can change the hyperpameters to tests/example_hyperparameters.txt.
Then, the output files should match those in the directory https://github.com/gitter-lab/SINGE/tree/master/tests/reference/latest.  You can start by comparing the SINGE_Gene_Influence.txt and SINGE_Ranked_Edge_List.txt files you generate versus those stored in the repository.  If those match, you can trust SINGE_Example.m is running correctly.  If you want to test in more detail, I can give you instructions for running our Python code that will compare the entire adjacency matrices.
The most relevant test script, which you don't have to run but may be a useful reference, is https://github.com/gitter-lab/SINGE/blob/master/tests/standalone_test.sh

I ran SINGE_Example from docker with hyperparameeters from tests folder as @agitter indicated and output files indeed match those in /tests/reference/latest. Furthermore, no warning message appeared this time so I can trust SINGE running correctly. Thanks a lot for the help.

That's great!  We can keep this issue open if you'd like to discuss strategies for running SINGE in parallel on a cluster as you scale up to your full dataset.  That is a larger dataset than any we've tested on previously, so we're happy to help come up with strategies.
@atuldeshpande we should also separately follow up on whether glmnet_matlab_new.zip causes problems with the example dataset.

Hi @agitter,  I reduced the dataset by selecting a particular cell type. The dataset now has 433 singe cells and a mean of 157 genes per cell. I am finding that when running this data set with tests/example_hyperparameters.txt the corresponding adjacency matrixes are outputted but the list of ranked edges and the gene influence files are not outputted. Furthermore, SINGE is killed when running run_SINGE_Aggregate.sh:
/usr/local/SINGE/run_SINGE_Aggregate.sh: line 30:    32 Killed                  "/usr/local/SINGE/SINGE_Aggregate" "GSE142016_RAW/SLE1/X_SCODE_data.mat" "GSE142016_RAW/SLE1/gene_list.mat" "Output"
Any clues as to why this may happen?   Could it be a size problem?
BTW: It would also be helpful to discuss how to run SINGE in parallel on a cluster since I would like to run bigger data sets and with default hyperparameters.

About the reduced data set size: There are 9082 unique genes, thus the size of the resulting X data matrix is 433x9082.

Are you still running SINGE from the Docker container?  If you were able to generate adjacency matrices successfully, you should now be able to run SINGE.sh in Aggregate mode to generate the edge list and gene influence files.  I have not previously seen SINGE fail at this stage with the behavior you described, so we'll have to help you debug this problem.
One idea would be to copy a small number, perhaps 2-4, of the adjacency matrices to a new directory for testing.  If those can be aggregated successfully, then it may indicate the dataset size is an issue.  If that still fails, you could zip those adjacency matrices and the input .mat files so we could try reproducing the issue in Docker.
We have an example of how we ran SINGE on a cluster using HTCondor in this directory of our supplemental repository.  The basic idea is that instead of creating a single hyperparameters file and running SINGE with all hyperparameter combinations in a single batch, each combination is split into a separate job.  Those jobs can be parallelized over different nodes in the cluster.  Then, after all jobs complete, the SINGE aggregate step can run.  We can work through the details with you depending on your cluster setup and whether you will be using Docker or running MATLAB directly.

In addition, the MATLAB crashes are usually an issue only for the first part of SINGE, which require glmnet. Since you already have successfully navigated that part, you can try running SINGE aggregate through the Matlab functions. (I wonder if the Aggregate trying to load 9000x9000 matrices and perform additions on them may be causing memory issues?)

@agitter Yes, still running SINGE from docker. I followed your suggestion and copied 1 of the 4 Adjacency Matrixes to a test output folder to run Aggregate mode. The error persists without producing  the list of ranked edges and the gene influence files. Attached are the zipped files so you can reproduce the issue.
gene_list.mat.zip
[X_SCODE_data.mat.zip](https://github.com/gitter-lab/SINGE/files/9547679/X_SCODE_data.mat.zi
AdjMats.zip
p)
With regards to running SINGE in a Cluster in parallel. I will be using docker and a Sonic HPC Cluster with the following characteristics. (https://www.ucd.ie/itservices/ourservices/researchit/researchcomputing/sonichpc/
In short, I will be able to use up to 48 cores, 50GB of file storage and 1.5TB of RAM.
It would be nice to hear suggestions on how to adapt the example in SINGE-supplementary  to run on Sonic HPC. Is it possible to run several datasets? Should the input data structure (.mat files) be modified?  How should the hyperparameters be specified now? Is there any wrapper script example to see how to run it with docker?

X_SCODE_data.mat.zip

@atuldeshpande I just tried to run aggregate mode on the 4 Adjacency matrixes through Matlab code and it did produce the Gene Influence and Ranked Edge List output files. Thanks for the suggestion.


User/aeloros/instancing

What is a roadmap?

@jonwis Can you delete this? I reported this spam bot multiple times but GitHub is dragging their feet.


ci: allow failures on 3.11

related: https://github.com/iterative/dvc-data/pull/98

Codecov Report

Merging #95 (bf5eac1) into main (c15141b) will decrease coverage by 0.74%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #95      +/-   ##
==========================================
- Coverage   66.07%   65.32%   -0.75%
==========================================
  Files          39       39
  Lines        2411     2411
  Branches      378      286      -92
==========================================
- Hits         1593     1575      -18
- Misses        789      808      +19
+ Partials       29       28       -1

Impacted Files
Coverage Δ

src/dvc_objects/fs/system.py
63.23% <0.00%> (-20.59%)
:arrow_down:

tests/test_reflink.py
87.50% <0.00%> (-12.50%)
:arrow_down:

Continue to review full report at Codecov.

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


[fix] update to work w/ latest prom client code

Fixes: #40
Prom client code changed the Counter Set() method to Add()

Didn't Set() set the absolute value while Add() increments the value?
https://github.com/prometheus/client_golang/commit/2fee50beaa152342e8347c41edf2202c3bd5f858#commitcomment-19628916 contains an explanation of the proper migration.

ah, breaking change introduced. Looks like mongodb_exporter will need to either vendor prometheus client at v0.8.0 or take on a larger refactor


Can't install on OroCommerce

I try to install this bundle on OroCommerce application, I have follow the instruction for single client but I have always [RuntimeException]                                                                      [Symfony\Component\Config\Definition\Exception\InvalidConfigurationException]             The child node "key" at path "sendinblue_api.clients.default" must be configured.
when i try to clear cache
php app/console cache:clear

Could you paste a sample of your configuration?

I just add this :
sendinblue_api:         endpoints:             - smtp         key: xkeysib-********
to the parameter.yml file in app/config

You're missing the sendinblue_api node. Also you need to set key and endpoints as confguration values, not parameters.

Just a typo error, i had define sendinblue_api: but certainly as parameters not as configuration value


Feature request: support buffer pooling

The LZ4Stream constructor accepts a "blockSize" parameter (defaulting to 1MB), which I assume results in an internal buffer of that size being created. If so, it would be great if an overload to this constructor could be provided where a buffer (byte array) could be provided to the LZ4Stream to use. This would allow us to allocate the buffer from a buffer pool (e.g. the ArrayPool class in the System.Buffers library) and return the buffer to the pool once the LZ4Stream is disposed. This would greatly reduce the stress on the garbage collector.

Having now looked through the LZ4Stream.cs source code, I suspect the best way to make use of a buffer pool is to pass a buffer pool into the LZ4Stream constructor so that when it needs to allocate a new buffer, it can uses the given buffer pool.
It would be important for the LZ4Stream class to support different buffer pool implementations, which could be achieved by defining an IBufferPool interface in the LZ4 library with the following two methods:

Allocate(int bufferSize)
Release(byte[] buffer)

The LZ4Stream class would then accept an IBufferPool optional parameter. If non-null, the LZ4Stream class would use the buffer pool to allocate any buffers it requires, releasing the buffers back to the pool as they are no longer needed (including on LZ4Stream.Dispose).
Using a buffer pool for internal LZ4Stream buffers not only vastly reduces strain on the garbage collector, it also greatly improves memory locality (because buffers are reused), which makes much better use of the CPU caches.
The performance impact is significant when using the LZ4Stream for compressing/decompressing moderately-sized data many times (rather than one long stream of data) - such as compressing/decompressing messages.
I've tested it out and found that the aggregate throughput I observed compressing and then decompressing a 100KByte byte array 50,000 times doubled on a single core from 200MByte/s to 400MByte/sec.

Please note, I will be wokring on this in NEXT version of K4os.Compression.LZ4. Please migrate to new library.


make stats flush interval configurable

Makes stats flush interval configurable. See https://github.com/istio/istio/issues/16928
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[X ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@ramaraochavali: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio
463bf5a1fd8f0b933187c3a7e80305ab02f04593
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio
167a9b6c6fcde1fbcc815e53eb47e5392e914132
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio
167a9b6c6fcde1fbcc815e53eb47e5392e914132
link
/test lint_istio

integ-mixer-k8s-tests_istio
167a9b6c6fcde1fbcc815e53eb47e5392e914132
link
/test integ-mixer-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/lgtm
/approve
Thanks!

@howardjohn @linsun @geeknoid can you please take a look at this?

could this be accomplished using our custom bootstrap overrides? see samples/custom-bootstrap

One doubt: how does this allow users configuring? Shouldn't you update injection template as well?

@hzxuzhonghu Yeah. Thanks for that. I missed to add it template. Fixed now. Can you PTAL?

@howardjohn It could probably be accomplished via custom bootstrap. But I think this is important enough config to be part of main bootstrap.

Did you try using the custom bootstrap overrides?
On Wed, Sep 11, 2019, 9:13 PM Rama Chavali<EMAIL_ADDRESS>wrote:

@hzxuzhonghu https://github.com/hzxuzhonghu Yeah. Thanks for that. I
missed to add it template. Fixed now. Can you PTAL?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/16929?email_source=notifications&email_token=AAEYGXOKK4IJXZRUE2TTXKLQJG6XBA5CNFSM4IU2NX5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6QS32I#issuecomment-530656745,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEYGXJQB7XZSVBT6PZIH73QJG6XBANCNFSM4IU2NX5A
.

I have n't tried that yet but as I mentioned I think it is important enough config to be part of main. What do you think?

@ramaraochavali: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
6e03a83ae2603c96c6cf1e41699866fb5a2f67e1
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
6e03a83ae2603c96c6cf1e41699866fb5a2f67e1
link
/test unit-tests_istio

racetest_istio
6e03a83ae2603c96c6cf1e41699866fb5a2f67e1
link
/test racetest_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
6e03a83ae2603c96c6cf1e41699866fb5a2f67e1
link
/test unit-tests_istio

racetest_istio
6e03a83ae2603c96c6cf1e41699866fb5a2f67e1
link
/test racetest_istio

codecov_istio
6e03a83ae2603c96c6cf1e41699866fb5a2f67e1
link
/test codecov_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

racetest_istio
6e03a83ae2603c96c6cf1e41699866fb5a2f67e1
link
/test racetest_istio

codecov_istio
6e03a83ae2603c96c6cf1e41699866fb5a2f67e1
link
/test codecov_istio

unit-tests_istio
97040afb3a88bbe13d2154c3f3fe83448ea064f0
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

codecov_istio
6e03a83ae2603c96c6cf1e41699866fb5a2f67e1
link
/test codecov_istio

unit-tests_istio
97040afb3a88bbe13d2154c3f3fe83448ea064f0
link
/test unit-tests_istio

racetest_istio
97040afb3a88bbe13d2154c3f3fe83448ea064f0
link
/test racetest_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
97040afb3a88bbe13d2154c3f3fe83448ea064f0
link
/test unit-tests_istio

racetest_istio
97040afb3a88bbe13d2154c3f3fe83448ea064f0
link
/test racetest_istio

codecov_istio
97040afb3a88bbe13d2154c3f3fe83448ea064f0
link
/test codecov_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test unit-tests_istio

/test racetest_istio

/test codecov_ist

@ramaraochavali: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
97040afb3a88bbe13d2154c3f3fe83448ea064f0
link
/test unit-tests_istio

racetest_istio
97040afb3a88bbe13d2154c3f3fe83448ea064f0
link
/test racetest_istio

codecov_istio
97040afb3a88bbe13d2154c3f3fe83448ea064f0
link
/test codecov_istio

integ-mixer-k8s-tests_istio
97040afb3a88bbe13d2154c3f3fe83448ea064f0
link
/test integ-mixer-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

racetest_istio
97040afb3a88bbe13d2154c3f3fe83448ea064f0
link
/test racetest_istio

codecov_istio
97040afb3a88bbe13d2154c3f3fe83448ea064f0
link
/test codecov_istio

integ-mixer-k8s-tests_istio
97040afb3a88bbe13d2154c3f3fe83448ea064f0
link
/test integ-mixer-k8s-tests_istio

unit-tests_istio
97040afb3a88bbe13d2154c3f3fe83448ea064f0
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

codecov_istio
97040afb3a88bbe13d2154c3f3fe83448ea064f0
link
/test codecov_istio

integ-mixer-k8s-tests_istio
97040afb3a88bbe13d2154c3f3fe83448ea064f0
link
/test integ-mixer-k8s-tests_istio

unit-tests_istio
97040afb3a88bbe13d2154c3f3fe83448ea064f0
link
/test unit-tests_istio

racetest_istio
97040afb3a88bbe13d2154c3f3fe83448ea064f0
link
/test racetest_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

codecov_istio
97040afb3a88bbe13d2154c3f3fe83448ea064f0
link
/test codecov_istio

integ-mixer-k8s-tests_istio
97040afb3a88bbe13d2154c3f3fe83448ea064f0
link
/test integ-mixer-k8s-tests_istio

racetest_istio
97040afb3a88bbe13d2154c3f3fe83448ea064f0
link
/test racetest_istio

unit-tests_istio
4060a4884c92ab598bfb93d721237819c8c1aa94
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

codecov_istio
97040afb3a88bbe13d2154c3f3fe83448ea064f0
link
/test codecov_istio

integ-mixer-k8s-tests_istio
97040afb3a88bbe13d2154c3f3fe83448ea064f0
link
/test integ-mixer-k8s-tests_istio

unit-tests_istio
4060a4884c92ab598bfb93d721237819c8c1aa94
link
/test unit-tests_istio

racetest_istio
4060a4884c92ab598bfb93d721237819c8c1aa94
link
/test racetest_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
97040afb3a88bbe13d2154c3f3fe83448ea064f0
link
/test integ-mixer-k8s-tests_istio

unit-tests_istio
4060a4884c92ab598bfb93d721237819c8c1aa94
link
/test unit-tests_istio

racetest_istio
4060a4884c92ab598bfb93d721237819c8c1aa94
link
/test racetest_istio

codecov_istio
4060a4884c92ab598bfb93d721237819c8c1aa94
link
/test codecov_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
4060a4884c92ab598bfb93d721237819c8c1aa94
link
/test unit-tests_istio

racetest_istio
4060a4884c92ab598bfb93d721237819c8c1aa94
link
/test racetest_istio

codecov_istio
4060a4884c92ab598bfb93d721237819c8c1aa94
link
/test codecov_istio

integ-new-install-k8s-tests_istio
7ebc997f51e2bd0aca769213a474725681206ae8
link
/test integ-new-install-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-new-install-k8s-tests_istio

@howardjohn How does the custom bootstrap work for bare metal cases?

/test integ-new-install-k8s-tests_istio

@ramaraochavali the custom bootstrap is just a file pointing to by an environment variable, so I don't see why it wouldn't work on bare metal (although I haven't tried it -- if there are problems opening an issue/PR would be welcomed).
I am not strongly against this if its something that would be useful, especially for mixerv2 - if @mandarjog or @douglas-reid maybe want to take a look

@howardjohn  Thanks. We will take a look at custom bootstrap for bare metal and get back to you if we see any issues.
@douglas-reid @mandarjog Do you think this would be in general?

/test integ-new-install-k8s-tests_istio

@ramaraochavali: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio
7c9787c625c3819136ac306475cf45dc8d9db6d1
link
/test integ-new-install-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali I think flush interval is a useful config setting, but we should not add it as command line args. There are already too many and it causes upgrade headaches.
I want bootstrap to have access to values without args, and working in a proposal.
You can either wait until that is available and use custom bootstrap till that time.
Or add an env var, which does not break upgrades.

@mandarjog Thank you. Do you have any time lines in mind for the new proposal?

@howardjohn  on a related note about custom bootstrap, what do you think about exposing a helm value that points the bootstrap override that sidecar injector can use? This has the benefit of not expecting every service to have that annotation and can be controlled at mesh level. If a service has the annotation, we could prefer that over helm value.

That sounds good to me

@ramaraochavali: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio
7c9787c625c3819136ac306475cf45dc8d9db6d1
link
/test integ-new-install-k8s-tests_istio

lint_istio
cd37df3460257a49619c5f91b906dd9df8665346
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio
7c9787c625c3819136ac306475cf45dc8d9db6d1
link
/test integ-new-install-k8s-tests_istio

lint_istio
cd37df3460257a49619c5f91b906dd9df8665346
link
/test lint_istio

racetest_istio
cd37df3460257a49619c5f91b906dd9df8665346
link
/test racetest_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio
7c9787c625c3819136ac306475cf45dc8d9db6d1
link
/test integ-new-install-k8s-tests_istio

lint_istio
cd37df3460257a49619c5f91b906dd9df8665346
link
/test lint_istio

racetest_istio
cd37df3460257a49619c5f91b906dd9df8665346
link
/test racetest_istio

unit-tests_istio
cd37df3460257a49619c5f91b906dd9df8665346
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio
7c9787c625c3819136ac306475cf45dc8d9db6d1
link
/test integ-new-install-k8s-tests_istio

lint_istio
cd37df3460257a49619c5f91b906dd9df8665346
link
/test lint_istio

racetest_istio
cd37df3460257a49619c5f91b906dd9df8665346
link
/test racetest_istio

unit-tests_istio
cd37df3460257a49619c5f91b906dd9df8665346
link
/test unit-tests_istio

codecov_istio
cd37df3460257a49619c5f91b906dd9df8665346
link
/test codecov_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

racetest_istio
cd37df3460257a49619c5f91b906dd9df8665346
link
/test racetest_istio

unit-tests_istio
cd37df3460257a49619c5f91b906dd9df8665346
link
/test unit-tests_istio

codecov_istio
cd37df3460257a49619c5f91b906dd9df8665346
link
/test codecov_istio

lint_istio
79aa75e5b9571f4a0a4d62236fbff4c37da6aba0
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
cd37df3460257a49619c5f91b906dd9df8665346
link
/test unit-tests_istio

codecov_istio
cd37df3460257a49619c5f91b906dd9df8665346
link
/test codecov_istio

lint_istio
79aa75e5b9571f4a0a4d62236fbff4c37da6aba0
link
/test lint_istio

racetest_istio
79aa75e5b9571f4a0a4d62236fbff4c37da6aba0
link
/test racetest_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

codecov_istio
cd37df3460257a49619c5f91b906dd9df8665346
link
/test codecov_istio

lint_istio
79aa75e5b9571f4a0a4d62236fbff4c37da6aba0
link
/test lint_istio

racetest_istio
79aa75e5b9571f4a0a4d62236fbff4c37da6aba0
link
/test racetest_istio

unit-tests_istio
79aa75e5b9571f4a0a4d62236fbff4c37da6aba0
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio
79aa75e5b9571f4a0a4d62236fbff4c37da6aba0
link
/test lint_istio

racetest_istio
79aa75e5b9571f4a0a4d62236fbff4c37da6aba0
link
/test racetest_istio

unit-tests_istio
79aa75e5b9571f4a0a4d62236fbff4c37da6aba0
link
/test unit-tests_istio

codecov_istio
79aa75e5b9571f4a0a4d62236fbff4c37da6aba0
link
/test codecov_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn Thanks. Will push a PR for custom bootstrap helm value.

@mandarjog  move stats flush interval to env var.

@ramaraochavali: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

racetest_istio
79aa75e5b9571f4a0a4d62236fbff4c37da6aba0
link
/test racetest_istio

unit-tests_istio
79aa75e5b9571f4a0a4d62236fbff4c37da6aba0
link
/test unit-tests_istio

codecov_istio
79aa75e5b9571f4a0a4d62236fbff4c37da6aba0
link
/test codecov_istio

lint_istio
db42540110b904b5fbc960e63afc16e8bd3ed731
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

codecov_istio
79aa75e5b9571f4a0a4d62236fbff4c37da6aba0
link
/test codecov_istio

lint_istio
db42540110b904b5fbc960e63afc16e8bd3ed731
link
/test lint_istio

e2e-simpleTests_istio
db42540110b904b5fbc960e63afc16e8bd3ed731
link
/test e2e-simpleTests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

codecov_istio
79aa75e5b9571f4a0a4d62236fbff4c37da6aba0
link
/test codecov_istio

e2e-simpleTests_istio
db42540110b904b5fbc960e63afc16e8bd3ed731
link
/test e2e-simpleTests_istio

lint_istio
d91dee4508937b6137b5db53390429ddd5f20e73
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio
d91dee4508937b6137b5db53390429ddd5f20e73
link
/test lint_istio

integ-mixer-k8s-tests_istio
d91dee4508937b6137b5db53390429ddd5f20e73
link
/test integ-mixer-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@mandarjog Do you have any timelines for the new proposal? If it is in the near future, we can probably wait - otherwise I have changed it to use Env var. Please take look.

@ramaraochavali: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

racetest_istio
38a5709c9957c438e6f7d0a06838bed97fdbdef6
link
/test racetest

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

racetest_istio
38a5709c9957c438e6f7d0a06838bed97fdbdef6
link
/test racetest

integ-new-install-k8s-tests_istio
38a5709c9957c438e6f7d0a06838bed97fdbdef6
link
/test integ-new-install-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

racetest_istio
38a5709c9957c438e6f7d0a06838bed97fdbdef6
link
/test racetest

integ-new-install-k8s-tests_istio
38a5709c9957c438e6f7d0a06838bed97fdbdef6
link
/test integ-new-install-k8s-tests

integ-mixer-k8s-tests_istio
38a5709c9957c438e6f7d0a06838bed97fdbdef6
link
/test integ-mixer-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

closing this PR for now


app/Http/Controllers/Auth/RegisterController.php Class 'App\User' not found

use App\User;
This Line, should be changed into "App\Models\User;" ?

谢谢了


Helm release (a CR release) is automatically purged immediately after created.

Output of helm version:
version.BuildInfo{Version:"v3.2.3", GitCommit:"8f832046e258e2cb800894579b1b3b50c2d83492", GitTreeState:"clean", GoVersion:"go1.13.12"}

Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"14+", GitVersion:"v1.14.7-eks-1861c5", GitCommit:"1861c597586f84f1498a9f2151c78d8a6bf47814", GitTreeState:"clean", BuildDate:"2019-09-24T22:12:08Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"15+", GitVersion:"v1.15.11-eks-af3caf", GitCommit:"af3caf6136cd355f467083651cc1010a499f59b1", GitTreeState:"clean", BuildDate:"2020-03-27T21:51:36Z", GoVersion:"go1.12.17", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform (AKS, GKE, Minikube etc.):  EKS
Describe the bug
Helm release is automatically purged immediately after created.
To Reproduce
Steps to reproduce the behaviour:
0. What's your setup?
kubectl apply -f https://raw.githubusercontent.com/fluxcd/helm-operator/1.1.0/deploy/crds.yaml
kubectl create ns flux
helm upgrade -i helm-operator fluxcd/helm-operator \
    --namespace flux \
    --set helm.versions=v3

Developed a chart named helm-release which mange the HelmRelase templates, and upload the chart to my own chart repo myrepo
Run helm template command to verify the generated templates

# helm template default-redis-cluster xcloudiq/helm-release -n ops7-r7
---
# Source: helm-release/templates/release.yaml
apiVersion: helm.fluxcd.io/v1
kind: HelmRelease
metadata:
  name: default-redis-cluster
  namespace: ops7-r7
spec:
  releaseName: default-redis-cluster
  chart:

    name: default-redis-cluster
    repository: <my-private-repo> #hide
    version: ~5.0.6
  valuesFrom:
  - configMapKeyRef:
      name: global
      key: global.yaml
  - configMapKeyRef:
      name: default-redis-cluster
      key: default-redis-cluster.yaml
      optional: true

Use helm install to deploy the release

helm  install default-redis-cluster myrepo/helm-release -n ops7-r7

The target resources (helmfile, pod, cm, etc) were created and purged immediately

# kubectl -n ops7-r7 get pod
NAME                      READY   STATUS        RESTARTS   AGE
default-redis-cluster-0   0/1     Terminating   0          2s
default-redis-cluster-1   0/1     Terminating   0          2s
default-redis-cluster-2   0/1     Terminating   0          2s

If I run command helm template default-redis-cluster xcloudiq/helm-release -n ops7-r7 | kubectl apply -f -, the target resources are created successfully

Expected behavior
The target resrouces (helmfile, pod, cm, etc) should be created and persistent
Logs
{"caller":"release.go:75","component":"release","helmVersion":"v3","info":"starting sync run","release":"default-redis-cluster","resource":"ops7-r7:helmrelease/default-redis-cluster","targetNamespace":"ops7-r7","ts":"2020-06-15T07:28:16.434451815Z"}
{"action":"upgrade","caller":"release.go:289","component":"release","helmVersion":"v3","info":"running upgrade","release":"default-redis-cluster","resource":"ops7-r7:helmrelease/default-redis-cluster","targetNamespace":"ops7-r7","ts":"2020-06-15T07:28:16.704545708Z"}
{"caller":"helm.go:69","component":"helm","info":"preparing upgrade for default-redis-cluster","release":"default-redis-cluster","targetNamespace":"ops7-r7","ts":"2020-06-15T07:28:16.731833594Z","version":"v3"}
{"caller":"helm.go:69","component":"helm","info":"resetting values to the chart's original version","release":"default-redis-cluster","targetNamespace":"ops7-r7","ts":"2020-06-15T07:28:16.736212656Z","version":"v3"}
{"caller":"helm.go:69","component":"helm","info":"performing update for default-redis-cluster","release":"default-redis-cluster","targetNamespace":"ops7-r7","ts":"2020-06-15T07:28:16.973515848Z","version":"v3"}
{"caller":"helm.go:69","component":"helm","info":"creating upgraded release for default-redis-cluster","release":"default-redis-cluster","targetNamespace":"ops7-r7","ts":"2020-06-15T07:28:17.000530661Z","version":"v3"}
{"caller":"helm.go:69","component":"helm","info":"checking 5 resources for changes","release":"default-redis-cluster","targetNamespace":"ops7-r7","ts":"2020-06-15T07:28:17.01316818Z","version":"v3"}
{"caller":"helm.go:69","component":"helm","info":"Created a new ConfigMap called \"default-redis-cluster-config\" in ops7-r7\n","release":"default-redis-cluster","targetNamespace":"ops7-r7","ts":"2020-06-15T07:28:17.020775895Z","version":"v3"}
{"caller":"helm.go:69","component":"helm","info":"Created a new ConfigMap called \"default-redis-cluster-script\" in ops7-r7\n","release":"default-redis-cluster","targetNamespace":"ops7-r7","ts":"2020-06-15T07:28:17.029159015Z","version":"v3"}
{"caller":"helm.go:69","component":"helm","info":"Created a new Service called \"default-redis-cluster\" in ops7-r7\n","release":"default-redis-cluster","targetNamespace":"ops7-r7","ts":"2020-06-15T07:28:17.04425402Z","version":"v3"}
{"caller":"helm.go:69","component":"helm","info":"Created a new Service called \"default-redis-cluster-headless\" in ops7-r7\n","release":"default-redis-cluster","targetNamespace":"ops7-r7","ts":"2020-06-15T07:28:17.052151143Z","version":"v3"}
{"caller":"helm.go:69","component":"helm","info":"Created a new StatefulSet called \"default-redis-cluster\" in ops7-r7\n","release":"default-redis-cluster","targetNamespace":"ops7-r7","ts":"2020-06-15T07:28:17.061530735Z","version":"v3"}
{"caller":"helm.go:69","component":"helm","info":"Deleting \"default-redis-cluster\" in ops7-r7...","release":"default-redis-cluster","targetNamespace":"ops7-r7","ts":"2020-06-15T07:28:17.061591798Z","version":"v3"}
{"caller":"helm.go:69","component":"helm","info":"updating status for upgraded release for default-redis-cluster","release":"default-redis-cluster","targetNamespace":"ops7-r7","ts":"2020-06-15T07:28:17.080548975Z","version":"v3"}
{"caller":"helm.go:69","component":"helm","info":"uninstall: Deleting default-redis-cluster","release":"default-redis-cluster","targetNamespace":"ops7-r7","ts":"2020-06-15T07:28:17.084303263Z","version":"v3"}
{"caller":"release.go:309","component":"release","helmVersion":"v3","info":"upgrade succeeded","phase":"upgrade","release":"default-redis-cluster","resource":"ops7-r7:helmrelease/default-redis-cluster","revision":"~5.0.6","targetNamespace":"ops7-r7","ts":"2020-06-15T07:28:17.123988486Z"}
{"caller":"helm.go:69","component":"helm","info":"Starting delete for \"default-redis-cluster-headless\" Service","release":"default-redis-cluster","targetNamespace":"ops7-r7","ts":"2020-06-15T07:28:17.224856067Z","version":"v3"}
{"caller":"helm.go:69","component":"helm","info":"Starting delete for \"default-redis-cluster\" Service","release":"default-redis-cluster","targetNamespace":"ops7-r7","ts":"2020-06-15T07:28:17.224875812Z","version":"v3"}
{"caller":"helm.go:69","component":"helm","info":"Starting delete for \"default-redis-cluster\" StatefulSet","release":"default-redis-cluster","targetNamespace":"ops7-r7","ts":"2020-06-15T07:28:17.253146166Z","version":"v3"}
{"caller":"helm.go:69","component":"helm","info":"Starting delete for \"default-redis-cluster-config\" ConfigMap","release":"default-redis-cluster","targetNamespace":"ops7-r7","ts":"2020-06-15T07:28:17.262206535Z","version":"v3"}
{"caller":"helm.go:69","component":"helm","info":"Starting delete for \"default-redis-cluster-script\" ConfigMap","release":"default-redis-cluster","targetNamespace":"ops7-r7","ts":"2020-06-15T07:28:17.262206474Z","version":"v3"}
{"caller":"helm.go:69","component":"helm","info":"purge requested for default-redis-cluster","release":"default-redis-cluster","targetNamespace":"ops7-r7","ts":"2020-06-15T07:28:17.272232084Z","version":"v3"}
{"caller":"release.go:326","component":"release","helmVersion":"v3","phase":"annotate","release":"default-redis-cluster","resource":"ops7-r7:helmrelease/default-redis-cluster","targetNamespace":"ops7-r7","ts":"2020-06-15T07:28:17.277457789Z","warning":"failed to annotate release resources: configmap/default-redis-cluster-script annotated\nError from server (NotFound): services \"default-redis-cluster\" not found\nError from server (NotFound): services \"default-redis-cluster-headless\" not found\nError from server (NotFound): statefulsets.apps \"default-redis-cluster\" not found\nError from server (NotFound): configmaps \"default-redis-cluster-config\" not found\n"}

Sorry, it turns out a configuration issue


npm install worked instead of expo install for Expo

Environment

Dev OS: [Win11]
Expo SDK 46

Steps to reproduce
The Expo installation page says to run expo install rnmapbox/maps#main but this doesn't work, since it fails to find the module and generates a broken package-lock.json entry. Maybe because this command is expected to work only for Expo SDK modules?
Doing npm install rnmapbox/maps#main worked fine instead.
Side note. I guess the example where you say to configure MapBox Access Token should have either mapbox or mapbox-gl as  RNMapboxMapsImpl's property value.

@giohappy can you please send more details?!
I don't have a windows machine, but on my machine expo install rnmapbox/maps#main works just fine:
npx expo install rnmapbox/maps#main
› Installing 1 other package using Yarn
> yarn add rnmapbox/maps#main
yarn add v1.22.18

@mfazekas have you checked the package.json afterwards? The commands seems to run fine but produces "undefined": "rnmapbox/maps#main" in the package.json. I can reproduce with npx expo install rnmapbox/maps#main and expo install rnmapbox/maps#main on macOS.

@KiwiKilian interesting, is seems to be ok for with yarn, but could reproduce with npm. Filed a bug to expo repo about it.
https://github.com/expo/expo-cli/issues/4545

@mfazekas didn't know about the --init npm/yarn and probably just picks npm in my project...


unama

sempreunama.com.br

@Maihos I am sorry, the domain sempreunama.com.br is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Program. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).


1.2.0-SNAPSHOT appears to be broken

Following the toString() changes in #1273 , it looks like the runtime-jvm artifact wasn't updated correctly in the published snapshot build.  The Query class seems to be missing the newly added parameters, causing build failures.
I also noticed that when I specify explicit snapshot versions for all the SQLDelight dependencies (ie. coroutines-extensions-jvm-1.2.0-20190518.003521-10 instead of coroutines-extensions-jvm-1.2.0-SNAPSHOT), the build fails because it can't find 1.2.0-SNAPSHOT for sqldelight-runtime-jvm and sqldelight-coroutines-extensions-jvm.
ERROR: Failed to resolve: sqldelight-coroutines-extensions-jvm-1.2.0-SNAPSHOT
Affected Modules: app

ERROR: Failed to resolve: sqldelight-runtime-jvm-1.2.0-SNAPSHOT
Affected Modules: app

I noticed that the Sonatypes repository has both "sqldelight-runtime-" and "runtime-" artifacts.  The "sqldelight-runtime-*" ones appear to be older, but is it possible something is still looking for those dependencies?
As far as environment, I'm building an Android only app on Windows with Android Studio 3.5 Beta 4.  I have the following dependencies in build.gradle:
implementation 'com.squareup.sqldelight:runtime-jvm:1.2.0-20190610.150659-39'
implementation 'com.squareup.sqldelight:android-driver:1.2.0-20190518.003803-43'
implementation 'com.squareup.sqldelight:rxjava2-extensions:1.2.0-20190518.003812-43'
implementation 'com.squareup.sqldelight:coroutines-extensions:1.2.0-20190518.003524-10'
implementation 'com.squareup.sqldelight:coroutines-extensions-jvm:1.2.0-20190518.003521-10'

We publish from two build machines and it may have broke. Can look later
today.
On Wed, Jun 12, 2019 at 10:00 AM Erik Christensen<EMAIL_ADDRESS>wrote:

Following the toString() changes in #1273
https://github.com/square/sqldelight/pull/1273 , it looks like the
runtime-jvm artifact wasn't updated correctly in the published snapshot
build. The Query class seems to be missing the newly added parameters,
causing build failures.
I also noticed that when I specify explicit snapshot versions for all the
SQLDelight dependencies (ie.
coroutines-extensions-jvm-1.2.0-20190518.003521-10 instead of
coroutines-extensions-jvm-1.2.0-SNAPSHOT), the build fails because it can't
find 1.2.0-SNAPSHOT for sqldelight-runtime-jvm and
sqldelight-coroutines-extensions-jvm.
ERROR: Failed to resolve: sqldelight-coroutines-extensions-jvm-1.2.0-SNAPSHOT
Affected Modules: app
ERROR: Failed to resolve: sqldelight-runtime-jvm-1.2.0-SNAPSHOT
Affected Modules: app
I noticed that the Sonatypes repository has both "sqldelight-runtime-" and
"runtime-" artifacts. The "sqldelight-runtime-*" ones appear to be older,
but is it possible something is still looking for those dependencies?
As far as environment, I'm building an Android only app on Windows with
Android Studio 3.5 Beta 4. I have the following dependencies in
build.gradle:
implementation 'com.squareup.sqldelight:runtime-jvm:1.2.0-20190610.150659-39'
implementation 'com.squareup.sqldelight:android-driver:1.2.0-20190518.003803-43'
implementation 'com.squareup.sqldelight:rxjava2-extensions:1.2.0-20190518.003812-43'
implementation 'com.squareup.sqldelight:coroutines-extensions:1.2.0-20190518.003524-10'
implementation 'com.squareup.sqldelight:coroutines-extensions-jvm:1.2.0-20190518.003521-10'
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/square/sqldelight/issues/1366?email_source=notifications&email_token=AAAQIEISNDZ44OCJYU6XLTLP2D6Q5A5CNFSM4HXJJVDKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GZCJIWA,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAQIEIENW46RRL233UCHSTP2D6Q5ANCNFSM4HXJJVDA
.

This seems to be working okay now -- or at least I can build using 1.2.0-SNAPSHOT after clearing out my Gradle and build cache again.  Not sure what was going on.


only pad if necessary

The number 1 should not be formatted to 1.00 unless it was explicitly requested by adding a precision to the format specifier.

The existing behavior is as designed per the following properties (which may be specified for each locale):
numberFormat.decimals // number of decimal places normally shown
numberFormat.percent.decimals // number of decimal places normally shown
numberFormat.currency.decimals // number of decimal places normally shown
This means "n" together with a decimals value of 2 is an implicit "n2"

My pull request doesn't change the behavior of n2. It changes the behavior of n as a format specifier. I don't see a valid reason why 1 should become 1.00 when the format specifier is just n. For example before the pull request (in a locale where . = ,):
Globalize.format(1, "n") // 1,00

After:
Globalize.format(1, "n") // 1

As far as I'm aware padding has nothing to do with a locale, only currencies require a certain amount of decimal padding. If this is not the solution how then do I get the same behavior where the number is formatted as is. So 1 becomes '1' and 1.05 becomes '1.05'. In the current behavior I have to chose between:
Globalize.format(1, 'n') // 1,00
Globalize.format(1.05, 'n') // 1,05

or:
Globalize.format(1, 'n0') // 1
Globalize.format(1.05, 'n0') // 1

I want the number to be formatted as is:
Globalize.format(1, 'n') // 1
Globalize.format(1.05, 'n') // 1,05
Globalize.format(1.555555, 'n') // 1,555555

My pull request doesn't change the behavior of n2

I wasn't suggesting your pull request changes the behavior of n2. My point is that n on its own has a default value of decimals places to show (padding if needed), defined by each locale.

As far as I'm aware padding has nothing to do with a locale

See the following locales:
am-ET
am
ar-BH
ar-EG
ar-JO
ar-KW
ar-LY
ar-OM
ar-TN
id-ID
id
is-IS
is
ja-JP
ja
ko-KR
ko
ms-BN
ms-MY
ms
uz-Latn-UZ
us-Latn
uz
that have non-default (!=2) values for decimals. Sometimes each of number, percent, and currency have all the same value. Sometimes the values are different.

only currencies require a certain amount of decimal padding

Currencies do indeed require a certain amount of decimal padding, but there are default padding values for number and percent as well. This piece of culture info in Globalize comes from (and the behavior is consistent with) http://msdn.microsoft.com/en-us/library/system.globalization.numberformatinfo.numberdecimaldigits.aspx

If this is not the solution how then do I get the same behavior where the number is formatted as is.

Don't specify that you want the 'n' format
Globalize.format(1) // 1
Globalize.format(1.05) // 1,05
Globalize.format(1.555555) // 1,555555


Leveling up the README

Adds some helpful links and badges to the README
Tweaks the LICENSE so that github will hopefully automatically recognize its type (curl https://api.github.com/repos/voxel51/fiftyone/license currently says our license type is "other")
Adds some additional project classifiers to setup.py
Adds higher resolution icons for use in the docs
Adds citation instructions to the end of the README

LGTM! I know this wasn't the case before, but maybe the first line of the README should qualify FiftyOne as a computer vision ML tool.

👍 I replaced ML with CV

LGTM! I know this wasn't the case before, but maybe the first line of the README should qualify FiftyOne as a computer vision ML tool.

👍 I replaced ML with CV


2D Matrix Rotation

Fixes issue #128
Changes made
I have written an logic to rotate a matrix by 90 degrees in clockwise direction in C++
This is a small contribution as a part of GSSoC21.
I have tested the code and it works fine for every test case and included some sample test cases and also the complete explanation of the algorithm.

write all the comments just above the code

write all the comments just above the code

Yess I will do the required changes and update it.

Link our code with the appropriate folder,

I have done the requested changes. Please review it.

Link our code with the appropriate folder,

I have done the requested changes. Please review it.

Heyy, you need to update the required readme to update the code. Plz go through the guidelines and the pinned issues : )

Link our code with the appropriate folder,

I have done the requested changes. Please review it.

Heyy, you need to update the required readme to update the code. Plz go through the guidelines and the pinned issues : )

I have updated the readme. Please merge the branch if no further changes required.

Link our code with the appropriate folder,

I have done the requested changes. Please review it.

I have done the requested changes


Link ports Iperf3 TCP disconnection

Hello, i am rather new to raising git  issue, please tell me if i should modify anything to make this post better for you.
About a week ago i tried out the project with Yi-Tseng's simple l1switch p4 script on a VEP4600.
I have been able to get it to pass iperf3 UDP traffic through very close to line rate (1Gbs and 10Gbs).
But  with iperf3 TCP, for example, on sender's side:

After which the dpdk switch seems unable to continue passing traffic through, as the two connected hosts can't even ping each other anymore. This happens with scp file transfer as well.
I tried capturing packet at each end points. At the sender's side:

And at the receiver's side:

Is the point when the dpdk switch link is broken. Seems like the sender was sending way FASTER than the receiver could respond. At last sender resent the last segment that had been ACK by receiver, and then the link went down.
At this point i've tried all sorts of MTU combinations, reduced the cwnd windows, but the problem persists
What could be going on here? Is this something related to dpdk's mbuf???
Any input is very welcome, thank you in advance

After increasing the DPDK's "MEMPOOL" size, the problem seems to have been solved, no idea why though, i though it supposed to be a circular buffer.


Add SwiftyMenu to Awesome iOS List

Project URL
https://github.com/KarimEbrahemAbdelaziz/SwiftyMenu
Category
Menu
Description
Simple and Elegant Drop down menu for iOS 🔥💥
Why it should be included to awesome-ios (mandatory)
Because it's built with a unique feature that doesn't exist in most common DropDown menus in the list.
Checklist

[x] Has 50 Github stargazers or more
[x] Only one project/change is in this pull request
[x] Isn't an archived project
[x] Has more than one contributor
[x] Has unit tests, integration tests or UI tests
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 9 / tvOS 10 or later
[x] Supports Swift 4 or later
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

@lfarah could you take a look here, please ? :)

@lfarah Any updates ?

@simonmitchell Any updates ?

Hi @KarimEbrahemAbdelaziz! I’m not a contributor to this list I’m afraid so can’t help you out myself! I’m sure this will get looked at in due course ☺

Hey @KarimEbrahemAbdelaziz, thanks for contributing 🎉
Unfortunately, we cannot merge your PR yet because it doesn't contain unit tests.
Feel free to reopen when it's ready.

My bad. I didn't see the tests in your example.

@KarimEbrahemAbdelaziz Merged! Thanks.


Alertmanager error : failed to join cluster

What happened?
Running CRD alertmanager in replica=1
shows error in logs of alertmanager saying "failed to join cluster"
wrong arguments are passed to alertmanger
--cluster.peer=alertmanager-ml-0.alertmanager-operated:9094
where it says host --cluster.peer=alertmanager-ml-0.alertmanager-operated:9094 not found
actual name of the host is --cluster.peer=alertmanager-ml-0.alertmanager:9094
Did you expect to see something different?
expecting not to see the error in logs
How to reproduce it (as minimally and precisely as possible):
start alertmanager with replica = 1
Environment
OS: ubuntu:18.04.3

Prometheus Operator version:
Image:      quay.io/coreos/prometheus-operator:v0.39.0

Kubernetes version information:
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.1", GitCommit:"7879fc12a63337efff607952a323df90cdc7a335", GitTreeState:"clean", BuildDate:"2020-04-08T17:38:50Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.1", GitCommit:"7879fc12a63337efff607952a323df90cdc7a335", GitTreeState:"clean", BuildDate:"2020-04-08T17:30:47Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes cluster kind:
insert how you created your cluster: kops, bootkube, etc.
installed using kubeadm

Prometheus Operator Logs:

logs of CRD alertmanager
level=info ts=2020-07-20T04:42:37.529Z caller=main.go:231 msg="Starting Alertmanager" version="(version=0.20.0, branch=HEAD, revision=f74be0400a6243d10bb53812d6fa408ad71ff32d)" level=info ts=2020-07-20T04:42:37.529Z caller=main.go:232 build_context="(go=go1.13.5, user=root@00c3106655f8, date=20191211-14:13:14)" level=warn ts=2020-07-20T04:42:37.614Z caller=cluster.go:228 component=cluster msg="failed to join cluster" err="1 error occurred:\n\t* Failed to resolve alertmanager-ml-0.alertmanager-operated:9094: lookup alertmanager-ml-0.alertmanager-operated on <dns ip>: no such host\n\n" level=info ts=2020-07-20T04:42:37.614Z caller=cluster.go:230 component=cluster msg="will retry joining cluster every 10s"
Anything else we need to know?:

Can you upgrade to v0.40.0? https://github.com/coreos/prometheus-operator/pull/3233 is only available starting with that release.

Thank you. It is working now without errors.


Issue #132 Fixed

Summary:
Issue #132 is fixed by decoding the token from bytes to string so the string can concatenate.
Submitter checklist:

[x] CHANGELOG  N/A
[x] Documentation N/A

Merger checklist:

[x] ALL tests have passed
[x] Code Review is done
[x] Dependencies satisfied

Dependencies:

[x]

@peterdeme added suggested changes and test cases. please have a look.
If there is anything that I can do please let me know.
Thanks & Regards.

@ferhatelmas it requires your approval


Log file recreated every time

Problem 1. Log file is not used when running from IDE (log file has only 2 lines)
Problem 2. When running from jar, log file is recreated every time I run the app.

@m133225 can fix this one?

Does this mean that the old log messages are being overwritten?

Yes.

Can't seem to reproduce 1). Maybe deleting the possibly old config file will help.

When running from IDE, this is all I see in the log file.
Sep 28, 2016 4:15:25 PM seedu.address.storage.XmlAddressBookStorage readAddressBook
INFO: AddressBook file .\src\test\data\XmlAddressBookStorageTest\NonExistentFile.xml not found

But problem 2 is still there. Every time I start the app (whether it is from IDE or jar file), the file is wiped clean.

Confirmed from home comp. If you cannot reproduce this, it could be a Windows-only thing.

@lejolly can you help to check this on your Mac?

doesn't happen to me
does


Create create-template in AsyncAPI organization

Reason/Context
Stumbled upon this and thought it would be perfect for the generator. We could offer a way to use the init function which will allow people to more quickly setup new templates.
By creating create-template in the AsyncAPI scope we can do the following example commands:

npm init @asyncapi/template --react
npm init @asyncapi/template --nunjucks
npm init @asyncapi/template

Description
This will significantly speed up the process of creating new ones and make it more accessible for people. This is similar to what React have - https://github.com/facebook/create-react-app

I think we should follow the same direction that will be done with https://github.com/asyncapi/cli/pull/418

@derberg @jonaslagoni can I work on this?

yeah, but problem is not the implementation, we need a clear definition of the project that we would like to have generated with this new command. Some brainstorming session is kinda needed

Still Relevant 🤝

Still relevant 🤝

I want to work on this. :)

Hi @derberg @jonaslagoni I would love to work on this issue, actually I am developing a similar kind of npm package https://github.com/DhairyaMajmudar/majirya-cli
This package a CLI Tool which simplifies mern stack and T3 stack web development.

Hi @DhairyaMajmudar @AayushSaini101 was the first to express his interest in working on this issue.
Feel free to pick the other issues in the project.
Thanks

Sure looking forward to apply for an another issue, thank you : )

We can implement a command that is asyncapi init that will generate a template for the user, and we have already have template of template structure https://github.com/asyncapi/template-for-generator-templates we can simply use it @Amzani @Souvikns

/bounty

Bounty Issue's service comment
Text labels: bounty/2024-Q3, bounty/advanced, bounty/coding
First assignment to third-party contributors: 2024-06-21 00:00:00 UTC+12:00
End Of Life after: 2024-07-31 23:59:59 UTC-12:00
@asyncapi/bounty_team
The Bounty Program is not a Mentorship Program. The accepted level of Bounty Program Participants is Middle/Senior.
Third-party contributors should coherently articulate how they are going to approach the resolution process when expressing a desire to work on this Bounty Issue.

The current command to generate the glee project is asyncapi new glee --name , and we need to generate only for react engine template because it is more efficient. In that case, we can introduce the new command that is :
asyncapi new template --name .
and the structure of the template will be:
asyncapitemplate
-->template
------>index.js
--->package.json
Reference template format for react engine: https://www.asyncapi.com/docs/tools/generator/template-development.

Bounty Issue's Timeline

Complexity Level
Assignment Date (by GitHub)
Start Date (by BP Rules)
End Date (by BP Rules)
Draft PR Submission
Final PR Merge Start
Final PR Merge End

Advanced
2024-06-18
2024-07-01
2024-08-25
2024-07-21
2024-08-11
2024-08-25

Please note that the dates given represent deadlines, not specific dates, so if the goal is reached sooner, it's better.
Keep in mind the responsibility for violations of the Timeline.

@Amzani
Please confirm the technical resolution of this Bounty Issue or delegate this action to other Maintainers.

Since @Amzani is vacationing

@Souvikns, @Shurtu-gal, can one of you please confirm the technical resolution of this Bounty Issue?

@aeworxet @AayushSaini101 has resolved this issue by merging #1476.

Bounty Issue Is Completed 🎉
@AayushSaini101, please go to the AsyncAPI page on Open Collective and submit an invoice for USD 400.00 with the expense title Bounty cli#337, tag bounty, and full URL of this Bounty Issue in the description.


Accounts could not be created

Error count on CMD keeps rising even if we use fresh client token in config file. No accounts can be made even with PROXYLESS option. Problem may be in API.

solved with the new update.


In concurrency, it may be better to use patch rather than update in updating the rosources.

In Kubernetes, there are two ways to inform the API server to update the resources--UPDATE and PATCH.
UPDATE is a total replacement that will replace the resources in the API server with the object in memory.  So we need to add the mutex in development if we use concurrency in the controller otherwise we may lose the previous modifications.
PATCH is an incremental replacement that will only replace the properties added and the other contents will remain in the API server. In this way, we only need to add the mutex in several special situations such as counting the dataset in the specific node.
It may be more efficient.

closed by #877


Fix #136 Dot after return consistency

As this is just a bunch of dots, I think we can merge without further review.


add "Compile and link statically to a bundled C++ library" example

Use cc crate to compile and link statically to a bundled C++ library inside of a build.rs file.
Please note that it will be important to mention that this is a build time crate.
Most likely we will dedicate a separate (last) chapter like "build_time.md"
cc https://github.com/rust-lang-nursery/rust-cookbook/issues/236

That link is broken for me - did the crate change it's name to cc? It seems to refer to itself both as cc and cc-rs. I'm assuming this is the crate you are referring to

@j-haj darn they renamed again. I've updated te link. Thanks!

I would like to take it if it is ok ?

Is this issue still open for contributor ?

@hackertron unfortunately it already has a PR awaiting review (please note the "wip / claimed" label) but you ar welcome to chose any nonclaimed example or propose a new one!

merged!


Using nuxt with Javalin

Hello,
I'm making an app with a Javalin backend and i would like to have my frontend with the nuxt.js framework but hosted by javalin ? is it possible or am I bound to use Node for my frontend ?

Yes, you can use Javalin to host the frontend through staticFiles and spaRoot:
    config.staticFiles   // static files and webjars
    config.spaRoot       // single page application roots

This depends on how you intend to use Nuxt. If you just want to genere static assets then you can use Javalin to host the static resources and set up a SPA root to handle client side routing. If you want to use Nuxt for anything else such as SSR or other server component, you're stuck with Node I'm afraid :)

Okay, thanks a lot. I've did some research on SSR with javalin and saw Jte. So I'll use that.
Have a great day


Update the issue template

I notice most people filing issues are ignoring the issue template. I think we should try making it more concise, in particular asking people to provide a rnplay.org reproduction if it is possible.

@facebook-GitHub-bot shipit

@facebook-github-bot shipit


OPERATOR: Changing WATCH_NAMESPACE seems to cause controller to leak on delete

Bug description
Changing the operator controller WATCH_NAMESPACE to different that istio-system is causing some resources (pods and services) to not get cleaned up/pruned when the IOP is deleted.
[ ] Configuration Infrastructure
[ ] Docs
[x] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
The operator controller pod should cleanup it's resources properly regardless of where the IOP is located.
Steps to reproduce the bug
Failing scenario:

create ns ibm-operators #24073
./istio-1.6.0/bin/istioctl operator init  --operatorNamespace ibm-operators --istioNamespace ibm-operators
create iop in ns ibm-operators with just:

  apiVersion: install.istio.io/v1alpha1
  kind: IstioOperator
  metadata:
    name: istio
    namespace: ibm-operators
  spec:
    profile: default

wait for control plane to come up in istio-system
k delete iop -n ibm-operators istio
pods and services in istio-system ns are not cleaned up

Working scenario:

create ns istio-system
./istio-1.6.0/bin/istioctl operator init
create iop in ns istio-system with just:

  apiVersion: install.istio.io/v1alpha1
  kind: IstioOperator
  metadata:
    name: istio
    namespace:  istio-system
  spec:
    profile: default

wait for control plane to come up in istio-system
k delete iop -n  istio-system istio
pods and services in istio-system ns are cleaned up

Logs show a much shorter prune list for the failure case, but no obvious errors.
Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
How was Istio installed?
Environment where bug was observed (cloud vendor, OS, etc)

cc @sdake

Looks like this is cased by the finalizer removal conflict.
2020-05-31T05:51:10.862910Z	info	Reconciling IstioOperator
2020-05-31T05:51:10.863208Z	info	Deleting IstioOperator
2020-05-31T05:51:11.026353Z	info	conflict during finalizer removal, retrying
2020-05-31T05:51:11.030239Z	info	Could not remove finalizer from ibm-operators/istio due to conflict. Operation will be retried in next reconcile attempt
2020-05-31T05:51:11.030292Z	info	Reconciling IstioOperator

Oops, not actually caused by finalizer removal conflict, just by the namespace mismatch when prune the resources.

I faced same issue. I changed WATCH_NAMESPACE=""


tg-spam.log permission denied

Hi umputun,
I used docker-compose to deploy the application, and I see a warning
tg-spam    | 2024/03/24 11:09:18.928 [INFO]  user **** as spammer: {name: stopword, spam: false, details: not found}, {name: emoji, spam: false, details: 0/2}, {name: similarity, spam: true, details: 1.00/0.50}, {name: classifier, spam: true, details: probability of spam: 100.00%}, {name: cas, spam: false, details: record not found}, "Нужен человек для удаленного заработка. С вас, телефон и 2 часа свободного времени. Доход достойный. Для связи (+) в ЛС"
tg-spam    | 2024/03/24 11:09:18.928 [WARN]  can't write to log, can't open new logfile: open /srv/logs/tg-spam.log: permission denied

in container I see created folders  from root user:
/srv $ ls -la
total 14356
drwxr-xr-x    1 root     root          4096 Mar 24 11:07 .
drwxr-xr-x    1 root     root          4096 Mar 24 11:07 ..
drwxrwxr-x    2 app      app           4096 Mar 24 11:09 data
drwxr-xr-x    2 root     root          4096 Mar 24 11:07 logs
-rwxr-xr-x    1 root     root      14684160 Mar 24 07:22 tg-spam
/srv $ ps -a
PID   USER     TIME  COMMAND
    1 app       0:04 /srv/tg-spam
   22 app       0:00 /bin/sh
   30 app       0:00 ps -a

on host mashine folder ./logs created from root:
user@ubuntu-vm:~/tg-spam$ ls -la
total 20
drwxrwxr-x 3 user   user   4096 Mar 24 08:07 .
drwxr-x--- 8 user   user   4096 Mar 23 19:06 ..
-rw-r--r-- 1 user   user   2132 Mar 24 08:07 docker-compose.yml
-rw-r--r-- 1 user   user    638 Mar 23 20:49 .env
drwxr-xr-x 2 root root 4096 Mar 24 08:07 logs

# example of a compose file with server enabled, logging turned on and samples on named volume
services:
  tg-spam:
    image: umputun/tg-spam:latest # use :master tag for latest (unstable) version
    hostname: tg-spam
    user: app
    restart: always
    container_name: tg-spam
    deploy:
      resources:
        limits:
          cpus: '0.25'
          memory: 50M
      restart_policy:
        condition: on-failure
        max_attempts: 3
    logging: &default_logging
      driver: json-file
      options:
        max-size: "5m"
        max-file: "2"
    env_file:
      - .env
    volumes:
      - tg-data:/srv/data       # mount volume with samples and dynamic files
      - ./logs:/srv/logs        # mount logs location to host's ./log directory
    ports:
      - <IP_ADDRESS>:4080:8080
volumes:
  tg-data:

This one has nothing to do with tg-spam but rather a way docker-compose handles direction creation if one of the mounted dirs is missing. In this case, it will make the directory under the root. You can chown/chmod it and restart it. Or even better - before you run compose for the first time, make sure this directory is created under your user


Update Firebase functions compatible with version 1.0

The Firebase functions used(^0.5) is no longer compatible with firebase-tools. Hence the Firebase Functions which are written in index.js  needs to updated. This link is guide for the updating Firebase Functions from Beta to version 1.0

oh thanks @saipran7777 , Let me have a look

Hey @saipran7777 ,
Have you updated the functions to >1.0, If yes can you issue a Pull request,
I will merge into the project.
Thanks!

Hi @cpavnn,
I haven't updated the functions completely as I am new to Firebase Functions.  Can we have a voice call where you can run me through the code and after which I will try to update the Functions?

I have update the index.js following the Cloud Functions Migration Guide: Beta to version 1.0, the functions should run fine now


[v1] Restructure to plugin structure

With this PR adding plugins to the Rancher Dashboard, the Kubewarden UI should be restructured to follow this practice.

Moving to blocked as work on #68 continues, which will also involve #83

Moving to blocked until these issues can be resolved


Linter waring when using @useResult and a switch expression

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
I'm not sure if this is the right repo. I checked the Dart repo, but it seems I should create this thread here. Anyway, sorry if I'm wrong.
I see a linter warning if I use @useResult from meta.dart and the result of a method call annotated with it is returned from a switch expression. Please check the sample code and the screenshot. You can also check it in dartpad.dev.
Expected results
No linter warnings because the result is used and returned from the switch expression
Actual results
Unfortunately, a linter warning
Code sample
Code sample
import 'package:meta/meta.dart';

void main() {
  final some = JustAClass();
  final string = 'some';
  final result = switch (string) {
    'some' => some.isEven(),
    _ => false,
  };

  print(result);
}

class JustAClass {
  @useResult
  bool isEven() {
    return 42.isEven;
  }
}

Screenshots or Video

Screenshots / Video demonstration

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
[✓] Flutter (Channel stable, 3.10.5, on macOS 13.3.1 22E772610a darwin-arm64, locale en-AU)
    • Flutter version 3.10.5 on channel stable at /Users/wolltone/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 796c8ef792 (9 days ago), 2023-06-13 15:51:02 -0700
    • Engine revision 45f6e00911
    • Dart version 3.0.5
    • DevTools version 2.23.1

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
    • Android SDK at /Users/wolltone/Library/Android/sdk
    • Platform android-33, build-tools 33.0.1
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E300c
    • CocoaPods version 1.12.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[!] Android Studio
    • Android Studio at /Applications/Android Studio Preview.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Unable to find bundled Java version.
    • Try updating or re-installing Android Studio.

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[✓] IntelliJ IDEA Community Edition (version 2022.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.77.3)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.62.0

[✓] Connected device (3 available)
    • SM T630 (mobile) • R52T904GDXJ • android-arm64  • Android 13 (API 33)
    • macOS (desktop)  • macos       • darwin-arm64   • macOS 13.3.1 22E772610a darwin-arm64
    • Chrome (web)     • chrome      • web-javascript • Google Chrome 114.0.5735.133

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

Hi @vysotsky
meta is a Dart package. It's best suited to be opened on dart-lang/sdk for better support there. Thus, I will close this issue. If you disagree, please write in the comments and I will reopen it. Thank you!


Redact last applied configuration annotation from secrets

https://github.com/jetstack/preflight/pull/133 removes the secret data but leaves the last applied configuration in annotations. We need to also redact the last-applied-configuration annotation too since it contains secret data.

#152 will close this.


Pass props to Drawer

With react-native-router-flux v4.0.6, can i pass props into drawer so that my drawer is dynamic?
In v3, this worked
Actions.refresh({ key: 'drawer', open: true, isNotification: true });

With v4, is something like this possible?
Something like
Actions.drawerOpen({isNotification: true});

I'm having this issue, as are others. We are all waiting for a solution...
https://github.com/aksonov/react-native-router-flux/issues/3478
https://github.com/aksonov/react-native-router-flux/issues/3461
https://github.com/aksonov/react-native-router-flux/issues/3434


Controlling sources URL in inlined source maps (sourceRoot)

When inlining/embedding a source map into files, TypeScript compiler seems to always generate local file names, instead of paths e.g. matching what would end up in --outDir. tsc does not accept a sourceRoot, and does not use rootDir for the denormalization.
Ideally, I would like to pass in a sourceRoot of '' (empty string), so that all files end up with the complete path showing properly.

In particular, these are the problems we're facing:
error TS5052: Option 'sourceRoot' cannot be specified without specifying option 'sourceMap'.
error TS5053: Option 'sourceRoot' cannot be specified with option 'inlineSourceMap'.

@sheetalkamat ran into this yesterday. she should have a fix for it.

@mprobst can you give typescript@next a try.

@mhegazy: I'll be OOO next week, will look into this once I'm back.
Mohamed Hegazy<EMAIL_ADDRESS>schrieb am Do., 12. Nov. 2015 um
13:31 Uhr:

@mprobst https://github.com/mprobst can you give typescript@next a try.
—
Reply to this email directly or view it on GitHub
https://github.com/Microsoft/TypeScript/issues/5613#issuecomment-156242316
.


Made pipeline cfn template and code source-provider-agnostic

For now in some parts of pipeline CFN template and code, they are GitHub-specific, we should try to make them provider-agnostic.

We can re-create this task whenever we need to integrate with a new provider, resolving :)


feat: Added Performance Metrics for Android

Fixes #1285
Test Plan

How do we know the code works?

Performance metrics are uploaded for each Android run on physical device
Checklist

[x] Unit tested

Codecov Report

Merging #1292 into master will increase coverage by 0.08%.
The diff coverage is 94.44%.

@@             Coverage Diff              @@
##             master    #1292      +/-   ##
============================================
+ Coverage     79.69%   79.78%   +0.08%
- Complexity      726      735       +9
============================================
  Files           235      236       +1
  Lines          4522     4560      +38
  Branches        780      786       +6
============================================
+ Hits           3604     3638      +34
- Misses          516      517       +1
- Partials        402      405       +3

@Mergifyio rebase


WIP: Getting cleaner and less error prone HMM parsing ready

Hey @althonos
I'm not sure you remember, but we had a chat here about getting ModelAngelo's HMM parsing all done with pyhmmer's utilities: https://github.com/althonos/pyhmmer/issues/40
I think it is close right now, but it seems to be having an issue with the consensus part of the HMM. Could you take a look if you have a chance? I get the following error:
Traceback (most recent call last):
  File "/Users/kiarash/Desktop/code/cambridge/3dem_model_angelo/model-angelo/model_angelo/utils/aa_probs_to_hmm_new.py", line 93, in <module>
    hmm = aa_log_probs_to_hmm("test", probs, confidence)
  File "/Users/kiarash/Desktop/code/cambridge/3dem_model_angelo/model-angelo/model_angelo/utils/aa_probs_to_hmm_new.py", line 83, in aa_log_probs_to_hmm
    hmm.validate()
  File "pyhmmer/plan7.pyx", line 3220, in pyhmmer.plan7.HMM.validate
  File "pyhmmer/plan7.pyx", line 3246, in pyhmmer.plan7.HMM.validate
ValueError: Invalid HMM: p7H_CONS flag down, but consensus string is present

There's quite a bit of code, but what is really important is line 66 onwards. If you wish, you can see how we do it in aa_probs_to_hmm.py

Hi @jamaliki,
This error was caused by an outdated fix (althonos/pyhmmer#5) which was causing the consensus flag to be always set. Since the update to v0.10.0 it shouldn't be needed anymore (but I forgot to remove it), so I'l make a new patch release. Make sure to require at least PyHMMER v0.10.1 and you should be all set! :)

Thanks, worked like a charm @althonos! Going to do some testing but it should be the same. Are there any ways to write the composition row as well?

You don't have to set it manually, it will be computed from the HMM occupancy, just call HMM.set_composition after you're done filling it (typically right before HMM.validate). Then the consensus attribute of the HMM will be a VectorF that you're free to edit if you want.
You can also call HMM.set_consensus if you wish to build or record a consensus.


Document: Model card

I've recently encountered a paper advocating the idea of "Model Card". I personally like the idea. and because we have quite a lot of models in our repository, it's something we should consider.

See: https://arxiv.org/pdf/1810.03993.pdf

Example cards from Google
https://modelcards.withgoogle.com/

Model Card https://github.com/PyThaiNLP/pythainlp/wiki/Model-Card