Added reminder to hit play to receive images.

New feature
Closes #236
Summary
Added a reminder to hit play in Ignition Gazebo to receive images in example 2.
I didn't initially know this and it took me a while to realize why I wasn't receiving images even though I followed the instructions to the letter.

Thank you for the PR, @joe28965 ! Would you mind signing your commit for the DCO checker?

@chapulina DCO is fixed


Exporting 3D world model

Many downstream robotic applications are not only reliant on the current pose estimate provided, but also world model collected by SLAM pipelines. This is relevant for planning domains such as in navigation stacks, but also exploration mapping techniques as well, e.g. frontier expansion.
Conventionally, exporting a SLAM framework's internal world representation often consists of projections into discretized occupancy models, either 2D maps or 3D or voxel grids, probabilistic or discrete depending upon application requirements or information available from internal world representation. Such projections could be computed online at runtime or offline ex post facto.
A LIDAR based pipelines, such as Cartographer, Slam Toolbox, often provide such online and offline methods.
Subscribe for Online

https://google-cartographer-ros.readthedocs.io/en/latest/assets_writer.html#exploiting-the-map-generated-by-cartographer-ros

Occupancy grid Node
The occupancy_grid_node listens to the submaps published by SLAM, builds an ROS occupancy_grid out of them and publishes it. This tool is useful to keep old nodes that require a single monolithic map to work happy until new nav stacks can deal with Cartographer’s submaps directly.
https://google-cartographer-ros.readthedocs.io/en/latest/ros_api.html#occupancy-grid-node

Published topics

map
nav_msgs/OccupancyGrid
occupancy grid representation of the pose-graph at map_update_interval frequency

https://github.com/SteveMacenski/slam_toolbox#published-topics

Export for Offline

Pbstream Map Publisher Node
The pbstream_map_publisher is a simple node that creates a static occupancy grid out of a serialized Cartographer state (pbstream format). It is an efficient alternative to the occupancy grid node if live updates are not important.
https://google-cartographer-ros.readthedocs.io/en/latest/ros_api.html#pbstream-map-publisher-node

Exposed Services

Topic
Type
Description

/slam_toolbox/deserialize_map
slam_toolbox/DeserializePoseGraph
Load a saved serialized pose-graph files from disk

/slam_toolbox/dynamic_map
nav_msgs/OccupancyGrid
Request the current state of the pose-graph as an occupancy grid

/slam_toolbox/save_map
slam_toolbox/SaveMap
Save the map image file of the pose-graph that is useable for display or AMCL localization. It is a simple wrapper on map_server/map_saver but is useful.

/slam_toolbox/serialize_map
slam_toolbox/SerializePoseGraph
Save the map pose-graph and datathat is useable for continued mapping, slam_toolbox localization, offline manipulation, and more

https://github.com/SteveMacenski/slam_toolbox/blob/eloquent-devel/README.md#exposed-services

That said, we could also see how to adjust navigation2 to deal with Kimera_VIO's world representation directly, but I think support exporting for conventional volumetric occupancy model could benefit for legacy or traditional planning approaches. A related discussion ticket about using mesh models directly for navigation: https://github.com/ros-planning/navigation2/issues/1461
Related:

https://github.com/MIT-SPARK/Kimera-VIO/issues/12

So relating to this issue, and as I was implying in https://github.com/ros-planning/navigation2/issues/1461, exporting the global 3D Mesh is already possible via Kimera-Semantics by using Voxblox API:  just call the rosservice
rosservice call /kimera_semantics_node/generate_mesh "{}"

Can I know what format would this exported 3d mesh have? I want to use this map further for AR applications.

Hi @ToniRV, trying to generate the full mesh here, is it possible to get the ESDF/TSDF file with this command? Also, is there any documentation for this service call?

Voxblox does support this as one of the services, and Kimera-Semantics will give you the esdf/tsdf file:
rosservice call /kimera_semantics_node/generate_mesh
rosservice call /kimera_semantics_node/save_map

And so on. For more info, see here.


[Unity][NN] Allow nn.Module to generate subroutines

Prior to this commit, nn.Module generated the relax expression within the body of relax.BlockBuilder.current().  For large models, this can result in extremely large function bodies, making it difficult to identify regions within the module.
This commit adds an option nn.Module.define_subroutine, which defaults to False (current behavior).  If set to True; either within a subclass, within an instance, or globally in nn.Module; function calls into the module will produce a subroutine representing the module's execution, and a call into that subroutine.  For example, calling a class Linear(nn.Module) would produce a def linear(arg, weights) function definition and a module.linear(arg, weights) function call.  To ensure correct shape propagation, a subroutine is generated for each unique set of argument shapes passed to the nn.Module subclass.
The PR branch contains three commits for ease of review.  The first commit extends relax.BlockBuilder to allow definitions to be generated while already making a function.  The second commit extends nn.Module to optionally generate and call subroutine functions.  The third commit adds backwards compatibility type checks to retain compatibility with mlc-ai's implementation of llama when generating subroutines.

From discussion with @junrushao , extended implementation to also support the new relax.frontend.nn.Module API.

This is super cool work and really improved the UX overall! Thanks @Lunderberg and @slyubomirsky!


iMessgae and facetime don't work without SMBIOS, Web camera and Bluetooth don't work with SMBIOS

Lenovo Model: Yoga X1 20QG-S1630J
CPU: Intel i7-8665U
Graphic: UHD 620

iMessgae and facetime not working without SMBIOS is obvious.
Bluetooth depends on OpenIntelWireless, Web Camera depends on ACPI patches. Would you mind posting your Bluetooth device?

Thanks @suhrmann. I am not a tech man.After applying SMBIOS MacBook pro 15.4 or MacBook Pro 15.1, both Bluetooth and web camera disppear on hardware list.

This is very weird behaviour. For Bluetooth I recommend following Troubleshooting of IntelBluetoothFirmware [OpenIntelWireless]

thanks for the suggestion.


Add memory router with prompt

This change adds a new RouterMemoryRouter component based on the RouterBrowserRouter component. Previously, our stories use the MemoryRouter from react-router directly, with which our router prompts would not work, and therefore the form dirty handlers would not work either. Using the RouterMemoryRouter in our stories causes the form dirty handlers to work correctly.

Since the MemoryRouter is exported from @comet/admin, maybe add it as a highlight to the changelog?

Since the MemoryRouter is exported from @comet/admin, maybe add it as a highlight to the changelog?

I wouldn't add it, as we're primarily using it for our stories. I'm not aware that we're using a memory router in our applications elsewhere. @nsams what do you think?

The original idea was to list only highlights (aka important things that comet-admin users could be interested in)
Practice did show that a dev working on a PR sometimes always sees this as kind of a highlight, so it turned more into a changelog. But that's ok - we can pick "real" highlights when releasing.

And no, RouterMemoryRouter is definitely not a highlight that others are interested in :)


fix: relative path html

Description
fix: #7818

Additional context
isExternalUrl is truth? html support ftp / file protocol?
this PR make script style src attr relative path
from
asset/main.js
asset/style.js
http://a.a/asset/style.js
https://a.a/asset/style.js

to
./asset/main.js // add ./
./asset/style.js // add ./
http://a.a/asset/style.js // no change
https://a.a/asset/style.js // no change

What is the purpose of this pull request?

[x] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the Commit Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[x] Ideally, include relevant tests that fail without this PR but pass with it.

I don't know if we could support this without a breaking change. Could we import an npm module directly before? 🤔
<script src="module-with-side-effect" type="module"></script>

Another issue is what happens with nested HTML, where does assets/file.js points for them? Is it ok to also point them relative to the HTML itself?
Maybe we should ask people to keep using relative paths instead?

I think no base path(aaset/main.js) is relative path too? 👀
https://github.com/vitejs/vite/pull/7644/files#diff-aa53520bfd53e6c24220c44494457cc66370fd2bee513c15f9be7eb537a363e7R758-R760
I don't know what is nested HTML

Nested html as in an MPA where you have:
index.html
pageA/index.html
pageB/index.html

I have tested a bit.
npm i normalize.css ./pkg
<link rel="stylesheet" href="normalize.css" /> <!-- this does not resolve to node_modules/normalize.css/normalize.css -->
<link rel="stylesheet" href="normalize.css/normalize.css" /> <!-- this does not resolve to node_modules/normalize.css/normalize.css -->
<script type="module" src="pkg"></script> <!-- this **does** resolve to node_modules/pkg/index.js -->

So it would be a breaking change?

I think we should use the preferRelative feature for HTML files only. Adding a importer?.endsWith('.html') on this line:
https://github.com/vitejs/vite/blob/8220ee57735831540297fd68a0470e34ed377767/packages/vite/src/node/plugins/resolve.ts#L177
Fixed the issue for me, and should avoid the breaking change. What do y'all think?

@sapphi-red now I know this use case <script src="module-with-side-effect" type="module"></script>. we make all the module script / link href to js import. we can use this case. My resolution is actually break change. 😂
thanks @bluwy good idea to avoid change it.


SwiftPM should be more resilient against random binaries named xcrun and sandbox-exec in the PATH

For the tools that are in fixed locations, SwiftPM should run them using absolute paths.
Failing to do so will cause the build to fail when running swift build under certain environments such as tests where PATH is set incorrectly.  It's also a bad idea to run sandbox-exec out of a random location.
Furthermore, it is not valid to invoke xcrun from any other location but /usr/bin, so we should not spend time looking up a constant.
rdar://68374424

@swift-ci please smoke test

Accidentally closed ("Close with comment" button is right next to "Comment").  Reopened.


Missing val, test ids in splits.json

Hi @vishalned , I noticed that the splits.json files for each of the dataset variants do not contain any indices for the val and test splits but are just empty lists. Is that information available somewhere else, since in your paper you report results for a specific test set? Thanks in advance!

Hey, we do not use val and test splits. In our paper MMEarth is used for pretraining and hence the splits is not needed. This was just created incase someone else wants to use the splits for some other reason. (you can always recreate the splits, using the utils/script.py and change the split percentages in the function.


added new solution page for communication-azure-kafka

added a new solution page and corresponding images / icons for Apache Kafka options on Microsoft Azure

Fine for me. Will provide additional content according standard levels.


Add node delete action

Allows the user to delete selected nodes by pressing X
As there's no way to add shortcuts to existing editor commands and deleting selected things is not exposed in Godot, we had to code this command ourselves.
Currently this is implemented only without user confirmation. So pressing X instantly deletes selected nodes, with undo/redo support.
Would you like me to add an optional confirmation popup? As in Godot with the Del. key, X could open a confirmation popup, and Shift X instantly delete nodes.
close #11

Yes, I think it is better to show a confirmation popup for pressing X, as this action is too destructive, and it is too easy to press it accidentally.

Done! The confirmation dialog mimicks the built-in one. If you press X it shows the confirmation dialog, and Shift X skips it.
As you'll see, I create the dialog in the function, but please let me know if you'd prefer it to be cached and to stay around hidden, and only be created and freed when the plugin loads or unloads.

Looks good to me, deleting nodes doesn't happen that frequently anyway.
Haven't really code in Godot 4, but connecting a method to signal is so cool: popup.confirmed.connect(popup.queue_free)
Thank you!


Don't send tar output to logger

The logger prefixes outputs on stderr with error, but on macos, tar
outputs logging messages to stderr, which has produced confusion (see
https://github.com/informalsystems/apalache/issues/1368#issuecomment-1044121136).
This change just lets the output go to std{out,err} as appropriate,
rather than thru the logger, so no misleading prefixes are attached.

Codecov Report

Merging #1382 (9a23efe) into unstable (bc227ff) will increase coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           unstable    #1382   +/-   ##
=========================================
  Coverage     75.10%   75.11%
=========================================
  Files           333      333
  Lines         10768    10768
  Branches        544      544
=========================================
+ Hits           8087     8088    +1
+ Misses         2681     2680    -1

Impacted Files
Coverage Δ

...he/io/annotations/parser/CommentPreprocessor.scala
93.97% <0.00%> (+1.20%)
:arrow_up:

Continue to review full report at Codecov.

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

MacOS builds don't have the misleading error prefix on the tar output now:


Tag 11.0 version. Laravel 11 just landed 🌕  🚀

Hey @cviebrock
Thanks for your work 🙏
I saw you already merged the Laravel 11 support PR. Let me know if there is something else to be done before tagging 11.0 that I can help you with.
Cheers

Until the final release use dev branch 11.0.x-dev

Version 11.0.0 is hot off the presses!


Tab problem

Press Tab at the start of a newline. It adds a couple of spaces and also something that looks like a blockquote.
Later when we go to a newline, the tab spacing is continued and there is no way to return back to the normal mode. (even backspace doesn't work)

I was experiencing this too. Ended up adding jquery.hotkeys.js. solved my issue.


Handle cookies

I stumbled upon a page that set cookies in the redirection. I don't know if it is part of the http spec or not, but I had to change the redirection code within request to handle this.
Since request does not handle cookies itself, it might make sense to build a generic callback where the caller can play with the headers etc.
Thanks,
Julien.
Mikeal changed the title to add more generic support for cookies.

juggy -- care to share your cookie changes to request?  i'll take hacks!
+1 on callback support to twiddle with headers or cookies support.

Here's a patch that adds cookie support.  Warning, js and node.js and git and github and http newbie here.  It works for my application, but no idea if it is per spec.  Depends on node-cookiejar, which means package.json should be updated.
From 4bf36075d354dd5c41f1598249bf05a161da0cc2 Mon Sep 17 00:00:00 2001
From: Wayne Lee<EMAIL_ADDRESS>Date: Tue, 11 Oct 2011 23:27:44 -0700
Subject: [PATCH] Add cookie support in redirects

main.js |    8 ++++++++
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/main.js b/main.js
index de75caf..28ef534 100644
--- a/main.js
+++ b/main.js
@@ -263,6 +263,14 @@ Request.prototype.request = function () {
self.uri = response.headers.location
self.redirects.push( { statusCode : response.statusCode,
redirectUri: response.headers.location })
+

   if (self.response.headers['set-cookie']) {

       var cj = require('cookiejar').CookieJar()

       cj.setCookies(response.headers['set-cookie'])

       cookies = cj.getCookies(CookieAccessInfo(url.parse(self.uri).host))

       self.headers['Cookie'] = cookies.toValueString()

   }

   delete self.req
   delete self.agent
   delete self._started

--
<IP_ADDRESS>

@waynelee Good but you might do the initial request with cookies, use those cookies for the redirection and, finally, se them after the redirection. My code is similar but you have a callback when the redirection occurs where you can do whatever you want (including cookies).

this is the API i want for cookies
var j = request.jar()
request({url:'http://www.google.com', jar:j}, function () {
  request({url:'http://images.google.com', jar:j})
})

The jar holds the state of the cookies being set, each request sends the proper cookies for that domain. The boiler is easy to get rid of with defaults.
var j = request.jar()
var r = request.defaults({jar:j})
request('http://www.google.com', function () {
  request('http://images.google.com')
})

It looks like https://github.com/bmeck/node-cookiejar might be a good candidate for this API?
@alessioalex - Do you want to try looking into this and seeing what you can do?

if we go with node-cookie jar please check the dependency. i do not want to add dependencies to the package.json if at all avoidable.

I'll take a look over the weekend on https://github.com/bmeck/node-cookiejar/blob/master/cookiejar.js + https://github.com/LearnBoost/tobi/blob/master/lib/cookie/jar.js and try to come up with a useful implementation

I think you can solve this without actually adding any specific code for cookies. When you do your request/redirect, a callback can be called to let the user deal with the headers/cookies. No new dependencies would be needed and it would be a little more future proof.
As a user of request, if I need cookies, I use any of the available libs to do that (or deal with them myself). A wiki page or a code exemple should be available to ease the implementation.
What do you think?

@juggy I did this, its a pain

I have this almost 90% implemented, no dependencies needed, I'll finish it in one hour or so and them make a pull request.

What's up about this issue, guys? I have the same problem.


Remember or Set Default Tab

Installed product versions

Visual Studio: 2019 Community
This extension: 0.14.3

Description
Add either an option to set what tab should be the default when VS opens, or remember the last tab opened.
Steps to recreate

Open Visual Studio and open the new Start Page+.
Select a tab other than the "Start" tab, IE, the "Favorites" tab.
Close and reopen Visual Studio.

Current behavior
When Visual Studio reopens, it always starts in the "Start" tab.
Expected behavior
I would like it to start in another tab such as the "Favorites" tab each time Visual Studio is opened. Either by having option set the default tab, or it just remember the tab I manually opened last.

PS1. I checked the road map and the "Goals for Start Page+" so I don't know if this falls under the "should be customizable" checkbox, but I wanted to point this particular behavior out as an explicit customization I would like to have.
PS2. I already love this new extension. I can't wait until the Favorites tab is functional. The new Start Window is complete garbage, and I used to use an extension in VS 2017 that sounds like it is identical (or really really close) to the plans you have listed on the Favorites tab. Keep up the good work!

For the time being, the tabs have been put on the back burner. As much as I'd love to be able to get stuck into the Favorites tab, I'm not sure if my health will allow it.
I still want to do this though. I'm going to close this for now, but it will definitely stay on my backlog.


check existing bridge names when creating networks

when creating a new networking, we should check existing networks for
their bridge names and make sure the proposed new name is not part of
this. reported by QE.
Signed-off-by: baude<EMAIL_ADDRESS>

ping? merge?

LGTM
@mheon @giuseppe @vrothberg @TomSweeneyRedHat @jwhonce @QiWang19 PTAL

/lgtm

LGTM

Merge bot seems to be hung.  Merging manually


Provide a real world example

Maybe something that searches for all *.jpeg in a directory, starts a thread pool, and in each thread, converts them to .png

I have a program doing this and creating thumbnails and calculating some more.
It is embedded into my deployment process and has zero comments so I am not certain it would be very useful for a beginner.
Would you like to include it with this repo or would you like to link to it?
If you are just interested in the solution, I can email it to you.

I'm interested in finding the simplest possible real world example. If your thumbnail generator is very simple, then yes, it sounds like it would be a good candidate.

I'm using your crate for this it's a remote command execution tool. This should work with hundreds of remote nodes, however i haven't tested that amount yet.

2 years later, I upvote this issue :+1:


FCS_STG_EXT.2 Key Storage Encryption (and 3)

Document inclusion criteria and the consequences of selections.

When do we need to store keys or credentials on the platform?

I would think not unless it was tied to Tennant services.

If the platform includes a TPM, wouldn't it store some keys related to attestation?


Switch to ruff linter

Switch from using Black to using ruff, as in https://github.com/mesh-adaptation/goalie/pull/166. Doing so allows us to define all the configuration inside pyproject.toml, in line with #68.

@jwallwork23 I'm happy to take this too if you'd like :)

I'm happy to take this too if you'd like :)

Perfect, thanks very much!

Done in #68


add contents for vuldesk website

closed by https://github.com/meroDera/vuldesk-ui/commit/acf1dd783fb681743c42af3eb360dc083dd3da21


Add Ballerina debugger support for module-class-defn and object constructor expressions

Description:
$subject.
Steps to reproduce:
Affected Versions:
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

Please note VariableVisibilityTest is disabled with https://github.com/ballerina-platform/ballerina-lang/pull/25637/commits/bb8ab74d5df43f04d340e68814d56f450d800876

Please note VariableVisibilityTest is disabled with bb8ab74

@rdhananjaya Ack! will look into it


feat(richtext-lexical): Blocks: generate type definitions for blocks fields

Description
Closes #3993
This also now always sets unreachableDefinitions: true when generating types. This is because richText blocks types (e.g. from interfaceName prop) which are put in the definitions are currently not referenced anywhere.
In my opinion, these should still be included in the generated types in case the user wants to use them in their project, though.

[X] I have read and understand the CONTRIBUTING.md document in this repository.

Type of change

[ ] Chore (non-breaking change which does not add functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Change to the templates directory (does not affect core functionality)
[ ] Change to the examples directory (does not affect core functionality)
[ ] This change requires a documentation update

Checklist:

[ ] I have added tests that prove my fix is effective or that my feature works
[ ] Existing test suite passes locally with my changes
[ ] I have made corresponding changes to the documentation

Definitely waiting for this feature :).
We're currently using a hidden global where blocks get referenced inside the fields array for types to get generated for these blocks.

Running into this issue as well. Patiently waiting for this. For now I'll use @Spreizu solution by creating a hidden global


11_webcam_features.py error

11_webcam_features.py in line 29 of the code there is an error.

error: (-5:Bad argument) in function 'circle'
Overload resolution failed:
Can't parse 'center'. Sequence item with index 0 has a wrong type
line 29, in
cv2.circle(img, (x, y), 12, red_color, -1)

Thanks for reporting @BaderAlsabbagh!
I've just fixed the code in the commit 66a9169e25a7c7f7bee967b9026e6bce8726fac4


SDSTOR-9070 fixing mblk size during upgrade

Looks good, but whats the strategy to revert this change?

We will have to make another image to remove the hot fix (also changing the default value of the dynamic config).


Create Marketplace page.

Do all work for this task in a branch called issue-9

close since functionality is finished. needs graphical improvements


[BEAM-7437] BQ integration test for streaming inserts in streaming

Integration test for BigQuery sink using Streaming Inserts, for streaming pipelines, using TestStream.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Run Python PostCommit

Run Python PostCommit

R: @pabloem

Run Python PostCommit

Run Python PostCommit

Run Python PostCommit

This lgtm tanay. Thanks!


Improve loading time for images

Currently, images take a while to load as they're quite large. Can we compress the images when they are committed using a GitHub action to improve loading speeds?

Hi, I'm really excited about this issue. Since I've never worked with GitHub actions before, and optimizing the image loading speed is something that I've achieved in entirely different ways in the past. So I'm super interested in taking up this issue if that's fine. Also, I don't mind anyone else working on this issue with me.


Deal with Abelian/Commutative objects better.

There are often optimizations the can be done if a semigroup/monoid/group is commutative.
How can we best communicate that?
Two obvious solutions: a property of the instance (.isCommutative). This rules out the ability to have some methods that only apply to commutative objects (because that check is at runtime).
A second type-class approach would be something like:
// use this to check at runtime:
sealed trait CommutativeStatus[O] {
  def commutes: Boolean
}
trait IsNotCommutative[O] extends CommutativeStatus[O] { val commutes = false }
// use this when you want to require commutativity
trait IsCommutative[O] extends CommutativeStatus[O] { val commutes = true }

trait LowP {
  implicit def defaultIsNot[O]: CommutativeStatus new IsNotCommutative[O] { }
}

object CommutativeStatus extends LowP {
  implicit def commutes[O](implicit isc: IsCommutative[O]): CommutativeStatus = isc
}

We can add instances of IsCommutative to the Monoid/Group/Semigroup objects.

@johnynek , I propose that we close this since we're adopting shared typeclasses soon.


DOCKER-160: Add port ranges to docker proxy

Basic non-ranged case seems to work.  I'll setup and test a case using the port ranges soon.

Did some testing with the ranges, seems okay.  Ship it.


Add Course to Visible Term

Inside Admin->Course Management the button with the text "Add Course" performs a misleading course creation when viewing everything except the current term. When you click this button, regardless of which term you're viewing the courses for, the new course is always created for the current term. We believe this is misleading.
Please change the "Add Course" button's functionality to create courses for the term that we're viewing and not always the term that is selected as the current term.

 Software


Revert "Started new branch for recovery controller"

Reverts mesosphere/kudo-cassandra-operator#96 in an attempt to de-flake the tests.
The kuttl tests failed on every commit since it was merged:
The change itself: https://github.com/mesosphere/kudo-cassandra-operator/commit/9265e3022f3aed7e8fee64905ce51a87d8977ea1

https://teamcity.mesosphere.io/buildConfiguration/Frameworks_DataServices_Kudo_Cassandra_Pr_CassandraPrKonvoyKudo_2/2739677?showLog=2739677_2338_1247.2338
https://teamcity.mesosphere.io/buildConfiguration/Frameworks_DataServices_Kudo_Cassandra_Nightly_CassandraNightlyKonvoyKudo/2739991?showLog=2739991_2110_961.2110
both failed with: failed to get file: command "docker exec --privileged kind-control-plane cat /kind/version" failed with error: exit status 1

My two PRs:

https://github.com/mesosphere/kudo-cassandra-operator/pull/109
https://teamcity.mesosphere.io/buildConfiguration/Frameworks_DataServices_Kudo_Cassandra_Pr_CassandraPrKonvoyKudo_2/2739678?showLog=2739678_2611_1247.2611

      kuttl/harness/node-failure: logger.go:41: 20:07:14 | node-failure | 2020-05-14 20:07:07 +0000 UTC  Warning  Unhealthy  Liveness probe failed: File replace.ip found with IP:<IP_ADDRESS>
22:07:14
          nodetool: Failed to connect to '<IP_ADDRESS>:7199' - ConnectException: 'Connection refused (Connection refused)'.

https://github.com/mesosphere/kudo-cassandra-operator/pull/108
https://teamcity.mesosphere.io/buildConfiguration/Frameworks_DataServices_Kudo_Cassandra_Pr_CassandraPrKonvoyKudo_2/2739676?showLog=2739676_2423_1247.2422.2423
again failed with failed to get file: command "docker exec --privileged kind-control-plane cat /kind/version" failed with error: exit status 1

I'm not sure how keeping master red is going to help?
https://github.com/kudobuilder/kudo/blob/master/CONTRIBUTING.md#general-guidelines

@porridge I don't see any guidelines for reverts 🤔 https://github.com/kudobuilder/kudo/blob/master/CONTRIBUTING.md#general-guidelines
I see for green builds which is the intention and priority here


Add a new Cystoid Nest Mechanics.

Description
Cystoids can wind up lingering on the map. A quick fix right now will be having them leave the map after a while, but a more fun opportunity can happen here.
Cystoids should be able to join together to create new cystoid nests, or join existing nests. increasing the amount of cystoids that will be created when they burst.
Art Needed
Potentially various new sizes of cystoid nests

Redownloaded this game to assist finding references for you guys, this is an instance of a Cystoid next growing on a wall outside Talos-1, I am searching for an instance in a non-zero-gravity environment but I am not sure if one exists in game

Potentially better image of a cystoid nest:

Followed by the frames I've got of it exploding (Cant compress my video file enough for Github to be happy with me sending it so frames is all you get for now):
Immediately after bullet impact, brighter colors:

Primary shockwave of the explosion:

Secondary boom:

And then it spawns cystoids themselves:

Thats what I've got for now on the cystoid matter, again will try to find a nest in a non-zero-gravity environment if I can.

Well I did find instances of non-zero-g cystoid nests and you where right:

They normally hang from the ceiling in gravity, however the smaller more bulbus ones are the only version of cystoid nests that stick to the ground in gravity influenced zones, which makes Polioguy's artwork accurate, its just missing the orange lines dotted about its surface.

Good point. I'd love to spend some time code-wise and get those visual effects working in a glowey manner, every time I've tried adding to the sprite it doesn't feel right. I might take advantage of some overlay stuff when I come back around to cystoids.


Bluetooth: Mesh: Update models metadata API

Bluetooth: Mesh: Update models metadata API
This commit updates models metadata API to simplify the usage and
removes the metadata pointer in health server model context.

Renamed PR title to not confuse other people.

I'm not sure it is good to change BT_MESH_MODEL_METADATA_CB to use variable arguments as it is specifically added for models with metadata.

This has been made this way based on initial discussion. Please agree between you two if you want common BT_MESH_MODEL_HEALTH_SRV definition, or seperate BT_MESH_MODEL_HEALTH_SRV_METADATA definition. This will cause changes at several places, I will wait until you decide which way to go.

Passed Architecture WG review. Decision in the linked RFC.


Add support for Timezones

@dotnet/aspnet-build could I get help with this error:
.packages\microsoft.dotnet.arcade.sdk\1.0.0-beta.20113.5\tools\Sign.proj(81,5): error SIGN001: Signing 3rd party library 'D:\a\1\s\artifacts\tmp\Release\ContainerSigning\32\tools/dotnetwasm/framework/System.Net.Http.WebAssemblyHttpHandler.dll' with Microsoft certificate 'Microsoft400'. The library is considered 3rd party library due to its copyright: ''.

How do I resolve this?

Sorry, @pranavkm I only have debugging suggestions such as packing the project locally or examining the bin log of the failing build.
In general $(DisableArcadeProjectLayout) from the Directory.Build.props file could be doing all kind of weird things, breaking unintended parts of Arcade. But I don't see how the small change in the failing project relates.

When I tried this script locally, I got the following warnings in the zic command invocation. is this expected?
"obj/data/input/asia", line 2252: warning: time zone abbreviation differs from POSIX standard (+06)
"obj/data/input/asia", line 2262: warning: time zone abbreviation differs from POSIX standard (+04)
"obj/data/input/asia", line 2263: warning: time zone abbreviation differs from POSIX standard (+05)
"obj/data/input/asia", line 2264: warning: time zone abbreviation differs from POSIX standard (+06)
"obj/data/input/asia", line 2273: warning: time zone abbreviation differs from POSIX standard (+03)
"obj/data/input/asia", line 2274: warning: time zone abbreviation differs from POSIX standard (+05)
```

Thanks @dougbu, I was able to figure out what was wrong (I had to turn off signing for a renamed filed).
@captainsafia  I did not see this locally. There's a reference to the warning here: https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8151876 which says this could be safely ignored. I wonder if it's caused by a difference in the version.

I'm going to get this PR but leave it open to get some head start on change in AspNetCore.


add new resource page for conferences

fixes# 343
This creates a "Conferences" page under Resources...
https://techqueria.org/resources/conferences
Initially this page will contain the following Latinx Tech Summit Organizations in card format with title, description, and link to website. The following initial organizations are as follows:

http://ltx-latinx-in-tech-summit.eventcreate.com/
https://www.latinxinai.org/
https://latintech.io/
http://www.latinotech.org/
https://www.latinxtechsummit.org/

✅ By submitting this PR, I have verified the following

[X ] Checked to see if a similar PR has already been opened 🤔
[ X] Reviewed the contributing guidelines 🔍
[X ] Added my name to the bottom of the list under the Contributors section in the README.md with a link to my personal website or GitHub profile 👥 (Optional)

Also I removed the emoji cause we don't use them anymore

@fvcproductions we should probably add an issue for translation as well.


⚠ Samsung has degraded performance

In 6d34895, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 6464 ms

Resolved: Samsung performance has improved in fa8dd96.


Bug Report: The dropdown icon for select category and select author seems so much odd

Reproduction steps
It is on the home page and i am sure that it looks odd to everyone,
look at the drop down icon, just seems a bit off
it just simply looks bad, i mean don't you think it should have a little gap atleast

Expected behavior
i am working on to fix it and give it a more standard look
Actual Behavior
it just simply looks bad, i mean don't you think it should have a little gap atleast

👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

hey @SauravMukherjee44, can i go for it ?

@arian0zen Go for it!


feat(contrib): optional graceful shutdown

This is an attempt to add logic to gracefully remove a node from a cluster when halt, shutdown or reboot units are called on the host. There are a few things that need to be cleaned up on this before its ready, so Im fishing for help / insight:

[x] Where should the graceful shutdown script actually live? Its just a gist right now for convenience. I guess it could be in write files, but I feel like that size script prob shouldnt be directly in user-data.
[x] The graceful stop unit does indeed get called during shutdown, halt or reboot, but seems to be unable to complete. Im not sure why yet. It runs as expected when called any other way.
[x] Refactor graceful stop unit to be less brittle.
[ ] Are there any other steps we can take to make this smoother?

Thanks for the contribution! Please ensure your commits follow our style guide. This code will be tested once a Deis maintainer reviews it.

Jenkins, add to whitelist.

@iancoffey just a couple of questions:

Why the removal of the node from etcd? (that will be done automatically by etcd if the node never joins the cluster again)
The ceph steps are interesting but what's the costs of doing that?

you are not deleting the ceph data from the node
creating a new osd from the same node can return a different id and that means potential data duplication.
during the initial synchronization (of a new node) the ceph gateway could not be available

The final fleet stop is not necessary (and it could be the guilty for the not completion of the shutdown)

Where should the graceful shutdown script actually live?

(It is currently at this gist just to help reviewers.) Ideally we wouldn't curl it from elsewhere, since that fails sometimes when a machine is starting up, even with the --retry flag. And user-data is already unwieldy, but including it directly there would be more reliable. At worst, we can host it for S3 download like we do some other artifacts.

good points @aledbf

Implicitly removing the node from etcd leaves no room for error - a dying server with filesystem issues could potentially hang around, making things weird.
The cost of the ceph recovery is usually about 2-6 minutes of waiting for the cluster to recover before moving to shutdown.
Im curious why we wouldnt want to be certain fleet is down. IMO, it would be even better to preemptively be able to tell fleet "this suckers going down, reschedule accordingly" (which we cant).

Im curious why we wouldn't want to be certain fleet is down

Because you already remove the node from etcd cluster.

The cost of the ceph recovery is usually about 2-6 minutes of waiting for the cluster to recover before moving to shutdown.

That is true if you don't remove the ceph data from the node and this step return the same id. If not this node will be considered a new "pristine" ceph node and it will replicate all the data (and the time is proportional to the current content).
Just in case I think that this is a good idea :) and it could solve (at least partially) the autoscale issues with ceph in AWS.

This needs rebasing now, sorry about that.

make -C docs/ test is very strict about formatting:
Warning, treated as error:
/var/lib/jenkins/jobs/test-ec2/workspace/src/github.com/deis/deis/docs/managing_deis/add_remove_host.rst:126: ERROR: Unexpected indentation.

make: *** [test] Error 1
make: Leaving directory `/var/lib/jenkins/jobs/test-ec2/workspace/src/github.com/deis/deis/docs'

@iancoffey How did you solve the script not completing?

@carmstrong Just pushed some updates, I changed the unit file around a lot based on some feedback in #systemd. It works but it has a couple flaws that Im not crazy about.
One is that the script will run if you just stop docker. Another is that accidentally stopping the graceful-deis-shutdown unit will also trigger the sequence start.
I have some ideas for cleaning that up, I just added a checkbox for it. Would love input if theres any.

Seems this is kinda blocked on https://github.com/deis/deis/pull/3645 since the cluster is never healthy, so it gets skipped.
Before rebasing though, it did what I expected - take the osd out, block shutdown for about 2-3 mins and let the cluster get healthy before removing itself.

Seems this is kinda blocked on #3645 since the cluster is never healthy, so it gets skipped.

#3645 now suppresses the warning for old clusters that are upgraded (as well as new ones provisioned), so we should be good once it's merged.

Looks like https://github.com/deis/deis/pull/3645 is merged - anything else we should do here?

Jenkins failed this due to #3690 but I saw it go green earlier so I think we're good here. LGTM asides for my one comment. I'm happy this is optional so that we can test it before actually enabling it by default!

Cool, updated. :beers: Agree about this needing to be optional - my hope is that we learn a lot about failover along the way.

Code LGTM. I'd like to manually test this today, and then we should be good to go. :+1:

This code LGTM, although it needs more manual testing before it is merged. Really nice work @iancoffey. Thanks for sticking with this!

I just tried this with a 5-node cluster and it failed :(
logs from the failure: https://gist.github.com/bacongobbler/0d720ba7c51cdcdc9e81

@bacongobbler what provider did you use to create this cluster? Ive actually only tested this on ec2.

I tested this on vagrant

Odd:
><> vs deis-01 -c "hostname -f"
hostname: Unknown host
Connection to <IP_ADDRESS> closed.
><> vs deis-01 -c "hostname"
deis-01
Connection to <IP_ADDRESS> closed.

Maybe in order to get this merged, we can document that this has been only tested on EC2 and other providers are unsupported at this time?

Yeah, that probably makes sense, since I wont be able to test every provider thoroughly.
Id like this to work for Vagrant at least though, but Im having bad getting a working coreos vagrant cluster  at the moment - let me figure that our and adjust the docs, and then maybe this will be good to go.

I found the issue. It's because there's no /etc/hosts file in the vagrant hosts, which is why it wouldn't work. Derp!
core@deis-01 ~ $ cat /etc/hostname
deis-01
core@deis-01 ~ $ hostname
deis-01
core@deis-01 ~ $ hostname -f
hostname: Unknown host
core@deis-01 ~ $ sudo vim /etc/hosts
core@deis-01 ~ $ cat /etc/hosts
<IP_ADDRESS>	deis-01
core@deis-01 ~ $ hostname -f
deis-01

I think this should work now on Vagrant with the addition of the manage_etc_hosts entry.
I cant tell for sure because I have not been able to get a healthy Vagrant Deis cluster up. Ill bring that up as a separate issue.

I think this should work now on Vagrant with the addition of the manage_etc_hosts entry.

I'm not too worried about this working for Vagrant outside of us being able to easily test it. We don't recommend long-lived Vagrant clusters anyhow due to issues like clock drift on VM/laptop suspension, etc., so it's not a major concern.

Cool - I retested this on ec2 with 4 nodes, went to plan.

Code LGTM! Once @bacongobbler has also confirmed this works well in manual testing, let's get it out there and get people testing it.

My cluster is still recovering, but the OSD did indeed remove itself:
root@ip-10-21-1-73:/# ceph -s
    cluster 607ac12e-175b-4d3e-aaa2-04fa8da839eb
     health HEALTH_WARN
            11 pgs degraded
            1 pgs stuck unclean
            recovery 21/270 objects degraded (7.778%)
     monmap e5: 5 mons at {ip-10-21-1-72.us-west-1.compute.internal=<IP_ADDRESS>:6789/0,ip-10-21-1-73.us-west-1.compute.internal=<IP_ADDRESS>:6789/0,ip-10-21-1-74.us-west-1.compute.internal=<IP_ADDRESS>:6789/0,ip-10-21-2-196.us-west-1.compute.internal=<IP_ADDRESS>:6789/0,ip-10-21-2-197.us-west-1.compute.internal=<IP_ADDRESS>:6789/0}
            election epoch 14, quorum 0,1,2,3,4 ip-10-21-1-72.us-west-1.compute.internal,ip-10-21-1-73.us-west-1.compute.internal,ip-10-21-1-74.us-west-1.compute.internal,ip-10-21-2-196.us-west-1.compute.internal,ip-10-21-2-197.us-west-1.compute.internal
     mdsmap e7: 1/1/1 up {0=ip-10-21-1-73.us-west-1.compute.internal=up:active}, 3 up:standby
     osdmap e30: 4 osds: 4 up, 4 in
      pgmap v83: 704 pgs, 11 pools, 7624 kB data, 90 objects
            24673 MB used, 330 GB / 374 GB avail
            21/270 objects degraded (7.778%)
                 693 active+clean
                  11 active+degraded
  client io 562 B/s rd, 4874 B/s wr, 0 op/s

LGTM!


Unable to send a friend request

I think we removed the "add friend" button by accident during the profile page refactor in #712...
Use this file as a reference to add it back in.

Overlap with #759, closing for duplicate.


Chat names can be used as a titles and file names for exported chats

Now that ChatGPT supports multiple chats, chat names can be used as file names (instead of "chatgpt+date") and as titles with header tag within the file. Let's say the chat in named "Patching KDE2 on FreeBSD", then the markdown file can be exported with this text:
# Patching KDE2 on FreeBSD

You:
How does one patch KDE2 under FreeBSD?

ChatGPT:
To patch KDE2 under FreeBSD, you will need to follow these steps:
(...)

and the file itself can be named Patching_KDE2_on_FreeBSD.md (I'd say the current date is unnecessary because it's stored in the metadata within the file system, but it's up to you).
The same with copied text and HTML exports.

Good point. How about ChatGPT-{title}.{ext} ?
Not sure if we should keep the timestamp? :/

ChatGPT-{title}.{ext} sounds good.
Not sure about the dash though. ChatGPT tends to generate natural titles with spaces in them, so the dash separator would look alien. Spaces in the title can be replaced with dashes or underscores, but maybe it's a better idea to let the browser decide how to adjust the name to the rules of the user's file system.
The timestamp would make sense if it reflected the time the chat was generated. If I understand correctly, currently the timestamp is just the time of exporting/copying. And that already exists as the time of file creation/modification within the file system.  I'd say, if the time the messages were actually posted/generated isn't present anywhere on the webpage, then there's little value in having a timestamp in the file or file name, but that's just me.

Spaces in the title will be replaced with _ to prevent the troublesome on different platforms.
Example: chatgpt-List_Solar_System_Planets.md
Will this dash still look like an alien? Dash is the separator of chatgpt and title.
And thanks for the input about timestamp. I will remove it.

Are spaces in filenames actually troublesome anywhere except for bad shell scripts? 😁 Underscores would work, but there's no guarantee ChatGPT won't put some special characters into the chat name, so fixing the name would be the browser's job anyway.
Also, fun fact: https://chat.openai.com/backend-api/conversations?offset=0&limit=20 does contain chat creation time, it just isn't displayed in the UI. Not sure how useful this is as the query requires a token. I don't know whether intercepting this query is possible and worth the hassle, but the data is there. https://chat.openai.com/backend-api/conversation/CHATGUID contains timestamps of every message too, among other things.

Actually I'm not sure how troublesome it gonna be. I will sanitize the title to prevent special characters.
It's possible to send out the request as a userscript. But it might not be worth it to retrieve this kind of information.
Anyway, thanks for the information.


[Epic]: Developer Experience - Workflows

Objective
this epice makes sure the exisiting developer experience on JS editor in the workflows UI is consistent with app ui
Success Metrics

Metric

Customer satisfaction score increases

Decrease churn rate down to 30%

Prioritised User Stories

User Story

e.g. as a user, I want to be able to access the platform via mobile phone

e.g as a user, I want to be able to communicate with the other members on the canvas

Developer Handoff Document in Figma
No response
Test Plan
No response
RACI matrix

Role
People

Responsible

Accountable

Consulted
@Nikhil-Nandagopal, @mohanarpit, @areyabhishek

Informed

completed for closed beta


Update bower.json

invalid-meta The "name" is recommended to be lowercase, can contain digits, dots, dashes

There are repercussions of changing the name. I should have referenced https://github.com/bower/bower/issues/1751 before making the pull request. I'm just trying to get more involved in the community. Changing it would likely cause problems with people using it as a dependency.


[binance.js] (addOrder) returned an irrecoverable error

Note: for support questions, please join our Discord server

I'm submitting a ...
[x ] bug report
[ ] feature request
[ ] question about the decisions made in the repository

Action taken (what you did)
Trading with Gekko on Binance... trading 3 different pairs where this error occur: USDTBTC, USDTLTC and USDTNEO

Expected result (what you hoped would happen)
when the fund is not sufficient (to buy the asset) it should just give this message, and go on...

Actual result (unexpected outcome)
gekko stops and gives this error:
10|live601 |
10|live601 | 2018-02-22 15:53:22 (INFO):	Trader Received advice to go long. Buying  NEO
10|live601 | 2018-02-22 15:53:25 (INFO):	Attempting to BUY 0.011 NEO at binance price: 110.3
10|live601 |
10|live601 |
10|live601 | Gekko encountered an error and can't continue
10|live601 |
10|live601 | Error:
10|live601 |
10|live601 | [binance.js] Response code 400
10|live601 |
10|live601 | 2018-02-22 15:53:26 (ERROR):	[binance.js] (addOrder) returned an irrecoverable error: Error: Response code 400

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc)

sthing is not right in the handling of the error message from binance *I think.
I am on the latest update of develop branch from 2 days ago (20.02)

Problem occurs only with USDT Pairs... USDTBTC, USDTLTC, USDTNEO

Binance Modul version: 1.3.3.

i found this diffrence:
in binance rules.. the min order for all usdt trades are now 10.. see image..

but in binance-markets.json it is over all 1 like this for example:
"pair": [
"USDT",
"BTC"
],
"minimalOrder": {
"amount": 0.000001,
"price": 0.01,
"order": 1
}
could the order field be the problem?
because i have like 1.5 dollar or so... but according to binance it will not accept it, and according to gekko it is above the minmal order...
could that be it?
i also noticed that almost all btc and eth pairs have the minmum order 0.02 or 0.002 in gekko, but on the rules page they are all at 0.01 or 0.001
if any developer of gekko here confirm that this needs a review... i am happy to make a pull request and update that file according to the binance values

I found this
let getOrderMinSize = currency => {
if (currency === 'BTC') return 0.002;
else if (currency === 'ETH') return 0.02;
else return 1;
};
in the update-binance.js
maybe we need to correct this to .001 , 0.02 and 10...

sorry just discovered that BNB basis for orders is 1, so we need to differ here from 1 for bnb and 10 for usdt

I was right. The size 10 for the usdt solved the problem

@askmike should I make a pull request and add the changes?


TXT record is not correct.

@mholt
I've confirmed the record by checking it from the dnspod website.
It created a record '_acme-challenge.domain.com' instead of '_acme-challenge', which leads to a record '_acme-challenge.domain.com.domain.com', and the challenge cannot be fulfilled.
Could you please check this issue? I've found some codes related:
challenge.go
func (c Challenge) DNS01TXTRecordName() string {
	return "_acme-challenge." + c.Identifier.Value
}

DNSPod API needs a relative subdomain instead of an absolute one.
Possible related PR (but for Digitalocean):
https://github.com/libdns/digitalocean/pull/3/commits/bac007bf507194c1629657a31095830eb7816ecd

I have accepted the PR

@lscgzwd Thank you.


Securing admin-only resources

Why
Before we open up user registration, we have to secure any pages that should only be accessible to admins (sysadmins). This actually turns out to be the vast majority of our controllers, so ideally we can solve this w/o a lot of drudge work.
Pre-Merge Checklist

[x] All new features have been described in the pull request
[x] Security & accessibility have been considered
[x] High quality tests have been added, or an explanation has been given why the features cannot be tested
[x] New features have been documented, and the code is understandable and well commented
[ ] All outstanding questions and concerns have been resolved
[x] Any next steps that seem like good ideas have been created as issues for future discussion & implementation

What

[x] Add code to AdminController that ensures current_user is an admin || sysadmin
[x] Show sample implementation with one admin-only controller (ContactMethodsController)

How

With pundit, we would usually authorize each action independently and create policy classes for each resource.
For admin-only resources, this seems like overkill: these controllers and actions all require exactly the same check.
Inheriting this logic from a base controller in the form of a before_action seems like a simpler solution.
 I recommend we extract them out into their own controllers so AdminController can become an abstract base class.

Testing
Added a spec specifically around the simple auth introduced in AdminController. It uses ContactMethodsController as a sample admin-only resource.
Next Steps

[ ] Make other admin-only controllers subclasses of AdminController
[ ] Extract restful controllers out of the existing actions in AdminController since we don't want all subclasses to inherit this extraneous logic. See #836 .

Outstanding Questions, Concerns and Other Notes
?

I think someday we should have two levels of admin, but agree this should be the path until then

I think someday we should have two levels of admin, but agree this should be the path until then

Support removing NON-RESTful actions!

Support removing NON-RESTful actions!

Ready for review. H/T @h-m-m for his help simplifying the auth implementation 🍠 .

Ready for review. H/T @h-m-m for his help simplifying the auth implementation 🍠 .


Memory leak / Causing HA to freeze

Describe the bug
The integration produces error messages in a regular basis (few minutes / couple of seconds apart). Furthermore, the RAM and SWAP of the system steadily gets filled up. Once it reaches 100%, the system does not respond anymore.
To Reproduce
Disconnect the robot (power off the robot or toggle WIFI off)
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots / Log
2022-12-26 09:47:38.054 ERROR (MainThread) [custom_components.dreame_vacuum] Update failed: Traceback (most recent call last):
  File "/config/custom_components/dreame_vacuum/coordinator.py", line 314, in _async_update_data
    await self.hass.async_add_executor_job(self.device.update)
  File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/dreame_vacuum/dreame/device.py", line 982, in update
    self.connect_device()
  File "/config/custom_components/dreame_vacuum/dreame/device.py", line 714, in connect_device
    self.info = DreameVacuumDeviceInfo(self._protocol.connect())
  File "/config/custom_components/dreame_vacuum/dreame/protocol.py", line 482, in connect
    response = self.send("miIO.info", retry_count=retry_count)
  File "/config/custom_components/dreame_vacuum/dreame/protocol.py", line 509, in send
    raise DeviceException("Unable to discover the device over cloud") from None
custom_components.dreame_vacuum.dreame.exceptions.DeviceException: Unable to discover the device over cloud

2022-12-26 09:48:59.728 ERROR (MainThread) [custom_components.dreame_vacuum] Update failed: Traceback (most recent call last):
  File "/config/custom_components/dreame_vacuum/coordinator.py", line 314, in _async_update_data
    await self.hass.async_add_executor_job(self.device.update)
  File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/dreame_vacuum/dreame/device.py", line 982, in update
    self.connect_device()
  File "/config/custom_components/dreame_vacuum/dreame/device.py", line 714, in connect_device
    self.info = DreameVacuumDeviceInfo(self._protocol.connect())
  File "/config/custom_components/dreame_vacuum/dreame/protocol.py", line 482, in connect
    response = self.send("miIO.info", retry_count=retry_count)
  File "/config/custom_components/dreame_vacuum/dreame/protocol.py", line 509, in send
    raise DeviceException("Unable to discover the device over cloud") from None
custom_components.dreame_vacuum.dreame.exceptions.DeviceException: Unable to discover the device over cloud

2022-12-26 09:50:21.339 ERROR (MainThread) [custom_components.dreame_vacuum] Update failed: Traceback (most recent call last):
  File "/config/custom_components/dreame_vacuum/coordinator.py", line 314, in _async_update_data
    await self.hass.async_add_executor_job(self.device.update)
  File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/dreame_vacuum/dreame/device.py", line 982, in update
    self.connect_device()
  File "/config/custom_components/dreame_vacuum/dreame/device.py", line 714, in connect_device
    self.info = DreameVacuumDeviceInfo(self._protocol.connect())
  File "/config/custom_components/dreame_vacuum/dreame/protocol.py", line 482, in connect
    response = self.send("miIO.info", retry_count=retry_count)
  File "/config/custom_components/dreame_vacuum/dreame/protocol.py", line 509, in send
    raise DeviceException("Unable to discover the device over cloud") from None
custom_components.dreame_vacuum.dreame.exceptions.DeviceException: Unable to discover the device over cloud

2022-12-26 09:51:43.060 ERROR (MainThread) [custom_components.dreame_vacuum] Update failed: Traceback (most recent call last):
  File "/config/custom_components/dreame_vacuum/coordinator.py", line 314, in _async_update_data
    await self.hass.async_add_executor_job(self.device.update)
  File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/dreame_vacuum/dreame/device.py", line 982, in update
    self.connect_device()
  File "/config/custom_components/dreame_vacuum/dreame/device.py", line 714, in connect_device
    self.info = DreameVacuumDeviceInfo(self._protocol.connect())
  File "/config/custom_components/dreame_vacuum/dreame/protocol.py", line 482, in connect
    response = self.send("miIO.info", retry_count=retry_count)
  File "/config/custom_components/dreame_vacuum/dreame/protocol.py", line 509, in send
    raise DeviceException("Unable to discover the device over cloud") from None
custom_components.dreame_vacuum.dreame.exceptions.DeviceException: Unable to discover the device over cloud

2022-12-26 09:53:04.939 ERROR (MainThread) [custom_components.dreame_vacuum] Update failed: Traceback (most recent call last):
  File "/config/custom_components/dreame_vacuum/coordinator.py", line 314, in _async_update_data
    await self.hass.async_add_executor_job(self.device.update)
  File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/dreame_vacuum/dreame/device.py", line 982, in update
    self.connect_device()
  File "/config/custom_components/dreame_vacuum/dreame/device.py", line 714, in connect_device
    self.info = DreameVacuumDeviceInfo(self._protocol.connect())
  File "/config/custom_components/dreame_vacuum/dreame/protocol.py", line 482, in connect
    response = self.send("miIO.info", retry_count=retry_count)
  File "/config/custom_components/dreame_vacuum/dreame/protocol.py", line 509, in send
    raise DeviceException("Unable to discover the device over cloud") from None
custom_components.dreame_vacuum.dreame.exceptions.DeviceException: Unable to discover the device over cloud

2022-12-26 09:54:26.638 ERROR (MainThread) [custom_components.dreame_vacuum] Update failed: Traceback (most recent call last):
  File "/config/custom_components/dreame_vacuum/coordinator.py", line 314, in _async_update_data
    await self.hass.async_add_executor_job(self.device.update)
  File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/dreame_vacuum/dreame/device.py", line 982, in update
    self.connect_device()
  File "/config/custom_components/dreame_vacuum/dreame/device.py", line 714, in connect_device
    self.info = DreameVacuumDeviceInfo(self._protocol.connect())
  File "/config/custom_components/dreame_vacuum/dreame/protocol.py", line 482, in connect
    response = self.send("miIO.info", retry_count=retry_count)
  File "/config/custom_components/dreame_vacuum/dreame/protocol.py", line 509, in send
    raise DeviceException("Unable to discover the device over cloud") from None
custom_components.dreame_vacuum.dreame.exceptions.DeviceException: Unable to discover the device over cloud

2022-12-26 09:55:48.313 ERROR (MainThread) [custom_components.dreame_vacuum] Update failed: Traceback (most recent call last):
  File "/config/custom_components/dreame_vacuum/coordinator.py", line 314, in _async_update_data
    await self.hass.async_add_executor_job(self.device.update)
  File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/dreame_vacuum/dreame/device.py", line 982, in update
    self.connect_device()
  File "/config/custom_components/dreame_vacuum/dreame/device.py", line 714, in connect_device
    self.info = DreameVacuumDeviceInfo(self._protocol.connect())
  File "/config/custom_components/dreame_vacuum/dreame/protocol.py", line 482, in connect
    response = self.send("miIO.info", retry_count=retry_count)
  File "/config/custom_components/dreame_vacuum/dreame/protocol.py", line 509, in send
    raise DeviceException("Unable to discover the device over cloud") from None
custom_components.dreame_vacuum.dreame.exceptions.DeviceException: Unable to discover the device over cloud

Additional Information (please complete the following information)

Model Name: dreame_bot_w10
Firmware Version [e.g. 1156]:
Home Assistant Version: 2022.12.8
Configuration Type [With or without map support]: with map - cloud preferred
Errors or warnings shown in the HA logs (if applicable): (see above)

Exactly, it uses more and more memory over time (as described in the issue). See also screenshot.
After a couple of hours, the HA becomes unresponsive, once it reaches 100% (arrow). If the plugin is disabled and HA restarted, the memory stays constant.

I think this issue is related to the Force Cloud feature. If your device is at the same network with HA you don't need to enable this feature until i fix it.

Actually (sadly) I have to stick to "force cloud", since the robot is on another network.

Hello @Tasshack, I'm using a RPI3 with 1 GB of RAM and I'm also having these issues (also related to #52 and other duplicated issues).
Some more detailed info:

With default swap memory my system will start rebooting as soon as I try to add my robot.
I've increased swap memory to 2 GB. Then, I have been able to integrate my robot (117 entities, wow, kudos :smile:) and add a Xiaomi Vacuum Map Card. However, after few minutes of usage, HA is unusable, then it will start rebooting.

I think this is a very important point to analyze, also considering that a lot of people have installed HA on RPIs. Then, all of us will use your amazing work done on reverse engineering the official Mi Home.
Btw I'll follow the updates on https://github.com/Tasshack/dreame-vacuum/issues/52#issuecomment-1380478994. Let's consider that I am totally available for any further clarification on my setup.

I tried the integration without map support. It found out around 50 entities and no problem at all. I'm using HA without any trouble.

@Tasshack i'm still using the integration without map support and no problem at all. As supposed, map is the problem here.
I'm for further support if needed.

I have a hang-up problem with my RPI4  when I turn on to display "path" on map. everything works perfectly without this parameter

@StahlTim @antoniolanza1996 can you test this issue on the latest beta version.
https://github.com/Tasshack/dreame-vacuum/releases/tag/v2.0.0b5

problem persists on beta 2.0.0b5 with rpi3

I have the same issue on a Raspberry Pi 4 (4 GB) with v1.0.1. It started when I was moving furniture about and placed the robot (dreame.vacuum.p2028) upside down, causing the integration setup to fail (after reboot). Memory leak is a bit over 100 MiB/hour.
I reckon the repro steps are:

Disconnect the robot (e.g. by placing it upside down)
Reboot Home Assistant (to get integration in setup attempt loop)

The log is spammed roughly every 90 seconds with the message below. I'll try beta 2.0.0b5 to see if anything changes.
ERROR (MainThread) [custom_components.dreame_vacuum] Update failed: Traceback (most recent call last):
  File "/config/custom_components/dreame_vacuum/coordinator.py", line 314, in _async_update_data
    await self.hass.async_add_executor_job(self.device.update)
  File "/usr/local/lib/python3.11/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/dreame_vacuum/dreame/device.py", line 995, in update
    self.connect_device()
  File "/config/custom_components/dreame_vacuum/dreame/device.py", line 725, in connect_device
    self.info = DreameVacuumDeviceInfo(self._protocol.connect())
                                       ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/dreame_vacuum/dreame/protocol.py", line 487, in connect
    response = self.send("miIO.info", retry_count=retry_count)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/dreame_vacuum/dreame/protocol.py", line 519, in send
    return self.device.send(method, parameters=parameters, retry_count=retry_count)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/miio/miioprotocol.py", line 161, in send
    self.send_handshake()
  File "/usr/local/lib/python3.11/site-packages/miio/miioprotocol.py", line 74, in send_handshake
    raise DeviceException("Unable to discover the device %s" % self.ip)

This was with stable release v1.0.1 - but I'm currently testing beta 2.0.0b6.

Same problem here with 2.0.0b6 on a Debian HA core installation: After starting HA with my Dreame D10 Plus offline, the HA log is spammed with the message quoted above by @ImpieYay. This creates more and more stale CLOSE_WAIT TCP-sessions leading to a HA crash after a few hours. Low resolution map on or off doesn't make a difference here.
There must be a way to stop spamming the log and to regularly close these sessions, thus avoiding the crash - I hope ;-)

Hi, same problem for me with 2.0.0b6.
i have raspberry 3b on last raspbian light with HA 2023.10.5 core 2023.10.5.
Have an error when i add integration in version 2.0.0b6 => ": {« message »:« Invalid handler specified »}"
Error occurred loading flow for integration dreame_vacuum: No module named 'paho'

So i install paho-mqtt in my virtual python environnement
pip3 install paho-mqtt

(dont know if should setup https://www.home-assistant.io/integrations/mqtt/)
Now i can add my entitie, i setup with my Dreame credentials but have a memory problem :

And it's strange but when i desactivate my vacuum entity , the memory stay high and i should restart HA for fix the memory.
So i have more 400 MiB when i use service + vacuum entity with Dreame credentials.
When have time, i will look the code if i can help too. It's goog project.


Merge develop to master 26.10.2020

Sprint 4 implementation.

Codecov Report

Merging #9 into master will decrease coverage by 0.20%.
The diff coverage is 95.45%.

@@            Coverage Diff             @@
##           master       #9      +/-   ##
==========================================
- Coverage   96.23%   96.03%   -0.21%
==========================================
  Files           7        8       +1
  Lines         478      504      +26
  Branches       16       23       +7
==========================================
+ Hits          460      484      +24
- Misses         17       18       +1
- Partials        1        2       +1

Impacted Files
Coverage Δ

django_etuovi/etuovi.py
65.38% <0.00%> (ø)

django_etuovi/utils/xml.py
93.10% <77.77%> (ø)

django_etuovi/items.py
100.00% <100.00%> (ø)

django_etuovi/utils/testing.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Administrators Group

We need there to be an Administrators Group that allows system administrators to see private data.
Among other things, this allow PBot ExCom to see what data have been in the private sphere for a long time and needs to go public.

Changed this to low-priority because it either already exists or is trivial to add.

I think this already exists, but regardless should folded into the broader groups/upgrade in issue #94


chore: update providers

@beeme1mr I didn't verified the preview site, since it is failing on build, currently can't see why, if you have any idea you can share. thanks

Yep, looking now. There seems to be an issue with the svgs. I'll push a fix once I figure out the issue.

Okay, it looks like I need to recreate one of the svgs. I'll take care of that tomorrow.

Okay, it looks like I need to recreate one of the svgs. I'll take care of that tomorrow.

Ok, you may create new ones from some other image source if needed.

Closing in favor of #278.


Fix error when throw exception without check $response->body type.

Add private function getErrorBody for always return string for throw exception

@ht22pt thank you for contribution


🐛 [firestore-bigquery-export] Fields with the type of timestamp are imported as a string instead of a JSON struct (re-open).

This is re-opened from https://github.com/firebase/extensions/issues/1813
[READ] Step 1: Are you in the right place?
Issues filed here should be about bugs for a specific extension in this repository.
If you have a general question, need help debugging, or fall into some
other category use one of these other channels:

For general technical questions, post a question on StackOverflow
with the firebase tag.
For general Firebase discussion, use the firebase-talk
google group.
To file a bug against the Firebase Extensions platform, or for an issue affecting multiple extensions, please reach out to
Firebase support directly.

[REQUIRED] Step 2: Describe your configuration

Extension name: firestore-bigquery-export
Extension version:

Extension itself:

0.1.41

Import script:

0.1.19

Configuration values (redact info where appropriate):

[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
$ fs-bq-import-collection --version
{"severity":"WARNING","message":"Warning, FIREBASE_CONFIG and GCLOUD_PROJECT environment variables are missing. Initializing firebase-admin will fail"}
0.1.19

$ fs-bq-import-collection \
  --non-interactive \
  --project $MY_PROJECT_NAME \
  --source-collection-path users/{user_id}/bookmarks \
  --query-collection-group true \
  --dataset firestore_export \
  --table-name-prefix bookmarks \
  --batch-size 300 \
  --dataset-location us \
  --multi-threaded true \
  --use-new-snapshot-query-syntax true \
  --use-emulator false

Expected result

Actual result

It seems the latest version didn't publish on npm. I will publish it now. Thanks!

A new version is now published, 0.1.20, which should fix this. Let me know if it still occurs.

I confirmed that the issue is resolved. Thanks!


chore: semantic release dry run

Description
PR split from:

https://github.com/traefik/faency/pull/288

Adds a GH action to trigger a "dry run" of semantic release during PR review
This is an experimental proposal to run the "dry run mode" of semantic release as a github action and output the release notes inside a PR, to allow reviewers to discuss the release.

There's a run which checks against all commits of a PR, to show devs what version would be expected from their commit messages.
There's a run which checks only against a simulation of the "squash and merge" behaviour of github PRs

The goal of this experiment is to show all capabilities of the toolkit we are studying, and spark a discussion around a possible usage.
Review expected
This PR is peculiar in the sense that I don't really expect to merge it as-is.
The workflow I implemented is not battled-tested, nor optimized. It's more of a POC.
I'm even wondering if my idea brings value.
I expect your review to revolve around:

improvements
alternatives
similar ideas
usefulness

Preset: conventional-commits
Dependency changes

Dependency
Version
State

semantic-release
^19.0.2
Added

@semantic-release/commit-analyzer
^9.0.2
Added

@semantic-release/github
^8.0.2
Added

@semantic-release/npm
^9.0.0
Added

@semantic-release/release-notes-generator
^10.0.3
Added

conventional-changelog-conventionalcommits
^4.6.3
Added

semantic-release is responsible for auto-releasing PRs, following plugins are the default ones required to handle the full feature:

@semantic-release/commit-analyzer
@semantic-release/github
@semantic-release/npm
@semantic-release/release-notes-generator

conventional-changelog-conventionalcommits is the preset we use for the commit analyzer to compute the proper release version, based on commit message merged on master

How to test
The GH action will be able to run only once we merge this PR.
You can play with our test repo with the dedicated PR:

https://github.com/matthieuh/test-semantic-release/pull/7

Please note that because of our fork-PR strategy, we cannot use pull_request GH event to trigger the workflow, whereas it is possible (for the sake of playground) on the test repo

Closing as we don't have the need for this feature for now


wget in node drainer skip has stopped working

Extracted from https://github.com/kubernetes-incubator/kube-aws/issues/1105#issuecomment-363316491.
The current node drainer scripting uses wget but it seems to have some problems with 502s:
wget -O - -q http://<IP_ADDRESS>/2016-09-02/meta-data/instance-id
wget: server returned error: HTTP/1.1 502 Bad Gateway

On a Running node drainer pod, I've exec-ed to the pod and done this:
/ # wget -O - -q http://<IP_ADDRESS>/latest/meta-data/
wget: server returned error: HTTP/1.1 502 Bad Gateway

/ # curl http://<IP_ADDRESS>/latest/meta-data/
ami-id
ami-launch-index
ami-manifest-path
block-device-mapping/
hostname
[...]

Probably related issue in wget in busybox: http://svn.dd-wrt.com/ticket/5771

Thanks for reporting!
Not sure this is affecting everyone's cluster, but let's improve node drainer to use curl instead and see if it works, according to our observation in the referenced issue.

@c-knowles @mumoshu How can I solve this? I am new to K8s 😄

@c-knowles @mumoshu This happens on new nodes or nodes that recently pulled the hyperkube container image. The hyperkube doesn't contain the wgetor curl anymore.

@c-knowles @mumoshu This happens for me on new nodes or nodes that recently pulled the aws-cli container image.
bash-4.3# wget -O - -q http://<IP_ADDRESS>/2016-09-02/meta-data/instance-id
wget: error getting response
bash-4.3# apk update
fetch http://dl-cdn.alpinelinux.org/alpine/v3.6/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.6/community/x86_64/APKINDEX.tar.gz
v3.6.2-248-g3f8eeb3ea1 [http://dl-cdn.alpinelinux.org/alpine/v3.6/main]
v3.6.2-250-g51a3714b5e [http://dl-cdn.alpinelinux.org/alpine/v3.6/community]
OK: 8437 distinct packages available
bash-4.3# apk add wget
(1/1) Installing wget (1.19.2-r0)
Executing busybox-1.26.2-r9.trigger
OK: 75 MiB in 35 packages
bash-4.3# wget -O - -q http://<IP_ADDRESS>/2016-09-02/meta-data/instance-id
i-0fccf94cf2be4de7a
bash-4.3#

Not sure if mine is the same issue - if not, I'm happy to raise a separate issue but what I have seen is that from a working k8s cluster that was spun up with kube-aws, where node-drainer is all working fine and they have started fine, IF i change the instance type of worker nodes to the new c5 range (actually i only tried with c5.4xlarge) and apply so that my worker nodes are now the new instance type, the node-drainers now start to CrashLoopBackOff.
The instance type is the ONLY thing I have changed between a working node-drainers on my worker nodes.
i.e.
Working:
kube-system           kube-node-drainer-ds-6xd9r                                           1/1       Running             0          8m
kube-system           kube-node-drainer-ds-kbpgv                                           1/1       Running             0          8m
kube-system           kube-node-drainer-ds-kmr9r                                           1/1       Running             0          8m

Non-Working:
kube-system           kube-node-drainer-asg-status-updater-f9f67c9c7-w7gwg                 0/1       CrashLoopBackOff    5          5m
kube-system           kube-node-drainer-ds-58vnq                                           0/1       CrashLoopBackOff    6          8m
kube-system           kube-node-drainer-ds-qlg76                                           0/1       CrashLoopBackOff    6          8m
kube-system           kube-node-drainer-ds-scsxl                                           0/1       CrashLoopBackOff    6          8m

I have also included the node-drainer-asg-status-updater because that is also failing now on the new c5 instance types with logs showing me:
kubectl logs kube-node-drainer-asg-status-updater-f9f67c9c7-w7gwg -n kube-system
+ metadata dynamic/instance-identity/document
+ wget -O - -q http://<IP_ADDRESS>/2016-09-02/dynamic/instance-identity/document
+ jq -r .region
wget: error getting response
+ REGION=
+ [ -n  ]

node-drainer also gives me same error message.
It does sound like a different problem so let me know if a new issue is required.
I have found https://github.com/coreos/bugs/issues/2331 which is kind of related.

FYI, I just spun up test container on the same worker node (c5.4xlarge) that has the failing node-drainer pod and from that test container, the same wget that fails from node-drainer works ok.

@vaibhavsingh97 a quick way to resolve is change the wget calls in the controller config to use curl and then update your cluster with that. Longer term I think we should change the default in kube-aws so it does not always pull master.

Thanks @c-knowles for pointing it out. I will make PR 👍

Looks like there is no good alternative tag - https://quay.io/repository/coreos/awscli?tag=latest&tab=tags. @mumoshu perhaps we should build an AWS CLI image ourselves or use a different one from docker hub so we can pinned the version a bit better?

Yeah, let's build one ourselves

@mumoshu yeah ok, I will pick this item up now.

@mumoshu PR done. I haven't swapped to the new image yet, I see there's some issues on the coreos repo to get some versions pinned.

Oops!! Looks like I am late 😄 , Any other beginner issue i can solve?

@vaibhavsingh97 sorry! Lots of good first issues, I'd suggest one of https://github.com/kubernetes-incubator/kube-aws/issues/950, https://github.com/kubernetes-incubator/kube-aws/issues/1085 or https://github.com/kubernetes-incubator/kube-aws/issues/1063.

@c-knowles Thanks for the PR! I'll take a look soon.
Regarding the awscli image pinning, I've just pushed kubeaws/awscli:0.9.0 via automated-build. I'd appreciate it if you could submit PRs to change awscli used by kube-aws to that one! @vaibhavsingh97 @c-knowles
// Btw, it works like this: As soon as a git tag is pushed, the automated build for the image tag with the same value as the git tag is triggered.

@mumoshu I would happy to submit PR, Can you please redirect to the resources.


[docs]: Add documentation for Paratool deployment of E4S on Perlmutter

Please describe the issue
Please consider having a separate page in the E4S docs that show how one is to use Paratool deployment of E4S on Perlmutter.
For instance here is what i did to access one of the deployment
(penv) e4s:login34> source /global/cfs/cdirs/m3503/ParaTools/E4S/22.05/module-use.sh
(penv) e4s:login34> source /global/cfs/cdirs/m3503/ParaTools/E4S/22.05/start-spack.sh

The following have been reloaded with a version change:
  1) gcc/10.3.0 => gcc/11.2.0

==> Warning: config:module_roots has been replaced by modules:[module set]:roots and is ignored
==> Warning: Top-level properties "prefix_inspections", "default", "tcl" in module config are ignored as of Spack v0.18. They should be set on the "default" module set. Run

	$ spack config update modules

to update the file to the new format
==> Warning: config:module_roots has been replaced by modules:[module set]:roots and is ignored
==> Warning: Top-level properties "prefix_inspections", "default", "tcl" in module config are ignored as of Spack v0.18. They should be set on the "default" module set. Run

	$ spack config update modules

to update the file to the new format
==> Warning: Did not move top-level module properties into "default" module set, because the "default" module set is already defined

This i sourced this file
(penv) e4s:login34> source /global/cfs/cdirs/m3503/ParaTools/E4S/22.05/module-use.sh

Due to MODULEPATH changes, the following have been reloaded:
  1) cray-mpich/8.1.15

I can now see the module generated spack
(penv) e4s:login34> ml av

----------------------------------- /global/cfs/cdirs/m3503/ParaTools/E4S/22.05/spack/share/spack/lmod/cray-sles15-x86_64/cray-mpich/8.1.15-royouxy/Core ------------------------------------
   adios/1.13.1                   exaworks/0.1.0                      lammps/20220107-openmp        petsc/3.17.1                   (D)    strumpack/6.3.1-cuda80-openmp
   adios2/2.8.0-cuda80            faodel/1.2108.1                     libquo/1.3.1                  phist/1.9.5-openmp                    strumpack/6.3.1-openmp        (D)
   adios2/2.8.0            (D)    flecsi/1.4.2                        mercury/2.1.0          (D)    precice/2.4.0                         sundials/6.2.0-cuda80
   amrex/22.05             (D)    fortrilinos/2.0.0                   metall/0.20                   pumi/2.2.7                            sundials/6.2.0                (D)
   arborx/1.2-cuda80              globalarrays/5.8             (D)    mfem/4.4.0-cuda80             py-cinemasci/1.7.0                    superlu-dist/7.2.0-cuda80
   arborx/1.2              (D)    hdf5/1.10.7                         mfem/4.4.0             (D)    py-libensemble/0.9.1                  superlu-dist/7.2.0            (D)
   axom/0.6.1-openmp              heffte/2.2.0-cuda80                 mpifileutils/0.11.1           py-petsc4py/3.17.1                    tasmanian/7.7-cuda80-openmp
   butterflypack/2.1.1            heffte/2.2.0                 (D)    nccmp/<IP_ADDRESS>                 py-warpx/22.05-dims2                  tasmanian/7.7-openmp          (D)
   cabana/0.4.0-cuda80            hpctoolkit/2022.04.15-cuda          nco/5.0.1                     py-warpx/22.05-dims3                  tau/2.31
   cabana/0.4.0            (D)    hpctoolkit/2022.04.15        (D)    netlib-scalapack/2.2.0        py-warpx/22.05-dimsRZ          (D)    tau/2.31.1-cuda               (D)
   caliper/2.7.0-cuda80           hpx/1.7.1-cuda80                    omega-h/9.34.1                scr/3.0rc2                            trilinos/13.0.1               (D)
   caliper/2.7.0           (D)    hpx/1.7.1                    (D)    openpmd-api/0.14.4     (D)    slate/2021.05.02-cuda80-openmp        turbine/1.3.0
   conduit/0.8.3           (D)    hypre/2.24.0-cuda80                 papyrus/1.0.2          (D)    slate/2021.05.02-openmp        (D)    unifyfs/0.9.2
   darshan-runtime/3.3.1          hypre/2.24.0                 (D)    parallel-netcdf/1.12.2 (D)    slepc/3.17.1-cuda80                   veloc/1.5
   datatransferkit/3.1-rc3        kokkos-kernels/3.6.00-cuda80        parsec/3.0.2012        (D)    slepc/3.17.1                   (D)
   dyninst/12.1.0-openmp   (D)    kokkos/3.6.00-cuda80                petsc/3.17.1-cuda80           stc/0.9.0

Can you please mark us as maintainers on e4s.readthedocs.io so that we can manage this?
We would like to use this for the documentation of facility deployments as well as containers.

I believe @wspear is a maintainer. @eugenewalker please create an account on readthedocs website and you can share that with me and I can make you admin

@shahzebsiddiqui @eugeneswalker Does this look like reasonable coverage for this deployment (and a reasonable place to integrate this information for other facilities in the future)? I'm not sure it's useful to include the output of module avail for each E4S install but I can if you prefer.
http://yu.nic.uoregon.edu/~wspear/E4S/html/deployment.html

Hi @wspear can you please issue a PR so we can review it. I think you go one step further and tell what happens when you load the stack and yes it can be fine if you show output of stack.

Here's the PR. I'm not sure if I need to do anything extra to get a render of the PR in readthedocs. https://github.com/E4S-Project/e4s/pull/74

No u don't need to do anything extra it's done automatically.


source_id registration of ICTP RegCM model

label
RegCM V5 MOLOCH
label_extended
The ICTP RegCM version 5 using non hydrostatic MOLOCH dynamical core
source_id
REGCM5-0
source_type
ARCM
release_year
2023
activity_participation
DD
institution_id
ICTP
further_info_url
https://agupubs.onlinelibrary.wiley.com/doi/full/10.1029/2022JD038199
What license do you choose?
CC BY 4.0

Hi @graziano-giuliani
just to make sure that you will switch the model name (source_id) to all capitals (REGCM5-0) in the filenames and DRS in general for CORDEX-CMIP6. Is this coordinated across the RegCM community? I ask because there are plans to run previous versions of the model which, for the moment, use the RegCM mixed-case syntax, although they have not tried to register the model name yet.
https://wcrp-cordex.github.io/simulation-status/CMIP6_downscaling_plans.html?search.search=regcm
Please, could you also check the driving GCMs/scenarios and update their expected date for completion?
https://wcrp-cordex.github.io/simulation-status/CMIP6_downscaling_plans.html?search.search=ictp
(we'll change the RCM name in this list to REGCM5-0 for ICTP, if you confirm the above)

Hi Jesus. Indeed the code would be RegCM5-0, but the capitalization went without my intervention. Does the form allow for mixed case? Or is it a problem generated by my Firefox client? For the simulations, we have as of now, as mentioned in the FPSCONV meeting, some issues with the HPC platform. We hope the problems to be solved during the summer. I would thus leave the expected dates as they are, hoping for the best, and update if needed only if we have bad news from the HPC provider. Some of the simulations will be run at ORNL and HKU, and indeed we are cross waiting, us for credentials, them for the model configuration which will be run on their cluster resources. The plan is unchanged, but we cannot currently put a figure on the (now probable) delay: all simulations (except Africa) have officially started the evaluation period, but are all now on hold with only a handful of simulated years until the HPC technical issues are closed.

OK, thank you. Not sure what happened with the source_id capitalization. In principle, the template should not modify the entries. Anyway, I updated your original post to show the mixed-case version.
And thank you also for the update on your plans. I will just put some date in the future, to avoid having past expected dates. Good luck with the new HPC!

/register