Adding app deploy command

Pre-review checklist

[ ] I've confirmed that instructions included in README.md are still correct after my changes in the codebase.
[ ] I've added or updated automated unit tests to verify correctness of my new code.
[ ] I've added or updated integration tests to verify correctness of my new code.
[x] I've confirmed that my changes are working by executing CLI's commands manually.
[ ] I've confirmed that my changes are up-to-date with the target branch.
[ ] I've described my changes in the release notes.
[x] I've described my changes in the section below.

Changes description
Adding the snow app deoply command, which syncs the local changes to the stage without creating/updating the application (More details in SNOW-1215781).
Since the deploy command is basically the same as the run command without the last step of creating/updating the application, the most minimal change would be to add a flag to skip this step in the existing NativeAppRunProcessor class.
An alternative approach would be to add a dedicated DeployProcessor and refactor the common code up to the base class.
The next step will be to extend the command to accept optional file paths arguments to sync only specific files: snow app deploy [file]*.
Test
Created a basic app:
snow app run -c QA3 --warehouse TEST1

Running deploy with no changes:
snow app deploy -c QA3

There are no new files that exist only in your local directory.
There are no new files that exist only on the stage.
There are no existing files that have been modified, or their status is unknown.
Existing files identical to the stage:
README.md
manifest.yml
setup_script.sql

Making a change to the readme and running deploy again:
snow app deploy -c QA3

Existing files modified or status unknown:
README.md
Existing files identical to the stage:
manifest.yml
setup_script.sql
Uploading diff-ed files from your local /Users/gbloom/gbloom-training-app/output/deploy directory to the Snowflake stage.

Closing this in favor of #921


Fix bytes marshalling issue in js sdk

Checklist

[x] Tested in playground or other setup

Summary by CodeRabbit

Refactor

Improved the retryAfter method for enhanced readability and efficiency.
Updated internal logic for better data handling and comparison within methods.

New Features

Added functionality to convert buffer data to base64 JSON format.
Implemented a new method for converting protobuf timestamps to JSON.

Documentation

Confirmed no changes to public API declarations.

This is merged with @kwapik PR


Add Delete Video and Get Channel Editors features

Reorder api entrypoint as Twitch documentation
Part of #74 issue

Pull Request Test Coverage Report for Build 761720738

15 of 19 (78.95%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.2%) to 86.961%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

channels_editors.go
8
10
80.0%

videos.go
7
9
77.78%

Totals

Change from base Build 761606497:
-0.2%

Covered Lines:
767

Relevant Lines:
882

💛  - Coveralls


Edit Order feature, and Comma delimiter for multiple orders

This PR includes the edit order feature as well as the new comma delimiter for adding multiple dishes.
Note that editing order refers to the editing of the customer and the dishes, which are the ones that would require editing. Other things like order number, time, or automatically assigned driver do not require editing under normal circumstances.

Codecov Report

Merging #104 (695fb30) into master (0bc8eef) will decrease coverage by 1.85%.
The diff coverage is 0.87%.

@@             Coverage Diff              @@
##             master     #104      +/-   ##
============================================
- Coverage     41.33%   39.48%   -1.86%
  Complexity      413      413
============================================
  Files           129      133       +4
  Lines          2269     2378     +109
  Branches        271      295      +24
============================================
+ Hits            938      939       +1
- Misses         1282     1389     +107
- Partials         49       50       +1

Impacted Files
Coverage Δ

...rc/main/java/seedu/address/logic/LogicManager.java
45.45% <0.00%> (-6.27%)
:arrow_down:

.../seedu/address/logic/commands/AddOrderCommand.java
0.00% <0.00%> (ø)

...seedu/address/logic/commands/EditOrderCommand.java
0.00% <0.00%> (ø)

...du/address/logic/parser/AddOrderCommandParser.java
0.00% <0.00%> (ø)

.../seedu/address/logic/parser/AddressBookParser.java
59.25% <0.00%> (-2.28%)
:arrow_down:

...u/address/logic/parser/EditOrderCommandParser.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/model/AddressBook.java
63.07% <0.00%> (-3.06%)
:arrow_down:

...rc/main/java/seedu/address/model/ModelManager.java
55.55% <0.00%> (-1.92%)
:arrow_down:

src/main/java/seedu/address/model/order/Order.java
0.00% <0.00%> (ø)

...ava/seedu/address/model/order/UniqueOrderList.java
19.14% <0.00%> (-3.93%)
:arrow_down:

... and 3 more

Continue to review full report at Codecov.

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


Package version is 1.x, even though API is not stable

In #60, the version was bumped to 1.0.0. This was a mistake, as our API is still unstable. At the very least, we depend on an unstable sdl2 crate, so every time we update our sdl2 dependency, it's a breaking change.
This means that we would have to increment the major version (i.e. 2.0.0, 3.0.0, ...) after every sdl2 upgrade.
I'm not sure if this can be fixed (either by yanking, or by special request, deleting for good our 1.x versions from crates.io), or if we are stuck having to upgrade the major version every time we make a breaking change.

crates.io supports yank. cargo yank
sdl2_mixer, sdl2_ttf use same version string as sdl2.
@xsleonard

@andelf are you able to admin the package on crates.io?

@xsleonard yes.
yanking 1.x will break following repos.  :(
serarch result

I'll yank v1.1.0 and v1.0.0.

@andelf Is it actually possible to start releasing lower versions than the ones we already published, even if we yank them? I'm concerned.

@crumblingstatue

I've published v0.16.0.
but our crates.io homepage shows:

This crate has been yanked, but it is still available for download for other crates that may be depending on it.

It only displays newest version of the create. :(

refer: https://github.com/rust-lang/crates.io/issues/76

:joy: Should we publish a new v1.1.1? Currently our crates.io page is completely gone.

Should we publish a new v1.1.1?

That would only make the situation even more confusing. We caused enough mess as it is already.

Closing, since this crate is deprecated.


CI: Fix docs build failure in CircleCI job

What does this PR do?
~Tries to resolve the current docs build failure in CircleCI job In parallel with #13422.~
Fixes the current unavailability of CircleCI job building docs by replacing readthedocs/build:latest (hub.docker.com, Dockerfile) with a simple Python docker image.
Closes #13422.
Does your PR introduce any breaking changes? If yes, please list them.
None
Before submitting

[x] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[n/a] Did you make sure to update the documentation with your changes? (if necessary)
[n/a] Did you write any new necessary tests? (not for typos and docs)
[n/a] Did you verify new and existing tests pass locally with your changes?
[n/a] Did you list all the breaking changes introduced by this pull request?
[n/a] Did you update the CHANGELOG? (not for typos, docs, test updates, or minor internal changes/refactors)

PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[ ] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃
cc @carmocca @akihironitta @borda

I would prefer to keep using official readthedocs image to flag some potential issues

Sounds reasonable!

having the same as gha does not have much sense...

I wonder why there's basically the same CI job among our GH workflows as this CircleCI job. Do you mean .github/workflows/docs-checks.yml can be completely removed (which I think can be)?

I wonder why there's basically the same CI job among our GH workflows as this CircleCI job.

CircleCI offer inspecting artifacts online which means you can browse built docs inline without downloading them and opening them locally... :rabbit:

CircleCI offer inspecting artifacts online which means you can browse built docs inline without downloading them and opening them locally... 🐰

I know, and we should definitely keep the CircleCI job for easy reference to built docs, but I'm asking if we can remove the GH workflow .github/workflows/docs-checks.yml. What do you think?

we need to keep the GHA jobs as we need to build two independent docs instances which won't be possible to parameterize with pure readthedocs, ref #13537

@Borda Sorry I'm not following the CI/CD on app side. I'm still not sure of the need even after I had a look at the PR (maybe because I know nothing about CI/CD in the app repo, e.g., how the app documentation is hosted).
However, I'm now reverting the change to the GHA as you suggest!

So far, I fixed the failure of building docs in CircleCI at the time of 6fae278. Then, given the review comment https://github.com/Lightning-AI/lightning/pull/13547#discussion_r915523547, I removed the CircleCI job and suggested its alternative #13572.
Does #13572 look like a good alternative? If yes, this PR is blocked by #13572. Otherwise, I'm not sure what to do from here. Do we want to keep running the CircleCI job or looking for other alternatives? It would be great if anyone could take over this PR (or create another PR) to fix the current CircleCI failure in building docs.


Limit on Orders API not owrking

Issue summary
I am trying to set a limit on the orders api call and I am unable to make it anything other than 50
Expected behavior
Specifying query : { limit: 10} should make only 10 orders show up
Actual behavior
Up to 50 orders show up
I make this call
restClient.get({
      tries: 100,
      limit: 10,
      query: { limit: 10 },
      path: `orders.json?status=open`,
      type: DataType.JSON,
    });

And I get this response

I20211215-12:57:46.152(-8)?   body: {
I20211215-12:57:46.152(-8)?     orders: [
I20211215-12:57:46.152(-8)?       [Object], [Object], [Object], [Object],
I20211215-12:57:46.152(-8)?       [Object], [Object], [Object], [Object],
I20211215-12:57:46.153(-8)?       [Object], [Object], [Object], [Object],
I20211215-12:57:46.153(-8)?       [Object], [Object], [Object], [Object],
I20211215-12:57:46.153(-8)?       [Object], [Object], [Object], [Object],
I20211215-12:57:46.153(-8)?       [Object], [Object], [Object], [Object],
I20211215-12:57:46.153(-8)?       [Object], [Object], [Object], [Object],
I20211215-12:57:46.153(-8)?       [Object], [Object], [Object], [Object],
I20211215-12:57:46.153(-8)?       [Object], [Object], [Object], [Object],
I20211215-12:57:46.154(-8)?       [Object], [Object], [Object], [Object],
I20211215-12:57:46.154(-8)?       [Object], [Object], [Object], [Object],
I20211215-12:57:46.154(-8)?       [Object], [Object], [Object]
I20211215-12:57:46.154(-8)?     ]
I20211215-12:57:46.155(-8)?   },
I20211215-12:57:46.155(-8)?   headers: Headers {
I20211215-12:57:46.155(-8)?     [Symbol(map)]: [Object: null prototype] {
I20211215-12:57:46.155(-8)?       date: [Array],
I20211215-12:57:46.155(-8)?       'content-type': [Array],
I20211215-12:57:46.155(-8)?       'transfer-encoding': [Array],
I20211215-12:57:46.155(-8)?       connection: [Array],
I20211215-12:57:46.155(-8)?       'x-sorting-hat-podid': [Array],
I20211215-12:57:46.155(-8)?       'x-sorting-hat-shopid': [Array],
I20211215-12:57:46.155(-8)?       vary: [Array],
I20211215-12:57:46.155(-8)?       'referrer-policy': [Array],
I20211215-12:57:46.156(-8)?       'x-frame-options': [Array],
I20211215-12:57:46.156(-8)?       'x-shopid': [Array],
I20211215-12:57:46.156(-8)?       'x-shardid': [Array],
I20211215-12:57:46.156(-8)?       'x-stats-userid': [Array],
I20211215-12:57:46.156(-8)?       'x-stats-apiclientid': [Array],
I20211215-12:57:46.156(-8)?       'x-stats-apipermissionid': [Array],
I20211215-12:57:46.156(-8)?       http_x_shopify_shop_api_call_limit: [Array],
I20211215-12:57:46.156(-8)?       'x-shopify-shop-api-call-limit': [Array],
I20211215-12:57:46.156(-8)?       'x-shopify-api-version': [Array],
I20211215-12:57:46.156(-8)?       'strict-transport-security': [Array],
I20211215-12:57:46.156(-8)?       'x-shopify-stage': [Array],
I20211215-12:57:46.157(-8)?       'content-security-policy': [Array],
I20211215-12:57:46.157(-8)?       'x-content-type-options': [Array],
I20211215-12:57:46.157(-8)?       'x-download-options': [Array],
I20211215-12:57:46.157(-8)?       'x-permitted-cross-domain-policies': [Array],
I20211215-12:57:46.157(-8)?       'x-xss-protection': [Array],
I20211215-12:57:46.157(-8)?       'x-dc': [Array],
I20211215-12:57:46.157(-8)?       'content-encoding': [Array],
I20211215-12:57:46.157(-8)?       'x-request-id': [Array],
I20211215-12:57:46.157(-8)?       'cf-cache-status': [Array],
I20211215-12:57:46.157(-8)?       'expect-ct': [Array],
I20211215-12:57:46.157(-8)?       server: [Array],
I20211215-12:57:46.158(-8)?       'cf-ray': [Array],
I20211215-12:57:46.158(-8)?       'alt-svc': [Array]
I20211215-12:57:46.158(-8)?     }
I20211215-12:57:46.158(-8)?   },
I20211215-12:57:46.158(-8)?   pageInfo: { limit: '10' }
I20211215-12:57:46.158(-8)? }

I was originally trying to extend the limit to 250 and realized it wasn't working. And I can't change the limit at all

[x ] I have described this issue in a way that is actionable (if possible)

It looks like you might be mixing your query usage. Can you give this a try:
restClient.get({
      tries: 100,
      query: { limit: 10, status: "open" },
      path: `orders`,
      type: DataType.JSON,
    });

Ah I had tried that but left
path: 'orders.json'
Which was showing a not found.
So it does work, but the documentation around this is very lacking and 'orders.json' not working does seem like an issue.

Glad it's working for you now @ToyboxZach! Since this appears to be a user error and possible documentation issue, rather than a bug with the library, I'm going to go ahead and close this for now. However, if you think you've come across a bug in the library or an issue with the code, please feel free to open a new issue. And I'll see about improving the usage example for the REST client to be more explicit about leaving of the .json part of the requested resource. Thanks folks!


Ensure non-zero exit on compile fail

This fixes an issue where tests with import errors were passing because
the number of failed tests was equal to 0 (because no tests ran).
@uber/ringpop

oops! lgtm


Add more tools

Google Chrome (GoogleChrome)
Notepad++ (NotepadPlusPlus)
Mimikatz (Pull from GH)
WinRAR (winrar)

These have been added since the 1.0 release


[image_picker] crash when start

I have a trouble when I am using image_picker 0.6.3, my app always crash when developing but can run when debug.
This is crash log
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.trj.rdctracker/com.trj.rdctracker.MainActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'void androidx.lifecycle.f.a(androidx.lifecycle.g)' on a null object reference
	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2977)
	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3114)
	at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:78)
	at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:113)
	at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:71)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1859)
	at android.os.Handler.dispatchMessage(Handler.java:106)
	at android.os.Looper.loop(Looper.java:201)
	at android.app.ActivityThread.main(ActivityThread.java:6831)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:547)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:927)
Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'void androidx.lifecycle.f.a(androidx.lifecycle.g)' on a null object reference
	at io.flutter.plugins.imagepicker.ImagePickerPlugin.a(Unknown Source:69)
	at io.flutter.plugins.imagepicker.ImagePickerPlugin.a(Unknown Source:27)
	at io.flutter.embedding.engine.c.a(Unknown Source:106)
	at c.a.b.a.e.a(Unknown Source:57)
	at c.a.b.a.d.onCreate(Unknown Source:22)
	at android.app.Activity.performCreate(Activity.java:7224)
	at android.app.Activity.performCreate(Activity.java:7213)
	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1271)
	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2957)
	... 11 more

Minsdkversion 16
Targetsdkversion 28
Deviceos android pie

Does this reproduce for you in the image_picker example app?  If not, can you provide a minimum reproduction so that this can be debugged/triaged?

Confirmed. Works when devving, but when doing flutter build apk and running that, I get the same errors.

I fixed this by disabling tree shaking with minifyEnabled and shrinkCode. It is simply bad and unreliable.
If anyone ever faces issues that pop up only during release build, try that.

Does this reproduce for you in the image_picker example app? If not, can you provide a minimum reproduction so that this can be debugged/triaged?

no, when I tried on example app it's work.
this is my code
  Future getImageCamera() async {
    var img = await ImagePicker.pickImage(
        source: ImageSource.camera, imageQuality: 60);
    setState(() {
      image = img;
    });
  }

  Future getImageGalery() async {
    var img = await ImagePicker.pickImage(
        source: ImageSource.gallery, imageQuality: 60);
    setState(() {
      image = img;
    });
  }

But when I remove that code and just import package image_picker my app still crash.

I fixed this by disabling tree shaking with minifyEnabled and shrinkCode. It is simply bad and unreliable.
If anyone ever faces issues that pop up only during release build, try that.

thankyou it got fixed.

I fixed this by disabling tree shaking with minifyEnabled and shrinkCode. It is simply bad and unreliable.
If anyone ever faces issues that pop up only during release build, try that.

it's fixed my problem. thank you very much

I fixed this by disabling tree shaking with minifyEnabled and shrinkCode. It is simply bad and unreliable.
If anyone ever faces issues that pop up only during release build, try that.

Can you give more details on how to do this?

I believe you can just pass --no-shrink to the Flutter tool to disable shrinking.
We shouldn't require you to disable shrinking for this plugin.
/cc @blasten - did we miss this one when evaluating proguard/r8 rules?

You can indeed, but when reverting to an old version that did work, other
plugins behaved inconsistently, compared to their debug release
counterparts. That's when I decided I was done with the tree shaking
altogether. However, I'd recommend passing the flags he just mentioned to
test if that fixes your problem.
On Mon, Jan 13, 2020, 18:45 Dan Field<EMAIL_ADDRESS>wrote:

I believe you can just pass --no-shrink to the Flutter tool to disable
shrinking.
We shouldn't require you to disable shrinking for this plugin.
/cc @blasten https://github.com/blasten - did we miss this one when
evaluating proguard/r8 rules?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/48622?email_source=notifications&email_token=AJIOJVLAYSQMTEYINKDX223Q5SSCDA5CNFSM4KFQJZUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIZUEDA#issuecomment-573784588,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJIOJVJQJA5ZKR4OTEEP4SDQ5SSCDANCNFSM4KFQJZUA
.

The issue is in the android_lifecycle plugin since it uses reflection:  https://github.com/flutter/plugins/blob/master/packages/flutter_plugin_android_lifecycle/android/src/main/java/io/flutter/embedding/engine/plugins/lifecycle/FlutterLifecycleAdapter.java#L29-L30
cc @amirh

Discussed with @amirh offline, the reflection was originally added in order to support 1.9 when it was stable. Now that a more recent version has rolled we should be able to avoid it entirely. I'll look into taking it out of flutter_plugin_android_lifecycle.

Version 1.0.4 of flutter_plugin_android_lifecycle has been published with the fix for this. This should be enough to resolve it for everyone on the latest Flutter stable, but people on older versions of Flutter will need to upgrade to the latest stable (v1.12) to get the fixed package version.
If you're still seeing this issue, please comment with minimal reproduction steps, your flutter version, and your pubspec.lock.

Version 1.0.4 of flutter_plugin_android_lifecycle has been published with the fix for this. This should be enough to resolve it for everyone on the latest Flutter stable, but people on older versions of Flutter will need to upgrade to the latest stable (v1.12) to get the fixed package version.
If you're still seeing this issue, please comment with minimal reproduction steps, your flutter version, and your pubspec.lock.

how to upgrade "flutter_plugin_android_lifecycle "  ?
thank you

Version 1.0.4 of flutter_plugin_android_lifecycle has been published with the fix for this. This should be enough to resolve it for everyone on the latest Flutter stable, but people on older versions of Flutter will need to upgrade to the latest stable (v1.12) to get the fixed package version.
If you're still seeing this issue, please comment with minimal reproduction steps, your flutter version, and your pubspec.lock.

Thant you!
I add "  flutter_plugin_android_lifecycle: ^1.0.4"  to pubspec.yaml
it's fixed my problem

Version 1.0.4 of flutter_plugin_android_lifecycle has been published with the fix for this. This should be enough to resolve it for everyone on the latest Flutter stable, but people on older versions of Flutter will need to upgrade to the latest stable (v1.12) to get the fixed package version.
If you're still seeing this issue, please comment with minimal reproduction steps, your flutter version, and your pubspec.lock.

Very nice! We will attempt a build with tree shaking enabled soon, including your fix, on the latest stable at least. Will check with dev and beta channels as well.

Hi, I ran into the same problem. I changed the Versions in my pubspec, but my App crashes again.
flutter_plugin_android_lifecycle: ^1.0.11
image_picker: ^0.6.7+12

10-22 12:14:24.269 22726-22726/? E/AndroidRuntime: FATAL EXCEPTION: main
java.lang.RuntimeException: Unable to destroy activity {de.facentis.pflanzmemo/io.flutter.embedding.android.FlutterActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'void androidx.lifecycle.d.c(androidx.lifecycle.f)' on a null object reference
at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:4337)
at android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:4355)
at android.app.ActivityThread.access$1500(ActivityThread.java:181)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1536)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:145)
at android.app.ActivityThread.main(ActivityThread.java:6145)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1399)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1194)
Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'void androidx.lifecycle.d.c(androidx.lifecycle.f)' on a null object reference
at io.flutter.plugins.imagepicker.ImagePickerPlugin.j()
at io.flutter.plugins.imagepicker.ImagePickerPlugin.f()
at io.flutter.embedding.engine.c.f()
at io.flutter.embedding.android.e.o()
at io.flutter.embedding.android.FlutterActivity.F()
at io.flutter.embedding.android.FlutterActivity.onDestroy()
at android.app.Activity.performDestroy(Activity.java:6608)
at android.app.Instrumentation.callActivityOnDestroy(Instrumentation.java:1154)
at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:4315)
at android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:4355)
at android.app.ActivityThread.access$1500(ActivityThread.java:181)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1536)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:145)
at android.app.ActivityThread.main(ActivityThread.java:6145)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1399)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1194)

Did I miss something else?

Привет, я столкнулся с той же проблемой. Я изменил версии в своем pubspec, но мое приложение снова вылетает.
flutter_plugin_android_lifecycle: ^ 1.0.11
image_picker: ^ 0.6.7 + 12

10-22 12: 14: 24.269 22726-22726 /? E / AndroidRuntime: FATAL EXCEPTION: main
java.lang.RuntimeException: невозможно уничтожить действие {de.facentis.pflanzmemo / io.flutter.embedding.android.FlutterActivity}: java.lang.NullPointerException: попытка вызвать виртуальный метод void androidx .lifecycle.dc (androidx.lifecycle.f) 'для ссылки
на нулевой объект в android.app.ActivityThread.performDestroyActivity (ActivityThread.java:4337)
в android.app.ActivityThread.handleDestroyActivity (ActivityThread.java:4355)
в android. app.ActivityThread.access $ 1500 (ActivityThread.java:181)
в android.app.ActivityThread $ H.handleMessage (ActivityThread.java:1536)
в android.os.Handler.dispatchMessage (Handler.java:102)
на android.os. Looper.loop (Looper.java:145)
в android.app.ActivityThread.main (ActivityThread.java:6145)
в java.lang.reflect.Method.invoke (собственный метод)
в java.lang.reflect.Method.invoke (Method.java:372)
в com.android .internal.os.ZygoteInit $ MethodAndArgsCaller.run (ZygoteInit.java:1399)
в com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1194)
Вызвано: java.lang.NullPointerException: попытка вызвать виртуальный метод 'void androidx.lifecycle.dc (androidx.lifecycle.f)' в ссылке
на нулевой объект в io.flutter.plugins.imagepicker.ImagePickerPlugin.j ()
в io.flutter.plugins.imagepicker.ImagePickerPlugin.f ()
в io .flutter.embedding.engine.cf ()
в io.flutter.embedding.android.eo ()
в io.flutter.embedding.android.FlutterActivity.F ()
в io.flutter.embedding.android.FlutterActivity.onDestroy ()
в android.app.Activity.performDestroy (Activity.java:6608)
в android.app.Instrumentation.callActivityOnDestroy (Instrumentation.java:1154)
в android.app.ActivityThread .performDestroyActivity (ActivityThread.java:4315)
в android.app.ActivityThread.handleDestroyActivity (ActivityThread.java:4355)
в android.app.ActivityThread.access $ 1500 (ActivityThread.java:181)
в android.app.ActivityThread $ H.handleMessage (ActivityThread.java:1536)
в android.os.Handler.dispatchMessage (Handler.java:102)
в android.os.Looper.loop (Looper.java:145)
в android.app.ActivityThread.main (ActivityThread.java: 6145)
в java.lang.reflect.Method.invoke (собственный метод)
в java.lang.reflect.Method.invoke (Method.java:372)
в com.android.internal.os.ZygoteInit $ MethodAndArgsCaller.run (ZygoteInit.java:1399)
в com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1194)

Я что-то еще пропустил?
Изменить: возможно, исправлено с помощью Gradle Downgrade: 3.6.3

flutter_plugin_android_lifecycle: ^1.0.11
image_picker: ^0.6.7+12
flutter build apk --no-shrink
it's fixed my problem.

Hi @TahaTesser
as per #48622 (comment) , tree shaking and minifyEnabled are not set in my gradle configuration. Does not seem to be relevant to my problem

For what it's worth, moving to flutter_plugin_android_lifecycle: ^1.0.4 also fixed an exception for me for file_picker.

For what it's worth, moving to flutter_plugin_android_lifecycle: ^1.0.4 also fixed an exception for me for file_picker.


Various stylus issues

So, I've migrated from Excalidraw to this awesome plugin a few days ago, and it solved most of my problems (mostly lag). Sadly, after a day or two of using it for actual note taking (used it in class), I realized there's a massive bug that makes the experience awful and nearly unusable.
I'm using a Samsung tablet that came with a stylus, and it works very well, it's fast and smooth, barely no input lag, etc... The thing is, for whatever reason, the pen keeps going to default. First pen type and medium size. Write a word? Half of it disappears. Write a sentence? You can't because the pen gets too big.
I've noticed that whenever this happens the pen mode gets disabled, or rather, the pen mode gets disabled and then this happens, which is weird since neither in Excalidraw or the official Tldraw website show this problem. I'm not too sure why, but the plugin seems to revert back certain actions? I'm not sure is this is an error on my side.
Heres a video for context:
https://github.com/user-attachments/assets/0d0dec49-62eb-4334-8152-6944a47d9afb

If this helps: I've realized that it usually happens after going to markdown mode and then switching back to the normal view. I can't confirm if this is what causes this specific problem, since I believe it has also happened before. I'll test it more tomorrow tho

I am able to reproduce this using a generic drawing tablet on the desktop version of Obsidian. I'll have to investigate this further, but switching to markdown mode does seem to trigger this bug. Although like you said, it may not be the root issue but it may exacerbate it to the point of allowing it to be detected at least. I'll have to do some debugging on my side to see what is exactly the root cause.

Well, after using Tldraw for taking notes on all my lectures for today, I can confirm I've had no issues by just not switching to markdown mode!
Still, another thing that seems to trigger this as well is changing the file name while the file is open (also, not sure if it's related or not, but changing the name isn't reflected until the tab is closed or markdown mode is switched on and off).

@Takaishisama Good news, I figured out the root cause and I am working on a solution to it. When that is done I'll create a preview release so that you could test. Then, I'll try to fix the file renaming bug. Thanks for your help in narrowing down the cause of the bug!

Release created here: https://github.com/jon-dez/tldraw-in-obsidian/releases/tag/1.12.1
You can install it using the BRAT community plugin, but you have to use my repository's URL https://github.com/jon-dez/tldraw-in-obsidian


Update append-transform

See https://github.com/TypeStrong/ts-node/issues/183#issuecomment-241302682. I recently updated ts-node to follow the same require extension transform pattern as pirates and the hook I had added originally to instabul. The problem now is that falling back to the "next loader", which in this case is istanbul, results in the old version of append-transform that threw errors instead of loading via .js.

I hope the PR is getting merged soon, though it didn't seem to have caught any attention! :-(

@cvle @blakeembrey sorry for dropping this on the floor for such a long time.
I've released a new version of istanbul-lib-hook; it is now available in the latest version of istanbul-api, and is available in the next release of nyc:
npm i nyc@next


Fixing editable / draggable value at circles

Google Maps API doesn't process the passed value of editable / draggable. Filtering the Google Maps events triggered on the circle, if it should be able to get edited or dragged.
The handling of the Google Maps API should be investigated.
Fixes #1110.

@SebastianM do you think this is the right approach to fix this issue?


Edit default value

It'd be really handy if there were an option to allow the default value to be edited. At the moment it gets deleted if you try.
Use case is e.g. asking for something like a hostname where you may want to make a minor adjustment rather than accept the default.

@v8oss can you give a try https://github.com/manifoldco/promptui/pull/45

This line in Prompt.go blanks out default values for confirm prompt types.
https://github.com/manifoldco/promptui/blob/master/prompt.go#L257
if p.IsConfirm {
	p.Default = ""                                                    // This line
	if tpls.Confirm == "" {
		confirm := "y/N"
		if strings.ToLower(p.Default) == "y" {    // Causes this logic to fail
			confirm = "Y/n"
		}

As well as the logic to accept Y as a default . I haven't had time to research where the fix for this would be and it's not a high priority for me right now.
By removing p.Default = "", functionality does work except the Default is displayed on the input, similar to normal prompts, which didn't seem desired since the default functionality with N as default doesn't show "N" on the input.


plex-rich-presence DOCKER builds for Synology (and more?)

I would love to see this as a docker app
i'm on Synology DSM224+ (DSM7.2) (Linux)
we use the Package Manager and Container Manager (Docker-compose2 basically)
any plans to make a release for this ? would love to uncouple this plug-in from my PC if possible.

Duplicate of #56


Freebsd pip install ImportError: cannot import name 'setuptools' from 'setuptools'

I have had a install of chia on freebsd since initial release. Usually things work just fine but it seems in some recent update that during the ./install.sh things get hung up on chiavdf and it fails to build for some reason. I tried to just do a normal pip install inside my venv running python3.9 and got the same error message, logs attached below.
chiavdf-install.log
Freebsd 13.1 and I tried freebsd 13.2 both have the same issues.

hmm maybe this is my problem: https://github.com/Chia-Network/chiavdf/pull/149

I updated my setup.py in chia to use your recent release 1.0.11 and the install got further but there seem to be issues with some other chia dependencies with the same issue. I guess I'll close this since it's been fixed here already just not some other places.


Update all docs links to 0.6, release 0.6

[ ] Improves consistency of our crate.io readmes
[x] Improves consistency of our crate.io tags
[ ] Improves the top-level readme.md (better gifs, highlighting mobile support)

https://github.com/user-attachments/assets/05f8b0a5-e03e-4b3c-aa66-98f51b6ec917
https://github.com/user-attachments/assets/6da371d5-3340-46da-84ff-628216851ba6

mostly happy with this PR, leaving it alive until 0.6 is released and then we can merge this


I got pinged in a random discussion post... don't know why, but kinda want it removed ngl

the comment contains "nsfw" (not gonna click the link as its prob a scam), but there were others also pinged so I was hopping it could get removed and/or reported...
Link: https://github.com/kercre123/wire-pod/discussions/24#discussioncomment-4519164

also looking at the top languages in this repo, I have no experience in the top 2, but have some Shell experience and I know a lot of HTML, CSS, and Javascript so if you need any help with that, lmk

A couple of those comments were made, they have been reported and the associated posts have been deleted. Sorry about the ping.

Its all cool man. Like i said, I can also help with any HTML, JavaScript, or CSS code if it isn't working as I'm good at those languages


about import css file

in your
https://github.com/almasaeed2010/AdminLTE/blob/master/build/less/AdminLTE.less

@import url(https://fonts.googleapis.com/css?family=Source+Sans+Pro:300,400,600,700,300italic,400italic,600italic);

however, when used in local network, it can not reach that site.
A friend has collected the zip file in http://files.cnblogs.com/files/tekikesyo/LocalGoogleFont.zip
code like, OK?
@import url('local.google.fonts.css');

ref: http://www.cnblogs.com/tekikesyo/p/4636412.html

#744
#498

thank you very much. I see.


Add Contributing workloads page

Closes #6288
Checklist

[x] By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@IanHoang: This is ready for your review.

@IanHoang: Mind taking one more look?


Constant ContextsToViewTransformer::SEPARATOR not defined on stable versions

There is an issue using the CalendarBundle with the platform 2.6:
request.CRITICAL: Uncaught PHP Exception Symfony\Component\Debug\Exception\FatalThrowableError: "Undefined class constant 'SEPARATOR'" at vendor/oro/calendar-bundle/Form/Type/CalendarEventAttendeesSelectType.php line 129 {"exception":"[object] (Symfony\\Component\\Debug\\Exception\\FatalThrowableError(code: 0): Undefined class constant 'SEPARATOR' at vendor/oro/calendar-bundle/Form/Type/CalendarEventAttendeesSelectType.php:129)"} []

In stable versions the class does not provide the constant:
version 2.6.0
version 2.6.1
In the dev branch, there is the constant:
version 2.6.x-dev

@mbessolov  You can specify incompatible versions among bundles using  composer conflict(s)
https://getcomposer.org/doc/04-schema.md#conflict
That would prevent composer from installing incompatible versions.
Have a good day,
Samuel

Hi @sadortun ,
Conflicts is very similar to what we are looking for, but we don't have possibility always test package with all previously released versions of all dependencies. So we found more easy solution.
Instead we decided to make all packages to require minimum patch version they was tested with on our CI, so we make sure them are always compatible.
Like requiring "oro/platform": "~2.6.1" from the "oro/calendar" package will make impossible to install new version of calendar package with 2.6.0 version of the platform.
Thank you for suggestion!


Add podUID as a template input in tasklog plugin

TL;DR
Add podUID as an additional template input variable so that Log URLs can refer to the UIDs.
Type

[ ] Bug Fix
[x] Feature
[ ] Plugin

Are all requirements met?

[x] Code completed
[x] Smoke tested
[x] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
A pod UID is unique across the cluster and logging systems can use them to refer to logs.
Tracking Issue
Remove the 'fixes' keyword if there will be multiple PRs to fix the linked issue
fixes https://github.com/flyteorg/flyte/issues/
Follow-up issue
NA
TODO: update documentation if the changes looks ok

@goyalankit thanks for this! Mind submitting a small PR to update the docs as well? Should be this page that is located here.


misrac: Checking the returned value of a non-void function

MISRA-C rule 17.7 says that the return value of a non-void must be
checked. For memcpy/memset there is no error handling or checking we
can do with the return value, so it is just casting it to void to
explicitly ignore while adhering to MISRA-C.
This patch was generated using the coccinelle script
ignore_return.cocci
Signed-off-by: Flavio Ceolin<EMAIL_ADDRESS>

Seems like some of the new indentation is "off" as it doesn't line up with the parenthesis above, etc.  Is that just me?

For anybody who cares: ￼ this:

pabigot removed request for pabigot, MaureenHelm, cvinayak, trond-snekvik, rveerama1, mike-scott, Mani-Sadhasivam, alexanderwachter, jfischer-phytec-iot, sjanc, carlescufi, galak, nordic-krch, nvlsianpu, loicpoulain, erwango, sathishkuttan, rlubos, aescolar, jakub-uC, thoh-ot and dcpleung now

was due to me removing myself and github refusing to allow me to leave more than 15 reviewers registered.  It was not intentional, but I can't restore them either.
I've seen a few of these recently, maybe a github change.

I believe we already went thru this before, and various people made it clear that they don't want to stuff finicky things in front of every memcpy/memset.

I believe we already went thru this before, and various people made it clear that they don't want to stuff finicky things in front of every memcpy/memset.

Now it can be different. Zephyr's moving towards to use a codeguideline based on MISRA-C. This is a required rule, while this is a silly fix because these functions are poor defined and there is nothing we can do, there are  other functions that return values that we should be checking. I intend to force it with GCC, but first we need to fix these problems. I just started with biggest/simplest one.

17.7 is a required rule, which allows deviations.  A reasonable deviation is that when the return value is a constant that cannot affect control flow, as it is with mem*, there is no need to explicitly indicate that it is being ignored.

17.7 is a required rule, which allows deviations. A reasonable deviation is that when the return value is a constant that cannot affect control flow, as it is with mem*, there is no need to explicitly indicate that it is being ignored.

I know that, I'm imagining if we start create deviation for this simple case we'll end up with deviations for almost all rules, honestly. People will be much more sensitive to other cases. Is that what we want, deviate from every single rule ?

Regardless of how this rule is applied, I would really appreciate it if Coccinelle fixes were applied in two stages: first a single commit that adds the SmPL script (possibly in scripts/coccinelle/misra or .../codingrules, or...).
Not having access to the scripts that perform the rewrite makes it harder for people to verify they aren't introducing new violations, let alone integrate checks into any sort of QA process.

@ceolin Do you intend to continuing pursing this PR to merge?

Will close this outdated patch and re-open a new one later.


Sequence header might be duplicated.

https://github.com/ossrs/srs/pull/3408#pullrequestreview-1290922439
            vps_sps_pps_change_ = true;
            h265_vps_ = vps;

            if ((err = write_h265_vps_sps_pps(dts, pts)) != srs_success) {

等 #3408 合并我再单独搞这个问题

Given the PR #3408 has been merged, this issue can be considered for further improvement.