Test environment does support uint64_t  - documentation should mention

Building the statHelpers library

https://github.com/RobTillaart/statHelpers/runs/1669359173?check_suite_focus=true

I found that printing uint64_t  is natively supported (UNO's Serial print does not )  by using %ld
Maybe the reference can mention 2 lines about this.
(low prio - documentation)

I'm getting a 404 on that link.
Just so I understand the issue, is it that the test environment is allowing uint64_t even though the actual hardware won't support it?

I'm getting a 404 on that link.
Just so I understand the issue, is it that the test environment is allowing uint64_t even though the actual hardware won't support it?

Oops might have removed that specific run as I had many test runs.
But yes , the UNO does support uint64_t in math but cannot print them (without my printHelpers class)
The test environment can print them, so that is good for testing!
This one should work
https://github.com/RobTillaart/statHelpers/actions/runs/472101006

Oops might have removed that specific run as I had many test runs.
But yes , the UNO does support uint64_t in math but cannot print them (without my printHelpers class)
The test environment can print them, so that is good for testing!
This one should work
https://github.com/RobTillaart/statHelpers/actions/runs/472101006


After phoenix/ecto upgrade, error: could not find array type for data type integer[]

Environment
I upgraded phoenix and ecto:
My old deps:
{:phoenix, "~> 1.1.4"},
{:postgrex, ">= 0.0.0"},
{:phoenix_ecto, "~> 2.0"},

Replaced with:
{:phoenix, "~> 1.2.0"},
{:phoenix_pubsub, "~> 1.0"},
{:phoenix_live_reload, "~> 1.0"},
{:postgrex, ">= 0.11.2"},
{:phoenix_ecto, "~> 3.0-rc"},

Elixir 1.2.2
PostgreSQL 9.4
ecto 2.0.2
Operating system:
OS X Yosemite 10.10.4
Current behavior
When asking  for "latest" execution I want to find all the latest executions for all sessions:
def select_by_execution_num(query, execution_num) do
    if String.equivalent?(String.downcase(execution_num), "latest") do
        executions = Repo.all(
        from e in query,
        select: [e.session_id, fragment("coalesce(?, ?)", max(e.execution_num), 0)],
        group_by: e.session_id
        )
        # resulting `executions`:
        #    [[20, 1], [21, 1]]
        # BELOW WILL FAIL
        from e in query, where: [e.session_id, e.execution_num] in ^executions
    else
        from e in query, where: e.execution_num == ^execution_num
    end
  end

Resulting query that will fail:
#Ecto.Query<from e in PipelineOperations.Execution,
 where: [e.session_id, e.execution_num] in ^[[20, 1], [21, 1]]>

Logs and Exception:
03:40:08.738 [info] GET /v1/execution
03:40:08.755 [debug] Processing by PipelineOperations.ExecutionController.index/2
  Parameters: %{"execution_num" => "latest"}
  Pipelines: [:api]
03:40:08.777 [debug] QUERY OK db=2.1ms
SELECT e0."session_id", coalesce(max(e0."execution_num"), 0) FROM "execution" AS e0 GROUP BY e0."session_id" []
03:40:08.788 [debug] QUERY ERROR db=6.0ms
SELECT e0."id", e0."execution_num", e0."workflow_config", e0."start", e0."stop", e0."received_by", e0."message", e0."session_id", e0."status_id", e0."inserted_at", e0."updated_at" FROM "execution" AS e0 WHERE (ARRAY[e0."session_id",e0."execution_num"] = ANY($1)) [[[20, 1], [21, 1]]]
03:40:08.805 [info] Sent 500 in 67ms
03:40:08.810 [error] #PID<0.484.0> running PipelineOperations.Endpoint terminated
Server: localhost:4000 (http)
Request: GET /v1/execution?execution_num=latest
** (exit) an exception was raised:
    ** (Postgrex.Error) ERROR (undefined_object): could not find array type for data type integer[]
        (ecto) lib/ecto/adapters/sql.ex:405: Ecto.Adapters.SQL.execute_and_cache/7
        (ecto) lib/ecto/repo/queryable.ex:127: Ecto.Repo.Queryable.execute/5
        (ecto) lib/ecto/repo/queryable.ex:40: Ecto.Repo.Queryable.all/4
        (pipeline_operations) web/controllers/execution_controller.ex:17: PipelineOperations.ExecutionController.index/2
        (pipeline_operations) web/controllers/execution_controller.ex:1: PipelineOperations.ExecutionController.action/2
        (pipeline_operations) web/controllers/execution_controller.ex:1: PipelineOperations.ExecutionController.phoenix_controller_pipeline/2
        (pipeline_operations) lib/pipeline_operations/endpoint.ex:1: PipelineOperations.Endpoint.instrument/4
        (pipeline_operations) lib/phoenix/router.ex:261: PipelineOperations.Router.dispatch/2
        (pipeline_operations) web/router.ex:1: PipelineOperations.Router.do_call/2
        (pipeline_operations) lib/pipeline_operations/endpoint.ex:1: PipelineOperations.Endpoint.phoenix_pipeline/1
        (pipeline_operations) lib/plug/debugger.ex:93: PipelineOperations.Endpoint."call (overridable 3)"/2
        (pipeline_operations) lib/pipeline_operations/endpoint.ex:1: PipelineOperations.Endpoint.call/2
        (plug) lib/plug/adapters/cowboy/handler.ex:15: Plug.Adapters.Cowboy.Handler.upgrade/4
        (cowboy) src/cowboy_protocol.erl:442: :cowboy_protocol.execute/4

Expected behavior
This code used to work until after the upgrade.
I tried a few things to get around it, but considering it just started happening after working for months, I thought I would open an issue -- sorry ahead of time if it ends up being false alarm!

Wait, did it work before? I didn't think we supported this feature. :)
let's add it back and include some tests.
On Sunday, July 17, 2016, Irina Guberman<EMAIL_ADDRESS>wrote:

Environment
I upgraded phoenix and ecto:
My old deps:
{:phoenix, "~> 1.1.4"},
{:postgrex, ">= 0.0.0"},
{:phoenix_ecto, "~> 2.0"},
Replaced with:
{:phoenix, "~> 1.2.0"},
{:phoenix_pubsub, "~> 1.0"},
{:phoenix_live_reload, "~> 1.0"},
{:postgrex, ">= 0.11.2"},
{:phoenix_ecto, "~> 3.0-rc"},
Elixir 1.2.2
PostgreSQL 9.4
ecto 2.0.2
Operating system:
OS X Yosemite 10.10.4
Current behavior
When asking for "latest" execution I want to find all the latest
executions for all sessions:
def select_by_execution_num(query, execution_num) do
if String.equivalent?(String.downcase(execution_num), "latest") do
executions = Repo.all(
from e in query,
select: [e.session_id, fragment("coalesce(?, ?)", max(e.execution_num), 0)],
group_by: e.session_id
)        # resulting executions:        #    [[20, 1], [21, 1]]        # BELOW WILL FAIL
from e in query, where: [e.session_id, e.execution_num] in ^executions
else
from e in query, where: e.execution_num == ^execution_num
end
end
Resulting query that will fail:
#Ecto.Query<from e in PipelineOperations.Execution,
where: [e.session_id, e.execution_num] in ^[[20, 1], [21, 1]]>
Logs and Exception:
03:40:08.738 [info] GET /v1/execution
03:40:08.755 [debug] Processing by PipelineOperations.ExecutionController.index/2
Parameters: %{"execution_num" => "latest"}
Pipelines: [:api]
03:40:08.777 [debug] QUERY OK db=2.1ms
SELECT e0."session_id", coalesce(max(e0."execution_num"), 0) FROM "execution" AS e0 GROUP BY e0."session_id" []
03:40:08.788 [debug] QUERY ERROR db=6.0ms
SELECT e0."id", e0."execution_num", e0."workflow_config", e0."start", e0."stop", e0."received_by", e0."message", e0."session_id", e0."status_id", e0."inserted_at", e0."updated_at" FROM "execution" AS e0 WHERE (ARRAY[e0."session_id",e0."execution_num"] = ANY($1)) [[[20, 1], [21, 1]]]
03:40:08.805 [info] Sent 500 in 67ms
03:40:08.810 [error] #PID<0.484.0> running PipelineOperations.Endpoint terminated
Server: localhost:4000 (http)
Request: GET /v1/execution?execution_num=latest
** (exit) an exception was raised:
** (Postgrex.Error) ERROR (undefined_object): could not find array type for data type integer[]
(ecto) lib/ecto/adapters/sql.ex:405: Ecto.Adapters.SQL.execute_and_cache/7
(ecto) lib/ecto/repo/queryable.ex:127: Ecto.Repo.Queryable.execute/5
(ecto) lib/ecto/repo/queryable.ex:40: Ecto.Repo.Queryable.all/4
(pipeline_operations) web/controllers/execution_controller.ex:17: PipelineOperations.ExecutionController.index/2
(pipeline_operations) web/controllers/execution_controller.ex:1: PipelineOperations.ExecutionController.action/2
(pipeline_operations) web/controllers/execution_controller.ex:1: PipelineOperations.ExecutionController.phoenix_controller_pipeline/2
(pipeline_operations) lib/pipeline_operations/endpoint.ex:1: PipelineOperations.Endpoint.instrument/4
(pipeline_operations) lib/phoenix/router.ex:261: PipelineOperations.Router.dispatch/2
(pipeline_operations) web/router.ex:1: PipelineOperations.Router.do_call/2
(pipeline_operations) lib/pipeline_operations/endpoint.ex:1: PipelineOperations.Endpoint.phoenix_pipeline/1
(pipeline_operations) lib/plug/debugger.ex:93: PipelineOperations.Endpoint."call (overridable 3)"/2
(pipeline_operations) lib/pipeline_operations/endpoint.ex:1: PipelineOperations.Endpoint.call/2
(plug) lib/plug/adapters/cowboy/handler.ex:15: Plug.Adapters.Cowboy.Handler.upgrade/4
(cowboy) src/cowboy_protocol.erl:442: :cowboy_protocol.execute/4
Expected behavior
This code used to work until after the upgrade.
I tried a few things to get around it, but considering it just started
happening after working for months, I thought I would open an issue --
sorry ahead of time if it ends up being false alarm!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/elixir-ecto/ecto/issues/1583, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAlbujq44iZ5NQsDkQ0MA-OWCs-KTRlks5qWe4FgaJpZM4JOL0V
.

--
José Valim
www.plataformatec.com.br
Skype: jv.ptec
Founder and Director of R&D

I may be wrong but I don't see a way we can support this. The limitation is that postgresql doesn't handle nested arrays very well.

Thanks you very much for responding!
So, just to confirm it worked, I downgraded to phoenix_ecto 2.0.2 and ran the same URL that was broken, and it is working again, the constrcuted query looks different now (same code on my end  from e in query, where: [e.session_id, e.execution_num] in ^executions):
17:10:33.066 [debug] SELECT e0."session_id", coalesce(max(e0."execution_num"), 0) FROM "execution" AS e0 GROUP BY e0."session_id" [] OK query=92.3ms queue=16.1ms
17:10:33.085 [debug] SELECT e0."id", e0."execution_num", e0."workflow_config", e0."start", e0."stop", e0."received_by", e0."message", e0."session_id", e0."status_id", e0."inserted_at", e0."updated_at" FROM "execution" AS e0 WHERE (ARRAY[e0."session_id",e0."execution_num"] IN ($1,$2)) [[20, 1], [21, 1]] OK query=15.3ms
comparing to
AS e0 WHERE (ARRAY[e0."session_id",e0."execution_num"] = ANY($1)) [[[20, 1], [21, 1]]]

It worked previously because we didn't support arrays as parameters. We used to split array element into individual parameters because of limitations in mysql (iirc). We now properly use the whole array as a single parameter because this gives us much better query caching in ecto.
It has the downside that it breaks your code, but I would argue it only worked accidentally before. For example your code would still break in previous ecto versions if you used a triple nested array.

It would work if instead of an array of an array you had an array of tuples but postgrex can't encode anonymous record types. We would need to add some kind of type hinting to postgrex for that to work.
@fishcakez any ideas?

I'm a little confused on the use of this "array as a parameter".   What's the point of its other benefits if it doesn't work at all for postgres?  Postgres is a pretty important db, IMHO ;)  (Sorry if I'm missing a point somewhere! :)  Also what I was trying to do is not at all uncommon.   Maybe there is an alternative better way of doing it in ecto or I can use fragments.  I will happily change the code on my end if this accidental feature isn't deemed important to support.   However when I was working on it, logically it seemed legit and in line my "ecto intuition" (Please keep in mind my ecto intuition is still rather questionable! :)

Using an array as parameter works as long as you don't have a nested array. We didn't support this before either, it only accidentally worked and if you had three-level nested array it wouldn't work on older versions either.
I agree that we need a way to solve this, but currently I don't see how we could do that without changes in the underlying postgres driver. Unfortunately I don't have a clear workaround for you either.

Also to show that this is actually more of a Postgres issue than an Ecto issue:
ericmj=# SELECT ARRAY[1, 2] = ANY(ARRAY[ARRAY[1, 2], ARRAY[3, 4]]);
ERROR:  operator does not exist: integer[] = integer
LINE 1: SELECT ARRAY[1, 2] = ANY(ARRAY[ARRAY[1, 2], ARRAY[3, 4]]);
                           ^
HINT:  No operator matches the given name and argument type(s). You might need to add explicit type casts.

Postgres actually do not support what you want to do. We could possibly work around it by using an array of records instead of an array of arrays, but postgres does not have great protocol support for this either so we would need to add some special support for it in the driver.

Below is the SQL equivalent of what I was trying to do, maybe there is a nice ecto way of doing it without arrays?
select * from execution where (session_id, execution_num)
IN (select session_id, max(execution_num) from execution group by session_id)

For now you have to write as a fragment until we support those kinds of subqueries:
from(e in Execution, where: fragment("(?, ?) IN (select ...)", e.session.id, e.execution_num))

Fragment is the way to go for now. Closing this. :) Sorry for the mishap @iguberman!

Thanks so much @josevalim @ericmj   fragment works  -- I really appreciate your continuous help and support!  You all rock! :)


print -> NSLog

Using NSLog, though a bit ugly in Swift, has the advantage, that the diagnostic is logged in the system console — which is useful when we debug app extensions, Watch apps, or observe the behavior of a non-debug app (e.g. from TestFlight, not locally run)

Good point. Thanks!


autokbisw does not recognize MacBooks internal keyboard anymore

I have used autokbisw for months now without any major problems. But today I realized that something with the layout switching is wrong. I use autokbisw to change between my MacBooks internal keyboard and my external keyboard with different keyboard layouts. After investigating the issue I noticed the following problem(s):

The devices are not recognized correctly anymore. autokbisw list gives me my external keyboard (2 times, because sometimes it's connected via Bluetooth and sometimes via USB) and my Logitech mouse. The internal keyboard of the MacBook however is not getting recognized at all. When I checked the last time a few weeks ago, the internal keyboard was correctly being recognized and the mouse was correctly not being recognized.
The program behaves "weirdly" at times. Deactivating the mouse at one time only worked for a few seconds. This also messed up the layout switching. But at the moment, this problem luckily seems to be gone.

After I noticed the problems I tried updating the program, re-started the service and re-granted the required privileges.
A few days ago I got a new keyboard. Prior to that I only used an external keyboard with a wired connection, so maybe that made me notice the problem? But that does not make too much sense, because everything worked fine in the first days.
Any help with my problem would be very much appreciated! I really do like the program and would love to be able to continue using it🙂
Thanks in advance!

Thanks for your detailed bug report! I can reproduce the issue und will look into it as soon as possible. It seems like in the new version 2.0, new devices are not recognized in all cases.
Maybe this workaround can help in the meantime.
Stop the service:
brew services stop ohueter/tap/autokbisw
Interact with the existing devices using the list, enable and disable commands (e.g., disable your mouse).
Start the service again:
brew services start ohueter/tap/autokbisw
Alternatively, you can download and use the latest working release from https://github.com/ohueter/autokbisw/releases/tag/1.4.4 and start autokbisw directly.

Hi @leojue, please try upgrading to version 2.0.1 und see if the fixes resolve your issues: brew upgrade ohueter/tap/autokbisw
Thanks for beta-testing! 😄

Yes, the new version fixes my issues! Now everything works as expected. Thank you very much @ohueter for your quick reply and solution for the problem😃
Have a nice day!

Glad that it works again! Happy holidays!


Two Issues with Documentation / Script

Thank you for this script, however, if anyone is following along it is impossible to run this as a scheduled task as per the documentation as the script 1) Does not allow for relative dates, anyone who downloads and runs it would just be pulling the same X days over and over and 2) Prompts for credentials. Can the documentation be changed or the script fixed to allow for relative dates and the usage of current users' credentials.
Thank you

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 24e29f25-b07b-99ff-8131-3980aae379b6
Version Independent ID: 49d6bf5f-56d7-0e19-3f39-7f1a051ad0cd
Content: Tutorial How to download and use a script to access signin logs
Content Source: articles/active-directory/reports-monitoring/tutorial-signin-logs-download-script.md
Service: active-directory
GitHub Login: @priyamohanram
Microsoft Alias: priyamo

@Antonlovesdnb thanks for the feedback! I have assigned this issue to the content author, @priyamohanram , to look into your comments.

Thank you for the feedback! I have created a work item in our backlog to refresh this article and will update it as soon as possible. Please feel free to open a new issue if you have any followup questions or concerns. Thank you!
#please-close


option size has no effect

Hi,
thanks for sharing this library.
Changing the option size has no effect at all.
`
kind regards
hasc

Just run bower install switchery and update your repository with the latest version of switchery. It worked for me


bump to v1.0

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


duplicated snippets because of internal error

I got this error
"There's been an internal error on the server; it probably wasn't anything you did, so don't worry too much about it. The site administrators have been emailed with the details, and they'll probably get it fixed real soon."
So I retried the operation
The result is I have multiple duplicated snippets
But I can't remove the duplicates
https://djangosnippets.org/users/depaolim/
Please remove the duplicates and possibly add a remove-button available to the user

Yeah, the earch was broken but works now again. Sorry for the problems!


Introduce parent-doi

A field parent-doi (or similarly named) shall be introduced to record project level DOIs, such as those in Zenodo, which collect child DOIs, i.e., version DOIs.
This will ensure sustained access to a software via the parent DOI, for which a landing page may exist which points to all versions, or the latest version.
This field shall be non-required.

@jspaaks Should this become part of 1.1.0 as well? It's cheap and useful to have (e.g., the RSD works on parent DOIs, right?).
I don't want to introduce unnecessary complexities (introducing this as part of 1.1.0 is feature-creepy enough), therefore I'd suggest to actually introduce parent-doifor the particular DOI use case. (This would also be in line with the principles, which suggest to use DOIs above other identifiers.)
If other identifiers exist that know the parent-version relationship, this could always be implemented as two complex types of identifier (cf. https://github.com/citation-file-format/citation-file-format/issues/85#issuecomment-551016103), i.e.:
identifiers:
  - type: custom-id
    value: cid://imacustomid
  - type: custom-id-parent
    value: cid://imabovecustomid'sparent

I think we should probably give it a little more time (than 1.1.0), as this warrants more discussion.
My initial thought would be to make this a post-1.1.0 expansion of https://github.com/citation-file-format/citation-file-format/issues/85#issuecomment-551016103 that adds an optional qualifier or something to each identifier. We would need to explain what relation exactly is being qualified though (probably a one-to-many relation).
This would take care of the granularity that @moranegg reported in #85 here. With regard to qualifier's type, we could consider using an enum based off of / including some terms that other standards already use, like isVersionOf, isSupplementTo, and whathaveyou (e.g. https://schema.datacite.org/meta/kernel-4.3/doc/DataCite-MetadataKernel_v4.3.pdf page 24). Note I don't know which relationType is used to identify something as a child of a parent, maybe child isPartOf parent?

Hm, the thing is that doi - I think - should stay a part of CFF beyond 1.1.0. This is because

DOI is the preferred identifier in the Principles paper
It provides backward-compatibility to pre-1.1.0.

In light of this, and because we want a way to express concepts for software via a DOI, I think it'd be good to have this as a root field (as parent-doi or concept-doi), which should have the exclusive semantic to provide the identifier for the parent of the doi root field, for use cases where people want to follow the principles, and stick with the non-complex fields.
I agree that after 1.1.0 we should think about providing a qualifier for the objects in identifiers to bring in this linkage. However, we may want to think about whether this may botch the "simplicity" approach of CFF as compared to CodeMeta.
I'll leave this issue alone for now in terms of bringing it into 1.1.0, until we can discuss in person.

I must say that the granularity of identification is much more delicate than separating parent-doi and concpet-doi, this is why it should be discussed in a larger forum (maybe the FORCE11 & RDA joint Working group for software identification).
Here is a first draft of an identifiers mapping, where we tried to identify all parts of software as a whole: https://github.com/force11/force11-rda-scidwg/blob/master/hackathon/FORCE2019/outcomes/crosswalk_identifiers.csv
I agree that doishould stay in the CFF vocabulary, specifically because CFF is dedicated to citation and should be compatible/aligned to bibtex/biblatex vocabulary.
For example, we have worked on a biblatex proposition for HAL where we keep a 'doi' property because this is standard practice for papers.

Revisting the qualifier I mentioned earlier: this could help resolve issues like picking an item from the list of identifiersautomatically, e.g. https://github.com/JabRef/jabref/pull/7946#issuecomment-899871919


Fixed #14368 -- Allowed setting a reverse OneToOne relation to None.

https://code.djangoproject.com/ticket/14368

I had trouble following the indentation changes in __set__() at first but then I realised they were needed because the previous branches don't systematically raise anymore.  The added test case looks good to me! You're on a fixed ticket identification spree Tim!


Only 1 Joycon will be sent to the server

The default SlimeVR server can only take up to 2 rotational inputs from each IP. One from the packet type 1 and packet type 16. Since this seems to only use packet type 1 it sends all the rotational data to one tracker. Adding an option for every pair of joycons to have a different IP could allow for redirecting the packets from another device like a phone.

Hi. This project hasn't been released yet

I have added support for more than one Joycon in the 0.2 release. Closing issue.


Remote browser display issue with embeds

Example: https://webrecorder.io/_embed/michaeleatsfood/dispersion/20021210203239$br:firefox:49/http://distributedhistory.com/pearl.htm

duplicate of #682


Can't create a stateless API since allauth uses sessions everywhere

Hi,
I am trying to create a stateless API but I am forced to use sessions since allauth requires session to work properly.
I was able to not use sessions by using my own ACCOUNT_ADAPTER. But, the AccountMiddleware forces using session and it's unavoidable.
This has to be fixed.

The issue exists because of dependency on django-allauth for social authentications. As per an issue recorded on django-allauth there are no plans of moving away from session auth.
See https://github.com/pennersr/django-allauth/issues/3805#issuecomment-2108200458 for more details.


Issues with CSV download

Some weird behaviour with the common name column in the export, eg Gleichenia dicarpa has the common name 'Waewae KÅtuku', and Pittosporum undulatum is Snowdrop Tree (lord Howe)
The voucher location column doesnt get populated by the voucher link for collections, only the herbarium abbreviation (whereas iNat records get the link to the observation)

I made some changes after downloading the plant data (which takes a few hours).
Maybe check for butterflies?
Also someone requested that the download be all records not just the most recent, so I think that's what it's doing now.  Maybe we should note that in the FAQs:
"I'd like to see all collections not just the most recent for each species.  How do I do that?"

Maybe check for butterflies?
No hyperlinks for vouchered butterfly records either

Also someone requested that the download be all records not just the most recent, so I think that's what it's doing now
It's definitely doing that right now

Maybe we should note that in the FAQs:

Already done -->
"This will download a CSV file containing all records within the target area (and buffer, if selected), not just the most recent records that are presented in the table."

I think I took common name out of later downloads as it looked too messy, so that should go away on the next iteration

that's fine by me

html links now that work, but excel doesn't like them :(

probably better with just the url and not the ugly html:

should be fixed i think


Notification not showing when Taskbar is upside down.

Describe the bug
Notification not showing when taskbar is out of default position.
To Reproduce
Steps to reproduce the behavior:

Turn taskbar upside down or any side beside it except the default
Make an example script
Run script
See error

I can make a Notification with upside-down.
`from winotify import Notification, audio
notify = Notification(app_id="temp", title='teemp',
msg='hi', duration='long')
notify.set_audio(audio.LoopingAlarm, loop=True)
notify.show()`
works for me


acutually rebuild v5

@jdef take two.

thanks for doing this. i see there's an /app/* file in there. git warned me about those because they're in .gitignore. should we really be committing that file in this PR?

It's already tracked in the tree... https://github.com/kubernetes/kube-ui/blob/master/app/assets/js/app.js
git add -A . wanted to include it. Maybe clean up seperately if those need not be included?

ok sounds good
On Fri, Jan 29, 2016 at 8:35 PM, Mike Danese<EMAIL_ADDRESS>wrote:

It's already tracked in the tree...
https://github.com/kubernetes/kube-ui/blob/master/app/assets/js/app.js
git add -A . wanted to include it. Maybe clean up seperately if those need
not be included?
—
Reply to this email directly or view it on GitHub
https://github.com/kubernetes/kube-ui/pull/51#issuecomment-177043131.

LGTM

Okay this is pushed now


When I run publish-bytecode then create-application, I'll get wrong application ID returned to terminal

Description:
When I run publish-bytecode then create-application, I'll get wrong application ID returned to terminal for some application.
Steps:
1  https://github.com/web3eye-io/res-peer/blob/6999e88c71c59dc39898eae84dfcfda807e53e70/deploy.sh#L45C1-L45C1 Here I deploy my application to local testnet
Result:
1  For the first 4 applications, I get right application ID returned to terminal
2  For the fifth application, I get wrong application ID which is different from the application list get from graphiql
In my test, I get the following value from terminal:
💙 Review application deployed
Bytecode ID:    e476187f6ddfeb9d588c7b45d3df334d5501d6499b3f9ad5595cae86cce16a650c0000000000000000000000
Application ID: e476187f6ddfeb9d588c7b45d3df334d5501d6499b3f9ad5595cae86cce16a650c0000000000000000000000e476187f6ddfeb9d588c7b45d3df334d5501d6499b3f9ad5595cae86cce16a650e0000000000000002000000
But graphiql gives me
e476187f6ddfeb9d588c7b45d3df334d5501d6499b3f9ad5595cae86cce16a650c0000000000000000000000e476187f6ddfeb9d588c7b45d3df334d5501d6499b3f9ad5595cae86cce16a650e0000000000000000000000

They might not be in the same order. If they've all been published and deployed on the same chain, their IDs will only differ in those last digits. Did none of the create-application calls return …00000000 on the terminal?

They might not be in the same order. If they've all been published and deployed on the same chain, their IDs will only differ in those last digits. Did none of the create-application calls return …00000000 on the terminal?

only the last one has different output '...02000000', others're '...00000000'.

and i try to sleep 5 seconds between two create-application, the result is same.

and i think i can confirm every application i only deploy one time.

Thanks! I have a suspicion that we're using the message ID index wrong somewhere. I'll look into it.


Is that right that channel/accept, channel/adapt, channel/allow and channel/tune are performed only for inlets?

Things change, issue rename :)


LayoutXLM pretraining data

Hello,
Thanks for the great work with the LayoutXLM.
I wonder if you could share some of your work with the dataset used for pretraining. I know this is not possible to share dataset itself, due to Common Crawl policy, but can you share code which was used for obtaining the data?

@rpowalski Thanks for asking! For now, we do not have plans to share the dataset and the code to obtain the data.


AsyncStorage.getItem() doesn't seem to work

When I try to set a value via AsyncStorage.getItem(), I cannot request it back.
Environment
Environment:
OS: macOS High Sierra 10.13.3
Node: 9.8.0
Yarn: 1.5.1
npm: 5.6.0
Watchman: 4.9.0
Xcode: Xcode 9.2 Build version 9C40b
Android Studio: Not Found
Packages: (wanted => installed)
react: ^16.3.0-alpha.1 => 16.3.0-alpha.1
react-native: 0.54.0 => 0.54.0
Expected Behavior
await AsyncStorage.setItem('foo', 'bar');
await AsyncStorage.getItem('foo').then(console.log); // 'bar'
await AsyncStorage.getAllKeys().then(console.log); // ['foo']

Actual Behavior
await AsyncStorage.setItem('foo', 'bar');
await AsyncStorage.getItem('foo').then(console.log); // null
await AsyncStorage.getAllKeys().then(console.log); // []

Steps to Reproduce
import { AsyncStorage } from 'react-native';

it('should be able to request a value after it was set', async () => {
  await AsyncStorage.setItem('foo', 'bar');
  const output = await AsyncStorage.getItem('foo');

  expect(output).toBe('bar');
});

it('should be able to see a new key after a value was set', async () => {
  await AsyncStorage.setItem('foo', 'bar');
  const output = await AsyncStorage.getAllKeys();

  expect(output).toContain('foo');
});

Updated react-native => 0.54.0

I'm getting the same issue, and I'm using 0.54.0 react-native version, so what I can do to solve this? is It the stable version ?

Try to run the install command again, it may to work.

@xiaonull did you mean I run npm install before run react-native run-android
If is it, I have tried, even I tried to unistall and after install aplication on the device

Having the same issue with 0.52.0. Really frustrating.
If you call setItem and then immediately call getItem or getAllKeys to reveal all in the store it works as normal and the value will be present. Reload of the app and back to square one, getItem returns null.

Running into this issue sporadically on 0.54.2

It is really frustrating. after few time of running the app. Aysnc AsyncStorage.getItem() stops working.
I tried many hacky way to work around it. but after few times. its just don't work.

RN is pretty new to me, anyone know any of the maintainers on here we can ping to have a look?
The implementation is definitely not stable, there is another issue here: https://github.com/facebook/react-native/issues/12830
Don't really fancy using SQLite just to store a couple of integer values 😕

I am thinking to use this as alternative : https://github.com/oblador/react-native-keychain

@AleskiWeb  that is very stressful.
It's happening to me.
Some alternative?

same here ...
let result = await AsyncStorage.getItem(key)
android just stuck there , try catch not work, only restart the app again or setting a timeout,
but it is not a solution. It still cannot load the data saved.

let value = await AsyncStorage.getItem("user");
this line blocks the execution ....
the next line is not working .....
i am using  ..........  "react-native": "0.55.3"  and android one device....
its frustating........

the same issue, is it supposed to work with expo app or the issue is global?

Hello
the same here.....
"dependencies": {
"expo": "^27.0.1",
"react": "16.3.1",
"react-native": "~0.55.2",
"react-native-router-flux": "^4.0.0-beta.31"
}
I don't understand why it's not working...

Any update on this?

Same issue, still waiting for a fix!

Same issue here.

I had the same problem and I found the reason was I was just going to fast for what the bundler could handle. I was often saving several changes in several files in close succession and what @AleskiWeb described was happening. I had to slow down and wait for the bundler to finish rebundling each time I save a file before I could save another. Hope this helps someone

Thanks for the hint.
Seems like we need to close the Hot Reloading and close the app. Then open back and it work.

What about redux-persist, is it good ?

Just as an aside, you don't actually have to close your emulator, or even your bundler/builder. Just long press the application (or go to the settings as per usual) open the settings and then "FORCE STOP" the application. If you then just re-open the application on the emulator, the localstorage is back and functioning again. Its been my sort-of-workaround for a while now.

You can write a batch file to do the following
adb shell am force-stop com.
adb shell am start com./com..MainActivity
Run this batch file instead of pressing RR on the emulator

@yashojha19, redux-persist is pretty bad. Too much code for nothing. There is "redux-offline" being a superstructure, more like opinionated interface to popular but unwieldy redux-persist. It doesn't make it better, just because redux-persist is bad at the core.

try {
     console.log('start')
     await AsyncStorage.getItem('token');
     alert('end') // << This never executes!
}catch(err){
     console.log(err);
 }

Same problem. The AsyncStorage.getItem() and the code followed never execute. No error at all.
I'm using react-native-navigation v2 and react native 0.56.

@stonecold123 I'm not sure how script work. Just to confirm.
Did you add AsyncStorage class while import from React Native?
In order to use "await", did you add async function?
Exp:
const fund = async (a)=>{

};

Did you close hot reloading? try close the app and start over again.
Remove the app and try build over again.
Should be work in some cases. For me, I just close app and open again.

@kkusanagi
Yes, the code snippet is inside an async function, and I don't use hot reloading. I have now moved on to use react-native-sqlite-storage to store the json objects. I can't get this specific method AsyncStorage.getItem() to work.

Okay I got into this problem when testing with android device, but so far there isn't any issue with the iOS simulator.
Is this problem only exist in the development mode or is it also happening on production apps?
I guess this only happens in development right? Given that some of the comments before telling about the JS recompiling stuff?

Having same problem while using expo client for my app on android. What happens is sqlite is not on the phone? Do I have to install sqlite with my app just so asyncstorage has a available storage?

Have the same problem on 55 version , and if someone knows an alternative solution , let us know @react-native-bot

Will this ever be fixed ?

Sounds like no one from maintainers interested in this issue.
On Thu, Aug 2, 2018, 2:45 PM Mitla<EMAIL_ADDRESS>wrote:

Will this ever be fixed ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/issues/18372#issuecomment-409877817,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA-MX0MQvcX4rQbIK6zQHAvYJMsXntiJks5uMtEngaJpZM4SqYil
.

Same problem here. Basic usage of AsyncStorage doesn't behave as expected.
(Development setup, using a real iPhone X with live reload enabled)

same problem here，after await AysncStorage.getItem() 's code never executes

For me the problem started when I changed data in Asyncstorage, so I downloaded the Asyncstorage data, to know what data to remove, use Asyncstorage.removeItem to remove the specific data and restarted the application.
Maybe Asyncstorage.clear don't actually clear. Hope it helps.

Hey Guys , I think I found the problem for myself ,it may seems stupid for you but what I did to work is just disable debug JS remotely and without logging my data inside AsyncStorage ,seems it's working every time that I need the data , so the solution for me was to disable Debug JS Remotely on Chrome , then it works perfectly , hopefully it solve other problem .

@Khsed4 Will try this but your solutions seems reasonable as maybe the cache is going to chrome? I know an instance of socket.io treating both the chrome debugger and my emulator as two different clients, and this may be a similar problem.

same here, debug mode emulator NO hot reload. seems timing dependent as on some machines it fails sometimes, on another machine it happens always

+1

Same issue here for react native 0.55.4.
What are some good AsyncStorage alternatives?
I will use the alternative until the fix is done. I used Realm but it is too complicated for simple usage.

I would say that just run react-native run-android again when you see issues pop up and they will be resolved. Also make sure that you don't use implementations from other people when you do a google search for how to store and receive. The newest page on Asyncstorage in React Native docs shows how you should have those async functions (i.e. how to properly do it).

Same issue here. Either getItem async or sync ways it doesn't work as expected. Many time it hangs but no error thrown.

I get a "red screen" error: "the bind value at index 1 is null" - but nothing matching it in the console.

Same problem here lol

do i have another way to replace asyncStorage for this issue?

I had basic asyncstorage commands (getItem, setItem) working last night. Then today they stopped working, which is how I got here. I am now using redux persist and this is successfully persisting the state.
I have experienced the not-working of asyncstorage - but for some reason redux-persist is working as expected.
"react": "16.3.1",
"react-native": "~0.55.2",
"react-navigation": "^2.11.2",
"react-redux": "^5.0.7",
"redux": "^4.0.0",
"redux-persist": "^5.10.0",

So the solution here is to
localdatabase.js
import { AsyncStorage } from 'react-native';
import _ from 'lodash';
export  const setItem= async(key, value) =>{
    try {
        return await AsyncStorage.setItem(key, JSON.stringify(value));
    } catch (error) {
        // console.error('AsyncStorage#setItem error: ' + error.message);
    }
}
export const getItem = async(key)=> {
    return await AsyncStorage.getItem(key)
        .then((result) => {
            if (result) {
                try {
                    result = JSON.parse(result);
                } catch (e) {
                    // console.error('AsyncStorage#getItem error deserializing JSON for key: ' + key, e.message);
                }
            }
            return result;
        });
}
export const  removeItem = async(key)=> {
    return await AsyncStorage.removeItem(key);
}

Use that file as :
import {setItem,getItem} from './localdatabase';
getValuesFromDb= async()=>{
    const key1 = await getItem('1').then((result) => this.setState({ index1: result }));
    const key2 = await getItem('2').then((result) => this.setState({ index2: result }));
    }
  }

Make sure to run

yarn run android or ios everytime you make a change; This makes it easy to write the code and the async storage works without any issues. Also when building for production it works like charm the issue is when you connect the debugger or enable hot loading it fucks up.

Same here, and literally forever. So I need to close the app on Android and open it again every time I reload -.-

Me and my team of 3 RN developers had simultaneously gotten stuck in the same issue, so I wrote a simple FIleSystem based alternative to AsyncStorage named react-native-fs-store module, which is drop-in replacement of asyncStorage for very simple use cases. It also allows automatic switch to actual AsyncStorage in production. I hope it unblocks someone else as well.

Same problem here.
I do a simple setItem then try a getItem
It just returns:
{
"_40":0,
"_65":0,
"_55":null,
"_72":null,
}

But as mentioned by many people for the maintainers it seems storage isn't important and won't be fixed anytime soon.
I recommend using:
MongoDB
SQLite

That's a Promise response. Try getItem(ITEMKEY).then(res => console.log(res)).......... or did you try that?

@goughjo02 same as well I tried but sadly my value is never returned hence I have switched to mongo and it works perfect now

Hmmm i had the same issue.
I tried many different syntaxes you probably got in the previous posts.  No success so far. At first i was incline to throw it away.  Then i tried less complex (imbrication-wise) syntaxes.
I got there and it finally worked for me.
    async componentDidMount() {
        var AsyncVal = await AsyncStorage.getItem("lchMoteurRch");
        await this.setState({ lchMoteurRch: AsyncVal });
        console.log("ControllerXXX/componentDidMount : state.lchMoteurRch=" + this.state.lchMoteurRch + "; AsyncVal=" + AsyncVal );
    }
// -> ControllerXXX/componentDidMount : state.lchMoteurRch=abcdef; AsyncVal=abcdef

and
    async myfunc(itemValue, itemIndex) { // <- from a Picker
        await AsyncStorage.setItem('lchMoteurRch', itemValue);
        await this.setState({ lchMoteurRch: itemValue }); //shown here if you need to set some state.xxx
        console.log("ControllerXXX/myfunc : index=" + itemIndex + "; val=" + itemValue + "; state.lchMoteurRch=" + this.state.lchMoteurRch)
    }

Version:

react-native-cli: 2.0.1
react-native: 0.56.0

with gradle configured like this:

buildToolsVersion = "27.0.3"
minSdkVersion = 16
compileSdkVersion = 27
targetSdkVersion = 27
supportLibVersion = "27.0.1"

It works in "normal debug" mode and variant=release for me.
Apparently minimizing the callbacks usage probably helped. It may not be that elegant but it's working properly. That's not a bad bargain all things considered.
Now, it raises questions about "this.setState" callback. While debugging i was using the setState callback parameter to log to the console the 'state' object supposedly updated values but with no success.
The asyncStorage value was saved, retrieved and passed properly. I could log it to the console in the 'then' statement.
something like : AsyncStorage.setItem('lchMoteurRch', itemValue).then(... ...);
The setState was executing (in a '.then()' statement) but for some reason it did not update the state object. I know the setState method is particular amongst the asynchronous methods. But i wasn't expecting that. Maybe:

1 The setState fired the callback too soon which is weird as it IS supposed to be a callback.
2 The setState did not update anything because it did not execute. Or it was not in the right place / context. Maybe a scope issue... dunno.

I'm left only with question on that. Is it an isolated issue or should we expect different callback behaviors depending on the function used ? Then, where's the doc ???
Well... The solution i found is supposed to do exactly the same. Still... this one worked for me.

I face this issue while I run on this condition :

Remote JS debugging enable
run on an emulator with: npm run android
"react-native": "~0.55.2"

this solution works for me:

Stop remote JS debugging.
close the app on the emulator.
run with react-native run-android
enable remote JS debugging to check the issue.

Experiencing this issue in production with a single AsyncStorage.getItem. Sometimes it works, sometimes it just returns null.

Can we update status of issue? 0.57 is released now, and from the changelog they mentioned AsyncStorage fix. Is the change solve this issue?

Did anyone test 0.57 version ? if it's solved there or no ? they promised that it would be solved.

@Khsed4, yes I have tested my app on 0.57 and it works fine. I have had the problem with previous versions consistently.

@apcjs, nice. I think we can close this issue now?

I'm trying to make this work for a very basic app that I test on expo.
I'm very new to this so pardon me if I'm wrong but for what I understand, It won't work with expo as:

since version 0.56 React Native is using Babel 7 and babel-preset-expo doesn't support Babel 7 (found here: https://github.com/expo/expo/issues/1954).
the fact that version 0.57 is not present in this file: https://github.com/react-community/create-react-native-app/blob/master/VERSIONS.md does not help.
This might be fine for those who use an emulator or an android device directly

you can check this.  storage

I had this problem until I removed all console logs in both my asynchronous functions and logger middleware!

but in 0.57, can you build your android apk? @apcjs @fikrikarim

@farzer yes, I'm able to build an APK using 0.57. This was never a problem for me in previous versions. The issue I had was with reading a value from asyncStorage once you reload the app using RR. The promise never got fulfilled. This was consistently failing for me. With 0.57, it works fine.
Also note that I did not upgrade from 0.55.4 to 0.57. I ran react-native init and copied my source code from the old folder. Not sure if that makes a difference.

for me, upgrade to 0.57 meet another problem. see #19211

by converting data to stringify and then setItem ......
and after getting it converting it back work for me ....
setting data:
AsyncStorage.setItem('saveData', JSON.stringify(value));
getting data:
AsyncStorage.getItem('saveData').then((value) => {
    data=JSON.parse(value);

}).done();
worked for me...

Hey Guys , I think I found the problem for myself ,it may seems stupid for you but what I did to work is just disable debug JS remotely and without logging my data inside AsyncStorage ,seems it's working every time that I need the data , so the solution for me was to disable Debug JS Remotely on Chrome , then it works perfectly , hopefully it solves other problem .

after build APK again facing same issue. is there any other alternative solution?

0.57.1 not fixed yet...

@sunithakk sorry for my late reply.
I was stuck with this stupid problem for almost one week , no way that is suggested in all communities worked for me , but then I found something that is built in with setState() function , which it has a callback function as this website says : https://medium.learnreact.com/setstate-takes-a-callback-1f71ad5d2296.
so the only way that I guarantee that it's the only secure way so far is this that u use the setState() function in your promise and everything that you need to run , put them on a function and call it for the setSate() callback function , this is only way you can make sure yourself that you neither get null nor never calling the function . Here I'm going to provide an example for it .
` try {
AsyncStorage.getItem('firebase_token', (err, item) => {
if (item) {
this.setState({
firebase_token: item,
}),this.tokenToServer();
}
});
} catch (error) {
  console.log("Error retrieving data" + error);
}`

same here

I have upgraded react-native to 0.57. The problem still persist, happen sporadically. and some devices not working.

Hello everyone,
Is there a workaround for this issue?
Thanks.

Hello,
Is there a workaround for this issue?
Thanks.

@sandersjj try Expo SecureStorage. Alternatively, make sure you eject from expo, and then set and get a very simple standard key when your app loads. For some reason if you can get a full cycle in, it works perfectly (I thin k it has something to do with initializations and failures being blocking on the UI thread, but have no real clue why this works).

@pshah123 how to use Expo SecureStorage in a native app?

Still face the same issue
async componentDidMount() {
try {
let cities = await AsyncStorage.getItem(key);
cities = JSON.parse(cities);
this.setState({ cities });
} catch (e) {
console.log("error from AsyncStorage: ", e);
}
}
$ react-native --version
react-native-cli: 2.0.1
react-native: 0.57.4

@sunithakk sorry for my late reply.
I was stuck with this stupid problem for almost one week , no way that is suggested in all communities worked for me , but then I found something that is built in with setState() function , which it has a callback function as this website says : https://medium.learnreact.com/setstate-takes-a-callback-1f71ad5d2296.
so the only way that I guarantee that it's the only secure way so far is this that u use the setState() function in your promise and everything that you need to run , put them on a function and call it for the setSate() callback function , this is only way you can make sure yourself that you neither get null nor never calling the function . Here I'm going to provide an example for it .
` try {
      AsyncStorage.getItem('firebase_token', (err, item) => {
        if (item) {
          this.setState({
            firebase_token: item,
          }),this.tokenToServer();
        }
      });
      } catch (error) {
      console.log("Error retrieving data" + error);
    }`

Actually m storing data in separate javascript file. not inside component. pls find below code.
import React from 'react';
import { AsyncStorage, Text, View, TextInput} from 'react-native'
var SQLite = require('react-native-sqlite-storage')
const LocalStorage = {
retrieveData : async (value) => {
try {
const value = await AsyncStorage.getItem('myKeySpl');
  if (value !== null) {

    return JSON.parse(value);
  }else{
    return false;
  }
 } catch (error) {
  return false;
 }

}
}
module.exports = LocalStorage;
your solution is not working here....

kkkkkk

i am also experiencing this problem any updates?

Hello everyone, same issue here with RN 56.0.
[...]
console.warn('Before user_id')
const user_id = await AsyncStorage.getItem(USER_ID)
console.warn('After user_id')
[...]

App log "Before user_id" and can't go further. It looks like the AsyncStorage promise is never resolved in some case. Which is really blocking. Anyone using an alternative to AsyncStorage ?

i think realm is the best choice.
2018-11-29 23:16 GMT+07.00, Olivier PASCAL<EMAIL_ADDRESS>
Hello everyone, same issue here with RN 56.0.
[...]
console.warn('Before user_id')
const user_id = await AsyncStorage.getItem(USER_ID)
console.warn('After user_id')
[...]

App log "Before user_id" and can't go further. It looks like the
AsyncStorage promise is never resolved in some case. Which is really
blocking. Anyone using an alternative to AsyncStorage ?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/facebook/react-native/issues/18372#issuecomment-442892950

--
Rustan, S.Si.

To all of those still experiencing the issue, the SecureStore from Expo is a viable alternative, which has APIs signatures very similar to AsyncStorage and already comes bundled with Expo. That solved the issue for me.

I'm also facing the same issue. Is there any update on this or maybe a workaround (other than using expo version) ? Thanks

I also encountered the same issue. I was binding an async function in the UI of  one screen. So whenever I was navigating to that screen, the app was getting stuck and restarting the app was not working. It was working only if i restart the expo app and then the project app.
Please check whether an async function is getting invoked on render or not. That could be the issue of AsyncStorage not fetching any item because the previous async has not completed yet. Thanks.

same issue......
in rn 0.57.8

Experiencing the same issue, AsyncStorage is just unusable.

@hramos why is the bug report label removed when the issue is not resolved :(
It's a really critical issue that needs more attention than it has been given so far

Hellp all,
I have had this issue once too making the app in production go freeze. what
a day that was.
what worked out for me for temporary solution was instead of getting and
setting value from asyncstorage. I used React natie file system (RNFS) and
used it as reading and writing file in app reserved root space which is not
accessible through file managers, and you're anyway going to store auth
tokens here or even you can encrypt/decrypt your stringified json there.
On Tue 16 Oct, 2018, 02:57 Farzad Qasim<EMAIL_ADDRESS>wrote:

same problem in expo
"react-native": "https://github.com/expo/react-native/archive/sdk-30.0.0.tar.gz",
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/issues/18372#issuecomment-430018954,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKauliyAL9MEA3L6T2GKK6nvC5E5Fa7Jks5ulP2xgaJpZM4SqYil
.

Problem is not getItem, the problem is setItem or that I think.
The difference between getItem and setItem is that set not return something (except a null). So, the await of setItem never pass to the next set. Actually, even never set the data.
So, the solution (at least for me) is: not to use await in setItem.

At last some valuable information! Thanks @Georgge

iOS simulator (iPhone X) works perfectly, but on a real iPhone 6, it fails (storage is empty after going to another screen or reloading).

This issue has been moved to react-native-community/react-native-async-storage#12.

To fix the live reload - switching to async await worked for me.
Checked this SO Answer

Have you remembered to put the item in asyncstorage as string (JSON.stringify) and when reading the parse item (JSON.parse) ?? this may be the mistake of many.

Problem is not getItem, the problem is setItem or that I think.
The difference between getItem and setItem is that set not return something (except a null). So, the await of setItem never pass to the next set. Actually, even never set the data.
So, the solution (at least for me) is: not to use await in setItem.

great !!! you save my day

//Login.js
..
onClickListener = (viewId) => {
AsyncStorage.setItem('logeado', JSON.stringify(this.usuario.auth));
AsyncStorage.setItem('usuario', JSON.stringify(this.usuario));
}
..
//Welcome.js
...
constructor(props) {
super(props);
this.state = {
  loading: false,
   usuarioSesion : null
}
this._bootstrapAsync();

}
_bootstrapAsync = async () => {
const usuario = await AsyncStorage.getItem('usuario');
Alert.alert("json",JSON.parse(usuario));
this.setState({usuarioSesion :usuario});
};
salir = () => {
AsyncStorage.removeItem('logeado');
AsyncStorage.removeItem('usuario');
this.props.navigation.navigate('AuthLoading', {});
}
its works for me.

I don't know what will be solution in your case but this one worked for me
Firstely i was importing some componets from react-native like this
import { Text, StyleSheet, TouchableHighlight, TextInput, } from 'react-native';
import {  AsyncStorage } from 'react-native';
and the AsyncStorage.getItem or AsyncStorage.setItem was not working, whatever code was there after AsunStorage was not running, so
I Modified my import like to this
import { Text, StyleSheet, TouchableHighlight, TextInput, AsyncStorage  } from 'react-native';
and now everything was working fine.
I don't know how it got resolved, but my  AsyncStorage.setItem and AsyncStorage.getItem both was working fine
AsyncStorage.setItem('DEMO', 'false');
try {
let data = await AsyncStorage.getItem("DEMO");
alert(data);
}
catch (error) {
    }

Hi everyone,

Problem is not getItem, the problem is setItem or that I think.
The difference between getItem and setItem is that set not return something (except a null). So, the await of setItem never pass to the next set. Actually, even never set the data.
So, the solution (at least for me) is: not to use await in setItem.

Not just this I think. I've used your solution, but getItem('key', callback) and getItem('key').then() also doesn't work. Also it does'nt work directly inside componentDidMount hook. It become working when I've took this away to another function like this:
_getItem = async function () {   const result = await AsyncStorage.getItem('key')   return result } componentDidMount () {   this._getItem().then((result) => {     <so something with result> }) }

I found solution for this
Use this link https://github.com/react-native-community/async-storage/blob/LEGACY/docs/advanced/DedicatedExecutor.md

Even the custom Hooks (UseStorage) in React Native causing the same Problem.
import {useState, useEffect} from 'react';
import {AsyncStorage} from '@react-native-community/async-storage';
/* Hook for AsyncStorage */
const useStorage = (key, defaultValue) => {
const [storage, updateStorageValue] = useState(defaultValue, '');
async function getStorageValue() {
let value = key || defaultValue;
try {
  value = JSON.parse(await AsyncStorage.getItem(key)) || defaultValue;
} catch (e) {
} finally {
  updateStorageValue(value);
}

}
async function updateStorage(newValue) {
try {
if (newValue === null) {
await AsyncStorage.removeItem(key);
} else {
const value = JSON.stringify(newValue);
await AsyncStorage.setItem(key, value);
}
} catch (e) {
} finally {
updateStorageValue(newValue);
}
}
useEffect(() => {
getStorageValue();
}, [getStorageValue]);
return [storage, updateStorage];
};
export default useStorage;


Fix CI intermitent failures on SGE

As stated in several places like in https://github.com/dask/dask-jobqueue/pull/466#issuecomment-701529961, SGE CI is regularly failing.
We should try to solve this, help is welcomed!

Closing this one has duplicated of #484 which has more details provided by @lesteve.

Closing this one has duplicated of #484 which has more details provided by @lesteve.


[6R2yEhGU] No procedure with name ... registered for this database instance

https://trello.com/c/6R2yEhGU/40-s3ria-financialno-procedure-with-name-xxxxx-registered-for-this-database-instance
Sometimes it can happen that during the refresh the system database has discrepancies with the cache (i.e. registeredProcedureSignatures and registeredUserFunctionSignatures) and therefore some procedures/functions are mistakenly de-registered.

Added synchronized in restoreProceduresAndFunctions, storeFunction and storeProcedure methods

Closed in favor of 4.4 analog https://github.com/vga91/neo4j-apoc-procedures/pull/384


Add a way to add custom contexts to all events

e.g.
snowplow('registerCommonContext', myContext);
snowplow('registerCommonContext', myContextGeneratingFunction);

I like!
How about:
snowplow('attachContext', '*', myContext);
snowplow('attachContext', myFilterFunction, myContextGeneratingFunction);

What does myFilterFunction filter?

If myFilterFunction returns true, attach the context. TBC the arguments passed to myFilterFunction.

@yalisassoon, @bogaert - feedback please!

I love it.
When users implement the JS tracker through GTM, a common pattern is to have some JS at the top of the page that constructs the contexts array out of the different objects in the dataLayer. Pseudocode looks something like this:

Create empty contexts array
If dataLayer array contains user object add schema to it and push it onto contexts array
If dataLayer array contains product object add schema to it and push it onto the contexts array
...

Then add the context to any subsequent track methods called in the tag.
So anything that simplifies the process of building the contexts array prior to firing the track methods is useful.

Bringing forwards

Team at Snowflake Analytics has expressed an interest in this. (And equivalent functionality in Objective C and Android trackers.)

See also: https://github.com/snowplow/snowplow/issues/3852

Hi there. There is "Global contexts" in the Snowplow 2.10.0 documentation - https://github.com/snowplow/snowplow/wiki/2-Specific-event-tracking-with-the-Javascript-tracker
I checked 2.10.0-rc1 for "addGlobalContexts" event but didn't find it or other global context functionality.
Will "Global contexts" be implemented in 2.10.0?


Update terratest to '>= 0.46.0'

what

Update terratest >= 0.46.0

why

Support OpenTofu for testing

References

https://github.com/gruntwork-io/terratest/releases/tag/v0.46.0
DEV-374 Add opentofu to all our Terragrunt Testing GHA matrix

/terratest


Report the manifest name when Addon enabling failed

Describe the bug

I hit an issue when enabling addon observability.
➜  addon-development git:(master) vela addon enable observability domain=abc.com
Error: fail to dispatch dependent addon resource: render addon definitions fail: yaml: invalid map key: map[interface {}]interface {}{".Values.systemDefinitionNamespace":interface {}(nil)}

By looking up all files, the error came from a trait definition xxx.yaml while the manifest name was included in the error message. For better development experience, it should be included.
To Reproduce

Expected behavior

Screenshots

KubeVela Version

Cluster information

Additional context

When the enabling going well, the manifest name is included. When errors occurred, the name did help.
I1223 10:45:24.520997   50671 apply.go:106] "patching object" name="pure-ingress" resource="core.oam.dev/v1beta1, Kind=TraitDefinition"
I1223 10:45:24.627017   50671 apply.go:106] "patching object" name="register-grafana-datasource" resource="core.oam.dev/v1beta1, Kind=TraitDefinition"

/assign


Can't instantiate abstract class BaseLanguageModel

I'm receiving this error when I try to call:
OutputFixingParser.from_llm(parser=parser, llm=ChatOpenAI())
Where parser is a class that I have built to extend BaseOutputParser. I don't think that class can be the problem because of the error I am receiving:
File "pydantic/main.py", line 341, in pydantic.main.BaseModel.init
pydantic.error_wrappers.ValidationError: 1 validation error for LLMChain
Can't instantiate abstract class BaseLanguageModel with abstract methods agenerate_prompt, generate_prompt (type=type_error)

        Hi there,

Thank you for bringing this issue to our attention. It looks like you are trying to instantiate an abstract class, BaseLanguageModel, which is not allowed. Abstract classes are classes that contain one or more abstract methods. Abstract methods are methods that are declared, but contain no implementation.
In order to fix this issue, you will need to create a concrete class that extends BaseLanguageModel and implements the abstract methods. You can find more information about abstract classes and methods in the Python documentation.
I hope this helps! Let me know if you have any other questions.
Best,
[Your Name]


refactor: upgrade pipeline catalog sha to upgrade go version

Signed-off-by: ankitm123<EMAIL_ADDRESS>Related to https://github.com/jenkins-x/jx/issues/8283

/approve


chore: release 0.1.3

:robot: I have created a release *beep* *boop*
0.1.3 (2021-11-27)
Features

is_anagram (a128298)
converts a string to camelcase (6c5bbe1)

Continuous Integration

add release-please (c7d326c)

This PR was generated with Release Please. See documentation.

Codecov Report

Merging #1 (8475226) into master (c7d326c) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master        #1   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            4         4
  Lines           33        33
=========================================
  Hits            33        33

Continue to review full report at Codecov.

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

:robot: Release is at https://github.com/azzamsa/30-seconds-of-rust/releases/tag/v0.1.3 :sunflower:


How to Global Search?

Like the search on the Telegram homepage, global search can be performed.Which API interface should I use?

The search on the chat page is searchRecentlyFoundChats + searchChats + searchChatsOnServer + searchPublicChats + searchMessages + searchSecretMessages.

聊天页面上的搜索是searchRecentlyFoundChats + searchChats + searchChatsOnServer + searchPublicChats + searchMessages + searchSecretMessages.

Thank u.  The searchChatsOnServer interface only returns data once when searching for the same content. Do developers need to save the returned data in the database themselves to avoid duplicate searches? Is there another interface for querying tdlib's saved search results?

You don't need database. You must add results from the mentioned request in the specified order. skipping previously received chats, users and messages.

You don't need database. You must add results from the mentioned request in the specified order. skipping previously received chats, users and messages.

Why sometimes using searchChatsOnServer to search does not return data, while using tg to search results in data? Is this a problem with the limit parameter? How should limit be written?

//@description Searches for the specified query in the title and username of already known chats via request to the server. Returns chats in the order seen in the main chat list @query Query to search for @limit The maximum number of chats to be returned
searchChatsOnServer query:string limit:int32 = Chats;

The method works as documented. It can return only chats from the chat list.


Not able to use lodash or jquery inside interpolations in .vue files

https://github.com/JeffreyWay/laravel-mix/issues/417

Thanks for filing the issue. Please follow the Issue Reporting Guidelines and provide a minimal JSFiddle or JSBin containing a set of reproducible steps that can lead to the behavior you described.
Why is this required?

Please ask questions on the forum or StackOverflow.

Do Vue.prototype._ = _ to use lodash as $_ in templates. But I recommend you to define your own filters/methods that use lodash methods instead


Major HP Tool Refactoring

Better organized outputs (csv, image, video subdirectories)
Fixed bug where exiftool would run over entire directory, instead of
just selected
Validation
Input & Output dirs remembered in prefs
OO Refactoring
Thumbnails/Names displayed when a row is selected in a spreadsheet
T/F Hotkeys
Open old spreadsheets without running hp_data process

Changelog (final version):

Better organized outputs (csv, image, video subdirectories)
Refactoring
Fixed bug where exiftool would run over entire output directory, instead of just new images
Validation
Input & Output dirs remembered in prefs
Thumbnails/Names displayed when a row is selected in a spreadsheet
Can fill spreadsheet selections with True/False with Ctrl-t/Ctrl-f
Open old spreadsheets without running hp_data process
New columns: CustomRendered, CameraKinematics
Spreadsheet window is expandable w/ click and drag
Preferences and metadata now edited internally (File-> Settings or Edit Preferences button)
Fixed bug where keywords sheet was being overwritten if ran multiple times


Fix AsyncHTTPConduit read timeout with exhausted connection pool

Fix for CXF-7122

@ffang : can you review this to make sure this doesn't conflict with or duplicate the async changes you already made this week.

Hi,
thank you for reviewing this merge request. I have been able to reproduce the problem even with the code using the timer task to remove the callback from the exchange.
About the merge request, I cannot reproduce the failing test org.apache.cxf.systest.jaxrs.sse.tomcat.TomcatBroadcasterTest.testBooksStreamIsBroadcasted on my environment.


Mouse pointer inconsistent

Current Behavior
menus on same page show different pointers

Expected Behavior
same pointer on all drop downs
Steps To Reproduce

Visit project/xxx-xxx-xxx-xxx/snapshots or project/xxx-xxx-xxx-xxx/device
inspect the action menu and table kebab menu

Environment

FlowForge version: latest-git
Browser: chrome

This is because the main project action menu is still using the old DropdownMenu component - not the component provided by forge-ui-components.
As such, this is not an issue for forge-ui-components - I will move over to the flowforge repo.


Rework the PIO API

Rationale
The current PIO API has a number of limitations:

As the state machines are contained in PIO, they cannot be moved around individually. Sometimes, a single PIO block implements multiple functions that are used in completely different parts of the code base.
StateMachine is not Send, although it could be.
Multiple state machines should be able to share code to reduce instruction space usage, yet currently they are not because PIOBuilder always allocates space. Sometimes, multiple state machines implement the same functionality (e.g., multiple SPI or I2C buses).
Some functions must only be called in specific configurations. For example, pin directions have to be set while the state machine is stopped, as PINCTRL is modified. The current API does not reflect such restrictions, which makes it harder to use than necessary.

Also, during my work, I found a bug where used instruction space was not marked properly.
This PR also fixes #141 by providing a function to set pin directions.
Design
This PR uses different types to represent state machines in different states - UninitStateMachine<P> is not associated with any program, whereas StateMachine<P, Stopped> and StateMachine<P, Running> are. Program installation in instruction memory is separated from state machine initialization via InstalledProgram and PIO::install(). Access from state machines to shared registers is performed via atomic operations to enable Send.
Old usage example:
let pio = rp2040_hal::pio::PIO::new(pac.PIO0, &mut pac.RESETS);
let sm = &pio.state_machines()[0];
let div = 0f32; // as slow as possible (0 is interpreted as 65536)
rp2040_hal::pio::PIOBuilder::default()
    .with_program(&program)
    .set_pins(led_pin_id, 1)
    .clock_divisor(div)
    .build(&pio, sm)
    .unwrap();

New usage example:
let (mut pio, sm0, _, _, _) = pac.PIO0.split(&mut pac.RESETS);
let installed = pio.install(&program).unwrap();
let div = 0f32; // as slow as possible (0 is interpreted as 65536)
let sm = rp2040_hal::pio::PIOBuilder::from_program(installed)
    .set_pins(led_pin_id, 1)
    .clock_divisor(div)
    .build(sm0);
sm.start();

Testing
I tested that the blink examples work, and I tested with my own code that, however, does not use much more PIO functionality yet (except for sideset pins). Those programs work fine.

The new example in this PR currently depends on rp-rs/pio-rs#9, so the two PRs should be merged together.

Apparently there are already issues for rp2040-pac and svd2rust.

Thanks a lot for the review. I will fix those bugs this evening.
After submitting the PR, I started to think about integrating DMA. While doing so, I noticed that the API needs some further restructuring. In particular, TX and RX FIFOs need to be managed by different objects than the state machine itself, so that the user is able to use TX and RX DMA in parallel. For example, an API such as the following may be possible:
let (sm, rx, tx) = rp2040_hal::pio::PIOBuilder::from_program(installed)
    .set_pins(led_pin_id, 1)
    .clock_divisor(div)
    .build(sm0);
let rx_dma = rx.read_with_dma(buffer);
sm.start();
// ...
let rx = rx_dma.wait().
let sm0 = sm.uninit(rx, tx);

However, in the last line, the API should ensure that only the right rx and tx objects can be used. This could, for example, be done by adding another generic parameter, where there would be the following types and sm.id would be removed:
UninitStateMachine<PIO, SM0>
StateMachine<PIO0, SM0, Running>
PIOTx<PIO0, SM0>

etc.
That, however, means that any function/type that receives a state machine object needs to be parametrized for the specific state machine index. I do not think that this would be a large problem, as we already have similar behavior for objects/functions operating on GPIO pins, where they need to be written as generics which take a specific GPIO pin type.
What do you think?

Oh, and with regards to MSP430 atomics: The scenario is somewhat different as MSP430, if I understand it correctly, uses atomic instructions to operate at the same addresses, which is probably much easier to implement in svd2rust. This kind of atomic register access (register aliases) would probably have to be implemented in rp2040-pac, but I have no idea how that would be done.

I think having everything be generic over the state machine won't be a problem. As you said, similar API is used elsewhere. Maybe one way to make it little easier to use would be to have types PIO0SM0, PIO0SM1, etc. and be generic over those instead. This way a function taking a state machine could have signature
fn foo<SM: ValidStateMachine>(_: StateMachine<SM, Running>) {}

instead of
fn foo<PIO: ValidPIO, SM: ValidStateMachine>(_: StateMachine<PIO, SM, Running>) {}

Regarding the atomics, I think I managed to hack something together already, though it is currently still a hack. Basically I just copied https://github.com/rust-embedded/svd2rust/blob/master/src/generate/generic_msp430_atomic.rs, changed the writes to something like
self.register
    .as_ptr()
    .add(0x2000 / core::mem::size_of::<REG::Ux>())
    .write_volatile(bits);

and force-added the file to every compiled crate. This has a couple of problems I haven't resolved yet: The most obvious one is that not every PAC crate should have this added, so a new flag or target needs to be added. More subtle problem is that the RP2040 documentation states that SIO device doesn't support atomic access (as it already is atomic by design), so this API shouldn't be exposed for SIO device.

I added parametrization for the state machines. I have to admit that my type design skills are not really great, so someone might want to check whether that's really the most elegant way to specify state machine indices.
Currently, the state machines still carry references around to the registers:
block: *const rp2040_pac::pio0::RegisterBlock,
sm: *const rp2040_pac::pio0::SM,

These fields have basically become unnecessary now, I will remove them in the next commit.

If you need atomics, what you'll want is the atomic- polyfill crate. It's not multi-core safe, but we are planning on making a fork that is.

and force-added the file to every compiled crate. This has a couple of problems I haven't resolved yet: The most obvious one is that not every PAC crate should have this added, so a new flag or target needs to be added. More subtle problem is that the RP2040 documentation states that SIO device doesn't support atomic access (as it already is atomic by design), so this API shouldn't be exposed for SIO device.

Definitely sounds like something that should be opt-in.
I was thinking more along the lines of using svdtools to copy the peripheral, add a suffix _or, and change the peripheral offset. That would work with current svd2rust, won't break any existing uses but might make the interface a little less nice to deal with.

How many registers do you need to add this for? Adding a few isn't a big deal.

Currently, the code only needs atomic access to the CTRL register.

Definitely sounds like something that should be opt-in.

Exactly. My implementation was just a quick POC to just check whether adding atomic methods to PAC is possible or not.

I was thinking more along the lines of using svdtools to copy the peripheral, add a suffix _or, and change the peripheral offset. That would work with current svd2rust, won't break any existing uses but might make the interface a little less nice to deal with.

I don't think copying the peripheral should be the first solution. Especially as then the Peripherals struct would have both PIO0 and PIO0_or fields, and both would need to be given to HAL, degrading the UX of the HAL greatly. Otherwise the user could use PIO0_or and PIO0_nand to modify the registers even if they had given access to PIO0 away.
Instead I suggest that the SVD file should contain an attribute for every register telling whether the register has atomic counterparts or not. This would then instruct the codegen to implement AtomicAccess trait on the register, allowing us to gate the access to the atomic methods by this trait. I'm just not familiar enough with SVD to know whether this is possible, or how difficult that would be to implement.

@mgottschlag Could you add an entry to the changelog for this?
I want CI to run with the latest pio-rs now that https://github.com/rp-rs/pio-rs/pull/9 is merged, after that I think this PR is good merge.

I added a changelog entry.

I will have a look at the failures this evening.

I fixed all clippy warnings, except for two warnings about very complex types that I somehow can't see in the CI output. I also marked most doc comment code examples as ignore, except for one which extended with use statements and a simple PIO program and marked as no-run.
I told clippy to ignore the return types of split() and build(), as those tuples are too complex for clippy. We could also package those into structs, but I do not think that it would help make the code more readable. GPIOs are placed into a struct instead of a tuple, for example, but there is no free() method for GPIOs. Here, there is, and that method simply expects the variables as returned by split() at the moment, and I think this symmetry is good.


How to set application icon in .net

hi,
How to set application icon like this
int main(int argc, char *argv[])
{
QCoreApplication::setAttribute(Qt::AA_EnableHighDpiScaling);
QGuiApplication app(argc, argv);
app.setWindowIcon(QIcon(":/favicon.ico"));
QQmlApplicationEngine engine;
engine.load(QUrl(QLatin1String("qrc:/main.qml")));

return app.exec();

}
thanks

I had similar issue and solved it by writing my  own plugin by overwriting QQuickWindow. I've used the plugin instead of ApplicationWindow in qml.  In the plugin class, you can easily set the windowIcon.

After that you can set the icon path in qml:

@MosiQt do you mind going in a bit more detail about the process? Newbie here.

An upcoming version of QML.net will have app.SetWindowIcon(png path) method that makes this simpler.


How to start services in local like NGUI with VITE_proxy in .env?

Hello @shadabmalik096rs
Here's a small guide to help you get started

Navigate to NGUI Directory:

cd ngui/ui

Configure Environment Variables:
Ensure that you set up the necessary environment variables. For local development, it should be sufficient to specify the VITE_PROXY variable. For detailed guidance on configuring the VITE_PROXY variable, please refer to this link.

Install Dependencies:
Make sure you have pnpm and node installed, we are currently using<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

pnpm i --frozen-lockfile

Start NGUI Project:

npm start

Yes ngui for front end But i want make changes in rest_api classes and test them via postman in my local machine?

You may build the custom version of the rest_api.

add your code to optscale repo
run . build.sh rest_api from optscale folder to build the new rest_api:local image on your local machine
delete current restapi pod via kubectl delete pod

The new restapi pod will include your changes.


createblog.html

@aditijhaa9901 Appreciate the PR, although this task was assigned to someone else.
Please ensure that you claim the task before working on it. If there aren't any tasks available feel free to create an issue, claim it and work on it.


Can't fetch buffer

Hello,
I am fairly new to Python and harvesters so there is a good chance I am doing some simple mistake.
I am using Allied Vision camera Manta_G-125B, it is GigE Vision camera. When I run following code, it gets stuck at cam.fetch_buffer(). When I tried changing Width and Height parameters to 8 or 16 it worked, but only sometimes (like once it did then 4 times not then twice did etc. etc.). Am I doing something wrong or is my camera just unsupported?
Also the camera was tested in Vimba Viewer and works.
from harvesters.core import Harvester

h = Harvester()
h.add_file('C:/Programy/Allied Vision/Vimba_4.0/VimbaGigETL/Bin/Win64/VimbaGigETL.cti')
h.update()
print(h.device_info_list)
cam = h.create_image_acquirer(0)

cam.remote_device.node_map.Width.value = 760
cam.remote_device.node_map.Height.value = 500
#works sometimes when set to small number (like 8 or 16)

cam.remote_device.node_map.PixelFormat.value = 'Mono8'

cam.start_acquisition()

with cam.fetch_buffer() as buffer:
            #2D component of acquired data
            component = buffer.payload.components[0]
            print(component.data)

cam.stop_acquisition()
cam.destroy()

h.reset()

input('Exit')

Hi,
I got the same problem, I'm using an Allied Vision camera (Manta G-319C).
The exception (crash) you are talking about comes from component = buffer.payload.components[0].
The exception is:

I found out where the problem is, however as of now I didn't find the solution in Harvester. If I use Allied Vision supplied API and modify the GVSPPacketSize node to 1500 (defaults to 8800) the frame acquisition is successful. The problem now is that Harvester is throwing exception that this node does not exist. Is there any way to list all available nodes? I suspect, that my camera uses some non-standard nodes that are not supported in genicam/Harvester by default.

@xlukas10 Hi, maybe you can change packet size through a GenICam node that the GenTL Producer exposes. I will write some more later. /Kazunari

@mrevah Hi.

Is there any way to list all available nodes?

dir(ia.remote_device.node_map)  # ia: an ImageAcquire object

should give you a list of feature nodes that the remote device, i.e. the camera has. /Kazunari

Thank you a lot. It works now. If someone has the same problem, the node that has to be edited is GevSCPSPacketSize.

Thanks for the hint. I tried to use Vimba to modify the GevSCPSPacketSize value to 1500, but seems like the program still stuck at fetch_beffer() step.
I tried to use wireshark to inspect the packets, the Control Channel Privilege register indicate the "Control Access" filed is False and followed by an "Access Denied" message from remote device. Tried to use the Vimba to capture the image with same GevSCPSPacketSize value and it works fine.
Any hints on cause of failed to fetch_buffer() even when GevSCPSPacketSize is set to 1500? Also I did not find a way to edit the CCP(Control Channel Privilege) register to debug if that is the root cause, any suggestions are appreciated.

About the issue with the packet size: You should make sure to enable Jumbo frames on the network adapter (On windows that is via device manager -> right click the network interface the camera is connected to -> properties -> Advanced -> Jumbo Packet -> choose the max size (9014 for me).
Not sure whether it fixes your problem, but I know that it fixes a lot of issues for us.