Allow specifying the target element for appending style tags

@mxstbr As requested here's the PR. Luckily there weren't many merge conflicts to resolve and all the tests @paul-veevers wrote are passing! My team and I also tested it locally on our application and it looks like it helped solved the rehydration problem caused by multiple styled-components that others also voiced in the issue.
I don't know if I have permissions to link this PR to #1102 since it'll essentially be a duplicate, so let know if there's any due diligence needed on my end.
Thanks again for all the help 😄

CI is failing?

Looking it into it now! For some reason the native tests on my machine can't run due to this Cannot find module 'ReactElementType' from 'ReactRef.js'. May be a problem with babel-plugin-flow-react-proptypes and react-native, but haven't drilled down to it.
But since my native tests failed, it skipped the bundlesize tests. Working on a fix for that now

@mxstbr Is there a protocol we should follow when deciding when to raise the bundlesize threshold?  Looks like the CI is failing from the bundlesize tests by 0.06KB FAIL  ./dist/styled-components.min.js: 14.56kB > maxSize 14.5kB gzip
Going to take a stab at minimizing it to get it passing, but just wanted to keep you in the loop and see if there were any alternatives? Tagging @siddharthkp as this may be related?

You can increase the max size in package.json, it's kind of annoying that this makes it so much bigger though :cry:

@bteng22 I've been in this situation 😄
@mxstbr Ideally you want to keep the threshold a good 2-3kB more than the current size (which is 14.49kB right now) so that you can catch mistakes. Keeping it too close to the current size sounds like micromanaging 🙂
I don't think you'll gain much out of optimising this PR.
I sound like a broken record but add the github token so that you can see the difference in each pull request! (or give me access for a few hours and i'll do it for you!)

Thanks for the input @mxstbr & @siddharthkp 👍 I raised the threshold to 14.7kB. It's a little more on the conservative side and will be about 1.4kB more than the current thresholds in the tests. Looks like that was enough to get the checks to pass 🎆

Looks awesome, thanks so much @bteng22! One point of discussion is, do we want to rename the StyleSheetManager to just StyleSheet?
<StyleSheetManager target={document.getElementById()}>

</StyleSheetManager>

// vs.

<StyleSheet target={document.getElementById()}>

</StyleSheet>

The second one seems more obvious to users, though it might be confusing since we also have ServerStyleSheet. How do we make the difference between those clear, and also what happens when you try to server-side render an app that has a StyleSheet? Users would have to use refs, right?

No problem @mxstbr. Just trying to get this in prod ASAP 😄
Hmm maybe StyleSheetProvider? It looks like it's essentially providing a StyleSheet instance to StyledComponents through it's context, whether explicitly through a sheet prop or implicitly from the given target. I'm game for either suggestion, but changing the name would be a breaking change for any teams using the StyleSheetManager. Is this something we want to address now or can we shelve it for later?
In regards to your other questions, we're going to investigate a little further, but I just wanted to clarify a couple questions:
*When server-side rendering with an app that has a StyleSheet, should we prevent the use of the target prop since we do not have a DOM? or are you implying there is a way to get a pointer to a ref of one of the components?
My team and I tested it locally by keeping the SSR rendering the same as the documentation with a ServerStyleSheet instance and then on the client-side we wrapped our application with a StyleSheetManager with a specific target prop pointing to our DOM element. This approach seemed to be working well so far.
Also, is there a better channel we could reach you or any of the moderators? We might have some quick questions that could be better clarified if we PM'd you directly?

@mxstbr > Wait, what would people be using it for right now? Why do we export that?!
It can be used when collectStyles is a bad option, i.e. to clean up code in SSR. It shouldn't be a major problem to rename though.
I would hold off from renaming it to StyleSheet though, as the confusion is simply to great when a component acts as a stylesheet while merely providing one.

Sounds good to me, let's leave it as-is then.

Some things to note:

Opened a PR for documentation here https://github.com/styled-components/styled-components-website/pull/178
The proposed documentation also potentially outlines how to handle SSRing with targeted styles. In short, the implementation is the same as the Server Side Rendering section, but we just need to inject the CSS under the specific target on the markup.
We pushed a commit with a couple tests for multiple instances of StyleSheetManager when they're targeting the same DOM element and for when they're nested. Let me know if they're valuable or need to be reworked
Still investigating your point regarding deeply nested StyleSheetManagers. At the moment, it looks like any StyledComponents outside the manager will get set on the document.head, while everything inside the manager will get applied to the style tag underneath the target if specified

Here's an example we got working of nested StyleSheetManagers:
<StyleSheetManager> // passing in ServerStyleSheet on server-side and target on client-side
  <StyledCompA/>
  <Frame>
    <div ref={(el) => {this.setState({ targetRef: el })}}>
      {this.state.targetRef && <StyleSheetManager target={this.state.targetRef}>
        <StyledCompB />
      </StyleSheetManager>}
    </div>
  </Frame>
</StyleSheetManager>

To your point @mxstbr , users would have to use refs (specifically on an HTMLElement and not a React Element), for the StyleSheetManager to access the given target. Unfortunately, this doesn't lend itself to collecting styles on the server-side and will only generate them on the client-side during runtime (because the ref callback occurs on mount).
Some other scenarios we explored with our app running its own instance of styled components:

running another application with it's own instance of styled-components rendered through an iframe
running another application rendered on the same page (as a sibling) with separate styled-components instance and a target. In our case, a separate application rendering a header and the content body of a page

In summary, using targets seems to work easily for pulling in external apps that are also using styled-components with a target, but requires a bit more work on the client-side if one is nesting StyleSheetManagers within a single application.

While this is still being figured out, is there any way to use this in a project?
This doesn't work with npm 5:
"dependencies": {
  "styled-components": "styled-components/styled-components#pull/1324/head"
}

@ivanakimov easiest is to clone styled-components, check out this branch, run the builds, run yarn pack/npm pack, vendor the resulting tarball into your repo, and run yarn add ./X.tar.gz.

Yep, never would've thought of that. 👍  Thanks @philpl, that works.

@bteng22 our widget uses <StyleSheetManager target={container}> and the stylesheet does load properly within the <div> we specified, as expected. 👍
But the problem is that main app now stops loading other styled components properly after that external widget loads its own. Is this expected behavior for this PR or are we doing something wrong? (btw the main app does not use StyleSheetManager)

But the problem is that main app now stops loading other styled components properly after that external widget loads its own

That sounds like a bug, any ideas what's up with that?

Also keyframes doesn't work when used inside <StyleSheetManager target={someIframe} />.

@ivanakimov hmm definitely sounds like a bug—are you using the same StyledComponents both inside and outside of your target container? If you could code up a small example on a gist to reproduce I could take a better look
@Fer0x I believe keyframes are global and as a result won't be appended to the target container within StyleSheetManager at least within this PR. Maybe we can open another issue to tackle that?

@bteng22 yes I've tried the same StyledComponents for both repos (and even using StyleSheetManager with a target for the main app) -- still definitely an issue with the main component not loading styles after another app loads its own.

@ivanakimov so, that sounds like either something’s wrong with this branch, or sth is wrong with your setup and you’re using two packages, maybe 😬
Can you make sure that your project is using a single version of styled-components? (Webpack can help ensure this)
And would you have time to help us and the PR submitter @bteng22 with a reproduction please? :)

@philpl I was using the same tgz for both repos when doing the tests. And yep, this issue is definitely a blocker for us, so I'm going to be diving in deeper to see if I can either setup a basic example or see what the problem is.

@ivanakimov could it be that it was installed in both repos but isn’t deduced? If those are sufficiently separate, the npm resolution algorithm will search the closest node_modules folder upwards, so if you install it in both they might still be duplicated even if they’re identical.
It unfortunately depends a lot on the folder structure and build pipeline :/ a quick fix if they’re nested in each other would be to use peer dependency in the lower project

@philpl hmm, well they're completely different repos in different folders with their own node_modules (and the repos are not nested). but i'll try to rm node_modules and do a fresh install and see if that helps.

Well, reinstalling node_modules didn't help, and I made sure both projects use the same version.
I've spent 2 hours today trying to build a basic example to reproduce the bug, but no luck. I've tried to recreate our conditions (with react router, with blueprintjs, with injectGlobal, with the same class names, with loading components dynamically, with separating into 2 separate apps), but can't trigger the issue.
I can clearly see it happening on our own project and the fact that styles do not load anymore right after loading the external widget, but the two repos are so big, I am not sure how else to try and trigger it in a reproducible way.
On the other hand, I guess this is good news for the PR... If there's any other suggestions on what I could try, I'm all ears.

Pleaaaase merge this!

Haven't really looked at this patch too much to be honest since I don't directly need it in production right now.
A thorough code review and test in production would be appreciated and would help us ship this

Picking this up, will work on the following topics:

Solve merge conflicts
Make the test suite pass
Do a scoped publish for real-world testing on some projects

Thank you so much for helping us improve styled-components! Based on our Community Guidelines every person that has a PR of any kind merged is offered an invitation to the styled-components organization—that is you right now!
Should you accept, you'll get write access to the main repository. (and a fancy styled-components logo on your GitHub profile!) You'll be able to label and close issues, merge pull requests, create new branches, etc. We want you to help us out with those things, so don't be scared to do them! Make sure to read our contribution and community guidelines, which explains all of this in more detail. Of course, if you have any questions just let me know!

@bteng22 Hiya, thanks to you as well! The changes have been merged with modifications by @marionebl in #1491


Make enter key work on mobile chat search v3

On master hitting enter does nothing. Now it'll add the user (like desktop)
This is due to a missing hoc. we should discuss this
@keybase/react-hackers

cc @MarcoPolo


add the ability to merge partial backups with the last full backup and restore

Describe your idea
I see there is an ability to merge and restore, but not on the 1,19 version of the mod? Could this be backported please? Our server's world got corrupted today and I had to manually merge two days worth of backups

If you need to do this anytime soon, you could just use the 1.20 version to merge the zips. Will backport this feature, just can’t give an ETA.

Oh, I just saw that the 1.19 version of the mod already has this feature. As you can see on this link, the 1.19.x branch has the command: https://github.com/ChaoticTrials/SimpleBackups/blob/1.19.x/src/main/java/de/melanx/simplebackups/commands/MergeCommand.java
And here is the version where it was introduced: https://modrinth.com/mod/simple-backups/version/1.19.4-2.2.6

Here is the CurseForge link to the same mod version: https://www.curseforge.com/minecraft/mc-mods/simple-backups/files/5123564

I think it doesn't work. Normally, I'd tag the older versions if I know that it works. In this case, I specifically removed theses tags here: https://github.com/ChaoticTrials/SimpleBackups/commit/41bf8744fa8d33e8b45b5be22d3245d7f16c2b9f
There must be a reason for that. But you can try!

I backported it to 1.19.2 :) Version 1.19.1-2.1.11


typo fix mistake word Update cn_doc and en_doc for elt.md

LGTM

Please rebase master

Please rebase master to re-trigger the understream check


Crash after title screen of Bubble Trouble

0.4.7 Game starts but sometimes intro-cutscene is not shown.

0.5.0 Game seems to work.


Rancher 2 on CoreOs

We are currently using Rancher on a CoreOs cluster. We would like to know if Rancher 2 is still working on CoreOs ?
thank you

I'm running Rancher 2.0 on CoreOS without too much difficulty:
    - name: rancher.service
      enable: true
      contents: |
        [Unit]
        Description=Rancher service for docker management
        After=docker.service
        After=srv-docker-rancher.mount
        Requires=docker.service
        Requires=srv-docker-rancher.mount

        [Service]
        Type=oneshot
        RemainAfterExit=true
        ExecStartPre=-/usr/bin/docker kill rancher
        ExecStartPre=-/usr/bin/docker rm rancher
        ExecStartPre=/usr/bin/docker pull rancher/server:preview
        ExecStart=/usr/bin/docker run -d --restart=unless-stopped --name rancher -p 8080:80 -p 8443:443 -v /srv/docker/rancher/server:/var/lib/rancher rancher/server:preview
        ExecStartPost=/usr/bin/bash /etc/rancher/agent-launch.sh
        ExecStop=/usr/bin/docker stop -t 2 rancher

        [Install]
        WantedBy=multi-user.target

Preferably, systemd unit would not launch instance in daemon mode. However, there appears to be bad exit code on stop that puts the service in a irrecoverable state until restarting docker. Daemon mode appears to work around the issue. Not sure if this is isolated to Rancher 2.0.

Perhaps it was the original question intent, but I was also wondering if rancher v2 can provision coreos nodes to create cluster (master  and worker nodes).
Something I have yet to try out. Curious to hear about others doing this.

I'd think the answer is yes. I currently run rancher server on CoreOS and bootstrap the node it's running on as a compute node in a cluster running all three kubernetes roles for my lab.

Thanks @tahoward .I will check it Out. I hope to have an official support since I will not take any chance in our production cluster.

Supported OS are:
Ubuntu 16.04 (64-bit)
Red Hat Enterprise Linux 7.5 (64-bit)
RancherOS 1.4.0 (64-bit)
Any OS with Docker should work fine though, you can always reach out for options with support.


Is it possible to put all the translation items in each language in one file

Is it possible to put all the translation items in each language in one file

yes

So why don't you use this solution?
Be the way, when I say a global IStringLocalizer I mean something like IStringLocalizer<MyGlobalClass>.

I’m already using it, I’m looking to see if there is a better way to implement it


[wip] initial split and Makefile cleanup

Split Makefile into build, iso, run, and test to make it more maintainable.

Done with testing, closing.


Atualização no pt-br

@VictorxD70 has been working on pt-BR recently. What do you think about this translation? Should I merge it?

Yes, you can merge!

Thank you both!


Failed to load sampled bitmap:

java.lang.RuntimeException: Failed to load sampled bitmap: file:///storage/emulated/0/file1507719041982.jpg
/storage/emulated/0/file1507719041982.jpg (No such file or directory)

How did you start the activity?
Which file to you pick?

For this...
java.lang.RuntimeException: Failed to load sampled bitmap: file:///storage/emulated/0/file1507719041982.jpg
/storage/emulated/0/file1507719041982.jpg (No such file or directory)
try to change the saving mode of your file.
save file in this way....
Bitmap photo = (Bitmap) data.getExtras().get("data");
//captured_photo.setImageBitmap(photo);
            String root = Environment.getExternalStorageDirectory().toString();
            File myDir = new File(root + "/DCIM/myCapturedImages");
            myDir.mkdirs();
            Random generator = new Random();
            int n = 10000;
            n = generator.nextInt(n);
            String fname = "FILENAME-"+ n +".jpg";
            File file = new File (myDir, fname);

            if (file.exists ()) file.delete ();
            try {
                FileOutputStream out = new FileOutputStream(file);
                photo.compress(Bitmap.CompressFormat.JPEG, 100, out);
                Toast.makeText(MainActivity.this, "Image Saved", Toast.LENGTH_SHORT).show();
                out.flush();
                out.close();

            } catch (Exception e) {
                e.printStackTrace();
            }

This will work

I got it....Thanks for your Library, It worked awsm...

what is the solution for this issue, I'm still facing this issue.

The issue seems to be coming when calling CropImage.getActivityResult(data) the result contains the error from above. It seems the image has changed in newer versions.
Looking at the solution above where exactly did you change this code as the CropActivity still has control.

Replace the method getCaptureImageOutputUri in the CropImage.java file with the below code, might solve the problem.
it worked for me
public static Uri getCaptureImageOutputUri(@nonnull Context context) {
Uri outputFileUri = null;
File getImage = context.getExternalCacheDir();
if (getImage != null) {
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.N) {
outputFileUri = FileProvider.getUriForFile(context, BuildConfig.APPLICATION_ID + ".provider",
new File(getImage.getPath(), "pickImageResult.jpeg"));
} else {
outputFileUri = Uri.fromFile(new File(getImage.getPath(), "pickImageResult.jpeg"));
}
}
return outputFileUri;
}

Hi May I know how you edit the read-only CropImage.class file?


Twitter download not working

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm reporting that yt-dlp is broken on a supported site
[X] I've verified that I'm running yt-dlp version 2023.07.06 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and I'm willing to share it if required

Region
Tanzania
Provide a description that is worded well enough to be understood
URL: https://twitter.com/City_Xtra/status/1692823718962335871?t=XX7AX6iTaEfhMfSdfQ8WHA&s=19
WARNING: [twitter] Twitter API gave 404 response, retrying with deprecated auth token. Only one media item can be extracted
ERROR: [twitter]<PHONE_NUMBER>962335871: Unable to download JSON metadata: HTTP Error 404: Not Found (caused by <HTTPError 404: 'Not Found'>); please report this issue on https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using yt-dlp -U
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
Uh I jus use an app but it told me to report here so I did

you or the developer of your app need to update yt-dlp to the nightly version, or wait for the next release


Trying to get in touch regarding a security issue

Hello 👋
I run a security community that finds and fixes vulnerabilities in OSS. A researcher (@ce-automne) has found a potential issue, which I would be eager to share with you.
Could you add a SECURITY.md file with an e-mail address for me to send further details to? GitHub recommends a security policy to ensure issues are responsibly disclosed, and it would help direct researchers in the future.
Looking forward to hearing from you 👍
(cc @huntr-helper)

Hello JamieSlome
thanks for your suggestion, we'll be adding our security policy soon  (around September15th);  looking forward to your more suggestions. If you are in a hurry, we can temporarily use this mail address<EMAIL_ADDRESS>to communicate.


What's new in 2.0?

Looks like a major version bump.
Any plans for a blog post?

There is actually a changelog with features here: https://github.com/GoogleChrome/puppeteer/releases/tag/v2.0.0

One thing I noticed is that r705776 build version is 79.0.3945.0 but release notes state 79.0.3942.0.
FYI @mathiasbynens

Per Omahaproxy:

Commit 4528b050 initially landed in 79.0.3942.0


BUG(?): Following the meson build instructions results in Python 3.10.1 being installed.

Describe your issue.
If I follow the instructions at https://github.com/scipy/scipy/blob/master/doc/source/dev/contributor/meson.rst, starting with the latest miniconda (which has Python 3.9), the environment created by the command
conda env create -f environment_meson.yml

installs Python 3.10.1.
Is this a bug, or a known (and hopefully temporary) glitch in the meson build configuration?

Maybe an oversight, but not specific to meson – conda env seems to have defaulted to Python 3.10 for some time now, although its 3.10 support has not been that robust so far (and the initially installed version is still 3.9).
For the time being, changing the dependencies line to python=3.9 may be the only option to ensure you use that version.

I guess conda just treats python as a dependency and so tales latest.

I guess conda just treats python as a dependency and so tales latest.

@tupui and @dhomeier are correct. Conda works like every other package manager (apt, brew, yum, etc.) and treats Python as a normal dependency - so it defaults to the latest version unless there's a conflict that would cause it to downgrade to 3.9. Which is a good thing:)

When I hesitantly called this a "bug", I didn't mean to suggest that this was a bug in conda.  I meant that this was a problem with the workflow recommended in meson.rst.  If I am using Python 3.9, I definitely do not want my Python version upgraded to 3.10 just so I can use meson.  Does meson require 3.10?

No, it's certainly not a bug. If you want to install meson, ninja and pkg-config in your existing Python 3.9 environment, you can. Meson works with all supported Python 3.x versions.
The conda env create -f environment_meson.yml creates a new environment, and that should just use the normal solver rules - which will give you Python 3.10. This is typically recommended - a fresh environment for every project - so the docs follow best practice.

OK.  It still feels wrong to me, but I guess I have a different mental model of the purpose of those instructions.

I think like all our instructions they are "from scratch". If you already have an existing environment, it's hard to write instructions - it could be just conda install meson ninja pkg-config, but it may not be (e.g. your environment doesn't have openblas).


Roll Flutter Engine from da3d49c30bcc to f372329c9099 (2 revisions)

https://github.com/flutter/engine/compare/da3d49c30bcc...f372329c9099
2024-02-25<EMAIL_ADDRESS>Further shard Android emulator tests (flutter/engine#50954)
2024-02-25<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from Oac3MZ5VgZ9g3Q3cL... to kLvCWEgbL1VTRW69e... (flutter/engine#50953)
Also rolling transitive DEPS:
fuchsia/sdk/core/linux-amd64 from Oac3MZ5VgZ9g to kLvCWEgbL1VT
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC jimgraham@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


After clone action new ticket has no heading or text visible in other browsers

Cloned tickets seems to bee empty! (Yellow ones were cloned..)

Verified as Fixed
Client version	v1.2.97
API version	v0.4.37
IMG version	v0.1.10


[SPARK-8564][Streaming]Add the Python API for Kinesis

This PR adds the Python API for Kinesis, including a Python example and a simple unit test.

Merged build triggered.

Merged build started.

Test build #35554 has started for   PR 6955 at commit 4957c0b.

Test build #35554 has finished for   PR 6955 at commit 4957c0b.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class KinesisUtils(object):
class InitialPositionInStream(object):

Merged build finished. Test PASSed.

Merged build triggered.

Merged build started.

Test build #38223 has started for   PR 6955 at commit 687446b.

Test build #38223 has finished for   PR 6955 at commit 687446b.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class KinesisUtils(object):
class InitialPositionInStream(object):

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #38230 has started for   PR 6955 at commit 466b425.

Merged build triggered.

Merged build started.

Test build #38236 has started for   PR 6955 at commit 7c5cfb0.

Test build #38230 has finished for   PR 6955 at commit 466b425.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test build #38236 has finished for   PR 6955 at commit 7c5cfb0.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #38312 has started for   PR 6955 at commit 6c37395.

Test build #38312 has finished for   PR 6955 at commit 6c37395.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class KinesisUtils(object):
class InitialPositionInStream(object):

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #38341 has started for   PR 6955 at commit 96670ff.

Test build #38341 has finished for   PR 6955 at commit 96670ff.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class KinesisUtils(object):
class InitialPositionInStream(object):

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #38353 has started for   PR 6955 at commit bcefc6e.

Test build #38353 has finished for   PR 6955 at commit bcefc6e.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class KinesisUtils(object):
class InitialPositionInStream(object):

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #38416 has started for   PR 6955 at commit b810127.

Test build #38416 has finished for   PR 6955 at commit b810127.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class KinesisUtils(object):
class InitialPositionInStream(object):

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #38426 has started for   PR 6955 at commit fca416b.

Test build #38426 has finished for   PR 6955 at commit fca416b.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class KinesisUtils(object):
class InitialPositionInStream(object):

Merged build finished. Test FAILed.

retest this please

Merged build triggered.

Merged build started.

Test build #100 has started for   PR 6955 at commit fca416b.

Merged build triggered.

Merged build started.

Test build #38433 has started for   PR 6955 at commit fca416b.

Test build #100 has finished for   PR 6955 at commit fca416b.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class KinesisUtils(object):
class InitialPositionInStream(object):

Merged build finished. Test FAILed.

Test build #38433 has finished for   PR 6955 at commit fca416b.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class KinesisUtils(object):
class InitialPositionInStream(object):

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #38449 has started for   PR 6955 at commit 5082d28.

Test build #38449 timed out     for PR 6955 at commit 5082d28     after a configured wait of 175m.

Merged build finished. Test FAILed.

retest this please

Merged build triggered.

Merged build started.

Test build #104 has started for   PR 6955 at commit 5082d28.

Merged build triggered.

Merged build started.

Merged build finished. Test FAILed.

Test build #104 has finished for   PR 6955 at commit 5082d28.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class KinesisUtils(object):
class InitialPositionInStream(object):

Merged build finished. Test PASSed.

Note: tests for kinesis was disabled in the last build.

Testing Kinesis by enabling the flag for all pull requests in the PR builder is not a good idea as shown over the weekend. So could you take a look into how you can enable the Kinesis flag only when the kinesis module is touched? This should require adding additional parameters (for env vars, similar to build_profiles) to modules in the sparktestsupport - https://github.com/apache/spark/blob/master/dev/sparktestsupport/modules.py#L32

Jenkins, test this please.

Merged build triggered.

Merged build started.

@zsxwing could you update this PR by merging with the master. And you probably need to add the environment variable thing to the new module.

Test build #39028 has started for   PR 6955 at commit 5082d28.

Merged build triggered.

Merged build started.

Test build #39032 has started for   PR 6955 at commit 455f7ea.

Test build #39028 has finished for   PR 6955 at commit 5082d28.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class KinesisUtils(object):
class InitialPositionInStream(object):

Merged build finished. Test FAILed.

Jenkins, test this please.

Merged build triggered.

Merged build started.

Test build #39038 has started for   PR 6955 at commit 455f7ea.

Test build #39032 has finished for   PR 6955 at commit 455f7ea.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test build #39038 has finished for   PR 6955 at commit 455f7ea.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
 public static final class FloatPrefixComparator extends PrefixComparator
class KinesisUtils(object):
class InitialPositionInStream(object):
case class UnsafeExternalSort(

Merged build finished. Test PASSed.

Test build #1240 has started for   PR 6955 at commit 455f7ea.

Test build #1240 has finished for   PR 6955 at commit 455f7ea.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build triggered.

Merged build started.

Test build #39127 has started for   PR 6955 at commit e42e471.

LGTM. I will merge this when this build passes.

Test build #39127 timed out     for PR 6955 at commit e42e471     after a configured wait of 175m.

Merged build finished. Test FAILed.

retest this please

Merged build triggered.

Merged build started.

Test build #173 has started for   PR 6955 at commit e42e471.

Merged build triggered.

Merged build started.

Test build #39149 has started for   PR 6955 at commit e42e471.

Test build #173 has finished for   PR 6955 at commit e42e471.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test build #39149 has finished for   PR 6955 at commit e42e471.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class KinesisUtils(object):
class InitialPositionInStream(object):

Merged build finished. Test FAILed.

retest this please

Merged build triggered.

Merged build started.

Test build #174 has started for   PR 6955 at commit e42e471.

Merged build triggered.

Merged build started.

Test build #39175 has started for   PR 6955 at commit e42e471.

Merged build finished. Test FAILed.

Test build #1255 has started for   PR 6955 at commit e42e471.

Test build #39175 has finished for   PR 6955 at commit e42e471.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class KinesisUtils(object):
class InitialPositionInStream(object):

Merged build finished. Test FAILed.

retest this please

Merged build triggered.

Merged build started.

Merged build triggered.

Merged build started.

Test build #176 has started for   PR 6955 at commit e42e471.

Test build #39201 has started for   PR 6955 at commit e42e471.

Test build #1255 has finished for   PR 6955 at commit e42e471.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

retest this please

Merged build triggered.

Merged build started.

Merged build triggered.

Merged build started.

Test build #177 has started for   PR 6955 at commit e42e471.

Test build #39205 has started for   PR 6955 at commit e42e471.

Test build #176 has finished for   PR 6955 at commit e42e471.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class KinesisUtils(object):
class InitialPositionInStream(object):

Merged build finished. Test FAILed.

Test build #39201 has finished for   PR 6955 at commit e42e471.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class KinesisUtils(object):
class InitialPositionInStream(object):

Merged build finished. Test PASSed.

Test build #177 has finished for   PR 6955 at commit e42e471.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test build #39205 has finished for   PR 6955 at commit e42e471.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class KinesisUtils(object):
class InitialPositionInStream(object):

Merged build finished. Test PASSed.

Test build #177 has finished for PR 6955 at commit e42e471.
This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

@tdas looks SlowSparkPullRequestBuilder doesn't have the AWS keys.

Yeah, it does not. Other tests passed, so I am merging this. Thanks!


feat(run/markdown-preview): use client library to mint identity tokens

This change switched the run/markdown-preview sample to use the client library to mint identity tokens for requests to the private renderer service. As part of this change, we now have built-in token reuse via the caching system prescribed by oauth2.ReuseTokenSource.

datastore: Could not find a free project. Try again soon.


Remove the install dependencies step from integration-test CI

Description
The Install dependencies step of the integration-test job in https://github.com/omnivector-solutions/slurmrestd-operator/blob/main/.github/workflows/ci.yaml#L66 only installs tox, which is also installed further by the Setup operator environment step (https://github.com/omnivector-solutions/slurmrestd-operator/blob/main/.github/workflows/ci.yaml#L68) (see the logs in https://github.com/omnivector-solutions/slurmrestd-operator/actions/runs/4130049841/jobs/7144948802).
How was the code tested?
The code was tested inside the GitHub CI pipeline that has been set up for this repository.
Checklist

[x] I am the author of these changes, or I have the rights to submit them.
[ ] I have added the relevant changes to the README and/or documentation.
[x] I have self reviewed my own code.
[ ] All requested changes and/or review comments have been resolved.

giving this my +1 even though the integration tests are failing as it doesn't have anything to do with these changes


Beta 16 broken

Trying to either load a SPIR-V resource or compile SPIR-V source in C# causes a crash in beta 16. I'll see if I can help fix this upstream, but beta 16 is probably unusable.

Bug confirmed upstream, we'll wait for beta 17.


build(main): release 1.0.1

:robot: I have created a release beep boop
1.0.1 (2024-09-24)
Code Refactoring

Refactor logger initialization in MenuItemRoot's init method (f2d475d)
Refactor logger initialization method, log and postAppend methods to make possible to have different log levels inside and outside, when the external logger is used (c2ba259)
SimpleLogger: Added appropriate tests (b13ee1c)
SimpleLogger: Refactor SimpleLogger to add two static methods: canLog and acceptableLevel (b13ee1c)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v1.0.1
:sunflower:


$fmt macro

Same as $dbg, $print or $warn for the file location, just returns the concatted string instead of printing. Can be useful for things like error traces?

Yeah, this could be useful to add

I added $file.filePath & $file.lineNumber during the 2.0 work - these should suffice methinks, allows you to append these how you like - that good?

Hm, maybe that gets long/verbose and hard to keep consistent? And one can't write a wrapper utility because that would break the callstack location. I'll have to try it for a bit.


Accessories no longer responding

Unable to control any of accessory via Homebridge or HomeKit.
Confirmed that everything is still working via the Tuya Smart app on iOS.
If I uninstall the plugin and re-install it, no accessories are found.
Issue arose over the weekend of 14-15 Dec 2024.
{
"name": "TuyaWebPlatform",
"options": {
"username": "REDACTED",
"password": "REDACTED",
"countryCode": "64",
"platform": "tuya"
},
"defaults": [
{
"id": "eb74d290572afee1261ez0",
"device_type": "light",
"min_brightness": "0",
"max_brightness": "1100",
"light_characteristics": [
"Brightness"
]
}
],
"scenes": false,
"_bridge": {
"username": "0E:D4:55:BB:7C:7B",
"port": 55921
},
"platform": "TuyaWebPlatform"
}

Also seeing this. Have done a number of attempts at reconfiguring, removing cached accessoties, and no luck.  If I had to guess, I'd suspect that Tuya might have changed something at their side?
Running in a Docker container - current homebridge/homebridge:ubuntu
TuyaWebPlatform v1.1.5
Node v22.12.0
HomeBridge v1.8.5
HomeBridge UI v4.65.1
$ docker logs homebridge | grep -i tuya
...
[12/16/2024, 7:53:09 PM] Loaded plugin<EMAIL_ADDRESS>[12/16/2024, 7:53:09 PM] Registering platform<EMAIL_ADDRESS>[12/16/2024, 7:53:09 PM] [TuyaWebPlatform] Initializing TuyaWebPlatform platform...
[12/16/2024, 7:53:09 PM] [TuyaWebPlatform] Initializing child bridge 0E:31:XX:XX:XX:XX
[12/16/2024, 7:53:10 PM] [TuyaWebPlatform] Launched child bridge with PID 152
[12/16/2024, 7:53:10 PM] Registering platform<EMAIL_ADDRESS>[12/16/2024, 7:53:10 PM] [TuyaWebPlatform] Loaded @milo526/homebridge-tuya-web v1.1.5 child bridge successfully
[12/16/2024, 7:53:10 PM] Homebridge v1.8.5 (HAP v0.12.3) (TuyaWebPlatform) is running on port 32969.
[12/16/2024, 7:53:10 PM] [TuyaWebPlatform]

Confirm same problem here. Also arose on the weekend of 14-15 December 2025. Have also tried deleting cached accessories.
Homebridge log shows the following:
16/12/2024, 22:48:09] [TuyaWebPlatform] Initializing TuyaWebPlatform platform...
[16/12/2024, 22:48:09] Loading 1 accessories...
[16/12/2024, 22:48:13] [TuyaWebPlatform]
The final entry above usually would state the login details and something like "successful connected" or similar.

I'm having the same issue. It was working perfectly fine and all of a sudden it's not working from today. I've only made a change to 'show scene' and all of my devices aren't updating either on hoobs nor homekit. It works on the Smartlife App, as well as Tuya Developer API calls. Seems hoobs API call isn't triggering the API correctly? I can't seem to turn on the debugger mode on Hoobs unfortunately :(

I've had the same issue.  Then adding the bridge to HomeKit has miraculously fixed everything. But I have 0 idea how or why.


Update Partners page

@jtawes the WeWork hyperlink on the partner page and the bottom of the Civic Camp main page isn't right. The url doesn't directly go to their website.
Also we need to add Innovate Carolina - logo is in the sponsor logo folder.

@jtawes I don't see WeWork on the main Partners page anymore.

Sorry, fixed it. I had to change the galleries to get the links to work.


Localize texts

[x] English
[x] Catalan
[x] Dutch
[x] English (UK)
[x] French
[x] German
[x] Hungarian
[x] Italian
[x] Polish
[x] Portugese
[x] Spanish
[x] Welsh

We have a number of translations for the old App; we can ask the community to provide them!

Tested on:

iPhone 11 Pro Max, iOS 16.7
Version:
geteduroam version 2.0.1 (60)
getgovroam version 2.0.1 (38)

✅ test approved
I see that I can set the apps in the languages set above. When I select the other language, I see that the app is updated


Add the option to set custom_user_agent

Add the option to set custom_user_agent when opening new connections.

Thanks!


Version bumps

bumping to commons-parent 53, spring 5.3.19, codeql-action 2

Ah. I didn't realize we were creating changes entries for that. Should I create an entry for this change as well? https://github.com/apache/commons-configuration/pull/140

Not small changes like that one, or fixing imports, simplifying a bit shift operation, etc. Unless you feel like there's a risk that that change could cause a regression.
Updates to dependencies normally go to changes.xml, including the Commons Parent, e.g. https://github.com/apache/commons-lang/blob/80889fc45cbfb3da0a916e0fc0d51663bb970c2a/src/changes/changes.xml#L283
But if you have multiple updates in a single PR, you can add a single entry with one update per line, e.g. https://github.com/apache/commons-configuration/blob/69260fa1e9c4f87b1abf1c301825a53a722b6007/src/changes/changes.xml#L103-L107

For dependabot updates, I add an entry, squash the commits, and push-force and merge :+1:

How is this?

Thanks, @kinow!


Caching is disrupting UI rolls

We have seen a circumstance twice in recent rolls where the HTML and JS propagate at different rates. For example a button added in HTML appears in the UI, but isn't wired up to the corresponding JS.
Something is probably wrong on the cache expiry settings of the various resources.

Static contents are set to expire every 3 hours through our app.yaml - these can be set to a lower threshold but there are trade-offs to consider.
Ref: https://cloud.google.com/appengine/docs/standard/python/config/appref#static_cache_expiration

I haven't seen this in our recent releases, but it's possible I'm just hard-reloading everything without thinking about it.
@domesticmouse, do you mind checking our cache settings?

Given the original description, I’d suspect the issue is actually the delay between rendering the HTML & JS, which is a fairly standard issue for web apps.


Fix insert graph method typing

Previously, the SingleQueryBuilder definition went first, so even if an array was passed as graph, it would be typed as SingleQueryBuilder. This created all sorts of weird effects, like making it impossible to write a type predicate on a model subclass.
This commit reorders it so it tries to type it as ArrayQueryBuilder first. It also adds a test to make sure that model subclasses work correctly.

Wow! I got a Maximum call stack exceeded when running yarn test:typings on this branch.
RangeError: Maximum call stack size exceeded
    at String.replace (<anonymous>)
    at /Users/rmenezes/code/objection.js/node_modules/typescript/lib/tsc.js:53002:90
    at Array.map (<anonymous>)
    at recursiveTypeRelatedTo (/Users/rmenezes/code/objection.js/node_modules/typescript/lib/tsc.js:53002:62)
    at isRelatedTo (/Users/rmenezes/code/objection.js/node_modules/typescript/lib/tsc.js:52642:34)
    at typeArgumentsRelatedTo (/Users/rmenezes/code/objection.js/node_modules/typescript/lib/tsc.js:52949:39)
    at relateVariances (/Users/rmenezes/code/objection.js/node_modules/typescript/lib/tsc.js:53490:34)
    at structuredTypeRelatedToWorker (/Users/rmenezes/code/objection.js/node_modules/typescript/lib/tsc.js:53438:46)
    at structuredTypeRelatedTo (/Users/rmenezes/code/objection.js/node_modules/typescript/lib/tsc.js:53080:30)
    at recursiveTypeRelatedTo (/Users/rmenezes/code/objection.js/node_modules/typescript/lib/tsc.js:53051:53)
error Command failed with exit code 1.

I noticed your previous struggles with this:
https://github.com/microsoft/TypeScript/issues/33460#issuecomment-534856200
Wow, we're really stretching what Typescript can do, huh? I'm going to give this a think...

Closing because Typescript won't let us fix this.
I'm going to try remove custom query builders in a fork and use that instead. See for more info: https://github.com/Vincit/objection.js/pull/2159#issuecomment-985586202


TaskRef: refer to a Task from another namespace

Expected Behavior
It would be nice to be able to refer a Task from another namespace. Something like the following.
apiVersion: tekton.dev/v1alpha1
kind: Pipeline
metadata:
  name: standard-go-pipeline
spec:
  params:
  - name: foo
    description: repository to clone
  tasks:
  - name: task-a
    taskRef:
      name: foo
      from:
        namespace: another-namespace

or
apiVersion: tekton.dev/v1alpha1
kind: Pipeline
metadata:
  name: standard-go-pipeline
spec:
  params:
  - name: foo
    description: repository to clone
  tasks:
  - name: task-a
    taskRef:
      name: foo
      namespace: another-namespace

The security aspect of this should be simple, we let kubernetes RBAC handle this (aka if the user can't access Task from the other namespace, then we fail and report an error :angel:
Actual Behavior
To refer a Task in taskRef, today you need to have this Task in the same namespace.
Additional Info
Related to https://github.com/tektoncd/pipeline/issues/964 (and https://docs.google.com/document/d/1O8VHZ-7tNuuRjPNjPfdo8bD--WDrkcz-lbtJ3P8Wugs/edit#)
/kind feature

/assign

Should we allow this for Pipelines/Conditions as well? Related: we have a feature request for Cluster scoped Conditions and Pipelines: https://github.com/tektoncd/pipeline/issues/1266

@dibyom right, this is something we need to discuss then. My gut feeling is yes, but maybe this means we don't need ClusterTask and other cluster scoped objects then :angel:

One concern I have with this is that at least currently the Tekton Controller is doing the taskref lookup with elevated privilege. This might be a real problem in a multi-tenant environment where we want to prevent lookup of private Tasks that might inadvertently contain secret-ish materials.

I'm concerned about the statement in the proposal:

The security aspect of this should be simple, we let kubernetes RBAC handle this (aka if the user can't access Task from the other namespace, then we fail and report an error :angel:

I don't think it's clear what would happen later on if the permissions changed. If any garbage collection scenarios would be changed with this (I don't believe owner references work across namespaces). Or what it would mean to have an instance of this TaskRun by someone who didn't have permission to see the other namespace (should it fail? should it succeed?); if it succeeds is there possibility of privilege escalation? Tasks can also reference things like volumes, service accounts, secrets and config maps. How do you reference those across namespaces ensuring permissions are maintained?
Also, I think there are side-channel attacks that open up if you start referencing things across namespaces. Unless you're very careful about error messages, you could probe for Tasks in other spaces by submitting pipelines and looking at the results.

We need to consider the overlap with ClusterTask and we are approaching the beta release soon. If we support both it and ClusterTask if goes into beta then do we need to support both in the long term?
Yes as @skaegi mentioned on other hand we need to handle the permission or authorization issue.

One concern I have with this is that at least currently the Tekton Controller is doing the taskref lookup with elevated privilege. This might be a real problem in a multi-tenant environment where we want to prevent lookup of private Tasks that might inadvertently contain secret-ish materials.

One way to address the permission issue by either placing the authorization checks in the tekton pipeline webhook based on the user's token/ServiceAccount provided PipelineRun/TaskRun or impersonate the request to resolve the TaskRef with ServiceAccount mentioned in PipelineRun(Pipeline)/TaskRun definition.

FWIW I'm neutral to -1 on this, but our use case (this was echoed by @rakhbari on the WG call) is that we use namespaces as a mechanism for isolation and some security guarantees, so if it were implemented we couldn't use it.

Slight preference for design 2:
  - name: task-a
    taskRef:
      name: foo
      namespace: another-namespace

Re. service account issues - could we initially assume the controller service account has the permissions it needs, and ask users to add more permissions to that account if needed?

Re. service account issues - could we initially assume the controller service account has the permissions it needs, and ask users to add more permissions to that account if needed?

The problem is opposite, if the user has less permission than the controller (which might easily be the case), then we are in a situation of privileged escalation (kinda).

I'm curious, can you not get the same/similar result by using a ClusterPipeline instead?
The nice thing about using a ClusterXXX is, if you create it, you go in knowing that your pipeline is not scoped to a namespace. This should resolve the many security concerns.

The problem is opposite, if the user has less permission than the controller (which might easily be the case), then we are in a situation of privileged escalation (kinda).

Ah interesting!! Is this already the case then, even with Tasks in the same namespace? Like a user only needs to be able to create a TaskRun or a PipelineRun, and the controller will fetch any Tasks etc. that are needed, and even create pods, even if the user doesn't have permission to?
(In some ways this reminds me of https://github.com/tektoncd/triggers/issues/77)

@bobcatfish yeah that's the case already :angel: You can refer a Task in the same namespace even if you don't have the right to get/list/update/… Tasks :angel:

Continuing discussion on https://github.com/tektoncd/pipeline/pull/1420#issuecomment-547798114

Another worry was on updates on the Task definition — if the refered task gets updated, it affect all the TaskRun/Pipeline/… that depends on it, and might break something, where a copy approach does not.

But a  namespaced task or a cluster-task does not solve this issue that the task definition can change and the next pipeline-run can fail.
So what is the recommended approach if a task definition need to be shared amongst only few namespaces/projects but not all?

@sthaha IMHO we're getting into the area of artifact versioning and that's already covered by your SCM tool, in most cases github. If you organize your shared tasks properly in a github repo, that repo can be attached to other repos as a git submodule. That submodule is defined at a particular SHA of the shared tasks repo giving you automatic version control.  You then have the choice to examine the shared tasks updates (at the HEAD of that repo), even set up a pipeline to test out the HEAD of that repo and if all is fine, update your submodule SHA to the HEAD and re-apply into your cluster again.
Lots of common script repos are shared this way here inhouse. The owners of the repos that have a dependency on the shared script repo decide when they're ready to update their repo to the HEAD of the shared repo.

@rakhbari thanks,  that is a good enough approach albeit it does feel like working around the limitation that a task can't be shared outside a namespace.

Trying to understand how is this different from using a ClusterTask?
For example in a pipeline using:
taskRef:
      name: foo
      namespace: another-namespace

vs
taskRef:
      name: foo
      kind: ClusterTask

ClusterTask available / viewable by everyone in the cluster vs if namespaced, the access to the task can be controlled by RBAC if we choose to implement this feature request.

@sthaha I actually don't see it as a "limitation" at all. I see it as proper use of existing tools features (rather combining features of different tools) to achieve an end. Use the right tool for the job. TektonCD shouldn't include any features that creep into version control. We already have a tool for that (Github). Hopefully that makes more sense. 😃

What should be our final take on this issue?
@vdemeester @bobcatfish @dibyom @sthaha @rakhbari @poy @ahpook @skaegi
(sorry for wide ping 🙏)

My take on this is that time will tell. Right now the overwhelming consensus seems to be that we do not need this feature (non-issue)  and if we can survive ( no demand for this feature from community) without the need for a SAR in tekton-controller/webhook since namespaces becomes the natural boundary for isolation then it does keep the codebase simpler.
I am happy for us to close this issue and revisit when there is a demand.

Given @sthaha 's comment I'm going to close this issue for now. We can revisit it again in the future
/close


1.19 support

If you use this mod with 1.19 fabric and 'Slight' Gui Modifications mod, it crashes game.
latest.log

yes


How to install Supermium 122 (new installer) silently?

Hello, I am using supermium well but I have a problem.
The problem is how to install supermium silently?
I integrated Supermium on windows 7 installation media, but it's not possible to use silent install flag on new version of 122.
Is there any way flag for silent installation?
And other BIG Problem is unable to uninstall Supermium.
This issue should be fixed.

Portable version would be nice too.

Supermium Portable-Ready is exclusive to subscribers of the Patreon:
https://www.patreon.com/win32
As for silent installation, that is currently not supported by the installer. For integration into Windows installation media, you could boot into Audit Mode and install all desired applications there and convert the vmdk (assuming vmware) back into a WIM. It's the most efficient way to get fully integrated, OEM-like restore discs of your own.

"exclusive to subscribers", oooook -_- Staying with catsxp then...

You can make portable yourself. Just unpack the installer. It is a regular 7-zip SFX archive. And make .bat or .lnk for chrome.exe with one parameter:
Chrome.exe **--user-data-dir="User Data"**
That's all. So easy.

Same issue here


feature: View column

This pull request introduces a new View column that can be used to render a custom view inside of a column cell.
It can be used like this:
View::make('Custom Column')
    ->view('path.to.custom.view')

By default, the view you specify with have access to the current record in the table ($record) as well as the column class itself ($column).
You can also pass through additional data using the data() method:
View::make('Custom Column')
    ->view('path.to.custom.view')
    ->data([
        'user' => Filament::auth()->user(),
    ])

@danharrin Instead of having the separate view and data methods, could we also accept an array of data in view() - what do you think?

@danharrin Instead of having the separate view and data methods, could we also accept an array of data in view() - what do you think?

Second view param could call data internally?

@danharrin Instead of having the separate view and data methods, could we also accept an array of data in view() - what do you think?

Second view param could call data internally?

Yeah, that's all it would do just a nice shortcut.

Cool, that keeps it consistent with Laravel then.

I absolutely love this idea! Nice @ryangjchandler !


Fixes for cq.cfg

A fun bug happened because our CQ config landed both global/ and
branch/ in the same commit. LUCI tries to discover where cq.cfg with
refs.cfg, however the processing of cq.cfg is done before refs.cfg. This
means that when everything was landed at once, the processing of cq.cfg
didn't where to look, and then refs.cfg was processed, but too late.
So this whitespace change will dirty cq.cfg and cause LUCI to discover
it.
PTAL @SenorBlanco

Thanks!


Wrong initial status in variant generation

variants created from a template seem to auto-check every box possible for the card(s) inserted by the feature?

d677980b78033e0cf1e4b3348c2863afbc55487c


Added variadic overloads to layout(:) and sv(:)

Added variadic overloads to layout(:) and sv(:) to make array usage optional.

This is just way too cool!

While Array syntax made sense for sv hierarchy, using it for layout could have been misleading for layout
This solves the ctrl + i auto indentation that was not the best (ending ]) was offset
This is less code without harming readability.
I love it !

We will need to update the docs in the README.


Gemini wont produce any results

Description
I have tried everything, followed the steps to set up the API key, and all I get when I try any command is the following...
Could not access Gemini.
This may be because Gemini has decided that your prompt did not comply with its regulations. Please try another prompt, and if it still does not work, create an issue on GitHub.
Steps To Reproduce
No response
Current Behaviour
nothing happens
Expected Behaviour
something to happen

Seems like this issue is about a specific extension, not the API. Would you mind opening a new issue using the correct template so that the authors of the extension are properly aware of it?