Accessing   open data

Accessing   open data
Intermediate
Cloud   Two, Data and the Cloud

open-data

Put this on hold for now. Lets focus on Nectar services

shelving


Heartbeat support

Hi,,
Heartbeat support would be a nice feature to have in kombu and later in celery, I can't find the way to do it right now, and I can't find it in the code, so I imagine is not supported already, I'm getting a lot of blocked queues because of network outages that disconnects in a non nicely way my clients from rabbitmq. I think that with this feature those problems will go away.
Bye.

I'm working on heartbeat support (and also publisher confirms) in https://github.com/ask/kamqp

any updates on this?


Binary release

Could this package be released in the main distros as kinetic and melodic?
This would go along with https://github.com/pal-robotics/pal_statistics/issues/4

I was taking a look at the dependencies and there is some mismatch with the deps in rosdistro:

libgoogle-perftools-dev -> deployed with gperftools
libmicrohttpd-dev -> deployed with libmicrohttpd

I would just swap those deps to easy the process


Bug: React Bootstrap button as link

Is there a better solution for this
I currently just  put Link as any
<Button as={Link as any} to="/pets" variant="primary">
          Adopt
</Button>

I found a package that helps with that, react-router-bootstrap.
It allows you to wrap their component around the react-bootstrap Button component to create an anchor link, opposed to wrapping the Button component in react-routers Link which leads to invalid HTML.

I found a package that helps with that, react-router-bootstrap.
It allows you to wrap their component around the react-bootstrap Button component to create an anchor link, opposed to wrapping the Button component in react-routers Link which leads to invalid HTML.

Alright wanna try it out?

I found a package that helps with that, react-router-bootstrap.
It allows you to wrap their component around the react-bootstrap Button component to create an anchor link, opposed to wrapping the Button component in react-routers Link which leads to invalid HTML.

Alright wanna try it out?

Sure!


Backported fixes to client migration feature

See HEAD branch for details

@Bischoff  ok seems good.  how is the result.html?


Maybe try css modules

https://css-tricks.com/css-modules-part-1-need/

@KrystianOg
Does it count? Commit: Extracted styles


Frequent Webhook panics

This happens randomly, both running locally or via Docker image.
Seems to happen more often if i don't interact with UI for a while, and come back.
goroutine 12 [running]:
github.com/casdoor/casdoor/object.getWebhooksByOrganization({0xc0004f03f0, 0x8})
	/Users/adam/go/src/casbin/casdoor/object/webhook.go:80 +0x118
github.com/casdoor/casdoor/object.SendWebhooks(0xc0001889a0)
	/Users/adam/go/src/casbin/casdoor/object/record.go:146 +0x2d
github.com/casdoor/casdoor/object.AddRecord(0xc0001889a0)
	/Users/adam/go/src/casbin/casdoor/object/record.go:89 +0x95
created by github.com/casdoor/casdoor/routers.RecordMessage
	/Users/adam/go/src/casbin/casdoor/routers/record.go:68 +0x118

Please let me know what other info i can provide to help.

more error detail?


Dummy issue - testing stale issue bot

The bot should close this issue in 30 days

@StellaHuang95 Looks like the bot worked! :)
Can you please create a work item to get this in place for the pylance and debugpy repos as well? This might be a good way to cut down on stale tickets.

@AdamYoblick Sure I can add the same thing to the other repos!


Because ee depends on libleptonica-dev (^1.80.0) which doesn't match any versions, version solving failed.

When I execute the command "poetry install", the terminal throws this error "Because ee depends on libleptonica-dev (^1.80.0) which doesn't match any versions, version solving failed". What should I do? My python version is 3.11.4 and the CUDA Version is 12.4.

@Furjesk Thanks for reporting this.
I have updated the pyproject.toml and README.md. Try to pull the latest changes from main and try again. Let me know if the issue persists.


LUCENE-10001: Make CollectionTerminatedException handling in MultiCollector configurable

Description
There could be use-cases where a user wants to terminate all wrapped collectors in a MultiCollector when one terminates. Today, other collectors continue collecting. For example, a user collecting matching docs while also collecting into a FacetsCollector may want to terminate both collectors when the "main" matching docs collector terminates.
#11040
Solution
Added the ability to configure the behavior through an enum specified to wrap
Tests
Updated the existing tests to check behavior under both options.
Checklist
Please review the following and check all that apply:

[x] I have reviewed the guidelines for How to Contribute and my code conforms to the standards described there to the best of my ability.
[x] I have created a Jira issue and added the issue ID to my pull request title.
[x] I have given Lucene maintainers access to contribute to my PR branch. (optional but recommended)
[x] I have developed this patch against the main branch.
[x] I have run ./gradlew check.
[x] I have added tests for my changes.

@gautamworah96 thanks for the feedback! Adrien and I have been having some conversation around whether-or-not this change makes sense over in the Jira issue. As a result, I'm going to try out a little bit of a different approach next, but I appreciate your comments here and will work them in as possible in my next revision. Thanks again!

I've put this in "Draft" state for now after a suggestion over on the Jira issue to approach this differently. I'll update here (and take out of "Draft") once I've had a chance to explore a different approach. Thanks everyone for the comments so far!

@gsmiller what should we do with this PR?  Are you working on the alternative (wrapping?) approach?  Should we close this PR and later open that approach?  Or leave this one open...?  Thanks.

@mikemccand I'm going to close this out. I haven't worked on this in a while now. Thanks for the ping!


Error message 'can't convert array to string' when using content.order.by with a taxonomy

Previously (and currently when testing locally) the live environment of our site would allow us to order the collection by the taxonomy. This meant that we could group together particular tags - each article would only have one tag. I appreciate that this could then create an array, and therefore the error message could appear, but this never used to happen (is this by pure happenstance?) and still doesn't happen on my local environment. In fact, Flavio has also tested the site, and it doesn't occur for him locally either.
To prevent the error showing on the front end for now, I have set it to order.by:default. However, I can break it again to show you if requested.
Steps taken to isolate the error so far include:

Upgraded PHP version from 5.5.9 to 7.0
Downgraded Admin plugin to 1.2.4 from latest
Downgraded Grav to 1.1.9 from latest
Used live backup to test site locally on Flavio and my local environments - (can't reproduce)

For reference the stack trace I was getting is as follows:
Twig_Error_Runtime thrown with message "An exception has been thrown during the rendering of a template ("Array to string conversion")."

Stacktrace:
#37 Twig_Error_Runtime in /home/grav/www/html/user/plugins/admin/themes/grav/templates/pages.html.twig:57
#36 Whoops\Exception\ErrorException in /home/grav/www/html/system/src/Grav/Common/Page/Pages.php:1115
#35 asort in /home/grav/www/html/system/src/Grav/Common/Page/Pages.php:1115
#34 Grav\Common\Page\Pages:buildSort in /home/grav/www/html/system/src/Grav/Common/Page/Pages.php:248
#33 Grav\Common\Page\Pages:sortCollection in /home/grav/www/html/system/src/Grav/Common/Page/Collection.php:180
#32 Grav\Common\Page\Collection:order in /home/grav/www/html/vendor/twig/twig/lib/Twig/Template.php:674
#31 call_user_func_array in /home/grav/www/html/vendor/twig/twig/lib/Twig/Template.php:674
#30 Twig_Template:getAttribute in /home/grav/www/html/cache/twig/e9/e9da0732dac06c3f348e28fa732f9839c20463d62583743955142588e1571b27.php:734
#29 __TwigTemplate_5e64f782dd484d82e6ae8fa68439774724f0569b40b6c918c82515eda0cbde4c:getloop in /home/grav/www/html/vendor/twig/twig/lib/Twig/Template.php:674
#28 call_user_func_array in /home/grav/www/html/vendor/twig/twig/lib/Twig/Template.php:674
#27 Twig_Template:getAttribute in /home/grav/www/html/cache/twig/e9/e9da0732dac06c3f348e28fa732f9839c20463d62583743955142588e1571b27.php:865
#26 __TwigTemplate_5e64f782dd484d82e6ae8fa68439774724f0569b40b6c918c82515eda0cbde4c:getloop in /home/grav/www/html/vendor/twig/twig/lib/Twig/Template.php:674
#25 call_user_func_array in /home/grav/www/html/vendor/twig/twig/lib/Twig/Template.php:674
#24 Twig_Template:getAttribute in /home/grav/www/html/cache/twig/e9/e9da0732dac06c3f348e28fa732f9839c20463d62583743955142588e1571b27.php:550
#23 __TwigTemplate_5e64f782dd484d82e6ae8fa68439774724f0569b40b6c918c82515eda0cbde4c:block_content in /home/grav/www/html/vendor/twig/twig/lib/Twig/Template.php:215
#22 Twig_Template:displayBlock in /home/grav/www/html/cache/twig/08/08a879ed4d6c7b83a20deb10f3db40646e3d31fbec80fdb5801cf89a16f83782.php:205
#21 __TwigTemplate_376c17ff3c287d3171ec0d56df0015b11bbe2c5a571377dc3eb48bba3de4a5e8:block_page in /home/grav/www/html/vendor/twig/twig/lib/Twig/Template.php:215
#20 Twig_Template:displayBlock in /home/grav/www/html/cache/twig/08/08a879ed4d6c7b83a20deb10f3db40646e3d31fbec80fdb5801cf89a16f83782.php:158
#19 __TwigTemplate_376c17ff3c287d3171ec0d56df0015b11bbe2c5a571377dc3eb48bba3de4a5e8:block_body in /home/grav/www/html/vendor/twig/twig/lib/Twig/Template.php:215
#18 Twig_Template:displayBlock in /home/grav/www/html/cache/twig/08/08a879ed4d6c7b83a20deb10f3db40646e3d31fbec80fdb5801cf89a16f83782.php:45
#17 __TwigTemplate_376c17ff3c287d3171ec0d56df0015b11bbe2c5a571377dc3eb48bba3de4a5e8:doDisplay in /home/grav/www/html/vendor/twig/twig/lib/Twig/Template.php:432
#16 Twig_Template:displayWithErrorHandling in /home/grav/www/html/vendor/twig/twig/lib/Twig/Template.php:403
#15 Twig_Template:display in /home/grav/www/html/cache/twig/e9/e9da0732dac06c3f348e28fa732f9839c20463d62583743955142588e1571b27.php:73
#14 __TwigTemplate_5e64f782dd484d82e6ae8fa68439774724f0569b40b6c918c82515eda0cbde4c:doDisplay in /home/grav/www/html/vendor/twig/twig/lib/Twig/Template.php:432
#13 Twig_Template:displayWithErrorHandling in /home/grav/www/html/vendor/twig/twig/lib/Twig/Template.php:403
#12 Twig_Template:display in /home/grav/www/html/vendor/twig/twig/lib/Twig/Template.php:411
#11 Twig_Template:render in /home/grav/www/html/vendor/twig/twig/lib/Twig/Environment.php:362
#10 Twig_Environment:render in /home/grav/www/html/system/src/Grav/Common/Twig/Twig.php:348
#9 Grav\Common\Twig\Twig:processSite in /home/grav/www/html/system/src/Grav/Common/Service/OutputServiceProvider.php:18
#8 Grav\Common\Service\OutputServiceProvider:Grav\Common\Service\{closure} in /home/grav/www/html/vendor/pimple/pimple/src/Pimple/Container.php:113
#7 Pimple\Container

cc/ @flaviocopes

I have tested this, we both cannot replicate locally the problem, with the same user/ folder that causes the problem on the server.

Can you provide the exact code you are using so i can take a look?

Sure, so it errors in two places. The admin areas when you try and accessing the 'pages' section, and the front end 'case-studies' page errors.
Within the case-studies frontmatter we have:
content:
    items<EMAIL_ADDRESS>    order:
        by: header.taxonomy.category
        dir: asc

You can see the frontend error message here: https://www.draytonpartners.com/case-studies
Attached is a screenshot of the error message in the admin area and the stack trace was pasted into the original comment. If you need more specific code, let me know.
Cheers!

Also the blueprint is as follows:
fields:
  header.taxonomy:
       type: taxonomy
       label: PLUGIN_ADMIN.TAXONOMY
       validate:
           type: array

Which, I believe (it's been a while since I've touched this code), when saved in the frontmatter of the case-studies child pages becomes:
taxonomy:
    category:
        - Retail

Ok, i was just looking at this order stuff on collection pages today.  It currently only supports one level under 'header... let me see if I can address it.

Fixed in develop


Arrays inside structures not being read when reading the whole variable

Hi Christoph,
When reading a variable declared as a structure with arrays inside, the array part is not fully read. Only the first element of the array is returned.
For example, when I try to read a variable of type MC_ENDLESS_STRUCTURE (from library ACP10_MC) I only get the values of the first elements of the array:
OrderedDict([('.EndlessPositionData.MTPhase', -1022448), ('.EndlessPositionData.MTDiffInteger', 0), ('.EndlessPositionData.MTDiffFract', 0), ('.EndlessPositionData.RefOffset', -1800000), ('.EndlessPositionData.Checksum',<PHONE_NUMBER>)])
This is the definition of MC_ENDLESS_POSITION:
MC_ENDLESS_POSITION : 	STRUCT  (*structure to save the endless position*)
	EndlessPositionData : ARRAY[0..1] OF MC_ENDLESS_POSITION_DATA;
END_STRUCT;
MC_ENDLESS_POSITION_DATA : 	STRUCT  (*structure to save the endless position*)
	MTPhase : DINT;
	MTDiffInteger : DINT;
	MTDiffFract : DINT;
	RefOffset : DINT;
	Checksum : UDINT;
END_STRUCT;
If I try to read directly the array inside the strcture, then it works fine (i.e. gEndlessPosition.EndlessPositionData):
(OrderedDict([('.MTPhase', -1022448), ('.MTDiffInteger', 0), ('.MTDiffFract', 0), ('.RefOffset', -1800000), ('.Checksum',<PHONE_NUMBER>)]), OrderedDict([('.MTPhase', -1022448), ('.MTDiffInteger', 0), ('.MTDiffFract', 0), ('.RefOffset', -1800000), ('.Checksum',<PHONE_NUMBER>)]))
Would it be possible to get the values of all the elements of the array when passing just the name of the variable?
Thank you!

Hi Jordi,
thank you for the feedback.
yep, can confirm that.
As any number of complex structures can be thought of here, it will probably take a little longer to solve this issue.

Hi @jmauriKB,
can you check if this works for you, please:
7f00c6ea96ac12083ea24585fe34f7c91385fe4b

Looks good!
Thank you so much @hilch !


IGNITE-5534 added method to activate cluster

https://issues.apache.org/jira/browse/IGNITE-5534 is closed, closing the PR


Uncaught Error: User did not grant permission when trying to execute python script

I'm trying to write a GUI for a python script for undervolting my laptop on linux, however when trying to run the command such as:
  readVoltage = () => {
    sudo.exec(
      'python /home/luke/workspace/undervolt-gui/undervolt/undervolt.py -r',
      options,
      function(error, stdout, stderr) {
        if (error) throw error;
        console.log('stdout: ' + stdout);
      }
    );
  };

I'm getting Uncaught Error: User did not grant permission when trying to execute python script. Am I doing things wrong?

Thanks @lukechadwick,
Can you try running sudo-prompt/test.js to test that sudo-prompt is working in your environment?

@lukechadwick , I am closing for lack of further information.

As opposed to opening a new ticket, I am running into the same thing with an electron application.
I'm on Linux trying to execute an elevated shell script from my app.  I am getting the following error...
stderr: pkexec must be setuid root
VM103:55 spawn error: Error: User did not grant permission.

Running the test.js returns permission denied.
Is there something that I'm missing in my setup that is preventing this from working as expected?

Your system pkexec binary either does not have the setuid bit set, or is not owned by the root user.
To find the path to your pkexec binary run: which pkexec
Then fix the permissions of the binary to have the setuid bit set, and make sure it is owned by the root user.

pkexec is what sudo-prompt uses on Linux systems to elevate privileges. This requires that pkexec itself has the power to do so.


Private DNS zone group deployed by DeployIfNotExists policy gets destroyed

I am running into a problem where Terraform tries to change the private_dns_zone_group, which is deployed by a DeployIfNotExists policy. This policy automatically creates a DNS entry for a private endpoint (source). Normally, I would use ignore_changes, but this only works for resources that are first deployed by Terraform, and then all future changes outside Terraform are ignored.
How can I deploy a private endpoint without a private_dns_zone_group, preventing any future deployments from deleting the private_dns_zone_group which is deployed by an Azure policy?
Within the Cloud Adoption Framework, having a centralized DNS, which is automatically updated by Azure policies is highly favorable. But it seems like Terraform conflicts with these specific policies.
resource "azurerm_private_endpoint" "private_endpoint" {
  name                = var.private_endpoint_name
  location            = var.location
  resource_group_name = var.resource_group_name
  subnet_id           = var.private_subnet_id

  private_service_connection {
    name                           = var.private_service_connection_name
    is_manual_connection           = false
    private_connection_resource_id = azurerm_app_service.app_service.id
    subresource_names              = ["sites"]
  }

  # This cannot be included, otherwise the DeployIfNotExists policy will not run
  # private_dns_zone_group {
  #   name = "deployedByPolicy"
  #   private_dns_zone_ids = []
  # }

  lifecycle {
    ignore_changes = [
      private_dns_zone_group
    ]
  }
}

+1

I also had this issue and tried different things. But none of them can be called more then a bad workaround.
IMO the best place to fix this would be the azurerm provider.
I wrote a feature request in which i also outlined my workarounds.
If this is still an issue for you, i invite you to upvote my feature request ;)
https://github.com/hashicorp/terraform-provider-azurerm/issues/24681


Update TryGetMonitor docs to clarify return

Clarify that TryGetMonitor returns null rather than throwing or returning a non-S_OK value.

@zhuman : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@stevewhims : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Custom domain name

This PR introduce a new feature that allows dock-cli to updates the /etc/hosts file of host when running projects. That way, any project of any container can have fixed DNS names, a useful feature for projects integrating OAuth for instance.
The configuration of domain name come from the composer.json file of the project, that should be next to the docker-compose.yml file of the project. Each component can have many associated domain name, as you can see in this sample composer.json file:
{
  "extra": {
    "dock-cli": {
      "extra-hostname": {
        "app": ["my-custom.dns.name"]
      }
    }
  }
}

Looks good!


Compatibility with LTS (Laravel 5.1)

Does this package actually use any Laravel 5.2 features?  I have just installed it in my Laravel LTS project by aliasing the version ("laravel/framework": "5.1.36 as 5.2.21") and in my limited testing it appears to be working.  I would like to suggest maintaining LTS compatibility moving forward!

I would very much like the package to be L5.1 compatible. However, I you run the unit tests on L5.1 you'd see that the it_can_replace_the_placeholders-test fails. I'm thinking that's because the array_get function works slightly different in Laravel 5.1
I'd would accept a PR that makes the tests pass in L5.1.

Thanks to @JeroenNoten version 1.0.3 of the package is compatible with Laravel 5.1


Incomplete knmi ts breaks get_recharge function

Solution provided by Davíd.
Missing values are filled with nearby time series by setting fill_missing_obs to True

I updated the fill_missing_obs functionality in hydropandas this week. It does not check if de Bilt has measurements anymore, if this is not needed (when no data needs to be filled). So we maybe need to increase the hydropandas version in the next nlmod release (if the new hydropandas has been released).

Also, evaporation-measurements were not filled in Hydropandas. This has been fixed in a PR last week: https://github.com/ArtesiaWater/hydropandas/pull/157

I've updated hydropandas and pinned the version in the requirements of nlmod. I would like to merge this PR asap so we can transfer nlmod to a new organisation without any open PR's


How to use

Hi,
a few lines in readme on how to use this would be nice.
Would also like to know how does this play with the newly isolated prop-types package.

You use it the same way you use any propTypes, including React.PropTypes. If you'd like to put up a PR with some text we can discuss that there.
The existence of the prop-types package doesn't change anything; the only interaction is when you pass function values around like PropTypes.number; where you got that value isn't relevant.

I would like to see a "how to use" guide as well. While some are very similar to standard props (i.e. numericString), most are not. childrenHavePropXorChildren, childrenSequenceOf, explicitNull, etc could all have different ways to use them.

Totally! Currently the tests themselves consist of most of the documentation; if someone wanted to write a PR that adds better docs for all the individual validators, that'd be great!


Issue #33

Ensured iat is an integer as specified in issue #33

@daleattree thanks for the PR, would you mind to fix the .gitignore?

.gitignore has been fixed. Apologies for that.

What will happen when trying to verify an old token with this new version? I think casting will automatically happen but can we add a test for that? :)

@daleattree any updates? When you're done with the test, could you also please squash everything in one commit? thanks

Sorry. Been a bit hectic at work. Will try and get the test done over the weekend.

@daleattree no need to be sorry, thanks for your effort! If you don't have time just let me know, we can help :)

@daleattree hi, If it's fine for you I will jump on this this week, updating the tests,  in order to merge these changes. ok?

Yes please.
On Sun, Dec 6, 2015 at 8:00 AM, cirpo<EMAIL_ADDRESS>wrote:

@daleattree https://github.com/daleattree hi, If it's fine for you I
will jump on this this week, updating the tests, in order to merge these
changes. ok?
—
Reply to this email directly or view it on GitHub
https://github.com/namshi/jose/pull/50#issuecomment-162275902.

@daleattree check https://github.com/namshi/jose/pull/60


Packaging for Debian and other distros: bootstrapping from source only without prebuilt binaries?

Hello,
There are growing interests in having Dart as an official Debian package.  For example, there are requests to have Flutter built for Debian, and as now Dart Sass has become the primary implementation of Sass, replacing the deprecated Ruby and C/C++ LibSass implementations.  These all require Dart to be packaged for Debian, similar to how Go (golang) has become an integral part of Debian, and as a reply to https://bugs.debian.org/931793 says:

No dart in Debian, still a long way to go!

As a Debian Developer myself, I have started looking into packaging Dart for Debian, but quickly encountered a problem:  seems to be no way of building Dart from source code only, and instead the current build system requires prebuilt binaries?  From what I could guess from git commit logs, the build system did allow bootstrapping Dart from source before 2018, but now it seems the use of prebuilt dart binaries (for speed) is the only way left?
So, am I missing something?  Is there anyway to bootstrap Dart from source only without reliance on prebuilt binaries, so that we as Linux distribution maintainers can package Dart for Debian/Ubuntu, Fedora, etc., and to test and to try to get Dart to work on architectures other than X86 and ARM?
Many thanks!
Anthony

In this particular case it is not really about the speed. In 2018 we moved from multiple Dart front-ends to a single Dart front-end (aka CFE) written in Dart itself, which created a circular dependency in the build graph: to be able to parse and run any Dart code you need to be able to parse and run Dart code implementing the CFE first. Similar to how building a GCC requires some C compiler to be available. The way we break this dependency is by using prebuilt binaries: you use a prebuilt Dart binary to run CFE to compile Dart code to its binary AST representation (aka Kernel) which then can be run on the VM. Another (more portable) way to break this dependency would be to store just an older version of CFE compiled to Kernel instead. But it is unclear if this portability yields anything meaningful: Dart supports a limited number of platforms and you can't just take it and build it say for Linux on MIPS. And for all platforms we support we have prebuilt binaries.

to try to get Dart to work on architectures other than X86 and ARM?

Porting Dart to a new architecture is not just about compiling it. Running Dart natively requires writing a new backend for Dart VM, which is a significant investment of time. (There is a trick to bypass this by building and running one of our simulated builds, but it is hardly useful because performance would be too bad to run anything meaningful).

In this particular case it is not really about the speed. In 2018 we moved from multiple Dart front-ends to a single Dart front-end (aka CFE) written in Dart itself, which created a circular dependency in the build graph: to be able to parse and run any Dart code you need to be able to parse and run Dart code implementing the CFE first. Similar to how building a GCC requires some C compiler to be available. The way we break this dependency is by using prebuilt binaries: you use a prebuilt Dart binary to run CFE to compile Dart code to its binary AST representation (aka Kernel) which then can be run on the VM. Another (more portable) way to break this dependency would be to store just an older version of CFE compiled to Kernel instead. But it is unclear if this portability yields anything meaningful: Dart supports a limited number of platforms and you can't just take it and build it say for Linux on MIPS. And for all platforms we support we have prebuilt binaries.

to try to get Dart to work on architectures other than X86 and ARM?

Porting Dart to a new architecture is not just about compiling it. Running Dart natively requires writing a new backend for Dart VM, which is a significant investment of time. (There is a trick to bypass this by building and running one of our simulated builds, but it is hardly useful because performance would be too bad to run anything meaningful).

Hello,
Bootstraping Dart using itself should be allowed. It would be a 2 stage process. First Dart would be built using prebuilt binaries and then it would rebuild itself. The biggest problems are that the build still requires Python2 and that it's not possible to use system build tools to build Dart instead of using those downloaded by depot tools.


in next app router using a Center before Heading leads to a hydration error

Description
Using a Center, View or Box on your page before any Heading leads to a hydration error. More components may be affected
CodeSandbox/Snack link
https://github.com/macrozone/gluestack-hydration-reproduction
Steps to reproduce
best checkout the repo above https://github.com/macrozone/gluestack-hydration-reproduction
not sure whether this would work in a codesandbox, so i created a new nextjs app that shows the error
the reproduction is a freshly created nextjs app where gluestack is installed according to the guidelines https://gluestack.io/ui/docs/guides/install-nextjs

clone the repo
yarn install
yarn dev
goto localhost:3000
click the first link
reload the page --> hydration error

the bug only happens if Center is used before any header. The same error happens with Box and View. I did not check other components
As a workaround, you can add a empty heading
gluestack-ui Version
"@gluestack-style/react": "^1.0.49",     "@gluestack-ui/config": "^1.1.16",     "@gluestack-ui/themed": "^1.1.9",     "@gluestack/ui-next-adapter": "^2.1.11",
Platform

[ ] Expo
[ ] React Native CLI
[X] Next
[ ] Web
[ ] Android
[ ] iOS

Other Platform
No response
Additional Information
No response

@macrozone Thanks for reporting this. We'll have a look.

@macrozone, thanks for the report. I encounter this months ago and couldn't find the cause and when back to page router. Confirmed this was indeed the case. +1 👀

has anyone found a way to handle this , I mainly get it when using the text component, ended up using tailwind for texts.
NextJS 14 App Router

Closing this issue for now, feel free to reopen on any issue encounter or discussion.


Fix-Sticky-Footer

Fixes #21

Ah I see my mistake why CI isn't running for forks. I see a composer change here, but I think you only wanted the css change.
Either way, I'll push up a fix to correct CI from forks in meantime.

Gotcha thanks! should be sticky now. Was going for "just stay at bottom" approach before lol. Also noticed some empty columns on home.blade.php file causing gamer form to be left-aligned instead of centered, left it alone as not sure if it was intentional.

Still learning flexbox myself, but there seem to be a good deal of utilities that might be able to be used - https://bulma.io/documentation/helpers/flexbox-helpers/

First time trying out Bulma myself it's not bad. I cleaned it up with classes but could not find height or width utilities though.

thanks! looks good


Switch to prettier?

It seems to have taken off in the js world.
It would alleviate issues with users running into eslint/stylelint errors.
This PR also adds a git hook to run prettier, which ensures that future commits are consistently styled.

By far the biggest reason for adopting Prettier is to stop all the on-going debates over styles. It is generally accepted that having a common style guide is valuable for a project and team but getting there is a very painful and unrewarding process.

If I'm understanding it right, Prettier decides the code style for you. This is a really bad direction to take as the agency I work for has a specific set of style rules we apply across all our projects (Sage + WP, Laravel, Magento, etc). I imagine it would be the same thing for many other users.
We would be unable to use Sage as-is if Prettier is merged into the theme. Forking and updating each time there is an update would cause a big headache.
I think we need to allow the developers to choose their coding styles as I am sure many others like us have spent significant time setting specific standards. For those who have not, the existing rules from eslint and stylelint should suffice.

Prettier does nothing to help with [code quality] rules. They are also the most important ones provided by linters as they are likely to catch real bugs with your code!

Regardless of using Prettier, eslint should still be included for code quality rules.

Overall if I had a say it would be to vote against this PR. Thanks for all your hard work on Sage, for reading this, and for working to continually improve this awesome project!

Yeah, I overestimated what prettier was capable of.
Since it completely rewrites all of the code it analyzes, I assumed that it would address code quality as well. I should have probably looked into it a bit more before deciding to go all in with it.


Update README.md

/jx chuck

/jx chuck

/test chuck

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

Test name
Commit
Details
Rerun command

chuck
dffa2478bb96097543976b3970b2693b39ec2a92
link
/test chuck

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

/test chuck

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

Test name
Commit
Details
Rerun command

chuck
dffa2478bb96097543976b3970b2693b39ec2a92
link
/test chuck

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


1-1 Foreign Key Unique Constraint is missing NULL filter

When I created my model back on EFCore 1.x the unique constraint on a 1-1 foreign key had a filter so I could have multiple nulls. After upgrading to EFCore 2.x new databases are created running the exact same migrations, but they don't create the filter.
Steps to reproduce
Create 1-1 Foreign Key
builder.Entity<Attempt>()
    .HasOne(q => q.Dishonour)
    .WithOne(v => v.Attempt)
    .HasForeignKey<Attempt>(q => q.DishonourId);

Resulting Index from EFCore 1.x

Resulting Index from EFCore 2.x

Further technical details
EF Core version: 2.0.0
Database Provider: Microsoft.EntityFrameworkCore.SqlServer
Operating system: Windows 10
IDE: Visual Studio 2017
Sql Server: 13.0.4001

Looks like it could be an issue with migrating from 1.x to 2.x.
After creating my next migration, I noticed all of my indexes and foreign keys were dropped and recreated. While this is an OK thing for me, I didn't see this in the migration documentation and was not aware I'd have to do it.
To resolve this issue, can you please add a section to the migration document (https://docs.microsoft.com/en-us/aspnet/core/migration/1x-to-2x/) mentioning that you should create a new migration to handle changes between the old and new migration code.
EFCore 1.x migration code
migrationBuilder.CreateIndex(
    name: "IX_Attempts_DishonourId",
    table: "Attempts",
    column: "DishonourId",
    unique: true);

EFCore 2.x migration code
migrationBuilder.CreateIndex(
    name: "IX_Attempts_DishonourId",
    table: "Attempts",
    column: "DishonourId",
    unique: true,
    filter: "[DishonourId] IS NOT NULL");

Hello @bjcull,
https://docs.microsoft.com/en-us/ef/core/miscellaneous/1x-2x-upgrade

@bjcull Thanks for reporting this. It looks like the issue is that in 1.1, that filter was applied by convention, whereas in 2.0 is is now explicitly scaffolded. We missed that this means that we need to this when running 2.0 code over migrations generated by 1.1 so that we can correctly infer the filter again in these cases.


Add depth to section

This PR adds support for depth.
app(Navigation::class)
    ->add('Home', route('home'))
    ->add('Blog', route('blog.index'), function (Section $section) {
        $section
            ->add('All posts', route('blog.index'))
            ->add('Topics', route('blog.topics.index'));
    });

app(Navigation::class)->tree();

[
    {
        "title": "Home",
        ...
        "depth": 0
    },
    {
        "title": "Blog",
        "children": [
            {
                "title": "All posts",
                ...
                "depth": 1
            },
            {
                "title": "Topics",
                ...
                "depth": 1
            }
        ],
        "depth": 0,
    },
]

In my opinion, very useful when building mega-menus, where the first level would be a horizontal menu, and the following levels would be different variations of dropdowns. I'm sure there are more cases where we could find this useful.
Cheers.

Thanks!

You're welcome, I can PR for docs as well if you want me to.


activate CI tests

If you claim your library works on macos, windows and linux you might want to test things.
as of https://github.com/gabrieldemarmiesse/python-on-whales/actions/runs/931356479
quite a few tests are skipped:
tests/python_on_whales/components/test_compose.py::test_docker_compose_build SKIPPED [  3%]
tests/python_on_whales/components/test_compose.py::test_docker_compose_up_down SKIPPED [  3%]
tests/python_on_whales/components/test_compose.py::test_no_containers SKIPPED [  4%]
tests/python_on_whales/components/test_compose.py::test_docker_compose_up_detach_down SKIPPED [  4%]
tests/python_on_whales/components/test_compose.py::test_docker_compose_pause_unpause SKIPPED [  5%]
tests/python_on_whales/components/test_compose.py::test_docker_compose_create_down SKIPPED [  5%]
tests/python_on_whales/components/test_compose.py::test_docker_compose_config SKIPPED [  6%]
tests/python_on_whales/components/test_compose.py::test_docker_compose_create_extra_options_down SKIPPED [  6%]
tests/python_on_whales/components/test_compose.py::test_docker_compose_up_detach_down_extra_options SKIPPED [  6%]
tests/python_on_whales/components/test_compose.py::test_docker_compose_up_build SKIPPED [  7%]
tests/python_on_whales/components/test_compose.py::test_docker_compose_up_stop_rm SKIPPED [  7%]
tests/python_on_whales/components/test_compose.py::test_docker_compose_up_rm SKIPPED [  8%]
tests/python_on_whales/components/test_compose.py::test_docker_compose_up_down_some_services SKIPPED [  8%]
tests/python_on_whales/components/test_compose.py::test_docker_compose_ps SKIPPED [  9%]
tests/python_on_whales/components/test_compose.py::test_docker_compose_kill SKIPPED [  9%]
tests/python_on_whales/components/test_compose.py::test_docker_compose_pull SKIPPED [  9%]
tests/python_on_whales/components/test_compose.py::test_docker_compose_up_abort_on_container_exit SKIPPED [ 10%]

Good catch, it's very suprising. I'll look into why they are skipped.

https://github.com/gabrieldemarmiesse/python-on-whales/blob/master/tests/run_tests.sh doesn't really test anything ... especially not docker compose up which can't work if the plugin is not installed as per #188


link through to sharding guide

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@46e1b1f). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #6218   +/-   ##
=========================================
  Coverage          ?   83.24%
  Complexity        ?    12512
=========================================
  Files             ?     1450
  Lines             ?    47393
  Branches          ?     5814
=========================================
  Hits              ?    39453
  Misses            ?     5250
  Partials          ?     2690

Continue to review full report at Codecov.

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


Add Configurable Master Interface for NetworkAttachmentDefinition in Helm Chart

Hi everyone,
I noticed that the NetworkAttachmentDefinition for macvlan-conf in the Network Manager defaults to using eth0 as the master interface. However, not all clusters use eth0 as the default network interface on their nodes. It would be helpful to add a configurable value in the values.yaml file of the Helm chart, allowing users to specify the desired master interface during installation. This change would enhance compatibility across different environments.

Hi @bl4ckj4c,
you're right, we worked with kind env in mind but as a matter of fact eth0 isn't standard at all (especially on Ubuntu 24).
We'll release a patch to address this issue.


Define _POSIX_C_SOURCE to expose popen/pclose

On musl libc
popen  and pclose aren't exposed  by musl libc unless one of the following macros is defined:
#if defined(_POSIX_SOURCE) || defined(_POSIX_C_SOURCE) \
 || defined(_XOPEN_SOURCE) || defined(_GNU_SOURCE) \
 || defined(_BSD_SOURCE)

On Glibc
According to manpage popen(3) on Linux  man-pages 6.05.01 :
   Feature Test Macro Requirements for glibc (see feature_test_macros(7)):

       popen(), pclose():
           _POSIX_C_SOURCE >= 2
               || /* glibc <= 2.19: */ _BSD_SOURCE || _SVID_SOURCE

Notes

_POSIX_SOURCE has been superseded by  _POSIX_C_SOURCE.
_POSIX_C_SOURCE with a value of 2 is the option that potentially causes  the least namespace contamination.

See feature_test_macros(7) for more  information  about the macros.

Seems the Mac OS X libc is broken. _POSIX_C_SOURCE == 2 means POSIX.2-1992 which should make the snprintf and vsnprintf functions available.

Yea. I do find strange things on OSX sometimes. :)


fix: open api errors

What this PR changes/adds
Resolving the current OpenAPI errors.
Why it does that
It resolves the OpenAPI error by adding the missing description fields.
Further notes
Linked Issue(s)
Closes #3120

Codecov Report
Patch and project coverage have no change.

Comparison is base (eb3a2de) 65.27% compared to head (e6e22a7) 65.27%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3178   +/-   ##
=======================================
  Coverage   65.27%   65.27%
=======================================
  Files         834      834
  Lines       16774    16774
  Branches      924      924
=======================================
  Hits        10949    10949
  Misses       5452     5452
  Partials      373      373

see 1 file with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

@git-masoud @konrad1adamczyk either one of you doesn't have a signed ECA yet. Without it, we cannot merge.


Use Black for Formatting

A quick demo of how to make black auto-format everything. This also shifts format checking to gh infrastructure.
All I did to generate a bulk of the changes in this PR was:
black picamera2 which in turn output the reformatted code:

This has the side benefit of killing a lot of diff noise between PR's
Signed-off-by: Matthew Goodman<EMAIL_ADDRESS>

Note that style check now takes about... 4 seconds:

Hi, thanks for posting this it looks interesting. Can you say how I could enforce this kind of style during development, for example by using the git pre-commit hook? Also, have you changed the style checking process on the test machine to complain if people don't stick to this style or not, I didn't quite understand that.

There are a number of options for this:

Before commiting run black picamera2 from the repository root
Install black and add black picamera2 to the .git/hooks/pre-commit
Install and use the pre-commit framework (which is what I do in my projects), which will manage installation of many potential pre-commit options (including black). It's nice because it comes with a raft of options that you can scale in as the code becomes more mature. Starting with formatting is easy, then adding lint, doc requirements, type-checking etc all just becomes a couple lines of config

Here is what that looks like in a project I am working on:

Also, this PR is likely to be conflicted by basically any other change, so let me know when/if you want it and I can freshen it :)

And to answer your earlier question. This line will cause the CI to reject PR's that are not consistant with the formatting requirements.

As a totally incidental side benefit, this takes the style check responsibility off the pi you are using to run tests :)

This change seems reasonable, but there are a couple of things that I can see we need to address:

The github action command probably wants to be black --check --diff picamera2 to show what formatting changes would be needed.
There does not seem to be a way to run black on a diff/patch as far as I can tell.  This is not ideal, since if we chose to ignore a particular style dictated by the tool for a single PR, the tool will end up complaining about it for all subsequent PRs, which defeats the purpose of the pre-commit check.

Hmmm. The flags are easy to switch out. Let me start there.
Following up on the second bullet point. Looking through the checker it seems that it completely checks all files/lines, then filters to lines contained in the diff only. I am more than a little confused as to how that can deal with multi-line expressions in a sane way, but that isn't the question here. black is named for the Henry Ford quote, its kinda hostile by design.

It might just not meet the needs of this group if y'all want to have exceptionally formatted sections.
FWIW, the not having redo PR's for code style issues is about 50% of the appeal, another 40% is not having to educate folks that contribute about the particular flavor of code style. :man_shrugging:

Apparently running on a diff has been a feature request for some time now - https://github.com/psf/black/issues/830.  Looks unlikely that this will be put into mainline.
There are a few wrapper-of-sorts that does seem to do this - https://github.com/akaihola/darker and https://github.com/wbolster/black-macchiato.  Perhaps it's worth looking to see if those could be used instead?

Seems like this ins't a real improvement here.


Add jQuery to list of allowed globals

Implements the fix @sephcoster found today. I just ran into the same bug while working on the generator.
Changes

Adds jQuery to list of allowed globals in .eslintrc.
Updates changelog appropriately.

Review

@sephcoster
@anselmbradford
@jimmynotjim

Notes

Setting it to false checks that your code doesn't overwrite $.

:+1:

So this was introduced in https://github.com/cfpb/front-end/pull/47, with the logic that the env setting would be used to adjust presence of jQuery (and on a project to project basis).
Dunno if @anselmbradford has a a different opinion, but my feeling is that there aren't too many downsides to the change in this PR. People who inexplicably want to use $ as a variable name can just adjust their local .eslintrc.
Also, re #46, jQuery is used in almost every project and probably deserves default status.

Yeah so as @wpears pointed out, the original thinking with this was not to bake in global jQuery. Plenty of projects use jQuery, but arguably it's a bad practice to have it set up to be global. I was on the fence about how to set this one up so I'm not surprised this PR came up.
Two questions I have with this are:

How does this work in a project if jQuery is used, but is not global? Certainly that's the minority of projects, but having a global jQuery defined in the linter potentially would mask errors where jQuery was, in fact, not defined.
Is there a difference between setting the jQuery value in globals vs env? It seems like there might be in that globals allows the explicit setting of whether the value can be overwritten or not. I can't find in the ESLint docs what the behavior is in env in regard to overwriting, but if anyone wants to test whether it would make more sense to turn this on in the env setting vs in the globals that may be good to look at further. My feeling is if they work the same way, that using the env setting would be better so that we're not defining vars in the globals, but instead switch a flag to say jQuery is present.

An alternative to this setting is using inline global comments in the file where its needed http://eslint.org/docs/user-guide/configuring.html#specifying-globals

I'd support using env rather than global. Next question is whether we set it to "true" by default. Only reason this came up for me was that this linter runs by default when you run the capital framework generator build. Without a true default (or some global set) the build will fail by default, which is not the most welcoming thing when you run through the steps :)


[WIP] text-input-v1 support

Adds support for tiv1
Doesn't seem to work yet due to chromium being weird...?
@fufexan for meson / nix (protocol added)

hm, so far so good, but something's off. Chromium insta-crashes on any text input from IME lol

Chromium doesn't crash most of the times now, oddly I can type entire sentences but the moment I try to type ！ after a 乾杯 it dies.

awright fixed crashes

@dragove can you test this as the original reporter for the issue

Tested this a bit on arch:
electron19 --enable-wayland-ime --ozone-platform=wayland https://github.com # doesn't work, same symptom as the comment above
electron20 --enable-wayland-ime --ozone-platform=wayland https://github.com # ditto
electron21 --enable-wayland-ime --ozone-platform=wayland https://github.com # works
electron22 --enable-wayland-ime --ozone-platform=wayland https://github.com # works

VSCode is currently using electron19, so I guess the electron/chromium behavior changed in recent versions of electron/chromium.

However, afaik all of the above works in weston and kwin, so there must be something that could be done by hyprland as well.

https://github.com/electron/electron/releases/tag/v21.0.0-alpha.1

Added support for --ozone-platform-hint flag on Linux. https://github.com/electron/electron/pull/34937 (Also in https://github.com/electron/electron/pull/35015, https://github.com/electron/electron/pull/35014)

And the positioning of the candidate word panel is always in the upper left corner

Odd, as the client should send the cursor box. If it doesn't, then maybe hl doesn't send some event it expects?
Although if it works with electron >=21 I'd say it's a minor issue.
I'd rather push this (because it generally works) and work on that minor problem as time goes on. Seems stable to me, so no harm in doing that.
Feel free to open another issue for that.
Thanks for the feedback!


Two useful possibilities leveraging GitHub

Though this spec is focused in git, not GitHub, there are three features of github that may be very useful.
The first is that all GitHub users who have registered GPG keys for file signing, you can access their public key by just appending .gpg to their user name, such as https://github.com/ChristopherA.gpg — this makes GitHub alternative source for keys rather than the problematic key servers.
The 2nd is that gists are actually small git repos, so you add additional files and can sign commits with GPG. You can check it out with git clone git@gist.github.com:855bf8e4774375613c6b2e1226501ba6.git
The third, as you'll note above, any user gist, such as https://gist.github.com/ChristopherA/855bf8e4774375613c6b2e1226501ba6 can also be accessed without the user name at https://gist.github.com/855bf8e4774375613c6b2e1226501ba6 which is short enough to fit in an BTCR OP_RETURN.
All of this may make gists a useful place to store a DID or VCs.
-- Christopher Allen
cc: @rxgrant @kimdhamilton @joeandrieu

Awesome, i didn't know about the gpg extension...
In the earliest version of GitHub DID we based the DID off the repo name, and also supported storing VCs on github... I'd be interested in adding something like that back for repos and gists at some point in the future, particularly to help make OCAP / ZCAPs easier to understand.

We could add a step to the GitHub DID resolver that makes sure that a GitHub DID also has a registered GPG key...
As you mentioned: https://github.com/OR13.gpg
This would prevent a GitHub DID from returning a DID Document that did not contain a registered GPG key, but it would make creating GitHub DIDs a much more complicated process.
IMO such an integration would not be worth the effort, since the main objective is to make it easy to create DIDs...
There is also: https://github.com/dhuseby/did-git-spec
I think I need to actually write a proper spec for GitHub DID soon.


FAQ section enhancement

Description
I would like to improve the FAQ section by adding smooth transition styles
Screenshots
No response
Checklist

[X] I have checked the existing issues.
[X] I have read the Contributing Guidelines
[X] I have read the Code Of Conduct
[X] The changes don't break the code

Go ahead!


[Meta Issue]: OpenAPI Support

🔖 Feature description
This is a collection of issues stemming from #2566. The goal of this ticket is to break apart the different types of work from that original ticket into separate camps and define a clearer roadmap for OpenAPI support in Backstage.
What do you mean by OpenAPI support in Backstage?
This can mean a multitude of things, which is partially why we want to replace the old ticket. Here it will mean

OpenAPI specs for plugins.
An OpenAPI spec-first developer experience, using the spec to drive server-side code writing.
A Backstage-only client generated using the spec.
Other language clients like Java, Python for interfacing with Backstage plugins.
new API fuzzing of OpenAPI documented plugins

Plugin Specs

[x] catalog-backend (#15667, #16238)
[x] search-backend (#17511)

Spec-first Development

[x] Typed express router methods (#15667)
[ ] Request, params and response validation (#17875)
[ ] Auto-generated server stubs
[ ] Test-driven feedback of OpenAPI specs

Internal Client Autogeneration

[ ] Custom generator from openapi-generator (#17470)
[ ] Migrate existing clients to use autogenerated versions

[ ] catalog-backend
[ ] others

Additional Client Autogeneration

[ ] Support for additional languages

[ ] Java
[ ] Python
[ ] Typescript

API Fuzzing
Context:

[ ] Integrate with Schemathesis.

Open Questions

Should we have a single monolithic client that includes all plugins and specs or should each plugin have its own autogenerated client?

Others

[ ] Serving these specs in Backstage for meta discovery. (#17535)
[ ] schema/openapi.yaml endpoint with a runtime generated API spec (#17535)

Also, found this library for jest that adds spec validation into the responses, https://github.com/openapi-library/OpenAPIValidators/tree/master/packages/jest-openapi#readme. Would be useful for verifying response values in test cases as a precursor to turning on validateResponses in the middleware.

@sennyeya as you think about the client autogeneration, you ought to check out Fern

@dannysheridan apart from discussion on the technical solution, this part of the experience is a blocker for us to adopt Fern as a default tool in the Backstage OSS project:

@dannysheridan apart from discussion on the technical solution, this part of the experience is a blocker for us to adopt Fern as a default tool in the Backstage OSS project:

@Rugvip we can add a --skip-login option on init/generate. Would that unblock adopting fern? (So far enforcing login has been great for analytics/support but I see why that's extremely limiting in an OSS project).

@dsinghvi If login is not required and there are no usage limitations for the core use-cases we're likely at a point where we wouldn't dismiss it. We'd still ofc need to evaluate whether it's a desirable solution and what level of lock-in there is.

@sennyeya if you need anything from the Schemathesis side, feel free to tag me and I’ll be happy to provide support on integrating it :)

@Stranger6667 That was quick! Will definitely keep you in the loop as I start exploring. Thanks for the great tool!

hey have we considered finding a way to not run openapi generate-client script when developing?
I felt the pain of writing yaml, then run a script to generate a .ts file which is then consumed by our typescript bundler.
I found the process really slow and is yet another thing that contributors need to learn before contributing to Backstage.
I would love to just write the openapi definition in typescript instead.

@vinzscam Reached out via DM, happy to help but I'd like a little more info on your use case.

@vinzscam Reached out via DM, happy to help but I'd like a little more info on your use case.

nothing fancy I am just developing a plugin which integrates with OpenAPI and found the process a bit complicated 😅
I'm thinking that writing the definition directly in typescript (for example by using some zod to openapi library) might simplify the development process.


Carthage update fails while building Polyline scheme

When I run scripts/setup.sh I get the attached Build Failed message.
carthage-logs.txt

I wonder if this is the culprit in Line 334 of Polyline.swift. In function extractNextChunk, line 334 causes the build error 'subscript' is unavailable because it was obsoleted in Swift 4. StackOverflow suggests this fix to your exact MapBox code:
https://stackoverflow.com/questions/45580072/why-wont-substrings-work-in-swift-4-anymore

Actually Polyline has already been updated to Swift 4 so your Cartfile dependencies should point to that:
https://github.com/raphaelmor/Polyline/tree/v4.2.0
or rather, MapboxDirections dependencies should point to that. I've raised an issue in MapboxDirections.

MapboxDirections dependencies should point to that

Looks like that will happen in https://github.com/mapbox/MapboxDirections.swift/pull/196

I get the attached Build Failed message

I think MapboxDirections.swift at "v0.11.2" should still work. I'm not able to reproduce the issue you have when I try with Xcode Version 9.0 (9A235) and Carthage v0.26.2. In my log I see:
...

/usr/bin/xcrun xcodebuild -project /Users/boundsj/workspace/mapbox-arkit-ios/Carthage/Checkouts/Polyline/Polyline.xcodeproj -scheme Polyline -configuration Release -derivedDataPath /Users/boundsj/Library/Caches/org.carthage.CarthageKit/DerivedData/9.0_9A235/Polyline/v4.1.1 -sdk iphoneos ONLY_ACTIVE_ARCH=NO BITCODE_GENERATION_MODE=bitcode CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES archive -archivePath ./ SKIP_INSTALL=YES GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=NO CLANG_ENABLE_CODE_COVERAGE=NO (launched in /Users/boundsj/workspace/mapbox-arkit-ios/Carthage/Checkouts/Polyline)User defaults from command line:
    IDEArchivePathOverride = /Users/boundsj/workspace/mapbox-arkit-ios/Carthage/Checkouts/Polyline
    IDEDerivedDataPathOverride = /Users/boundsj/Library/Caches/org.carthage.CarthageKit/DerivedData/9.0_9A235/Polyline/v4.1.1

...

** BUILD SUCCEEDED **

...

Can you try clearing the Carthage Build and Checkouts folders in your project also and the derived data in from the directory noted in the log you attached (/Users/wa/Library/Caches/org.carthage.CarthageKit/DerivedData/)?

Hm, cleared Carthage/Build and Carthage/Checkouts and Derived Data. Ran scripts/setup.sh again, got same errors. Same xcode, same carthage versions.


readme updates

The README current states that node 14 is supported. Have removed node version specific info here and left a link to the Homebridge wiki page so this is one less place to keep version numbers maintained.
Also took the opportunity to fix some grammatical errors that my IDE suggested!

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.09%) to 43.4%

Totals

Change from base Build<PHONE_NUMBER>:
0.09%

Covered Lines:
2113

Relevant Lines:
4507

💛  - Coveralls


Resolve unhandled promise warnings in unit tests

We have a few unhandled promise rejections, these need to be resolved:
 Unit Tests - debugging
    ✓ Debugger should start (unittest) (466ms)
rejected promise not handled within 1 second
rejected promise not handled within 1 second
rejected promise not handled within 1 second
rejected promise not handled within 1 second
rejected promise not handled within 1 second
rejected promise not handled within 1 second

  Interpreters display version
rejected promise not handled within 1 second
rejected promise not handled within 1 second
rejected promise not handled within 1 second
rejected promise not handled within 1 second
rejected promise not handled within 1 second
rejected promise not handled within 1 second
rejected promise not handled within 1 second
    ✓ Must return the Python Version (706ms)

To help manage our issues and to better communicate what the team plans to work on we are closing issues that we don't plan to work on but would accept a pull request from a volunteer for. To be clear, closing this issue does not mean we won't consider a pull request for this enhancement as outlined in our contributing guide, just that the development team has no plans to work on it themselves.


add user name to blob metadata

So it can be extracted later by listening events

This is really a more general purpose need to add any metadata to a blob when it's committed.


Fix paste button being permanently disabled because SSH session was not yet open.

Fixes #295.
I'd prefer this not be merged until @alescdb weighs in on it.

LGTM pending verification from @alescdb

Working OK !
I confirm this PR corrects the #295 issue :-)

Great! :fireworks:


Month First Parses ISO Dates Incorrectly

With monthFirst set to False, if you pass in an ISO Formatted date (YYYY-MM-DD) from the database the component mixes up the month and day where DD <= 12.
Not sure if this is expected behaviour for parsing the date as I want the date to appear with the Day before the Month, but still parse the date correctly.
https://jsbin.com/fojavulame/edit

Try overriding the parser to handle specific database formats. See #5.


Fix flaky ONNX Runtime generation test with past key value reuse

As per title.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Yes, locally I had no issue. Will have a look.


Swapped interval and timeout

What happened?
In the e2e tests, there are instances where the timeout and interval are swapped within the arguments list. This causes no issues in the current setup, https://github.com/k8ssandra/k8ssandra-operator/pull/1314/commits/6a05eeac031d5e757d7e38637cc4775de38b9113.

I think this got merged with #1314

I think this got merged with #1314

I think this got merged with https://github.com/k8ssandra/k8ssandra-operator/pull/1314

It did ;)


cmp_nvim_lsp module not found

local capabilities = vim.lsp.protocol.make_client_capabilities()
capabilities = require('cmp_nvim_lsp').update_capabilities(capabilities)

Can't find cmp_nvim_lsp module, error coming from the require method.
I have cmp installed with all relevant extensions, yet it yields the same result wherever I try to place these lines (lspconfig.lua file or in seperate lsp configuration files).

You should upload the minimal vimrc

I have this same issue.

Not sure if the same issue, but when running CmpStatus on nvim, I get the following output:
unknown source names

nvim_lsp

Please upload the minimal vimrc

Nevermind. Just found out that I have to launch RustStartStandaloneServerForBuffer manually on nvim for whatever reason :) Thanks for your answer anyway.

OK.  I think the issue should be closed.

I'm having the same issue.  Here is a minimal init.lua:
require('packer').startup(function()
  -- Base functionality
  use 'wbthomason/packer.nvim'

  -- Autocomplete
  use 'hrsh7th/nvim-cmp'
  use { 'hrsh7th/cmp-nvim-lsp', after = 'nvim-cmp' }
  use { 'hrsh7th/cmp-buffer', after = 'nvim-cmp' }
  use { 'hrsh7th/cmp-path', after = 'nvim-cmp' }
  use { 'hrsh7th/cmp-cmdline', after = 'nvim-cmp' }
end)

local lsp_servers = {'gopls'}
-- Setup Autocomplete capabilities
local capabilities = require('cmp_nvim_lsp')
  .update_capabilities(vim.lsp.protocol.make_client_capabilities())

for _, lsp in pairs(lsp_servers) do
  require('lspconfig')[lsp].setup {
    capabilities = capabilities,
  }
end

Ok, so this turns out to be a problem with my packer config.
For some reason, packer was marking all the plugins with the after key as optional, and not loading them.
If I remove the after or put those dependencies in the requires field of nvim-cmp then all works as expected.
Sorry for the noise, hope this helps someone else.

@hrsh7th I think it can be closed.

Yes. If you want to use `require('cmp_nvim_lsp') in your vimrc, You can't use lazy-loading.


updated for ghc 8.4.2; exported everything as a library

Will be coming in after I make sure that everything builds on CI with a range of compiler versions.


MindPX update

We make some important improvement for MindPX hardware.
Major changes include:
1. add RC input/SBUS/Spektrum/FrSky telemetry receiver IO hardware circuit
2. expand to 8 pwm outputs.
This PR is an adaptation to the new hardware.

Great! One thing I noticed is that you have the wrong product ID in nuttx-configs/mindpx/nsh/defconfig. The CDC ACM PID should match the one in the boot loader. Right now you're using the Pixhawk PID, which is incorrect since its different hardware.

Thanks for the amazing quick response. :) @LorenzMeier
Have a check for the product id, I found that pid defined in bootloader is
define USBPRODUCTID                   0x0030
and in nsh/defconfig
CONFIG_CDCACM_PRODUCTID=0x0030.
The pid MindPX used is different from Pixhawkv2 (0x0011), PixRacer(0x0012).

Ok, great - could you look into the CI failures? Thanks!

@iZhangHui Where can we get your v2.6 hardware? Would you mind dropping me an email at<EMAIL_ADDRESS>? Your website is still a bit confusing: ) Thanks!

@iZhangHui
Just an heads up, There was a change to the pwm rgbled  that I think may have broken mindpx
Please see https://github.com/PX4/Firmware/issues/5710#issuecomment-256798164
Is the 2.6 schematic published?
Will the 2.4 and 2.6 version need to be supported or is the 2.4 End Of Life and this replaces it?
@LorenzMeier CONFIG_CDCACM_PRODUCTID was only wrong on nuttx_v3 - that was fixed a bit ago.

@iZhangHui Can you please test wether the RGB led is still working for you?

Pretty nice diff. Thanks for cleaning up a lot of the earlier hackery.

@iZhangHui
From the fact this was merged on top of the 2.4 HW I assume you have stopped support 2.4 completely.
Is the 2.6 schematic published?
I have already merged the 2.4 into nuttx_v3. At some point next week I will be merging into nuttx_v3 again.
At that point there will be a bit of work needed in the src/board files. Which should be structured like the px4fmu-v2 is on nuttx_v3. As an example all the IO is initialized in stm32_boardinitialize, hardfault_log is supported and the nuttx-config will also need to be harmonized to that of the px4fmu-v2 is on nuttx_v3.

@davids5
2.8 is the latest revision. The schematic PR is on the way.
2.4/2.6 are all internal iterations and never officially go public. 2.8 is the public stable hardware release as future base, ready for shipping now.
Release 1.4.1 will be the latest firmware works on existing 2.3 hardware and will keep working. Any new releases only works on 2.8 though.
Previous 2.3 users can contact us for discussion of further support if needed. A micro revision management solution is also under consideration to ensure smooth transition.
Thanks a lot for the heads up!

@airmind Where can we buy the latest revisions?

@mhkabir
2.6 is internal iteration, 2.8 is the public stable hardware release. I will drop you a mail on that.
Thanks!

@airmind - then it sounds like I should wait for the 2.8 PR before any real time on the merge of this version on master into nuttx_v3.

@davids5
will be there soon.

@davids5
the 2.8PR is here: #71
https://github.com/PX4/Hardware/pull/71

@airmind
Thank you for the update.
What is the ETA on the SW PR for 2.8?

@davids5
Sorry but there seems some misunderstanding here?
The codes @iZhangHui already submitted in this PR just matches the 2.8 schematics PR (#71). So all codes already in Master.
I am not sure why you mentioned 2.4/2.6 in above, as its only our internal releases.  2.4 is an even earlier and non-stable version. We actually did not mention these versions publicly. The previous latest hardware we released publicly is 2.2/2.3(as in PX4 hardware repo).
Hope i have made everything clear now :-)

@airmind - thank you I was definitely confused by this https://github.com/PX4/Firmware/pull/5769#issuecomment-256873598
Now I am clear!
I will merge this to nuttx_v3 when I doe the next merge.

no problem @davids5 and thank you for the merge!


Page / Identifier and Alias Update / Delete

In M3, able to create new Identifiers and read them in the Identifiers page. Enhancement desired to implement ability to rename the Alias.  Not planning on implementing Delete, but may consider a Hiding feature later.


Frontend edit of DateTimeField fails with ValidationError "Enter a valid date/time."

Mezzanine 4.2.3 (also tested development)
Django 1.8 to 1.11 (no error with 1.8, error with > 1.8)
Python 2.7.12
SQLite 3.8.11
Windows 7  (also tested on Macos and Ubuntu)

Steps to reproduce:

Fresh install venv with mezzanine, mezzanine-project projectname
create Blogentry, try to change publish_date from frontend

Tried Django versions 1.9 to 1.11 with no luck. Debugging shows that the DateTime formfield gets a list with date and time, but requires a single string with date and time.
At last tried Django 1.8 and recognized a deprecation warning saying
\lib\site-packages\django\forms\fields.py:162: RemovedInDjango19Warning: Using SplitDateTimeWidget with DateTimeField is deprecated. Use SplitDateTimeField instead.
value = self.to_python(value)
I made a few attempts to change the formfield class of the form DateTimeField to SplitDateTimeField but with no success. Changing the form class in mezzanine/forms/fields.py seems to have no effect.

Hello!
I think this is Django issue. The date/time picker is a convenience offered in the admin, but if you're editing on the frontend you'll need to provide your own JavaScript to coerce whatever the user enters into the string expected by Django.
Feel free to re-open if I didn't understand correctly.

I'm a little bit confused. The fronted editing is part of the blog app. And it worked correct up to django 1.8, so i suppose it should work with newer versions of django. Django made a braking change to the mezzanine blog frontend editing by removing the support of SplitDateTimeWidget in conjunction with a DateTimeField. They recommended to use SplitDateTimeField instead. I think this change was never made in mezzanine. I don't think we should require people to create custom javascript code when setting up a mezzanine instance, only to make the blog app work correctly.
I appreciate the software quality of mezzanine, so let's keep this issue open until anyone in the community (including myself) had the chance to provide a solution for this bug. I did not have time to dig deep enough into the mezzanine code to find the right place to fix this, but had not given up yet.

I'm not able to reopen, since you, jerivas, closed this as a collaborator, sorry. Thanks for reopen it.

Okay, I tried frontend editing the publish_date of a BlogPost (Django 1.11 + Mezzanine master and Django 1.8 + Mezzanine 4.2.3) and it is working fine. I get a regular text input, but as long as I enter the correctly-formatted string everything works as expected.
Could you elaborate a bit more on what you're experiencing?

This is what I entered:

This is the error i get:

Does this look like yours? And do you get the deprecation warning i mentioned above when trying Django 1.8?

At least I was able to reach a state as described by jerivas. The change gives me a text input, where i can write in a corrctly formatted string. I changed the DATE_TIME Widget (forms/fields.py:74) to "forms.DateTimeInput" and the style of the input field width to 150px (core/static/mezzanine/css/editable.css).

(this time using german localization)
No dropdowns anymore but working.


Need to add extra data in callkit

I need pass call extra data to my IOS device by apn callkit. But idk where add.

ps. Sorry for my english

Hi @Edman-99
https://github.com/hiennguyen92/flutter_callkit_incoming/blob/e09b5cfeb3b23d33a757dcd0d2f0cb397b207dbe/example/ios/Runner/AppDelegate.swift#L68
data.extra = .....

@hiennguyen92 ok thanks, what about Android how i can make with terminate state in Android can you have example how to connect ?


spend is not working

I tried the
aecli account spend mywallet ak_XXXXXXXXXXXXXXXXXXXXXXXX 5000
and I get an error saying:
"Error: Sender account not found"
And I don't understand what is going on.
Using tag <IP_ADDRESS>b1

That fixes it. thank you @noandrea


add loading example with flux

Signed-off-by: insekkei<EMAIL_ADDRESS>Provided an example with flux in README, hope to help others who need it, thanks.

Hi @insekkei.  Thanks for the PR.  I'm hesitant to pull this in because this is very flux-specific code, and if someone is working with flux, I don't think it's a leap to figure out how to change state in a component since that's the basis of flux.


Cannot log in 2020-02-05

Hi, there's another "cannot log in" issue as of 2020-02-05.

Are you using the latest commit?

give me a link to it... not sure :/
its 2.0 i use
On Thu, Feb 6, 2020, 10:28 AM Jack<EMAIL_ADDRESS>wrote:

Are you using the latest commit?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ArthurG/Kijiji-Repost-Headless/issues/166?email_source=notifications&email_token=AMUQHCB7QTTPSD5G4T57V3TRBQUCXA5CNFSM4KQV34ZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEK7T6BA#issuecomment-582958852,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMUQHCEBSMZHQKXDTZKUKGTRBQUCXANCNFSM4KQV34ZA
.

Just pull the latest commit from this repo.
I'm not sure what you mean by "its 2.0", this project hasn't been incrementing any version number.

Just pull the latest commit from this repo.
I'm not sure what you mean by "its 2.0", this project hasn't been incrementing any version number.

I don't even know who that is. Op here, I'm using the latest version.

I'm trying it again now and it is working. Here's a screenshot of the error I got yesterday: https://i.imgur.com/dDf5eB0.png
Not sure what happened but all is fine now.


add deployment of Storybook to Github pages

Closes #70

We also shouldn't forget about docs update 🙂

Added docs update to #76


Is there a way to change the size of the hole in the middle that frames the client?

Basically title. I want to crop the view in a bit so the time remaining numbers aren't visible within the client itself.

Hi, I'm not sure I understand what you mean.
You may use "color key" in your streaming software to make the green rectangle at the center of the screen transparent, and put whatever you desire instead. If you choose to put the League Client in place of the rectangle, it's up to you to crop appropriately in your streaming software.
There's also a way to disable the champion previews when a player hovers a champion: in config.conf, set championSplashesEnabled to false.
You can also have an image instead of the green rectangle: put the image of your choice in web/img/custom/stream_bg.png.
Hope this helps!


Add "default" and "error" fields to selector expression

Proposing to add "default" and "error" fields to selector expression like it was done for Mapper algorithm, i.e. if selector cannot find a value for requested path it will return "default" value, and if error occurs when calculating value it will return "error" value. For example,
"selector": {
  "default": "unknown",
  "error": "invalid",
  "path": [
    {
      "attr": "client_id"
    }
  ],
  "type": "string",
  "uri": "local:clients/policy"
}

If these new fields are not defined, there will be no changes in selector behavior.
Adding these fields to selector expression would give more control over expressions like
try [
  {selector1},
  {selector2},
  {selector3}
]

i.e. user could distinguish "Missing value" from other error and add appropriate handling

fixed with #231


Removed Spring Security dependency, added actual "Hello World!"

Added an index.html in the templates folder with "Hello World!"

Thanks Dylan.  I approve.


[jobset] Add prebuilt workload support.

What type of PR is this?
/kind feature

What this PR does / why we need it:
Adds prebuilt workload support for jobset.
Which issue(s) this PR fixes:

Relates to #693
Special notes for your reviewer:
Does this PR introduce a user-facing change?

Add Prebuilt Workload support for JobSets.

We can do that as a follow up.
This is assigned, but there hasn't been any progress
https://github.com/kubernetes-sigs/kueue/issues/1463

We can do that as a follow up.
This is assigned, but there hasn't been any progress
https://github.com/kubernetes-sigs/kueue/issues/1463

Sounds good, also the enablement of prebuilt support for JobSet will be indirectly tested on higher level when we have full support for JobSet in MK.
/lgtm

/lgtm


Fix _as_list method

bug fix

Preparing review...

PR Reviewer Guide 🔍
Here are some key observations to aid the review process:

⏱ Estimated effort to review: 1 🔵⚪⚪⚪⚪
🧪 No relevant tests
🔒 No security concerns identified
⚡ Recommended focus areas for review
Logic ErrorThe new implementation of _as_list method always wraps the input in a list, regardless of whether it is already a list or not. This changes the behavior of the method and could lead to nested lists where not expected.

Preparing review...

Persistent review updated to latest commit https://github.com/omriel1/langchain-milvus/commit/4330f59c59ae07f87530a09c1f56c8ee4bbff7f9

Generating PR code suggestions
Work in progress ...


Fix, Refactor, style, and Build, for the Issue: #1005

Fixed issues in the website UI/UX, and homepage also edited the code along with resolving the mess that persisted in the code before to a clear and readable code

[x] Have you renamed the PR Title meaningfully?

Related Issue

Closes: #<1005>
Description
Inside this issue I have edited the entire homepage, improved the UI/UX of the website, refactored the pre-written code removed the bugs existing in the code, fixed the duplication of code present in the code, resolved the inaccuracies, wrote the entire code again for the home page to make it readable by the future contributors and also redesigned the other related files also edited the code to make it responsive for any device size and added the dark and light mode toggle option in it work perfectly and make the website work smoothly
How Has This Been Tested? ⚙
I have tested the code previewing the outcome and also reviewing the older code with the new one along with the proper testing of the functions present inside the website
Screenshots 📷

mobile preview:

Type of change
What sort of changes have you made:
Checklist

[x] My code follows the code style of this project.
[x] My code follows the code style of this project.
[x] I have followed the contribution guidelines
[x] I have performed a self-review of my code.
[x] I have ensured my changes don't generate new warnings or errors.
[x] I have updated the documentation (if necessary).
[x] I have resolved all merge conflicts.

Video of the afterview:
https://github.com/user-attachments/assets/fe34b399-4bbc-424a-b3bf-4584138509ce

I'm rejecting this PR right now because The ui is completely different now from earlier ui.

but bro i have already mentioned that it needed a UI improvement and also it need to be improved


detect-engine-state/v2: add tests

Link to redmine ticket: https://redmine.openinfosecfoundation.org/issues/4911
Conversion:
detect-engine-state-01: DeStateSigTest03-DeStateSigTest06
detect-engine-state-02: DeStateSigTest07
detect-engine-state-03: DeStateSigTest08- DeStateSigTest10
detect-engine-state-04: DeStateSigTest01-02
Previous PR: #741
Changes:

Add tests for DeStateSigTest01-02
Add fileinfo check

I am not sure why detect-engine-state-04 does not give any alert. I think I'm doing something wrong with the pcap.

I am not sure why detect-engine-state-04 does not give any alert. I think I'm doing something wrong with the pcap.

I noticed that you are using specific calls to populate the packet with HTTP fields. I'd suggest doing like with those other tests where you added the buffers as part of a raw payload to a TCP stream... But I'm not sure how to achieve the same effect here. Maybe you could have 4 packets, where you would incrementally add the buffers together as raw payload... 🤔
We could still end up with a different behavior, since I'm not sure we can recriate the same scenario from DeStateSigTest01 with an s-v test. But I would give that a try...

Followed By: https://github.com/OISF/suricata-verify/pull/807


Add DOTNET_CLI_TELEMETRY_OPTOUT=1 to build script

For those worried about the dotnet CLI telemetry, we should set DOTNET_CLI_TELEMETRY_OPTOUT=1 in the build script. Should improve build stability on CI as well.

Fixed in https://github.com/OSVR/OSVR-Config/pull/40

Also fixed (for Windows) in https://github.com/OSVR/OSVR-Config/pull/41


Sync eng/common directory with azure-sdk-tools for PR 1467

Sync eng/common directory with azure-sdk-tools for PR https://github.com/Azure/azure-sdk-tools/pull/1467  See eng/common workflow

/check-enforcer override


mediapipe_tasks_vision_image_segmenter_imagesegmentergraph__mediapipe_tasks_components_processors_imagepreprocessinggraph__ImageToTensorCalculator

Have I written custom code (as opposed to using a stock example script provided in MediaPipe)
None
OS Platform and Distribution
MacOS 14.3.1
MediaPipe Tasks SDK version
0.10.9
Task name (e.g. Image classification, Gesture recognition etc.)
selfie_multiclass_hairr
Programming Language and version (e.g. C++, Python, Java)
Python
Describe the actual behavior
An error occurred when I entered the image of type float32
Describe the expected behaviour
It is expected to handle images of type float32
Standalone code/steps you may have used to try to get what you need
import os
from functools import reduce
import wget
import cv2, sys
import numpy as np
from PIL import Image
import mediapipe as mp

BaseOptions = mp.tasks.BaseOptions
ImageSegmenter = mp.tasks.vision.ImageSegmenter
ImageSegmenterOptions = mp.tasks.vision.ImageSegmenterOptions
VisionRunningMode = mp.tasks.vision.RunningMode

MASK_OPTION_1_HAIR = 'hair'

output_image_path = './mask.jpg'

# image = Image.open(f"{image_path}")

mask_targets = ['hair']
mask_dilation = 1

model_folder_path = 'mediapipe'
os.makedirs(model_folder_path, exist_ok=True)

model_path = os.path.join(model_folder_path, 'selfie_multiclass_256x256.tflite')
model_url = 'https://storage.googleapis.com/mediapipe-models/image_segmenter/selfie_multiclass_256x256/float32/latest/selfie_multiclass_256x256.tflite'
if not os.path.exists(model_path):
    print(f"Downloading 'selfie_multiclass_256x256.tflite' model")
    wget.download(model_url, model_path)

options = ImageSegmenterOptions(base_options=BaseOptions(model_asset_path=model_path),
                                running_mode=VisionRunningMode.IMAGE,
                                output_category_mask=True)

def get_mediapipe_image(numpy_image: Image) -> mp.Image:
    # Convert gr.Image to NumPy array
    # numpy_image = cv2.imread(numpy_image)
    image_format = mp.ImageFormat.VEC32F1

    # Convert BGR to RGB (if necessary)
    if numpy_image.shape[-1] == 4:
        image_format = mp.ImageFormat.VEC32F1
    elif numpy_image.shape[-1] == 3:
        image_format = mp.ImageFormat.VEC32F1
        numpy_image = cv2.cvtColor(numpy_image, cv2.COLOR_BGR2RGB)

    return mp.Image(image_format=image_format, data=numpy_image)

def process(image):
    # Create the image segmenter
    with ImageSegmenter.create_from_options(options) as segmenter:

        # Retrieve the masks for the segmented image
        media_pipe_image = get_mediapipe_image(numpy_image=image)

        segmented_masks = segmenter.segment(media_pipe_image)

        masks = []
        for i, target in enumerate(mask_targets):
            mask_index = 1  # Hair mask index
            masks.append(segmented_masks.confidence_masks[mask_index] if i == 0 else np.zeros(media_pipe_image.shape[:2], dtype=np.uint8))

        image_data = media_pipe_image.numpy_view()

        # convert the image shape from "rgb" to "rgba" aka add the alpha channel
        if image_data.shape[-1] == 3:
            image_shape = (image_data.shape[0], image_data.shape[1], 4)
            alpha_channel = np.ones((image_shape[0], image_shape[1], 1), dtype=np.uint8) * 255
            image_data = np.concatenate((image_data, alpha_channel), axis=2)

        image_shape = image_data.shape

        mask_background_array = np.zeros(image_shape, dtype=np.uint8)
        mask_background_array[:] = (0, 0, 0, 0)
        image_array = np.zeros(image_shape, dtype=np.uint8)
        image_array[:] = (255, 255, 255, 255)

        mask_arrays = []

        for i, mask in enumerate(masks):
            condition = np.stack((mask.numpy_view(),) * image_shape[-1], axis=-1) > 0.25
            mask_array = np.where(condition, image_array, mask_background_array)
            # mask_array = np.where(condition, image_data,mask_background_array)
            mask_arrays.append(mask_array)

        # Merge our masks taking the maximum from each
        merged_mask_arrays = reduce(np.maximum, mask_arrays)

        # Dilate or erode the mask
        if mask_dilation > 0:
            merged_mask_arrays = cv2.dilate(merged_mask_arrays, cv2.getStructuringElement(cv2.MORPH_ELLIPSE, (2*mask_dilation + 1, 2*mask_dilation + 1), (mask_dilation, mask_dilation)))
        elif mask_dilation < 0:
            merged_mask_arrays = cv2.erode(merged_mask_arrays, cv2.getStructuringElement(cv2.MORPH_ELLIPSE, (2*mask_dilation + 1, 2*mask_dilation + 1), (mask_dilation, mask_dilation)))

        # Create the image
        mask_image = Image.fromarray(cv2.cvtColor(merged_mask_arrays, cv2.COLOR_BGR2RGB))
        mask_image.save(output_image_path)
        mask_image_np = np.array(mask_image)
        return mask_image_np.astype('float32')

image = sys.argv[1]
im = cv2.imread(image)
h, w, _ = im.shape
inputs = cv2.resize(im, (480, 480))
inputs = inputs.astype('float32')
inputs.shape = (1,) + inputs.shape
inputs /= 255
process(inputs)

Other info / Complete Logs
python3 mult_test.py ./IMG313.jpg
WARNING: All log messages before absl::InitializeLog() is called are written to STDERR
I0000 00:00:1712389878.567908       1 gl_context.cc:344] GL version: 2.1 (2.1 Metal - 88), renderer: Apple M1 Pro
INFO: Created TensorFlow Lite XNNPACK delegate for CPU.
E0000 00:00:1712389878.577591       1 calculator_graph.cc:876] INVALID_ARGUMENT: CalculatorGraph::Run() failed:
Calculator::Process() for node "mediapipe_tasks_vision_image_segmenter_imagesegmentergraph__mediapipe_tasks_components_processors_imagepreprocessinggraph__ImageToTensorCalculator" failed: Unsupported format: 9
Traceback (most recent call last):
  File "/Users/kangjian/media/mult_test.py", line 63, in process
    segmented_masks = segmenter.segment(media_pipe_image)
  File "/Users/kangjian/miniconda3/envs/mediapipe/lib/python3.9/site-packages/mediapipe/tasks/python/vision/image_segmenter.py", line 302, in segment
    output_packets = self._process_image_data({
  File "/Users/kangjian/miniconda3/envs/mediapipe/lib/python3.9/site-packages/mediapipe/tasks/python/vision/core/base_vision_task_api.py", line 95, in _process_image_data
    return self._runner.process(inputs)
ValueError: CalculatorGraph::Run() failed:
Calculator::Process() for node "mediapipe_tasks_vision_image_segmenter_imagesegmentergraph__mediapipe_tasks_components_processors_imagepreprocessinggraph__ImageToTensorCalculator" failed: Unsupported format: 9

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/kangjian/media/mult_test.py", line 115, in <module>
    process(inputs)
  File "/Users/kangjian/media/mult_test.py", line 106, in process
    return mask_image_np.astype('float32')
  File "/Users/kangjian/miniconda3/envs/mediapipe/lib/python3.9/site-packages/mediapipe/tasks/python/vision/core/base_vision_task_api.py", line 226, in __exit__
    self.close()
  File "/Users/kangjian/miniconda3/envs/mediapipe/lib/python3.9/site-packages/mediapipe/tasks/python/vision/core/base_vision_task_api.py", line 209, in close
    self._runner.close()
ValueError: CalculatorGraph::Run() failed:
Calculator::Process() for node "mediapipe_tasks_vision_image_segmenter_imagesegmentergraph__mediapipe_tasks_components_processors_imagepreprocessinggraph__ImageToTensorCalculator" failed: Unsupported format: 9

image_format = mp.ImageFormat.SRGB
if numpy_image.shape[-1] == 4:
image_format = mp.ImageFormat.SRGBA
elif numpy_image.shape[-1] == 3:
image_format = mp.ImageFormat.SRGBIf I change this to mp.ImageFormat.SRGB, I get the following error:

image_format = mp.ImageFormat.SRGB     if numpy_image.shape[-1] == 4:         image_format = mp.ImageFormat.SRGBA     elif numpy_image.shape[-1] == 3:         image_format = mp.ImageFormat.SRGB    If I change this to mp.ImageFormat.SRGB, I get the following error:     Traceback (most recent call last):
File "/Users/kangjian/media/mult_test.py", line 115, in
process(inputs)
File "/Users/kangjian/media/mult_test.py", line 61, in process
media_pipe_image = get_mediapipe_image(numpy_image=image)
File "/Users/kangjian/media/mult_test.py", line 53, in get_mediapipe_image
return mp.Image(image_format=image_format, data=numpy_image)
RuntimeError: float image data should be either VEC32F1, VEC32F2, or VEC32F4 MediaPipe image formats.

Hi @kinarr,
I can replicate the problem in Colab Gist, as indicated by @tarakang. I encounter the same error message: "failed: Unsupported format: 9". For now, this issue does not appear to be specific to macOS. Could you please have look into this issue? From our standpoint, it appears to be a legitimate bug.
Thank you!!

@kuaashish I believe it's caused by the limited Image formats supported by MediaPipe but there should be a way to normalize the inputs so that it can passed through to the model. Lemme take a look.

Oh and there's no need to preprocess the inputs like this:
inputs = inputs.astype('float32')
inputs.shape = (1,) + inputs.shape
inputs /= 255

Please see the following for the correct usage of the API:
https://github.com/google/mediapipe/blob/7dcf9ae0e6ec82559e7e733ff71063960650874e/mediapipe/tasks/cc/vision/image_segmenter/image_segmenter_test.cc#L99
https://github.com/google/mediapipe/blob/7dcf9ae0e6ec82559e7e733ff71063960650874e/mediapipe/tasks/cc/vision/image_segmenter/image_segmenter_test.cc#L381
These are C++ API calls but it should be similar for Python.

@tarakang @kuaashish Here's the working notebook for your reference: https://colab.research.google.com/drive/1B0mPPfcWCyr07CBwXgraBIkdqri5BGff?usp=sharing

The model card for the MediaPipe Selfie Segmentation model provides essential information about the expected input format for the model. So PTAL here: https://mediapipe.page.link/selfiesegmentation-mc

@tarakang I've added your image utility (get_mediapipe_image) in the notebook so you can uncomment it and try it out too and it should work fine.

Hi @kinarr,
Thank you, @tarakang. It appears there may be an issue with the limited image format support in Mediapipe. Could you kindly test the provided working notebook and inform us if the issue persists?
Thank you!!


evalcap preparation

Thanks for sharing the amazing work. Here I encounter a problem that I have to run the script in conda envs, instead of dockers. From the setup.sh, maybe /evalcap/coco_caption and /evalcap/cider are required in the project, as the error information:
Traceback (most recent call last):
  File "/home/SwinBERT/src/tasks/run_caption_VidSwinBert.py", line 22, in <module>
    from src.evalcap.utils_caption_evaluate import evaluate_on_coco_caption
  File "/home/SwinBERT/src/evalcap/utils_caption_evaluate.py", line 13, in <module>
    from .coco_caption.pycocotools.coco import COCO
ModuleNotFoundError: No module named 'src.evalcap.coco_caption'

Is there any instruction to prepare coco_caption and cider? Thanks for your attention!

hello, I want to run the project in conda envs too, but it seems that the eval source codes are not provided. Have you solved the problem? Thanks!

Hi,Have you solved the problem? Thanks!


autoload is not working

After creating  a custom installer the files moves to the given dir but the auto load doesn't work anymore.

Hey @sunel are you able to provide more information. I don't think there is enough information here to help you.

i have created a new installer that will move the package to custom location. The files are moved correctly , but once the package is moved the "autoload" config that is given is not considered any more.

Are you able to provide the code of the new installer, and also provide what your expectation is (like the location of the code etc).

Check this links for files
https://gist.github.com/sunel/fb4551be185eddfa9c45be94168613c4
when i run using the given composer.json
the package moves to the correct location as given in the
root
Modules
Admin
But the autoload

"autoload-dev": {
    "psr-4": {
      "Modules\\Admin\\": "src/"
    }
  },

this doesn't work any more

@camspiers any updates on this


Fixing #797 by adding Birthday input on passenger selection.

As an alternative we could give only categories as options, which might be closer to how it would be handled in a real life scenario, but the manual approach allows for more flexibility in testing.

Well, the issue is that passenger.id is assigned by the API, not the client. Client app can only produce the externalRefs and use them for reference in offer and also booking stage when full passengers get created.
Indeed, you are right on "passenger categories". We have developed a proprietary resource that reads all possible passenger categories for given retailer, and return tuples (string label, osdm anonymous passenger specification to send) so you can only copy the specification to offer request.

Well, the issue is that passenger.id is assigned by the API, not the client. Client app can only produce the externalRefs and use them for reference in offer and also booking stage when full passengers get created.

oh I see, so the earliest we know the passenger id is after requesting a booking?

Well, the issue is that passenger.id is assigned by the API, not the client. Client app can only produce the externalRefs and use them for reference in offer and also booking stage when full passengers get created.

oh I see, so the earliest we know the passenger id is after requesting a booking?

That's right. Pax Spec has reduced content compared to Pax (misses personal details
protected by GDPR). Also Pax Spec has much shorter retention also due to data protection.