Package upgrades: Request link to changelog in commit message?

Note: The discussion appears to be at a state of everyone agreeing that putting a Changelog tag in the commit is a bad idea. See eg. https://github.com/NixOS/nixpkgs/issues/50483#issuecomment-439603594 for an alternative way to put the same information at a correct place.

Issue description
It is currently quite hard to know what exactly changes during package bumps when reviewing the commits, be it during a PR review or after-the-fact, when re-reading the commits, as there is often no link to a Changelog file easily accessible.
If the Changelog was necessarily present, it'd mean that reviewers could easily go and read it to check whether an update needs backporting (eg. whether it fixes security issues). It'd also make it much easier for people who follow the git history of nixpkgs to figure out what changed in a package update, without having to scout the web for a Changelog.
Proposed solution
Request that every package bump include, in its commit message, Changelog: [url of the changelog], or Changelog: none if upstream doesn't provide a Changelog.
This is a policy change, and will likely require quite some time to get all reviewers to check for the presence of the Changelog tag.
Future work
@GrahamcOfBorg can be useful here by adding a check for commits that have -> in their title, checking for a Changelog tag. However, it should not display as a failed check if it's absent, as the “-> in the title” heuristic may catch non-upgrade commits.
It may also be possible to, later on, request that people who submit PRs add in a Security fix: [CVE or URL list] or Security fix: none, to make it easier for specifically security fixes. I didn't propose this straight away because it requires potentially more work to figure out, and sometimes the security fixes aren't even known at the time the update is made.
Finally, this is part of a long-term plan of mine to revive the “Security fixes from 20xx-xx-xx” series, by making it easier to figure out which commits introduce security fixes.
Alternatives
It would also be possible to request a link to the changelog in a meta.changelog field, but changelogs may change location between versions, so it wouldn't be a good place to put it in if we want automated tools to check that the Changelog link is always up-to-date.
On the other hand, requesting it to just always be present in the commit message, even if it is the same Changelog as the previous one, means that there must always be a conscious effort of searching for it.
Drawbacks
It's more burden when bumping a package, as it also requires fetching the Changelog. This could be mitigated by actually adding a meta.changelog item that would hold the link to the Changelog, for packages for which it is known not to change often.
What do you think about it?

It would also be possible to request a link to the changelog in a meta.changelog field, but changelogs may change location between versions, so it wouldn't be a good place to put it in if we want automated tools to check that the Changelog link is always up-to-date.
On the other hand, requesting it to just always be present in the commit message, even if it is the same Changelog as the previous one, means that there must always be a conscious effort of searching for it.
Drawbacks
It's more burden when bumping a package, as it also requires fetching the Changelog. This could be mitigated by actually adding a meta.changelog item that would hold the link to the Changelog, for packages for which it is known not to change often.

I think allowing meta entries about changelog should happen before policy changes requiring changelog, in the sense that things that can be done cheaply and only once should be done before falling back to a more costly solution.

I think there might be an intermediate case: there is a stable page that doesn't change often, that contains changelog. I mean a layout like https://kernel.org/ — maybe it would also be good to reflect in meta. Changelog never existing might also be a good thing to record, to avoid making a thorough check every time instead of every year.

In the ideal world >50% of updates will be done by r-ryantm or equivalents. How the case when the bot does the update and testing — and changelog is always in a different place — should be handled?

I think we agree here, but kind of preferred to ask for general opinions about a changelog before sending in a PR, especially as I'm not sure the fallback of my last PR changing meta is over yet :)
For kernel.org, I'd think one could just point the meta.changelog (or Changelog: in the commit, depending on what the outcome of this discussion gives) url to this page: it's meant to be used by a human anyway, using it automatically would require much more metadata I'm not sure we'd be willing to input.
In this case, I think the bot should be taught how to find the changelog. If it can't, anyway a human will have to go and seek the changelog to figure out whether the change needs to be backported, so that human could also commit --amend to add the changelog while they're at it…?

Also, thinking about it, maybe for user-friendliness it may make sense to actually have all changelog entries be in meta.changelog, with a format like:
{
  # ...
  meta.changelog = {
    "1.2.3 -> 1.2.4" = https://example.org/changelog;
    "1.2.4 -> 2.3.5" = https://example.org/changelog-v2;
  };
}

And then either add an entry to the “list” or increase the version number of the last entry upon an update.
This would make display of changelog lists possible on eg. the packages page.
Maybe this would be better than using the commit messages for this information?

And having = null for version upgrades that have no changelog, so that automated tooling could warn if the meta.changelog set is the same before and after the upgrade.

I'm in favor of adding a changelog or releaseNotes meta entry. E.g. this for postgresql:
{
  meta.changelog = "https://www.postgresql.org/docs/current/release.html";
}

Which will also allow people to more easily link the changelog in the PR.

@Ekleog I think structured meta entries are not supported?
Amending commits is not a straightforward approach, as the person to review would often be a person without access to updater bot branches.
I would say that direct link to changelog vs indirect link to a page that usually has the changelog might be a useful distinction for expectation management. Or maybe not.

There is a difference between the people writing packages and those consuming packages.
For consumers, everyone can see that it's great to have such links. Especially as a specific URL that doesn't change or perhaps even a copied changelog (because URLs can die).
For producers, it's just more work (and it's not exactly a creative activity). It's something that just needs to be automated or not done at all, IMHO.
As such, I am very much against this. The idea to increase the amount of work when there is still a pile of work does not compute for me. No, the way to run an organisation or process is to increase efficiency first (for example by doing what ryantm is doing which sort of seems to be getting more broader acceptance)  and only then to raise either the volume of products (= more packages) or the quality (=adding a changelog).
Increasing work load without the required efficiency improvements in the process does not scale. All it will do is create a greater risk for maintainers to leave and for NixOS to rot away.
In general, I think every such suggestion increasing the amount of work to be done without obvious improvements in efficiencies that happened before (for example more committers might also count as a process improvement) should be closed without discussion. A lot of similar ideas have come by and they have all failed.
If we want something useful to come out of this issue, I think we should have the policy to as quickly as possible close such "ideas".

@7c6f434c My reading (coming from https://github.com/NixOS/nix/issues/2532) of https://github.com/NixOS/nix/blob/6924bdf2bf8f50f2e6ec5d490571594450aba13a/src/libexpr/get-drvs.cc#L166 is that both lists (eg. maintainers) and attrsets (which I don't think we have right at top-level now indeed, but we do have these as eg. items of the maintainers list) are allowed, so I don't think it'd be impossible per se :)
@coretemp The package updater must already look for the changelog anyway. If they don't, they aren't doing their job properly, because an update might include security fixes and need to be backported. Requiring that the changelog is explicitly updated helps ensure updaters actually do their job and don't make the things worse for everyone by merging a security update in master only, making people assume they checked the changelog.

@coretemp The package updater must already look for the changelog anyway. If they don't, they aren't doing their job properly, because an update might include security fixes and need to be backported. Requiring that the changelog is explicitly updated helps ensure updaters actually do their job and don't make the things worse for everyone by merging a security update in master only, making people assume they checked the changelog.

I wonder what is the share of contributors who never use stable, never going to use stable, and are never sure if stable needs a backport in the corner cases… I definitely don't actually care about stable even if I try to remember in the clear-cut cases.
Anyway, sooner or later some user will wonder whether a backport is needed; so having a way to store the changelog habits of a project is a net process improvement. Once we see how it works out, then maybe we could automate nagging about the changelogs for updates.
Maybe the changelog nagging will sometimes be investigated by people who want to contribute but lack confidence to write code or docs…

I wonder what is the share of contributors who never use stable, never
going to use stable, and are never sure if stable needs a backport in
the corner cases… I definitely don't actually care about stable even
if I try to remember in the clear-cut cases.

That's actually part of the reason I want changelogs easily accessible:
to be able to easily review the changelogs of (at least part of) the
updates that are merged into master to scan through for security fixes,
so that even if one backport is forgotten someone would hopefully
notice. (not saying “I” because I know I won't reasonably have time to
review more than a handful of commits compared to the mass merged, but
if enough people do the same we should cover a statistically significant
portion of the bumps)

Can this issue get closed now since https://github.com/NixOS/nixpkgs/pull/60371 is merged and an issue in https://github.com/NixOS/ofborg/issues/416 exists?

If there is anything left to be done, that should live in the RFC repo.


Support restoring from the same MyGet feed packages are pushed to

Adds support for restoring NuGet packages from the same MyGet feed packages are pushed to.
Btw. whats the reason for having https://www.myget.org/F/gep13/api/v2 there?

@pascalberger said...
Btw. whats the reason for having https://www.myget.org/F/gep13/api/v2 there?

It's actually not required anymore.  In the original gep13.DefaultBuild version, I was restoring some MSBuild Targets from NuGet packages that were hosted on that MyGet feed.  Those packages are not required anymore.
I will remove it just now.

@gep13 Just found out that this doesn't work as the SourceUrl is https://www.myget.org/F/cake-contrib/api/v2/package instead of https://www.myget.org/F/cake-contrib/api/v2

DANG IT!

The url's are different between push and pull.
We can create a new parameter if you want to, or feel free to hard code it in just now.


ODP-179 - HIVE-7145|HIVE-20016|HIVE-28121  Backporting changes f on top of ODP hive-2.3.101 and merge into 2.3.102 branch

What changes were proposed in this pull request?
Below commits are backported
https://github.com/apache/hive/commit/ff41c46601c756330e9fdce91f6da94a04da4eff
https://github.com/apache/hive/commit/10b3b0310d486fdb665de9b0d70dfa6c5163be79
https://github.com/apache/hive/commit/0b8dc8b040e8a58d8fd85f5364ef5f9608f99ecb

it just has 204 commits in this PR, something messy, closing


Added new MQTT /EVTotalEnergyCharged topic to track EV energy in Home Assistant

Since there is no topic containing the total ev energy, I created a new one. It works as expected with my Inverse Eastron EV meter. 'EnergyEV' is also used on the main-page, can I assume it works for all EV meters?

Yes that will work for all kWh meters; thx for your contribution!


CodeClimate: Setting Up Test Coverage

@shernshiou would you mind to either add me as an admin to this repo or follow this instructions to enable code coverage reports for this project? Would be nice to see where we at :)

I will assign you as the admin.

Thanks! Turns out, admin level rights are only available for organization-maintained repos. In other words, you're the only one who could setup it up :)
I'd vote for it. Hope you can find some time to help with it.

@agraebe yeah too bad. I tried to insert the token into .travis.yml but it doesn't work. I wonder whether the token is correct.

I think I got it figured out. I'm adding some more tests to have > 90% coverage :)

see latest merged PR 👍


Add returns property to node_execute so npm doesn't freak out on warnings

ping @chef-cookbooks/delivery-migration-team

This PR was superceded by https://github.com/chef-cookbooks/languages/pull/23


add TestContainerApiPause case

Signed-off-by: Yuan Sun<EMAIL_ADDRESS>

Hi duglin,
Function getSliceOfPausedContainers has been updated. Could you please review it ?

LGTM

LGTM


Fixed spelling of finished in error message

While trying to deploy my first ruby app on Openwhisk, I noticed this spelling typo.

Thanks @juliancheal


Wrong set requirments of YII

I want to report that requirments for Yii are set wrongly and they dosn't allow the framework to work.
For example, in many requirments is set an unnessecary set a fixed versions or a upper limits of it.
To fix this issue, please replace in the requirments that instead of fixed ones were fixed a actual version and above ( for example: >= 1.0) or that it would allow any version ("*")
Please add into the standard above requirment, plus that the notification of "^", "~", "<", "<=" won't be used anymore to preventing that Yii stop to become usable after it's components updates, with would become excluded by the limiting the version rules

Please refer to specfic problems in eg. composer.json files.

Please refer to specfic problems in eg. composer.json files.

I was attempting to download thru composer the avaliable templates (basic and advanced) and I had recieved errors, like for example the one, that my version of PHP (8.0) is above the set version limit (<8.0).
When I had downloaded it as archives, I had recieved the same errors when I tryed to download requirments thru composer

I've checked Yii main package and both basic and advanced templates, all require just the minimum version of PHP, not limiting the maximum one. This most probably comes from one of the additional dependencies, the question is which one. Please provide the composer message you see when trying to install dependencies.

I paste a dump of whole download process, that you can see the whole situation from the begining to the end: pastebin dump

So that's https://github.com/Codeception/module-yii2

that's too, but the main problem is the line above it

codeception/module-yii2[1.0.0, 1.0.1, 1.1.0, 1.1.1] require php >=5.6.0 <8.0 -> your php version (8.0.0) does not satisfy that requirement.

with probably block it's download. See in this line that there someone has (unessecary) set a upper limit for PHP, with blocks Yii from working after the PHP got updated to version 8

That's what I am referring to as well. That is https://github.com/Codeception/module-yii2.
They have a php8 version in development.

the question is, why there is no info on the download page that the actual version won't work with php8? if there would be one then the issue wouldn't become reported in the first place

You're still barking up the wrong tree. Please report to https://github.com/Codeception/module-yii2
Also PR https://github.com/Codeception/module-yii2/issues/17 has been created yesterday.

The Yii itself works well with PHP 8. Codeception does not yet.

Since the issue can't be solved from within Yii, closing.


use libtorch c++ distribution with c++11 strings in gpu image

So this tries to install libtorch with the goal of building the libtorch fallback in TVM with that.
Hopefully, I can push #10758 along, it was a long time.
Unfortunately, if this would work, it'd need a build image update.

Thank you @masahi


Add secondary navigation to Support claims page

Context
We want to add in the following flows:

Payments (Downloading CSV of claims, uploading CSV of payments)
Sampling (Uploading CSV of claims to be sampled)
Clawback (Uploading CSV of claims to be clawed back)

This is the initial PR to add in the tabs, without adding the functional parts to keep future change sets to a minimum.
Changes proposed in this pull request

This commit adds the "Payments", "Sampling", and "Clawback" tabs to the Claims page.

Guidance to review

Content will change in a future PR.
This PR is a starting point to add in these flows in an incremental manner.

Screenshots

Actually, I've decided to drop this PR.
As we're now moving to implement 1 flow at a time, we can add the tabs in as the flows are added.


Make the distributed learning example runnable on a single machine

What do these changes do?
Previously we provided the distributed learning example, but the notebook is not runnable. We fix this in the PR.
Related issue number

Fixes #issue number

Please clear outputs in the notebook.


O instalar nao funciona

What Happened
Eu clico em instalar e o pluging não instala
How to Reproduce
godot-block-coding-1c877c7589ad35d11a57048b3a2a089039c55332.zip
Operating System
Android
Logs or command-line output
No response
Anything else?
No response

@mar1br1ght obrigado por informar! Deve ser corrigido pelo #154

This should be fixed in latest release https://github.com/endlessm/godot-block-coding/releases/tag/v0.6.1


False positive - redundant cloudtrails

Describe the bug
Thrifty Mod returns incorrect number of Global Trails when Org Trails are in use
FooliOrgTrails-ModifyEventsCloudTrail-xJdAZqCR4abt is one of 18 global trails.
Steampipe version (steampipe -v)
SPC v0.18.0
Plugin version (steampipe plugin list)
Plugin 0.18.0
To reproduce
In an AWS Org with 6 accounts and 3 CloudTrails defined by the organizational parent, the incorrect number of redundant trails is reported.
Create an AWS Org
Create a child account
Create three trails
Note that the number of trails is 6 not three
Expected behavior
The thrifty mod should not double count identical cloudtrails that are managed by the AWS Organizations management account.
Additional context
May be related to https://github.com/turbot/steampipe-mod-aws-compliance/issues/536

Hey @jchrisfarris, sorry for the delayed response on this one.
I have made some changes to the query for the control called multiple_global_trails in this pull request. Could you please test it out and share your feedback with us?

Exiting behaviour -
> with global_trails as (
      select
        count(*) as total
      from
        aws_cloudtrail_trail
      where
        is_multi_region_trail
      )
    select
      arn as resource,
      case
        when total > 1 then 'alarm'
        else 'ok'
      end as status,
      case
        when total > 1 then name || ' is one of ' || total || ' global trails.'
        else name || ' is the only global trail.'
      end as reason
    from
      aws_cloudtrail_trail,
      global_trails
    where
      is_multi_region_trail;
+----------------------------------------------------------------------------+--------+--------------------------------------------------------+
| resource                                                                   | status | reason                                                 |
+----------------------------------------------------------------------------+--------+--------------------------------------------------------+
| arn:aws:cloudtrail:us-east-1:122324354354:trail/turbot-aab-us-east-1-trail | alarm  | turbot-aab-us-east-1-trail is one of 18 global trails. |
| arn:aws:cloudtrail:us-east-1:122324354354:trail/turbot-aab-us-east-1-trail | alarm  | turbot-aab-us-east-1-trail is one of 18 global trails. |
| arn:aws:cloudtrail:us-east-1:122324354354:trail/turbot-aab-us-east-1-trail | alarm  | turbot-aab-us-east-1-trail is one of 18 global trails. |
| arn:aws:cloudtrail:us-east-1:122324354354:trail/turbot-aab-us-east-1-trail | alarm  | turbot-aab-us-east-1-trail is one of 18 global trails. |
| arn:aws:cloudtrail:us-east-1:122324354354:trail/turbot-aab-us-east-1-trail | alarm  | turbot-aab-us-east-1-trail is one of 18 global trails. |
| arn:aws:cloudtrail:us-east-1:122324354354:trail/turbot-aab-us-east-1-trail | alarm  | turbot-aab-us-east-1-trail is one of 18 global trails. |
| arn:aws:cloudtrail:us-east-1:122324354354:trail/turbot-aab-us-east-1-trail | alarm  | turbot-aab-us-east-1-trail is one of 18 global trails. |
| arn:aws:cloudtrail:us-east-1:122324354354:trail/turbot-aab-us-east-1-trail | alarm  | turbot-aab-us-east-1-trail is one of 18 global trails. |
| arn:aws:cloudtrail:us-east-1:122324354354:trail/turbot-aab-us-east-1-trail | alarm  | turbot-aab-us-east-1-trail is one of 18 global trails. |
| arn:aws:cloudtrail:us-east-1:122324354354:trail/turbot-aab-us-east-1-trail | alarm  | turbot-aab-us-east-1-trail is one of 18 global trails. |
| arn:aws:cloudtrail:us-east-1:122324354354:trail/turbot-aab-us-east-1-trail | alarm  | turbot-aab-us-east-1-trail is one of 18 global trails. |
| arn:aws:cloudtrail:us-east-1:122324354354:trail/turbot-aab-us-east-1-trail | alarm  | turbot-aab-us-east-1-trail is one of 18 global trails. |
| arn:aws:cloudtrail:us-east-1:122324354354:trail/turbot-aab-us-east-1-trail | alarm  | turbot-aab-us-east-1-trail is one of 18 global trails. |
| arn:aws:cloudtrail:us-east-1:122324354354:trail/turbot-aab-us-east-1-trail | alarm  | turbot-aab-us-east-1-trail is one of 18 global trails. |
| arn:aws:cloudtrail:us-east-1:122324354354:trail/turbot-aab-us-east-1-trail | alarm  | turbot-aab-us-east-1-trail is one of 18 global trails. |
| arn:aws:cloudtrail:us-east-1:122324354354:trail/turbot-aab-us-east-1-trail | alarm  | turbot-aab-us-east-1-trail is one of 18 global trails. |
| arn:aws:cloudtrail:us-east-1:122324354354:trail/turbot-aab-us-east-1-trail | alarm  | turbot-aab-us-east-1-trail is one of 18 global trails. |
| arn:aws:cloudtrail:us-east-1:122324354354:trail/turbot-aab-us-east-1-trail | alarm  | turbot-aab-us-east-1-trail is one of 18 global trails. |
+----------------------------------------------------------------------------+--------+--------------------------------------------------------+

After query update -
with global_trails as (
      select
        account_id,
        count(*) as total
      from
        aws_cloudtrail_trail
      where
        is_multi_region_trail and region = home_region
      group by
        account_id,
        is_multi_region_trail
    )
    select
      arn as resource,
      case
        when total > 1 then 'alarm'
        else 'ok'
      end as status,
      case
        when total > 1 then name || ' is one of ' || total || ' global trails.'
        else name || ' is the only global trail.'
      end as reason
    from
      aws_cloudtrail_trail,
      global_trails
    where
      is_multi_region_trail
      and region = home_region;
+----------------------------------------------------------------------------+--------+------------------------------------------------------+
| resource                                                                   | status | reason                                               |
+----------------------------------------------------------------------------+--------+------------------------------------------------------+
| arn:aws:cloudtrail:us-east-1:122324354354:trail/turbot-aab-us-east-1-trail | ok     | turbot-aab-us-east-1-trail is the only global trail. |
+----------------------------------------------------------------------------+--------+------------------------------------------------------+

The above fix works as expected in our tests. We will release it soon. Please feel free to let us know if you face any issues.


Slider OnClick is not being prevented on Carousel movement

pure-react-carousel version: 1.27.6
react version: 17.0.2
node version: v10.16.1

Relevant code or config:
 <Slider> > handleOnClickCapture(ev) line #286

const your = code => 'here';

What you did:
We are attempting to prevent clicks of the carousel slider when the carousel is in movement.

What happened:
The onClick event is still triggered on drag events

Reproduction:

Suggested solution:
Remove the line #293 from <Slider /> =

Can you help us fix this issue by submitting a pull request?

Hey this is not stale.


fix: Fix wrong handling of SAF-returned Uri

Note that importing the module you sent in the Discord server (ezmanager.zip) failed with a JSONException.

you should use the dev branch doe

o right


Documentation: difference between Sfc5xxxShdlcDevice.get_calibration_initial_conditions() and Sfc5xxxShdlcDevice. get_calibration_recalibration_conditions() is unclear

The documentation says the follwoing:
Sfc5xxxShdlcDevice. get_calibration_recalibration_conditions(index)
Get the recalibration conditions of a specific calibration index.
Sfc5xxxShdlcDevice.get_calibration_initial_conditions(index)
Get the initial calibration conditions of a specific calibration index.
However, the difference between "initial calibration" and "recalibration" is unclear to me. As far as I can tell, the SFC5xxx MFC units have a number of calibration blocks for different gas types, and they are just that: calibrations. What is an initial calibration, and what it is a re-calibration? Why/how do these need to be treated differently?
Edit (to provide some background to my question): in the example code given at https://sensirion.github.io/python-shdlc-sfc5xxx/master/quickstart.html , how would you expand the loop showing the calibration information to also show if the the calibrations are "real gas" or "gas conversion" calibrations? Which of the two commands (initial_calibration vs recalibration) would one use?

The initial calibrations are the calibrations done during production of the MFC at Sensirion. However, each of the calibrations can be re-calibrated for example to match with a particular reference device, or to map it to a slightly different gas. This can be done either by Sensirion or by a Sensirion representative. The information about such a recalibration is then stored within the MFC, next to the initial calibration data. However, MFCs usually don't contain a recalibration if you never explicitly let your MFCs recalibrate.
If there's no recalibration, all the recalibration condition parameters are zero (e.g. "company" is an empty string). I hope this answers your questions.

Thanks for this explanation, makes sense now. It would be nice to add this information to the documentation.


Lazy people don't like typing project in the cli again, and again, and again…

In my focus group of 1, every swagger … CLI command I type happens in the context of a project. But I have to type swagger project start and swagger project edit. Why not just assume the project?
This would feel more like heroku CLI to me. I heroku create _name_ and heroku logs and heroku local without having to specify my app name, at least when I'm in the context of a project directory.

#lazywbe

alias swaggerp="swagger project"


Search Time Events in Time Graph Views

Added a dialog-box to timegraph-output-component to search for events
The view updates its contents as the user enters the string
The filter is applied and unsuccessful time events are dimmed

This patch depends on:

https://git.eclipse.org/r/c/tracecompass.incubator/org.eclipse.tracecompass.incubator/+/200991
https://github.com/eclipse-cdt-cloud/timeline-chart/pull/243

Screen Recording 2022-11-23 at 11.45.00 AM.webm
The time event filtering uses its own domain-specific language (DSL) . Various logical operators are suppported:

&& performs a logical AND operation between two filter expressions. Example: ioctl && 5755
|| performs a logical OR operation between two filter expressions. Example: ioctl || splice
! performs a logical NOT operation between two filter expressions. Example: !ioctl

Filter expressions have the following pattern field operator argument in general. Several relational operators are available:

test whether the value of the specified field is equal to the given argument. Example: TID == 5755
test whether the value of the specified field is not equal to the given argument. Example: TID != 5755
matches test whether the value of the specified field matches to the given argument. Example: TID matches 5.*5$
contains test whether the value of the specified field contains to the given argument. Example: TID contains 7
test whether the value of the specified field is greater than the given argument. Example: "SOFT IRQ" > 4
test whether the value of the specified field is less than the given argument. Example: "SOFT IRQ" < 4

Making use of Material UI to help create the search box. I found it much easier to use as compared to Semantic UI. Here's a mockup of a future patch that would allow users to save multiple filters - the chips are built using Material UI:

@hriday-panchasara The gap style seems to be applied correctly. However, when removing the filter the states seemed to still dimmed. Could you please look into this?

This is still an issue with the recent timeline-chart update of PR https://github.com/eclipse-cdt-cloud/timeline-chart/pull/243.

@hriday-panchasara The gap style seems to be applied correctly. However, when removing the filter the states seemed to still dimmed. Could you please look into this?

This is still an issue with the recent timeline-chart update of PR eclipse-cdt-cloud/timeline-chart#243.

Yup, I'm assuming its related to the timeline-chart repo. I'll keep all patches open until this is resolved

@hriday-panchasara The gap style seems to be applied correctly. However, when removing the filter the states seemed to still dimmed. Could you please look into this?

This is still an issue with the recent timeline-chart update of PR eclipse-cdt-cloud/timeline-chart#243.

I've added a small fix for this issue, could you let me know if it looks good?


adding intendation feature

A nice "visual" way we group some related cards in the same list together is by prepending the card title by one, two or three tildes characters (~). This pull request i did does intend the cards up to three levels when you prepend the card title by -, --, --- or ~, ~~, ~~~ visually (see screenshot).
I use this method, for example, when some original card once had a checklist but then the points got separated to full cards. Then i prepend this cards with one or more tildes to not "lose" the checklist feeling/related feeling

It would be nice if you can test it and merge it to the master or give me an advice to make it even better
(Edited to clean up my messy english)

This is a good idea. I went thru the code a bit via mobile, I would need to rename some of the classes for better English (it's indent, not intend) and I would need to move those regex to config. I'll go over it tomorrow on my laptop, merge it in and optimize. In the meantime I'm thinking about the feature itself, wondering if there might be a better way to visually present them.

Yay, me and my english spelling :/ sorry for that. I can cleanup this mess and re-commit it if you like. I would be glad to hear another way to visually present this but a simple itendation is enough for me right now ^^  I took the margin approach but there are sure many other ways to do it.

Hey, sorry for not commenting earlier, I'm on vacation and I didn't have even a decent Internet connection. The thing that bothers me (and a couple of other Pro4Trello users) with this feature is that the indentation portrays a dependence between cards but only visually => cards are not actually dependent. This means that when I move a card that has siblings (visually) to another list, the indented cards remain indented and can (visually) start being dependent on another card, just like that... I guess what I'm trying to say this is not a versatile solution. I have to give it additional thought but I don't see this as a good feature for Pro4Trello in this form.


Complete the CommonHTML output

This is a meta-issue.

[x] add webfonts support
[x] #1035  improve fractions
[x] proper stretchy characters
[x] stretchy embellished operators
[x] support mtable attributes
[x] variable-width mtable elements
[x] #968  add mlabeledtr support
[x] TeX versus MathML spacing
[x] allow mtextInheritFont
[x] support mathsize attribute
[x] match font heights
[x] support displayAlign and displayIndent
[x] support line breaking
[x] bevelled fractions
[x] handle hrefs, class, and other attributes
[x] support maction
[x] support menclose
[x] support ms
[x] support mglyph
[x] support mphantom
[x] support mmultiscripts
[x] handle VCENTER TeXAtom
[x] add isMathJax to created nodes
[x] handle zoom action
[x] update web fonts
[ ] https://github.com/mathjax/MathJax-dev/issues/11 create new combined configurations with CommonHTML as default

What else?

Really looking forward to this release @pkra !

=> Merged  (the chtml branch has been merged into develop).

:party:

:beers:

@dvpc the about window shows "generic fonts" right now (with local fonts installed). IIUC, that's in the menu code. Should I open a separate issue?

:clap:

the about window shows "generic fonts" right now

OK, I've fixed that.

I think this is complete at this point, so I'm closing it.  Bugs with CommonHTML output should get their own issues at this point.


ClojureScript packaging

This project's build script packages a minimized core js + desired languages into a single file.  Would you consider an option to output these as separate files? (i.e. core file, lang1 file, lang2 file).
Having the separate pieces of the library as separate files allows us to defer the inclusion decisions to other build systems.  The recent standardization of how ClojureScript imports JS libs would benefit from this.
(ns example
  (:require
    highlight
    highlight.html
    highlight.javascript))

Why you cannot use npm build for that?

In fact, you have two different options:

Use the raw source to build whatever you need. We specifically keep it free from any packaging convention to allow for any build target. So the core and every language are just JavaScript functions in separate files that can be wrapped in something.
As @Sannis said, use the NPM build which keeps all the languages and the core separate but wraps them into the CommonJS interface with module.exports.

I mean, if I was doing this outside the build script, I would definitely write my own thing to split the browser target highlight.pack.js into separate files so that we benefit from the minification steps and we wouldn't have to make assumptions on what to wrap the language files with (i.e. hljs.registerLanguage).
So I thought this could be inserted as an option to the build script to get the intermediate output that already exists before concatenation.  Would you accept a patch for this?
(npm build is specific to commonJS and non-minified)

Let me lay out my thoughts one by one, as I seem to have trouble to make a coherent point today, sorry :-)

Actually, the browser build is compressed after it's concatenated, so you can't just have separate compressed files for free. And I'd be against reordering that because it would make the build way slower (we tried).

The separate compressed language files are useless as-is, they have to be wrapped in some code registering them with the library. If ClojureScript has its own module convention then the best way is probably make a separate build target, not an option for the browser build (but see the next point).

There's another build type — "cdn" — that may be closer to what you need. It creates separate minified language files in the form hljs.registerLanguage('<language name>', '<file contents>');. The core library is usually bundled with some common languages but it can be avoided with node -t cdn :none to get the pure library core.

What do you think?

The "cdn" build is perfect!  Thanks for clearing up the options @isagalaev

OK, glad it worked for you. We probably have to document it better.

@isagalaev we found cdn build hosted here.  Could I submit a PR there to add a highlight.core.min.js?  (for no integrated languages)

@shaunlebron that repo is a verbatim source for our CDN hostings and it is updated by a script, so adding manually a file there will be obsolete as soon as a new version is released.


Problem with integrating data

My graph output does not split the experimental and control groups into separate violin plots. Look at the graph and see that the violin plots do not contain two columns or violins, as the experimental and control groups are plotted as one using the same color. I need help splitting the graph.

Here is the code leading up to this point:
`suppressPackageStartupMessages({
library(dplyr)
library(Rcpp)
library(harmony)
library(Seurat)
library(patchwork)
library(SeuratData)
library(qs)
library(ggplot2)
})
{
ctrl.d1.data <- Read10X(data.dir = r"(C:\Users\cellsworth\Documents\R data\SC_data\B6_2dpi_F1_filtered_feature_bc_matrix)")
ctrl.d1 <- CreateSeuratObject(counts = ctrl.d1.data, project = "C3.now", min.cells = 3, min.features = 200)
ctrl.d2.data <- Read10X(data.dir = r"(C:\Users\cellsworth\Documents\R data\SC_data\B6_2dpi_F2_filtered_feature_bc_matrix)")
ctrl.d2 <- CreateSeuratObject(counts = ctrl.d2.data, project = "C3.now", min.cells = 3, min.features = 200)
stim.d1.data <- Read10X(data.dir = r"(C:\Users\cellsworth\Documents\R data\SC_data\C3KO_F1_filtered_feature_bc_matrix)")
stim.d1 <- CreateSeuratObject(counts = stim.d1.data, project = "C3.now", min.cells = 3, min.features = 200)
stim.d2.data <- Read10X(data.dir = r"(C:\Users\cellsworth\Documents\R data\SC_data\C3KO_F2_filtered_feature_bc_matrix)")
stim.d2 <- CreateSeuratObject(counts = stim.d2.data, project = "C3.now", min.cells = 3, min.features = 200)
}
If you are just loading data from your saved file and dont have a saved ifnb.list object
ctrl.d1$donor <- "d1"
ctrl.d2$donor <- "d2"
stim.d1$donor <- "d1"
stim.d2$donor <- "d2"
ifnb.list <- list("ctrl.d1" = ctrl.d1, "ctrl.d2" = ctrl.d2,
"stim.d1" = stim.d1, "stim.d2" = stim.d2)
pbmc <- merge(ifnb.list[["ctrl.d1"]], y = c(ifnb.list[["ctrl.d2"]],
ifnb.list[["stim.d1"]], ifnb.list[["stim.d2"]]),
add.cell.ids = c("ctrl.d1", "ctrl.d2",
"stim.d1", "stim.d2"), project = "pbmc")
The [[ operator can add columns to object metadata. This is a great place to stash QC stats
grep ("^CCL", rownames(pbmc[["RNA"]]),value = T)
pbmc[["percent.mt"]] <- PercentageFeatureSet(pbmc, pattern = "^mt-") # this dataset doesnt contain MT DNA, otherwise we subset on <10% MT
VlnPlot(pbmc, features = c("nFeature_RNA", "nCount_RNA"), ncol = 2)
#OUTPUT
FeatureScatter(pbmc, feature1 = "nCount_RNA", feature2 = "nFeature_RNA")
#OUTPUT`

Hi @Depraved-Dolphin
Can you please tell me the output of<EMAIL_ADDRESS>as well as sessionInfo() thanks

Any updates on this?

Hello @Dragonmasterx87 ,
Thank you for the attention to this issue. I was able to find the problem. I did not specify the metadata in the D1, D2 objects. Once I added the metadata, the integration was able to proceed.

Hello @Dragonmasterx87 ,
Thank you for the attention to this issue. I was able to find the problem. I did not specify the metadata in the D1, D2 objects. Once I added the metadata, the integration was able to proceed.

Yes, thats why I was asking for<EMAIL_ADDRESS>that would have told me what kind of metadata you have in your object, and if a slot was present having the data you needed. R needs to be told which data belongs to what kind of individual/experiment etc, and it does that via the metadata slot. So always remember to allocate metadata information carefully.
I am closing this issue now as resolved, if you have other questions related to this you can still message within this thread (even when closed) if you have other questions please raise a new issue.
🐉


AutSPACEs Data Management

Summary
This issue lists data management processes for AutSPACEs for reporting, ethics submission and other purposes.

This may be more useful somewhere in the repo than in an open issue


[9.x] PHP 8, switch to match

much shorter and nicer way

This is actually a breaking change. The old code used to work with stringable objects. The new code does not.

So, I close the pull request?


Celaction: collect audio refactory

Description
At the moment the function get_subsets is returning versions and it is strangely confusing.
Also the label is Append Audio and name of plugin Collect audio.
[cuID:PYPE-1326]

Considering the lack of celaction demand, outside of the current implementation. I'd suggest dropping this


提示中需要可以添加链接

Is your feature request related to a problem? Please describe.
链接组件和富文本提示中加富文本
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

可以新增基础组件——提示组件，组件属性包含 提示语可以富文本编辑，提示图标可以自定义


Server-Side

Hi, I just want to ask if how to make a server side paging?
Thank You!

I have not started this feature yet, however, it is on the roadmap https://github.com/IvanJosipovic/BlazorTable/issues/39

Hey @IvanJosipovic do you have an ETA for this?
This is an absolutely essential feature when working with large amounts of data.
Thanks.

Yes, that should be on the stable version because when we build the product, especially in admin pages, then we always need to do paging on the server-side.

Yes, that should be on the stable version because when we build the product, especially in admin pages, then we always need to do paging on the server-side.


Expand direction

Is there a way to change the expand direction of the fab, so it'll open downwards?

A downward direction is very desirable.

Closing too old issue.


Set default response formatter configs using array syntax

With the exception of JSONP, if a controller wants to change default response formatter options, currently it needs to respecify the formatter class name:
Yii::$app->response->formatters[Response::FORMAT_JSON] = [
    'class' => 'yii\web\JsonResponseFormatter',
    'prettyPrint' => true,
];

With this change, you can just tweak the setting, since the formatter config will already be defined as an array:
Yii::$app->response->formatters[Response::FORMAT_JSON]['prettyPrint'] = true;

Q
A

Is bugfix?
no

New feature?
yes

Breaks BC?
no

Tests pass?
yes

Looks OK to merge. @yiisoft/core-developers do you see any consequences regarding BC breaks?

Merged. Thanks!


missing required inputs for function slack#/functions/send_message

I read workflows.md and got an error with my code like this:
workflow.addStep("slack#/functions/send_message", {
  channel: "C03ABCDEF",
  message: 'hello',
});
> 1: Workflow function `my_workflow` step `0` is missing required inputs for function `slack#/functions/send_message` (wf_function_step_missing_inputs)

I need more information about required inputs for 'slack#/functions/send_message' and found this comment thread.
If 'functions.list' is a private endpoint, how should I handle this error?

Oh sorry, I watched older version.


python310Packages.strawberry-graphql: 0.215.1 -> 0.217.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.strawberry-graphql is: A GraphQL library for Python that leverages type annotations
meta.homepage for python310Packages.strawberry-graphql is: https://strawberry.rocks
meta.changelog for python310Packages.strawberry-graphql is: https://github.com/strawberry-graphql/strawberry/blob/0.217.1/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.217.1 with grep in /nix/store/pakjj015bhkpna97frrigp41h3p8wqzj-python3.10-strawberry-graphql-0.217.1
found 0.217.1 in filename of file in /nix/store/pakjj015bhkpna97frrigp41h3p8wqzj-python3.10-strawberry-graphql-0.217.1

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
python310Packages.strawberry-graphql
python311Packages.strawberry-graphql

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/pakjj015bhkpna97frrigp41h3p8wqzj-python3.10-strawberry-graphql-0.217.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/a6a12e000d496e5cb154f7b5c3b9a2f3acb97898#python310Packages.strawberry-graphql

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/pakjj015bhkpna97frrigp41h3p8wqzj-python3.10-strawberry-graphql-0.217.1
ls -la /nix/store/pakjj015bhkpna97frrigp41h3p8wqzj-python3.10-strawberry-graphql-0.217.1/bin

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

2 packages built:

python310Packages.strawberry-graphql
python311Packages.strawberry-graphql

Maintainer pings
cc @Izorkin for testing.

@ofborg build python310Packages.strawberry-graphql python310Packages.strawberry-graphql.passthru.tests


HTTP checks: add an option to prevent Cabot from following redirections

fix #20

I need some help with tests running in Travis: I have no clue why in Travis, the migration cabotapp.0008_statuscheck_follow_redirects is not called. On my computer it works (I hate to have to write this):
# on my computer
docker-compose -f docker-compose-test.yml run --rm --entrypoint bin/test_with_coverage test -v2

produces the following log. As you can see cabotapp.0008_statuscheck_follow_redirects is applied.
+ output_dir=test-results
+ mkdir -p test-results
+ ./manage.py collectstatic --no-input
Found another file with the destination path 'admin/js/jquery.init.js'. It will be ignored since only the first encountered file is collected. If this is not what you want, make sure every static file has a unique path.

0 static files copied to '/code/cabot/.collectstatic', 404 unmodified.
+ TEMPLATE_DEBUG=True
+ coverage run --source=./cabot/ manage.py test -v2
Creating test database for alias 'default' (':memory:')...
Operations to perform:
  Synchronize unmigrated apps: bootstrapform, compressor, dal, dal_select2, django_filters, jsonify, messages, polymorphic, rest_framework, staticfiles
  Apply all migrations: admin, auth, cabot_alert_email, cabot_alert_hipchat, cabot_alert_slack, cabot_alert_twilio, cabotapp, contenttypes, sessions, sites
Synchronizing apps without migrations:
  Creating tables...
    Running deferred SQL...
Running migrations:
  Applying contenttypes.0001_initial... OK
  Applying auth.0001_initial... OK
  Applying admin.0001_initial... OK
  Applying admin.0002_logentry_remove_auto_add... OK
  Applying contenttypes.0002_remove_content_type_name... OK
  Applying auth.0002_alter_permission_name_max_length... OK
  Applying auth.0003_alter_user_email_max_length... OK
  Applying auth.0004_alter_user_username_opts... OK
  Applying auth.0005_alter_user_last_login_null... OK
  Applying auth.0006_require_contenttypes_0002... OK
  Applying auth.0007_alter_validators_add_error_messages... OK
  Applying auth.0008_alter_user_username_max_length... OK
  Applying cabotapp.0001_initial... OK
  Applying cabot_alert_email.0001_initial... OK
  Applying cabot_alert_hipchat.0001_initial... OK
  Applying cabotapp.0002_auto_20170131_1537... OK
  Applying cabotapp.0003_auto_20170201_1045... OK
  Applying cabot_alert_slack.0001_initial... OK
  Applying cabot_alert_twilio.0001_initial... OK
  Applying cabotapp.0004_auto_20170802_1327... OK
  Applying cabotapp.0005_auto_20170818_1202... OK
  Applying cabotapp.0006_auto_20170821_1000... OK
  Applying cabotapp.0007_statuscheckresult_consecutive_failures... OK
  Applying cabotapp.0008_statuscheck_follow_redirects... OK
  Applying sessions.0001_initial... OK
  Applying sites.0001_initial... OK
  Applying sites.0002_alter_domain_unique... OK
System check identified no issues (0 silenced).
test_global_alert_test (cabot.cabotapp.tests.test_plugin_settings.PluginSettingsTest) ... ok
test_global_settings (cabot.cabotapp.tests.test_plugin_settings.PluginSettingsTest) ... ok

This looks pretty useful, but I guess it's abandoned by now?

I guess so, no new release in years. And Python 2 isn't supported anymore


Add timeout property to RequestInit

fetch has timeout option, but this is not possible to use it in TypeScript because this property is not declared
Please add this property to the typings

Ahoi
I created a PR #2084 to add the parameter as I faced the same warning, even if it compiles.
Cheers

Fixed by now


support for host-bonding

data interface for container traffic needs to be allowed to use host-bonding aka port-channel to uplink switch/switches.

being tracked


Fix e2e tests.

Using 'select' on a combo box does not work reliably.
Instead we click on the widget and use keyboard input.
Bug: http://b/206075027
Test: Ran locally.

I am fine with the version via the keyboard which is done here. My potential alternative is #3036, which should work, but I haven't tested how reliable it is


Sprinkler status in multizone setup

I have integrated this plugin with my Orbit B-Hyve internal WIFI controller. It works great in both ways - starting waterring, stopping it from Iphone Home or native B-Have app is fast and acurate but I have noticed 2 of problems how a sprinkler status is presented in Home app.

Plugin doesn’t block possibility to start more then one zone at a time. You can klick Zone A, then Zone B and it looks like both are working but it’s not true because controller stopping Zone A and starting Zine B (only one Zone can work at a time). You can stop Zone B manually but Zone A - no, it will try to stop endless because from a controller perspective it was already stopped. You need to start Zone A again and stop it or restart plugin.

Worse problem is when you start a program witch is a sequence of Zones starting one by one for a given time. It works but you never know what Zone is actually working. Form a GUI perspective the first one starts for a second and stops and other are waiting but in fact it works as it should. After that, when according to a program, the second starts, it looks like it just has stopped   Only the last couple is presented properly.

End the status for a program itself is not updated after finishing the last Zone in a program.

See if the new version corrects any of this. I had been working on this one for a while, It may correct some or all of this. Let me know

Thanks for update.
First issue seems to work. Sometimes, randomly, when I change a program, both are finishing - maybe it's a race of messages which in some cases it comes to a controller in wrong order. But mostly it works as expected. Some warnings are thrown in logs
Error:
at SetDuration.Characteristic.characteristicWarning (/var/lib/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:3011:105)
at SetDuration.Characteristic.validateUserInput (/var/lib/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2862:14)
at SetDuration.Characteristic.updateValue (/var/lib/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2328:20)
at OrbitPlatform.updateService (/var/lib/homebridge/node_modules/homebridge-orbit-irrigation/orbitupdate.js:255:70)
at /var/lib/homebridge/node_modules/homebridge-orbit-irrigation/orbitapi.js:363:6
at ReconnectingWebSocket._callEventListener (/var/lib/homebridge/node_modules/homebridge-orbit-irrigation/node_modules/reconnecting-websocket/dist/reconnecting-websocket-cjs.js:557:13)
at /var/lib/homebridge/node_modules/homebridge-orbit-irrigation/node_modules/reconnecting-websocket/dist/reconnecting-websocket-cjs.js:176:81
at Array.forEach ()
at WebSocket.ReconnectingWebSocket._handleMessage (/var/lib/homebridge/node_modules/homebridge-orbit-irrigation/node_modules/reconnecting-websocket/dist/reconnecting-websocket-cjs.js:176:38)
at callListener (/var/lib/homebridge/node_modules/homebridge-orbit-irrigation/node_modules/ws/lib/event-target.js:290:14)

As of a program status - nothing has changed. It still marks a zone as stopped when it starts. From GUI perspective of course, in background a program works properly.

For issue 1, what Orbit hardware are you using do you have more than one, curious if it is one I have tested against? Also what firmware version is it running?  The error seems like it is tied to the websocket message not having a correct value or missing the field "total_run_time_sec". It might be the the firmware on the device is old or even newer then what is expected. Debug logs with all the plugin options on should show something like this.
  "firmware_version": "49",
  "name": "Front Porch",
  "type": "sprinkler_timer",
  "mac_address": "446755900742",
  "mesh_id": null,
  "id": "62030b544f0c6f063b8a0b4f",
  "hardware_version": "HT32-0001",
  "is_connected": true

then you start a zone you should see som incoming messages
[9/25/2023, 6:01:47 AM] [B-Hyve-Dev] Back Deck program manual for zone-1 Flowers running
[9/25/2023, 6:01:53 AM] [B-Hyve-Dev] incoming message {
event: 'change_mode',
mode: 'manual',
program: null,
stations: [ { station: 1, run_time: 3 } ],
device_id: '614fbb9e4f0cf51668ea838a',
timestamp: '2023-09-25T12:01:52.000Z'
}
[9/25/2023, 6:01:53 AM] [B-Hyve-Dev] Back Deck mode changed to manual
[9/25/2023, 6:01:53 AM] [B-Hyve-Dev] incoming message {
current_station: 1,
water_event_queue: [],
event: 'watering_in_progress_notification',
status: 'watering_in_progress',
rain_sensor_hold: false,
device_id: '614fbb9e4f0cf51668ea838a',
timestamp: '2023-09-25T12:01:52.000Z',
program: 'manual',
started_watering_station_at: '2023-09-25T12:01:51.000Z',
run_time: 2.98,
total_run_time_sec: 180
}
If you do not see something like these please let me know.

Issue 2 sounds like it maybe working as designed. Homebridge display in not great maybe a homebridge bug, it will show the active zone counting down the others will show as running or complete. In Homekit this displays correctly it will show as stopped, running or waiting depending on where they are in the schedule. If you are using Eve I have not looked at how that app displays.

It may be the reason. I am using this one
https://www.easternirrigation.com/products/8-station-orbit-b-hyve-smart-wi-fi-indoor-timer
It has few years and maybe Orbit does not support it yet. Firmware version is much lower :(
Logs show this
  },
  "firmware_version": "0022",
  "name": "B-hyve Milanówek",
  "type": "sprinkler_timer",
  "mac_address": "446755421047",
  "mesh_id": "5f01fc214f0c1a1979b925dd",
  "id": "5f01fc1f4f0c226b41a9319d",
  "hardware_version": "WT24I-0001",
  "is_connected": true
}

After starting a zone I receive this
[25.09.2023, 15:14:14] [B-Hyve] incoming message {
event: 'change_mode',
mode: 'manual',
program: null,
stations: [ { station: 1, run_time: 30 } ],
device_id: '5f01fc1f4f0c226b41a9319d',
timestamp: '2023-09-25T13:14:14.000Z'
}
[25.09.2023, 15:14:14] [B-Hyve] B-hyve Milanówek mode changed to manual
[25.09.2023, 15:14:14] [B-Hyve] incoming message {
current_station: 1,
water_event_queue: [],
event: 'watering_in_progress_notification',
status: 'watering_in_progress',
rain_sensor_hold: false,
device_id: '5f01fc1f4f0c226b41a9319d',
timestamp: '2023-09-25T13:14:14.000Z',
program: 'manual',
started_watering_station_at: '2023-09-25T13:14:14.000Z',
run_time: 30,
total_run_time_sec: null
}
[25.09.2023, 15:14:14] [homebridge-orbit-irrigation] This plugin generated a warning from the characteristic 'Set Duration': characteristic was supplied illegal value: null! Home App will reject null for Apple defined characteristics. See https://homebridge.io/w/JtMGR for more info.
[25.09.2023, 15:14:14] [homebridge-orbit-irrigation] Error:
at SetDuration.Characteristic.characteristicWarning (/var/lib/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:3011:105)
at SetDuration.Characteristic.validateUserInput (/var/lib/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2862:14)
at SetDuration.Characteristic.updateValue (/var/lib/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2328:20)
at OrbitPlatform.updateService (/var/lib/homebridge/node_modules/homebridge-orbit-irrigation/orbitupdate.js:255:70)
at /var/lib/homebridge/node_modules/homebridge-orbit-irrigation/orbitapi.js:363:6
at ReconnectingWebSocket._callEventListener (/var/lib/homebridge/node_modules/homebridge-orbit-irrigation/node_modules/reconnecting-websocket/dist/reconnecting-websocket-cjs.js:557:13)
at /var/lib/homebridge/node_modules/homebridge-orbit-irrigation/node_modules/reconnecting-websocket/dist/reconnecting-websocket-cjs.js:176:81
at Array.forEach ()
at WebSocket.ReconnectingWebSocket._handleMessage (/var/lib/homebridge/node_modules/homebridge-orbit-irrigation/node_modules/reconnecting-websocket/dist/reconnecting-websocket-cjs.js:176:38)
at callListener (/var/lib/homebridge/node_modules/homebridge-orbit-irrigation/node_modules/ws/lib/event-target.js:290:14)

I have to talk with Orbit, because it looks like they have changed the code name of this product. So my gear is identified as WT24I-0001 but they publish updates for WT24-00001 then update process doesn't see any new version for my timer. I don't see any information about new generation so it's possible their support issue.

V1.2.26 should get rid of those errors. If that field is null I am just using the runtime requested in minutes x 60 so it might be off a few seconds, but better then the error.

Good news! I have asked Orbit support to update my timer remotely, they did it and now I have 0051 version on firmware. Both issues work as expected. If you want me to test it more thoroughly and put some feedback, I am willing to do it, but at a first glance - problems solved!!!

glad it worked out, and it is patched too if anyone else is behind.


Bug in create_region with Maxwell2d / MagnetostaticZ

When creating a region in Maxwell 2D cylindrical, the offset is realized only in R (X) direction and not in z direction. Here, only a "zero" is passed.
In Maxwell 3D and also 2D XY the error does not seem to occur.
Test code:
from pyaedt import Maxwell2d
m2d = Maxwell2d(solution_type="MagnetostaticZ")
magnet = m2d.modeler.primitives.create_rectangle([0, 0, 0], ["10mm", "5mm"], name="Box", matname="ndfe30")
region = m2d.modeler.primitives.create_region(200)

Fixed in #763

Hello @BLeistr it has been added to new version 0.4.24


Docs: reference to old boilerplate code

Bug Report
Docs are still referring to old Boilerplate code.
https://sdk.operatorframework.io/docs/golang/quickstart/#manager
Docs refers:
manager.New(cfg, manager.Options{Namespace: namespace}) which doesn't exists.
Example Ref.
https://github.com/operator-framework/operator-sdk-samples/tree/master/go/kubebuilder/memcached-operator
What did you do?
Operator Migration v0.18 -> 0.19
What did you expect to see?
mgr, err := ctrl.NewManager(ctrl.GetConfigOrDie(), ctrl.Options{
		...
		Namespace: 			"mynamespace"
	})

What did you see instead? Under which circumstances?
manager.New(cfg, manager.Options{Namespace: namespace}) doesn't exists.
Environment

operator-sdk version: 0.19

go version: 0.14

Kubernetes version information: 1.18

Kubernetes cluster kind: minikube

Are you writing your operator in ansible, helm, or go? Go

Possible Solution
Docs Fix
Additional context
Please traverse docs and follow each and every instruction written there Practically.
Only then we can identify Gaps.
It's Problematic to raise issues at every step.

Same for the next Sections
At https://sdk.operatorframework.io/docs/golang/quickstart/#manager
mgr, err := manager.New(cfg, manager.Options{
   NewCache: cache.MultiNamespacedCacheBuilder(namespaces),
})

and
By default the main program will set the manager’s namespace using the value of WATCH_NAMESPACE env defined in deploy/operator.yaml

should be updated as per v0.19 release

This fix needs to be made in master and cherry-picked to the v0.19.x branch.

I'm seeing the same thing (walking through the memcached example tutorial) for config/default/kustomization.yaml referring to a ../crd directory that doesn't exist

@marcstreeter that directory will exist once you run create api then make manifests.

Hi @marcstreeter and @deepak1725,
I did a PR to fix the migration guide and it is https://github.com/operator-framework/operator-sdk/pull/3543 could you please check it and help us with the review. I also will push a PR to update the Memcached Sample with the new layout too :-)

The PR for the samples is https://github.com/operator-framework/operator-sdk-samples/pull/137. We might be able to improve the migration guide and use it as an example too.


Build error with Gradlew

Got this error when run eas build
something went wrong with the gradlew
Running './gradlew :app:bundleRelease' in /home/expo/workingdir/build/android
Downloading https://services.gradle.org/distributions/gradle-7.3.3-all.zip
10
%.
20%.
30%
40%.
50%.
60%.
70%.
80
%
90
%
100
%
Welcome to Gradle 7.3.3!
Here are the highlights of this release:

Easily declare new test suites in Java projects
Support for Java 17
Support for Scala 3
For more details see https://docs.gradle.org/7.3.3/release-notes.html
To honour the JVM settings for this build a single-use Daemon process will be forked. See https://docs.gradle.org/7.3.3/userguide/gradle_daemon.html#sec:disabling_the_daemon.
Daemon will be stopped at the end of the build
Unable to list file systems to check whether they can be watched. Assuming all file systems can be watched. Reason: Could not query file systems: could not open mount file (errno 2: No such file or directory)

Task :react-native-gradle-plugin:compileKotlin
'compileJava' task (current target is 1.8) and 'compileKotlin' task (current target is 11) jvm target compatibility should be set to the same Java version.
w: /home/expo/workingdir/build/node_modules/react-native-gradle-plugin/src/main/kotlin/com/facebook/react/ReactExtension.kt: (10, 37): 'BaseVariant' is deprecated. Deprecated in Java
w: /home/expo/workingdir/build/node_modules/react-native-gradle-plugin/src/main/kotlin/com/facebook/react/ReactExtension.kt: (119, 30): 'BaseVariant' is deprecated. Deprecated in Java
w: /home/expo/workingdir/build/node_modules/react-native-gradle-plugin/src/main/kotlin/com/facebook/react/ReactExtension.kt: (135, 26): 'BaseVariant' is deprecated. Deprecated in Java
w: /home/expo/workingdir/build/node_modules/react-native-gradle-plugin/src/main/kotlin/com/facebook/react/ReactExtension.kt: (155, 32): 'BaseVariant' is deprecated. Deprecated in Java
w: /home/expo/workingdir/build/node_modules/react-native-gradle-plugin/src/main/kotlin/com/facebook/react/ReactExtension.kt: (161, 31): 'BaseVariant' is deprecated. Deprecated in Java
w: /home/expo/workingdir/build/node_modules/react-native-gradle-plugin/src/main/kotlin/com/facebook/react/ReactExtension.kt: (169, 36): 'BaseVariant' is deprecated. Deprecated in Java
w: /home/expo/workingdir/build/node_modules/react-native-gradle-plugin/src/main/kotlin/com/facebook/react/ReactPlugin.kt: (100, 48): 'reactRoot: DirectoryProperty' is deprecated. reactRoot was confusing and has been replace with rootto point to your root project and reactNativeDir to point to the folder of the react-native NPM package
w: /home/expo/workingdir/build/node_modules/react-native-gradle-plugin/src/main/kotlin/com/facebook/react/TaskConfiguration.kt: (10, 37): 'ApplicationVariant' is deprecated. Deprecated in Java
w: /home/expo/workingdir/build/node_modules/react-native-gradle-plugin/src/main/kotlin/com/facebook/react/TaskConfiguration.kt: (11, 37): 'BaseVariant' is deprecated. Deprecated in Java
w: /home/expo/workingdir/build/node_modules/react-native-gradle-plugin/src/main/kotlin/com/facebook/react/TaskConfiguration.kt: (12, 37): 'LibraryVariant' is deprecated. Deprecated in Java
w: /home/expo/workingdir/build/node_modules/react-native-gradle-plugin/src/main/kotlin/com/facebook/react/TaskConfiguration.kt: (28, 51): 'BaseVariant' is deprecated. Deprecated in Java
w: /home/expo/workingdir/build/node_modules/react-native-gradle-plugin/src/main/kotlin/com/facebook/react/TaskConfiguration.kt: (131, 12): 'ApplicationVariant' is deprecated. Deprecated in Java
w: /home/expo/workingdir/build/node_modules/react-native-gradle-plugin/src/main/kotlin/com/facebook/react/TaskConfiguration.kt: (132, 12): 'LibraryVariant' is deprecated. Deprecated in Java
w: /home/expo/workingdir/build/node_modules/react-native-gradle-plugin/src/main/kotlin/com/facebook/react/TaskConfiguration.kt: (252, 14): 'BaseVariant' is deprecated. Deprecated in Java
Task :react-native-gradle-plugin:compileJava
[stderr] Note: /home/expo/workingdir/build/node_modules/react-native-gradle-plugin/src/main/java/com/facebook/react/codegen/generator/SchemaJsonParser.java uses or overrides a deprecated API.
[stderr] Note: Recompile with -Xlint:deprecation for details.
Task :react-native-gradle-plugin:pluginDescriptors
Task :react-native-gradle-plugin:processResources
Task :react-native-gradle-plugin:classes
Task :react-native-gradle-plugin:inspectClassesForKotlinIC
Task :react-native-gradle-plugin:jar
Configure project :app
Unable to detect AGP versions for included builds. All projects in the build should use the same AGP version. Class name for the included build object: org.gradle.composite.internal.DefaultIncludedBuild$IncludedBuildImpl_Decorated.
Configure project :expo-av
Checking the license for package NDK (Side by side) 21.4.7075529 in /home/expo/Android/Sdk/licenses
License for package NDK (Side by side) 21.4.7075529 accepted.
Preparing "Install NDK (Side by side) 21.4.7075529 (revision: 21.4.7075529)".
"Install NDK (Side by side) 21.4.7075529 (revision: 21.4.7075529)" ready.
Installing NDK (Side by side) 21.4.7075529 in /home/expo/Android/Sdk/ndk/21.4.7075529
"Install NDK (Side by side) 21.4.7075529 (revision: 21.4.7075529)" complete.
"Install NDK (Side by side) 21.4.7075529 (revision: 21.4.7075529)" finished.
Checking the license for package CMake <IP_ADDRESS>88404 in /home/expo/Android/Sdk/licenses
License for package CMake <IP_ADDRESS>88404 accepted.
Preparing "Install CMake <IP_ADDRESS>88404 (revision: 3.10.2)".
"Install CMake <IP_ADDRESS>88404 (revision: 3.10.2)" ready.
Installing CMake <IP_ADDRESS>88404 in /home/expo/Android/Sdk/cmake/<IP_ADDRESS>88404
"Install CMake <IP_ADDRESS>88404 (revision: 3.10.2)" complete.
"Install CMake <IP_ADDRESS>88404 (revision: 3.10.2)" finished.
Configure project :expo-eas-client
Warning: The 'kotlin-android-extensions' Gradle plugin is deprecated. Please use this migration guide (https://goo.gle/kotlin-android-extensions-deprecation) to start working with View Binding (https://developer.android.com/topic/libraries/view-binding) and the 'kotlin-parcelize' plugin.
Configure project :expo-structured-headers
Warning: The 'kotlin-android-extensions' Gradle plugin is deprecated. Please use this migration guide (https://goo.gle/kotlin-android-extensions-deprecation) to start working with View Binding (https://developer.android.com/topic/libraries/view-binding) and the 'kotlin-parcelize' plugin.
Configure project :expo-updates-interface
Warning: The 'kotlin-android-extensions' Gradle plugin is deprecated. Please use this migration guide (https://goo.gle/kotlin-android-extensions-deprecation) to start working with View Binding (https://developer.android.com/topic/libraries/view-binding) and the 'kotlin-parcelize' plugin.
Configure project :expo
Using expo modules

expo-app-auth (11.1.1)

expo-application (4.1.0)
expo-av (11.2.3)
expo-camera (12.2.0)
expo-constants (13.1.1)
expo-crypto (10.2.0)
expo-device (4.2.0)
expo-document-picker (10.2.1)
expo-eas-client (0.2.1)
expo-error-recovery (3.1.0)
expo-file-system (14.0.0)
expo-font (10.1.0)
expo-google-sign-in (10.2.0)
expo-image-loader (3.2.0)
expo-image-picker (13.1.1)
expo-json-utils (0.3.0)

expo-keep-awake (10.1.1)

expo-manifests (0.3.0)
expo-modules-core (0.9.2)
expo-notifications (0.15.2)
expo-splash-screen (0.15.1)
expo-structured-headers (2.2.1)
expo-updates (0.13.1)
expo-web-browser (10.2.0)

Configure project :react-native-reanimated
AAR for react-native-reanimated has been found
/home/expo/workingdir/build/node_modules/react-native-reanimated/android/react-native-reanimated-68-jsc.aar
Checking the license for package Android SDK Build-Tools 30.0.2 in /home/expo/Android/Sdk/licenses
License for package Android SDK Build-Tools 30.0.2 accepted.
Preparing "Install Android SDK Build-Tools 30.0.2 (revision: 30.0.2)".
"Install Android SDK Build-Tools 30.0.2 (revision: 30.0.2)" ready.
Installing Android SDK Build-Tools 30.0.2 in /home/expo/Android/Sdk/build-tools/30.0.2
"Install Android SDK Build-Tools 30.0.2 (revision: 30.0.2)" complete.
"Install Android SDK Build-Tools 30.0.2 (revision: 30.0.2)" finished.
Checking the license for package Android SDK Platform 31 in /home/expo/Android/Sdk/licenses
License for package Android SDK Platform 31 accepted.
Preparing "Install Android SDK Platform 31 (revision: 1)".
"Install Android SDK Platform 31 (revision: 1)" ready.
Installing Android SDK Platform 31 in /home/expo/Android/Sdk/platforms/android-31
"Install Android SDK Platform 31 (revision: 1)" complete.
"Install Android SDK Platform 31 (revision: 1)" finished.
Checking the license for package Android SDK Build-Tools 31 in /home/expo/Android/Sdk/licenses
License for package Android SDK Build-Tools 31 accepted.
Preparing "Install Android SDK Build-Tools 31 (revision: 31.0.0)".
"Install Android SDK Build-Tools 31 (revision: 31.0.0)" ready.
Installing Android SDK Build-Tools 31 in /home/expo/Android/Sdk/build-tools/31.0.0
"Install Android SDK Build-Tools 31 (revision: 31.0.0)" complete.
"Install Android SDK Build-Tools 31 (revision: 31.0.0)" finished.
Task :app:generatePackageList
Task :app:preBuild
Task :app:preReleaseBuild
Task :app:bundleReleaseJsAndAssets
[stderr] warn Package expo-modules-core has been ignored because it contains invalid configuration. Reason: "dependency.platforms.ios" must be of type object
warning: the transform cache was reset.
Welcome to Metro!
Fast - Scalable - Integrated
info Writing bundle output to:, /home/expo/workingdir/build/android/app/build/generated/assets/react/release/index.android.bundle
info Writing sourcemap output to:, /home/expo/workingdir/build/android/app/build/generated/sourcemaps/react/release/index.android.bundle.map
info Done writing bundle output
info Done writing sourcemap output
info Copying 62 asset files
info Done copying assets
Task :app:mergeReleaseShaders
Task :app:compileReleaseShaders NO-SOURCE
Task :app:generateReleaseAssets UP-TO-DATE
Task :expo:generateExpoModulesPackageList
Task :expo:preBuild
Task :expo:preReleaseBuild
Task :expo:mergeReleaseShaders
Task :expo:compileReleaseShaders NO-SOURCE
Task :expo:generateReleaseAssets UP-TO-DATE
Task :expo:packageReleaseAssets
Task :expo-app-auth:preBuild UP-TO-DATE
Task :expo-app-auth:preReleaseBuild UP-TO-DATE
Task :expo-app-auth:mergeReleaseShaders
Task :expo-app-auth:compileReleaseShaders
NO-SOURCE
Task :expo-app-auth:generateReleaseAssets UP-TO-DATE
Task :expo-app-auth:packageReleaseAssets
Task :expo-application:preBuild UP-TO-DATE
Task :expo-application:preReleaseBuild UP-TO-DATE
Task :expo-application:mergeReleaseShaders
Task :expo-application:compileReleaseShaders NO-SOURCE
Task :expo-application:generateReleaseAssets UP-TO-DATE
Task :expo-application:packageReleaseAssets
Task :expo-av:preBuild UP-TO-DATE
Task :expo-av:preReleaseBuild UP-TO-DATE
Task :expo-av:mergeReleaseShaders
Task :expo-av:compileReleaseShaders NO-SOURCE
Task :expo-av:generateReleaseAssets UP-TO-DATE
Task :expo-av:packageReleaseAssets
Task :expo-camera:preBuild UP-TO-DATE
Task :expo-camera:preReleaseBuild UP-TO-DATE
Task :expo-camera:mergeReleaseShaders
Task :expo-camera:compileReleaseShaders NO-SOURCE
Task :expo-camera:generateReleaseAssets UP-TO-DATE
Task :expo-camera:packageReleaseAssets
Task :expo-constants:preBuild UP-TO-DATE
Task :expo-constants:preReleaseBuild UP-TO-DATE
Task :expo-constants:mergeReleaseShaders
Task :expo-constants:compileReleaseShaders NO-SOURCE
Task :expo-constants:createReleaseExpoConfig
Execution optimizations have been disabled for task ':expo-constants:createReleaseExpoConfig' to ensure correctness due to the following reasons:

Gradle detected a problem with the following location: '/home/expo/workingdir/build/android'. Reason: Task ':expo-constants:createReleaseExpoConfig' uses this output of task ':app:bundleReleaseJsAndAssets' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.3.3/userguide/validation_problems.html#implicit_dependency for more details about this problem.
Gradle detected a problem with the following location: '/home/expo/workingdir/build/android'. Reason: Task ':expo-constants:createReleaseExpoConfig' uses this output of task ':app:compileReleaseShaders' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.3.3/userguide/validation_problems.html#implicit_dependency for more details about this problem.
Gradle detected a problem with the following location: '/home/expo/workingdir/build/android'. Reason: Task ':expo-constants:createReleaseExpoConfig' uses this output of task ':app:mergeReleaseShaders' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.3.3/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Task :expo-constants:copyReleaseExpoConfig
Task :expo-constants:generateReleaseAssets UP-TO-DATE
Task :expo-constants:packageReleaseAssets
Task :expo-crypto:preBuild UP-TO-DATE
Task :expo-crypto:preReleaseBuild UP-TO-DATE
Task :expo-crypto:mergeReleaseShaders
Task :expo-crypto:compileReleaseShaders NO-SOURCE
Task :expo-crypto:generateReleaseAssets UP-TO-DATE
Task :expo-crypto:packageReleaseAssets
Task :expo-device:preBuild UP-TO-DATE
Task :expo-device:preReleaseBuild UP-TO-DATE
Task :expo-device:mergeReleaseShaders
Task :expo-device:compileReleaseShaders NO-SOURCE
Task :expo-device:generateReleaseAssets UP-TO-DATE
Task :expo-device:packageReleaseAssets
Task :expo-document-picker:preBuild UP-TO-DATE
Task :expo-document-picker:preReleaseBuild UP-TO-DATE
Task :expo-document-picker:mergeReleaseShaders
Task :expo-document-picker:compileReleaseShaders NO-SOURCE
Task :expo-document-picker:generateReleaseAssets UP-TO-DATE
Task :expo-document-picker:packageReleaseAssets
Task :expo-eas-client:preBuild UP-TO-DATE
Task :expo-eas-client:preReleaseBuild UP-TO-DATE
Task :expo-eas-client:mergeReleaseShaders
Task :expo-eas-client:compileReleaseShaders NO-SOURCE
Task :expo-eas-client:generateReleaseAssets UP-TO-DATE
Task :expo-eas-client:packageReleaseAssets
Task :expo-error-recovery:preBuild UP-TO-DATE
Task :expo-error-recovery:preReleaseBuild UP-TO-DATE
Task :expo-error-recovery:mergeReleaseShaders
Task :expo-error-recovery:compileReleaseShaders NO-SOURCE
Task :expo-error-recovery:generateReleaseAssets UP-TO-DATE
Task :expo-error-recovery:packageReleaseAssets
Task :expo-file-system:preBuild UP-TO-DATE
Task :expo-file-system:preReleaseBuild UP-TO-DATE
Task :expo-file-system:mergeReleaseShaders
Task :expo-file-system:compileReleaseShaders NO-SOURCE
Task :expo-file-system:generateReleaseAssets UP-TO-DATE
Task :expo-file-system:packageReleaseAssets
Task :expo-font:preBuild UP-TO-DATE
Task :expo-font:preReleaseBuild UP-TO-DATE
Task :expo-font:mergeReleaseShaders
Task :expo-font:compileReleaseShaders NO-SOURCE
Task :expo-font:generateReleaseAssets UP-TO-DATE
Task :expo-font:packageReleaseAssets
Task :expo-google-sign-in:preBuild UP-TO-DATE
Task :expo-google-sign-in:preReleaseBuild UP-TO-DATE
Task :expo-google-sign-in:mergeReleaseShaders
Task :expo-google-sign-in:compileReleaseShaders NO-SOURCE
Task :expo-google-sign-in:generateReleaseAssets UP-TO-DATE
Task :expo-google-sign-in:packageReleaseAssets
Task :expo-image-loader:preBuild UP-TO-DATE
Task :expo-image-loader:preReleaseBuild UP-TO-DATE
Task :expo-image-loader:mergeReleaseShaders
Task :expo-image-loader:compileReleaseShaders NO-SOURCE
Task :expo-image-loader:generateReleaseAssets UP-TO-DATE
Task :expo-image-loader:packageReleaseAssets
Task :expo-image-picker:preBuild UP-TO-DATE
Task :expo-image-picker:preReleaseBuild UP-TO-DATE
Task :expo-image-picker:mergeReleaseShaders
Task :expo-image-picker:compileReleaseShaders NO-SOURCE
Task :expo-image-picker:generateReleaseAssets UP-TO-DATE
Task :expo-image-picker:packageReleaseAssets
Task :expo-json-utils:preBuild UP-TO-DATE
Task :expo-json-utils:preReleaseBuild UP-TO-DATE
Task :expo-json-utils:mergeReleaseShaders
Task :expo-json-utils:compileReleaseShaders NO-SOURCE
Task :expo-json-utils:generateReleaseAssets UP-TO-DATE
Task :expo-json-utils:packageReleaseAssets
Task :expo-keep-awake:preBuild UP-TO-DATE
Task :expo-keep-awake:preReleaseBuild UP-TO-DATE
Task :expo-keep-awake:mergeReleaseShaders
Task :expo-keep-awake:compileReleaseShaders NO-SOURCE
Task :expo-keep-awake:generateReleaseAssets UP-TO-DATE
Task :expo-keep-awake:packageReleaseAssets
Task :expo-manifests:preBuild UP-TO-DATE
Task :expo-manifests:preReleaseBuild UP-TO-DATE
Task :expo-manifests:mergeReleaseShaders
Task :expo-manifests:compileReleaseShaders NO-SOURCE
Task :expo-manifests:generateReleaseAssets UP-TO-DATE
Task :expo-manifests:packageReleaseAssets
Task :expo-modules-core:preBuild UP-TO-DATE
Task :expo-modules-core:preReleaseBuild UP-TO-DATE
Task :expo-modules-core:mergeReleaseShaders
Task :expo-modules-core:compileReleaseShaders NO-SOURCE
Task :expo-modules-core:generateReleaseAssets UP-TO-DATE
Task :expo-modules-core:packageReleaseAssets
Task :expo-notifications:preBuild UP-TO-DATE
Task :expo-notifications:preReleaseBuild UP-TO-DATE
Task :expo-notifications:mergeReleaseShaders
Task :expo-notifications:compileReleaseShaders NO-SOURCE
Task :expo-notifications:generateReleaseAssets UP-TO-DATE
Task :expo-notifications:packageReleaseAssets
Task :expo-random:preBuild UP-TO-DATE
Task :expo-random:preReleaseBuild UP-TO-DATE
Task :expo-random:mergeReleaseShaders
Task :expo-random:compileReleaseShaders NO-SOURCE
Task :expo-random:generateReleaseAssets UP-TO-DATE
Task :expo-random:packageReleaseAssets
Task :expo-splash-screen:preBuild UP-TO-DATE
Task :expo-splash-screen:preReleaseBuild UP-TO-DATE
Task :expo-splash-screen:mergeReleaseShaders
Task :expo-splash-screen:compileReleaseShaders NO-SOURCE
Task :expo-splash-screen:generateReleaseAssets UP-TO-DATE
Task :expo-splash-screen:packageReleaseAssets
Task :expo-structured-headers:preBuild UP-TO-DATE
Task :expo-structured-headers:preReleaseBuild UP-TO-DATE
Task :expo-structured-headers:mergeReleaseShaders
Task :expo-structured-headers:compileReleaseShaders NO-SOURCE
Task :expo-structured-headers:generateReleaseAssets UP-TO-DATE
Task :expo-structured-headers:packageReleaseAssets
Task :expo-updates:preBuild UP-TO-DATE
Task :expo-updates:preReleaseBuild UP-TO-DATE
Task :expo-updates:mergeReleaseShaders
Task :expo-updates:compileReleaseShaders NO-SOURCE
Task :expo-updates:generateReleaseAssets UP-TO-DATE
Task :expo-updates:packageReleaseAssets
Task :expo-updates-interface:preBuild UP-TO-DATE
Task :expo-updates-interface:preReleaseBuild UP-TO-DATE
Task :expo-updates-interface:mergeReleaseShaders
Task :expo-updates-interface:compileReleaseShaders NO-SOURCE
Task :expo-updates-interface:generateReleaseAssets UP-TO-DATE
Task :expo-updates-interface:packageReleaseAssets
Task :expo-web-browser:preBuild UP-TO-DATE
Task :expo-web-browser:preReleaseBuild UP-TO-DATE
Task :expo-web-browser:mergeReleaseShaders
Task :expo-web-browser:compileReleaseShaders NO-SOURCE
Task :expo-web-browser:generateReleaseAssets UP-TO-DATE
Task :expo-web-browser:packageReleaseAssets
Task :react-native-async-storage_async-storage:preBuild UP-TO-DATE
Task :react-native-async-storage_async-storage:preReleaseBuild UP-TO-DATE
Task :react-native-async-storage_async-storage:mergeReleaseShaders
Task :react-native-async-storage_async-storage:compileReleaseShaders NO-SOURCE
Task :react-native-async-storage_async-storage:generateReleaseAssets UP-TO-DATE
Task :react-native-async-storage_async-storage:packageReleaseAssets
Task :react-native-community_datetimepicker:preBuild UP-TO-DATE
Task :react-native-community_datetimepicker:preReleaseBuild UP-TO-DATE
Task :react-native-community_datetimepicker:mergeReleaseShaders
Task :react-native-community_datetimepicker:compileReleaseShaders NO-SOURCE
Task :react-native-community_datetimepicker:generateReleaseAssets UP-TO-DATE
Task :react-native-community_datetimepicker:packageReleaseAssets
Task :react-native-community_google-signin:preBuild UP-TO-DATE
Task :react-native-community_google-signin:preReleaseBuild UP-TO-DATE
Task :react-native-community_google-signin:mergeReleaseShaders
Task :react-native-community_google-signin:compileReleaseShaders NO-SOURCE
Task :react-native-community_google-signin:generateReleaseAssets UP-TO-DATE
Task :react-native-community_google-signin:packageReleaseAssets
Task :react-native-community_masked-view:preBuild UP-TO-DATE
Task :react-native-community_masked-view:preReleaseBuild UP-TO-DATE
Task :react-native-community_masked-view:mergeReleaseShaders
Task :react-native-community_masked-view:compileReleaseShaders NO-SOURCE
Task :react-native-community_masked-view:generateReleaseAssets UP-TO-DATE
Task :react-native-community_masked-view:packageReleaseAssets
Task :react-native-gesture-handler:preBuild UP-TO-DATE
Task :react-native-gesture-handler:preReleaseBuild UP-TO-DATE
Task :react-native-gesture-handler:mergeReleaseShaders
Task :react-native-gesture-handler:compileReleaseShaders NO-SOURCE
Task :react-native-gesture-handler:generateReleaseAssets UP-TO-DATE
Task :react-native-gesture-handler:packageReleaseAssets
Task :react-native-safe-area-context:preBuild UP-TO-DATE
Task :react-native-safe-area-context:preReleaseBuild UP-TO-DATE
Task :react-native-safe-area-context:mergeReleaseShaders
Task :react-native-safe-area-context:compileReleaseShaders NO-SOURCE
Task :react-native-safe-area-context:generateReleaseAssets UP-TO-DATE
Task :react-native-safe-area-context:packageReleaseAssets
Task :react-native-screens:preBuild UP-TO-DATE
Task :react-native-screens:preReleaseBuild UP-TO-DATE
Task :react-native-screens:mergeReleaseShaders
Task :react-native-screens:compileReleaseShaders NO-SOURCE
Task :react-native-screens:generateReleaseAssets
UP-TO-DATE
Task :react-native-screens:packageReleaseAssets
Task :react-native-vector-icons:preBuild UP-TO-DATE
Task :react-native-vector-icons:preReleaseBuild UP-TO-DATE
Task :react-native-vector-icons:mergeReleaseShaders
Task :react-native-vector-icons:compileReleaseShaders NO-SOURCE
Task :react-native-vector-icons:generateReleaseAssets UP-TO-DATE
Task :react-native-vector-icons:packageReleaseAssets
Task :react-native-webview:preBuild UP-TO-DATE
Task :react-native-webview:preReleaseBuild UP-TO-DATE
Task :react-native-webview:mergeReleaseShaders
Task :react-native-webview:compileReleaseShaders NO-SOURCE
Task :react-native-webview:generateReleaseAssets UP-TO-DATE
Task :react-native-webview:packageReleaseAssets
Task :app:mergeReleaseAssets
WARNING: [Processor] Library '/home/expo/.gradle/caches/modules-2/files-2.1/com.google.android.exoplayer/exoplayer-ui/2.13.3/d05c978bd34ecd5ac1bd312d8c4063faed0aed99/exoplayer-ui-2.13.3.aar' contains references to both AndroidX and old support library. This seems like the library is partially migrated. Jetifier will try to rewrite the library anyway.
Example of androidX reference: 'androidx/core/app/NotificationCompat$Builder'
Example of support library reference: 'android/support/v4/media/session/MediaSessionCompat$Token'
Task :app:copyReleaseBundledJs
Task :expo:packageReleaseRenderscript NO-SOURCE
Task :expo-app-auth:packageReleaseRenderscript NO-SOURCE
Task :expo-application:packageReleaseRenderscript NO-SOURCE
Task :expo-av:packageReleaseRenderscript NO-SOURCE
Task :expo-camera:packageReleaseRenderscript NO-SOURCE
Task :expo-constants:packageReleaseRenderscript NO-SOURCE
Task :expo-crypto:packageReleaseRenderscript NO-SOURCE
Task :expo-device:packageReleaseRenderscript NO-SOURCE
Task :expo-document-picker:packageReleaseRenderscript NO-SOURCE
Task :expo-eas-client:packageReleaseRenderscript NO-SOURCE
Task :expo-error-recovery:packageReleaseRenderscript NO-SOURCE
Task :expo-file-system:packageReleaseRenderscript NO-SOURCE
Task :expo-font:packageReleaseRenderscript NO-SOURCE
Task :expo-google-sign-in:packageReleaseRenderscript NO-SOURCE
Task :expo-image-loader:packageReleaseRenderscript NO-SOURCE
Task :expo-image-picker:packageReleaseRenderscript NO-SOURCE
Task :expo-json-utils:packageReleaseRenderscript NO-SOURCE
Task :expo-keep-awake:packageReleaseRenderscript NO-SOURCE
Task :expo-manifests:packageReleaseRenderscript NO-SOURCE
Task :expo-modules-core:packageReleaseRenderscript NO-SOURCE
Task :expo-notifications:packageReleaseRenderscript NO-SOURCE
Task :expo-random:packageReleaseRenderscript NO-SOURCE
Task :expo-splash-screen:packageReleaseRenderscript NO-SOURCE
Task :expo-structured-headers:packageReleaseRenderscript NO-SOURCE
Task :expo-updates:packageReleaseRenderscript NO-SOURCE
Task :expo-web-browser:packageReleaseRenderscript NO-SOURCE
Task :react-native-async-storage_async-storage:packageReleaseRenderscript NO-SOURCE
Task :react-native-community_datetimepicker:packageReleaseRenderscript NO-SOURCE
Task :react-native-community_google-signin:packageReleaseRenderscript NO-SOURCE
Task :react-native-community_masked-view:packageReleaseRenderscript NO-SOURCE
Task :react-native-gesture-handler:packageReleaseRenderscript NO-SOURCE
Task :react-native-safe-area-context:packageReleaseRenderscript NO-SOURCE
Task :react-native-screens:packageReleaseRenderscript NO-SOURCE
Task :react-native-vector-icons:packageReleaseRenderscript NO-SOURCE
Task :react-native-webview:packageReleaseRenderscript NO-SOURCE
Task :app:compileReleaseRenderscript NO-SOURCE
Task :app:generateReleaseResValues
Task :app:generateReleaseResources
Task :app:processReleaseGoogleServices
Parsing json file: /home/expo/workingdir/build/android/app/google-services.json
Task :expo:compileReleaseRenderscript NO-SOURCE
Task :expo:generateReleaseResValues
Task :expo:generateReleaseResources
Task :expo:packageReleaseResources
Task :expo-app-auth:compileReleaseRenderscript NO-SOURCE
Task :expo-app-auth:generateReleaseResValues
Task :expo-app-auth:generateReleaseResources
Task :expo-app-auth:packageReleaseResources
Task :expo-application:compileReleaseRenderscript NO-SOURCE
Task :expo-application:generateReleaseResValues
Task :expo-application:generateReleaseResources
Task :expo-application:packageReleaseResources
Task :expo-av:compileReleaseRenderscript NO-SOURCE
Task :expo-av:generateReleaseResValues
Task :expo-av:generateReleaseResources
Task :expo-av:packageReleaseResources
Task :expo-camera:compileReleaseRenderscript NO-SOURCE
Task :expo-camera:generateReleaseResValues
Task :expo-camera:generateReleaseResources
Task :expo-camera:packageReleaseResources
Task :expo-constants:compileReleaseRenderscript NO-SOURCE
Task :expo-constants:generateReleaseResValues
Task :expo-constants:generateReleaseResources
Task :expo-constants:packageReleaseResources
Task :expo-crypto:compileReleaseRenderscript NO-SOURCE
Task :expo-crypto:generateReleaseResValues
Task :expo-crypto:generateReleaseResources
Task :expo-crypto:packageReleaseResources
Task :expo-device:compileReleaseRenderscript NO-SOURCE
Task :expo-device:generateReleaseResValues
Task :expo-device:generateReleaseResources
Task :expo-device:packageReleaseResources
Task :expo-document-picker:compileReleaseRenderscript NO-SOURCE
Task :expo-document-picker:generateReleaseResValues
Task :expo-document-picker:generateReleaseResources
Task :expo-document-picker:packageReleaseResources
Task :expo-eas-client:compileReleaseRenderscript NO-SOURCE
Task :expo-eas-client:generateReleaseResValues
Task :expo-eas-client:generateReleaseResources
Task :expo-eas-client:packageReleaseResources
Task :expo-error-recovery:compileReleaseRenderscript NO-SOURCE
Task :expo-error-recovery:generateReleaseResValues
Task :expo-error-recovery:generateReleaseResources
Task :expo-error-recovery:packageReleaseResources
Task :expo-file-system:compileReleaseRenderscript NO-SOURCE
Task :expo-file-system:generateReleaseResValues
Task :expo-file-system:generateReleaseResources
Task :expo-file-system:packageReleaseResources
Task :expo-font:compileReleaseRenderscript NO-SOURCE
Task :expo-font:generateReleaseResValues
Task :expo-font:generateReleaseResources
Task :expo-font:packageReleaseResources
Task :expo-google-sign-in:compileReleaseRenderscript NO-SOURCE
Task :expo-google-sign-in:generateReleaseResValues
Task :expo-google-sign-in:generateReleaseResources
Task :expo-google-sign-in:packageReleaseResources
Task :expo-image-loader:compileReleaseRenderscript NO-SOURCE
Task :expo-image-loader:generateReleaseResValues
Task :expo-image-loader:generateReleaseResources
Task :expo-image-loader:packageReleaseResources
Task :expo-image-picker:compileReleaseRenderscript NO-SOURCE
Task :expo-image-picker:generateReleaseResValues
Task :expo-image-picker:generateReleaseResources
Task :expo-image-picker:packageReleaseResources
Task :expo-json-utils:compileReleaseRenderscript NO-SOURCE
Task :expo-json-utils:generateReleaseResValues
Task :expo-json-utils:generateReleaseResources
Task :expo-json-utils:packageReleaseResources
Task :expo-keep-awake:compileReleaseRenderscript NO-SOURCE
Task :expo-keep-awake:generateReleaseResValues
Task :expo-keep-awake:generateReleaseResources
Task :expo-keep-awake:packageReleaseResources
Task :expo-manifests:compileReleaseRenderscript NO-SOURCE
Task :expo-manifests:generateReleaseResValues
Task :expo-manifests:generateReleaseResources
Task :expo-manifests:packageReleaseResources
Task :expo-modules-core:compileReleaseRenderscript NO-SOURCE
Task :expo-modules-core:generateReleaseResValues
Task :expo-modules-core:generateReleaseResources
Task :expo-modules-core:packageReleaseResources
Task :expo-notifications:compileReleaseRenderscript NO-SOURCE
Task :expo-notifications:generateReleaseResValues
Task :expo-notifications:generateReleaseResources
Task :expo-notifications:packageReleaseResources
Task :expo-random:compileReleaseRenderscript NO-SOURCE
Task :expo-random:generateReleaseResValues
Task :expo-random:generateReleaseResources
Task :expo-random:packageReleaseResources
Task :expo-splash-screen:compileReleaseRenderscript NO-SOURCE
Task :expo-splash-screen:generateReleaseResValues
Task :expo-splash-screen:generateReleaseResources
Task :expo-splash-screen:packageReleaseResources
Task :expo-structured-headers:compileReleaseRenderscript NO-SOURCE
Task :expo-structured-headers:generateReleaseResValues
Task :expo-structured-headers:generateReleaseResources
Task :expo-structured-headers:packageReleaseResources
Task :expo-updates-interface:packageReleaseRenderscript NO-SOURCE
Task :expo-updates:compileReleaseRenderscript NO-SOURCE
Task :expo-updates:generateReleaseResValues
Task :expo-updates:generateReleaseResources
Task :expo-updates:packageReleaseResources
Task :expo-updates-interface:compileReleaseRenderscript NO-SOURCE
Task :expo-updates-interface:generateReleaseResValues
Task :expo-updates-interface:generateReleaseResources
Task :expo-updates-interface:packageReleaseResources
Task :expo-web-browser:compileReleaseRenderscript NO-SOURCE
Task :expo-web-browser:generateReleaseResValues
Task :expo-web-browser:generateReleaseResources
Task :expo-web-browser:packageReleaseResources
Task :react-native-async-storage_async-storage:compileReleaseRenderscript NO-SOURCE
Task :react-native-async-storage_async-storage:generateReleaseResValues
Task :react-native-async-storage_async-storage:generateReleaseResources
Task :react-native-async-storage_async-storage:packageReleaseResources
Task :react-native-community_datetimepicker:compileReleaseRenderscript NO-SOURCE
Task :react-native-community_datetimepicker:generateReleaseResValues
Task :react-native-community_datetimepicker:generateReleaseResources
Task :react-native-community_datetimepicker:packageReleaseResources
Task :react-native-community_google-signin:compileReleaseRenderscript NO-SOURCE
Task :react-native-community_google-signin:generateReleaseResValues
Task :react-native-community_google-signin:generateReleaseResources
Task :react-native-community_google-signin:packageReleaseResources
Task :react-native-community_masked-view:compileReleaseRenderscript NO-SOURCE
Task :react-native-community_masked-view:generateReleaseResValues
Task :react-native-community_masked-view:generateReleaseResources
Task :react-native-community_masked-view:packageReleaseResources
Task :react-native-gesture-handler:compileReleaseRenderscript NO-SOURCE
Task :react-native-gesture-handler:generateReleaseResValues
Task :react-native-gesture-handler:generateReleaseResources
Task :react-native-gesture-handler:packageReleaseResources
Task :react-native-safe-area-context:compileReleaseRenderscript NO-SOURCE
Task :react-native-safe-area-context:generateReleaseResValues
Task :react-native-safe-area-context:generateReleaseResources
Task :react-native-safe-area-context:packageReleaseResources
Task :react-native-screens:compileReleaseRenderscript NO-SOURCE
Task :react-native-screens:generateReleaseResValues
Task :react-native-screens:generateReleaseResources
Task :react-native-screens:packageReleaseResources
Task :react-native-vector-icons:compileReleaseRenderscript NO-SOURCE
Task :react-native-vector-icons:generateReleaseResValues
Task :react-native-vector-icons:generateReleaseResources
Task :react-native-vector-icons:packageReleaseResources
Task :react-native-webview:compileReleaseRenderscript NO-SOURCE
Task :react-native-webview:generateReleaseResValues
Task :react-native-webview:generateReleaseResources
Task :react-native-webview:packageReleaseResources
Task :app:mergeReleaseResources FAILED
Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See https://docs.gradle.org/7.3.3/userguide/command_line_interface.html#sec:command_line_warnings
Execution optimizations have been disabled for 1 invalid unit(s) of work during this build to ensure correctness.
Please consult deprecation warnings for more details.
161 actionable tasks: 161 executed
Unable to list file systems to check whether they can be watched. The whole state of the virtual file system has been discarded. Reason: Could not query file systems: could not open mount file (errno 2: No such file or directory)
[stderr] FAILURE: Build failed with an exception.
[stderr] * What went wrong:
[stderr] Execution failed for task ':app:mergeReleaseResources'.
[stderr] > A failure occurred while executing com.android.build.gradle.internal.res.Aapt2CompileRunnable
[stderr]    > Android resource compilation failed
[stderr]      ERROR:/home/expo/workingdir/build/android/app/build/generated/res/react/release/drawable-mdpi/assets_images_illustrations_no_image.png: AAPT: error: failed to read PNG signature: file does not start with PNG signature.
[stderr]
[stderr]      ERROR:/home/expo/workingdir/build/android/app/build/generated/res/react/release/drawable-mdpi/assets_images_illustrations_no_image.png: AAPT: error: file failed to compile.
[stderr]
[stderr] * Try:
[stderr] > Run with --stacktrace option to get the stack trace.
[stderr] > Run with --info or --debug option to get more log output.
[stderr] > Run with --scan to get full insights.
[stderr] * Get more help at https://help.gradle.org
[stderr] BUILD FAILED in 6m 44s
Error: Gradle build failed with unknown error. Please see logs for the "Run gradlew" phase

failed to read PNG signature: file does not start with PNG signature.
you have a file there that is either malformed or it's jpeg with a png name

https://docs.expo.dev/versions/v45.0.0/config/app/#image

Local path or remote URL to an image to fill the background of the loading screen. Image size and aspect ratio are up to you. Must be a .png.

Hello, am having the issue with the build "Run gradlew"

How can I solve it pls

I am also seeing the same error running npx eas build --platform android --profile $EAS_PROFILE.

I am also seeing similar problem "Run gradlew", when running npx cross-env EAS_NO_VCS=1 eas build
I upgraded to last JDK but this don't seem to be doing anything.


FastAPI with run.py

the repository actually runs the deep learning models so this has to be where the api is made. it also needs a http endpoint to tell it to run a report. we are not having the cron defined here

the cron is going to be here and the API