text:
429 Too Many Requests error for an account that scrapes Instagram stories of up to over 270 accounts twice nightly

Describe the bug
I currently split my Instagram story scraping into right now four accounts given the number of people I follow is quite high (my main account is following about 584). However, it seems one of my accounts get hit with a hard 429 Too Many Requests error, even though I scrape Instagram stories roughly twice a day. That account has been scraping about 277 accounts at a time, which is pretty high to a point that I could hit Instagram API limits easily. It's been working normal since around September 20, and I've been using Instaloader for Instagram story scraping following my favorite site used to do as such shut down last month.
To Reproduce
I created separate folders for each account that I use to scrape Instagram stories. For each folder, I set up a custom CMD file:
@echo off
instaloader +args.txt --no-posts --no-profile-pic --stories --no-metadata-json

And for each args.txt in the folder are the following:
--login=<IG username>
--password=<IG password>
--fast-update
account1
account2
account3
etc...
...
accountn

where account1, account2, account3, accountn are the list of accounts that I follow that I want to scrape its Instagram stories.
Expected behavior
It should not pop out the following error below. For instances where I'm scraping more than 75 accounts for that particular account I'm using to scrape Instagram stories, there should be a Too many queries in the last time cooldown message roughly every 10-12 minutes.
Error messages and tracebacks
Loaded session from <redacted>.
Logged in as <redacted>.
JSON Query to 345insta/feed/: 429 Too Many Requests [retrying; skip with ^C]
Requests within last 10/11/20/22/30/60 minutes grouped by type:
   <redacted>:    1    1    1    1    1    1
 *                            other:    1    1    1    1    1    1
Instagram responded with HTTP error "429 - Too Many Requests". Please
do not run multiple instances of Instaloader in parallel or within
short sequence. Also, do not use any Instagram App while Instaloader
is running.
'The request will be retried in 666 seconds, at 18:42.

As you see, that was my only request within the last hour. I was just getting started my first of two Instagram story scraping sessions per day, roughly around 6:30 PM and 11:30 PM each night. But it didn't work. I tried removing the account from the JSON Query, but when I tried again, I received the same 429 error again. Once it picks up all accounts, it will start to 'scrape' (receive and download) stories content (images and, if available, video) to my hard drive.
Instaloader version
4.5.3
Additional context
This account was one of three accounts that I am purposely using for story scraping after someone suggested me on Reddit. I was not receiving login errors. When I logged in to the account that was impacted by above issue at Instagram's website, I'm not receiving error messages on the site either (though I don't follow any other accounts with that account involved, plus two additional accounts for the purposes of Instagram story scraping).
I tried the other three accounts (my main account and two additional accounts for scraping-only duties including one that focused on a subset group of accounts based on the theme of following members that are or were members of a well-known series of Japanese female idols), and they were working just fine, except for my main account apparently, it got hit with the same error as well midway...
Loaded session from <redacted>.
Logged in as ryandtw. (note: this is my main IG account)
JSON Query to imsa_racing/feed/: 429 Too Many Requests [retrying; skip with ^C]
Requests within last 10/11/20/22/30/60 minutes grouped by type:
    <redacted>:    1    1    1    1    1    1
 *                            other:   39   39   39   39   39   39
Instagram responded with HTTP error "429 - Too Many Requests". Please
do not run multiple instances of Instaloader in parallel or within
short sequence. Also, do not use any Instagram App while Instaloader
is running.
The request will be retried in 573 seconds, at 19:45.

Also, the clause "logged-in accesses do not seem to be affected" does not apply to this issue - as explicitly stated, I was logged in for all instances.
*I put <redacted> over any material that can be considered private, particularly login username and password. Also, to clarify, I am running all four accounts for Instaloader under the same, single IP address.

EDIT: There was a similar issue (#822) where that person was also having a 429 error as well. See also issue #774.
Anyways, I've been scraping Instagram stories for years, but it seems Instagram Facebook (the parent company of Instagram) is closing more and more doors, limiting my choices on how I view and download stories of accounts that I follow. Going through each Instagram account on the website is inefficient and time-consuming, given how many accounts I follow. When my favorite website to scrape Instagram stories shut down last month, that was a large hole that Facebook covered up for scraping these stories (okay, it wasn't shut down by Facebook, but the owner of the site was concerned about 'legal issues', so he shut it down). Instaloader is proving me to be the last hole out right now, but I'm fearing Facebook is closing that hole as well. F Facebook.
There's another site called gramsave(dot)com but it only works for extracting actual Instagram posts, not downloading Instagram stories. :(
Or wait. Is Instagram down or something? Oh My IG (Chrome extension for regular Instagram posts, not stories) is still working fine.

Removing "feed/" seems to work.

Same problem, after one picture download :
Requests within last 10/11/20/22/30/60 minutes grouped by type:
d6f4427fbe92d846298cf93df0b937d3:    1    1    1    1    1    1
other:    1    1    1    1    1    1

                      iphone:    2    2    2    2    2    2

Instagram responded with HTTP error "429 - Too Many Requests". Please
do not run multiple instances of Instaloader in parallel or within
short sequence. Also, do not use any Instagram App while Instaloader
is running.
The request will be retried in 665 seconds, at 20:25.

Removing the "feed/" seems to work.
https://github.com/instaloader/instaloader/blob/f4ecfea64cc11efba44cda2b44c8cfe41adbd28a/instaloader/structures.py#L613

Many thanks. This solved the issue.

Remove "feed/" results in
Fatal error: 400 Bad Request

I run Instaloader out of the WIndows executable, not Python. What will I need to do? Do I have to run the Python version of Instaloader to take advantage of these changes? Or will a future update makes this possible?

Remove "feed/" results in
Fatal error: 400 Bad Request

In my case (I use separate accounts for my Android and instaloader), "400 Bad Request" means "account temporarily blocked by IG".
When I login with browser using the account for instaloader, IG requires me to verify my email and reset the password.
Following the instructions, I can use instaloader again.
However, it seems that IG blocks accounts more frequently than before.
I hadn't been blocked for months, but blocked 9 times in the last 3 months.

Is there a way to 'slow down' instaloader?

Instagram responded with HTTP error "429 - Too Many Requests". Please
do not run multiple instances of Instaloader in parallel or within
short sequence. Also, do not use any Instagram App while Instaloader
is running.
The request will be retried in 665 seconds, at 20:25.

I tried downloading a few (5-6 profiles) and afterwards started getting this issue permanently as well, even if I leave it rest for a few hours. Any suggestions how to get it successfully running again?

I signed out all sessions in Sign In Activity in IG settings so every single device is signed out. I am trying to download saved galery from single profile. I'm getting this after downloading single picture. Deleted /feed from the code but I am still getting this. Can anyone help how to get this running?

Requests within last 10/11/20/22/30/60 minutes grouped by type:
d6f4427fbe92d846298cf93df0b937d3:    2    2    2    2    2    2
f883d95537fbcd400f466f63d42bd8a1:    1    1    1    1    1    1
2b0673e0dc4580674a88d426fe00ea90:    1    1    1    1    1    1

                      iphone:    1    1    1    1    1    1

Instagram responded with HTTP error "429 - Too Many Requests". Please
do not run multiple instances of Instaloader in parallel or within
short sequence. Also, do not use any Instagram App while Instaloader
is running.
The request will be retried in 666 seconds, at 13:34.

It seems the no feed version hits me with a permanent rate limit. I have to wait several hours before it goes away.
I have a hypothesis. Without the feed/, it may be hitting the iPhone endpoint harder than ever. This ultimately makes the rate limit trip ooner.

The no feed/ version makes me hit rate limits much quicker. Now I can only do 10-15 accounts before I get a 429 error. Usually, I can download 50+ profiles without any issue.

I went back to the regular version with feed/, that fixed the issue of the issue ;)

Hi,
I tried instaloader once and it worked perfectly.
My code is as below
`
from instaloader import *
L = instaloader.Instaloader()
post =  Post.from_shortcode(L.context, 'CHQUZwssntm')
post_likes = post.get_likes()
for likee in post_likes:
print(likee.username)
`
Since yesterday I'm getting
`
JSON Query to graphql/query: 429 Too Many Requests [retrying; skip with ^C]
Requests within last 10/11/20/22/30/60 minutes grouped by type:
2b0673e0dc4580674a88d426fe00ea90:    1    1    1    1    1    1

1cb6ec562846122743b61e492c85999f:    1    1    1    1    1    1
Instagram responded with HTTP error "429 - Too Many Requests". Please
do not run multiple instances of Instaloader in parallel or within
short sequence. Also, do not use any Instagram App while Instaloader
is running.
The request will be retried in 666 seconds, at 20:32.
`

It would be really great if you could help me with this. Please let me know if there is a work around

I'm just starting out with instaloader, and have hit the same problem.
I did a simple loop script that brings back the followers of a test account with 50 followers.
I used the following code (so I should also be an authenticated user too).
[code]
Get instance
import instaloader
L = instaloader.Instaloader()
Login or load session
L.login("redact", "redact")        # (login)
Obtain profile metadata
profile = instaloader.Profile.from_username(L.context, "testaccount")
Print list of followees
follow_list = []
count=0
file = open("output.txt","a+")
for followee in profile.get_followers():
username = followee.username , followee.external_url
file.write(username + "\n")
print(username)
file.close()
I get straight away
JSON Query to testuser/feed/: 429 Too Many Requests [retrying; skip with ^C]
Requests within last 10/11/20/22/30/60 minutes grouped by type:

                       other:    1    1    1    1    1    1

Instagram responded with HTTP error "429 - Too Many Requests". Please
do not run multiple instances of Instaloader in parallel or within
short sequence. Also, do not use any Instagram App while Instaloader
is running.
The request will be retried in 666 seconds, at 10:17.
I spun up an instance in AWS, different part of the world, nothing else on the host, totally different IP block, same code, straight away exactly the same error.
I'm assuming this is the same problem ?

it works for me..
reboot your router.

Scraping stories with L.download_stories using a list of account ID's instead of names never ever returns error 429 - even when logged in - and I've no idea why
It only returns error 500, but you can easily overcome this by scraping the account IDs in batches of 50

it works for me..
reboot your router.

@ConfitureCheung after restarting the router, how can i resume process from last downloaded photo?

it works for me..
reboot your router.

@ConfitureCheung after restarting the router, how can i resume process from last downloaded photo?

First, i didn't use '--login' function to use instaloader as this is not a must requirement. so when i encounter this issue, i reboot my router. It really works for me although i don't know the true reason behind. but I see no one has mentioned it about this solution here so I hope to raise it out and hope it can help. But seems people don't appreciate..
you can also set 'max_connection_attempts' in the code. i set it to 1 as it gives me the optimal result but you better check with other comments here. they have better knowledge about that.
about your question, i am actually using instaloader to download multi accounts in a regular time base (say weekly). and when i design my code base on my need, i apply using excel function for storing information like ig name and file download record. so the file can download automatically into the folder i want and remove duplicate downloads by comparing with the excel created last week.
so in case you need to 'resume' the process, i would say to check the progress (say you have 20 ig ac to dl and you have finished 10, edit the excel and rerun the remaining 10 ig ac).
if you just need to 'resume' download progress for a single ig ac, i would suggest to add date & time condition for your download code.

It is mostly caused by additional higher resolution image url fetches done by _iphone_struct functions. When I disable this 429 errors become much rarer. It would be nice to have an option to disable this additional fetches from the command line. Those higher resolution images do not worth it.

Receiving a 429 error is always frustrating. However, a 429 message usually does not mean that the entire download process of Instaloader failed. Instead, Instaloader automatically stalls its download process for a few minutes and then should be able to continue without problems.
Nonetheless, getting a 429 response is something that should not happen. Instaloader's rate controlling logic intends to prevent these unusual responses by keeping track of the requests being sent and deferring subsequent ones in order to not reach Instagram's rate limits. In theory, this mechanism should work fine and completely prevent 429 errors, as long as the suggestions in the error message are followed (do not run multiple instances of Instaloader in parallel or within short sequence. Also, do not use any Instagram App while Instaloader is running).
I tried your Instaloader invocation (--no-posts --no-profile-pic --stories --no-metadata-json) with a similar-sized (about 300) set of profiles several times, both with version 4.5.3 and version 4.6rc1, and I do not receive the here-reported error. To me it seems that the default rate controller works fine.
When the 429 is happening, Instaloader automatically retries the failing request a few times. What has been the result of these retries?
Is the error reproducible or consistent in any way? For example, does the error always occur at the same profile, or does the request count table in the error message always show the same request counts?

Also, the clause "logged-in accesses do not seem to be affected" does not apply to this issue - as explicitly stated, I was logged in for all instances.

Maybe we're wrong. This clause refers to services, that in their nature offer promiscuous IP addresses, such as cloud, VPN and public proxy service. - Are you on such a service when getting the reported error?

I currently split my Instagram story scraping into right now four accounts given the number of people I follow is quite high (my main account is following about 584).
[...]
Also, to clarify, I am running all four accounts for Instaloader under the same, single IP address.

Do you run these four scraping processes in parallel?
(although, strictly speaking, unrelated to the 429 problem itself:) There was a recently-fixed efficiency-bug affecting your set of flags, which led Instaloader to do unnecessary queries (https://github.com/instaloader/instaloader/pull/905#issuecomment-743779187). This fix is included in version 4.6rc1, making your only-stories download task (--no-posts --no-profile-pic) very much faster. Version 4.6 also downloads stories in better quality (#712) than version 4.5. I recommend trying it out, and there is a chance that this problem disappears.

It is mostly caused by additional higher resolution image url fetches done by _iphone_struct functions. When I disable this 429 errors become much rarer. It would be nice to have an option to disable this additional fetches from the command line. Those higher resolution images do not worth it.

No, it's not. Instaloader 4.5 with the here-used invocation does not call any of the _iphone_struct functions nor does it do any additional higher resolution image url fetch. These high-quality story image fetches (#712) have been introduced later, and first been released in December 2020, more than two months after this issue has been reported.

Receiving a 429 error is always frustrating. However, a 429 message usually does not mean that the entire download process of Instaloader failed. Instead, Instaloader automatically stalls its download process for a few minutes and then should be able to continue without problems.
Nonetheless, getting a 429 response is something that should not happen. Instaloader's rate controlling logic intends to prevent these unusual responses by keeping track of the requests being sent and deferring subsequent ones in order to not reach Instagram's rate limits. In theory, this mechanism should work fine and completely prevent 429 errors, as long as the suggestions in the error message are followed (do not run multiple instances of Instaloader in parallel or within short sequence. Also, do not use any Instagram App while Instaloader is running).
I tried your Instaloader invocation (--no-posts --no-profile-pic --stories --no-metadata-json) with a similar-sized (about 300) set of profiles several times, both with version 4.5.3 and version 4.6rc1, and I do not receive the here-reported error. To me it seems that the default rate controller works fine.
When the 429 is happening, Instaloader automatically retries the failing request a few times. What has been the result of these retries?
Is the error reproducible or consistent in any way? For example, does the error always occur at the same profile, or does the request count table in the error message always show the same request counts?

Also, the clause "logged-in accesses do not seem to be affected" does not apply to this issue - as explicitly stated, I was logged in for all instances.

Maybe we're wrong. This clause refers to services, that in their nature offer promiscuous IP addresses, such as cloud, VPN and public proxy service. - Are you on such a service when getting the reported error?

I currently split my Instagram story scraping into right now four accounts given the number of people I follow is quite high (my main account is following about 584).
[...]
Also, to clarify, I am running all four accounts for Instaloader under the same, single IP address.

Do you run these four scraping processes in parallel?
(although, strictly speaking, unrelated to the 429 problem itself:) There was a recently-fixed efficiency-bug affecting your set of flags, which led Instaloader to do unnecessary queries (https://github.com/instaloader/instaloader/pull/905#issuecomment-743779187). This fix is included in version 4.6rc1, making your only-stories download task (--no-posts --no-profile-pic) very much faster. Version 4.6 also downloads stories in better quality (#712) than version 4.5. I recommend trying it out, and there is a chance that this problem disappears.

It is mostly caused by additional higher resolution image url fetches done by _iphone_struct functions. When I disable this 429 errors become much rarer. It would be nice to have an option to disable this additional fetches from the command line. Those higher resolution images do not worth it.

No, it's not. Instaloader 4.5 with the here-used invocation does not call any of the _iphone_struct functions nor does it do any additional higher resolution image url fetch. These high-quality story image fetches (#712) have been introduced later, and first been released in December 2020, more than two months after this issue has been reported.

I've literally downloaded like 10 posts from a profile or something
then I get
JSON Query to api/v1/media/2476648287284918078/info/: HTTP error code 403. [retrying; skip with ^C]
JSON Query to api/v1/media/2476648287284918078/info/: HTTP error code 403. [retrying; skip with ^C]
JSON Query to api/v1/media/2476648287284918078/info/: HTTP error code 403. Unable to fetch high quality image version of <Post CJe0n7VMnc->.
 somfilepath unchanged
HTTP redirect from https://www.instagram.com/graphql/query to https://www.instagram.com/accounts/login/
JSON Query to graphql/query: Redirected to login [retrying; skip with ^C]
Requests within last 10/11/20/22/30/60 minutes grouped by type:
                              other:    1    1    1    1    1    1
                             iphone:    3    3    3    3    3    3
   2b0673e0dc4580674a88d426fe00ea90:    1    1    1    1    1    1
 * 97b41c52301f77ce508f55e66d17620e:    1    1    1    1    1    1
Instagram responded with HTTP error "429 - Too Many Requests". Please
do not run multiple instances of Instaloader in parallel or within
short sequence. Also, do not use any Instagram App while Instaloader
is running.
The request will be retried in 666 seconds, at 13:24.

idk why it's totally unusable (API). If I manually (cmd) get a profile I think it does perfectly download the profile or at least gets the first 100.

I've literally downloaded like 10 posts from a profile or something
then I get
JSON Query to api/v1/media/2476648287284918078/info/: HTTP error code 403. [retrying; skip with ^C]
JSON Query to api/v1/media/2476648287284918078/info/: HTTP error code 403. [retrying; skip with ^C]
JSON Query to api/v1/media/2476648287284918078/info/: HTTP error code 403. Unable to fetch high quality image version of <Post CJe0n7VMnc->.
 somfilepath unchanged
HTTP redirect from https://www.instagram.com/graphql/query to https://www.instagram.com/accounts/login/
JSON Query to graphql/query: Redirected to login [retrying; skip with ^C]
Requests within last 10/11/20/22/30/60 minutes grouped by type:
                              other:    1    1    1    1    1    1
                             iphone:    3    3    3    3    3    3
   2b0673e0dc4580674a88d426fe00ea90:    1    1    1    1    1    1
 * 97b41c52301f77ce508f55e66d17620e:    1    1    1    1    1    1
Instagram responded with HTTP error "429 - Too Many Requests". Please
do not run multiple instances of Instaloader in parallel or within
short sequence. Also, do not use any Instagram App while Instaloader
is running.
The request will be retried in 666 seconds, at 13:24.

idk why it's totally unusable (API). If I manually (cmd) get a profile I think it does perfectly download the profile or at least gets the first 100.

I've literally downloaded like 10 posts from a profile or something
then I get
JSON Query to api/v1/media/2476648287284918078/info/: HTTP error code 403. [retrying; skip with ^C]
JSON Query to api/v1/media/2476648287284918078/info/: HTTP error code 403. [retrying; skip with ^C]
JSON Query to api/v1/media/2476648287284918078/info/: HTTP error code 403. Unable to fetch high quality image version of <Post CJe0n7VMnc->.
 somfilepath unchanged
HTTP redirect from https://www.instagram.com/graphql/query to https://www.instagram.com/accounts/login/
JSON Query to graphql/query: Redirected to login [retrying; skip with ^C]
Requests within last 10/11/20/22/30/60 minutes grouped by type:
                              other:    1    1    1    1    1    1
                             iphone:    3    3    3    3    3    3
   2b0673e0dc4580674a88d426fe00ea90:    1    1    1    1    1    1
 * 97b41c52301f77ce508f55e66d17620e:    1    1    1    1    1    1
Instagram responded with HTTP error "429 - Too Many Requests". Please
do not run multiple instances of Instaloader in parallel or within
short sequence. Also, do not use any Instagram App while Instaloader
is running.
The request will be retried in 666 seconds, at 13:24.

idk why it's totally unusable (API). If I manually (cmd) get a profile I think it does perfectly download the profile or at least gets the first 100.

For me the same. I can download ~100 images, than wait, than ~100 or less and than I get same table. And the day after my account will be locked. ;)

I've literally downloaded like 10 posts from a profile or something
then I get
JSON Query to api/v1/media/2476648287284918078/info/: HTTP error code 403. [retrying; skip with ^C]
JSON Query to api/v1/media/2476648287284918078/info/: HTTP error code 403. [retrying; skip with ^C]
JSON Query to api/v1/media/2476648287284918078/info/: HTTP error code 403. Unable to fetch high quality image version of <Post CJe0n7VMnc->.
 somfilepath unchanged
HTTP redirect from https://www.instagram.com/graphql/query to https://www.instagram.com/accounts/login/
JSON Query to graphql/query: Redirected to login [retrying; skip with ^C]
Requests within last 10/11/20/22/30/60 minutes grouped by type:
                              other:    1    1    1    1    1    1
                             iphone:    3    3    3    3    3    3
   2b0673e0dc4580674a88d426fe00ea90:    1    1    1    1    1    1
 * 97b41c52301f77ce508f55e66d17620e:    1    1    1    1    1    1
Instagram responded with HTTP error "429 - Too Many Requests". Please
do not run multiple instances of Instaloader in parallel or within
short sequence. Also, do not use any Instagram App while Instaloader
is running.
The request will be retried in 666 seconds, at 13:24.

idk why it's totally unusable (API). If I manually (cmd) get a profile I think it does perfectly download the profile or at least gets the first 100.

For me the same. I can download ~100 images, than wait, than ~100 or less and than I get same table. And the day after my account will be locked. ;)

Is there any workaround for this? I can't download anything because Instagram automatically locks my account after instaloader parses like 4 or 5 accounts.

Is there any workaround for this? I can't download anything because Instagram automatically locks my account after instaloader parses like 4 or 5 accounts.

When using 4.6, 429 gets returned much more often, compared to 4.5.5. Within an hour when using 4.6, 429 gets returned dozens of times, while on 4.5.5 in that same hour, the process goes smoothly without a single error.
I suspect it's because of https://github.com/instaloader/instaloader/pull/712 - now it's making these "more expensive" requests, and hits the rate limit faster. If that's the case, then having an --option to choose what kind of quality to get (and what kind of request to make) could solve this problem.

When using 4.6, 429 gets returned much more often, compared to 4.5.5. Within an hour when using 4.6, 429 gets returned dozens of times, while on 4.5.5 in that same hour, the process goes smoothly without a single error.
I suspect it's because of https://github.com/instaloader/instaloader/pull/712 - now it's making these "more expensive" requests, and hits the rate limit faster. If that's the case, then having an --option to choose what kind of quality to get (and what kind of request to make) could solve this problem.

I would like to have an option to throttle too, hitting 429 result in penalty which need to wait for a really long time lift the punishment.

I would like to have an option to throttle too, hitting 429 result in penalty which need to wait for a really long time lift the punishment.

@aandergr

No, that cannot be the cause here. Instaloader 4.5.3 with the here-used invocation does not call any of the _iphone_struct functions nor does it do any additional higher resolution image url fetch. These high-quality story image fetches (#712) have been introduced later, and first been released in December 2020, more than two months after this issue had been reported. Here are some off-topic comments though, with error messages that must have been caused by entirely different invocations, and not providing not even closely the level of detail that this issue's description has. My comment refers to the original issue.

There are many reasons why instagram limit policy is triggered and cause 429 errors and additional _iphone_struct  requests is one of them. Although it was not introduced when this issue was created it is now one of them and it would be nice to have an option to disable this additional unimportant requests. I've disabled them in the code and it helped me to postpone instagram limit triggering from like 20 accounts to 50 accounts or so.

@aandergr

No, that cannot be the cause here. Instaloader 4.5.3 with the here-used invocation does not call any of the _iphone_struct functions nor does it do any additional higher resolution image url fetch. These high-quality story image fetches (#712) have been introduced later, and first been released in December 2020, more than two months after this issue had been reported. Here are some off-topic comments though, with error messages that must have been caused by entirely different invocations, and not providing not even closely the level of detail that this issue's description has. My comment refers to the original issue.

There are many reasons why instagram limit policy is triggered and cause 429 errors and additional _iphone_struct  requests is one of them. Although it was not introduced when this issue was created it is now one of them and it would be nice to have an option to disable this additional unimportant requests. I've disabled them in the code and it helped me to postpone instagram limit triggering from like 20 accounts to 50 accounts or so.

There are many reasons why instagram limit policy is triggered and cause 429 errors and additional _iphone_struct requests is one of them. Although it was not introduced when this issue was created it is now one of them and it would be nice to have an option to disable this additional unimportant requests. I've disabled them in the code and it helped me to postpone instagram limit triggering from like 20 accounts to 50 accounts or so.

Is it possible to determine what are the causes through logs and disable certain features in the code?

There are many reasons why instagram limit policy is triggered and cause 429 errors and additional _iphone_struct requests is one of them. Although it was not introduced when this issue was created it is now one of them and it would be nice to have an option to disable this additional unimportant requests. I've disabled them in the code and it helped me to postpone instagram limit triggering from like 20 accounts to 50 accounts or so.

Is it possible to determine what are the causes through logs and disable certain features in the code?

I'm now getting a lot of 400 Bad Request Unable to fetch high quality image version of <Post XXXXXXX>, it was downloading correctly for various minutes then out of the blue it started throwing that message for every post now (from multiple profiles), at least now I'm not getting 429 Too Many Requests but having that other error (400) means I'm getting low quality media?

I'm now getting a lot of 400 Bad Request Unable to fetch high quality image version of <Post XXXXXXX>, it was downloading correctly for various minutes then out of the blue it started throwing that message for every post now (from multiple profiles), at least now I'm not getting 429 Too Many Requests but having that other error (400) means I'm getting low quality media?

Well to add I'm starting to get the error with very low connections:
Requests within last 10/11/20/22/30/60 minutes grouped by type:
   d6f4427fbe92d846298cf93df0b937d3:    0    0    0    0    2    2
   f883d95537fbcd400f466f63d42bd8a1:    0    0    0    0    1    1
 *                           iphone:    2    2    4    4    5    5

So is there something buggy with the iPhone API implementation or something? I don't mind having to wait longer to get higher res videos and images but I don't understand why Instagram says to many request when there has been very few.

Well to add I'm starting to get the error with very low connections:
Requests within last 10/11/20/22/30/60 minutes grouped by type:
   d6f4427fbe92d846298cf93df0b937d3:    0    0    0    0    2    2
   f883d95537fbcd400f466f63d42bd8a1:    0    0    0    0    1    1
 *                           iphone:    2    2    4    4    5    5

So is there something buggy with the iPhone API implementation or something? I don't mind having to wait longer to get higher res videos and images but I don't understand why Instagram says to many request when there has been very few.

@ryandtw I guess the problem you reported has resolved in the meantime?

@ryandtw I guess the problem you reported has resolved in the meantime?

@aandergr This is not fixed at all, many of us are having this problem, just read the comments here...

@aandergr This is not fixed at all, many of us are having this problem, just read the comments here...

If you close the issue and make a bot that automatically ignore and close issues the problems wont disappear. Some developers just hate open tickets and I don't know why, the lack of open tickets won't make software better.

If you close the issue and make a bot that automatically ignore and close issues the problems wont disappear. Some developers just hate open tickets and I don't know why, the lack of open tickets won't make software better.

Is there a way to only get the followers of a certain account? Biography would also be useful but not a must. I think Instaloader is not the right way to do this. I want to go through certain celebrities' followers to find like-minded people (that, for example, also follow Tony Robbins and have the same area in their biography like I do.
The only way I see right now is building the thing from scratch on my own with selenium. Already got to the followers page. Next steps are grabbing the names of the followers (and take care of the "infinite scrolling" problem).
Any thoughts on that?

hello
I solved with set proxy
Enviroment variables
export HTTP_PROXY="http://...:8080"
export HTTPS_PROXY="http://...:8080"

authors: AndCycle ConfitureCheung DeathWithKebab Dimianovic LaticePrime LouisVA MassihEydavi Shadowsrik Terrobility VasiliPupkin256 aandergr fbck gujas ikonia jlntrt jqdoumen parasiteoflife peterkaragyozov pjw91 plcdnl ryandtw somera

repo: instaloader/instaloader


text:
feat: centralize wrapping of component execution

Because

Every component repeats the same wrapping. This is an opportunity to remove duplication and also concerns from the individual components (they shouldn't care about the wrapping, only about the core business logic in each component).
Context: pipeline-backend needs to pass and later access the ID of the component that's being executed (i.e. the component ID within the recipe) for the logging feature. This requires modifying the store.CreateExecution signature, so I'm taking the opportunity to clean up a bit.

This commit

Modifies the CreateExecution signature to return an interface, not a wrapper implementation.
Wraps the execution in a single place (store.CreateExecution).

@chuang8511 let me know what you think about the changes in the base and store packages. cc @donch1989

@chuang8511 let me know what you think about the changes in the base and store packages. cc @donch1989

Yeah, the original wrapper is somewhat counter-intuitive and hard to understand. I'm looking forward to this change.

QA
Tested on https://github.com/instill-ai/pipeline-backend/pull/577#issuecomment-2258740713

lgtm

LGTM! Just write my thoughts as a record.
In the long-term future, when we start to consider failover in the perspective of component, the execution seems to be instance. So, execution will need its ID as well.
(Relationship between component & execution is component ||-|< execution)
I guess it is a long term future.
When we decide to do failover system, we will need to reconsider how to deal with failover feature.
The current design seems to have the extensibility in this point of view.
note: not sure if failover is a good word.

execution will need its ID as well

The way we discussed it for the logging feature was that the pipeline trigger ID + the component ID form a unique key, which was enough for this feature. That might be an option for failover, assigning an Execution ID is also valid.
Thanks for the reviews 💞 I'll proceed with the merge

source: gharchive/pull-request

repo: instill-ai/component

license: MIT

license_type: permissive

license_source: github-api


text:
Problems with executing migrations

composer install
You are running composer with xdebug enabled. This has a major impact on runtime performance. See https://getcomposer.org/xdebug
Warning: This development build of composer is over 60 days old. It is recommended to update it by running "/usr/bin/composer self-update" to get the latest version.
Loading composer repositories with package information
Installing dependencies (including require-dev) from lock file
Warning: The lock file is not up to date with the latest changes in composer.json. You may be getting outdated dependencies. Run update to update them.
  - Installing doctrine/common (2.2.3)
    Loading from cache

  - Installing symfony/yaml (v2.8.7)
    Loading from cache

  - Installing symfony/polyfill-mbstring (v1.2.0)
    Loading from cache

  - Installing symfony/console (v2.8.7)
    Loading from cache

  - Installing zendframework/zend-eventmanager (3.0.1)
    Loading from cache

  - Installing zendframework/zend-code (2.6.3)
    Loading from cache

  - Installing ocramius/proxy-manager (1.0.2)
    Loading from cache

  - Installing doctrine/dbal (2.2.2)
    Loading from cache

  - Installing doctrine/migrations (dev-master 93a4458)
    Cloning 93a4458195aaf65a84b3d8b5a98b89149ef49776

  - Installing incenteev/composer-parameter-handler (v2.1.2)
    Loading from cache

  - Installing symfony/routing (v3.0.7)
    Loading from cache

  - Installing ircmaxell/password-compat (v1.0.4)
    Loading from cache

  - Installing symfony/polyfill-php55 (v1.2.0)
    Loading from cache

  - Installing symfony/polyfill-php54 (v1.2.0)
    Loading from cache

  - Installing symfony/http-foundation (v2.8.7)
    Loading from cache

  - Installing symfony/event-dispatcher (v2.8.7)
    Loading from cache

  - Installing psr/log (1.0.0)
    Loading from cache

  - Installing symfony/debug (v2.8.7)
    Loading from cache

  - Installing symfony/http-kernel (v2.8.7)
    Loading from cache

  - Installing pimple/pimple (v1.1.1)
    Loading from cache

  - Installing silex/silex (v1.3.5)
    Loading from cache

  - Installing swiftmailer/swiftmailer (v4.1.8)
    Loading from cache

  - Installing symfony/process (v2.8.7)
    Loading from cache

  - Installing paragonie/random_compat (v1.4.1)
    Loading from cache

  - Installing symfony/security (v2.6.13)
    Loading from cache

  - Installing twig/twig (v1.24.1)
    Loading from cache

  - Installing symfony/twig-bridge (v2.8.7)
    Loading from cache

zendframework/zend-eventmanager suggests installing container-interop/container-interop (^1.1.0, to use the lazy listeners feature)
zendframework/zend-eventmanager suggests installing zendframework/zend-stdlib (^2.7.3 || ^3.0, to use the FilterChain feature)
zendframework/zend-code suggests installing doctrine/annotations (Doctrine\Common\Annotations >=1.0 for annotation features)
zendframework/zend-code suggests installing zendframework/zend-stdlib (Zend\Stdlib component)
ocramius/proxy-manager suggests installing ocramius/generated-hydrator (To have very fast object to array to object conversion for ghost objects)
ocramius/proxy-manager suggests installing zendframework/zend-json (To have the JsonRpc adapter (Remote Object feature))
ocramius/proxy-manager suggests installing zendframework/zend-soap (To have the Soap adapter (Remote Object feature))
ocramius/proxy-manager suggests installing zendframework/zend-stdlib (To use the hydrator proxy)
ocramius/proxy-manager suggests installing zendframework/zend-xmlrpc (To have the XmlRpc adapter (Remote Object feature))
doctrine/migrations suggests installing jdorn/sql-formatter (Allows to generate formatted SQL with the diff command.)
symfony/routing suggests installing doctrine/annotations (For using the annotation loader)
symfony/routing suggests installing symfony/config (For using the all-in-one router or any loader)
symfony/routing suggests installing symfony/dependency-injection (For loading routes from a service)
symfony/routing suggests installing symfony/expression-language (For using expression matching)
symfony/event-dispatcher suggests installing symfony/dependency-injection ()
symfony/http-kernel suggests installing symfony/browser-kit ()
symfony/http-kernel suggests installing symfony/class-loader ()
symfony/http-kernel suggests installing symfony/config ()
symfony/http-kernel suggests installing symfony/dependency-injection ()
symfony/http-kernel suggests installing symfony/finder ()
symfony/http-kernel suggests installing symfony/var-dumper ()
paragonie/random_compat suggests installing ext-libsodium (Provides a modern crypto API that can be used to generate random bytes.)
symfony/security suggests installing symfony/class-loader (For using the ACL generateSql script)
symfony/security suggests installing symfony/expression-language (For using the expression voter)
symfony/security suggests installing symfony/finder (For using the ACL generateSql script)
symfony/security suggests installing symfony/validator (For using the user password constraint)
symfony/twig-bridge suggests installing symfony/asset (For using the AssetExtension)
symfony/twig-bridge suggests installing symfony/expression-language (For using the ExpressionExtension)
symfony/twig-bridge suggests installing symfony/finder ()
symfony/twig-bridge suggests installing symfony/form (For using the FormExtension)
symfony/twig-bridge suggests installing symfony/stopwatch (For using the StopwatchExtension)
symfony/twig-bridge suggests installing symfony/templating (For using the TwigEngine)
symfony/twig-bridge suggests installing symfony/translation (For using the TranslationExtension)
symfony/twig-bridge suggests installing symfony/var-dumper (For using the DumpExtension)
Generating autoload files
> Incenteev\ParameterHandler\ScriptHandler::buildParameters
Updating the "config/parameters.yml" file

./console migrations:migrate
[20-Jun-2016 19:28:50 Europe/Moscow] PHP Fatal error:  Class 'Kurl\Silex\Provider\DoctrineMigrationsProvider' not found in /var/tmp/pinboard/console on line 17
[20-Jun-2016 19:28:50 Europe/Moscow] PHP Stack trace:
[20-Jun-2016 19:28:50 Europe/Moscow] PHP   1. {main}() /var/tmp/pinboard/console:0

grep -r DoctrineMigrationsProvider ./
./console:    new \Kurl\Silex\Provider\DoctrineMigrationsProvider($console),

grep -r silex-doctrine-migrations-provider ./
./composer.json:        "kurl/silex-doctrine-migrations-provider": "~0.1",
./vendor/doctrine/migrations/README.md:  * [Silex](https://packagist.org/packages/kurl/silex-doctrine-migrations-provider)

May be problem in composer.lock as we see above:
Warning: The lock file is not up to date with the latest changes in composer.json. You may be getting outdated dependencies. Run update to update them.

ls -la vendor
total 68
drwxrwxr-x 16 lebnik lebnik 4096 июня  20 19:28 .
drwxrwxr-x  8 lebnik lebnik 4096 июня  20 19:32 ..
-rw-rw-r--  1 lebnik lebnik  183 июня  20 19:28 autoload.php
drwxrwxr-x  2 lebnik lebnik 4096 июня  20 19:28 bin
drwxrwxr-x  2 lebnik lebnik 4096 июня  20 19:28 composer
drwxrwxr-x  5 lebnik lebnik 4096 июня  20 19:28 doctrine
drwxrwxr-x  3 lebnik lebnik 4096 июня  20 19:28 incenteev
drwxrwxr-x  3 lebnik lebnik 4096 июня  20 19:28 ircmaxell
drwxrwxr-x  3 lebnik lebnik 4096 июня  20 19:28 ocramius
drwxrwxr-x  3 lebnik lebnik 4096 июня  20 19:28 paragonie
drwxrwxr-x  3 lebnik lebnik 4096 июня  20 19:28 pimple
drwxrwxr-x  3 lebnik lebnik 4096 июня  20 19:28 psr
drwxrwxr-x  3 lebnik lebnik 4096 июня  20 19:28 silex
drwxrwxr-x  3 lebnik lebnik 4096 июня  20 19:28 swiftmailer
drwxrwxr-x 15 lebnik lebnik 4096 июня  20 19:28 symfony
drwxrwxr-x  3 lebnik lebnik 4096 июня  20 19:28 twig
drwxrwxr-x  4 lebnik lebnik 4096 июня  20 19:28 zendframework

pinboard v1.5.2
I think you need to delete /composer.lock from .gitignore and than execute the command:
composer update kurl/silex-doctrine-migrations-provider doctrine/migrations

Because ignore composer.lock it very bad practice.

It is very bad practice https://github.com/symfony/symfony/blob/master/.gitignore#L2 ? :)

As far as I know, when you installing the symfony is used the symfony/symfony-standard and file https://github.com/symfony/symfony-standard/blob/master/composer.lock

Thanks! I will add lock-file in nearest version.

source: gharchive/issue

authors: muxx yapro

repo: intaro/pinboard

license: mit

license_source: bigquery


text:
fix #397 refactor distributed shell

Ideally, I think only 3 files are needed.
Client, AppMaster, and Executor.
All other definition can be put in companion object of these three.

Now the class RegisterExecutor is in org.apache.gearpump.streaming package, so for other applications is it needed?

Hi Huafeng,
Other app should define its own RegisterExecutor if they need it.

+1

Please rebase.

authors: clockfly huafengw

repo: intel-hadoop/gearpump


text:
Mraa ISR time-out in Python

Is similar functionality possible like pulseIn on Arduino?
pulseIn(pin, value, timeout)
I wan't to use an interrupt but with a time-out of a given amount, let's say 0.5 seconds.
Relevant:
gpio-interrupt-isr
hello_isr.py

No there's nothing like this, the problem is that we're on Linux so you simply can't make assumptions about timings this way.

As long as @arfoll has provided an answer, I'm closing this one

authors: BTWS alext-mkrs arfoll

repo: intel-iot-devkit/mraa


text:
k8s.io 1.28.1 update and SGX rework

Fixes: #1304
The goal is to rework the deployments so that sgx* do not use hostNetwork: true to make IAS scanners happier.

Codecov Report

Merging #1513 (7529944) into main (eab8c68) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 7529944 differs from pull request most recent head c322f2b. Consider uploading reports for the commit c322f2b to get more accurate results

@@           Coverage Diff           @@
##             main    #1513   +/-   ##
=======================================
  Coverage   50.04%   50.04%
=======================================
  Files          43       43
  Lines        4884     4884
=======================================
  Hits         2444     2444
  Misses       2301     2301
  Partials      139      139

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

@hj-johannes-lee ptal

authors: codecov-commenter mythi


text:
device_plugins: Added README for QAT

Added QAT documentation.
Signed-off-by: chaitanya1731 chaitanya.kulkarni@intel.com

LGTM

The PR looks good to me. We can continue to add more content to clarify the device plugin parameters later.

authors: chaitanya1731 hershpa uMartinXu


text:
error: ‘PyArray_Descr’ has no member named ‘elsize’

pytorch<2.3.0 doesn't support numpy 2.0 so you may experience the issue when running ./scripts/test-triton.sh --venv --tutorial.

many thanks!

authors: YarShev dimitriHao

repo: intel/intel-xpu-backend-for-triton


text:
Logistic linear model trouble

I know this isn't strictly about the code in this repo, but it's been driving me insane.
Whenever I try to build a model via train-ml-bot.py or nova-train.py by using an ml bot with an existing model (be it from a rand bot, or an alphabeta bot, or whatever) I get this error just as it finishes the last game:
Traceback (most recent call last):
File "nova-train.py", line 203, in
main()
File "nova-train.py", line 66, in main
generate_model(data, target)
File "nova-train.py", line 74, in generate_model
model = learner.fit(data, target)
File "/Users/paul/anaconda/lib/python2.7/site-packages/sklearn/linear_model/logistic.py", line 1186, in fit
sample_weight=sample_weight)
File "/Users/paul/anaconda/lib/python2.7/site-packages/sklearn/svm/base.py", line 875, in fit_liblinear
" class: %r" % classes[0])
ValueError: This solver needs samples of at least 2 classes in the data, but the data contains only one class: 'lost'

This is a known problem; the bots are too passive and don't move, therefore they reach the max limits and only lose. @pbloem answered this question in the BlackBoard discussion forum.

Thanks a lot

authors: CorralPeltzer PaulUrsulean

repo: intelligent-systems-course/planet-wars


text:
Documentation - RepetSim has code for Repet

The two examples on the RepetSim class page mistakenly duplicates the code from the Repet class.
Both instances of
# Set up a Repet object
repet = nussl.Repet(signal)

(under get_similarity_matrix() and make_audio_signals()) should read
# Set up a Repet object
repet = nussl.RepetSim(signal)

Yeah, looks like the documentation needs to be beefed up for RepetSim

authors: ethman tuchandra

repo: interactiveaudiolab/nussl


text:
add curl_easy_getinfo

It's not fully tested but virtually works as the curl_easy_setopt.
Accordingly with the docs, the curl_easy_setopt:

Request internal information from the curl session with this function. The third argument MUST be a pointer to a long, a pointer to a char *, a pointer to a struct curl_slist *, or a pointer to a double.

So I have included a double (real(kind = 8)) version of the Fortran interface and the respective new constants.
I'm not sure but I bumped the MINOR version since it adds new functionality, but is backward compatible.
PS: context -> I'm creating a higher-level library called fortran-requests (just like python's requests module)

Thank you. Some corrections were necessary, but should work now. I’ve added an example getinfo.

The Fortran interfaces are indeed way better now, thank you.

repo: interkosmos/fortran-curl

license: ISC


text:
feat: optional console log message filter

Resolves https://github.com/internet-computer-protocol/evm-rpc-canister/issues/201 by adding an optional consoleFilter install arg.
Show all log messages (default):
dfx deploy evm_rpc --argument "(record { consoleFilter = opt variant { ShowAll } })"

Hide all log messages:
dfx deploy evm_rpc --argument "(record { consoleFilter = opt variant { HideAll } })"

Only show INFO ... messages:
dfx deploy evm_rpc --argument "(record { consoleFilter = opt variant { ShowPattern = "^INFO" } })"

Hide TRACE_HTTP ... messages:
dfx deploy evm_rpc --argument "(record { consoleFilter = opt variant { HidePattern = "^TRACE_HTTP" } })"

Only show messages related to eth_getLogs:
dfx deploy evm_rpc --argument "(record { consoleFilter = opt variant { ShowPattern = "eth_getLogs" } })"

Note that ShowPattern and HidePattern accept regular expressions and are evaluated using the regex crate.

We should make sure this is properly documented with a new release. Do we expect projects that deploy their own evm rpc canister to only deploy the latest release as well?

We should make sure this is properly documented with a new release.

For sure. I'll work with @gregorydemay and @jessiemongeon1 on making sure the documentation is updated for the new changes.

Do we expect projects that deploy their own evm rpc canister to only deploy the latest release as well?

We could recommend this, although the previous version should continue working as well.

We can recommend this, although the previous version should continue working as well.

what about deploying main?

If I understand the question correctly, this is a work in progress since it requires an NNS proposal. We also want to give a window of time for developers to migrate to the new version before redeploying.

Documentation PR: https://github.com/dfinity/portal/pull/3575

what i meant was should we advise projects not to deploy from main, but only from releases instead :)

Haha, okay, I see what you're saying. Yes, that is what we should recommend.

authors: letmejustputthishere rvanasa


text:
Access to BLE classes

I'm working on a windows desktop application that needs to communicate with BLE devices.  For various reasons it can't be UWP.  I can see the BLE classes in the folder structure, but not in any of the csproj files.  This brings up a couple of questions.

What csproj should they be added into, assuming they don't get their own csproj?
What versions of Windows do these classes support?

Thanks.

The Bluetooth LE functionality is now in its own dedicated library - InTheHand.BluetoothLE which is on NuGet and inside a separate project in the source code. You can use the Windows APIs from .NET Framework desktop apps. A .NET Core build will be available shortly.

authors: gberkheiser peterfoot


text:
[Bug]: {{selected_code}}, {{active_editor_file_url}} and similar template arguments don't work as described

Before Reporting

[X] I have checked FAQ, and there is no solution to my issue
[X] I have searched the existing issues, and there is no existing issue for my issue

What happened?
I'm trying to use the {{selected_code}} and {{active_editor_file_url}} template arguments, but they are not being replaced by the actual values as expected when I run commands in the chat window.
Perhaps I'm trying this in an unexpected way?
How to reproduce the bug.
Open plugin chat window, type "/run echo {{selected_code}}"
Expected output:

echo of whatever is currently highlighted in my Xcode editor window

Actual output:
{{selected code}}
Relevant log output
N/A

macOS version
13.4.1
Xcode version
14.1
Copilot for Xcode version
0.20.0(200)
Node version
16.19.0

This works if you set it up as a custom command.

It currently only works for custom commands. Do you think it should be supported for sending messages as well?

Well perhaps my issue is strictly with custom commands then 😅
I started by trying to use this from a custom command, but I couldn't get that to actually be run. I created a similar test command as what you showed @KieranConlon, closed and re-opened Xcode, but then couldn't figure out how to actually execute it. What exactly did you do in the chat window to execute that command? :)

It's available from the Xcode > Editor > Copilot menu and the context menu of the circular widget.

Ah nice, got it working, thank you!
I'll close this issue out, I'd suggest making it more clear how to use custom commands, since the steps shared here I was definitely not able to intuit from the material available thus far 👍

authors: KieranConlon coolbnjmn intitni

repo: intitni/CopilotForXcode


text:
🛑 Het Markiezenhof is down

In 52fb3c8, Het Markiezenhof (https://www.markiezenhof.nl) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Het Markiezenhof is back up in 0f3425c after 26 minutes.

repo: intk/intk-upptime


text:
This fixes event clicks/double clicks

Currently, event clicks can't be clicked on the master branch, because the onClick event is passed on a react component (NoopWrapper) and not a Dom element
https://github.com/intljusticemission/react-big-calendar/blob/master/src/DayColumn.js#L198
This PR propagates the onClick and onDoubleClick to the containing div element, so that clicks on events work again.

thanks!

authors: SudoPlz jquense

repo: intljusticemission/react-big-calendar


text:
UI upload files view

Package version (if known): RDM 6.2
Describe the bug
Files can not be uploaded using the UI upload form. Using the REST API the files can be uploaded.
Records can not be published. Publish button is enabled, can be clicked but it does not publish the record.
Steps to Reproduce
The system is Red Hat Enterprise Linux Server release 7.9 (Maipo)
I am using python3.6.
The installation follows the local installation, there is an issue where the environment and installation is shown

@cfgamboa Can you paste the console messages you get when performing a UI upload? i.e. the browser's console tab will probably list some things and having a look at them might elucidate this.

Ok, I found the culprit of this behavior, the
SITE_UI_URL
and
SITE_API_URL

Need to use the actual user enable URL. IF set to the local hostname the UI deposit form does not work as mentioned on this  issue.

authors: cfgamboa fenekku

repo: inveniosoftware/invenio-app-rdm


text:
add file_id to json schema

(Closes #68)

I agree with Vlad, I don't see any breaking changes with this modification.

authors: ntarocco vladbmihaescu

repo: inveniosoftware/invenio-records-files


text:
cli: vocabulary convert

Implement a command to convert/process the content of a vocabulary. This would be useful to process big files, that are in other formats, contain many unused fields, etc.
invenio vocabularies convert <vocabulary> <orig_file_path> <dst_file_path>

in names branch, merge to master https://github.com/inveniosoftware/invenio-rdm-records/issues/831

repo: inveniosoftware/invenio-vocabularies


text:
Improve "tabs" displayed on various pages

Some pages (e.g. Part view) are getting a lot of tabs which are becoming cumbersome to display.
A better idea is to display them on the side of the page, as icons with optional expandable text.
For example OpenProject:

Also could overlay the "badge" to the icon, much like the old email counter for gmail (e.g.)

https://bootstrapious.com/p/bootstrap-sidebar

repo: inventree/InvenTree


text:
Default system time

Hi there,
Can I change the default system time zone of my inventree system? When I export the stock item tracking imformation, the default time zone is GMT. If I want to change to other time zone, what can I do?

Change the "timezone" option in config.yaml file
https://inventree.readthedocs.io/en/latest/start/config/

Thank you!!!


text:
[FR] maintenance page should return 503

Currently the "site is down for maintenance" page returns 200 status code. Ideally it should return 503
https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/503

Looks like this is a quirk of the demo server, not of the InvenTree software itself.


text:
ValueError: The class sequence '{example.classes[i]}' did not start on a token boundary

Hi guys,
Thanks for hosting this great competition! During one of my experiments, I ran into the following two errors:
ValueError                                Traceback (most recent call last)
[/usr/local/lib/python3.7/dist-packages/eval_pipeline/models.py](https://localhost:8080/#) in _evaluate_classification(self, examples)
    470                 try:
--> 471                     token_index = text_offset.index(text_index)
    472                 except ValueError as e:

ValueError: 537 is not in list

followed by
ValueError: The class sequence '{example.classes[i]}' did not start on a token boundary

It has previously worked with other datasets, so I am at a loss for why it breaks? If anyone could help that'd be greatly appreciated :))

Hi!
That line was missing an f-string, which I've added now, so it should tell you which class is causing the issue. This error occurs when the "answer" part of the prompt isn't separated from the "question" part properly; i.e. they aren't separated by a full token. This usually happens when there's no space at the start of the class sequence, since most tokens start with a space.
If you run the script again now you should see the class that's causing the issue in the error message.

Ok, now the code throws:
    472                 except ValueError as e:
    473                     raise ValueError(
--> 474                         f"The class sequence '{example.classes[i]}' did not start on a token boundary"
    475                     )
    476                 class_logprob = 0

IndexError: list index out of range

which is a bit unexpected - I will keep on digging and let you know what I find :))

Ok, I solved it: apparently, the questions had different number of options which caused the index error. I solved it by making them all have the same number of options.

authors: Rysias naimenz

repo: inverse-scaling/prize


text:
Doesn't Work on Flutter Beta Channel

Sample function compiles fine on stable channel but throws error on beta channel. I am assuming this should be fixed before it reaches stable.
flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel beta, 3.13.0-0.2.pre, on macOS 13.4 22F66 darwin-arm64, locale en-TR)

⠹ Compiling 1 functions... (1.8s)Compilation of the Dart entry file failed:

../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/fetch.dart:377:55:
Warning: Initializers for parameters are ignored on static interop external functions.
  external static Response redirect(String url, [int? status = 302]);
                                                      ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/dom.dart:1835:36:
Warning: Initializers for parameters are ignored on static interop external functions.
  external factory Text._([String? data = '']);
                                   ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/dom.dart:1992:39:
Warning: Initializers for parameters are ignored on static interop external functions.
  external factory Comment._([String? data = '']);
                                      ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/css_typed_om_1.dart:1173:16:
Warning: Initializers for parameters are ignored on static interop external functions.
      [dynamic alpha = 1]);
               ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/css_typed_om_1.dart:1205:16:
Warning: Initializers for parameters are ignored on static interop external functions.
      [dynamic alpha = 1]);
               ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/css_typed_om_1.dart:1237:16:
Warning: Initializers for parameters are ignored on static interop external functions.
      [dynamic alpha = 1]);
               ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/css_typed_om_1.dart:1270:16:
Warning: Initializers for parameters are ignored on static interop external functions.
      [dynamic alpha = 1]);
               ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/css_typed_om_1.dart:1302:16:
Warning: Initializers for parameters are ignored on static interop external functions.
      [dynamic alpha = 1]);
               ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/css_typed_om_1.dart:1334:16:
Warning: Initializers for parameters are ignored on static interop external functions.
      [dynamic alpha = 1]);
               ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/css_typed_om_1.dart:1366:16:
Warning: Initializers for parameters are ignored on static interop external functions.
      [dynamic alpha = 1]);
               ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/css_typed_om_1.dart:1398:16:
Warning: Initializers for parameters are ignored on static interop external functions.
      [dynamic alpha = 1]);
               ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/encoding.dart:80:16:
Warning: Initializers for parameters are ignored on static interop external functions.
      [String? label = 'utf-8', TextDecoderOptions? options]);
               ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/encoding.dart:147:16:
Warning: Initializers for parameters are ignored on static interop external functions.
      [String? label = 'utf-8', TextDecoderOptions? options]);
               ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/webrtc.dart:2200:59:
Warning: Initializers for parameters are ignored on static interop external functions.
  external factory RTCError._(RTCErrorInit init, [String? message = '']);
                                                          ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/webidl.dart:26:16:
Warning: Initializers for parameters are ignored on static interop external functions.
      [String? message = '', String? name = 'Error']);
               ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/webidl.dart:26:38:
Warning: Initializers for parameters are ignored on static interop external functions.
      [String? message = '', String? name = 'Error']);
                                     ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/geometry_1.dart:43:35:
Warning: Initializers for parameters are ignored on static interop external functions.
      [/* double | NaN */ dynamic x = 0,
                                  ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/geometry_1.dart:44:34:
Warning: Initializers for parameters are ignored on static interop external functions.
      /* double | NaN */ dynamic y = 0,
                                 ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/geometry_1.dart:45:34:
Warning: Initializers for parameters are ignored on static interop external functions.
      /* double | NaN */ dynamic z = 0,
                                 ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/geometry_1.dart:46:34:
Warning: Initializers for parameters are ignored on static interop external functions.
      /* double | NaN */ dynamic w = 1]);
                                 ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/geometry_1.dart:93:35:
Warning: Initializers for parameters are ignored on static interop external functions.
      [/* double | NaN */ dynamic x = 0,
                                  ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/geometry_1.dart:94:34:
Warning: Initializers for parameters are ignored on static interop external functions.
      /* double | NaN */ dynamic y = 0,
                                 ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/geometry_1.dart:95:34:
Warning: Initializers for parameters are ignored on static interop external functions.
      /* double | NaN */ dynamic z = 0,
                                 ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/geometry_1.dart:96:34:
Warning: Initializers for parameters are ignored on static interop external functions.
      /* double | NaN */ dynamic w = 1]);
                                 ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/geometry_1.dart:175:35:
Warning: Initializers for parameters are ignored on static interop external functions.
      [/* double | NaN */ dynamic x = 0,
                                  ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/geometry_1.dart:176:34:
Warning: Initializers for parameters are ignored on static interop external functions.
      /* double | NaN */ dynamic y = 0,
                                 ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/geometry_1.dart:177:34:
Warning: Initializers for parameters are ignored on static interop external functions.
      /* double | NaN */ dynamic width = 0,
                                 ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/geometry_1.dart:178:34:
Warning: Initializers for parameters are ignored on static interop external functions.
      /* double | NaN */ dynamic height = 0]);
                                 ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/geometry_1.dart:224:35:
Warning: Initializers for parameters are ignored on static interop external functions.
      [/* double | NaN */ dynamic x = 0,
                                  ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/geometry_1.dart:225:34:
Warning: Initializers for parameters are ignored on static interop external functions.
      /* double | NaN */ dynamic y = 0,
                                 ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/geometry_1.dart:226:34:
Warning: Initializers for parameters are ignored on static interop external functions.
      /* double | NaN */ dynamic width = 0,
                                 ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/geometry_1.dart:227:34:
Warning: Initializers for parameters are ignored on static interop external functions.
      /* double | NaN */ dynamic height = 0]);
                                 ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/compute_pressure.dart:77:48:
Error: External extension members with the keyword 'static' on JS interop and @Native types are disallowed.
  external static Iterable<PressureSource> get supportedSources;
                                               ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/performance_timeline.dart:66:40:
Error: External extension members with the keyword 'static' on JS interop and @Native types are disallowed.
  external static Iterable<String> get supportedEntryTypes;
                                       ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/mediacapture_streams.dart:767:16:
Warning: Initializers for parameters are ignored on static interop external functions.
      [String? message = '']);
               ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/notifications.dart:50:46:
Error: External extension members with the keyword 'static' on JS interop and @Native types are disallowed.
  external static NotificationPermission get permission;
                                             ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/notifications.dart:52:27:
Error: External extension members with the keyword 'static' on JS interop and @Native types are disallowed.
  external static int get maxActions;
                          ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/websockets.dart:48:53:
Warning: Initializers for parameters are ignored on static interop external functions.
  external factory WebSocket._(String url, [dynamic protocols = const []]);
                                                    ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/push_api.dart:47:40:
Error: External extension members with the keyword 'static' on JS interop and @Native types are disallowed.
  external static Iterable<String> get supportedContentEncodings;
                                       ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/webusb.dart:210:13:
Warning: Initializers for parameters are ignored on static interop external functions.
      [int? bytesWritten = 0]);
            ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/webusb.dart:288:13:
Warning: Initializers for parameters are ignored on static interop external functions.
      [int? bytesWritten = 0]);
            ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/media_source_2.dart:101:28:
Error: External extension members with the keyword 'static' on JS interop and @Native types are disallowed.
  external static bool get canConstructInDedicatedWorker;
                           ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/indexeddb_3.dart:597:64:
Warning: Initializers for parameters are ignored on static interop external functions.
  external static IDBKeyRange lowerBound(dynamic lower, [bool? open = false]);
                                                               ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/indexeddb_3.dart:598:64:
Warning: Initializers for parameters are ignored on static interop external functions.
  external static IDBKeyRange upperBound(dynamic upper, [bool? open = false]);
                                                               ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/indexeddb_3.dart:600:14:
Warning: Initializers for parameters are ignored on static interop external functions.
      [bool? lowerOpen = false, bool? upperOpen = false]);
             ^
../../../../.pub-cache/hosted/pub.dev/js_bindings-0.1.2+2/lib/bindings/indexeddb_3.dart:600:39:
Warning: Initializers for parameters are ignored on static interop external functions.
      [bool? lowerOpen = false, bool? upperOpen = false]);
                                      ^
Error: Compilation failed.

The same issue on the stable channel now.
#### General info

- Dart 3.1.0 (stable) (Tue Aug 15 21:33:36 2023 +0000) on "macos_arm64"
- on macos / Version 13.5 (Build 22G74)
- locale is en-UA

The same issue on the stable channel: Flutter 3.13.0 • channel stable •

What was the last version you guys had this working?
Currently having this issue on stable as well :(

What was the last version you guys had this working?

I have a working project based on Dart 3.0.1 && edge 0.0.6+1, maybe you can check from that point.

Hey all this is due to changes in the js interop layer, which I think is so the interop code can compile to wasm.
We recently applied fixes to Zapp which had the same errors. I'll take a look at the fixes there and apply those (on Monday)

Can someone please confirm if this is now working?

@TC3000 Still not working :(

Temporary workaround is to use fvm with previous version.
fvm use 3.7.12 -f
then run edge via fvm dart run edge build supabase_functions --dev

Temporary workaround is to use fvm with previous version.
fvm use 3.7.12 -f
then run edge via fvm dart run edge build supabase_functions --dev

Same error using this

Any workarounds please?

Any workarounds please?


text:
Fix Safari performance issues with Gallery

Fixes #1004
Testing determined the cause of performance issue to be nested CSS grids.
Redid layout using flexbox, except for the on-hover image action buttons in gallery, as in testing leaving this as grid had zero hit on performance and it was easy to retain exactly the previous layout.

I'm testing a bit more, but seems to work like a charm 👍

repo: invoke-ai/InvokeAI


text:
🛑 Bitwage API (Sandbox) is down

In d3e7978, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 352 ms

Resolved: Bitwage API (Sandbox) is back up in f37cab2 after 52 minutes.


text:
🛑 Bitwage API (Sandbox) is down

In c801cc7, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 282 ms

Resolved: Bitwage API (Sandbox) is back up in f43529e after 29 minutes.


text:
🛑 Bitwage API (Sandbox) is down

In c7182d1, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 97 ms

Resolved: Bitwage API (Sandbox) is back up in 805ceeb after 22 minutes.


text:
🛑 Bitwage API (Sandbox) is down

In a820d05, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 63 ms

Resolved: Bitwage API (Sandbox) is back up in 2f59e9d after 1 hour, 20 minutes.


text:
Bump hue

Closes https://github.com/iobroker-community-adapters/ioBroker.hue/issues/115

RE-CHECK!

Automated adapter checker
ioBroker.hue

:thumbsup: No errors found
Add comment "RE-CHECK!" to start check anew


text:
vis-2-beta versteckte Felder

Wenn man versteckte Felder im Widget verwendet und dann mehrere Widgets selektiert hat, bekommt man beim Start die Fehlermeldung (im Chrome Developertool): "Cannot execute hidden on "true"..." (siehe Screenshot):

Ich denke, es liegt an der Codestelle:
    const isHidden = [];
    for (let i = 0; i < selectedWidgets.length; i++) {
        const data = project[selectedView].widgets[selectedWidgets].data;
        const style = project[selectedView].widgets[selectedWidgets].style;

Diese müsste m.E. geändert werden in:
    const isHidden = [];
    for (let i = 0; i < selectedWidgets.length; i++) {
        const data = project[selectedView].widgets[selectedWidgets[i].data;
        const style = project[selectedView].widgets[selectedWidgets[i].style;

@formifan2002 Please check with 2.0.24

OK, many thanks for the feedback. On npm I only find the version 2.0.23. By when will you distribute the new version?

Works perfect with 2.0.24 !


text:
...filtered out, because does not belongs to specified time interval

Hi, iCal stopped displaying calendar entries a few days ago. When I increase the log level I see that events are read in, but behind each line is: "...filtered out, because does not belongs to specified time interval". That happens to old and upcoming dates.
Any idea hot to fix that?

The last two lines in the log are:
ical.0 (1977) displaying dates because of callback
ical.0 (1977) Terminated (NO_ERROR): Without reason

Installed today the iCal adapter, connected to gmail-calendar for the trash. Connection from ioBroker to gmail-calendar is successfully and starts reading data. Could see this in log file in debug-mode. Breaks with error message "does not belongs to specified time interval".
Seems to be same problem as user mdn-united has. Can somebody help with this?

Hello, same issue in my system.
First start works fine and then: (14585) Terminated (NO_ERROR): Without reason

Hi,
same problem here: Trash-Calendar with "whole-day" events: all events are filtered out.


text:
Using TZID without Luxon available is unsupported.

https://github.com/iobroker-community-adapters/ioBroker.ical/issues/325
It's back again...
v1.13.0
js 4.0.23
node v14.19.2
Thank you

Seems like the errors wasn't fixed: https://github.com/jakubroztocil/rrule/issues/501#issuecomment-1146503580

@klein0r Thats why rrule downgrade again :-)

@Apollon77 Downgrade to which version? 1.13.0 contains "rrule": "2.6.9"

Ahh ok, then I missed that :-)) e should just make sure not to upgrade rrule :-)

I have rrule 2.6.4 and I also have this issue. It is even that extreme that after one day kern.log and syslog get that big (in my case 11+ GB) until the disk is full and everything stops working until I flush the logs.

Is there anything we can do to hotfix this. I see Alexa adapter using a newer version of rrule. I am not to deep into npm/nodejs. Would it fix to change the dependencies of the contained package.json? Rrule is set to static 2.6.9. Which version would work without this issues. If I got it right whether ^ in front of the verions to follow master versions update wise or specifying the correct vesion should do the trick.
"dependencies": {
"@iobroker/adapter-core": "^2.6.0",
"axios": "^0.27.2",
"cloneextend": "^0.0.3",
"json-schema": "^0.4.0",
"node-ical": "^0.15.1",
"rrule": "2.6.9"
},
Can you recommend any measure?
Thank you!

Ok, last time the fix was to have rrule 2.6.4 ... but then dependabot upgradded it to 2.6.9 again ...

1.13.2 on it's way

When will 1.13.2 be available as stable version?


text:
Further performace improvements for rendering (image caching)

First of all, thank you for the awesome book! I just started learning Rust and it was fun and helpful to build the game.
I had the issue that even after implementing batch rendering the FPS were somewhere between 40 and 50, but never 60. After finishing the book I continued playing around with the code trying to reach 60 FPS. I managed by introducing a cache for the images. Now the game reaches 60 FPS after a few seconds. Would this be an addition to the book you would be interested in?
I am not sure if my implementation is well done (really new to rust), but if you are interested:
The biggest change is https://github.com/NiklasEi/sokoban-rust/blob/master/src/systems/rendering_system.rs#L56-L63

hey @NiklasEi, glad you enjoyed it!
yep loading the image every frame is certainly not ideal, this would be an awesome addition, I think we have an issue about this somewhere. the code looks pretty good to me, maybe you can submit a draft PR? I think you can make the change directly in the 3.4 chapter since it's pretty small, maybe just towards the end after the batch rendering changes.

authors: NiklasEi iolivia

repo: iolivia/rust-sokoban


text:
Fix(iOS): Issues related to keyboard dismissal (4.x)

Sister PR for 2.x: PR #532

The history of the keyboard dismissal problems are kind of messy so here we go:
1)
The main bug that started this all is reported here:

cordova-plugin-ionic-webview #176
cordova-plugin-wkwebview-engine #71
cordova-ios #417 Which best identifies the problem.

To summarize: Apple did something and broke a part of WKWebView for iOS 12 and 13.  The problem occurs when the keyboard is dismissed.  After dismissal the bottom part of the page has a white unused portion / the content behind the keyboard becomes unusable.
The issue is truly an apple problem.  So this PR, and the previously accepted PR #201, should not be required if apple ever actually releases the fix.  (The fix has been completed already apparently).
You can see the apple bug report links here.
2)
PR #179 and PR #201 attempt to fix this problem.

PR #179 is denied.
PR #201 is accepted.

3)
Unfortunately, PR #201 introduces another a secondary bug, #399.
Now, when the keyboard is dismissed the screen scrolls all the way back to the top.
(Also reported in cordova-plugin-ionic-keyboard #84.)
4)
To fix the scroll to top issue we have PR #342.  Unfortunately, this introduces another (less problematic bug): the view now "jumps" a little when moving between text fields.

Proposed Solution
Modify the changes from PR #201 using inspiriration from PR #342.
In KeyboardWillHide event:

Detect when the presence of the keyboard has allowed the user to scroll further than they would have been able to without the keyboard.  (aka. If there will be whitespace at the bottom when the keyboard goes down)
If in the situation above, do some math to calculate the maximum allowed offset, and set the view to that.  This causes the view to move into place properly.  (So no empty whitespace or unusable portion of the view.)

Environment
I have been testing with:

Xcode 10.2

I have been testing on these devices:

iPad mini 2, iOS 12.4.5 (real)
iPhone 6s, iOS 13.3.1 (real)
iPhone X, iOS 12.2 (emulator)

And these projects:
modified ionic tutorial

cordova-plugin-ionic-webview 4.x
cordova-plugin-ionic-keyboard / NO cordova-plugin-ionic-keyboard

modified cordova helloWorld

NO cordova-plugin-ionic-keyboard

I have also tested this change with, and without, the changes in PR #531
I have also tested the 2.x sister PR #532 (which has identical changes basically) with this project:
cordova

cordova-plugin-ionic-webview 2.x
no keyboard plugins
Lots of other plugins that shouldn't matter

Summary
Fixes:

#399
#509
cordova-plugin-ionic-keyboard #84

Compatible with PR #531.
Alternate Solution

Remove all changes from PR #201 (the keyboard event listeners)
And recommend that users use cordova-plugin-wkkeyboardfix until Apple releases the fix in an iOS update

Pros:

Less code muddling on our side (cleaner history)

Cons:

Apparently the plugin may result in a rejection

(tested this plugin on the ionic and cordova project for 4.x, and cordova for 2.x)
Since this plugin has already fixed this issue, I suppose it is probably better to just fix the fix at this point rather than this.

@Lindsay-Needs-Sleep It looks like iOS 13.4 fixes this issue?

@dwieeb I didn't notice the release, thanks!
I just updated to 13.4 and 12.4.6 on my devices and tried it out.
You are right, it looks like the issue is fixed on 13.4!  (Really Apple, the day after I make my fix? :p)
But the issue still appears to exist on 12.4.6.  (Also, "Really Apple?")
So this fix is still valid for 12.x (and probably 11.x).  I'll add a commit to limit it.

@Lindsay-Needs-Sleep I just downloaded IOS 13.4 and the scroll top bug still exists in my Ionic app consuming cordova-plugin-ionic-webview 4.1.3.  It seems like some of the previous PRs addressing WkWebview IOS error are now doing more harm than good since IOS 13.4 fixes the keyboard dismissal bug.
Does anyone have a work around they're using to not see the hideous keyboard dismissal bug but aren't getting the equally as shitty scroll to the top bug.

Does anyone have a work around they're using to not see the hideous keyboard dismissal bug but aren't getting the equally as shitty scroll to the top bug.

That is exactly what this PR is.  :S
Background:

ios 13.4 fixed the whitespace/unusable portion at the bottom on keyboard dismissal.

But this is still a problem on ios 11 - 13.3.x

The ‘scroll to top’ was a bug introduced solely in this plugin while implementing a workaround for the issue in the point above.

This PR modifies the fix that introduced the ‘scroll to top’ bug:

The new fix only applies to iOS less than 13.4
It uses a different solution for the original whitespace/unusable keyboard dismissal bug which is ‘scroll to top’ bug free.

But until this PR (or similar) is approved, if you are looking to not change any native code, I guess the best you can do is drop this plugin and go to cordova-plugin-wkwebview-engine.

As recommended, shall I use this plugin cordova-plugin-wkkeyboardfix?
Is anyone used and publish their app in Apple Store? because they have given note as - plugin is a hack around a bug in iOS. It might result in your app being rejected from the App Store! Use this at your own risk.

@andaralex
Note: For the cordova-plugin-wkkeyboardfix to work, you can not use cordova-plugin-ionic-webview

@Lindsay-Needs-Sleep  I see this PR has been merged.  Is it available for use yet, or does it need to go into a release?

@mattcwebster It depends on how you have added cordova-plugin-ionic-webview to your project.
Probably, you should remove the plugin and re-add it.
cordova plugin remove cordova-plugin-ionic-webview
cordova plugin add https://github.com/ionic-team/cordova-plugin-ionic-webview#master

This will include the changes made in this pull request.

:tada: This PR is included in version 4.2.0 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:

@mattcwebster It depends on how you have added cordova-plugin-ionic-webview to your project.
Probably, you should remove the plugin and re-add it.
cordova plugin remove cordova-plugin-ionic-webview
cordova plugin add https://github.com/ionic-team/cordova-plugin-ionic-webview#master

This will include the changes made in this pull request.

I see this was included in release 4.2.0, however when upgrading to this version, I'm still getting the scroll issue.  Not sure if there's something I'm missing?

When using version 4.2.0 I'm getting both the scroll to top issue and the white-space on keyboard dismissal issue.  The only way I can prevent the white-space keyboard dismissal is by adding     <preference name="KeyboardResize" value="false" /> to my config.xml.  The problem with adding that line is that after I dismiss the keyboard, my footer is now un-clickable.

@mattcwebsterhttps://github.com/mattcwebster
Can you tell me which version of iOS you are still seeing the issue on?  (eg. iOS 11)
And can you share the output of “cordova plugin” please
On Apr 18, 2020, at 10:31, mattcwebster <notifications@github.commailto:notifications@github.com> wrote:
@mattcwebsterhttps://github.com/mattcwebster It depends on how you have added cordova-plugin-ionic-webview to your project.
Probably, you should remove the plugin and re-add it.
cordova plugin remove cordova-plugin-ionic-webview
cordova plugin add https://github.com/ionic-team/cordova-plugin-ionic-webview#master
This will include the changes made in this pull request.
I see this was included in release 4.2.0, however when upgrading to this version, I'm still getting the scroll issue. Not sure if there's something I'm missing?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/ionic-team/cordova-plugin-ionic-webview/pull/533#issuecomment-615899554, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMLADYZLXFDPVWSUZ4EPDZ3RNHIXXANCNFSM4LR2HV4A.

@mattcwebster Can you tell me which version of iOS you are still seeing the issue on? (eg. iOS 11) And can you share the output of “cordova plugin” please

I'm using version 13.4
cordova-plugin-device 2.0.3 "Device"
cordova-plugin-inappbrowser 3.2.0 "InAppBrowser"
cordova-plugin-ionic-keyboard 2.2.0 "cordova-plugin-ionic-keyboard"
cordova-plugin-ionic-webview 4.2.0 "cordova-plugin-ionic-webview"
cordova-plugin-splashscreen 5.0.3 "Splashscreen"
cordova-plugin-statusbar 2.4.3 "StatusBar"
cordova-plugin-whitelist 1.3.4 "Whitelist"

Actually, I may have solved my own problem but I don't know how.  I dumped my node_modules folder and deleted my cordova-plugin-ionic-webview folder from within plugins.  Did a fresh npm install, and prod build and it seems to be working!  Coolio and sorry for the confusion.
Thanks again for your hard work and responsiveness on this one @Lindsay-Needs-Sleep

NP!  Glad to hear it!  :D

authors: Ionitron Lindsay-Needs-Sleep andaralex dwieeb mattcwebster

repo: ionic-team/cordova-plugin-ionic-webview


text:
Not able to download app code from ionic view

I am using ionic 2 to build my app. I have uploaded my app to ionic view. My app id is 779eb729
I lost my code locally.
How can i download the code uploaded to ionic view?
I have tried the following

Entering app Id to download it as a zip using the below link.

https://apps.ionic.io/settings/data
Getting error as below.
<Error>

repo: ionic-team/ionic


text:
webapp使用浏览器后退键没法后退上级页面

Resources:
Before submitting an issue, please consult our troubleshooting guide (http://ionicframework.com/docs/troubleshooting/) and developer resources (http://ionicframework.com/docs/developer-resources/)
Ionic version:  (check one with "x")
[ ] 1.x (For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[x] 3.x
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:

我使用ionic开发webapp,因为在Android手机上有返回的按键效果类似于浏览器的返回按钮,但是我在点击返回时url变化了,页面没有返回上一级页面,我家在页面使用的是lazy-load
Expected behavior:

Steps to reproduce:

Related code:
insert any relevant code here

Other information:

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
insert the output from ionic info here

Hello! Thank you for opening an issue with us!
Can you please edit your issue to describe the current behavior in English, and to provide the Ionic info output in the appropriate section?
Also, please provide a sample application via GitHub that demonstrates the issue you are having.
Thank you for using Ionic
Google Translate says: I use the web development webapp, because the Android phone has a return button similar to the browser's return button, but I click on the return url changes, the page did not return to the previous page, my home in the page using lazy- load

I'am so sorry, I am still improving my English. I downloaded a case from the website and solved the problem, I quit using lazy loading.
Thanks!
----- 原始邮件 -----
发件人：Ken Sodemann notifications@github.com
收件人：ionic-team/ionic ionic@noreply.github.com
抄送人：baobz baobz@sina.cn,  Author author@noreply.github.com
主题：Re:_[ionic-team/ionic]webapp使用浏览器后退键没法后退上级页面(#12794)
日期：2017年09月01日 19点10分
Hello! Thank you for opening an issue with us!
Can you please edit your issue to describe the current behavior in English, and to provide the Ionic info output in the appropriate section?
Also, please provide a sample application via GitHub that demonstrates the issue you are having.
Thank you for using Ionic
Google Translate says: I use the web development webapp, because the Android phone has a return button similar to the browser's return button, but I click on the return url changes, the page did not return to the previous page, my home in the page using lazy- load
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@baobz
you can register "setupBrowserBackButtonBehavior"  on app.component.ts
private setupBrowserBackButtonBehavior(): void {
window.onpopstate = (event) => {
if (this.ionicApp) {
let activePortal: any =
this.ionicApp._loadingPortal.getActive() ||
this.ionicApp._modalPortal.getActive() ||
this.ionicApp._toastPortal.getActive() ||
this.ionicApp._overlayPortal.getActive();
            if (activePortal) {
                activePortal.dismiss();
                return;
            }
        }
    };
}

webapp使用浏览器后退键没法后退上级页面.
It means "can not go back using BrowserBackButton  on web Application".

Thank you for the responses. If I understand this conversation correctly, it sounds like you have found a solution. I am going to close this issue for now but will be happy to reopen it if the solutions being discussed do not work for you.

Thank you, I quit the method of lazy loading and It's working now
----- 原始邮件 -----
发件人：vellengs notifications@github.com
收件人：ionic-team/ionic ionic@noreply.github.com
抄送人：baobz baobz@sina.cn,  Mention mention@noreply.github.com
主题：Re:_[ionic-team/ionic]webapp使用浏览器后退键没法后退上级页面(#12794)
日期：2017年09月04日 16点48分
@baobz
you can register "setupBrowserBackButtonBehavior"  on app.component.ts
private setupBrowserBackButtonBehavior(): void {
window.onpopstate = (event) => {
if (this.ionicApp) {
let activePortal: any =
this.ionicApp._loadingPortal.getActive() ||
this.ionicApp._modalPortal.getActive() ||
this.ionicApp._toastPortal.getActive() ||
this.ionicApp._overlayPortal.getActive();
if (activePortal) {
activePortal.dismiss();
return;
}
}
};
}
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

authors: baobz kensodemann vellengs


text:
Images are not showing on device in ios 10 [ionic 1]

I have spotted some weird behaviour. I have recently updated my iphone 6 to iOS 10 (beta 4) and all the images in my app disappeared while running my app on a iOS device with ionic run ios --device. If a run the same for emulator everything seems to work fine and the images are shown. Another thing while do run the livereload like `ionic run ios --livereload', for both emulator or device everything works fine.
Any ideas ?
P.S
I found out the above is working on iphone 5 with ios 10 (beta 4) but not on iphone 6.

Hello! Thanks for opening an issue with us! Would you mind posting about this issue here? That is our tracking issue for IOS10 support. At this time, since ios10 is still beta, we do not officially support it, but we do plan on official support as soon as it hits stable and becomes the public release. Thanks for using Ionic!

SOLVED

Add your images to src/assets/imgs directory

Set image path in HTML like
<img src="assets/imgs/example.jpg">

Set image path in SCSS like
background-image: url(../assets/imgs/example.jpg);

It will work browser, emulator and build

Same issue here. I’m getting the image dynamically from an api though. It works on google chrome but no image on iOS and safari

authors: jgw96 kristiyandobrev loloDawit renjithvk


text:
Generate the 'next' version for a changelog with an Unreleased section

I want to add a concept of 'the next prerelease version if there's an unreleased section', so that folks get a sane auto-generated version number when they do local builds. Logic would be something like:

take the unreleased segment
take the last release entry
check the changes in the unreleased segment to determine what kind of bump (similar to what I created in FsAutoComplete)
do that bump, but with a prerelease segment of -alpha.<COUNTER>, where counter is determined by the number of lines of changes in the unreleased portion overall. idea being that each PR or commit would map to a single change line in the changelog, so you'd have a minimal amount of traceability out of the box.

Would also need a 'don't do that please' flag that folks could set in case they really didn't want the automatic version selection.
Big open issue is how to determine the expected bump, but I can just put a flag in the ground here and get feedback later.

repo: ionide/KeepAChangelog


text:
F#.: Run script command fails

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behaviour:
Try to execute any f# script with F# Run script command
Expected behaviour
Script output, but instead the following text is displayed on terminal:
_Could not execute because the specified command or file was not found.
Possible reasons for this include:

You misspelled a built-in dotnet command.
You intended to execute a .NET Core program, but dotnet-fsi --fsi-server-input-codepage:65001 does not exist.
You intended to run a global tool, but a dotnet-prefixed executable with this name could not be found on the PATH._

Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):

OS: Win 10
Ionide version: 4.3.1
VSCode version: 1.40.1
dotnet SDK version: 3.0.101
mono / .Net Framework version:

Additional context
Fails with Ionide 4.3.1, 4.3.0, but works with 4.2,
Command that Ionide tries to execute contains extra double quotes, terminal command history contains last command
cd "c:....\source\repos\ELRS\src\slrutils" && cls && "C:\Program Files\dotnet\dotnet.exe" ""fsi" "--fsi-server-input-codepage:65001"" "c:...\source\repos\ELRS\src\slrutils\CpfTest.fsx" && pause && exit

Did you set “"Use SDK Scripts" to true in the ionide settings.”?

Yes. As I mentioned in  description,  problem is dotnet fsi command, which contains extra double quotes. Terminal stays opened with the error message and its possible to check this command in history buffer. After deleting extra quotes, command executes just fine.

Have you set a custom FSharp.fsiFilePath setting or is that still on the default?

Default value.

Thanks for confirming. Yay for windows quote escaping...

Hey, this may be out of topic a bit but let me ask one question - why do you use F#: Run script rather than FSI: Send file? I've been considering removing F#: Run script to simplify stuff

FSI: Run Script is the  the first button in the row, convenient to use.

Ionide-fsharp 4.6.0 will fix this problem.

authors: Krzysztof-Cieslak baronfel dgrimmin kalvis77 matarillo

repo: ionide/ionide-vscode-fsharp


text:
Nicer UX for inlay hints

Part of #1693
The main thing this does is overhaul the tooltips for the inlay hints - now there are command-links (clickable links) that will disable:

this specific kind of hint (type hint vs parameter name)
all hints
(if the version of VSCode is at least 1.67.0) a configuration that lets the user press Ctrl+Alt to toggle the display of the hints while held
dismissing the clickable tooltips here

This was actually pretty easy to set up, we should do things like this more often!

Lgtm

authors: Krzysztof-Cieslak baronfel