ssh_keys_test image fix

No ubuntu image exists on quay, so changed it to kinvolk nginx repo.
This is to avoid docker pull limit errors.
Signed-off-by: knrt10<EMAIL_ADDRESS>See build https://yard.lokomotive-k8s.net/builds/43831 for more information

    util.go:311: test-ssh-keys-27lc4-44jfj/test-ssh-keys: sha512sum: /home/core/.ssh/authorized_keys: Permission denied
    util.go:311: test-ssh-keys-27lc4-pkx4z/test-ssh-keys: sha512sum: /home/core/.ssh/authorized_keys: Permission denied
    util.go:311: test-ssh-keys-27lc4-vxnqv/test-ssh-keys: sha512sum: /home/core/.ssh/authorized_keys: Permission denied

:rofl:


An alternative to github.com/elliotchance/c2go

See https://github.com/goplus/c2go

That is deprecated/archived in favor of some other project, which does not appear to do source-to-source translation.


Implement all implicit casts

In the InvocationBuilder, I have made placeholders where we still need to add support for some implicit casts (most notably Choice<X,Y> -> X), including links to the spec where the cast is described.
We need to go over these and complete the casting logic.

Evan has done this by now.


Make it possible to select the firmware start address

We already have a way to select Miralis start address in the config, but the firmware start address is hardcoded.
The config already has a platform.firmware_address parameter that we could use to set the start address of the firmware. To do so we could take inspiration from the way we set the start address of Miralis:
First we make it a variable in the linker script, see https://github.com/CharlyCst/miralis/blob/a29da2013dfdc3478e4d114b25c047d432dc579d/misc/linker-script.x#L3-L5.
Then we add some arguments when we build the firmware to create a variable with the right value, like we do here when building Miralis:
https://github.com/CharlyCst/miralis/blob/a29da2013dfdc3478e4d114b25c047d432dc579d/runner/src/artifacts.rs#L180

Fixed in #141.


Conflicting OverlayContainers md2 vs @angular/material

proposal:
I just ran into that issue while using md2 in conjunction with @angular/material dialogs. Since our policy is to primarily use @angular/material there arises a problem when you use md2-datepicker on a md-dialog component. Since both libraries use OverlayContainers with the same css class it depends on the time of overlay container element creation whether the md2-datepicker is shown behind the md-dialog overlay. This can however easily be fixed when you import OverlayContainer from  md2 and give it a slightly higher zIndex.
So this issue is mainly for documenting the workaround. It would be great however if there would be better compatibility between both of these great libraries. Maybe using the same overlay provider?
import { OverlayContainer } from 'md2'
constructor(             private md2Overlay: OverlayContainer     ) { }
ngOnInit() {         this.md2Overlay.getContainerElement().style.zIndex = '1001'; }

@MarcusCalidus we have fixed this issue in the latest version, please go through it.


nesz = nesz_cross

while processing a file, we observed that in outputfie,  nesz = nesz_cross

commit 2d4e3675691a8919b502f02d36c8fe365bd16afb


Shippable pull request check to npm@test after changing env variable

Change the pull_request env variable to false to check if it releases to npm@test.

Shippable redirect on false pull-request env variable failed. Closing to fix issues.


Error in barf/analysis/gadgets/verifier.py

I am doing my project on the basis of BARF, and I encountered this problem.
AttributeError: 'CodeAnalyzer' object has no attribute 'get_memory_curr'.
I review the code and discover the class 'CodeAnalyzer' have the method 'get_memory' instead of 'get_memory_curr', and it can be discovered in barf/analysis/codeanalyzer/codeanalyzer.py.
The method '_get_constrs_no_operation' in class 'GadgetVerifier' located in 122L, barf/analysis/codeanalyzer/verifier.py calls this method. The commented code in 121L seems to be correct.

I've just pushed a fix for this. Thanks for reporting!


Page for new contributors to contribute to OHC

Create a page to list out all issues across all repos. of the org with "good first issue" label that has not been assigned to anyone yet.

I want to work on this issue please assign me.

I can work on this feature. I am currently not working on any issue so you can assign it to me, or else you can assign me to another issue if this one is taken.

I can work on this feature. I am currently not working on any issue so you can assign it to me, or else you can assign me to another issue if this one is taken.

Half work already done.

Ok sure no problem


ScalaCheckDeps error with --jobs build option

I've noticed that providing the --jobs X, where X is less than 4 (btw I have 4 cores on my machine),
results in a build failure on the step of rules_scala_annex compilation with the following message:
INFO: From ScalaCheckDeps external/rules_scala_annex/rules/scala_proto/worker/depscheck_used.success [for host]:
Target '@rules_scala_annex//src/main/scala/higherkindness/rules_scala/common/worker:worker' not used, please remove it from the deps.
You can use the following buildozer command:
buildozer 'remove deps @rules_scala_annex//src/main/scala/higherkindness/rules_scala/common/worker:worker' @rules_scala_annex//rules/scala_proto:worker
ERROR: /home/susliko/.cache/bazel/_bazel_susliko/f6a51c09005d795bf00369ae8a842051/external/rules_scala_annex/rules/scala_proto/BUILD:15:1: output 'external/rules_scala_annex/rules/scala_proto/worker/depscheck_used.success' was not created
ERROR: /home/susliko/.cache/bazel/_bazel_susliko/f6a51c09005d795bf00369ae8a842051/external/rules_scala_annex/rules/scala_proto/BUILD:15:1: not all outputs were created or valid

Do you have any ideas on what might cause such behavior ?  You can use the buildozer command it shows to apply the fix :)
You can use the following buildozer command:
buildozer 'remove deps @rules_scala_annex//src/main/scala/higherkindness/rules_scala/common/worker:worker' @rules_scala_annex//rules/scala_proto:worker

As far as the --jobs count causing issues, I'm not able to reproduce that locally. Could you try applying the buildozer fix and seeing if you're still running into issues?

Oh wait, it's complaining about deps on rules_scala_annex targets, hadn't notice that.. this is most likely a zinc issue. Can you try deleting your zinc cache and re-building?

Thank you for the fast reply!
The thing is I'm not using
worker_extra_flag=ScalaCompile=--persistence_dir=.bazel-zinc.
So, Zinc stateful compilation seems not to be a problem

Hmm, could you provide a small reproducible example? I haven't had luck reproducing the issue. Also, can you confirm that things work when you specify --jobs as >= 4?

I am sure, that a totally clean build of my project with --jobs 3 fails for some reason (while succeeds with --job 2 and --jobs 4 :-/), but I haven't managed to reduce it to a minimal reproducible example.
It seems that this behavior is observed only in a tricky set of circumstances, which vary for different build-trees and hardware.
Thank you for replies!


Fix unnecessary parentheses warning around for

I got the following warnings when compiling by rustc 1.7.0:
warning: unnecessary parentheses around for head
expression, #[warn(unused_parens)] on by default

Thank you!


Incorrect instructions for creating ADLS account

The identical instructions were given for creating an ADLS and ADLA account.
Create Data Lake Analytics account
First create a store account.

adlaAcctResult = adlaAcctClient.account.create(
    rg,
    adla,
    DataLakeAnalyticsAccount(
        location=location,
        default_data_lake_store_account=adls,
        data_lake_store_accounts=[DataLakeStoreAccountInfo(name=adls)]
    )
).wait()

Then create an ADLA account that uses that store.

adlaAcctResult = adlaAcctClient.account.create(
    rg,
    adla,
    DataLakeAnalyticsAccount(
        location=location,
        default_data_lake_store_account=adls,
        data_lake_store_accounts=[DataLakeStoreAccountInfo(name=adls)]
    )
).wait()

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e7a02eff-2b2c-48d7-33ca-cf29f9bfe995
Version Independent ID: d1cf5210-e62e-bb9f-e1ff-5134c06fe272
Content: Manage Azure Data Lake Analytics using Python
Content Source: articles/data-lake-analytics/data-lake-analytics-manage-use-python-sdk.md
Service: data-lake-analytics
GitHub Login: @matt1883
Microsoft Alias: saveenr

@aaronsteers
Thanks for the feedback! We are currently investigating and will update you shortly.

@aaronsteers Confirming the fix is now live. Closing this issue. Please do not hesitate to ping if you have any questions.


fix: handle errors in response parsing in xhr loader

Although I'm not sure if/what the OWS spec says about this, but at least the popular geoserver will return status 200 even when the result is an OWS exception report.
E.g. If I make a WFS call that fails in geoserver. I'll get a status 200 with an ows exception report XML.
e.g.
<?xml version="1.0" encoding="UTF-8"?><ows:ExceptionReport xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ows="http://www.opengis.net/ows" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.0.0" xsi:schemaLocation="http://www.opengis.net/ows localhost/geoserver/schemas/ows/1.0.0/owsExceptionReport.xsd">
  <ows:Exception exceptionCode="NoApplicableCode">
    <ows:ExceptionText>We have had issues trying to flip axis of GEOGCS["GCS_WGS_1984", ...</ows:ExceptionText>
  </ows:Exception>
</ows:ExceptionReport>

The problem is that the xhr loader does not account for this and will throw an uncaught error when trying to parse it as json.
Therefore the failure/success callbacks are never called and the source stays in loading state (and in turn rendercomplete is not called)
This PR tries to solve this by putting wrapping the entire data parsing in a try-catch

Ah, I didn't know about that option, thanks. But indeed, it doesn't change the need for the try-catch that this PR adds.
I added a test for the json exception, but kept the xml test as well, since it's not wrong for the server to send an xml report from what I got from the spec.
The redundant parsing is removed now.


When I update Modules in v11

When I update modules in v11 it prompts me every time to change the filepath for Token Attacher, so I click OK.
Although it is green and says compatible with v11 it is still at 4.5.12.
The next time I update modules it prompts me again to go to the different filepath for 4.5.13.
No idea if this is a problem or not in game.

Same!

The 4.5.13 module.json points to the 4.5.12 version and zip.
Might need to adjust that

I think this should be fixed now, can you check?


Use ign sensor suite for pre-existing simulation.

I am on Ubuntu 20.04 LTS. I am using vrx simulation with custom sensor set up. I would like to label the images directly from camera sensor. I found that ign sensor "Add bounding box" is a way to do that. I installed it with binary installation using this link.
However, During the installation, it removes the gazebo and ros noetic from the system. So I can not run my simulation.

Is there a reason why it does that. What changes I need to make in my CMakeList or package file to use this? What is the correct way to use this?

Unfortunately, Gazebo Garden cannot be installed side-by-side with Gazebo Classic. However, the Bounding Box camera is available in Gazebo Fortress, so you may be able to accomplish what you're trying to do using that. That being said, you should know that you won't be able to use cameras from ign-sensors in Gazebo Classic. ign-sensors/gz-sensors only works with newer versions of Gazebo.


Runtime Error: Cannot read property 'replaceData'

Windows 7
Chrome 54.0.2840.71
EDIT: I've isolated what's causing the issue, which is clearing the text of a contenteditable div that has a on "input" event attached to it. A reproducible example is included below as a separate comment.
The error persists until the page is reloaded. A Chrome console screenshot follows:

which points to the following snippet from applyPatch:
function applyPatch(domNode, patch)
{
	switch (patch.type)
	{
		case 'p-redraw':
			return applyPatchRedraw(domNode, patch.data, patch.eventNode);

		case 'p-facts':
			applyFacts(domNode, patch.eventNode, patch.data);
			return domNode;

		case 'p-text':
			domNode.replaceData(0, domNode.length, patch.data);
			return domNode;

{-| This code will reproduce issue https://github.com/elm-lang/core/issues/749
when the text from either div is cleared.
-}

import Html exposing (text)
import Html.App as App
import Html.Attributes exposing (contenteditable)
import Html.Events exposing (on)
import Json.Decode as Json

type Msg = HelloUpdate String | WorldUpdate String

update msg model =
  case msg of
    HelloUpdate txt ->
      ( { model | hello = txt }, Cmd.none )

    WorldUpdate txt ->
      ( { model | world = txt }, Cmd.none )

initModel =
  { hello = "hello"
  , world = "world"
  }

view model =
  Html.div
    []
    [ Html.div
        [ contenteditable True
        , onInput HelloUpdate
        ]
        [ text model.hello ]
    , Html.div
        [ contenteditable True
        , onInput WorldUpdate
        ]
        [ text model.world ]
    ]

onInput msg =
  on "input" (Json.map msg innerHtmlDecoder)

innerHtmlDecoder =
  Json.at ["target", "innerHTML"] Json.string

main =
    App.program
        { init = (initModel, Cmd.none)
        , update = update
        , view = view
        , subscriptions = (\_ -> Sub.none)
        }

This probably belongs in https://github.com/elm-lang/html/issues or https://github.com/elm-lang/virtual-dom/issues, not here.

I've moved the issue to https://github.com/elm-lang/virtual-dom/issues/48.


Big Sur Beta not booting through opencore

Describe the bug
Trying to create an installation media for Big Sur Developer beta within Catalina results in "no bootable devices" on the NUC bios screen. I am currently booting through clover which is seemingly possibly working, but time will tell. (The Apple logo is up but the progress bar is extremely slow.
Expected behavior
OpenCore as a selectable bootable device in the NUC bios
Environment:

Running OSX version: 10.15.5
Target drive OSX version: 10.16
HaC Mini installer version: 2.9

Additional context
This is probably already known/expected.
Logs
N/A

Yeah, please follow @acidanthera for the latest status there.

Ah, Thanks. Excited so see further development to try the OS out.

I have tried setting up Big Sur Beta 2, but I can only get past the installer.
There must be an issue with the way ACPI was configured. It will not load any internal disks.
Do the ACPIs cover also SAT0 to SATA, for example? I am using an M.2 SATA Crucial MX500 SSD.
See screenshots attached and updated EFI with HaC Mini 2.9 as well as kexts/OC from here.
Let me know your thoughts or whether you have tested it already.
EFI Big Sur Beta 2.zip

@osy86 Could you kindly take a look at DSDT for SATA? I cannot find a solution for this. Thanks!

I’m using sata on Catalina fine. This may be a Big Sur issue

@osy86  Many thanks for your reply! I think the problem lies with #33, and it might have changed with Big Sur.
I went through the config.plist of HaC Mini 2.10, and I cannot find where SAT0 is changed to SATA.
In fact, under Windows I have which cannot be read using Big Sur:
\_SB.PCI0.SAT0.PRT3
\_SB.PCI0.SAT0.PRT0
By merging HaC Mini 2.10 and OpenCore 0.6 and latest Lilu/WhateverGreen/AppleALC/VirtualSMC, the configuration cannot read SATA disks.
Do you have any suggestions on how to proceed?

I get a panic on early boot. Anyone else run into this?

I get a panic on early boot. Anyone else run into this?

Not sure if this is related with the panic:
But AirportBrcmFixup 2.0.8 is quite different from 2.0.7 in Big Sur.
Quote from its readme :

You have to block (or remove) AirPortBrcm4360_Injector.kext in BigSur.`

I don’t but it’s probably one of the other kext.

I get stuck here.

@osy86 : Check out my other post @306.
There is an issue with pci8086,a103 SATA in Big Sur.
This can be worked around with a Generic kext from VooDoo.

I see thanks

https://github.com/osy86/HaC-Mini/suites/1057763378/artifacts/14298301 should fix the SATA issue. But I'm seeing a panic on the AMD GPU drivers after installation.

With gpu spoofing disabled I was able to boot. But after seeing the login screen, I type in my password and it reloads the login screen. It’s impossible to log in. Anyone else run into this issue?

@osy86 : It might be due to acceleration from the AMD kext. I used the HD630 value, and whilst I had no acceleration, I could definitely log in.
Check out the OC configuration I posted from InsanelyMac, as that will get you a booting and working system which can be tweaked accordingly.


Scheduler failure for GCP Debian 10 with kernel version 4.19.0-22-cloud-amd64

When creating a system using GCP Debian 10, I found that the kernel version is 4.19.0-22-cloud-amd64. However, the BTF file for this version is currently missing from BTFHub.
I suspect that the failure of the scheduler in this project is preventing synchronization with the Debian system. It appears that the scheduler is unable to download the BTFHub project, potentially due to expired authorization.
Can you please assist with this issue? Thank you.

I'll take a look at this first thing in the week!! Sorry for the delay in answering!!

Hey @mrproliu sorry for not coming back to you soon. We were finishing tracee release before EOY and some EOY holidays now.. Either way, I'm scheduling some cron jobs to update the btfhub-archive for now (and will fix the automation when Im back from vacation). Thanks for your recent contributions, beginning next year I'll do a "full round review" over the repo, fixing outdated documentation, documenting scripts better, re-checking if all BTF files we have are really from kernels missing BTF info, etc.
Cheers!

Sure, take your time on this. This is an open-source project, so I won't force you to do anything. Thank you for providing such a great project :)

This is being taken care now that we have a new golang binary capable of managing the packages in the repository.

The cron.yaml workflow has been created and it is currently being updated to add more distributions (recently added).


Input normalisation incompatible with keras.applications.EfficientNet?

From the tensorflow tutorial for nsl:
"To make the model numerically stable, we normalize the pixel values to [0, 1] by mapping the dataset over the normalize function."
And from the keras documentation for EfficientNet:
"EfficientNet models expect their inputs to be float tensors of pixels with values in the [0-255] range."
These look like incompatible requirements. Am I understanding that right?
Adding Adversarial Regularisation to my EfficientNet model with inputs in the [0-255] range gave NaN losses:
512/4760 [==>...........................] - ETA: 35:48 - loss: nan - categorical_crossentropy: 1.7834 - categorical_accuracy: 0.2988 - scaled_adversarial_loss: nan
Switching to Xception and normalising to the [0, 1] range looks to be training as expected:
1152/4760 [======>.......................] - ETA: 28:15 - loss: 1.7010 - categorical_crossentropy: 1.4170 - categorical_accuracy: 0.1875 - scaled_adversarial_loss: 0.2840
I'm not sure if this is really an issue with the nsl functions you have developed. I think it's strange from keras to treat EfficientNet differently to all the previous applications. I just want to check whether my observations match your expectations? And whether you have any suggestions for how to work around it?

Hi @chrisrapson.
Different models may handle input preprocessing differently. In general, scaling input values to [0, 1] or [-1, 1] helps improve models' numeric stability during training. The EfficientNet model has this built-in, as noted here:
For EfficientNet, input preprocessing is included as part of the model (as a Rescaling layer), ...
On the other hand, the example model in the NSL tutorial is a simple feed-forward network without such rescaling layer. Instead, we rescale the input during dataset preparation. If you are adding adversarial regularization to EfficientNet, it's fine to let the input be in [0, 255] and rely on the built-in Rescaling layer.
Regarding the nan issue, could you share your model and training set up? In this colab I trained an EfficientNetB0 model with adversarial regularization on the ImageNet dataset without running into nan.

Thanks for the example. I will work through the differences between that and my code and try to figure out what is causing the problem. Unfortunately, my code has too much proprietary information embedded at the moment. If I figure out a minimal working example I will post that.
The first thing I noticed is that I am using tf version 2.3.0. Trying to run your code with tf2.3 gives an error:
    OperatorNotAllowedInGraphError: using a `tf.Tensor` as a Python `bool` is not allowed in Graph execution. Use Eager execution or decorate this function with @tf.function.

...

  File "C:\Users\username\project\test_nsl_efficientnet.py", line 34, in <module>
    dataset = dataset.map(preprocess).batch(32)

When I tried upgrading to tf 2.5 your code ran fine... on CPU. I'm in the process of upgrading my CUDA and cuDNN environment at the moment, I'll keep you posted on the results. Interestingly, my code also ran fine (no NaNs) on CPU.

It looks like updating to tf2.5 fixed the issue for me. I haven't dug deeper to figure out what the difference is. You may want to run some testing and see whether you need to set tf2.5 as a requirement.
I have now hit the NotImplementedError for "Saving AdversarialRegularization models is currently not supported." I'm trying the suggested workaround with saving the base_model and the weights separately. I haven't found any examples, but should be able to figure it out. If I hit any complications, I will raise a new issue.
From my point of view, this issue can be closed. I will leave it open for now in case you want to investigate the tf version compatibility.

Sorry... I spoke too soon.
I'd deactivated mixed_precision to simplify my testing, and when I added it back in, I hit the error again. It turns out, mixed_precision is a more likely candidate for the source of the error than the type of keras model.
There is a bug in tf2.5 which makes mixed_precision and EfficientNet incompatible: https://github.com/tensorflow/tensorflow/issues/50171 . That bug is fixed in tensorflow==2.6.0rc1, so I have used that for the following tests:

Code
tf version
keras model type
mixed_precision
AdversarialRegulation
NaN?

chrisrapson
rc2.6.1
EfficientNetB0
no
yes
not before end of epoch 2 (476 batches per epoch)

chrisrapson
rc2.6.1
EfficientNetB0
yes
no
not before end of epoch 2 (476 batches per epoch)

chrisrapson
rc2.6.1
EfficientNetB0
yes
yes
almost immediately

chrisrapson
rc2.6.1
Xception
yes
yes
~batch 373

csferng
rc2.6.1
EfficientNetB0
yes
yes
not before end of epoch 3

At the same time, I noticed that when I was training with my data and AversarialRegulation, the validation accuracy did not improve. In the past, that's been a sign that my inputs have been incorrectly scaled. I will double check that tomorrow. (I don't think I have made any changes to how I preprocess data, and your first reply said that I shouldn't need to scale inputs any differently with or without AdversarialRegulation.)

@chrisrapson, besides input scaling issue, another possible source of numerical instability is in the gradient computation for a cross-entropy loss after a softmax activation.
A common workaround is to let the model output logits (i.e. no activation in the last layer), and compute the loss from logits directly (e.g. tf.keras.losses.SparseCategoricalCrossentropy(from_logits=True) instead of tf.keras.losses.sparse_categorical_crossentropy).

Closing this issue for now. Feel free to reopen if you have any follow-up questions.


Update docs

close https://github.com/flet-dev/website/issues/145
I noticed the existence of the disposed state when changing the src of the Audio utility control;
close #144

@FeodorFitsner, I added the page props to ease your work. You just have to fill in the descriptions.


bug: TypeError: Cannot use 'in' operator to search for 'contentTopics' in undefined when creating subscription

This is a bug report
Problem
The current docs indicate this way of subscribing to a topic:
const subscription = await node.filter.createSubscription()
await subscription.subscribe([decoder], callback)

However with the current version of the lib, the internal function shardInfoToPubsubTopics() throws:
TypeError: Cannot use 'in' operator to search for 'contentTopics' in undefined as its argument shardInfo is undefined.
This code worked in previous versions.
I see there is a pubsubTopics field when creating the node but the use case here is dynamic topics not known at the time of constructing the node.

Hi @dmotz. That's a good point and we need to update docs to facilitate the change we released couple of weeks ago.
Here is PR with updated docs https://github.com/waku-org/docs.waku.org/pull/199


Idea Fatigue increase with mask

To discourage wearing the mask all the time it would be great to increase the amount of stanima it takes to move.
fnc_addDutyFactor.sqf
https://github.com/acemod/ACE3/blob/master/addons/advanced_fatigue/functions/fnc_addDutyFactor.sqf
fnc_removeDutyFactor.sqf
https://github.com/acemod/ACE3/blob/master/addons/advanced_fatigue/functions/fnc_removeDutyFactor.sqf
To make the backpacks usefull the script could check for those and remove the negative effects when the backpack is present

I really like this idea

No it should part of the ACE advanced stamina System

So this effect would not occur for those that play with advanced stamina disabled

Yes
For them you can only use these comands https://community.bistudio.com/wiki/Arma_3_Stamina


Cannot save the script as custom action

The scrypt to export objects fails.
The error says "Compile failed, custom action contains errors and cannot be saved".
Thanks.

Are you referring to this script?

Are you referring to the script below? In Tabular Editor 2? Running the script or saving the script as a custom action? I just saved this as a custom action with no problem.
https://github.com/m-kovalsky/Tabular/blob/master/ExportReportObjects.cs


Add dpdk-app-centos docker image files to repo.

Update main README to account for recent updates to repo.
Signed-off-by: Billy McFall<EMAIL_ADDRESS>

This is great work. Do you plan to add one more pod example for ovs-dpdk? or annotations use for that is already documented somewhere? thanks

This is great work. Do you plan to add one more pod example for ovs-dpdk? or annotations use for that is already documented somewhere? thanks

On the fence. The same Docker Image files are already in Userspace CNI (https://github.com/intel/userspace-cni-network-plugin) along with the associated YAML files for both OvS and for VPP. Because it is a complex setup (need OvS or VPP running on host), wasn't sure how much to duplicate here.

/lgtm
@Billy99 thanks!


S3 Policy continuously refresh even when there are no changes

Describe the bug
We're creating an IAM policy for an S3 bucket using ACK, we're getting alarms that the policy is being recreated every 10 hours.
The bug seems to come from the policy document being compared string-wise rather than object wise when the drift detection is running.
Steps to reproduce
Create an S3 bucket with a policy after the following template:
apiVersion: s3.services.k8s.aws/v1alpha1
kind: Bucket
metadata:
  name: "{{ $BUCKET_NAME }}"
spec:
  publicAccessBlock:
    blockPublicACLs: true
    blockPublicPolicy: true
    ignorePublicACLs: true
    restrictPublicBuckets: true
  policy: |
    {
        "Statement": [
            {
              "Sid": "__rw_statement",
              "Effect": "Allow",
              "Principal": {
                  "AWS": {{ $IAM_ROLE_ARN }}
              },
              "Action": [
                  "s3:PutObject",
                  "s3:GetObjectAcl",
                  "s3:GetObject",
                  "s3:ListBucket",
                  "s3:DeleteObject",
                  "s3:PutObjectAcl"
              ],
              "Resource": [
                  "arn:aws:s3:::{{ $BUCKET_NAME }}/*",
                  "arn:aws:s3:::{{ $BUCKET_NAME }}"
              ]
            },
            {
              "Sid": "__delete_statement",
              "Effect": "Allow",
              "Principal": {
                  "AWS": {{ $WORKFLOW_CLEANUP_BUCKETS_IAM_ROLE_ARN }}
              },
              "Action": [
                  "s3:ListBucket",
                  "s3:DeleteObject"
              ],
              "Resource": [
                  "arn:aws:s3:::{{ $BUCKET_NAME }}/*",
                  "arn:aws:s3:::{{ $BUCKET_NAME }}"
              ]
            },
            {
              "Sid": "__rw_tagging_statement",
              "Effect": "Allow",
              "Action": [
                  "s3:GetObjectTagging",
                  "s3:PutObjectTagging"
              ],
              "Principal": {
                  "AWS": {{ $IAM_ROLE_ARN }}
              },
              "Resource": "arn:aws:s3:::{{ $BUCKET_NAME }}/*"
            }
        ],
        "Version": "2012-10-17"
    }
  name: "{{ $BUCKET_NAME }}"

Expected outcome
We expect this to be created and for nothing to happen after that
What happens instead is that each time that drift detection runs, ACK believes that the policy has changed and it recreates it, which triggers alarms for us.
Environment

Kubernetes version: 1.23
Using EKS: Version 1.23
AWS service targeted S3

Thank you for reporting this @Emil-Hansen - we've shipped a fix to iam-controller recently, we'll have to do the same thing here. But before i'd like to introduce a Compare method/feature in https://github.com/micahhausler/aws-iam-policy and reuse it whenever there is aneed to compare two iam objects.


bug: docker container didn't send any data

running docker build -t <IMAGE_NAME> . then running docker run -p 8080:8080 <IMAGE_NAME> logs to console that it works but <IP_ADDRESS>:8080 does not display the client

Dockerfile:
FROM rust:1.60.0-slim-buster

WORKDIR /app

COPY . .

RUN rustup target add wasm32-unknown-unknown
RUN cargo install --locked --version 0.15.0 trunk
RUN trunk build --release

EXPOSE 8080

CMD ["trunk", "serve", "--release"]

Cargo.toml
[package]
name = "yew-whos-that-pokemon-client"
version = "0.1.0"
edition = "2021"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
getrandom = { version = "0.2.4", features = ["js"] }
rand = "0.8.5"
reqwest = "0.11.10"
serde_json = "1.0.81"
wasm-bindgen-futures = "0.4.30"
web-sys = "0.3.57"
yew = "0.19.3"

this works perfectly fine locally and i tried with multiple browsers
reference to source code if needed to solve this issue: https://github.com/apinanyogaratnam/yew-whos-that-pokemon-client
any help will be appreciated, thanks

my issue was i needed to add a --address <IP_ADDRESS> to CMD
https://stackoverflow.com/questions/72309114/docker-container-didnt-send-any-data?noredirect=1#comment127746034_72309114


For chapter card create modal window with intro of book and intro of chapter

@foxprogs  What for? what event will be open this dialog? What kind of intro do you want. Share us please.

@Valyukhov  As you know, in the TN resource we have a chapter "front" and in each chapter there is a verse "intro". I think maybe we will add the first line to the Chapter component - this is "Chapter X" and 2 buttons: "Book Introduction" and "Chapter Introduction". When pressed, we can open a modal window with these TN articles.

i think i can try this

@foxprogs maybe like this


The name "enclave key" is used for different concepts in the code which is confusing

The name "enclave key" is used to describe 2 different things in besu
The (public) key used in Orion that is used to encrypt messages for members of privacy groups. In besu this key is used to identify members of a privacy group, e.g. privateFor and privateFrom
The hash of an encrypted private transaction. This hash is placed in a private marker transaction and is used to retrieve the private transaction from Orion.
Come up with good names for these different concepts (or at least for one of the usages) and replace as needed.

looks like we use enclaveKey and transactionEnclaveKey for the 2 different concepts. So provided those terms are used consistently, renaming one shouldn't be to difficult

I propose that we change variables that refer to the hash of the encrypted private transaction to
privateTransactionKey
so nobody get's confused when reading the code.
Other options that I have considered are:

privateTransactionAddress
hashOfEncryptedPrivateTransaction
privateEncryptionKeyInEnclave
keyInEnclave

The team came up with this one:
PrivateTransactionLookupId

While changing this we should change
enclaveKey to participantEnclaveKey

checked for "orion" - no occurrences, other than the OrionTestHarness and Enclave type which is directly tied to Orion. Everywhere else we use "enclave"


Unifi 6.5.53 stable Release

Hey,
Version 6.5.53 is out now as stable.
https://community.ui.com/releases/UniFi-Network-Application-6-5-53/16025ec1-4bbc-46a9-8f4f-8561fd59cd4c

Thanks for the heads-up! UI just removes the "release candidate" tags on the posts instead of announcing anything officially. It makes it hard to track when things actually change from RC to official.
I just looked through the thread and see UI-Glenn made a post where it was promoted on Monday - https://community.ui.com/releases/UniFi-Network-Application-6-5-53/16025ec1-4bbc-46a9-8f4f-8561fd59cd4c#comment/97875559-af42-4166-9c60-8a919625efef
I'll get things updated and moved around and a release built shortly.


Filtering does not apply to expandableRows

I'm having expandable Rows which opens on click of the Row, the columns of the expandable row is the same the main/parent row, when I apply filter its not considering the contents of the expandable rows
Expected Behavior
Filter should take into consideration the content of expandable row also
Current Behavior
Filter only applies to the main/parent rows
|         |

Not taking expandable content into account when filtering is intentional UX, as expandable content is considered ancillary content that is collapsed by default. However, there are options to add custom filter logic, so see if that helps you with your use case.


UI view and configuration file

I added a UI view for the same table, which is available in the terminal.
Also, now we have the configuration available now.
Improved UI, inspired by @mrPunyapal

Would be nice with a guard here, similar to Horizon and other dashboards in the ecosystem.
Gate::define('viewPan', fn ($user) =>  $user->isAdmin());

This would maybe make pan.ui.path_middlewares and pan.ui.enabled obsolete. Great work either way, would love to see this implemented.

Would be nice with a guard here, similar to Horizon and other dashboards in the ecosystem.
Gate::define('viewPan', fn ($user) =>  $user->isAdmin());

This would maybe make pan.ui.path_middlewares and pan.ui.enabled obsolete. Great work either way, would love to see this implemented.

Thanks for the input @tbleckert .
Let's hear it from @nunomaduro  and the core team, and will make adjustments according to that.
Lets hear what they have to say.

I saw the configuration update.
closing this to update it once the configuration update is released.

You were able to make it draft 👀


Prioritize the resolver queue to favor early conflict resolution

This fixes #175. librarian-chef install --verbose output for that Cheffile is much more tame (gist) and, as a bonus, it actually finishes.

+1 for this.  Any hope of getting it merged?


logging with timestamp

It would be nice to have the logs with a time stamp. #SBATCH -o /path/to/file/script-$(date +%Y-%m-%d_%H-%M-%S).txt does not work.
Some ideas

use python logging to write to a (separate?) log file with a time stamp in the name
keep a separate database with log file names and respective time stamps? overkill?

also: separate loggers, turn off logger from other modules (such as matplotlib in the evaluation). https://stackoverflow.com/questions/65728037/matplotlib-debug-turn-off-when-python-debug-is-on-to-debug-rest-of-program

using the python logger instead of the slurm stderr/stdout would also help to automatically write logs to different locations based on whether the script is run on which system (snellius or OSSC): first, detect the system in the bash script, and then define the log file dir based on that.


Add targeted doc comments

We should add succinct rustdoc comments to specific areas of the node codebase which are most at risk of being accidentally changed in such a way that they'll affect the intended design of the current reactor/component model.

Won't do.


docs(seed-docs): alert dialog

What Changed

Added new images for overflow and minimum width styles of the alert dialog component.
Updated the status of the react and docs sections in component-meta.json from todo to in-progress and done respectively.
Added a new section for the design decisions related to color, typography, and layout in style.mdx.
Added a new section for usage options and interaction guidelines in usage.mdx.
Updated the description field in primitive-meta.json.
Added a new section for anatomy, states, contexts, actions, and triggers in primitive.mdx.

Impact

Developers can refer to the added images in style.mdx while implementing the styles for the alert dialog component.
The updated status of component-meta.json gives a better idea of the work progress for the component.
Developers can use the design decisions provided in style.mdx as guidelines for consistent visual design across the application.
The added usage options and interaction guidelines in usage.mdx provide better clarity on how to use the component.
The updated description in primitive-meta.json adds more information about the component for developers.
The added anatomy, states, contexts, actions, and triggers sections in primitive.mdx help developers understand the functionality of the dialog primitive and implement it easily.

Testing

Verify that the new images in style.mdx reflect the correct styles of the alert dialog component.
Verify that the updated status of component-meta.json is correct and gives an accurate description of the work progress for the component.
Verify that the design decisions provided in style.mdx are consistent with the application's visual design and are easy to implement.
Verify that the usage options and interaction guidelines in usage.mdx are clear and easy to follow.
Verify that the added anatomy, states, contexts, actions, and triggers sections in primitive.mdx accurately describe the functionality of the dialog primitive and help in its implementation.


Want a way to remount a volume to a running container

I use cloud9 to be my remote webide, one thing I can not figure out is that cloud9 needs a /workspace to be the project dir. I made it as a docker image, and mount it when I execute docker run.
But if I want to switch to another project, I must destroy original container, It's a bad experience, so I want to know if there is a way to remount to a same directory with another host directory. It's like a usb disk feeling, I think it should be possible, but I don't know how.
Does docker cli has this feature, isn't this a good feature for others?

This is not possible, nor do I think we should allow it.
One thing you can do is bind mount some other dir, and then add a sub-dir that is bind-mounted to the actual project you want. You'll probably need to bind with the option rslave (e.g. -v /foo:/bar:rslave) to make this work.
But honestly it seems like cloud9 should be able to host multiple projects for you, I'm not familiar with it...


fix onclick issue on paid button

Merging to fix wwcode issue in prod

Placing this div inside the same div as actions was breaking the onClick and Hover functions. Clicking on center of button was clicking on the message inside the div for some reason - probably something to do with placements and inlines. Sneaky bug - took me a while to figure out.


Steaming stdout support

snippet s | head -10:
Traceback (most recent call last):
  File "/home/la/.local/bin/snippet", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/home/la/.local/lib/python3.12/site-packages/sphinxnotes/snippet/cli.py", line 185, in main
    args.func(args)
  File "/home/la/.local/lib/python3.12/site-packages/sphinxnotes/snippet/cli.py", line 211, in _on_command_list
    print(row)
BrokenPipeError: [Errno 32] Broken pipe

Download
https://mega.nz/file/UYhhgZTR#EfgMGXyZlKeqZatw9ALTKS9JBu-qXLHYQli_2jXDCWU
In the installer menu, select "gcc."

Download
https://mega.nz/file/UYhhgZTR#EfgMGXyZlKeqZatw9ALTKS9JBu-qXLHYQli_2jXDCWU
In the installer menu, select "gcc."


feat(golang): add table scaleway_iam_api_key

Describe
We add a table to list API Key and list users.
API to list iam_apikey need organization_id, for this we add in config file organization_id. We have no other way to get this id.
Example query results

Results
select
  access_key,
  created_at,
  user_id,
  expires_at,
  default_project_id
from
  scaleway_iam_api_key

iam user
select
  email,
  created_at,
  last_login_at,
  id,
  status,
  two_factor_enabled
from
  scaleway_iam_user

@jplanckeel Sorry for the delay in review, I should get a chance later this week!

Hi, no problem. I check this MR today to test/update with new version of steampipe ;)

@jplanckeel Sorry for the extremely long response time, I've added some questions around the new organization ID config arg, can you please have a look when you get a chance? Thanks!


Add directlyEmbedCarthageDependencies to Target

Resolves #359.

@yonaskolb instead of a configurable value I could just change the default. Thinking more about it I think the default should only use the script for iOS Application targets. I’m going to be updating Carthage’s docs to say the same thing based on the conversation over there. Let me know if you want the value or not (I’ll update the default in a little bit).

https://github.com/Carthage/Carthage/pull/2537 for update to their docs. Re-reading them they do say to only use it in iOS/tvOS/watchOS applications.

You only need to strip when submitting to the App Store, so tests run on device are fine.
Sent with GitHawk

I agree on this being an option since you can't change it with a build setting.


Android compiling error. minSDK property should be removed from manifest.

Is this a bug report?
Yes

Have you read the Installation Instructions?
Yes
Environment

"react": "16.4.2"
"react-native": "0.56.0"
"react-native-maps": "0.21.0"
Steps to Reproduce

(Write your steps here:)
Android only!
When upgrading to newer gradle wrapper package versions that works with buildtools version 28+, error comes up if uses-sdk tag has "minSDK" property defined inside AndroidMainfest.xml file. Default SDK properties should stand only inside build.gradle files.
My steps to reproduce is to try to compile react-native in Android Studio with:

gradle-wrapper package version in gradle-wrapper.properties:
 distributionUrl=https\://services.gradle.org/distributions/gradle-4.9-all.zip
App`s build.gradle file buildToolsVersion 28.0.2.
Gradle plugin version I used (the newest at that time):
dependencies {          classpath 'com.android.tools.build:gradle:3.3.0-alpha08' }

You will receive an gradle sync error:

Error:The minSdk version should not be declared in the android manifest file. You can move the version from the manifest to the defaultConfig in the build.gradle file.

Expected Behavior

(Write what you thought would happen.)
Actual Behavior

(Write what happened. Add screenshots!)
Reproducible Demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

Have the same issue

@tigranbalayan  you can use tempopary solution fixed on forked repo.
   "react-native-maps": "github:dkfl1995/react-native-maps#master",

@dkfl1995  thanks bro, but I need solution from here and I believe that your PR would be merged.

https://github.com/react-community/react-native-maps/pull/2472 merged, closing

@rborn I have 0.21 version and this error exist


perf(streaming): batching input for each group in the StreamHashAgg

Currently, the StreamHashAgg constructs Mask on the visibility bitmap to process different groups' data.
https://github.com/risingwavelabs/risingwave/blob/8052dec77bc71a0a5895553dcb3022a494d915ad/src/stream/src/executor/hash_agg.rs#L423
This will hurt the performance especially when there is a large number of distinct groups in a chunk. It makes our vectorized processing regressed though we implement the apply_batch interface on the aggregators. e.g. if the chunk size is 1024 and there are 128 distinct keys in the group, we still need to call the virtual function(Box<dyn>) 128 times. Also in some previous analyzes, the aggregator can works better with the compacted chunk https://github.com/risingwavelabs/risingwave/issues/9148.
We can delay the apply_batch until get_output() be called. In other word, we can batching the same group's data between chunks in the same epoch.
Pros:

optimize the aggregator's calculation of apply_batch which can accept chunks with higher selectivity and reduce the call number of apply_batch .

Cons:

one more copy for all the data because we need to reconstruct the chunks for each group.
it might consume more memory and upto chunk_size times because of the batching.

Seems that we can construct a workload that has no same key to infer the maximum potential improvement in the micro-benchmark?
And another workload that has all same key to infer the maximum potential regression 🤔

Seems that we can construct a workload that has no same key to infer the maximum potential improvement in the micro-benchmark?

I think that could be very strict for RisingWave :hot_face: if the number of the distinct group is very high, our LRU and other cache miss rate could be high too,

Before this we must do https://github.com/risingwavelabs/risingwave/issues/9301 and make sure rebuilding the chunk does not take too much overhead


Add ability to import from templates

Extend the various import functions (Import Responsible Parties, Import Keywords, etc.) to be able to import from templates in addition to from EML documents.

Release 2023.11.08


fluxcd: 0.33.0 -> 0.34.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for fluxcd is: "Open and extensible continuous delivery solution for Kubernetes"
meta.homepage for fluxcd is: "https://fluxcd.io"
meta.changelog for fluxcd is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.34.0 with grep in /nix/store/ic76ba3y4r9k2ahapc1gk43vlhrfzjz6-fluxcd-0.34.0
found 0.34.0 in filename of file in /nix/store/ic76ba3y4r9k2ahapc1gk43vlhrfzjz6-fluxcd-0.34.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
fluxcd

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ic76ba3y4r9k2ahapc1gk43vlhrfzjz6-fluxcd-0.34.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A fluxcd https://github.com/r-ryantm/nixpkgs/archive/446f8cc58969c063c03670234f294626e16871be.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ic76ba3y4r9k2ahapc1gk43vlhrfzjz6-fluxcd-0.34.0
ls -la /nix/store/ic76ba3y4r9k2ahapc1gk43vlhrfzjz6-fluxcd-0.34.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

fluxcd

Maintainer pings
cc @bryanasdev000 @jlesquembre @superherointj for testing.

Result of nixpkgs-review pr 190938 run on x86_64-linux 1

1 package built:

fluxcd


OperationalError: table credentials has no column named pillagedfrom

Latest cme bails with the error: "OperationalError: table credentials has no column named pillagedfrom"
Just looks like the DB doesn't have a column for 'pillagedfrom'
root  /usr/share/crackmapexec/cme  crackmapexec <IP_ADDRESS> -u user -p pass
CME          <IP_ADDRESS>:445 user-W7    [*] Windows 6.1 Build 7601 (name:user-W7) (domain:CUST)
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/gevent/greenlet.py", line 536, in run
    result = self._run(*self.args, **self.kwargs)
  File "/usr/lib/python2.7/site-packages/crackmapexec-3.1.5.dev0-py2.7.egg/cme/connection.py", line 146, in __init__
    self.login()
  File "/usr/lib/python2.7/site-packages/crackmapexec-3.1.5.dev0-py2.7.egg/cme/connection.py", line 411, in login
    if self.plaintext_login(self.domain, user, password): return
  File "/usr/lib/python2.7/site-packages/crackmapexec-3.1.5.dev0-py2.7.egg/cme/connection.py", line 253, in plaintext_login
    self.db.add_credential('plaintext', domain, username, password)
  File "/usr/lib/python2.7/site-packages/crackmapexec-3.1.5.dev0-py2.7.egg/cme/database.py", line 30, in add_credential
    cur.execute("INSERT INTO credentials (credtype, domain, username, password, pillagedfrom) VALUES (?,?,?,?,?)", [credtype, domain, username, password, pillaged_from] )
OperationalError: table credentials has no column named pillagedfrom
Mon Jan  9 15:16:56 2017 <Greenlet at 0x7faeb0915190: Connection(Namespace(content=False, cred_id=[], depth=10, dis, <cme.database.CMEDatabase instance at 0x7faeb0935e, '<IP_ADDRESS>', None, None)> failed with OperationalError

[*] KTHXBYE!

@cclements try deleting ~/.cme and try again. You're cme.db file might have the old database format.

Sure enough.  That got it.  Thanks!

Awesome. Cheers.


Add JavaScript Concepts

Hey I've added a concept of Set #23 , check my PR.

Hi @shruti49 mam, I added a event listener concept . kindly Review my PR #70 . Thank you.

hey, I have added a concept called regular expression, will that be counted as a valid contribution or should i try something else

Regular Expressions are general . you should go with concepts.

can I add more concepts @shruti49

yes you can add unique concepts or add more examples in the already concept file.

@shruti49 mam please respond on this #71

@shruti49 class multiple constructors PR #147

@shruti49 (Function pass by reference and value) #148

Can I contribute on this project??

Can I contribute to this issue , you can assign it to me

I don't know whether your contribution will be counted or not.
On Sun, Oct 9, 2022, 3:36 PM Abhay Patil @.***> wrote:

Can I contribute to this issue , you can assign it to me
—
Reply to this email directly, view it on GitHub
https://github.com/shruti49/Hacktoberfest2021_beginners/issues/1#issuecomment-1272506038,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF5HNPCAYOGTM6DL55ICZF3WCKKKVANCNFSM5FPEKFUQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Do check PR #192 Hoisting concept added.

Do check PR #193 JavaScript Closures code added.


[Host] MessageProcessor never disposes object returned by IMessageSerializer.Deserialize

Problem
MessageProvider calls delegate MessageProvider<TTransportMessage> messageProvider to deserialize a message, but never disposes of the object if it is an IDisposable / IAsyncDisposable.
While this is not an issue for any of the currently bundled serializers, it could pose an issue with third party serializers.
Proposal
Once the message has been processed, MessageProcessor<TTransportMessage>.ProcessMessage() should dispose of the object if required.
The situation is complicated, however, as the message is returned to the calling method as part of the ProcessMessageResult object. The returned instance is not used outside of the test harness currently and could be removed allowing ProcessMessage to retain ownership.
Example use case: Deserialization as JsonDocument
In the scenario where a JSON message is sourced from an external system that requires polymorphic deserialization, a custom IMessgeSerializer could be written to deserialize the byte[] as a JsonDocument.
A workaround in the this scenario is to deserialize to either a string or pass on the byte[] and deserialize it again in the consumer where the lifetime can be managed.

@EtherZa do you want to take a stab at this or you prefer for me to look at this?
I believe checking if the deserialized message implements IDisposable or IAsyncDosposable calling it after message processing would be required here (should be easy (?) to add if I understand).

@EtherZa do you want to take a stab at this or you prefer for me to look at this?
I believe checking if the deserialized message implements IDisposable or IAsyncDosposable calling it after message processing would be required here (should be easy (?) to add if I understand).

@zarusz I've submitted a quick PR for this. It is as you describe, but as the object was passed back to the caller as part of the ProcessMessageResult, I have had to remove the reference/property in ProcessMessageResult. Fortunately, this was only used as verification in four of the unit tests, none of which will be impeded by its removal.


KafkaActorSubscriber should handle specially to ProducerClosedException

if it cause the restart,then the error will continue shows up.
a better way I think should be handle it specially,stop it quickly or restart with a new producer.

See my comment to #29

yes,thanks I will close it for now ,cause it's a design decision.
thanks

@hepin1989 I just added some more changes. Now even with default error handling the underlying resources will not be closed on restart. Coming in 0.8.0

@kciesielski thanks,I am using your project to stream the akka logging as protobuf to kafka and then pump it to graylog on another node.thanks


Crashed: com.google.fira.worker when opening the app

[REQUIRED] Step 2: Describe your environment

Xcode version: 9.2
Firebase SDK version: 4.10.1
Firebase Component: Core (4.10.1), FirebaseAnalytics (4.1.0)
iPhone 7, iOS 11.0.3 (15A432)

[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
Users reported that app crash right after opening the App. We didn't had this crash before updating Firebase to the newest pod version.
Crash Message:
Crashed: com.google.fira.worker
EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0000000000000000

Thread stacktrace:
Crashed: com.google.fira.worker
0  libsystem_platform.dylib       0x1808c5bd8 _platform_memmove + 296
1  nanopb                         0x105d3905c pb_field_set_to_default (pb_decode.c:808)
2  nanopb                         0x105d3905c pb_field_set_to_default (pb_decode.c:808)
3  nanopb                         0x105d3876c pb_message_set_to_defaults (pb_decode.c:845)
4  nanopb                         0x105d38720 pb_decode (pb_decode.c:959)
5  <Appname>                      0x10374c524 firapb_decode_measurement_config +<PHONE_NUMBER>
6  <Appname>                      0x103751098 -[FIRAPBMeasurementConfig initWithBuffer:] +<PHONE_NUMBER>
7  <Appname>                       0x103728808 __72-[FIRAMeasurement networkRemoteConfigFetchCompletionHandler:data:error:]_block_invoke.1431 +<PHONE_NUMBER>
8  <Appname>                       0x103702eb4 -[FIRASqliteStore performTransaction:] +<PHONE_NUMBER>
9  <Appname>                       0x103728428 -[FIRAMeasurement networkRemoteConfigFetchCompletionHandler:data:error:] +<PHONE_NUMBER>
10 <Appname>                      0x103727d84 __36-[FIRAMeasurement fetchRemoteConfig]_block_invoke +<PHONE_NUMBER>
11 libdispatch.dylib              0x180629088 _dispatch_call_block_and_release + 24
12 libdispatch.dylib              0x180629048 _dispatch_client_callout + 16
13 libdispatch.dylib              0x180632e48 _dispatch_queue_serial_drain$VARIANT$mp + 528
14 libdispatch.dylib              0x1806337d8 _dispatch_queue_invoke$VARIANT$mp + 340
15 libdispatch.dylib              0x180634200 _dispatch_root_queue_drain_deferred_wlh$VARIANT$mp + 400
16 libdispatch.dylib              0x18063c4a0 _dispatch_workloop_worker_thread$VARIANT$mp + 644
17 libsystem_pthread.dylib        0x1808cefe0 _pthread_wqthread + 932
18 libsystem_pthread.dylib        0x1808cec30 start_wqthread + 4

Podfile.lock:
PODS:
  - Alamofire (4.5.1)
  - Bolts (1.8.4):
    - Bolts/AppLinks (= 1.8.4)
    - Bolts/Tasks (= 1.8.4)
  - Bolts/AppLinks (1.8.4):
    - Bolts/Tasks
  - Bolts/Tasks (1.8.4)
  - CocoaLumberjack (2.4.0):
    - CocoaLumberjack/Default (= 2.4.0)
    - CocoaLumberjack/Extensions (= 2.4.0)
  - CocoaLumberjack/Core (2.4.0)
  - CocoaLumberjack/Default (2.4.0):
    - CocoaLumberjack/Core
  - CocoaLumberjack/Extensions (2.4.0):
    - CocoaLumberjack/Default
  - Crashlytics (3.9.3):
    - Fabric (~> 1.7.2)
  - Device (3.0.3)
  - DynamicColor (4.0.1)
  - ESTabBarController-swift (2.6)
  - Fabric (1.7.2)
  - FBSDKCoreKit (4.29.0):
    - Bolts (~> 1.7)
  - FBSDKLoginKit (4.29.0):
    - FBSDKCoreKit
  - Firebase (4.10.1):
    - Firebase/Core (= 4.10.1)
  - Firebase/Core (4.10.1):
    - FirebaseAnalytics (= 4.1.0)
    - FirebaseCore (= 4.0.17)
  - FirebaseAnalytics (4.1.0):
    - FirebaseCore (~> 4.0)
    - FirebaseInstanceID (~> 2.0)
    - GoogleToolboxForMac/NSData+zlib (~> 2.1)
    - nanopb (~> 0.3)
  - FirebaseAppIndexing (1.2.0)
  - FirebaseCore (4.0.17):
    - GoogleToolboxForMac/NSData+zlib (~> 2.1)
  - FirebaseInstanceID (2.0.9):
    - FirebaseCore (~> 4.0)
  - GoogleAnalytics (3.17.0)
  - GoogleIDFASupport (3.14.0)
  - GoogleTagManager (3.15.2):
    - GoogleAnalytics (= 3.17.0)
  - GoogleToolboxForMac/Defines (2.1.3)
  - GoogleToolboxForMac/NSData+zlib (2.1.3):
    - GoogleToolboxForMac/Defines (= 2.1.3)
  - Kingfisher (3.13.1)
  - lottie-ios (2.1.5)
  - LUKeychainAccess (1.2.5)
  - MBProgressHUD (0.9.2)
  - Moya (8.0.5):
    - Moya/Core (= 8.0.5)
  - Moya-ObjectMapper (2.4):
    - Moya-ObjectMapper/Core (= 2.4)
  - Moya-ObjectMapper/Core (2.4):
    - Moya (~> 8.0)
    - ObjectMapper (~> 2.2)
  - Moya/Core (8.0.5):
    - Alamofire (~> 4.1)
    - Result (~> 3.0)
  - nanopb (0.3.8):
    - nanopb/decode (= 0.3.8)
    - nanopb/encode (= 0.3.8)
  - nanopb/decode (0.3.8)
  - nanopb/encode (0.3.8)
  - ObjectMapper (2.2.9)
  - OCMock (3.4)
  - ProtocolBuffers-Swift (3.0.23)
  - PureLayout (3.0.2)
  - Result (3.2.3)
  - SwiftyStoreKit (0.11.1)

DEPENDENCIES:
  - Alamofire
  - CocoaLumberjack (~> 2.4.0)
  - Crashlytics (~> 3.9)
  - Device
  - DynamicColor (from `https://github.com/puelocesar/DynamicColor.git`, commit `cf9478bbc2dfda8895cb3630418ba53e3d680eca`)
  - ESTabBarController-swift (from `https://github.com/eggswift/ESTabBarController`, tag `2.6`)
  - Fabric (~> 1.7.0)
  - FBSDKCoreKit (~> 4.29.0)
  - FBSDKLoginKit (~> 4.29.0)
  - Firebase (~> 4.10.1)
  - FirebaseAppIndexing
  - FirebaseCore
  - GoogleIDFASupport
  - GoogleTagManager
  - Kingfisher (~> 3.x)
  - lottie-ios
  - LUKeychainAccess (~> 1.2.0)
  - MBProgressHUD (~> 0.9.2)
  - Moya (~> 8.0.0)
  - Moya-ObjectMapper
  - OCMock (~> 3.2)
  - ProtocolBuffers-Swift
  - PureLayout
  - SwiftyStoreKit

EXTERNAL SOURCES:
  DynamicColor:
    :commit: cf9478bbc2dfda8895cb3630418ba53e3d680eca
    :git: https://github.com/puelocesar/DynamicColor.git
  ESTabBarController-swift:
    :git: https://github.com/eggswift/ESTabBarController
    :tag: 2.6

CHECKOUT OPTIONS:
  DynamicColor:
    :commit: cf9478bbc2dfda8895cb3630418ba53e3d680eca
    :git: https://github.com/puelocesar/DynamicColor.git
  ESTabBarController-swift:
    :git: https://github.com/eggswift/ESTabBarController
    :tag: 2.6

SPEC CHECKSUMS:
  Alamofire: 2d95912bf4c34f164fdfc335872e8c312acaea4a
  Bolts: 8a7995239dbe724f9cba2248b766d48b7ebdd322
  CocoaLumberjack: aa9dcab71bdf9eaf2a63bbd9ddc87863efe45457
  Crashlytics: dbb07d01876c171c5ccbdf7826410380189e452c
  Device: 9a5264ee4e0f392e7153d2c46b10c8df46b7aad2
  DynamicColor: 22bbab2db3bffb03a731ed8f001feaec5bea6ba6
  ESTabBarController-swift: d5e7dd83b06917d9805111de063c8edd9468e485
  Fabric: 9cd6a848efcf1b8b07497e0b6a2e7d336353ba15
  FBSDKCoreKit: 6f139173dc63a1deaff4430a55f2fe5bb222d2af
  FBSDKLoginKit: 56a057ca6822535ea0faa25f57a7c41edb697fd4
  Firebase: 92c6ba593e32db0defde464a9adc981d5cb49f97
  FirebaseAnalytics: 3dfae28d4a5e06f86c4fae830efc2ad3fadb19bc
  FirebaseAppIndexing: adf2f3b14b6828f1d4c539fc72434962cf29ea2c
  FirebaseCore: 872307b001bbefda1dfa0dbfffa50a6919023d4a
  FirebaseInstanceID: d2058a35e9bebda1b6dd42486b84917bde552a9d
  GoogleAnalytics: f42cc53a87a51fe94334821868d9c8481ff47a7b
  GoogleIDFASupport: aaf8c10bd429abb1c15349d5252244f5eda8ead1
  GoogleTagManager: 43b61f634e42e4b9566ab41e9fd6aa0f6adf47a5
  GoogleToolboxForMac: 2501e2ad72a52eb3dfe7bd9aee7dad11b858bd20
  Kingfisher: ed9707a409cc47fddafbcd12a43a9757e3600af5
  lottie-ios: 836cdbba92f62f3c6a00e37a4ce485321fe317cf
  LUKeychainAccess: d22fc00b33ad92c7532962b86daa94c14b85ecbe
  MBProgressHUD: 1569cf7ace17a8bac47aabfbb8580a49690386d1
  Moya: c37eec09a098ba9991b5a963b291fc5704bdb9ef
  Moya-ObjectMapper: 5807a3f30fea8fd07a9fc0e324cda1655e1602ab
  nanopb: 5601e6bca2dbf1ed831b519092ec110f66982ca3
  ObjectMapper: 63cfe41bc6f8e7c8f44344c49901b8ae7de14c52
  OCMock: 35ae71d6a8fcc1b59434d561d1520b9dd4f15765
  ProtocolBuffers-Swift: e0b959c0fbb5dcadb3846f9b42c2cbfae6918422
  PureLayout: 4d550abe49a94f24c2808b9b95db9131685fe4cd
  Result: 128640a6347e8d2ae48b142556739a2d13f90ce6
  SwiftyStoreKit: d52d1473f5baf8385c86d7455c9f6b0d0a74cef2

PODFILE CHECKSUM: 0435e038b75d5be9e4cd0e98a6ed9aa130217f8f

COCOAPODS: 1.4.0

@baolocdo can we fix this by just early-exiting and returning nil in -[FIRAPBMeasurementConfig initWithBuffer:]?

Yes, I think it would solve it. By the way, where's the FIRAMeasurement class? I can't find it on Firebase code.

FIRAMeasurement is part of FirebaseAnalytics which has not open sourced.

Filed a bug at b/77468768

I still this bugs in the lasted version.

Internally tracked at b/77468768. It would be nice to be able to reproduce the issue by having some sample project. Thanks

Hi!
Seems we are experiencing the same crash (XCode version: 9.3):
Crashed: com.google.fira.worker
EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0000000000000000

Stack trace:
0 libsystem_platform.dylib _platform_memmove + 296
1 nanopb pb_decode.c - Line 808 pb_field_set_to_default
2 nanopb pb_decode.c - Line 808 pb_field_set_to_default
3 nanopb pb_decode.c - Line 845 pb_message_set_to_defaults
4 nanopb pb_decode.c - Line 959 pb_decode
5 <appname> firapb_decode_measurement_config +<PHONE_NUMBER>
6 <appname> -[FIRAPBMeasurementConfig initWithBuffer:] +<PHONE_NUMBER>
7 <appname> __72-[FIRAMeasurement networkRemoteConfigFetchCompletionHandler:data:error:]_block_invoke.1476 +<PHONE_NUMBER>
8 <appname> -[FIRASqliteStore performTransaction:] +<PHONE_NUMBER>
9 <appname> -[FIRAMeasurement networkRemoteConfigFetchCompletionHandler:data:error:] +<PHONE_NUMBER>
10 <appname> __36-[FIRAMeasurement fetchRemoteConfig]_block_invoke +<PHONE_NUMBER>
11 libdispatch.dylib _dispatch_call_block_and_release + 24
12 libdispatch.dylib _dispatch_client_callout + 16
13 libdispatch.dylib _dispatch_queue_serial_drain$VARIANT$mp + 608
14 libdispatch.dylib _dispatch_queue_invoke$VARIANT$mp + 336
15 libdispatch.dylib _dispatch_root_queue_drain_deferred_wlh$VARIANT$mp + 340
16 libdispatch.dylib _dispatch_workloop_worker_thread$VARIANT$mp + 668
17 libsystem_pthread.dylib _pthread_wqthread + 860
18 libsystem_pthread.dylib start_wqthread + 4

PODS:
PODS:
  - Crashlytics (3.10.1):
    - Fabric (~> 1.7.5)
  - DynamicBlurView (2.0.2)
  - Fabric (1.7.6)
  - Firebase/Core (5.0.0):
    - Firebase/CoreOnly
    - FirebaseAnalytics (= 5.0.0)
  - Firebase/CoreOnly (5.0.0):
    - FirebaseCore (= 5.0.0)
  - FirebaseAnalytics (5.0.0):
    - FirebaseCore (~> 5.0)
    - FirebaseInstanceID (~> 3.0)
    - "GoogleToolboxForMac/NSData+zlib (~> 2.1)"
    - nanopb (~> 0.3)
  - FirebaseCore (5.0.0):
    - "GoogleToolboxForMac/NSData+zlib (~> 2.1)"
  - FirebaseInstanceID (3.0.0):
    - FirebaseCore (~> 5.0)
  - GoogleToolboxForMac/Defines (2.1.4)
  - "GoogleToolboxForMac/NSData+zlib (2.1.4)":
    - GoogleToolboxForMac/Defines (= 2.1.4)
  - nanopb (0.3.8):
    - nanopb/decode (= 0.3.8)
    - nanopb/encode (= 0.3.8)
  - nanopb/decode (0.3.8)
  - nanopb/encode (0.3.8)
  - PopupDialog (0.7.1):
    - DynamicBlurView (~> 2.0)

The crash is 100% reproducible using below steps:

make sure application is NOT installed,
install the application,
run the application,
on first screen (or any screen for that matter) put the application into background and back to foreground.

This will cause application to crash (not sure when the app crashes - either when going to background or when coming back to foreground) - bottom point is that it crashes 10/10.
Notes:

from this point on, application works without any problems and cannot reproduce the crash anymore unless we repeat the above steps;
not 100% sure, but it seems the crash only happens when app is builded on the build server - build with an enterprise certificate, not sure if this makes any sense to anybody, but we cannot reproduce the crash on developer machines, only with builds coming from build server and the only difference I can think of is the signing.

Tried to build the project on the build server directly using XCode (archive, export, sign with enterprise cert) to rule out the signing and crash cannot be reproduced. Seems like issue is related to fastlane build, still not sure why, just wanted to share.

OK, just found the reason why it was crashing, hope it might help someone - in fastlane, we had:
gym( ... xcargs: "GCC_PREPROCESSOR_DEFINITIONS='SOMEFLAG=1'",  ....)
which removed all other defines, so replacing it with:
gym( ... xcargs: "GCC_PREPROCESSOR_DEFINITIONS='$(inherited) SOMEFLAG=1'",  ....)
fixed the crash.

We have that same crash when be build with crashlytics and via xcodebuild. The build flags solution does not solve the crashes neither the bug decribed in issue . However both seems to have the reason somehow in nanopb.

Since we don't have access to source code to try to understand why this crash, can anyone at Firebase team take a look at this and provide at least a workaround?

I think you have to set PB_FIELD_32BIT=1 PB_NO_PACKED_STRUCTS=1 in your GCC_PREPROCESSOR_DEFINITIONS for your xcodebuild. Otherwise nanopb will crash during runtime, which is used by FIRAPBMeasurementConfig. Normally the configuration is inherited, be sure you don't override the GCC_PREPROCESSOR_DEFINITIONS as we accidentally. So now it works for us.

I'll try that, thanks!

I used xcodebuild over the command line with Firebase 5.2.0.
xcodebuild -workspace <workspace> -scheme <scheme> -sdk iphoneos -configuration Release ARCHS="arm64 armv7" GCC_PREPROCESSOR_DEFINITIONS="PB_FIELD_32BIT=1 PB_NO_PACKED_STRUCTS=1" clean build

I could reproduce @crnjan 's crashes with going to background and back again today when I missed adding the GoogleToolboxForMac framework to our project that uses Firebase Analytics. No (linker) errors, no nothing except for a very short stack trace.
Adding the framework fixed it for us.

Thanks to @xaverlohmueller, adding GoogleToolboxForMac.framework fixed my problem.

@puelocesar is this still an issue?


Just a few small things.

Mostly I made an attempt at storing login in local storage but things got out of hand so I undid everything and I think I did no harm.

matt, if you want to just restore things do we need this pull request?

I fixed the major things. This is just for the small stuff I did.


STYLE: Use local include syntax to include ITK files

Use local include syntax to include ITK files.
PR Checklist

[X] No API changes were made (or the changes have been approved)
[X] No major design changes were made (or the changes have been approved)

ITK.macOS.Python failure is unrelated.

@jhlegarreta There are merge conflicts that need to be addressed.

@jhlegarreta There are merge conflicts that need to be addressed.

Done in 24f2892.


Number sequence is not transcribed when a chunk starts with it

I'm attaching an audio file (it's reproducible with longer files split into chunks).
Disabling VAD helps but it does not explain the issue because VAD correctly identifies where speech stars (around 2.5 seconds).
It affects both batch and non-batch methods.
With VAD:
chunks_metadata [{'start_time': 2.416, 'end_time': 12.72}]
duration_after_vad 10.304
Sentence: [0 7.83s -> 12.13s]  It's important that that first piece can't be misinterpreted as a decimal.
Without VAD:
chunks_metadata [{'start_time': 0.0, 'end_time': 13.11925}]
duration_after_vad 13.11925
Sentence: [0 3.42s -> 12.14s]  8892. It's important that that first piece can't be misinterpreted as a decimal.
digit-speech.zip

Whisper model can just miss something in transcription for no apparent reason
A one byte change in audio can trigger a different result
A one token change is prompt can trigger different result

Btw, for me it's opposite. with VAD "8892" appears, without VAD it disappears. 😄
Maybe for model it's unusual to start with digits, try initial_prompt="OK"


cmd/cgo/internal/test: seg fault on linux-arm-aws builder

The dashboard shows cmd/cgo/internal/test seg faults on the linux-arm-aws builder since https://golang.org/cl/508135 . Specifically, it is cmd/cgo/internal/test:static failing.  Also the same failure on trybot https://go-review.googlesource.com/c/go/+/320910/3#message-34862db7fe6eb712e5699ce7ab0a7f53aed5a2e5
However, I tried to run all.bash or go tool dist test cmd/cgo/internal/test:static on the linux-arm-aws gomote and it doesn't fail. I double checked that the environment looks the same for gomote and the builder.
It is strange as CL 508135 shouldn't change anything semantically (even the order of sorted items). It is double strange that the failure is not reproducible locally.
Filing an issue to investigate.

Thanks for filing the issue, @cherrymui -- this is very odd, indeed.
Could the test be failing sporadically after all (and we get unlucky), maybe running it locally with a high count can hit a failure?

Anything is possible, but the build dashboard shows the test failing consistently since that CL and never before that CL.

I tried running go tool dist test cmd/cgo/internal/test:static in a loop for 100 times and it doesn't fail. I'm now trying to do some experiments with trybots in CL 511978

Did some experiments on CL 511978. Essentially if I change any function(s) to use old code, like https://go-review.googlesource.com/c/go/+/511978/8/src/sort/sort_impl_go121.go , or https://go-review.googlesource.com/c/go/+/511978/9/src/sort/sort_impl_go121.go , trybot passes. It fails if all functions using new implementation. (They all pass on gomote.)
On the other hand, on the build dashboard it passes again since CL https://go.dev/cl/511837 .
Maybe there is something weird on the builder for that time, or how the test are run on the builder/trybot (bad caching?).
Anyway, closing for now. We can reopen if it occurs again.


Compile using compact mode

https://blog.mariusschulz.com/2016/07/12/speeding-up-babel-transpilation-with-compact-mode
tl;dr: Babel's compact mode seems to speed up compilation time (although it doesn't seem like it has a too huge compact for Mozaik)

@kurtextrem, the post have been updated, this setting doesn't seem to be relevant anymore as default is sensible enough. BTW, thank for trying to improve Mozaïk!


docs: update the upgrading guide

Latest React Native CLI will bring an improved upgrade command, see: https://github.com/react-native-community/react-native-cli/pull/176
This PR attempts to document it.
cc @cpojer @pvinis @kelset

Feedback is addressed, I believe :)


Never connects when using reconnect method after forced close

Hi,
I've been using you lib for a long time, but today I made some updates in my code to force close on websocket active instance, but when I try to reconnect I have no luck.
Looking the code the _closeCalled flag is still true, probably the reconnect method may set it to false.
https://github.com/pladaria/reconnecting-websocket/blob/master/reconnecting-websocket.ts#L360
I'm using this in react-native environment, basically my code close websocket instance when app goes to background and reconnects when app goes to foreground, so here is the piece of code (websocketConnect method called when app in foreground / first time, websocketDisconnect on background):

const ws = null;

export const websocketConnect = () => async (dispatch, getState) => {
  if (!ws) {
    ws = new ReconnectingWebSocket(Settings.WEBSOCKET_URL, [], {
      debug: __DEV__
    });
    // stubs
  } else {
    ws.reconnect();
  }
};

export const websocketDisconnect = () => async (dispatch, getState) => {
  if (ws) {
    ws.close();
  }
};

Thanks !!!

Hi,
Thanks for reporting. Fixed in 4.1.6
Let me know if you find any other issue

wooow,
awesome @pladaria, now it works as expected thanks for your time, really appreciated 🎉
even you add a missing else statement to make disconnection when websocket is already connected.
Thanks once again !!!


Does Multiple work?

Using the multiple option seems to do nothing and have no effect on the output html. Is this an option that's supposed to be working?

@PeteMichaud, The :multiple option must be used in conjunction with data-delimeter and should result in an array being submitted rather than multiple values combined into a single delimited string.  From the client side it should look the same.
If it is not working like this it would be helpful if you could post a GitHub link to a minimal project implementation replicating the issue.
form_for @product do |f|
  f.autocomplete_field :brand_names, autocomplete_brand_name_products_path,
  'data-delimiter' => ',', :multiple => true
end


[enhancement] Create PerValidatorQueue which implements MessageQueue

Summary
PerValidatorQueue is an implementation of the MessageQueue trait. It internally uses a HashMap  Validators => Queue<Message> to store messages per validator. The Queue is configurable to be FIFO or LIFO and the max Queue size per Validator is also configurable.
When popping messages, PerValidatorQueue performs round robin among validators which have pending messages and sends them out one by one.
In addition to the HashMap, the PerValidatorQueue data structure also stores a Vec<Validator> and a HashSet<Validator>. These two collections represent the set validators which have messages pending and are used for performing round-robin.
Related to #1323
Test Plan
Added unit tests

I might be missing something but I think we could implement the round-robin in a simpler way. Do you think we could have a queue of pending validators (implemented by a VecDeque)?
Something like this:
fn push(&mut self, message: Self::Message) {
  let validator = message.get_validator();
  if !self.has_messages_pending(validator) {
    self.pending_validators.push_back(validator);
  }
  ...
}

fn pop(&mut self) -> Option<Self::Message> {
  if let Some(validator) = self.pending_validators.pop_front() {
    let msg = self.next_msg(validator);
    if self.has_messages_pending(validator) {
      self.pending_validators.push_back(validator);
    }
    Some(msg)
  }
  None
}

fn has_messages_pending(&self, validator: AccountAddress) -> bool {
  self.per_validator_queue.get(validator).map_or(false, |msgs| !msgs.is_empty())
}

In case it's more complicated we could isolate the logic of picking the validator to a separate struct: the current functions are a little bit confusing.

:v: @ankushagarwal can now approve this pull request

Regarding multiple commits, I used --fixup for the minor changes. My understanding is that bors-libra would automatically squash them into a single commit.

@bors-libra r+

:pushpin: Commit 5dc4b92 has been approved by ankushagarwal

:hourglass: Testing commit 5dc4b9298fd4d4d3b73938b1cfef098248c910ef with merge 010d7ae4e42379313e092f1c82fd8454a33a3f17...

@bors-libra r+

:pushpin: Commit 257c6ed has been approved by ankushagarwal

:hourglass: Testing commit 257c6ed2c9ce2ce656652f59dbcb9436b85165d8 with merge 6dd665b787bce2dc1d20d56d43c80982e92bb706...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: ankushagarwal
Pushing 6dd665b787bce2dc1d20d56d43c80982e92bb706 to master...


Toggled Voice state isn't persisted

Issue:
Even if you toggle voice state to disable it while you are editing and using the extension, it isn't persisted on the contribution configuration for the extension. If you down and up vscode and use it again, the extension read the voice state (enabled/disable) from the configuration.
Goal:
If you toggle voice state to disable or enable it while you are editing, it should be persisted on the contribution configuration for the extension.

The issue has been fixed in 0.2.0

https://github.com/yokawasa/vscode-translator-voice/releases/tag/0.2.0


Does not create lstmf file: Compute CTC targets failed!

I have tried to train this bengali data.
I have run this command:
make training MODEL_NAME=ben RATIO_TRAIN=0.90 LANG_TYPE=Indic TESSDATA=/mnt/c/T.Faisal/OFFICE/tesstrain START_MODEL=ben GROUND_TRUTH_DIR=data/ben-ground-truth DATA_DIR=data
I have used the best traineddata from here.
But it does not generate lstmf file in ben-ground-truth folder for all images like an example<PHONE_NUMBER>_fathers_name_info.png in data. It also gives Normalization failed for string. You can check here: ben-ground-truth.zip
And it gives the following output.

It's very little data and it isn't properly segmented. IIUC you have just seven images in the data and of those, some are two lines (e.g.<PHONE_NUMBER>_address_info.png) or even three lines (e.g.<PHONE_NUMBER>_address_info.png).
So I suggest you get some more data and make sure that the image-ground-truth pairs are only a single line.

Thank you for your reply @kba. Can you describe to me what do you mean by "it isn't properly segmented"?

tesstrain (and every modern trainable OCR engine) is trained on line-wise image/text ground-truth. As I said, you have multi-line images in there, that should be split into individual lines. @stefanCCS had a similar issue.

Thanks @kba for your help. I am closing this issue

Thanks @kba for your help. I am closing this issue.


pixi init --format pyproject && pixi shell fails

Checks

[X] I have checked that this issue has not already been reported.

[X] I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example
➜  ~ mkdir test2
➜  ~ pixi init --format pyproject
✔ Created /Users/zbowling/pyproject.toml
➜  ~ pixi shell
  × error updating pypi prefix
  ├─▶ Failed to prepare distributions
  ├─▶ Failed to fetch wheel: zbowling @ file:///Users/zbowling
  ├─▶ Failed to build: `zbowling @ file:///Users/zbowling`
  ╰─▶ Build backend failed to build wheel through `build_editable()` with exit status: 1
      --- stdout:

      --- stderr:
      Traceback (most recent call last):
        File "<string>", line 11, in <module>
        File "/Users/zbowling/Library/Caches/rattler/cache/uv-cache/environments-v0/.tmpK5v58O/lib/python3.12/
      site-packages/hatchling/build.py", line 83, in build_editable
          return os.path.basename(next(builder.build(directory=wheel_directory, versions=['editable'])))
                                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/Users/zbowling/Library/Caches/rattler/cache/uv-cache/environments-v0/.tmpK5v58O/lib/python3.12/
      site-packages/hatchling/builders/plugin/interface.py", line 155, in build
          artifact = version_api[version](directory, **build_data)
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/Users/zbowling/Library/Caches/rattler/cache/uv-cache/environments-v0/.tmpK5v58O/lib/python3.12/
      site-packages/hatchling/builders/wheel.py", line 494, in build_editable
          return self.build_editable_detection(directory, **build_data)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/Users/zbowling/Library/Caches/rattler/cache/uv-cache/environments-v0/.tmpK5v58O/lib/python3.12/
      site-packages/hatchling/builders/wheel.py", line 505, in build_editable_detection
          for included_file in self.recurse_selected_project_files():
                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/Users/zbowling/Library/Caches/rattler/cache/uv-cache/environments-v0/.tmpK5v58O/lib/python3.12/
      site-packages/hatchling/builders/plugin/interface.py", line 180, in recurse_selected_project_files
          if self.config.only_include:
             ^^^^^^^^^^^^^^^^^^^^^^^^
        File "/Users/zbowling/Library/Caches/rattler/cache/uv-cache/environments-v0/.tmpK5v58O/lib/python3.12/
      site-packages/hatchling/builders/config.py", line 806, in only_include
          only_include = only_include_config.get('only-include', self.default_only_include()) or self.packages
                                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/Users/zbowling/Library/Caches/rattler/cache/uv-cache/environments-v0/.tmpK5v58O/lib/python3.12/
      site-packages/hatchling/builders/wheel.py", line 260, in default_only_include
          return self.default_file_selection_options.only_include
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/Users/zbowling/.pixi/envs/default/lib/python3.12/functools.py", line 993, in __get__
          val = self.func(instance)
                ^^^^^^^^^^^^^^^^^^^
        File "/Users/zbowling/Library/Caches/rattler/cache/uv-cache/environments-v0/.tmpK5v58O/lib/python3.12/
      site-packages/hatchling/builders/wheel.py", line 248, in default_file_selection_options
          raise ValueError(message)
      ValueError: Unable to determine which files to ship inside the wheel using the following heuristics:
      https://hatch.pypa.io/latest/plugins/builder/wheel/#default-file-selection

      The most likely cause of this is that there is no directory that matches the name of your project
      (zbowling).

      At least one file selection option must be defined in the `tool.hatch.build.targets.wheel` table, see:
      https://hatch.pypa.io/latest/config/build/

      As an example, if you intend to ship a directory named `foo` that resides within a `src` directory located
      at the root of your project, you can define the following:

      [tool.hatch.build.targets.wheel]
      packages = ["src/foo"]
      ---

Issue description
Hatchling is failing to compile the pyproject which is the default that init produces as a build backend now after a recent commit to swap setuptools to hatchling.build
Change the init to this gets it to work:
[build-system]
requires = ["setuptools"]
build-backend = "setuptools.build_meta"
Expected behavior
Should work.

Hey @zbowling  👋🏻
To be honest, I wonder if what you see here is fine?
The error message is pretty clear and it also makes sense to me that if you have a pyproject.toml that there's also a corresponding python package.

The issue is you can't get into a shell to then use tools within the shell like python to help you generate the actual package since init doesn't generate a full package, just a pyproject.toml. Bit of a chicken and egg issue. Both pixi run and pixi shell shell fail immediately. This creates even more fun in vscode when you open the env in that folder. You get stuck in a loop.

Like if init something like hatch new and generated a src/, tests/, etc project with an empty init.py then it would be fine

I thought about it more and I agree with you. Let's adapt pixi init accordingly!

I think we talking about adding a proper init template system at one point. there is a feature bug for that. Something like npm init so we can generate off scaffolds. that would help us down here downstream in mojo a ton :) but then we can have a hatch or poetry or pdm style init generation for different backends. long term bigger solution maybe.

also build backend failures to install the current project by pypi into the current env that can prevent a pixi shell and pixi run to execute is also a fun meta problem. You could be in the middle of working on your code and if your code doesn't work then your shell might not start but then you can't use tools in your env to help you debug those issues. Thinking out loud but if uv can't install the package for the current directory then maybe not fail to create a shell? Just hobble along? I don't know the right answer but decoupling failing to install the current folder from the env maybe somehow?

Related issue: https://github.com/prefix-dev/pixi/issues/1903
Maybe we should just create a source hierarchy for now if it does not exist?
I do agree with @zbowling that there is maybe more to this and we should think about it a bit more, but I feel it might be a good short term solution?


Discord Linux Application

What is your username and discriminator?
computer_geek64#7076
Why did you join Discord Linux?
I'm a daily (Kali) Linux user, and I want to join a community where I can talk to other Linux users.
Where did you hear about Discord Linux?
Discord.me
What is the passphrase that was assigned to you by the bot?
248181238278520832

From simonizor#0420 :
The passphrase you have entered is not correct.  Please check the message that mentions you in the welcome channel to find your passphrase.

From simonizor#0420 :
Closing as it has been more than 24 hours.


Add-GSTeamDriveMember

Hi Nate,
Is there already a way to add users as members to a team drive and set their permissions?
I have tried:
Update-GSTeamDrive -TeamDriveId 0AMJaWArZXy3jUk9PVA -User my-test-user -CanComment
but get:
Update-GSTeamDrive : Exception calling "Execute" with "0" argument(s): "Google.Apis.Requests.RequestError
The operation was successful, but there was an error preparing the response. [500]
Errors [
Message[The operation was successful, but there was an error preparing the response.] Location[ - ]
Reason[responsePreparationFailure] Domain[global]
]
"
At line:1 char:1

Update-GSTeamDrive -TeamDriveId 0AMJaWArZXy3jUk9PVA -User my-test-use ...

  + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
  + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Update-GSTeamDrive

Cheers,
Neil

As an additional I would like to be able to add users and groups as members to team drives.

hey @n-searle - Totally doable! You can see a sample below, but the command you're looking for is Add-GSDrivePermission 😃 There's a Type` parameter on that where you specify if the permission is for a User, a Group, the Domain, or Anyone:
Add-GSDrivePermission -User $OwnerOfDriveFile -FileId $TeamDriveId -Role Commenter -Type User -EmailAddress<EMAIL_ADDRESS>

Awesome, will give it a shot cheers.

Cool! Let me know if you run into any issues, otherwise close this out if you're comfortable!


No  Output to Console

Note: this is the technical bug tracker, please use other platforms for getting support and starting a (non technical) discussion. See the getting help page for details.
I'm submitting a ...
[X] bug report
[ ] question about the decisions made in the repository
Action taken (what you did)
I recently updated my gekko version to the latest one. I was running a version from last year and thought it was time to ugrade. Now I've noticed that there is no console output anymore.  My strats are using log.info("...") to send status and actions to the console. Now with the latest gekko version no output is shown. I did already checked core/log but could not found the issue.
Thanks for helping in advance.
Best,
Chris

#2451
same issue and same solution
therefore closing this one
sry


GPS stuck on searching, except when I'm running GPSTest at the same time.

I noticed the app is never able to detect any kind of GPS signal, so I installed GPSTest to see if I couldn't figure out what the problem was... and then it started working, until I stopped GPSTest, at which point it instantly lost the signal again.
I've noticed this happens with certain other apps as well, for example BLE Radar but not with others, like Organic Maps.
Maybe there are different ways of accessing GPS location?
I'm using the Nothing Phone 1 and have Magisk and MicroG, in case that affects it.

Hi, can you try the following:

Under Trail Sense Settings > Sensors > GPS, disable "Require satellite fix"
If that doesn't help, can you open Trail Sense Settings > Diagnostics and let me know if there are any issues reported

For reference, in the nightly builds I updated how Trail Sense determines how many satellites there are since some phones were not populating the satellite count directly (#1942). If you would like to see if this is fixed on the nightly build, that would be greatly appreciated. Details on the nightly builds can be found here: https://github.com/kylecorry31/Trail-Sense/discussions/1940

Disabling "Require satellite fix" solved my problem, but the satellite count still displayed as 0, on the nightly build though everything worked correctly (GPS signal is found and satellites show up, both with and without "Require satellite fix").
Seems like it's the satellite count issue you mentioned then, thanks!

Glad that worked, and thanks for testing out the nightly build! It was hard for me to test that that new method myself since my device manufacturer populates the satellite count using the old method as well, so this was perfect timing.


Version A

Bug fix for Save (all three required fields must be in place to enable Save, however Removal Reason is only relevant if Markup = Remove)
Bug fix for Removal Reason:  I can still get it to save Null by leaving Removal Reason blank and filling in a Comment (which makes the Save button available)!
Change colours for Presence symbology (in map and legend), leaving transparency as is

Present = 76, 0, 115
Presence Expected 169, 0, 230
Historical = 223, 115, 255

removal reason bug seems to be fixed with previous check-in from the developer branch. cannot repro on local build


pass classes through to cytoscapejs

The classes attribute of nodes and edges wasn't making it all the way to the actual cytoscapejs object. This PR brings those attributes all the way through, thereby enabling using selectors based on classes.

Hey @ianhi, thanks! :)
Huh, I forgot about this completely since I never really used them.
Thank you so much for the catch! I'll open an issue to fix the rest!


Error with Remote MySQL: no dbhost passed to wp-cli when creating config

In version 3+ when creating a new site we get an error like so:
Unable to move file from /var/www/testsite222.com/htdocs/wp-config.php to /var/www/testsite222.com
From testing on our beta box it looks to be a problem with site_functions.py - setupwordpress
the dbhost for our remote server is not supplied and we do not have mysql running on localhost. This causes wp-cli to throw an error and no config file is created.
This in turn causes the unable to move error.


Added functionality to write CSV and JSON output to file

Implemented with sys.stdout = open(args.output).


FIX: Location permission fix on Android 12 an higher

This issue is related to the emulator, not the application. On real device everything works well.


Updating tests to Nunit 3

Current coverage is 59.64%

Merging #12 into master will not affect coverage as of 81fe214

@@            master     #12   diff @@
======================================
  Files           13      13
  Stmts          902     902
  Branches       119     119
  Methods          0       0
======================================
  Hit            538     538
  Partial         29      29
  Missed         335     335

Review entire Coverage Diff as of 81fe214

Powered by Codecov. Updated on successful CI builds.


Add godotcpp 3.4.3

Scons 4.3.0 is required for Visual Studio 2022 support (#1041)

This PR should be ready. Msys2 is failing because of a different reason


Add laby.net extension

Description
This extension two commands for searching laby.net. Laby.net is a Minecraft profile database with skins and capes.
One command adds a profile search for quickly converting a username to the corresponding uuid and allows to open their profile to see their skins and capes.
The second command adds a texture search that allows to quickly glance at how many users a certain cape/skin has and to open the page to download the skin.
Screencast
https://user-images.githubusercontent.com/7442307/205350411-d99e2346-0e06-4efa-b08e-310a86734f10.mov
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

error  Wrong size: 1000 x 625 pixels. Required size is 2000 x 1250 pixels

I was using the Window Capture feature to take these screenshots, should I just do these manually then?

@neemspees That worked, thanks!


HPA should be linked from user-guides for Deployment and RC

I think it'll help users find out about this feature.
User guides:
http://kubernetes.io/docs/user-guide/managing-deployments/
http://kubernetes.io/docs/user-guide/deploying-applications/
@mwielgus @bgrant0607

@fgrzadkowski  Any reason why you can't make this change in a PR? It would probably take as long as it did to file this bug? :)

cc @janetkuo @pwittrock

We're adding content about Deployment to the thorough walkthrough now.

Managing deployments doc already links to hpa --> http://kubernetes.io/docs/user-guide/managing-deployments/#scaling-your-application
Do you think it's observable enough for the users?


Functions returning None if the type is incorrect

All functions return None if the input geometry is not the correct type, instead of raising an exception.
I suggest changing, for example, this:
    if isinstance(geometry, LineString):
        return LineString(catmullrom(geometry.coords, alpha, subdivs))
    elif isinstance (geometry, Polygon):
        return Polygon(catmullrom(geometry.exterior.coords, alpha, subdivs),
                       [catmullrom(hole.coords, alpha, subdivs) for hole in
                        geometry.interiors])
    elif isinstance (geometry, list):
        return catmullrom(geometry, alpha, subdivs)

to
    if isinstance(geometry, LineString):
        return LineString(catmullrom(geometry.coords, alpha, subdivs))

    if isinstance (geometry, Polygon):
        return Polygon(catmullrom(geometry.exterior.coords, alpha, subdivs),
                       [catmullrom(hole.coords, alpha, subdivs) for hole in
                        geometry.interiors])
    try:
        mp = MultiPoint(geometry)
    except (TypeError, AttributeError, ValueError) as ex:
        raise TypeError("`geometry` must be either LineString, Polygon, or list of (x, y) coordinates.") from ex

    return catmullrom([(p.x, p.y) for p in mp.geoms], alpha, subdivs)

I can open a PR if interested.

I'll open a PR.

Any reason why you'd prefer try: mp = MultiPoint(... over simply adding else: raise TypeError(...?

The reason is that MultiPoint supports all combinations of list of tuples, list of lists, tuple of tuples, tuple of lists, and numpy arrays. So, this way, the function does not strictly require users to pass only a list of tuples.


ci: use Allure reports

Description
Adds Allure reports to our unit and E2E tests.
@igorgn, can we have Allure CLI installed on our CI machines here?
./scripts/ci.sh: line 21: allure: command not found

Allure is not installed

Congratulations, we have first Allure reports on CI.

👏🏼 👏🏼 👑


FIX and Add options to chart2music plotly integration

Green!

Not really sure how we should proceed, if you want to keep on approving my pull requests so I can add to your pull request or if you give me permission to post to your repo here (is that possible?). It's up to you.

[x] Updates w/ master.
[x] Adds options to let dev control placement of closed caption div
[x] Defaults from plot_config.js weren't loading during testing, so we check and reinforce at runtime. Don't love this.
[x] Change default dev control placement to NOT generate a closed caption div- dev must create it.

I will post a larger comment in the pull request right now about how to move forward this.
PS. saving this link because otherwise pull requests are hard to make....
https://github.com/aliwelchoo/plotly.js/compare/aliwelchoo:plotly.js:chart2music...geopozo:plotly.js:pikul-music-import-promise

I can give you access here, will do that!


fix(ci): Added extension parameter to distinguish between zip and exe

Description

Fixes issue with new deployment mechanism looking for .exe files instead of .zip

Added a extension parameter to the job that will be set on the config generator.
Type of change

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)

How has this been tested?

Manual Tests (please write what did you do?)

Ran the validation and generator loally.
Docs

No updates needed

I accept the consequences of not waiting for a reviewer. But since its a CI only change, it's safe enough.


Re-order plot sections to match usage

Reorder the layout of the sensor pages

This PR is targetting v0.2.x as it should, but the changes were based on master, leading to the commits and diffs being all borked. To fix this, in your branch, run the following command:
git rebase --onto v0.2.x master new_layout

And fix any merge conflicts (there shouldn't be any, AFAIK).
Otherwise, LGTM, thanks.

This PR is targeting v0.2.x as it should, but the changes were based on master, leading to the commits and diffs being all borked. To fix this, in your branch, run the following command:
git rebase --onto v0.2.x master new_layout

And make sure to fix any merge conflicts (there shouldn't be any, AFAIK).

Alright, should be good to go now!

Unfortunately looks like it did a weird merge of some sort instead. I'll take a crack at fixing it myself, hold on (same caveats as #12 apply if you want to re-pull the fixed commits).

@pbitzer Huh, I dropped the spurious merge comment and then re-ran the exact command above on your branch and it worked exactly as expected, so I'm not sure what went wrong. Good 'ole git, I guess...looks good now.