ZKUI-423 fix-data-browser-reload-on-token-renewal

[JBWatenbergScality]

No description provided.

[bert-e]

Hello jbwatenbergscality,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Status report is not available.

[bert-e]

Incorrect fix version

The Fix Version/s in issue ZKUI-423 contains:

• None

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

• 2.1.8

• 2.2.0

Please check the Fix Version/s of ZKUI-423, or the target
branch of this pull request.

[JBWatenbergScality]

/approve

[bert-e]

Incorrect fix version

The Fix Version/s in issue ZKUI-423 contains:

• None

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

• 2.1.8

• 2.2.0

Please check the Fix Version/s of ZKUI-423, or the target
branch of this pull request.

The following options are set: approve

[JBWatenbergScality]

/status

[bert-e]

Status

Status report is not available.

The following options are set: approve

[bert-e]

Conflict

A conflict has been raised during the creation of
integration branch w/2.2/bugfix/ZKUI-423-fix-data-borwser-reload-on-token-renewal with contents from bugfix/ZKUI-423-fix-data-borwser-reload-on-token-renewal
and development/2.2.

I have not created the integration branch.

Here are the steps to resolve this conflict:

 $ git fetch
 $ git checkout -B w/2.2/bugfix/ZKUI-423-fix-data-borwser-reload-on-token-renewal origin/development/2.2
 $ git merge origin/bugfix/ZKUI-423-fix-data-borwser-reload-on-token-renewal
 $ # <intense conflict resolution>
 $ git commit
 $ git push -u origin w/2.2/bugfix/ZKUI-423-fix-data-borwser-reload-on-token-renewal

The following options are set: approve

[bert-e]

Waiting for approval

The following approvals are needed before I can proceed with the merge:

• the author

• one peer

Peer approvals must include at least 1 approval from the following list:

• @MonPote

• @JBWatenbergScality

• @ChengYanJin

The following options are set: approve

[bert-e]

Waiting for approval

The following approvals are needed before I can proceed with the merge:

• the author

• one peer

Peer approvals must include at least 1 approval from the following list:

• @JBWatenbergScality

• @MonPote

• @ChengYanJin

The following options are set: approve

[hervedombya]

LGTM 👍

[bert-e]

In the queue

The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.

The changeset will be merged in:

• ✔️ development/2.1

• ✔️ development/2.2

The following branches will NOT be impacted:

• development/1.4
• development/1.5
• development/1.6
• development/2.0

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.

IMPORTANT

Please do not attempt to modify this pull request.

• Any commit you add on the source branch will trigger a new cycle after the
  current queue is merged.
• Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.

The following options are set: approve

[bert-e]

I have successfully merged the changeset of this pull request
into targetted development branches:

• ✔️ development/2.1

• ✔️ development/2.2

The following branches have NOT changed:

• development/1.4
• development/1.5
• development/1.6
• development/2.0

Please check the status of the associated issue ZKUI-423.

Goodbye jbwatenbergscality.