Change import order in LayoutContainer

The import order affect css loading order.

Hi, thanks for your PR. Could you give me some details about this change? Why order matter?

If you look at the output of a page you'll find Header and Footer css styles are loaded before the LayoutContainer ones.
I don't think is a big issue if you use CSS Modules the right way, but can be confusing.
Usually I expect a global normalize.css to be loaded before any other style.
This was the philosophy of Cascading Style Sheet.

I understand your concern. But Header and Footer component use CSS Modules. So this is not a necessary change.

Usually I expect a global normalize.css to be loaded before any other style.

Well. If you work with Webpack long enough. CSS loading order is a mess. You can't guarantee which file will be loaded before which.
If this PR can eliminate confusion for new user. I'm hapy to merge it.
cc @MoOx

I'm new to webpack, react, css modules, postcss and almost everything in this stack, and each time I put my hands on it I regret myself to went this way.
I said "this is the future so I need to go this way", but I see confusion and over engineering everywhere.
I needed to change also IDE to work on this stack!
If you say so maybe there is something evil going on here.
I'd like to know and understand each piece of my puzzle, I don't like when (black) magic happen in an unpredictable way.
This is just a little insignificant fix that doesn't fix anything but at least now my reset code appear where I supposed it to be!

@AdamQuadmon YESSSS. This is the future.
FYI: https://github.com/webpack/webpack/issues/215
So when using webpack I recommend that you don't use the "Cascading" of CSS. I have to !important everything when I need to overide a global styling.

I see it.
Things are changing a lot (but I'm not sure for good).
Still feeling lost in the postcss word! Maybe the "post" here means CSS is dead or something like that.
PastCss, DeC(e)ss, RestCss(inPeace)...
Hope to find some guidelines to update my knowledge and habits.
Thanks for your patience with this old coder!

@AdamQuadmon thank you for raising this issue.
CSS loading order is not a mess due to webpack, it's due to how we load the components in the page.
Keep in mind that the same issue might happen with browserify (if you use it to load styles) since you won't really control how components are loaded.
For example, if you open one route that load a component, then another that load some others components (and styles) - if you do the opposite, you will have the CSS behing loaded in the browser with another order - so might affect your global rendering if you rely on global styles - that's a reason why inline styles and CSS modules have been created.
@AdamQuadmon Would you mind adding a simple comment on top of the global.css import like // Importing global CSS before other components an their styles ?
Another possibility is to import styles like normalize in the script/phenomic.browser.js using import "normalize.css" but you will need to tweaks the webpack loaders config for this. Maybe we should add this ability in the default boilerplate (css from node_modules as global css by default? This might create issue with components from npm that use css modules, but those might require some webpack config adjustements anyway)

I'm doing:
LayoutController/index.js
import "./reset.global.css"
import "./index.global.css"

(I split the file to better read the output code)
reset.global.css
@import "normalize.css";
@import "cssrecipes-defaults";

webpack.config.babel.js
//...
        {
          test: [ /\.css$/, /\.scss$/ ],
          include: path.resolve(__dirname, "node_modules"),
          loader: ExtractTextPlugin.extract(
            "style-loader",
            [ "css-loader", "postcss-loader", "sass-loader" ].join("!"),
          ),
        },
// ...
postcss: () => [
      require("stylelint")({
        ignoreFiles: path.dirname(__dirname, "node_modules/**/*.css"),
      }),
      require("postcss-reporter")(),
      require("postcss-import"),
    ],

I'm trying to leverage on PostCss as much as I can, I was used to stuff like Bootstrap and Foundation, and I'm trying to change my mindset

@AdamQuadmon that's a possibility indeed.
Do you want to handle the small add I requested for the comment?

@MoOx done

Thanks @AdamQuadmon!


2024-11-21_01-35-33_master-next_python3-boto3

Automatically created.

Backport failed for kirkstone-next, because it was unable to cherry-pick the commit(s).
Please cherry-pick the changes locally and resolve any conflicts.
git fetch origin kirkstone-next
git worktree add -d .worktree/backport-10446-to-kirkstone-next origin/kirkstone-next
cd .worktree/backport-10446-to-kirkstone-next
git switch --create backport-10446-to-kirkstone-next
git cherry-pick -x 648f121096e2b0cf0f7340c3221b76c7b0a1401c

Backport failed for scarthgap-next, because it was unable to cherry-pick the commit(s).
Please cherry-pick the changes locally and resolve any conflicts.
git fetch origin scarthgap-next
git worktree add -d .worktree/backport-10446-to-scarthgap-next origin/scarthgap-next
cd .worktree/backport-10446-to-scarthgap-next
git switch --create backport-10446-to-scarthgap-next
git cherry-pick -x 648f121096e2b0cf0f7340c3221b76c7b0a1401c

Backport failed for styhead-next, because it was unable to cherry-pick the commit(s).
Please cherry-pick the changes locally and resolve any conflicts.
git fetch origin styhead-next
git worktree add -d .worktree/backport-10446-to-styhead-next origin/styhead-next
cd .worktree/backport-10446-to-styhead-next
git switch --create backport-10446-to-styhead-next
git cherry-pick -x 648f121096e2b0cf0f7340c3221b76c7b0a1401c


Destroy or cancel connection scenario

Required handling disconnect char on IOS wallet similar to android Wallet.

Merging current PR to bring IOS cancel flow on develop branch.


Cell borders not working properly

NPOI Version
2.6.2
File Type

[ X ] XLSX

Issue Description
When creating a border for a merged cell, some of the sides come out wrong.
Here is an example:
  rowIdx += 2;
  currentRow = sheet1.CreateRow(rowIdx);
  currentRow.CreateCell(13).SetCellValue("Saving Summary");

  currentRow.GetCell(13).CellStyle = summarySavingsStyle;
  currentRow.GetCell(13).CellStyle.BorderTop = BorderStyle.Thick;
  currentRow.GetCell(13).CellStyle.BorderLeft = BorderStyle.Thick;
  currentRow.GetCell(13).CellStyle.BorderRight = BorderStyle.None;
  currentRow.GetCell(13).CellStyle.BorderBottom = BorderStyle.Thin;

  currentRow.CreateCell(14);
  currentRow.GetCell(14).CellStyle = summarySavingsStyle;
  currentRow.GetCell(14).CellStyle.BorderTop = BorderStyle.Thick;
  currentRow.GetCell(14).CellStyle.BorderLeft = BorderStyle.None;
  currentRow.GetCell(14).CellStyle.BorderRight = BorderStyle.None;
  currentRow.GetCell(14).CellStyle.BorderBottom = BorderStyle.Thin;

  currentRow.CreateCell(15);
  currentRow.GetCell(15).CellStyle = summarySavingsStyle;
  currentRow.GetCell(15).CellStyle.BorderTop = BorderStyle.Thick;
  currentRow.GetCell(15).CellStyle.BorderLeft = BorderStyle.None;
  currentRow.GetCell(15).CellStyle.BorderRight = BorderStyle.Thick;
  currentRow.GetCell(15).CellStyle.BorderBottom = BorderStyle.Thin;

  CellRangeAddress region = new CellRangeAddress(rowIdx, rowIdx, 13, 15);
  sheet1.AddMergedRegion(region);

In the code above you can see that I set a thick border for the following:

Cell 13: top and left
Cell 14: top
Cell 15: top and right

Which is not reflected in the excel file:

If you wondering what's the style applied to the cells, this is the code:
 XSSFCellStyle summarySavingsStyle = (XSSFCellStyle)workbook.CreateCellStyle();
  summarySavingsStyle.SetFont(font);
  summarySavingsStyle.Alignment = HorizontalAlignment.Center;
  summarySavingsStyle.VerticalAlignment = VerticalAlignment.Center;
  summarySavingsStyle.SetFillForegroundColor(new XSSFColor(new byte[] { 3, 252, 44 }));
  summarySavingsStyle.FillPattern = FillPattern.SolidForeground;

Update:
So, I found out that you cannot assign a style to a cell and then, later on, add the borders, so for cells with the same style but with different borders, you will need to create a new style just with a different border.
Now that I figure that out, I manage to create the spreadsheet as I wanted it to be, but it's a bit annoying because there is a lot of duplicated code, for one table, I need to have a style for each corner, another one for the central of the table sides and finally another style for the core cells in the table.
Basically, to build a table I had to copy the same style 9 times just to adapt the borders.

I believe it's not a bug, you can clone the existing style with CloneStyleFrom  methid and then change it.


Deploy to Bluemix button

We should start looking at injecting a 'Deploy to Bluemix' button. The button should leverage DevOps pipeline. Please see here
https://developer.ibm.com/recipes/tutorials/deploy-kubernetes-pods-to-the-bluemix-container-service-using-devops-pipelines/
Also we should have a deployment tracker in the button - see here at BluePic (https://github.com/IBM-Swift/BluePic) -- they track the number of times the app has been deployed.
@rmoe Please look into it for GitLab

@Tomcli maybe something you can look at in spare


Does your code support rendering from UV map?

It can be done using deferred shading, where you render a UV coordinate map instead of RGB values, and then use these to bilinearly index a texture afterwards using pure tensorflow ops. Unfortunately I don't have any sample code for this just now, but the idea of deferred shading is illustrated in samples/deferred.py (you would need to add another gbuffer channel for the UV values), and the bilinear texture sampling is similar to a spatial transformer net.

If time permits, I still hope that the author can update render with texture. It's a little difficult for people who are not familiar with texture to do so.
Thanks a lot~

I've added an example of rendering from a UV map using deferred shading in a6fee1fb. See samples/textured.py


@Version attribute isn't set as 0 when creating a new entity

Hi team,
I am upgrading com.vladmihalcea:hibernate-types-55 from 2.17.3 to 2.21.1, and get some failing tests due to @Version attribute value is not as expected.
The test is about creating a new entity and check its version is 0.
But actually the version is 1, which is not as expected.
I tried to test on several versions between 2.17.3 and 2.21.1. It seems that since 2.20.0, the issue starts happening.
Could you please help to check if is there any change about the default value of @Version attribute? Thank you :)

Hi @vladmihalcea ,
Thank you for your quick reply. I just figured out which case causes a problem.
I have an entity Books, which defines bookDetails is a nested Map with Publisher keys and another nested Map with BookTypes keys and BookInventory value as below:
@Type(type = "jsonb")
@Column(columnDefinition = "jsonb")
private Map<Publisher, Map<BookTypes, BookInventory>> bookDetails;

Here is my test case:

Check if bookId is existed in DB
2a. If it isn't existed, it will save a new record into DB
2b. If it is existed, just update a record
Once saving successfully in DB, the test do some assertion to validate.

After finishing a test, the console log shows what Hibernate did:

Hibernate:
select
books0_.id as id1_0_0_,
books0_.book_details as book_det2_0_0_,
books0_.version as version3_0_0_
from
sh_books books0_
where
books0_.id=?
-> This log matches with step 1

Hibernate:
insert
into
sh_books
(book_details, version, id)
values
(?, ?, ?)
-> This log matches with step 2a, because my given book_id is not in the DB

Hibernate:
update
sh_books
set
book_details=?,
version=?
where
id=?
and version=?
-> This is weird. Because we don't want to update anything. It could be the point, which causes the current problem of @Version.

Hibernate:
select
books0_.id as id1_0_0_,
books0_.book_details as book_det2_0_0_,
books0_.version as version3_0_0_
from
sh_books books0_
where
books0_.id=?
-> This matches with step 3

I also try to test another case of Map. By modifying bookDetails as a Map with String keys and Publisher values as below:
@Type(type = "jsonb")
@Column(columnDefinition = "jsonb")
private Map<String, Publisher> bookDetails;

Then run a test without any error. Here is the console log shows what Hibernate did:

Hibernate:
select
books0_.id as id1_0_0_,
books0_.book_details as book_det2_0_0_,
books0_.version as version3_0_0_
from
sh_books books0_
where
books0_.id=?
-> This log matches with step 1

Hibernate:
insert
into
sh_books
(book_details, version, id)
values
(?, ?, ?)
-> This log matches with step 2a

Hibernate:
select
books0_.id as id1_0_0_,
books0_.book_details as book_det2_0_0_,
books0_.version as version3_0_0_
from
sh_books books0_
where
books0_.id=?
-> This log matches with step 3

It didn't try to update a new record in DB.
https://github.com/vladmihalcea/hypersistence-utils/compare/hibernate-types-parent-2.19.2...hibernate-types-parent-2.20.0
I read the changes between com.vladmihalcea:hibernate-types-55 2.17.3 and 2.20.0, there is some change on Map also.
I updated my quick demo on github (https://github.com/dyleph/books-demo/commits/main). Could you please help to take a look?
I really appreciate 😄

@dyleph I won't have the time to investigate it, but most likely the problem is caused by the lack of equals and hashCode in all the Objects you store in that Map (keys and values).

Sorry @vladmihalcea about asking you in Easter time.
Not sure if I get your suggestion in wrong way, but I added @EqualsAndHashCode annotation in that Map.
However, we can keep this until you are back. Again, I am sorry and enjoy your holiday. :-)

In the meantime, you need to provide a Pull Request into this project that contains a test case demonstrating the issue. There are test cases that assert the number of executed SQL statements. You need to use those too.
So, you need to adapt your example into this project so that it becomes a test that will run automatically.

Hi @vladmihalcea ,
It seems that I don't have permission to push my testing branch into this project. Then I can create a PR for checking :(

You need to fork the repository and push to your fork.
Then, you can send the Pull Request.

Here is the pull request. I put it here as we can keep track.
Thanks @vladmihalcea :)


Wrap some utilities in flent ?

Issue description
I tried to run some tests with the newly packaged https://flent.org/ thanks to @mmlb.
The flent-gui works which was nice. So I tried to launch a few tests but I stumbled from error to error.
11:49:18 INFO: Starting http-1up test. Expected run time: 70 seconds.
11:49:18 ERROR: Runner HTTP latency failed check: No http-getter binary found in PATH.
11:51:58 INFO: Starting rrul_be_iperf test. Expected run time: 70 seconds.
11:51:58 WARNING: Found iperf binary (), but it does not have an --enhancedreports option. Not using.
11:51:58 ERROR: Runner TCP upload BE failed check: No suitable Iperf binary found.
12:35:29 INFO: Starting rrul_be_iperf test. Expected run time: 70 seconds.
12:35:29 ERROR: Runner Ping (ms) ICMP failed check: Cannot parse output of the system ping binary (/run/current-system/sw/bin/ping6). Please install fping v3.5+.

I had an iperf3 in PATH but it seems flent only supports iperf2. It could
I tried
nix-shell -p iperf2 http-getter fping flent --command "flent-gui"but it still doesn't pickup fping. Any idea  @mmlb ? I wonder if the package shouldn't wrap these utilities to make it easier to use ?
EDIT: I ran flent with -v and it didn't use fping because  WARNING: Found fping, but it does not appear to support IPv6. Not using.. It parses the output of fping -h which doesn't appear if not root hence the error. Running it as sudo, it picks up fping.
Steps to reproduce
launch flent-gui with the previous command then try "File -> Run new tests"
Technical details
Btw I packaged locally http-getter (necessary for some http requests tests)
{ stdenv, fetchFromGitHub, cmake
, curl, pkgconfig }:

stdenv.mkDerivation rec {
  name = "http-getter";
  version = "20180606";

  src = fetchFromGitHub {
    owner = "tohojo";
    repo = "http-getter";
    rev = "79bcccce721825a745f089d0c347bbaf2e6e12f4";
    sha256 = "1zxk52s1h5qx62idil237zdpj8agrry0w1xwkfx05wvv9sw4ld35";
  };

  buildInputs = [ cmake pkgconfig curl ];

  meta = with stdenv.lib; {
    homepage = https://github.com/tohojo/http-getter;
    description = "Simple getter for HTTP URLs using cURL";
    platforms = platforms.unix;
    license = licenses.gpl3;
  };
}

I did some wrapping there https://github.com/NixOS/nixpkgs/pull/41614

Wrapping was not such a good idea after all.

@teto can we resurrect this issue? I think we should probably add the tools as dependencies so that they will be available for use. We can add a flent-gui if necessary to get a package that only had that if necessary. I'm not sure why we want to wrap flent? So that it will refer to the versions of the tools it depends on?


Logging

Description of the feature

Is there a different logging level where it wont show this error?

I have the same errors, but the opposite request: how can I debug what the problem causing the error is?
2022-03-06T20:23:15.119071722+01:00 [ERROR] ** rainmachine.domain.net - 1004 DNS Validation Error
2022-03-06T20:23:15.030924884+01:00 [ERROR] ** agh.domain.net - 1004 DNS Validation Error
2022-03-06T20:23:13.022975416+01:00 [ERROR] ** pbs.domain.net - 1004 DNS Validation Error
2022-03-06T20:23:12.972342271+01:00 [ERROR] ** aghsync.domain.net - 1004 DNS Validation Error
2022-03-06T20:23:10.860061229+01:00 [ERROR] ** inverter.domain.net - 1004 DNS Validation Error
2022-03-06T20:23:10.875191799+01:00 [ERROR] ** jellyfin.domain.net - 1004 DNS Validation Error

I believe that error is coming from the Cloudflare python module.  I don't believe there is any more output to get out of it.

Thanks. I don't know how to fix it, the creation of the CNAMEs is working, but I costantly have those errors on all the records. Can't understand what the problem could be.


Initial implementation of Aite.

 * (A) Dockerfile.aite
   - Dockerfile to build Aite. This implementation requires
     kernel-level privileges, which can be added through
     --privileged, but --cap-add NET_ADMIN may be sufficient (for
     Docker), requires additional examination.
 * (A) srv/srv.go
   - Initial server implementation of Aite.
 * (A) proto/aite
   - Protobuf gRPC API for Aite. This interface allows a test to
     interface with Aite.
 * (A) cmd/aite
   - Binary acting as the Aite main.

To add:

Some form of testing -- likely in the form of an e2e test that can
validate functionality integrates with the kernel since there is
limited package logic here.

Leaving open for @akrentsel and @alshabib to take a look before submitting.


[api-minor] Respect the drawingDelay also when CSS-only zooming is used (issue 18022)

If a user manually calls PDFPageView.prototype.update() with a drawingDelay-option then it'll always be necessary to re-call the method without a delay afterwards, regardless of the maxCanvasPixels-value (e.g. even when CSS-only zooming is used).

/botio-linux preview

/botio integrationtest

I assume it's not really easy/possible to add a test for this particular issue

I believe it is possible to test this by listening to the pagerendered event while zooming, I can try providing a test in the next few days.

The change looks good to me aside from the comment above, and two questions:

I probably won't have time to create tests for this, unfortunately.

Given that this is part of viewer components, note https://github.com/mozilla/pdf.js/blob/master/web/pdf_viewer.component.js which "power" these examples, I figured that [api-minor] might not hurt. Although you're obviously correct that this isn't the primary library API.

I believe it is possible to test this by listening to the pagerendered event while zooming, I can try providing a test in the next few days.

If that's possible that'd be great; thanks! It's not a must-have for landing this PR, but if it's possible to have some (basic) testing for either this issue or CSS zooming in general that would increase confidence in the code.

[...] I figured that [api-minor] might not hurt [...]

I agree. Let's keep this as-is then.

@timvandermeij Unfortunately I don't think I'll be able to submit a test until next week.

Unfortunately I don't think I'll be able to submit a test until next week.

No worries; we're already happy that you're willing to help out with this, so no rush. Let's land this PR so the issue is resolved, and I'll open a follow-up issue for introducing tests for this functionality (since that scope is a bit broader than just this particular patch).
@Snuffleupagus Thank you for the patch!


running old flows against new src causes errors

Current Behavior
it is possible to get a situation where breakpoints are not defined

Expected Behavior
should guard or provide defaults
Steps To Reproduce
No response
Environment

Dashboard version: git source
Node-RED version:
Node.js version:
npm version:
Platform/OS:
Browser:

Have you provided an initial effort estimate for this issue?
I have provided an initial effort estimate

@gayanSandamal can you take this is a high priority please, we'll need this addressed before a release.

I will prioritise this


Incorrect behaviour when using two states

System configuration
OS: Windows 11
Bevy:  0.10.1 (from crates.io)
rustc --version: rustc 1.68.2 (9eb3afe9e 2023-03-27)
rustup default: stable-x86_64-pc-windows-msvc
What versions the problems happens on
This problem happens with bevy_asset_loader 0.16 and the latest version on the github (when I fetched it the latest commit was 5cd90672eb5b9a8a2127bd225c3f9d3a57c963d4)
The issue
I have been trying to implement some multistep loading in my game prototype by having two states -- one that tracks loading and the other tracks the game state.
It seems that bevy_asset_loader does something incorrect in such configurations and the assets don't get loaded.
Minimal examples
Program 1 (Single probing)
use bevy::{prelude::*, log::LogPlugin};
use bevy_asset_loader::prelude::{AssetCollection, LoadingStateAppExt, LoadingState};

#[derive(Clone, Copy, Debug, States, Default, PartialEq, Eq, Hash)]
enum Game {
    #[default]
    Booting,
    Play,
}

#[derive(Clone, Copy, Debug, States, Default, PartialEq, Eq, Hash)]
enum Loading {
    #[default]
    Loading,
    Done,
}

#[derive(Resource, AssetCollection)]
pub struct Collection {
    #[asset(path = "bevy.png")]
    _img: Handle<Image>,
}

fn probe(_res: Res<Collection>) {}

fn transition(
    mut next_g: ResMut<NextState<Game>>,
    mut next_l: ResMut<NextState<Loading>>,
) {
    next_g.0 = Some(Game::Play);
    next_l.0 = Some(Loading::Done);
}

fn main() {
    App::new()
    .add_plugins(MinimalPlugins)
    .add_plugin(AssetPlugin::default())
    .add_plugin(LogPlugin::default())
    .add_state::<Loading>()
    .add_state::<Game>()
    .add_loading_state(
        LoadingState::new(Loading::Loading)
        .continue_to_state(Loading::Done)
    )
    .add_system(transition.in_schedule(OnEnter(Loading::Done)))
    .add_system(probe.in_schedule(OnEnter(Game::Play)))
    .run();
}

Program 2 (repeated probing)
use bevy::{prelude::*, log::LogPlugin};
use bevy_asset_loader::prelude::{AssetCollection, LoadingStateAppExt, LoadingState};

#[derive(Clone, Copy, Debug, States, Default, PartialEq, Eq, Hash)]
enum Game {
    #[default]
    Booting,
    Play,
}

#[derive(Clone, Copy, Debug, States, Default, PartialEq, Eq, Hash)]
enum Loading {
    #[default]
    Loading,
    Done,
}

#[derive(Resource, AssetCollection)]
pub struct Collection {
    #[asset(path = "bevy.png")]
    _img: Handle<Image>,
}

fn probe(res: Option<Res<Collection>>) {
    info!("probe: {}", res.is_some())
}

fn transition(
    mut next_g: ResMut<NextState<Game>>,
    mut next_l: ResMut<NextState<Loading>>,
) {
    next_g.0 = Some(Game::Play);
    next_l.0 = Some(Loading::Done);
}

fn main() {
    App::new()
    .add_plugins(MinimalPlugins)
    .add_plugin(AssetPlugin::default())
    .add_plugin(LogPlugin::default())
    .add_state::<Loading>()
    .add_state::<Game>()
    .add_loading_state(
        LoadingState::new(Loading::Loading)
        .continue_to_state(Loading::Done)
    )
    .add_system(transition.in_schedule(OnEnter(Loading::Done)))
    .add_system(probe.in_set(OnUpdate(Game::Play)))
    .run();
}

What you expected to happen
The first program shouldn't crash. The second program should have printed probe: true
What happened
The first program crashed
     Running `target\debug\bevy_ald.exe`
2023-04-10T12:07:27.081547Z  INFO bevy_asset_loader::loading_state::systems: Loading state 'Loading' is done
thread 'Compute Task Pool (7)' panicked at 'Resource requested by bevy_ald::probe does not exist: bevy_ald::Collection', bevy_ecs-0.10.1\src\system\system_param.rs:460:17

The second program not only prints false, but also never prints true
     Running `target\debug\bevy_ald.exe`
2023-04-10T12:06:12.621932Z  INFO bevy_asset_loader::loading_state::systems: Loading state 'Loading' is done
2023-04-10T12:06:12.623797Z  INFO bevy_ald: probe: false
2023-04-10T12:06:12.625324Z  INFO bevy_ald: probe: false
2023-04-10T12:06:12.627005Z  INFO bevy_ald: probe: false
2023-04-10T12:06:12.628147Z  INFO bevy_ald: probe: false
2023-04-10T12:06:12.629495Z  INFO bevy_ald: probe: false
2023-04-10T12:06:12.630807Z  INFO bevy_ald: probe: false
2023-04-10T12:06:12.632035Z  INFO bevy_ald: probe: false
2023-04-10T12:06:12.633344Z  INFO bevy_ald: probe: false
2023-04-10T12:06:12.634580Z  INFO bevy_ald: probe: false
2023-04-10T12:06:12.635828Z  INFO bevy_ald: probe: false
2023-04-10T12:06:12.637343Z  INFO bevy_ald: probe: false
2023-04-10T12:06:12.638524Z  INFO bevy_ald: probe: false

Aren't you forgetting to add the collection to the loading state? Try adding
.add_collection_to_loading_state::<_, Collection>(Loading::Loading)

to your app after you add the loading state.

Aren't you forgetting to add the collection to the loading state? Try adding
.add_collection_to_loading_state::<_, Collection>(Loading::Loading)

to your app after you add the loading state.

Indeed! Sincerest apologies.
I have updated the examples to have the collections actually set to be loaded. Seems the problem needs two asset loads in a row to happen

Thanks a lot! I was able to reproduce and fix your issue :+1:


reCaptcha callback when finished loading.

You are using a timeout of 1000ms as a workaround for not knowing when the captcha is finished loading, but you can actually provide that callback in the options of the reCaptcha.create() call.
See: https://developers.google.com/recaptcha/docs/display#recaptcha_methods
and read the remarks for the create() function.

Hello
Any updates here? I seem to have my captcha flicker away all the time. (I'm guessing it doesn't load within the timeout wait of 1s.)
This is not viable for many of my customers.
Regards

@RobzInadE This issue is very old and is about captcha v1. We updated the library to use the new Google recaptcha a while ago in 2.0, so this thread doesn't apply to the latest release of the library.
If you are having problems with the latest release, then is surely not related to this thread so please open a new issue in this repo.
Thanks.


Unable to use JcePKCSPBEOutputEncryptorBuilder in bc fips 1.0.0

I am getting an error attempting to use the above mentioned class.  I searched through the sample code for usage (bcfipsin100) and I'm getting the same error when I run Pem.java with bc-fips-1.0.0.jar and bcpkix-fips-1.0.0.jar on the classpath.
Exception in thread "main" org.bouncycastle.operator.OperatorCreationException: unable to create OutputEncryptor: null
	at org.bouncycastle.pkcs.jcajce.JcePKCSPBEOutputEncryptorBuilder.build(Unknown Source)
	at bcfipsin100.pbeks.Pem.writeEncryptedKey(Pem.java:86)
	at bcfipsin100.pbeks.Pem.main(Pem.java:149)
Caused by: java.lang.NullPointerException
	at org.bouncycastle.jcajce.provider.BaseCipher.engineGetParameters(Unknown Source)
	at javax.crypto.Cipher.checkCryptoPerm(Cipher.java:1020)
	at javax.crypto.Cipher.init(Cipher.java:1245)
	... 3 more

The following line will cause error:
new JcePKCSPBEOutputEncryptorBuilder(NISTObjectIdentifiers.id_aes256_CBC).setProvider("BCFIPS").build("keyPassword".toCharArray());

I've tried several different algorithms and it doesn't seem to matter.  I'm using JDK 1.8.0_144.

This is issue BC-FJA-1.0.0-7 - it's fixed in 1.0.1, but you can work around it by making sure the unrestricted policy files are installed.

Thank you! That did it.  (Yay for Java 9 coming with unrestricted out of the box!)


Make the image dynamic according to weather

There is an ic_couple.xml in drawable. Add some more similar images according to different weather types.

sir, I want to contribute to this issue please assign me this .
but I have one problem I can add images according to the weather but how to make to dynamic according to the weather, the app does not tell the weather till now it is in a default mode


What is priority of styles compilation?

Context
I trying set styles for Typography component with className property, it is pre-generated with makeStyles.
Current result
After rendering i see, what is my class styles have low priority.As I understand it, the new engine should combine all styles into one class and prioritize. But that doesn't happen here.

Code sandbox: https://codesandbox.io/s/if8mv
Question
I noticed this behavior not only in this component. Also mui v4 dont have current problem, at least I haven't encountered her.
Can someone explain why this is happening?

I had the same issue, and I've resolved thanks to the migration guide:
https://mui.com/guides/migration-v4/#heading-style-library
The style library used by default in v5 is emotion. While migrating from JSS to emotion, and if you are using JSS style overrides for your components (for example overrides created by makeStyles), you will need to take care of the CSS injection order. To do so, you need to have the StyledEngineProvider with the injectFirst option at the top of your component tree.
Here is an example:
import * as React from 'react';
import { StyledEngineProvider } from '@mui/material/styles';
export default function GlobalCssPriority() {
return (
{/* Inject emotion before JSS /}

{/ Your component tree. Now you can override MUI's styles. */}

);
}
Better read the migration guide...

@elehaf16 Thanks for the detailed explanation.
@YuriyEmpty The styling engine is changed from JSS (makeStyles) in v4 to emotion (default) in v5. This is the fix from your codesandbox. https://codesandbox.io/s/goofy-grass-vy2hb


Input and Output parameters required to profile custom workflow activities

To investigate: Some report that plug-ins without input or output parameters cannot be profiled.
Also, what good is a custom workflow activity without input/output parameters?

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

ID: 9ae2bca0-76de-3f98-b0e7-65a137baafa2
Version Independent ID: eb803d04-bddc-0c43-3dcb-110187fbf379
Content: Debug Workflow Activities (Common Data Service) - PowerApps
Content Source: powerapps-docs/developer/common-data-service/workflow/debug-workflow-activites.md
Service: powerapps
GitHub Login: @JimDaly
Microsoft Alias: jdaly

@JimDaly Thanks for your feedback. We are closing this issue because we are either unable to find relevant information or reproduce this. If you're still experiencing the issue described here, please reopen or create a new issue.


Add QuickCheck detection and inject EQC macro when found.

This includes some general cleanup, but the primary feature is detection of QuickCheck and setting the EQC macro in the test profile's compiler options when it's present.
Common Test and EUnit run in the test profile by default, and the macro is only injected there - other profiles are unaffected - and only when it is not previously defined, so it won't cause duplicate definition errors.
This replicates some behavior from Rebar2 that was removed (with good reason) from Rebar3.
It's suitable for inclusion in a basho-specific tool like this plugin, though.

👍


While using Select it still gives access to other properties in GraphiQL

Bug description
When I am using Prisma select to select only a particular property, I can access all the other properties in GraphiQL.
Although they are always returned as null, I don't think they should even appear when I hit CTRL + SPACE in GraphiQL.
How to reproduce
I am using Prisma select like:
schema.extendType({
  type: 'Query',
  definition(t) {
    t.crud.blogs()
    t.crud.blog({
      alias: 'blog',
    })
    t.field('getAllTitles', {
      type: 'Blog',
      list: true,
      resolve(root, args, ctx) {
        return ctx.db.blog.findMany({
          select: {
            title: true,
          },
        })
      },
    })

My schema is simple as:
model Blog {
  id             String   @default(cuid()) @id
  title          String
}

Expected behavior
Now when I type the following in GraphiQL, I only expect it to return all title:
{
  getAllTitles {
    title
  }
}

But I can also type id in there without any errors like:
{
  getAllTitles {
    id
    title
  }
}

And I get even results like:
[
  {
    "title": "Join the Prisma Slack on https://slack.prisma.io",
    "id": null
  },
  {
    "title": "Follow Prisma on Twitter",
    "id": null
  }
]

I don't think id should be there when I use select specifically.
Environment & setup

OS: Mac OS
Database: SQLite
Prisma version: @prisma/cli: 2.0.1
Node.js version: v14.4.0
Nexus version: v0.24.2

Again not sure this is Prisma issue or Nexus, confused 😂

And I also get a red squiggly line over resolve saying:

Type '{ title: string; }' is missing the following properties from type 'Blog': id, createdAt, updatedAt, link, and 6 more

I've simplified the Schema above but I have 9 other fields.

The red squiggly lines won't let me generated the build using nexus build so my app doesn't work. Would love to know any workarounds?

Try running:
npx ts-node --transpileOnly src/yourapp.ts

This will build without checking for type errors.

Also, this is a nexus issue so I would appriciate if you can open this in the correct repository and close this one.
Here is the nexus repo: https://github.com/graphql-nexus/nexus

Opened up a new issue at https://github.com/graphql-nexus/nexus/issues/1158

It's not transpileOnly as it said Unknown or unexpected option: --transpileOnly, it's transpile-only so I ran:
$ npx ts-node --transpile-only api/app.ts

But it didn't generate any .nexus/build/api folder which is what I need to run as I saw that as the start command in the hello world example at nexus/examples repo.


refactor(api-docs): rework ApiExplorerPage to use EntityListProvider

Signed-off-by: Phil Kuang<EMAIL_ADDRESS>Hey, I just made a Pull Request!
Rework ApiExplorerPage to ultilize EntityListProvider to provide a consistent UI with the CatalogIndexPage which now exposes support for starring entities, pagination, and customizing columns.
Closes #4637

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[x] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Noting too that I'm not 100% sure this closes #5310, since that mentions using the pagination exposed by catalog-backed. The catalog page, and therefore this PR as well, do client-side pagination rather than backend pagination.

Noting too that I'm not 100% sure this closes #5310, since that mentions using the pagination exposed by catalog-backed. The catalog page, and therefore this PR as well, do client-side pagination rather than backend pagination.

good point, I'll remove that issue from this PR

@timbonicus updated this change with implementations for lifecycle and owner filters

Thanks Phil! This is looking really good, thanks for adding those missing filters. I hope you don't mind, I added one commit - primarily to add some spacing around the filters, and some minor language tweaks. I also added these new filters to the CatalogPage 😍
One more minor comment -- and we'll need @backstage/maintainers for final approval. I think this is just about ready to go, though!

thanks for the updates!

@timbonicus really sorry but I rebased my branch and forced pushed without pulling down your commit and accidentally erased your changes.

@Rugvip updated per your review comments, thanks!


Typo in user_playlist_remove_all_occurrences_of_tracks docstring

https://github.com/plamere/spotipy/blob/4c2c1d763a3653aa225c4af848409ec31286a6bf/spotipy/client.py#L510
s/to add/to remove/

Thanks @zhammer, fixed


winbox pcap cannot parse

I use winbox v3.18 to communicate with routeros 6.41.3, i captured before i click connect, and then i saved all data to pcap file format.
The problem is when i use winbox_pcap_parse to parse the pcap file, it print as follow:
Opening upload.pcap
Server side parsing error.
Server side parsing error.
Server side parsing error.
Server side parsing error.
Server side parsing error.
...
DONE
It seems that parse error, please help me

Hello @hanjideng. The parser only works on unencrypted connections. Furthermore, in order to debug this I'd need the pcap to reproduce the issue.

Now I find the reason, the winbox i use is the newest version, so it use safe mode as default, and i cannot turn it off.


Boolean-integer type compatibility.

This assertion fails on the following program:
.class TestExceptionsWhen {
  .method void Main () cil managed {
	.locals init (bool)
	  ldc.i4.1
	  stloc.0
	  ldloc.0
	  ldc.i4.0
	  cgt.un
	  ret
  }
}

The issue is that the arguments to the greater-than operation (cgt.un) are given incompatible Boogie types (int and bool) — the bool is due to the store and subsequent load to Boolean-typed local variable 0. In fact, this is valid CIL code (e.g., according to ECMA-335), since Boolean values are loaded onto the stack as zero-extended int32s. As far as I can tell, there are no relevant type-conversion operations here.
As far as context goes, this is a minimization of the code generated for the TestExceptionsWhen test on Mono, which is trips the assertion. I suppose that different code is being generated on Windows (?).
This code is based on code generated with this compiler:
$ csc
Microsoft (R) Visual C# Compiler version <IP_ADDRESS>916 (2ad4aabc)
Copyright (C) Microsoft Corporation. All rights reserved.

This duplicates edgardozoppi/analysis-net#10.


Parameter names should be at least 3 characters long.  Fixes #195

Build failed

I'm working on tests at the moment.  I just wanted to get the PR out there for feedback on the code.  Currently for testing I'm creating C# methods using short parmater names to make sure the method signature and their use in the method itself (which I almost forgot to change before doing the PR) match and the method still works correctly after renaming.

Build and tests passed.

Build failed

Please double check the build failure before merging

Created an issue for the build failure: https://github.com/mono/Embeddinator-4000/issues/230

Build and tests passed.

Build failed

Build failure fixed by PR #231

build

Build and tests passed.

@chamons Need updated review

Build and tests passed.


disconnect state support

The function I want to achieve is to report the disconnection (network cable disconnection) status. The idea is to try to ping the laser to determine if the network is disconnected when the data acquisition fails.
We recommend to use sick_scan_xd for further development.
Regarding the issue, there are two different timelimits:

the const timeout of 30 seconds is required, since a lidar response may take up to 30 seconds, and
the timelimit configured in the launchfile is used as max. timeout during startup (max. timeout for a sopas response).

Originally posted by @rostest in https://github.com/SICKAG/sick_scan/issues/160#issuecomment-1111840323

To detect or report the network status, you can run tools like ping or netstat (or other network tools) in a loop and parse the output, e.g. each second.
Note that sick_scan_xd automatically reconnects after network errors: https://github.com/SICKAG/sick_scan_xd#driver-states-timeouts. There is no need to monitor the network status, just to reconnect to the lidar after network errors.


Why payment channel and escrow only support XRP, what if it supports issued currency?

We want to escrow some issuing currency ,but found that escrow only support xrp. What if I change the code to support issuing currency?

We can’t stop you from changing the code to add such support, or from campaigning to get the amendment associated with your changes approved. If you want to submit a pull request, to include your changes in our release branch that would be cool and we would certainly review your code and consider it for inclusion.
But the change you are suggesting is quite extensive and is not as cut and dry. Please consider that unlike an XRP escrow, where the XRP itself is being held within the escrow object and there is no counterparty, an IOU escrow involves a counterparty and  represents an obligation of the that counterparty.
You will need to provide a mechanism that allows issuers to explicitly opt in to allowing their issuances to be escrowed and to decide how other, existing, features interact with IOU escrows.
Also challenging, such an object will need to thread against three accounts: the sender, the receiver and the issuer. No such support exists at this time, and adding it will likely require low-level changes.
This is certainly a challenging modification. Beyond the technical, I think that the semantics of an IOU escrow would be somewhat surprising to people, and that will be the bigger challenge.

As far as I understand Escrow, it is just a semi-automatic way to have funds sent somewhere after some timestamp has passed and/or to have a way to encode branching into a transaction ("If X gets revealed by Y then Z, otherwise Cancel"). I'm not sure why this would be unexpected functionality just because the currency that is transacted that way is not called XRP or because the base asset is held by a third party instead of nonexistent (XRP just stand for themselves).
There are some immediate concerns coming to my mind around freezing, (changing) issuer fees and QualityIn/QualityOut settings as well as a potential receiver not having enough "room" in a trust line for additional IOUs. I suspect IOU Escows actually might only be allowed to release into Checks instead of directly releasing funds into target accounts.
I don't see why issuers would have to opt in to have their issuances Escrowed, after all the same functionality could be provided invisible to XRPL off-chain too by handing limited control of an account to a smart contract. Unlike Freezing I would rather see IOU Escrow being implemented as "issuer opt-out" and "default on".
All in all I think IOU Escrow might be possible and I can see a lot of use cases for it actually, I wouldn't rank it as top priority on my wish list though - IOU PayChan for example would be ranked higher. This is of course just my opinion and it would be awesome to see a more concrete design for IOU Escrow. As Nik said though, it is definitely a challenge.

@MarkusTeufelberger, a couple of thoughts:

I don't see why issuers would have to opt in to have their issuances Escrowed

Issuers should be able to quickly sum up their total obligations; they do so by examining all the trustlines associated with their account.
Escrowed funds would not be kept in a trust line, but in the escrowed object itself, which means that, without the ability to opt-out, issuers would be, at a minimum, be forced to make changes to their accounting systems if this amendment were activated.
Interaction with existing IOU-specific features is also challenging, as we both pointed out.

Depending on the design, an Escrowed IOU could consist of both an Escrow object that contains the escrow related settings and a RippleState (towards the Escrow object) that contains the balance related stuff. That way iterating over RippleState objects would still give the correct, total outstanding balance - the downside is that it is now ~twice as expensive data wise than an XRP only escrow.

@nbougalis I have made a change in my code and it works fine except for that  total obligations is not easy to sum up.
I applied the change and just update on a chain without Escrow transaction before，there's no problem. I know that if I change on the public chain, it must be done with a new feature.
So,  do you have some suggestions for summing up total obligations ?  If I add every escrow to Issuer's dir, it seems not so elegant.

@MarkusTeufelberger thanks for your 'immediate concerns',  I will think more deeply about it.

If you can push your changes to a branch on GitHub and give me a link, I’d be happy to take a look at what you did.

@nbougalis I had tried to push my branch. But failed, seems I don't have the right ?
Git outputs:
$ git push --set-upstream origin feature/escrowForIOU
Enter passphrase for key '/c/Users/Jerry/.ssh/id_rsa':
ERROR: Permission to ripple/rippled.git denied to luleigreat.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists

@luleigreat On GitHub, the typical workflow is for you to create a fork (click the Fork button at the top right) and then push to your fork. You can use git remote add to add your fork as a remote.
You can then create a Pull Request (PR) at https://github.com/ripple/rippled/compare (click compare across forks).

Thanks very much @intelliot .
I have successfully made a pull request.

Thank you for opening PR #2672, @luleigreat! I'm going to close this issue and we can continue the discussion there.


UEFI sound not working.

I was able to get the UEFI script thing to work, and boot into Kubuntu 20.04, and KDE Neon, both had no sound, via the internal speakers, or via the headphone jack, i tried fiddling with alsa and whatever, didn't work.  Bluetooth worked though, and was able to get sound to work with that, but it had horrible sound quality(i don't exactly know why).

this 1) isn't a script issue, and 2) isn't a firmware issue. It's a kernel/driver/Alsa UCM config one.

Is it solvable?
On Wed, Nov 25, 2020 at 9:25 AM MrChromebox<EMAIL_ADDRESS>wrote:

this 1) isn't a script issue, and 2) isn't a firmware issue. It's a
kernel/driver/Alsa UCM config one.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MrChromebox/scripts/issues/138#issuecomment-733738225,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APJRLPOEGWEG4ZTLKTZ4YA3SRUHVLANCNFSM4UCLD74A
.

depends on the device/platform, distro, kernel, etc.
GalliumOS has working audio for some older platforms. Newer devices don't work regardless.  Check out https://www.reddit.com/r/GalliumOS and https://www.reddit.com/r/chrultrabook


replace hdfs download url

Codecov Report

Merging #1209 (2a661a4) into main (94f0d79) will increase coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1209      +/-   ##
==========================================
+ Coverage   57.57%   57.60%   +0.02%
==========================================
  Files         127      127
  Lines       21326    21326
==========================================
+ Hits        12278    12284       +6
+ Misses       7556     7551       -5
+ Partials     1492     1491       -1

Impacted Files
Coverage Δ

pkg/meta/sql.go
68.14% <0.00%> (-0.11%)
:arrow_down:

pkg/meta/redis.go
71.91% <0.00%> (+0.22%)
:arrow_up:

pkg/vfs/writer.go
79.66% <0.00%> (+1.01%)
:arrow_up:

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 94f0d79...2a661a4. Read the comment docs.


xCertReq: Permit ECDH key-lengths

Details of the scenario you tried and the problem that is occurring:
When attempting to use xCertReq to request an ECDH certificate, you typically use a key length of 192, 224, 256, 384 or 521. Currently if you try to specify one of those key lengths, the module throws an error of:
At least one of the values '256' is not supported or valid for property 'KeyLength' on class 'xCertReq'. Please
specify only supported values:
1024, 2048, 4096, 8192.

Patching this in for a one-off is simple enough, but it is a "dumb" patch that permits any of the key sizes for any of the certificates, even if they are not valid for that certificate type. Maybe that's a valid workaround for this module? If so, more than happy to provide a PR.
E.g. RSA keys should have 1024, 2048, 4096, 8192, but EDCH keys should have 192, 224, 256, 384, 521
Version of the Operating System and PowerShell the DSC Target Node is running:
Windows Server 2016, PSVersion 5.1.14393.1884
Version of the DSC module you're using, or 'dev' if you're using current dev branch:
<IP_ADDRESS>

Hi @mhenderson-so - good call out.
I think the best method is for the parameter to support all the available key sizes for RSA and EDCH keys but we will need to create an Assert-ResourceProperty function that will be called inside Test-TargetResource and Set-TargetResource that will validate the parameter combination.
I'll take a look at implementing this over this weekend.


Adds type=table to queries on sqlite_master. Avoids returning indices…

…, which could cause duplicate "create table" statements on dump.

Great thanks!


Adding function key support from F17 to F35

OSX supports everything by default,
Linux is also capable of supporting every function key,
Windows as I know support only up to F24
Bugsquad edit: This closes https://github.com/godotengine/godot-proposals/issues/4628.

I recommend using --doctool to correct the document format and pass the CI test.
https://docs.godotengine.org/en/stable/community/contributing/updating_the_class_reference.html

force-pushed the master branch from 645666f to 52880c3 11 hours ago in this commit, I've uploaded the updated class references,
I checked twice in the new commit, no new changes in the class references, so I think it has to work

based on the result of the last run, I have two options, I can rollback the "enum class Key {" section as it was originally and add the keys differently, or we modify the related test.

Thanks!


Update and rename team3.html to protocol.html

Othman4
Quraish313
dotsale
Axio01
Johnny174

I added team name to all the .html and added your team member names. Please make sure to read README.md to understand how to make changes. Thank you


Pull azure-functions and azure-functions-durable from PyPI

Currently, azure-functions and azure-functions-durable have out of date auto-generated docs. This appears to be due to the code source being on blob storage, instead of pulling from PyPI.
This PR aims to change this behavior so that the source code for these packages is pulled directly from the latest release on PyPI
@danieljurek, @gavin-aguiar

Reverting because this failed the docs build. Followed up in email to fix errors noted in the docs CI system.


dtf v1.2 --> v1.3 Migration

Migration from v1.2 to v1.3 progress. I'll update this as I start doing commits.
Modules

apkget (https://github.com/jakev/dtfmods-core/commit/aae99d76f3743676bb18d6629605cda2ac2644f3)
appdexdb (https://github.com/jakev/dtfmods-core/commit/e56266d9a5f0cf2dab87e35c0accb0b4d4fd718f)
autosign (https://github.com/jakev/dtfmods-core/commit/aae99d76f3743676bb18d6629605cda2ac2644f3)
bindiff (https://github.com/jakev/dtfmods-core/commit/ff7094f41a80f03bda38544b649e7c54cb9a7975)
classsearch (https://github.com/jakev/dtfmods-core/commit/ff7094f41a80f03bda38544b649e7c54cb9a7975)
devdb (https://github.com/jakev/dtfmods-core/commit/aae99d76f3743676bb18d6629605cda2ac2644f3)
devdiff (https://github.com/jakev/dtfmods-core/commit/aae99d76f3743676bb18d6629605cda2ac2644f3)
[Removed] drozer (https://github.com/jakev/dtfmods-core/commit/c9a2275cf35ff9e5dd67a89ea9bdd2ef46985cc6)
findimp (https://github.com/jakev/dtfmods-core/commit/a171325ef9f7f31b448f8cd30754790dce9708ef
framework2jar (https://github.com/jakev/dtfmods-core/commit/a171325ef9f7f31b448f8cd30754790dce9708ef
frameworkdb (https://github.com/jakev/dtfmods-core/commit/a171325ef9f7f31b448f8cd30754790dce9708ef
frameworkdexdb (https://github.com/jakev/dtfmods-core/commit/e56266d9a5f0cf2dab87e35c0accb0b4d4fd718f)
frameworkres (https://github.com/jakev/dtfmods-core/commit/ff7094f41a80f03bda38544b649e7c54cb9a7975)
getbins (https://github.com/jakev/dtfmods-core/commit/ff7094f41a80f03bda38544b649e7c54cb9a7975)
getpermissions (https://github.com/jakev/dtfmods-core/commit/aae99d76f3743676bb18d6629605cda2ac2644f3)
getsyslibs (https://github.com/jakev/dtfmods-core/commit/aae99d76f3743676bb18d6629605cda2ac2644f3)
[Removed] installdrozer (https://github.com/jakev/dtfmods-core/commit/aae99d76f3743676bb18d6629605cda2ac2644f3) (https://github.com/jakev/dtfmods-core/commit/c9a2275cf35ff9e5dd67a89ea9bdd2ef46985cc6)
intentsender (https://github.com/jakev/dtfmods-core/commit/aae99d76f3743676bb18d6629605cda2ac2644f3)
libinfo (https://github.com/jakev/dtfmods-core/commit/aae99d76f3743676bb18d6629605cda2ac2644f3)
mkaosp (https://github.com/jakev/dtfmods-core/commit/25bcbf640a3c24433fa3089c60c51a52709841d1)
newapp (https://github.com/jakev/dtfmods-core/commit/aae99d76f3743676bb18d6629605cda2ac2644f3)
oatdextract (https://github.com/jakev/dtfmods-core/commit/a171325ef9f7f31b448f8cd30754790dce9708ef
pbroadcasts (https://github.com/jakev/dtfmods-core/commit/a171325ef9f7f31b448f8cd30754790dce9708ef
permissions (https://github.com/jakev/dtfmods-core/commit/846377e7bf19e1bfebcd51e53fb04dda68b378c0)
platformdiff (https://github.com/jakev/dtfmods-core/commit/aae99d76f3743676bb18d6629605cda2ac2644f3)
process-all (https://github.com/jakev/dtfmods-core/commit/25bcbf640a3c24433fa3089c60c51a52709841d1)
[Added] resetserial (https://github.com/jakev/dtfmods-core/commit/356020dbb59c4cb3f0365ac4ebd39f30005380fd)
secretcode (https://github.com/jakev/dtfmods-core/commit/aae99d76f3743676bb18d6629605cda2ac2644f3)
sharedid (https://github.com/jakev/dtfmods-core/commit/a171325ef9f7f31b448f8cd30754790dce9708ef
sysappdb (https://github.com/jakev/dtfmods-core/commit/356020dbb59c4cb3f0365ac4ebd39f30005380fd)
syslibdiff (https://github.com/jakev/dtfmods-core/commit/a171325ef9f7f31b448f8cd30754790dce9708ef
sysservicedb (https://github.com/jakev/dtfmods-core/commit/846377e7bf19e1bfebcd51e53fb04dda68b378c0)
testperm (https://github.com/jakev/dtfmods-core/commit/ff7094f41a80f03bda38544b649e7c54cb9a7975)
userapps (https://github.com/jakev/dtfmods-core/commit/aae99d76f3743676bb18d6629605cda2ac2644f3)
usesperm (https://github.com/jakev/dtfmods-core/commit/a171325ef9f7f31b448f8cd30754790dce9708ef

Everything should be updated. All further issues will get their own issue #.


Accept a tabBarOnPress param

Changes
Accept a tabBarOnPress param for TabNavigator to handle tap events. If provided, this method will be called instead of the default, and the tab will not be changed automatically.
The API is consistent across Android and iOS (TabBarTop and TabBarBottom).
Hopefully resolves https://github.com/react-community/react-navigation/issues/314.
Usage
const MyTabs = TabNavigator({
  ...
}, {
  tabBarComponent: TabBarBottom /* or TabBarTop */,
  tabBarPosition: 'bottom' /* or 'top' */,
  navigationOptions: ({ navigation }) => ({
    tabBarOnPress: (scene, jumpToIndex) => {
      console.log('onPress:', scene.route);
      jumpToIndex(scene.index);
    },
  }),
});

Test Plan

Copy the code above into the NavigationPlayground example app
Run the app and try it out with both TabBarBottom and TabbarTop

This is very helpful to me！
非常感谢

@satya164 agreed. I'll try to refactor soon.

@satya164 thanks for the feedback. I've implemented tabBarOnPress as a Navigation Option per your suggestion. It does depend on one small change in react-native-tab-bar: https://github.com/react-native-community/react-native-tab-view/pull/231.
I understand you'd eventually like to use event emitters per your RFC, but by the looks of things that will probably take some time to spec and implement. I think this PR is a good workable solution until then (and may not need to change even after the proposal).
The older PR that adds an onTabPress callback does not allow for overriding/canceling/ignoring the tap event; this PR does, which is very necessary for several legitimate use cases that have been discussed in past issues.
What are your thoughts on these changes?

Note to reviewers: I'll be traveling for the next couple weeks. Hopefully this can be merged without issue, but I'll try to respond to comments when possible (or on May 23 when I return). Branch is rebased and up to date, and owners have permission to push directly to this branch:
git remote add cooperka https://github.com/cribspot/react-navigation.git
git fetch cooperka
git checkout -b tab-bar-on-press

Will tabBarOnPress receive the navigation prop? I want to open the drawer using a tabbar press and for as far as I know I need the navigation object for this.

jumpToIndex won't work...
alert(scene.index); shows the right index and works, but jumpToIndex won't call the function.

any progress ?

any update on this, @cooperka @satya164 ?

Just waiting to hear his thoughts; I can rebase and clean up for merge any time if this is the right direction.
Seems like the owners are quite busy right now, so in the meantime @gregorykan you can always fork this repo in order use this feature in your app right away if necessary. I can give you more instructions if you need help doing it, just let me know.

+1

+1

+1

+1

@cooperka I forked your repo and used tabBarOnPress as a navigation option on my tab navigator and the callback works great.  My app has a redux integration and I need to fire an action to the redux store when the tabBarOnPress is called.  Any idea how I can do that inside the TabNavigator's navigation options?

@nataroo hmm, if you could figure out a way to have dispatch in scope within tabBarOnPress that would be easy. Otherwise, you could use screen tracking with redux (this is what I do in my app, and it's very useful). There may be other solutions, too.

@cooperka Is there ETA on when this might be merged? What is holding this up, exactly?

@cooperka I looked at screen tracking with redux - from what I understand onNavigationStateChange will be called whenever the screen changes.  However in my case, I change the tabs sometimes programmatically but I want to fire the redux event only when the user changes tabs.  I don't think onNavigationStateChange would be able to differentiate between the two.  I am not able to get dispatch in scope within the tabBarOnPress.  tabBarOnPress is in a TabNavigator which is a const.  I am not sure how to connect a const to a redux store.  I tried returning the TabNavigator from a react component's render method, but that doesn't work either.

@danstepanov your guess is as good as mine 😕 it seems like the maintainers are very busy and haven't been merging very many PRs lately. If you need this in your app, you can always fork this repo and do it manually for now.

@nataroo could you simply use the dispatch provided, since you're already connected to redux? I haven't tested this, but it might work:
  navigationOptions: ({ navigation }) => ({
    tabBarOnPress: (scene, jumpToIndex) => {
      navigation.dispatch(...);
    },
  }),

@cooperka  That doesn't work.  I tried this:
navigationOptions: ({ navigation }) => ({
tabBarOnPress: (scene, jumpToIndex) => {
navigation.dispatch(ActionCreators.testMethod(parameter));
},
}),

I forked @cooperka branch and rebased it on top of the latest master:
https://github.com/fabriziomoscon/react-navigation/commits/tab-bar-on-press
I have tested it on iOS and Android and it works on both very well.
I understand this PR might not be in line with the future plans for react-navigation but today it fixes the problem I have!
Thank you @cooperka
My implementation is the following:
navigationOptions: ({ navigation }) => ({
        tabBarOnPress: (tab, jumpToIndex) => {
            const {
                dispatch,
                state,
            } = navigation
            const stackRouteName = ['FirstScreenTab1', 'FirstScreenTab2', 'FirstSceneTab3'][tab.index]

            // the new tab is not first in the stack
            if (tab.route.index !== 0) {
                // the tab wasn't focused
                if (tab.focused === false) {
                    jumpToIndex(tab.index)
                }
                dispatch(NavigationActions.reset({
                    index: 0,
                    key: state.key,
                    actions: [NavigationActions.navigate({ routeName: stackRouteName })],
                }))
            } else {
                jumpToIndex(tab.index)
            }
        },

I hope this could help others stuck with #314

Thanks @fabriziomoscon. I've rebased here again as well.

Solved my problem ! Thanks @cooperka !

+1

Need support on this #2239 .

+1

Example: Tapping Tab Always Navigates to Initial Screen of Tab’s StackNavigator
1. Install via package.json
Install SHA 187913749f61f27e109af841b5558235032652b7 from https://github.com/cribspot/react-navigation/tree/tab-bar-on-press
"react-navigation": "git://github.com/cribspot/react-navigation.git#187913749f61f27e109af841b5558235032652b7",

Of course this could change if the code in this PR changes.
2. Configure TabNavigator
Create a StackNavigator for each tab and use the following TabNavigatorConfig
export const TabScreens = TabNavigator({
  TabOne: {
    screen: TabOneStackNavigator
  },
  TabTwo: {
    screen: TabTwoStackNavigator
  }
}, {
  initialRouteName: 'Track',
  navigationOptions: ({ navigation }) => ({
    tabBarOnPress: (tab, jumpToIndex) => {
      if (tab.focused) { // if tab currently focused tab
        if (tab.route.index !== 0) { // if not on first screen of the StackNavigator in focused tab.
          navigation.dispatch(NavigationActions.reset({
            index: 0,
            actions: [
              NavigationActions.navigate({ routeName: tab.route.routes[0].routeName }) // go to first screen of the StackNavigator
            ]
          }))
        }
      } else {
        jumpToIndex(tab.index) // go to another tab
      }
    }
  })
})

Inspired by and slightly more automated than @fabriziomoscon's example above.

@cooperka have you already tried to rebase the fork on top of master? There are few fixes

+1

Status on this? Is there anything that I can help you with?

Hi @albinekb, as discussed above, it seems like the maintainers are busy and haven't been merging many PRs lately. We've tried pinging them several times to no avail. If you need this in your app, you can always do it manually for now, e.g.:
"react-navigation": "git://github.com/cribspot/react-navigation.git#1879137"

Allright! Just tell me if there's anything i can do to make this move :) If the maintainers want it implemented in another way, I can submit a PR for that. Really love this project and want to help if possible!
Thanks for the tip 👌

Hey all! Just wanted to say that there are a few new folks (myself included) joined to help get this project moving forward again. We're trying to get the issues under control and get some communication lines going before we start merging PRs. I don't have any ETAs at this point but know that we're trying to get the ball moving again 😄

@cooperka (et al.) thanks for your awesome fork that addresses this need.
Just want to point out a seemingly minor issue but actually makes this solution slightly less attractive as it stands (also want to document this for anyone else who stumbles on this thread). More of an issue with NavigationActions.reset, than tabBarOnPress, but this case is the only time I could imagine it would come up.
In your proposed solution, if the current index isn't 0 we dispatch a reset action like so:
navigation.dispatch(NavigationActions.reset({
  index: 0,
  actions: [
    NavigationActions.navigate({ routeName: tab.route.routes[0].routeName })
  ]
}))

The problem here is that it resets all of the state, including the scroll position on the initial route. For an app experience like Instagrams, you can imagine scrolling down in a feed, going down a little way stacking up screens and then wanting to reset right back to where you were initially. I've been looking around a little bit and can't find a solution for getting back to the initial state without resetting everything.
In any case, I support this PR 👍

fyi, it's not necessary to fork to have this functionality:
https://github.com/brentvatne/chain-react-conf/blob/master/navigation/CustomTabBarBottom.js
https://github.com/brentvatne/chain-react-conf/blob/master/navigation/MainTabNavigator.js#L68-L87

@brentvatne I would argue that installing from a minor fork is much easier than copying in a whole custom component just to handle onPress :) but thank you for the awesome example!

to each their own! either way, this type of functionality is pretty important

+1

First of all, I want to make clear that I strongly support this PR. Tho I think there's a much simplier and safe (I don't trust forks from betas): override the TabBarComponent.
Here's a working example
// CustomTabBar.js
import React from 'react'
import { NavigationActions, TabBarBottom } from 'react-navigation'

const getCurrentTabRoot = (state) => {
  return state.routes[state.index].routes[0].routeName
}

const resetTabNavigation = (dispatch, rootRouteName) => {
  dispatch(NavigationActions.reset({
    index: 0,
    actions: [NavigationActions.navigate({
      routeName: rootRouteName,
    })],
  }))
}

export const Lowerbar = (props) => {
  return <TabBarBottom
    {...props}
    jumpToIndex={(index, ...args) => {
      // if trying to move to the same tab
      if (index === props.navigation.state.index) {
        // reset the navigation
        resetTabNavigation(
          props.navigation.dispatch,
          getCurrentTabRoot(props.navigation.state),
        )
      }

      // in any case proceed with normal jumpToIndex functionality
      props.jumpToIndex(index, ...args)
    }}
  />
}

This small component will be added as TabNavigatorConfig option
import CustomTabBar from './CustomTabBar'

TabNavigator({
  MyRoute: {
    screen: MyRoute,
  },
  /* more routes */
}, {
  tabBarComponent: CustomTabBar,
})

Thanks for the example @sospedra! Luckily this no longer requires a fork as my other PR was merged a while ago. I've updated this PR description accordingly.

@sospedra how would you make it work for TabBarTop?
@cooperka I am totally confused by your statement. Could you please add more context? Are you talking about this issue? Was a PR merged?

Hi @fabriziomoscon, I'm replying to @sospedra's concern that this PR relies on a forked version of react-native-tab-view (specifically https://github.com/react-native-community/react-native-tab-view/pull/231). This is no longer true, because that PR was merged and included in v0.0.63 so a fork of react-native-tab-view is no longer necessary.

@fabriziomoscon I didn't tried, but I'm pretty sure that would be same but overriding TabBarTop instead of TabBarBottom

@spencercarli what's stopping this from being merged? If I create a new PR towards master, can you merge it? Do you want anything changed? It's such a small change it feels bad to let everyone wait for it...  💯  I'm happy to help! Thanks.

@albinekb please don't create a duplicate PR, that will just slow things down even more 😊  as repeated above, the team is bogged down right now so things are just moving very slowly.
If you want to use this code right now, feel free to reference my fork directly. It's rebased and up-to-date as of yesterday, but I'm happy to rebase again if needed.

I tried your fork, but got this error
Warning: Failed prop type: The prop `onIndexChange` is marked as required in `TabViewAnimated`, but its value is `undefined`.
    in TabViewAnimated (at TabView.js:195)
    in TabView (at withCachedChildNavigation.js:60)
...

Seems like the fix is in this PR https://github.com/react-community/react-navigation/pull/2527
It would be awesome if you had time to rebase your fork, otherwise tell me and I'll set up my own and post it here. Thanks @cooperka 🙌

@albinekb done!

Thank you @cooperka for your efforts!
I'm using your changes to display a screen as a modal from the tab bar, which is not possible now without workarounds.

My implementation is as the following:
const Tabs = TabNavigator({
  TabOne: {
    screen: TabOneStack,
    // icon and other options
  },
  TabTwo: {
    screen: TabTwoStack,
    navigationOptions: ({ navigation }) => ({
      tabBarOnPress: (tab, jumpToIndex) => {
        navigation.navigate('TabTwoModal');
      },
    }),
  },
  TabThree: {
    screen: TabThreeStack,
    // icon and other options
  },
});

const App = StackNavigator({
  Tabs: {
    screen: Tabs,
  },
  TabTwoModal: {
    screen: TabTwoStack,
  },
}, {
  mode: 'modal',
  headerMode: 'none',
});

🎉 🎉 🎉

Awesomeness, thanks for merging this! ❤

❤

I have tried to put the param but I still not able to get the callback. Can anyone tell me where it went wrong?
Wallet: {
    screen: WalletStack,
    path: 'wallet',
    navigationOptions: ({navigation}) => ({
      tabBarOnPress: (scene, jumpToIndex) => {
        console.log('test', scene.route);
        jumpToIndex(scene.index);
      },
      tabBarLabel: TAB_TEXT.TAB_WALLET,
      tabBarIcon: ({tintColor}) => (<Image
        source={require('../images/icon_wallet.png')}
        style={[
        navStyles.tabar_icon, {
          tintColor: tintColor
        }
      ]}/>)
    })
  },

@endtojunc are you using the version from NPM or are you using the master branch?

@rmevans9 I'm using the version from NPM. How can I use the master branch? Thanks!

This has not been released yet so it won't be on NPM. If you want to use the master branch directly you can follow this:
https://stackoverflow.com/questions/17509669/how-to-install-an-npm-package-from-github-directly

after this it works
npm install<EMAIL_ADDRESS>

@antakov it's best practice to avoid referring to a dynamic branch like that (it defaults to master which changes over time). A better solution would be to include a specific commit hash so it doesn't change unexpectedly:
npm install<EMAIL_ADDRESS>

does anyone know how to implement scroll to top using tabBarOnPress?

@cooperka do I have to have GIT installed to include that specific commit on my project?

Hmm, I have no idea @JoseVf! My best recommendation is to search for that error online. I would guess you probably do need git, since it's installing from a git repo.

Yes @itswaze use tabBarOnPress with  scrollTo If you need more help feel free to join this slack and contact me there. I'm @albinekb there too :) Don't want to clutter this issue with chat/support 😄

tabBarOnPress does not call at all for me.

@cooperka Hi. I really appreciate your contributions. I want to reset the whole stack navigation of my tabs app.
Tabs Nav(Parent Navigator)
Tab 1 (Stack Nav)
Tab 2 (Stack Nav)
Tab 3 (Stack Nav)
I used tab tabBarOnPress to reset stack:
tabBarOnPress: (tab, jumpToIndex) => {
const {
dispatch,
state,
} = navigation
if (tab.focused) {
dispatch(NavigationActions.reset({
index: 0,
actions: [
NavigationActions.navigate({ routeName:"HomeScreen" })
]
}))
} else {
jumpToIndex(tab.index) // go to another tab (the default behavior)
}
}
The issue is:
After the reset, it says that "There is no route defined for key HomeScreen" but I can see in console that homescreen component has been executed coz I have put some console statements there.
Please help me regarding this.

I have the same issue @bakarshams, I think it's a bug with reset, but I have no solution for it now, I'm working around it with very ugly hacks.

@cooperka is there any way to set screen property nullable/not required? I have in my tabBar a logout button that just shows up a modal with an Accept and Cancel, but I have to create a empty screen (actually just the necesary thing to be referenced as a screen) just to avoid the error (example code below).
const tab_bar = TabNavigator({  // This tabNavigator is inside a stackNavigator, wich contains the 'login' view
   Home: {
     screen: Home
   },
   Logout: {
     screen: Logout     // Empty screen, useless in this specific case
       ,navigationOptions: ({navigation}) => ({
           tabBarOnPress: (scene, jumpToIndex) => {
               return Alert.alert(   // Shows up the alert without redirecting anywhere
                   'Confirmation required'
                   ,'Do you really want to logout?'
                   ,[
                     {text: 'Accept', onPress: () => { navigation.dispatch(NavigationActions.navigate({ routeName: 'login' }))}},
                     {text: 'Cancel'}
                    ]
               );
           },
       })
    },
});

@JoseVf it sounds like you're looking for custom tab items that don't refer to an actual scene. That's not currently possible without overriding tabBarComponent (see docs here). If you override that component you can make the tabs do whatever you want.

@albinekb How to handle ScrollView scrollTo with tabBarOnPress. Can you please give me an example?

This is now available in prerelease "react-navigation": "^1.0.0-beta.13" :)

Hi @sanjayholla94, that's a strange issue you're facing! I recommend opening a new issue to discuss more easily. Good luck!

Created a new issue for the same: https://github.com/react-community/react-navigation/issues/2725

Does anyone know how to implement both scroll to top and reset stack with tabBarOnPress?
Like, the first click scrolls to top and the second one resets the stack.

Yes @itswaze, you need to

Check what tab you're on

If it's the same tab

Check if it's focused

If it's focused check the scroll position

And add the desired logic for which action to call, hit me up in the slack i linked to you if you wanna chat :) Don't want to have support in this issue 👍

Hello everyone, I'm new to React Native and have been playing with navigation to learn how it works. My problem here is that I have a main tab navigator with three tabs, and the first app have three stack navigators inside, Home, Module 1 and Module 2.
When I enter the app, Home is showed then I have to click for the other modules. So I want to tap the first tab button to navigate back to the Home screen, but resetting the tab stacks, so it is not possible to swipe back using the stack header or the android back button.
My code is the following:
Main tab navigator:
export const MainTabs = TabNavigator({     Home: {         screen: HomeStack,         navigationOptions: ({ navigation }) => ({             tabBarIcon: ({ tintColor }) => <Icon name="home" size={22} color={tintColor} />,             tabBarOnPress: (tab, jumpToIndex) => {                 console.log(tab.focused);                 if (tab.focused) {                     jumpToIndex(tab.index);                 }             },         }),     }, .......
The Home stack:
export const HomeStack = StackNavigator({     Home: {         screen: HomeScreen,     },     Module1: {         screen: Module1Stack,     },     Module2: {         screen: Module2Stack,     }, }, {     headerMode: 'none', });
jumpToIndex is not working (I'm using the master branch) so I tried with the following:

This one works, but creates stacks that can be navigated back with a left to right swap (iOS only) and the android back button:
Home: {       screen: HomeStack,       navigationOptions: ({ navigation }) => ({           tabBarIcon: ({ tintColor }) => <Icon name="home" size={22} color={tintColor} />,           tabBarOnPress: (tab, jumpToIndex) => {               navigation.navigate('Home');           },       }),   },

On the TabNavigator second parameter I've set swipeEnabled: false,, but I can still swipe the stack inside the tab...
The full code is in my repo: https://github.com/marceloHashzen/navigation

@beausmith is your solution still valid? For me doesn't work since tab.focused is always false.

Hi all,
It's really great to have the tabBarOnPress available!
However, I'm stuck with an issue. The tab navigator is not my top navigator but a screen in a StackNavigator. Something like this:
const AppNavigator = StackNavigator({
    main: { screen: MainScreenNavigator },
    login: { screen: LoginScreen },
    recover: { screen: RecoverScreen },
    register: { screen: RegisterScreen },
    photo: { screen: PhotoScreen },
    intro: { screen: IntroScreen }
});

const MainScreenNavigator = TabNavigator({
    home: { screen: HomeNavigator },
    mywishlist: { screen: MyWishBoxNavigator },
    friends: { screen: FriendsNavigator },
   messages: { screen: MessagesNavigator },
   more: { screen: MoreNavigator }
});

Unfortunately I was not able to make @beausmith  above code work. The issue was that dispatching the reset action was throwing an error because the route name must be from the previous screen  from MainScreenNavigator, but not from the TabNavigator.
My TabNavigator navigationOptions and tabBarOnPress looks like this:
    navigationOptions: ({ navigation }) => ({
      tabBarOnPress: (scene, jumpToIndex) => {
        const { route, focused, index } = scene;
        if (!focused) {
          if (route.index > 0) {
            const { routeName, key } = route.routes[0];
            navigation.dispatch(
              NavigationActions.reset({
                index: 0,
                key,
                actions: [
                  NavigationActions.navigate({ routeName })
                ]
              })
            );
          } else {
            jumpToIndex(index);
          }
        }
      },
    }

Any hints will be highly appreciated.
Thanks in advance!

@albinekb With react-navigation beta 22 and expo sdk 24, your solution returns a redbox of jumpToIndex is not a function. I read the breaking changes for all the recent releases and there was a recent modification to tabBarOnPress to make jumpToIndex available. Any idea what might be wrong?

@danstepanov there was a breaking change a few versions ago for tabBarOnPress. @albinekb example would now be
class Screen extends React.Component {
  static navigationOptions = (props) => {
    return {
      tabBarOnPress: ({ scene jumpToIndex }) => {
        if (!scene.focused) {
          jumpToIndex(scene.index)
        } else {
          props.navigation.state.params.handleTabBarPress(scene)
        }
      },
    }
  }

  ...
}

@spencercarli I have implemented the following and still get the following red box:
static navigationOptions = ({ navigation }) => ({
    tabBarOnPress: (tab, jumpToIndex) => {
      if (!tab.focused) {
        jumpToIndex(tab.index);
      } else {
        navigation.state.params.handleTabBarPress(tab);
      }
    },
});

I have updated the code to this and now params on navigation is undefined
tabBarOnPress: ({ scene, jumpToIndex }) => {
      if (!scene.focused) {
        jumpToIndex(scene.index);
      } else {
        navigation.state.params.handleTabBarPress(scene);
      }
    },
});

Combining both methods and  using the following tabBarOnPress, it works!
tabBarOnPress: ({ scene, jumpToIndex }) => {
      if (!scene.focused) {
        jumpToIndex(scene.index);
      } else {
        _scrollView.scrollToIndex({ animated: true, index: 0 });
      }
    },
});

Great @danstepanov 💪

Is there an ETA for this being released?

Hi All,
My project mainly using react navigation tabnavigator for navigation to screen and could like to change tab to HomeScreen. When I copy captioned code "jumpToIndex" is not define, I can't make change in tab navigation.
My Router is:
Stacknavigation:
Home screen -- StackNavigator
----One screen (Tab) --TabNavigator
----Two screen (Tab) --TabNavigator
Profile screen -- StackNavigator
----Three screen (Tab) --TabNavigator
----Home screen (Tab) --TabNavigator
My Code is:
export const HomeStack = StackNavigator({
Home: {screen: TabNavigator(
{
One: {screen: One},
Two: { screen: Two},
},
{
tabBarComponent: TabBarBottom,
tabBarPosition: 'bottom',
}
)},
Profile: {screen: TabNavigator(
{
Three: {screen: Three},
Home: { screen: Home},
},
{
tabBarComponent: TabBarBottom,
tabBarPosition: 'bottom',
}
)},
When I click Home screen (Tab) at Profile screen, it go to Home screen. But the Tab dose not change to 'One screen (Tab)' and Two screen (Tab), it still show 'Three (Tab)' and 'Home (Tab)'
I don't know how to write the code.

Expected behaviour when pressing a tab:

if the current tab is selected and the initial route is focused => do nothing
if the current tab is not selected => jump to the new tab
if the route is not the initial one => pop all stacked routes from the sstack to reach the initial route
(this doesn't take scrolls into considerations)
I am not sure if I will be able to remove this code completely with version 2. Does anybody know?

Using version 1.5.2 I could simplify a lot the code reported in my previous comment.
navigationOptions: ({navigation}) => ({
        tabBarOnPress: ({scene, jumpToIndex}) => {
            // the new scene is the first in the stack
            if (scene.focused === true && scene.route.index === 0) {
                return
            }
            if (scene.focused === false) {
                jumpToIndex(scene.index)
            }
            if (scene.route.index !== 0) {
                navigation.popToTop()
            }
        },
    })

Any comment or correction is greatly appreciated

why mine doesnt work using any onpress example from everyone ?
the one that works for me is
tabBarComponent: ({ jumpToIndex, ...props }) => (
<TabBarBottom
{...props}
jumpToIndex={(index) => {
if(props.navigation.state.index === index) {
props.navigation.dispatch(NavigationActions.back());
} else {
jumpToIndex(index);
}
}
}
/>
),
any hint guys ?

@Kodax9 - please create a new issue and follow the issue template if you believe you have found a bug


VSCode Animations: Please install Apc Customize UI++ for animations to work

I successfully installed it but it still prompts me

What happens if you reload vscode, or click the install button?

Still show this pop-up window.

Ok, could you possibly try reinstalling this extension or try quickly switching the install method to custom css and js and back quickly?

I found the reason, it was caused by a setting in vscode
extensions.experimental.affinity

Ok great.


Storybook v7

Hi,
Thanks for all the work developing this plugin.
at my place we decided to already upgrade to Storybook v7 due to better Vue support. We're wondering if there are already plans here to make the plugin ready for Storybook 7. Considering it's already on release candidates I doubt there will be any big changes.
From the migrations notes
https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#70-core-addons-changes
https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#70-addon-authors-changes

Hey,
I'm super open to making this Storybook 7 safe, i'll see what I can do over the bank holiday weekend

Hey folks, i've pushed a canary release 2.0.0--canary.12.aa9de47.0
Could I trouble you to test in your environments please?
Once I've had a few folks say they're happy with it then i'll cut 2.0.0
It's not really a breaking change, but thought best to mark it as due to the Storybook Preview pattern changing.

@geometricpanda Canary release compiles without warnings && works as intended in SB v7.0.2 with Vue v2:

Works like a charm! Question though, since in Storybook 7 they seperated docs and canvas different, is it possible to show the badges on the docs page? Or do I need to make a new enhancement request for this?
Thanks for the good work!

@Sephyr0s Yeah i noticed that, i'll keep looking into it, but thanks to you and @tommiv for testing - i'll release 2.0.0 now


Reading the entities provided by the user

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add Docker environment & web demo

Hey @mehdidc! 👋
We find your model so cool that it generates images from prompts ultra fast!
This pull request makes it possible to run your model inside a Docker environment, which makes it easier for other people to run it.  We're using an open source tool called Cog to make this process easier.
This also means we can make a web page where other people can try out your model! View it here: https://replicate.ai/mehdidc/feed_forward_vqgan_clip
Claim your page here so you can edit it, and we'll feature it on our website and tweet about it too.
In case you're wondering who I am, I'm from Replicate, where we're trying to make machine learning reproducible. We got frustrated that we couldn't run all the really interesting ML work being done. So, we're going round implementing models we like. 😊

Awesome, this is super cool, thank you very much!


Add assert that the root widget has been attached.

nit: We require from our contributors that they provide meaningful PR descriptions that add some context to why a change was made. We should lead with a good example :)

Ok, I restructured this to better solve the problem it was intending to solve (and updated the PR description to match the template).
PTAL.


Investigate resident set vs heap total memory difference

Lodestar nodes show a significant difference between the process resident set or total process memory and the total heap size. As far as I'm concerned, there's no other large memory item that could justify a 500MB difference

This issue is to track research into what could cause this difference:

[x] Worker threads: I've disabled all workers (second part of the chart above) and while the total process size is slightly lower the difference is roughly the same
[ ] ??

It might be array buffer backing stores or native code package allocation? How do we debug this? Need to investigate that first. Core dumps?


Associate a list of People with Locations to auto. treat as Owners

Associate an optional list of People with each Location who would automatically be treated as Owners of Events at that Location.

Requires #18


realtime: 32 bits compatibility

Fix realtime::Timespec services on 32 bits systems and Windows by moving some critical code to C. This PR does not change the API. However, I have plans for a future revamp of the API to reduce the number of mallocs.

test osx please

Break osx http://gresil.org/jenkins/view/Intégration/job/CI Github OSX/434/testReport/ :(

test osx please


Add Media Services

These resources use custom VPC.

[x] MediaConnect
[x] MediaLive Inputs
[x] MediaStore Container Policy

Added MediaConnect check.

Added Media Store Policy check.


Extending the columns similar to nisq analyser

Adding the columns to execution tab of implementation

implementation-execution part LG automatic refresh-branch can be deleted? nisq-analyzer part: execute button does not work.

compiler-comparision-automated-refresh can be removed


Open a new tab from the working directory of the current tab

New tabs always start from the working directory before starting tab, rather than the tab where you were.
Example
tab home
Ctrl-t foo
cd projects/foo
kak # runs in projects/foo
Ctrl-t foo/server
make serve # runs in home

Ah, interesting.  This would be a nice feature.  The 'current directory' context was something I added for the fuzzy finder, so that switching between workspaces was more intuitive.  It could be hooked into the new tab directory as well.
I'm also planning a new feature #242 in v0.6.0 that would help.  When you want to open foo/server/ it would notice foo/ exists, and inherit the initial directory/YAML config of foo/

It looks a nice way to inherit / not inherit a working directory without configuration.  Let’s see how it is in practice.


Rationalize how database connections and transactions are used

Rationalize how database connections and transactions are used
The current connection or transaction is now part of the Context class along with the log context, and the database can only be interacted with through a Context object.
There are some incidental changes related to this work:

Database reconnection code was moved out of the stream implementation and into the Postgres class itself. This is not something that should be handled by the stream code.
Refer to a connection pool as a pool instead of a "connection" in the backend.
Replace pg-promise with pg. pg-promise is a thin layer on top of pg and it is causing problems with its incomplete typings and, uh, unique approach to transactions: you cannot use a connection after ending a transaction with it.

And to reduce the number of major versions this also includes:

Removal of the Kernel.errors and Kernel.cards fields and privatization of the sessions field. Access to first two fields can be replaced by by the exported errors module and CARDS constant. The admin session can be retrieved through the adminSession method.
The Kernel.backend field is now private. withPostgres returns the connection pool that can be used by external code that must connect to the same database.

Plus some minor internal reorganization.
Change-type: major
Signed-off-by: Carol Schulze<EMAIL_ADDRESS>

PR is not even near a usable state

Getting close to ready. Need more work on the transaction stuff and find out why some tests are hanging.

TODO:

[ ] Finish implementing Context.withTransaction
[ ] Finish fixing test/integration/backend/postgres/jsonschema2sql/index.spec.ts
[ ] Do a final review of the changes. The actual meaningful changes are not as big as the diff line count might suggest.

I've added code to serialize queries within the same connection/transaction in an attempt to fix another issue. The code is still there but I'm not sure if it's necessary or if node-postgres does that already.

just one test failure to clear

@balena-ci I self-certify!


Unknown device

Hi tananaev,
I have issue with device imei i putted log below.
can you please help me what was the issue.
2015-12-10 20:23:07  INFO: Query not provided: database.selectDevicesAll
2015-12-10 20:23:07  WARN: Unknown device -<PHONE_NUMBER>42254
Thanks,
Ravi

Check you traccar.xml, if you have upgraded you have to add the extra configurations.
your traccar.xml is missing at least something like this :
<entry key='database.selectDevicesAll'>
    SELECT * FROM device;
</entry>

@addonravi, if you are updating from old version of Traccar, you should read this:
https://www.traccar.org/update-from-2-x-to-3-0/

@tananaev  if I add a device in backend directly, does traccar accepts it without restarting the service?

Yes, Traccar will automatically pick up new devices from the database.

Thanks,
its work for me
-Ravi
On Friday 11 December 2015 12:25 AM, ivanfmartinez wrote:

Check you traccar.xml, if you have upgraded you have to add the extra
configurations.
your traccar.xml is missing at least something like this :
| SELECT * FROM device;  |
—
Reply to this email directly or view it on GitHub
https://github.com/tananaev/traccar/issues/1588#issuecomment-163716657.


python310Packages.zigpy-znp: 0.6.4 -> 0.7.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.zigpy-znp is: "Python library for zigpy which communicates with TI ZNP radios"
meta.homepage for python310Packages.zigpy-znp is: "https://github.com/zigpy/zigpy-znp"
meta.changelog for python310Packages.zigpy-znp is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.7.0 with grep in /nix/store/xmsvcsk8ygrwmfp24ybwkvq1vlak3ymn-python3.10-zigpy-znp-0.7.0

found 0.7.0 in filename of file in /nix/store/xmsvcsk8ygrwmfp24ybwkvq1vlak3ymn-python3.10-zigpy-znp-0.7.0

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

3 x86_64-linux rebuild(s)
0 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
home-assistant-component-tests.zha
python310Packages.zigpy-znp
python39Packages.zigpy-znp

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/xmsvcsk8ygrwmfp24ybwkvq1vlak3ymn-python3.10-zigpy-znp-0.7.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.zigpy-znp https://github.com/r-ryantm/nixpkgs/archive/d12377b3c42b59d5d4803ee8a867df4b3b096789.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/xmsvcsk8ygrwmfp24ybwkvq1vlak3ymn-python3.10-zigpy-znp-0.7.0
ls -la /nix/store/xmsvcsk8ygrwmfp24ybwkvq1vlak3ymn-python3.10-zigpy-znp-0.7.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

home-assistant-component-tests.zha
python310Packages.zigpy-znp
python39Packages.zigpy-znp

Maintainer pings
cc @mvnetbiz for testing.

Home assistant is still on 0.6.4. I don't have a ZNP radio to test with.

Looks like bugfixes only, no API changes. https://github.com/zigpy/zigpy-znp/releases/tag/v0.7.0
And the home-assistant tests still pass.

3 packages built:

home-assistant-component-tests.zha
python310Packages.zigpy-znp
python39Packages.zigpy-znp


Adding React 18 to the peerDependencies

Adding React 18 into the mix as the dependencies were locked to v16 or v17. I got the following error when trying to install the module on a NextJS React 18 project
> npm install --save moment react-moment
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>|| ^17.0.0" from<EMAIL_ADDRESS>npm ERR! node_modules/react-moment
npm ERR!   react-moment@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Coverage decreased (-0.0%) to 83.028% when pulling 3881ad058fb6e403e76f5b52cde312958f370e15 on mrpbennett:patch-1 into 9568de4fa1ad2f72c2bd7cf7a031fc0997a96b85 on headzoo:master.

Thanks! Published as<EMAIL_ADDRESS>


Add log aggregator sidecar for Ansible Operator

Description of the change:
Adds a sidecar container to Ansible Operator deployments that aggregates the stdout of the ansible logs.
Motivation for the change:
Currently looking at the ansible stdout log (what people are generally accustomed to seeing with Ansible) is a huge pain (you need to exec into a pod, and look at the stdout file in a very specific directory, /tmp/ansible-operator/runner/{group}/{version}/{kind}/{namespace}/{name}/artifacts/{job id}/stdout). This PR allows you to see the aggregated stdout without interfering with the machine readability of the standard operator logs.

https://github.com/openshift/ocp-release-operator-sdk/pull/4

@fabianvf Think you need to fix up the CI jobs to deal with the new container.
https://travis-ci.org/operator-framework/operator-sdk/jobs/504883755#L1163

Yep I'll write up a doc, wanted to make sure the approach was sane first


Upload test results nb

Upload all of the test results so we can look at the logs.
I.e. don't upload only failures.

Codecov Report

Merging #11346 (b43a339) into main (01481b2) will decrease coverage by 0%.
The diff coverage is n/a.

@@          Coverage Diff           @@
##            main   #11346   +/-   ##
======================================
- Coverage     63%      63%   -1%
======================================
  Files        476      476
  Lines      33925    33925
  Branches    5496     5496
======================================
- Hits       21556    21551    -5
+ Misses     10324    10323    -1
- Partials    2045     2051    +6

Impacted Files
Coverage Δ

.../notebooks/controllers/controllerDefaultService.ts
65% <0%> (-9%)
:arrow_down:

...otebooks/controllers/controllerPreferredService.ts
85% <0%> (-6%)
:arrow_down:

src/platform/common/process/baseDaemon.node.ts
50% <0%> (-4%)
:arrow_down:

src/kernels/raw/session/rawJupyterSession.node.ts
79% <0%> (-3%)
:arrow_down:

src/kernels/installer/productInstaller.node.ts
78% <0%> (-2%)
:arrow_down:

src/kernels/raw/launcher/kernelProcess.node.ts
72% <0%> (-1%)
:arrow_down:

src/platform/msrCrypto/msrCrypto.js
19% <0%> (-1%)
:arrow_down:

.../notebooks/controllers/vscodeNotebookController.ts
82% <0%> (+1%)
:arrow_up:

src/kernels/jupyter/jupyterKernelService.node.ts
76% <0%> (+1%)
:arrow_up:

src/kernels/jupyter/finder/remoteKernelFinder.ts
93% <0%> (+4%)
:arrow_up:

... and 2 more