Support for Shadow Root

Since there was no direct way to define Shadow Root in SitePrism, I handled it by adding an option.
I would appreciate it if you could inform me about the following concerns:

When obtaining the Shadow Root, I am using the Capybara::Node::Element#shadow_root method, which requires Capybara version 3.37.0 or later. It also requires Ruby version 2.7 or later. Therefore, may I change the required_ruby_version in SitePrism? Are there any alternative solutions available?
(I was also considering making changes to determine the availability of :shadow_root based on the Ruby version.)
FYI: https://github.com/teamcapybara/capybara/blob/master/History.md#version-3370
In the current implementation, the inclusion of :shadow_root as an argument in the existing section method allows for achieving the functionality. However, do you think it would be better to separate it into a separate method, similar to iframe?

This is my first time contributing to an OSS, so I may have other areas where I lack experience. Nevertheless, I appreciate your support and guidance. Thank you :)

Hi there. I've been paying attention to the shadow root stuff in the last year or so in selenium (I was more active pre-covid there).
What I would say is first of all.

we're looking into doing a lot of bug fix / optimisation work in the coming months, no real new features

caveating this, with I'm already planning the next big major release as I want to chop up the massive internal DSL module

I've never really "got" into the shadow root stuff. So it's likely when I start scaling back on my full-time work (About 3/4 weeks time), I'll maybe put some time into learning some of this stuff
All minimum versions are just that, minimum versions. So in theory if this stuff works on 2.7 and later versions of capybara then we're all happy.

Not disregarding any of this, just for the short-term (2-4 weeks), I will unlikely have time to learn/study any of this. Please feel free to continue and work async on anything here, I'll happily accept/support

Thank you for your reply! It seems there are various circumstances involved.
Of course, I would like to continue this initiative, so please count on my support going forward!

5 second view is looks good :+1:
My first piece of large refactor work is also tentatively pushed up which will just move a lot of code around, in this PR I'll be doing some dependency / ruby updates, so you "shouldn't" have to worry about these (Maybe, not 100% sure).

I haven't forgot about this. I promise.
I think it'll be easier for this to land in a v5 beta - purely because large changes by and large are good then plus it will remove a reasonable amount of complexity for you? WDYT? @souchan2000

@luke-hill Thanks for the message. I also think it would be better to implement it in v5 beta.

In which case I'm going to start merging all of my beta branches in in the next week or so. If you check back in about 2 weeks you'll notice the main part of the repo will be very muddy, but should have dependencies that are a lot larger and will hopefully help you then.

I've addressed the review comments, but is this correct? I might have misunderstood something.

@luke-hill  I've addressed the review, so please take a look when you have time.

Thanks, have approved and got CI to run. I have some other priorities atm. Namely cutting and releasing v5 beta first.
Once that's done I'll come back to this and get it in for v5 proper

So predictably we need some form of graceful fallback.
Or failing that if you know the version you want this to target we can delay it until then?

The CI for Gemfile.low_spec is failing. Should I fix the Gemfile.low_spec?

It's failing because the version in the low spec gemfile is not compatible. The gemfile isn't broken itself, it's the code needing to have a graceful fallback.
So we either need to .....

When a "too low" version of capybara is used and shadow root is used

Permit this, but just don't make it a shadow root. Throw a warning in logger
Do not permit this, throw a custom error

Acknowledge this is a build error. And treat it like other build errors that v4 started throwing with the env var config.

I apologize for the delayed response.

Permit this, but just don't make it a shadow root. Throw a warning in logger
Do not permit this, throw a custom error

Assuming we address one of these options, I anticipate the CI will consistently fail. Do we have a plan of action for handling this? (e.g., skipping it)

You omit certain test runs by throwing a pending exception for cucumber tests. This returns an exit code of 0 for the scenario.

I've addressed it,  https://github.com/site-prism/site_prism/pull/159/commits/e95da1eb1a687e59479733b511e6a7538180bf45
How does it look like now?

Can you enable contributions on your branch. I think you're misinterpreting what to do. It's probably easier I just fix up the remaining items.

I apologize for any inconvenience.
I should have contributions enabled on my branch, so please proceed accordingly. Thank you.

Thankyou @souchan2000 this is now merged into main


Use Tailwind CSS?

Any interest in using Tailwind CSS for the front-end for this? If so, I’ll happily submit a PR getting it all set up.

That's very kind of you.  I need to research Tailwind more. I've never used it myself.
Let me have a think and get back to you about this


Cover basics of SNS and push notifications

@alexanderatallah another you might have great expertise on. :)

Where would this be placed in the list of Specific AWS Services? (See also #304)


Titles scroll vertically if in UINavigationController

If you put your custom ViewController inside UINavigationController you will be able to scroll title labels vertically
@interface BTBViewController() <TTSlidingPagesDataSource, TTSliddingPageDelegate>
...
[[UINavigationController alloc] initWithRootViewController:[[BTBViewController alloc] init]]

solution is to add a line of code into TTScrollSlidingPagesController
topScrollView.pagingEnabled = YES;
new line ---->  topScrollView.scrollEnabled = NO;

Trying to get this work for iOS 9, and I'm getting the vertical scrolling issue.
@kentarokai : which viewController are you referring to?


[ENH] extendin deep_equals for ForecastingHorizon

Solves issue #2215, ensures that deep_equals returns the correct output if the nested structure contaians ForecastingHorizon somewhere.
The utility uses recursion, making use of the fact that two ForecastingHorizon are equal iff their _value (pandas or numpy container) and is_relative (bool) attributes are equal.
The extension avoids importing the ForecastingHorizon, ensuring that the deep_equals utility does not have an sktime dependency.
(for reviewers: that's why type(x).__name__ is used and not isinstance)

FYI @ltsaprounis, this is what you needed, right?
Turns out I also needed it here #2207 😄

Thanks @fkiraly! this is really good and I need it for #2197!
Left one minor comment/question.


[backport-target] Backport test PR

To test backporting:

Update the v1.0-test label with the changes you want to test (i.e., update the label based on your topic branch)
Update the BACKPORT-TEST.md file with some minor change as the basis for the change to be backported
Enter the following comment

@gitbot backport backport-target

A backport PR against the backport-target branch should be created where you can merge that PR to that branch
Backport of #11

This is a test backport and so not merging to backport-target


v12 release notes

MERGE OTHER ISSUE IN HERE: https://github.com/inveniosoftware/docs-invenio-rdm/issues/536

check all closed issues/PRs in the board
features that might contain schema changes

access requests: https://github.com/inveniosoftware/invenio-rdm-records/pull/1392
safe moderations
record and user deletion

programmatic API breaking changes

the RoleNeed now uses the role id instead of name
Python 3.8 will be required (because of invenio-rdm-records)

have a look to this: https://github.com/inveniosoftware/invenio-app-rdm/issues/1914

Documentation

overridable: document that the JavaScript block must contain {{ webpack['overridable-registry.js'] }} as here (Uni Munster)
notifications

https://github.com/inveniosoftware/invenio-app-rdm/issues/2204
https://github.com/inveniosoftware/docs-invenio-rdm/issues/558

access requests

the data model has changed in a few ways (e.g. allowing only a single record owner) – c.f. the PR description of https://github.com/inveniosoftware/invenio-rdm-records/pull/1306#issue-1707170959

user moderation

(EPIC) https://github.com/inveniosoftware/invenio-app-rdm/issues/2290
New configs were added:

(invenio-accounts) ACCOUNTS_DEFAULT_USERS_VERIFIED
invenio-rdm-records RDM_SEARCH_SORT_BY_VERIFIED

New db migration was added to invenio-accounts
need to update the setup command $ invenio roles create administration-moderation
 $ invenio access allow administration-moderation role administration-moderation
 $ invenio roles add <email> administration-moderation

record and user deletion

record deletion will require a new vocabulary type (removalreasons), as outlined in the PR description https://github.com/inveniosoftware/invenio-rdm-records/pull/1386#issue-1823962069

https://github.com/inveniosoftware/docs-invenio-rdm/issues/532
previewer

PR from Dan with new config var
PREVIEWER_TXT_MAX_BYTES.
PR

invenio-github:

(EPIC) https://github.com/inveniosoftware/invenio-app-rdm/issues/2249 - first documentation provided in the issue

allow edit of published files (Do we want to document that?) - See here
badges (added in February but not documented):

https://github.com/zenodo/zenodo-rdm/pull/253
https://github.com/inveniosoftware/invenio-app-rdm/pull/2145
TL;DR : in the landing page, we added support to render badges in a new box named External resources. This depends on a set of conditions to be met (e.g. the record having related identifiers that match a Github release). This is extensible already and is being used in Zenodo-RDM

stats

in case someone started to use the new invenio-stats already, v4 comes with breaking changes: the default stat indices are monthly and not anymore daily, and the templates/mappings have a new field updated_timestamp. A recipe to manually upgrade is here: https://github.com/CERNDocumentServer/cds-rdm/issues/108

https://github.com/inveniosoftware/invenio-rdm-records/pull/1433/files#diff-e22bdb78803ca92e6132b3900d02e197ff63b97add0575ef7a5e6dfcc0738768R65

other releated issue: https://github.com/inveniosoftware/invenio-app-rdm/issues/2343

note to self: went through all of those
Remaining:

Previewer section
Github integration section
Go through the CHANGES.md of all repos

closed via https://github.com/inveniosoftware/docs-invenio-rdm/pull/681


Revamp build system

Closes #113 and #118

@samhh anything I can do to help get this merged?

Hey @andreavaccari! Sorry for my slow follow up, I've been mostly AFK the last few weeks.
It would be helpful for me to know what exactly tsup is doing differently under the hood. On the plus side it's very tempting for me to offload all this bundling stuff to a third party like this... :wink:

Closing as stale. Happy to revisit if there's interest.

Closing as stale. Happy to revisit if there's interest.


feat: anchors, fixes #295

This PR adds a new Anchor component, which can wrap headings to add an anchor. Clicking the anchor copies a sharable link to the section.
Added to tags, operations and models. Not yet to headings in the description.
I didn’t even try to make it look good and just used an emoji. @cameronrohani can you help here? 🙏

I can take a swing at styling this

Alright, updated the anchors to use a "#" and only appear on hover, also they're stuck to the last line / character of of the header. Added some accessibility stuff too.
Demo:
https://github.com/scalar/scalar/assets/6374090/b5f0a19c-58fb-44e1-834e-ffa74ecb9570
Demo showing the hit areas:
https://github.com/scalar/scalar/assets/6374090/af3a193d-b360-4aed-9385-b47ca4486c9f

Pushed

Way better 😁


Display matching team name on case result highlights

https://trello.com/c/V9VoZQbC/1167-case-search-result-page-returning-team-ids-instead-of-names
Description
Displays the matching team name in case search result highlights rather than their ID.
Note Opensearch is currently configured to wrap highlights in its result set in <em> tags. This can be changed, but would involve a much larger refactoring, so I elected to strip them out in order to resolve the team name. An exception will be thrown if the team cannot be resolved from the ID. This should be safe since we do not delete teams for various reasons which would break things elsewhere.
I nalso changed the label 'teams with access' to 'team added to the case' to be consistent with the label in the filter list.

Codecov Report

Merging #1748 (c00a324) into master (9f61c3a) will decrease coverage by 86.06%.
The diff coverage is 28.57%.

@@            Coverage Diff             @@
##           master   #1748       +/-   ##
==========================================
- Coverage   89.74%   3.67%   -86.07%
==========================================
  Files         399     399
  Lines        8622   13132     +4510
  Branches     1252     232     -1020
==========================================
- Hits         7738     483     -7255
- Misses        701   12648    +11947
+ Partials      183       1      -182

Impacted Files
Coverage Δ

app/helpers/investigations/display_text_helper.rb
25.39% <28.57%> (-47.02%)
:arrow_down:

app/models/role.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/models/team.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/models/alert.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/models/contact.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/models/country.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/models/product.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/models/accident.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/models/incident.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/models/location.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 357 more

Continue to review full report at Codecov.

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


[Impeller] Simple program on Android Vulkan backend eventually fails

import 'dart:math' as math;
import 'dart:ui';

Color randomColor([double opacity = 1.0]) =>
    Color((math.Random().nextDouble() * 0xFFFFFF).toInt()).withOpacity(opacity);

void main() async {
  window.onBeginFrame = (_) {
    final recorder = PictureRecorder();
    final canvas = Canvas(recorder);
    canvas.drawPaint(Paint()..color = randomColor());
    canvas.drawRect(
      const Rect.fromLTWH(200, 200, 300, 300),
      Paint()..color = randomColor(.5),
    );
    final picture = recorder.endRecording();
    final builder = SceneBuilder();
    builder.addPicture(Offset.zero, picture);
    final scene = builder.build();
    window.render(scene);
    scene.dispose();
    picture.dispose();

    window.scheduleFrame();
  };
  window.scheduleFrame();
}

Run this on a Pixel 7 pro for a minute or so and eventually:
E/flutter (10821): [ERROR:flutter/impeller/base/validation.cc(49)] Break on 'ImpellerValidationBreak' to inspect point of failure: Failed to encode and submit command buffer while ending render pass.
E/flutter (10821): [ERROR:flutter/impeller/base/validation.cc(49)] Break on 'ImpellerValidationBreak' to inspect point of failure: Failed to encode and submit command buffer while ending render pass.

And the app stops rendering.

Patched in some more validation logs in to command_encoder_vk.cc and got this:
 [ERROR:flutter/impeller/base/validation.cc(49)] Break on 'ImpellerValidationBreak' to inspect point of failure: Failed to end command buffer: ErrorOutOfHostMemory

This program seems to be continuously allocating graphics memory and not releasing it. Eventually command encoding fails because there's not enough memory.

Trying to reproduce this ona. production pixel 6 and it's definitely holding on to memory too much, but the device I was reproducing this on was a developer testing device which may have some issue...

Note to self- it was helpful to do a heapprofd trace here, which showed uncollected vkCommandBuffers over the trace period.


add trailing slash to scoped packages

Wanted to do the tweaks and the fix into separate PR's but had to fix the implementation because of XO so I fixed everything into one PR. If you want separate PR's, let me know.

Just commit all the unrelated stuff directly to master and then rebase your PR ;)

Done! Have difficulties squashing them though.

Ping :)

:+1:

Nice, thanks :)


How to detect if someone is speaking when muted?

Hello! Zoom has this lovely feature that tells you if you're muted when you're speaking. Is there a way to achieve this with Livekit?
Once the local track is muted, it doesn't seem to receive any updates. Would we need to run a separate mic listener while the track is muted (and not broadcasting) or is there a way to do this with Livekit as is?

hi @MathieuLoutre,
there's currently no helper function in livekit to detect this, but it's an interesting idea!
I imagine the implementation on the audio level to detect this, would look similar to how the sdk is detecting silence currently (https://github.com/livekit/client-sdk-js/blob/main/src/room/track/utils.ts#L80-L102), just instead of detecting silence, this would need to detect levels over a certain threshold.

Thank you! What I did in the end is run another mic listener that runs when the livekit track is muted and run an audio analyser to check for spikes of activity. It works but would have loved to re-use the mic listener/track from Livekit instead of having another own (though it's fairly painless).


drop horned-bin dependency, use parsers directly in CLI

I think our dependency on horned-bin is just for the convenience parse_path method. Let's modify the whelk-rs CLI to guess the format based on file extension (and also allow direct specification of format with an argument) and just use the specific parser directly (which I believe are in the horned-owl lib).
https://github.com/INCATools/whelk-rs/issues/12#issuecomment-1433152411

Fixed by #14.


List command

Pull Request Test Coverage Report for Build 163

29 of 30 (96.67%) changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 84.612%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/main/java/seedu/investigapptor/logic/commands/ListCommand.java
14
15
93.33%

Totals

Change from base Build 159:
0.1%

Covered Lines:
2018

Relevant Lines:
2385

💛  - Coveralls


Conflicting problem with vimix-gtk-themes..

Hello, I think your extension conflicts in someway with the GNOME theme called Vimix, i use the Dark-Deoder variant. I also tried with the other versions but nothing change. :) Here is the video demostration: https://www.youtube.com/watch?v=asrzJoHNx2M

Thank you for reporting.
I have no idea what it may do wrong. It consist of 2 obvious lines. I'll try to investigate the problem.
Cross reference: vinceliuice/vimix-gtk-themes#33

Couldn't reproduce the problem. My config:

Fedora 24 (with latest updates)
GNOME 3.20.2

@Warmuser, please give more details on your config. At least: OS version, GNOME version, vmix-gtk-themes version. I'll try to reproduce your setup.

@aXe1 My config is based on these Specs:

Manjaro 17.0.2
GNOME 3.24.2
Linux 4.9.43-1-MANJARO
bash 4.4.12
Gallium 0.4 on SVGA3D
VMWare Workstation 12 Player

@Warmuser, sorry, I have no time currently. But I'll try to reproduce issue as soon as possible.


update titles

this may not be correct as report only requires a different dir structure and fir this reu we simplified it to project/index.md instead of report/index or report/report.md
to be sure macros have to be looked as and each dir structure verified.
However as clicking works with the currently used macro the new one will likely not work and therefore should not be used


hacktoberfest-practice

Sachin Parihar

Hey @sachinparihar I see you are made a pr to main-old branch. Please shift the pr to main branch which can be done from the edit button above.


Building-Dominic

My artwork aimed to depict a city skyline with the reflection of buildings as horizontal lines. Initially, I intended to add additional elements atop the buildings, but this resulted in messing up the other buildings. In terms of my experience in programming, I am familiar with Java and a bit with Python. I have also tinkered around with Arduino and Raspberry pi. Recently, I've been trying to learn JavaScript and stumbled upon this great opportunity to challenge myself by reading a bit of documentation and learning how to program blot, particularly since I was unfamiliar with it.

I really like it. You're the first to make use of color in the gallery I think. The shapes are simple and geometric but clearly evoke the subject matter. Nice work.
 You can order it here.


Smart Gateway Operator Release 1.0.0

Thanks submitting your Operator. Please check below list before you create your Pull Request.

Flat operator directory structure is obsolete from 23-rd of October 2019, only nested directory structure will be accepted.

New Submissions

[x] Has you operator nested directory structure?
[ ] Have you selected the Project Community Operator Submissions in your PR on the right-hand menu bar?
[x] Are you familiar with our contribution guidelines?
[x] Have you packaged and deployed your Operator for Operator Framework?

[x] Is your submission signed?

Updates to existing Operators

[ ] Is your new CSV pointing to the previous version with the replaces property?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Submit operators to both upstream-community-operators and community-operators at once
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file a PR against this repo and explain your need
2 For more information see here

Note that substantial changes have been done to our Operator since originally submitted by @aneeshkp so I'm removing the old Operator and replacing it with this new version from our repository.

Hi @leifmadsen, good to see operator in bundle format. Please check a preview, looks like double header, first one i automatically generated.
@aneeshkp need to sign off or approve it as he is the original author.

@aneeshkp can you please note that I am the maintainer of this package now? Thanks!

@J0zi thanks for the review. Not a double header, but I have adjusted the description text to be more verbose and not just the same as the displayName.

/test CVP

not all tests triggered

/approved

@leifmadsen, we need only 1 commit. But still checking if we support bundle format, despite it is near future definitely.

@leifmadsen, we cannot merge it because we are unable to push to quay. But today was a meeting regarding bundle format. So we are working on it. However it will take some time, so bundle format is not supported yet.

FYI rebased back to a single commit. Curious what the problem is with pushing to quay.io. I already push this up with operator-courier push without issue. The bundle format is there, but I don't actually use it for anything yet. Ultimately it's just a bunch of extra files in the directory that end up getting ignored it seems.
Anyways, I mostly just wanted to try and get this updated. What I'd actually prefer in the meantime is really to just drop the old Smart Gateway Operator entirely from the community-operators repo since it effectively just conflicts with my custom OperatorSource.

Hi @leifmadsen, bundle format is not supported nor tested at the moment. Please convert to nested format. I would like to ensure you, that we are working on it to be supported. It will take some time, definitely. Conversion is the only option, sorry for that.

@J0zi just to clarify, the issue is the metadata/annotations.yaml and Dockerfile correct? I'm still supposed to use versioned directories to hold the CSV and CRD?
Thanks!

Hi @leifmadsen, you are right, correct directory structureis described here.

@J0zi ok cool thanks, I think the latest changes reflect the ideal reality. Thanks!

not all tests triggered

@leifmadsen, please check a preview, looks like double header, one is generated automatically.

/retest

Sorry, think I fixed it somewhere, then forgot to backport it. Double description title should be gone now.

@leifmadsen, something is wrong, relevant tests were not triggered. I can not find what is wrong.
Meanwhile, I was testing manually. Please remove replaces which point to non-existing operator. Or do you want to replace smartgateway?

@leifmadsen, I see it:) some edits are in smartgateway and some in smart-gateway folder. Please edit just one operator at a time.

/test

/retest

@leifmadsen I tested this locally using our test-scripts and your replacement 0.2.0 doesn't exist in the catalog, only 0.1.0.

Yea sorry, this is a bit of a mess because it's trying to replace and update the old Smart Gateway with our new one. I'm going through documentation now, and I'm starting to become concerned this is going to conflict with other catalog sources that I need to exist.
At this point I'm thinking about just pulling Smart Gateway from the community catalog entirely and waiting until after I have what we need in the Red Hat catalog downstream. At that point I can determine what our upstream source should actually be.

Closing in favour of another pull request that will just remove SmartGateway Operator from the community catalog.


Properly apply aria-label to editors

As @bpasero points out
We use
this.editorContainer.setAttribute('aria-label', this.computeAriaLabel());
But we actually do not update the editor options ariaLabel property at all. Neither from group changes nor from label changes. In fact I think we are computing the aria label twice: https://github.com/microsoft/vscode/blob/master/src/vs/workbench/browser/parts/editor/textEditor.ts#L97

The ARIA label for untitled is back to the form of "Untitled-". In addition, changing groups will now properly update the ARIA label for the editor container as well as the editor widget itself.

Verification:

untitled editors should read as "Untitled-N" to screen readers independent of their content
editors should read out their group name only if more than one group is opened

Thanks Ben. I will verify this once we have the insiders build out.

@isidorn can you verify and set the label? Thanks!

Works great, adding verified label. Thanks!


Transfer ownership

Details

Read the Docs project URL: https://readthedocs.org/projects/nest-simulator/
Build URL (if applicable): https://nest-simulator.readthedocs.io/en/latest/
Read the Docs username (if applicable): graber

Expected Result
I'm working on https://github.com/nest/nest-simulator and like to update the documentation.
Actual Result
Can not update the documentation, as the repository is owned by someone else, who is not part of the nest developers.
Can you please ask the user to transfer the ownership or add me as owner as well?
thanks in adanvce!

@steffengraber hi! I'm assigning this to myself to take care of.
We do have a policy for this cases at http://docs.readthedocs.io/en/latest/abandoned-projects.html
I will contact the user in the next week hopefully. Thanks

Sorry for the delay. I was able to send an email today. I will come back to this in 6 weeks from now.
datetime.datetime(2018, 6, 22, 11, 35, 48, 961598)

@steffengraber hi! He gave you permissions to update the docs.
Let us know if there is any problem. I'm closing this issue.
Thanks,


Items in ListView collapsing

Good Morning, my list view is displaying ok, but when I try to scroll through it, it's like if it was aplying another css and not displaying the height assigned by CSS
Also, this plugin is not displaying.
Could you help me?
https://play.nativescript.org/?template=play-ng&id=AY40xi&v=4

Hi @DMarinsa,
When you are setting up the height of the Label via CSS, you should set up the component inside some of the available Layouts(e.g GridLayout). This will help with the correct measuring the Label's height when the ListView cells are reloaded.  For example:
<ListView [items]="partidas" class="lista-partidas">
			<ng-template let-item="item">
				<GridLayout>
					<Label [text]="item" class="partida-item"></Label>
				</GridLayout>
			</ng-template>
		</ListView>

Regarding the nativescript-floatingactionbutton.
In NativeScript playground you can use a limited number of plugins, unfortunately, nativescript-floatingactionbutton  is not one of the supported plugins. Also if you are facing issues with the plugin, while building the app locally, please contact the author while using this repository.


Add support for defining global objects via TS/JS scripts

As per the discussion in #76, it would be beneficial to support adding global objects (as opposed to importable modules) in JS. Once this is implemented, the code from #76 should be moved to the global scope as well.
cc @MasatoDev

This is done in main


Mock auth requests

This gets CI working and removes dependency on the live auth server for testing.
I'm using this small docker mock service that I wrote:
https://github.com/jayrbolton/mock_microservice
Issue #12

Still debuggin the Travis run here...

Thanks , good catches as usual. I moved that function out because I found
it weird to have a function called bulk import and a separate module called
bulk import. I’ll try to rearrange things
On Wed, Nov 21, 2018 at 5:47 AM James Jeffryes<EMAIL_ADDRESS>wrote:

@JamesJeffryes commented on this pull request.
Debugging travis can be such a pain but it'll be nice to have CI running
and never have to worry about tokens. Other than duplicating the bulk
import logic, I think it looks good
In src/relation_engine_server/bulk_import.py
https://github.com/kbase/relation_engine_api/pull/15#discussion_r235390304
:

@@ -33,3 +35,17 @@ def _write_edge_key(json_line):
json_line["_from"].encode() + json_line["_to"].encode(), digest_size=8
).hexdigest()
return json_line

+def _import_from_file(file_path, query):

"""Open a file of line-separated JSON and bulk-import it."""
with open(file_path, 'rb') as file_desc:

   resp = requests.post(

       db_url + '/_api/import',

       data=file_desc,

       auth=(db_user, db_pass),

       params=query

   )

if not resp.ok:

   raise ArangoServerError(resp.text)

return resp.text

I could make a case for why we'd want this function here or in
arango_cilent (though I probably lean towards the latter) but if we do move
it here, I think you should remove the bulk_import from arango_cilent
In src/test/test_api.py
https://github.com/kbase/relation_engine_api/pull/15#discussion_r235391567
:

     resp = requests.get(url + '/api/schemas/example_edges').text

     self.assertTrue('_from' in resp)
     resp = requests.get(url + '/api/schemas/example_vertices').text
     self.assertTrue('_key' in resp)

def test_save_documents_no_auth(self):

   # Missing bearer

   resp = requests.put(url + '/api/documents?on_duplicate=error&overwrite=true&collection').json()

   self.assertTrue('Missing header' in resp['error'])

   # Invalid bearer

def test_save_documents_missing_auth(self):

   """Test an invalid attempt to save a doc with a missing auth token."""

   resp = requests.put(

       url + '/api/documents?on_duplicate=error&overwrite=true&collection'

   ).json()

   self.assertEqual(resp['error'], 'Missing header: Authorization')

def test_save_documents_invalid_auth(self):

   """Test an invalid attempt to save a doc with a bad auth token."""
   resp = requests.put(
       url + '/api/documents?on_duplicate=error&overwrite=true&collection',
       headers={'Authorization': 'Bearer xyz'}

Pedantic, but if you define an 'invalid_token' variable, I'd expect it to
be used here
In src/test/test_api.py
https://github.com/kbase/relation_engine_api/pull/15#discussion_r235391705
:

 def test_admin_query_invalid_auth(self):

     """Test the error response for an ad-hoc admin query without auth."""
     resp = requests.post(
         url + '/api/query_results',
         params={},

       headers={'Content-Type': 'application/json', 'Authorization': 'xyz'},

And here
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kbase/relation_engine_api/pull/15#pullrequestreview-177242929,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIVefBrh-aW_CEggYaVkYR7JPXy0cw6Bks5uxVlpgaJpZM4YruNe
.

Reorganized the bulk import functions, removed accidental dupe code
Using invalid_token in the tests

Dammit travis.

We're hitting the github API rate limits on travis. This rate limit is only for fetching the latest release of the specs. I think you can download the release gzip without limits. I'm thinking we can just put the url of the latest spec release in the environment and use that as a fallback.


Implemented initial fractional strategy

I've implemented a fractional strategy. The math could definitely use double checking. There are some corner cases that may need additional work such as the pll3_r_ck below being below the target value instead of above, but that would require adjusting the other clocks i think, so it may just be a oddity.
Is there a good way to confirm the output clock values short of throwing a scope on it ( I don't have one)?
PllConfigStrategy::FractionalNotLess
sys_ck = 400 MHz
pll3_p_ck = 12288002 MHz (target was 12_288_000)
pll3_q_ck = 6144001 MHz (target was 6_144_000)
pll3_r_ck = 3023546 MHz (target was 3024000)

Closes #98

Great! In terms of checking, maybe we can extend the existing unit test routines a little more? Particularly for
q and r ck? Testing on hardware is also possible, a digital counter/logic analyser would be ideal for that rather than an oscilloscope. Combined with sigrok many people like these analysers.
The corner case with r_ckhappens because p:q:r must always be in an integer ratio (that's fixed in hardware) and the PLL strategy only runs for the requested p_ck. Once the p_ck is fixed then q and r are calculated here and the integer divisor is always rounded up. Perhaps you could change that to round down for FractionalNotLess?

Extending the tests sounds like a good idea. Unsure how I would go about implementing either of those hardware solutions.

I re-wrote part of the example to use pll2 and mco2, and then used pulseview to count the pulses on PC9.

Value in _mco2_ck
Measured
Error

mco2_from_hse
6_250_000
6_248_460
-246ppm

mco2_from_pll2_p_ck
6_144_000
6_142_490
-246ppm

This mostly tells us that there's a 246ppm error between the oscillator on my board and my PC. But also shows that the fractional strategy is at least somewhat working

A  method of testing this with minimal hardware (you need 1 wire) would be to set one timer peripheral to output a divided version of the PLL clock, then use the capture functionality of another timer peripheral to measure it. The HAL timer implementation definitely doesn't support that yet

Ok. I have a cheap logic analyzer otw I can test the clocks with hopefully this weekend. Seems like a useful tool to have around.

Ran a couple of tests. Found and fixed a bug. Sampled the MCO2 clock and it seems to be in the right general range.

I added some more documentation to the new functions (calc_...), and fixed the name of the 2nd variable in calc_ck_div. That highlights another bug, that if target_ck < calc_ck(...) always evaluates to true here.
In fact I was confused why the calc_ck_div takes both the VCO output frequency and N divider value. I think there's some confusion between the target and actual/achieved VCO output frequencies (and it was a problem before this PR). In particular the Q and R output dividers should be calculated using the actual VCO output frequency.

Ok, I think that's resolved it. This has changed the outcome of the fractional_not_less test, the Q divider is now 156 (Q CK = 6.144001MHz) rather than 155 (Q CK = 6.183639MHz) before. I think this is correct.

Looks good. Built and ran just fine on my daisy board still.

bors r+


Hard to type in category field after searching

Steps to reproduce:

Type in a search query, the slower the query the more obvious the problem will be.  1k is a great example.
Click into the Category field and start typing the name of a category.  I typed "Resistors"

Expected result: I can type fluidly and the search does not re-run until I am done typing.
Actual result: There is a long lag after every keystroke while the query re-runs.
Known workaround: open the dropdown and pick your desired category from the menu.
NOTE: the problem does not occur when typing in the Subcategory field.  Hopefully it is an easy fix to apply debouncing to the Category field as well.

I had the idea to add an wx.ActivityIndicator but apparently the db search itself blocks the GUI refresh, so the spinner does not spin while the search is running 😑
Maybe we can utilize a thread and events in order to populate the listview after the search is done ...


Add StorySource

I want to add Storysource on Design System to perform the documentation.
I try to add this localy but i have a bug with the actual synthaxe of stories.
The Design System use his own addon to write stories but this one is not compatible with Story Source.
I propose to rewrite all stories with the standard synthaxe with storiesOf because this solution works.
Versions 1.3.2-alpha.0

Installed packages : "@storybook/addon-storysource": "^5.1.9"

What do you think to migrate to the new format ?
https://storybook.js.org/docs/formats/component-story-format/


[Question] How to specifiy short names for a resource?

The docs mentions a resource can have shortNames, but I didn't found a way to do this in code.

/triage support
hey @yaxinlx , take the content of example/pkg/apis/innsmouth/zz_generated.api.register.go as example, if u want to add short name(s) to that resource, u can simply append a method for its storage like:
func (s *storageDeepOne) ShortNames() []string {
	return []string{"do"}
}

@yue9944882 what about "customize Server-side printing", currently , the output of kubectl get myresource is quite a few.  BTW, how do find I these ShortNames() interface, I cannot find any code include these( I only find some create,update strategies).

As a user, it will be great if we can get support for specifying shortnames. Seems like #283 was pretty close, any update on it?

for now, we can support shortname/catagory by customizing REST and i added an example by #359. the other pull is breaking underlying api-machinery hierarchy as i reviewed and commented.
alternatively, we can support providing shortnames via resources tag like // +resource: ....,shortNames=abc in the type definition.

for now, we can support shortname/catagory by customizing REST and i added an example by #359. the other pull is breaking underlying api-machinery hierarchy as i reviewed and commented.

I will try this out

alternatively, we can support providing shortnames via resources tag like // +resource: ....,shortNames=abc in the type definition.

That will be nice to have.


Change to process *.scss instead of only project.scss.

@omin, thanks! I should ask, have you tested this?

Yep. Well, it depends on what the author was trying to achieve. If he/she was trying to concatenate to a single file, we need another solution.
Sames goes for processing javascript files with gulp btw.


add a beforeupdate event

New Pull Request
I'd like a beforeupdate event
Type of change
Please delete options that are not relevant.

[ ] New feature (non-breaking change which adds functionality)
[ ] This change requires a documentation update - maybe add it to the events list

Checklist:
I haven't tested this I just wrote it via guthub in the browser

There has not been an issue submitted in which making this change was discussed or approved.


FIX: Don't break if RAISE_NOT_CONNECTED is False when determining the API.

Tests are passing locally


Implement locking in the replicator

Part of #2777.

Ah, so – what should the replicator do if it finds the row is locked?
It shouldn’t do any work – that’s why the lock is there! But nor should it swallow the message silently; if we’ve created a lock that can’t be removed, the message will silently disappear into the aether.
Does the ingests service need to know about locks?


Keyboard Flickering on TextInput with secureTextEntry

Description
If you have 2 text inputs, (One with secure text entry enabled and the other set to disabled), When typing, highlighting and scrolling in the non-secure text entry, the keyboard will flicker.
This is an iOS issue only, I have tested this using iOS 17, on an iPhone 13 mini. I cannot repeat this issue in the simulator, only on the device.
It appears to be when iOS recognizes it as a login field, so it presents the auto-fill passwords UI. See the attached video on the flickering issue described.
https://github.com/facebook/react-native/assets/33269267/d0222621-afc8-4090-a0c8-9dcdb7d35bcb
React Native Version
0.72.4
Output of npx react-native info
System:
OS: macOS 13.4.1
CPU: (10) arm64 Apple M1 Pro
Memory: 115.16 MB / 16.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 20.3.1
path: /opt/homebrew/bin/node
Yarn:
version: 1.22.19
path: /usr/local/bin/yarn
npm:
version: 9.6.7
path: /opt/homebrew/bin/npm
Watchman:
version: 2<IP_ADDRESS>
path: /opt/homebrew/bin/watchman
Managers:
CocoaPods:
version: 1.11.3
path: /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 22.4
- iOS 16.4
- macOS 13.3
- tvOS 16.4
- watchOS 9.4
Android SDK:
API Levels:
- "28"
- "31"
- "32"
- "33"
Build Tools:
- 30.0.2
- 30.0.3
- 32.0.0
- 33.0.0
- 34.0.0
System Images:
- android-30 | Google Play ARM 64 v8a
- android-33 | Google APIs ARM 64 v8a
- android-33 | Google Play ARM 64 v8a
- android-34 | Google APIs ARM 64 v8a
Android NDK: Not Found
IDEs:
Android Studio: 2022.1 AI-221.6008.13.2211.9619390
Xcode:
version: 14.3.1/14E300b
path: /usr/bin/xcodebuild
Languages:
Java:
version: <IP_ADDRESS>
path: /usr/bin/javac
Ruby:
version: 2.6.10
path: /usr/bin/ruby
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 18.2.0
wanted: 18.2.0
react-native:
installed: 0.72.4
wanted: 0.72.4
react-native-macos: Not Found
npmGlobalPackages:
"react-native": Not Found
Android:
hermesEnabled: true
newArchEnabled: false
iOS:
hermesEnabled: true
newArchEnabled: false
Steps to reproduce
Have 2 TextInput components inside a view, one set with secureTextEntry, one without.
This issue is only seen on device, not in simulator
Snack, screenshot, or link to a repository
https://github.com/gcon97/KeyboardFlickeringDemo

I also encountered the similar issue when in login screen

I am experiencing the same on login screens. It's a newer issue. It seems to be caused by the suggested autofill.
The problem is reduce by using default value prop passed to TextInput component that holds its own text ref and passes out ref value on change.

I figured out the problem
It appears to be that at some point recently (pre iOS 17) a bug was introduced. Whenever secureTextEntry is enabled and textContentType is set, various Text Input changes (typing, focus, etc...) will fire a native keyboardWillChangeFrame event that causes the keyboard to re-render. This also causes iOS's AutoFill QuickType Bar (forgive me if my terminology is incorrect) to flicker.
This can be especially problematic for any RN apps using KeyboardAvoidingView with iOS behavior={'position'} since it will cause a layout flicker as it adjusts to the disappearing and reappearing AutoFill QuickType Bar.
You can actually see the issue in native iOS apps:

Go to the login screen of a native iOS app.
Change focus from username and password fields.
In many apps you can see a slight bounce as the keyboard animations handle the  AutoFill QuickType Bar flicker.

I began seeing this after updating the device i test on (iPhone 14 Pro) to iOS 17. Using Expo Go.

I believe this is caused by the "Passwords"-thing (see attached image) that appears on iOS when the OS believes you want to use a password from your keychain.
When I test on a phone that does not have a keychain, there is no jumping or flickering.

I can confirm that it is an issue with the Passwords option in the Keyboard toolbar. Seems to be an issue across iOS 17 rather than a ReactNative issue. (It also isn't fixed in iOS 17.1, so we may be waiting a while for a fix).
Closing as it isn't a React Native-specific issue.

I'd like to add that adding textContentType='oneTimeCode' to your TextInput disables the Password toolbar, which also eliminates the described issue.

@ThorANilsson I tried this, but it's not working for me.

Here's what I did.
TL;DR: If it's a password field, on each change update the actual string value in a map, and then render the value as bullets '•'.
Somewhere created a file called maskMap.ts with the following:
export const maskMap = new Map<string, string>();

And in your custom TextField component (I'm assuming most of you have wrapped TextInput into one of your own TextField components):
import * as React from 'react';
import { TextInput } from 'react-native-paper';
import { maskMap } from './maskMap';

const PASSWORD_MASK_CHAR = '•';
. . .
// secureTextEntry determines whether or not this is a password field
const TextField = React.memo(({ onChange, secureTextEntry, ...props }: YourTextFieldProps) => {
  const [textFieldId] = React.useState(uuid()); // use whatever uuid generator you'd like
. . .
  React.useEffect(() => {
	  maskMap.set(textFieldId, '');

	  return () => {
		  maskMap.delete(textFieldId);
	  };
  }, [secureTextEntry]);

  const handleChange = React.useCallback((e: string) => {
	  if (secureTextEntry) {
		  const previousValue = maskMap.get(textFieldId) as string;
		  const formattedNewValue = e.replace(new RegExp(PASSWORD_MASK_CHAR, 'g'), '');

		  const newValue = previousValue + formattedNewValue;
		  onChange(newValue);
		  maskMap.set(textFieldId, previousValue + formattedNewValue);
	  } else {
		  onChange(e);
	  }
  }, [secureTextEntry]);

  const getValue = React.useCallback(() => {
	  if (!secureTextEntry) {
		  return value;
	  }

	  return value.replaceAll(/./g, PASSWORD_MASK_CHAR);
  }, [value, secureTextEntry, showText, maskMap]);
. . .

    return (
        . . .
            <TextInput
                value={getValue()}
                onChangeText={handleChange}
                textContentType='none' // add this
                . . .
            />
        . . .
    )
})

how this can be closed if its still happening ?

@Engazan It's closed because it's an iOS bug. iOS started over-triggering keyboardWillChangeFrame events every time the input changes when the arguments you specified are implemented. We can't ignore this event because it's relied on for many component designs and reactivity. So, sadly we have to put in temporary patch fixes until Apple fixes it on their side.

Adding textContentType='oneTimeCode' to your TextInput disables the Password toolbar, which also eliminates the described issue.

This works! Thank you sir! Just saved my weekend lol

Any updates

I have found the solution. The error is caused by props value , you can hide the value and handle the logic with ref

Hi everyone, is there any update on this?

Also happening on my side :) Seems to be an issue in flutter, too https://github.com/flutter/flutter/issues/134723

I have problem also in android,, can somebody helpme?
https://github.com/facebook/react-native/assets/7281791/5cdfed29-6aec-4f47-bad4-fd0c97d3e508

How to hide the "password" panel on the keyboard when we use secureTextEntry?

Hi there!
On iOS 17.3.1 problem still exists.
On iOS lower version all works fine.

The problem still exist on iOS 17.4

Can confirm this is happening on 17.4, on an email field for me, despite the type being emailAddress:
autoCapitalize='none'
autoComplete='email'
textContentType='emailAddress'
keyboardType='email-address'

I've found in my case problem was caused by 'value' prop. I'am using 'react-hook-form' and if I pass value of email input from hook directly to email input it calls keyboard event on every single character input. After removing prop, everything works fine.

I've found in my case problem was caused by value prop. I'am using react-hook-form and if I pass value of email input from hook directly to email input it calls keyboard event on every single character input. After removing prop, everything works fine.

@Bialson, how do you manage the field's value in this case? I'm facing the same problem, and it is driving me crazy.
<Controller
            name="email"
            defaultValue=""
            control={control}
            rules={{
              validate: async (value) => {
                try {
                  await signInSchema.parseAsync({ email: value });
                  return true;
                } catch (error: any) {
                  return error.message;
                }
              },
            }}
            render={({ field: { onChange, onBlur, value } }) => (
              <Input>
                <InputField
                  fontSize="$sm"
                  placeholder="Email"
                  type="text"
                  value={value}
                  onChangeText={onChange}
                  onBlur={onBlur}
                  onSubmitEditing={handleKeyPress}
                  returnKeyType="done"
                />
              </Input>
            )}
          />

If I remove the prop value={value}, it gets better, not 100%, but it flickers much less. But then how would you clean the input?
Thanks in advance

In addition to this flickering issue, it seems that in 17.4, when you try to tap a specific character in a TextInput to put the cursor at the middle of the string, it always jumps to the end of the TextInput.
It even happens on the official react native demo (if you use the QR code to open in Expo): https://reactnative.dev/docs/textinput
https://github.com/facebook/react-native/assets/120388/706d25c7-dece-4d20-8a8d-5862a2abade8
Why is no one talking about this? Why is this ticket closed?
Feels like this should be a P0 given how fundamental TextInputs are.

If you add multline={true} to the email field that fixed it for me. So then I thought okay it's just to do with height, so I set a fixed height on both of my inputs, and the flickering when typing is gone but it still flickers when you change fields but I think that's because I have two different types of input.

@Bialson, how do you manage the field's value in this case? I'm facing the same problem, and it is driving me crazy.
<Controller
            name="email"
            defaultValue=""
            control={control}
            rules={{
              validate: async (value) => {
                try {
                  await signInSchema.parseAsync({ email: value });
                  return true;
                } catch (error: any) {
                  return error.message;
                }
              },
            }}
            render={({ field: { onChange, onBlur, value } }) => (
              <Input>
                <InputField
                  fontSize="$sm"
                  placeholder="Email"
                  type="text"
                  value={value}
                  onChangeText={onChange}
                  onBlur={onBlur}
                  onSubmitEditing={handleKeyPress}
                  returnKeyType="done"
                />
              </Input>
            )}
          />

If I remove the prop value={value}, it gets better, not 100%, but it flickers much less. But then how would you clean the input?
Thanks in advance

@loe-lobo You can declare reference to input and when needed use clear() method from ref object to clear the value of input. I have been struggling with flickering for a long period and for me this is the best temporary solution. I think there is a problem with unnecessary re-render, some native event is triggering which isn't supposed to execute when value changes.

I have this issue on iPhone 17.3.1
It happens on email field, but not on password one (regardless of whether I set keyboard type or not).
Autocorrect solution did not work for me and I'd rather not go to other hacky stuff like setting it to multiline or changing node modules manually. I see that AirBnb login form does not have this issue on the same device, so there must be a way to handle this flickering from code. Please reopen this issue

I have this issue on iPhone 17.3.1 It happens on email field, but not on password one (regardless of whether I set keyboard type or not). Autocorrect solution did not work for me and I'd rather not go to other hacky stuff like setting it to multiline or changing node modules manually. I see that AirBnb login form does not have this issue on the same device, so there must be a way to handle this flickering from code. Please reopen this issue

autoCorrect={false} should be set only on your email input and dont forgot to reload your app when you test.

I figured out the problem
It appears to be that at some point recently (pre iOS 17) a bug was introduced. Whenever secureTextEntry={false} and textContentType is set, various Text Input changes (typing, focus, etc...) will fire a native keyboardWillChangeFrame event that causes the keyboard to re-render. This also causes iOS's AutoFill QuickType Bar (forgive me if my terminology is incorrect) to flicker.
This can be especially problematic for any RN apps using KeyboardAvoidingView with iOS behavior={'position'} since it will cause a layout flicker as it adjusts to the disappearing and reappearing AutoFill QuickType Bar.
You can actually see the issue in native iOS apps:

Go to the login screen of a native iOS app.
Change focus from username and password fields.
In many apps you can see a slight bounce as the keyboard animations handle the  AutoFill QuickType Bar flicker.

For those who are using KeyboardAvoidingView
For those who are wrapping their text inputs in a <KeyboardAvoidingView behavior= 'position'}> and <ScrollView>, you are likely dealing with your screen jumping on text change and focus change.
This isn't a pretty solution (and keep in mind it does not fix the root issue of the keyboard re-render), but you can do the following **TEMPORARY and NOT fully tested** fix for this issue:

Go to the file at: node_modules/react-native/Libraries/Components/Keyboard/KeyboardAvoidingView.js
Add ignoreIOSKeyboardWillChangeEvents?: boolean | undefined; to the KeyboardAvoidingView props.
Go to the types file at: node_modules/react-native/Libraries/Components/Keyboard/KeyboardAvoidingView.d.ts
Add ignoreIOSKeyboardWillChangeEvents?: boolean | undefined; to the KeyboardAvoidingView props.
Replace the const {duration, easing, endCoordinates} = this._keyboardEvent; line with the following:

const {duration, easing, endCoordinates} = this._keyboardEvent;

if(Platform.OS === 'ios' && duration === 0 && !!this.props.ignoreIOSKeyboardWillChangeEvents ) {
      return;
}

Use patch package to save the changes.

be sure to set ignoreIOSKeyboardWillChangeEvents={true} with care. I, for example, am only using it on a login screen for a very specific keyboard avoiding use case scenario that I detail above. Hope this helps.

The only solution that worked for me without negative effects, thanks.

I figured out the problem
It appears to be that at some point recently (pre iOS 17) a bug was introduced. Whenever secureTextEntry={false} and textContentType is set, various Text Input changes (typing, focus, etc...) will fire a native keyboardWillChangeFrame event that causes the keyboard to re-render. This also causes iOS's AutoFill QuickType Bar (forgive me if my terminology is incorrect) to flicker.
This can be especially problematic for any RN apps using KeyboardAvoidingView with iOS behavior={'position'} since it will cause a layout flicker as it adjusts to the disappearing and reappearing AutoFill QuickType Bar.
You can actually see the issue in native iOS apps:

Go to the login screen of a native iOS app.
Change focus from username and password fields.
In many apps you can see a slight bounce as the keyboard animations handle the  AutoFill QuickType Bar flicker.

For those who are using KeyboardAvoidingView (RN V0.72.* Patch Fix)
For those who are wrapping their text inputs in a <KeyboardAvoidingView behavior= 'position'}> and <ScrollView>, you are likely dealing with your screen jumping on text change and focus change.
This isn't a pretty solution (and keep in mind it does not fix the root issue of the keyboard re-render), but you can do the following **TEMPORARY and NOT fully tested** fix for this issue:

Go to the file at: node_modules/react-native/Libraries/Components/Keyboard/KeyboardAvoidingView.js
Add ignoreIOSKeyboardWillChangeEvents?: boolean | undefined; to the KeyboardAvoidingView props.
Go to the types file at: node_modules/react-native/Libraries/Components/Keyboard/KeyboardAvoidingView.d.ts
Add ignoreIOSKeyboardWillChangeEvents?: boolean | undefined; to the KeyboardAvoidingView props.
Replace the const {duration, easing, endCoordinates} = this._keyboardEvent; line with the following:

const {duration, easing, endCoordinates} = this._keyboardEvent;

if(Platform.OS === 'ios' && duration === 0 && !!this.props.ignoreIOSKeyboardWillChangeEvents ) {
      return;
}

Use patch package to save the changes.

be sure to set ignoreIOSKeyboardWillChangeEvents={true} with care. I, for example, am only using it on a login screen for a very specific keyboard avoiding use case scenario that I detail above. Hope this helps.

2024 and still using this workaround...

@ThorANilsson solution worked for me.
set textContentType='oneTimeCode' prop in textinput. Thanks

Has anyone found any solution for the keyboard to keep the password suggestion without flickering?

Please check my above comment. One solution worked for me. Thanks

Has anyone found any solution for the keyboard to keep the password suggestion without flickering?

Please check my above comment. One solution worked for me. Thanks

@1989kumarsunil With textContentType="oneTimeCode" it partially solved the problem. The keyboard has stopped flickering, but the password suggestion is not being displayed. I want to keep the suggestion, as many users use password management applications and need this functionality...

Has anyone found any solution for the keyboard to keep the password suggestion without flickering?

Please check my above comment. One solution worked for me. Thanks

@1989kumarsunil With textContentType="oneTimeCode" it partially solved the problem. The keyboard has stopped flickering, but the password suggestion is not being displayed. I want to keep the suggestion, as many users use password management applications and need this functionality...

@matheuscostadesign From what I understand, there is no current solution that completely fixes the flickering problem. Above I have described a solution when in an avoiding view to stop view jumping, but it does not stop the flickering. This problem is the result of an iOS bug, but I will be looking into an updated temporary hack-fix soon. I will post the patch in here when it is complete.

Is this problem exist in new major version 73.X, 74.X?

...
textContentType='none'
...

not working on iOS 17+

I figured out the problem
It appears to be that at some point recently (pre iOS 17) a bug was introduced. Whenever secureTextEntry={false} and textContentType is set, various Text Input changes (typing, focus, etc...) will fire a native keyboardWillChangeFrame event that causes the keyboard to re-render. This also causes iOS's AutoFill QuickType Bar (forgive me if my terminology is incorrect) to flicker.
This can be especially problematic for any RN apps using KeyboardAvoidingView with iOS behavior={'position'} since it will cause a layout flicker as it adjusts to the disappearing and reappearing AutoFill QuickType Bar.
You can actually see the issue in native iOS apps:

Go to the login screen of a native iOS app.
Change focus from username and password fields.
In many apps you can see a slight bounce as the keyboard animations handle the  AutoFill QuickType Bar flicker.

For those who are using KeyboardAvoidingView (RN V0.72.* Patch Fix)
For those who are wrapping their text inputs in a <KeyboardAvoidingView behavior= 'position'}> and <ScrollView>, you are likely dealing with your screen jumping on text change and focus change.
This isn't a pretty solution (and keep in mind it does not fix the root issue of the keyboard re-render), but you can do the following **TEMPORARY and NOT fully tested** fix for this issue:

Go to the file at: node_modules/react-native/Libraries/Components/Keyboard/KeyboardAvoidingView.js
Add ignoreIOSKeyboardWillChangeEvents?: boolean | undefined; to the KeyboardAvoidingView props.
Go to the types file at: node_modules/react-native/Libraries/Components/Keyboard/KeyboardAvoidingView.d.ts
Add ignoreIOSKeyboardWillChangeEvents?: boolean | undefined; to the KeyboardAvoidingView props.
Replace the const {duration, easing, endCoordinates} = this._keyboardEvent; line with the following:

const {duration, easing, endCoordinates} = this._keyboardEvent;

if(Platform.OS === 'ios' && duration === 0 && !!this.props.ignoreIOSKeyboardWillChangeEvents ) {
      return;
}

Use patch package to save the changes.

be sure to set ignoreIOSKeyboardWillChangeEvents={true} with care. I, for example, am only using it on a login screen for a very specific keyboard avoiding use case scenario that I detail above. Hope this helps.

Uploading Screen-recording-20240501-122505.mp4…

Adding textContentType='oneTimeCode' to your TextInput disables the Password toolbar, which also eliminates the described issue.

Thanks @ThorANilsson

Btw with iOS 17.5 and expo SDK 51 I don't see this issue in my apps ( they are gone )

Adding textContentType='oneTimeCode' to your TextInput disables the Password toolbar, which also eliminates the described issue.

Thank you for saving my Day. <3

Thanks for textContentType='oneTimeCode'
I hope apple fixes this
https://github.com/facebook/react-native/assets/134932472/b820652e-5567-45ec-b122-6f8ed95fd60f

My main issue was a continuous state update on a screen that wasn't focused, causing the app to continuously rerender.

problem still exists. The textContentType="oneTimeCode" solves it, but removes the password autofill option.

I figured out the problem
It appears to be that at some point recently (pre iOS 17) a bug was introduced. Whenever secureTextEntry={false} and textContentType is set, various Text Input changes (typing, focus, etc...) will fire a native keyboardWillChangeFrame event that causes the keyboard to re-render. This also causes iOS's AutoFill QuickType Bar (forgive me if my terminology is incorrect) to flicker.
This can be especially problematic for any RN apps using KeyboardAvoidingView with iOS behavior={'position'} since it will cause a layout flicker as it adjusts to the disappearing and reappearing AutoFill QuickType Bar.
You can actually see the issue in native iOS apps:

Go to the login screen of a native iOS app.
Change focus from username and password fields.
In many apps you can see a slight bounce as the keyboard animations handle the  AutoFill QuickType Bar flicker.

For those who are using KeyboardAvoidingView (RN V0.72.* Patch Fix)
For those who are wrapping their text inputs in a <KeyboardAvoidingView behavior= 'position'}> and <ScrollView>, you are likely dealing with your screen jumping on text change and focus change.
This isn't a pretty solution (and keep in mind it does not fix the root issue of the keyboard re-render), but you can do the following **TEMPORARY and NOT fully tested** fix for this issue:

Go to the file at: node_modules/react-native/Libraries/Components/Keyboard/KeyboardAvoidingView.js
Add ignoreIOSKeyboardWillChangeEvents?: boolean | undefined; to the KeyboardAvoidingView props.
Go to the types file at: node_modules/react-native/Libraries/Components/Keyboard/KeyboardAvoidingView.d.ts
Add ignoreIOSKeyboardWillChangeEvents?: boolean | undefined; to the KeyboardAvoidingView props.
Replace the const {duration, easing, endCoordinates} = this._keyboardEvent; line with the following:

const {duration, easing, endCoordinates} = this._keyboardEvent;

if(Platform.OS === 'ios' && duration === 0 && !!this.props.ignoreIOSKeyboardWillChangeEvents ) {
      return;
}

Use patch package to save the changes.

be sure to set ignoreIOSKeyboardWillChangeEvents={true} with care. I, for example, am only using it on a login screen for a very specific keyboard avoiding use case scenario that I detail above. Hope this helps.

Also work for me, but instead of editing files in node_modules, I've created a custom KeyboardAvoidingView class component that extends original KeyboardAvoidingViewComponent. So this "temporary" fix will be sill applied if dependencies are re-installed (eg. using a CI in specific env to build).
(As TS doesn't support props overrind in a class component inheretance pattern, @ts-nocheck is needed at top of file o avoid TS errors.)
`
// @ts-nocheck
import {
LayoutAnimation,
Platform,
KeyboardAvoidingView as RNKeyboardAvoidingView,
KeyboardAvoidingViewProps as RNKeyboardAvoidingViewProps,
} from "react-native";
export interface KeyboardAvoidingViewProps extends RNKeyboardAvoidingViewProps {
ignoreIOSKeyboardWillChangeEvents?: boolean | undefined;
}
export default class KeyboardAvoidingView extends RNKeyboardAvoidingView {
constructor(props: KeyboardAvoidingViewProps) {
super(props);
}
_updateBottomIfNecessary = async () => {
if (this._keyboardEvent == null) {
this.setState({ bottom: 0 });
return;
}
const { duration, easing, endCoordinates } = this._keyboardEvent;

if (
  Platform.OS === "ios" &&
  duration === 0 &&
  !!this.props.ignoreIOSKeyboardWillChangeEvents
) {
  return;
}

const height = await this._relativeKeyboardHeight(endCoordinates);

if (this.state.bottom === height) {
  return;
}

if (duration && easing) {
  LayoutAnimation.configureNext({
    // We have to pass the duration equal to minimal accepted duration defined here: RCTLayoutAnimation.m
    duration: duration > 10 ? duration : 10,
    update: {
      duration: duration > 10 ? duration : 10,
      type: LayoutAnimation.Types[easing] || "keyboard",
    },
  });
}
this.setState({ bottom: height });

};
}
`

           Try this simple solution:

           <TextInput
           ...
            multiline
            returnKeyType="done"
            blurOnSubmit
          />

Try this simple solution :)
           <TextInput
           ...
            multiline
            returnKeyType="done"
            blurOnSubmit
          />

Try this simple solution :)
           <TextInput
           ...
            multiline
            returnKeyType="done"
            blurOnSubmit
          />

@deekstone This worked for me, except in my case I used "next" for returnKeyType. Thank you!

Still no real solution. Disabling "passwords" autofill with textContentType="oneTimeCode", using multiline, or overriding KeyBoardAvoidingView is slop.

Still no real solution. Disabling passwords autofill with textContentType="oneTimeCode", using multiline, or overriding KeyBoardAvoidingView is slop.

no one said this is a permanent fix, but its the only one that works with less code.

Still no real solution. Disabling passwords autofill with textContentType="oneTimeCode", using multiline, or overriding KeyBoardAvoidingView is slop.

no one said this is a permanent fix, but its the only one that works with less code.

Sorry, not bashing any solution that works for people, It's just unfortunate that this issue is closed.

Agree the issue should not be closed. These are all workarounds to a real issue, and doesn't seem like there are any other open issues in this repo that are directly related?
If there are, would be good to link here.

Still happening, and none of the proposed solutions actually solve the problem. The ideal scenario would be, just to clarify:

No need to remove the password suggestion, for obvious reasons
No need to set the TextInput as multiline, since that will cause side-effects
No need to override the KeyboardAvoidingView, since not everyone will use that same template posted a few comments above

Wow, still no update. Are there any news regarding this?

Wow, still no update. Are there any news regarding this?

Make a fork with your own changes like everyone else

+1

It should not be closed!

It's even worse on iOS 18 (beta 8) 😕

It works even worse on iOS 😕

Are we the only persons in the world with this issue ? I don't understand why this flickering is not coming up on other apps? And why the simulator doesn't show the flickering ? IOS is widely used right now. Can't ignore this.

Try adding autoCorrect={false} to TextInput

Hate the .textContentType(.oneTimeCode) "fix".
Any update?

Are we the only persons in the world with this issue ? I don't understand why this flickering is not coming up on other apps? And why the simulator doesn't show the flickering ? iOS 17 is widely used right now. Can't ignore this.

Maybe because other apps are not using React Native?

I sometimes observe that problem in other apps so I guess there is something wrong with iOS. Hope iOS 18 will resolve the problems.

I sometimes observe that problem in other apps so I guess there is something wrong with iOS. Hope iOS 18 will resolve the problems.

I'm not sure https://github.com/facebook/react-native/issues/39411#issuecomment-2321221696

Try adding autoCorrect={false} to TextInput

Thanks! Helped in my case - I have email textInput with autoComplete set to username. Flickering is gone 👍

Thanks! Helped in my case - I have email textInput with autoComplete set to username. Flickering is gone 👍

@artiemez Would you mind pasting your TextInput code? I still have the flickering, no matter what I try for autoComplete or autoCorrect.

Thanks! Helped in my case - I have email textInput with autoComplete set to username. Flickering is gone 👍

@artiemez Would you mind pasting your TextInput code? I still have the flickering, no matter what I try for autoComplete or autoCorrect.
(Testing on iPhone 13 Pro with iOS 18)

                <Input
                    size="lg"
                    className="text-center"
                    label="email address"
                    enterKeyHint="next"
                    onSubmitEditing={handleSubmit}
                    placeholder="email address"
                    autoCapitalize="none"
                    autoComplete="username"
                    keyboardType="email-address"
                    autoCorrect={false}
                    showClearButton
                    {...field}
                />

I have the same problem with keyboardType="phone-pad" and autoComplete="tel"

Form inside KeyboardAvoidingView flickering on input AndreiRadchenko/scenery#7

Could you please specify which apps you encountered the same issue in?

Same issue here

In my case add keyboardType="email-address" solved this annoying bug

Has anyone discovered a good solution to this issue. In my Login/SignUp screens here are my Input Fields:

Email

Password
          />

Keep in mind that the keyboard only flickers when the email text input is changed, not the password.

I found this guys post on stackoverflow and it solved it for me. Simply adding autoCorrect= {false} to the input itself removes the flashing.
https://stackoverflow.com/a/78681410/4146738

in iOS 18.2 this is resolved.

in iOS 18.2 this is resolved.

It will be never resolved, use expo dom component and html input inside it (it's Webview but working rlly good)
Yea it sound crazy but its only working solution cuz React team does not want to fix it :/


Increased the default value of the max-connection-pool-size database setting (#7411)

Pull request opened by the merge tool on behalf of #7411

Merged into branches iso6 in c5939c985876b7c9fc7c4d7d901135fea34e0fd8


Don't overwrite existing STAC collection when doing a new extraction

Currently, when an extraction is done, the job_manager will always create a new STAC collection from scratch. This is inconvenient, if you want to do extra extractions on top of previous work.
Proposed solution: allow an existing STAC collection to be given as an input to the job_manager. The job_manager will then add the new extractions as items to the existing collection. In case no STAC collection is provided to the job_manager, it will create one from scratch.

Currently https://github.com/Open-EO/openeo-python-client/issues/558 is blocking this. To be discussed if this needs to be adressed in GFMap or in the Python Client.


Change block only if left click

Only change the tool if the player tries to actually use the tool on the block

Not working well with entities, the sword is taken after the hit is done.

Look at ClientPlayerInteractionManager::syncSelectedSlot()

ook at net.fabricmc.fabric.mixin.eventsinteraction.MixinClientPlayerInteractionManager

Solution is to let the sword be selected in case you attack an entity, makes things a lot easier.


Move source into a src subdir

This avoids accidental imports when running tests and forces the tests to run
against the installed version.
Should fix #1 .
Does this make sense, @nedbat @brechtm @rfleschenberg ?
It appears to me that --parallel + coverage combine perfectly works with the [paths] approach, while coverage run -a doesn’t.  I always get an output like this:
Name                                                                        Stmts   Miss Branch BrPart  Cover   Missing
-----------------------------------------------------------------------------------------------------------------------
.tox/py35/lib/python3.5/site-packages/prometheus_async/__init__.py             20      2      2      1    86%   30-32, 34->-3
.tox/py35/lib/python3.5/site-packages/prometheus_async/_util.py                 9      3      0      0    67%   16-18
.tox/py35/lib/python3.5/site-packages/prometheus_async/aio/__init__.py          3      0      0      0   100%
.tox/py35/lib/python3.5/site-packages/prometheus_async/aio/_decorators.py      36      0      6      0   100%
.tox/py35/lib/python3.5/site-packages/prometheus_async/aio/web.py              19     10      0      0    47%   21-23, 36-47
.tox/py35/lib/python3.5/site-packages/prometheus_async/tx/__init__.py           2      1      0      0    50%   8
.tox/py35/lib/python3.5/site-packages/prometheus_async/tx/_decorators.py       23     21      4      0     7%   9-44
src/prometheus_async/__init__.py                                               20      0      2      0   100%
src/prometheus_async/_util.py                                                   9      0      0      0   100%
src/prometheus_async/aio/__init__.py                                            3      0      0      0   100%
src/prometheus_async/aio/_decorators.py                                        36      0      6      0   100%
src/prometheus_async/aio/web.py                                                19      0      0      0   100%
src/prometheus_async/tx/__init__.py                                             2      0      0      0   100%
src/prometheus_async/tx/_decorators.py                                         23      0      4      0   100%
-----------------------------------------------------------------------------------------------------------------------
TOTAL                                                                         224     37     24      1    83%

I should note that coverage report runs on Python 3.5 so maybe that’s a reason?  Is this a bug or PEBKAC?

Another weird thing is that I only get “Not tracing…” output (with correct paths) but the result is correct.

[paths] is only used for coverage combine AFAIU; coverage combine does nothing if you don't use --parallel.
AFAIU if you don't use the above to do path munging, you're supposed to point coverage's --source= to the place where the package is installed (.tox/pyXX/.../).  That would be difficult, given that the name is dynamic. Luckily, you can also say --source=packagename (or the equivalent [run] source = ... in .coveragerc), and coverage will look it up from site-packages automatically.  Note that that method breaks if you have a local file called ./packagename.py or a local directory called ./packagename; this is one of the reasons it's nice to have a ./src/ at the top level.


See the link to github and Code; in the design.

As somebody trying out the SSO Demo
I can get to the Github source code for the page I am looking at
So I can see what code is running, understand its and understand how to implement it on my own website
Definition of done

[ ] mockup created for both web and mobile version

get a github icon that leads to the page with the source code

https://discordapp.com/channels/1029385699071381524/1039498641968205834/1085188328841822268

final work
https://www.figma.com/file/cvV48t0f7O2znT6QBxK0Zj/Tonomy-ID?node-id=4394-23181&t=9ldsIeD9hDGktdfh-4


[Shiny] Compatibility issues with Shiny v2.0+

Shiny v2.0 removed built in caching feature. It also introduced a reshaped logging feature relying on Microsoft.Extensions.Logging.
Workaround: Don't call .UseWhatever(...) from Shiny intergration package anymore but .AddWhatever(...) instead and set options fluently like caching and logging providers.
Fix: I'm working on a new release relying on Microsoft.Extensions.Logging.Abstraction to get things less specific/more generic, just like Shiny does. Caching feature should now be activated fluently with the provider of your choice (e.g. MonkeyCache or Akavache).

Removed from v4


fix tracking value

Hello there. I found a duplicated value and  followed the  "tracking" values logic to replace the wrong value.

Good catch! Thanks