Cannot start 4.5.0 - DbLocked

I got an update from 4.4.1 to 4.5.0 today.
After the update, I can no longer start Daedalus. It goes in a cycle of "Connecting to network", "Stopping cardano node", "Cardano node crashed".
node.log shows that it keeps crashing with the DbLocked error:
DbLocked "C:\\Users\\david\\AppData\\Roaming\\Daedalus Mainnet\\chain\\lock"

cardano-node: The db is used by another process. File "C:\Users\david\AppData\Roaming\Daedalus Mainnet\chain\lock" is locked

At this point, there are always two instances of cardano-node.exe running - one using 4 GB of RAM, and one that runs, crashed, gets restarted, etc.
I already tried several times to close Daedalus, make sure no cardano-node.exe process runs, deleted the lockfile is existing, etc. - but again, when I start Daedalus, it starts again two instances, with the second one obviously failing.

What can I do to fix this?

I tried attaching a debugger to understand what's going on.
Apparently Daedalus is checking the wrong PID somehow. It checks PID 34200 all the time (this process doesn't exist). Also, there is an error about failing to store the PID (empty in this case, because it did detect that 34200 is no longer running).

This is because it calls store.set("mainnet-PREVIOUS-CARDANO-PID", undefined) instead of store.delete("mainnet-PREVIOUS-CARDANO-PID").
I finally solved the problem by manually deleting the line 	"mainnet-PREVIOUS-CARDANO-PID": 28844, from config.json. Still this is a bug that can leave Daedalus in an unusable state, and normal users can't be expected to figure out this solution.

@CherryDT Hello. Thank you for your research and such a detailed report.
We are currently investigating the issue in order to fix it asap.
Please let me know if it works now as expected after your tweak.
Thank you in advance.

Hm, no, seems it works only once this way. After closing Daedalus, the mainnet-PREVIOUS-CARDANO-PID again doesn't get removed and next time it will go into the same cycle as described above. I have to manually delete this line every time I want to start Daedalus.

@CherryDT Can you please provide the Logs zipped?
Thank you!

Sent you an email.

Can you please attach the Log.zip to this card in GH ?
Thank you in advice!

Just to confirm, it won't contain any sort of sensitive information?

@CherryDT Yes, it doesn't not contain any sensitive information. However I have received the logs so thank you! No need to attach it.
Thank you , we are continue the research.

On that note, I looked at the log files now because I'd have removed anything problematic and then posted here, but I discovered that there is problematic information in wallet-migration-report.json. It showed names of wallets.

This is my config.json by the way, in case it's relevant:

@CherryDT by now to have your Daedalus back in a good shape I suggest you to perform a clean re-installation process.
Unfortunately you would need to Sync the chain from the scratch. Please make sure you have all your mnemonics near by so you can restore your wallets once Node is fully synced.
Please follow the instruction https://iohk.zendesk.com/hc/en-us/articles/360013170694-Uninstall-Daedalus-and-remove-wallet-s-data
Thank you!

This is very inconvenient. How come that something that looks like an issue in controlling the state of the cardano node (from the outside) would require the chain to be resynced? Can't I keep the "chain" folder and put it back after reinstallation?

Yes, you can try to keep the chain folder and use it after the re-installation but I cant guarantee that it would resolve the crashing loop issue. You can try this is as a Plan A and if it doesn't helps then Re-install + full re-sync is a Plan B.

I don't think this will help, thanks anyway for the suggestion. Instead I investigated the root cause and fixed it. See https://github.com/input-output-hk/daedalus/pull/2749

Thanks for the analysis and workaround. Daedalus has been broken for me all day until I found this workaround. Hope the fix is pushed through so I don't have to keep cleaning up the config file. I can confirm I was seeing the same symptoms of two nodes starting on my PC and contending for the lock file. One was healthy and processing the chain data, whilst the other was perma-crash looping. It wasn't clear to me whether the healthy node was a singular instance online the whole time, or just one node that gets to do work before restarting. The wallet was complaining the whole time.

Thanks for the analysis and workaround. Daedalus has been broken for me all day until I found this workaround. Hope the fix is pushed through so I don't have to keep cleaning up the config file. I can confirm I was seeing the same symptoms of two nodes starting on my PC and contending for the lock file. One was healthy and processing the chain data, whilst the other was perma-crash looping. It wasn't clear to me whether the healthy node was a singular instance online the whole time, or just one node that gets to do work before restarting. The wallet was complaining the whole time.

Thank you @greg-pendlebury for your feedback!
Would you pls tell me what is your operating system?

Hi @CherryDT thank you so much for the PR.
It is a long story, originally another problem related to how do we start cardano-node implemented here caused this race condition. Your code definitely solves one side of the puzzle, that is why we will provide a complete fix very soon!
Thank you for your time and your suggestions!

Thanks for the analysis and workaround. Daedalus has been broken for me all day until I found this workaround. Hope the fix is pushed through so I don't have to keep cleaning up the config file. I can confirm I was seeing the same symptoms of two nodes starting on my PC and contending for the lock file. One was healthy and processing the chain data, whilst the other was perma-crash looping. It wasn't clear to me whether the healthy node was a singular instance online the whole time, or just one node that gets to do work before restarting. The wallet was complaining the whole time.

Thank you @greg-pendlebury for your feedback! Would you pls tell me what is your operating system?

Windows 10

Hi!
This issue should be fixed in the latest release 4.5.1.
Can you please see if it works?
Thanks!

Hi, thank you, but I think the bug is still lingering. From how I understand, the commit https://github.com/input-output-hk/daedalus/pull/2755/commits/44fcccbebfe56087effa5f934e468eb3fcaf9c9d does remove the trigger that made it appear most of the time by removing on of the disk space check calls, and the window for the race condition is now probably smaller (actually I originally somehow assumed that _canBeStarted would already check for STARTING - but apparently it didn't, and adding that solves a lot already), but the race condition as I described it still exists.
Imagine:

status is STOPPED
invocation A of start happens
invocation B of start happens
in invocation A, start calls _canBeStarted
in invocation A, _canBeStarted passes the first condition since state is currently still STOPPED
in invocation A, _canBeStarted asynchronously calls _ensurePreviousCardanoNodeIsNotRunning
in invocation B, start calls _canBeStarted (possible because it's asynchronous)
in invocation B, _canBeStarted also passes the first condition and now calls _ensurePreviousCardanoNodeIsNotRunning
in invocation A, _canBeStarted returns true, and start sets status to STARTING, but it's already too late
in invocation B, _canBeStarted also returns true

The only way to prevent this would be to have another state that is set synchronously before _canBeStarted is called, which is why I introduced a separate flag in my PR for this (piggy-backing on the node state is not possible here).
Please review it again, to get rid of this race condition entirely! Thanks

Thanks @CherryDT!
We are refactoring that part at the moment.
Thank you for the pointers - we will make sure all race conditions are eliminated.

Closing the ticket as the team is working on improvements and most of the discussed issues supposed to resolved in 4.5.2 release.
Please create a new ticket if you still experience any issues described.
Thank you!


Tabs will go up when I open keyboard. Is there a way on how to fix this? Please help.

Latest Version:: ^4.0.6
Here is the Issue

Please check latest 4.2.0-beta.1. If it doesn't help try pure react-navigation tabbar and report issue if it is there..


Fix bug where test assumes existence of UserRole

Warning
Info
Issues
Fixed #1806

I resolved the issue in UTIL_UnitTestData_Test by performing a check for an existing UserRole, and querying that one if it exists.  If it did not exist, then it creates it.
To facilitate testing, I broke the createNewUserForTests() method into one that accepts a UserRole name and one that delegates using the default 'COO'.
I wasn't sure where to add the test methods, since this class was already suffixed '_TEST', so I added the @IsTest annotation to UTIL_UnitTestData_TEST and added the test methods to that class.  If this is an issue for any reason, let me know and I can move the test methods elsewhere.
Also, as I was testing I found another part of the code that has this same issue, ERR_Handler_TEST.testInactiveUserEmailBehavior(), which tries to create a test user with IsActive set to false for testing.  I added this functionality to UTIL_UnitTestData_TEST and replaced the code in testInactiveUserEmailBehavior() with a call to the utility test data method.


Failing on RUN /opt/install-sdk.sh

On running  docker compose up android-emulator
The build fails with this error -

[+] Building 418.2s (12/15)                                                                                docker:default
 => [android-emulator internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 2.55kB                                                                                0.0sx => [android-emulator internal] load metadata for docker.io/library/openjdk:18-jdk-slim                                                                 1.0s
 => [android-emulator internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => CACHED [android-emulator  1/11] FROM docker.io/library/openjdk:18-jdk-slim@sha256:8e17383576d7e71988ee5927473a32e8461381c7a29eefa9a0c24b3a28926272  0.0s
 => [android-emulator internal] load build context                                                                                0.0s
 => => transferring context: 256B                                                                                0.0s
 => [android-emulator  2/11] RUN apt update && apt install -y curl  sudo wget unzip bzip2 libdrm-dev  libxkbcommon-dev libgbm-dev libasound-dev libn  415.7s
 => [android-emulator  3/11] WORKDIR /opt                                                                                0.0s
 => [android-emulator  4/11] RUN mkdir /root/.android/ &&  touch /root/.android/repositories.cfg &&  mkdir /data                                        0.3s
 => [android-emulator  5/11] COPY keys/* /root/.android/                                                                                0.0s
 => [android-emulator  6/11] COPY scripts/install-sdk.sh /opt/                                                                                0.0s
 => [android-emulator  7/11] RUN chmod +x /opt/install-sdk.sh                                                                                0.4s
 => ERROR [android-emulator  8/11] RUN /opt/install-sdk.sh                                                                                0.5s
------
 > [android-emulator  8/11] RUN /opt/install-sdk.sh:
0.487 /bin/bash: /opt/install-sdk.sh: /bin/bash^M: bad interpreter: No such file or directory
------
failed to solve: process "/bin/bash -c /opt/install-sdk.sh" did not complete successfully: exit code: 126

Hi @SakshamSahgal, thanks for reporting this issue.  I don’t have the time to fix it at the moment but if you manage to fix it I’m willing to take in pull requests


Improved Binary Search

🚀 Feature
I want to add improved bubble sort algorithm to make it adaptive.
Have you read the Contributing Guidelines on Pull Requests?
YES
Motivation
I would like to work on it under GSSoc'21
Pitch
This feature will make the bubble sort algorithm adaptive so that its best case complexity will become O(n)

Issue Title states: Improved Binary Search
Issue Description states: Improved Bubble Sort
What exactly will you be doing?

I will be using a flag variable inside first for loop which will help to keep track if the array is already sorted .  If it is already sorted then it will not enter the inner loop.

So what exactly are you trying to achieve here, may I know?

I won't check further if the array is already sorted on every step (any swaps made). This check is necessary, in order to preserve adaptive property.

Hi I am GSSoC'21 participant
i would like to contribute in Improved Bubble Sort using C++
i can make the bubble sort optimized by ADAPTIVE WAY
i will write the clean code with  brief commenting and algorithm.
so i would like @HarshCasper  to please assign this project to me :)

I am a GSSOC'21 participant and want to work on issue.
I can provide the code in C++ with proper comment description and best time complexity .
please assign me this issue.

I am a Gssoc'21 participant , I would like to work on it . Kindly assigned it to me.


[Plugin][Bug]: Bug when share is empty

Issue validation

[X] I checked the issue to prevent duplicate
[X] I checked my configurations files and the documentation

Command used
Refresh published and upload new notes
Plugin version
6.7.1
Describe the bug
I was able to publish some individual notes just fine, but when I tried to reftesh and upload several notes at once, I got this bug.
plugin:obsidian-mkdocs-publisher:19 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'toString')
    at ce (plugin:obsidian-mkdocs-publisher:19:53057)
    at Ys.getAllFileWithPath (plugin:obsidian-mkdocs-publisher:28:10213)
    at eval (plugin:obsidian-mkdocs-publisher:23:20428)
    at Generator.next (<anonymous>)
    at eval (plugin:obsidian-mkdocs-publisher:2:871)
    at new Promise (<anonymous>)
    at m (plugin:obsidian-mkdocs-publisher:2:691)
    at so (plugin:obsidian-mkdocs-publisher:23:20333)
    at eval (plugin:obsidian-mkdocs-publisher:23:22746)
    at Generator.next (<anonymous>)

After some picking around I figured out the issue: one of my notes had the "share" property empty instead of true or false. After turning it to false the bug vanished. I looked at the code, and the thing is, it does not check if the property equals exactly null, and Obsidian does not treat null and false as the same thing anymore. It seems to be easy enough to fix, just add additional check for null along with undefined.
How to reproduce ?
Create the note with the empty share property (can be created in the source mode) and try to share it of several notes at once.
Minimal Reproducible Example
-

Configuration
-

Relevant log output
No response
OS
No response
Anything else?
No response
Obsidian information
-

Oh ! Good catch umu! Will fix that asap :)

Please, try the new version <3


workbench.editor.showTabs set to false in upgrade

This issue is mostly to talk about upgrade experience. My vscode started behaving as if workbench.editor.showTabs was false and it took me a few days to figure it out WHAT it was and set to true. Just had never touched this setting before. Maybe a new default was introduced?

VSCode Version: 1.45.1
OS Version: mac 10.14.6

Steps to Reproduce:

update to 1.45.1 or 1.45 from 1.44
workbench.editor.showTabs behaves as if false, but you never set it to false.

Does this issue occur when all extensions are disabled?: Yes
Setting the setting manually brings back old behavior (having workbench.editor.showTabs: true). Even after setting this to true in the settings UI it would NOT show up in my settings json. Kinda odd.

We did not change this setting at all. I think you have issues with the settings file maybe, can you check the contents of the file has this entry and then check the settings editor?

ok, Could be a local issue, just wanted to document here with an issue just in case, thanks.

I just updated my VS Code insiders and had this same experience.  All of a sudden my tabs had disappeared and required me to turn on workbench.editor.showTabs "on" which did not update my settings.json.
Version: 1.46.0-insider
Commit: a5d1cc28bb5da32ec67e86cc50f84c67cc690321
Date: 2020-06-09T17:34:56.826Z (4 hrs ago)
Electron: 7.3.1
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.5.0


problem in saving the file

when I click save button the code was calabash and it mixed with another line code

Can you add more details?
Do you have steps to reproduce?


missing grid for the last column displayed in output area

Issue Type: Bug

open a sql notebook
run query select * from sys.databases
results look like

we can see the grid is not drawn at the end of the window. If we move the scroll bar at the bottom, the grid will be added.
Could we display the grid for all visible columns?
Note:
this is from saved notebook. I just executed the query against a valid connection. Look like no such problem.
Azure Data Studio version: azuredatastudio 1.5.0 (9ca6200018fc206d67a47229f991901a8a453781, 2017-12-15T12:00:00.000Z)
OS version: Windows_NT x64 6.3.9600

System Info

Item
Value

CPUs
Intel(R) Xeon(R) CPU E5-2695 v2 @ 2.40GHz (48 x 2394)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: unavailable_softwarevideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
255.93GB (171.87GB free)

Process Argv
. --remote-debugging-port=9222 --no-first-run --no-default-browser-check --inspect=5875 --no-cached-data

Screen Reader
no

VM
0%

Extensions (1)

Extension
Author (truncated)
Version

sql-vnext
Mic
0.10.3

Not able to repro this issue. Talked to Yurong as well. Closing it.

Azure Data Studio version: azuredatastudio 1.5.0 (9ca6200, 2017-12-15T12:00:00.000Z)
OS version: Windows_NT x64 6.3.9600
Repro on the version. query select * from sys.database_files

I can't repro for now. @YurongHe do you have a good repro still?

Moving to April since I cannot repro.

Closing as no repro.  Please reactive if the issue persists.


Build fails when uglifying material component script

Do you want to request a feature or report a bug?
Bug?
What is the current behavior?
yarn start works without error. yarn build and yarn serve fail with this same error.
If the current behavior is a bug, please provide the steps to reproduce.
It doesn't happen with out of the box configurations, but since it's dealing with a material design component, it feels like it could be related to the project:
on yarn build:
yarn run v1.3.2
$ preact build
Build [==                  ] 10% (0.1s) building modules(node:46019) DeprecationWarning: Chunk.modules is deprecated. Use Chunk.getNumberOfModules/mapModules/forEachModule/containsModule instead.
✖ ERROR bundle.09240.js from UglifyJs
Unexpected token: name (MDCFoundation) [../node_modules/@material/base/foundation.js:21,6][bundle.09240.js:926,4]
Build failed!
error Command failed with exit code 1.

Please mention other relevant information.

node version - 8.4.0
yarn version - 1.3.2
Operating system - OSX Sierrra.

I got a similar error:
✖ ERROR route-home.chunk.3d3d6.js from UglifyJs Unexpected token: name (Card) [../node_modules/preact-material-components/Card/index.js:8,6][route-home.chunk.3d3d6.js:38,4] ✖ ERROR route-profile.chunk.75226.js from UglifyJs Unexpected token: name (Profile) [./routes/profile/index.js:6,21][route-profile.chunk.75226.js:37,4] ✖ ERROR bundle.cc43e.js from UglifyJs Unexpected token: operator (>) [../node_modules/preact-material-components/themeUtils/generateThemeClass.js:1,15][bundle.cc43e.js:166,61] Build failed! null
preact watch doesn´t throw any errors, but preact build does

node version: 9.7.1
yarn version: 1.3.2
OS: OSX Sierra

@sydev The unexpected token: name (...) seems to go away to giving them the .jsx extension on default configurations. however, im yet to resolve the operator >
Might be that the template for preact-cli  "material" is wrongly configured for build?

looking into it

operator > is a bug on preact-material-components side, publishing a patch ASAP. upgrade to 1.3.9

Same issue in my setup as well. Cannot play around the webpack config as there is no eject command in the cli.
Unexpected token errors keep coming up in various parts of the codebase. How to circumvent this error? Running with --no-prerender doesn't work too.

☝ should fix this

 ERROR route-home.chunk.df78c.js from UglifyJs Unexpected token: name (ContentTypes) [../node_modules/msexcel-builder/lib/msexcel-builder.js:43,0][route-home.chunk.df78c.js:19724,23]
This is the error I get. And the code where it fails is just this
ContentTypes = class ContentTypes {

@vijaybritto that is something that will not be fixed with it 😆
looks like it comes from msexcel-builder

It does not happen in dev build and the same file is being loaded there as well. This has something to do with the uglifyJs config in the prod build.

yeah, may be pmc is being used inside this or something. let me just publish the update in a day or two.

in case its not super blocking!

btw if it is super urgent, just use
import {Button,....} from 'preact-material-components'
till then, its a full es5 export

I'm not using pmc anywhere in my app. I'm taking out the webpack config into the project root folder and attempting to play with it!

are you using material template of preact-cli or some other one?

preact-cli's 'default' template


HDF5 reader or Zarr reader?

These lines in the readme:
# Try to read using pynwb
# (This part does not work yet)
with pynwb.NWBHDF5IO(file=client, mode="r") as io:
    nwbfile = io.read()
    print(nwbfile)

seem to indicate we will be using h5py to read the file, which confused me. The rest of the readme workflow looks like we are doing something similar to kerchunk, so I would expect to use Zarr here.

It does use zarr... but what @rly and I are proposing is that we have a h5py-like client that wraps the zarr nwb. That way we can seamlessly use zarr or hdf5 in the same pynwb.

Ok so what would the type of the in-memory Dataset be? ZarrDataset, h5py.Dataset, or a new type?

Ok so what would the type of the in-memory Dataset be? ZarrDataset, h5py.Dataset, or a new type?

It is a new type, lindi.LindiDataset
But it is duck typed the same as h5py.Dataset... and when it comes to slicing, it just passes that through to Zarr slicing (or h5py slicing if hdf5 is what is being wrapped at that part of the nwb)
We would need to modify pynwb to allow usage of lindi.LindiGroup and lindi.LindiDataset throughtout

Wrapping for h5py is an interesting approach and seems useful, but, I think it may be easier to go through hdmf-zarr first to integrate with PyNWB to use Zarr directly.

It is a new type, lindi.LindiDataset

Would 'lindi.LindiDataset' inherit from 'h5py.Dataset'?

Wrapping for h5py is an interesting approach and seems useful, but, I think it may be easier to go through hdmf-zarr first to integrate with PyNWB to use Zarr directly.

The problem with using the zarr python client here is that it is not flexible enough to link to different types of data as part of the NWB. For example, an existing NWB that has a lot of datasets moderate sized datasets, plus one giant dataset with 1 million chunks (raw ephys). It's not practical to represent that as a Zarr. It needs to be a Zarr with a special annotation on that one dataset with a pointer to the original NWB on DANDI. This is what lindi.LindiClient can handle... with an h5py-compatible api.

Would 'lindi.LindiDataset' inherit from 'h5py.Dataset'?

Possibly... I'm not sure...

For example, an existing NWB that has a lot of moderate sized datasets, plus one giant dataset with 1 million chunks (raw ephys). It's not practical to represent that as a Zarr.

It looks like the Zarr community is dealing with this by implementing sharding. @magland, are you familiar with this codec specification for sharding in Zarr merged two months ago? Does this resolve the issue with millions of chunks or are there other issues you are hoping to address with LINDI?

It looks like the Zarr community is dealing with this by implementing sharding. @magland, are you familiar with this codec specification for sharding in Zarr merged two months ago? Does this resolve the issue with millions of chunks or are there other issues you are hoping to address with LINDI?

I hadn't see that, thanks. I think sharding is the right way to go for newly created NWBs. However I don't think it's practical to re-chunk and re-upload all the existing hdf5 nwb files, and that's where LINDI comes in.

@bendichter things are explained better now in the latest README... and the pynwb integration even works!
If it answers your question we can close this issue.


Task :app:checkDebugAarMetadata FAILED

Description
I am unable to run the application. When I am running react-native run-android, I am getting this error. I have re-installed the node-modules also but still I am facing the same issue.
Version
0.66.4
Output of npx react-native info
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:checkDebugAarMetadata'.

Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
Could not resolve com.facebook.react:react-native:+.
Required by:
project :app
project :app > project :react-native-maps
project :app > project :react-native-community_async-storage
project :app > project :react-native-community_checkbox
project :app > project :react-native-community_clipboard
project :app > project :react-native-community_geolocation
project :app > project :react-native-community_masked-view
project :app > project :react-native-community_netinfo
project :app > project :react-native-firebase_app
project :app > project :react-native-firebase_messaging
project :app > project :react-native-document-picker
project :app > project :react-native-gesture-handler
project :app > project :react-native-image-picker
project :app > project :react-native-localization
project :app > project :react-native-location-enabler
project :app > project :react-native-pager-view
project :app > project :react-native-permissions
project :app > project :react-native-push-notification
project :app > project :react-native-reanimated
project :app > project :react-native-restart
project :app > project :react-native-safe-area-context
project :app > project :react-native-screens
project :app > project :react-native-splash-screen
project :app > project :react-native-svg
project :app > project :react-native-tooltips
project :app > project :react-native-webview
project :app > project :rn-fetch-blob
Failed to list versions for com.facebook.react:react-native.
Unable to load Maven meta-data from https://jcenter.bintray.com/com/facebook/react/react-native/maven-metadata.xml.
Could not HEAD 'https://jcenter.bintray.com/com/facebook/react/react-native/maven-metadata.xml'.
Read timed out

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 1m 46s
Steps to reproduce
I am unable to run the application. When I am running react-native run-android, I am getting this error. I have re-installed the node-modules also but still I am facing the same issue.
Snack, code example, screenshot, or link to a repository

@moin-maniar check this Duplicate of #35136

Closing as JCenter was temporarily down. Now is restored

not sure if this is what I need


Node-Problem-Detector should Patch NodeStatus not Update

Problem:
kubelet, node-controller, and now the node-problem-detector all update the Node.Status field.
Normally this is not a problem because if changes happen rapidly, resource version mismatch fails and everything is ok.
When a new field is added to Node Status, however:

Since kubelet and node-controller are in the same repository they are recompiled with the new field and Status updates continue to operate normally.
However, since node-problem-detector is in a separate repository and has not been recompiled with the new version, its Update calls end up squashing the new (unknown) field, resetting it to nil.

Suggested Solution:
node-problem-detector should do a patch instead of an update to prevent wiping out fields it is not aware of. Incidentally, kubelet and node-controller should do this as well, but that is not as critical since they are in the same repository and new types are normally added their first.
CC @kubernetes/sig-node @kubernetes/sig-api-machinery @Random-Liu @bgrant0607

You can use the Patch() method in the dynamic client, but you'll need to modify that function to allow specifying a subresource. cc @krousey

I didn't know you guys were building this in a different repository. If you aren't going to be version-locked like the other components are, then you need some features that aren't built into our client.
Patch and/or dynamic client seems to be your best way forward.
There are various ways we could have made this easier, but they won't happen in time for your first release...

@saad-ali Thanks a lot for reporting!

You can use the Patch() method in the dynamic client, but you'll need to modify that function to allow specifying a subresource. cc @krousey

I'll try this!
@lavalamp Thanks a lot! Patch is good enough for now~ Let me try :)

I think we should also have a node e2e that verifies the Kubelet itself
does not regress and drop node conditions it does not manage.  I don't
think we have anything that verifies that today and it would help avoid
regressions.
On Thursday, May 26, 2016, Lantao Liu<EMAIL_ADDRESS>wrote:

@saad-ali https://github.com/saad-ali Thanks a lot for reporting!
You can use the Patch() method in the dynamic client, but you'll need to
modify that function to allow specifying a subresource. cc @krousey
https://github.com/krousey
I'll try this!
@lavalamp https://github.com/lavalamp Thanks a lot!
Reply to this email directly or view it on GitHub
https://github.com/kubernetes/node-problem-detector/issues/9#issuecomment-221783313

Yes, I talked @Random-Liu on e2e test verifying this.

@saad-ali Ah, so it was getting clobbered. Great catch!  Where multiple components update a resource, they'll need a way to patch, either via PATCH or via a dedicated subresource.
This is a problem already with node controller and Kubelet. I'm surprised we hadn't been bit by it yet.
We have a similar problem with kubectl round-tripping, which we're working to eliminate.

@bgrant0607 Yeah. Very surprising this is the first time we've hit this. BTW making kubectl not round-trip wouldn't be sufficient, but @krousey was actually switching everything to use the dynamic client, which will be sufficient to prevent this.
Also, this is the canary in the coal mine: everyone who built automation using our current client will have this problem in 1.3.

I think we should also have a node e2e that verifies the Kubelet itself
does not regress and drop node conditions it does not manage.  I don't
think we have anything that verifies that today and it would help avoid
regressions.

Yeah, we are going to add test for this. :)

FYI, I tried many ways to patch the NodeCondition, but the apiserver keeps throwing out 405 error. I'll work with @caesarxuchao to figure out how to patch status correctly (Thanks! :)).
And I had an offline discussion with @saad-ali, to unblock him we'll:

disable node-problem-detector temporarily
get https://github.com/kubernetes/kubernetes/pull/26351 merged
update the api client version in node-problem-detector
re-enable node-problem-detector

Because node-problem-detector only touches NodeStatus and #26351 seems to be the only PR for now adding new field in NodeStatus, so this could be a temporarily walk around.
At the mean time, I'll change the node-problem-detector to use Patch asap.
@dchen1107 @bgrant0607 @lavalamp Is this OK?

Offline discussed with @dchen1107, we will:

Go with https://github.com/kubernetes/node-problem-detector/issues/9#issuecomment-221949895 to unblock @saad-ali
Wait for https://github.com/kubernetes/kubernetes/pull/26381 to land (Thanks @caesarxuchao )
Switch node-problem-detector to use Patch instead of UpdateStatus

but @krousey was actually switching everything to use the dynamic client, which will be sufficient to prevent this.
@lavalamp - what do you mean by everything? If you really mean "everything", then we need to support protobufs in it, which we currently don't. @smarterclayton FYI

Yeah, dynamic client only talk json right now afaik.
On Wed, Jun 1, 2016 at 11:27 PM, Wojciech Tyczynski <
<EMAIL_ADDRESS>wrote:

but @krousey https://github.com/krousey was actually switching
everything to use the dynamic client, which will be sufficient to prevent
this.
@lavalamp https://github.com/lavalamp - what do you mean by everything?
If you really mean "everything", then we need to support protobufs in it,
which we currently don't. @smarterclayton
https://github.com/smarterclayton FYI
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/node-problem-detector/issues/9#issuecomment-223206521,
or mute the thread
https://github.com/notifications/unsubscribe/AAnglj--252rYNcJXBo49u0HU6oad_5tks5qHnfSgaJpZM4InIBd
.


dogecoin  Not yet redeemed

transaction id:   ecc37016b5c5c00844bdf02e965502c7ebeed42293956d5911db87b8c7c35e49
dogecoin  Not yet redeemed
help how to conformation transaction

There's no need to confirm or redeem anything.
Some wallets etc will use the phrase not yet redeemed to make clear, that the coins sent haven't been used/transferred again since the original transaction.


Support added for setting up all team channels on discord

This should allow both creation when a new team is made, and the ability to update all teams

Added this


Add Code Typing Tutor Badge

[x] I have followed (at least) the PR section of the contributing guide.

@kulakowka I'm a big fan of what you have done with Material-UI, it's really high quality 👌. I understand that you are trying to create momentum. I'm not sure that this badge will help 🤔.

I'm sorry to disappoint you. Perhaps this is really not appropriate.

@kulakowka The lack of good learning content for Material-UI is one of our top problem we want to solve. The wording of the badge might confuse people. I'm not sure it describes correctly the offering.

An appropriately worded link from the Learn page OTOH...


Please add a (cross-) compile guide for custom Ultrascale+ MPSoC with any Linux

Hi,
We have a custom Ultrascale+ MPSoC device with a Debian derived OS. Unfortunately, the VAI 3.0 User Guide and older versions of it only contain a build guide for Petalinux (link). The same applies to the Setting up a Zynq UltraScale+ MPSoC Target guide link in the github.io documentation.
We have built XRT (Xilinx Runtime), ZOCL-Driver, VART (Vitis AI Runtime) and the Vitis-AI-Library on the device itself. But finding out the dependencies and how to do it was a little bit challenging.
Is somewhere maybe a custom build guide, which includes the installation of the necessary dependencies, compilation of XRT and ZOCL and compilation of the VART und Vitis-AI-Library? Or could you create a custom build guide? This would be extremely helpful.
AFAIK there is an Ubuntu apt-package, developed by Canonical, which installs Vitis-AI (link). So, there might be already somewhere a build guide.
Thank you very much for your help!

Very good question, looking forward to an official reply from Xilinx...

Unfortunately, Xilinx currently maintains the Petalinux tool exclusively. Regarding the VitisAI framework, it does not provide support for any other systems. However, Xilinx has a project called PYNQ, which is based on the Ubuntu system and can support the specified version of VitisAI and DPU. Below are some links to the project that you can refer to:
https://github.com/Xilinx/DPU-PYNQ
https://github.com/Xilinx/Kria-PYNQ/blob/main/README.md

Ok, what a pity. But thank you very much for your response. My request has been clarified.

@RapidEdgeAI have you also been discussing this with our ML Specialist in Europe, Sophie?  I just want to understand if this is the same request that I am aware of.

Hi @quentonh. Yes, but not directly. In February we asked the Xilinx support if there are prebuilt Debian packages for Vitis-AI because Xilinx offers the certified Ubuntu for the Kria boards. But the answer was no because the Ubuntu image that includes those packages is distributed by Canonical. Because of this it would be super helpful if a build guide, including dependencies, cross compilation, etc. for custom Linux systems would be included in a future Vitis AI release.
Petalinux works very well for us with our prototype. But unfortunately, we cannot use Petalinux in the product because our whole product ecosystem is based on our own Linux derivate due to maintainability reasons.

I'm sorry. I accidentally skipped "Sophie". No, we didn't talk to Sophie. We talked to another Xilinx employee via the Xilinx support page.

This is also an issue for our usecase. Having detailed guides for bringing up the runtime environment is crucial.


False "Invalid URL" message

Happened when I tried to add link https://www.dcode.fr/exif-thumbnail

Working for me in 2 devices. I have faced this once but then it is not there.

If I understand correctly, the message happens sometimes. What we can do is to make error message more explicit/granular: in particular, there might be limit of redirects reached or something else. We should investigate which HTTP functions are used and which kinds of exceptions they can throw. After that we should catch them separately.


Document semantics

This is a documentation request. It's not clear to me the intended semantics of this library.
If setItem promise resolves, does that indicate that a subsequent getItem will return the latest value? Or that it will be eventually consistent?
If it fails, is the state of the store the old value, or undefined?
For setMultiple, is it atomic?
etc...
Thanks!

Hey @xaviershay,
Thanks for suggestion, I guess it'd be great to have such info. Would you like to give it a go?
thanks.

I don't know what the intent is :) if you give me a sketch of an answer, I'll happily clean it up and send a pr for the docs.
On Thu, Apr 18, 2019, at 6:12 PM, Krzysztof Borowy wrote:

Hey @xaviershay https://github.com/xaviershay,

Thanks for suggestion, I guess it'd be great to have such info. Would you like to give it a go?

thanks.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/react-native-community/react-native-async-storage/issues/85#issuecomment-484400713, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAANMX2E6KX7MIDY7S2MMTPRAUOHANCNFSM4HG2ABLQ.

@xaviershay ,
That'd involve going into the source code and filling up the docs with semantic information you mentioned. We do it partially, but could definitely be done better.
thanks.

ok, I'm extremely new to react-native, and in particular don't quite understand how native modules work / the bridge yet. I can revisit once I've learned some more.

Right, so I'm closing this one for now, let me know when should we re-open it.
thanks.


About gradient calculation of mask operation

Thank you for your excellent work!
I'm somewhat confused about the gradient calculation of the mask operation. It seems that input of the get_im_subim_channels function includes channels_im and map_add, while the output is computed by using top-k for map_add and generates binary mask. So, how does the gradient backward to map_add?  And How are the weights of  self.fc updated?

Hi, thanks for your interest. map_add is split into two parts and each part has its gradient. Perhaps you can imagine that there are two parallel gradient backward graphs, A and B. The function of top-k is simply to select which channels (or time) go through graph A and the rest through graph B.


Fix swagger schema (typo & syntax)

Description
In both the JSON and YAML files, I:

fixed the spelling of "minumum" to "minimum"
fixed the type declaration of definitions.LivePlayByPlay.properties.drives.items.properties.plays.items.properties.team

Motivation and Context
Fixes #269
How Has This Been Tested?
I validated each of the raw outputs in this branch:

JSON

validator link
image link

YAML

validator link
image link

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.

@BlueSCar

[no ci] looks good!


Alternate qubes-windows-tools available

https://github.com/tabit-pro/qwt-crossbuild/
This may help address the win10/windows server issues w/r/t volume setup necessary to support templates.

Hi Brendan,
I believe you're referring specifically to this file here: https://github.com/tabit-pro/qwt-crossbuild/blob/master/diskpart.ps1
It may indeed be possible for us to patch the private volume setup issue locally in this project. However, it isn't my goal to make this project a bunch of dodgy fixes for QWT when what should really be happening is those issues being addressed upstream.
This issue in particular may have already been patched upstream, see here:
https://github.com/elliotkillick/qvm-create-windows-qube/issues/13
Though, as I'm sure you are well aware of by now, QWT lacks an active maintainer and so that patch, while merged, hasn't been applied to a new version of the installer. :/

Please feel free to fork if you would like to implement these upstream fixes locally in your own repo. However, I will not be maintaining them myself.

Please feel free to fork if you would like to implement these upstream fixes locally in your own repo. However, I will not be maintaining them myself.

Understood. I'll do so. :)
Thanks for all the work so far.
B


Prepare GC commits: only calculate and return active commits

In the new GC flow, only active commits are required in the output of the prepare commits endpoint.
This change will greatly simplify the code, and also improve performance.

We also need to consider removing the incremental flag


增加Linux平台的action运行的xml文件

需要注意的是修改了代码FfmpegMuxer.cpp中的一句日志打印语句

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.yiliang seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Getting the full list of Game Clips for a user account

Hi, I've been using this package for a year or so now and it's been great! Thanks for open-sourcing this, it's been a great help.
I noticed recently the point about the mid-2019 games not being returned by the current getPlayerGameclips method (related to https://github.com/XboxReplay/xboxlive-api/issues/5 ?)
The suggestion to use the getPlayerGameClipsFromActivityHistory was promising so I updated the package to v3 and switched over. However, now I'm only seeing 2 clips come back for a given user, regardless of what I put in the numItems field.
Is there a workaround that will allow me to see all clips for a user, even for recent games?

Hey,
Unfortunately, the "activity" trick doesn't work anymore and games such as Cyberpunk 2077 won't be returned.
The only viable workaround is the use "mediahub.xboxlive.com" domain (which is used by mobile / desktop apps) but it requires a XSTSToken created from UserToken, TitleToken and DeviceToken combination.
Right now, this library can not handle it by itself.
Good news, the upcoming update of XboxReplay.net and its API (v2) will.
Another good news, you'll be able to use it for free.
I'm leaving this issue opened and I'll communicate about the update in a few weeks.

A new branch (4.0.0) has been created.

https://github.com/XboxReplay/xboxlive-api/tree/4.0.0

To overcome this issue, this library will expose additional methods to call the upcoming v2 XboxReplay API ; which is able to retrieve all missing content.
Once the update is live, the library will be updated.

A new branch (4.0.0) has been created.

https://github.com/XboxReplay/xboxlive-api/tree/4.0.0

To overcome this issue, this library will expose additional methods to call the upcoming v2 XboxReplay API ; which is able to retrieve all missing content.
Once the update is live, the library will be updated.

Ah, excellent. I'll give this a go when I get a bit of time.
So this will mean we're hitting your back end service, rather than going directly to MS, is that right?

Ah, excellent. I'll give this a go when I get a bit of time.
So this will mean we're hitting your back end service, rather than going directly to MS, is that right?

If you must, yes :)

If you must, yes :)

With the requirements for the device specific headers etc. does that rule out decentralising it in the way it was before? It's handy being able to go straight to MS since it won't add extra load on intermediaries

With the requirements for the device specific headers etc. does that rule out decentralising it in the way it was before? It's handy being able to go straight to MS since it won't add extra load on intermediaries

Everything is cached on XR side (max TTL of 15 minutes) and pulled from the mediahub endpoint with a valid XSTS token (signed + title / device combination).
If you really want to exclusively use XSAPI endpoints (Xbox Services API), upcoming endpoints will allow you to create your own signed XSTS token which grants the same access as XboxReplay to this service.

Everything is cached on XR side (max TTL of 15 minutes) and pulled from the mediahub endpoint with a valid XSTS token (signed + title / device combination).
If you really want to exclusively use XSAPI endpoints (Xbox Services API), upcoming endpoints will allow you to create your own signed XSTS token which grants the same access as XboxReplay to this service.

Ah, that's pretty comprehensive. Good to know both options exist. I look forward to giving this a go!

Ah, that's pretty comprehensive. Good to know both options exist. I look forward to giving this a go!

Major update: As recently specified on @XboxReplay twitter account, due to an internal privacy update on XBL APIs, there's no way anymore to retrieve recent users' screenshots (except for ESRB:E (Everyone) rated games such as Minecraft).
The only way to fetch them is to ask the user to authenticate itself on XboxReplay.net (for instance) and use its token to fetch its content.
This process also requires "signed tokens" but as I managed to reverse the signature algorithm, this is not an issue (already used on halodotapi.com projects).

Hi there,
I am trying to use this library to get clips but I am seeing next to nothing when using my gamertags. This issue seems relevant, but I am confused as to the status of things and the solutions to the issues.
It sounds like the 4.0.0 branch might work? Or is there more to it?

I tried 4.0.0 but I get a 404 error when trying to fetch clips via getPlayerGameClips, which uses https://mediahub.xboxlive.com/clips/search. Some internet searching led me nowhere with regard to that.
The documentation for 4.0.0 mentions an XboxReplay wrapper, which sounds like it uses xboxreplay.net as a middle man, but it requires a token ( const XRSimpleAPIInstance = new XRSimpleAPI('YOUR_CLIENT_TOKEN');) and I don't see anything on the site about signing up and getting a token.
I realize 4.0.0 is WIP, but any help is appreciated! Cheers

Hi, is there a merge between the branch 4.0 and the main branch planned ?

Hey there, just wanted to add in my interest for an update to this repo and the 4.0 branch. I pulled down the branch and tried using getPlayerGameClips but get 404s when trying to hit https://mediahub.xboxlive.com/clips/search. Would love an update on this so we could directly make calls to the MS service!

Hey @RyanEwen @xenursXX @Develonaut, sorry for the late reply.
Right now I do not have bandwidth to continue my work on the 4.0.0 and the new XboxReplay API due to my major implication on HaloDotAPI (see: https://autocode.com/community/announcements/halodotapi-is-joining-autocode/)
Once everything is done I may be able to finish it :)
Cheers!

@RyanEwen @Develonaut the right endpoint for mediahub is https://mediahub.xboxlive.com/gameclips/search. I request like this should work:
curl --location --request POST 'https://mediahub.xboxlive.com/gameclips/search' \
--header 'Authorization: XBL3.0 x=userhash;xsts_token \
--header 'Content-Type: application/json' \
--data-raw '{"query": "OwnerXuid eq xuid"}'

However using this endpoint I'm still missing some clips for specific games, like FIFA and Halo Infinite. If you guys find a solution for that, please share :)

@RyanEwen @Develonaut the right endpoint for mediahub is https://mediahub.xboxlive.com/gameclips/search. I request like this should work:
curl --location --request POST 'https://mediahub.xboxlive.com/gameclips/search' \
--header 'Authorization: XBL3.0 x=userhash;xsts_token \
--header 'Content-Type: application/json' \
--data-raw '{"query": "OwnerXuid eq xuid"}'

However, using this endpoint, I'm still missing some clips for specific games, like FIFA and Halo Infinite. If you guys find a solution for that, please share :)

@KarineValenca were you able to find a way to grab clips for Halo Infinite? I'm having the same issue.

@ferhanmm no luck yet  :/


add method to get the first-contentful-paint

added a getFirstContentfulPaint() method in surfnperf.js to be the similar to getFirstPaint() with the "first-contentful-paint" name instead of "first-paint"

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for the PR! Can you please make a couple changes so we can get this merged?

Add tests for the new getFirstContentfulPaint() function. These will be very similar to getFirstPaint()'s function.
Run grunt precommit, and I believe that should revert all the whitespace changes so your PR will only be the changes

made the mentioned changes please have a look at it and let me know if anything else required to complete this PR


enable better code hub support

https://bettercodehub.com

Think we have moved a fair bit away from better code hub. Would be fine with closing this issue


Dependencies upgrade

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 98.07%. Comparing base (89a0651) to head (e793ff5).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main       #6   +/-   ##
=======================================
  Coverage   98.07%   98.07%
=======================================
  Files          43       43
  Lines        4478     4478
  Branches      747      747
=======================================
  Hits         4392     4392
  Misses         63       63
  Partials       23       23

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[COOK-3296] Fix all foodcritic violations

https://tickets.opscode.com/browse/COOK-3296
Fix all Foodcritic violations.
Fix all Tailor violations, except line length, which was ignored.

We're green in Foodcritic with the current release.


experimenting with edge configurations in next

Keeping it how I had it for now, I want all edge and I don't want to manually specify it everywhere


[RFC] Moving strategy for espresso, stomp, and partial

As discussed in #380 we're moving  espresso, stomp, and partial to the Friends of ReactPHP. We ca do that in several different ways:

Move the repository, and all it's issues, PR's etc etc over leaving everything intact (Github will arrange the redirect for us so packagist and travis still work). This does keep the package (initially) in the react vendor.
Fork the repository, having to port a all outstanding issues and PR's over, and loosing the history for them on our active repository. But that means we release a new first version under the new vendor and abandon the react package in favour of the Friends of ReactPHP package.

Ping @cboden, @clue, @jsor

Forking has a lot more benefits in this case, we can e.g. also mark react/stomp deprecated in favor of friendlyreaction/stomp (or what ever the name)

@the-eater Looks like you can do this also when moving the repository. The php-cs-fixer repo has been moved over to an organisation:
https://packagist.org/packages/fabpot/php-cs-fixer (abandoned) -> https://packagist.org/packages/friendsofphp/php-cs-fixer.

I'm 👍 for moving the repos.

Oh if that's the case, :+1: for moving!

Yes, you can just move it and rename the package in composer.json afterwards and resubmit to Packagist.

Move the repository, and all it's issues, PR's etc etc over leaving everything intact (Github will arrange the redirect for us so packagist and travis still work). This does keep the package (initially) in the react vendor.

Big plus :+1:
The PRs/issues provide a lot of value (to consumers and maintainers of these packages). If we were to only copy things to a new location, we would still have to somehow mark the old location as deprecated, which could cause further friction.
Moving everything to the new location first makes a lot of sense. We could defer the decision if/when renaming the package and vendor namespace makes sense, I have no strong opinion here and would love to hear some more thoughts on this from others :+1:

We've decided to move these repositories to https://github.com/friends-of-reactphp Wednesday evening. I'll move them, and make sure all redirects are working and they can still be installed through composer without issues.

The repositories have been moved :tada:


netcdf_SO_VERSION mismatch (SONAME) in 4.9.2

netCDF_SO_VERSION is defined in two places.  In 4.9.2 and earlier, this SO number is mismatched.
configure.ac:
# These linker flags specify libtool version info ...
# These values should match those in CMakeLists.txt
AC_SUBST([netCDF_SO_VERSION]) netCDF_SO_VERSION=21:2:2

CMakeLists.txt:
# These values should match those in configure.ac ...
SET(netCDF_SO_VERSION 19)

Please synchronize these for new releases.  If there is some reason to not synchronize, please explain that in the comments.

They are synchronized; the autoconf build system uses the numbers provided to calculate an SO. This value is then synchronized to be reflected in the cmake based system. In both systems, the SO (calculated and assigned) is 19.

Thanks for explaining.  My understanding of sonames and compatibility versioning is incomplete.


Emitter doesn't work properly with Event Stream

Looks like comparing with current ob_level prevents emitter to flush the main stream
https://github.com/yiisoft/yii-runner-http/blob/23d89de28a761ea06727ee895cec80c2dfcd309e/src/SapiEmitter.php#L112
In the dev panel I see results only when event stream times out.

Problem not here:


[WFCORE-3303] Bump the logging subsystem schema and model versions.

https://issues.jboss.org/browse/WFCORE-3303

Full integration - Windows Build 4277 outcome was FAILURE using a merge of 677f4bcf3f1fbe2034a77b1bb850e00a7db1d11f
Summary: Tests failed: 11 (11 new), passed: 4065, ignored: 95 Build time: 01:52:29
Failed tests
org.jboss.as.test.integration.domain.mixed.eap630.MixedDomainDeployment630TestCase: java.lang.AssertionError: Slave server-one did not start within 20000 ms
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSupport.startSlaveServer(MixedDomainTestSupport.java:163)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSupport.start(MixedDomainTestSupport.java:126)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:154)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:131)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:78)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:68)
	at org.jboss.as.test.integration.domain.mixed.eap630.MixedDomain630TestSuite.initializeDomain(MixedDomain630TestSuite.java:44)
	at org.jboss.as.test.integration.domain.mixed.eap630.MixedDomainDeployment630TestCase.beforeClass(MixedDomainDeployment630TestCase.java:38)
------- Stdout: -------
21:52:04,058 INFO  [org.jboss.modules] (main) JBoss Modules version 1.6.1.Final
21:52:04,387 INFO  [org.jboss.as.process.Host Controller.status] (main) WFLYPC0018: Starting process 'Host Controller'
[Host Controller] 21:52:04,886 INFO  [org.jboss.modules] (main) JBoss Modules version 1.6.1.Final
[Host Controller] 21:52:05,188 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.7.SP1
[Host Controller] 21:52:05,248 INFO  [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: WildFly Full 11.0.0.Final-SNAPSHOT (WildFly Core 4.0.0.Alpha1-SNAPSHOT) starting
[Host Controller] 21:52:05,770 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/core-service=management/management-interface=native-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
[Host Controller] 21:52:05,772 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/core-service=management/management-interface=http-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
[Host Controller] 21:52:05,838 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'permgen-size' in the resource at address '/host=master/jvm=default' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
[Host Controller] 21:52:05,838 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'max-permgen-size' in the resource at address '/host=master/jvm=default' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
[Host Controller] 21:52:05,873 INFO  [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0003: Creating http management service using network interface (management) port (9990) securePort (-1)
[Host Controller] 21:52:05,879 INFO  [org.xnio] (MSC service thread 1-1) XNIO version 3.5.1.Final
[Host Controller] 21:52:05,884 INFO  [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.5.1.Final
[Host Controller] 21:52:05,905 INFO  [org.jboss.as.patching] (MSC service thread 1-6) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
[Host Controller] 21:52:05,936 WARN  [org.jboss.as.domain.management.security] (MSC service thread 1-3) WFLYDM0111: Keystore C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\mixed-domain\target\domains\MixedDomain630TestSuite\master\configuration\application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
[Host Controller] 21:52:05,961 INFO  [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 5.0.2.Final
[Host Controller] 21:52:06,004 INFO  [org.jboss.as.remoting] (MSC service thread 1-8) WFLYRMT0001: Listening on [::1]:9999
[Host Controller] 21:52:07,302 INFO  [org.wildfly.security] (Controller Boot Thread) ELY00001: WildFly Elytron version 1.2.0.Beta3
[Host Controller] 21:52:07,345 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=default/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
[Host Controller] 21:52:07,384 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=ha/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
[Host Controller] 21:52:07,415 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=full/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
[Host Controller] 21:52:07,444 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=full-ha/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
[Host Controller] 21:52:07,613 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0062: Http management interface listening on http://[::1]:9990/management and https://[::1]:-1/management
[Host Controller] 21:52:07,614 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0054: Admin console is not enabled
[Host Controller] 21:52:07,614 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 11.0.0.Final-SNAPSHOT (WildFly Core 4.0.0.Alpha1-SNAPSHOT) (Host Controller) started in 3128ms - Started 51 of 55 services (19 services are lazy, passive or on-demand)
INFO  [org.jboss.as.test.integration.domain.management.util.DomainLifecycleUtil] HostController started in 4237 ms
[Host Controller] 21:52:09,617 INFO  [org.jboss.as.controller.management-deprecated] (management-handler-thread - 3) WFLYCTL0028: Attribute 'default-stack' in the resource at address '/' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
[Host Controller] 21:52:10,186 INFO  [org.jboss.as.controller.management-deprecated] (management-handler-thread - 4) WFLYCTL0028: Attribute 'stack' in the resource at address '/' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
[Host Controller] 21:52:10,666 WARN  [org.jboss.as.messaging] (management-handler-thread - 2) WFLYMSG0071: There is no resource matching the expiry-address jms.queue.ExpiryQueue for the address-settings #, expired messages from destinations matching this address-setting will be lost!
[Host Controller] 21:52:10,667 WARN  [org.jboss.as.messaging] (management-handler-thread - 2) WFLYMSG0072: There is no resource matching the dead-letter-address jms.queue.DLQ for the address-settings #, undelivered messages from destinations matching this address-setting will be lost!
[Host Controller] 21:52:10,894 WARN  [org.wildfly.iiop.openjdk] (management-handler-thread - 4) WFLYIIOP0111: SSL has not been configured but ssl-port property has been specified - the connection will use clear-text protocol
[Host Controller] 21:52:11,499 INFO  [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: WildFly Full 11.0.0.Final-SNAPSHOT (WildFly Core 4.0.0.Alpha1-SNAPSHOT) stopped in 20ms
[Host Controller] 21:52:11,500 INFO  [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Full 11.0.0.Final-SNAPSHOT (WildFly Core 4.0.0.Alpha1-SNAPSHOT) starting
[Host Controller] 21:52:11,518 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/core-service=management/management-interface=native-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
[Host Controller] 21:52:11,519 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/core-service=management/management-interface=http-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
[Host Controller] 21:52:11,523 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'permgen-size' in the resource at address '/host=master/jvm=default' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
[Host Controller] 21:52:11,523 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'max-permgen-size' in the resource at address '/host=master/jvm=default' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
[Host Controller] 21:52:11,527 INFO  [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0003: Creating http management service using network interface (management) port (9990) securePort (-1)
[Host Controller] 21:52:11,533 INFO  [org.jboss.as.patching] (MSC service thread 1-8) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
[Host Controller] 21:52:11,538 WARN  [org.jboss.as.domain.management.security] (MSC service thread 1-2) WFLYDM0111: Keystore C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\mixed-domain\target\domains\MixedDomain630TestSuite\master\configuration\application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
[Host Controller] 21:52:11,588 INFO  [org.jboss.as.remoting] (MSC service thread 1-2) WFLYRMT0001: Listening on [::1]:9999
[Host Controller] 21:52:11,734 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'default-stack' in the resource at address '/profile=full-ha/subsystem=jgroups' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.

org.jboss.as.test.integration.domain.mixed.eap630.DomainHostExcludes630TestCase: java.lang.RuntimeException: java.lang.RuntimeException: MgmtOperationException{operation={
    "operation" => "remove",
    "address" => [("system-property" => "java.net.preferIPv4Stack")]
}, result={
    "outcome" => "failed",
    "failure-description" => {"domain-failure-description" => "WFLYCTL0216: Management resource '[(\"system-property\" => \"java.net.preferIPv4Stack\")]' not found"},
    "rolled-back" => true
}}
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:158)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:131)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupportForLegacyConfig(MixedDomainTestSuite.java:125)
	at org.jboss.as.test.integration.domain.mixed.eap630.LegacyConfig630TestSuite.initializeDomain(LegacyConfig630TestSuite.java:37)
	at org.jboss.as.test.integration.domain.mixed.eap630.DomainHostExcludes630TestCase.beforeClass(DomainHostExcludes630TestCase.java:38)
Caused by: java.lang.RuntimeException: MgmtOperationException{operation={
    "operation" => "remove",
    "address" => [("system-property" => "java.net.preferIPv4Stack")]
}, result={
    "outcome" => "failed",
    "failure-description" => {"domain-failure-description" => "WFLYCTL0216: Management resource '[(\"system-property\" => \"java.net.preferIPv4Stack\")]' not found"},
    "rolled-back" => true
}}
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSupport.startAndAdjust(MixedDomainTestSupport.java:205)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSupport.start(MixedDomainTestSupport.java:119)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:154)
	... 41 more
Caused by: MgmtOperationException{operation={
    "operation" => "remove",
    "address" => [("system-property" => "java.net.preferIPv4Stack")]
}, result={
    "outcome" => "failed",
    "failure-description" => {"domain-failure-description" => "WFLYCTL0216: Management resource '[(\"system-property\" => \"java.net.preferIPv4Stack\")]' not found"},
    "rolled-back" => true
}}
	at org.jboss.as.test.integration.domain.management.util.DomainTestUtils.executeForResult(DomainTestUtils.java:160)
	at org.jboss.as.test.integration.domain.mixed.LegacyConfigAdjuster.removeIpv4SystemProperty(LegacyConfigAdjuster.java:84)
	at org.jboss.as.test.integration.domain.mixed.LegacyConfigAdjuster.adjust(LegacyConfigAdjuster.java:70)
	at org.jboss.as.test.integration.domain.mixed.LegacyConfigAdjuster.adjustForVersion(LegacyConfigAdjuster.java:65)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSupport.startAndAdjust(MixedDomainTestSupport.java:187)
	... 43 more
------- Stdout: -------
INFO  [org.jboss.as.test.integration.domain.management.util.DomainLifecycleUtil] HostController started in 292 ms
Failed operation:
{
    "operation" => "remove",
    "address" => [("system-property" => "java.net.preferIPv4Stack")]
}
Response:
{
    "outcome" => "failed",
    "failure-description" => {"domain-failure-description" => "WFLYCTL0216: Management resource '[(\"system-property\" => \"java.net.preferIPv4Stack\")]' not found"},
    "rolled-back" => true

org.jboss.as.test.integration.domain.mixed.eap630.MixedDomainOverlay630TestSuite: java.lang.RuntimeException: java.lang.RuntimeException: MgmtOperationException{operation={
    "operation" => "write-attribute",
    "address" => [("server-group" => "main-server-group")],
    "name" => "profile",
    "value" => "default"
}, result={
    "outcome" => "failed",
    "failure-description" => {"domain-failure-description" => "WFLYCTL0369: Required capabilities are not available:
    org.wildfly.domain.profile.default in context 'server-groups'; Possible registration points for this capability:
  /profile=*"},
    "rolled-back" => true
}}
java.lang.RuntimeException: java.lang.RuntimeException: MgmtOperationException{operation={
    "operation" => "write-attribute",
    "address" => [("server-group" => "main-server-group")],
    "name" => "profile",
    "value" => "default"
}, result={
    "outcome" => "failed",
    "failure-description" => {"domain-failure-description" => "WFLYCTL0369: Required capabilities are not available:
    org.wildfly.domain.profile.default in context 'server-groups'; Possible registration points for this capability:
		/profile=*"},
    "rolled-back" => true
}}
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:158)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:102)
	at org.jboss.as.test.integration.domain.mixed.eap630.MixedDomainOverlay630TestSuite.initializeDomain(MixedDomainOverlay630TestSuite.java:43)
Caused by: java.lang.RuntimeException: MgmtOperationException{operation={
    "operation" => "write-attribute",
    "address" => [("server-group" => "main-server-group")],
    "name" => "profile",
    "value" => "default"
}, result={
    "outcome" => "failed",
    "failure-description" => {"domain-failure-description" => "WFLYCTL0369: Required capabilities are not available:
    org.wildfly.domain.profile.default in context 'server-groups'; Possible registration points for this capability:
		/profile=*"},
    "rolled-back" => true
}}
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSupport.startAndAdjust(MixedDomainTestSupport.java:205)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSupport.start(MixedDomainTestSupport.java:119)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:154)
	... 29 more
Caused by: MgmtOperationException{operation={
    "operation" => "write-attribute",
    "address" => [("server-group" => "main-server-group")],
    "name" => "profile",
    "value" => "default"
}, result={
    "outcome" => "failed",
    "failure-description" => {"domain-failure-description" => "WFLYCTL0369: Required capabilities are not available:

org.jboss.as.test.integration.domain.mixed.eap640.KernelBehavior640TestSuite: java.lang.AssertionError: expected:<EAP_6_3_0> but was:<EAP_6_4_0>
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getVersion(MixedDomainTestSuite.java:56)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:137)
	at org.jboss.as.test.integration.domain.mixed.KernelBehaviorTestSuite.getSupport(KernelBehaviorTestSuite.java:41)
	at org.jboss.as.test.integration.domain.mixed.eap640.KernelBehavior640TestSuite.initializeDomain(KernelBehavior640TestSuite.java:42)

org.jboss.as.test.integration.domain.mixed.eap640.LegacyConfig640TestSuite: java.lang.AssertionError: expected:<EAP_6_3_0> but was:<EAP_6_4_0>
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getVersion(MixedDomainTestSuite.java:56)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:137)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:131)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupportForLegacyConfig(MixedDomainTestSuite.java:125)
	at org.jboss.as.test.integration.domain.mixed.eap640.LegacyConfig640TestSuite.initializeDomain(LegacyConfig640TestSuite.java:37)

org.jboss.as.test.integration.domain.mixed.eap640.MixedDomain640TestSuite: java.lang.AssertionError: expected:<EAP_6_3_0> but was:<EAP_6_4_0>
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getVersion(MixedDomainTestSuite.java:56)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:137)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:131)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:78)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:68)
	at org.jboss.as.test.integration.domain.mixed.eap640.MixedDomain640TestSuite.initializeDomain(MixedDomain640TestSuite.java:44)

org.jboss.as.test.integration.domain.mixed.eap640.MixedDomainOverlay640TestSuite: java.lang.AssertionError: expected:<EAP_6_3_0> but was:<EAP_6_4_0>
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getVersion(MixedDomainTestSuite.java:56)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:137)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:102)
	at org.jboss.as.test.integration.domain.mixed.eap640.MixedDomainOverlay640TestSuite.initializeDomain(MixedDomainOverlay640TestSuite.java:43)

org.jboss.as.test.integration.domain.mixed.eap700.KernelBehavior700TestSuite: java.lang.AssertionError: expected:<EAP_6_3_0> but was:<EAP_7_0_0>
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getVersion(MixedDomainTestSuite.java:56)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:137)
	at org.jboss.as.test.integration.domain.mixed.KernelBehaviorTestSuite.getSupport(KernelBehaviorTestSuite.java:41)
	at org.jboss.as.test.integration.domain.mixed.eap700.KernelBehavior700TestSuite.initializeDomain(KernelBehavior700TestSuite.java:42)

org.jboss.as.test.integration.domain.mixed.eap700.LegacyConfig700TestSuite: java.lang.AssertionError: expected:<EAP_6_3_0> but was:<EAP_7_0_0>
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getVersion(MixedDomainTestSuite.java:56)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:137)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:131)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupportForLegacyConfig(MixedDomainTestSuite.java:125)
	at org.jboss.as.test.integration.domain.mixed.eap700.LegacyConfig700TestSuite.initializeDomain(LegacyConfig700TestSuite.java:37)

org.jboss.as.test.integration.domain.mixed.eap700.MixedDomain700TestSuite: java.lang.AssertionError: expected:<EAP_6_3_0> but was:<EAP_7_0_0>
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getVersion(MixedDomainTestSuite.java:56)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:137)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:131)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:78)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:68)
	at org.jboss.as.test.integration.domain.mixed.eap700.MixedDomain700TestSuite.initializeDomain(MixedDomain700TestSuite.java:44)

org.jboss.as.test.integration.domain.mixed.eap700.MixedDomainOverlay700TestSuite: java.lang.AssertionError: expected:<EAP_6_3_0> but was:<EAP_7_0_0>
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getVersion(MixedDomainTestSuite.java:56)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:137)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:102)
	at org.jboss.as.test.integration.domain.mixed.eap700.MixedDomainOverlay700TestSuite.initializeDomain(MixedDomainOverlay700TestSuite.java:43)

##### there are 1 more failed tests, see build details


Update jsoniter-scala-core, ... to 2.10.2

Updates

com.github.plokhotnyuk.jsoniter-scala:jsoniter-scala-core
com.github.plokhotnyuk.jsoniter-scala:jsoniter-scala-macros

from 2.10.0 to 2.10.2.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.github.plokhotnyuk.jsoniter-scala" } ]

labels: library-update, semver-patch

Codecov Report

Merging #295 (b280ac5) into master (86d520e) will increase coverage by 0.11%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #295      +/-   ##
==========================================
+ Coverage   34.89%   35.01%   +0.11%
==========================================
  Files          29       29
  Lines         298      297       -1
  Branches        6        8       +2
==========================================
  Hits          104      104
+ Misses        194      193       -1

Impacted Files
Coverage Δ

...com/permutive/pubsub/consumer/ConsumerRecord.scala
0.00% <0.00%> (ø)

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 86d520e...b280ac5. Read the comment docs.


chore: croc-hunter-jenkinsx to 0.0.64

chore: Promote croc-hunter-jenkinsx to version 0.0.64

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@carlossg: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

promotion-build
e7a6dd032abd15034ea54d996b15396e646b9165
link
/test this

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/meow

@carlossg:

In response to this:

/meow

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@carlossg: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

promotion-build
e7a6dd032abd15034ea54d996b15396e646b9165
link
/test this

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


[style]: The theme toggle button hides after a particular screen width

What's the style idea?
The theme toggle button is not visible (i.e. it hides behind the searchbar) from 769px to 1100px
Add screenshots

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@SaranshBangar I would love to fix this issue. Please assign this issue to me. I am a contributor for GSSOC' 24.

Resolved in PR #981

@SaranshBangar I would love to fix this issue. Please assign this issue to me. I am a contributor for GSSOC' 24.

I have already raised a PR (#981) @PranavKeshav24

@shyamtawli  sir, please look into this issue, it is closed in PR #981


How to: .es6 to .js

How do I use grunt-6to5 to compile one directory to another directory (including sub-folders), and instead of compiling the .es6 from to .es6, I want them to be .js file. Can you tell me how to do this? I can't figure it out. It seems like most people want to compile from .es6 to .js, so I am wondering if this is supported. Or, is this something that I should just do with another grunt task?

unless I'm missing something profound it's all in the standard grunt files config right?
"6to5": {
    all: {
        files: [
            {
                expand: true,
                cwd: "<%= publicDir %>",
                src: ["js/src/**/*.es6",
                dest: "<%= tmpDir %>",
                ext: ".js"
            }
        ]
    }
}

Yes, it's just the standard grunt config. Read the grunt docs.

Just hit this question myself and wanted to clarify that dest isn't required for the sake of the extension rename. Here's an updated example (note it's babel now and not 6to5):
In the following, sourceMap, presets and compact are also not required for a rename, but I needed to be able to source specific files with ES6 (not worrying about which files were which) so I use grunt to concat my files to my dest folder, then I target them with babel and my site targets those files. Sourcemaps were getting out of hand so I've disabled for now (since I rarely use them for debugging).
babel: {
    options: {
        sourceMap: false,
        presets: ['es2015'],
        compact: true
    },
    files: {
        expand: true,
        src: ['dist/scripts/**/*.es6'],
        ext: '.js'
    }
},


Guard 1.0 and fixes

+1 for bumping the guard dependency.

I planned time early next week for the maintenance of this gem

This is just a friendly reminder that we'd all love to get this incorporated into the master branch, even if no versioned release is ready yet.

There was a small conflict merging this due to 966b8e6.
Feel free to merge from my fork where I've resolved it.


MySQL Group Replication Exploration

Resources

Distributed Recovery

Possible Performance Improvement

Use separate port for distributed recovery
Use compression during recovery through binlog replay

Possible Performance Improvement

Use separate port for distributed recovery
Use compression during recovery through binlog replay


🍒 Cherry pick PR #20704 to staging 🍒

🍒 Cherry pick https://github.com/Expensify/App/pull/20704 to staging 🍒

🚀 Cherry-picked to staging by https://github.com/OSBotify in version: 1.3.27-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by https://github.com/AndrewGable in version: 1.3.27-7 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Cherry-picked to staging by https://github.com/AndrewGable in version: 1.3.28-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by https://github.com/AndrewGable in version: 1.3.28-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


[main] Add Konflux configurations

Add Konflux components and pipelines

/hold
Until we cut 1.34

/lgtm

/unhold

/hold

/unhold
as we need to create the components first (before we add the pipelines (https://github.com/openshift-knative/serverless-operator/pull/2824))


Map performance could be better?!

Is your feature request related to a problem? Please describe.
This is more of an open question / spike ticket that may yield more tickets, but we're noticing a few areas where map performance could be improved, for example at zoom level 7 in the South. We could use some help identifying concrete improvements we can make to the map to help with performance in different specific regions as well as overall.
Notably, some of the improvements may be back end rather than front end. We're looking for ideas that we could implement at any layer of the stack.
Describe the solution you'd like
Buttery smooth and fast zoom and map performance everywhere!

@switzersc-usds is there a demo instance up somewhere so that performance issues can be easily assessed?

@KameronKerger, @BethMattern - is this still an issue?


docs: update code-of-conduct URLs

Relates-to PyCQA/pycodestyle#1236.

cc @asottile; purely a broken-hyperlink fixup, this changeset.


Expand client configurability and switch to pretty-printed JSON.

This allows overriding the client's config setting via environment variable and the new --set command-line flag. It also adds a config knob to control JSON rendering with/without pretty-printing, defaulting it to on.
Example: to turn that flag off, you'd say zeek-client --set client.pretty_json=false ....
(Unit tests forthcoming, I'm putting the basic harness for it together in a separate PR)

Closing this, commits got merged via another branch.


Fixes for a couple Google-related issues

Closing until I can figure out why Travis CI isn't playing nice with tox and pytest's conftest files.


GitHub email not necessarily becoming user email

I discovered a camper's record that had a "githubEmail" property (pulled from GitHub), but had no "email" property. They weren't getting our email updates and wanted them.
"githubEmail"<EMAIL_ADDRESS>User story: When I link my GitHub account with my FCC account, it should check whether I have an email address, and if not set it to my githubEmail.
@BerkeleyTrue what do you think of this?

Yeah, ai had this problem too. I would like to subscribe to news aggregation email you announced on Medium but didn't get any.
I registered through Github auth,

@NicholasAsimov If you go to your settings page on FreeCodeCamp, you can update your email with us. This has been introduced recently.

@BerkeleyTrue this issue is also resolved with the below I believe?
https://github.com/FreeCodeCamp/FreeCodeCamp/blob/staging/server/utils/auth.js#L37

@raisedadead Yeah, I updated the email recently and it worked flawlessly, I recieved Quincy's news email too.

Yes.
Happy Coding!


Avoid converting array holding existentials

Motivation:
When converting an Array that holds existentials, it is necessary for Swift to allocate a new Array and copy the elements into it, so that it can fix up their existential boxes. We forced this to happen with taking a [ChannelHandler] to [ChannelHandler & Sendable], without rewriting the other functions.
The result of that was that the other functions needed to convert the channel handler types, causing extra allocations in this path.
Modifications:
Propagate the constraint down to the point where we iterate the Array.
Result:
Allocations reduced.

Of course, this change just moved the cost into the SyncOperations instead. So they now need to have totally separate codepaths to avoid reprojecting the array.


Overlay:  bounds prop set wrong position of an image

I have trouble with an image overlay.
Is this a bug report?
BUG

Have you read the Installation Instructions?
yes
Environment
{
 "react-native": "0.59.2",
 "react-native-maps": "0.23.0",
 "react": "16.8.3",
}

Simulator/iPhone 8 (AppleMaps)
Steps to Reproduce
Bounds example:
 const bounds = [
  [field.SouthLat, field.WestLon],
  [field.NorthLat, field.EastLon]
 ]

Output:
[
  [-30.173081337,149.6555078531],
  [-30.1882609123,149.664137526]
]

Expected Behavior
There is the result in browser (leaflet.js) (for the same bounds)

Actual Behavior
There is the result on iPhone 8 emulator:

Reproducible Demo
Code:
...
<Overlay bounds={[[field.SouthLat, field.WestLon], [field.NorthLat, field.EastLon]]}
                                     image={{uri}}/>
...

@gangstaJS why sorry?  Update the issue and I'll re-open it.
Ping me once you did it.

@rborn ping :)

@gangstaJS can you try to use a big  zIndex for your overlay?

@radeno I have found the issue, it is the fitToCoordinates. When I removed it the image fully was rendered. but this does not solve my problem cuz I need fitToCoordinates

Result:

@gangstaJS try to execute fit after a delay , maybe the map still needs to execute stuff (out of curiosity)

@rborn I have tried setTimeout 2sec it did not help. I can use region  prop for fit to a center of overlay but in this case, I do not have cool animation :(

@radeno Look at this wired behavior https://monosnap.com/file/HyCiFNe4JeDHsEYXcZFg9UKtWLi51W

fit = () => {
    if(this.props.shape) {
      const c = center(this.props.shape);

      const [longitude, latitude] = c.geometry.coordinates;

      this.setState({longitude, latitude}) // set regin to MapView
    }

    setTimeout(() => {
      this.props.shape && this.map.fitToCoordinates(this.props.shape.features[0].geometry.coordinates[0].map(c => ({
        latitude: c[1],
        longitude: c[0]
      })), {animated: false});
    }, 2000)
  };

@rborn and one more wired thing, when zoom the image overlay is cutting https://monosnap.com/file/MYrKy5ffX7LtqLJxqbVFyOuaa3AQLP

Looks like the problem from the above video in the Polygon, when I commented it all zooming fine
Example: https://monosnap.com/file/WVKnHcihFdYWPHhHTUIoxxh4a3vpyK

<MapView
        ref={(ref) => {
          this.map = ref;
        }}
        provider={null}
        style={styles.map}
        mapType="satellite"
        region={{
          latitude: this.state.latitude,
          longitude: this.state.longitude,
          latitudeDelta: LATITUDE_DELTA,
          longitudeDelta: LONGITUDE_DELTA,

        }}
        onPress={e => this.onPress(e)}
        zoomControlEnabled={true}
      >
        {this.props.shape ? <Polygon zindex={2} strokeWidth={3} strokeColor="rgb(51, 136, 255)"
                                     coordinates={this.props.shape.features[0].geometry.coordinates[0].map(c => ({
                                       latitude: c[1],
                                       longitude: c[0]
                                     }))}/> : null}
        {field ? <Overlay
          zindex={9}
          bounds={[[field.NorthLat, field.WestLon], [field.SouthLat, field.EastLon]]}
          image={'https://storage.googleapis.com/flurosat-au/processed-v1/fc57b8a0f8ea48181bcc07d3b4994c57/20180523T001111/20180523T001111_T55JGG_S2A_ccci_singleDate.png'}
        /> : null}

      </MapView>

@gangstaJS is your overlay image with enough resolution? iPhone simulator uses retina with 2x or 3x (depends on iPhone) bigger density than in browser. Just brainstorming about blurry image when upscaling.
Anyway incomplete rendering of image is weird. Can you test it with Google maps? Just for curiosity if it is same result.

@radeno Hey man the google maps really work perfectly
https://monosnap.com/file/mF96gyMYYbShBIeIKtmpLkZMSflGqW

@gangstaJS ok thanks for info. If i am right, Google maps uses bitmap tiles, and Apple uses vectors on iOS. So need to check where is real issue. Harder part :)

@radeno How the satellite tiles can be vectors?

@gangstaJS ah i see, you used satellite tiles. My bad. Can you test it with different map type layers? Road, satellite. It could help isolate real issue.


fix(deps): update gomod

This PR contains the following updates:

Package
Type
Update
Change

github.com/IBM/platform-services-go-sdk
require
minor
v0.48.1 -> v0.49.0

github.com/go-git/go-git/v5
require
minor
v5.8.1 -> v5.9.0

Release Notes

IBM/platform-services-go-sdk (github.com/IBM/platform-services-go-sdk)
v0.49.0
Compare Source
Features

Context-Based Restrictions: add service group support to operations (#277) (8ecdfa5)

go-git/go-git (github.com/go-git/go-git/v5)
v5.9.0
Compare Source
What's Changed

git: worktree: add Amend option to CommitOptions by @john-cai in https://github.com/go-git/go-git/pull/438
git: worktree, reset ignored files that are part of the worktree: Fixes #819 by @daolis in https://github.com/go-git/go-git/pull/821
plumbing: Do not swallow http message coming from VCS providers by @matejrisek in https://github.com/go-git/go-git/pull/835
plumbing: transport, handle IPv6 while parsing endpoint. Fixes #740 by @ninedraft in https://github.com/go-git/go-git/pull/820
*: update goproxy dependency to fix CVE-2023-37788 vulnerability by @svghadi in https://github.com/go-git/go-git/pull/832
*: bump dependencies and Go to 1.19 by @pjbgf in https://github.com/go-git/go-git/pull/837

New Contributors

@svghadi made their first contribution in https://github.com/go-git/go-git/pull/832
@daolis made their first contribution in https://github.com/go-git/go-git/pull/821

Full Changelog: https://github.com/go-git/go-git/compare/v5.8.1...v5.9.0

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This PR is included in version 1.21.6 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


How to refresh token when web client send many refresh request at one time

IdentityServer use Jwt and set RefreshTokenUsage eq OneTimeOnly, when web client use axios request api with token and return 401, the client will use axios to refresh token and retry to request api with new token.There is no question when axios send request one by one, but when axios send two or more request on time with expired token, only one request can return new token, the others can't refresh token successfully because the refresh_token has been used already.Could any one tell me how to deal with the expired token bettwen web client and IdentityServer?Thanks!

If you client lib is not clever enough to coordinate the refresh requests, then either change the library - or do not use OneTimeOnly semantics.