INT- B-19532-approved-advance-v3

B-19532
Summary
INTEGRATION
This PR is a v3 followup to the original PR.  An issue was discovered during PO demo where a PPM is in REJECT status and advance number is modified and SAVED, the status is automatically displayed as ACCEPT when PPM view is reloaded after SAVED. This means status of REJECTED was overwritten to EDITED/ACCEPT. After consulting with Dan Matthews, it was decided the UI shall programmatically select ACCEPT if user enters a new advance number regardless if REJECT is selected. It is assumed user's intent is to ACCEPT if he/she modifies the advance request number.
Verification Steps for the Author
These are to be checked by the author.

[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] Have the Agility acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.

[ ] Has the branch been pulled in and checked out?
[ ] Have the BL acceptance criteria been met for this change?
[ ] Was the CircleCI build successful?
[ ] Has the code been reviewed from a standards and best practices point of view?

Setup to Run the Code

Instructions for starting storybook
Instructions for starting the MilMove application
Instructions for running tests

How to test
Steps to test:

Log in as Services Counselor in Office and edit shipment on PPM

Enter an amount for Amount Requested and select Approve and hit Save & Continue

Edit Shipment again and edit the Amount Requested to different number but take note of saved value. Click REJECT radio button. Note the Advance Requested input reverts back to the persisted value.

Now, change advance number again, the status should automatically change to ACCEPT from REJECT. Modifying request in REJECT assumes user wants to ACCEPT before saving.

Given I am a SC on the "Edit shipment details" page,
When I am reviewing the "Incentive & advance" area of the page,
Then when I update the advance amount,  Accept radio button is automatically selected if  Reject was previously selected.

Frontend

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, Edge).
[ ] There are no new console errors in the browser devtools.
[ ] There are no new console errors in the test output.
[ ] If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.
[ ] This change meets the standards for Section 508 compliance.

I was able to change the value and select reject by selecting reject and the pasting a new value into the amount requested field. The API returns that it took the new value and changes the advanceStatus to EDITED which shows as Approved in the UI.


InputChecker update

input_checker doesn't crash anymore when a value that's not a digit is entered.

Thx for the review, I merged! :)


[Issue] Task list is not cleared after complete task

I'm currently working with server, I found that control plane does not clear task list after complete task.
Consequently, the server runs a task repeatedly after some delay.
Here is my test code for pytest.
import pytest
import time
import logging
from llama_agents import LlamaAgentsClient

_logger: logging.Logger = logging.getLogger(__name__)

client = LlamaAgentsClient(control_plane_url="http://<IP_ADDRESS>:8001")

def get_task_list():
    taskList = client.get_tasks()
    _logger.info(f"{taskList.keys()}")

def request_task(task: str):
    _logger.info(f"QUERY :: {task}")
    return client.create_task(task_def=task)

def get_task_results(task_id: str):
    retries = 3
    delay = 10
    initial_delay = 10

    _logger.info(f"Waiting for {initial_delay} seconds before the first request.")
    time.sleep(initial_delay)

    for attempt in range(retries):
        try:
            taskResult = client.get_task_result(task_id=task_id)
            _logger.info(taskResult)
            break
        except Exception as e:
            _logger.info(f"Attempt {attempt + 1} failed: {e}")
            if attempt < retries - 1:
                time.sleep(delay)
            else:
                _logger.info("All attempts failed")

def test_run_task():
    get_task_list() # returns [] as expected.

    task_id = request_task(task="<put your query here>")

    get_task_results(task_id=task_id)

    get_task_list() # returns [task_id],  task list is not cleared.

Thanks @jp-kh-kim for submitting the issue! May I know more details about the control plane, specifically what type of orchestrator that you are using?

@nerdai
Hi Andrei :)
I'm currently using gemini-1.5-flash. Here is a part of my pytest code.
from llama_index.llms.gemini import Gemini
from llama_index.core import Settings

Settings.cheap_llm = Gemini(
    model=config["LLM"]["CHEAP_LLM_MODEL_NAME"],
    api_key=config["API"]["GOOGLE_API_KEY"],
    temperature=0,
)

def create_control_plane_server(message_queue, port):
    return ControlPlaneServer(
        host="<IP_ADDRESS>",
        port=port,
        message_queue=message_queue,
        orchestrator=AgentOrchestrator(llm=Settings.cheap_llm),
        services_retrieval_threshold=1,
    )

We've done a major refactor, and I don't think this issue is relevant anymore


[Exam] Exam management: Add database constraint to ensure that an exercise belongs only to a course OR to an exam

An exercise belongs either directly to a course OR to an exam. As we will rely in many places on this we should add a corresponding database constraint.

I don't think this is needed any more. It also works without such a constraint


hulk output.

With a directory structure like:
project /
  |
  +--static /
      |
      +--templates /
      |   |
      |   +--title.mustache
      |
      +--js /
          |
          +--templates.js

When running:
hulk static/templates/*.mustache > static/js/templates.js

the output names the template templates.static/templates/title which is illegal in JS. This is due to not getting the basename of the file first, or perhaps slugifying the path in some predictable and safe way.
The short term fix is to run:
cd static/mustache && hulk *.mustache > ../js/templates.js

Bump

Since hulk doesn't currently traverse a directory tree, I think we're fine not having to worry about name collisions. The best solution here is to just use the filename as the name of the template. I've done this in my above commit. Perhaps they'll cherry pick that one for inclusion.
If hulk ever traverses the directory tree, perhaps we'd want to namespace each file based on parent directory name.
My commit: pthrasher/hogan.js@02293aedbd92c2607ad0b58b3000dcb65ea85850

looks ok to me. @fat, what do you say?

cherry picked.

Awesome! Glad I could help. :-)


Feature/code cleanup v2

Some cleanup around navigation builder.

Current coverage is 0.00% (diff: 100%)

Merging #142 into develop will not change coverage

@@           develop   #142   diff @@
=====================================
  Files            1      1
  Lines           36     36
  Methods          0      0
  Messages         0      0
  Branches         0      0
=====================================
  Hits             0      0
  Misses          36     36
  Partials         0      0

Powered by Codecov. Last update 70b6120...cf71a75


Re-enable Portainer deployment

Once the fix the bug. If they ever fix the bug.

They fixed the bug. Gotta figure out why github is failing


feat: added entities serialization interceptor

https://github.com/mikro-orm/nestjs/issues/37

I just tested this approach and it works pretty well so far. I wonder if we should use toObject rather than toPOJO. There are minor differences between the two.

@H6LS1S when this new interceptor is used together with ClassSerializerInterceptor, are class-transformer decorators such as @Expose and @Exclude supposed to work?

Would be nice if this could be reopened, because without this mikro-orm and nestjs can't work together.

For anyone finding this issue, take a look at Automapper if you're okay with explicit mapping as it has support for NestJS and Mikro ORM via an officially supported adapter: https://automapperts.netlify.app/docs/nestjs


[5d] Research: Figure out what's needed to stand-up Diego next to DEAs

In order to be able to write stories that will help us get Diego deployed next to the DEAs, we'll spend 5 days researching the current state of Diego and how best to deploy it in our environment.
Acceptance Criteria

[ ] We've got enough information to create a backlog that results in Diego deployed in an entirely separate GovCloud account

[Addressed in https://github.com/18F/cg-atlas/issues/96]
The currently deployed CF release as of Thursday, June 16 was v234, which has a recommended Diego release v0.1463.0.  Both CF v234 and Diego v0.1463.0 have bugs that I think we should address by upgrading to a later release of CF (and thus Diego).  Notably:
CF: https://www.pivotaltracker.com/story/show/112562131
Diego: https://www.pivotaltracker.com/n/projects/1003146/stories/112308797

In order to make use of new bosh features and bug fixes as required by newer versions of CF and Diego, as ops engineers we need to verify and possibly upgrade the currently deployed bosh version.
Acceptance Criteria

[ ] Deployed bosh release is at least 225.4 as required for Diego v0.1473.0

To ensure we can adequate service customers, as ops engineers we need to appropriately size our Diego deployment.
Acceptance Criteria

[ ] Establish manifest parameters with regards to size and number of Diego cells and other components
[ ] Determine and document thresholds where sizing should be adjusted

Implementation Sketch

In order to make Diego available to platform users, as ops engineers we need to deploy Diego integrated with the existing CF deployment.
Acceptance Criteria

[ ] A concourse pipeline task that pulls in the dynamically generated CF manifest and feeds it to the Diego manifest generation script
[ ] A concourse pipeline that deploys an appropriate version of Diego for the deployed version of CF
[ ] A concourse pipeline task that runs the smoke tests to exercise diego
[ ] A concourse pipeline task that runs the acceptance tests to exercise diego

Research notes:
As of June 15, cg is on v234 (https://github.com/cloudfoundry/cf-release/releases/tag/v234), which was released on April 6
Recommended Diego version for that release is https://github.com/cloudfoundry-incubator/diego-release/tree/v0.1463.0
Recommended Garden Linux release is https://github.com/cloudfoundry-incubator/garden-linux-release/tree/v0.335.0
Recommended etcd release is https://github.com/cloudfoundry-incubator/etcd-release/releases/tag/v43

Notable since Diego 1463:

stderr through ssh:  https://www.pivotaltracker.com/n/projects/1003146/stories/112308797 fixed in 1465
Volume drivers (experimental)
Move to SQL from etcd (as of 1474 still experimental) : experimental support added starting with 1466
1468-1471 have known vulnerabilities.
cflinuxfs2 is now its own release and must be uploaded to the director first
The Garden team has recently renamed 'guardian' to 'garden-runc'
1473 requires a relatively new bosh

Since we upgraded to CF v237 in 18F/cg-atlas#96, we should look to deploying Diego v0.1472.0 or later.


For example on the product detail page all the gallery images are loaded in full size in the background for the hidden zoom modal. This is a lot of data which needs to be loaded on page load and the user might never open the zoom modal.
Good example from demo shop:
https://www.shopwaredemo.store/Fred-3-Burner-Gas-Grill/941044

Example
Possible solution: Add data-src and not src to images and load them later manually if the user opens the modal.

Hello,
thank you for creating this issue.
I have opened a ticket on our Issue Tracker for you. See the ticket link: https://issues.shopware.com/issues/NEXT-8616
Please use this ticket to track the state of your issue.

Maybe you want to take a look at this as well: https://github.com/shopware/platform/issues/847


[master] Upgrade to latest dependencies

Produced via:
./hack/update-deps.sh --upgrade
./hack/update-codegen.sh

Cron. -knative-prow-robot
/cc knative-sandbox/networking-wg-leads
/assign knative-sandbox/networking-wg-leads

/lgtm
/approve

/hold not sure if we should wait for the release cut first


some world files added

@chapulina, I am continuing this pull-up request from #644. I have included a few world files like camera, sensors, cars, tri-copter. Note: I have taken the mesh files from Google warehouse and constructed the .sdf file by referring to the tutorials on gazebosim.org.
Thanks

@addy1997
Thank you for the PR!. Could you sign-off your commits by git commit -sm <commit_message>?. More details can be found here

@addy1997
Thank you for the PR! Could you sign-off your commits by git commit -sm <commit_message>? More details can be found here

Done.

@addy1997 The changes aren't being reflected here. You also need to run git commit --amend --no-edit --signoff, and git push --force-with-lease origin ign-gazebo4.
Counting objects: 100% (59/59), done.
Delta compression using up to 4 threads
Compressing objects: 100% (40/40), done.
Writing objects: 100% (56/56), 3.75 MiB | 2.77 MiB/s, done.
Total 56 (delta 11), reused 52 (delta 9)
remote: Resolving deltas: 100% (11/11), completed with 3 local objects.
To https://github.com/addy1997/ign-gazebo.git
 + a541ebf0...400ac845 ign-gazebo4 -> ign-gazebo4 (forced update)

Yes, most of them (cars especially) have royalty-free or non-commercial licenses. I will include it while uploading on fuel.
I agree that adding more models will make the software bulky. I'll add the links and upload the models and worlds on ignition fuel.
As my inference is justified, I am closing this issue. Thanks


np.linalg.norm

I am going to port np.linalg.norm(...)

It's not same as ?

ok, you are right. that implements the L2 norm I need. I'll add the shortcut np.linalg.norm(...) just for Python  compatibility

no, after checking the code against the numpy docs, actually, the 2-norm is not the same what has been implemented in normalize(). There is no squaring of coefficients. Is that a bug?
https://het.as.utexas.edu/HET/Software/Numpy/reference/generated/numpy.linalg.norm.html

Yes, they're different.

Hi,
I also noticed that the function is missing in 0.20.5.
I think one could add a shortcut from np.linalg.norm(a) => np.sqrt(a.dot(a)) instead, which should be equivalent.
Not sure about the overloads though.
Does this make sense to you?
Take care,
Martin


add howieyuen to sig-doc-zh-owners

Please allow me to nominate myself to be an approver of sig-docs-zh.
I found most PRs got stuck because lack of'/approve' label, currently only @tengqm is active regularly, but we cannot reply on him for everything. So I open this PR to apply approver authority.
I check the community rules:

I have been a review over 1 year
58 PRs contributed: https://github.com/kubernetes/website/pulls?q=is%3Apr+is%3Amerged+author%3Ahowieyuen
90+ PRs reviewed: https://github.com/kubernetes/website/pulls?q=is%3Apr+reviewed-by%3Ahowieyuen

Please @tengqm and @sftim take a look, see whether I am eligible to be responsible for sig-docs.
Thanks.

/check-cla

/easycla

/check-cla

/easycla

/assign @tengqm

/approve
Thank you very much for stepping forward.

(Ref: my case #31206)
Maybe you need to add yourself to https://github.com/kubernetes/org/blob/main/config/kubernetes/sig-docs/teams.yaml as sig-docs-zh-reviews and sig-docs-zh-owners too. 😊

(Ref: my case #31206)
Maybe you need to add yourself to https://github.com/kubernetes/org/blob/main/config/kubernetes/sig-docs/teams.yaml as sig-docs-zh-reviews and sig-docs-zh-owners too. 😊

Thanks!

ping @sftim , please take a look~

/assign @sftim

/approve

/lgtm


Reorganizing Swarm Mode content

Signed-off-by: Mano Marks<EMAIL_ADDRESS>

cc @StefanScherer, @lucj  as an FYI

@vcoisne looking for a LGTM/merge
cc @StefanScherer, @lucj as an FYI

LGTM


How to publish robot's current floor name in the level name field of its RobotState?

I have built my own world environment, rviz panel, gazebo works fine.
However the robot cant be spawned.
The navigation file path is found, the waypoints are added. However I get the following error message.

Please advise.

Hi,
When reporting an issue, kindly provide basic information including the OS version, branch names of the various RMF packages in your workspace and the commands used to launch your world.
Having said that, in your case it looks like a process (building_map_server) has crashed on launch. Could you copy-paste the entire terminal output here?

Hi,
When reporting an issue, kindly provide basic information including the OS version, branch names of the various RMF packages in your workspace and the commands used to launch your world.
Having said that, in your case it looks like a process (building_map_server) has crashed on launch. Could you copy-paste the entire terminal output here?

Hi,
When reporting an issue, kindly provide basic information including the OS version, branch names of the various RMF packages in your workspace and the commands used to launch your world.
Having said that, in your case it looks like a process (building_map_server) has crashed on launch. Could you copy-paste the entire terminal output here?

OS version: 20.04, ros foxy
Branch: Master of rmf demos
commands used: ros2 launch demos imda.launch.xml
terminal output:
marcus@hp:~$ source ~/rmf_demos_ws/install/setup.bash
marcus@hp:~$ ros2 launch demos imda.launch.xml
[INFO] [launch]: All log files can be found below /home/marcus/.ros/log/2021-01-15-10-27-25-297489-hp-2601
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [rmf_traffic_schedule-1]: process started with pid [2603]
[INFO] [rmf_traffic_blockade-2]: process started with pid [2605]
[INFO] [building_map_server-3]: process started with pid [2607]
[INFO] [rviz2-4]: process started with pid [2609]
[INFO] [fleet_state_visualizer-5]: process started with pid [2611]
[INFO] [building_systems_visualizer-6]: process started with pid [2613]
[INFO] [rviz2-7]: process started with pid [2615]
[INFO] [door_supervisor-8]: process started with pid [2617]
[INFO] [lift_supervisor-9]: process started with pid [2619]
[INFO] [gzserver-10]: process started with pid [2621]
[INFO] [gzclient-11]: process started with pid [2623]
[INFO] [full_control-12]: process started with pid [2625]
[INFO] [robot_state_aggregator-13]: process started with pid [2627]
[rmf_traffic_blockade-2] [INFO] [1610677645.611318307] [rmf_traffic_blockade_node]: Beginning traffic blockade node
[full_control-12] [INFO] [1610677645.614957622] [tinyRobot_fleet_adapter]: Parameter [discovery_timeout] set to: 60.000000
[rmf_traffic_schedule-1] [INFO] [1610677645.618636733] [rmf_traffic_schedule_node]: Beginning traffic schedule node
[rmf_traffic_schedule-1] [INFO] [1610677645.624141219] [rmf_traffic_schedule_node]: [1] Registered query
[full_control-12] [INFO] [1610677645.634992282] [tinyRobot_fleet_adapter]: Parameter [linear_velocity] set to: 0.500000
[full_control-12] [INFO] [1610677645.635108364] [tinyRobot_fleet_adapter]: Parameter [angular_velocity] set to: 0.600000
[full_control-12] [INFO] [1610677645.635201427] [tinyRobot_fleet_adapter]: Parameter [linear_acceleration] set to: 0.750000
[full_control-12] [INFO] [1610677645.635286197] [tinyRobot_fleet_adapter]: Parameter [angular_acceleration] set to: 2.000000
[full_control-12] [INFO] [1610677645.635362101] [tinyRobot_fleet_adapter]: Parameter [footprint_radius] set to: 0.300000
[full_control-12] [INFO] [1610677645.635432209] [tinyRobot_fleet_adapter]: Parameter [vicinity_radius] set to: 1.500000
[full_control-12] [INFO] [1610677645.635500330] [tinyRobot_fleet_adapter]: Parameter [reversible] set to: 1
[full_control-12] The fleet [tinyRobot] has the following named waypoints:
[full_control-12]  -- lift_lobby
[full_control-12]  -- 12
[full_control-12]  -- 11
[full_control-12]  -- exit_lift
[full_control-12]  -- 5
[full_control-12]  -- 3
[full_control-12]  -- 4
[full_control-12]  -- 14
[full_control-12]  -- 6
[full_control-12]  -- 1
[full_control-12]  -- tinyRobot2_charger
[full_control-12]  -- 9
[full_control-12]  -- enter_lift
[full_control-12]  -- 15
[full_control-12]  -- 2
[full_control-12]  -- 7
[full_control-12]  -- 8
[full_control-12] [INFO] [1610677645.639051939] [tinyRobot_fleet_adapter]: Parameter [delay_threshold] set to: 15.000000
[full_control-12] [INFO] [1610677645.641077130] [tinyRobot_fleet_adapter]: Starting Fleet Adapter
[rmf_traffic_schedule-1] [INFO] [1610677645.861383676] [rmf_traffic_schedule_node]: [2] Registered query
[rviz2-4] [INFO] [1610677645.874506669] [viz]: VisualizerDataNode /viz started...
[gzclient-11] Gazebo multi-robot simulator, version 11.3.0
[gzclient-11] Copyright (C) 2012 Open Source Robotics Foundation.
[gzclient-11] Released under the Apache 2 License.
[gzclient-11] http://gazebosim.org
[gzclient-11]
[gzserver-10] Gazebo multi-robot simulator, version 11.3.0
[gzserver-10] Copyright (C) 2012 Open Source Robotics Foundation.
[gzserver-10] Released under the Apache 2 License.
[gzserver-10] http://gazebosim.org
[gzserver-10]
[rviz2-7] [INFO] [1610677646.148779849] [rviz2]: Stereo is NOT SUPPORTED
[rviz2-7] [INFO] [1610677646.148935820] [rviz2]: OpenGl version: 4.3 (GLSL 4.3)
[rviz2-7] [INFO] [1610677646.190915604] [rviz2]: Stereo is NOT SUPPORTED
[rviz2-4] [INFO] [1610677646.519207645] [rviz_node]: Rviz parameters updated
[fleet_state_visualizer-5] [INFO] [1610677646.522919317] [fleet_state_visualizer]: hello i am fleet state visualizer
[building_systems_visualizer-6] [INFO] [1610677646.776867417] [building_systems_visualizer]: Building systems visualizer started...
[building_map_server-3] [INFO] [1610677646.796187001] [building_map_server]: loading map path: /home/marcus/rmf_demos_ws/install/rmf_demo_maps/share/rmf_demo_maps/imda/imda.building.yaml
[gzserver-10] [INFO] [1610677647.055437788] [slotcar_tinyRobot2]: Setting nominal drive speed to: 0.500000
[gzserver-10] [INFO] [1610677647.055846090] [slotcar_tinyRobot2]: Setting nominal drive acceleration to: 0.250000
[gzserver-10] [INFO] [1610677647.055866144] [slotcar_tinyRobot2]: Setting max drive acceleration to: 0.750000
[gzserver-10] [INFO] [1610677647.055876122] [slotcar_tinyRobot2]: Setting nominal turn speed to:0.600000
[gzserver-10] [INFO] [1610677647.055885281] [slotcar_tinyRobot2]: Setting nominal turn acceleration to:1.500000
[gzserver-10] [INFO] [1610677647.055893892] [slotcar_tinyRobot2]: Setting max turn acceleration to:2.000000
[gzserver-10] [INFO] [1610677647.055902473] [slotcar_tinyRobot2]: Setting stop distance to:0.750000
[gzserver-10] [INFO] [1610677647.055911004] [slotcar_tinyRobot2]: Setting stop radius to:0.750000
[gzserver-10] [INFO] [1610677647.055919963] [slotcar_tinyRobot2]: Setting tire radius to:0.100000
[gzserver-10] [INFO] [1610677647.055928432] [slotcar_tinyRobot2]: Setting base width to: 0.320600
[gzserver-10] [INFO] [1610677647.055936185] [slotcar_tinyRobot2]: Setting nominal voltage to: 12.000000
[gzserver-10] [INFO] [1610677647.055942953] [slotcar_tinyRobot2]: Setting nominal capacity to: 24.000000
[gzserver-10] [INFO] [1610677647.055949322] [slotcar_tinyRobot2]: Setting charging current to: 2.000000
[gzserver-10] [INFO] [1610677647.055955693] [slotcar_tinyRobot2]: Setting mass to: 20.000000
[gzserver-10] [INFO] [1610677647.055962193] [slotcar_tinyRobot2]: Setting inertia to: 10.000000
[gzserver-10] [INFO] [1610677647.055968559] [slotcar_tinyRobot2]: Setting friction coefficient to: 0.300000
[gzserver-10] [INFO] [1610677647.055974791] [slotcar_tinyRobot2]: Setting nominal power to: 10.000000
[gzserver-10] [INFO] [1610677647.055986872] [slotcar_tinyRobot2]: Setting name to: tinyRobot2
[gzserver-10] [INFO] [1610677647.075901522] [slotcar_tinyRobot2]: Initialising slotcar for tinyRobot2
[gzserver-10] [INFO] [1610677647.105274160] [door]: Loading DoorPlugin for [Cargo_lift_door]
[gzserver-10] [Msg] Waiting for master.
[gzserver-10] [Msg] Connected to gazebo master @ http://<IP_ADDRESS>:11345
[gzserver-10] [Msg] Publicized address: <IP_ADDRESS>
[gzserver-10] [Msg] Loading world file [/home/marcus/rmf_demos_ws/install/rmf_demo_maps/share/rmf_demo_maps/maps/imda_world/imda.world]
[gzserver-10] Using specified value [0.5] for property [v_max_door]
[gzserver-10] Using specified value [0.3] for property [a_max_door]
[gzserver-10] Using specified value [0.15] for property [a_nom_door]
[gzserver-10] Using specified value [0.01] for property [dx_min_door]
[gzserver-10] Using specified value [500] for property [f_max_door]
[gzserver-10] Using specified attribute value [empty_joint] for property [left_joint_name]
[gzserver-10] Using specified attribute value [right_joint] for property [right_joint_name]
[gzserver-10] Using specified attribute value [SwingDoor] for property [type]
[gzserver-10] Using specified attribute value [right_joint] for property [name]
[gzserver-10] Using specified value [0] for property [lower]
[gzserver-10] Using specified value [1.57] for property [upper]
[gzserver-10] Using specified attribute value [right_joint] for property [name]
[gzserver-10] Using specified value [0] for property [lower]
[gzserver-10] Using specified value [1.57] for property [upper]
[gzserver-10] [INFO] [1610677647.111080342] [door]: Finished loading [Cargo_lift_door]
[gzserver-10] [WARN] [1610677647.111296312] [rcl.logging_rosout]: Publisher already registered for provided node name. If this is due to multiple nodes with the same name then all logs for that logger name will go out over the existing publisher. As soon as any node with that name is destructed it will unregister the publisher, preventing any further logs for that name from being published on the rosout topic.
[gzserver-10] [INFO] [1610677647.120467305] [door]: Loading DoorPlugin for [lift_door_1]
[gzserver-10] Using specified value [0.5] for property [v_max_door]
[gzserver-10] Using specified value [0.3] for property [a_max_door]
[gzserver-10] Using specified value [0.15] for property [a_nom_door]
[gzserver-10] Using specified value [0.01] for property [dx_min_door]
[gzserver-10] Using specified value [500] for property [f_max_door]
[gzserver-10] Using specified attribute value [empty_joint] for property [left_joint_name]
[gzserver-10] Using specified attribute value [right_joint] for property [right_joint_name]
[gzserver-10] Using specified attribute value [SwingDoor] for property [type]
[gzserver-10] Using specified attribute value [right_joint] for property [name]
[gzserver-10] Using specified value [0] for property [lower]
[gzserver-10] Using specified value [1.57] for property [upper]
[gzserver-10] Using specified attribute value [right_joint] for property [name]
[gzserver-10] Using specified value [0] for property [lower]
[gzserver-10] Using specified value [1.57] for property [upper]
[gzserver-10] [INFO] [1610677647.125765868] [door]: Finished loading [lift_door_1]
[gzserver-10] [WARN] [1610677647.126063475] [rcl.logging_rosout]: Publisher already registered for provided node name. If this is due to multiple nodes with the same name then all logs for that logger name will go out over the existing publisher. As soon as any node with that name is destructed it will unregister the publisher, preventing any further logs for that name from being published on the rosout topic.
[gzserver-10] [INFO] [1610677647.134629848] [door]: Loading DoorPlugin for [lift_door_2]
[gzserver-10] Using specified value [0.5] for property [v_max_door]
[gzserver-10] Using specified value [0.3] for property [a_max_door]
[gzserver-10] Using specified value [0.15] for property [a_nom_door]
[gzserver-10] Using specified value [0.01] for property [dx_min_door]
[gzserver-10] Using specified value [500] for property [f_max_door]
[gzserver-10] Using specified attribute value [empty_joint] for property [left_joint_name]
[gzserver-10] Using specified attribute value [right_joint] for property [right_joint_name]
[gzserver-10] Using specified attribute value [SwingDoor] for property [type]
[gzserver-10] Using specified attribute value [right_joint] for property [name]
[gzserver-10] Using specified value [0] for property [lower]
[gzserver-10] Using specified value [1.57] for property [upper]
[gzserver-10] Using specified attribute value [right_joint] for property [name]
[gzserver-10] Using specified value [0] for property [lower]
[gzserver-10] Using specified value [1.57] for property [upper]
[gzserver-10] [INFO] [1610677647.139641741] [door]: Finished loading [lift_door_2]
[gzserver-10] [WARN] [1610677647.139885978] [rcl.logging_rosout]: Publisher already registered for provided node name. If this is due to multiple nodes with the same name then all logs for that logger name will go out over the existing publisher. As soon as any node with that name is destructed it will unregister the publisher, preventing any further logs for that name from being published on the rosout topic.
[gzserver-10] [INFO] [1610677647.151255158] [door]: Loading DoorPlugin for [lift_door_3]
[gzserver-10] Using specified value [0.5] for property [v_max_door]
[gzserver-10] Using specified value [0.3] for property [a_max_door]
[gzserver-10] Using specified value [0.15] for property [a_nom_door]
[gzserver-10] Using specified value [0.01] for property [dx_min_door]
[gzserver-10] Using specified value [500] for property [f_max_door]
[gzserver-10] Using specified attribute value [empty_joint] for property [left_joint_name]
[gzserver-10] Using specified attribute value [right_joint] for property [right_joint_name]
[gzserver-10] Using specified attribute value [SwingDoor] for property [type]
[gzserver-10] Using specified attribute value [right_joint] for property [name]
[gzserver-10] Using specified value [0] for property [lower]
[gzserver-10] Using specified value [1.57] for property [upper]
[gzserver-10] Using specified attribute value [right_joint] for property [name]
[gzserver-10] Using specified value [0] for property [lower]
[gzserver-10] Using specified value [1.57] for property [upper]
[gzserver-10] [INFO] [1610677647.156829928] [door]: Finished loading [lift_door_3]
[gzserver-10] [WARN] [1610677647.157090954] [rcl.logging_rosout]: Publisher already registered for provided node name. If this is due to multiple nodes with the same name then all logs for that logger name will go out over the existing publisher. As soon as any node with that name is destructed it will unregister the publisher, preventing any further logs for that name from being published on the rosout topic.
[gzserver-10] [INFO] [1610677647.166015357] [door]: Loading DoorPlugin for [lift_door_6]
[gzserver-10] Using specified value [0.5] for property [v_max_door]
[gzserver-10] Using specified value [0.3] for property [a_max_door]
[gzserver-10] Using specified value [0.15] for property [a_nom_door]
[gzserver-10] Using specified value [0.01] for property [dx_min_door]
[gzserver-10] Using specified value [500] for property [f_max_door]
[gzserver-10] Using specified attribute value [left_joint] for property [left_joint_name]
[gzserver-10] Using specified attribute value [empty_joint] for property [right_joint_name]
[gzserver-10] Using specified attribute value [SwingDoor] for property [type]
[gzserver-10] Using specified attribute value [left_joint] for property [name]
[gzserver-10] Using specified value [-1.57] for property [lower]
[gzserver-10] Using specified value [0] for property [upper]
[gzserver-10] Using specified attribute value [left_joint] for property [name]
[gzserver-10] Using specified value [-1.57] for property [lower]
[gzserver-10] Using specified value [0] for property [upper]
[gzserver-10] [INFO] [1610677647.175446786] [door]: Finished loading [lift_door_6]
[gzserver-10] [WARN] [1610677647.175979493] [rcl.logging_rosout]: Publisher already registered for provided node name. If this is due to multiple nodes with the same name then all logs for that logger name will go out over the existing publisher. As soon as any node with that name is destructed it will unregister the publisher, preventing any further logs for that name from being published on the rosout topic.
[building_map_server-3] Traceback (most recent call last):
[building_map_server-3]   File "/home/marcus/rmf_demos_ws/install/building_map_tools/lib/building_map_tools/building_map_server", line 11, in
[building_map_server-3]     load_entry_point('building-map-tools==0.0.0', 'console_scripts', 'building_map_server')()
[building_map_server-3]   File "/home/marcus/rmf_demos_ws/install/building_map_tools/lib/python3.8/site-packages/building_map_server/building_map_server.py", line 206, in main
[building_map_server-3]     n = BuildingMapServer(map_path)
[building_map_server-3]   File "/home/marcus/rmf_demos_ws/install/building_map_tools/lib/python3.8/site-packages/building_map_server/building_map_server.py", line 46, in init
[building_map_server-3]     self.map_msg = self.building_map_msg(self.building)
[building_map_server-3]   File "/home/marcus/rmf_demos_ws/install/building_map_tools/lib/python3.8/site-packages/building_map_server/building_map_server.py", line 71, in building_map_msg
[building_map_server-3]     msg.levels.append(self.level_msg(level_data))
[building_map_server-3]   File "/home/marcus/rmf_demos_ws/install/building_map_tools/lib/python3.8/site-packages/building_map_server/building_map_server.py", line 135, in level_msg
[building_map_server-3]     gn.name = v[2]['name']
[building_map_server-3]   File "/home/marcus/rmf_demos_ws/install/building_map_msgs/lib/python3.8/site-packages/building_map_msgs/msg/_graph_node.py", line 167, in name
[building_map_server-3]     assert
[building_map_server-3] AssertionError: The 'name' field must be of type 'str'
[gzserver-10] [INFO] [1610677647.188789468] [door]: Loading DoorPlugin for [lift_door_5]
[gzserver-10] Using specified value [0.5] for property [v_max_door]
[gzserver-10] Using specified value [0.3] for property [a_max_door]
[gzserver-10] Using specified value [0.15] for property [a_nom_door]
[gzserver-10] Using specified value [0.01] for property [dx_min_door]
[gzserver-10] Using specified value [500] for property [f_max_door]
[gzserver-10] Using specified attribute value [left_joint] for property [left_joint_name]
[gzserver-10] Using specified attribute value [empty_joint] for property [right_joint_name]
[gzserver-10] Using specified attribute value [SwingDoor] for property [type]
[gzserver-10] Using specified attribute value [left_joint] for property [name]
[gzserver-10] Using specified value [-1.57] for property [lower]
[gzserver-10] Using specified value [0] for property [upper]
[gzserver-10] Using specified attribute value [left_joint] for property [name]
[gzserver-10] Using specified value [-1.57] for property [lower]
[gzserver-10] Using specified value [0] for property [upper]
[gzserver-10] [INFO] [1610677647.195628741] [door]: Finished loading [lift_door_5]
[gzserver-10] [WARN] [1610677647.195976671] [rcl.logging_rosout]: Publisher already registered for provided node name. If this is due to multiple nodes with the same name then all logs for that logger name will go out over the existing publisher. As soon as any node with that name is destructed it will unregister the publisher, preventing any further logs for that name from being published on the rosout topic.
[gzserver-10] [INFO] [1610677647.207358466] [door]: Loading DoorPlugin for [lift_door_4]
[gzserver-10] Using specified value [0.5] for property [v_max_door]
[gzserver-10] Using specified value [0.3] for property [a_max_door]
[gzserver-10] Using specified value [0.15] for property [a_nom_door]
[gzserver-10] Using specified value [0.01] for property [dx_min_door]
[gzserver-10] Using specified value [500] for property [f_max_door]
[gzserver-10] Using specified attribute value [left_joint] for property [left_joint_name]
[gzserver-10] Using specified attribute value [empty_joint] for property [right_joint_name]
[gzserver-10] Using specified attribute value [SwingDoor] for property [type]
[gzserver-10] Using specified attribute value [left_joint] for property [name]
[gzserver-10] Using specified value [-1.57] for property [lower]
[gzserver-10] Using specified value [0] for property [upper]
[gzserver-10] Using specified attribute value [left_joint] for property [name]
[gzserver-10] Using specified value [-1.57] for property [lower]
[gzserver-10] Using specified value [0] for property [upper]
[gzserver-10] [INFO] [1610677647.215892814] [door]: Finished loading [lift_door_4]
[gzserver-10] [WARN] [1610677647.216242705] [rcl.logging_rosout]: Publisher already registered for provided node name. If this is due to multiple nodes with the same name then all logs for that logger name will go out over the existing publisher. As soon as any node with that name is destructed it will unregister the publisher, preventing any further logs for that name from being published on the rosout topic.
[gzserver-10] [INFO] [1610677647.226037079] [door]: Loading DoorPlugin for [ShaftDoor_Lift1_L6_lift_door]
[gzserver-10] Using specified value [0.3] for property [v_max_door]
[gzserver-10] Using specified value [0.2] for property [a_max_door]
[gzserver-10] Using specified value [0.1] for property [a_nom_door]
[gzserver-10] Using specified value [0.0001] for property [dx_min_door]
[gzserver-10] Using specified value [35] for property [f_max_door]
[gzserver-10] Using specified attribute value [left_joint] for property [left_joint_name]
[gzserver-10] Using specified attribute value [right_joint] for property [right_joint_name]
[gzserver-10] Using specified attribute value [DoubleSlidingDoor] for property [type]
[gzserver-10] Using specified attribute value [right_joint] for property [name]
[gzserver-10] Using specified value [0] for property [lower]
[gzserver-10] Using specified value [0.5] for property [upper]
[gzserver-10] Using specified attribute value [right_joint] for property [name]
[gzserver-10] Using specified value [0] for property [lower]
[gzserver-10] Using specified value [0.5] for property [upper]
[gzserver-10] Using specified attribute value [left_joint] for property [name]
[gzserver-10] Using specified value [-0.5] for property [lower]
[gzserver-10] Using specified value [0] for property [upper]
[gzserver-10] Using specified attribute value [ramp_joint] for property [name]
[gzserver-10] [INFO] [1610677647.233926577] [door]: Finished loading [ShaftDoor_Lift1_L6_lift_door]
[gzserver-10] [WARN] [1610677647.234256122] [rcl.logging_rosout]: Publisher already registered for provided node name. If this is due to multiple nodes with the same name then all logs for that logger name will go out over the existing publisher. As soon as any node with that name is destructed it will unregister the publisher, preventing any further logs for that name from being published on the rosout topic.
[gzserver-10] [INFO] [1610677647.245361252] [door]: Loading DoorPlugin for [ShaftDoor_Lift1_L7_lift_door]
[gzserver-10] Using specified value [0.3] for property [v_max_door]
[gzserver-10] Using specified value [0.2] for property [a_max_door]
[gzserver-10] Using specified value [0.1] for property [a_nom_door]
[gzserver-10] Using specified value [0.0001] for property [dx_min_door]
[gzserver-10] Using specified value [35] for property [f_max_door]
[gzserver-10] Using specified attribute value [left_joint] for property [left_joint_name]
[gzserver-10] Using specified attribute value [right_joint] for property [right_joint_name]
[gzserver-10] Using specified attribute value [DoubleSlidingDoor] for property [type]
[gzserver-10] Using specified attribute value [right_joint] for property [name]
[gzserver-10] Using specified value [0] for property [lower]
[gzserver-10] Using specified value [0.5] for property [upper]
[gzserver-10] Using specified attribute value [right_joint] for property [name]
[gzserver-10] Using specified value [0] for property [lower]
[gzserver-10] Using specified value [0.5] for property [upper]
[gzserver-10] Using specified attribute value [left_joint] for property [name]
[gzserver-10] Using specified value [-0.5] for property [lower]
[gzserver-10] Using specified value [0] for property [upper]
[gzserver-10] Using specified attribute value [ramp_joint] for property [name]
[gzserver-10] [INFO] [1610677647.255045911] [door]: Finished loading [ShaftDoor_Lift1_L7_lift_door]
[ERROR] [building_map_server-3]: process has died [pid 2607, exit code 1, cmd '/home/marcus/rmf_demos_ws/install/building_map_tools/lib/building_map_tools/building_map_server /home/marcus/rmf_demos_ws/install/rmf_demo_maps/share/rmf_demo_maps/imda/imda.building.yaml --ros-args'].
[gzserver-10] [INFO] [1610677647.288554575] [lift]: Loading LiftPlugin for [Lift1]
[gzserver-10] Using specified value [2] for property [v_max_cabin]
[gzserver-10] Using specified value [1.2] for property [a_max_cabin]
[gzserver-10] Using specified value [1] for property [a_nom_cabin]
[gzserver-10] Using specified value [0.001] for property [dx_min_cabin]
[gzserver-10] Using specified value [25323] for property [f_max_cabin]
[gzserver-10] Using specified value [cabin_joint] for property [cabin_joint_name]
[gzserver-10] Using specified attribute value [L6] for property [name]
[gzserver-10] Using specified attribute value [-20] for property [elevation]
[gzserver-10] Using specified attribute value [CabinDoor_Lift1_lift_door] for property [cabin_door]
[gzserver-10] Using specified attribute value [ShaftDoor_Lift1_L6_lift_door] for property [shaft_door]
[gzserver-10] Using specified attribute value [L7] for property [name]
[gzserver-10] Using specified attribute value [0] for property [elevation]
[gzserver-10] Using specified attribute value [CabinDoor_Lift1_lift_door] for property [cabin_door]
[gzserver-10] Using specified attribute value [ShaftDoor_Lift1_L7_lift_door] for property [shaft_door]
[gzserver-10] Using specified value [L6] for property [initial_floor]
[gzserver-10] Loaded lift: Lift1
[gzserver-10] Names  |  Elevations
[gzserver-10] L7  |  0
[gzserver-10] L6  |  -20
[gzserver-10] [INFO] [1610677647.294367184] [lift]: Finished loading [Lift1]
[gzserver-10] [WARN] [1610677647.294589433] [rcl.logging_rosout]: Publisher already registered for provided node name. If this is due to multiple nodes with the same name then all logs for that logger name will go out over the existing publisher. As soon as any node with that name is destructed it will unregister the publisher, preventing any further logs for that name from being published on the rosout topic.
[gzserver-10] [INFO] [1610677647.306105802] [door]: Loading DoorPlugin for [CabinDoor_Lift1_lift_door]
[gzserver-10] Using specified value [0.3] for property [v_max_door]
[gzserver-10] Using specified value [0.2] for property [a_max_door]
[gzserver-10] Using specified value [0.1] for property [a_nom_door]
[gzserver-10] Using specified value [0.0001] for property [dx_min_door]
[gzserver-10] Using specified value [35] for property [f_max_door]
[gzserver-10] Using specified attribute value [left_joint] for property [left_joint_name]
[gzserver-10] Using specified attribute value [right_joint] for property [right_joint_name]
[gzserver-10] Using specified attribute value [DoubleSlidingDoor] for property [type]
[gzserver-10] Using specified attribute value [right_joint] for property [name]
[gzserver-10] Using specified value [0] for property [lower]
[gzserver-10] Using specified value [0.5] for property [upper]
[gzserver-10] Using specified attribute value [right_joint] for property [name]
[gzserver-10] Using specified value [0] for property [lower]
[gzserver-10] Using specified value [0.5] for property [upper]
[gzserver-10] Using specified attribute value [left_joint] for property [name]
[gzserver-10] Using specified value [-0.5] for property [lower]
[gzserver-10] Using specified value [0] for property [upper]
[gzserver-10] [INFO] [1610677647.316474356] [door]: Finished loading [CabinDoor_Lift1_lift_door]
[rviz2-7] [INFO] [1610677647.829294312] [rmf_panel]: Loading tinyRobot..
[rmf_traffic_schedule-1] [INFO] [1610677647.829808176] [rmf_traffic_schedule_node]: Registered participant [0] named [tinyRobot2] owned by [tinyRobot]
[full_control-12] [INFO] [1610677647.830707833] [tinyRobot_fleet_adapter]: Added a robot named [tinyRobot2] with participant ID [0]
[rviz2-7] Nav File Path Found: /home/marcus/rmf_demos_ws/install/rmf_demo_maps/share/rmf_demo_maps/maps/imda_world/nav_graphs/0.yaml
[rviz2-7] Adding waypoint [1] as a parking spot
[rviz2-7] Adding waypoint [3] as a parking spot
[rviz2-7] Adding waypoint [16] as a parking spot
[rviz2-7] Adding waypoint [17] as a parking spot
[rviz2-7] Named waypoints:
[rviz2-7]  -- [lift_lobby]
[rviz2-7]  -- [12]
[rviz2-7]  -- [11]
[rviz2-7]  -- [exit_lift]
[rviz2-7]  -- [5]
[rviz2-7]  -- [3]
[rviz2-7]  -- [4]
[rviz2-7]  -- [14]
[rviz2-7]  -- [6]
[rviz2-7]  -- [1]
[rviz2-7]  -- [tinyRobot2_charger]
[rviz2-7]  -- [9]
[rviz2-7]  -- [enter_lift]
[rviz2-7]  -- [15]
[rviz2-7]  -- [2]
[rviz2-7]  -- [7]
[rviz2-7]  -- [8]
[rviz2-7] [INFO] [1610677647.863111655] [rmf_panel]: New Fleet found, refreshing...
[full_control-12] [ERROR] [1610677648.330803689] [tinyRobot_fleet_adapter]: Robot named [tinyRobot2] belonging to fleet [tinyRobot] is lost because we cannot figure out what floor it is on. Please publish the robot's current floor name in the level_name field of its RobotState.
[gzclient-11] [INFO] [1610677648.536276686] [gazebo_ros_node]: ROS was initialized without arguments.
[rviz2-7] [INFO] [1610677648.640713917] [lift_panel_session_node]: New lift [Lift1] found, refreshing...
[full_control-12] [ERROR] [1610677648.834471256] [tinyRobot_fleet_adapter]: Robot named [tinyRobot2] belonging to fleet [tinyRobot] is lost because we cannot figure out what floor it is on. Please publish the robot's current floor name in the level_name field of its RobotState.
[full_control-12] [ERROR] [1610677649.337084918] [tinyRobot_fleet_adapter]: Robot named [tinyRobot2] belonging to fleet [tinyRobot] is lost because we cannot figure out what floor it is on. Please publish the robot's current floor name in the level_name field of its RobotState.

Hi,
When reporting an issue, kindly provide basic information including the OS version, branch names of the various RMF packages in your workspace and the commands used to launch your world.
Having said that, in your case it looks like a process (building_map_server) has crashed on launch. Could you copy-paste the entire terminal output here?

OS version: 20.04, ros foxy
Branch: Master of rmf demos
commands used: ros2 launch demos imda.launch.xml
terminal output:
marcus@hp:~$ source ~/rmf_demos_ws/install/setup.bash
marcus@hp:~$ ros2 launch demos imda.launch.xml
[INFO] [launch]: All log files can be found below /home/marcus/.ros/log/2021-01-15-10-27-25-297489-hp-2601
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [rmf_traffic_schedule-1]: process started with pid [2603]
[INFO] [rmf_traffic_blockade-2]: process started with pid [2605]
[INFO] [building_map_server-3]: process started with pid [2607]
[INFO] [rviz2-4]: process started with pid [2609]
[INFO] [fleet_state_visualizer-5]: process started with pid [2611]
[INFO] [building_systems_visualizer-6]: process started with pid [2613]
[INFO] [rviz2-7]: process started with pid [2615]
[INFO] [door_supervisor-8]: process started with pid [2617]
[INFO] [lift_supervisor-9]: process started with pid [2619]
[INFO] [gzserver-10]: process started with pid [2621]
[INFO] [gzclient-11]: process started with pid [2623]
[INFO] [full_control-12]: process started with pid [2625]
[INFO] [robot_state_aggregator-13]: process started with pid [2627]
[rmf_traffic_blockade-2] [INFO] [1610677645.611318307] [rmf_traffic_blockade_node]: Beginning traffic blockade node
[full_control-12] [INFO] [1610677645.614957622] [tinyRobot_fleet_adapter]: Parameter [discovery_timeout] set to: 60.000000
[rmf_traffic_schedule-1] [INFO] [1610677645.618636733] [rmf_traffic_schedule_node]: Beginning traffic schedule node
[rmf_traffic_schedule-1] [INFO] [1610677645.624141219] [rmf_traffic_schedule_node]: [1] Registered query
[full_control-12] [INFO] [1610677645.634992282] [tinyRobot_fleet_adapter]: Parameter [linear_velocity] set to: 0.500000
[full_control-12] [INFO] [1610677645.635108364] [tinyRobot_fleet_adapter]: Parameter [angular_velocity] set to: 0.600000
[full_control-12] [INFO] [1610677645.635201427] [tinyRobot_fleet_adapter]: Parameter [linear_acceleration] set to: 0.750000
[full_control-12] [INFO] [1610677645.635286197] [tinyRobot_fleet_adapter]: Parameter [angular_acceleration] set to: 2.000000
[full_control-12] [INFO] [1610677645.635362101] [tinyRobot_fleet_adapter]: Parameter [footprint_radius] set to: 0.300000
[full_control-12] [INFO] [1610677645.635432209] [tinyRobot_fleet_adapter]: Parameter [vicinity_radius] set to: 1.500000
[full_control-12] [INFO] [1610677645.635500330] [tinyRobot_fleet_adapter]: Parameter [reversible] set to: 1
[full_control-12] The fleet [tinyRobot] has the following named waypoints:
[full_control-12]  -- lift_lobby
[full_control-12]  -- 12
[full_control-12]  -- 11
[full_control-12]  -- exit_lift
[full_control-12]  -- 5
[full_control-12]  -- 3
[full_control-12]  -- 4
[full_control-12]  -- 14
[full_control-12]  -- 6
[full_control-12]  -- 1
[full_control-12]  -- tinyRobot2_charger
[full_control-12]  -- 9
[full_control-12]  -- enter_lift
[full_control-12]  -- 15
[full_control-12]  -- 2
[full_control-12]  -- 7
[full_control-12]  -- 8
[full_control-12] [INFO] [1610677645.639051939] [tinyRobot_fleet_adapter]: Parameter [delay_threshold] set to: 15.000000
[full_control-12] [INFO] [1610677645.641077130] [tinyRobot_fleet_adapter]: Starting Fleet Adapter
[rmf_traffic_schedule-1] [INFO] [1610677645.861383676] [rmf_traffic_schedule_node]: [2] Registered query
[rviz2-4] [INFO] [1610677645.874506669] [viz]: VisualizerDataNode /viz started...
[gzclient-11] Gazebo multi-robot simulator, version 11.3.0
[gzclient-11] Copyright (C) 2012 Open Source Robotics Foundation.
[gzclient-11] Released under the Apache 2 License.
[gzclient-11] http://gazebosim.org
[gzclient-11]
[gzserver-10] Gazebo multi-robot simulator, version 11.3.0
[gzserver-10] Copyright (C) 2012 Open Source Robotics Foundation.
[gzserver-10] Released under the Apache 2 License.
[gzserver-10] http://gazebosim.org
[gzserver-10]
[rviz2-7] [INFO] [1610677646.148779849] [rviz2]: Stereo is NOT SUPPORTED
[rviz2-7] [INFO] [1610677646.148935820] [rviz2]: OpenGl version: 4.3 (GLSL 4.3)
[rviz2-7] [INFO] [1610677646.190915604] [rviz2]: Stereo is NOT SUPPORTED
[rviz2-4] [INFO] [1610677646.519207645] [rviz_node]: Rviz parameters updated
[fleet_state_visualizer-5] [INFO] [1610677646.522919317] [fleet_state_visualizer]: hello i am fleet state visualizer
[building_systems_visualizer-6] [INFO] [1610677646.776867417] [building_systems_visualizer]: Building systems visualizer started...
[building_map_server-3] [INFO] [1610677646.796187001] [building_map_server]: loading map path: /home/marcus/rmf_demos_ws/install/rmf_demo_maps/share/rmf_demo_maps/imda/imda.building.yaml
[gzserver-10] [INFO] [1610677647.055437788] [slotcar_tinyRobot2]: Setting nominal drive speed to: 0.500000
[gzserver-10] [INFO] [1610677647.055846090] [slotcar_tinyRobot2]: Setting nominal drive acceleration to: 0.250000
[gzserver-10] [INFO] [1610677647.055866144] [slotcar_tinyRobot2]: Setting max drive acceleration to: 0.750000
[gzserver-10] [INFO] [1610677647.055876122] [slotcar_tinyRobot2]: Setting nominal turn speed to:0.600000
[gzserver-10] [INFO] [1610677647.055885281] [slotcar_tinyRobot2]: Setting nominal turn acceleration to:1.500000
[gzserver-10] [INFO] [1610677647.055893892] [slotcar_tinyRobot2]: Setting max turn acceleration to:2.000000
[gzserver-10] [INFO] [1610677647.055902473] [slotcar_tinyRobot2]: Setting stop distance to:0.750000
[gzserver-10] [INFO] [1610677647.055911004] [slotcar_tinyRobot2]: Setting stop radius to:0.750000
[gzserver-10] [INFO] [1610677647.055919963] [slotcar_tinyRobot2]: Setting tire radius to:0.100000
[gzserver-10] [INFO] [1610677647.055928432] [slotcar_tinyRobot2]: Setting base width to: 0.320600
[gzserver-10] [INFO] [1610677647.055936185] [slotcar_tinyRobot2]: Setting nominal voltage to: 12.000000
[gzserver-10] [INFO] [1610677647.055942953] [slotcar_tinyRobot2]: Setting nominal capacity to: 24.000000
[gzserver-10] [INFO] [1610677647.055949322] [slotcar_tinyRobot2]: Setting charging current to: 2.000000
[gzserver-10] [INFO] [1610677647.055955693] [slotcar_tinyRobot2]: Setting mass to: 20.000000
[gzserver-10] [INFO] [1610677647.055962193] [slotcar_tinyRobot2]: Setting inertia to: 10.000000
[gzserver-10] [INFO] [1610677647.055968559] [slotcar_tinyRobot2]: Setting friction coefficient to: 0.300000
[gzserver-10] [INFO] [1610677647.055974791] [slotcar_tinyRobot2]: Setting nominal power to: 10.000000
[gzserver-10] [INFO] [1610677647.055986872] [slotcar_tinyRobot2]: Setting name to: tinyRobot2
[gzserver-10] [INFO] [1610677647.075901522] [slotcar_tinyRobot2]: Initialising slotcar for tinyRobot2
[gzserver-10] [INFO] [1610677647.105274160] [door]: Loading DoorPlugin for [Cargo_lift_door]
[gzserver-10] [Msg] Waiting for master.
[gzserver-10] [Msg] Connected to gazebo master @ http://<IP_ADDRESS>:11345
[gzserver-10] [Msg] Publicized address: <IP_ADDRESS>
[gzserver-10] [Msg] Loading world file [/home/marcus/rmf_demos_ws/install/rmf_demo_maps/share/rmf_demo_maps/maps/imda_world/imda.world]
[gzserver-10] Using specified value [0.5] for property [v_max_door]
[gzserver-10] Using specified value [0.3] for property [a_max_door]
[gzserver-10] Using specified value [0.15] for property [a_nom_door]
[gzserver-10] Using specified value [0.01] for property [dx_min_door]
[gzserver-10] Using specified value [500] for property [f_max_door]
[gzserver-10] Using specified attribute value [empty_joint] for property [left_joint_name]
[gzserver-10] Using specified attribute value [right_joint] for property [right_joint_name]
[gzserver-10] Using specified attribute value [SwingDoor] for property [type]
[gzserver-10] Using specified attribute value [right_joint] for property [name]
[gzserver-10] Using specified value [0] for property [lower]
[gzserver-10] Using specified value [1.57] for property [upper]
[gzserver-10] Using specified attribute value [right_joint] for property [name]
[gzserver-10] Using specified value [0] for property [lower]
[gzserver-10] Using specified value [1.57] for property [upper]
[gzserver-10] [INFO] [1610677647.111080342] [door]: Finished loading [Cargo_lift_door]
[gzserver-10] [WARN] [1610677647.111296312] [rcl.logging_rosout]: Publisher already registered for provided node name. If this is due to multiple nodes with the same name then all logs for that logger name will go out over the existing publisher. As soon as any node with that name is destructed it will unregister the publisher, preventing any further logs for that name from being published on the rosout topic.
[gzserver-10] [INFO] [1610677647.120467305] [door]: Loading DoorPlugin for [lift_door_1]
[gzserver-10] Using specified value [0.5] for property [v_max_door]
[gzserver-10] Using specified value [0.3] for property [a_max_door]
[gzserver-10] Using specified value [0.15] for property [a_nom_door]
[gzserver-10] Using specified value [0.01] for property [dx_min_door]
[gzserver-10] Using specified value [500] for property [f_max_door]
[gzserver-10] Using specified attribute value [empty_joint] for property [left_joint_name]
[gzserver-10] Using specified attribute value [right_joint] for property [right_joint_name]
[gzserver-10] Using specified attribute value [SwingDoor] for property [type]
[gzserver-10] Using specified attribute value [right_joint] for property [name]
[gzserver-10] Using specified value [0] for property [lower]
[gzserver-10] Using specified value [1.57] for property [upper]
[gzserver-10] Using specified attribute value [right_joint] for property [name]
[gzserver-10] Using specified value [0] for property [lower]
[gzserver-10] Using specified value [1.57] for property [upper]
[gzserver-10] [INFO] [1610677647.125765868] [door]: Finished loading [lift_door_1]
[gzserver-10] [WARN] [1610677647.126063475] [rcl.logging_rosout]: Publisher already registered for provided node name. If this is due to multiple nodes with the same name then all logs for that logger name will go out over the existing publisher. As soon as any node with that name is destructed it will unregister the publisher, preventing any further logs for that name from being published on the rosout topic.
[gzserver-10] [INFO] [1610677647.134629848] [door]: Loading DoorPlugin for [lift_door_2]
[gzserver-10] Using specified value [0.5] for property [v_max_door]
[gzserver-10] Using specified value [0.3] for property [a_max_door]
[gzserver-10] Using specified value [0.15] for property [a_nom_door]
[gzserver-10] Using specified value [0.01] for property [dx_min_door]
[gzserver-10] Using specified value [500] for property [f_max_door]
[gzserver-10] Using specified attribute value [empty_joint] for property [left_joint_name]
[gzserver-10] Using specified attribute value [right_joint] for property [right_joint_name]
[gzserver-10] Using specified attribute value [SwingDoor] for property [type]
[gzserver-10] Using specified attribute value [right_joint] for property [name]
[gzserver-10] Using specified value [0] for property [lower]
[gzserver-10] Using specified value [1.57] for property [upper]
[gzserver-10] Using specified attribute value [right_joint] for property [name]
[gzserver-10] Using specified value [0] for property [lower]
[gzserver-10] Using specified value [1.57] for property [upper]
[gzserver-10] [INFO] [1610677647.139641741] [door]: Finished loading [lift_door_2]
[gzserver-10] [WARN] [1610677647.139885978] [rcl.logging_rosout]: Publisher already registered for provided node name. If this is due to multiple nodes with the same name then all logs for that logger name will go out over the existing publisher. As soon as any node with that name is destructed it will unregister the publisher, preventing any further logs for that name from being published on the rosout topic.
[gzserver-10] [INFO] [1610677647.151255158] [door]: Loading DoorPlugin for [lift_door_3]
[gzserver-10] Using specified value [0.5] for property [v_max_door]
[gzserver-10] Using specified value [0.3] for property [a_max_door]
[gzserver-10] Using specified value [0.15] for property [a_nom_door]
[gzserver-10] Using specified value [0.01] for property [dx_min_door]
[gzserver-10] Using specified value [500] for property [f_max_door]
[gzserver-10] Using specified attribute value [empty_joint] for property [left_joint_name]
[gzserver-10] Using specified attribute value [right_joint] for property [right_joint_name]
[gzserver-10] Using specified attribute value [SwingDoor] for property [type]
[gzserver-10] Using specified attribute value [right_joint] for property [name]
[gzserver-10] Using specified value [0] for property [lower]
[gzserver-10] Using specified value [1.57] for property [upper]
[gzserver-10] Using specified attribute value [right_joint] for property [name]
[gzserver-10] Using specified value [0] for property [lower]
[gzserver-10] Using specified value [1.57] for property [upper]
[gzserver-10] [INFO] [1610677647.156829928] [door]: Finished loading [lift_door_3]
[gzserver-10] [WARN] [1610677647.157090954] [rcl.logging_rosout]: Publisher already registered for provided node name. If this is due to multiple nodes with the same name then all logs for that logger name will go out over the existing publisher. As soon as any node with that name is destructed it will unregister the publisher, preventing any further logs for that name from being published on the rosout topic.
[gzserver-10] [INFO] [1610677647.166015357] [door]: Loading DoorPlugin for [lift_door_6]
[gzserver-10] Using specified value [0.5] for property [v_max_door]
[gzserver-10] Using specified value [0.3] for property [a_max_door]
[gzserver-10] Using specified value [0.15] for property [a_nom_door]
[gzserver-10] Using specified value [0.01] for property [dx_min_door]
[gzserver-10] Using specified value [500] for property [f_max_door]
[gzserver-10] Using specified attribute value [left_joint] for property [left_joint_name]
[gzserver-10] Using specified attribute value [empty_joint] for property [right_joint_name]
[gzserver-10] Using specified attribute value [SwingDoor] for property [type]
[gzserver-10] Using specified attribute value [left_joint] for property [name]
[gzserver-10] Using specified value [-1.57] for property [lower]
[gzserver-10] Using specified value [0] for property [upper]
[gzserver-10] Using specified attribute value [left_joint] for property [name]
[gzserver-10] Using specified value [-1.57] for property [lower]
[gzserver-10] Using specified value [0] for property [upper]
[gzserver-10] [INFO] [1610677647.175446786] [door]: Finished loading [lift_door_6]
[gzserver-10] [WARN] [1610677647.175979493] [rcl.logging_rosout]: Publisher already registered for provided node name. If this is due to multiple nodes with the same name then all logs for that logger name will go out over the existing publisher. As soon as any node with that name is destructed it will unregister the publisher, preventing any further logs for that name from being published on the rosout topic.
[building_map_server-3] Traceback (most recent call last):
[building_map_server-3]   File "/home/marcus/rmf_demos_ws/install/building_map_tools/lib/building_map_tools/building_map_server", line 11, in
[building_map_server-3]     load_entry_point('building-map-tools==0.0.0', 'console_scripts', 'building_map_server')()
[building_map_server-3]   File "/home/marcus/rmf_demos_ws/install/building_map_tools/lib/python3.8/site-packages/building_map_server/building_map_server.py", line 206, in main
[building_map_server-3]     n = BuildingMapServer(map_path)
[building_map_server-3]   File "/home/marcus/rmf_demos_ws/install/building_map_tools/lib/python3.8/site-packages/building_map_server/building_map_server.py", line 46, in init
[building_map_server-3]     self.map_msg = self.building_map_msg(self.building)
[building_map_server-3]   File "/home/marcus/rmf_demos_ws/install/building_map_tools/lib/python3.8/site-packages/building_map_server/building_map_server.py", line 71, in building_map_msg
[building_map_server-3]     msg.levels.append(self.level_msg(level_data))
[building_map_server-3]   File "/home/marcus/rmf_demos_ws/install/building_map_tools/lib/python3.8/site-packages/building_map_server/building_map_server.py", line 135, in level_msg
[building_map_server-3]     gn.name = v[2]['name']
[building_map_server-3]   File "/home/marcus/rmf_demos_ws/install/building_map_msgs/lib/python3.8/site-packages/building_map_msgs/msg/_graph_node.py", line 167, in name
[building_map_server-3]     assert
[building_map_server-3] AssertionError: The 'name' field must be of type 'str'
[gzserver-10] [INFO] [1610677647.188789468] [door]: Loading DoorPlugin for [lift_door_5]
[gzserver-10] Using specified value [0.5] for property [v_max_door]
[gzserver-10] Using specified value [0.3] for property [a_max_door]
[gzserver-10] Using specified value [0.15] for property [a_nom_door]
[gzserver-10] Using specified value [0.01] for property [dx_min_door]
[gzserver-10] Using specified value [500] for property [f_max_door]
[gzserver-10] Using specified attribute value [left_joint] for property [left_joint_name]
[gzserver-10] Using specified attribute value [empty_joint] for property [right_joint_name]
[gzserver-10] Using specified attribute value [SwingDoor] for property [type]
[gzserver-10] Using specified attribute value [left_joint] for property [name]
[gzserver-10] Using specified value [-1.57] for property [lower]
[gzserver-10] Using specified value [0] for property [upper]
[gzserver-10] Using specified attribute value [left_joint] for property [name]
[gzserver-10] Using specified value [-1.57] for property [lower]
[gzserver-10] Using specified value [0] for property [upper]
[gzserver-10] [INFO] [1610677647.195628741] [door]: Finished loading [lift_door_5]
[gzserver-10] [WARN] [1610677647.195976671] [rcl.logging_rosout]: Publisher already registered for provided node name. If this is due to multiple nodes with the same name then all logs for that logger name will go out over the existing publisher. As soon as any node with that name is destructed it will unregister the publisher, preventing any further logs for that name from being published on the rosout topic.
[gzserver-10] [INFO] [1610677647.207358466] [door]: Loading DoorPlugin for [lift_door_4]
[gzserver-10] Using specified value [0.5] for property [v_max_door]
[gzserver-10] Using specified value [0.3] for property [a_max_door]
[gzserver-10] Using specified value [0.15] for property [a_nom_door]
[gzserver-10] Using specified value [0.01] for property [dx_min_door]
[gzserver-10] Using specified value [500] for property [f_max_door]
[gzserver-10] Using specified attribute value [left_joint] for property [left_joint_name]
[gzserver-10] Using specified attribute value [empty_joint] for property [right_joint_name]
[gzserver-10] Using specified attribute value [SwingDoor] for property [type]
[gzserver-10] Using specified attribute value [left_joint] for property [name]
[gzserver-10] Using specified value [-1.57] for property [lower]
[gzserver-10] Using specified value [0] for property [upper]
[gzserver-10] Using specified attribute value [left_joint] for property [name]
[gzserver-10] Using specified value [-1.57] for property [lower]
[gzserver-10] Using specified value [0] for property [upper]
[gzserver-10] [INFO] [1610677647.215892814] [door]: Finished loading [lift_door_4]
[gzserver-10] [WARN] [1610677647.216242705] [rcl.logging_rosout]: Publisher already registered for provided node name. If this is due to multiple nodes with the same name then all logs for that logger name will go out over the existing publisher. As soon as any node with that name is destructed it will unregister the publisher, preventing any further logs for that name from being published on the rosout topic.
[gzserver-10] [INFO] [1610677647.226037079] [door]: Loading DoorPlugin for [ShaftDoor_Lift1_L6_lift_door]
[gzserver-10] Using specified value [0.3] for property [v_max_door]
[gzserver-10] Using specified value [0.2] for property [a_max_door]
[gzserver-10] Using specified value [0.1] for property [a_nom_door]
[gzserver-10] Using specified value [0.0001] for property [dx_min_door]
[gzserver-10] Using specified value [35] for property [f_max_door]
[gzserver-10] Using specified attribute value [left_joint] for property [left_joint_name]
[gzserver-10] Using specified attribute value [right_joint] for property [right_joint_name]
[gzserver-10] Using specified attribute value [DoubleSlidingDoor] for property [type]
[gzserver-10] Using specified attribute value [right_joint] for property [name]
[gzserver-10] Using specified value [0] for property [lower]
[gzserver-10] Using specified value [0.5] for property [upper]
[gzserver-10] Using specified attribute value [right_joint] for property [name]
[gzserver-10] Using specified value [0] for property [lower]
[gzserver-10] Using specified value [0.5] for property [upper]
[gzserver-10] Using specified attribute value [left_joint] for property [name]
[gzserver-10] Using specified value [-0.5] for property [lower]
[gzserver-10] Using specified value [0] for property [upper]
[gzserver-10] Using specified attribute value [ramp_joint] for property [name]
[gzserver-10] [INFO] [1610677647.233926577] [door]: Finished loading [ShaftDoor_Lift1_L6_lift_door]
[gzserver-10] [WARN] [1610677647.234256122] [rcl.logging_rosout]: Publisher already registered for provided node name. If this is due to multiple nodes with the same name then all logs for that logger name will go out over the existing publisher. As soon as any node with that name is destructed it will unregister the publisher, preventing any further logs for that name from being published on the rosout topic.
[gzserver-10] [INFO] [1610677647.245361252] [door]: Loading DoorPlugin for [ShaftDoor_Lift1_L7_lift_door]
[gzserver-10] Using specified value [0.3] for property [v_max_door]
[gzserver-10] Using specified value [0.2] for property [a_max_door]
[gzserver-10] Using specified value [0.1] for property [a_nom_door]
[gzserver-10] Using specified value [0.0001] for property [dx_min_door]
[gzserver-10] Using specified value [35] for property [f_max_door]
[gzserver-10] Using specified attribute value [left_joint] for property [left_joint_name]
[gzserver-10] Using specified attribute value [right_joint] for property [right_joint_name]
[gzserver-10] Using specified attribute value [DoubleSlidingDoor] for property [type]
[gzserver-10] Using specified attribute value [right_joint] for property [name]
[gzserver-10] Using specified value [0] for property [lower]
[gzserver-10] Using specified value [0.5] for property [upper]
[gzserver-10] Using specified attribute value [right_joint] for property [name]
[gzserver-10] Using specified value [0] for property [lower]
[gzserver-10] Using specified value [0.5] for property [upper]
[gzserver-10] Using specified attribute value [left_joint] for property [name]
[gzserver-10] Using specified value [-0.5] for property [lower]
[gzserver-10] Using specified value [0] for property [upper]
[gzserver-10] Using specified attribute value [ramp_joint] for property [name]
[gzserver-10] [INFO] [1610677647.255045911] [door]: Finished loading [ShaftDoor_Lift1_L7_lift_door]
[ERROR] [building_map_server-3]: process has died [pid 2607, exit code 1, cmd '/home/marcus/rmf_demos_ws/install/building_map_tools/lib/building_map_tools/building_map_server /home/marcus/rmf_demos_ws/install/rmf_demo_maps/share/rmf_demo_maps/imda/imda.building.yaml --ros-args'].
[gzserver-10] [INFO] [1610677647.288554575] [lift]: Loading LiftPlugin for [Lift1]
[gzserver-10] Using specified value [2] for property [v_max_cabin]
[gzserver-10] Using specified value [1.2] for property [a_max_cabin]
[gzserver-10] Using specified value [1] for property [a_nom_cabin]
[gzserver-10] Using specified value [0.001] for property [dx_min_cabin]
[gzserver-10] Using specified value [25323] for property [f_max_cabin]
[gzserver-10] Using specified value [cabin_joint] for property [cabin_joint_name]
[gzserver-10] Using specified attribute value [L6] for property [name]
[gzserver-10] Using specified attribute value [-20] for property [elevation]
[gzserver-10] Using specified attribute value [CabinDoor_Lift1_lift_door] for property [cabin_door]
[gzserver-10] Using specified attribute value [ShaftDoor_Lift1_L6_lift_door] for property [shaft_door]
[gzserver-10] Using specified attribute value [L7] for property [name]
[gzserver-10] Using specified attribute value [0] for property [elevation]
[gzserver-10] Using specified attribute value [CabinDoor_Lift1_lift_door] for property [cabin_door]
[gzserver-10] Using specified attribute value [ShaftDoor_Lift1_L7_lift_door] for property [shaft_door]
[gzserver-10] Using specified value [L6] for property [initial_floor]
[gzserver-10] Loaded lift: Lift1
[gzserver-10] Names  |  Elevations
[gzserver-10] L7  |  0
[gzserver-10] L6  |  -20
[gzserver-10] [INFO] [1610677647.294367184] [lift]: Finished loading [Lift1]
[gzserver-10] [WARN] [1610677647.294589433] [rcl.logging_rosout]: Publisher already registered for provided node name. If this is due to multiple nodes with the same name then all logs for that logger name will go out over the existing publisher. As soon as any node with that name is destructed it will unregister the publisher, preventing any further logs for that name from being published on the rosout topic.
[gzserver-10] [INFO] [1610677647.306105802] [door]: Loading DoorPlugin for [CabinDoor_Lift1_lift_door]
[gzserver-10] Using specified value [0.3] for property [v_max_door]
[gzserver-10] Using specified value [0.2] for property [a_max_door]
[gzserver-10] Using specified value [0.1] for property [a_nom_door]
[gzserver-10] Using specified value [0.0001] for property [dx_min_door]
[gzserver-10] Using specified value [35] for property [f_max_door]
[gzserver-10] Using specified attribute value [left_joint] for property [left_joint_name]
[gzserver-10] Using specified attribute value [right_joint] for property [right_joint_name]
[gzserver-10] Using specified attribute value [DoubleSlidingDoor] for property [type]
[gzserver-10] Using specified attribute value [right_joint] for property [name]
[gzserver-10] Using specified value [0] for property [lower]
[gzserver-10] Using specified value [0.5] for property [upper]
[gzserver-10] Using specified attribute value [right_joint] for property [name]
[gzserver-10] Using specified value [0] for property [lower]
[gzserver-10] Using specified value [0.5] for property [upper]
[gzserver-10] Using specified attribute value [left_joint] for property [name]
[gzserver-10] Using specified value [-0.5] for property [lower]
[gzserver-10] Using specified value [0] for property [upper]
[gzserver-10] [INFO] [1610677647.316474356] [door]: Finished loading [CabinDoor_Lift1_lift_door]
[rviz2-7] [INFO] [1610677647.829294312] [rmf_panel]: Loading tinyRobot..
[rmf_traffic_schedule-1] [INFO] [1610677647.829808176] [rmf_traffic_schedule_node]: Registered participant [0] named [tinyRobot2] owned by [tinyRobot]
[full_control-12] [INFO] [1610677647.830707833] [tinyRobot_fleet_adapter]: Added a robot named [tinyRobot2] with participant ID [0]
[rviz2-7] Nav File Path Found: /home/marcus/rmf_demos_ws/install/rmf_demo_maps/share/rmf_demo_maps/maps/imda_world/nav_graphs/0.yaml
[rviz2-7] Adding waypoint [1] as a parking spot
[rviz2-7] Adding waypoint [3] as a parking spot
[rviz2-7] Adding waypoint [16] as a parking spot
[rviz2-7] Adding waypoint [17] as a parking spot
[rviz2-7] Named waypoints:
[rviz2-7]  -- [lift_lobby]
[rviz2-7]  -- [12]
[rviz2-7]  -- [11]
[rviz2-7]  -- [exit_lift]
[rviz2-7]  -- [5]
[rviz2-7]  -- [3]
[rviz2-7]  -- [4]
[rviz2-7]  -- [14]
[rviz2-7]  -- [6]
[rviz2-7]  -- [1]
[rviz2-7]  -- [tinyRobot2_charger]
[rviz2-7]  -- [9]
[rviz2-7]  -- [enter_lift]
[rviz2-7]  -- [15]
[rviz2-7]  -- [2]
[rviz2-7]  -- [7]
[rviz2-7]  -- [8]
[rviz2-7] [INFO] [1610677647.863111655] [rmf_panel]: New Fleet found, refreshing...
[full_control-12] [ERROR] [1610677648.330803689] [tinyRobot_fleet_adapter]: Robot named [tinyRobot2] belonging to fleet [tinyRobot] is lost because we cannot figure out what floor it is on. Please publish the robot's current floor name in the level_name field of its RobotState.
[gzclient-11] [INFO] [1610677648.536276686] [gazebo_ros_node]: ROS was initialized without arguments.
[rviz2-7] [INFO] [1610677648.640713917] [lift_panel_session_node]: New lift [Lift1] found, refreshing...
[full_control-12] [ERROR] [1610677648.834471256] [tinyRobot_fleet_adapter]: Robot named [tinyRobot2] belonging to fleet [tinyRobot] is lost because we cannot figure out what floor it is on. Please publish the robot's current floor name in the level_name field of its RobotState.
[full_control-12] [ERROR] [1610677649.337084918] [tinyRobot_fleet_adapter]: Robot named [tinyRobot2] belonging to fleet [tinyRobot] is lost because we cannot figure out what floor it is on. Please publish the robot's current floor name in the level_name field of its RobotState.

Looks like your building_map_server is crashing. As a result, the building information is not available to the slotcar plugin which using the same to initialize the level the robot is located on.
I suspect the crash is happening due to the naming of your level in traffic_editor with numericals only. Eg "1" instead of "L1". Could you share your .building.yaml file? If that is not permitted, could you share more on the names assigned to levels in traffic_editor?

Looks like your building_map_server is crashing. As a result, the building information is not available to the slotcar plugin which using the same to initialize the level the robot is located on.
I suspect the crash is happening due to the naming of your level in traffic_editor with numericals only. Eg "1" instead of "L1". Could you share your .building.yaml file? If that is not permitted, could you share more on the names assigned to levels in traffic_editor?

Looks like your building_map_server is crashing. As a result, the building information is not available to the slotcar plugin which using the same to initialize the level the robot is located on.
I suspect the crash is happening due to the naming of your level in traffic_editor with numericals only. Eg "1" instead of "L1". Could you share your .building.yaml file? If that is not permitted, could you share more on the names assigned to levels in traffic_editor?

My levels were named L6 and L7.

Looks like your building_map_server is crashing. As a result, the building information is not available to the slotcar plugin which using the same to initialize the level the robot is located on.
I suspect the crash is happening due to the naming of your level in traffic_editor with numericals only. Eg "1" instead of "L1". Could you share your .building.yaml file? If that is not permitted, could you share more on the names assigned to levels in traffic_editor?

My levels were named L6 and L7.

Ah just noticed this

[building_map_server-3] File "/home/marcus/rmf_demos_ws/install/building_map_msgs/lib/python3.8/site-packages/building_map_msgs/msg/_graph_node.py", line 167, in name

Same problem with numeric names but this time for waypoints not level names. Could you ensure none of your waypoints are named as numbers alone?

Ah just noticed this

[building_map_server-3] File "/home/marcus/rmf_demos_ws/install/building_map_msgs/lib/python3.8/site-packages/building_map_msgs/msg/_graph_node.py", line 167, in name

Same problem with numeric names but this time for waypoints not level names. Could you ensure none of your waypoints are named as numbers alone?

Ah just noticed this

[building_map_server-3] File "/home/marcus/rmf_demos_ws/install/building_map_msgs/lib/python3.8/site-packages/building_map_msgs/msg/_graph_node.py", line 167, in name

Same problem with numeric names but this time for waypoints not level names. Could you ensure none of your waypoints are named as numbers alone?

Thanks. This fixes the problem! Really appreciate the help

Ah just noticed this

[building_map_server-3] File "/home/marcus/rmf_demos_ws/install/building_map_msgs/lib/python3.8/site-packages/building_map_msgs/msg/_graph_node.py", line 167, in name

Same problem with numeric names but this time for waypoints not level names. Could you ensure none of your waypoints are named as numbers alone?

Thanks. This fixes the problem! Really appreciate the help


Replace kleur with styleText

Describe the problem
Can use node built-in in favor of extra dependency
Describe the proposed solution
Requires Node 20
https://stackoverflow.com/a/78604048
Alternatives considered
No response
Importance
nice to have
Additional Information
No response

Is there a branch, similar to version-2 for https://github.com/sveltejs/kit/pull/11172, that can be used to upgrade node from 18.13 to 20.13?

No. We need to wait until we're ready to do the next major release. There's no timeline on that currently.


databricks: print_dbt_project_evaluator_issues - quoting

Describe the bug
Printing the results does not work when the databricks schema contains special characters
Steps to reproduce
using special characters in your schema: for example ch-123
Expected results
the expected behaviour = printing the results
Actual results
on-run-end failed, error:
[INVALID_IDENTIFIER] The identifier ch-51278 is invalid. Please, consider quoting it with back-quotes as ch-51278.(line 4, pos 28)
== SQL ==
/* {"app": "dbt", "dbt_version": "1.7.3", "dbt_databricks_version": "1.7.2", "databricks_sql_connector_version": "2.9.3", "profile_name": "user", "target_name": "qas", "connection_name": "master"} */
    select * from qas.ch-51278.fct_test_coverage

----------------------------^^^
Screenshots and log output

System information
The contents of your packages.yml file:
packages:

package: dbt-labs/dbt_external_tables
version: 0.8.7
package: dbt-labs/dbt_utils
version: [">=1.0.0", "<2.0.0"]
package: dbt-labs/dbt_project_evaluator
version: 0.8.0

Which database are you using dbt with?

[ ] postgres
[ ] redshift
[ ] bigquery
[ ] snowflake
[ ] trino/starburst
[ x] other (specify: databricks)

The output of dbt --version:
Running with dbt=1.7.3
Registered adapter: databricks=1.7.2
Additional context
dbt_project_evaluator > macros > on-run-end > print_dbt_project_evaluator_issues
set db_schema: quote a lowercase the three level namespace

When we do a new release you will be able to use print_dbt_project_evaluator_issues(quote='`')


Always display signature and public key on signinfo

Release Note

Always display signature and public key on signinfo view page.


feat(Datepicker): multiple event color bar

Feature Description
Can we add multiple event color in datepicker?
Use Case
It's will be like v-calendar bar attribute
one date allow multiple color

I don't see us adding support for this since it's not really captured in the Material Design spec.


move postgres config files into system/TEMPLATE

system/COPY has files that are always overlayed onto the build image.
system/TEMPLATE is being used to store optional files.
The database files are only overlay'ed if the user installs a database. They can't be copied because the database volume is not formatted or mounted yet.
So we are moving them out of the COPY directory.
Since we are adding apache config files to COPY/opt, this change will simplify the install process and allow the kickstart to just overlay all files from COPY blindly.
/cc @jrafanie @mkanoor @Fryguy

How do we then apply changes such as improved configuration values?  Generally, we are our own DBA.  My original suggestion was to supply multiple .conf files, one of which is supplied by us, and a separate one which is configured with overrides by a customer.  Is that possible?

This PR is just moving pg_ident.conf and 2 files that I don't recognize. I want to move to simplify system/COPY and streamline http install for Madhu.
We've been using erb to support those improved values. Currently only ssl is changed.
Is this change you are proposing potentially large?

I believe what @Fryguy is suggesting is if it's possible to do something like apache where a base configuration file would load *.conf in a directory and allow you to do something like miq.conf and user.conf where miq is ours and is read first, and user is read last and would override any values in miq.  IDK if there are mechanisms for this in postgresql nor how much effort it is.

@mkanoor Does this address the issue you were seeing with the files you wanted to deploy into the appliance?

I have no idea what you just said and how it relates to the code changes you are making.
The reason we are using system/COPY is because we, as maintainers of our appliance db, need to make changes to the .conf files and have them deployed on upgrade.  Moving them to system/TEMPLATE kills that feature.
Alternately, we currently have a problem where customers also make their own changes to the .conf files for their own reasons, but system/COPY kills that feature by overwriting their files.
So, we are stuck in the middle...my suggestion (from a BZ triage conversation, so probably not written down yet, but I'll get the BZ ticket) was to use multiple .conf files if possible, one updated by us, and the other updated by the customer.  One would be ours from system/COPY, and the other can come from system/TEMPLATE which can be changed as needed.
See https://bugzilla.redhat.com/show_bug.cgi?id=1182331 cc @jrafanie

Sorry, yes, I was also conflating apache and postgres, but my idea still is the same, if it's possible to do with postgres.

@kbrock I am rereading your initial post and I think I got/am confused cause you started explaining all this stuff about apache which isn't really pertinent here?  Can you just pinpoint what you are trying to solve?

@Fryguy apache configuration is moving from /etc/.. to /opt/...
So the apache configuration need to be moved from system/COPY/etc/... to system/COPY/opt/...
kickstart currently does not copy files from system/COPY/opt/... to /opt/...
So we want to add that.
But there are some database configuration files in system/COPY/opt that don't want to be copied in the kickstart. If they are copied, then the database won't install. (postgres disk volume is not setup yet).
This pr suggests moving the database configuration files out of system/COPY/opt so all of system/COPY/opt can be blindly copied.
Alternatively we can build the kickstart so it only copies across the apache configuration files from opt across.

@Fryguy @jrafanie As for postgres, there is an include file directive. I will put in a PR for that. So we can have static files. It will work for most of them. (but either way, we will not be able to copy this file across in the kickstart)

closing
@mkanoor / @jvlcek change the kickstart to just copy that opt directory
@jrafanie @Fryguy I will look into changing the way we configure ssl in postgres to get back to static files. (it has been using templates since May 2014)
@mkanoor @abellotti we need to look at IPA to see if we can get to static configuration files.

But there are some database configuration files in system/COPY/opt that don't want to be copied in the kickstart.

I think this is the part the confuses me.  The entire purpose of the COPY directory is that everything is being copied on every install, and TEMPLATE is like "copy once".  If we are not following that rule, then we need to discuss because the system directory doesn't work as expected.

Doh, meant to cc @brandondunne, @jrafanie @jvlcek on the above.

This pr suggests moving the database configuration files out of system/COPY/opt so all of system/COPY/opt can be blindly copied.

Again, this goes back to my confusion.  Given that all of COPY is blindly copied (which it should be, if it isn't), then why the need to move it out of COPY.  Why shouldn't postgres just get copied?  As I asked originally, if the files are TEMPLATE (or not copied) "How do we then apply changes such as improved configuration values?"


Add support for PostgreSQL arrays

This adds support for multidimensional ARRAY types in base-jdbc.  There's also an example implementation in PostgreSql.

Thanks @ebyhr , updated with your suggestions

@ebyhr thanks for doing first review pass. Appreciated!
@vincentpoon  thanks for your PR!
In my opinion, there are some design changes to be done. In particular, I don't like the fact that we're constructing List<JdbcColumnHandle> and then remap them to another List<JdbcColumnHandle>. This is error prone, as it's possible to add future call site obtaining wrong List<JdbcColumnHandle> without remapping them.
My suggestion regarding moving it forward:

Extract a commit introducing Block-typed read and write functions (call it eg Add BlockReadFunction, BlockWriteFunction).
This change touches multiple files but otherwise is rather straightforward. You can even create a separate PR, so we can merge this sooner and have less code changes here.

Replace private static ResultSet BaseJdbcClient#getColumns(JdbcTableHandle, java.sql.DatabaseMetaData) with protected Map<String,JdbcTypeHandle> getColumnTypes(ConnectorSession session, JdbcTableHandle). (map to be key-ed by column name)
Default implementation would still use java.sql.DatabaseMetaData#getColumns of course.
(Call this eg Allow overriding querying column metadata)

Add the code to handle postgres arrays.

extend JdbcTypeHandle with additional fields (not sure what these should be: "dimensions"? "elementType"?)
override this new getColumnTypes method in PostgresClient
... i don't know yet how this should look like -- see below

I don't have yet answer on how  arrayReadFunction and arrayWriteFunction could look like.
What are the abstractions needed, what assumptions are OK to be made.
If we consider the fact that we don't a priori know how a base-jdbc -based connector is going to make in/out values, we probably don't know how it will map in/out array elements.
Maybe for starter, this should be a Postgres-specific feature?
cc @electrum

Thanks for looking at this @findepi .  Agree that the new methods in BaseJdbcClient here aren't ideal - I think that was a result of me trying to push as much reusable code up into BaseJdbcClient as possible.  This work actually came out of my work on the Phoenix connector (#76) as I figured I could get rid of a lot of array-specific stuff there if I made a more general solution.  But as you suggest, perhaps it's best to leave a lot of this in the specific jdbc implementations.
The BlockReadFunction and BlockWriteFunction are the only things I really need, i think.  I'll create a separate PR for that.
Let me try to rework this a little.  AFAIK, the main thing with jdbc ARRAY is there's no standard naming convention (but that's already true with other types, which is why we have e.g. WriteMapping#getDataType), and no standard in terms of what ResultSet#getArray returns you (as the javadoc clearly states).

@findepi I updated this, now that #454 is merged.  There's less impact on base-jdbc now, and all the ARRAY-related functionality is in presto-postgresql.
I couldn't quite implement getColumnTypes() the way you suggested, since there was a recent change that uses the ResultSet to get whether a column is nullable.  So in other words, getColumns() and getJdbcTypeHandle() both need to use the ResultSet, which is why I pass that as a parameter.
Let me know what you think, thanks!

@findepi I've updated this with two separate commits.  The first only adds arrayDimensions to base-jdbc.  Everything else in the second commit is in presto-postgresql now.
Thanks for your helpful comments, it's looking a lot better now.

one more comment that i have now is about tests -- please look
into how we usually test type mappings in TestPostgreSqlTypeMapping.

@vincentpoon to be clear: i am not sure this will be applicable. This needs trying / more thinking.

Thanks, I'll take a look at TestPostreSqlTypeMapping

@findepi I've pushed another commit with new TestPostreSqlTypeMapping tests.  They helped my catch a bug with certain char[] - I now throw NOT_SUPPORTED explicitly in TypeUtils to avoid this kind of error.
Also, apparently PostgreSQL's JDBC driver doesn't yet support varbinary arrays, so I removed support for that.

@findepi Thanks again for the review, I have pushed a new squashed revision.  I believe I have addressed all the comments, and have replied to some specifically.

LGTM. Thanks @vincentpoon for working on this.
Can you please rebase?

@findepi  rebased

Thanks @findepi , addressed your latest comments

Merged, thanks!

Note: as per https://github.com/prestosql/presto/pull/687, this needs to be explicitly enabled.
cc @hashbash (https://github.com/prestodb/presto/issues/11422), @troels (https://github.com/prestodb/presto/pull/8849)


ion-segment mode attribute stopped working after updating to beta.16-17

Bug Report
Ionic Info
Ionic:

   ionic (Ionic CLI)             : 4.5.0 (/usr/local/lib/node_modules/ionic)
   Ionic Framework               : @ionic/angular 4.0.0-beta.17
   @angular-devkit/build-angular : 0.12.0-beta.0
   @angular-devkit/schematics    : 0.8.8
   @angular/cli                  : 7.2.0-beta.0
   @ionic/angular-toolkit        : 1.2.0

Cordova:

   cordova (Cordova CLI) : 8.0.0
   Cordova Platforms     : ios 4.5.5
   Cordova Plugins       : cordova-plugin-ionic-keyboard 2.1.3, cordova-plugin-ionic-webview 2.2.5, (and 7 other plugins)

System:

   ios-deploy : 1.9.2
   NodeJS     : v10.13.0 (/usr/local/bin/node)
   npm        : 6.4.1
   OS         : macOS Mojave
   Xcode      : Xcode 10.1 Build version 10B61

Describe the Bug
Hi all, I am using ion-segments within my project, I wanted to force the style to Material Design so I added mode="md" to my segment and it worked great up until I upgraded to betas 16 and 17. The styling is no longer forced to Material Design when I'm on iOS (it displays the native iOS style).
Here is a demo of related code where I added the mode and a screenshot of what it looks like now:
  <ion-segment (ionChange)="segmentChanged($event)" mode="md">
    <ion-segment-button value="upcoming" checked>
      <ion-label>Upcoming</ion-label>
    </ion-segment-button>
    <ion-segment-button value="released">
      <ion-label>Released</ion-label>
    </ion-segment-button>
  </ion-segment>

It also appears that the universal attributes used to modify segments styles also no longer work, for example:
ion-segment {
    --border-color: rgba(255,255,255,0.1);
    --border-color-checked: rgba(107,157,250, 1);
    --color-checked: #fff;
    --color: #fff;
}

Expected Behavior
Expected to see the ion-segment design in Material Design on iOS.

Thanks for your issue and your time to reporting it!
It seems that you made a mistake on declaring the right mode and the css variables.
First: You have to add the mode to the segment-buttons, too:
    <ion-segment (ionChange)="segmentChanged($event)" mode="md">
        <ion-segment-button value="upcoming" checked  mode="md">
          <ion-label>Upcoming</ion-label>
        </ion-segment-button>
        <ion-segment-button value="released"  mode="md">
          <ion-label>Released</ion-label>
        </ion-segment-button>
      </ion-segment>

Second: The css variables has to be set to the ion-segment-button, so it's
ion-segment-button {
    --border-color: rgba(255,255,255,0.1);
    --border-color-checked: rgba(107,157,250, 1);
    --color-checked: #fff;
    --color: #fff;
}

And if you do so, it's working :)

If you have any further questions, let me know :)

@paulstelzer ah of course, thank you very much for your time and for catching my mistake!


Add a Security Considerations section.

The spec already has various mitigations for security concerns baked in,
this ties it all together and links to them from one central place.
This addresses Issue #170.
@jakearchibald PTAL.

My main goal is to ensure we don't unnecessarily resist making requirements normative if making them normative convinces @othermaciej to ship this in Safari and the normative requirements don't prevent anything we actually think is a good idea.

Just to be clear, I'm not promising any particular Security Considerations changes would convince us to implement or ship this in Safari. We still share Mozilla's privacy concerns, for one thing. But we'll re-review the spec once it's updated.
More broadly, though, I do think that behavior which seems needed for safety should be normative, and while UA flexibility is nice, it's not necessary if anyone would actually implement the imagined different behavior.


Add distance-perhaps other parameters

Thanks!- A gui for jxl is sorely lacking!  I even considered trying to pick up the pieces of MegaPixel Qt-which was the best so far. Perhaps look at it and as I said add distance other parameters-regardless thanks!

Thank you, for your input.
All Parameters will be add in near future with https://github.com/dhcgn/jxlgui/issues/2.
An GUI for configuration is documented, but not first prio, because it adds only comfort to the text based configuration.

You can now use distance or quality to convert images.

Use Quality

Use Distance

Error when using both

Release will be uploaded today.

https://github.com/dhcgn/jxlgui/releases/tag/v1.0.4


Add Result<Value, Error>

This PR adds Result<Value, Error>, as an implementation of Adding Result to the Standard Library.
This PR has basic tests at the moment, suggestions for additional tests and proper annotations are welcome.

@DevAndArtist I've updated to match the style you mentioned.

I think I've created all of the API I need. Should I also do the inline documentation?


Wallet drop

Added functionality to add wallet manually.

@Sumit570
while we're at it, can we rename "Wallets" in the side bar to "Balances", and change the + button to say "+ ADD BALANCE"

@Sumit570
while we're at it, can we rename "Wallets" in the side bar to "Balances", and change the + button to say "+ ADD BALANCE"

Also the title at the top "Wallets" -> "Balances"

Also the title at the top "Wallets" -> "Balances"

@thedoublejay can you check if this is good to merge?


config: use ko

Reason: to be able to pass config params as env variables to run in Cloud
Build.

@kovetskiy I can't merge.

I've added you Stas to collaborators


Can't find the default  mapping in help file

I almost had to give up on this plugin because I could not find which key is the <Leader>. In the whole :help nerdcommenter I could not find that it is mapped to '\' by default. Only this comment on stackoverflow says it. It should be right at the beginning of the help in the functionality summary.

Thanks, I'll try to create a pull request later. I had no idea that  is defined in vim and in vim help, I thought it's just a nerdcommenter's thing.

No, <Leader> is pretty much the de facto way for plugins to define keymaps so they don't step on common native mappings. Probably 70% of vim-plugins you run across will use this, as well as many user configs you'll find online. It isn't quite universal, but it's kind of expected users will know about this.
I don't mind adding something to the help, but keep it short and keep in mind it isn't universally \, that's just tho most common default out of the box. Probably the best thing to do is just add a quick link to the :help Leader section in the help, and in the README just comment that <Leader> is whatever vim is configured to use.

Pull request created.


show_report parameter p_out_filename issue downloading the report automatically

I'm using JasperReportsIntegration <IP_ADDRESS>.
If I call the show_report and pass NULL to p_outfilename the report displays in PDF which is great. If I click the download button it default the name to f.pdf
I want to change the default name to something else so I tried I'm passing the default report name like 'myreport.pdf' to p_outfilename.
The issue is when you run the report it downloads the file but you get an empty all white blank space.
Thanks

I think you hv to use the parameters such as:
xlib_jasperreports.show_report (p_rep_name => 'my_jasper_report',
p_rep_format => 'pdf', --:P2_REP_FORMAT,
p_data_source => 'my_datasource',
--    p_out_filename => 'myreport.pdf',                            <----- or as below
p_out_filename => 'myReportt_'||:P2_order:nr||'.pdf',   <-------
p_rep_locale => 'de_DE',
p_rep_encoding => 'UTF-8',
p_additional_params => l_additional_parameters);
late.. but I hope that helps... I just came across this...

@golfmeister2005 : Did that fix your issue?

I am closing this issue because the op didn't respond. If you still encounter this issue, please reopen the issue. Thanks.


Switch to github actions

In general this should have parity with the existing Jenkins pipeline.

On pull requests all steps are run except the conda package step
On pushes to branches named branch-* the check script is skipped, and the conda package step is run

It isn't clear if the nightly builds were actually enabled/working.
Fixes #154

@gpucibot merge


[ZDNet] Fix article layout (#1791)

Removes the sharing tools HTML block causing messed up layout as highlighted in #1791

gj @ORelio !