Argument handling, invalid option error

I usually update homebrew approx every few days - week and I’ve just started to have an issue with passing arguments to brew bundle exec.
I think that the issue I’m having, could be caused by this recent PR:
https://github.com/Homebrew/homebrew-bundle/pull/643
#! /usr/bin/env zsh

brew bundle exec \
  mint run swiftlint \
  swiftlint --path "$TARGET_NAME" --config "../swiftlint.yml"

When running that script, I’m getting the following output:
Usage: brew bundle subcommand

Bundler for non-Ruby dependencies from Homebrew, Homebrew Cask and the Mac App
Store.

  brew bundle [install]

  Install or upgrade all dependencies in a Brewfile.

  brew bundle dump

  Write all installed casks/formulae/taps into a Brewfile.

  brew bundle cleanup

  Uninstall all dependencies not listed in a Brewfile.

  brew bundle check

  Check if all dependencies are installed in a Brewfile.

  brew bundle exec command

  Run an external command in an isolated build environment.

  brew bundle list

  List all dependencies present in a Brewfile. By default, only Homebrew
dependencies are listed.

        --file                       Read the Brewfile from this file. Use
                                     --file=- to pipe to stdin/stdout.
        --global                     Read the Brewfile from ~/.Brewfile.
    -v, --verbose                    install output is printed from commands
                                     as they are run. check prints all missing
                                     dependencies.
        --no-upgrade                 install won't run brew upgrade on
                                     outdated dependencies. Note they may still
                                     be upgraded by brew install if needed.
    -f, --force                      dump overwrites an existing Brewfile.
                                     cleanup actually perform the cleanup
                                     operations.
        --no-lock                    install won't output a
                                     Brewfile.lock.json.
        --all                        list all dependencies.
        --brews                      list Homebrew dependencies.
        --casks                      list Homebrew Cask dependencies.
        --taps                       list tap dependencies.
        --mas                        list Mac App Store dependencies.
        --describe                   dump a description comment above each
                                     line, unless the dependency does not have a
                                     description.
        --no-restart                 dump does not add restart_service to
                                     formula lines.
        --zap                        cleanup casks using the zap command
                                     instead of uninstall.
    -h, --help                       Show this message.
Error: invalid option: --path

If I just run the command  brew bundle exec xcodebuild --help, I’m getting similar output.
Here is some additional info:
> brew config
HOMEBREW_VERSION: 2.2.6-31-g2834a75
ORIGIN: https://github.com/Homebrew/brew.git
HEAD: 2834a75f195ef632a23533098777b32f82ea4df7
Last commit: 13 hours ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 1ca9851f299d383843972104ad90b6e4b7641165
Core tap last commit: 4 hours ago
HOMEBREW_PREFIX: /usr/local
HOMEBREW_GITHUB_API_TOKEN: set
CPU: octa-core 64-bit skylake
Homebrew Ruby: 2.6.3 => /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
Clang: 11.0 build 1100
Git: 2.25.0 => /usr/local/bin/git
Curl: 7.68.0 => /usr/bin/curl
Java: 1.8.0_92
macOS: 10.15.4-x86_64
CLT: <IP_ADDRESS>
Xcode: 11.3.1

> brew environment
HOMEBREW_CC: clang
HOMEBREW_CXX: clang++
MAKEFLAGS: -j8
CMAKE_PREFIX_PATH: /usr/local
CMAKE_INCLUDE_PATH: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/usr/include/libxml2:/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/System/Library/Frameworks/OpenGL.framework/Versions/Current/Headers
CMAKE_LIBRARY_PATH: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/System/Library/Frameworks/OpenGL.framework/Versions/Current/Libraries
PKG_CONFIG_LIBDIR: /usr/lib/pkgconfig:/usr/local/Homebrew/Library/Homebrew/os/mac/pkgconfig/10.15
HOMEBREW_GIT: git
HOMEBREW_SDKROOT: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk
ACLOCAL_PATH: /usr/local/share/aclocal
PATH: /usr/local/Homebrew/Library/Homebrew/shims/mac/super:/usr/bin:/bin:/usr/sbin:/sbin

Brewfile
# https://github.com/Homebrew/homebrew-bundle

brew "mint"
brew "rbenv"
brew "zsh"

brew bundle exec \

Change this to brew bundle exec -- (or generally add the -- somewhere before --path.

Thanks @MikeMcQuaid, much appreciated!


Test Case Needed for Non-Existent Image in GetPatchCmd

Description:
While reviewing the test coverage for the GetPatchCmd function, it was noticed that there is no test case that verifies the behavior of this function when it's run with a non-existent image argument.
This scenario is important to test because it ensures that the function correctly handles invalid inputs and returns the appropriate error message.
The proposed test case should:

Create a mock Kubescape interface
Call the GetPatchCmd function with the mock interface
Run the command with a non-existent image argument
Check that there is an error and the error message is "image tag is required"

This issue can be closed once the test case has been implemented and is passing.

Assign me this issue,  I am working on this issue.

Hey! @Umair0343. Can you confirm if the issue has been resolved with this PR?

Hey! @Umair0343. Can you confirm if the issue has been resolved with this PR?

Hey, @ShivamJha2436, yes.

The issue was resolved with the PR: Update patch_test.go (Add Test Case for Non-Existent Image in GetPatchCmd) #1529

Thanks for letting me know @Umair0343 .


Blacksmith spawns XP orbs client-side after repair

You had me confused for a second, but i know what you mean now :P


Upgrade django misc

Purpose
A group of small Django upgrade related fixes.
Changes

removes unused PostgresFailoverRouter comment
Stop direct assigning m2m fields
ensure storage region doesn't use cached property.

QA Notes
Please make verification statements inspired by your code and what your code touches.

Verify
Verify

What are the areas of risk?
Any concerns/considerations/questions that development raised?
Documentation

Side Effects

Ticket

Put ES metrics library requirement pinning in here.


Allow bulk editing of members

Should be able to edit more than one members roles at a time. So for example you might want to change user1, user2 and user3 to the role of admin.
Is it possible to update the current user edit method to accept an array of user ids @leijie-wang ? To me this seems to make the most sense as they it will work for single and bulk editing, however if you have a better solution please post.

I added a few code to support this, but i am wondering which branch i should merge with?

If push/merge into the new-frontend-members branch. Have associated that branch with this issue now.

I was thinking if a user can have multiple roles then would it also make sense to be able to allow a user to assign or revoke multiple roles too?
So for example you want to assign 5 users the role of admin and special roles x then you would currently have to perform 2 submissions (one for each role you want assign). If we allow users to assign multiple roles to multiple users this could be performed in only 1 submission.
So roles would an array of roles like users.

I am a little bit worried that this might be confusing to users sometimes, for example, when one of the users does not have one of the revoked roles. I also think cases where users need to assign  multiple roles to multiple users might be quite infrequent?

Ok let's leave it at assigning or revoking one role for multiple users as I agree with your point above.


ZeroCopyOutputStream and flat_buffer..

A question on a closed item from some months ago if somebody happens to know.
https://github.com/boostorg/beast/issues/1180#issuecomment-402920428
Trying the code from this issue I get warnings about a missing_const_iterator on 'boost::asio::mutable_buffer.  I was calling it via:
            ZeroCopyOutputStream<beast::flat_buffer> zcopy(outputbuffer_, 8192);
I can't spot any iterators on flatbuffer.  Anybody know what I'm missing?  (using #define BOOST_BEAST_VERSION 181)
Cheers and thanks

Whoops... that ZeroCopyOutputStream is from before Asio made the changes to the buffer sequences.
Try using this instead:
using iterator = buffers_iterator_type<buffers_type>;

The metafunction buffers_iterator_type is here:
https://github.com/boostorg/beast/blob/5361224a7d4c3b318fc92616eff23442851bdc6a/include/boost/beast/core/buffer_traits.hpp#L145

Thanks @vinniefalco.  That got me headed in the right direction.
For anybody that happens upon this comment I ended up with this.  (Slight modification to begin() and end() as well to get it to build.
/** Implements ZeroCopyOutputStream around a Streambuf.
    Streambuf matches the public interface defined by boost::asio::streambuf.
    @tparam Streambuf A type meeting the requirements of Streambuf.
*/
template <class Streambuf>
class ZeroCopyOutputStream
    : public ::google::protobuf::io::ZeroCopyOutputStream
{
private:
    using buffers_type = typename Streambuf::mutable_buffers_type;
    using iterator = boost::beast::buffers_iterator_type<buffers_type>;
    using mutable_buffer = boost::asio::mutable_buffer;

    Streambuf& streambuf_;
    std::size_t blockSize_;
    google::protobuf::int64 count_ = 0;
    std::size_t commit_ = 0;
    buffers_type buffers_;
    iterator pos_;

public:
    explicit
        ZeroCopyOutputStream(Streambuf& streambuf,
            std::size_t blockSize);

    ~ZeroCopyOutputStream();

    bool
        Next(void** data, int* size) override;

    void
        BackUp(int count) override;

    google::protobuf::int64
        ByteCount() const override
    {
        return count_;
    }
};

//------------------------------------------------------------------------------

template <class Streambuf>
ZeroCopyOutputStream<Streambuf>::ZeroCopyOutputStream(
    Streambuf& streambuf, std::size_t blockSize)
    : streambuf_(streambuf)
    , blockSize_(blockSize)
    , buffers_(streambuf_.prepare(blockSize_))
    , pos_(net::buffer_sequence_begin(buffers_))
{
}

template <class Streambuf>
ZeroCopyOutputStream<Streambuf>::~ZeroCopyOutputStream()
{
    if (commit_ != 0)
        streambuf_.commit(commit_);
}

template <class Streambuf>
bool
ZeroCopyOutputStream<Streambuf>::Next(
    void** data, int* size)
{
    if (commit_ != 0)
    {
        streambuf_.commit(commit_);
        count_ += commit_;
    }

    if (pos_ == net::buffer_sequence_end(buffers_))
    {
        buffers_ = streambuf_.prepare(blockSize_);
        pos_ = net::buffer_sequence_begin(buffers_);
    }

    *data = boost::asio::buffer_cast<void*>(*pos_);
    *size = static_cast<int>(boost::asio::buffer_size(*pos_));
    commit_ = *size;
    ++pos_;
    return true;
}

template <class Streambuf>
void
ZeroCopyOutputStream<Streambuf>::BackUp(int count)
{
    assert(count <= commit_);
    auto const n = commit_ - count;
    streambuf_.commit(n);
    count_ += n;
    commit_ = 0;
}


Add support for dual heaters/temperature range

Is your feature request related to a problem? Please describe:
When trying to use "auto" mode (which will heat OR cool depending on the ambient temperature), it is impossible to set a temperature range.
Describe the solution you'd like:
Ability to set a minimum and maximum temperature range; currently they are locked to the same number.
Describe alternatives you've considered:
In this case, I don't believe an alternative is warranted.
Additional context:
Screenshot of the issue:

Minimum and maximum temperatures are inseparable
Screenshot of expected behavior (using a different thermostat, obviously):

Minimum and maximum temperatures are seperated

This is a limitation of GREE AC units. They do not accept temperature ranges in Auto mode. The Home App behavior is in sync with the device capabilities.


KE-38098 Spark driver pod cleanup when application is completed

What changes were proposed in this pull request?

Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

https://github.com/Kyligence/spark/pull/528


Can we see private repos within this dataset?

Within the dataset are we able to view user contributions for private repositories. For instance, I am getting a lot of activity for the  LombiqBot on Github. For instance,  for 8-25-2020  I get 2938678 PullRequest Events. And LombiqBot is a trending user on https://www.gitlive.net/.    But, if I head to https://github.com/LombiqBot,  there are no contributions visible for 2020.

Received my answer. Thanks!

Received my answer. Thanks!

Hi Vanessa, I wonder if you can share your answer? I am also confused by the activity.

No, you cannot see private repos. Unless, a private repo was made public and history is pushed.


custom-template-text doesn't fit container

There is an issue once text is too long. See screen below

Yea, examples are not super well done, if you think that this is plugin's fault, let me know 👍 😄


feature_location

Location data for correspondence will soon be added. Experiment with how this could be visualised and used as a filter.

Discussion with James is to use this as one of the spiral sort orders. Will add this once James provides the data. Closing now as nothing really to do.


Today's Fullstack ⚡📻  Show Notes 1/11 @ 8th Light Downtown

Stand up

ProTip: New to Fullstack? Check out our member directory and add yourself to the list: https://github.com/fullstackla/pairing-meetup/blob/master/community/README.md

How should we improve this page? How can we open source and share this project so other meetup groups can make pages like this of themselves?

ProTip: Is your 2017 resolution to code more katas? Try a different language? Join our Exercism team http://exercism.io/teams/dtla-pair-programming/ Set it as your desktop homepage.

📅  Fullstack Winter Break: https://github.com/fullstackla/pairing-meetup/issues/122

Open source picks!

@gr2m wrote a sauce labs thing: https://github.com/gr2m/selsa
@cityhubla digs into LA data and maps it: https://cityhubla.github.io/lacity_exploration_12/#13.08/34.1389/-118.2547

Where to start:

Completely new to coding? Start by pairing on Exercism puzzles.
First Timers Only: New to contributing to applications/projects: 1) https://github.com/fullstackla/pairing-meetup/issues/127 2) https://github.com/fullstackla/pairing-meetup/issues/125 3) https://github.com/fullstackla/pairing-meetup/issues/127 4) https://github.com/fullstackla/pairing-meetup/issues/125  5) https://github.com/exercism/exercism.io/issues/3228#issuecomment-257933565
I want to try Go: https://github.com/fullstackla/pairing-meetup/issues/1
I am itching to work on a group project but I don't have ideas or friends to start one with: https://github.com/fullstackla/pairing-meetup/issues/134 https://github.com/fullstackla/pairing-meetup/issues/125 https://github.com/fullstackla/pairing-meetup/issues/126

Contributors + stuff you want to work on:

Attendees: https://www.meetup.com/la-fullstack
@kpearson
@machikoyasuda - I am going to work on the webpage that shows the Fullstack 2017 schedule. I will write some code to calculate directions, show parking info, show Metro info, all sorts of fun stuff.

@dopatraman - I'll be working on a slackbot that can order pizza

For any new contributors: There is a typo in the fullstack LA code of conduct: The word "religion" should be in the sublist of " + offensive verbal comments related to".

https://github.com/fullstackla/fullstackla.github.io/pull/45 hi @xuhdev we missed you a lot

hi @machikoyasuda gonna be there today!

@dcmoore & @xuhdev & i paired on these commits in Clojure:
https://github.com/dcmoore/resilient-integration-workshop/commit/65e2143bc809324f8e71b3d85fd4a4a655e01520
https://github.com/dcmoore/resilient-integration-workshop/commit/8d5b114620236e1f6d16ca643a4b76523e4d822e
and i learned git diff --cached
and i learned you can change the git authors manually. doesn't show up on github though (yet)


logger prints/output only first argument in v 3.2.0

Environment

winston version?

[ ]<EMAIL_ADDRESS>

node -v outputs:

[ ] v10.13.0

Operating System? (macOS)

Problem
logger.info('First', 'Second') is printing only First in the console and in File.
With 3.0, this is printing both arguments, First & Second. (Second in the new line)
What do you expect to happen instead?
Expecting output as
First
Second

What formatters and other config are you using?  In particular, handling of splats/metadata has changed from 3.0 to 3.2.

You could log like logger.info(['First', 'Second']) if you need that kind of call.  Generally winston isn't really designed for that call style; for the leveled log methods, the first param is a string message, and all other params are treated as splats/metas.
That being said, I think https://github.com/winstonjs/logform/pull/85 with the metadataArray might help achieve what you want.  I can leave this issue open till that gets merged.

I think this is such a breaking change...

You could log like logger.info(['First', 'Second']) if you need that kind of call. Generally winston isn't really designed for that call style; for the leveled log methods, the first param is a string message, and all other params are treated as splats/metas.
That being said, I think winstonjs/logform#85 with the metadataArray might help achieve what you want. I can leave this issue open till that gets merged.

But util.format('First', 'Second') will output First Second, the same as console.log and winston@2.  Why winston@3  with format splat  break this behavior?

You could log like logger.info(['First', 'Second']) if you need that kind of call. Generally winston isn't really designed for that call style; for the leveled log methods, the first param is a string message, and all other params are treated as splats/metas.
That being said, I think winstonjs/logform#85 with the metadataArray might help achieve what you want. I can leave this issue open till that gets merged.

But util.format('First', 'Second') will output First Second, the same as console.log and winston@2. Why winston@3 with format splat break this behavior?

i

I think this is such a breaking change...
The partial solution is:
const wrapper = ( original ) => {
    return (...args) => {
      for (let index = 0; index < args.length; index++) {
        if(args[index] instanceof Error){
          args[index] = args[index].stack
        }
      }
      original(args.join(" "))
    }
};

logger.error = wrapper(logger.error);
logger.warn = wrapper(logger.warn);
logger.info = wrapper(logger.info);
logger.verbose = wrapper(logger.verbose);
logger.debug = wrapper(logger.debug);
logger.silly = wrapper(logger.silly);

agree, it's the break change.
the meta key in the info object is gone under the new version.
the new key named as the numeric, such as { '0': 'string', '1': 'object'}

Definitely a breaking change. The wrapper works in a very limited way.


test failure due to missing uuid against legacy provider

health tests fail on:
https://github.com/apache/incubator-openwhisk-package-kafka/blob/master/tests/src/test/scala/system/health/BasicHealthTest.scala#L96
activation result is "result":{"response":{"success":true}}}
details
{"duration":878,"name":"messageHubFeed","subject":"xxxxx","activationId":"a8fdba8b785f41d98e02b64a768a83ba","publish":false,"annotations":[{"key":"limits","value":{"logs":10,"memory":256,"timeout":60000}},{"key":"path","value":"whisk.system/messaging/messageHubFeed"}],"version":"0.0.22","response":{"status":"success","statusCode":0,"success":true,"result":{"response":{"success":true}}},"end":1499095251408,"logs":["2017-07-03T15:20:50.802808123Z stdout: Checking Message Hub credentials...","2017-07-03T15:20:51.300456642Z stdout: Status code: 200","2017-07-03T15:20:51.300683477Z stdout: Successfully authenticated with Message Hub","2017-07-03T15:20:51.300736892Z stdout: Topic exists.","2017-07-03T15:20:51.406753626Z stdout: Status code: 200"],"start":1499095250530,"namespace":"xxxxx"}

This test is not intended to pass on provider versions prior to 1.1.0. The version of the test must match the version of the provider you are testing against.


update README with build instructions

Update README.md with instructions to build Sia from source.

Hello! Nice to see a PR from you again

I am not sure why your build is failing, I think it's related to travis maxing out the number of requests allowed for one of our dependencies, it downloads it every time. We should be able to have a fix in the next few days.

Oh, it's because you aren't pushing from the Sia repo, the keys to get around the ratelimit only work for the Sia repo. I will fix this by moving your commit to a branch on our repo.

Closing as this has been moved to https://github.com/NebulousLabs/Sia/pull/1098


Try a second integration with Lwt, with Luv as an Lwt_engine

Luv already integrates with the Lwt core, by providing an alternative Lwt I/O library (a logical sibling to Lwt_unix) with an Lwt promise-based API.
This issue is about turning Luv into an Lwt_engine so that both the Lwt core and Lwt_unix are running on top of Luv. It might not actually be possible, but it would be instructive to know what the limit is. Integrating as an Lwt_engine would offer a very gradualistic path to porting Lwt to Luv.

@ulrikstrid is doing this in https://github.com/ocsigen/lwt/pull/811.


feat: abstract cross platform server start/stop concerns

Regarding the non obvious aspect of it daemonising:
Problems arising from it not being obvious that systemd was involved:

https://github.com/jmorganca/ollama/issues/1152
https://github.com/jmorganca/ollama/issues/1084
https://github.com/jmorganca/ollama/issues/1391#issuecomment-1842125520
https://github.com/jmorganca/ollama/issues/1018
https://github.com/jmorganca/ollama/issues/727
https://github.com/jmorganca/ollama/issues/707

Problems arising from lack of server control:

https://github.com/jmorganca/ollama/issues/300
https://github.com/jmorganca/ollama/issues/793
https://github.com/jmorganca/ollama/issues/546

It looks like some of these have been closed as directing users to handle it via systemd.
systemctl stop ollama.service

Should this not be made obvious by an abstraction?
ollama server start --system

# linux: prompts for sudo to create system.d unit if it doesn't exist and start it
# mac: something something something steve jobs?

ollama server stop --system

# again, sudo required.

ollama server start

# no sudo required

# user presses: ctrl + d

# server stops.

Originally posted by @airtonix in https://github.com/jmorganca/ollama/issues/690#issuecomment-1852844736

Perhaps all this could be easier if these lines were optional?
https://github.com/jmorganca/ollama/blob/main/scripts/install.sh#L113C4-L115
ask the user during install?

second this

sudo systemctl stop ollama.service


[fix][broker] Update TransferShedder underloaded broker check to consider max loaded broker's msgThroughputEMA and update IsExtensibleLoadBalancerImpl check

Motivation

Checking zero traffic is not practical to identify if a broker is too underloaded or not(when first joining the cluster). There might be some health-checking traffic, which might make the broker's traffic slightly bigger than 1 byte/s. We better consider some relative measurements to check if a broker is significantly underloaded.
Modifications

Update TransferShedder underloaded broker check to consider max loaded broker's msgThroughputEMA
Delete isLoadManagerExtensionEnabled(ServiceConfiguration conf) to use only isLoadManagerExtensionEnabled(PulsarService pulsar) func

Verifying this change

[x] Make sure that the change passes the CI checks.

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

[ ] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The threading model
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] The metrics
[ ] Anything that affects deployment

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository:

Hi, @mattisonchao I saw you merged this PR , https://github.com/apache/pulsar/pull/22379. Can we also merge this too? It appears that CI is broken now?


Release build apk size

Describe the bug
This is not a bug, rather concerning the app's release apk size. I have been using couchbase_lite. Now that I wanted to try cbl-flutter as a drop in replacement, the app still function as expected but apk size (without much code change) jumped from 23MB to 41MB. Is this expected behavior or did I miss some key configurations here? Right now I only use cbl-flutter for android and iOS, but soon I will try to implement on desktop environments as well. Thank you.
To Reproduce
Steps to reproduce the behavior:

flutter build apk in terminal

Expected behavior
Modestly increase in apk size
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):

OS:

 cbl: ^2.0.0+0
 cbl_flutter: ^2.0.0
 cbl_flutter_ce: ^2.0.0

Additional context
flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.0.1, on Ubuntu 20.04.4 LTS 5.13.0-52-generic, locale en_US.UTF-8)
[✓] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
[✓] Chrome - develop for the web
[✓] Linux toolchain - develop for Linux desktop
[✓] Android Studio (version 2021.2)
[✓] VS Code (version 1.68.1)
[✓] Connected device (4 available)
[✓] HTTP Host Availability

An increase of ~20 MB is to be expected, but it's not as bad as it seems. The Couchbase Lite binaries are ~5 MB for each supported architecture, and APKs are built to run on 4 architectures.
When submitting an app to the Play Store as an app bundle, multiple versions of the app are created for distribution. These versions are architecture-specific and will only contain the binaries for one architecture.

Actually, I just looked into android app sizes a bit, and it turns out for Android the size of the binaries is around 16 MB. I confused them with the binaries for iOS, which are quite a bit smaller. I am not sure why. Android is definitely an outlier in terms of binaries sizes compared to other platforms.
When building an Android app for the arm architecture only, an empty Flutter app is ~5 MB, and when cbl is added it is ~21 MB.
To better understand what is going on, you could run flutter build apk --target-platform android-arm --analyze-size to analyze the size of the app.

Another update: The 16 MB that are reported when analyzing the app size with the Flutter dev tools are of the compressed binaries. Uncompressed, the binaries are ~50 MB, which means that the Android Gradle Plugin is not stripping debug symbols from native binaries as it should. Someone has already filed a bug for this.
This should not be a blocker though when deploying to the Play Store through app bundles because debug symbols get stripped in the release process.

My apology. You are absolutely right. Since I usually build release bundle and forgot to target arm64 when test build apk it does include all other architectures. With --target-platform android-arm64 flag on, the size is 26.2MB (a 10% increase from from 23MB) which I think is much more acceptable (libcblite.so is 14.6MB and libcblitedart.so is 730KB).


iPhone X 11.3.1 can't jailbreak

Im using the latest beta version of unc0ver and when the iPhone gets to the 37/38 then it freezes on a loop and come to normal (no jailbreak)

Im using the version that was just released and its not really jailbreaking. Says jailbroken, but I never went into a post JB success respring. And Cydia keeps crashing


Allow the batching renderer to be used with new enough Sodium versions

Modern versions of Sodium (0.5.4+) correctly fall back to using VertexConsumer even if it doesn't implement the VertexBufferWriter interface. Therefore, hard-disabling the batcher should no longer be required. This PR adjusts the detection logic to detect the specific version(s) of Sodium that would have this problem and only disables the batcher for those specific versions.
I've tested that the batcher does work fine with Sodium 0.5.8 on MC 1.20.4, unfortunately there is no Sodium 0.4 version to test with on this Minecraft version.

Could you merge this commit onto an older version branch to verify this behaves correctly? There should be no merge conflicts.

Sure. Checked on 1.20.1, it correctly disables the batching renderer when running alongside Sodium 0.4.10.