text:
[BUG] beginner_multimodal.ipynb stuck on single node dual 4090 system

[x ] I have checked that this bug exists on the latest stable version of AutoGluon
[ ] and/or I have checked that this bug exists on the latest mainline of AutoGluon via source installation

Describe the bug
The default run of beginner_multimodal.ipynb hangs on dual-node 4090s
Expected behavior
Task should finish within a few minutes (default time_limit per iter = 120s ==> 10epochs should finish fast)
To Reproduce
Download Colab beginner_multimodal.ipynb to .py file. Run "python beginner_multimodal.py" on shell in proper python environment.
Screenshots
If applicable, add screenshots to help explain your problem.
Installed Versions
Which version of AutoGluon are you are using?  0.7
If you are using 0.4.0 and newer, please run the following code snippet:

# Replace this code with the output of the following:
INSTALLED VERSIONS
------------------
date                   : 2023-02-28
time                   : 15:59:34.670966
python                 : 3.10.9.final.0
OS                     : Linux
OS-release             : 5.19.0-32-generic
Version                : #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2
machine                : x86_64
processor              : x86_64
num_cores              : 64
cpu_ram_mb             : 515617
cuda version           : 12.525.78.01
num_gpus               : 2
gpu_ram_mb             : [22372, 24134]
avail_disk_size_mb     : 3500447

accelerate             : 0.16.0
autogluon.common       : 0.7.0
autogluon.core         : 0.7.0
autogluon.features     : 0.7.0
autogluon.multimodal   : 0.7.0
autogluon.tabular      : 0.7.0
autogluon.timeseries   : 0.7.0
boto3                  : 1.26.80
catboost               : 1.1.1
defusedxml             : 0.7.1
evaluate               : 0.3.0
fairscale              : 0.4.13
fastai                 : 2.7.11
gluonts                : 0.12.3
hyperopt               : 0.2.7
jinja2                 : 3.1.2
joblib                 : 1.2.0
jsonschema             : 4.17.3
lightgbm               : 3.3.5
matplotlib             : 3.7.0
networkx               : 2.8.8
nlpaug                 : 1.1.11
nltk                   : 3.8.1
nptyping               : 2.4.1
numpy                  : 1.23.5
omegaconf              : 2.2.3
openmim                : None
pandas                 : 1.5.3
PIL                    : 9.4.0
psutil                 : 5.9.4
pytesseract            : 0.3.10
pytorch-metric-learning: None
pytorch_lightning      : 1.9.3
ray                    : 2.2.0
requests               : 2.28.2
scipy                  : 1.10.0
sentencepiece          : 0.1.97
seqeval                : None
setuptools             : 67.3.1
skimage                : 0.19.3
sklearn                : 1.2.1
statsforecast          : 1.4.0
statsmodels            : 0.13.5
tensorboard            : 2.12.0
text-unidecode         : None
timm                   : 0.6.12
torch                  : 1.12.1
torchmetrics           : 0.8.2
torchvision            : 0.13.1
tqdm                   : 4.64.1
transformers           : 4.26.1
ujson                  : 5.7.0
xgboost                : 1.7.4

Additional context
Add any other context about the problem here.
I suspect it is related to outstanding nvidia driver bug. https://forums.developer.nvidia.com/t/standard-nvidia-cuda-tests-fail-with-dual-rtx-4090-linux-box/233202/24

Have you resolved the issue?

As you may notice, nVidia has fixed the bug in version 525. I am on driver 530.30.02, and they have not forward ported the fix yet. Once they do, I will retry and report back.

Closing this issue assuming it's fixed.

authors: mirachakshu shchur zhiqiangdon

repo: autogluon/autogluon


text:
bug(python): Drain prints before ending flow.

Fixes: ENG-1660

Tested manually, ran @itayd 's workflow before fix and saw missing every 3-4 runs. Now see all prints every time.

source: gharchive/pull-request

repo: autokitteh/autokitteh

license_type: permissive

license_source: github-api


text:
Prevent panic when string contains a null character.

@alexjg, @orionz and @ConradIrwin, I've changed the entire C API to use an AMbyteSpan struct instead of a char const* for all string values in order to resolve issue #455.
At @alexjg's suggestion, I've also hard-coded the automerge-c library's initial independent version number to "0.0.1".
Starting with this PR, the revision number of automerge-c will be bumped independently of the revision number for automerge-rs.

@ConradIrwin, I believe those functions are covered by the changes I've made already but I should add unit tests to confirm.

Sorry I didn't check! I thought they might not because those APIs do not return an AMresult.

Reading that I'm reminded of Frank Zappa's quote about curing dandruff with decapitation.

Agreed! It's definitely not the idiomatic C way to do things.
I mostly want it not to panic, so I would also be happy with the options of:

automerge errored when setting strings containing U+0000, so this situation can't happen.
automerge itself works fine with U+0000, but automerge-c reports a sensible error.

As you say, this should be rare in practice.
It's possible we could split the difference: no U+0000 allowed in map keys; and either handle (or error) on string values with U+0000.

Can you rebase on main, that should fix the failing JS test.

Can you rebase on main, that should fix the failing JS test.

@alexjg, it has been done but the "js_tests" check is still failing but for a different, seemingly-unrelated problem this time.
The "windows" check failed because of insufficient disk space.

authors: ConradIrwin alexjg jkankiewicz

repo: automerge/automerge-rs

license: MIT


text:
Candidate resolution DSL issue configuring dependencies

Build scan link
gradlew --scan buildHealth: https://scans.gradle.com/s/nl5ukhfciwirw
Plugin version
1.20.0
Gradle version
8.1.1
IDE version
IntelliJ Ultimate 2023.1
Verified platforms
Mac and Windows
Describe the bug
I'm getting an IDE warning and subsequent errors trying to configure dependency bundles:
dependencyAnalysis {
	dependencies { // Candidate resolution warning (full text below)
		bundle("kotlinx-coroutines-core") { // Unresolved reference: bundle
			includeDependency("org.jetbrains.kotlinx:kotlinx-coroutines-core") // Unresolved reference: includeDependency
			includeDependency("org.jetbrains.kotlinx:kotlinx-coroutines-core-jvm") // Same unresolved reference
		}
	}
}

Candidate resolution will be changed soon, please use fully qualified name to invoke the following closer candidate explicitly:
public final fun dependencies(action: Action): Unit defined in com.autonomousapps.DependencyAnalysisExtension

To Reproduce
Reproducer: https://github.com/sdkotlin/sd-kotlin-spring-talks/tree/dagp-dependencies-configuration
Attempted change: https://github.com/sdkotlin/sd-kotlin-spring-talks/commit/5546c9f3f0178cdf2881ebd4b8a3b398b5c8df96
Expected behavior
There are no IDE warnings, and "org.jetbrains.kotlinx:kotlinx-coroutines-core-jvm" isn't reported as an unused dependency given the bundle configuration.
Actual behavior
Running buildHealth does succeed, but the bundle configuration appears to have no effect:

Unused dependencies which should be removed:
integrationTestImplementation("org.jetbrains.kotlinx:kotlinx-coroutines-core-jvm:1.6.4")

Additional context
Perhaps this is just another Gradle 8 incompatibility, #851.

I'm able to work around the issue by using this.dependencies:
dependencyAnalysis {
	this.dependencies {
		bundle("kotlinx-coroutines-core") {
			includeDependency("org.jetbrains.kotlinx:kotlinx-coroutines-core")
			includeDependency("org.jetbrains.kotlinx:kotlinx-coroutines-core-jvm")
		}
	}
}

I think the solution here would just be to replace it with a new one and deprecate the previous. Maybe dependencyHandling?

source: gharchive/issue

authors: ZacSweers ianbrandt


text:
When will the use of collab be released?

I can't do machine learning on my computer.
I want to use this model right away with my dataset. Is there any way?

I will implement a colab in the coming days :)

Done :heavy_check_mark:

authors: shampooooo xl-sr


text:
Are you planning to support uncertainty evaluation?

Hi,
It seems that the current sdfstudio lacks an uncertainty evaluation of the results. Noticed that similar work exists in nerf and has shown great results (such as BayesRays). Are you planning to support uncertainty evaluation for sdf-based nerf?
I think it’s very interesting and meaningful.

Hi, uncertainty estimation is very interesting but I am not sure if BayesRays is directly applicable here. Contributions are very much welcome.

repo: autonomousvision/sdfstudio


text:
The training effect is very poor！

I used four 3080ti, the CPU was 40 cores, and I trained for 41 times, the training duration was 37 hours, and the training code was CUDA_VISIBLE_DEVICES=0,1,2,3 OMP_NUM_THREADS=40 OPENBLAS_NUM_THREADS=1 torchrun --nnodes=1 --nproc_per_node=4 --max_restarts=0 --rdzv_id=1234576890 --rdzv_backend=c10d train.py --root_dir /home/ubuntu/ZY/ZY_2T/PROJECT_AUTO/transfuser/dataset  --parallel_training 1 --batch_size 12, not using all 210G data sets, but only using about 160G data sets, as shown in the following figure.

However, the test result of the trained model is very poor. The test code is, and the visual results are as follows bash leaderboard/scripts/local_evaluation.sh.

What is the problem? I hope to get a solution, and I will be very grateful.

This looks like a bug or something is wrong with the setup.
Could you set loading to strict to see whether the model was loaded correctly.
Did the training losses go down properly?

I followed your instructions and encountered two issues:
1)My total training loss is shown in the figure below.

2)The error message when strict is set to True is different for my model and the Transfuser model (both fail to execute with strict set to True). Figure 1 shows the error message for my_train_model, and Figure 2 shows the error message for the Transfuser model (since the full message cannot be displayed, I have also submitted error.txt for my_model).

error.txt
The loss seems normal, so as you mentioned, the issue is likely related to model loading. However, based on the error messages, I can't determine the exact problem. I hope to get your advice, thank you!

The error for the Transfuser model is normal, it was trained with an older codebase.
It probably has something to do with the name.
Did you change how the model was saved here?
When trained with distributed data parallel we remove part of the name that comes from ddp here.
Are there any optimizer files in your model folder (that could get loaded accidentally)?

You are right. I found that my training results seem to contain optimization files (as shown in Figure 1 below). My submission_agent.py is shown in Figure 2 below, and the training code is CUDA_VISIBLE_DEVICES=0,1,2. 3 OMP_NUM_THREADS=40 OPENBLAS_NUM_THREADS=1 torchrun --nnodes=1 --nproc_per_node=4 --max_restarts=0 --rdzv_id=1234576890 --rdzv_backend=c10d train.py - -root _ dir/home/Ubuntu/zy/zy _ 2t/project _ auto/transfuser/dataset-parallel _ training1-batch _ size12, what's wrong with this training result? When I use model_41.pth+optimizer_41.pth, the problem is that the vehicle directly turns right and deviates from the route. When I only use the model_41.pth file, the problem is that the vehicle does not move at all (if the transfuser model is used, the vehicle runs well).

Your training result seems correct.
Inference needs to be different. The correct way to use the code is to copy the args.txt + model_31.pth file into a new folder (no optimizer files) and use this folder for inference.
Then you should not get any error when you load the model with strict.
Can you send the visualization file again when you do this.

Typically epoch 31 yields the best or close to the best results.
Sometimes TransFuser gets stuck due to causal confusion. If it does not happen very often this is normal.
After a while a crepping mechanism will unblock it if this happens. This is discussed in Table 10 of the paper.

Then it means that I should directly change the default epoch=41 to 31 and use 31 as the final model, which can also reduce the training time.

you can do that. We have done that as well in our follow up work.

Ok, thank you for your patience. I appreciate it very much. I will close this question.

repo: autonomousvision/transfuser


text:
docs: add perception design

Description

This PR contains following three documents.

Perception component design
Perception component Reference Implementation Design
Perception Interface Design

These documents are written for sharing the design philosophy with engineers who want to contribute to Perception Component in autoware.

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The Reviewers must check the checkboxes below before approval.

[x] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[x] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

@mitsudome-r @xmfcx
I had left this document in draft for a while, but it has now been updated by my team, and the review process is complete.
I believe it's fine to be merged, but do you have any concerns?


text:
behavior_path_planner crashes when it is launched in .launch.py for the scenario UC-PB-002-0001-Hsinchu

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I'm convinced that this is not my fault but a bug.

Description
This issue is a part of https://github.com/autowarefoundation/autoware.universe/issues/566
behavior_path_planner crashes when it is launched using behavior_planning.launch.py which it is running along with other launch files once UC-PB-002-0001-Hsinchu is run with scenario_test_runner
[openscenario_interpreter_node-3] [component_container_mt-13] terminate called after throwing an instance of 'std::bad_alloc'
[openscenario_interpreter_node-3] [component_container_mt-13]   what():  std::bad_alloc
[openscenario_interpreter_node-3] [ERROR] [component_container_mt-13]: process has died [pid 6215, exit code -6, cmd '/opt/ros/galactic/lib/rclcpp_components/component_container_mt --ros-args -r __node:=behavior_planning_container -r __ns:=/planning/scenario_planning/lane_driving/behavior_planning --params-file /tmp/launch_params_mep7xn71'].

Full log file is here (bpp_bad_alloc.txt)
Video is here.
Here you can observe that behavior_planning_container  is died and it is because behavior_path_planner crashes.
So if one would  launch scenario_test_runner after disabling the line behavior_path_planner_component in the launch file and then run behavior_path_planner with the following code ; it doesn't crash.
source ~/autoware/install/setup.bash && \
ros2 run behavior_path_planner behavior_path_planner \
--ros-args \
-r __ns:=/planning/scenario_planning/lane_driving/behavior_planning \
-r __node:=behavior_path_planner \
-r behavior_path_planner/input/route:=/planning/mission_planning/route \
-r behavior_path_planner/input/vector_map:=/map/vector_map \
-r behavior_path_planner/input/perception:=/perception/object_recognition/objects \
-r behavior_path_planner/input/odometry:=/localization/kinematic_state \
-r behavior_path_planner/input/scenario:=/planning/scenario_planning/scenario \
-r behavior_path_planner/input/external_approval:=/planning/scenario_planning/lane_driving/behavior_planning/behavior_path_planner/path_change_approval \
-r behavior_path_planner/input/force_approval:=/planning/scenario_planning/lane_driving/behavior_planning/behavior_path_planner/path_change_force \
-r behavior_path_planner/output/path:=path_with_lane_id \
-r behavior_path_planner/output/ready:=/planning/scenario_planning/lane_driving/behavior_planning/behavior_path_planner/ready_module \
-r behavior_path_planner/output/running:=/planning/scenario_planning/lane_driving/behavior_planning/behavior_path_planner/running_modules \
-r behavior_path_planner/output/force_available:=/planning/scenario_planning/lane_driving/behavior_planning/behavior_path_planner/force_available \
-r behavior_path_planner/output/turn_indicators_cmd:=/planning/turn_indicators_cmd \
-r behavior_path_planner/output/hazard_lights_cmd:=/planning/hazard_lights_cmd \
-p bt_tree_config_path:=$HOME/autoware/src/universe/autoware.universe/planning/behavior_path_planner/config/behavior_path_planner_tree.xml \
--params-file $HOME/autoware/src/universe/autoware.universe/launch/tier4_planning_launch/config/scenario_planning/lane_driving/behavior_planning/behavior_path_planner/side_shift/side_shift.param.yaml \
--params-file $HOME/autoware/src/universe/autoware.universe/launch/tier4_planning_launch/config/scenario_planning/lane_driving/behavior_planning/behavior_path_planner/avoidance/avoidance.param.yaml \
--params-file $HOME/autoware/src/universe/autoware.universe/launch/tier4_planning_launch/config/scenario_planning/lane_driving/behavior_planning/behavior_path_planner/lane_change/lane_change.param.yaml \
--params-file $HOME/autoware/src/universe/autoware.universe/launch/tier4_planning_launch/config/scenario_planning/lane_driving/behavior_planning/behavior_path_planner/lane_following/lane_following.param.yaml \
--params-file $HOME/autoware/src/universe/autoware.universe/launch/tier4_planning_launch/config/scenario_planning/lane_driving/behavior_planning/behavior_path_planner/pull_over/pull_over.param.yaml \
--params-file $HOME/autoware/src/universe/autoware.universe/launch/tier4_planning_launch/config/scenario_planning/lane_driving/behavior_planning/behavior_path_planner/pull_out/pull_out.param.yaml \
--params-file $HOME/autoware/src/universe/autoware.universe/launch/tier4_planning_launch/config/scenario_planning/lane_driving/behavior_planning/behavior_path_planner/behavior_path_planner.param.yaml \
--params-file $HOME/autoware/src/universe/autoware.universe/vehicle/vehicle_info_util/config/vehicle_info.param.yaml

!!! Please give the right file paths if your autoware repo is now at $HOME !!!
Expected behavior
behavior_path_planner shouldn't crash.
Actual behavior
behavior_path_planner crashes for a certain scenario.
Steps to reproduce

Download map_data.
Download the scenario file.
Launch the scenario_test_runner with the following code after setting the right file paths:

source ~/autoware/install/setup.bash && \
ros2 launch scenario_test_runner scenario_test_runner.launch.py sensor_model:=sample_sensor_kit vehicle_model:=sample_vehicle \
scenario:=$HOME/operational-design-domains/public_road_bus/UC-PB-002-0001-Hsinchu.yaml \
architecture_type:=awf/universe launch_rviz:=true launch_autoware:=true

Versions

OS: Ubuntu 20.04
ROS2 Galactic
https://github.com/autowarefoundation/autoware/commit/5e76cfd1a0359d6c275accadfa5dc2dff9f0d861
autoware.universe: https://github.com/autowarefoundation/autoware.universe/commit/932ff58be7f51a8461def4bd57876f3bd766e2aa
https://github.com/tier4/scenario_simulator_v2/commit/7318ece6d59bed4b7a82d648af34113a2e8faf39
Operational Design Domains: c589c2

Possible causes
No response
Additional context
No response

I would appreciate if someone else also can produce the error.

Well, I was also confused about this kind of issue. Sometimes lateral controller or even the whole control module was not able to be launched successfully either, and the info displayed was just like above "process has died" without any other helpful description. I had to relaunch the module or node individually.

@JianKangEgon
Thank you for the input, It might be related to the container structure and the memory allocation related to it I guess.

Investigation
I reproduced the issue by following the Steps to reproduce.
The only way (as far as I know) to debug a ComposableNode is with a core dump.
# enable core dump of unlimited size
ulimit -c unlimited
# add pid to file name
echo -n 1 | sudo tee /proc/sys/kernel/core_uses_pid

After reproducing the error, it generates a core file that can be replayed with gdb.

:warning: Usually this file goes in the current folder but with the scenario_test_runner I am not able to find the location of the file.
Alternative: a crash file /var/crash/_opt_ros_galactic_lib_rclcpp_components_component_container_mt.1000.crash was generated.

The crash file needs to be unpacked apport-unpack /var/crash/_opt_ros_galactic_lib_rclcpp_components_component_container_mt.1000.crash crash_folder.
The crash_folder then contains the CoreDump and other information (e.g., ExecutablePath with the path to the executable that crashed).
Now we can debug with gdb `cat ExecutablePath` CoreDump.

After checking the backtrace, the only issues I could find are vectors within autoware_auto_perception_msgs::msg::PredictedPath objects that have a larger length than capacity (std::vector of length 2497072894800, capacity 2497072894629) and negative length (std::vector of length -22769416, capacity 60).
Solution
The PredictedPath message definition is currently written in IDL format with a capacity limit of 100 to its path field. Removing this capacity limit and rebuilding Autoware solves the issue and I was able to run the complete scenario without any crash.
I opened a PR to remove this capacity: https://github.com/tier4/autoware_auto_msgs/pull/32
Please test it and confirm that this fixes the issue.

@maxime-clem
Thank you for the solution you proposed however that didn't work for me even though I deleted build/install/log just to be sure and checked out your branch (fix-PredictedPath-remove_capacity_limit) and re-build whole autoware repo. Yet the same issue is still there.

Sorry for my previous post. I was too quick to claim that the issue was solved.
I have found two problems so far that cause crashes of the behavior_path_planner.

std::bad_alloc happens when copying some messages.

I have not found the root cause yet but some messages seem to have impossible sizes (e.g., std::vector of length -17545788653642, capacity -17545788653637 as reported by gdb).
Avoiding unnecessary copies help with this issue but they still sometimes occur (https://github.com/maxime-clem/autoware.universe/commit/6fe4bf7de76792fa21c36d941c66f0fffa79db2d).
The capacity of IDL messages may be related to this issue but I need to experiment more to confirm that.

vector::_M_range_check happens when accessing pre-calculated indexes that somehow becomes out of bound.

For example: https://github.com/autowarefoundation/autoware.universe/blob/main/planning/behavior_path_planner/src/scene_module/lane_change/util.cpp#L373-L383

Indexes for elements inside PredictedObjects::ConstSharedPtr dynamic_objects are precalculated.
By the time the elements are accessed using these indexes, they can become out of bound.

The only explanation I can find is that the pointer is updated while the function is running, changing to a message with less elements such that some of the calculated indexes are out of bound.
Passing the PredictedObjects::ConstSharedPtr by value rather than by reference seems to solve the issue (https://github.com/maxime-clem/autoware.universe/commit/ca3b9afaf6dc0c9aafb4a0e9217c599a61d478dd) but I need to confirm that this works correctly.

These issues do not happen consistently and with my current test branch (https://github.com/maxime-clem/autoware.universe/tree/fix-issue1049-behavior_path_planner_crashes) I am sometimes able to run the full scenario without any crash.
I will keep investigating but any help or suggestion would be welcome.

@maxime-clem happens the same when I test UC-PB-009-0001_Db20-Shalun as well. For the versions that I test please check here.

@mehmetdogru Thank you for reporting another scenario where the issue occurs.
I made a fix that should solve the issue for both scenarios: https://github.com/autowarefoundation/autoware.universe/pull/1091

authors: JianKangEgon maxime-clem mehmetdogru


text:
fix(ekf_localizer): update the state and publish the estimated pose only after initialization

Description
ekf_localizer has a bug that it publishes the default pose (identity) and accepts poses and twists for state update even before state initialization.
To resolve this error, I added a flag that manages the initialization state and made them update the state and publish messages only after the state initialization.
Related links
https://github.com/autowarefoundation/autoware.universe/issues/1421
Tests performed
The test really needs to be added. But a lot of refactoring work is necessary before writing tests.

Notes for reviewers

This behavior change can affect other Autoware modules. Please carefully read the code and validate the behavior
I added the branch to the original repository so that other people can commit to this

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

@IshitaTakeshi Are there any updates on this? What is still needed before making this ready for review?

@mitsudome-r No, so I turned this into ready

LGTM from the localization module perspective, but I cannot tell whether other modules (e.g. planning, perception) will be OK as well...

@IshitaTakeshi It seems that the semantic-pull-request failed since the commit message is not the same as the PR title.
Would you fix this?

I think that both the commit message and the PR title are valid. Why does it fail?

@IshitaTakeshi
This PR contains only one commit Update the state and publish pose only after initialization
you need to set commit message  fix(ekf_localizer): update the state and publish the estimated pose only after initialization to the first commit or add more commit to this PR.
I suggest to set first commit message to fix(ekf_localizer): update the state and publish the estimated pose only after initialization

Changed the commit message

authors: IshitaTakeshi kminoda mitsudome-r taikitanaka3


text:
fix: remove rtc staus when no avoidance candidate is output

Signed-off-by: tomoya.kimura tomoya.kimura@tier4.jp
Description

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[ ] I've confirmed the contribution guidelines.
[ ] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

Result:
https://user-images.githubusercontent.com/59680180/185597652-f0f872bb-a947-41ba-b2ef-ef774600036a.mp4
https://user-images.githubusercontent.com/59680180/185597662-6f457cd6-f390-4d82-8bbe-ab4058f058fd.mp4


text:
feat(mission_planner): refine goal pose with parameter and add config file

Description
This PR adds config file to mission_planner and  parameter for refining goal pose in order to skip goal validation step. If added parameter is set to true, then given goal is refined according to the closest lane orientation.
autoware_launch PR (must be merged with this PR): https://github.com/autowarefoundation/autoware_launch/pull/225
Tests performed
https://user-images.githubusercontent.com/56237550/212691970-35c7803d-7609-4d29-886b-e0a08274dc06.mp4
Notes for reviewers

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

@takayuki5168 Hi, I also added config file for mission planner . Could you check it?

@takayuki5168 thanks for the review, i updated the branch with your suggestions :+1: .

LGTM


text:
Can not install Autoware by source

Bug report
Required information:

Operating system and version:

<Ubuntu 16.04, ROS kinetic>

Autoware installation type:

Autoware version or commit hash

ROS distribution and version:

ROS installation type:

Package or library, if applicable:

Description of the bug
<Hi everyone,
After finish all the install procedure for Autoware,  in the last step when I start "./catkin_make_release", the terminal says bash: /.catkin_make_release : there is no such file. Could you help me to solve this problem? >
Steps to reproduce the bug

Expected behavior

Actual behavior

Screenshots

Additional information

Thanks for using Autoware and for your question. However the issue tracker is for posting confirmed bugs and feature requests.
We ask that you please ask questions at the ROS Answers website following our support guidelines: https://github.com/autowarefoundation/autoware/wiki/Support-guidelines#ros-answers. Please pay particular attention to the information we ask you to provide.

authors: FleverX gbiggs

repo: autowarefoundation/autoware


text:
Lanelet misplaced in Autoware

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I'm convinced that this is not my fault but a bug.

Description
I have draw a simple lanelet using Tier IV Vector Map Builder. But when I load it to Autoware (using 713dfa1b8d118557226473f5f596877ce137c9e1), the lanelet is wrongly located.
Expected behavior
Based on how I draw it on Tier IV Vector Map Builder, it should look like this;

Actual behavior
Below is how it is located.

Not only that, the lanelet we draw is only for a short distance, but the shown looks like have longer distance.
Steps to reproduce

Assume Autoware has been configured.
Run autoware command: ros2 launch autoware_launch autoware.launch.xml vehicle_model:=sample_vehicle sensor_model:=sample_sensor_kit map_path:=$HOME/ros2_ws/map-one
Wait until Autoware full load (PCD and lanelet).
Issue reproduced.

Versions

OS: Ubuntu 22.04.2 LTS
ROS2: Humble
Autoware: 713dfa1b8d118557226473f5f596877ce137c9e1

Possible causes
We assume that newer version of Autoware have the ability to know if the pointcloud is global shifted or not. Because we never had this issue on previous version of Autoware.
Additional context
No response

Try modifying the projection type in lanelet2_map_loader to local from the default MGRS
https://github.com/autowarefoundation/autoware_launch/blob/c6312c7dcaa8fdcf17b54c11953b2c23861cd577/autoware_launch/config/map/lanelet2_map_loader.param.yaml#L3
We have made change to the projector in https://github.com/autowarefoundation/autoware.universe/pull/3492, and user must choose the local projection type explicitly if the map is using local coordinates from pointcloud.

Thank you @mitsudome-r for your response. I have made the changes from the default MGRS to local as you suggest.
I will now close this issue.


text:
Fix spelling issues

Hello
I found several spelling issues in your docs.
Glad I could help
Br, Elias.

Hey, thank you for your contribution.
We try to stay as close as possible to the upstream repo and we don't want to fix something that could be a conflict later.
You can make the same PR in the upstream repo.

repo: availproject/avail-apps


text:
Add pc-rtems BSP to OSAL

For development under RTEMS it is helpful to have a basic BSP that does not require any special development boards.
The RTEMS project provides this via the "pc686" BSP. This makes it possible to boot and run an RTEMS application on ordinary commodity PC hardware.
This also boots and runs in virtual machines i.e. QEMU which is very desirable for testing.
This ticket will add a "pc-rtems" BSP to OSAL that can be used for this purpose.

Imported from trac issue 29.  Created by jphickey on 2015-03-18T14:31:39, last modified: 2015-11-20T16:22:16

Trac comment by jphickey on 2015-03-18 23:01:18:
Pushed branch "trac-29-pc-rtems", commit [changeset:eec4f2f]
This adds a simple RTEMS BSP that runs using the "pc686" BSP from the upstream RTEMS.

Trac comment by jphickey on 2015-04-14 13:11:37:
This changeset has been rebased to the (unapproved) 2015-04-14 baseline
This is due to a dependency on files added/changed as part of that baseline.  Attempting to base this change on the official 2015-02-26 OSAL is potentially possible but will result in merge conflicts when putting these back together again.
The new commit is [changeset:22da0be]

Trac comment by glimes on 2015-05-18 20:24:10:
Accept, based on the [changeset:cb82d8f] commit. I'm not an RTEMS
expert and can't test it -- but presuming it works, it seems like
a slam-dunk to include it.

Trac comment by glimes on 2015-07-13 13:17:21:
accept
(with the caveat that I'm not an RTEMS expert,
and do not currently have an RTEMS build environment)

Trac comment by jphickey on 2015-07-09 14:41:26:
== REBASED AND UPDATED ==
For the 2015-07-14 CCB review/discussion
This has been rebased to the current OSAL development baseline, commit [changeset:c50630e] reflects the current proposed modifications.
In addition to adding the pc-rtems BSP, this also integrates with the unit testing framework that was approved at the 2015-06-30 CCB so that the unit tests can be executed on RTEMS using this BSP.
This has been tested by running the a pc686 RTEMS build in QEMU and confirmed that all unit tests are passing in this environment.

Trac comment by acudmore on 2015-07-10 15:14:12:
This will be good, recommend accept

Trac comment by sstrege on 2015-07-13 18:58:39:
accept

Trac comment by sduran on 2015-07-14 11:51:30:
accept

Trac comment by jwilmot on 2015-07-14 12:37:39:
Recommend accept.

Trac comment by glimes on 2015-07-16 10:23:12:
Included in [changeset:ec67bd4 2015-07-14 development merge],
now present on Babelfish and IPAS-LIB.


text:
fileinfo crashes when initializing Asn1Sequence during digital-signature verification

fileinfo crashes when initializing Asn1Sequence during digital-signature verification of the PE file below.
Input
Run
$ retdec-fileinfo FILE

where FILE is:

21617B9A2D143CBFBE7B84DB794763415E1F3FA391483F805FE5B13D255B0B80

Output
Segmentation fault

Expected output
fileinfo does not crash when analyzing the file.
Output from valgrind
Invalid read of size 1
   at 0x4C33B58: memmove (vg_replace_strmem.c:1258)
   by 0x243593: unsigned char* std::__copy_move<...>::__copy_m<unsigned char>(...) (stl_algobase.h:368)
   by 0x243515: unsigned char* std::__copy_move_a<...>(...) (stl_algobase.h:386)
   by 0x322DB8: __gnu_cxx::__normal_iterator<...> std::__copy_move_a2<...>(...) (stl_algobase.h:422)
   by 0x3225B7: __gnu_cxx::__normal_iterator<...> std::move<...>(...) (stl_algobase.h:488)
   by 0x322037: std::vector<...>::_M_erase(...) (vector.tcc:171)
   by 0x3217A3: std::vector<...>::erase(...) (stl_vector.h:1210)
   by 0x320B04: retdec::fileformat::Asn1Sequence::init() (asn1.cpp:248)
   by 0x320947: retdec::fileformat::Asn1Sequence::Asn1Sequence(...) (asn1.cpp:226)
   by 0x325951: void __gnu_cxx::new_allocator<...>::construct<...>(...) (new_allocator.h:136)
   by 0x32516F: void std::allocator_traits<...>::construct<...>(...) (alloc_traits.h:475)
   by 0x3248B3: std::_Sp_counted_ptr_inplace<...>::_Sp_counted_ptr_inplace<...>(...) (shared_ptr_base.h:526)
 Address 0x74b6f87 is 20 bytes after a block of size 19 alloc'd
   at 0x4C2D54F: operator new(unsigned long) (vg_replace_malloc.c:334)
   by 0x242C85: __gnu_cxx::new_allocator<unsigned char>::allocate(unsigned long, void const*) (new_allocator.h:111)
   by 0x242821: std::allocator_traits<...>::allocate(std::allocator<unsigned char>&, unsigned long) (alloc_traits.h:436)
   by 0x2422BD: std::_Vector_base<...>::_M_allocate(unsigned long) (stl_vector.h:172)
   by 0x322469: void std::vector<...>::_M_range_initialize<...>(...) (stl_vector.h:1323)
   by 0x321ED3: void std::vector<...>::_M_initialize_dispatch<...>(...) (stl_vector.h:1299)
   by 0x32161C: std::vector<...>::vector<__gnu_cxx::__normal_iterator<...>, void>(...) (stl_vector.h:414)
   by 0x31FF32: retdec::fileformat::Asn1Item::getContentData() const (asn1.cpp:111)
   by 0x320A34: retdec::fileformat::Asn1Sequence::init() (asn1.cpp:241)
   by 0x320947: retdec::fileformat::Asn1Sequence::Asn1Sequence(...) (asn1.cpp:226)
   by 0x325951: void __gnu_cxx::new_allocator<...>::construct<...>(...) (new_allocator.h:136)
   by 0x32516F: void std::allocator_traits<...>::construct<...>(...) (alloc_traits.h:475)

Analysis
PeFormat::verifySignature() in src/fileformat/file_format/pe/pe_format.cpp contains the following code:
1226   std::vector<std::uint8_t> contentInfoData(contentInfoPtr, contentInfoPtr + contentInfoLen);
1227   auto contentInfo = Asn1Item::parse(contentInfoData);

On line 1227, Asn1Item::parse() gets called, which, in the end, constructs Asn1Sequence:
60     case Asn1Tag_Sequence:
61         return std::make_shared<Asn1Sequence>(data);

The constructor of Asn1Sequence calls Asn1Sequence::init(), which contains the following code:
240 void Asn1Sequence::init()
241 {
242     auto contentData = getContentData();
243     while (!contentData.empty())
244     {
245         auto element = Asn1Item::parse(contentData);
246         if (element == nullptr)
247             return;
248
249         contentData.erase(contentData.begin(), contentData.begin() + element->getLength());
250         _elements.push_back(std::move(element));
251     }
252 }

On line 249, attempts to erase elements from contentData are made. However, in one of the attempts, contentData.size() is 7 but element->getLength() returns 39, which is more than contentData.size(). This access results in a segmentation fault.
Configuration

Commit: 4b94da8f90ddc3101a7f9558353d93c60408c3b9 (current master)
64b Arch Linux, GCC 7.3.0, Debug build of RetDec

I have added an assertion into Asn1Sequence::init() until this issue is fixed (08953bb74cfae7b959e9df9a1dfa97e965136c3e). In this way, we will know when we stumble upon this problem in the future.

I added a check that prevents moving vector iterator beyond vector end. Fixing the problem this way was not that complicated. I also attempted to find out why this situation happened in the first place. The problem is that Asn1Item element created from data has greater size than the data itself. I was not able to find any obvious bug here, it looks like the algorithm to create Asn1Sequence allows this - it somehow computes the size of element and this computation gives this greater value.

repo: avast-tl/retdec


text:
retdec-decompiler.py: error: the following arguments are required: FILE

The retdec\bin directory is already in my windows env path.
I am using retdec-offline plugin for binary ninja, upon decompilation the plugin generated the following command line for retdec-decompiler.py :
retdec-decompiler.py --backend-no-debug-comments --cleanup --mode raw --raw-section-vma 0x43e52d --raw-entry-point 0x43e52d --arch x86 --endian little --config C:\Users\nameless\AppData\Local\Temp\tmpf5bjocmg C:\Users\nameless\AppData\Local\Temp\tmpursu763x

But no matter what i have done, retdec always failed to seek the FILE or tmpursu763x
retdec-decompiler.py: error: the following arguments are required: FILE

The generated config file and the target file attached :
FILE.zip
What could be wrong?
[EDIT]
Adding python complete path into the command line is make it work :
"C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64\python.exe" C:\Users\nameless\Documents\Tools\Retdec\bin\retdec-decompiler.py --backend-no-debug-comments --cleanup --mode raw --raw-section-vma 0x43e52d --raw-entry-point 0x43e52d --arch x86 --endian little --config C:\Users\nameless\AppData\Local\Temp\tmpf5bjocmg C:\Users\nameless\AppData\Local\Temp\tmpursu763x

On *.py i have set it to use C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64\python.exe

Found out the solution is to put or hard-coded the python path and put the hardcoded "retdec-decompiler.py" path, is there any plan to make retdec-decompiler.py understand it's own relative-path?

Hi. This seems to be an issue in retdec-offline (a 3rd-party project that we have no affiliation with). As you can see in our README, the way to run RetDec on Windows is by specifying the path to the retdec-decompiler.py script:
python $RETDEC_INSTALL_DIR/bin/retdec-decompiler.py test.exe

Specifying the full path to python.exe should not be necessary (unless it is not reachable from your system's PATH).
As for the following question:

Is there any plan to make retdec-decompiler.py understand it's own relative-path?

Can you please elaborate what do you mean by "understand it's own relative path"?

@s3rvac
What i have meant is running retdec without hardcoding the full retdec-decompiler.py path by adding the retdec bin directory into environment variable.

What i have meant is running retdec without hardcoding the full retdec-decompiler.py path by adding the retdec bin directory into environment variable.

On Windows, this can be achieved as follows:

Add the path to retdec\bin into your system's PATH.
Open a new instance of cmd.exe.
Run retdec-decompiler.py. If Windows ask you by which application you want to open the script, select your Python installation.

After this, you should be able to run just retdec-decompiler.py (i.e. without python in front) from the command line instead of via python path\to\retdec\bin\retdec-decompiler.py.
Please note that running python retdec-decompiler.py on Windows will only work if you are in the bin directory (see below).
Also, please note that since this is a retdec repository, I am only talking about retdec, not about retdec-offline, as I do not know anything about retdec-offline.

Currently even i am moving my position in the windows command prompt into retdec bin directory, it's still required to use the retdec-decompiler.py full path.

This is not necessary. I have just tried that in Windows 7 and it works:
# Open cmd.exe
cd path\to\retdec\bin
python retdec-decompiler.py --help
retdec-decompiler.py --help

The last two commands correctly print the help. Can you please elaborate on why is it still required to use a full path for you? Maybe you are doing something differently than I and we misunderstand each other.
Please, let me know if this has answered your questions.

Closing due to inactivity. If the issue persists, please re-open (but please read the above comment and give us your feedback on it).

repo: avast/retdec


text:
Add option to split out some columns into separate user table

For example the I get/use column in Networks or the Last watched IMDB ect columns in Shows in the Watchlist app.

Added property to map columns
Columns to be placed in separate table linked to source table (Sheet1 in example below) and a user in the account table.
Sheet1.user=E
Column list in Sheet2DB.strToCols() format.


text:
Support only newer versions of Vim (8+) and NeoVim

As Ubuntu LTS has already move to next version of vim(vim 8) and looking for async performance improvements, I think we can support by now vim 8+ and neovim.

Because of  0dadff61a57537acfbd1654ad32250452afa43de and d52cc948dc56d9230a62444b72c64955b6d0b68e, we can close this issue.

repo: avelino/vim-bootstrap

license: mit

license_source: bigquery


text:
JJ.	Alerter l’étudiant quand il modifie une trace

Informer l’étudiant que s’il modifie un lien ou un fichier dans un trace qu’il faudra qu’il supprime la trace dans la page action telle qu’une saé sinon le lien depuis la page saé vers le fichier dans la trace ne fonctionnera plus

Une bulle d'aide expliquera comment faire si on change le libellé de la trace.

@AdrienPrugnaud pourquoi cette ré-ouverture ?

Fait

authors: AdrienPrugnaud giraudin jgribonvald olivier-gerbe

repo: avenirs-esr/Karuta-APC


text:
Update Javadoc to be compliant with Java-17

Java-17 is a bit stricter on Javadoc. Unmatched tags are sometimes throwing an error.
Furthermore, the Version with a $Revision$ from SVN is still part of some class descriptions. These lines can be removed.

No warnings anymore on maven clean javadoc:javadoc in the entire project.

repo: averbraeck/djutils


text:
Discussion: CSS color parser

My use case for CSS color parser is a WYSIWYG editor that produces CSS colors, the rendering is done in elm, I adjust some of the colors before rendering (like ensuring contrast...), that's where I need a CSS color parser.
Follow up of: https://github.com/avh4/elm-color/issues/4#issuecomment-419789478

I would definitely use this in my project. I think css colors are a de-facto interchange format for colors on the web, so if you need interop with a system you don't control, CSS colors are going to come into play.
Whether it should be in the core package is another question. Personally I'm a fan of a batteries included approach, so would support that.

@kuon you mentioned you possibly had some existing code for this?  Can you list the formats that it's able to parse?

rgb() rgba() hsl() hsla() and hex (both percentage and 0-255 ranges) it was written for 0.18
https://gist.github.com/kuon/19b14cd5f913c8b60c08dbbdb0156514
Consider it BSD3 licensed.
I read your hex parser and I think yours is better as it uses pattern matching instead of regex.

You should probably also include keyword colors in the parser:

Example using elm/parser
keywords : Parser Color
keywords =
    oneOf
        [ fromHexString "#000000" |. keyword "black"
        , fromHexString "#c0c0c0" |. keyword "silver"
        , fromHexString "#808080" |. keyword "gray"
        , fromHexString "#ffffff" |. keyword "white"
        , fromHexString "#800000" |. keyword "maroon"
        , fromHexString "#ff0000" |. keyword "red"
        , fromHexString "#800080" |. keyword "purple"
        , fromHexString "#ff00ff" |. keyword "fuchsia"
        , fromHexString "#008000" |. keyword "green"
        , fromHexString "#00ff00" |. keyword "lime"
        , fromHexString "#808000" |. keyword "olive"
        , fromHexString "#ffff00" |. keyword "yellow"
        , fromHexString "#000080" |. keyword "navy"
        , fromHexString "#0000ff" |. keyword "blue"
        , fromHexString "#008080" |. keyword "teal"
        , fromHexString "#00ffff" |. keyword "aqua"
        , fromHexString "#ffa500" |. keyword "orange"
        , fromHexString "#f0f8ff" |. keyword "aliceblue"
        , fromHexString "#faebd7" |. keyword "antiquewhite"
        , fromHexString "#7fffd4" |. keyword "aquamarine"
        , fromHexString "#f0ffff" |. keyword "azure"
        , fromHexString "#f5f5dc" |. keyword "beige"
        , fromHexString "#ffe4c4" |. keyword "bisque"
        , fromHexString "#ffebcd" |. keyword "blanchedalmond"
        , fromHexString "#8a2be2" |. keyword "blueviolet"
        , fromHexString "#a52a2a" |. keyword "brown"
        , fromHexString "#deb887" |. keyword "burlywood"
        , fromHexString "#5f9ea0" |. keyword "cadetblue"
        , fromHexString "#7fff00" |. keyword "chartreuse"
        , fromHexString "#d2691e" |. keyword "chocolate"
        , fromHexString "#ff7f50" |. keyword "coral"
        , fromHexString "#6495ed" |. keyword "cornflowerblue"
        , fromHexString "#fff8dc" |. keyword "cornsilk"
        , fromHexString "#dc143c" |. keyword "crimson"
        , fromHexString "#00ffff" |. keyword "cyan"
        , fromHexString "#00008b" |. keyword "darkblue"
        , fromHexString "#008b8b" |. keyword "darkcyan"
        , fromHexString "#b8860b" |. keyword "darkgoldenrod"
        , fromHexString "#a9a9a9" |. keyword "darkgray"
        , fromHexString "#006400" |. keyword "darkgreen"
        , fromHexString "#a9a9a9" |. keyword "darkgrey"
        , fromHexString "#bdb76b" |. keyword "darkkhaki"
        , fromHexString "#8b008b" |. keyword "darkmagenta"
        , fromHexString "#556b2f" |. keyword "darkolivegreen"
        , fromHexString "#ff8c00" |. keyword "darkorange"
        , fromHexString "#9932cc" |. keyword "darkorchid"
        , fromHexString "#8b0000" |. keyword "darkred"
        , fromHexString "#e9967a" |. keyword "darksalmon"
        , fromHexString "#8fbc8f" |. keyword "darkseagreen"
        , fromHexString "#483d8b" |. keyword "darkslateblue"
        , fromHexString "#2f4f4f" |. keyword "darkslategray"
        , fromHexString "#2f4f4f" |. keyword "darkslategrey"
        , fromHexString "#00ced1" |. keyword "darkturquoise"
        , fromHexString "#9400d3" |. keyword "darkviolet"
        , fromHexString "#ff1493" |. keyword "deeppink"
        , fromHexString "#00bfff" |. keyword "deepskyblue"
        , fromHexString "#696969" |. keyword "dimgray"
        , fromHexString "#696969" |. keyword "dimgrey"
        , fromHexString "#1e90ff" |. keyword "dodgerblue"
        , fromHexString "#b22222" |. keyword "firebrick"
        , fromHexString "#fffaf0" |. keyword "floralwhite"
        , fromHexString "#228b22" |. keyword "forestgreen"
        , fromHexString "#dcdcdc" |. keyword "gainsboro"
        , fromHexString "#f8f8ff" |. keyword "ghostwhite"
        , fromHexString "#ffd700" |. keyword "gold"
        , fromHexString "#daa520" |. keyword "goldenrod"
        , fromHexString "#adff2f" |. keyword "greenyellow"
        , fromHexString "#808080" |. keyword "grey"
        , fromHexString "#f0fff0" |. keyword "honeydew"
        , fromHexString "#ff69b4" |. keyword "hotpink"
        , fromHexString "#cd5c5c" |. keyword "indianred"
        , fromHexString "#4b0082" |. keyword "indigo"
        , fromHexString "#fffff0" |. keyword "ivory"
        , fromHexString "#f0e68c" |. keyword "khaki"
        , fromHexString "#e6e6fa" |. keyword "lavender"
        , fromHexString "#fff0f5" |. keyword "lavenderblush"
        , fromHexString "#7cfc00" |. keyword "lawngreen"
        , fromHexString "#fffacd" |. keyword "lemonchiffon"
        , fromHexString "#add8e6" |. keyword "lightblue"
        , fromHexString "#f08080" |. keyword "lightcoral"
        , fromHexString "#e0ffff" |. keyword "lightcyan"
        , fromHexString "#fafad2" |. keyword "lightgoldenrodyellow"
        , fromHexString "#d3d3d3" |. keyword "lightgray"
        , fromHexString "#90ee90" |. keyword "lightgreen"
        , fromHexString "#d3d3d3" |. keyword "lightgrey"
        , fromHexString "#ffb6c1" |. keyword "lightpink"
        , fromHexString "#ffa07a" |. keyword "lightsalmon"
        , fromHexString "#20b2aa" |. keyword "lightseagreen"
        , fromHexString "#87cefa" |. keyword "lightskyblue"
        , fromHexString "#778899" |. keyword "lightslategray"
        , fromHexString "#778899" |. keyword "lightslategrey"
        , fromHexString "#b0c4de" |. keyword "lightsteelblue"
        , fromHexString "#ffffe0" |. keyword "lightyellow"
        , fromHexString "#32cd32" |. keyword "limegreen"
        , fromHexString "#faf0e6" |. keyword "linen"
        , fromHexString "#ff00ff" |. keyword "magenta"
        , fromHexString "#66cdaa" |. keyword "mediumaquamarine"
        , fromHexString "#0000cd" |. keyword "mediumblue"
        , fromHexString "#ba55d3" |. keyword "mediumorchid"
        , fromHexString "#9370db" |. keyword "mediumpurple"
        , fromHexString "#3cb371" |. keyword "mediumseagreen"
        , fromHexString "#7b68ee" |. keyword "mediumslateblue"
        , fromHexString "#00fa9a" |. keyword "mediumspringgreen"
        , fromHexString "#48d1cc" |. keyword "mediumturquoise"
        , fromHexString "#c71585" |. keyword "mediumvioletred"
        , fromHexString "#191970" |. keyword "midnightblue"
        , fromHexString "#f5fffa" |. keyword "mintcream"
        , fromHexString "#ffe4e1" |. keyword "mistyrose"
        , fromHexString "#ffe4b5" |. keyword "moccasin"
        , fromHexString "#ffdead" |. keyword "navajowhite"
        , fromHexString "#fdf5e6" |. keyword "oldlace"
        , fromHexString "#6b8e23" |. keyword "olivedrab"
        , fromHexString "#ff4500" |. keyword "orangered"
        , fromHexString "#da70d6" |. keyword "orchid"
        , fromHexString "#eee8aa" |. keyword "palegoldenrod"
        , fromHexString "#98fb98" |. keyword "palegreen"
        , fromHexString "#afeeee" |. keyword "paleturquoise"
        , fromHexString "#db7093" |. keyword "palevioletred"
        , fromHexString "#ffefd5" |. keyword "papayawhip"
        , fromHexString "#ffdab9" |. keyword "peachpuff"
        , fromHexString "#cd853f" |. keyword "peru"
        , fromHexString "#ffc0cb" |. keyword "pink"
        , fromHexString "#dda0dd" |. keyword "plum"
        , fromHexString "#b0e0e6" |. keyword "powderblue"
        , fromHexString "#bc8f8f" |. keyword "rosybrown"
        , fromHexString "#4169e1" |. keyword "royalblue"
        , fromHexString "#8b4513" |. keyword "saddlebrown"
        , fromHexString "#fa8072" |. keyword "salmon"
        , fromHexString "#f4a460" |. keyword "sandybrown"
        , fromHexString "#2e8b57" |. keyword "seagreen"
        , fromHexString "#fff5ee" |. keyword "seashell"
        , fromHexString "#a0522d" |. keyword "sienna"
        , fromHexString "#87ceeb" |. keyword "skyblue"
        , fromHexString "#6a5acd" |. keyword "slateblue"
        , fromHexString "#708090" |. keyword "slategray"
        , fromHexString "#708090" |. keyword "slategrey"
        , fromHexString "#fffafa" |. keyword "snow"
        , fromHexString "#00ff7f" |. keyword "springgreen"
        , fromHexString "#4682b4" |. keyword "steelblue"
        , fromHexString "#d2b48c" |. keyword "tan"
        , fromHexString "#d8bfd8" |. keyword "thistle"
        , fromHexString "#ff6347" |. keyword "tomato"
        , fromHexString "#40e0d0" |. keyword "turquoise"
        , fromHexString "#ee82ee" |. keyword "violet"
        , fromHexString "#f5deb3" |. keyword "wheat"
        , fromHexString "#f5f5f5" |. keyword "whitesmoke"
        , fromHexString "#9acd32" |. keyword "yellowgreen"
        , fromHexString "#663399" |. keyword "rebeccapurple"
        , succeed (Color 0 0 0 0) |. keyword "transparent"
        ]

On September 11, 2018 1:06:01 PM GMT+02:00, Jakub Hampl notifications@github.com wrote:

You should probably also include keyword colors in the parser:

Example using elm/parser
keywords : Parser Color
keywords =
   oneOf
       [ fromHexString "#000000" |. keyword "black"
       , fromHexString "#c0c0c0" |. keyword "silver"
       , fromHexString "#808080" |. keyword "gray"
       , fromHexString "#ffffff" |. keyword "white"
       , fromHexString "#800000" |. keyword "maroon"
       , fromHexString "#ff0000" |. keyword "red"
       , fromHexString "#800080" |. keyword "purple"
       , fromHexString "#ff00ff" |. keyword "fuchsia"
       , fromHexString "#008000" |. keyword "green"
       , fromHexString "#00ff00" |. keyword "lime"
       , fromHexString "#808000" |. keyword "olive"
       , fromHexString "#ffff00" |. keyword "yellow"
       , fromHexString "#000080" |. keyword "navy"
       , fromHexString "#0000ff" |. keyword "blue"
       , fromHexString "#008080" |. keyword "teal"
       , fromHexString "#00ffff" |. keyword "aqua"
       , fromHexString "#ffa500" |. keyword "orange"
       , fromHexString "#f0f8ff" |. keyword "aliceblue"
       , fromHexString "#faebd7" |. keyword "antiquewhite"
       , fromHexString "#7fffd4" |. keyword "aquamarine"
       , fromHexString "#f0ffff" |. keyword "azure"
       , fromHexString "#f5f5dc" |. keyword "beige"
       , fromHexString "#ffe4c4" |. keyword "bisque"
       , fromHexString "#ffebcd" |. keyword "blanchedalmond"
       , fromHexString "#8a2be2" |. keyword "blueviolet"
       , fromHexString "#a52a2a" |. keyword "brown"
       , fromHexString "#deb887" |. keyword "burlywood"
       , fromHexString "#5f9ea0" |. keyword "cadetblue"
       , fromHexString "#7fff00" |. keyword "chartreuse"
       , fromHexString "#d2691e" |. keyword "chocolate"
       , fromHexString "#ff7f50" |. keyword "coral"
       , fromHexString "#6495ed" |. keyword "cornflowerblue"
       , fromHexString "#fff8dc" |. keyword "cornsilk"
       , fromHexString "#dc143c" |. keyword "crimson"
       , fromHexString "#00ffff" |. keyword "cyan"
       , fromHexString "#00008b" |. keyword "darkblue"
       , fromHexString "#008b8b" |. keyword "darkcyan"
       , fromHexString "#b8860b" |. keyword "darkgoldenrod"
       , fromHexString "#a9a9a9" |. keyword "darkgray"
       , fromHexString "#006400" |. keyword "darkgreen"
       , fromHexString "#a9a9a9" |. keyword "darkgrey"
       , fromHexString "#bdb76b" |. keyword "darkkhaki"
       , fromHexString "#8b008b" |. keyword "darkmagenta"
       , fromHexString "#556b2f" |. keyword "darkolivegreen"
       , fromHexString "#ff8c00" |. keyword "darkorange"
       , fromHexString "#9932cc" |. keyword "darkorchid"
       , fromHexString "#8b0000" |. keyword "darkred"
       , fromHexString "#e9967a" |. keyword "darksalmon"
       , fromHexString "#8fbc8f" |. keyword "darkseagreen"
       , fromHexString "#483d8b" |. keyword "darkslateblue"
       , fromHexString "#2f4f4f" |. keyword "darkslategray"
       , fromHexString "#2f4f4f" |. keyword "darkslategrey"
       , fromHexString "#00ced1" |. keyword "darkturquoise"
       , fromHexString "#9400d3" |. keyword "darkviolet"
       , fromHexString "#ff1493" |. keyword "deeppink"
       , fromHexString "#00bfff" |. keyword "deepskyblue"
       , fromHexString "#696969" |. keyword "dimgray"
       , fromHexString "#696969" |. keyword "dimgrey"
       , fromHexString "#1e90ff" |. keyword "dodgerblue"
       , fromHexString "#b22222" |. keyword "firebrick"
       , fromHexString "#fffaf0" |. keyword "floralwhite"
       , fromHexString "#228b22" |. keyword "forestgreen"
       , fromHexString "#dcdcdc" |. keyword "gainsboro"
       , fromHexString "#f8f8ff" |. keyword "ghostwhite"
       , fromHexString "#ffd700" |. keyword "gold"
       , fromHexString "#daa520" |. keyword "goldenrod"
       , fromHexString "#adff2f" |. keyword "greenyellow"
       , fromHexString "#808080" |. keyword "grey"
       , fromHexString "#f0fff0" |. keyword "honeydew"
       , fromHexString "#ff69b4" |. keyword "hotpink"
       , fromHexString "#cd5c5c" |. keyword "indianred"
       , fromHexString "#4b0082" |. keyword "indigo"
       , fromHexString "#fffff0" |. keyword "ivory"
       , fromHexString "#f0e68c" |. keyword "khaki"
       , fromHexString "#e6e6fa" |. keyword "lavender"
       , fromHexString "#fff0f5" |. keyword "lavenderblush"
       , fromHexString "#7cfc00" |. keyword "lawngreen"
       , fromHexString "#fffacd" |. keyword "lemonchiffon"
       , fromHexString "#add8e6" |. keyword "lightblue"
       , fromHexString "#f08080" |. keyword "lightcoral"
       , fromHexString "#e0ffff" |. keyword "lightcyan"
       , fromHexString "#fafad2" |. keyword "lightgoldenrodyellow"
       , fromHexString "#d3d3d3" |. keyword "lightgray"
       , fromHexString "#90ee90" |. keyword "lightgreen"
       , fromHexString "#d3d3d3" |. keyword "lightgrey"
       , fromHexString "#ffb6c1" |. keyword "lightpink"
       , fromHexString "#ffa07a" |. keyword "lightsalmon"
       , fromHexString "#20b2aa" |. keyword "lightseagreen"
       , fromHexString "#87cefa" |. keyword "lightskyblue"
       , fromHexString "#778899" |. keyword "lightslategray"
       , fromHexString "#778899" |. keyword "lightslategrey"
       , fromHexString "#b0c4de" |. keyword "lightsteelblue"
       , fromHexString "#ffffe0" |. keyword "lightyellow"
       , fromHexString "#32cd32" |. keyword "limegreen"
       , fromHexString "#faf0e6" |. keyword "linen"
       , fromHexString "#ff00ff" |. keyword "magenta"
       , fromHexString "#66cdaa" |. keyword "mediumaquamarine"
       , fromHexString "#0000cd" |. keyword "mediumblue"
       , fromHexString "#ba55d3" |. keyword "mediumorchid"
       , fromHexString "#9370db" |. keyword "mediumpurple"
       , fromHexString "#3cb371" |. keyword "mediumseagreen"
       , fromHexString "#7b68ee" |. keyword "mediumslateblue"
       , fromHexString "#00fa9a" |. keyword "mediumspringgreen"
       , fromHexString "#48d1cc" |. keyword "mediumturquoise"
       , fromHexString "#c71585" |. keyword "mediumvioletred"
       , fromHexString "#191970" |. keyword "midnightblue"
       , fromHexString "#f5fffa" |. keyword "mintcream"
       , fromHexString "#ffe4e1" |. keyword "mistyrose"
       , fromHexString "#ffe4b5" |. keyword "moccasin"
       , fromHexString "#ffdead" |. keyword "navajowhite"
       , fromHexString "#fdf5e6" |. keyword "oldlace"
       , fromHexString "#6b8e23" |. keyword "olivedrab"
       , fromHexString "#ff4500" |. keyword "orangered"
       , fromHexString "#da70d6" |. keyword "orchid"
       , fromHexString "#eee8aa" |. keyword "palegoldenrod"
       , fromHexString "#98fb98" |. keyword "palegreen"
       , fromHexString "#afeeee" |. keyword "paleturquoise"
       , fromHexString "#db7093" |. keyword "palevioletred"
       , fromHexString "#ffefd5" |. keyword "papayawhip"
       , fromHexString "#ffdab9" |. keyword "peachpuff"
       , fromHexString "#cd853f" |. keyword "peru"
       , fromHexString "#ffc0cb" |. keyword "pink"
       , fromHexString "#dda0dd" |. keyword "plum"
       , fromHexString "#b0e0e6" |. keyword "powderblue"
       , fromHexString "#bc8f8f" |. keyword "rosybrown"
       , fromHexString "#4169e1" |. keyword "royalblue"
       , fromHexString "#8b4513" |. keyword "saddlebrown"
       , fromHexString "#fa8072" |. keyword "salmon"
       , fromHexString "#f4a460" |. keyword "sandybrown"
       , fromHexString "#2e8b57" |. keyword "seagreen"
       , fromHexString "#fff5ee" |. keyword "seashell"
       , fromHexString "#a0522d" |. keyword "sienna"
       , fromHexString "#87ceeb" |. keyword "skyblue"
       , fromHexString "#6a5acd" |. keyword "slateblue"
       , fromHexString "#708090" |. keyword "slategray"
       , fromHexString "#708090" |. keyword "slategrey"
       , fromHexString "#fffafa" |. keyword "snow"
       , fromHexString "#00ff7f" |. keyword "springgreen"
       , fromHexString "#4682b4" |. keyword "steelblue"
       , fromHexString "#d2b48c" |. keyword "tan"
       , fromHexString "#d8bfd8" |. keyword "thistle"
       , fromHexString "#ff6347" |. keyword "tomato"
       , fromHexString "#40e0d0" |. keyword "turquoise"
       , fromHexString "#ee82ee" |. keyword "violet"
       , fromHexString "#f5deb3" |. keyword "wheat"
       , fromHexString "#f5f5f5" |. keyword "whitesmoke"
       , fromHexString "#9acd32" |. keyword "yellowgreen"
       , fromHexString "#663399" |. keyword "rebeccapurple"
       , succeed (Color 0 0 0 0) |. keyword "transparent"
       ]

--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/avh4/elm-color/issues/15#issuecomment-420235668

Well wouldn't using a dict be faster for color names? I also think it should be case insensitive.
I used regex for my parser, but with elm/parser now available maybe it would be better to use it for the CSS formats.
Nicolas Goy

My use case is interfacing with an existing system that uses css colors. I don't control that system so can't change it to a different format (nor would I want to, it's a totally reasonable choice in context.)
In my case, that information is coming in json, so my ideal situation would be to have a Decoder Color, but I'd be fine with any String -> Maybe Color or String -> Result Color. (I'd like to detect errors and fail the decoding rather than choose a default.)
Since this functionality is not exposed, I'm planning on reimplementing or copying an existing parser, which is not ideal.

authors: avh4 gampleman kuon skyqrose


text:
Chi-Squared distribution doctests

#58 - doctests for chi-squared distribution
@avhz I have also implemented following functions along the way. Please have a look.
inv_cdf
entropy (based on this : Properties > Entropy)

Thanks so much!

authors: avhz chammika-become

repo: avhz/RustQuant


text:
Updating website name and  favicon

Describe the bug
The website's favicon is missing, also the title is wrong
Expected behavior
Adding the title 'Amazing Python Script'  which is the name of the website
Screenshots

Issue Aleady Open and Assigned to Someone else.

repo: avinashkranjan/Amazing-Python-Scripts


text:
Calendar-GUI

AIM-
Create a GUI-based Calendar that can show the calendar with respect to the given year, given by the user.
I am A GGSOC participant .pls assign me this issue.

@aishwaryachand assigned to you

@aishwaryachand updates?

will make a pr by today @kaustubhgupta

authors: aishwaryachand kaustubhgupta


text:
Fix an issue with jbuilder.1.0+beta19

Related to https://github.com/ocaml/opam-repository/pull/11605
The bytes dependency should be avoided since jbuilder/dune already depends on the OCaml >= 4.02.0.

thanks!

authors: avsm jpdeplaix

repo: avsm/ocaml-version

license: ISC


text:
translatable bugs:

when change translatable => false to config/fjord.php file , not working ,, admin panel still has two languages

The translatable option in the config file fjord.php is for the translation of the backend. If you want your data to not be translatable your need to change the options in the config file translatable.php as explained here: https://www.fjord-admin.com/docs/basics/localization/#php

repo: aw-studio/fjord