fix: check agent safe in low funds, update thresholds

Proposed changes

Apply these changes: https://valory-workspace.slack.com/archives/C07CKA5TN5V/p1734958844685979?thread_ts=1734723917.174429&cid=C07CKA5TN5V

Check agent safe in low funds as per this (2d point) https://valory-workspace.slack.com/archives/C07CKA5TN5V/p1734953185330669?thread_ts=1734723917.174429&cid=C07CKA5TN5V

Types of changes
What types of changes does your code introduce?
Put an x in the boxes that apply

[ ] Bugfix (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)

released as rc54 @Tanya-atatakai


Feat/add protocol fee

Thanks @bonomat for the comments! I accidentally opened this PR against the p2pderivatives repo, rather than my own fork. So I'll close this, but I appreciate you jumping in with some feedback! Let me know if you have any questions or comments!

Thanks @bonomat for the comments! I accidentally opened this PR against the p2pderivatives repo, rather than my own fork. So I'll close this, but I appreciate you jumping in with some feedback! Let me know if you have any questions or comments!

No worries, feel free to ping me if you want further feedback on this.


add displayName in component

To support 中文名称，we can add a annotation in Chart.yaml like
apiVersion: v2
name: core
annotations:
  core.kubebb.k8s.com.cn/displayname: "内核"
description: Kubebb Core provides core implementations on Component Lifecycle Management.Our design and development follows operator pattern which extends kubernetes APIs.
type: application
version: v0.1.12
appVersion: v0.1.4
icon: https://avatars.githubusercontent.com/u/85277200
keywords:
  - repository
  - helm
  - lifecycle-management
sources:
  - https://github.com/kubebb/core
maintainers:
  - name: bjwswang
    url: https://github.com/bjwswang
  - name: Abirdcfly
    url: https://github.com/Abirdcfly
  - name: 0xff-dev
    url: https://github.com/0xff-dev

When repository controller sync the components, we extract the annotation to component.

When pushed a new version with different displayname in annotation,we keep the latest one


load lapack,blas headers from Accelerate.h

vecLib/clapack.h doesn't work on OS X 10.10, and I think has been deprecated for some time.
I'm not sure for how many versions Accelerate.h works here, but I think it's at least a few.
This was the only patch I needed for proteus to build on 10.10.

let me check quickly on 10.9

yup, looks good.

I think Accelerate.h should be good back to 10.6, but I'm not certain.

It's up to @cekees on what he wants to continue to support, but I tend to merge if it works on at least 10.9, and at this point, if I'm pretty sure it won't break 10.10.

What are you using for your Fortran compiler, homebrew gfortran?

yup


Size of lime installation

Hello,
The only class I'm using from lime is LimeTextExplainer. I'm trying to fit it into AWS lambda limitation which is 250 mb. Lime alone with all dependencies has this size. Do you know maybe a way how to shrink it?

lime itself is quite small (the egg is less than 400kb). I don't know which of the dependencies are large (I'm guessing skimage, maybe scipy?). One thing you could do is install it with only the dependencies you need (e.g. remove skimage if you're not using LimeImageExplainer).


Docs common deploy results

Category

[x] New Feature

What's in this Pull Request?
Documentation - initial output of common results when executing deploy.ps1.

thx Eric, appreciated.


Attempting to use on Rasberry Pi 3: ValueError: Namespace Gst not available

I have a Rasberry Pi 3 running Raspbian GNU/Linux 9 (stretch).
I get the following error after installing playsound and trying to test following the instructions here: https://pypi.org/project/playsound/
pi@raspberrypi:~/Desktop $ python test.py
Traceback (most recent call last):
  File "test.py", line 2, in <module>
    playsound('./Desktop/DEFCON level change.mp3')
  File "/home/pi/.local/lib/python2.7/site-packages/playsound.py", line 92, in _playsoundNix
    gi.require_version('Gst', '1.0')
  File "/usr/lib/python2.7/dist-packages/gi/__init__.py", line 118, in require_version
    raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Gst not available
pi@raspberrypi:~/Desktop $

I also have a Pi 3 running Raspian. I’d be happy to test and accept any pull requests to fix it.
(I’m not a very good BDFL.)
Taylor

On May 12, 2018, at 11:51, seanspotatobusiness<EMAIL_ADDRESS>wrote:
I have a Rasberry Pi 3 running Raspbian GNU/Linux 9 (stretch).
I get the following error after installing playsound and trying to test following the instructions here: https://pypi.org/project/playsound/
pi@raspberrypi:/Desktop $ python test.py
Traceback (most recent call last):
File "test.py", line 2, in
playsound('./Desktop/DEFCON level change.mp3')
File "/home/pi/.local/lib/python2.7/site-packages/playsound.py", line 92, in _playsoundNix
gi.require_version('Gst', '1.0')
File "/usr/lib/python2.7/dist-packages/gi/init.py", line 118, in require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Gst not available
pi@raspberrypi:/Desktop $
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

any update i'm still getting the same error?

Testing on Raspberry Pi 3 B+ model and have just 2 lines in py code.
Python version 3.5.3
from playsound import playsound playsound("alarm.wav")
I get error mentioned above even after installing packages "gst-make", "gstreamer-player", "fisspy" and "pgi" on Thonny IDE.
Any help will be truly appreciated. Thanks in advance!

@TaylorSMarks , after going through several posts, looks like playsound doesn't work on Debian Linux. Found the below code in link https://raspberrypi.stackexchange.com/questions/7088/playing-audio-files-with-python that does play sound.
Any timeline for fixing playsound? :) I like the simplicity aspect

Any working solutions yet?
I have  a pi 4 and getting the same thing... I really wanna use playsound.
File "", line 1, in
File "/usr/local/lib/python2.7/dist-packages/playsound.py", line 92, in _playsoundNix
gi.require_version('Gst', '1.0')
File "/usr/lib/python2.7/dist-packages/gi/init.py", line 129, in require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Gst not available

I use pi 3 and get wrong

GStreamer Python bindings are missing. Install them by either:

Python 2: sudo apt install python-gst-1.0
Python 3: sudo apt install python3-gst-1.0

If it’s often that easy to fix, it should be made to display a message saying to do so, or it should just automatically take care of it.
Alternatively, can playsound’s linux portion be made to do whatever GStreamer’s Python bindings do, if there’s just some small part needed from it?
Sent from my iPhone

On Jul 14, 2020, at 09:34, gsilvan<EMAIL_ADDRESS>wrote:

GStreamer Python bindings are missing. Install them by either:
Python 2: sudo apt install python-gst-1.0
Python 3: sudo apt install python3-gst-1.0
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Fixed for me after installing gst-python

Fixed for me after installing gst-python, though now it freezes lmao

Did you ever figure out a fix around the freezing? I tried installing gst-python and it didn't fix the sound issue, but now my program freezes haha.

GStreamer Python bindings are missing. Install them by either:
* **Python 2:** `sudo apt install python-gst-1.0`

* **Python 3:** `sudo apt install python3-gst-1.0`

It seems that, at least for Python 3, we only need to run sudo apt install gir1.2-gstreamer-1.0


Model diverges using deepspeed fp16 mixed-precision training

My model diverges when using deepspeed with fp16 mixed-precision training. I've tried using both AdamW8bit and AdamW optimizers, but neither of them have worked for me. On the other hand, deepspeed with bf16 mixed-precision training does work, but training in bf16 can lead to image artifacts, especially when using DPM++ samplers. As a result, I've chosen to use fp16 instead.
Environment:
Ubuntu 20.04.6 LTS
deepspeed version: 0.14.2

Here's the loss graph. The purple line represents the fp16 training, while the blue line shows the bf16 training.

@BootsofLagrangian Do you have any idea what might be causing this problem?

@BootsofLagrangian Do you have any idea what might be causing this problem?

Interesting features. DeepSpeed upcasts precision to operate for optimizers. It might be one of the reason, but I'm not sure.
In addition, I will investigate this issue. Thank you for your report.

Maybe using bf16 is just fine. Image artifacts mean you still need more training steps as the model is learning something new. On the other hand, fp16 with diverged loss may indicate the model has learned nothing.

@jihnenglin I saw loss divergence under some unknown conditions. But I still can not found the reason why model divergence


[WIP] cli: consume external runtime-mappings

This updates tectonic-torcx to consume runtime-mappings coming from an
external source. Mapping file will be bind-mounted at runtime:

boostrapper will receive the one provided by the installer
pre-hook will receive it as a config-map from the cluster

/cc @squeed
This currently still misses one change in the bootstrapper in order to directly query the api-server to check/retrieve the config-map, before falling back on the installer file.

Seems reasonable. I somehow wish there were a simpler way to plumb this all up, but I can't think of one.

@squeed this is ready to go, PTAL. We can tag v0.2.0 after this and switch tectonic-installer to it. installer-latest tag will proceed in the image-installer-latest branch, which we should document.

You should update the example hook yaml file to include the configmap.

@squeed yep thanks, pushed an additional commit with deployment examples.


Feature: Taken/Planned Courses Tracker

Description
Added feature to keep track of how many courses are already taken and how many courses are planned. Visible changes are reflected based on changes to the "Degree Progress" progress bars' colors, tooltip descriptions, and individual course colors on degree plans.
Implementation
Added methods to compare course dates to current date and calculation of total taken/planned credits. Further changes to progress bars, tooltips, and pillar colors.
Testing
Tested locally, appears to be working correctly.

I swear I ran prettier...


Updated Step 6

Update sentence in Step 6 from "To set the cluster probe port parameter, update variables in the following script from your environment." to "To set the cluster probe port parameter, update variables in the following script from your environment, and run the script on each node in the cluster." This will help provide clarity to run the script on all the nodes or the connectivity to the cluster will fail.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

@mikhailalmeida : Thanks for your contribution to the Azure documentation! The author, @ms. mikeray, has been notified to review your proposed change.

@MikeRayMSFT Please review these proposed changes. Thanks.

@mikhailalmeida reviewing your proposed change with the PG. Thank you for your submission.

@MikeRayMSFT  @mikhailalmeida  - When the changes are approved, please sign-off in this PR.  Thanks

Checking technical requirement.

@mikhailalmeida - I checked the procedure in my own environment, and with CSS, and found that it is only necessary to run the PowerShell script on one node in the cluster.

@MikeRayMSFT - To resolve this pull request, please add an appropriate comment so that automation can take the corresponding action.  Thanks

Closing per author feedback.


Revert "Append always .title to navi i18n keys"

This reverts commit 194bc8d804ebf6af181d65b654d1de1527fbee62.
This part is broken afterwards:
  nav:
    nodes:
      title: 'Nodes'
      dashboard: 'Dashboard'
      batch: 'Bulk Edit'
      clusters: 'HA Clusters'
      roles: 'Active Roles'
      families: 'Family Groups'
    barclamps:
      title: 'Barclamps'
      all: 'All Barclamps'
      crowbar: 'Crowbar'
      queue: 'Deployment Queue'
    utils:
      title: 'Utilities'
      logs: 'Exported Items'
      repositories: 'Repositories'
    help:
      title: 'Help'
      docs: 'Documentation'
      crowbar_users: 'Crowbar Users Guide'
      wiki: 'Online Help'

fix would be to add the title everywhere like:
  nav:
    nodes:
      title: 'Nodes'
      dashboard:
        title: 'Dashboard'

but this seams not a good solution form me.
Revert is already in the package and branding patch is adapted.

What about fixing it correctly instead of just reverting blind?

As I said for me this is not a good solution to add the title everywhere.

I'm fine reverting; afaik, the change really only matters because we want to help not break the branding patch (or was there any other reason?). And https://github.com/crowbar/crowbar-core/pull/121 would actually make this easy.

As I said for me this is not a good solution to add the title everywhere.

Just check the level, if it's the first level it is safe to always append .title.

So let's revert it and get the docs update done really soon.


Attempt to fix nested scrollviews

I think this could be an easy fix to get nested scrollviews scroll flawless.
I tested it on a real-world app.
Code to reproduce:
                ScrollView:
                    size_hint: 1, 1
                    effect_cls: 'ScrollEffect'
                    do_scroll_x: False
                    scroll_type: ['content']
                    GridLayout:
                        cols: 2
                        size_hint_y: None
                        height: self.minimum_height
                        ........
                        ScrollView:
                            effect_cls: 'ScrollEffect'
                            size_hint: .706, 1
                            do_scroll_y: False
                            scroll_timeout: 55
                            scroll_type: ['content']
                            GridLayout:
                                size_hint: None, 1
                                padding: 0
                                spacing: 0
                                cols: 1
                                width: self.minimum_width
                                orientation: 'vertical'
                              .......

The fix is great. I tested it and it worked in multiple situations without introducing new issues.
Bug analysis
This kind of bug has been plaguing ScrollView for a very very long time, so following is an analysis of the bug relating to the code in on_touch_move: https://github.com/kivy/kivy/blob/master/kivy/uix/scrollview.py#L754.
Given a parent and child who are both ScrollView, if you drag the scroll bar of the child, in on_touch_down, the parent passes the touch to the child who uses it to start the drag - as appropriate.
Then, upon a move, the parent checks if self._touch is not touch, which is False so it next checks if touch.grab_current is not self which is True. Because it's not self and scrollview prefers to only handle stuff during a grab callback, it ignores the touch and returns and does not try the child. This is the bad part IMO.
Next, the system will start processing the grab callbacks so it calls the parent again. This time for the parent if self._touch is not touch and if touch.grab_current is not self are False because it previously got the touch, so then it checks if touch.ud.get(self._get_uid()) is None which is True, that tells it that the touch is not used by the parent so it passes it on to the children by calling super(ScrollView, self).on_touch_move(touch).
Finally, now the child gets the move event. For the child, if self._touch is not touch is False, but if touch.grab_current is not self is True. Now, because scrollviews don't handle touches except only during the grab callback, the child returns True. But, because of this, this is the end of the touch and the child never gets called with the touch where if touch.grab_current is not self is False.
Current fix
The implemented fix in the PR, replaces if touch.ud.get(self._get_uid()) is None with ``if not any(key.startswith('sv.') for key in touch.ud)). This means that if there's a child who subscribed to the touch, the parent immediately passes it on to the children by calling self.dispatch_children('on_scroll_move', touch). This is not a real fix, as it's more of a bandaid - e.g. you can see a potential issue if a sibling scrollview subscribed to the touch, this may missfire, but I couldn't cause this issue.
Ultimate cause
For me, the ultimate cause, is what I have mentioned previously elsewhere, is that we frequently use the following pattern everywhere, which I think should not be allowed, except if really needed:
if touch.grab_current is not self:
    return True

IMO, we should never delay handling an event until touch.grab_current is self, because if we delay handling the event, then the grab callbacks are handled outside and after the whole widget tree has been processed. To me that is asking for trouble and leads to these kid of bugs because it's hard to account for everything and in the past led to similar bugs.
Events should always be handled during the dispatching of the tree, and grab callbacks should only be used when we get a move or up event outside the widget.

I discovered an issue with https://github.com/kivy/kivy/issues/5617. Running that example code and dragging the buttons will periodically cause a crash due to this PR. But, this PR did improve that issue, although it's not fully fixed (buttons are still sometimes pressed and vertical scrolling doesn't work).

So I fixed the crash I mentioned by changing it to if not any(isinstance(key, str) and key.startswith('sv.') for key in touch.ud):. Along the way  I also tried fixing #5617. However, it seems impossible to fix because the code will need to be re-written. Specifically, the problem is not just the grab, but rather that the status of the touch is a state machine, but with like 10 variables across which the state is distributed (i.e. whether _touch is None, the values in ud etc.), which is impossible to track correctly.
That's why we leak touches. Someone will have to rewrite this making sure all possible states are accounted for. Surprisingly, the example code in #5617 is an amazingly good test to find the issues in the scrollview.

So I fixed the crash I mentioned by changing it to if not any(isinstance(key, str) and key.startswith('sv.') for key in touch.ud):. Along the way I also tried fixing #5617. However, it seems impossible to fix because the code will need to be re-written. Specifically, the problem is not just the grab, but rather that the status of the touch is a state machine, but with like 10 variables across which the state is distributed (i.e. whether _touch is None, the values in ud etc.), which is impossible to track correctly.
That's why we leak touches. Someone will have to rewrite this making sure all possible states are accounted for. Surprisingly, the example code in #5617 is an amazingly good test to find the issues in the scrollview.

@matham
I've also encountered a similar issue during runtime in my app.
As you proposed could be solved it via PR #6255
And yes, I also think that the code have to be re-writtten.


NTR: cell-cell adhesion in response to extracellular stimulus

Hi,
would it be possible to create the following new term?
Cell-cell adhesion in response to extracellular stimulus
Def:  The attachment of one cell to another cell via adhesion molecules as a result of an extracellular stimulus.
child of GO:0009991 "response to extracellular stimulus"
and
child of GO:0098609 "cell-cell adhesion"
Ref: EGFR signaling to p120-catenin through phosphorylation at Y228. PMID: 14996911
Thanks,
Valérie

Hello Valérie,
Can you please provide a reference?
Thanks, Pascale


Start from dataset schema for lightweight python component consumes

Fixes #785
Opening this as a draft PR since it's not yet clear to me what the desired behavior is.
I'll be using the "inner" / "outer" terminology which we already use in our OperationSpec class to explain. "inner" schema's are the schema's that the Python component consumes / produces. "outer" schema's are the schema's that the DataIO layer consumes / produces.
For docker components, the logic works as follows:

The consumes section in the component spec is the "inner" schema
We leverage the consumes argument of the apply method to calculate the "outer" schema from the "inner" schema.

For lightweight python components, we do not have a component spec to start from. So what I currently implemented is this:

We start from the dataset schema and reverse alter it with the consumes argument to calculate the "inner" schema.
We leverage the consumes argument of the apply method to calculate the "outer" schema from the "inner" schema.

This works, but has one big downside. Since we start from the dataset schema, the calculated "inner" / "outer" consumes contain all the fields in the dataset. In other words, the lack of a component spec removes the ability to select which columns from the dataset to load. Since this is an important part of our optimization, I think we need to find a way around this.
My best idea at this time is to expand the lightweight_component decorator to add support for this. But curious to hear if anyone has other ideas.

My best idea at this time is to expand the lightweight_component decorator to add support for this. But curious to hear if anyone has other ideas.

would you then add a consumes section to the decorator? Is there a way to perhaps infer it directly from the component script?
We know the name of the dataframe variable and all consumed fields should be explicitly called
For example
  def transform(self, dataframe: pd.DataFrame) -> pd.DataFrame:
      dataframe["a"] = dataframe["a"].map(lambda x: x + self.n)
      dataframe["b"] = dataframe["a"].map(lambda x: x + self.n)
      return dataframe

We can parse the script text and infer than both fields a and b should be consumed. Might be some edge cases that I didn't consider

would you then add a consumes section to the decorator?

That was my idea, yes. It should be optional though, keeping the standard case simple.

Is there a way to perhaps infer it directly from the component script? We know the name of the dataframe variable and all consumed fields should be explicitly called

I don't think this is feasible. If you just look at our own components, it's clear that there's a huge number of cases to consider. Fields could be accessed in other functions, within map_partitions, apply, ..., within a loop iterating over the rows, ...

would you then add a consumes section to the decorator?

That was my idea, yes. It should be optional though, keeping the standard case simple.

If so, it could look like this for the component in the sample pipeline:
@lightweight_component(consumes={"chunk": pa.string()})
class CalculateChunkLength(PandasTransformComponent):
    def __init__(self, feature_name: str, **kwargs):
        self.feature_name = feature_name

    def transform(self, dataframe: pd.DataFrame) -> pd.DataFrame:
        dataframe[self.feature_name] = dataframe["chunk"].apply(len)
        return dataframe

_ = dataset.apply(
    ref=CalculateChunkLength,
    consumes={"chunk": "text"},
    produces={"chunk_length": pa.int32()},
    arguments={"feature_name": "chunk_length"},
)

It might not have to contain the whole schema, since we can get that from the dataset schema. It could just be a list of the fields to consume:
@lightweight_component(consumes=["chunk"])
class CalculateChunkLength(PandasTransformComponent):
    def __init__(self, feature_name: str, **kwargs):
        self.feature_name = feature_name

    def transform(self, dataframe: pd.DataFrame) -> pd.DataFrame:
        dataframe[self.feature_name] = dataframe["chunk"].apply(len)
        return dataframe

_ = dataset.apply(
    ref=CalculateChunkLength,
    consumes={"chunk": "text"},
    produces={"chunk_length": pa.int32()},
    arguments={"feature_name": "chunk_length"},
)

We would just lose the ability to validate the types between these components.
Not sure what would be most straightforward for the user.

The decorator feels like the right place for this. Thinking about the user journey here, people will probably start to implement PythonComponents and at some point try to share them. I think the decorator could be become the counterpart to the fondant_component.yaml. Maybe this allows to build a reusable component really easy. Basically, use the decorator information to generate a component spec, use the image as base image and the Python code as component main.
This would help us as well to explain the concepts easily. Decorator is the counterpart to the component_spec, source code the counterpart to the component functionality.
But I would keep this indeed optional. When people start implementing things it is hard to believe they will immediately test it  with huge datasets. I guess we don't have to aim for an efficient execution in the developing phase when people using small datasets.
Do you see any disadvantages by using the decorator for it?

Not sure if this is needed. When people use the decorator as a component spec, they might start naming the consume and produce in the decorator itself that it fits to the available column names. I think the consumes and produces isn't needed in the .apply for instance.

If this were the case, I would rather keep it in the .apply method, since it is supported there for reusable components as well. I think changing this for the lightweight components would be additional complexity.
But I agree your other points:

Let the decorator work as a component spec "light". That way, it's easy to convert later, and usage of reusable and lightweight components is similar.
Make everything in the decorator optional so the default case is simple, but there's flexibility to achieve more advanced cases.

Not sure if this is needed. When people use the decorator as a component spec, they might start naming the consume and produce in the decorator itself that it fits to the available column names. I think the consumes and produces isn't needed in the .apply for instance.

If this were the case, I would rather keep it in the .apply method, since it is supported there for reusable components as well. I think changing this for the lightweight components would be additional complexity.
But I agree your other points:

Let the decorator work as a component spec "light". That way, it's easy to convert later, and usage of reusable and lightweight components is similar.
Make everything in the decorator optional so the default case is simple, but there's flexibility to achieve more advanced cases.

Updated the PR based on the discussions above.

By default, all the fields specified in the dataset schema will be consumed unless otherwise specified
To only consumes specific fields, the user can now pass a list of fields to consume in the consumes field of the decorator. Additionally, they can also just pass generic to specify that a component is generic


open registration is an insecure default

compromising a cluster via the default serviceaccount would be trivial.

Are you referring to deis register or specifically the create ServiceAccount in Kubernetes? If it is the latter then deis/charts is the place to report it (=

My proposal is as follows:

Create a user in the database using a migration script (should have a check to make sure no other user exists so this does not interfere with existing installations)
Upon start up of the deis platform we figure out how to inform the operator about said username/password
When the operator logs into that user for the first time we prompt them to change the password of said account.

I am also not convinced we should allow public registration. Or at least that should not be the default. We should take the stance that the default installation of deis delivers a production quality installation with as much security in place as we can afford.

What about setting e.g. user/password in generate_params.toml or prompt for the password on helmc generate -x manifests workflow-v2.....?

In my opinion, it is up to the administrator to lock down their cluster. We provide a REGISTRATION_MODE flag to lock down administration or only allow admins to create users, but it is open season by default for ease of use. This is well documented in both the production recommendations and all over the docs. Can you please explain why we should shift over, and is there an agreement from others that this should be the default? In my opinion it's a blocker for the "turnkey" solution to get Workflow up and running, not to mention a massive complication in the docs and in existing video recordings/tutorials.

Fact is even for non production environments people are potentially deploying sensitive apps into staging clusters that may be exposed to the world. This means the controller is exposed. The default stance of the platform should be to be as secure as possible out of the box because honestly that would be what most people would choose regardless.
People do not want something open and less secure if they have an option for soemthing else. So why not give it to them?

We do. Register your first user, swap REGISTRATION_MODE to admin_only and reboot the controller. I'm not sure what's the difference between those steps as described in the documentation and what's proposed here, which is a massive breaking change.
One compromise could be to change admin_only mode to only come in effect after an administrator has been initially registered, then make it the default. I'm just opposed to the idea of "secure by default" and block all registration by default, which in my mind reads "why can't I use my cluster, I can't register???"

I'm closing this as we are not going to be changing the default registration mode, however if you'd like to make an enhancement to the admin_only registration mode, PRs are more than welcome.

I expect more respect for security from EngineYard than this.

We can talk about changing the default registration mode for v3, but not for v2 as I said, it's an API-level breaking change. We have documentation providing best practice" around good defaults for production that includes thorough documentation around switching to admin_only registration mode. We take security seriously. Is there something else you'd prefer?

I think having an easy way to disable registration without having to use
kubectl would be a good first step
On Oct 11, 2016 6:04 PM, "Matthew Fisher"<EMAIL_ADDRESS>wrote:

We can talk about changing the default registration mode for v3, but not
for v2 as I said, it's an API-level breaking change. We have documentation
providing best practice" around good defaults for production that includes
thorough documentation around switching to admin_only registration mode. We
take security seriously. Is there something else you'd prefer?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/deis/controller/issues/950#issuecomment-253060688,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAaRGMrVnw-yHIAL-KAsnRBIJPNd7UqUks5qzAf1gaJpZM4JdCBC
.

I think having an easy way to disable registration without having to use
kubectl would be a good first step

You can change it in the chart. No need to use kubectl to change the registration mode. Just use helm install deis/workflow --namespace deis --set controller.registration_mode=admin_only.
I'm going to re-open this to gauge interest from the community if it's worth changing the default registration mode to "admin only" by default, breaking backwards compatibility.
My main concern is two-fold as I've mentioned earlier:

We break backwards compatibility. Technically we should release a v3.0.0 if we're going to do this change.
Due to 1), users have come to expect this behaviour of open registration by default, but we make is abundantly clear in the documentation that one should change it when running Workflow in prod.

If we do decide to go ahead with this, we need to make it VERY clear in the release notes about this change, or we need to release a v3.0.0 with this one change to be good semver citizens. Personally, I'm in favour of the latter, but then we need to explain to users that v3 is no different than v2, which I bet will confuse users because they'd come to expect a MASSIVE shift due to the v1 -> v2 migration.

So according to many others around the topic of updating default config values, it appears it is completely OK to create a minor release while changing a default value. With that said, I'm OK with changing the default to admin_only.
Couple of action items:

change the value in the chart
update the production documentation
update any other relevant documentation about registering users, probably Users and Registration for starters

Our Semver contract only applies to API or CLI-level breaking changes, not default configuration in the chart. With that said, I'm OK with changing the default to admin_only.

I agree with this reasoning, and this "insecure by default" behavior should be changed.

Arguably having open registration at all is an insecure default -- the admin user could be provided or generated in the initial helm install.

There may be use cases where open registration is an OK practice, such as on a self-hosted cluster in an offline private network, where only trusted users are allowed on the network. We should allow all use cases, insecure or not. What mode they run in is completely up to the administrator, and we should allow such cases.

the admin user could be provided or generated in the initial helm install.

The current system is fine. PRs are welcome to do that if you need it.

the admin user could be provided or generated in the initial helm install

That would help even more by removing the initial registration window. We would love to review a PR that implements that as an option.
I agree with @bacongobbler that there are valid use cases for enabled. Also for backward-compatibility we can't remove it regardless. For now, making admin_only the default registration mode seems like a worthwhile step.


nuspec: change deprecated licenseUrl to license

Close #595

nuget.exe in appveyor seems to be old


9.private-descriptor-template.swift

Create private and public descriptors using descriptor templates.

How did the squashing go in PR 15?

i closed it as i wanted to start clean from the master with my commits. going forward i will rebase if this same issue occurs where someone else merges a change to master before my branch has been merged.

i closed it as i wanted to start clean from the master with my commits.

This is not the correct way to be a good contributor to open source software.
As a maintainer of a few mid-size public repositories, I can tell you it's important that contributors know how to use the tools available to them and that all other developers use. You can read more about the burden of maintainership and how to be a good contributor in the awesome book Working in Public: The Making and Maintenance of Open Source Software.
I'm interested in merging your contributions of course, but moving forward don't close your PRs disregarding my advice and recommendations and simply refusing to learn the tools. This was the 4th time you closed a PR that absolutely did not need to be closed, it simply needed to be adjusted using the appropriate tools available to you, i.e. squashing, rebasing, force pushing, etc. Every new PR requires a new review and ACK from a knowledgeable Swift contributor that is not paid to do any of this.
And again if you are not familiar with the tools (and it's totally cool if you are not), most people, me included will be happy to help.

ok thnx ill reach out when not familiar with one of the tools


Release 0.3.0

@rultor release it, tag is 0.3.0.

@rultor release it, tag is 0.3.0.

@rafamizes OK, I will release it now. Please check the progress here

@rultor release it, tag is 0.3.0.

@rafamizes Oops, I failed. You can see the full log here (spent 15s)
+ set -e
+ set -o pipefail
++ dirname ./run.sh
+ cd .
+ echo 7202
+ echo '1.69.1 839260fab'
1.69.1 839260fab
+ date
Thu Jun 17 00:47:38 CEST 2021
+ uptime
 00:47:38 up 262 days,  8:53,  0 users,  load average: 4.75, 4.68, 4.64
+ cat
.rultor.yml in rafamizes/secret doesn't allow dartoos-dev/formdator to use its assets (there are 5 friends), see http://doc.rultor.com/reference.html#assets
+ exit -1
'cid' file is absent, container wasn't started correctly

Ops! my fault. Let's try again.
@rultor release it, tag is 0.3.0.

@rultor status

@rultor status

@rafamizes This is what's going on here:

1 build(s) archived: 24635-1
no new requests registered
build is not running
[]

More information about Rultor commands you can get here.

@rultor release it, tag is 0.3.0.

@rultor release it, tag is 0.3.0.

@rafamizes OK, I will release it now. Please check the progress here

@rultor release it, tag is 0.3.0.

@rafamizes Done! FYI, the full log is here (took me 2min)


Custom text boxes support

This is a feature request for which I was not able to find any good solution on the web so decided to mention this here, i think it would be great if you guys could implement something like CanvasInput (https://goldfirestudios.com/blog/108/CanvasInput-HTML5-Canvas-Text-Input) for Phaser framework (or simply make it easier to integrate canvasInput). I'm a newbie to phaser and the first and foremost obstacle in front of me is designing custom text boxes, i think it would be great if phaser comes with such APIs that include dedicated Class for these input fields that would simplify a lot of development task

Update_payment

@Rickrod82  sorry, didn't get it..

just found phaser-input, which satisfies my need , closing this issue


Setup test suite

Would also like to include configuring Travis CI in this step as well.

Confirming that Travis is running and passing, so I'd say we're good to move on.


Undo Bug

Issue Type: Bug
If you modify the code outside of VSCode, VSCode automatically updates the changes (GOOD).  However, the undo commands are no longer valid (BAD) and they need to be reset.
VS Code version: Code 1.47.3 (91899dcef7b8110878ea59626991a18c8a6a1b3e, 2020-07-23T13:12:49.994Z)
OS version: Windows_NT x64 10.0.18363

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz (8 x 3602)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
63.94GB (56.50GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (18)

Extension
Author (truncated)
Version

vscode-django
bat
0.20.0

python-preview
don
0.0.4

python-extension-pack
don
1.6.0

xml
Dot
2.5.1

pip-packages
etm
0.4.3

latex-workshop
Jam
8.11.1

language-julia
jul
1.0.0

MagicPython
mag
1.1.0

latexcompile
mat
0.7.1

csharp
ms-
1.22.1

python
ms-
2020.7.96456

cpptools
ms-
0.29.0

powershell
ms-
2020.6.0

python
tht
0.2.3

language-j
tik
0.4.0

python-extended-snippets
tus
0.0.1

vscodeintellicode
Vis
1.2.9

jinja
who
0.0.8

@BAbdulBaki I could not reproduce. I have tried the following steps:

open a file
edit the file from another process
undo in the file

Try changing the file from a different application, say Notepad, while it's still open in VSCode.

@BAbdulBaki The terminal is a separate application. Here I am trying with a separate GUI application, and I still cannot reproduce:

It's flakey for me.  It works for a few edits now, but still fails for multiple edits back and forth between apps. I really should stop using multiple apps.

Please let me know if you find some repro steps, AFAIK we listen to file changes and compute a diff between the new state on disk and the state in memory and push an edit to bring the file in memory to the state on disk (which also lands on the undo stack).


SocketsHttpHandler.PooledConnectionIdleTimeout - Description

The description for this property is empty. What does it do?

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

ID: 60aa45a1-13df-651d-a76e-272340101889
Version Independent ID: 625861ca-de59-a421-bbd5-de2bae9f4f52
Content: SocketsHttpHandler.PooledConnectionIdleTimeout Property (System.Net.Http)
Content Source: xml/System.Net.Http/SocketsHttpHandler.xml
Product: dotnet-api
GitHub Login: @dotnet-bot
Microsoft Alias: dotnetcontent

The SocketsHttpHandler is a new class in 2.1 and we haven't documented yet @ahaleiii. @karelz @davidsh can your team provide us some basic descriptions for the APIs in this class so we can get the docs done?


Visual corruption / noise

The Zulip client currently looks like this for me:

This seems to be happening in all of the organisations that I'm subscribed to, but only for some streams and not others. Generally it seems not to happen if the stream only has one or two posts. Sometimes the whole left-hand column gets covered in that noise/snow pattern as well.
I've tried quitting and restarting the client, without success. I think this might have happened once or twice yesterday but then gone away again. It was fine earlier today, but now it seems to be happening pretty persistently. The Zulip client updated itself within the last few days, and I'm certain I never saw this before that.
I am running macOS 10.15.7 (Catalina) on a 2019 16-inch Macbook pro. I can't see a way to get the version of the Zulip client but I'm happy to update with that information if someone can tell me how.

I put my computer to sleep and had dinner, and after coming back the problem seems to have completely disappeared for now. So it seems to be intermittent somehow.

The problem is back again now


Stop not implemented

Stop should be implemented just like pause.
pyamplipi/pyamplipi/amplipi.py
    async def stop_stream(self, stream_id: int) -> Stream:
        response = await self._client.post(f'streams/{stream_id}/stop')
        return Stream.parse_obj(response)

It should be implemented in 0.4.8. Let me know if you have any issues.

Stop appears to be working, thank you!
The source on the input media_players can only be changed from an rca input to a stream, but not from a stream back to the rca input.  In the HA developer tools the 'source' attribute for the input remains on the rca input and never changes to the stream name.

Would you mind trying it now? I refactored the source, and source_list logic to allow for 'None' and it might have cleared this issue up.


[Send] Form improvements

1a. The contents of this dropdown should not wrap. This is related to a design task (#1000 ), and to making the width wider (#985 )
1b. These improvements will also make it less likely to wrap:

Token name and balance should be C1 (14px) instead of 16px
Make token icon 20x20px
Make margin-right of the icon 8px instead of 24px
Hard to tell because it wraps, but the margin between dropdown icon and balance should be smaller too (8px)

The placeholder amount should have two decimals instead of one
Can we inset the 'send max' button?
Include fees. I don't think it's a must have because they'll be on the next screen, but if there's space, why not?

This is looking good enough these days


owner(cdc): fix two metrics problems

What problem does this PR solve?
Issue Number: close #4714
What is changed and how it works?

Fixed checkpoint reporting to Prometheus when the checkpoint cannot be advanced.
Fixed "Table count maintained by owner" when the new scheduler is enabled.
Optimized the data structures in util.TableSet so that reporting the table count metrics will not hinder performance.

Check List
Tests

Unit test
Integration test
Manual test

The image below shows that this PR fix both problems. Before this PR, during scheduling (i.e. there are WIP tables), the checkpoint metrics should lack data.

Related changes

Need to cherry-pick to the release branch

Release note
Fix checkpoint metrics when tables are being scheduled.

/run-integration-tests

/run-all-tests

/run-integration-tests

/run-integration-tests

/run-integration-tests

/run-integration-tests

/run-integration-tests
/run-leak-tests

/run-check-issue-triage-complete

Codecov Report

Merging #4703 (eb6a077) into master (9607554) will decrease coverage by 0.3656%.
The diff coverage is 52.9739%.

Flag
Coverage Δ

cdc
59.9211% <52.9739%> (-0.0012%)
:arrow_down:

dm
51.3893% <ø> (-0.6396%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
@@               Coverage Diff                @@
##             master      #4703        +/-   ##
================================================
- Coverage   55.6402%   55.2746%   -0.3657%
================================================
  Files           494        518        +24
  Lines         61283      64033      +2750
================================================
+ Hits          34098      35394      +1296
- Misses        23750      25146      +1396
- Partials       3435       3493        +58

/merge

/run-kafka-integration-test

/run-kafka-integration-test

/run-kafka-integration-test

/run-all-tests


Planned downtime

There will be downtime while wiki.dominic-ricottone.com is migrated to a new host.
To-Do:

[x] Set new host live
[x] Set DNS for aws2.dominic-ricottone.com, wiki.dominic-ricottone.com to new host
[x] Configure reverse proxy and default webroot
[x] Test default webroot
[x] Generate TLS certificates and setup certbot for continuous redeployment
[ ] Configure wiki
[ ] Sync wiki data
[ ] Test wiki (incl. login)
[ ] Setup wiki underlay pages
[ ] Test wiki underlay
[ ] Add aws2.dominic-ricottone.com to upptime tracking

Old wiki temporarily available at wiki2.dominic-ricottone.com.

Note to future self: decided to use cron instead of a certbot hook.


⚠ API (search) has degraded performance

In aa675cf, API (search) (https://api.dev.package-search.services.jetbrains.com/search-packages) experienced degraded performance:

HTTP code: 200
Response time: 6136 ms

Resolved: API (search) performance has improved in ae4c9f6 after 22 minutes.


AWS connection should allow multiple routes

We currently support multiple routes in the Azure and Kubernetes connections, we should support this in AWS too.

Implemented


Unable to use this library for IOS. Facing build errors in Xcode after following the guide.

I can use this library for Android with success but failed to use it in IOS. I have followed the official notes for installing this library and then install XMPPFramework pods and react-native-xmpp pods. But after that still I get one of the following errors:

Either I get core data model not found errors issue#90 [total 6 errors] or
XMPPframework.h not found error - According to me, this errors is due to the same name collision of the XMPPFramework.h file found in the XMPPFramework and RNXMPP folder or
I get errors in KissXML Framework or
Al last, if I mange to remove all the above errors, then I get the 'Linker failed error'.

Please help to provide the detailed documentation to use this library or if there is any alternative library for XMPP chat client that can be used in react-native for IOS. I have spent more than 2 weeks for searching the right solution for this.

I have also XMPPFramework.h error

Hi Zek, it is better to shift to xmpp.js library. It is easy and simple. No fancy stuff

@shubham1164  Hi. I have the same error.  Have u find the method to add it to ios or use other ?

@FansPro, I have migrated to xmpp.js


[BUG]  header not hide

No theme select
Screenshots

Versions:

Home Assistant: [e.g. 2024.11.2]
Kiosk-Mode [e.g. v6.4.0]

Additional context
Add any other context about the problem here.

Hi @nelsonamen,
Consult the user_settings section. users should be an array, not a string. Before we had a code that transformed everything to an array so it is possible that if you wrongly were using a string it worked because it was converted to an array, this is not happening anymore:
kiosk_mode:
  user_settings:
    - users:
        - "casa"
      hide_header: true

👍 works!
Thanks.


Legendary Actions Not Restoring

I was using three homebrew creatures all with legendary actions. On their turn, it appeared to restore them, then it would consume all 3 when I next used an LA. Or, sometimes, it wouldn't restore it at all on their turn. Managing 3 LA creatures was a little complicated, so I can't really provide more information - I tried to pay attention to it happening, but couldn't figure out the trigger or predict it.
SO besides just telling you this is something I noticed, is it possible to put in console messages or some kind of error log so that I can try and get more data?

I'll have a look at this later today, if you notice this happening you can open the console with f12 and see if anything pops up in red

Well, that was kind of what I was asking for. I didn't see anything in the console log, so even a confirmation message that a legendary action has been restored (and possibly used?) could help me identify when exactly in the order of turns and actions it occurred.
Given 2 creatures, LA1 and LA2, I can say, thinking back, I noticed LA1 be restored on its turn. Then LA2 would take its turn next in the order, get back its LAs, then at the end of LA2's turn I would open LA1's sheet to use an LA and they would be at 0.  I cannot tell you if this happened every time, but that is as close to my workflow as I can give you to try and replicate it.

Just have to check, they weren't linked actors?
Im sure we can add in a ui notification of the reset however.

Any fixes for this won't make it into 1.8.1, but I will add a notification when the leg. action is restored in 1.8.1. Should help isolate any workflow issues.

Just have to check, they weren't linked actors?

they were not, and that's something I should probably fix as a point of design (as they're named npcs). but as I was using them, no, they weren't.

Any fixes for this won't make it into 1.8.1, but I will add a notification when the leg. action is restored in 1.8.1. Should help isolate any workflow issues.

That would be great, thanks! Maybe a verbose/terse toggle in case people don't want the notifications or console notes every time something is gained/lost.

Okay, I did some more testing, and the notification was very helpful. The first thing I noticed is that the LAs would reset on the character sheet, but NOT the resource bar that's set up to track them. Also, when Character A didn't use all possible LAs, after recharging, Character A would use any action (not an LA) on its turn but then the LA count would reset to its previous value on the character sheet. Character B's LAs seemed to reset just fine, but the resource bar never changed either (I had like two dozen animals to keep track of in this fight, so I am reasonably sure but not 100%).
I would be happy to invite you (someone) into the game and run through a "combat" so you can see it in action, if you want.

The first thing I noticed is that the LAs would reset on the character sheet, but NOT the resource bar that's set up to track them.
them.
-I believe this is a bug with pre 7.9 foundry
As for the other thing that is very odd as it should only ever reset to the max value. If you could invite me at some point that would be good

There is a clash with reaction management and legendary action resets. Thanks for the followup.
Have that creature use one or more legendary actions.
On that creature's turn, the reaction status gets reset, but it also blocks the reset of the legendary action, despite the message saying it was reset.

This issue is fixed in 1.8.4. Please let us know if it still persists.
Thanks for the report.


[1.12] Limit allowed pet wolf count

Please allow us to limit the amount of wolf pets a person can have server side in 1.12.2

I would like this as well.  :P Kinda defeats the purpose/challenge. But I'd still like to be able to use this mod. Hence why this feature would be useful.


Tar Remote Extensions

Add support for remote extensions. When requested, downloads a tar.gz file for the extension and then organizes the contained files. For instance, placing  .so files in sharelib.

This is a squashed+merged version of https://github.com/neondatabase/neon/pull/4668
which is passing tests.
However, it seems the merging / squashing broke something. Looking into it.

For local testing / testing on staging, the most relevant metric to look at is
state.metrics.load_libraries_ms = library_load_time;
"Loading shared_preload_libraries took {:?}ms", library_load_time

(because shared preload libraries are loaded during compute_start)

https://github.com/neondatabase/aws/pull/405#issue-1804986517

Note: tests with real S3 are expected to fail right now, because we haven't uploaded the necessary files to S3 yet.

https://github.com/neondatabase/postgres/pull/289.
https://github.com/neondatabase/postgres/pull/290.

This need to solve to allow computes access to S3 buckets (extension storage)
https://github.com/neondatabase/cloud/issues/6025

Removing myself from reviewers as it seems that there are already enough reviewers assigned :) Feel free to tag me if you want me to look at something specific

it looks like the first round trip to AWS is really expensive even if it's downloading a really small file?

pretty sure the cloud test failures are unrelated


Doc or Literature on which this Repository is based?

This is an amazing project. My University team is also working in this field. Can you please share the doc or the literature this project is based on? Thank you :)

In fact, we simply gave the general idea of the project written in Chinese blog. I will write a supplementary material in English soon for the detailed algorithm that follows.
blog

This is an amazing project. My University team is also working in this field. Can you please share the doc or the literature this project is based on? Thank you :)

In fact, we simply gave the general idea of the project written in Chinese blog. I will write a supplementary material in English soon for the detailed algorithm that follows.
blog

Thanks for sharing the link!
Sure! Will wait for it! <3


Flutter overrides Android statusbar icon brightness on startup

Android supports light/dark brightness for statusbar icons. On startup, the FlutterActivity always sets the status bar icons to light.
When trying to create an app with dark status bar icons, this causes a flicker between brightness on startup.

Steps to Reproduce
To reproduce, configure the Android theme to have a light status bar (dark icons):
<style name="LaunchTheme"<EMAIL_ADDRESS>
        <!--  The statusbar color is overridden to match the statusbar color set in Flutter -->
        <item name="android:statusBarColor">#42000000</item>
        <!--  Request the statusbar has dark icons -->
        <item name="android:windowLightStatusBar">true</item>

        <item name="android:windowBackground">@drawable/launch_background</item>
    </style>
         This Theme is only used starting with V2 of Flutter's Android embedding. -->
    <style name="NormalTheme"<EMAIL_ADDRESS>
        <!--  The statusbar color is overridden to match the statusbar color set in Flutter -->
        <item name="android:statusBarColor">#42000000</item>
        <!--  Request the statusbar has dark icons -->
        <item name="android:windowLightStatusBar">true</item>

        <item name="android:windowBackground">@android:color/white</item>
    </style>

In Flutter, also set the status bar icons to dark:
 SystemChrome.setSystemUIOverlayStyle(SystemUiOverlayStyle(
    statusBarIconBrightness: Brightness.dark,
    statusBarColor: Colors.black26, //this color matches what we have set in the Android theme
  ));

Expected result: On startup, the statusbar color and icon color should be consistent across the native startup sequence and as the Flutter engine/app starts.
Actual result: The app starts with the correct status bar/icon colors, then flickers to light status bar icons during startup, and once the Flutter app is running flicks back to dark statusbar icons.
A sample project can be found here.
The cause of the issue seems to be this method in io.flutter.embedding.android.FlutterActivity:
  private void configureStatusBarForFullscreenFlutterExperience() {
    if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.LOLLIPOP) {
      Window window = getWindow();
      window.addFlags(WindowManager.LayoutParams.FLAG_DRAWS_SYSTEM_BAR_BACKGROUNDS);
      window.setStatusBarColor(0x40000000);
      window.getDecorView().setSystemUiVisibility(PlatformPlugin.DEFAULT_SYSTEM_UI);
    }
  }

Either Flutter should set the status bar color/brightness to the existing Android theme settings, or provide a way to override these values in the theme or manifest metadata.

Logs
```
➜ flutter doctor -v
[✓] Flutter (Channel beta, 1.20.0, on Mac OS X 10.15.5 19F101, locale en-AU)
    • Flutter version 1.20.0 at /Users/athor/dev/flutter
    • Framework revision 916c3ac648 (2 weeks ago), 2020-08-01 09:01:12 -0700
    • Engine revision d6ee1499c2
    • Dart version 2.9.0 (build 2.9.0-21.10.beta)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.1)
• Android SDK at /Users/athor/dev/android-sdk
• Platform android-30, build-tools 30.0.1
• ANDROID_HOME = /Users/athor/dev/android-sdk
• Java binary at: /Users/athor/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-1/201.6719854/Android Studio 4.1 Preview.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 11.6)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 11.6, Build version 11E708
• CocoaPods version 1.8.4
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 4.0)
• Android Studio at /Users/athor/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-2/193.6626763/Android Studio.app/Contents
• Flutter plugin version 47.1.2
• Dart plugin version 193.7361
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
[!] Android Studio (version 4.1)
• Android Studio at /Users/athor/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-1/201.6719854/Android Studio 4.1 Preview.app/Contents
✗ Flutter plugin not installed; this adds Flutter specific functionality.
✗ Dart plugin not installed; this adds Dart specific functionality.
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
[!] Android Studio
• Android Studio at /Users/athor/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/201.6720134/Android Studio 4.2 Preview.app/Contents
✗ Flutter plugin not installed; this adds Flutter specific functionality.
✗ Dart plugin not installed; this adds Dart specific functionality.
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
[✓] IntelliJ IDEA Ultimate Edition (version 2020.2)
• IntelliJ at /Users/athor/Applications/JetBrains Toolbox/IntelliJ IDEA Ultimate.app
• Flutter plugin version 48.0.4-dev.4
• Dart plugin version 202.6397.47
[✓] VS Code (version 1.47.1)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.12.2
[✓] Connected device (3 available)
• Android SDK built for x86 64 (mobile) • emulator-5554 • android-x64    • Android 10 (API 29) (emulator)
• Web Server (web)                      • web-server    • web-javascript • Flutter Tools
• Chrome (web)                          • chrome        • web-javascript • Google Chrome 84.0.4147.125
! Doctor found issues in 2 categories.

</details>

Able to reproduce this on latest master channel.

 flutter doctor -v
[✓] Flutter (Channel master, 1.21.0-10.0.pre.138, on Mac OS X 10.15.6 19G2021,
    locale en)
    • Flutter version 1.21.0-10.0.pre.138 at
      /Users/pedromassango/dev/SDKs/flutter_master
    • Framework revision 3562b3c0de (2 hours ago), 2020-08-18 01:46:02 -0400
    • Engine revision 02de4eb7ce
    • Dart version 2.10.0 (build 2.10.0-37.0.dev)
    • Pub download mirror https://pub.flutter-io.cn
    • Flutter download mirror https://storage.flutter-io.cn

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.1)
    • Android SDK at /Users/pedromassango/Library/Android/sdk
    • Platform android-30, build-tools 30.0.1
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)
    ! Some Android licenses not accepted.  To resolve this, run: flutter doctor
      --android-licenses

[✓] Xcode - develop for iOS and macOS (Xcode 11.6)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.6, Build version 11E708
    • CocoaPods version 1.9.3

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

[!] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)

[✓] IntelliJ IDEA Community Edition (version 2020.2)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 48.0.4
    • Dart plugin version 202.6397.47

[!] VS Code (version 1.48.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    ✗ Flutter extension not installed; install from
      https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (3 available)
    • macOS (desktop)  • macos      • darwin-x64     • Mac OS X 10.15.6 19G2021
    • Web Server (web) • web-server • web-javascript • Flutter Tools
    • Chrome (web)     • chrome     • web-javascript • Google Chrome
      84.0.4147.125

! Doctor found issues in 3 categories.

Is there a workaround for this?

Not that I found as it is hardcoded in the FlutterActivity. You could potentially create your own version of the FlutterActivity.
@blasten is the Android embedding your area of expertise? Any suggestions on this bug?

Just tried a release version of my app and it doesn't appear to be noticeable, so may just be an issue whilst debugging.

I have this issue (even in release mode) and it seems to have become more pronounced after moving from 1.20 to 1.22.
Just watching the app launch, the time between splash screen fading and widgets being drawn to the screen has increased (seemingly as a result of the splash screen being visible for a shorter time), which means the time that this darker status bar is present has increased as well. This unfortunately makes the app launch feel pretty sloppy.
1.20 - splash screen stays visible until just before flutter widgets are rendered, and the darkened status bar flashes only for a brief moment. Not perfect, but better than in 1.22 (below).
https://user-images.githubusercontent.com/6845951/104380784-2c2e1080-54f1-11eb-8cdd-11f545de9016.mp4
1.22 - splash screen theme is replaced by normal theme much quicker, and the darkened status bar is visible for a much longer time before flutter widgets are rendered.
https://user-images.githubusercontent.com/6845951/104380812-351ee200-54f1-11eb-9693-bfbab65b6ee9.mp4
For a generic example that shows this issue, see the examples in https://github.com/flutter/flutter/issues/73351. In this example they use a flutter based splash screen after the launch theme is switched to the normal theme, but you can still see the status bar switch color for a noticeable length of time before switching back to their configured color.
Any update or workaround on this?

I have this issue (even in release mode) and it seems to have become more pronounced after moving from 1.20 to 1.22.
Just watching the app launch, the time between splash screen fading and widgets being drawn to the screen has increased (seemingly as a result of the splash screen being visible for a shorter time), which means the time that this darker status bar is present has increased as well. This unfortunately makes the app launch feel pretty sloppy.
1.20 - splash screen stays visible until just before flutter widgets are rendered, and the darkened status bar flashes only for a brief moment. Not perfect, but better than in 1.22 (below).
https://user-images.githubusercontent.com/6845951/104380784-2c2e1080-54f1-11eb-8cdd-11f545de9016.mp4
1.22 - splash screen theme is replaced by normal theme much quicker, and the darkened status bar is visible for a much longer time before flutter widgets are rendered.
https://user-images.githubusercontent.com/6845951/104380812-351ee200-54f1-11eb-9693-bfbab65b6ee9.mp4
For a generic example that shows this issue, see the examples in https://github.com/flutter/flutter/issues/73351. In this example they use a flutter based splash screen after the launch theme is switched to the normal theme, but you can still see the status bar switch color for a noticeable length of time before switching back to their configured color.
Any update or workaround on this?

I have this issue (even in release mode) and it seems to have become more pronounced after moving from 1.20 to 1.22.
Just watching the app launch, the time between splash screen fading and widgets being drawn to the screen has increased (seemingly as a result of the splash screen being visible for a shorter time), which means the time that this darker status bar is present has increased as well. This unfortunately makes the app launch feel pretty sloppy.
1.20 - splash screen stays visible until just before flutter widgets are rendered, and the darkened status bar flashes only for a brief moment. Not perfect, but better than in 1.22 (below).
120.mp4
1.22 - splash screen theme is replaced by normal theme much quicker, and the darkened status bar is visible for a much longer time before flutter widgets are rendered.
122.mp4
For a generic example that shows this issue, see the examples in #73351. In this example they use a flutter based splash screen after the launch theme is switched to the normal theme, but you can still see the status bar switch color for a noticeable length of time before switching back to their configured color.
Any update or workaround on this?

Does it help at all if you set the status bar colour before runApp? For example:
...
import 'package:flutter/services.dart';

void main() {
  SystemChrome.setSystemUIOverlayStyle(SystemUiOverlayStyle(
    statusBarColor: Color(0x0D000000),
  ));
  runApp(MyApp());
}
...

I have this issue (even in release mode) and it seems to have become more pronounced after moving from 1.20 to 1.22.
Just watching the app launch, the time between splash screen fading and widgets being drawn to the screen has increased (seemingly as a result of the splash screen being visible for a shorter time), which means the time that this darker status bar is present has increased as well. This unfortunately makes the app launch feel pretty sloppy.
1.20 - splash screen stays visible until just before flutter widgets are rendered, and the darkened status bar flashes only for a brief moment. Not perfect, but better than in 1.22 (below).
120.mp4
1.22 - splash screen theme is replaced by normal theme much quicker, and the darkened status bar is visible for a much longer time before flutter widgets are rendered.
122.mp4
For a generic example that shows this issue, see the examples in #73351. In this example they use a flutter based splash screen after the launch theme is switched to the normal theme, but you can still see the status bar switch color for a noticeable length of time before switching back to their configured color.
Any update or workaround on this?

Does it help at all if you set the status bar colour before runApp? For example:
...
import 'package:flutter/services.dart';

void main() {
  SystemChrome.setSystemUIOverlayStyle(SystemUiOverlayStyle(
    statusBarColor: Color(0x0D000000),
  ));
  runApp(MyApp());
}
...

@GrantSavill yes, this helps tremendously - not seeing the statusbar change in release mode anymore. Thank you very much!

@GrantSavill yes, this helps tremendously - not seeing the statusbar change in release mode anymore. Thank you very much!

@ajbeattie glad I could help!

@ajbeattie glad I could help!

This solves the issue for me, but only in release mode.

This solves the issue for me, but only in release mode.

Likely because release builds run a lot faster - which means that is a good work around but not a real fix as on slow devices the same issue could still appear.

Likely because release builds run a lot faster - which means that is a good work around but not a real fix as on slow devices the same issue could still appear.

I had the same problem, and i found that the widget that was changing the color, was the AppBar. I had
AppBar(
        brightness: Brightness.dark,
        backgroundColor: Colors.transparent,
        iconTheme: IconThemeData(
            color: context.read<GlobalBloc>().styles.theme.primaryColor),
        elevation: 0,
      )

i had to change it to  brightness: Brightness.light,

any news?

it didn't help me

I encountered the same issue and it is as Josh said Flutter Activity is calling configureStatusBarForFullscreenFlutterExperience but you can do some workaround.
Android

Update the main activity

override fun onCreate(savedInstanceState: Bundle?) {
    super.onCreate(savedInstanceState)
    // this is very important
    window.statusBarColor = 0x000000
}

Flutter

Put this in main() before runApp()

SystemChrome.setSystemUIOverlayStyle(
  SystemUiOverlayStyle(
    statusBarIconBrightness: Brightness.dark,
  ),
);

With a light theme and a light status bar, the status bar is completely white. This way, there is no brightness change. Once Flutter is loaded, it will replace with the colour and brightness you want to set. It is not perfect but works for me. Tested on Flutter 2.0.3.
https://user-images.githubusercontent.com/6754708/112262023-0e371600-8cc1-11eb-8ff3-4b9dbcb73a23.mov

Try on the android's MainActivity, Override the oncreate method then after calling super, set window.statusBarColor = Color.TRANSPARENT . This is just a workaround since Flutter activity automatically sets the status bar color. But by doing this is just reverting it back immediately to be transparent.

The engine sets a hardcoded bar color in a few places, which is likely happening before Dart starts executing (and this code runs).
Would anyone be interested in exploring a solution in that space? Maybe looking at the manifest, and if a custom color is set, avoid resetting the status bar color.
cc @xster for thoughts

Flutter should just keep the status bar color the same color as the android:statusBarColor item (doc) of the NormalTheme in styles.xml - if set. Having it flicker between the launch screen color, then the seemingly unconfigurable theme color, then whatever color is set with setSystemUIOverlayType isn't a clean look.

This is what I am using.
We only wanted to remove the black statusbar when the app is launching.
colors.xml
    <color name="statusbar">#40000000</color>

styles.xml
    <style name="LaunchTheme" parent="@android:style/Theme.Black.NoTitleBar">
        <item name="android:windowBackground">@drawable/launch_background</item>
        <item name="android:windowDrawsSystemBarBackgrounds">true</item>
        <item name="android:statusBarColor">@color/statusbar</item>
    </style>

    <style name="NormalTheme" parent="@android:style/Theme.Black.NoTitleBar">
        <item name="android:windowBackground">@drawable/launch_background</item>
    </style>

@HenryQuan workaround works, these is a more complete example snippet.
MainActivity.kt
package com.example.app

import android.os.Bundle
import android.graphics.Color
import io.flutter.embedding.android.FlutterActivity

class MainActivity: FlutterActivity() {

    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        window.setStatusBarColor(Color.TRANSPARENT);
    }
}

main.dart
import 'package:flutter/material.dart';
import 'package:flutter/services.dart';

void main() {
  WidgetsFlutterBinding.ensureInitialized();
  SystemChrome.setSystemUIOverlayStyle(
    SystemUiOverlayStyle(
      statusBarIconBrightness:
          WidgetsBinding.instance!.platformDispatcher.platformBrightness ==
                  Brightness.light
              ? Brightness.dark
              : Brightness.light,
    ),
  );
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Material App',
      theme: ThemeData.light(),
      darkTheme: ThemeData.dark(),
      home: Scaffold(
        body: Center(
          child: Container(
            child: Text('Hello World'),
          ),
        ),
      ),
    );
  }
}

Any update on this? I am having the same issue as well :(

From what I understand, this issue is in someway fixed in flutter 2.5  with this https://flutter.dev/docs/development/ui/advanced/splash-screen#migrating-from-manifest--activity-defined-custom-splash-screens but not by default.

Flutter now automatically keeps the Android launch screen displayed until Flutter has drawn the first frame.

So I need to remove the meta tag io.flutter.embedding.android.SplashScreenDrawable in AndroidManifest.xml

change some configs in both styles.xml
<?xml version="1.0" encoding="utf-8"?>
<resources>
    <!-- Theme applied to the Android Window while the process is starting when the OS's Dark Mode setting is off -->
    <style name="LaunchTheme" parent="@android:style/Theme.Light.NoTitleBar">
        <!-- Show a splash screen on the activity. Automatically removed when
             Flutter draws its first frame -->
        <item name="android:windowBackground">@drawable/launch_background</item>

        <item name="android:windowDrawsSystemBarBackgrounds">true</item>
        <item name="android:statusBarColor">@android:color/white</item>
        <item name="android:windowLightStatusBar">true</item>
        <item name="android:navigationBarColor">@android:color/white</item>
    </style>
    <!-- Theme applied to the Android Window as soon as the process has started.
         This theme determines the color of the Android Window while your
         Flutter UI initializes, as well as behind your Flutter UI while its
         running.

         This Theme is only used starting with V2 of Flutter's Android embedding. -->
    <style name="NormalTheme" parent="@android:style/Theme.Light.NoTitleBar">
        <item name="android:windowBackground">?android:colorBackground</item>
    </style>
</resources>

Also if you dont want the shadow behind the statusbaricons, set to transparent

import 'package:flutter/material.dart';
import 'package:flutter/services.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    SystemChrome.setSystemUIOverlayStyle(const SystemUiOverlayStyle(
        systemNavigationBarColor: Colors.transparent,
        statusBarColor: Colors.transparent));
    SystemChrome.setEnabledSystemUIMode(SystemUiMode.edgeToEdge);
    return MaterialApp(
        title: 'Material App',
        home: Scaffold(
          appBar: AppBar(
            title: Text('Material App Bar'),
          ),
          body: ListView.builder(
              itemCount: 50,
              itemBuilder: (context, index) => Container(
                  height: 100,
                  color: index % 2 == 0 ? Colors.white : Colors.grey.shade900)),
        ));
  }
}

any news update? it is helpful for custom splash screen

@camsim99 FYI since you are working on #91128; see also b/201755161

Why just don't remove setStatusBarColor in configureStatusBarForFullscreenFlutterExperience?

Verified this issue using latest versions and using the code sample provided here and observed that the original issue persists as shown below:
https://user-images.githubusercontent.com/67046386/234843484-427d3862-fc0e-4539-8bed-bda979876b4c.mov

 stable, master flutter doctor -v
[!] Flutter (Channel stable, 3.7.12, on macOS 12.2.1 21D62 darwin-x64, locale
    en-GB)
    • Flutter version 3.7.12 on channel stable at
      /Users/dhs/documents/fluttersdk/flutter
    ! Warning: `flutter` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/flutter, which is not inside
      your current Flutter SDK checkout at
      /Users/dhs/documents/fluttersdk/flutter. Consider adding
      /Users/dhs/documents/fluttersdk/flutter/bin to the front of your path.
    ! Warning: `dart` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/dart, which is not inside your
      current Flutter SDK checkout at /Users/dhs/documents/fluttersdk/flutter.
      Consider adding /Users/dhs/documents/fluttersdk/flutter/bin to the front
      of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 4d9e56e694 (3 days ago), 2023-04-17 21:47:46 -0400
    • Engine revision 1a65d409c7
    • Dart version 2.19.6
    • DevTools version 2.20.1
    • If those were intentional, you can disregard the above warnings; however
      it is recommended to use "git" directly to perform update checks and
      upgrades.

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

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

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

[✓] Connected device (5 available)
    • SM G975F (mobile)       • RZ8M802WY0X • android-arm64   • Android 11 (API 30)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 98.0.4758.80

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

[!] Flutter (Channel master, 3.10.0-15.0.pre.22, on macOS 12.2.1 21D62
    darwin-x64, locale en-GB)
    • Flutter version 3.10.0-15.0.pre.22 on channel master at
      /Users/dhs/documents/fluttersdk/flutter
    ! Warning: `flutter` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/flutter, which is not inside
      your current Flutter SDK checkout at
      /Users/dhs/documents/fluttersdk/flutter. Consider adding
      /Users/dhs/documents/fluttersdk/flutter/bin to the front of your path.
    ! Warning: `dart` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/dart, which is not inside your
      current Flutter SDK checkout at /Users/dhs/documents/fluttersdk/flutter.
      Consider adding /Users/dhs/documents/fluttersdk/flutter/bin to the front
      of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision fdd6b87636 (44 minutes ago), 2023-04-27 00:29:23 -0400
    • Engine revision d9f91aadff
    • Dart version 3.1.0 (build 3.1.0-48.0.dev)
    • DevTools version 2.23.1
    • If those were intentional, you can disregard the above warnings; however
      it is recommended to use "git" directly to perform update checks and
      upgrades.

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/dhs/Library/Android/sdk
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for
      more details.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 13C100
    • CocoaPods version 1.11.2

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

[✓] IntelliJ IDEA Ultimate Edition (version 2021.3.2)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 65.1.4
    • Dart plugin version 213.7228

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

[✓] Connected device (3 available)
    • Darshan's iphone (mobile) • 21150b119064aecc249dfcfe05e259197461ce23 • ios
      • iOS 15.3.1 19D52
    • macOS (desktop)           • macos                                    •
      darwin-x64     • macOS 12.2.1 21D62 darwin-x64
    • Chrome (web)              • chrome                                   •
      web-javascript • Google Chrome 109.0.5414.119

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

! Doctor found issues in 1 category.

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

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

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

[✓] Connected device (5 available)
    • SM G975F (mobile)       • RZ8M802WY0X • android-arm64   • Android 11 (API 30)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 98.0.4758.80

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

Thank you. This fixed it for me.
> void main() {
>   WidgetsFlutterBinding.ensureInitialized();
>   SystemChrome.setSystemUIOverlayStyle(
>     SystemUiOverlayStyle(
>       statusBarIconBrightness:
>           WidgetsBinding.instance!.platformDispatcher.platformBrightness ==
>                   Brightness.light
>               ? Brightness.dark
>               : Brightness.light,
>     ),
>   );
>   runApp(MyApp());
> }

@RolandDaum This seems to be more complex than just that, also, SystemChrome.setSystemUIOverlayStyle() seems obsolete now and AnnotatedRegion is preferable. I have a full description of the theming solution I'm using, perfected over many years, that addresses the issue of pretty startup as well:
https://deakjahn.github.io/flutter_theming_howto/


FYI - Landsat8 downloading made easier

Having looked through what you've done with the import pipeline it looks lovely - but a few things strike me;
a: we are working with the project builder and it would be amazing if rather than having to create our own subject sets we could pick which imagery provider and location we want to have images for and the import pipeline would be used to that effect.
b: I know you've said that the import-pipeline code wasn't supposed to be a 'here is how to do it' thing rather a 'here is what we did' - but it would be greatly beneficial if you mention that to be able to do something similar using USGS, you need an account with the right access rights, which is on a case by case basis.
c: There is now landsat-utils which developmentseed [1] have written (you probably already know this) - but I am thinking it could greatly simplify the processing pipeline (at least for L8). I've been having a play with it but I'm not a Ruby man (yet) - so work in progress.
[1] https://github.com/developmentseed/landsat-util

Thanks!  The zooniverse devs and @brianaharder have done amazing things with it.  Right now we're in a bit of a holding pattern, as we need to fix the import script. It does not pull lat/long and projection info from the landsat scenes, which is problematic, as the projection (lat/long WGS84) that it assumes and populates our database with is incorrect. We're working on a post-hoc fix, but, before we pull in any more data, it needs to be fixed in the import pipeline.  As to your questions
a) YES. That's something that would be incredibly valuable - even to us. We have contacts with non-landsat imagery of kelp canopies for non-giant-kelp species. If we could process them into FF using one pipeline, that would be amazing. Or even have spinoff projects.  But, geotiff in, image set with correct projection and latlong info out would be amazing. Happy to talk more about it and the other kinds of imagery our collaborators have.
b) In the readme or somesuch? We can likely update this.
c) I'm not sure if the other devs, @brianaharder , @Irosenthal, @kyleccav, or others have seen this. While great for L8, I'm not sure if its a general solution. Maybe it is?

Hi @jebyrnes  - thanks for the quick response.
a) - Yup I can imagine it'll be very useful for you - I guess I'm hoping it'll make it into the zooniverse core project (Panopes?) and then trickle down to be exposed in the project builder. How great would it be if you could select an area on a map, select satellites / data providers / resolutions / bands and just click go. I'll keep dreaming for a bit.
b) - here a similar issue with a good explanation (https://github.com/mapbox/usgs/issues/19)
c) - they are looking to do something similar for Sentinel 2 - so worth keeping an eye on.


enable/disable functionality not working in some cases

If the RIP is defined in more than one VIP, enable disable doesn't work
Reason display doesn't work (looks like problem with figuring out what file to read)

Enable doesn't work because assumption about VIP ordering is wrong.
The order that ipvsadm -L lists VIPs/RIPs is not the same that snimpy lists them.


Correct code for Codechef All String

Make correct code for branch Codechef.

Hello, I'm new to Open source contribution. Can you please guide me as to what do to in a more elaborative way? :)

Welcome aboard!
The best way is to search for projects which interests you, go through Readme.md most of the instructions you will find there (like how to setup, about the project, where to contribute etc) and start with issues marked with beginner or easy tag.
More elaborated :- https://rubygarage.org/blog/how-contribute-to-open-source-projects
Feel free to ping me for any queries. Happy Hacking.

hey @atyant  what is this new issue?

hey @atyant what is this new issue?

It's regarding the correct code for Codechef problem "All String" .
Happy Coding!

Please correct the email id.
On Mon, Oct 5, 2020, 11:05 PM Atyant Yadav<EMAIL_ADDRESS>wrote:

Closed #7 https://github.com/atyant-yadav/Hactoberfest2020/issues/7.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/atyant-yadav/Hactoberfest2020/issues/7#event-3841649948,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACMTXGADOWUPXUWGSXR5RXTSJH7VXANCNFSM4I4NZ3KQ
.


How to rebuild on top of latest tensorboard version?

Hi, recently Tensorboard added the ability to customize images per page (https://github.com/tensorflow/tensorboard/commit/0981512ee1934118d5c59fb6b7278a8d6e393ef3). This is a very useful feature for me but I use PyTorch and hence tensorboardX.
I'd like to update tensorboardX to have this feature. I expect I'd have to build from source to do this as pip shows me as having the latest tensorboardX version (0.8). But reading through your source code, I can't find where / what I would need to change to update the underlying tensorboard web server. Any advice would be appreciated. Thanks for maintaining a great project.

Nevermind, didn't realize that the tensorboard web server is a separate project that I update independently.


Feature Request: mirror traffic to two sets of endpoints

Do you want to request a feature or report a bug?
Feature
What did you expect to see?
Please add a feature to mirror/shadow incoming traffic to two sets of endpoints and be able to configure which amount goes where...e.g., something like this:
https://dzone.com/articles/traffic-shadowing-with-istio-reducing-the-risk-of

Hi! I'm Træfiker :robot: the bot in charge of communication regulation.
Thanks for your interest in Træfik!
Please edit your issue and use the provided template.
Issue templates help us help you by providing all necessary information.
Here are the available templates:

Standard issue
Feature request
Bug report

And remember: each time someone ignores the template, a cute little bunny dies.

#SaveTheCuteBunny :heart: :rabbit: :heart:

@kenyee I’ve actually started working on a PR, but given time constraints not sure I’ll finish before the March 20th cutoff for the 1.6 release, so most likely will be added in 1.7. :(

Cool...thanks @aantono :-)

Hello folks,
Just a friendly ping to understand where this feature is standing. Not urgent for me but it would be a nice to have in a near future (I'd rather not switch to something else if I can help it :)).
Thanks for all the great product!

Hello Traefik team! We really need this feature. Is there a chance that this feature would be in the future releases?

Is there any further progress on this? We currently use traefik but need to find a way to shadowing or similar and are starting to look at alternatives. A timeframe would be very useful if this is a WIP. Thank you!


Http adapter update

Major rework including removing dependencies on Guzzle and updating to use an instance based approach instead of a static one.  Closes #12 and #20.

For all of the "triple backtick" code blocks, if you use "triple backtick" + php like '''php but with backticks, it'll use syntax highlighting which will help with readability too. You might have to include the opening <?php though.

ok this time I promise all of the \t's are gone

OK tested this locally, still works for sending transmissions, I say :shipit:


smt diff should compare on contents as well as file name

In the long form of "smt diff", we should distinguish the case where the file name has changed (e.g. because it contains a timestamp) but the contents are unchanged.
Imported from Bitbucket issue 111,  created by apdavison on 10-25-2012 at 15:15, last modified: 12-17-2012 at 21:34

Implemented in r582
Trac comment by apdavison on 12-17-2012 at 21:34


Reader needs to know to hit Enter

tkn task start source-lister
prompts for contextDir
https://www.screencast.com/t/9CxAuY9Xr
the end-user needs to be told to hit Enter on their keyboard to accept the defaults

This is too much a ask in a tutorial to say you press enter to continue.. if the user is that dumb then he needs to get to his computer basics class 😁
Get Outlook for iOShttps://aka.ms/o0ukef

From: Burr Sutter<EMAIL_ADDRESS>Sent: Sunday, July 26, 2020 7:48:56 PM
To: redhat-developer-demos/tekton-tutorial<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [redhat-developer-demos/tekton-tutorial] Reader needs to know to hit Enter (#12)
tkn task start source-lister
prompts for contextDir
https://www.screencast.com/t/9CxAuY9Xrhttps://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.screencast.com%2Ft%2F9CxAuY9Xr&data=02|01||54e38224b21e481c6fda08d8316ed5e5|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637313699383930968&sdata=mHI91r7i9NyB%2Fu4EilA85itE3B%2FYrDqTbBT3FFEpS9w%3D&reserved=0
the end-user needs to be told to hit Enter on their keyboard to accept the defaults
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredhat-developer-demos%2Ftekton-tutorial%2Fissues%2F12&data=02|01||54e38224b21e481c6fda08d8316ed5e5|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637313699383940963&sdata=e11uqJ2Byx%2Bwx4iHKCSVni%2Bo36qZ0PxnJ6WKR1IlKDs%3D&reserved=0, or unsubscribehttps://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAHHMINLQY2SPEE5OE2IPO3R5Q3NBANCNFSM4PIABMVQ&data=02|01||54e38224b21e481c6fda08d8316ed5e5|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637313699383940963&sdata=XCTdtYlYqHciuFG78%2BMrKCwzJIPZxIRqVXmBNYZcDxA%3D&reserved=0.

Fixed via 6b97fc8


fix: resolve allday schedule data issue(fix #662)

Please check if the PR fulfills these requirements

[x] It's submitted to right branch according to our branching model
[x] It's right issue type on title
[x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[x] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes/features)
[ ] Docs have been added/updated (for bug fixes/features)
[ ] It does not introduce a breaking change or has description for the breaking change

Description
// test schedule data
{id: 1707234, title: '[allday]00:00 ~ same day 00:00', isAllDay: true, start: '2020-07-23T15:00:00Z', end: '2020-07-23T15:00:00Z', color: '#ffffff', isVisible: true, bgColor: '#ff9800', dragBgColor: '#ff9800', borderColor: '#ff9800', calendarId: 'workout', category: 'allday', dueDateClass: '', customStyle: '', isPending: false, isFocused: false, isReadOnly: false, isPrivate: false, location: '', attendees: '', recurrenceRule: '', state: ''}

AS-IS
rendered on 07/23 (wrong)
TO-BE
should be rendered on 07/24

Thank you for your contribution to TOAST UI product. 🎉 😘 ✨

It does not render normally in ie9.
More testing is needed.


Bump fred to 6.3.0

Hello,
fred should be bumped to the latest version :).

Hey, thanks for reaching out. I thought I already had dependabot set up properly, but it seems that's not the case. I'll fix things up as soon as possible.

Resolved here: v0.1.5.


no extractable files error inside folder with .rar

Hi; looking for help solving this logged error and no file extraction:
system: synology 918+ DSM 7.2 installed in container manager
Symptom: unpackerr not unpacking files
Errors:
"no extractable files found at: /volume1/downloads/**FILE NAME** (stat err: stat /volume1/downloads/**FILE NAME**: no such file or directory"
"[INFO] 2023/11/13 03:12:11 [Sonarr] Waiting for Start Delay: **FILE NAME**  (1m0s remains)"
"[INFO] 2023/11/13 03:19:11 [Unpackerr] Queue: [7 waiting] [0 queued] [0 extracting] [0 extracted] [0 imported] [0 failed] [0 deleted]"

Config file:
[[sonarr]]
  url = "http://<IP_ADDRESS>:8989"
  api_key = "1d45454d9**************a9a8b25f73"
  paths = ['/volume1/downloads']
  protocols = "torrent"
  timeout = "10s"
  delete_orig = false

Ive opened up all the permissions and confirmed my UID and GID numbers are programmed into docker

How did you install unpackerr?

Hi thanks for the reply. I will attatch the exported container settings.
unpackerr.json
currently I have mounted "/downloads" which i assume is really "volume1/downloads" where the downloads are located. I will try playing with the file mounting inside docker and specifically include volume1.

So it wont let me directly add "volume 1" Its has a dropdown for the folder, and a text editor field.  I have tried several options including:
"/downloads___________/downloads"
"/downloads___________/splat"
"/downloads___________/splat.splat"
I cant leave the second text box blank and the results in the container description show:
"/volume1/downloads:/downloads:rw"
"/volume1/downloads:splat:rw"
"/volume1/downloads:/splat.splat:rw"
all 3 end with the same result:
[INFO] 2023/11/13 14:43:29 [Unpackerr] Totals: [0 retries] [0 finished] [0|0 webhooks] [0|0 cmdhooks] [stacks; event:0, hook:0, del:0] [INFO] 2023/11/13 14:43:29 [Unpackerr] Queue: [8 waiting] [0 queued] [0 extracting] [0 extracted] [0 imported] [0 failed] [0 deleted]
unpackerr is connecting to sonarr so i assume it is correctly accessing the conf file? which is also specified in the volume mounting
[INFO] 2023/11/13 14:42:29  => Using Config File: /config/unpackerr.conf
"/docker/unpackerr___________/config"
or in the descripction as:
"/volume1/docker/unpackerr:/config:rw"
I don't understand how the names are different conf =/= config??
the above was specified in a tutorial i followed.

OK, so it turns out the problem is my lack of understanding of container manager.....
It works if the config file is set to /downloads and the container manager has the native /downloads mapped to /downloads inside the container. I thought that volume settings was all referencing back to native directories on the DSM not folders inside docker.
please close this thread, sorry to waist your time

/volume1/downloads does not exist in the container as you've called it /downloads within the container
the (community) install docs from the website should have helped with this.  What tutorial did you follow?
If download clients are downloading to /volume1/downloads you need to mount that exactly into the container or use the path in the config file to tell unpackerr what the equivalent is.  https://unpackerr.zip/docs/unpackerr/troubleshooting


Version 2.4.0

I'm going to give EasyDB a very quick code review. Once this is closed, consider the review completed.
Once this is done, at your earliest convenience, @shadowhand, can you convert and create the PHP 5.x release? I'll tag/sign/release 2.4.0 shortly thereafter.

Forgot to update the CHANGELOG. Let me do that first.