Indian phone numbers not supported

On trying to register with Indian phone numbers, it says that Indian phone numbers are currently not supported. What is the issue, and when is it likely to be fixed?

I have already registered with email. But before i migrate my family and
friends, I need the support for mobile numbers because that's kind of the
standard for IM services here in India(reference WhatsApp). Also, not
everyone necessarily uses email, and WhatsApp is like a primary mode of
communication. So that's why!!
On Sun, May 13, 2018, 7:51 AM SkyWheel<EMAIL_ADDRESS>wrote:

Sorry for asking, but why can't you use email instead?🙂 Or just register
without any emails and phone numbers?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vector-im/riot-android/issues/2232#issuecomment-388596245,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APUlLfOFC1dYfV54ArG38RseQMeDG_-rks5tx5ijgaJpZM4Tsbrn
.


Add audio windowing iterator

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

Project coverage is 59.33%. Comparing base (1de846f) to head (4826ce2).
Report is 6 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #142   +/-   ##
=======================================
  Coverage   59.33%   59.33%
=======================================
  Files          83       83
  Lines        2850     2850
=======================================
  Hits         1691     1691
  Misses       1159     1159

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

@ibevers any updates?

@fabiocat93 I will aim to get this one done by 09/20

@fabiocat93 this is ready for review!🌱 This will be very helpful for Bridge2AI. Thank you in advance!


Create new phone alias based on libphonenumber

https://github.com/RobinHerbots/Inputmask/issues/1378#issuecomment-358948580

Not checked yet but that sounds perfect so far :)

https://github.com/catamphetamine/libphonenumber-js

https://github.com/RobinHerbots/inputmask.phone/issues/1


feature : I18n all-countries.js

We would like to customize the list of countries to i18n it.
It will depend on the locale of the user and we need to be able to switch all the time.

This would indeed be useful.
I'm guessing https://github.com/EducationLink/vue-tel-input/blob/master/src/vue-tel-input.vue#L141 could just be made into a prop.

@iamstevendao I can create a PR for this

@Blanen that would be lovely and much appreciated!! We are a bit tight on time here :(

Whatever happened to this? It's surprising an international phone field would only offer the country names in one language...

@ryanmwc I ended up making a solution that wasn't really good enough to make a PR for but worked for us.

If there isn't any effort at translating or allowing the developer to add translations of country names, why isn't there at least a setting to remove them?  Just show the flag and the phone code.  Or is there a way?

@Blanen curious to know your solution?

This issue was closed because it has been stalled with no activity.


Changes don't show in gutter for file with the name same as parent directory

Issue Type: Bug

Open VSCode
File name stem is same as parent directory (eg processing.py in the processing folder)
Make a change to source code in file
-> No indication of change in gutter, but change still shows in source control tab.

VS Code version: Code - Insiders 1.64.0-insider (7b9e5c32a053669d4e72f998e4fa217090c32f59, 2021-12-22T05:15:28.225Z)
OS version: Windows_NT x64 10.0.19042
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-10850H CPU @ 2.70GHz (12 x 2712)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.61GB (9.12GB free)

Process Argv
--crash-reporter-id cb42f697-ad09-444c-b86d-8cd62a1d3e46

Screen Reader
no

VM
0%

Extensions: none
A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythontb:30258533
pythonvspyt551cf:30291413
pythonptprofiler:30281269
vshan820:30294714
pythondataviewer:30285072
vscod805:30301674
pythonvspyt200:30323110
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30404738
vscop804cf:30404767
vscop453:30404998
vsclayoutctrc:30405799
py55gd98:30408621
vscexrecpromp3c:30407757
azactmsal:30409287

This gif shows:

Edit processing.py in processing folder. Change shows in source control but not in gutter.
Change name of processing.py to processing_.py. Commit change.
Edit processing_.py in processing folder. Change shows in BOTH source control AND gutter.

Issue seems to be case insensitive. Ie) issue persists if instead I name processing.py to Processing.py

@wcheek, apologies for not getting back to you on this until now. I was wondering if you are still able to reproduce this problem with the latest version of VS Code? If so, is this a public repository that I could clone locally in order to reproduce the issue and further debug it? Thank you very much!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


add minimum version numbers to python modules in requirements.txt

Describe the bug
The requirements.txt file should specify the minimum version number of each python package.

Hi @simsong , this will be addressed in the next release.
Thanks,
--Erik


root namespace and namespace from directory cannot be used together

cfg::__get_file_source handles the ns from directory option only if a root ns is not provided. These options should be able to be used together

fixed in release 0.0.4


Support connecting to a pruned Bitcoin node

It may be possible to run satstack with a pruned chain state, which can significantly reduce the disk usage to just a few GBs. The downside is that historical transactions won't show up on Ledger Live.
This feature should be accompanied by Ledger Live displaying an appropriate message to the user if the Bitcoin node is pruned.
Ref: https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-0.12.0.md#wallet-pruning

Yup, txindex=1 is not compatible with -prune=XXX therefore you get sth like this when running lss.exe:

FATAL Failed to initialize Bus                      error=failed to detect txindex: failed to get block
I hacked my way pass that error by setting txIndexEnabled to always true. txindex=1 is not mandatory according to the readme.
But then I got:
[2022/04/17 - 02:18:16]  INFO worker: #RunTheNumbers successful                     actualSupply=19013535.93066619 BTC expectedSupply=19013743.75 BTC height=732199
[GIN] 2022/04/17 - 02:18:18 | 200 |    475.8226ms |       <IP_ADDRESS> | GET      "/blockchain/v3/explorer/status"
[GIN] 2022/04/17 - 02:18:18 | 200 |    127.1599ms |       <IP_ADDRESS> | GET      "/blockchain/v3/explorer/status"
[GIN] 2022/04/17 - 02:18:19 | 200 |      80.418ms |       <IP_ADDRESS> | GET      "/blockchain/v3/explorer/status"
[2022/04/17 - 02:18:19] ERROR worker: Failed while importing descriptors            error=-4: This type of wallet does not support this command
[2022/04/17 - 02:18:19] FATAL worker: Failed to send INTERRUPT signal               error=not supported by windows pid=21488

I haven't looked enough to see if satstack has a chance to work with pruned nodes.


Fixed examples and tests for windows without MSYS2 (Unicode and multi)

Hi, I made some changes to tests and examples for them to run on Windows without MSYS2. On both Unicode and multi-byte.
As you can see, on Windows commands like echo or cd are internal  to cmd.exe, so you need to launch cmd process.
But timeout (somehow equivalent to sleep) is not internal, so no cmd needed.
Unicode support requires using windows TEXT() macro for literals to support both cases. And choose between std::to_string or std::to_wstring.

Thank you again, but I have to give this some thought. The examples and tests are getting a bit ugly, but that is maybe not avoidable.

Yes, I know. I felt the same way.
This is the nicer I could do. Maybe a second pair of eyes can improve.

Maybe instead of having the library interface with wide strings, have it interface with UTF-8 encoded narrow strings and internally convert to UTF-16 encoded wide strings for Windows. The user would just write something like Process process3(u8"timeout 5"); instead of Process process3(L"timeout 5");. This would also have a side effect of writing easier code for test units.

If you don't actually need to support unicode, I think you can also just call CreateProcessA instead of plain CreateProcess.
From windows headers:
#ifdef UNICODE
#define CreateProcess  CreateProcessW
#else
#define CreateProcess  CreateProcessA
#endif // !UNICODE

That way you will always be using non-unicode version, regardless of UNICODE being defined or not. You will also not need any #ifdef UNICODE or kind of stuff. Just always non-unicode.
I can do it, please confirm you are willing to drop unicode support from your interface.

I have removed unicode support from interface, (back to std::string) and updated tests and examples. On windows this works on both cases, Unicode and MultiByte.
I will be out-of-the office for a couple of weeks, so I will not be able to update this.

As this is somewhat non-critical, I've postponed working on it. Hopefully, I'll come to a conclusion/solution during the following week.

I decided to not use too many defines in the examples. See the commit above. Thanks for the useful info and testing on Windows without MSYS2!


Added a form modal for the mentor to assign task to the user and I fixed a little bug on the mentee dashboard

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- src/components/MentorDashbord/tasks/AssignTaskForm.js  2
- src/components/MenteeDashboard/WelcomeAlert.js  2

See the complete overview on Codacy


SOL --> Koinly import not working anymore

Hi,
Koinly import for SOL does not seem to work anymore. It was working a couple of days ago.
Koinly error message on import:
file must have these headers: ID (read-only),Date (UTC),Type,Tag,From Wallet ID,From Amount,From Currency,To Wallet ID,To Amount,To Currency,Fee Amount,Fee Currency,Net Worth Amount,Net Worth Currency,Fee Worth Amount,Fee Worth Currency,Deleted,TxSrc,TxDest,TxHash,Description
Job link:
https://stake.tax/?jobId=922aa93847904c7b9808c0d1106f6a10
Thanks!!

Those are the headers which are present in the Koinly csv from stake.tax:
Date,Sent Amount,Sent Currency,Received Amount,Received Currency,Fee Amount,Fee Currency,Net Worth Amount,Net Worth Currency,Label,Description,TxHash

Thanks for the report!  Will get on it ASAP
On Fri, Feb 2, 2024 at 3:10 AM coreworx @.***> wrote:

Those are the headers which are present in the Koinly csv from stake.tax:
Date,Sent Amount,Sent Currency,Received Amount,Received Currency,Fee
Amount,Fee Currency,Net Worth Amount,Net Worth
Currency,Label,Description,TxHash
—
Reply to this email directly, view it on GitHub
https://github.com/hodgerpodger/staketaxcsv/issues/332#issuecomment-1923587623,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AATDGEJX7YICAAA3KUVN6GTYRTCR7AVCNFSM6AAAAABCWPTO5KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRTGU4DONRSGM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Just tried that wallet.  Koinly import seems to be fine (just one error saying currency not found; but that makes sense).  Perhaps downloaded the wrong CSV?

Perhaps a chance koinly is doing some sort of rolling release.  Anyhoo, if any more folks encounter this, please let us know so I know where to look.

Thanks for looking into it.
Yes, that's what i thought too, that i was downloading the wrong csv, but then i did it again and made multiple downloads, I also used different browsers (Edge, Brave, Chrome).
I will try it again now and will let you know, if it works or not.

koinly-20240203-064435.csv has been imported
Now it is working, maybe there were changes in the koinly backend while i was trying it.
Many thanks for your time!


Website v3 (or the Material Redesign)

Hey everyone!
Some of you might have noticed me pushing to the material-web branch lately. And you might be wondering why. Well, here's the short version:

I started redesigning the website to be more approachable, look better and improve UX.

So, I am basing the new design off of Material Design and trying to add a bit of character to it, while keeping some of the personality the website already has. I've already made a lot of progress and will probably push the updated designs next week or the week after.
Here's the list of things happening:

After a lot of thought, asking friends and colleagues and gathering feedback, I think it's safe to say that the landing page has to go. Most people - myself included - see it as an inevitable obstacle in their quick search for snippets. We're gonna swap out the current home page for the array page as the default landing page of the website and turn the current page into multiple other pages that will be linked from the footer area, namely:

About page - Just a few words about the project, the team and stuff
Contribution guidelines
Package - Installation of the npm package and hopefully the VSCode package later down the line

The website is getting a facelift. This means that the code previews are gonna look a bit different and we are going to use a dark color palette for the code areas to make them stand out.
Difficulty for everyone! Every snippet card will have a colored corner with small letters displaying beginner, intermediate and advanced to inform users of the difficulty. Initially, we are going to keep anything tagged as advanced under advanced, the snippets on the beginner page as beginner and everything in-between as intermediate. Eventually we will start curating these properly in the tag_database or another file (we'll see about it).
The daily picks section is going away. Not many people use this and it doesn't feel like it's worth all the custom CSS and JS it uses. We can focus on other things.
Social media buttons are coming. Maybe not on launch, maybe not even very soon afterwards, but they are. And I promise to post more consistently on the Facebook page.
The glossary page is probably coming, too. I think we can all agree it's something worthwhile and we can build it in the same style as the beginner page. Short and simple. Link will probably be in the footer, too.
Sometime in the future, I want to add the glossary term descriptions as tooltips that will show on clicking keywords in any snippet's card. That will take some work and might make the website mighty slow, but I'd like it to be part of the website someday.
Historic members of the team are going to be added in the About page, top contributors that are not part of the team will not be shown yet. I'm trying to figure out a more interesting way to show the list of all contributors from the repository on the website.

That's it. Have a sneak peek at the new home page, which is going to be split into pages and the new snippet listing page layout.
P.S.: My CSS is currently a mess, I'll clean it up once I figure out the whole design.

🖌 🎨 👨🎨

Update
Things are looking good - most of the redesign is already complete, pages are generating nicely on the branch I am working on. There's a little bit left over, along with a couple of additional changes coming:

I need to build the About page from the stuff we had before. It's not gonna be terribly fancy, but it should work.
I need to build the Contribution Guidelines page. Again, not very fancy, not a lot there, but should work.
I need to generate the Archive page, similarly to the rest of the pages.
I need to generate the Glossary page, similarly to the rest of the pages.
I need to generate the Integrations page or (even better) integrate it into the About page.
I decided that the Beginner page, although useful will be retired, at least for a little while. Maybe we'll tackle this again later down the line with a far more interesting design. As it now stands, difficulty corners are added to all questions, so it feels like this page has no purpose anymore. I am thinking about sort of combining it with the glossary tooltips and relaunching it in a little while to gather some statistics about what people think of the idea.
Later down the line (maybe in a week or so), I'll probably also add a cookie disclaimer for Google Analytics.

Estimated launch: This week? Hopefully?

Cool design and very interesting approach in removing pages and content that is not all that relevant. I feel like you should check the snippet list again, pick some more beginner snippets, so that the tag for those is a bit more accurate.


Drop unused image field from Attribute mdoel

Closes #672

Current coverage is 63.63% (diff: 100%)

Merging #676 into master will decrease coverage by <.01%

@@             master       #676   diff @@
==========================================
  Files            91         91
  Lines          4296       4295     -1
  Methods           0          0
  Messages          0          0
  Branches        462        462
==========================================
- Hits           2734       2733     -1
  Misses         1468       1468
  Partials         94         94

Powered by Codecov. Last update a3c9199...19177f9


Trying to use with cielo breez plus

Hey, I have been trying to get this to work with my cielo breez plus (same controller as mrcool) but I cannot get it to connect to the device. I’m curious that since the web address has change that it could be causing an issue.

I'm having a similar problem, the config wants the "public IP the AC resides at", however that IP does not work. I login to Cielo on their website, but don't know the IP that would go here for that.

Hey all,
I took both of @nicholasrobinson's packages, updated them as best I could, and republished them. node-mrcool is the re-implemented library, and homebridge-mrcool is the homebridge plugin. Please feel free to install and let me know how it works (and any bugs you find...!). I only have 3rd gen single zone MrCool units, so I can't guarantee they'll work on the Cielo units, but if you install and let me know, I'd be more than happy to give it a shot. The config public IP you guys are talking about, I believe, is just supposed to be your internet's public IP (it's used as a session identifier in the kinda terrible Cielo API). The API URL did change though, and I've accounted for that in my package.

@isaac-webb So I finally got around to playing with it again and it's still not working but I do appreciate the try. I'm not sure what else could be done to try and get it to work

I dug in a bit more (though it's been a while now), and I found that the API you are accessing from Cielo either doesn't exist anymore or doesn't work with my Cielo Breeze. I'm not sure, I contacted Cielo and they said,

"Thanks for reaching out. Unfortunately we do not offer any API integration at the moment. We have conveyed your suggestion to our tech team. If we release any APIs for third party integration in future, we will surely update you. Currently Cielo Smart controllers are compatible with Amazon Alexa, Google Home Assistant, Samsung SmartThings, Apple Siri shortcuts and IFTTT."

I've been using IFTTT recently, which kinda works. I set up my heating/cooling a switches triggered by IFTTT, however changing temp is sadly not possible.
Would love it if there is a way to get this thing working, though no API on Cielo's end is where I got stuck.

See this comment I just made. Unfortunately, they've never had a public API, so it takes some manual effort to figure out how to play nicely with their "private" APIs... I'll try and make some progress on this soon, I just haven't had the time since I initially published the plugin to get it to work again after it broke.

Closing per https://github.com/nicholasrobinson/homebridge-smartcielo/issues/22


New node: Fill From Stroke

This node can be added after a stroke node in a set of vector data. Upon doing so, it will account for the stroke's shape and add it to the vector data. The stroke will be treated as a solid part of the shape or line segment. Both closed shapes and line segments are supported.
Closes #1092

!build

Welcome, thanks for the contribution!
It looks like this does not currently compile.

Welcome, thanks for the contribution!
It looks like this does not currently compile.

Sorry, had a missing import. Should compile now.

!build

I think I have noticed an issue where even for a closed vector shape the node assumes it's an open shape and uses the wrong vectodata....looking into this.

!build

!build

!build

Can you please rename this to "Solidify Stroke"?
Also, the stroke width doesn't seem to be the same. Is it perhaps being doubled (diameter being treated as radius)?

!build

!build

There's one bug I found, but I'm not sure if it's caused by your code: a layer with a shape and a non-1x1 transform, when you have it selected and switch to the Path tool, changes in size to gain a 1x1 transform. I'm probably just going to merge this anyways and we can work on a followup fix.
@0HyperCube do you know if that's a general bug or if that's because this node is doing (or not doing) something special?


Bugfix for working on Safari

In Safari, the Uint8Array constructor behaves differently than in other browsers.
const a = new Uint8Array(buf, undefined, undefined);
// the result "a" will have zero length no matter buf.byteLength.

Resolved by 5220c0412c71c6cf2801e26f45ad29b59989f195 . Thanks a lot for the report!


modified definition of hemopoiesis

I would like to request a modification of the
definition of the term GO:0030097 'hemopoiesis' that
should not require obsoletion of the term.
The current definition states: "The process of blood
formation, especially the formation of blood cells,
occurring mainly in bone marrow."
The problem is that the site of hematopoiesis is
variable during development in many animals, and in
adult zebrafish, hemopoiesis takes place in the kidney
rather than the bone marrow even though the genes
involved are highly conserved.
PROPOSED NEW DEFINITION: "The process of blood cell
formation.  The site of hemopoiesis is variable during
development, but occurs primarily in bone marrow or
kidney in many adult vertebrates."
-Doug
Reported by: doughowe
Original Ticket: "geneontology/ontology-requests/1502":https://sourceforge.net/p/geneontology/ontology-requests/1502

thanks www.movied.org


repo: Release 1.20.7

Signed-off-by: Ryan Northey<EMAIL_ADDRESS>Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

/docs

@mattklein123 i have set the release date to today so probs would be good to land this and kick out a release

Will do.


Tests for samconfig use with all commands

Issue #, if available:
Description of changes:
Checklist:

[ ] Write Design Document (Do I need to write a design document?)
[x] Write unit tests
[ ] Write/update functional tests
[ ] Write/update integration tests
[ ] make pr passes
[ ] Write documentation

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

since you are writing tests, could you also add version=0.1 to the toml document? when we create it.

I believe this change broke tag values that actually contain spaces (i.e. MyKey=My\ Value)


Revert "Revert "release build broken on Docker 1.6""

Perhaps reverted too quickly.
Reverts GoogleCloudPlatform/kubernetes#8063

Retry #7927


[Bug Report] Lunar Lander reset determinism

Describe the bug
Hi All,
Thanks for the library! I'm currently trying to use the LunarLander-v2 environment with some degree of determinism involved. I'm wanting to be able to run the environment for different seeds, and learn some "weights" for a controller based on the demo controller present in the library. In my setting I often have a "batch" of weights I'd like to try for each environment, so have written a simple loop to do so (as this is fast enough for my needs).
For instance, I might want to run the environment for seeds 42 and 43, with two different sets of weights w1 and w2. My current approach was to just call env.reset(seed=seed) at the start of each run, so call env.reset(seed=42) then run an episode with weights w1 for the controller, then call env.reset(seed=42) and run an episode with weights w2 for the controller, then call env.reset(seed=43) and run an episode with weights w1 etc. My understanding is that if I call env.reset(seed=x) and run the environment with the same controller, I should get the same results? However, there seems to be some state which doesn't get reset in the environment? Most of the time things seem to be OK, but sometimes running the environment with the same seed and weights seems to yield a different result, depending on what seeds it has been run with before. Please find a code example attached.
When running the example I get the following output:
Seed: 42 Reward:<PHONE_NUMBER>996316
Seed: 42 Reward:<PHONE_NUMBER>996316
Seed: 43 Reward: -154.39439542058136
Seed: 43 Reward: -264.19797533115525

Despite both runs of each seed being with the same controller weights, the two runs with the seed set to 43 yield different rewards. Am I misunderstanding the use of env.reset() or is this a bug? Interestingly if I don't run the environment with seed=42 beforehand I get the same result for seed=43 both times (-264.19797533115525), and if I create a new instance of the environment via gym.make() between the two calls to evaluate_demo_heuristic_lander the results are also consistent (-264.19797533115525 for seed=43 on both occasions).
Thanks in advance!
Code example
import gymnasium as gym
import numpy as np
from gymnasium.utils.step_api_compatibility import step_api_compatibility

def heuristic_controller(s, weights):
    angle_targ = s[0] * weights[0] + s[2] * weights[1]
    if angle_targ > weights[2]:
        angle_targ = weights[2]
    if angle_targ < -weights[2]:
        angle_targ = -weights[2]
    hover_targ = weights[3] * np.abs(s[0])

    angle_todo = (angle_targ - s[4]) * weights[4] - (s[5]) * weights[5]
    hover_todo = (hover_targ - s[1]) * weights[6] - (s[3]) * weights[7]

    if s[6] or s[7]:
        angle_todo = weights[8]
        hover_todo = -(s[3]) * weights[9]

    a = 0
    if hover_todo > np.abs(angle_todo) and hover_todo > weights[10]:
        a = 2
    elif angle_todo < -weights[11]:
        a = 3
    elif angle_todo > +weights[11]:
        a = 1
    return a

def evaluate_demo_heuristic_lander(env, weight_configs, seed=None):
    for weight_config in weight_configs:
        total_reward = 0
        steps = 0
        s, info = env.reset(seed=seed)
        while True:
            a = heuristic_controller(s, weight_config)
            s, r, terminated, truncated, info = step_api_compatibility(env.step(a), True)
            total_reward += r

            steps += 1
            if terminated or truncated:
                print(f"Seed: {seed} Reward: {total_reward}")
                break
    return total_reward

if __name__ == "__main__":
    np.set_printoptions(precision=20)
    a = 2.0 * np.array([[0.23369889038420863 , 0.26774014620508657 , 0.2735376051121257  ,
                         0.2997768858021939  , 0.6177483298073877  , 0.7301028167611718  ,
                         0.5806673609739257  , 0.9615451067519928  , 0.07313039905288293 ,
                         0.3626741110509404  , 0.07945107270237381 , 0.009656828642440243]])
    a = np.vstack([a, a])
    env = gym.make("LunarLander-v2")
    evaluate_demo_heuristic_lander(env, a, seed=42)
    evaluate_demo_heuristic_lander(env, a, seed=43)

System info

Gymnasium installed using pip.
Gymnasium Version: 0.29.1
OS: MacOS Ventura 13.5.2
Python 3.10.10

Additional context
No response
Checklist

[X] I have checked that there is no similar issue in the repo

I'm not 100% sure, but I think there was a similar issue either here or back in Gym. The conclusion was probably that the underlying issue is some Box2D black magic and there isn't much we can do until we get rid of it and replace it with literally anything else (which iirc is somewhere on the roadmap, but might not be anytime soon)

Let me update my new finds here:
I've added some more debugging info in the test codes as the following:
def evaluate_demo_heuristic_lander(env, weight_configs, seed=None):
    obs_list = []
    for weight_config in weight_configs:
        total_reward = 0
        steps = 0
        env.close()
        s, info = env.reset(seed=seed)
        obs_sub_list = []
        obs_sub_list.append(s)
        obs_list.append(obs_sub_list)
        while True:
            a = heuristic_controller(s, weight_config)
            #s, r, terminated, truncated, info = step_api_compatibility(env.step(a), True)
            s, r, terminated, truncated, info  = env.step(a)
            obs_sub_list.append((s,r))
            total_reward += r
            #
            steps += 1
            if terminated or truncated:
                print(f"Seed: {seed} Reward: {total_reward}, steps:{steps}")
                break
    return total_reward, obs_list

np.set_printoptions(precision=20)
a = 2.0 * np.array([[0.23369889038420863 , 0.26774014620508657 , 0.2735376051121257  ,
                     0.2997768858021939  , 0.6177483298073877  , 0.7301028167611718  ,
                     0.5806673609739257  , 0.9615451067519928  , 0.07313039905288293 ,
                     0.3626741110509404  , 0.07945107270237381 , 0.009656828642440243]])
a = np.vstack([a, a])
env = gym.make("LunarLander-v2")
total_reward_42, obs_list_42 = evaluate_demo_heuristic_lander(env, a, seed=42)
total_reward_43, obs_list_43 = evaluate_demo_heuristic_lander(env, a, seed=43)

I found that for seed=43, we've executed episodes two times, the first episode steps count is 353, but the second is 346, and then I've checked in which step they start to be different as the following codes:
for i in range(len(obs_list_43[1])):
    if not np.all(np.equal(obs_list_43[1][i][0],obs_list_43[0][i][0])):
        print(f"i:{i}")
        break

It report as 235, so :
>>> obs_list_43[0][234]
(array([-8.6891845e-02, -1.0146881e-03, -1.5059064e-01, -6.3774064e-07,
        1.5923785e-03,  2.8275241e-07,  1.0000000e+00,  1.0000000e+00],
      dtype=float32), -0.6966045942906287)
>>> obs_list_43[1][234]
(array([-8.6891845e-02, -1.0146881e-03, -1.5059064e-01, -6.3774064e-07,
        1.5923785e-03,  2.8275241e-07,  1.0000000e+00,  1.0000000e+00],
      dtype=float32), -0.6966045942906287)
>>> obs_list_43[1][235]
(array([-8.8439748e-02, -1.0163331e-03, -1.5478876e-01, -7.2242561e-05,
        1.5940322e-03,  3.2485405e-05,  1.0000000e+00,  1.0000000e+00],
      dtype=float32), -0.6047604628131988)
>>> obs_list_43[0][235]
(array([-8.8439748e-02, -1.0163331e-03, -1.5478876e-01, -7.2242561e-05,
        1.5940322e-03,  3.2485405e-05,  0.0000000e+00,  1.0000000e+00],
      dtype=float32), -10.604760462813198)

So our question is: when in step 234, the 2 observations are exactly same, and with the exactly same action, why we get the different obs? and the two obs are exactly same except the 7th value, one is 1.0, the other is 0.0.
We need more debugging work on this problem.

According to the result my checking on the source codes and the values in obs_list_43, it seems relates to the lander's legs.ground_contact, because the following codes:
        state = [
            (pos.x - VIEWPORT_W / SCALE / 2) / (VIEWPORT_W / SCALE / 2),
            (pos.y - (self.helipad_y + LEG_DOWN / SCALE)) / (VIEWPORT_H / SCALE / 2),
            vel.x * (VIEWPORT_W / SCALE / 2) / FPS,
            vel.y * (VIEWPORT_H / SCALE / 2) / FPS,
            self.lander.angle,
            20.0 * self.lander.angularVelocity / FPS,
            1.0 if self.legs[0].ground_contact else 0.0,
            1.0 if self.legs[1].ground_contact else 0.0,
        ]

It's very possible that the self.legs[0].ground_contact aare in different siutations(one is Ture, the other is False) in our tests, but why? We don't know yet. As @RedTachyon said, the contactListener is implemented in Box2D, so currently I've not setup its debugging env yet.

Hi, new updates on this problem:
I've confired the root cause relates to the LunarLander.world reset. In current LunarLander codes, we init it in init() and reset(), but in the reset() we reset self.world instead of create a totally new self.world, but it's possible that some states values we have clean enough through codes in _destroy() and reset(), which causes this bug.
I've added "self.world = Box2D.b2World(gravity=(0, self.gravity))" in the reset(), this bug disappears. The code patch is here:
https://github.com/Farama-Foundation/Gymnasium/commit/32d5ebccfbe2f82c2b2aead92a87f01daa9e8242

@clockzhong Wow, thanks for finding this.
This seems like a serious bug that will seriously affect performance.
As making this change will require a version number change, i.e., LunarLander-v3, then we need to investigate the performance difference.
@clockzhong Could you do this? It would require using SB3, CleanRL, etc with an algorithm, PPO, DQN, etc and tracking the performance for the two environment versions with graphs of the performance. See https://github.com/openai/gym/pull/2762 for example

@clockzhong Wow, thanks for finding this.
This seems like a serious bug that will seriously affect performance. As making this change will require a version number change, i.e., LunarLander-v3, then we need to investigate the performance difference. @clockzhong Could you do this? It would require using SB3, CleanRL, etc with an algorithm, PPO, DQN, etc and tracking the performance for the two environment versions with graphs of the performance. See openai/gym#2762 for example

Yes, I'm setting up SB3 environment here, I'll make some tests to check the difference on those RL algorithms' performance on this bug fix. I guess this bug's fix will not influence those RL algorithms' performence largely, because those agents(PPO/DQN) has no idea on which env is right or wrong. Anyway, we need get final conclusion after completing the A/B test.

To confirm, could you just train an agent (3 repeat) for the original v2 and then a v3 environment and plot the training results for both and confirm the results

@clockzhong Hey, any progress on this?

@Kallinteris-Andreas We should add this for v3 though


Empty Fragments (<></>) no longer work

@react.component
let make = (~title: string) => {

        {switch title {
        | "" => <></>
        | myTitle =>
{React.string(title)}

        }}

}

After updating to rescript 11 and rescript react 11, empty fragments no longer work even if they have something inside them (like a react string). Replacing it with React.Fragment works.
It gives a slightly cryptic error message: Empty record literal {} should be type annotated or used in a record context.
Is this an issue with the JSX parser or did I miss something in the migration notes?

What's ReScript-React 11?
The minimum required version for ReScript 11 is ReScript-React 0.12.
https://rescript-lang.org/docs/manual/latest/migrate-to-v11#compiler-libraries
Your code compiles fine in the playground which uses the most current versions.

It turns out I was on using this version (https://github.com/rescript-lang/rescript-react/releases/tag/v0.11.0). My mistake! After updating to version 12 fragments work as expected. Thanks for the help!


Update BUILD

Thank you for your pull request. Before we can look at your contribution, we need to ensure all contributors are covered by a Contributor License Agreement.
After the following items are addressed, please respond with a new comment here, and the automated system will re-verify.

User @Siddhant2209 isn't covered by a CLA. They will need to complete the form at https://identity.linuxfoundation.org/projects/cncf

Regards,
CLA GitHub bot


bug: Text not rendering on screen, it shows after tap

Bug Report
Ionic version:

[x] 4.x
Current behavior:

I have session timeout functionality in my app so after x minute or second if the app is idle, the user will be logged out from the app and redirected to the login page.
When the session is expired while the app is in the background, then all text/labels are showing blank on-screen until the user tap on the screen.
This is how it looks

This is after a tap on the screen

Expected behavior:

It should render all the text correctly without tap
Steps to reproduce:

Open the app and click the login button
Press the device home button to put the application in background mode.
Open the app from background after 20-30 second
You will see the text is not rendering behind the alert, also after a click on login when you come to the home page, it will show blank initially

Related code:

Here git repo with minimum code to reproduce the issue.
Other information:

I am testing this on a physical device with android version 7.0
Ionic info:

Ionic:

   Ionic CLI                     : 5.0.3
   Ionic Framework               : @ionic/angular 4.6.0
   @angular-devkit/build-angular : 0.13.9
   @angular-devkit/schematics    : 7.3.9
   @angular/cli                  : 7.3.9
   @ionic/angular-toolkit        : 1.5.1

Cordova:

   Cordova CLI       : 8.0.0
   Cordova Platforms : android 7.0.0
   Cordova Plugins   : cordova-plugin-ionic-keyboard 2.1.3, cordova-plugin-ionic-webview 4.1.1, (and 18 other plugins)

Utility:

   cordova-res : 0.4.0
   native-run  : 0.2.6

System:

   Android SDK Tools : 26.1.1 (/Users/divyesh/Library/Android/sdk)
   ios-deploy        : 1.9.2
   NodeJS            : v11.4.0 (/usr/local/bin/node)
   npm               : 6.4.1
   OS                : macOS Mojave
   Xcode             : Xcode 10.2.1 Build version 10E1001

Does no one have a solution for this?

Hi there,
Is this still an issue on the latest version of Ionic Framework?

No, with new version its resolved.


Edit item bitstreams

This PR adds an implementation for the bitstreams tab on an item's edit page.
UI
Similar to DSpace 6, the page contains a table listing all bitstreams separated by bundle.
You'll notice the columns are about the same, except it contains an "Actions" column at the end instead of the "View" and "Order" columns.
This "Actions" column contains buttons for each bitstream:

Download - this replaces the "view" column and downloads or displays the bitstream
Edit - Opens the bitstream's edit page
Remove - Marks the bitstream for removal
Undo changes - Reverts any changes made to the bitstream (currently the only change it can revert is the bitstream being marked for removal)

The bundle row also has a button in the action column for uploading a new bitstream to that bundle. This is the same as clicking the upload button on the top-left of the page, but it'll automatically select the relevant bundle in the dropdown.
Instead of the order column, the user is now able to drag bitstreams around within a bundle, using a handle in the front of the bitstream's table tow.
Hovering over a bitstream's row will make the handle appear. Clicking and dragging this handle will move the bitstream to whatever position you drop it on.
If the list of bitstreams within a bundle contains pagination (more than 10 bitstreams), it's possible to drop a bitstream on top of a page number, which will move that bitstream to the top of that page.
All of these changes are kept locally until the user clicks "Save".
Upon clicking "Save", requests (delete and patch) are sent to the REST API, notifications will be displayed and the table is refreshed.
Technical details
Table component structure
The main component containing the table and submit implementation is ItemBitstreamsComponent. This component renders a table header and a ItemEditBitstreamBundleComponent for each of the bundles within the item. This component renders the bundle header (name and upload button) and a PaginatedDragAndDropBitstreamListComponent.
In turn, this component renders the draggable bitstream rows within a pagination component. The contents of the draggable bitstream row are defined in ItemEditBitstreamComponent.
Paginated drag-and-drop components
The PaginatedDragAndDropBitstreamListComponent extends from a new abstract component: AbstractPaginatedDragAndDropListComponent.
This is an abstract component containing general methods and logic to be able to drag and drop objects within a paginated list. In this case Bitstreams, but the implementation could be used for any type of DSpaceObject.

@Atmire-Kristof : Could you please rebase this PR.  It's got some minor code conflicts.  Also, Travis should now approve it (as the prior failure was not a fault of the PR itself & I've updated Travis settings so that this should now succeed).

@Atmire-Kristof I've tested this functionality and noticed:

I I try to upload a file to a new bundle (so clicking the main upload button, typing a new bundle name, and uploading a file), I get an exception because a POST to /placeholder is attempted
Similar to Tim's error, uploading a large file fails, but this failure occurs in REST, so not a problem with this PR

@Atmire-Kristof I'm still encountering problems when uploading a file to a new bundle, but this time a different error
When uploading a bitstream to an existing bundle, it works fine
When uploading a bitstream to a new bundle, I get CORS errors:

Access to XMLHttpRequest at 'https://dspace7-demo.atmire.com/server/api/core/bundles/9b8fc0a1-98da-4ba7-9d69-d607bc088f0c/bitstreams' from origin 'http://localhost:3000' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.

When ignoring the CORS headers, the upload succeeds, but the UI doesn't update after completing the update

I've done some further testing on this PR with our internal REST API containing the necessary changes to CORS, but I've discovered another issue. Even though the upload succeeds and the bitstream is now added to the new bundle, the UI still doesn't display any progress and doesn't redirect the user to the next page.
For some reason the uploader's onCompleteItem event is not triggered after the upload. I'll have to fix this issue first, before we can merge this PR.

Merging as this is now at +2. I've logged the bug that @benbosman noted above as a separate issue: https://github.com/DSpace/dspace-angular/issues/641

@Atmire-Kristof : Apologies, I seem to have not seen your comment here before pressing merge on the PR.  If you could create a followup PR to fix the issue you noted, we can prioritize that for quick review. Thanks!


[SUPPORT] insert into supports writing by partition without specifying a partition field

Currently only insert into table xxx partition(a) can be used
When expecting insert into table xxx, support automatic partition routing function

Thank you @duxia , I have created a jira to track it HUDI-4404


localParticipant which was returned by useLocalParticipant does not have correct connection state

Select which package(s) are affected
@livekit/components-react
Describe the bug
What I'm expecting
The RTCEngine.isClosed state which is held in localParticipant's instance returned by useLocalParticipant is correctly synchronised with the room state.
What happens instead
The RTCEngine.isClosed state which is held in localParticipant's instance returned by useLocalParticipant is not correctly synchronised with the room state.
We can avoid this issue by getting localParticipant from room which was returned by useRoomContext. However, I believe that is not expected behavior.
Reproduction
This is what it looks like if you extract the relevant section from my code.
const room = useLiveKitRoom(/* some options*/);

return <RoomContext.Provider>{children}</RoomContext.Provider>

// inside of the RoomContext
const { localParticipant } = useLocalParticipant();
const [stream, setStream] = useState<MediaStream | false>(false);

useEffect(() => {
  if (typeof stream === 'boolean') {
    localParticipant.setScreenShareEnabled(false);
    return;
  }
  const [track] = stream.getVideoTracks();
  // debug: value of isClosed is true even if the localParticipant was connected to the room.
  console.log('isClosed', localParticipant.engine.isClosed);
  // track publishing was failed by error "cannot publish track when not connected"
  localParticipant.publishTrack(track, { source: Track.Source.ScreenShare });
}, [stream])

Logs
No response
System Info
Not needed

Severity
serious, but I can work around it
Additional Information
No response

you're using internal state when accessing engine on the local participant.
use useConnectionState for figuring out what connection state a room is currently in

yeah, you should only initiate track publishing once the room is already connected!
You can also use the  component (or inspect the useTrackToggle hook to see how we do this internally)


[WFCORE-1722] add tests for ignore-unused-configuration in conjunction…

… with --backup
https://issues.jboss.org/browse/WFCORE-1722

Core - Full Integration Build 3250 outcome was FAILURE using a merge of 16c643ab9e02e4fd2208a7d8d71c3f99003ad76b
Summary: Execution timeout (new); tests failed: 1 (1 new), passed: 3442, ignored: 196 Build time: 01:45:24
Failed tests
org.jboss.as.test.clustering.cluster.web.ConcurrentFineWebFailoverTestCase(SYNC-tcp).testGracefulSimpleFailover: java.lang.AssertionError: Session failed to replicate after container 1 was shutdown. expected:<7> but was:<6>
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testFailover(AbstractWebFailoverTestCase.java:211)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testGracefulSimpleFailover(AbstractWebFailoverTestCase.java:79)
------- Stdout: -------
05:08:39,473 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
05:08:39,473 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
05:08:39,473 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
 [0m05:08:39,483 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /opt/buildAgent/work/29472398f1ae6497/full/testsuite/integration/clustering/target/wildfly-SYNC-tcp-0/standalone/data/content/c4/11b4d95c8cbdad03b92ebb70c6f8bc54c32356/content
 [0m [0m05:08:39,486 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "fine-concurrent-distributable.war" (runtime-name: "fine-concurrent-distributable.war")
 [0m [33m05:08:39,502 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.fine-concurrent-distributable.war" is using a private module ("org.jboss.as.clustering.common:main") which may be changed or removed in future versions without notice.
 [0m [33m05:08:39,502 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.fine-concurrent-distributable.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
 [0m [33m05:08:39,502 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.fine-concurrent-distributable.war" is using a private module ("org.infinispan:main") which may be changed or removed in future versions without notice.
 [0m [0m05:08:39,506 INFO  [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment fine-concurrent-distributable.war
 [0m [0m05:08:39,510 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "fine-concurrent-distributable.war"' are as follows:

	java:global/fine-concurrent-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:app/fine-concurrent-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:module/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:jboss/exported/fine-concurrent-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:global/fine-concurrent-distributable/TopologyChangeListenerBean
	java:app/fine-concurrent-distributable/TopologyChangeListenerBean
	java:module/TopologyChangeListenerBean

 [0m [0m05:08:39,537 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 21) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m05:08:39,537 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 21) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m05:08:39,550 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 81) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m05:08:39,550 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 81) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m05:08:39,551 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 82) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m05:08:39,551 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 82) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m05:08:39,551 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 21) WFLYCLINF0002: Started client-mappings cache from ejb container
 [0m [0m05:08:39,594 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 82) WFLYCLINF0002: Started fine-concurrent-distributable.war cache from web container
 [0m [0m05:08:39,594 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 81) WFLYCLINF0002: Started routing cache from web container
 [0m [0m05:08:39,740 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 81) WFLYUT0021: Registered web context: /fine-concurrent-distributable
 [0m [0m05:08:39,748 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "fine-concurrent-distributable.war" (runtime-name : "fine-concurrent-distributable.war")
 [0m05:08:39,756 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
 [0m05:08:39,768 INFO  [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0001: Content added at location /opt/buildAgent/work/29472398f1ae6497/full/testsuite/integration/clustering/target/wildfly-SYNC-tcp-1/standalone/data/content/c4/11b4d95c8cbdad03b92ebb70c6f8bc54c32356/content
 [0m [0m05:08:39,771 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "fine-concurrent-distributable.war" (runtime-name: "fine-concurrent-distributable.war")
 [0m [33m05:08:39,789 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.fine-concurrent-distributable.war" is using a private module ("org.jboss.as.clustering.common:main") which may be changed or removed in future versions without notice.
 [0m [33m05:08:39,790 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.fine-concurrent-distributable.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
 [0m [33m05:08:39,790 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.fine-concurrent-distributable.war" is using a private module ("org.infinispan:main") which may be changed or removed in future versions without notice.
 [0m [0m05:08:39,797 INFO  [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment fine-concurrent-distributable.war
 [0m [0m05:08:39,800 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "fine-concurrent-distributable.war"' are as follows:

	java:global/fine-concurrent-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:app/fine-concurrent-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:module/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:jboss/exported/fine-concurrent-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:global/fine-concurrent-distributable/TopologyChangeListenerBean
	java:app/fine-concurrent-distributable/TopologyChangeListenerBean
	java:module/TopologyChangeListenerBean

Full integration - Windows Build 1696 outcome was FAILURE using a merge of 16c643ab9e02e4fd2208a7d8d71c3f99003ad76b
Summary: Execution timeout (new); tests passed: 3426, ignored: 197 Build time: 01:45:42

Linux Build 4274 outcome was FAILURE using a merge of 16c643ab9e02e4fd2208a7d8d71c3f99003ad76b
Summary: Tests failed: 2 (2 new), passed: 3778, ignored: 56 Build time: 00:49:22
Failed tests
org.wildfly.core.test.standalone.mgmt.PreparedResponseTestCase.reloadServer: java.lang.RuntimeException: java.io.IOException: java.util.concurrent.CancellationException: Operation was cancelled
	at org.jboss.threads.AsyncFutureTask.operationCancelled(AsyncFutureTask.java:70)
	at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:267)
	at org.jboss.as.controller.client.impl.AbstractDelegatingAsyncFuture.get(AbstractDelegatingAsyncFuture.java:57)
	at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147)
	at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75)
	at org.wildfly.core.testrunner.ManagementClient.executeForResult(ManagementClient.java:234)
	at org.wildfly.core.test.standalone.mgmt.PreparedResponseTestCase.reloadServer(PreparedResponseTestCase.java:102)
------- Stdout: -------
07:01:29,900 WARN  [org.jboss.as.protocol.connection] (Remoting "management-client" task-5) WFLYPRT0018: No such request (1) associated with channel Channel ID 81339bbb (outbound) of Remoting connection 000a3173 to /0:0:0:0:0:0:0:1:9990 of endpoint "management-client" <cdce02>

org.wildfly.core.test.standalone.mgmt.PreparedResponseTestCase: org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper$ServerDeploymentException: java.lang.RuntimeException: java.io.IOException: WFLYPRT0054: Channel closed
	at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:166)
	at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:143)
	at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:64)
	at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:139)
	at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:114)
	at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263)
	at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168)
	at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeAsync(AbstractModelControllerClient.java:111)
	at org.jboss.as.controller.client.helpers.DelegatingModelControllerClient.executeAsync(DelegatingModelControllerClient.java:93)
	at org.jboss.as.controller.client.helpers.standalone.impl.ModelControllerClientServerDeploymentManager.executeOperation(ModelControllerClientServerDeploymentManager.java:50)
	at org.jboss.as.controller.client.helpers.standalone.impl.AbstractServerDeploymentManager.execute(AbstractServerDeploymentManager.java:79)
	at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.undeploy(ServerDeploymentHelper.java:106)
	at org.wildfly.core.test.standalone.mgmt.PreparedResponseTestCase.undeploy(PreparedResponseTestCase.java:95)
	at org.wildfly.core.test.standalone.mgmt.PreparedResponseTestCase.stopContainer(PreparedResponseTestCase.java:79)

Core - Full Integration Build 3251 outcome was FAILURE using a merge of 16c643ab9e02e4fd2208a7d8d71c3f99003ad76b
Summary: Tests failed: 2 (1 new), passed: 3441, ignored: 196 Build time: 01:14:33
Failed tests
org.jboss.as.test.clustering.cluster.web.ConcurrentCoarseWebFailoverTestCase(SYNC-tcp).testGracefulSimpleFailover: java.lang.AssertionError: Session failed to replicate after container 1 was shutdown. expected:<7> but was:<6>
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testFailover(AbstractWebFailoverTestCase.java:211)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testGracefulSimpleFailover(AbstractWebFailoverTestCase.java:79)
------- Stdout: -------
07:06:16,410 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
07:06:16,410 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
07:06:16,410 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
 [0m07:06:16,459 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location /opt/buildAgent/work/29472398f1ae6497/full/testsuite/integration/clustering/target/wildfly-SYNC-tcp-0/standalone/data/content/0c/9e8016a8a1bc8a54511fb59e4d90db4c18092c/content
 [0m [0m07:06:16,463 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "coarse-concurrent-distributable.war" (runtime-name: "coarse-concurrent-distributable.war")
 [0m [33m07:06:16,490 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) WFLYSRV0018: Deployment "deployment.coarse-concurrent-distributable.war" is using a private module ("org.jboss.as.clustering.common:main") which may be changed or removed in future versions without notice.
 [0m [33m07:06:16,490 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) WFLYSRV0018: Deployment "deployment.coarse-concurrent-distributable.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
 [0m [33m07:06:16,490 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) WFLYSRV0018: Deployment "deployment.coarse-concurrent-distributable.war" is using a private module ("org.infinispan:main") which may be changed or removed in future versions without notice.
 [0m [0m07:06:16,496 INFO  [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0003: Processing weld deployment coarse-concurrent-distributable.war
 [0m [0m07:06:16,500 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-7) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "coarse-concurrent-distributable.war"' are as follows:

	java:global/coarse-concurrent-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:app/coarse-concurrent-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:module/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:jboss/exported/coarse-concurrent-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:global/coarse-concurrent-distributable/TopologyChangeListenerBean
	java:app/coarse-concurrent-distributable/TopologyChangeListenerBean
	java:module/TopologyChangeListenerBean

 [0m [0m07:06:16,545 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 19) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m07:06:16,545 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 19) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m07:06:16,547 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 22) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m07:06:16,548 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 22) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m07:06:16,548 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 14) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m07:06:16,549 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 14) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m07:06:16,553 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 19) WFLYCLINF0002: Started client-mappings cache from ejb container
 [0m [0m07:06:16,561 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 14) WFLYCLINF0002: Started routing cache from web container
 [0m [0m07:06:16,566 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 19) WFLYCLINF0002: Started coarse-concurrent-distributable.war cache from web container
 [0m [0m07:06:16,759 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 19) WFLYUT0021: Registered web context: /coarse-concurrent-distributable
 [0m [0m07:06:16,769 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "coarse-concurrent-distributable.war" (runtime-name : "coarse-concurrent-distributable.war")
 [0m07:06:16,779 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
 [0m07:06:16,793 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /opt/buildAgent/work/29472398f1ae6497/full/testsuite/integration/clustering/target/wildfly-SYNC-tcp-1/standalone/data/content/0c/9e8016a8a1bc8a54511fb59e4d90db4c18092c/content
 [0m [0m07:06:16,797 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "coarse-concurrent-distributable.war" (runtime-name: "coarse-concurrent-distributable.war")
 [0m [33m07:06:16,829 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.coarse-concurrent-distributable.war" is using a private module ("org.jboss.as.clustering.common:main") which may be changed or removed in future versions without notice.
 [0m [33m07:06:16,829 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.coarse-concurrent-distributable.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
 [0m [33m07:06:16,829 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.coarse-concurrent-distributable.war" is using a private module ("org.infinispan:main") which may be changed or removed in future versions without notice.
 [0m [0m07:06:16,834 INFO  [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Processing weld deployment coarse-concurrent-distributable.war
 [0m [0m07:06:16,837 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "coarse-concurrent-distributable.war"' are as follows:

	java:global/coarse-concurrent-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:app/coarse-concurrent-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:module/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:jboss/exported/coarse-concurrent-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:global/coarse-concurrent-distributable/TopologyChangeListenerBean
	java:app/coarse-concurrent-distributable/TopologyChangeListenerBean
	java:module/TopologyChangeListenerBean

org.jboss.as.test.clustering.cluster.web.ConcurrentFineWebFailoverTestCase(SYNC-tcp).testGracefulSimpleFailover: java.lang.AssertionError: Session failed to replicate after container 1 was shutdown. expected:<7> but was:<6>
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testFailover(AbstractWebFailoverTestCase.java:211)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testGracefulSimpleFailover(AbstractWebFailoverTestCase.java:79)
------- Stdout: -------
07:04:00,270 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
07:04:00,270 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
07:04:00,270 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
 [0m07:04:00,290 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location /opt/buildAgent/work/29472398f1ae6497/full/testsuite/integration/clustering/target/wildfly-SYNC-tcp-0/standalone/data/content/7e/6d68b76ccbfe942aa1fc463e45a18acee5748f/content
 [0m [0m07:04:00,294 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "fine-concurrent-distributable.war" (runtime-name: "fine-concurrent-distributable.war")
 [0m [33m07:04:00,310 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.fine-concurrent-distributable.war" is using a private module ("org.jboss.as.clustering.common:main") which may be changed or removed in future versions without notice.
 [0m [33m07:04:00,311 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.fine-concurrent-distributable.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
 [0m [33m07:04:00,311 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.fine-concurrent-distributable.war" is using a private module ("org.infinispan:main") which may be changed or removed in future versions without notice.
 [0m [0m07:04:00,318 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment fine-concurrent-distributable.war
 [0m [0m07:04:00,325 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "fine-concurrent-distributable.war"' are as follows:

	java:global/fine-concurrent-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:app/fine-concurrent-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:module/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:jboss/exported/fine-concurrent-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:global/fine-concurrent-distributable/TopologyChangeListenerBean
	java:app/fine-concurrent-distributable/TopologyChangeListenerBean
	java:module/TopologyChangeListenerBean

 [0m [0m07:04:00,429 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 80) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m07:04:00,430 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 80) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m07:04:00,445 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 32) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m07:04:00,446 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 32) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m07:04:00,446 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 18) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m07:04:00,446 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 18) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m07:04:00,456 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 80) WFLYCLINF0002: Started client-mappings cache from ejb container
 [0m [0m07:04:00,458 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 32) WFLYCLINF0002: Started fine-concurrent-distributable.war cache from web container
 [0m [0m07:04:00,461 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 18) WFLYCLINF0002: Started routing cache from web container
 [0m [0m07:04:00,765 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 80) WFLYUT0021: Registered web context: /fine-concurrent-distributable
 [0m [0m07:04:00,780 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "fine-concurrent-distributable.war" (runtime-name : "fine-concurrent-distributable.war")
 [0m07:04:00,789 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
 [0m07:04:00,809 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /opt/buildAgent/work/29472398f1ae6497/full/testsuite/integration/clustering/target/wildfly-SYNC-tcp-1/standalone/data/content/7e/6d68b76ccbfe942aa1fc463e45a18acee5748f/content
 [0m [0m07:04:00,814 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "fine-concurrent-distributable.war" (runtime-name: "fine-concurrent-distributable.war")
 [0m [33m07:04:00,838 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment "deployment.fine-concurrent-distributable.war" is using a private module ("org.jboss.as.clustering.common:main") which may be changed or removed in future versions without notice.
 [0m [33m07:04:00,839 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment "deployment.fine-concurrent-distributable.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
 [0m [33m07:04:00,839 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment "deployment.fine-concurrent-distributable.war" is using a private module ("org.infinispan:main") which may be changed or removed in future versions without notice.
 [0m [0m07:04:00,844 INFO  [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment fine-concurrent-distributable.war
 [0m [0m07:04:00,851 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "fine-concurrent-distributable.war"' are as follows:

	java:global/fine-concurrent-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:app/fine-concurrent-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:module/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:jboss/exported/fine-concurrent-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:global/fine-concurrent-distributable/TopologyChangeListenerBean
	java:app/fine-concurrent-distributable/TopologyChangeListenerBean
	java:module/TopologyChangeListenerBean

retest this please

Core - Full Integration Build 3257 outcome was FAILURE using a merge of 16c643ab9e02e4fd2208a7d8d71c3f99003ad76b
Summary: Tests failed: 1 (1 new), passed: 3437, ignored: 194 Build time: 01:00:40
Failed tests
org.jboss.as.test.xts.annotation.compensationScoped.CompensationScopedTestCase.shouldSeeDifferentValuesInDifferentTransactions: com.arjuna.mw.wsas.exceptions.WrongStateException: ARJUNA041018: Cannot enlist child activity with parent as parent's status is: Status.Completed
	at com.arjuna.mwlabs.wsas.activity.ActivityImple.addChild(ActivityImple.java:583)
	at com.arjuna.mwlabs.wsas.activity.ActivityImple.start(ActivityImple.java:160)
	at com.arjuna.mwlabs.wsas.UserActivityImple.start(UserActivityImple.java:136)
	at com.arjuna.mwlabs.wsas.UserActivityImple.start(UserActivityImple.java:99)
	at com.arjuna.mwlabs.wscf.model.sagas.arjunacore.CoordinatorServiceImple.begin(CoordinatorServiceImple.java:108)
	at org.jboss.narayana.compensations.impl.local.LocalBAController.beginBusinessActivity(LocalBAController.java:28)
	at org.jboss.as.test.xts.annotation.compensationScoped.CompensationScopedTestCase.shouldSeeDifferentValuesInDifferentTransactions(CompensationScopedTestCase.java:76)
------- Stdout: -------
 [0m00:27:57,435 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 93) WFLYUT0022: Unregistered web context: /transactional-test
 [0m [0m00:27:57,438 INFO  [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint."transactional-test.war".TransactionalServiceImpl
 [0m [0m00:27:57,454 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 94) WFLYCLINF0003: Stopped client-mappings cache from ejb container
 [0m [0m00:27:57,465 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment transactional-test.war (runtime-name: transactional-test.war) in 31ms
 [0m [0m00:27:57,472 INFO  [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0002: Content removed from location /opt/buildAgent/work/29472398f1ae6497/full/testsuite/integration/xts/target/jbossas/standalone/data/content/48/fd0e2ffe16dfdf06eb3132df59bdbabef1f374/content
 [0m [0m00:27:57,472 INFO  [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0009: Undeployed "transactional-test.war" (runtime-name: "transactional-test.war")
 [0m [0m00:27:58,181 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location /opt/buildAgent/work/29472398f1ae6497/full/testsuite/integration/xts/target/jbossas/standalone/data/content/3a/9ffbef4c277187de6fdb61fb266f0fb46264dd/content
 [0m [0m00:27:58,185 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war")
 [0m [0m00:27:58,333 INFO  [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment test.war
 [0m [0m00:27:58,558 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 94) WFLYUT0021: Registered web context: /test
 [0m [0m00:27:58,566 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "test.war" (runtime-name : "test.war")
 [0m

retest this please

Windows Build 3631 outcome was FAILURE using a merge of 16c643ab9e02e4fd2208a7d8d71c3f99003ad76b
Summary: Tests failed: 1 (1 new), passed: 3778, ignored: 56 Build time: 00:50:02
Failed tests
org.jboss.as.test.integration.management.cli.CliAliasTestCase.testAliasPersistence: java.nio.file.NoSuchFileException: C:\BuildAgent\work\4c983eca15c0017f\testsuite\standalone\target\junit4713632736580878956\.aesh_aliases
	at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:79)
	at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97)
	at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102)
	at sun.nio.fs.WindowsFileSystemProvider.newByteChannel(WindowsFileSystemProvider.java:230)
	at java.nio.file.Files.newByteChannel(Files.java:361)
	at java.nio.file.Files.newByteChannel(Files.java:407)
	at java.nio.file.spi.FileSystemProvider.newInputStream(FileSystemProvider.java:384)
	at java.nio.file.Files.newInputStream(Files.java:152)
	at java.nio.file.Files.newBufferedReader(Files.java:2784)
	at java.nio.file.Files.readAllLines(Files.java:3202)
	at org.jboss.as.test.integration.management.cli.CliAliasTestCase.testAliasPersistence(CliAliasTestCase.java:187)

Core - Full Integration Build 3264 outcome was FAILURE using a merge of 16c643ab9e02e4fd2208a7d8d71c3f99003ad76b
Summary: Execution timeout (new); unexpected error: java.lang.RuntimeException: Failed to create context for build runner: Error creating bean with name 'jetbrains.buildServer.agent.impl.buildStages.startStages.steps.StepExecutor#0' defined in URL [jar:file:/... Build time: 01:25:34

retest this please
@luck3y please approve

Looks good to me.


Add typescript type declarations

This change is

Oops, did I jump the gun on the review?  Sorry.

nodefire.d.ts, line 185 at r1 (raw file):
Previously, pkaminski (Piotr Kaminski) wrote…
Is it possible to declare this as Promise<void> as some such, to assert that no useful value is returned?  Or just declare the method as async ... : void?
Also, options here and below are {timeout: number?}.

In the past you've preferred {timeout?: number} to {timeout: number?}.  The former means either {timeout: number} or {} while the latter means {timeout: number | null}.  Do we want the latter here?

nodefire.d.ts, line 185 at r1 (raw file):
Previously, dhbradshaw (Douglas H. Bradshaw) wrote…
In the past you've preferred {timeout?: number} to {timeout: number?}.  The former means either {timeout: number} or {} while the latter means {timeout: number | null}.  Do we want the latter here?

Oops, my TypeScript-fu is weak.  I meant the former, and failed to even realize that they're different.  (Though really, {timeout?: number?} would be most accurate I guess...)

I'm closing this since we converted the js to typescript instead in pull request https://github.com/Reviewable/nodefire/pull/21


Budgeting

Hi,
Firstly, thanks for the awesome service. It was really easy to get set up.
I wanted to ask if there was a budgeting feature. Right now in production I can't seem to set a limit for my monthly spend.
I would like to do this even if it stops users from signing up.
Thanks

Hi there, you should reach out to our support team over at<EMAIL_ADDRESS>


feat: add get file status rest api for indexer gateway

This change is

merged in this (PR)[https://github.com/0glabs/0g-storage-client/pull/72]


chore: remove stalebot config

Description of changes

Removes stalebot config to prevent it from running. It will later be disabled/removed from the repo integrations, and a similar solution will be added in the future.
Issue #, if available

n/a
Description of how you validated changes
Checklist

[ ] PR description included
[ ] yarn test passes
[ ] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #7768 (0630c3d) into master (00d6676) will increase coverage by 0.87%.
The diff coverage is 58.77%.

@@            Coverage Diff             @@
##           master    #7768      +/-   ##
==========================================
+ Coverage   51.79%   52.66%   +0.87%
==========================================
  Files         547      549       +2
  Lines       27626    27680      +54
  Branches     5342     5357      +15
==========================================
+ Hits        14308    14578     +270
+ Misses      12326    12119     -207
+ Partials      992      983       -9

Impacted Files
Coverage Δ

...es/amplify-cli/src/init-steps/s0-analyzeProject.ts
40.25% <0.00%> (-1.08%)
:arrow_down:

...chable-transformer/src/cdk/create-cfnParameters.ts
100.00% <ø> (ø)

...r-awscloudformation/src/amplify-service-manager.js
6.48% <0.00%> (-0.07%)
:arrow_down:

...r-awscloudformation/src/amplify-service-migrate.js
10.97% <0.00%> (ø)

...der-awscloudformation/src/configuration-manager.ts
5.47% <0.00%> (-0.09%)
:arrow_down:

...y-provider-awscloudformation/src/push-resources.ts
9.80% <0.00%> (ø)

...vider-awscloudformation/src/utils/admin-helpers.ts
19.60% <0.00%> (ø)

...ges/amplify-util-mock/src/utils/dynamo-db/index.ts
0.00% <0.00%> (ø)

.../src/utils/lambda/populate-lambda-mock-env-vars.ts
0.00% <0.00%> (ø)

...s/graphql-transformer-core/src/GraphQLTransform.ts
27.23% <ø> (ø)

... and 23 more

Continue to review full report at Codecov.

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


[Release] Check list for v0.10.0

v0.10.0
Overview
The release process mainly follows from this dependency graph.
flowchart LR
    Trustee --> Versions.yaml
    Guest-Components --> Versions.yaml
    Kata --> kustomization.yaml
    Guest-Components .-> Client-tool
    Guest-Components --> enclave-agent
    enclave-cc --> kustomization.yaml
    Guest-Components --> versions.yaml
    Trustee --> versions.yaml
    Kata --> versions.yaml

    subgraph Kata
        Versions.yaml
    end
    subgraph Guest-Components
    end
    subgraph Trustee
        Client-tool
    end
    subgraph enclave-cc
        enclave-agent
    end
    subgraph Operator
        kustomization.yaml
        reqs-deploy
    end
    subgraph cloud-api-adaptor
        versions.yaml
    end

Starting with v0.9.0 the release process no longer involves centralized dependency management.
In other words, when doing a CoCo release, we don't push the most recent versions of the subprojects
into Kata and enclave-cc. Instead, dependencies should be updated during the normal process of development.
Releases of most subprojects are now decoupled from releases of the CoCo project.
The Steps
Note: It may be useful when doing these steps to refer to a previous example. The v0.9.0 release applied these changes. After following steps 1-5 below, you should end up with a similar set of changes.
Determine release builds
Identify/create the bundles that we will release for Kata and enclave-cc.

[ ] 1. :eyes: Create enclave-cc release
Enclave-cc does not have regular releases apart from CoCo, so we need to make one.
Make sure that the CI is green and then use the Github release tool to create a tag and release.
This should create a bundle here.

[x] 2. :eyes: Find Kata release version
The release will be based on an existing Kata containers bundle.
You should use a release of Kata containers.
Release bundles can be found here.
There is also a bundle built for each commit.
If you absolutely cannot use a Kata release,
you can consider releasing one of these bundles.

[ ] 3. :eyes: Create a peer pods release
Create a peer pods release based on the Kata release, by following the documented flow.

Test Release with Operator

[ ] 4. :eyes: Check operator pre-installation and open PR if needed
The operator uses a pre-install container to setup the node.
Check that the container matches the dependencies used in Kata
and that the operator pulls the most recent version of the container.

Check that the version of the nydus-snapshotter used by Kata matches the one used by the operator

Compare the nydus-snapshotter version in Kata versions.yaml (search for nydus-snapshotter and check its version field) with the Makefile (check the NYDUS_SNAPSHOTTER_VERSION value) for the operator pre-install container.

If they do not match, stop and open a PR now. In the PR, update the operator's Makefile to match the version used in kata. After the PR is merged, continue.

[ ] 5. :wrench: Open a PR to the operator to update the release artifacts
Update the operator to use the payloads identified in steps 1, 2, 3, and 4.
Make sure that the operator pulls the most recent version of the pre-install container

Find the last commit in the pre-install directory

As a sanity check, the sha hash of the last commit in that pre-install directory will correspond to a pre-install image in quay, i.e. a reqs-payload image here.

Make sure that the commit matches the preInstall / postUninstall image specified for enclave-cc CRD and ccruntime CRD

If these do not match (for instance if you changed the snapshotter in step 4), update the operator so that they do match.

There are a number of places where the payloads are referenced. Make sure to update all of the following to the tag matching the latest commit hash from steps 1, 2, and 3:

Enclave CC:

sim
hw
base

Kata Containers:

default
s390x
peer-pods
Note that we need the quay.io/confidential-containers/runtime-payload-ci registry and kata-containers-latest tag

Also, update the operator version (update the newTag value)

Final Touches

[ ] 6. :trophy: Cut an operator release using the GitHub release tool

[ ] 7. :green_book: Make sure to update the release notes and tag/release the confidential-containers repo using the GitHub release tool.

[ ] 8. :hammer: Poke Wainer Moschetta (@wainersm) to update the release to the OperatorHub. Find the documented flow here.

Post-release

[ ] 9. :wrench: Open a PR to the operator to go back to latest payloads after release
After the release, the operator's payloads need to go back to what they were (e.g. using "latest" instead of a specific commit sha). As an example, the v0.9.0-alpha1 release applied these changes. You should use git revert -s for this.

Step 2: We will be using kata-containers v3.8.0

Step 2: We will be using kata-containers v3.8.0

Why are you using v3.8.0, when this release is supposed to sync up with v3.9.0?

Hi @confidential-containers/enclave-cc-maintainers ! We're doing the v0.10.0 CoCo release, and Step 1 is to release enclave-cc. Could I have a hand with this? We need to create a release from the enclave-cc github page.

I can do that.

Why are you using v3.8.0, when this release is supposed to sync up with v3.9.0?

Oh, this could my mistake, then. I was choosing the latest bundle from here.

Why are you using v3.8.0, when this release is supposed to sync up with v3.9.0?

Oh, this could be my mistake, then. I was choosing the latest bundle from here.

Yeah, the kata release hasn't happened yet and is due on Thursday.

Step 4 completed here

Step 8 is merged here.


location of events should be shown if different.

This should probably have it's own map or a map with all the events marked.

they now have a separate tab


Correct build status badge

The badge was pointing to an invalid location.
@samdutton @louquillio

Thanks! I broke it :).


Arch linux build failed

Steps to reproduce
This will generate a JSON format file containing all messages that
need to be translated.
Launching lib/main.dart on Linux in debug mode...
/home/sun_god_nika_luffy/mangayomi/linux/flutter/ephemeral/.plugin_symlinks/flutter_qjs/cxx/quickjs/quickjs.c:9843:16: error: incompatible pointer to integer conversion returning 'void *' from a function with result type 'JSClassID' (aka 'unsigned int') [-Wint-conversion]
/home/sun_god_nika_luffy/mangayomi/linux/flutter/ephemeral/.plugin_symlinks/flutter_qjs/cxx/quickjs/quickjs.c:10793:30: warning: implicit conversion from 'long' to 'double' changes value from<PHONE_NUMBER>854775807 to<PHONE_NUMBER>854775808 [-Wimplicit-const-int-float-conversion]
Building Linux application...
Error: Build process failed
Expected behavior
I expected the file to be builded when ran flutter run and yes i did run flutter_rust_bridge_codegen generate
Actual behavior
it doesnt build the file
Mangayomi version
5.6.6
Device
I have arch linux and my device is hp laptop pavilion
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, I should be opening an issue in the extensions repository.
[X] I have updated all installed extensions.

fixed, you can try to build again


Rename this variable to not match a restricted identifier in CsvUtil.…

I changed the variable name record to recordData.
Describe your changes :

I worked on the ..... because ...

Type of change :

[x] Bug fix
[x] Improvement
[x] New feature
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation

Frontend Preview (Screenshots) :
For frontend related change, please link screenshots of your changes preview! Optional for backend related changes.

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Reviewers

@lap1597 thank you for this contribution. Can you run mvn googleformatter:format@reformat-sources command to format the code and update the pull request?


[WIP] Add a hidden column __natural_order__.

Adding a hidden column __natural_order__ for ordering the rows as it is, especially for window-like operations like cumxxx.

Codecov Report

Merging #1146 into master will decrease coverage by 1.61%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1146      +/-   ##
==========================================
- Coverage   95.19%   93.57%   -1.62%
==========================================
  Files          35       35
  Lines        7075     7067       -8
==========================================
- Hits         6735     6613     -122
- Misses        340      454     +114

Impacted Files
Coverage Δ

databricks/koalas/series.py
96.46% <100%> (-0.03%)
:arrow_down:

databricks/koalas/indexing.py
94.57% <100%> (ø)
:arrow_up:

databricks/koalas/generic.py
95.76% <100%> (-0.43%)
:arrow_down:

databricks/koalas/groupby.py
91.41% <100%> (-0.22%)
:arrow_down:

databricks/koalas/internal.py
96.49% <100%> (+0.06%)
:arrow_up:

databricks/koalas/frame.py
96.3% <100%> (-0.58%)
:arrow_down:

databricks/koalas/usage_logging/__init__.py
24.32% <0%> (-72.98%)
:arrow_down:

databricks/koalas/usage_logging/usage_logger.py
50% <0%> (-50%)
:arrow_down:

databricks/koalas/__init__.py
76.59% <0%> (-8.52%)
:arrow_down:

databricks/conftest.py
92% <0%> (-6%)
:arrow_down:

... and 5 more

Continue to review full report at Codecov.

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

I am merging this for now. I will think about how to clean up too ... we can address the comments together later.


Extension ID case not preserved in web extension context

Originally created by @joyceerhl

Go to insiders.vscode.dev
Open sources
Search for remotehub extension bundle
Pretty print the file
Set a breakpoint on line 40222
Reload the page
🐛 See that context.extension.id === 'GitHub.remotehub-insiders' evaluates to false because context.extension.id is 'github.remotehub-insiders`. This is only the case on web insiders and stable--on desktop insiders and stable, case is preserved

I believe this behavior changed at least two releases ago, because RemoteHub uses this check to determine whether to enable an experimental setting--but it's possible that this has always been the case in web. I can look into running web out of sources to check if/when this changed.
IMO this is a surprising behavior discrepancy between web and desktop that may cause certain functionality to silently break in web. As an example, in web if you install RemoteHub stable and RemoteHub insiders together, you don't get the extension's warning since it's gated on a check for 'GitHub.remotehub-insiders'

/verified


Make the formatter for IStringable const

Without this, IStringable and types which implement IStringable technically did not meet the formattable concept, which uses a const formatter<remove_cvref_t<T>, charT> to verify for formattability.

Some multi_threaded_map failed even though it's unrelated. Do they have known reliability issues?

Yes, that test is a bit unreliable. I'll rerun it for you.

Some multi_threaded_map failed even though it's unrelated. Do they have known reliability issues?

Yeah, the multi_threaded_map and multi_threaded_vector shares code and they like to fail occasionally: #1202


Delete Dockerfile.devel-gpu-cuda9-cudnn7

our default dockerfiles now use cuda9-cudnn7.
No need for this file anymore.
CC @flx42

Great!
Quick question: to build a new CUDA 9.0+cuDNN v7 container image with the new Dockerfiles, what magic value of TF_DOCKER_BUILD_CENTRAL_PIP do I need to pass to parameterized_docker_build.sh?

Right now, there is not a correct value for that.
However, by tomorrow morning we should have our nightlies built, and ready to use.
We should be able to pass our nightly pip package URLs to the script.
As a note, I have a bug open, and the first chance I get I will rewrite all our dockerfiles and get rid of parameterized_docker_build script.

thanks @gunan, I'm not seeing the new pip packages at https://pypi.python.org/pypi/tf-nightly-gpu yet.
Also, looks like there hasn't been any nightly GPU docker image for a while:
https://hub.docker.com/r/tensorflow/tensorflow/tags/
Is your CI system currently on fire? :) Let me know if I can help.

We are also working on the 1.4.1 release, so the CI was backed up last night. I will see what I can do to push these out today.


Documentation updates

Codecov Report

Merging #20 (4d7274b) into main (37f83a4) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #20   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            9         9
  Lines          111       111
  Branches        16        16
=========================================
  Hits           111       111

Impacted Files
Coverage Δ

src/bluetooth_numbers/dicts.py
100.00% <ø> (ø)

src/bluetooth_numbers/utils.py
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Clear cache according to a maximum age since modification

This is my idea on how to clear the cache using a maximum age as threshold similar to the clear by maxsize API. While the image expire time is available this could be used

New version of Q42.WinRT with this code is up on NuGet:
https://www.nuget.org/packages/Q42.WinRT/
Thanks for the pull request!


core-to-plc: correctly convert spec booleans into our booleans

As I recently noticed (cf my email today), the booleans in the spec are not the usual Scott-encoded booleans, because they bake in the lazy matching. Regardless of whether this is a good idea or not, this means that we need to convert the spec-booleans that come out of builtins into our booleans. This is something of a hassle, since we'd been translating to builtins as functions, so we need to post-compose the conversion function, which adds some ceremony. I ended up restructuring some of the primitive code a bit to make this less annoying.
(And I realised this should almost certainly use Roman's typed builtin work in some way, but I'm leaving that for now).
The resulting code is somewhat painful, but it will get nicer again if we bring our booleans into sync.
On top of the value restriction PR, this allows me to move another test to the typechecking section!

I'm going to merge this because I think there's not much to say - it's just what we need to do.


typedef "call-signature" and "parameter" trigger on array of function

Bug Report

TSLint version: 5.8.0
TypeScript version: 2.5.3
Running TSLint via: gulp-tslint (has type information)

TypeScript code being linted
type Operation = (a: number, b: number) => number;
const Operations: Operation[] = [];

Operations.push(function add(a, b) {
    return a + b;
});

Operations.push(function subtract(a, b) {
    return a - b;
});

with tslint.json configuration:
{
    "rules": {
        "typedef": true
    }
}

Actual behavior
ERROR: (typedef) Example.ts[5, 26]: expected call-signature: 'add' to have a typedef
ERROR: (typedef) Example.ts[5, 30]: expected parameter: 'a' to have a typedef
ERROR: (typedef) Example.ts[5, 33]: expected parameter: 'b' to have a typedef
ERROR: (typedef) Example.ts[9, 26]: expected call-signature: 'subtract' to have a typedef
ERROR: (typedef) Example.ts[9, 35]: expected parameter: 'a' to have a typedef
ERROR: (typedef) Example.ts[9, 38]: expected parameter: 'b' to have a typedef

Expected behavior
Type definition should be inferred from the type of the array.
TypeScript itself does this properly and displays correct type hints.

Please note that this rule is not about what could be inferred. It's used to enforce type annotations even if they are not strictly necessary.
If you only want to enforce type annotations where necessary, you should not use this rule and enable --noImplicitAny in your compilerOptions instead.