cloudstack driver

This is a fully working and tested CloudStack driver for docker machine. All info needed to use this driver for your (private) CloudStack setup can be found in the updated README.
Of course there are a lot of use cases (different CloudStack setups) that could need more and/or other options to make the driver also work for those use cases. But since this is not predictable and this is currently tested with standard basic and advanced zones, most use cases should be covered without additional work.
This PR is a follow up of PR #129
Signed-off-by: Sander van Harmelen<EMAIL_ADDRESS>

@dduportal would be great if you (and anyone else who's up for it) could give this a few test runs...

@svanharmelen Which kind do you expect exactly :

Use case scenarii in a markdown doc or here ?
Path to a end-to-end testing (devcloud VM with automated tests)
Go functionnal tests ?
Basic shell script running our machine tests

?
(I just want to be sure :) )

@dduportal well I don't expect anything really... I know you tested the driver before when it was just build and since it now changed quite a lot it would be nice if you can confirm your use cases still work as expected with the updated code.
The use cases I have myself are tested of course, but it would be nice to have some feedback and/or confirmations from other users.
And well... If your up to it, by all means write all the test you would like to add! Adding tests (both unit tests and functional tests) are still on the todo list.
If you want I can make you an collaborator of my machine fork so you can work in there and merge your PR's in there so they'll end up in this PR. On the other hand I also spoke with @ehazlett on IRC this afternoon and hopefully it will not take long anymore before we can merge this. Most likely as soon as v0.1.0 is release which is close to being done..

Testing will be done around the end of the week (can't make access to our CS before)

Hi svanharmelen,
I tried to apply this patch and got this error.  Any reason this could be the case?  I cloned the original machine repo, used wget to download the patch (425.patch) and used "git am" to patch.  I'm running all this on a coreos VM.  Could you please take a look and see what the issue is?
Kind regards,
coretezone

@cortezone what error did you get? As I notice that it needs to be rebased again (that almost seems to become a daily task lately) I assume a build error?
Will try to update the PR so it can be build/merged again.

The errors are as follows:
error: patch failed: README.md:266
error: README.md: patch does not apply
error: patch failed: commands.go:16
error: commands.go: patch does not apply
From: Sander van Harmelen<EMAIL_ADDRESS>Sent: 10 February 2015 04:58 PM
To: docker/machine
Cc: YUUNI, OSAY OSMAN
Subject: Re: [machine] cloudstack driver (#425)
@cortezonehttps://github.com/cortezone what error did you get? As I notice that it needs to be rebased again (that almost seems to become a daily task lately) I assume a build error?
Will try to update the PR so it can be build/merged again.
—
Reply to this email directly or view it on GitHubhttps://github.com/docker/machine/pull/425#issuecomment-73712417.

@cortezone just rebased the PR so it should be good now...

@svanharmelen works great thanks!

@svanharmelen, hi.  I'm facing some issues with the cloudstack driver.  I've successfully built the binary and when I run it I get some syntax errors.  I need guidance.  Here's an example and the errors generated:
./machine create -d cloudstack --cloudstack-api-url="http://<IP_ADDRESS>/client/api"--cloudstack-template="coreos-production-xen-image" --cloudstack-offering="Container Instance" --cloudstack-api-key=FXHM348BTmSfn00000y4rk26Px6dTJYMBOHagJZrBytHLENIlYBp-z0J0r-YX4atcbOpTSOx0642duMUM99WDg --cloudstack-secret-key=zpSidvvP0Fwia-EsSxRyl5bEOa5lusP2vvxvsUSZuOt5D2tFI3-ohHqO5rooCv7vgd_yE-IIxveMq7W0L4ZjEA --cloudstack-no-public-ip=yes --cloudstack-zone="DEVZONE" node01
ERRO[0000] Error creating machine: cloudstack driver requires the --cloudstack-public-ip option
WARN[0000] You will want to check the provider to make sure the machine and associated resources were properly removed.
FATA[0000] Error creating machine
TIA
@cortezone

Hi @svanharmelen my bad.  I fixed the syntax and it's working.  I assumed that the cloudstack-no-public-ip required an argument hence the mistake.
Thanks for the good work.  One question though. Can I use for instance an Ubuntu template and still get it install Docker?  My test used a CoreOS template.

@cortezone currently the driver is expecting a CoreOS image (see README), but I guess it would be nice to extend that later on so you can also use Ubuntu or EL...

@cortezone we will need to use Ubuntu 14.04 for the drivers.  That's what we have standardized on for now.  In the future we are planning to use cloudinit to allow for customization.

Thanks @svanharmelen and @ehazlett.  I bumped into an issue using the driver today.  I launched a machine on CoreOS and it supposedly failed though the VM was created and I could use the instance in ACS GUI but Docker-Machine returned an error about an exit code of 255.  Error creating machine: exit status 255. Googling I saw something about vm name with "." or "-" not supported for the DigitalOcean driver though later retracted.  I've tried with vm name without "." or "-" but I get the same error though the VM gets created.
ERRO[0230] Error creating machine: exit status 255
WARN[0230] You will want to check the provider to make sure the machine and associated resources were properly removed.
FATA[0230] Error creating machine

Usually that's networking related I believe.  The "." and "-" was not an
issue or at least didn't appear to be.  I successfully created using both
and the OP never responded with any more debugging / issues.  It could be a
race condition with the instance being "up" but ssh not responding or ready
yet.
On Wed, Feb 11, 2015 at 2:29 PM, cortezone<EMAIL_ADDRESS>wrote:

Thanks @svanharmelen https://github.com/svanharmelen and @ehazlett
https://github.com/ehazlett. I bumped into an issue using the driver
today. I launched a machine on CoreOS and it supposedly failed though the
VM was created and I could use the instance in ACS GUI but Docker-Machine
returned an error about an exit code of 255. Error creating machine: exit
status 255. Googling I saw something about vm name with "." or "-" not
supported for the DigitalOcean driver though later retracted. I've tried
with vm name without "." or "-" but I get the same error though the VM gets
created.
ERRO[0230] Error creating machine: exit status 255
WARN[0230] You will want to check the provider to make sure the machine
and associated resources were properly removed.
FATA[0230] Error creating machine
—
Reply to this email directly or view it on GitHub
https://github.com/docker/machine/pull/425#issuecomment-73947281.

@ehazlett check about Ubuntu 14.04 being the standardised OS for machine drivers. I'll update this PR accordingly within the coming days so it complies to that.
@cortezone did it happen once, or can you reproduce the problem?

@svanharmlen this happened on three occasions with coreos and centos templates.  Will try with ubuntu 14.04 template tomorrow.

@cortezone the driver will currently not work with CentOS and/or Ubuntu (unless your templates have cloud-init running on them)

@svanharmelen and @ehazlett, I've tried with a Ubuntu 14.04 template and the result is the same.  I can ssh into the machine created so I guess the network is up.  If there's a timeout installing the ssh keys it might be because it takes time for the network to come up as the vm is created.
INFO[0000] Creating SSH key pair...
INFO[0000] Creating CloudStack instance...
INFO[0072] Stopping Docker...
ERRO[0072] Error creating machine: exit status 255
WARN[0072] You will want to check the provider to make sure the machine and associated resources were properly removed.
FATA[0072] Error creating machine

We are going to be refactoring the internals a bit very soon to help
alleviate the variance in the driver stack.  This should help with basic
things like ssh etc.  Also, you shouldn't need to use cloudinit at the
moment (we are hoping to move to that in the future and you won't have to
do anything in your driver for that).  Right now, all of the provider
drivers are installing from the docker apt repos.
On Thu, Feb 12, 2015 at 3:44 AM, cortezone<EMAIL_ADDRESS>wrote:

@svanharmelen https://github.com/svanharmelen and @ehazlett
https://github.com/ehazlett, I've tried with a Ubuntu 14.04 template
and the result is the same. I can ssh into the machine created so I guess
the network is up. If there's a timeout installing the ssh keys it might be
because it takes time for the network to come up as the vm is created.
INFO[0000] Creating SSH key pair...
INFO[0000] Creating CloudStack instance...
INFO[0072] Stopping Docker...
ERRO[0072] Error creating machine: exit status 255
WARN[0072] You will want to check the provider to make sure the machine
and associated resources were properly removed.
FATA[0072] Error creating machine
—
Reply to this email directly or view it on GitHub
https://github.com/docker/machine/pull/425#issuecomment-74035990.

Hey guys,
patch application issues arising again.  Still with the README.md:306 patch does not apply.  Has this been rebased recently?
@cortezone

@cortezone do you still have the issue? I see that the PR is still good to be merged automatically, so I would not expect any merge errors...

Not sure what I'm doing wrong but this is what I get when I try to patch using
git am < 425.patch
Applying: cloudstack driver
error: patch failed: README.md:306
error: README.md: patch does not apply
Patch failed at 0001 cloudstack driver
The copy of the patch that failed is found in:
/root/machine/.git/rebase-apply/patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

Please go ahead and merge.  I believe the error must be coming from something in my environment.  Looks crazy though.

@cortezone check... Not able to merge though, as we will need one more refactor to make the driver work with Ubuntu 14.04 and the default Docker apt repos...

@svanharmelen you may want to hold off for a bit longer.  we are working on the driver refactor which will be (hopefully) the last time you need to make changes to the driver as far as machine is concerned.  this is the last refactor to get all of the pending drivers on the same page and have them merged.  #756 is the issue if you want to track.  thanks!

@svanharmelen and @ehazlett,
I run the patch with a 3 way merge.  After a successful build I tried to create a machine (CoreOS template) but this failed.  The Cloud-init script couldn't get the ssh keys.  Below are the errors I could pick up.
machine create output:
INFO[0000] Creating CA: /root/.docker/machine/certs/ca.pem
INFO[0002] Creating client certificate: /root/.docker/machine/certs/cert.pem
INFO[0003] Creating SSH key pair...
INFO[0004] Creating CloudStack instance...
ERRO[0041] Error creating machine: error installing docker: exit status 255
WARN[0041] You will want to check the provider to make sure the machine and associated resources were properly removed.
FATA[0041] Error creating machine
CoreOS console stuff showing failure of ssh key fetch:
[  OK  ] Reached target Login Prompts.
[  OK  ] Started Authorization Manager.
[  OK  ] Reached target Multi-User System.
[  OK  ] Stopped Sets SSH key from metadata.
Starting Sets SSH key from metadata...
[  OK  ] Started Modifies /etc/environment for CoreOS.
[    9.491095] cloudstack-ssh-key[654]: Adding/updating cloudstack:
[    9.498895] cloudstack-ssh-key[654]: /home/core/.ssh/authorized_keys.d/cloudstack.hYBiW54Mjn is not a public key file.
[FAILED] Failed to start Sets SSH key from metadata.
See "systemctl status cloudstack-ssh-key.service" for details.
[  OK  ] Stopped Cloudinit from CloudStack-style metadata.
Starting Cloudinit from CloudStack-style metadata...
[  OK  ] Reached target Run Docker containers before main Docker starts up.
Starting Docker Application Container Engine...
[  OK  ] Started Docker Application Container Engine.
[  OK  ] Started Cloudinit from CloudStack-style metadata.
[  OK  ] Started Load cloud-config from /usr/share/oem/cloud-config.yml.
[  OK  ] Reached target Load system-provided cloud configs.
[  OK  ] Reached target Load user-provided cloud configs.
[   10.188622] ip_tables: (C) 2000-2006 Netfilter Core Team
[   10.262409] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.

VM was created as per instance running in ACS web gui but of course I can't access it without ssh key.

Surprise surprise.  Apparently the keys were successfully uploaded and I could login with the key found at ~/.docker/machine/machines/<machine_name>.  CoreOS reports however that two units failed
CoreOS stable (557.2.0)
Failed Units: 2
cloudstack-ssh-key.service
docker.service

@ehazlett thanks! Will keep an eye on #756 and refactor this one to align it right after it's merged... Will contact you as soon as that is done so we can review and (hopefully) get this one merged...

@cortezone it could very well be that some things have changed between the moment this PR was created and current HEAD, that is causing issues when trying to use this PR and HEAD together.
As @ehazlett pointed out a refactor/update of the driver layout is forthcoming, so I'll purpose to not invest time in testing/debugging this PR until the refactor of the driver layout is done and this PR is refactored accordingly.
After that any testing would be more then helpful in getting the PR merged so we no longer have to keep refactoring and just use HEAD :wink:

@ehazlett I noticed PR #756 is now merged... So would this be the right moment to refactor this driver and right afterwards review it? If so I'll make time for the refactor coming Monday.
Would be really nice if we can finally get this one in...

@svanharmelen yes.  i'm working on driver docs probably next week so if you want to start that would be great to get your feedback and make sure we don't miss anything.  thanks!

@svanharmelen @ehazlett We want to start trying this driver, please kindly advise should we grab the fork or patiently wait you guys finish the refectoring? :)
Best,
Dong

@xied75 I think it would be smart to wait for the refactor... I'll have that planned for coming Monday, so if you can wait a few days...
Otherwise you could of course already try and play with this one, but currently it needs a CoreOS image (see the readme for more info).

thanks @svanharmelen for your hard work on this. @ehazlett just so you know, there quite a few cloudstack cloud users who want to use machine and need this driver (same for the exoscale driver that is also cloudstack based).  so you have a big +1 from the cloudstack community to merge this. thx

@runseb Thx! I was planning to update the PR today to be inline with the latest guidelines, but other prio's prevented me from doing so :disappointed:
But I'll expect to be able to do so before the end of this week...

good to hear, thanks for sticking to it.

any updates on this? could use it as well...

Well... It's on my agenda for a while now, but things are way to busy to get anything done. Really hope to be able to make some time for this coming week...

I must admit I'm having difficulties finding time to pick this one up... So if there is anyone out there who can/will step in, I'm more then willing to donate the code currently in this PR to you so it can be refactored and hopefully merged...

let me see. I might do it myself, but I will ask on the cloudstack list

@runseb and? Any takers?
@dduportal don't know if you still use this or want to use it? As our company hardly uses any Docker I simple cannot find time to sit down for this (even through I don't believe updating this PR would be that much work, but still). So if you're interested you can just copy over the code to your fork and create a new PR based on that. I will then close this PR...
Let me know your thoughts! If nobody cares anymore, I'll just close this PR and call it a day :wink:

Hi !
Sorry, our Cloudstack may (or may not) be replaced by another tech., discussions are going up, so i don't have more time those days.
I'm still interested anyway, to replace our vagrant + vbox stack by a docker-machine + b2d one.
I need time to check the changes, so you can close, we'll repopen a new one in the future when needed : it'll help maintainers to have a clear view I think.

@dduportal thanks for your update! Will wait just a little more (also for @runseb his reaction) and if nothing happens will indeed close this one...

@svanharmelen give me another week. I am traveling right now.

@runseb sure, no problem...

Hi @svanharmelen , @runseb , @dduportal
I want generic cloudstack driver to use docker machine on advanced zone.
I can have some time to write some code if it is needed.
Is there anything I can do?

@atsaki that would be great. We need to refactor this driver according to the exoscale driver that was recently merged. The go driver for cloudstack needs to be updated...

@atsaki sounds good! I think the easiest way forward is you just copy the code in this PR (branch: https://github.com/svanharmelen/machine/tree/f-cloudstack-driver) to a new fork of the machine repo. Then if your ready to make a PR just give me a ping. I will then close this PR and refer to your new PR.
Does that sound like a plan?

Hi @svanharmelen ,
Sorry for late reply.
I opened a new PR #1323.
I copied the code from your branch and modified to support basic zone and swarm.

Closing this PR in favour of PR #1323
Just gave my feedback on the code there, so that one should become the main PR for adding CloudStack support.


NTAG216 Set Lock Bit with Password.

NTAG213/6 has the ability to set lock bits which means a user can provide a password to set the tag as read only and then set a password again to change the tag to writable.
"Configurable password protection with optional limit of unsuccessful attempts" - Source: http://www.nxp.com/documents/data_sheet/NTAG213_215_216.pdf
Reading on a functioning implementation available at: http://stackoverflow.com/questions/31734059/android-error-when-resetting-dynamic-locks-on-nfc-ntag213-28h
I would expect this would be an android only implementation as I doubt other providers expose the required methods.  I'm comfortable with that.
I would expect behaviour such as nfc.lockWithPassword(1234, onSuccess, onFailure); would be the correct approach.  1234 would be the password, I expect we would need to limit the # of digits and allow only for integers..

Might be related to #176

Hey, any updates or PR's on password protected ntag216?


Big Picture View/Insights

Seeing insights for each contact, email, event, website, etc. is fine and good, however, I don't understand how I can see an all up view of all activities. E.g. Total Number of Clicks for All Emails, or All Events, or All Pages. Trending information for these activities? Ability to see these all on a dashboard?

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

ID: 6a5a9d2c-83d6-ce34-3e6a-4a1a553bd7bb
Version Independent ID: b00bbb9c-2e44-735a-82d2-2146810a15df
Content: Analyze marketing results and gain insights (Dynamics 365 for Marketing)
Content Source: ce/marketing/insights.md
Service: crm-online
GitHub Login: @kamaybac
Microsoft Alias: kamaybac

@mhammons , we do supply several Marketing dashboards, and an events dashboard, out of the box. You can find them by going to the dashboard (from the navigator) and then choosing among the available dashboards using the view selector, which is a drop-down list on the page title, just below the command bar. Do those give you what you are looking for?

Thank you for your detailed reply and screenshots, @mhammons. It looks like this is probably a feature request rather than documentation feedback (though it looks like we could also improve this topic by mentioning the dashboards here). I was about to send you to our product forum to submit this idea there, but I can see you already have! So, thanks again for that.


gds file

Please also check my uploaded file

@Sahar-Safarloo
Please put the file in the "submissions" folder.


:memo: About section for Several Task page

Added about.md for Zero-shot-object-detection, text-to-3d and mask-generation. Also added use cases for them all.

@merveenoyan
Hey, I have added the changes you suggested. Thank you so much for your time.

@merveenoyan
Hey, I have made the changes.
Changed .vscode/setting.json back to its original content (from this repository).
Removed the dataset 3D-Future from data.ts. Will find it and add to the hub and then maybe modify this file again to mention it.

@merveenoyan
Hi again, I have changed that file. If it still crashes the checks, I'll just open a new PR and ensure to not commit any changes to .vscode folder.
Thank you

@rajaryan18 can you merge this PR into your branch? https://github.com/rajaryan18/huggingface.js/pull/1 this will lint your code so the tests pass

I fixed the conflicts and brought this up to date, but the linter still fails for some reason cc @coyotte508 @merveenoyan

Thank you @coyotte508! Merging now, thanks @rajaryan18 for the contribution and sorry for the delay 🙌


added fine tuned models in conf.py, renamed some

I moved my local repo to another partition and stupidly git thinks all files changed.... so don't worry..

👌


why do i need to CREATE_NEW_USERS?

Hi,
why is CREATE_NEW_USERS needed? i am using DRF as API server only (no direct access at all) with azure, and can pass the idToken i get from the frontend to my django DRF backend to validate, successfully.
now, since there is no direct access to django, i'm not looking to track users in the backend, simply validate their token and proceed. however, if i set CREATE_NEW_USERS   to false (and the user was not created before, i get  django_auth_adfs User '...' doesn't exist and creating users is disabled.
what is the use of a user being created for such a scenario? and if not - can i avoid creating them?

Funding

You can sponsor this specific effort via a Polar.sh pledge below
We receive the pledge once the issue is completed & verified

Not sure if I understand what you're asking?
The setting is pretty clearly described in the docs.

This is the documentation:
Determines whether users are created automatically if they do not exist.

If set to False, then you need to create your users before they can log in.

But my users are already created, in azure. I don't need an entry in the database for the user, but it seems like I cannot avoid it

@ehudkaldor It sounds like you want some other type of class to represent the user besides a User model. If that's correct, what you're looking for isn't provided out of the box by django-auth-adfs.
You're effectively trying to remove django.contrib.auth entirely from the project. Which is probably fine, but that's outside of the scope of this library.
You can use it for inspiration, or even as a base for your own integration. You might be able to patch something together by subclassing AdfsAuthCodeBackend or AdfsAccessTokenBackend, then customizing process_access_token to only do the authentication and authorization bits.
I'm going to close this as a won't fix.

no, that is fine. i was mostly wondering if it could be done, but i understand now that it cannot, without a major hassle.
my main problem is that it creates credentials, along with user and pass, locally. i don't know if a user can login using those (they should not get the password, anyway), but having it there, without me needing or using it to auth, feels like something that should not be.

@ehudkaldor it creates a user record, but they are created with an unusable password. You can confirm this by reviewing the library's code.

Correct, they are not able to use that password. It's a Django built-in 😊


Added Travis CI build status icon to README

Thanks for your PR @ltfschoen  . We now have our CLA in place. Please rebase your PR and sign the CLA.


feat: npm package vulnerabilities fix

NPM audit and fix

I think the dependencies on this PR is latest, please reopen this one I'll close mine.


fix(react-vapor): remove ts-transformer-keys

Proposed Changes
Remove custom typescript transformer to generate arrays from interfaces.
Potential Breaking Changes
Might have changed how some interfaces related to the tableWithNewPagination are exported, but the type of this interface was in error.
Acceptance Criteria

[ ] The proposed changes are covered by unit tests
[ ] The potential breaking changes are clearly identified
[ ] README.md is adjusted to reflect the proposed changes (if relevant)

It will probably sound basic, but why did we use this package before and why are we removing it now? was it only for its utility that we used it? if so, we do we remove it now?
Regards,
Félix Blais

It will probably sound basic, but why did we use this package before and why are we removing it now? was it only for its utility that we used it? if so, we do we remove it now?
Regards,
Félix Blais

Very relevant question. Here are the pros and cons of using this lib I can think of that helps understanding the whys of this change.
Pros (or why it was added)

Ease of use, it requires less effort to list the props we want to omit, because the compiler does it for us
If an interface changes, we don't have to think about manually changing the array of props to omit

Cons (or why we're removing it)

Adds complexity to the build process. We have to use a custom transformer to the typescript compiler to make it work.
Slows down the transpilation because the compiler has to run an additional step
When using this you cannot turn off the type checking to speed up the build (transpileOnly: true) or else it won't have information about the interfaces keys.
Having the arrays of props to omit dynamic makes you less aware of what props are omitted or not (more error prone)


[BEAM-12918] Add PostCommit_Java_Tpcds_Dataflow job

[BEAM-12918] Add PostCommit_Java_Tpcds_Dataflow job

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

 Thanks or merging!


Fix: o11y-definition bad defs and update the prism image

Description of your changes
Related to https://github.com/kubevela/kubevela/issues/6113

How has this code been tested?

Checklist

I have:

[ ] Title of the PR starts with type (e.g. [Addon] , [example] or [Doc]).
[ ] Updated/Added any relevant documentation and examples.
[ ] New addon should be put in experimental.
[ ] Update addon should modify the version in metadata.yaml to generate a new version.

Verified Addon promotion rules
If this pr wants to promote an experimental addon to verified, you must check whether meet these conditions too:

[ ] This addon must be tested by addon's e2e-test to guarantee this addon can be enabled successfully.
This addon must have some basic but necessary information.

[ ] An accessible icon url and source url defined in addon's metadata.yaml.
[ ] A detail introduction include a basic example about how to use and what's the benefit of this addon in README.md.
[ ] Also provide an introduction in KubeVela documentation.
[ ] It's more likely to be accepted if useful examples provided in example dir.

@somefive, I tried to use older version of kubeveal - 1.8.2 and it resolved the problem - thanks !


Discard signature_check job,check image signature directly

[wewang@fedora release-tests]$ python cli -r 4.13.2 image-signed-check
2023-06-21T09:01:18Z: INFO: task [Payload image is well signed] status is changed to [In Progress]
sha256:6ef3cf4bed1970d547dce08a6e334b675d361b212xxxxxxxxxxxxxxxxxxx
Comparing digest from url: https://mirror.xxxxxx.com/pub/xxxxx-xx/signatures/xxx/release/sha256=6ef3cf4bed1970d547dcxxx4b675d361b2xxxxxxxxxxxxxxxxxxxxxxxxx/
request status code 200
Signature check PASSED
2023-06-21T09:01:25Z: INFO: task [Payload image is well signed] status is changed to [Pass]

@rioliu-rh  Please review it, thanks

/lgtm


More tests and changes of data from numeric to character

Travis encountered this error message:
Error in setwd("F:/U/Annualreport/nfsnsitedata/WY2014/") :
    cannot change working directory
  Calls: test_check ... lapply -> FUN -> sys.source2 -> eval -> eval -> setwd

Ahh, the Travis test has failed because it can't find the dplyr library. When we want to leverage a new package, we need to add it to the DESCRIPTION file so that our automated tools (Rstudio, Travis, Jenkins, etc) know which packages to download and install. There are two relevant sections of the DESCRIPTION file: Imports and Suggests. Imports is for packages that need to be available to the code in the R/ directory. Suggests is for packages that need to be available to the code in the tests/ directory. So in this case, if you add dplyr to the Suggests field, the Travis build should pass, or at least get a lot further :)

The Travis build is passing once more! Merging time!


Webview tooltips

As a user, I would like to see extra information about my tabs by hovering over the title so I can get the information I need at a glance.
As an extension developer, I want to specify webview tab tooltips so users can get the information they need.

Like in Paratext 9, web view providers should be able to specify a tooltip for their webview tab:

This could hopefully simply be on the WebViewDefinitionBase in web-view.model.ts and carried along from the webview provider.
It should also be updatable, so it needs to be added to WebViewDefinitionUpdatableProperties (and the code using it) as well.

Fixed in #657

Hi, tooltips also appear in the overflow menu, which makes it hard to select other items. So there they should be hidden in my opinion.

We closed this for now. When the UX question is resolved, please open a new issue.


Ceph Object Storage

We need object storage as a service in Deis v2. The likely candidate is Ceph OS Gateway.

With deis/minio and deis/riak, should we also close this out?


Zod is calling addIssueToContext when no error is happening

I noticed since 3.10 (new parsing engine) that we call addIssueToContext whenever we use an enum with union. See:
3.11:

3.9:

After digging further, I noticed it's coming from here: https://github.com/colinhacks/zod/blob/cc8ad1981ba580d1250520fde8878073d4b7d40a/src/types.ts#L2820-L2826
Seems like the union is mapping through all the items and still calling error in the new parsing engine, whereas that wasn't the case before.
Fix is to downgrade to 3.9 unfortunately.

@colinhacks makes sense - I think this has caused a huge slowness in recent versions of zod. Probably 2x more


Fix IDE0003

Don't qualify member properties/methods/etc. with this - https://docs.microsoft.com/en-us/dotnet/fundamentals/code-analysis/style-rules/ide0003-ide0009
Note that this (and a few other rules) currently can't fail the build by design.
See https://github.com/dotnet/roslyn/issues/53215 for the reason why and https://github.com/dotnet/roslyn/blob/main/src/Analyzers/Core/Analyzers/EnforceOnBuildValues.cs#L106 for the list of rules that this happens for.

I'm curious about this one. For properties (just taking an example), there seems like there's a benefit to being explicit here, and not hunting for a variable that could be in a couple of scopes (e.g. during PR time). What do you two think?

The general idea here is that it removes the qualifier if it's in the same scope that you're in. So this is unnecessary in these cases since you know that you're already working in this object so it couldn't be anything else. (for properties especially)
But honestly this is one of those things where I don't have a preference either way. It doesn't impact anything code wise so as long as we're consistent I'm fine with whatever. I just went with this since it was the default VS generated so I figured that's more likely to be consistent across other projects. (although I know SMO greatly prefers using this for everything)

Offline discussion, this is good 😄


mmi1 structure missing from gene page?

This mmi1  structure doesn't appear to be available from the mmi1 gene page?
https://www.pombase.org/reference/PMID:27165520

It looks OK to me?
Publication page:

Gene page:

Yes you are right.
I was confuse by this:

when I went to Mmi1 page because I thought that all the structures sere from this publication,
maybe we should workshop that?


Add github workflow

Summary
Add github workflow to the project. This includes linter and code coverage.

reference (liquidity module case)

https://github.com/tendermint/liquidity/actions
https://github.com/tendermint/liquidity/tree/develop/.github/workflows


Add 'AsFields()' extended methods for the IEnumerable

The feature is already present.

Simply set as public for exposure.

Will be available on build > v1.9.9-beta1.


Update ipfs to 49.0.4

Update ipfs to 49.0.4
https://github.com/graphprotocol/graph-cli/issues/653

there are a few PRs will work on getting a update in


cache post-setup failures

all of a sudden this morning our cache post-setup started failing with
Post Set up cache 15s
Post job cleanup.
/bin/tar -cz -f /home/runner/work/_temp/2c4ed222-ac5c-466d-b163-19853e6fd4a2/cache.tgz -C /home/runner/work/cloud-custodian/cloud-custodian/.tox/py37 .
[warning]Cache service responded with 500 during chunk upload.
events.js:187
      throw er; // Unhandled 'error' event
      ^
Error: EBADF: bad file descriptor, read
Emitted 'error' event on ReadStream instance at:
    at internal/fs/streams.js:167:12
    at FSReqCallback.wrapper [as oncomplete] (fs.js:470:5) {
  errno: -9,
  code: 'EBADF',
  syscall: 'read'
}

Same error here this morning!

Thanks for reporting!  Issue was caused by an automated OS update that started failing requests with large bodies.  We have been deploying a fix using the old OS image.  The fix has already deployed to 2 of the 3 scale units, so this may be mitigated for some of you.  Will be fixed on the last scale unit in about 20 minutes.

Thanks a ton! Just re ran and all is well. <3

Should be mitigated everywhere, now.  Sorry for the inconvenience.

thanks, lgtm

I get same error today


Bug: Deploy to Azure validation error for the Azure Firewall Subnet CIDR Range

Deployment Mode
Deploy To Azure
Steps to reproduce
This is a UI related bug. The default value in the Azure Firewall Subnet CIDR Range throws an error as soon as you come on the screen but changing the value to something different and then changing it back it to the default value fixes it. It's a minor inconvenience but could lead to some confusion. See screenshots below:
Error Message
See below.

Screenshots
The initial error with the default values in place:

Step 1 - Remove the "/24" and click on the screen to see a different validation error:

Step 2 - Enter "/24" again and click on the screen to magically see the validation error disappear:

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I reproduced this error and fixed it with the proposed workaround.

Thanks @tuterbatuhan. Let me take a look later this week and fix it. Thanks for the heads-up!


Live-editing with Next.js 15 on Vercel

Describe the issue you're facing
I closely followed the described setup process for Next.js App Router with RSC (really happy about the improved README btw) and live-editing is working perfectly on a local environment. But when I deploy the app to Vercel, the dotted boxes are gone and data only gets updated when hard refreshing the visual editor preview.
I made sure that all routes are rendered dynamically, when fetching data from Storyblok, the preview token is used,  version is set to draft and cv is Date.now(). What conditions should be met to enable live-editing? Am I missing something obvious here?
Reproduction

Steps to reproduce
No response
System Info
node: 18.19.0
next.js: 15.0.1
@storyblok/react: 4.0.0

Used Package Manager
yarn
Error logs (Optional)
No response
Validations

[X] Follow our Code of Conduct

Hi @peperoli, how is the app running on the deployment? Is it configured for SSR?

Hi @peperoli, how is the app running on the deployment? Is it configured for SSR?

Generally no, but inside the visual editor, the app enables draft mode to switch to dynamic rendering.

@peperoli the only thing I can think of is some configuration issue on Vercel, if the local env work then the live preview is configured correctly and should work

@edodusi yeah, makes sense to me. I'm going to do some more research about my Vercel configuration.

ok @peperoli let me know if you find something that we can add to the doc

Alrighty I promptly found the issue. I'm using an api route to enable draft mode and then redirect to the actual slug. I forgot to pass the search params to the redirect URL which are needed to initialize Storyblok bridge. There's even a hint in the docs: https://www.storyblok.com/docs/guide/essentials/visual-editor#additional-query-params
// api/draft/route.ts

import { draftMode } from 'next/headers'
import { redirect } from 'next/navigation'
import StoryblokClient from 'storyblok-js-client'

export async function GET(request: Request) {
  const { searchParams } = new URL(request.url)
  const slug = searchParams.get('slug')

  const storyblok = new StoryblokClient({ accessToken: process.env.STORYBLOK_TOKEN })
  const { data } = await storyblok.get(`cdn/stories/${removeLocaleFromSlug(slug)}`, {
    version: 'draft',
    excluding_fields: 'header,body,seo',
  })

  if (!data?.story) {
    return new Response('Invalid slug', { status: 401 })
  }

  const draft = await draftMode()
  draft.enable()

  // Redirect to the path from the fetched story,
  // pass the search parameters to initialize Storyblok bridge
  redirect(`/${data.story.full_slug}?${searchParams.toString()}`)
}


Scaling Down from Machine Pools page removes the machine and kube node from the cluster but the DO droplet is not removed

If this is a UI issue, please file an issue at https://github.com/rancher/dashboard/
Rancher Server Setup

Rancher version: v2.6-head 4b6af95

Information about the Cluster

Kubernetes version: v1.23.3-rc4+rke2r2
Cluster Type (Local/Downstream):

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider): RKE2 provisioned by DO

Describe the bug

Scaled down my machine pool to have less machines, but the machine in DO is not removed.
To Reproduce

Create a cluster with multiple machine pools (3) and each pool has 3 machines. The 2 additional machine pools are worker only machine pools
After the cluster is up and running, scale down from the Cluster Management-> Machine Pools page by selecting the - button in the machine pool section.

Result
UI shows that the machine and kube node are no longer part of the cluster.
BUT the DO droplet is still running in DO.
Expected Result

DO droplet should be removed as well
Screenshots

Additional context
<!--Add any other context about the problem here.—>

This seems to be working as expected now. I was able to scale worker nodes up and down.

Rancher version: v2.6-head (08/13/2021) 4def656
local cluster k8s: RKE1 v1.21.3
Downstream clusters RKE2 kubernetes:  v1.21.3-rc5+rke2r2
I was able to reduce scale and observe the nodes deleted on DO cloud with these configurations:
Configuration #1

etcd/control plane - 3 nodes
worker - 3 nodes
worker - 3 nodes

Configuration #2

etcd - 3 nodes
control plane - 3 nodes
worker - 3 nodes


Using ComObject Word.Application

Hello everybody, i am encountering an issue.
I need to convert some old PDF files (encoded with word 2006 .xml schema) as PDF.
I already used PowerShell and ComObject to do this on a Windows system :
$word = New-Object -ComObject Word.Application
$word.Documents.Open($filename).SaveAs($filename.replace(".xml", ".pdf"), 17)

but now I have to automate this process on a Linux system (every XML files are generated onto).
PowerShell on Linux able to me to use these commands but not ComObject due to a missing of api-ms-win-core-com-l1-1-0.dll
Is there any way to load this dll into a Linux system ? If not, is there any other way to do the same ?
Command
$word = New-Object -ComObject Word.Application

Expected behavior

Actual behavior
New-Object : Unable to load DLL 'api-ms-win-core-com-l1-1-0.dll': The specified module or one of its dependencies could not be found.
 (Exception from HRESULT: 0x8007007E)
At line:1 char:9
+ $word = New-Object -ComObject Word.application
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [New-Object], DllNotFoundException
    + FullyQualifiedErrorId : System.DllNotFoundException,Microsoft.PowerShell.Commands.NewObjectCommand

Environment data

> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      6.0.0-beta
PSEdition                      Core
GitCommitId                    v6.0.0-beta.7
OS                             Linux 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

@JeremyBidet Thanks for your report!
Unix systems don't support COM. You could use remoting from Unix to Windows system.
We should return more user-friendly message.
/cc @daxian-dbw

Thanks to you @iSazonov for your feedback

Reopening this to have better error message

have better error message

Or to not expose -ComObject on Unix plats?

@daxian, even better!


SRS Review #12

@karolserkis
In User Responsibilities:
You have two points.

Ensure that the input data is fits the system model(...)  ----> Do you mean to say that user should enter input in correct units? If so please rewrite this sentence. If you have a different criteria for input data to fit in the system, please mention it clearly.

Ensure that the input data is within scope(See Table of Units and Symbols) --> You say that user has to ensure input data is within scope and you have referenced table of units and symbols. Did you mean to reference the scope section?

@Malavika-Srinivasan @smiths
Thank you for the good feedback!


Prevent interacting with chips while paused

It didn't seem like a big issue at first, but i found ways to abuse this very easily, and with wildly different recruit upgrades.

Selling and buying the same chip right away while on pause resets that chip's cooldown. Needless to say this is overly powerful with the MEM chip, which means you only get to pay 12bit for any attacker to instantly disapear once the pause is resumed, then pause again and replace it with a new MEM.
A variation of the above abuse allows the player to safely deal with coins (although at a great cost). Wait for the coin to pass over an upgraded SHR chip, then pause and sell it, buy a SUB chip in its place, unpause-repause to see if the coin got destroyed, if not, sell the SUB chip, buy a SHR instead and upgrade it to the max, unpause-repause, replace it with a SUB… repeat until coin is destroyed.
Exploiting Tramiel's last upgrade allows you to get lots of extra money by infinitely reselling above the buying price (as reported in #71 ), even at the start of a game if you chose to get more initial info through Hollerith.

I'd like to retain the ability to sell chips in PAUSED state; I think this has also been reqested by someone. Better address the problems you've mentioned.

Selling and buying again the same chip should not reset the cooldown. I'll have to think of a way to prevent this, even if I'm not quite sure how. The simplest way would be to start an initial cooldown cycle when it is placed, but that may be too hard when a chip is placed the first time. Or have a last cooldown after selling it, so that you can't immediately put a new one in the same slot.

phew ... yes. If you want to, why not ... But that's so tedious, it will turn you from a player into a worker.

Currently, the max refund is 110%. I thought it was fun to have this little extra coin, but if you think this is a problem, then Tramiel can easily be limited to 100%.

I think the most promising solution is to complete the last cooldown phase after selling a chip, and only then permit to place a new one. This should resolve all the three problems.

I think the most promising solution is to complete the last cooldown phase after selling a chip

I agree this must be the best solution :)
Le 16 janvier 2024 12:27:00 GMT+01:00, ochadenas @.***> a écrit :

I'd like to retain the ability to sell chips in PAUSED state; I think this has also been reqested by someone. Better address the problems you've mentioned.

Selling and buying again the same chip should not reset the cooldown. I'll have to think of a way to prevent this, even if I'm not quite sure how. The simplest way would be to start an initial cooldown cycle when it is placed, but that may be too hard when a chip is placed the first time. Or have a last cooldown after selling it, so that you can't immediately put a new one in the same slot.

phew ... yes. If you want to, why not ... But that's so tedious, it will turn you from a player into a worker.

Currently, the max refund is 110%. I thought it was fun to have this little extra coin, but if you think this is a problem, then Tramiel can easily be limited to 100%.

I think the most promising solution is to complete the last cooldown phase after selling a chip, and only then permit to place a new one. This should resolve all the three problems.
--
Reply to this email directly or view it on GitHub:
https://github.com/ochadenas/cpudefense/issues/92#issuecomment-1893555081
You are receiving this because you authored the thread.
Message ID: @.***>

Done as discussed (in 1.28): When selling chips, they first become grey, but complete their cooldown cycle. They can no  longer be upgraded. After that time, they disappear completely.
The refund is credited the moment they are sold.
Also fixed a bug that the cooldown was reset when changing between apps.

will test that next update!
Le 18 janvier 2024 14:30:21 GMT+01:00, ochadenas @.***> a écrit :

Closed #92 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/ochadenas/cpudefense/issues/92#event-11525265087
You are receiving this because you authored the thread.
Message ID: @.***>


BACKLOG-23059 Fixed permissions on lock context action

JIRA

https://jira.jahia.org/browse/BACKLOG-23059
Description

This PR changes the lock and unlock context actions permission rules.

Lock action respects the lockPage permission for pages
Unlock action checks if you are root or the owner of the lock
Note that we need https://github.com/Jahia/javascript-components/pull/268 to be released first, and version bumped here.

Tests
The following are included in this PR

[ ] Unit Tests (Most changes should have unit tests)
[ ] Integration Tests

Checklist

I have considered the following implications of my change:

[ ] Security (in particular for changes to authentication, authorization, data fetching, ...)
[ ] Performance
[ ] Migration
[ ] Code maintainability

Documentation

[ ] Inline documentation
[ ] Internal Documentation (wiki)
[ ] User-facing Documentation

JS components library is released, this is ready to merge


undefined method `the_thumb_url' error if I click on user created tag

Hi,
I am getting undefined method `the_thumb_url' error if I click on user created tag on article/product post.
Here is the exception.
undefined method `the_thumb_url' for #<CamaleonCms::PostTagDecorator:0x007fbc485b46e8>

    # Delegates missing instance methods to the source object.
    def method_missing(method, *args, &block)
      return super unless delegatable?(method)

      self.class.delegate method
      send(method, *args, &block)

draper (1.4.0) lib/draper/automatic_delegation.rb:7:in `method_missing'
camaleon_cms (2.1.0) app/helpers/camaleon_cms/frontend/seo_helper.rb:24:in `cama_the_seo'
camaleon_cms (2.1.0) app/helpers/camaleon_cms/frontend/site_helper.rb:71:in `the_head'
camaleon_cms (2.1.0) app/apps/themes/camaleon_first/views/layouts/index.html.erb:14:in

I am using camaleon_cms version 2.1

Hi,
PostTag doesn't support for thumbs, if you need thumbs or other attributes you can use the custom fields for PostTags.

No, I am not using postTag for thumbs, I just created a post and added tag to that post,  i am getting above exception if I click on tag.

fixed!

Thank you :)

Working with latest code, hence closing this issue. Thanks for the fix.


Homebase needed?

 Do I need a homebase for this addon to work in HA? I currently only own a wired doorbell, and was hoping to hook that up to Home Assistant.
Anyways, thanks for the great work on the addon, really appreciated!!

Thanks, I have :)
Unfortunately the logs keep telling me no devices found.
2021-11-17 14:31:39.637  INFO Eufy Security server listening on port 3000  2021-11-17 14:31:41.026  INFO No stations found.  2021-11-17 14:31:41.338  INFO No devices found.  2021-11-17 14:31:41.657  INFO Push notification connection successfully established
I created an additional account to which I shared my doorbell, as a guest, not an admin (is that needed?). If i log onto the app on that account, I can successfully see the doorbell.

give it a try with admin rights

I have, unfortunately same issue. I have this doorbell https://us.eufylife.com/products/t8200
Is there anything else I could try?

Try to remove the devices from new account and share them back again with admin rights. This had solved many issues earlier.

@fuatakgun , that solved it :) Thank you so much for the help!


Compiling OpenSSL for 8-bit AVR use

Hi all,
I have been attempting to compile OpenSSL for use with the CW303 XMEGA Target found here. This device is listed as having an 8-bit Harvard-style Architecture. After reading documentation and numerous tests, the best command sequence I could come up with is as follows:
./config --prefix=/usr --cross-compile-prefix=avr- no-threads --mmcu=avrxmega7
sudo make

I'm not sure if the "--mmcu=avrxmega7" is necessary, but it didn't seem to affect my issue at the moment, so I kept it as an option. Regardless of the last option, this fails with the following error:
avr-gcc: error: unrecognized command line option '-m64'

When manually removing the '-m64' inclusions from the Makefile prior to running sudo make, a multitude of errors regarding missing system header files come into play.
I'm not sure where to proceed from here and have had difficulty moving past this barrier, surely there must be a simple way to accomplish this. I've attached the output of perl configdata.pm --dump below.
Command line (with current working directory = .):

    /usr/bin/perl ./Configure linux-x86_64 --prefix=/usr --cross-compile-prefix=avr- no-threads

Perl information:

    /usr/bin/perl
    5.26.1 for x86_64-linux-gnu-thread-multi

Enabled features:

    aria
    asm
    async
    autoalginit
    autoerrinit
    autoload-config
    bf
    blake2
    camellia
    capieng
    cast
    chacha
    cmac
    cmp
    cms
    comp
    ct
    deprecated
    des
    dgram
    dh
    dsa
    dso
    dtls
    dynamic-engine
    ec
    ec2m
    ecdh
    ecdsa
    engine
    err
    filenames
    fips
    gost
    idea
    legacy
    makedepend
    md4
    mdc2
    module
    multiblock
    nextprotoneg
    pinshared
    ocb
    ocsp
    padlockeng
    pic
    poly1305
    posix-io
    psk
    rc2
    rc4
    rdrand
    rfc3779
    rmd160
    scrypt
    secure-memory
    seed
    shared
    siphash
    siv
    sm2
    sm3
    sm4
    sock
    srp
    srtp
    sse2
    ssl
    static-engine
    stdio
    tests
    tls
    ts
    ui-console
    whirlpool
    tls1
    tls1-method
    tls1_1
    tls1_1-method
    tls1_2
    tls1_2-method
    tls1_3
    dtls1
    dtls1-method
    dtls1_2
    dtls1_2-method

Disabled features:

    afalgeng            [cross-compiling] OPENSSL_NO_AFALGENG
    asan                [default]         OPENSSL_NO_ASAN
    buildtest-c++       [default]
    crypto-mdebug       [default]         OPENSSL_NO_CRYPTO_MDEBUG
    devcryptoeng        [default]         OPENSSL_NO_DEVCRYPTOENG
    ec_nistp_64_gcc_128 [default]         OPENSSL_NO_EC_NISTP_64_GCC_128
    egd                 [default]         OPENSSL_NO_EGD
    external-tests      [default]         OPENSSL_NO_EXTERNAL_TESTS
    fuzz-libfuzzer      [default]         OPENSSL_NO_FUZZ_LIBFUZZER
    fuzz-afl            [default]         OPENSSL_NO_FUZZ_AFL
    ktls                [default]         OPENSSL_NO_KTLS
    md2                 [default]         OPENSSL_NO_MD2 (skip crypto/md2)
    msan                [default]         OPENSSL_NO_MSAN
    rc5                 [default]         OPENSSL_NO_RC5 (skip crypto/rc5)
    sctp                [default]         OPENSSL_NO_SCTP
    ssl-trace           [default]         OPENSSL_NO_SSL_TRACE
    threads             [option]
    trace               [default]         OPENSSL_NO_TRACE
    ubsan               [default]         OPENSSL_NO_UBSAN
    unit-test           [default]         OPENSSL_NO_UNIT_TEST
    uplink              [no uplink_arch]  OPENSSL_NO_UPLINK
    weak-ssl-ciphers    [default]         OPENSSL_NO_WEAK_SSL_CIPHERS
    zlib                [default]
    zlib-dynamic        [default]
    ssl3                [default]         OPENSSL_NO_SSL3
    ssl3-method         [default]         OPENSSL_NO_SSL3_METHOD

Config target attributes:

    AR => "ar",
    ARFLAGS => "r",
    CC => "gcc",
    CFLAGS => "-Wall -O3",
    CXX => "g++",
    CXXFLAGS => "-Wall -O3",
    HASHBANGPERL => "/usr/bin/env perl",
    RANLIB => "ranlib",
    RC => "windres",
    asm_arch => "x86_64",
    bn_ops => "SIXTY_FOUR_BIT_LONG",
    build_file => "Makefile",
    build_scheme => [ "unified", "unix" ],
    cflags => "-m64",
    cppflags => "",
    cxxflags => "-std=c++11 -m64",
    defines => [  ],
    disable => [  ],
    dso_ldflags => "-z defs",
    dso_scheme => "dlfcn",
    enable => [ "afalgeng" ],
    ex_libs => "-ldl",
    includes => [  ],
    lflags => "",
    lib_cflags => "",
    lib_cppflags => "-DOPENSSL_USE_NODELETE -DL_ENDIAN",
    lib_defines => [ "OPENSSL_BUILDING_OPENSSL" ],
    module_cflags => "-fPIC",
    module_cxxflags => undef,
    module_ldflags => "-Wl,-znodelete -shared -Wl,-Bsymbolic",
    multilib => "64",
    perl_platform => "Unix",
    perlasm_scheme => "elf",
    shared_cflag => "-fPIC",
    shared_defflag => "-Wl,--version-script=",
    shared_defines => [  ],
    shared_ldflag => "-Wl,-znodelete -shared -Wl,-Bsymbolic",
    shared_rcflag => "",
    shared_sonameflag => "-Wl,-soname=",
    shared_target => "linux-shared",
    thread_defines => [  ],
    thread_scheme => "pthreads",
    unistd => "<unistd.h>",

Recorded environment:

    AR =
    ARFLAGS =
    AS =
    ASFLAGS =
    BUILDFILE =
    CC =
    CFLAGS =
    CPP =
    CPPDEFINES =
    CPPFLAGS =
    CPPINCLUDES =
    CROSS_COMPILE =
    CXX =
    CXXFLAGS =
    HASHBANGPERL =
    LD =
    LDFLAGS =
    LDLIBS =
    MT =
    MTFLAGS =
    OPENSSL_LOCAL_CONFIG_DIR =
    PERL =
    RANLIB =
    RC =
    RCFLAGS =
    RM =
    WINDRES =
    __CNF_CFLAGS =
    __CNF_CPPDEFINES =
    __CNF_CPPFLAGS =
    __CNF_CPPINCLUDES =
    __CNF_CXXFLAGS =
    __CNF_LDFLAGS =
    __CNF_LDLIBS =

Makevars:

    AR              = avr-ar
    ARFLAGS         = r
    CC              = avr-gcc
    CFLAGS          = -Wall -O3
    CPPDEFINES      =
    CPPFLAGS        =
    CPPINCLUDES     =
    CROSS_COMPILE   = avr-
    CXX             = avr-g++
    CXXFLAGS        = -Wall -O3
    HASHBANGPERL    = /usr/bin/env perl
    LDFLAGS         =
    LDLIBS          =
    PERL            = /usr/bin/perl
    RANLIB          = avr-ranlib
    RC              = avr-windres
    RCFLAGS         =

NOTE: These variables only represent the configuration view.  The build file
template may have processed these variables further, please have a look at the
build file for more exact data:
    Makefile

build file:

    Makefile

build file templates:

    Configurations/common0.tmpl
    Configurations/unix-Makefile.tmpl
    Configurations/common.tmpl

Any help would be much appreciated!

You're cross-compiling, please refer to: https://github.com/openssl/openssl/blob/master/INSTALL.md#cross-compile-prefix


feat: Add support for bc4,5,7 formats

Allows BC4, BC5, and BC7 to be used in the convert command to create VTFs of those formats.
Also fixes some crashes/bugs in the convert command / image library.

Should VTFLib submodule be bumped? Looks good otherwise

Just saw the VTFLib PR. After that's approved + merged, the submodule will need to be bumped.

vtflib needs to be bumped again


RFC: gencap-write

Add #write, a new gencap for use in type parameter constraints, implying the capability set: {iso, trn, ref}.
https://github.com/ponylang/rfcs/blob/master/text/0043-gencap-write.md

@jemc it looks like you had this almost finished when the rfc went in, do you want to finish this off?

Sorry about this.
It turned out that this gencap didn't actually solve my problem (5 years ago), and neither I nor anyone else has had a pressing reason to add this.
Additionally, now (5 years later) that I know more about the subtle edge cases with generic subtyping, I'm a lot more wary about adding new generic caps, since that means more tricky edge cases.
So if nobody is actively needing this feature, and it risks introducing new bugs, I suggest we don't continue with this at this time.


Set default ANCM hosting model to InProcess from .App metapackage

The default hosting model is currently out-of-proc. When we are ready, let's enable in-proc by default.
To do this, we need a copy of the MSBuild properties in M.A.Server.IIS -- which sets the AspNetCoreHostingModel msbuild property -- copied into the .App metapackage.
https://github.com/aspnet/IISIntegration/blob/dev/src/Microsoft.AspNetCore.Server.IIS/Microsoft.AspNetCore.Server.IIS.targets
Depends on https://github.com/aspnet/Universe/issues/762

Moving to 2.1.0

In-proc got moved out past 2.1.0

@shirhatti / @DamianEdwards / @muratg - what's the plan for this issue?

We can't make this change in 2.2.0. It's too big of a behavior change.
For 3.0, we've already made this change in the websdk https://github.com/aspnet/websdk/pull/407

Yes


Advanced text

This PR brings all the improvements that have been introduced in the advanced-text branch. Specifically:

#1697
#1748
#1811
#1822
#1828

It's hard to overstate the importance of these changes! All of these features combined make one of the biggest changesets to land in master since the inception of the library!
These efforts should lay the foundations for acquiring maturity in the long run (multi-line text input, accessibility, rendering parallelization, and more!). For more details, check out the latest roadmap diagram.
Closes #33.
Fixes #41.
Closes #1071.
Closes #1199.

This is a complete revolution!
I'm so excited to see what iced will accomplish in the future 🚀

Bug report: image seems broken on this branch.
Repro steps: Create a minimum iced app with a single image.
use iced::{Application, Settings};

fn main() -> iced::Result {
    app::App::run(iced::Settings {
        window: iced::window::Settings {
            size: (400, 300),
            position: iced::window::Position::Centered,
            ..Default::default()
        },
        ..Default::default()
    })
}

pub mod app {
    use iced::{widget::image, Sandbox};

    #[derive(Default)]
    pub struct App;

    #[derive(Debug, Clone, Copy)]
    pub enum Message {}

    impl Sandbox for App {
        type Message = Message;

        fn new() -> Self {
            App {}
        }

        fn title(&self) -> String {
            String::from("My Title")
        }

        fn update(&mut self, message: Self::Message) {}

        fn view(&self) -> iced::Element<'_, Self::Message> {
            image(image::Handle::from_path("resources/bg2.png"))
                .content_fit(iced::ContentFit::Fill)
                .into()
        }
    }
}

With advanced-text:

With iced 0.9.0:

@gabrieldechichi Cannot reproduce.

@hecrj @bungoboingo That's weird, I just had the same results in a different machine (same graphics cards though).
System specs:

OS: Windows 11
Graphics adapter: NVIDIA Geforce RTX 3060 Laptop GPU
Graphics backend: Vulkan

I'm unsure how to check what iced renderer I'm using (sorry, I'm new to iced/rust), can you tell me how I can look this up?
I just a new project in the examples folder in a clone of this repo, checked out to this PR and pointing to the local iced source. These are the images I used to test (both have bugs):
resources.zip

Thanks @bungoboingo. So it looks like I'm running wgpu + Vulkan by default (sharing full logs in case anyone is interested).
 So it could be an issue with wgpu + Vulkan + possibly my specific graphics card an drivers.
For context, the tour example also works for me, it's unclear if this is related to the specific image files, or the specific code I'm writing. If anyone is interested to test, this is a zip with everything (main.rs on my first post + resources). Assumes it is placed on iced/examples folder.
image-test.zip
Don't let this stall this PR if it's a non-repro though. Also let me know if this is not the correct place to raise this, and it's preferred to open issues.

Logs
[WARN  wgpu_hal::vulkan::instance] Unable to find layer: VK_LAYER_KHRONOS_validation
[INFO  wgpu_hal::vulkan::instance] Instance version: 0x4030e0
[INFO  wgpu_hal::vulkan::instance] Enabling debug utils
[INFO  wgpu_hal::vulkan::instance] Enabling device properties2
[INFO  wgpu_hal::gles::egl] Loading X11 library to get the current display
[INFO  wgpu_hal::gles::egl] EGL_MESA_platform_surfaceless not available. Using default platform
[INFO  wgpu_hal::gles::egl] Display vendor "Google Inc. (adapter LUID:<PHONE_NUMBER>012047)", version (1, 4)
[WARN  wgpu_hal::gles::egl]     EGL surface: -srgb
[INFO  wgpu_hal::gles::egl]     Trying native-render
[WARN  wgpu_hal::gles::egl] No config found!

[INFO  wgpu_core::device] Created buffer Valid((0, 1, Vulkan)) with BufferDescriptor { label: Some("glyphon params"), size: 16, usage: BufferUsages(COPY_DST | UNIFORM), mapped_at_creation: false }
[INFO  wgpu_core::device] Created texture Valid((0, 1, Vulkan)) with TextureDescriptor { label: Some("glyphon atlas"), size: Extent3d { width: 256, height: 256, depth_or_array_layers: 1 }, mip_level_count: 1, sample_count: 1, dimension: D2, format: Rgba8UnormSrgb, usage: TextureUsages(COPY_DST | TEXTURE_BINDING), view_formats: [] }
[INFO  wgpu_core::device] Created texture Valid((1, 1, Vulkan)) with TextureDescriptor { label: Some("glyphon atlas"), size: Extent3d { width: 256, height: 256, depth_or_array_layers: 1 }, mip_level_count: 1, sample_count: 1, dimension: D2, format: R8Unorm, usage: TextureUsages(COPY_DST | TEXTURE_BINDING), view_formats: [] }
[INFO  wgpu_core::device] Created render pipeline Valid((0, 1, Vulkan)) with RenderPipelineDescriptor { label: Some("iced_wgpu::quad pipeline"), layout: Some((1, 1, Vulkan)), vertex: VertexState { stage: ProgrammableStageDescriptor { module: (1, 1, Vulkan), entry_point: "vs_main" }, buffers: [VertexBufferLayout { array_stride: 8, step_mode: Vertex, attributes: [VertexAttribute { format: Float32x2, offset: 0, shader_location: 0 }] }, VertexBufferLayout { array_stride: 68, step_mode: Instance, attributes: [VertexAttribute { format: Float32x2, offset: 0, shader_location: 1 }, VertexAttribute { format: Float32x2, offset: 8, shader_location: 2 }, VertexAttribute { format: Float32x4, offset: 16, shader_location: 3 }, VertexAttribute { format: Float32x4, offset: 32, shader_location: 4 }, VertexAttribute { format: Float32x4, offset: 48, shader_location: 5 }, VertexAttribute { format: Float32, offset: 64, shader_location: 6 }] }] }, primitive: PrimitiveState { topology: TriangleList, strip_index_format: None, front_face: Cw, cull_mode: None, unclipped_depth: false, polygon_mode: Fill, conservative: false }, depth_stencil: None, multisample: MultisampleState { count: 1, mask:<PHONE_NUMBER>3709551615, alpha_to_coverage_enabled: false }, fragment: Some(FragmentState { stage: ProgrammableStageDescriptor { module: (1, 1, Vulkan), entry_point: "fs_main" }, targets: [Some(ColorTargetState { format: Bgra8UnormSrgb, blend: Some(BlendState { color: BlendComponent { src_factor: SrcAlpha, dst_factor: OneMinusSrcAlpha, operation: Add }, alpha: BlendComponent { src_factor: One, dst_factor: OneMinusSrcAlpha, operation: Add } }), write_mask: ColorWrites(RED | GREEN | BLUE | ALPHA) })] }), multiview: None }
[INFO  wgpu_core::device] Created buffer Valid((1, 1, Vulkan)) with BufferDescriptor { label: Some("iced_wgpu::quad vertex buffer"), size: 32, usage: BufferUsages(VERTEX), mapped_at_creation: true }
[INFO  wgpu_core::device] Created buffer Valid((2, 1, Vulkan)) with BufferDescriptor { label: Some("iced_wgpu::quad index buffer"), size: 12, usage: BufferUsages(INDEX), mapped_at_creation: true }
[INFO  wgpu_core::device] Created render pipeline Valid((1, 1, Vulkan)) with RenderPipelineDescriptor { label: Some("iced_wgpu::triangle::msaa pipeline"), layout: Some((2, 1, Vulkan)), vertex: VertexState { stage: ProgrammableStageDescriptor { module: (1, 2, Vulkan), entry_point: "vs_main" }, buffers: [] }, primitive: PrimitiveState { topology: TriangleList, strip_index_format: None, front_face: Cw, cull_mode: None, unclipped_depth: false, polygon_mode: Fill, conservative: false }, depth_stencil: None, multisample: MultisampleState { count: 1, mask:<PHONE_NUMBER>3709551615, alpha_to_coverage_enabled: false }, fragment: Some(FragmentState { stage: ProgrammableStageDescriptor { module: (1, 2, Vulkan), entry_point: "fs_main" }, targets: [Some(ColorTargetState { format: Bgra8UnormSrgb, blend: Some(BlendState { color: BlendComponent { src_factor: One, dst_factor: OneMinusSrcAlpha, operation: Add }, alpha: BlendComponent { src_factor: One, dst_factor: OneMinusSrcAlpha, operation: Add } }), write_mask: ColorWrites(RED | GREEN | BLUE | ALPHA) })] }), multiview: None }
[INFO  wgpu_core::device] Created render pipeline Valid((2, 1, Vulkan)) with RenderPipelineDescriptor { label: Some("iced_wgpu::triangle::solid pipeline"), layout: Some((3, 1, Vulkan)), vertex: VertexState { stage: ProgrammableStageDescriptor { module: (1, 3, Vulkan), entry_point: "vs_main" }, buffers: [VertexBufferLayout { array_stride: 24, step_mode: Vertex, attributes: [VertexAttribute { format: Float32x2, offset: 0, shader_location: 0 }, VertexAttribute { format: Float32x4, offset: 8, shader_location: 1 }] }] }, primitive: PrimitiveState { topology: TriangleList, strip_index_format: None, front_face: Cw, cull_mode: None, unclipped_depth: false, polygon_mode: Fill, conservative: false }, depth_stencil: None, multisample: MultisampleState { count: 4, mask:<PHONE_NUMBER>3709551615, alpha_to_coverage_enabled: false }, fragment: Some(FragmentState { stage: ProgrammableStageDescriptor { module: (1, 3, Vulkan), entry_point: "fs_main" }, targets: [Some(ColorTargetState { format: Bgra8UnormSrgb, blend: Some(BlendState { color: BlendComponent { src_factor: SrcAlpha, dst_factor: OneMinusSrcAlpha, operation: Add }, alpha: BlendComponent { src_factor: One, dst_factor: OneMinusSrcAlpha, operation: Add } }), write_mask: ColorWrites(RED | GREEN | BLUE | ALPHA) })] }), multiview: None }
[INFO  wgpu_core::device] Created render pipeline Valid((3, 1, Vulkan)) with RenderPipelineDescriptor { label: Some("iced_wgpu::triangle::gradient pipeline"), layout: Some((4, 1, Vulkan)), vertex: VertexState { stage: ProgrammableStageDescriptor { module: (1, 4, Vulkan), entry_point: "vs_main" }, buffers: [VertexBufferLayout { array_stride: 8, step_mode: Vertex, attributes: [VertexAttribute { format: Float32x2, offset: 0, shader_location: 0 }] }] }, primitive: PrimitiveState { topology: TriangleList, strip_index_format: None, front_face: Cw, cull_mode: None, unclipped_depth: false, polygon_mode: Fill, conservative: false }, depth_stencil: None, multisample: MultisampleState { count: 4, mask:<PHONE_NUMBER>3709551615, alpha_to_coverage_enabled: false }, fragment: Some(FragmentState { stage: ProgrammableStageDescriptor { module: (1, 4, Vulkan), entry_point: "fs_main" }, targets: [Some(ColorTargetState { format: Bgra8UnormSrgb, blend: Some(BlendState { color: BlendComponent { src_factor: SrcAlpha, dst_factor: OneMinusSrcAlpha, operation: Add }, alpha: BlendComponent { src_factor: One, dst_factor: OneMinusSrcAlpha, operation: Add } }), write_mask: ColorWrites(RED | GREEN | BLUE | ALPHA) })] }), multiview: None }
[INFO  wgpu_core::device] configuring surface with SurfaceConfiguration { usage: TextureUsages(RENDER_ATTACHMENT), format: Bgra8UnormSrgb, width: 1280, height: 960, present_mode: AutoVsync, alpha_mode: Auto, view_formats: [] }
[INFO  wgpu_core::device] Automatically choosing presentation mode by rule AutoVsync. Chose Fifo
[INFO  wgpu_core::device] Automatically choosing alpha mode by rule Auto. Chose Opaque
[INFO  wgpu_core::device] configuring surface with SurfaceConfiguration { usage: TextureUsages(RENDER_ATTACHMENT), format: Bgra8UnormSrgb, width: 1280, height: 960, present_mode: AutoVsync, alpha_mode: Auto, view_formats: [] }
[INFO  wgpu_core::device] Automatically choosing presentation mode by rule AutoVsync. Chose Fifo
[INFO  wgpu_core::device] Automatically choosing alpha mode by rule Auto. Chose Opaque
[INFO  wgpu_core::device] Created buffer Valid((3, 1, Vulkan)) with BufferDescriptor { label: Some("iced_wgpu::quad uniforms buffer"), size: 80, usage: BufferUsages(COPY_DST | UNIFORM), mapped_at_creation: false }
[INFO  wgpu_core::device] Created buffer Valid((4, 1, Vulkan)) with BufferDescriptor { label: Some("iced_wgpu::quad instance buffer"), size: 1048576, usage: BufferUsages(COPY_DST | VERTEX), mapped_at_creation: false }
[INFO  wgpu_core::device] Created buffer Valid((5, 1, Vulkan)) with BufferDescriptor { label: Some("iced_wgpu::triangle index buffer"), size: 512, usage: BufferUsages(COPY_DST | INDEX), mapped_at_creation: false }
[INFO  wgpu_core::device] Created buffer Valid((6, 1, Vulkan)) with BufferDescriptor { label: Some("iced_wgpu::triangle::solid vertex buffer"), size: 3072, usage: BufferUsages(COPY_DST | VERTEX), mapped_at_creation: false }
[INFO  wgpu_core::device] Created buffer Valid((7, 1, Vulkan)) with BufferDescriptor { label: Some("iced_wgpu::triangle::solid uniforms"), size: 64, usage: BufferUsages(COPY_DST | UNIFORM), mapped_at_creation: false }
[INFO  wgpu_core::device] Created buffer Valid((8, 1, Vulkan)) with BufferDescriptor { label: Some("iced_wgpu::triangle::gradient vertex buffer"), size: 1024, usage: BufferUsages(COPY_DST | VERTEX), mapped_at_creation: false }
[INFO  wgpu_core::device] Created buffer Valid((9, 1, Vulkan)) with BufferDescriptor { label: Some("iced_wgpu::triangle::gradient uniforms"), size: 96, usage: BufferUsages(COPY_DST | UNIFORM), mapped_at_creation: false }
[INFO  wgpu_core::device] Created buffer Valid((10, 1, Vulkan)) with BufferDescriptor { label: Some("iced_wgpu::triangle::gradient storage"), size: 32, usage: BufferUsages(COPY_DST | STORAGE), mapped_at_creation: false }
[INFO  wgpu_core::device] Created buffer Valid((11, 1, Vulkan)) with BufferDescriptor { label: Some("iced_wgpu::triangle index buffer"), size: 4068, usage: BufferUsages(COPY_DST | INDEX), mapped_at_creation: false }
[INFO  wgpu_core::device] Created buffer Valid((12, 1, Vulkan)) with BufferDescriptor { label: Some("iced_wgpu::triangle::solid vertex buffer"), size: 16272, usage: BufferUsages(COPY_DST | VERTEX), mapped_at_creation: false }
[INFO  wgpu_core::device] Created buffer Valid((13, 1, Vulkan)) with BufferDescriptor { label: Some("iced_wgpu::triangle::solid uniforms"), size: 576, usage: BufferUsages(COPY_DST | UNIFORM), mapped_at_creation: false }
[INFO  wgpu_core::device] Created buffer Valid((14, 1, Vulkan)) with BufferDescriptor { label: Some("glyphon vertices"), size: 4096, usage: BufferUsages(COPY_DST | VERTEX), mapped_at_creation: false }
[INFO  wgpu_core::device] Created buffer Valid((15, 1, Vulkan)) with BufferDescriptor { label: Some("glyphon indices"), size: 4096, usage: BufferUsages(COPY_DST | INDEX), mapped_at_creation: false }
[INFO  wgpu_core::device] Created render pipeline Valid((4, 1, Vulkan)) with RenderPipelineDescriptor { label: Some("glyphon pipeline"), layout: Some((0, 1, Vulkan)), vertex: VertexState { stage: ProgrammableStageDescriptor { module: (0, 1, Vulkan), entry_point: "vs_main" }, buffers: [VertexBufferLayout { array_stride: 28, step_mode: Vertex, attributes: [VertexAttribute { format: Sint32x2, offset: 0, shader_location: 0 }, VertexAttribute { format: Uint32, offset: 8, shader_location: 1 }, VertexAttribute { format: Uint32, offset: 12, shader_location: 2 }, VertexAttribute { format: Uint32, offset: 16, shader_location: 3 }, VertexAttribute { format: Uint32, offset: 20, shader_location: 4 }, VertexAttribute { format: Float32, offset: 24, shader_location: 5 }] }] }, primitive: PrimitiveState { topology: TriangleList, strip_index_format: None, front_face: Ccw, cull_mode: None, unclipped_depth: false, polygon_mode: Fill, conservative: false }, depth_stencil: None, multisample: MultisampleState { count: 1, mask:<PHONE_NUMBER>3709551615, alpha_to_coverage_enabled: false }, fragment: Some(FragmentState { stage: ProgrammableStageDescriptor { module: (0, 1, Vulkan), entry_point: "fs_main" }, targets: [Some(ColorTargetState { format: Bgra8UnormSrgb, blend: Some(BlendState { color: BlendComponent { src_factor: SrcAlpha, dst_factor: OneMinusSrcAlpha, operation: Add }, alpha: BlendComponent { src_factor: One, dst_factor: OneMinusSrcAlpha, operation: Add } }), write_mask: ColorWrites(RED | GREEN | BLUE | ALPHA) })] }), multiview: None }
[INFO  wgpu_core::device] Buffer (14, 1, Vulkan) is destroyed
[INFO  wgpu_core::device] Created buffer Valid((16, 1, Vulkan)) with BufferDescriptor { label: Some("glyphon vertices"), size: 8192, usage: BufferUsages(COPY_DST | VERTEX), mapped_at_creation: true }
[INFO  wgpu_core::device] Created texture Valid((3, 1, Vulkan)) with TextureDescriptor { label: Some("iced_wgpu::triangle::msaa attachment"), size: Extent3d { width: 1280, height: 960, depth_or_array_layers: 1 }, mip_level_count: 1, sample_count: 4, dimension: D2, format: Bgra8UnormSrgb, usage: TextureUsages(RENDER_ATTACHMENT), view_formats: [] }
[INFO  wgpu_core::device] Created texture Valid((4, 1, Vulkan)) with TextureDescriptor { label: Some("iced_wgpu::triangle::msaa resolve target"), size: Extent3d { width: 1280, height: 960, depth_or_array_layers: 1 }, mip_level_count: 1, sample_count: 1, dimension: D2, format: Bgra8UnormSrgb, usage: TextureUsages(TEXTURE_BINDING | RENDER_ATTACHMENT), view_formats: [] }
[INFO  wgpu_core::hub] Dropping Global
[INFO  wgpu_core::device] Destroying 3 command encoders
[WARN  wgpu_hal::auxil::dxgi::exception] Process is terminating. Using simple reporting. Please call ReportLiveObjects() at runtime for standard reporting.
[WARN  wgpu_hal::auxil::dxgi::exception] Live Producer at 0x0000022BA5422EF0, Refcount: 2.
[WARN  wgpu_hal::auxil::dxgi::exception]        Live Object at 0x0000022BA54F8BB0, Refcount: 0.
[WARN  wgpu_hal::auxil::dxgi::exception]        Live Object at 0x0000022BA56992F0, Refcount: 0.
[WARN  wgpu_hal::auxil::dxgi::exception]        Live Object at 0x0000022BA56A7260, Refcount: 0.
[WARN  wgpu_hal::auxil::dxgi::exception]        Live Object at 0x0000022BA56B5670, Refcount: 0.
[WARN  wgpu_hal::auxil::dxgi::exception]        Live Object at 0x0000022BA56EE9C0, Refcount: 0.
[WARN  wgpu_hal::auxil::dxgi::exception]        Live Object at 0x0000022BA56EE2F0, Refcount: 0.
[WARN  wgpu_hal::auxil::dxgi::exception]        Live Object at 0x0000022BA56E6640, Refcount: 0.
[WARN  wgpu_hal::auxil::dxgi::exception]        Live Object at 0x0000022BA56E8CD0, Refcount: 0.
[WARN  wgpu_hal::auxil::dxgi::exception]        Live Object at 0x0000022BA58C1700, Refcount: 0.
[WARN  wgpu_hal::auxil::dxgi::exception] Live                         Object :      9
[WARN  wgpu_hal::auxil::dxgi::exception] Live Producer at 0x0000022BA5907B80, Refcount: 2.
[WARN  wgpu_hal::auxil::dxgi::exception]        Live Object at 0x0000022BA54F8970, Refcount: 0.
[WARN  wgpu_hal::auxil::dxgi::exception]        Live Object at 0x0000022BA593C4A0, Refcount: 0.
[WARN  wgpu_hal::auxil::dxgi::exception]        Live Object at 0x0000022BA5962410, Refcount: 0.
[WARN  wgpu_hal::auxil::dxgi::exception]        Live Object at 0x0000022BA599C530, Refcount: 0.
[WARN  wgpu_hal::auxil::dxgi::exception]        Live Object at 0x0000022BA599CCA0, Refcount: 0.
[WARN  wgpu_hal::auxil::dxgi::exception]        Live Object at 0x0000022BA5968670, Refcount: 0.
[WARN  wgpu_hal::auxil::dxgi::exception]        Live Object at 0x0000022BA58C0660, Refcount: 0.
[WARN  wgpu_hal::auxil::dxgi::exception]        Live Object at 0x0000022BA599D500, Refcount: 0.
[WARN  wgpu_hal::auxil::dxgi::exception]        Live Object at 0x0000022BA58C22E0, Refcount: 0.
[WARN  wgpu_hal::auxil::dxgi::exception] Live                         Object :      9

I just noticed after testing the tour example that any longish glyph (like the gs here) is getting cut off at the bottom (tested on windows & linux). Adjusting the to_absolute function for the logical pixels of LineHeight and just adding some manual padding makes the long characters render correctly, so I'm assuming the issue is with the new LineHeight changes. Or perhaps longer glyphs go outside the "bounds" of the text?

I'm noticing the same issue

@bungoboingo @tarkah This is caused by 9a8b30d7e9cf76c097d68c84736e7687b452d5c0.
I have incremented the default line height to 1.3 since it seems more readable to me and should prevent this issue. It may be interesting to eventually expose a flag to control the clipping behavior on overflow.

@bungoboingo I would expect the same. Seems it's an issue others have encountered as well: https://github.com/pop-os/cosmic-text/issues/123.

Hopefully, the 1.3 default line height makes the issue less common. If it still persists, I can revert 9a8b30d7e9cf76c097d68c84736e7687b452d5c0 for now.

One question I have is whether the candidate backend selection should order backends based on the most performant option. I'd think something like this:

All hardware adapters for wgpu in the order wgpu enumerates
Software renderer
Software vulkan implementations (via wgpu)

https://github.com/iced-rs/iced/blob/advanced-text/renderer/src/compositor.rs#L155

Can we reliably guarantee that our software rendering implementation is more performant than the driver virtual implementations? I don't know if this has an obvious answer or we need to run some actual numbers.

I guess the answer is it depends. Lavapipe might be able to use AVX-512 if supported but then there is the issue of compiler overhead. tiny-skia does have some simd support.
Probably needs to be measured anyways.

@gabrieldechichi I was able to reproduce and fix the issue in #1847.


Expressions in function parameters are accepted by the compiler

Description
The following code is accepted by the compiler:
#let foo((test: "bar")) = {}

To my knowledge, this function can't be called, without the compiler throwing an error.
I would expect this code to not be accepted at all, even without calling it.
To solve this, it might be enough to just switch the false to true.
https://github.com/typst/typst/blob/main/src/syntax/parser.rs#L1250
Reproduction URL
No response
Operating system
No response
Typst version

[X] I am using the latest version of Typst

FYI I just tried flipping the false to true at https://github.com/typst/typst/blob/2dc0478ffe283f2433cbb58cf75d4f5f156fe74c/crates/typst-syntax/src/parser.rs#L1316 but the compiler still accepts #let foo((test: "bar")) = {} without error :)


[LOG4J2-3426] Refactors wrapping code

Refactors the wrapping logic into single wrap or adapt methods to be sure we always perform the correct logic.

@ppkarwasz,
Hi Piotr,
I am not building log4j2 1.x bridge jars but downloading the jar. I wanted to test with this Pull Request changes, is it possible for you to provide log4j1.x bridge.jar log4j2-core.jar and log4j2-api.jar built with this change ??

Hi @pooja-achievement ,
I am waiting for a second opinion on these changes: there is not much sense in testing something that will not end up in the next release. If everything is alright, we can generate a snapshot.


Split xtensor-r and Xtensor.R

@wolfv I leave it to you to merge this!

Looks good to me!
Is there no way to run the R-only unit test on commit in this repo?

Is there no way to run the R-only unit test on commit in this repo?

Not at the moment.
We could install Xtensor.R with --configure-args=--novendor` as part of this and check that we can build the same unit test.

I think that would be cool so that we keep the unit tests on push in here
do you want to merge now or should we figure that out first?

Working on the build for Xtensor.R in a separate PR


Media can not play when paused status change from true to false

Current behavior
I have embedded Video component in my js component(named Player.js) like below code snippet
<Video paused={this.state.paused} .... />
fist I trigger this.setState({paused: true}) and 1s or 2s later trigger  this.setState({paused: false})
now, playWhenReady will be set as false in ReactExoplayerView on onHostResume method
and front  code onProgress does not invoked.
Reproduction steps
see above
Expected behavior
media can play auto when paused set to false
Platform
Which player are you experiencing the problem on:

Android ExoPlayer

Video sample
n/a
key log info
10-19 19:18:03.063 12183 12183 D ReactExoplayerView: initializePlayer to setPlayWhenReady(true)
10-19 19:18:03.063 12183 12183 D ReactExoplayerView: setPlayWhenReady to set playWhenReady=true
10-19 19:18:03.067  1846  4669 I MediaFocusControl: requestAudioFocus() from uid/pid 10110/12183<EMAIL_ADDRESS>V.E...... ......I. 0,0-0,0} callingPack=xxxxx.development req=1 flags=0x0 sdk=26
10-19 19:18:03.068 12183 12183 D ReactExoplayerView: setPlayWhenReady hasAudioFocus = true
10-19 19:18:03.069 12183 12183 D ReactExoplayerView: onStateChanged: playWhenReady=true, playbackState=idle
10-19 19:18:03.078 12183 12183 D ReactExoplayerView: onStateChanged: playWhenReady=true, playbackState=buffering
10-19 19:18:03.194 12183 12183 D ReactExoplayerView: onHostResume to setPlayWhenReady true,playInBackground=true,isInBackground=false
10-19 19:18:03.194 12183 12183 D ReactExoplayerView: setPlayWhenReady to set playWhenReady=true
10-19 19:18:03.196  1846  4669 I MediaFocusControl: requestAudioFocus() from uid/pid 10110/12183<EMAIL_ADDRESS>V.E...... ......ID 0,0-1080,0 #b77} callingPack=xxxxxxx.development req=1 flags=0x0 sdk=26
10-19 19:18:03.197 12183 12183 D ReactExoplayerView: setPlayWhenReady hasAudioFocus = true
10-19 19:18:03.280 12183 12183 D AudioManager: dispatching onAudioFocusChange(-1) to<EMAIL_ADDRESS>V.E...... ......I. 0,0-0,0}
10-19 19:18:04.724 12183 12183 D ReactExoplayerView: onStateChanged: playWhenReady=true, playbackState=ready
10-19 19:18:05.471 12183 12183 D ReactExoplayerView: onStateChanged: playWhenReady=true, playbackState=buffering
10-19 19:18:05.482 12183 12183 D ReactExoplayerView: onStateChanged: playWhenReady=true, playbackState=ready
10-19 19:18:11.001 12183 12183 D ReactExoplayerView: pausePlayback .. player = com.google.android.exoplayer2.SimpleExoPlayer@bce9a2b,,player.getPlayWhenReady() = true
10-19 19:18:11.002 12183 12183 D ReactExoplayerView: setPlayWhenReady to set playWhenReady=false
10-19 19:18:11.002 12183 12183 D ReactExoplayerView: onStateChanged: playWhenReady=false, playbackState=ready
10-19 19:18:11.014  1846  4669 I MediaFocusControl: abandonAudioFocus() from uid/pid 10110/12183<EMAIL_ADDRESS>V.E...... ......ID 0,0-1080,0 #b77}

@pengcao1 Can you tell more specific? Thanks.


all same entry, with different meanings won't be returned

When there is an entry with more than one meaning BUT same spelling, what is the easiest way to return all of them. As I couldn't find any.
query('test.mdx', entry,) --> it will return only one of them.

It is a packing and unpacking tool, not for query word that is simple test to validate your just packed MDX file.

That's fine. I will find another way for now, but it would be better to be taken into account for your future updates. It can be used also for searching. It would be a nice feature.
Thanks, by the way, for your great repo.


Is It Possible To Use A Custom InputView For The Textfields?

Hi,
Great library 👍
I am just wondering whether it is possible to use a custom input view for the textfields?

Fixed ^^


Allow to setup API baseURL

What happened?
In my integration tests, I use stripe-mock in a docker container to serve the Stripe APIs.
Stripe Java has a Stripe.overrideApiBase to setup API base URL to localhost:12111 when using stripe-mock to serve the Stripe APIs.
But I can not find such a function in the Stripe JS.
It is a feature request.
Environment
No response
Reproduction
No response

This package is a helper module for Stripe.js, which does not support using other API hosts, so that would not be possible to add here. I don't expect this to be something that gets added to the underlying Stripe.js functionality (similar to previous request around this).
Are you perhaps looking for stripe-node for a Node backend SDK? Using that, you can set the host during initialization (docs).

Thanks for your message @brendanm-stripe, I must have misunderstood the purpose of the module.  Could how it works a little?
also, Could you explain why adding a different base url wouldn't be possible? Not that I do not want to use stripe-node instead.

It's not possible to override the base url because this is not supported (and not expected to be added to) the underlying Stripe.js SDK. This module is a helper/wrapper for loading that Stripe.js SDK conveniently in module-based apps & build systems, and aims to provide TypeScript typings for it.


fix the oai index issue when submitter is null

when submitter is null, it will cause NPE exception, so it will stop the OAI index process. eg. if using harvest, the submitter probably will be null in db.

There was no Jira issue for this bug, but it was discussed on Stack Overflow: http://stackoverflow.com/questions/26300190/oai-import-dspace
I've created a Jira issue: https://jira.duraspace.org/browse/DS-2554
+1 for the change (I haven't tested it, but the change is very obvious -- don't add the item.submitter field to the OAI Solr document, which is fine since the submitter is not a required field).

Thanks a lot for the review. :)

I haven't tested it neither, but I like this PR too.
TravisCI currently seems to have some issues, the build fails during set up of the build environment. While I don't see anything that may fail, I still would like to see this PR pass Travis CI. I'll try to restart the build, but maybe we need to wait until TravisCI works as expected again.

+1 tested this and it works.  It's an obvious, small fix, so I'll merge it.


Use find_packages to include missing submodules

The package available in PyPI is broken, it doesn't include patreon.{jsonapi,schemas,version_compatibility}. This PR fixes it by using the find_packages function from setuptools, instead of listing every submodule explicitly.

thanks so much for noticing this! 😥  0.3.1 is now pushed


[ar] Probabilities and Statistics

Hey, added few translations to the refresher-probabily. That's the ones I found easy to start with, will add some later.

Thanks @slashtea, keep up the great work!

Closed due to inactivity (work continued in #89).


Allow module tests to be run from VS Code

We are close to having module unit tests work within VS Code. This will also make it easy to debug module code/tests.
The only thing missing is that ftltest.WithProjectFiles() relies on FTL_CONFIG envar.
Workarounds:

Set the variable in hermit, open vscode with code .
Set it up as an envar in VS Code's settings json
Both of these are annoying because you have to make sure you don't commit the changes because the path includes your home directory.

Possible solution:
We switch logic to look for expected file names in the current folder, if missing go up a level ... repeat.
This is similar to how you can call just from anywhere within the directory structure
We could make FTL_CONFIG and ftltest.WithProjectFiles(...) do this. This would make passing in strings to the test function actually usable in more cases, and the ftl config value to be able to be commited to git

from discussion with @mistermoe

The current logic when running ftl dev is here. We should probably replicate that.

If a config is passed via either the CLI or envar use them.
Otherwise use `internal.GitRoot() + "/ftl-project.toml" if it exists.

In fact we should probably use ConfigPaths() directly...

good first issue?


[SPARK-50496][SQL]Change rebalance partitioning to SinglePartition if partition number is 1

Change partitioning to SinglePartition.
What changes were proposed in this pull request?

For node  RebalanceByExpression, if partition number is 1 we can use SinglePartition instead of other Partitioning.
Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

Was this patch authored or co-authored using generative AI tooling?

Add test

@dongjoon-hyun  Could you review this renaming PR

@zhengruifeng  Could you review this PR


USHIFT-1238: fix changelog truncation in changelog script

The previous attempt to fix this issue included the message saying the
changelog was being truncated but did not actually shorten the message
text.
/assign @pmtk

/lgtm


[Trivial] Release highlights for v<IP_ADDRESS>

Full changelog (excluding Trivial, maybe I will add a category "Miscellaneaous" with some of this changes):
Still missing PR that will need to be merged tomorrow
### Features:
  * Trezor Safe 5 & Coldcard Q support by @turbolay in https://github.com/WalletWasabi/WalletWasabi/pull/13438
  * Modernize Tor usage technology by @lontivero in https://github.com/WalletWasabi/WalletWasabi/pull/13339
  * Functional Payment in Coinjoin  by @lontivero in https://github.com/WalletWasabi/WalletWasabi/pull/13458
  * Add coinjoin inputs/outputs summary by @turbolay in https://github.com/WalletWasabi/WalletWasabi/pull/13469
  * New format for BTC Amounts by @turbolay in https://github.com/WalletWasabi/WalletWasabi/pull/13491
  * Decrease RevealDelay for PrivacyChars on hover by @MarnixCroes in https://github.com/WalletWasabi/WalletWasabi/pull/13504
  * Extend Input/Output Lists to TxPreview and TxDetails by @turbolay in https://github.com/WalletWasabi/WalletWasabi/pull/13507
  * Add Transaction Hex as copyable content by @turbolay in https://github.com/WalletWasabi/WalletWasabi/pull/13508
  * Add context menu in Input/Output lists to copy BTC Address by @turbolay in https://github.com/WalletWasabi/WalletWasabi/pull/13511

### Bug Fixes
  * Incorrect clipboard content casting by @lontivero in https://github.com/WalletWasabi/WalletWasabi/pull/13447
  * Fix spacing in MusicBox by @turbolay in https://github.com/WalletWasabi/WalletWasabi/pull/13454
  * IOException when corrupted index by @turbolay in https://github.com/WalletWasabi/WalletWasabi/pull/13456
  * Error importing wallets with space in their names by @remcoros in https://github.com/WalletWasabi/WalletWasabi/pull/13476
  * Duplicated p2p network messages by @lontivero in https://github.com/WalletWasabi/WalletWasabi/pull/13518
  * Improve propagation confirmation by @lontivero in https://github.com/WalletWasabi/WalletWasabi/pull/13492

### Coordinator
  * Collect coordinator output if and only if economical by @turbolay in https://github.com/WalletWasabi/WalletWasabi/pull/13451
  * Amount credential size configurable by @lontivero in https://github.com/WalletWasabi/WalletWasabi/pull/13499

### Package/Release
  * Debian: Use `xz` instead of `zst` for compression by @lontivero in https://github.com/WalletWasabi/WalletWasabi/pull/13460
  * Update version in doc after a release by @turbolay in https://github.com/WalletWasabi/WalletWasabi/pull/13463
  * Auto update version number on Website by @turbolay in https://github.com/WalletWasabi/WalletWasabi/pull/13466
  * Fix version number in MacOs plist by @turbolay in https://github.com/WalletWasabi/WalletWasabi/pull/13473

Tweet/Nostr:

Tweet 1:
🚨 New release <IP_ADDRESS> is out 🚨

🌐 Enhanced Tor integration
📊 Better BTC amount formatting
🔍More insight on transactions
💰 [Beta] Payment in Coinjoin (RPC)
🔒 Trezor Safe 5 & ColdCard Q support

Release notes & Download: https://github.com/WalletWasabi/WalletWasabi/releases/tag/v<IP_ADDRESS>

https://github.com/user-attachments/assets/580553d5-ccfb-498a-b50b-84f8217b13d1

Tweet 2:
🌐 Enhanced Tor integration

Complete rewrite of our Tor integration using standard HttpClient. Better performance, clearer code, and improved identity management for enhanced security.

Tweet 3:
📊 Better BTC amount formatting

Improved readability for all amounts with instant BTC-to-Sats conversion. Cleaner, more consistent UI across all screens showing amounts: balances, fees, Coinjoin outputs...

Tweet 4:
🔍 More insight on transactions

Detailed input/output lists for all transactions, including Coinjoins and transaction preview. See how your privacy is enhanced by Coinjoins and understand how are constructed your transactions, including when using a privacy suggestion.

Tweet 5:
💰 [Beta] Payment in Coinjoin (RPC)

Our Payment in Coinjoin feature enters beta! Currently available via RPC only. Test it out and share your feedback!

Learn more: docs.wasabiwallet.io/using-wasabi/RPC.html#payincoinjoin

Tweet 6:
🔒 Hardware Wallet Updates
Added support for Trezor Safe 5 & ColdCard Q with HWI 3.1.0 update.

Tweet 7:
This release continues our vision of simplifying the codebase and improving the resiliency of the software, while still shipping long-awaited quality-of-life features. By building stronger foundations today, we're paving the way for more exciting features tomorrow!

Video attached to Tweet 1:
https://github.com/user-attachments/assets/580553d5-ccfb-498a-b50b-84f8217b13d1

Looks very good.

Payments in coinjoin were previously available with the RPC .

PiCJ was never fully supported. It was in some kind of development stage or preview for a long time because two this:

the rpc was a feature that nobody wanted to use. Even devs were not aware of what was possible and they never used it for anything.
except for a very few enthusiast, PiCJ didn't have any real support from zkSNACKs
the PiCJ functionality was never announced and it didn't work because of a bug.

PiCJ is a feature and we are releasing the first version of it that is finally usable. This means that users can use it for real-world scenarios and they can automate payments as wasn't possible before.
I think that now that we finally have a working version, we can release it officially and announce it as what it is: a feature.

Modernize Tor usage technology
Add coinjoin inputs/outputs summary by @turbolay in https://github.com/WalletWasabi/WalletWasabi/pull/13469

New format for BTC Amounts by @turbolay in https://github.com/WalletWasabi/WalletWasabi/pull/13491
Decrease RevealDelay for PrivacyChars on hover by @MarnixCroes in https://github.com/WalletWasabi/WalletWasabi/pull/13504
Extend Input/Output Lists to TxPreview and TxDetails by @turbolay in https://github.com/WalletWasabi/WalletWasabi/pull/13507
Add Transaction Hex as copyable content by @turbolay in https://github.com/WalletWasabi/WalletWasabi/pull/13508
Add context menu in Input/Output lists to copy BTC Address by @turbolay in https://github.com/WalletWasabi/WalletWasabi/pull/13511

Bug Fixes

Incorrect clipboard content casting by @lontivero in https://github.com/WalletWasabi/WalletWasabi/pull/13447
Fix spacing in MusicBox by @turbolay in https://github.com/WalletWasabi/WalletWasabi/pull/13454
IOException when corrupted index by @turbolay in https://github.com/WalletWasabi/WalletWasabi/pull/13456
Error importing wallets with space in their names by @remcoros in https://github.com/WalletWasabi/WalletWasabi/pull/13476
Duplicated p2p network messages by @lontivero in https://github.com/WalletWasabi/WalletWasabi/pull/13518
Improve prop


Added support to expand skip half expanded mode

Closes #122
Adds skipHalfExpanded in the parameters to enable bottom sheet to show in full mode.

@adrielcafe @DevSrSouza can you please have a look?

Thanks!


Align license for go files

where license was missing, update apache 2.0 license with current year
where license was present, align its format and keep original year

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 remained the same at 36.701%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
356

Relevant Lines:
970

💛  - Coveralls

Let wait for CI to pass to merge

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 36.701%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
356

Relevant Lines:
970

💛  - Coveralls


Please update /source/index.js

File: /source/index.js
This line no longer valid in the latest version of RN.
let Dimensions=require("Dimensions");
Recommended:
import { Dimensions } from 'react-native'
Thank you!

<EMAIL_ADDRESS>


Feature#632 (Translating GUIDELINES_CA.md)

Section 2.1.2 of GUIDELINES_CA has been modified, updating and translating the information into Catalan.
A line that was apparently deleted by mistake (section 2.6 in the table of contents) has also been fixed.

There are many files changed in this PR. Only need a little change in GUIDELINES_CA.md. Please, review that