Getting 400 response when trying to upload a photo

I log in correctly, i tried some other requests (getting the profile picture of an user) and everything worked perfeclty fine.
But when i try to upload a photo, an IGResponseException is thrown, and the logs show that the request returned a 400 response.
I tried using a File, a byte array, dooing the request 10 seconds after login, simulate the login, but none of them worked.
My code
try {
            IGClient instagram = IGClient.builder()
                    .username("********")
                    .password("********")
                    .onTwoFactor(twoFactorHandler)
                    .onChallenge(challengeHandler)
                    .simulatedLogin();
            System.out.println("Logged into instagram");
            new Timer().schedule(new TimerTask() {
                @SneakyThrows
                @Override
                public void run() {
                    FileInputStream fis = new FileInputStream("yeet.png");
                    instagram.actions()
                            .timeline()
                            .uploadPhoto(fis.readAllBytes(), "caption")
                            .thenAccept(r -> System.out.println("uploaded lol"))
                            .join();
                }
            }, 10000);
        } catch (Exception e) {
            e.printStackTrace();
            System.out.println("NOOOOOOOOOOOOOOOO");
        }

Logs
> Task :Main.main()
[main] INFO com.github.instagram4j.instagram4j.IGClient - Sending request : https://b.i.instagram.com/api/v1/launcher/sync/
[main] INFO com.github.instagram4j.instagram4j.IGClient - Sending request : https://b.i.instagram.com/api/v1/qe/sync/
[main] INFO com.github.instagram4j.instagram4j.IGClient - Sending request : https://b.i.instagram.com/api/v1/accounts/contact_point_prefill/
[main] INFO com.github.instagram4j.instagram4j.IGClient - Sending request : https://b.i.instagram.com/api/v1/accounts/get_prefill_candidates/
[OkHttp https://b.i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://b.i.instagram.com/api/v1/accounts/contact_point_prefill/ : 200
[OkHttp https://b.i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://b.i.instagram.com/api/v1/accounts/contact_point_prefill/ with body (truncated) : {"status": "ok"}
[OkHttp https://b.i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://b.i.instagram.com/api/v1/accounts/get_prefill_candidates/ : 200
[OkHttp https://b.i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://b.i.instagram.com/api/v1/accounts/get_prefill_candidates/ with body (truncated) : {"prefills": [{"usage": "account_recovery_omnibox", "candidates": []}], "status": "ok"}
[OkHttp https://b.i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://b.i.instagram.com/api/v1/launcher/sync/ : 200
[OkHttp https://b.i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://b.i.instagram.com/api/v1/qe/sync/ : 200
[OkHttp https://b.i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://b.i.instagram.com/api/v1/launcher/sync/ with body (truncated) : {"configs": {"ig_android_carrier_signals_killswitch": {"params": {"is_enabled": {"value": true}}}, "
[OkHttp https://b.i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://b.i.instagram.com/api/v1/qe/sync/ with body (truncated) : {"experiments": [{"name": "ig_android_direct_add_direct_to_android_native_photo_share_sheet", "group
[main] INFO com.github.instagram4j.instagram4j.IGClient - Sending request : https://i.instagram.com/api/v1/qe/sync/
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/qe/sync/ : 200
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/qe/sync/ with body (truncated) : {"experiments": [{"name": "ig_android_shopping_checkout_signaling", "group": "rollout", "additional_
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Sending request : https://i.instagram.com/api/v1/accounts/login/
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/accounts/login/ : 200
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/accounts/login/ with body (truncated) : {"logged_in_user": {"pk":<PHONE_NUMBER>, "username": "uku3lig", "full_name": "", "is_private": true, "p
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Logged into uku3lig<PHONE_NUMBER>)
[main] INFO com.github.instagram4j.instagram4j.IGClient - Sending request : https://i.instagram.com/api/v1/launcher/sync/
[main] INFO com.github.instagram4j.instagram4j.IGClient - Sending request : https://i.instagram.com/api/v1/qp/get_cooldowns/?signature=signed_body%3DSIGNATURE.%257B%257D
[main] INFO com.github.instagram4j.instagram4j.IGClient - Sending request : https://i.instagram.com/api/v1/multiple_accounts/get_account_family/
[main] INFO com.github.instagram4j.instagram4j.IGClient - Sending request : https://i.instagram.com/api/v1/linked_accounts/get_linkage_status/
[main] INFO com.github.instagram4j.instagram4j.IGClient - Sending request : https://i.instagram.com/api/v1/loom/fetch_config/
[main] INFO com.github.instagram4j.instagram4j.IGClient - Sending request : https://i.instagram.com/api/v1/media/blocked/
[main] INFO com.github.instagram4j.instagram4j.IGClient - Sending request : https://i.instagram.com/api/v1/feed/timeline/
[main] INFO com.github.instagram4j.instagram4j.IGClient - Sending request : https://i.instagram.com/api/v1/feed/reels_tray/
[main] INFO com.github.instagram4j.instagram4j.IGClient - Sending request : https://i.instagram.com/api/v1/users/arlink_download_info/?version_override=2.2.1
[main] INFO com.github.instagram4j.instagram4j.IGClient - Sending request : https://i.instagram.com/api/v1/discover/topical_explore/?max_id=0&is_prefetch=true&module=explore_popular&use_sectional_payload=true&omit_cover_media=true&session_id=ab83a65d-5903-4e4e-989d-706cea7b1e70
[main] INFO com.github.instagram4j.instagram4j.IGClient - Sending request : https://i.instagram.com/api/v1/news/inbox/?mark_as_seen=false
[main] INFO com.github.instagram4j.instagram4j.IGClient - Sending request : https://i.instagram.com/api/v1/direct_v2/get_presence/
[main] INFO com.github.instagram4j.instagram4j.IGClient - Sending request : https://i.instagram.com/api/v1/direct_v2/inbox/?visual_message_return_type=unseen&limit=0&persistent_badging=true
[main] INFO com.github.instagram4j.instagram4j.IGClient - Sending request : https://i.instagram.com/api/v1/direct_v2/inbox/?visual_message_return_type=unseen&thread_message_limit=10&limit=20&persistent_badging=true&fetch_reason=initial_snapshot
[main] INFO com.github.instagram4j.instagram4j.IGClient - Sending request : https://i.instagram.com/api/v1/status/get_viewable_statuses/
Logged into instagram
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/qp/get_cooldowns/?signature=signed_body%3DSIGNATURE.%257B%257D : 200
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/qp/get_cooldowns/?signature=signed_body%3DSIGNATURE.%257B%257D with body (truncated) : {"ttl": 604800, "global": 0, "default": 1200, "surfaces": [{"surface_id": 4715, "cooldown": 1200}, {
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/multiple_accounts/get_account_family/ : 200
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/multiple_accounts/get_account_family/ with body (truncated) : {"child_accounts": [], "main_accounts": [], "current_account": {"pk":<PHONE_NUMBER>, "username": "uku3l
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/loom/fetch_config/ : 200
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/loom/fetch_config/ with body (truncated) : {"status": "ok"}
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/linked_accounts/get_linkage_status/ : 200
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/linked_accounts/get_linkage_status/ with body (truncated) : {"linkage": {"facebook": {"is_linked": true, "name": "Yet Yet", "fbid": "100046517226574", "error_co
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/media/blocked/ : 200
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/media/blocked/ with body (truncated) : {"media_ids": [], "status": "ok"}
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/users/arlink_download_info/?version_override=2.2.1 : 200
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/users/arlink_download_info/?version_override=2.2.1 with body (truncated) : {"checksum": "c56dbc151cb78f1d6fcea075d6bce5e5c44d8e57b880797ef76f33944d2752a4", "download_url": "ht
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/launcher/sync/ : 200
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/feed/reels_tray/ : 200
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/feed/reels_tray/ with body (truncated) : {"tray": [{"id":<PHONE_NUMBER>, "latest_reel_media":<PHONE_NUMBER>, "expiring_at":<PHONE_NUMBER>, "seen": 160
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/launcher/sync/ with body (truncated) : {"configs": {"ig_android_ad_platform_funnel_logging": {"params": {"is_enabled_stories": {"value": fa
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/direct_v2/inbox/?visual_message_return_type=unseen&limit=0&persistent_badging=true : 200
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/direct_v2/inbox/?visual_message_return_type=unseen&limit=0&persistent_badging=true with body (truncated) : {"pending_requests_total": 0, "has_pending_top_requests": true, "should_hide_message_preview": false
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/news/inbox/?mark_as_seen=false : 200
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/news/inbox/?mark_as_seen=false with body (truncated) : {"aymf": {"items": [{"user": {"pk": "10337732900", "username": "em_bnt", "full_name": "emma", "is_pr
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/direct_v2/get_presence/ : 200
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/direct_v2/get_presence/ with body (truncated) : {"user_presence": {"35158101376": {"is_active": false, "last_activity_at_ms":<PHONE_NUMBER>202}, "40266
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/status/get_viewable_statuses/ : 200
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/status/get_viewable_statuses/ with body (truncated) : {"statuses": {}, "status": "ok"}
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/feed/timeline/ : 200
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/feed/timeline/ with body (truncated) : {"num_results": 7, "more_available": true, "auto_load_more_enabled": true, "feed_items": [{"media_or
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/discover/topical_explore/?max_id=0&is_prefetch=true&module=explore_popular&use_sectional_payload=true&omit_cover_media=true&session_id=ab83a65d-5903-4e4e-989d-706cea7b1e70 : 200
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/discover/topical_explore/?max_id=0&is_prefetch=true&module=explore_popular&use_sectional_payload=true&omit_cover_media=true&session_id=ab83a65d-5903-4e4e-989d-706cea7b1e70 with body (truncated) : {"sectional_items": [{"layout_type": "one_by_two_left", "layout_content": {"one_by_two_item": {"clip
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/direct_v2/inbox/?visual_message_return_type=unseen&thread_message_limit=10&limit=20&persistent_badging=true&fetch_reason=initial_snapshot : 200
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/api/v1/direct_v2/inbox/?visual_message_return_type=unseen&thread_message_limit=10&limit=20&persistent_badging=true&fetch_reason=initial_snapshot with body (truncated) : {"viewer": {"pk":<PHONE_NUMBER>, "username": "uku3lig", "full_name": "", "is_private": true, "profile_p
[Timer-0] INFO com.github.instagram4j.instagram4j.IGClient - Sending request : https://i.instagram.com/rupload_igphoto/1604057130401_0_5413576662
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/rupload_igphoto/1604057130401_0_5413576662 : 400
[OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/rupload_igphoto/1604057130401_0_5413576662 with body (truncated) : {"debug_info":{"retriable":false,"type":"ProcessingFailedError","message":"Request processing failed
Exception in thread "Timer-0" java.util.concurrent.CompletionException: com.github.instagram4j.instagram4j.exceptions.IGResponseException
	at com.github.instagram4j.instagram4j.IGClient$1.handle(IGClient.java:86)
	at com.github.instagram4j.instagram4j.IGClient.lambda$sendRequest$5(IGClient.java:152)
	at java.base/java.util.concurrent.CompletableFuture.uniExceptionally(CompletableFuture.java:986)
	at java.base/java.util.concurrent.CompletableFuture$UniExceptionally.tryFire(CompletableFuture.java:970)
	at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
	at java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2144)
	at com.github.instagram4j.instagram4j.IGClient$2.onResponse(IGClient.java:136)
	at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:504)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:830)
Caused by: com.github.instagram4j.instagram4j.exceptions.IGResponseException
	at com.github.instagram4j.instagram4j.requests.IGRequest.parseResponse(IGRequest.java:72)
Caused by: com.github.instagram4j.instagram4j.exceptions.IGResponseException

	at com.github.instagram4j.instagram4j.IGClient.lambda$sendRequest$4(IGClient.java:149)
	at java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:642)
	... 7 more

same thing here
my code
IGClient client = IGClient.builder()
.username("")
.password("")
.login();
client.actions()
.timeline()
.uploadPhoto(thumbnail, "My Caption #java")
.thenAccept(response -> {
System.out.println("Successfully uploaded photo!");
})
.join();
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
java.util.concurrent.CompletionException: com.github.instagram4j.instagram4j.exceptions.IGResponseException
at com.github.instagram4j.instagram4j.IGClient$1.handle(IGClient.java:86)
at com.github.instagram4j.instagram4j.IGClient.lambda$sendRequest$5(IGClient.java:152)
at java.base/java.util.concurrent.CompletableFuture.uniExceptionally(CompletableFuture.java:986)
at java.base/java.util.concurrent.CompletableFuture$UniExceptionally.tryFire(CompletableFuture.java:970)
at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
at java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2137)
at com.github.instagram4j.instagram4j.IGClient$2.onResponse(IGClient.java:136)
at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:504)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630)
at java.base/java.lang.Thread.run(Thread.java:832)
Caused by: com.github.instagram4j.instagram4j.exceptions.IGResponseException
at com.github.instagram4j.instagram4j.requests.IGRequest.parseResponse(IGRequest.java:72)
at com.github.instagram4j.instagram4j.IGClient.lambda$sendRequest$4(IGClient.java:149)
at java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:642)
Caused by: com.github.instagram4j.instagram4j.exceptions.IGResponseException
... 7 more

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.5/userguide/command_line_interface.html#sec:command_line_warnings

If this issue is reproducible, can you please enable DEBUG level logging and log the full JSON response. As far as I know, it is still working. The truncated response indicated the photo upload has failed. Please make sure the photo is within acceptable dimensions for Instagram.

Having the same issue only when uploading photos (or albums), everything else works but upload throws an exception
Exception in thread "main" java.util.concurrent.CompletionException: com.github.instagram4j.instagram4j.exceptions.IGResponseException
	at com.github.instagram4j.instagram4j.IGClient$1.handle(IGClient.java:86)
	at com.github.instagram4j.instagram4j.IGClient.lambda$sendRequest$5(IGClient.java:152)
	at java.util.concurrent.CompletableFuture.uniExceptionally(CompletableFuture.java:884)
	at java.util.concurrent.CompletableFuture$UniExceptionally.tryFire(CompletableFuture.java:866)
	at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:488)
	at java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1975)
	at com.github.instagram4j.instagram4j.IGClient$2.onResponse(IGClient.java:136)
	at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:504)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: com.github.instagram4j.instagram4j.exceptions.IGResponseException
	at com.github.instagram4j.instagram4j.requests.IGRequest.parseResponse(IGRequest.java:72)
	at com.github.instagram4j.instagram4j.IGClient.lambda$sendRequest$4(IGClient.java:149)
	at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:616)
	at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:591)
	... 7 more

And this is the log data
11:24:18.765 [main] INFO com.github.instagram4j.instagram4j.IGClient - Sending request : https://i.instagram.com/rupload_igphoto/1604917458756_0_6670466801
11:24:18.833 [main] INFO com.github.instagram4j.instagram4j.IGClient - Sending request : https://i.instagram.com/rupload_igphoto/1604917458832_0_8832262046
11:24:18.833 [main] INFO com.github.instagram4j.instagram4j.IGClient - Sending request : https://i.instagram.com/rupload_igphoto/1604917458833_0_2168694099
11:24:18.835 [main] INFO com.github.instagram4j.instagram4j.IGClient - Sending request : https://i.instagram.com/rupload_igphoto/1604917458835_0_7205570840
11:24:18.836 [main] INFO com.github.instagram4j.instagram4j.IGClient - Sending request : https://i.instagram.com/rupload_igphoto/1604917458836_0_3318497686
11:24:19.447 [OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/rupload_igphoto/1604917458756_0_6670466801 : 400
11:24:19.450 [OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/rupload_igphoto/1604917458756_0_6670466801 with body : {"debug_info":{"retriable":false,"type":"ProcessingFailedError","message":"Request processing failed"}}
11:24:19.451 [OkHttp https://i.instagram.com/...] DEBUG com.github.instagram4j.instagram4j.requests.IGRequest - rupload_igphoto/1604917458756_0_6670466801 parsing response : {"debug_info":{"retriable":false,"type":"ProcessingFailedError","message":"Request processing failed"}}
11:24:19.869 [OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/rupload_igphoto/1604917458835_0_7205570840 : 200
11:24:19.869 [OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/rupload_igphoto/1604917458835_0_7205570840 with body : {"upload_id": "1604917458746", "xsharing_nonces": {}, "status": "ok"}
11:24:19.869 [OkHttp https://i.instagram.com/...] DEBUG com.github.instagram4j.instagram4j.requests.IGRequest - rupload_igphoto/1604917458835_0_7205570840 parsing response : {"upload_id": "1604917458746", "xsharing_nonces": {}, "status": "ok"}
11:24:19.886 [OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/rupload_igphoto/1604917458836_0_3318497686 : 500
11:24:19.886 [OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/rupload_igphoto/1604917458836_0_3318497686 with body : {"debug_info":{"retriable":false,"type":"ProcessingFailedError","message":"Request processing failed"}}
11:24:19.886 [OkHttp https://i.instagram.com/...] DEBUG com.github.instagram4j.instagram4j.requests.IGRequest - rupload_igphoto/1604917458836_0_3318497686 parsing response : {"debug_info":{"retriable":false,"type":"ProcessingFailedError","message":"Request processing failed"}}
11:24:19.902 [OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/rupload_igphoto/1604917458832_0_8832262046 : 200
11:24:19.903 [OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/rupload_igphoto/1604917458832_0_8832262046 with body : {"upload_id": "1604917458745", "xsharing_nonces": {}, "status": "ok"}
11:24:19.903 [OkHttp https://i.instagram.com/...] DEBUG com.github.instagram4j.instagram4j.requests.IGRequest - rupload_igphoto/1604917458832_0_8832262046 parsing response : {"upload_id": "1604917458745", "xsharing_nonces": {}, "status": "ok"}
11:24:19.909 [OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/rupload_igphoto/1604917458833_0_2168694099 : 500
11:24:19.910 [OkHttp https://i.instagram.com/...] INFO com.github.instagram4j.instagram4j.IGClient - Response for https://i.instagram.com/rupload_igphoto/1604917458833_0_2168694099 with body : {"debug_info":{"retriable":false,"type":"ProcessingFailedError","message":"Request processing failed"}}
11:24:19.910 [OkHttp https://i.instagram.com/...] DEBUG com.github.instagram4j.instagram4j.requests.IGRequest - rupload_igphoto/1604917458833_0_2168694099 parsing response : {"debug_info":{"retriable":false,"type":"ProcessingFailedError","message":"Request processing failed"}}

The whole JSON response I'm getting is
{"debug_info":{"retriable":false,"type":"ProcessingFailedError","message":"Request processing failed"}}
Login and retrieving other kind of data however works fine

Hi please make sure your photos are within acceptable dimensions for Instagram. If possible could you provide the photos that are causing the issue? It seems some photos work while others do not in your logs. I cannot reproduce the issue on my end.

Thank you, that was indeed the issue I was not meeting the minimum image size apparently.
Now I'm resizing images up to 800x800 and squaring them for good measure and it seems to be working properly.
Although I feel like it might be worth mentioning somewhere in wiki or javadocs that images should meet certain standards in order to be uploaded

I will make a note of this. For now and future reference
here is the Instagram article detailing what dimensions are allowed.
Article

I think it's also worth mentioning that PNG images are rejected as well regardless the size requirements, I suspect that might have to do with the fact they have the alpha channel and Instagram doesn't support that, or the PNG format altogether specifically using BufferedImage.TYPE_INT_ARGB at least from my tests.

Does its solve your issue @NxDs ?
I have changed image size & everything but still getting same response
{"debug_info":{"retriable":false,"type":"ProcessingFailedError","message":"Request processing failed"}}

Yes for me the issue was the image size and the image format, this is the method I made to normalize images and make them squared, at least 800x800 and RGB format
public BufferedImage squareImage(BufferedImage image, int type) {
        if (image.getWidth() == image.getHeight() && image.getWidth() >= 800  && image.getType() == type) return image;

        int size = Math.max(800, Math.max(image.getWidth(), image.getHeight()));
        BufferedImage res = new BufferedImage(size, size, type);
        Graphics2D g2 = res.createGraphics();

        double ratio = size / (double) (Math.max(image.getWidth(), image.getHeight()));
        int width = (int) (image.getWidth() * ratio);
        int height = (int) (image.getHeight() * ratio);

        g2.drawImage(image, res.getWidth() / 2 - width / 2, res.getHeight() / 2 - height / 2, width, height, null);
        g2.dispose();

        return res;
    }

And to use it
squareImage(image, BufferedImage.TYPE_INT_RGB)
Although it should be noted that there's most likely a maximum size for the images that instagram can allow, the method I just provided doesn't take that into account as it only scales up small images
I'm also not entirely sure if squaring the image is a requirement but since it suits my purpose I do that too, note that it doesn't simply square the image it keeps the ratio and simply adds black bands either on top or on the sides depending on the original ratio, you may rework my method to fit your needs
Also note that 800 pixels is an arbitrary size I used that worked for me, the minimum limit might be smaller than that tho I suppose unless there's a clearer API specification somewhere it will require some trial and error

@NxDs thanks for your quick response

hi i have same problem and none of above approach worked for me!
previous version (1.x.x) upload photo but new release (2.x.x) not uploading same photo
please help me!!!

hi i have same problem and none of above approach worked for me!
previous version (1.x.x) upload photo but new release (2.x.x) not uploading same photo
please help me!!!

https://github.com/instagram4j/instagram4j/issues/564#issuecomment-819816701


Fixed D2D1_LAYER_PARAMETERS contentBounds description

I'm assuming that the description at the following URL is the correct description (that content outside of the content bounds is guaranteed not to render).
https://docs.microsoft.com/en-us/windows/win32/direct2d/direct2d-layers-overview#creating-layers

The content bounds of the layer. Content outside these bounds is guaranteed not to render.

As such, I'm proposing to change the current page to match.

I'll check which of these is correct. I could see it going either way. Let's hold off completing this PR until I get info from the D2D PM.

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

This is the wording we want. I'm currently fixing the Creating layers topic to match this wording.
Thanks!
Steve

This is the wording we want. I'm currently fixing the Creating layers topic to match this wording.
Thanks!
Steve

Thanks Steve! Glad to get them consistent :-)


no negative numbers

It's optional to merge, but I'm unsure if you want negatives for your counter.

I like the idea!
Maybe we can add an optional prop that decides if it should count up towards the number or down towards 0?

alright cool made some new changes

This is awesome! LGTM :)


Change order of dependencies in libjvm_stub target

When using this project as an external dependency, I get the following error:
external/fmeum_rules_jni/jni/tools/libjvm_stub/libjvm_stub.c:234: error: undefined reference to 'rules_jni_internal_get_bazel_java_home'
I believe that it comes from the current order of dependencies specified in the libjvm_stub target:
https://github.com/fmeum/rules_jni/blob/d4f53044727e80729886b53eedd5c90fb73e6e11/jni/tools/libjvm_stub/BUILD.bazel#L23-L32
libjvm_stub_lib target declares a function rules_jni_internal_get_bazel_java_home in rules_jni_internal.h file and its definition is supplied in bazel.cpp file, which is a part of the bazel target.
Because of this, bazel target should be after libjvm_stub_lib in the dependencies of libjvm_stub.
Here is a discussion about the linking order: https://stackoverflow.com/questions/45135/why-does-the-order-in-which-libraries-are-linked-sometimes-cause-errors-in-gcc. tldr: "library that needs symbols must be first, then the library that resolves the symbol"

Nice catch, thanks for sending a fix. I just added some more extensive comments.
I suspect that this can only happen if you don't call rules_jni_init since that symbol is only defined in and would thus mark :bazel as required. Is that correct? If so, you might want to add that call just so that hermetic JDK discovery works as expected.

Thanks for the quick reply and new release :smile:
Thanks for mentioning rules_jni_init. This seems to be exactly what's happening. After adding a call to rules_jni_init in a previously failing target, it compiles even with v0.8.0. It was the only target using this as a dependency that failed, all the others called rules_jni_init.


How to link

Hi,
I am struggling with link an object to its detail information in the same swagger file.
I am currently using html hyperlink.
Here are what I did:

I have a link in GeoAddress definition to see PostalAddress detail in different uri in the same swagger.yaml ( first image);

when I clicked on PostalAddress link, the url on the address bar changed to position where PostalAddress tab should be opened, but it didn't  open automatically  until I clicked on refresh button/ F5(second image);

Any idea to solve the issue?

I'm sorry but this is an issue to be filed in swagger-ui.


[SPARK-19716][SQL][follow-up] UnresolvedMapObjects should always be serializable

What changes were proposed in this pull request?
In https://github.com/apache/spark/pull/17398 we introduced UnresolvedMapObjects as a placeholder of MapObjects. Unfortunately UnresolvedMapObjects is not serializable as its function may reference Scala Type which is not serializable.
Ideally this is fine, as we will never serialize and send unresolved expressions to executors. However users may accidentally do this, e.g. mistakenly reference an encoder instance when implementing Aggregator, we should fix it so that it's just a performance issue(more network traffic) and should not fail the query.
How was this patch tested?
N/A

Test build #75809 has started for PR 17639 at commit bb0a14a.

cc @koertkuipers

Test build #75809 has finished for PR 17639 at commit bb0a14a.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class UnresolvedMapObjects(

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75809/
Test PASSed.

@cloud-fan thanks for doing this

merging to master!


Which Cupy/CUDA version is required to run the involution_cuda?

Which Cupy/CUDA version is required to run the involution_cuda?  I installed the following with conda:
cudatoolkit               11.0.221             h6bb024c_0    anaconda
cudnn                     <IP_ADDRESS>             h90431f1_0    conda-forge
cupy                      9.0.0            py37h4fdb0f7_1    conda-forge
cutensor                  <IP_ADDRESS>              h96e36e3_3    conda-forge

And although I can import cupy successfully, the following error occurs when I try to use involution_cuda:
cupy.cuda.compiler.CompileException: /tmp/tmpkhpxkpnj/817e920ba5cfc69af1016cdb64b60bad_2.cubin.cu(6): error: identifier "None" is undefined

/tmp/tmpkhpxkpnj/817e920ba5cfc69af1016cdb64b60bad_2.cubin.cu(6): error: identifier "None" is undefined

/tmp/tmpkhpxkpnj/817e920ba5cfc69af1016cdb64b60bad_2.cubin.cu(6): error: identifier "None" is undefined

/tmp/tmpkhpxkpnj/817e920ba5cfc69af1016cdb64b60bad_2.cubin.cu(13): error: identifier "None" is undefined

4 errors detected in the compilation of "/tmp/tmpkhpxkpnj/817e920ba5cfc69af1016cdb64b60bad_2.cubin.cu".

Would appreciate any help, thanks!

same errors with cupy=8.3.0 with a RTX3060 in cuda=11.2. Could you share the methods to solve it? THX


Roll Engine from 3cda7f5807db to f90698a89695 (18 revisions)

https://github.com/flutter/engine/compare/3cda7f5807db...f90698a89695
2021-05-18<EMAIL_ADDRESS>Roll Fuchsia Mac SDK from 7WNQRHsHN... to F5TX4MaEg... (flutter/engine#26220)
2021-05-18<EMAIL_ADDRESS>Roll Dart SDK from 510f26486328 to 13e329e614f2 (1 revision) (flutter/engine#26218)
2021-05-18<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from AUWVgDkx6... to boele8geO... (flutter/engine#26217)
2021-05-18<EMAIL_ADDRESS>Roll Skia from e8cd0a54041e to 3d854bade6de (4 revisions) (flutter/engine#26216)
2021-05-18<EMAIL_ADDRESS>Roll Skia from 2fed9f62d29a to e8cd0a54041e (2 revisions) (flutter/engine#26213)
2021-05-18<EMAIL_ADDRESS>Roll Dart SDK from 67be110b5ba8 to 510f26486328 (3 revisions) (flutter/engine#26212)
2021-05-18<EMAIL_ADDRESS>Add more diagrams for deferred components docs, fix alignment of existing one (flutter/engine#26209)
2021-05-18<EMAIL_ADDRESS>Roll Fuchsia Mac SDK from KmSY84b_E... to 7WNQRHsHN... (flutter/engine#26207)
2021-05-18<EMAIL_ADDRESS>Roll Skia from 5b38536d76ae to 2fed9f62d29a (7 revisions) (flutter/engine#26206)
2021-05-17<EMAIL_ADDRESS>Web ImageFilter.matrix support (flutter/engine#25982)
2021-05-17<EMAIL_ADDRESS>Prepare to move --delete-tostring-package-uri option to Dart SDK (flutter/engine#26196)
2021-05-17<EMAIL_ADDRESS>[icu] Upgrade ICU to 69.1, the same commit used by Chromimum latest (flutter/engine#26200)
2021-05-17<EMAIL_ADDRESS>Roll Skia from<PHONE_NUMBER>36 to 5b38536d76ae (7 revisions) (flutter/engine#26202)
2021-05-17<EMAIL_ADDRESS>Reland outputs a json version of the package manifest. (flutter/engine#26163)
2021-05-17<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from l6XmTSLnt... to AUWVgDkx6... (flutter/engine#26201)
2021-05-17<EMAIL_ADDRESS>Add image generator registry (flutter/engine#25987)
2021-05-17<EMAIL_ADDRESS>Roll Skia from c1f641104531 to<PHONE_NUMBER>36 (4 revisions) (flutter/engine#26197)
2021-05-17<EMAIL_ADDRESS>fuchsia: Only send different ViewProperties (flutter/engine#26170)
Also rolling transitive DEPS:
fuchsia/sdk/core/linux-amd64 from l6XmTSLnt_jR to boele8geOQxF
fuchsia/sdk/core/mac-amd64 from KmSY84b_Efmz to F5TX4MaEgZsf
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<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Commit queue failed; closing this roll.


[LANG-1723]: Throw NumberFormatException instead of IndexOutOfBoundsException in NumberUtils.getMantissa(String, int)

This PR wraps possible IndexOutOfBoundsException with NumberFormatException when invalid string is parsed to NumberUtils.getMantissa(String, int) method and cause the String.substring(int, int) throws IndexOutOfBoundsException.

Codecov Report
Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (e298d0b) 92.15% compared to head (b81ac60) 92.14%.
 Consider uploading reports for the commit 2236e39 to get more accurate results

Files
Patch %
Lines

...ava/org/apache/commons/lang3/math/NumberUtils.java
50.00%
1 Missing and 1 partial :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #1145      +/-   ##
============================================
- Coverage     92.15%   92.14%   -0.02%
- Complexity     7596     7598       +2
============================================
  Files           200      200
  Lines         15910    15914       +4
  Branches       2925     2927       +2
============================================
+ Hits          14662    14664       +2
- Misses          675      676       +1
- Partials        573      574       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


MonteCarloAnalyzerWithStochasticMaterial bug

There is a bug concerning I/O streams with respect to
using (sw = File.CreateText(fileNameTimes))
System.IO.IOException
HResult=0x800704C8
Message=The requested operation cannot be performed on a file with a user-mapped section open

Link to code segment plz...

https://github.com/isaar/MSolve/blob/606e86f31728f2ac0db0df94beebea784c9d143e/ISAAR.MSolve.Analyzers/MonteCarloAnalyzerWithStochasticMaterial.cs#L284-L291


Add Json output for registry output

Documentation changes: Please include [skip ci] in your commit message as well
/kind documentation
[skip ci]

What does does this PR do / why we need it:
Which issue(s) this PR fixes:
Fixes #3659
add json output method for registry list command
PR acceptance criteria:

[ ] Unit test

[ ] Integration test

[ ] Documentation

How to test changes / Special notes to the reviewer:
odo registry list -o json

@dharmit thanks~, updated just now

/retest

/lgtm


chroot: fix parsing of --userspec argument

Fix the parsing of the --userspec=USER:GROUP argument so that the both the user and the group are optional, and update the error message to match that of GNU chroot. This commit also removes the incorrect clap arguments for --user and --group. In chroot --user=USER, the --user is an abbreviation of --userspec, and in chroot --group=GROUP, the --group is an abbreviation of --groups.
Closes #7040.

I need to update the tests to only run chroot as root.


wrapping version issue

Describe the bug
i used the quick star example but i got the following
Unhandled Exception: MissingPluginException(No implementation found for method create on channel agora_rtc_engine)
To Reproduce
Steps to reproduce the behavior:

pub get agora_rtc_engine: ^5.1.0
copied the quick star example
i make sure every thing fine
i got the previous error message

Expected behavior
to work as expected in doc .
Desktop (please complete the following information):

OS: [windows]
Browser [chrome]

Smartphone (please complete the following information):

Device: [redmi note 9]
OS: [android]

Additional context
when i got that error message so i decided to flutter clean then it is completely not install the plugin with new error message which is
FAILURE: Build failed with an exception.
Where:
Script 'C:\src\flutter\packages\flutter_tools\gradle\flutter.gradle' line: 1102
What went wrong:
Execution failed for task ':app:compileFlutterBuildDebug'.
Process 'command 'C:\src\flutter\bin\flutter.bat'' finished with non-zero exit value 1
Try:
Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
Get more help at https://help.gradle.org/
BUILD FAILED in 52s
Exception: Gradle task assembleDebug failed with exit code 1
my flutter sdk is 2.10.5  and the gradle-7.4.1 .. with latest classpath 'com.android.tools.build:gradle:7.1.3'
everything seem good in my flutter doctor
thanks

hey i am facing the same error

It seems it's duplicated issue https://github.com/AgoraIO/Agora-Flutter-SDK/issues/659

Duplicated. Pls keep track here https://github.com/AgoraIO/Agora-Flutter-SDK/issues/659


Fix artifact path for debug builds

Currently build artifacts are only getting uploaded for the Release configuration jobs. This change updates the AppVeyor definition to include artifacts for all build jobs.

:memo: Verified the build output for the AppVeyor job before merging


[Feature Request]: Form Library

Feature description
Support a form library, maybe formik?
PF has an interface here: https://github.com/patternfly-labs/formik-pf
Describe alternatives you've considered
No response
Anything else?
No response

Maybe related to #1042

Migrated to:  https://issues.redhat.com/browse/RHOAIENG-2406


[SIL] Do not drop inner ExtInfo while rebuilding FunctionTypes

This is really a question in the form of a pull request. Why are we dropping the inner ExtInfo here? This seems like a bug.

@swift-ci please test

It could be that nothing looks at the extInfo, inner or outer, or the function type we build here.

Yeah, the way ExtInfo is used to carry state across SIL function type lowering is pretty haphazard and gross in general. It might be worth redoing it so that the ExtInfo in any intermediate function types is just completely ignored, and the SIL ExtInfo gets computed separately.

ExtInfo handling in general seems haphazard. It seems really easy to drop ExtInfo bits on the floor when deriving one function type from another. I imagine the idea was/is that most of the time the bits don't matter and they can be copied, but I'm not sure that works well in practice. Are people fond of the design?


Amended hello-world/description.md to be formatted to 80 chars.

Should allow reading of the rendered README.md easier if viewing in a restricted window.
I am not sure if this is even needed but I thought I would say anyway. I don't mind going through the rest of the description files and doing the same but I am aware this could be overkill.
When viewed through a restricted window in vim the README for a hello-world exercise was looking like this:

A quick format and it now looks like this:

Yes, I think so. We do have predecent at https://github.com/exercism/x-common/pull/200#r55940147 indicating we would like wrapping.

In a more general vein (not directly related to this PR, but only as an extension of it), we might like to write somewhere, maybe in the contributing guide, that we like to wrap our descriptions at N characters.
We might also like to consider looking for all files that have long lines: git grep -El '.{81,}' exercises/*/description.md

This looks great! Yeah, I agree with both of you; I think we should generally reformat to 80 columns for the description.md files, not because terminals are narrow (they usually aren't anymore), but because narrower lines are easier for humans to parse.
The Go project has some "readability" guidelines that are used for all code reviews internally at Google, and also on the Go project itself, and it has a section on long lines: https://github.com/golang/go/wiki/CodeReviewComments#line-length

Comments are typically wrapped before no more than 80 characters, not because it's a rule, but because it's more readable when viewing in an editor that might be sized to show hundreds of columns wide. Humans are better at following narrow text (e.g. columns in a newspaper) than giant walls of wide text, as a wide editor might show. Regardless, godoc should render it nicely either way.

I'm tempted to open a new issue that generally talks about reformatting the description.md file, and then generating one issue for each exercise that is to verify that it's formatted correctly, and reformat it if it isn't.
This way we could tag these with "good first patch" and "hacktoberfest" and we could get a bunch of people helping with it.

I have a branch in my local that formats the remaining description.md files. I might put that up and see what happens. Just need time to go through it make sure it is ok. I should have that done for tomorrow night (BST). Thanks for the merge @kytrinyx

I have a branch in my local that formats the remaining description.md files.

Nice! I won't worry about generating lots of tickets, then :)


Disable on open socket connection

Is there a way to disable the spinning at the top left corner when we have an open socket connection? We'd like to trigger the spinning symbol when we make URL requests only. Thanks!

All of this logic is currently contained in AFNetworkActivityIndicatorManager.
If you require custom logic, you'll need to write your own similar class.
Thanks!


add the capability to override memory options

since the last release , the xmx and xms are hardcoded on env , the goal is to use ACTIVEMQ_OPTS_MEMORY environement variable if needed to override memory options

Thanks for the PR, this seems reasonable to me, would you be able to create a Jira for this and include the Jira number in the commit to track the change? https://issues.apache.org/jira/projects/AMQ

Looks like this was changed here: https://github.com/apache/activemq/commit/a767bda603119387af8e8ce06af268470fe33c3a
The Xms change made sense (going lower) but obviously dropping that If statement is an issue. So been broken for a while but we should change it back to allow overriding.


Massive xunit test performance degradation in .NET core 2.1.700 and 2.2.300

FYI. I haven't raised this against xunit, because the only difference is the two releases of .NET Core.
General
Operating System

OS: Linux - specifically containers
Versions: 2.1.700 and 2.2.300

I've found that the latest release .NET Core 2.1 & 2.2 have introduced a performance degradation when executing xunit tests via dotnet test.
I have found this with 3 different OSS projects I maintain, and across two different CI providers (CircleCI & Travis). The specific details are below.
The following are builds of identical source code running against 4 different releases of .NET core running in CircleCI using containers.
Please see the compare-dotnet-releases branch of https://github.com/JSkimming/abioc.

Built Against .NET Core 2.1.604 - Takes 42 seconds
Built Against .NET Core 2.2.204 - Takes 48 seconds
Built Against .NET Core 2.1.700 - Takes 19 minutes 13 seconds seconds
Built Against .NET Core 2.2.300 - Takes 19 minutes 3 seconds seconds

As you can see the test execution takes an order of magnitude longer.
Here is the same build in travis. - NOTE: The mac build is fine because it is pinned to an earlier version of .NET Core.
Here are two completely different projects, both exhibiting the same issue in CircleCI and Travvis
https://circleci.com/gh/JSkimming/tesla-net/tree/master
https://travis-ci.org/JSkimming/tesla-net/builds/531160500
https://circleci.com/gh/JSkimming/Castle.Core.AsyncInterceptor/tree/master
https://travis-ci.org/JSkimming/Castle.Core.AsyncInterceptor/builds/530615608

Did you get a chance to collect traces and compare where the difference comes from?
Given that latest version is fast, is it worth investigation?
cc @adamsitnik @billwert @brianrob

Given that latest version is fast, is it worth investigation?

@karelz It's the latest versions that are slow.

Did you get a chance to collect traces and compare where the difference comes from?

Not yet, how should I go about collecting traces?

oh, I didn't notice it is minutes, not seconds. That is bad.
@adamsitnik can you please take a look? This looks serious.
@livarcocc @nguerrera is it a known issue?

oh, I didn't notice it is minutes, not seconds. That is bad.
@adamsitnik can you please take a look? This looks serious.
@livarcocc @nguerrera is it a known issue?

@karelz I'm unable to replicate it on my machine 😉

I've tried on Windows, WSL and Docker (there's a helper Dockerfile in the root of the repo), but given it's happening on two different CI systems, and three different OSS projects, I figured it worth reporting before being able to replicate on my laptop.
The fastest way to execute the tests is to run coverage.cmd on windows, and coverage.sh on linux, coverage.cmd just tests .NET Framework though.

OK, that is interesting - I assume we will have similar problems to replicate it.
Are you able to reproduce it on similar machine setup in cloud? (similar VM used by the CI systems)

I assume we will have similar problems to replicate it.

Quite possibly.

Are you able to reproduce it on similar machine setup in cloud? (similar VM used by the CI systems)

Nope, I haven't tried that. I'm not in a position to try that at the moment either.

I'm going to try the Dockerfile out and see if I can reproduce the regression.

@livarcocc @nguerrera is it a known issue?

First I hear of it.

As you can see the test execution takes an order of magnitude longer.

Strangely, the dotnet test runs are reporting mere seconds of total time while the overall job takes much longer. Is it possible to get timestamps at the start/end of each command?

CC @singhsarab

I'm going to try the Dockerfile out and see if I can reproduce the regression.

@brianrob I've just pushed an updated Dockerfile, and I'm experimenting with tweaking the following:
docker build --cpuset-cpus=0 --cpuset-mems=0 --cpu-period=50 --build-arg CACHE_BUST=1 .

You need to keep changing CACHE_BUST and it will cache up to the test execution.

Is it possible to get timestamps at the start/end of each command?

@nguerrera I've just pushed an update to display the dates, checkout the builds of this PR JSkimming/abioc#82

It seems that I'm not able to reproduce this either.

@brianrob is there something we can ask @JSkimming to collect that we can then analyze?

Yes.  If you're able to reproduce the issue, please follow the instructions at https://github.com/dotnet/coreclr/blob/master/Documentation/project-docs/linux-performance-tracing.md to create a trace for each of the good and bad cases.  You don't need to capture the whole thing - let's just start with 20 seconds for each.

@brianrob any tips on how to get that running in a hosted CI system?
So far I've only been able to replicate the issue on CircleCI and Travis.
There's a lot of sudo and having multiple shell windows open in those instructions, none of which I'm sure I can do easily. I believe I can configure Travis to be able to use sudo, though I think that will change it from container builds to VMs, which may no longer exhibit the issue.
If it's something that can be enabled on Azure DevOps, I'm willing to set-up the build there too, though until I try, I don't know if I'll be able to replicate things.

Strangely, the dotnet test runs are reporting mere seconds of total time while the overall job takes much longer. Is it possible to get timestamps at the start/end of each command?

@nguerrera I've updated the main description with links to the builds with timings between the commands.

@JSkimming sadly we are not familiar with those environments.
If it is related only to specific environment (special container in CI systems), it may be very well some problem in the environment setup ...

OK, I think I've found the issue.
TL;DR
On a hunch, I changed the script to stop displaying the output of dotnet test, and things are back to normal. See here for CircleCI, and here for Travis.
The Hunch
I noticed the test output flickered when displaying a message.

Test run in progress...

Here's an example

I get the impression the CLI is writing that message a lot, which eventually results in the flickering because a buffer somewhere is filled.
Hosted CI systems capture the stdout of the tools being executed, but in their case, all those writes are going through code (that ultimately streams to the browser) rather than directly to a terminal, and all those stdout writes from dotnet test are destroying things.
This also explains the discrepancy between the test execution timings from the dotnet test and the actual timings I inserted. See below; the CLI states the tests executed in 2.1397 Seconds whereas the real execution time is 10m 49s.
Wed May 22 20:53:05 UTC 2019
0 minutes and 7 seconds elapsed.

$ dotnet test --no-restore --no-build -f netcoreapp2.1 -c Release /root/project/test/Abioc.Tests.Internal/Abioc.Tests.Internal.csproj --results-directory /root/project/test/TestResults/output/ --logger "trx;LogFileName=Abioc.Tests.Internal.trx"
Test run for /root/project/test/Abioc.Tests.Internal/bin/Release/netcoreapp2.1/Abioc.Tests.Internal.dll(.NETCoreApp,Version=v2.1)
Microsoft (R) Test Execution Command Line Tool Version 16.1.0
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...
Test run in progress.Test run in progress ... Results File: /root/project/test/TestResults/output/Abioc.Tests.Internal.trx

Test Run Successful.
Total tests: 310
     Passed: 310
 Total time: 2.1397 Seconds

Wed May 22 21:03:54 UTC 2019
10 minutes and 56 seconds elapsed.

I'm not sure where to start looking for what changed in the dotnet cli that caused all this. All scenarios are using v16.1.0 of vstest.

Awesome to see we are closer to a root cause!
@nguerrera do you have an idea if CLI is responsible for too frequent text update in this case?

Looks like https://github.com/microsoft/vstest/pull/1964
@singhsarab

@nguerrera Ahh, I misread the numbers. The earlier (working) release was 16.0.1, and those changes when into 16.1.0. So it is in vstest.

From a quick reading of the code I think I may have identified the issue.
The ProgressIndicator clears and redisplays the progress message whenever it receives successive calls to Pause() then Start().
This occurs whenever ConsoleLogger.TestMessageHandler() or  ConsoleLogger.TestResultHandler is called regardless of the verbosity level.
As a result, the log message is constantly being redrawn, even if the verbosity level would not result in a message.
I'm going to have a look at a potential fix, and submit a PR later. I'll keep you updated on progress.

@karelz This should be moved to microsoft/vstest repo.

@JSkimming Awesome work tracking this down!

@karelz I've raised this PR microsoft/vstest#2024, all feedback is welcome.
Do you want to raise this as an issue in the microsoft/vstest repo, I'm happy to do it if it helps.

Awesome. Please open issue there if they need it, but maybe PR is enough. We can't move issues cross-org.
ZenHub would make just a copy.
Awesome work, thanks a ton!!!

I observed a degradation of performance even in a Linux host environment (not only in a CI environment).
One of our test project (around 2800 tests)  took about 30 seconds (on 2.1.604) and now it takes about 1.87 minutes. We talk about a 4.5 times longer to run tests than previous SDK.
Do you know if the PR involved will fix that too?

@karelz this issue is still not resolved.
The fix I implemented was merged on the 28th May, and the NuGet package was released on the 30th May, but until there is a .NET Core SDK release where the latest version of VSTest is "inserted", the problem persists.
Is there any update on when a new SDK will be released incorporating the latest VSTest?

The .NET SDK releases 2.1.701 & 2.2.301 are now available and contain the fixes.


Fix shebang to use /usr/bin/env for Python 3

This pull request updates the shebang in the Python script to use the more portable #!/usr/bin/env python3 instead of #!/usr/env python3.
Using /usr/bin/env in the shebang allows the script to find the Python 3 interpreter in the user's $PATH, making the script more portable across systems with different Python installations. This change ensures compatibility and consistent behavior for users running the script on various systems.

Thanks!


Authorization Policy vNext -> Nested Table References

To further enhance the authorization policy capability, add the ability to map to nested tables/columns. For example:

Database Policy: Entity (book) "New Starch Press" eq @item().publisher_id.name

Because the policy is applied to the book entity, the nested policy will search the Publishers table using publisher_id to acquire the record where name column is "New Starch Press"
Nesting will apply to the @item "Policy Expression System Object" described in the request authorization RFC.

Hi, Is there any news on this, whether it is on the roadmap for the next releases?


Add Custom-Properties support for Orgs, Apps and Users

User story
Adding support to manage custom properties for organizations in the same way as for APIs

Custom-Properties support added for all entities: Application, Organizations and Users. Will be released with the next version 1.3.0.
#87


Status view not showing "Not Configured" component

Describe the bug
After Installing Dialogflow o from control center and before configuring the connector, one can't find the component on Status view as an Installed component but Not Configured.
To Reproduce
Steps to reproduce the behavior:

I installed Dialogflow from Catalog view
I opened Status view to find Dialogflow component as not configured.
I kept refreshing the status view.
See error when Dialogflow component doesn't appear.

Expected behavior
Dialogflow component should appear on Status view with "Not configured" status to give the user indication that this component missing configuration to run.
Screenshots
Environment

Browser: [Chrome]
Version: [0.50.0-alpha]

Additional context
Add any other context about the problem here.

@M-Shorouk one suggestion, perhaps we shouldn't allow Enable for components that are not configured (and are marked that require configuration in order to run). That way we enforce our desired flow: Install -> Configure (if required) -> Enable.

@ljupcovangelski yes as far as i remember the design flow was covering this sequence; just allowing Disable button when the component is actually Enabled... Otherwise, the component is shown there since its is "Installed" and shows "Not Configured" status.

@ljupcovangelski yes as far as i remember the design flow was covering this sequence; just allowing Disable button when the component is actually Enabled... Otherwise, the component is shown there since its is "Installed" and shows "Not Configured" status.

Ok, I'm just pointing out that "Checking whether the component can be enabled or not" is not something that we are doing at the moment.

@ljupcovangelski ah i thought it was done here 3361..
Also if it is not working for some reason, we can consider this current bug with this ticket 3357

3357

This is a separate issue I think and yes :+1: a very important one!
For enabling a non-configured component, you can try creating a new instance on the latest version (or use an existing instance). Install any source or some component that requires configuration. You are redirected to the Configuration screen after installation, but if you skip the Configuration part - you can still enable the component from the Status page.

Solved in v.53.0


[fcl][verify] adopt hash algo by key's hash algo

In some specific hardware key environments, SHA3_256 is not included. However, fcl uses SHA3_256 as the only hash algorithm when verifying user message and signature.
The hash algorithm bound to the key for user signature verification will be a better choice.

Thank you for contributing @sking789 🤓👍
We’ll review asap and provide feedback if necessary.


fix bloom viewport

Objective
fix bloom when used on a camera with a viewport specified
Solution

pass viewport into the prefilter shader, and use it to read from the correct section of the original rendered screen
don't apply viewport for the intermediate bloom passes, only for the final blend output

bors try

@james7132 before we merge this, this PR will generally be superseded by https://github.com/bevyengine/bevy/pull/6677, which is done and just needs reviewing. Up to you whether to still merge this until then, or not.

bors r+

bors retry

bors r+


Meta-release

Right now we each do one project at a time. If, given the order, could releaser do all of them?

That way each project 'lead' could say, project x is good and when all are good, one person does the release.

There is one small problem which is the promotion of artifacts from sonatype to central. We can of course automate this but we will have to introduce a waiting period (or rather pinging central to see if the artifact is already there). Our libs require the JARs to be available in Maven Central before their release process gets executed... So the release process can be pretty lengthy (which is not a problem of course)

This is working


[Feature] Get version of files before they were edited

Is this feature missing in the latest version?

[X] I'm using the latest release

Is your feature request related to a problem? Please describe.
I need a CI that makes sure a change is correct, so if a file was edited, i need the old ver. There is already recover_deleted_files, but I need something like recover_modified_files. The feature is the same, just need not limit it to deleted.
Describe the solution you'd like?
recover_modified_files?
Describe alternatives you've considered?
No response
Anything else?
No response
Code of Conduct

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

Hi @justanotheranonymoususer this seems like one off use case for now I’ll suggest utilizing a script that you can use to recover modified files.
We can revisit this in the future if it does become a general problem.

Isn't recover_deleted_files also a one-off problem then?
Basically I don't agree, I think it has many use cases, and it's a bummer to write a non-trivial script (with fetch and whatnot) for something you guys already worked on to implement correctly, all's needed is to not limit it to deleted files.

Basically all that's needed is to control this:
https://github.com/tj-actions/changed-files/blob/35d5a4d79f865a1a8db02b9f6fb4c5cd4b4809ef/src/main.ts#L159
To be able to also pass 'M'


Uncaught ECONNRESET somewhere in our code base

Hi,
a node operator on Kiwi News always reports the following error:

We don't know where this is coming from, but we think it is libp2p. Before opening an issue, I asked in the libp2p TG if someone could help us find the cause of this, but it was suggested that I open an issue: https://t.me/c/2109810685/11/818

Version: We use libp2p v0.40.0 https://github.com/attestate/kiwistand/blob/41aa70347eb8786f1cefa6746aa700a563c053c1/package.json#L83 we don't really have budget to upgrade this ATM

Platform: Ubuntu

Subsystem: I'm not sure. But we use a variety of libp2p packages where this could originate from, see this part of the package.json: https://github.com/attestate/kiwistand/blob/41aa70347eb8786f1cefa6746aa700a563c053c1/package.json#L47-L55

Severity: Critical because it makes our application panic
Description: This happens once two nodes are connected and exchanging messages. If one of the nodes unexpectedly crashes or gets terminated, then the other one will throw this error. I have checked most/all interactions I have with libp2p methods to make sure I'm try catching everything, but I haven't managed to find where this error is coming from. And also: the error doesn't have a stack trace, so I'm also unsure how I'd anyways find out more.
Steps to reproduce the error: Run two Kiwi News nodes, wait until they start the set reconciliation. Kill one node with Ctrl - C. Most likely the other will throw the ECONNRESET.

Version 0.40.0 of js-libp2p is around 2 years old. Since then there have been some significant changes and fixes to js-libp2p including some fixed memory leaks.
One thing you could try is enabling more verbose logging from libp2p by setting the DEBUG env var to *,*:debug to get everything and then narrow down.

I would strong advise upgrading to the latest libp2p, we simply do not have the capacity to support older versions.
There are detailed migration guides to make this as painless as possible.
The TCP transport has had several changes made to it in recent releases which make it more resilient, improves error handling and fixes a number of memory leaks.
Please upgrade and report back if this is still happening.