Flyway version check fails.

Which version and edition of Flyway are you using?
Community 9.22.3
If this is not the latest version, can you reproduce the issue with the latest one as well? (Many bugs are fixed in newer releases and upgrading will often resolve the issue)
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Java API
Which database are you using? (Type & version)
MariaDB 1.0.11
Which operating system are you using?
Debian 10
What did you do? (Please include the content causing the issue, any relevant configuration settings, the SQL statement(s) that failed (if any), and the command you ran)
Run Migration via Java API
What did you expect to see?
Successful migration
What did you see instead?
Unsupported  Database error

Hi @DxsSucuk , could you provide detailed info about the error message you encountered and the operation you ran?

Sure!
The Issue is quite weird, since I adding the library to another project that I use as library in my main project. It happends sometimes that it does not work on my main application but secondary, which uses springboot.
I am running both of them on Debain 11 with Java 17.
When running the Springboot Application, it works fine. But when trying to run it within the normal Java application this error occures?
Sadly its not only on my machine, as of report from users that use the open source project it also happends to them on Pterodactyl?

The Project I am talking about is here:
Normal Application, where it fails -> https://github.com/Ree6-Applications/Ree6
Springboot Application, where it works? -> https://github.com/Ree6-Applications/Webinterface

Anything new @JasonLuo-Redgate ?

Have you included a dependency on the flyway-mysql module?

Have you included a dependency on the flyway-mysql module?

Unsure what you mean with included a dependency on the module?
If the question is if I added the mysql module as dependency yes I have.

What specific error message did you get?

I receive the error message that the current Database is not supported, even thou it is stated that it is being supported by the Website. And when trying to do the same with another project, that uses the exact same thing it works fine.

Even after checking the dependencies via InteliJ, there is no dependency that overwrites the version that is being used.

So it should work, but doesnt.

You'll need to make sure the flyway-mysql jar is on the classpath at runtime


Outdated documentation (with regards to the partition controller)

In the documentation: https://griddb.org/python_client/PythonAPIReference.htm it states that gridstore has a property for the partition controller: partition_controller but it doesn't work.
The actual property is called partition_info. As in, partition_controller = gridstore.partition_info

Thank you for your information.
I'll update documentation.

thank you


Gazebo SImulation Problem

Hello sirs,
I am trying to get the gazebo simulation working but it seems to run into an issue. The simulation loads but then does not work. I have attached the terminal outputs below. Sorry if this is an obvious problem, as I am quite new to using ROS/Gazebo.
Gazebo:
... logging to /home/robotis/.ros/log/50b22eaa-40ec-11eb-b989-645d86d0e2d3/roslaunch-robotis-op3-4927.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

xacro: Traditional processing is deprecated. Switch to --inorder processing!
To check for compatibility of your document, use option --check-order.
For more infos, see http://wiki.ros.org/xacro#Processing_Order
xacro.py is deprecated; please use xacro instead
started roslaunch server http://<IP_ADDRESS>:42283/

SUMMARY
========

PARAMETERS
 * /robot_description: <?xml version="1....
 * /robotis_op3/head_pan_position/joint: head_pan
 * /robotis_op3/head_pan_position/pid/d: 0.0
 * /robotis_op3/head_pan_position/pid/i: 0.0
 * /robotis_op3/head_pan_position/pid/p: 5.0
 * /robotis_op3/head_pan_position/type: effort_controller...
 * /robotis_op3/head_tilt_position/joint: head_tilt
 * /robotis_op3/head_tilt_position/pid/d: 0.0
 * /robotis_op3/head_tilt_position/pid/i: 0.0
 * /robotis_op3/head_tilt_position/pid/p: 5.0
 * /robotis_op3/head_tilt_position/type: effort_controller...
 * /robotis_op3/joint_state_controller/publish_rate: 50
 * /robotis_op3/joint_state_controller/type: joint_state_contr...
 * /robotis_op3/l_ank_pitch_position/joint: l_ank_pitch
 * /robotis_op3/l_ank_pitch_position/pid/d: 0.0
 * /robotis_op3/l_ank_pitch_position/pid/i: 0.0
 * /robotis_op3/l_ank_pitch_position/pid/p: 50.0
 * /robotis_op3/l_ank_pitch_position/type: effort_controller...
 * /robotis_op3/l_ank_roll_position/joint: l_ank_roll
 * /robotis_op3/l_ank_roll_position/pid/d: 0.0
 * /robotis_op3/l_ank_roll_position/pid/i: 0.0
 * /robotis_op3/l_ank_roll_position/pid/p: 50.0
 * /robotis_op3/l_ank_roll_position/type: effort_controller...
 * /robotis_op3/l_el_position/joint: l_el
 * /robotis_op3/l_el_position/pid/d: 0.0
 * /robotis_op3/l_el_position/pid/i: 0.0
 * /robotis_op3/l_el_position/pid/p: 10.0
 * /robotis_op3/l_el_position/type: effort_controller...
 * /robotis_op3/l_hip_pitch_position/joint: l_hip_pitch
 * /robotis_op3/l_hip_pitch_position/pid/d: 0.0
 * /robotis_op3/l_hip_pitch_position/pid/i: 0.0
 * /robotis_op3/l_hip_pitch_position/pid/p: 50.0
 * /robotis_op3/l_hip_pitch_position/type: effort_controller...
 * /robotis_op3/l_hip_roll_position/joint: l_hip_roll
 * /robotis_op3/l_hip_roll_position/pid/d: 0.0
 * /robotis_op3/l_hip_roll_position/pid/i: 0.0
 * /robotis_op3/l_hip_roll_position/pid/p: 50.0
 * /robotis_op3/l_hip_roll_position/type: effort_controller...
 * /robotis_op3/l_hip_yaw_position/joint: l_hip_yaw
 * /robotis_op3/l_hip_yaw_position/pid/d: 0.0
 * /robotis_op3/l_hip_yaw_position/pid/i: 0.0
 * /robotis_op3/l_hip_yaw_position/pid/p: 50.0
 * /robotis_op3/l_hip_yaw_position/type: effort_controller...
 * /robotis_op3/l_knee_position/joint: l_knee
 * /robotis_op3/l_knee_position/pid/d: 0.0
 * /robotis_op3/l_knee_position/pid/i: 0.0
 * /robotis_op3/l_knee_position/pid/p: 50.0
 * /robotis_op3/l_knee_position/type: effort_controller...
 * /robotis_op3/l_sho_pitch_position/joint: l_sho_pitch
 * /robotis_op3/l_sho_pitch_position/pid/d: 0.0
 * /robotis_op3/l_sho_pitch_position/pid/i: 0.0
 * /robotis_op3/l_sho_pitch_position/pid/p: 10.0
 * /robotis_op3/l_sho_pitch_position/type: effort_controller...
 * /robotis_op3/l_sho_roll_position/joint: l_sho_roll
 * /robotis_op3/l_sho_roll_position/pid/d: 0.0
 * /robotis_op3/l_sho_roll_position/pid/i: 0.0
 * /robotis_op3/l_sho_roll_position/pid/p: 10.0
 * /robotis_op3/l_sho_roll_position/type: effort_controller...
 * /robotis_op3/r_ank_pitch_position/joint: r_ank_pitch
 * /robotis_op3/r_ank_pitch_position/pid/d: 0.0
 * /robotis_op3/r_ank_pitch_position/pid/i: 0.0
 * /robotis_op3/r_ank_pitch_position/pid/p: 50.0
 * /robotis_op3/r_ank_pitch_position/type: effort_controller...
 * /robotis_op3/r_ank_roll_position/joint: r_ank_roll
 * /robotis_op3/r_ank_roll_position/pid/d: 0.0
 * /robotis_op3/r_ank_roll_position/pid/i: 0.0
 * /robotis_op3/r_ank_roll_position/pid/p: 50.0
 * /robotis_op3/r_ank_roll_position/type: effort_controller...
 * /robotis_op3/r_el_position/joint: r_el
 * /robotis_op3/r_el_position/pid/d: 0.0
 * /robotis_op3/r_el_position/pid/i: 0.0
 * /robotis_op3/r_el_position/pid/p: 10.0
 * /robotis_op3/r_el_position/type: effort_controller...
 * /robotis_op3/r_hip_pitch_position/joint: r_hip_pitch
 * /robotis_op3/r_hip_pitch_position/pid/d: 0.0
 * /robotis_op3/r_hip_pitch_position/pid/i: 0.0
 * /robotis_op3/r_hip_pitch_position/pid/p: 50.0
 * /robotis_op3/r_hip_pitch_position/type: effort_controller...
 * /robotis_op3/r_hip_roll_position/joint: r_hip_roll
 * /robotis_op3/r_hip_roll_position/pid/d: 0.0
 * /robotis_op3/r_hip_roll_position/pid/i: 0.0
 * /robotis_op3/r_hip_roll_position/pid/p: 50.0
 * /robotis_op3/r_hip_roll_position/type: effort_controller...
 * /robotis_op3/r_hip_yaw_position/joint: r_hip_yaw
 * /robotis_op3/r_hip_yaw_position/pid/d: 0.0
 * /robotis_op3/r_hip_yaw_position/pid/i: 0.0
 * /robotis_op3/r_hip_yaw_position/pid/p: 50.0
 * /robotis_op3/r_hip_yaw_position/type: effort_controller...
 * /robotis_op3/r_knee_position/joint: r_knee
 * /robotis_op3/r_knee_position/pid/d: 0.0
 * /robotis_op3/r_knee_position/pid/i: 0.0
 * /robotis_op3/r_knee_position/pid/p: 50.0
 * /robotis_op3/r_knee_position/type: effort_controller...
 * /robotis_op3/r_sho_pitch_position/joint: r_sho_pitch
 * /robotis_op3/r_sho_pitch_position/pid/d: 0.0
 * /robotis_op3/r_sho_pitch_position/pid/i: 0.0
 * /robotis_op3/r_sho_pitch_position/pid/p: 10.0
 * /robotis_op3/r_sho_pitch_position/type: effort_controller...
 * /robotis_op3/r_sho_roll_position/joint: r_sho_roll
 * /robotis_op3/r_sho_roll_position/pid/d: 0.0
 * /robotis_op3/r_sho_roll_position/pid/i: 0.0
 * /robotis_op3/r_sho_roll_position/pid/p: 10.0
 * /robotis_op3/r_sho_roll_position/type: effort_controller...
 * /rosdistro: kinetic
 * /rosversion: 1.12.14
 * /use_sim_time: True

NODES
  /robotis_op3/
    controller_spawner (controller_manager/spawner)
  /
    gazebo (gazebo_ros/gzserver)
    gazebo_gui (gazebo_ros/gzclient)
    urdf_spawner (gazebo_ros/spawn_model)

ROS_MASTER_URI=http://<IP_ADDRESS>:11311

process[gazebo-1]: started with pid [4966]
process[gazebo_gui-2]: started with pid [4971]
process[urdf_spawner-3]: started with pid [4975]
ERROR: cannot launch node of type [controller_manager/spawner]: controller_manager
ROS path [0]=/opt/ros/kinetic/share/ros
ROS path [1]=/home/robotis/catkin_ws/src
ROS path [2]=/opt/ros/kinetic/share
[ INFO] [1608267429.074960294]: Finished loading Gazebo ROS API Plugin.
[ INFO] [1608267429.077592434]: waitForService: Service [/gazebo/set_physics_properties] has not been advertised, waiting...
[ INFO] [1608267429.415269459]: Finished loading Gazebo ROS API Plugin.
[ INFO] [1608267429.419324586]: waitForService: Service [/gazebo/set_physics_properties] has not been advertised, waiting...
SpawnModel script started
shutdown request: new node registered with same name
[INFO] [1608267429.967050, 0.000000]: Loading model XML from ros parameter
[INFO] [1608267429.982124, 0.000000]: Waiting for service /gazebo/spawn_urdf_model
[INFO] [1608267429.984069, 0.000000]: Calling service /gazebo/spawn_urdf_model
Traceback (most recent call last):
  File "/opt/ros/kinetic/lib/gazebo_ros/spawn_model", line 313, in <module>
    sm.callSpawnService()
  File "/opt/ros/kinetic/lib/gazebo_ros/spawn_model", line 271, in callSpawnService
    initial_pose, self.reference_frame, self.gazebo_namespace)
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/gazebo_ros/gazebo_interface.py", line 28, in spawn_urdf_model_client
    rospy.wait_for_service(gazebo_namespace+'/spawn_urdf_model')
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/rospy/impl/tcpros_service.py", line 159, in wait_for_service
    raise ROSInterruptException("rospy shutdown")
rospy.exceptions.ROSInterruptException: rospy shutdown
[ INFO] [1608267430.359857990]: <robotNamespace> set to: //
[ INFO] [1608267430.359931330]: <topicName> set to: //robotis_op3/imu
[ INFO] [1608267430.359969095]: <frameName> set to: body_link
[ INFO] [1608267430.360012959]: <updateRateHZ> set to: 10
[ INFO] [1608267430.360041992]: <gaussianNoise> set to: 0
[ INFO] [1608267430.360073828]: <xyzOffset> set to: 0 0 0
[ INFO] [1608267430.360122969]: <rpyOffset> set to: 0 -0 0
[INFO] [1608267430.461895, 0.000000]: Spawn status: SpawnModel: Successfully spawned entity
[urdf_spawner-3] process has finished cleanly
log file: /home/robotis/.ros/log/50b22eaa-40ec-11eb-b989-645d86d0e2d3/urdf_spawner-3*.log
[ INFO] [1608267431.050111649]: Camera Plugin: Using the 'robotNamespace' param: '/'
[ INFO] [1608267431.071445666]: Camera Plugin (ns = /)  <tf_prefix_>, set to ""
[ INFO] [1608267556.775078705, 18.153000000]: waitForService: Service [/gazebo/set_physics_properties] is now available.
[ INFO] [1608267556.776317821, 18.153000000]: waitForService: Service [/gazebo/set_physics_properties] is now available.
[ INFO] [1608267557.158470679, 18.215000000]: Physics dynamic reconfigure ready.
[ INFO] [1608267557.161445120, 18.216000000]: Physics dynamic reconfigure ready.

Manager:
robotis@robotis-op3 ~ $ roslaunch op3_manager op3_manager.launch
... logging to /home/robotis/.ros/log/50b22eaa-40ec-11eb-b989-645d86d0e2d3/roslaunch-robotis-op3-5760.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

started roslaunch server http://<IP_ADDRESS>:37035/

SUMMARY
========

PARAMETERS
 * /device_name: /dev/ttyUSB0
 * /gazebo: False
 * /gazebo_robot_name: robotis_op3
 * /init_file_path: /home/robotis/cat...
 * /offset_file_path: /home/robotis/cat...
 * /op3_manager/angle_unit: 30
 * /robot_file_path: /home/robotis/cat...
 * /rosdistro: kinetic
 * /rosversion: 1.12.14

NODES
  /
    op3_localization (op3_localization/op3_localization)
    op3_manager (op3_manager/op3_manager)

ROS_MASTER_URI=http://<IP_ADDRESS>:11311

process[op3_manager-1]: started with pid [5777]
process[op3_localization-2]: started with pid [5778]
[ WARN] [1608267596.775736095, 19.994000000]: Shutdown request received.
[ WARN] [1608267596.776140845, 19.994000000]: Reason given for shutdown: [new node registered with same name]
[ INFO] [1608267596.877677373]: manager->init
[ INFO] [1608267597.151671749, 20.001000000]: Torque on DXLs!
/dev/ttyUSB0 added. (baudrate: 2000000)
(/dev/ttyUSB0) [ID:  1]         XM-430 added.
(/dev/ttyUSB0) [ID:  2]         XM-430 added.
(/dev/ttyUSB0) [ID:  3]         XM-430 added.
(/dev/ttyUSB0) [ID:  4]         XM-430 added.
(/dev/ttyUSB0) [ID:  5]         XM-430 added.
(/dev/ttyUSB0) [ID:  6]         XM-430 added.
(/dev/ttyUSB0) [ID:  7]         XM-430 added.
(/dev/ttyUSB0) [ID:  8]         XM-430 added.
(/dev/ttyUSB0) [ID:  9]         XM-430 added.
(/dev/ttyUSB0) [ID: 10]         XM-430 added.
(/dev/ttyUSB0) [ID: 11]         XM-430 added.
(/dev/ttyUSB0) [ID: 12]         XM-430 added.
(/dev/ttyUSB0) [ID: 13]         XM-430 added.
(/dev/ttyUSB0) [ID: 14]         XM-430 added.
(/dev/ttyUSB0) [ID: 15]         XM-430 added.
(/dev/ttyUSB0) [ID: 16]         XM-430 added.
(/dev/ttyUSB0) [ID: 17]         XM-430 added.
(/dev/ttyUSB0) [ID: 18]         XM-430 added.
(/dev/ttyUSB0) [ID: 19]         XM-430 added.
(/dev/ttyUSB0) [ID: 20]         XM-430 added.
(/dev/ttyUSB0) [ID:200]        OPEN-CR added.
[ INFO] [1608267598.045100598, 20.028000000]: Load offsets...
[ WARN] [1608267598.397615243, 20.038000000]: Head control - angle unit : 30
[ INFO] [1608267598.699967199, 20.047000000]: parse pose for moving init pose
[ WARN] [1608267598.704118912, 20.047000000]: Get the init gain from Dxl init file
[ INFO] [1608267598.846664266, 20.050000000]: Go to init pose
[ INFO] [1608267598.865311984, 20.050000000]: Base Module is enabled
[ INFO] [1608267598.950302469, 20.051000000]: [start] send trajectory
[ INFO] [1608267602.956757226, 20.151000000]: [end] send trajectory

Hi @full0134
I'm sorry about the delayed response, but I don't see a particular issue from your log.
If you see the  icon instead of Pause  icon at the bottom of Gazebo screen, Gazebo is not running, but waiting to be played.


Include image file returned from assistant reply

currently, if I ask for a chart summarizing some given data, I can see that an image file is returned as part of the assistant response in the respective thread on platform.openai.com but it does not seem to be part of the response in the ui. How can we go about it so that the image is included in the ui response along with the option to download the file?

can't answer this but pls refer to the demo link about Format and display the Assistant Messages for text and images.


Comment using Disqus from the AMP version

I've try to comment from Disqus in the AMP version of my post but this is not send... Only you can view the comments?

I've fixed it!
Into the sandbox property of the amp-iframe you have to add the "allow-forms". I now you can comment from AMP pages. :)

Fixed in #12.


Playready material fails silently on Tizen 2.4

Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
2.5.9
Can you reproduce the issue with our latest release version?
Yes
Can you reproduce the issue with the latest code from master?
Yes
Are you using the demo app or your own custom app?
Custom
If custom app, can you reproduce the issue using our demo app?
Demo app crashes when I try to navigate to it
What browser and OS are you using?
Tizen 2.4
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
Tizen 2.4 (2016), tried two different models.
What are the manifest and license server URIs?

Not sure I am allowed to share this.
What did you do?
Play material protected by playready which works on IE11 and Edge.
What did you expect to happen?
Playback to start.
What actually happened?
Black screen. It works if I set disableAudio: true, or disableVideo: true.

I think that it's related to https://github.com/google/shaka-player/issues/813


⚠ Anthelion has degraded performance

In f5d5917, Anthelion ($ATH) experienced degraded performance:

HTTP code: 200
Response time: 3373 ms

Resolved: Anthelion performance has improved in 3a6d958 after 411 days, 17 hours, 59 minutes.


awk-language-server: init at 0.10.6

Description of changes
Adds the awk-language-server. Closes #234354
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Priorities
Add a :+1: reaction to pull requests you find important.

Obsolete by https://github.com/NixOS/nixpkgs/pull/346009

Calling this obsolete is kinda rude, considering the author of the other PR didn't check for an existing open PR

…considering the author of the other PR didn't check for an existing open PR

They might actually have. The other PR introduces this package in a newer version than this PR. Either way, this PR is superseded (is this less rude?) by the other PR, thus this PR can be closed, now or after the other PR was merged. Considering this PR is stale, it could actually be closed immediately.

The update.sh script from passthrou.updateScript still works, I just haven't updated. Regardless, I don't remember why I decided to package it this way vs using node-packages.nix. If you believe adding it via node-packages.nix has more merits, feel free to close.

Considering this PR is stale, it could actually be closed immediately.

It's not stale, it's on committers for not reviewing the PR.

I don't remember why I decided to package it this way vs using node-packages.nix

Some committers didn't like nodePackages, I don't know the details though, so maybe this PR is preferable (without me having reviewed the code carefully, anyway).


Fixes HSL colour error and adds simplified logos

The colour did not render properly as it was defined in HSV/B and not HSL.

Codecov Report
Base: 36.16% // Head: 36.88% // Increases project coverage by +0.71% :tada:

Coverage data is based on head (21055a1) compared to base (305c096).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #7102      +/-   ##
==========================================
+ Coverage   36.16%   36.88%   +0.71%
==========================================
  Files         967      977      +10
  Lines       17225    17262      +37
  Branches     4463     4482      +19
==========================================
+ Hits         6230     6367     +137
+ Misses      10995    10895     -100

Flag
Coverage Δ

e2e
47.49% <ø> (+0.92%)
:arrow_up:

merged
36.88% <ø> (+0.71%)
:arrow_up:

unit
5.29% <ø> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

shell/plugins/plugin.js
51.61% <0.00%> (-28.39%)
:arrow_down:

shell/utils/grafana.js
12.76% <0.00%> (-21.93%)
:arrow_down:

shell/plugins/extend-router.js
56.00% <0.00%> (-8.00%)
:arrow_down:

shell/utils/url.ts
38.88% <0.00%> (-1.39%)
:arrow_down:

shell/utils/dynamic-importer.js
40.00% <0.00%> (-1.38%)
:arrow_down:

shell/plugins/dashboard-store/resource-class.js
46.87% <0.00%> (-0.16%)
:arrow_down:

shell/nuxt.config.js
0.00% <0.00%> (ø)

shell/config/types.js
100.00% <0.00%> (ø)

shell/pages/prefs.vue
0.00% <0.00%> (ø)

shell/edit/service.vue
0.00% <0.00%> (ø)

... and 41 more

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Performance metrics

Is the test performance index mAP in the paper experiment mAP50-95?

Yes, we used the default coco accuracy metric in mmdet, and the mAP mentioned in the paper is actually mAP50-95:0.05. I suggest you refer to the website for specific information: https://github.com/open-mmlab/mmdetection/blob/main/mmdet/evaluation/metrics/coco_metric.py.


Gradle 5.0 support

I get now this warning, that some features won't be supported in gradle 5.
Task :full:ikvm
Some problems were found with the configuration of task ':full:ikvm'. Registering invalid inputs and outputs via TaskInputs and TaskOutputs methods has been deprecated and is scheduled to be removed in Gradle 5.0.
 - No value has been specified for property '$1'.
 - No value has been specified for property '$2'.
IKVM.NET Compiler version 8.1.5717.0
Copyright (C) 2002-2015 Jeroen Frijters

it has been fixed in release 2.10


Feat/java unit coversall

Description
Modules

[ ] UI
[ ] Controller
[ ] Agent
[ ] Client
[ ] Python-SDK
[ ] Others

Checklist

[ ] run code format and lint check
[ ] add unit test
[ ] add necessary doc

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
801 unchanged lines in 26 files lost coverage.
Overall coverage increased (+2.3%) to 7.899%

Files with Coverage Reduction
New Missed Lines
%

starwhale/cli/project.py
1
0%

starwhale/utils/ui.py
2
0%

starwhale/utils/debug.py
4
0%

starwhale/cli/mngt.py
5
0%

starwhale/cli/dataset.py
8
0%

starwhale/cli/init.py
8
0%

starwhale/utils/config.py
9
91.26%

starwhale/utils/error.py
9
0%

starwhale/utils/http.py
15
0%

starwhale/api/_impl/model.py
16
0%

Totals

Change from base Build<PHONE_NUMBER>:
2.3%

Covered Lines:
226

Relevant Lines:
2861

💛  - Coveralls


Add pinned deployments to projects

Checklist

[x] Appropriate branch selected (all PRs must first be merged to dev before they can be merged to master)
[x] Any modified or new methods or classes have helpful JavaDoc and code is thoroughly commented
[x] The description lists all applicable issues this PR seeks to resolve
[x] The description lists any configuration setting(s) that differ from the default settings
[x] All tests and CI builds passing

Description
This change allows the persistence of a pinned deployment. Pinned deployments are being added to help complete https://github.com/conveyal/datatools-ui/issues/422. The pinned deployment is sometimes used to compare feed versions within the app in and in a specific deployment.
These changes assume that the deployment module is enabled in the UI.

Codecov Report

Merging #191 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##               dev    #191   +/-   ##
=======================================
  Coverage     6.21%   6.21%
  Complexity     115     115
=======================================
  Files          133     133
  Lines         6954    6954
  Branches       912     912
=======================================
  Hits           432     432
  Misses        6486    6486
  Partials        36      36

Impacted Files
Coverage Δ
Complexity Δ

...com/conveyal/datatools/manager/models/Project.java
23.07% <ø> (ø)
2 <0> (ø)
:arrow_down:

Continue to review full report at Codecov.

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

I improved the comment a bit. It's not necessarily future proofed since it lists the 2 specific places this is used in datatools-ui, but it's entirely possible that more places in datatools-ui could use this and we'd forget to update this comment.

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


Mis-parse of relative paths. Alway based-on “www/“ instead of the HTML page.

Case: In "settings/set.html”, read “settings/data.json” using fetch().
Current situation: Fetching “data.json” will get an error. I have to fetch “settings/data.json” to make it work.
Supposed: I should be able to fetch "data.json" directly since they are in the same folder.
It caused many bugs with dynamically loaded resources.

@jammind Hi Jam, We will analyse the reported the issue and get back to you.

Hi Jam, This is doesn't seems to be plugin issue. Plugin follows similar standards of web development, the context root is place where the index.html page lives which is the app bundle and www folder. You need to map your files accordingly.


Fehlermeldungen beim Adapterstart

Beim Start der  0.1.4-beta.3 (2023-03-10) bekomme ich beim Start folgenden Log:
roborock.0
2023-03-10 23:47:11.414	warn	Unknown block type! Please report this to the developer. Block type is:1024

roborock.0
2023-03-10 23:47:11.413	warn	Unknown block type! Please report this to the developer. Block type is:26

roborock.0
2023-03-10 23:47:11.413	warn	Unknown block type! Please report this to the developer. Block type is:25

roborock.0
2023-03-10 23:47:11.412	warn	Unknown block type! Please report this to the developer. Block type is:24

roborock.0
2023-03-10 23:47:11.411	warn	Unknown block type! Please report this to the developer. Block type is:22

roborock.0
2023-03-10 23:47:11.410	warn	Unknown block type! Please report this to the developer. Block type is:19

roborock.0
2023-03-10 23:47:11.382	warn	Unknown block type! Please report this to the developer. Block type is:16

roborock.0
2023-03-10 23:47:11.382	warn	Unknown block type! Please report this to the developer. Block type is:15

roborock.0
2023-03-10 23:47:11.381	warn	Unknown block type! Please report this to the developer. Block type is:12

roborock.0
2023-03-10 23:47:11.375	warn	Unknown block type! Please report this to the developer. Block type is:21

mapdata ist hier hochgeladen:
https://forum.iobroker.net/topic/62328/roborock-adapter-tester-gesucht/425

Fixed via https://github.com/copystring/ioBroker.roborock/commit/abc0bf8e182755eccc8ce856a15e972f7a3e3a60


No Download in 1080 format.

Can you update for download in 1080 format, this tool, download 720 format only.
Thanks you!

#26 sorry it's still pending


InlinePanel - add unit test coverage

Is your proposal related to a problem?

InlinePanel and the related buildExpandingFormset utils are quite fragile and can break in cases where the DOM structure changes or in more complex cases like nested panels easily.

Describe the solution you'd like

Unit test coverage should help us be a bit more confident about changes and understanding the behaviour.
It might be suitable to import the html template for testing this also.

Describe alternatives you've considered

Integration tests or browser testing could also be suitable for this or the pattern library.

Additional context

https://github.com/wagtail/wagtail/pull/9149
https://github.com/wagtail/wagtail/issues/9145

Hey @lb- I was just going to open some discussion about that particular thingie! The issue #9145 is way too big and affected everybody that upgraded to wagtail 4.x! This shouldn't be taken lightly.
The fact that a bug this important slipped from testing means that there's something flawed in the way new wagtail releases are tested; adding some tests for inlinepanels is definitely a good first step but what about other similar issues? The whole wagtail-admin seems way too fragile too me because of the javascript-python trickery it includes so how can anybody be reassured that other things won't break in next updates?
It feels that people that update to new wagtail versions when they are released are actually doing beta-testing without their consent!
I really don't know how this could be improved; however I feel that some discussion with the Wagtail team would be good. Maybe avoid such big changes? Maybe don't allow changes that have a probability of breaking things? Maybe add even more integration tests? Maybe give more priority to testing (i.e do not add any more features to the project until everything has been covered by tests)?
Thank you and kind regards,
Serafeim

@spapas thanks for the input.
If we steer away from making big changes, then we will end up making no changes.
We do lots of manual testing when reviewing PRs, but we're also only human.. I don't seen an issue with the Python + JavaScript "trickery", but we do want to increase our coverage and this is one of those steps.
FWIW, the version jump came from the fact we had so many changes and it is a way to indicate further testing may be needed before just upgrading. Heh, ideally we would just be able to do the version bump and everything else would just work, but we cannot and do not want to control what and how people build their sites, or what packages they use or don't use. There is a reason we do a couple of weeks of release candidate (and sometimes 2 release candidates) and ask people to test with their projects.
Regardless, this is not something that we just take lightly. And it most certainly something that we can and should improve. We cannot do it alone, and we do need help from the community. From providing constructive feedback, to bug fixes, to doing the real-life testing (sometimes even with the nightly builds, or release candidates), to keeping packages up to date, and.. helping us achieve the "everything has been covered by tests" state.
Finally, we can probably continue this in a discussion.

Hello @zerolab thank you for understanding the situation and taking it seriously. Also forgive me for hijacking LB's thread ; I wasn't aware the discussions feature is used for Wagtail, I'd keep it in mind from now on...
I'd be grateful if the testing and release process is actually improved and similar bugs are catched in the future before reaching production sites. This will definitely make Wagtail updates less problematic and imrove Wagtail as a framework in general.
Kind regards,
Serafeim
PS I think that it's better to not release a new version than releasing something that introduces (or has a probability of introducing) bugs to production apps.

@spapas thanks for the input and I hear your frustration.
I agree 100% with everything @zerolab said - including that further discussion should be a standalone discussion about automated or manual ways to pick up things sooner.
There are plans underway (beyond just this issue) for some other testing layers to be added. All of these take time and resources and may not be prioritised and unlikely to be sponsored so there is no locked in roadmap for these.

Storybook testing support (good line between integration tests and unit tests).
More integration tests (we already have some for critical accessibility bugs).
RFC78 to simplify and abstract some of the easy gotchas when working with 'JavaScript trickery' (for example this exact bug would never be an issue with Stimulus' approach to targeting scoped elements in the DOM).

Thanks again Serafeim.


Publish Conan package

If you haven't heard of Conan, it's a C/C++ package manager that is gaining a lot of popularity.
I think it'd be great if every release of Nano Protocol Buffers was automatically published as a new version of a Conan package. It'll make it consuming it in other projects really easy, and also to update to newer versions.

Ok, can you perhaps make a pull request about what would be needed to achieve this?

Sure, I'll create a PR when ready.


Heroku example for the Deployment Guide

Re: https://github.com/socketry/falcon-rails-example/issues/1, adding some documentation to show a full working example Heroku configuration for Falcon.
Note I wasn't sure where to put this, but I believe this could be a reasonable place. I also tried to follow the new configuration style in the guides, but feedback is welcome.
Note also that I included preload, cache, and count config examples which may or may not be desirable. I'm happy to adjust. We could also adjust to use a different ENV var etc as opposed to FALCON_COUNT -- feel free to adjust as you like, or let me know what you'd prefer and I'll make adjustments.
Fixes https://github.com/socketry/falcon/issues/189
Fixes https://github.com/socketry/falcon/issues/121
Types of Changes

Documentation.

Contribution

[x] I agree to the Developer's Certificate of Origin 1.1.

This looks great to me.
For all the major configuration options you've listed, it would be great to explain what it does, and how to use it.

Ok, I made some updates. Let me know what you think! I added some more info and links. I changed FALCON_COUNT to WEB_CONCURRENCY since this is what most people use for Puma, but let me know what you think. I also removed cache false because from my testing it appears that the cache is disabled by default now. (Is that right? I thought I remembered it being enabled by default, which I found surprising, but perhaps we disabled it by default now?)

Thanks, this looks great!


New gradient UI

New Button UI:
(you don't need to worry about the conflicted file, resolved in my latest commit)

I can't merge this branch until conflicts with main are dealt with. Please remove Phoenix/.DS_Store which is in .gitignore and shouldn't be tracked, and please fix Phoenix/Phoenix.xcodeproj/project.pbxproj so that it doesn't conflict with main. Looking at the changes it seems like the the Development Team has been changed, so a pull from main should fix it.


States with optional and unknown Query Params

This is a:

[ ] Bug Report
[ ] Feature Request
[x] General Query

My version of UI-Router is: 0.3.1
General Query

[x] I have already asked my question on StackOverflow and nobody could answer the question

[x] I have already reviewed the sample application for examples of common approaches

[x] I believe my question can only be answered by the UI-Router maintainers

Hello !!
Somebody knows how to create states structure that permits something like this:

https://urlexample.com/route?unknownParam1=1&unknownParam2=2....
https://urlexample.com/route
https://urlexample.com/route/ -> redirect to 2

In case with QueryParams, I don't know the names and number of params.
I want that the three URLs goes to the same state without losing the query params. And without duplicating states.
I have checked the app demo with angularjs but these demo app was created with 1.0 version of ui-router and ES6 typescript.
Could somebody help me?
Thanks !!

Sorry, I have a $state.go to toState state in a $stateChangeStart event. I don't define query params in url of the states so when $state.go goes to state, goes to url without parameters.
Thanks !!


How can I build and use nvvs alone?

Hi,
That is impossible for several reasons: nvvs and the rest of dcgm use shared static libraries which are built before the nvvs build step, and nvvs needs nv-hostengine (embedded or standalone) to work.


Updates for using webpack 5. Please review

A PR for building using webpack 5. It is working but please review, I am by no means an expert in this area.
Especially regarding the import of .css in the src/index.js I think is likely not the right way to do it, but cannot find another way without a protest regarding the exports in cesium:
import "../dist/Widgets/widgets.css"

Any progress made on this?  We are trying to update our project to use Webpack 5 and the Cesium library is the only library blocking completing that task.  Thanks!

Hi, It works but I also realized there is another PR with webpack 5 https://github.com/CesiumGS/cesium-webpack-example/pull/23
But would be good if someone with more insight reviewed this / that.

I am getting a ReferenceError: __dirname is not defined in the index.cjs file at the point below:
module.exports = webpack_require("../../node_modules/cesium sync recursive")(path.join(
__dirname,
"Build/CesiumUnminified/index.cjs"
));

replaced by https://github.com/CesiumGS/cesium-webpack-example/pull/52


introduce scripts.yaml file to store commands for easier reading.

have more than 10 commands in pubspec.yaml makes it too long to read split it into a new file

fork
https://github.com/masreplay/rps

Hi @masreplay 👋🏻
Thank you for your contribution, it has now been merged. I will be working more on this package in the coming weeks, I will let you know when the new version of the package is available.

Thanks

Hi @masreplay 👋🏻
The above change is now available in rps version 0.9.0.
However, there are some minor changes to the implementation provided.

scripts.yaml is renamed to rps.yaml － to reduce the risk of conflicts with other files.
in the rps.yaml file, the scripts key should be specified, as in the pubspec.yaml file － this is to allow configuration properties to be inserted into this file in the future.

For more information, see the readme  － external scripts file section.


[Feature Request]: Full VS Code Support

To start things off, the experience of getting a development environment spun up has been refreshingly painless with devbox.
As mentioned in this post, starting devbox shell automatically in the VS Code terminal is extremely helpful however it does not sufficiently integrate the devbox environment with VS Code processes (like tasks, debugger, etc.)
As one example, VS Code automatically reads and exposes the scripts defined with the  package.json of the open project.
.
When a task is run, VS Code spins up a process to execute npm run dev.
However, these processes are initiated from the shell where VS Code was launched. For obvious reasons (npm only being installed within devbox), attempting to run this task fails, which in some ways greatly defeats the promise of devbox and the power of VS Code.

This "workaround" better illustrates the importance of the shell context VS Code is running in. When code is executed after entering devbox shell, we get the expected behavior.

This "workaround" is more a proof-of-concept though as it is full of other compromises to the daily development experience.
This execution of tasks is fundamental to the VS Code platform. They expect extension authors to provide similar features (executing binaries through the VS Code command palette) through this mechanism.
Code linters / formatters, unit testing platforms, dependency management tools, etc. execute directly through the shell.
This is the power of the available Remote Extensions (SSH, Containers, WSL, etc.) provided by Microsoft. To really oversimplify, these remote extensions "trick" VS Code into thinking it is running from within the container or the SSH connection. The "trick" in this case just being that a lightweight "server" version of VS Code is installed in the container / SSH connection. This allows VS Code to execute these tasks with the packages available in that environment instead of those available on your local OS and it's packages (or ideally lack thereof).
Unfortunately (though I would be extremely happy to learn I'm just doing something wrong) the Dockerfile / devcontainer feature of devbox does not provide this tight VS Code integration as it just pushes the problem one layer deeper.
VS Code is "tricked" into thinking it is running in the container, however like a more traditional setup, the devbox packages are not installed in the container, they're installed within the devbox that's installed in the container. The VS Code tasks are then just run in the context of the container shell.
It would be fantastic if the devbox VS Code extension could support this. I tried to look into how the official Remote Extensions pull this off but I do not think they are open source.
Happy to help out if I can.

After chatting with some folks over on the NixOS Matrix Space, it's a far more streamlined experience to use devbox generate direnv with the Nix Extension Pack in VS Code.

After chatting with some folks over on the NixOS Matrix Space, it's a far more streamlined experience to use devbox generate direnv with the Nix Extension Pack in VS Code.

Thanks for sharing this discovery. It seems only the direnv extension is required, rather than the entire Nix Extension Pack.
For those that do want to go down the dev container route (e.g. for better isolation), see #1028.


add xxHash library

Currently we use std::hash for hashing which is not consistent across platforms. This introduces xxHash which is portable, fast, and used by many other open-source projects.
After this PR is merged, I will followup with a change to update ENVOY_BUILD_SHA and convert usages of std::hash.

@danielhochman is this hash going to be strong enough to resolve #1452?

@htuch yeah, it should be strong enough. we largely used https://github.com/rurban/smhasher to evaluate different options. smhasher assigns a quality score based on collision probability, etc for which xxhash earned a 10.


How to send an event to another Pipeline

This might be a dumb question, since it is already possible to solve by using a stage, but, is there an ALF-way to send an event from one pipeline to another?
As an example:
DecoderPipeline receives a raw message and converts it to a Message. Extracts metadata and saves it in the database. Based on the "kind" of message, it should then be routed to another pipeline.
The other pipelines handle logic specific to that kind of event.
As far as I understand, the only way right now to do this is to call/cast the pipeline from a stage.

Hey @fermuch !
Calling another pipeline from a stage is a possible solution, however, it may lead to a quite complex topology.
If the "event" in the original pipeline is similar to the one in another pipeline, I would rather combine the pipelines in one big pipeline and use "switch" to send events to the corresponding branches.
If the "event" is quite different. You can implement your own "middleware/adapter" logic, that first sends an event to the original pipeline, then takes the result, prepares a new event, and sends it to another pipeline.


connection_time doesn't show as date in Grafana. When selecting 'Date' as type, 'Invalid Date' is shown

Few examples above - not sure if I should file this with the Grafana team or if something needs to be done this end? Might be that there's no trailing zeroes.

Figured it's because Grafana expects this value as milliseconds. Not sure if that is something that can be implemented easily - not very experienced in golang otherwise would have made a pull request!


Work queue for FC

Similar to the print queue, the formal clearing should be able to see a list of waiting resolutions and work on them consecutively.

solved in #143


Not able to clear selection or reset calendar

Can we add a functionality to clear date range section on clicking a button like below screen

We need to clean input field as well as dates in the calendar as well or we can say resetting the calendar to its default settings.

Hi @ssarya  Yeah, I might need to think of a few scenarios around it and get back on this but this can be marked as an enhancement.
I will update here once this is available in the next version. The target should be this week.
Thank you again for using this library. :)

This issue PR work is in progress. It should have few more features including the clear selection.

@Kumar-Aakash is there a way to clear the selection programmatically in the current version?

@ssarya @tomgruszowski
you may find clear date range functionality on below version:
V16 : 1.2.10
V17 : 2.2.4

Thanks Aakash


Add Campaign Title to Follower UI landing page

UX enhancement for the "Enter Address" screen.
AS A Follower of an organization
WHEN I click the campaign short-link (e.g. facebook, email)
I WANT TO see the title of the Campaign above the address field to remind me why I'm being asked for my address.
Note: UX design needed

I think this ties into a much needed improvement for campaigns - some sort of "info" section that describes the purpose of the campaign, along with a little bit more verbose instructions. If we feel this is something that would be useful, we can create a separate issue. Either way, I'm happy to grab this one in the mean time.

After consulting with some of our orgs who volunteered to test, re: branding, having the name of the organization and the same kind of logo that they already use for ex: Facebook, Twitter, is just enough personalization for them.

Thanks for the user research, Kate!
On Thu, Dec 6, 2018, 8:50 AM kbertash<EMAIL_ADDRESS>wrote:

After consulting with some of our orgs who volunteered to test, re:
branding, having the name of the organization and the same kind of logo
that they already use for ex: Facebook, Twitter, is just enough
personalization for them.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/helloGov/webapp/issues/173#issuecomment-444943482,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD3e4E8joB65c2jrgxwg5nuDtSvsLG6Cks5u2UrEgaJpZM4YscVO
.

Should probably add some copy over it.
"Follow these steps to make your voice heard on this important issue."
[Campaign Title]

is this sort of what we're going for?

@Jeremy-D Looks Great!  Kate's good with this for MVP.
We may have copy tweaks later, but we're in a great place.  Thank you!
@kbertash


Need access to DID_INL2_STATUS but inl2_status_t struct is not defined.

Hello,
I need access to DID_INL2_STATUS, but inl2_status_t struct is not defined in the SDK. Therefore, I can't map the buffer onto the struct.
Is it possible to provide the inl2_status_t struct?
Thanks!

I hope this helps.
typedef struct PACKED
{
int ahrs;
int zero_accel;
int zero_angrate;
int accel_motion;
int rot_motion;
int zero_vel;
int ahrs_gps_cnt; // Counter of sequential valid GPS data (for switching
from AHRS to navigation)
float att_err;
int att_coarse; // Flag whether initial attitude error converged
int att_aligned; // Flag whether initial attitude error converged
int att_aligning;
int start_proc_done; // Cold/hot start procedure completed
int mag_cal_good;
int mag_cal_done;
int stat_magfield;
} inl2_status_t;

Thanks Walt!
That's what I needed!


η not defined here?

https://github.com/DavisThuillier/Ludwig.jl/blob/983ea415143ce77f9859ec0f940c28f5f52eb831/src/integration.jl#L42
I could not find where η is defined in this function.
Also, it is defined in ee_kernel with a different convention (Delta Epsilon / 2 already included in eta), so that might cause confusion.

Old version of function scrubbed from integration.jl


Add ability to open/close all results in the online scanner

If the site has a lot of errors it gets annoying to open/expend the result one by one.

Something similar for adults with lots of results is when you reach the end of a rule and want to collapse it. You need to scroll all the way up and then close it.
Don't know if short cuts could be an option on top of something else?


Fix views

Since ejs is configured as tamplating engine in /lib/views.js it has to be a dependency. Otherwise views will not work.
Changed the path to the views directory in /lib/views.js. It now correctly points to /lib/views (the old version pointed to /node_modules/boyle/lib/viewsbecause __dirname points to the path of the current source file not the project root).

Thanks!


is tag v19.02 right?

Release 19.02 released this 6 days ago
But latest commit for tag v19.02 is 3 months ago.
is tag v19.02 right?

@kwangchoon thanks for reporting this. The Release 19.02 tag was not correct, this is now updated and we are reviewing our release process to ensure this doesn't happen again.


Shell completion escape handling

This PR fixes #1708 by using Python's shlex module to parse and split argument strings for shell completion. Incomplete arguments where splitting with shlex.split fails with a ValueError are handled by inspecting the state of the parser after the failure. There are only two such failures:

A missing closing quote for an incomplete argument. This is handled by appending the missing quote. Therefore, shell completion suggestions for an argument 'path to will be generated with incomplete = "path to".
An incomplete escape sequence. This is handled by removing the incomplete sequence. Therefore, shell completion suggestions for an argument 'path\ will be generated with incomplete = "path". This mirrors the behaviour of zsh and possibly other shells.

Checklist:

[x] Add tests that demonstrate the correct behavior of the change. Tests should fail without the change.
[x] Add or update relevant docs, in the docs folder and in code.
[x] Add an entry in CHANGES.rst summarizing the change and linking to the issue.
[x] Add .. versionchanged:: entries in any relevant code docs.
[x] Run pre-commit hooks and fix any issues.
[x] Run pytest and tox, no tests failed.

lex.token contains the incomplete token after an error, so that can be used instead of modifying and re-splitting the string. Also, used parametrize and added a test of standard unquoted behavior.


Unable to resolve module ./assertEnvironment

After upgrading from "mobx": "^5.15.7" and "mobx-react": "^6.3.0" to "mobx": "^6.0.0" and "mobx-react": "^7.0.0" I receive an Unable to resolve module `./assertEnvironment error.
Intended outcome
The app doesn't have any errors
Actual outcome
error: Error: Unable to resolve module `./assertEnvironment` from `node_modules/mobx-react-lite/es/index.js`:

None of these files exist:
  * node_modules/mobx-react-lite/es/assertEnvironment(.native|.android.js|.native.js|.js|.android.json|.native.json|.json|.android.ts|.native.ts|.ts|.android.tsx|.native.tsx|.tsx)
  * node_modules/mobx-react-lite/es/assertEnvironment/index(.native|.android.js|.native.js|.js|.android.json|.native.json|.json|.android.ts|.native.ts|.ts|.android.tsx|.native.tsx|.tsx)
    at ModuleResolver.resolveDependency (/Users/virtumonde/Desktop/dev/project/project-client/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:163:15)
    at ResolutionRequest.resolveDependency (/Users/virtumonde/Desktop/dev/project/project-client/node_modules/metro/src/node-haste/DependencyGraph/ResolutionRequest.js:52:18)
    at DependencyGraph.resolveDependency (/Users/virtumonde/Desktop/dev/project/project-client/node_modules/metro/src/node-haste/DependencyGraph.js:287:16)
    at Object.resolve (/Users/virtumonde/Desktop/dev/project/project-client/node_modules/metro/src/lib/transformHelpers.js:267:42)
    at /Users/virtumonde/Desktop/dev/project/project-client/node_modules/metro/src/DeltaBundler/traverseDependencies.js:434:31
    at Array.map (<anonymous>)
    at resolveDependencies (/Users/virtumonde/Desktop/dev/project/project-client/node_modules/metro/src/DeltaBundler/traverseDependencies.js:431:18)
    at /Users/virtumonde/Desktop/dev/project/project-client/node_modules/metro/src/DeltaBundler/traverseDependencies.js:275:33
    at Generator.next (<anonymous>)
    at asyncGeneratorStep (/Users/virtumonde/Desktop/dev/project/project-client/node_modules/metro/src/DeltaBundler/traverseDependencies.js:87:24)

How to reproduce the issue
Install "mobx": "^6.0.0" and "mobx-react": "^7.0.0" on  "react-native": "0.63.3"
Versions
"mobx": "^6.0.0",
"mobx-react": "^7.0.0"
"react-native": "0.63.3"

could you verify in your lockfile / node_modules which version of mobx-react-lite is installed? should be 3.0.0 at least

@mweststrate Isn't the path wrong here?
node_modules/mobx-react-lite/es/assertEnvironment
Should be in utils dir<EMAIL_ADDRESS>

What I mean is the assertEnvironment is used by mobx-react-lite internally only. How is it possible something else is importing it from a different path?

@mweststrate
    "mobx-react": {
      "version": "6.3.1",
      "resolved": "https://registry.npmjs.org/mobx-react/-/mobx-react-6.3.1.tgz",
      "integrity": "sha512-IOxdJGnRSNSJrL2uGpWO5w9JH5q5HoxEqwOF4gye1gmZYdjoYkkMzSGMDnRCUpN/BNzZcFoMdHXrjvkwO7KgaQ==",
      "requires": {
        "mobx-react-lite": "^2.2.0"
      }
    },
    "mobx-react-lite": {
      "version": "2.2.2",
      "resolved": "https://registry.npmjs.org/mobx-react-lite/-/mobx-react-lite-2.2.2.tgz",
      "integrity": "sha512-2SlXALHIkyUPDsV4VTKVR9DW7K3Ksh1aaIv3NrNJygTbhXe2A9GrcKHZ2ovIiOp/BXilOcTYemfHHZubP431dg=="
    },

@virtumonde yeah that sounds like you have somehow a hardcoded import into the mobx-react-library somewhere? VSCode tends to do that sometimes :-P. I suspect this issue is further unrelated to the actual package. That file has moved indeed recently, but is internal so should not affect anything.

    "mobx-react": {
      "version": "7.0.0",
      "resolved": "https://registry.npmjs.org/mobx-react/-/mobx-react-7.0.0.tgz",
      "integrity": "sha512-yxbTG+ovn/GbgF3+QdQahkL5sXiITtwvkoXM6PNqd0V4jvO53cnr/YM4PYuA+0Ig95IW1nojA3qViJx9ufJm6w==",
      "requires": {
        "mobx-react-lite": "^3.0.0"
      }
    },
    "mobx-react-lite": {
      "version": "3.0.0",
      "resolved": "https://registry.npmjs.org/mobx-react-lite/-/mobx-react-lite-3.0.0.tgz",
      "integrity": "sha512-SJgrTD9mfClFOsamB+0y6zjteSMr4gkp9usnpIeEi8E+lW3lMgDa3hnD4PJgLGoENpJ8/9OmO3vrkA50SNy0mw=="
    },

@mweststrate let me look into it.

@mweststrate by hardcoded import you mean I am myself trying to access node_modules/mobx-react-lite/es/index.js?

yes
On Thu, Oct 1, 2020 at 2:44 PM Dan Clipca<EMAIL_ADDRESS>wrote:

@mweststrate https://github.com/mweststrate by hardcoded import you
mean I am myself trying to access node_modules/mobx-react-lite/es/index.js
?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mobxjs/mobx-react/issues/899#issuecomment-702145603,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAN4NBABVZOMB5LV35LVQCTSISBVDANCNFSM4SALP44A
.

having something in the form of import from "mobx-react-lite/something"
On Thu, Oct 1, 2020 at 2:46 PM Michel Weststrate<EMAIL_ADDRESS>wrote:

yes
On Thu, Oct 1, 2020 at 2:44 PM Dan Clipca<EMAIL_ADDRESS>wrote:

@mweststrate https://github.com/mweststrate by hardcoded import you
mean I am myself trying to access
node_modules/mobx-react-lite/es/index.js?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mobxjs/mobx-react/issues/899#issuecomment-702145603,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAN4NBABVZOMB5LV35LVQCTSISBVDANCNFSM4SALP44A
.

@mweststrate the only mention of mobx-react-lite is in my package-lock.json. I am sure that my code does not import it. Might other packages might import it? Here are my dependencies:
  "dependencies": {
    "@react-native-community/async-storage": "^1.12.0",
    "@react-native-firebase/app": "^8.4.5",
    "@react-native-firebase/crashlytics": "^8.4.8",
    "@react-native-mapbox-gl/maps": "^8.1.0-rc.4",
    "google-protobuf": "^3.13.0",
    "grpc-web": "^1.2.1",
    "lottie-react-native": "^3.5.0",
    "mobx": "^6.0.0",
    "mobx-react": "^7.0.0",
    "react": "16.13.1",
    "react-native": "0.63.3",
    "react-native-action-button": "^2.8.5",
    "react-native-modal": "^11.5.6",
    "react-native-permissions": "^2.2.2",
    "react-native-popup-menu": "^0.15.9",
    "react-native-safe-area-context": "^3.1.8",
    "react-native-sound": "^0.11.0",
    "react-native-toast-message": "^1.3.3",
    "react-native-vector-icons": "^7.1.0"
  },
  "devDependencies": {
    "@babel/core": "^7.11.6",
    "@babel/plugin-proposal-class-properties": "^7.10.4",
    "@babel/plugin-proposal-decorators": "^7.10.5",
    "@babel/runtime": "^7.11.2",
    "@react-native-community/eslint-config": "^2.0.0",
    "@types/geojson": "^7946.0.7",
    "@types/jest": "^26.0.14",
    "@types/react-native": "^0.63.23",
    "@types/react-test-renderer": "^16.9.3",
    "@types/uuid-parse": "^1.0.0",
    "@typescript-eslint/eslint-plugin": "^4.3.0",
    "@typescript-eslint/parser": "^4.3.0",
    "@types/google-protobuf": "^3.7.3",
    "@types/react-native-vector-icons": "^6.4.6",
    "babel-jest": "^26.3.0",
    "eslint": "^7.10.0",
    "jest": "^26.4.2",
    "metro-react-native-babel-preset": "^0.63.0",
    "prettier": "^2.1.2",
    "react-test-renderer": "16.13.1",
    "typescript": "^4.0.3"
  }

Also, switching back to "mobx-react": "^6.3.0" and "mobx": "^6.0.0" doesn't trigger the error.

Something is apparently importing the old file. Maybe even some sort of cache? Might be even duplicate versions of packages. I recommend deleting node_modules and reinstalling from the scratch.

@FredyC I already did that 5 times. I will look into other possibilities soon as for now this is not critical to me.

If switching to mobx-react:6.3 and mobx:6 does work for you, there is
definitely something wrong, as those should normally not be able to work
together :-P. There is something weird, are you sure you have cleared all
caches, have the same folder open in terminal, ide and project that is
running, etc? Otherwise I recommend to build a minimal repro, usually the
process of doing that finds the culprit
On Thu, Oct 1, 2020 at 2:55 PM Dan Clipca<EMAIL_ADDRESS>wrote:

@FredyC https://github.com/FredyC I already did that 5 times. I will
look into other possibilities soon as for now this is not critical to me.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mobxjs/mobx-react/issues/899#issuecomment-702152939,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAN4NBHRF44T2FSJ6B4RYUTSISC6LANCNFSM4SALP44A
.

@mweststrate I meant "mobx": "^5.15.7" instead of "mobx": "^6.0.0". My bad.

ok, nonetheless would be great to build a minimal reproduction. Might be an
uncommon module format or something that messes things up.

Just for confirmation, I just tried both a fresh CRA and a fresh RN project with mobx@6 + mobx-react@7 and they work fine. So this really seems to be a local issue. You can try to run yarn why mobx-react-lite (or the other 2) to see if another package accidentally brings a different version of those packages.

Healthy output looks like:
yarn why mobx-react-lite
yarn why v1.22.4
[1/4] 🤔  Why do we have the module "mobx-react-lite"...?
[2/4] 🚚  Initialising dependency graph...
[3/4] 🔍  Finding dependency...
[4/4] 🚡  Calculating file sizes...
=> Found<EMAIL_ADDRESS>info Reasons this module exists
   - "mobx-react" depends on it
   - Hoisted from "mobx-react#mobx-react-lite"
info Disk size without dependencies: "316KB"
info Disk size with unique dependencies: "316KB"
info Disk size with transitive dependencies: "316KB"
info Number of shared dependencies: 0
✨  Done in 0.48s.

Closing until more info becomes available


Working PR - Restructure accessibilty SPEC

A working PR for @MarsBarLee and I to review restructuring this SPEC and adding relevant content before opening a PR to the upstream repo.

Closing this to make a PR upstream. Thank you for the feedback!

Upstream PR is at scientific-python/specs #134


Unicode errors

I'm trying to load a series of CSVs into agate so that I can merge them. I'm using Python 2.7, and I have csvkit installed.
Agate keeps choking on some of them. It gives errors along these lines:
UnicodeDecodeError: 'utf8' codec can't decode byte 0xc9 in position 0: invalid continuation byte
Here are two of the lines that have unicode characters:
14-038753,2014-08,08/22/2014 23:00,Y, , ,1, , 67701,4,LARCENY-FROM BUILDING UNDER $500,3131,OLIVE ST,37,DOUBLE APPLE CAFÉ AND HOOKAH LOUNGE, ,3131,OLIVE,898807.7,1020477
14-038854,2014-08,08/25/2014 14:00,Y, , ,1, , 67601,4,"LARCENY-FROM BUILDING $500 - $24,999",701,CONVENTION PZ,35,AMERICA’S CENTER CONVENTION COMPLEX, ,701,CONVENTION,908773.3,1019107
Here's a traceback:
Traceback (most recent call last):
    File "crime-report-parser.py", line 649, in <module>
        main()
    File "crime-report-parser.py", line 638, in main
        clean_files()
    File "crime-report-parser.py", line 93, in clean_files
        agate.Table.from_csv('monthly_files/' + filename, column_names=column_names, column_types=column_types)
    File "/Users/stlrenaj/.virtualenvs/crime/lib/python2.7/site-packages/agate/table.py", line 283, in from_csv
        rows = list(csv.reader(f, **kwargs))
    File "/Users/stlrenaj/.virtualenvs/crime/lib/python2.7/site-packages/agate/csv_py2.py", line 59, in next
        row = next(self.reader)
    File "/Users/stlrenaj/.virtualenvs/crime/lib/python2.7/site-packages/six.py", line 558, in next
        return type(self).__next__(self)
    File "/Users/stlrenaj/.virtualenvs/crime/lib/python2.7/site-packages/agate/csv_py2.py", line 43, in __next__
        return next(self.reader).encode('utf-8')
    File "/Users/stlrenaj/.virtualenvs/crime/lib/python2.7/codecs.py", line 618, in next
        line = self.readline()
    File "/Users/stlrenaj/.virtualenvs/crime/lib/python2.7/codecs.py", line 533, in readline
        data = self.read(readsize, firstline=True)
    File "/Users/stlrenaj/.virtualenvs/crime/lib/python2.7/codecs.py", line 480, in read
        newchars, decodedbytes = self.decode(data, self.errors)

After lots of hair-pulling, I saw in the docs that I could specify an encoding. Specifying "latin1" solved this issue.


Include response headers from all operations

For shared response envelopes, ensure that header responses from all
operations are included in the envelope.

Fixes https://github.com/Azure/autorest.go/issues/292

Note that we don't have any swaggers that model this at present so I had to fabricate a local test to verify the fix.


Windows update

￼@Asymvivastos **_````

@Asymvivastos Thank you for your post . We have three similar issues for this one . Hence we will be closing this out as duplicate.

@Asymvivastos  Thank you for your post . I checked the other issues you have opened for the same thing I have closed the duplicates . We use this repo of azure-docs for improvements in azure Documentation . Could you please provide details of the azure documentation which you feel is linked to the WHCP windows release ? In case you are searching for documentation of windows or the windows docs repository , Please find them as below.
Windows Docs :- https://docs.microsoft.com/en-us/windows/
Windows Server Documentation :- https://docs.microsoft.com/en-us/windows-server/
Github Repos :-
Windows Driver Docs :- https://github.com/MicrosoftDocs/windows-driver-docs
Windows Server Docs :- https://github.com/MicrosoftDocs/windowsserverdocs
Windows 10 docs for IT pros :- https://github.com/MicrosoftDocs/windows-itpro-docs
Windows Hardware Dev docs :- https://github.com/MicrosoftDocs/windows-driver-docs
In case you have any further questions on the above you can open an issue in the related repo . If you still have any questions, please feel free to let us know and we will be glad to help .
Thank you..

Good


carlo will not launch on win10

Accoding to some bug/feature in puppeteer, carlo/puppeteer will not launch on win10 sometimes. see: https://github.com/GoogleChrome/puppeteer/issues/3186
here is how to fix I found:
when launch puppeteer, add an option ignoreDefaultArgs: ['--disable-extensions'], to puppeteer.launch in this line
https://github.com/GoogleChromeLabs/carlo/blob/master/lib/carlo.js#L619

Adding the option "ignoreDefaultArgs: ['--disable-extensions']," does not appear to resolve the problem.  Is this issue being addressed or are there any other short term work around?

Adding the option "ignoreDefaultArgs: ['--disable-extensions']," does not appear to resolve the problem. Is this issue being addressed or are there any other short term work around?

The option shoud put into the source of carlo where carlo init the pptr, not the code of yours where init carlo.Carlo doesn't have this option at the moment.


Kotlin support

No error with compilation but this does not work with Kotlin.

@orhanobut Any update on this? Or can you guide me to contribute so as to make it work with Kotlin?


Fails to index default unnamed export

While indexing, any files that have a straight default export will fail to index
/Users/userName/Projects/projectName/app/scenes/sceneName.js
TypeError: Cannot read property 'name' of null

export default function () { … }

Naming the export fixes it
export default function Scene() { … }

Thanks for reporting. This is the known issues list. Will get to it soon.
I'm curious, how are you finding the tool? I'm curious to know what people find the most useful and what you think could improve?

I've only spent a few minutes with it so far, definitely fond of the concept but I'll have to dedicate more time to see if I like the workflow before I can speak to that
First impressions are basically around appearance and usability:
If the stage used my VS Code theme (with any necessary extra properties that it can't grab from the existing set) it'd be a lot more pleasant to play around with
Dream interaction would be like Figma where I can scroll around in any direction without having to click and drag to pan
Also a zoom out to overview so I can then zoom in on the target symbol that might be too far to comfortably pan back and forth at 100% scale


Does not detect change in state

This module doesn't detect a change in camera state. Here is an example program which polls the module every 1 second. While the program is running, if I start or stop using the camera, the output never reflects the new state. Terminating my program and starting it again does reflect the new state.
package main

import (
	"log"
	"time"

	mediaDevices "github.com/antonfisher/go-media-devices-state"
)

func main() {
	for {
		isCameraOn, err := mediaDevices.IsCameraOn()
		if err != nil {
			log.Println("Error:", err)
		} else {
			log.Println("Is camera on:", isCameraOn)
		}

		time.Sleep(1 * time.Second)
	}
}

Hi @TravisTX,
Yes, can confirm i see the same. Interesting that if i run it like:
while sleep 1; do go run ./cmd/demo.go; done;

it detects the camera properly. One workaround can be spawning a process for each check:
./cmd/demo.go:
package main

import (
	"fmt"
	"os/exec"
	"time"
)

func main() {
	for {
		checkCmd := exec.Command("bash", "-c", "go run /tmp/check.go")
		checkOut, _ := checkCmd.Output()
		fmt.Printf("Is camera on: %v", string(checkOut))
		time.Sleep(1 * time.Second)
	}
}

/tmp/check.go:
package main

import (
	"fmt"

	mediaDevices "github.com/antonfisher/go-media-devices-state"
)

func main() {
	isCameraOn, _ := mediaDevices.IsCameraOn()
	fmt.Println(isCameraOn)
}

and run it like:
go run ./cmd/demo.go

There seem to be some kind of caching for running in the same process 🤔


Have the terminal color turn off when piping output.

When I look at the command line options:
sg scan --help
Scan and rewrite code by configuration

Usage: sg scan [OPTIONS] [PATHS]...

Arguments:
  [PATHS]...  The paths to search. You can provide multiple paths separated by spaces [default: .]

Options:
  -c, --config <CONFIG>              Path to ast-grep root config, default is sgconfig.yml
  -r, --rule <RULE>                  Scan the codebase with one specified rule, without project config setup
  -i, --interactive                  Start interactive edit session. Code rewrite only happens inside a session
      --color <COLOR>                Controls output color [default: auto]
      --report-style <REPORT_STYLE>  [default: rich] [possible values: rich, medium, short]
      --json                         Output matches in structured JSON text. This is useful for tools like jq. Conflicts with color and report-style
      --accept-all                   Apply all rewrite without confirmation if true
      --no-ignore <NO_IGNORE>        Do not respect ignore files. You can suppress multiple ignore files by passing `no-ignore` multiple times [possible values: hidden, dot, exclude, global, parent, vcs]
  -h, --help                         Print help

the indentation makes it look like --color is auto by default, which makes me think:
sg scan | cat

should produce an output without color. It is still colored for me. Even when I try:
sg scan --color auto | cat

it is still colored.
So when I try:
sg scan --color auto | grep "^error"

it doesn't match anything. However, when I run:
sg scan --color never | grep "^error"

it works as expected.
Also, minor note, the available options for <COLOR> aren't visible in the help, unless you try an unsupported value (e.g.  sg scan --color something shows the list of valid values). Where as the options are available for ls:
ls --help | grep colo
  --colo[u]r=WHEN    when to use terminal colours (always, auto, never)
  --colo[u]r-scale   highlight levels of file sizes distinctly

or ripgrep:
rg --help
...
        --color <WHEN>
            This flag controls when to use colors. The default setting is 'auto', which
            means ripgrep will try to guess when to use colors. For example, if ripgrep is
            printing to a terminal, then it will use colors, but if it is redirected to a
            file or a pipe, then it will suppress color output. ripgrep will suppress color
            output in some other circumstances as well. For example, if the TERM
            environment variable is not set or set to 'dumb', then ripgrep will not use
            colors.

            The possible values for this flag are:

                never    Colors will never be used.
                auto     The default. ripgrep tries to be smart.
                always   Colors will always be used regardless of where output is sent.
                ansi     Like 'always', but emits ANSI escapes (even in a Windows console).

            When the --vimgrep flag is given to ripgrep, then the default value for the
            --color flag changes to 'never'.
...

Thanks for the reporting. I think it is reasonable to align ast-grep's behavior with rg.


Dynamic dispatch – version 1

Summary
Implementing a simplified method dispatch model for Enso.
Value
Polymorphic dispatch is the basis of code reuse. This first implementation will allow us to focus on the
Specification

V1 only dispatches based on the constructor of self argument.
Any symbol that is not a local binding or a globally defined type constructor should be assumed dynamic. Whenever the word self is used we mean either the explicit method call target or the first argument is the method is called using functional syntax.
(suggestion from MK, not actual spec): from point 2. it seems to me it would be wise to desugar any dynamic symbol application to the canonical form of x.sym y z. Seems like it would inline better in Truffle.
Methods need to be defined for monomorphic constructors (not types). I.e. valid method definitions are e.g. Cons.reverse, Just.isPresent or False.isTrue, but not (List Int).sum, (Just Int).isPresent, Boolean.isFalse or a.toString.
We're still working in a single global scope, not taking multiple files scoping into consideration.

Acceptance Criteria & Test Cases

Test case: [1, "foo", False, Just (Just Nil)].map toString.
Benchmarks: tail recursive functions used in the benchmarks so far (summing numbers upto n, reversing a list, summing a list), each defined as a method on the respective type. Goal here would be to have them up to 10%-20% slower than local lambda versions. Some slowdown is necessary, because even with polymorphic inline caches in place we still need one more comparison + conditional jump to ensure cache is valid.
Eyeballing Assembly: post here the relevant bits of assembly code for JITed versions of the benchmarks above. The difference between these and local-lambda versions in the case of at-most-two different call targets (as is the case when recursing over lists) should be just a simple cache comparison in an otherwise tight loop.

In fact it seems entirely possible to get benchmarks working on lists to be as fast as the local lambda versions or even faster. Note we're trading an explicit pattern match for dynamic dispatch. Still the number based benchmarks will probably slow down with one more conditional jump in the loop.

This also needs to account for improving performance of mutual recursion in the global scope as currently that's super slow.


fix: better email notifications and error reporting when importing Pros

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


[rag eval] add rag ans section

https://github.com/datacommonsorg/website/assets/69875368/7334d32d-4042-41a8-aca0-c7a8ef75e62f

Awesome!
usability nit: on the claim-count UI, should we make the "-" and "+" bigger?  That's the one we'll be clicking more.  Also should we put "+" on the LHS, so its more natural to click it (I imagine we more often hit +)?

Awesome!
usability nit: on the claim-count UI, should we make the "-" and "+" bigger? That's the one we'll be clicking more. Also should we put "+" on the LHS, so its more natural to click it (I imagine we more often hit +)?

made the buttons bigger, but putting + on LHS feels unintuitive .. can change if we feel like that's useful though
https://screenshot.googleplex.com/6CpphnDKkXgtyEa

Awesome!
usability nit: on the claim-count UI, should we make the "-" and "+" bigger? That's the one we'll be clicking more. Also should we put "+" on the LHS, so its more natural to click it (I imagine we more often hit +)?

made the buttons bigger, but putting + on LHS feels unintuitive .. can change if we feel like that's useful though https://screenshot.googleplex.com/6CpphnDKkXgtyEa

ok.  but curious the reason it feels unintuitive?
my rationale was, given english is L->R lang, the first thing to do comes to the L.  And starting from 0, the first thing to do is +, not - :)

Awesome!
usability nit: on the claim-count UI, should we make the "-" and "+" bigger? That's the one we'll be clicking more. Also should we put "+" on the LHS, so its more natural to click it (I imagine we more often hit +)?

made the buttons bigger, but putting + on LHS feels unintuitive .. can change if we feel like that's useful though https://screenshot.googleplex.com/6CpphnDKkXgtyEa

ok. but curious about the reason it feels unintuitive?
my rationale was, given english is L->R lang, the first thing to do comes to the L. And starting from 0, the first thing to do is +, not - :)

But leaving it as is, is fine for now.

Awesome!
usability nit: on the claim-count UI, should we make the "-" and "+" bigger? That's the one we'll be clicking more. Also should we put "+" on the LHS, so its more natural to click it (I imagine we more often hit +)?

made the buttons bigger, but putting + on LHS feels unintuitive .. can change if we feel like that's useful though https://screenshot.googleplex.com/6CpphnDKkXgtyEa

ok. but curious about the reason it feels unintuitive?
my rationale was, given english is L->R lang, the first thing to do comes to the L. And starting from 0, the first thing to do is +, not - :)

I think it feels unintuitive because on a number line, numbers decrease going to the left and increase going to the right. So I associate left with decreasing and right with increasing .. but that might just be me


bug - not recalculating formulas using the values of new included rows

Hi, my code has in the last row a totalizer using a SUM formula for de prices, and when i added a new row and put the new price, this formula is not updated. But, when i change the value of another pre existing row, the formula is recalculated and, if i change the value of the row that i have inserted early, the formula is recalculated correctly. I think that means like is missing a refresh on the formula after insert the values of a new row.
<!DOCTYPE html>

    <meta charset="UTF-8">
    <title></title>

    <link rel="stylesheet" href="https://jsuites.net/v4/jsuites.css" type="text/css">
    <link rel="stylesheet" href="https://bossanova.uk/jspreadsheet/v4/jexcel.css" type="text/css">

<button id="add_row">INSERT ROW BEFORE SECOND ROW</button>

I inserted the row of 'Subaru' and the value of the formula keeps the same:

I change the price of the row 'Civic' and the value of the formula was recalculated:

Then when i change the value of the row 'Subaru', the formula was recalculated including this row

Are there any way to force a formula recalculation/refresh on event oninsertedrow?

Your example using JSS Pro + Formula Pro extension.
https://jsfiddle.net/spreadsheet/hzc3r01o/


documentation

Hello
is there any documetacion about which parameters can be set ? for example when I am connecting do existing proxmox claster i trying to create new vm, terraform remove vm with id 101 and creates a new one in its place.

this documentation is a complete mess. Installation steps are not complete, no info about how to set credentials to Proxmox servers.

Its a huge pain. Not to mention it not working or I am doing something wrong. Don't know why the TF apply wants to modify the host every time and fail.


fix aardvark output logic

When we have debug level we want stderr connected. If this is not the
case we should use /dev/null.
Also do not connect stdin and use Stdio::inherit() instead of the unsafe
call.

@flouthoc @mheon @baude @rhatdan @vrothberg PTAL This should unblock podman CI.

/lgtm


TapDS API

API part of envoyproxy/envoy#7194
This introduces the API for the changes coming for the tap filter.
The main features are adding a grpc server sink, and a configuration via xDS.
Risk Level: Low (just API - no implementation)
Testing: N/A
Docs Changes: docs are there but hidden.
Release Notes: N\A
Part of envoyproxy/envoy#6110

/retest

the cat-bot doesn't seem to be able to re-test azure pipelines?

/retest

@yuval-k friendly request to not force push, it makes it much harder to review. Thank you!

@mattklein123  sorry about the force push - I had to do it to fix DCO, as i used the github interface to accept a suggested fix, which resulted in a commit without a signoff.. not sure how to fix DCO without force push


Boilerplate code rediction

Boilerplate code reduced

Coverage remained the same at 97.917% when pulling e9239fbe7d3c897b29fe3bde857d772469541c01 on trierra:code-duplicates-fix into 4718daefac2d16bfb3b32b9761c356cdd2461d71 on form-data:master.

Coverage remained the same at 97.917% when pulling aa9924626bd9168334d73fea568c0ad9d8fbaa96 on trierra:code-duplicates-fix into 4718daefac2d16bfb3b32b9761c356cdd2461d71 on form-data:master.


Got an error during the install

Running in a Python 3.6.1 venv. I got the following error when running 'python setup.py install':
Installed /home/user/.venv/stakemachine/lib/python3.6/site-packages/stakemachine-0.0.6-py3.6.egg Processing dependencies for stakemachine==0.0.6 Searching for click-datetime Reading https://pypi.python.org/simple/click-datetime/ Downloading https://pypi.python.org/packages/61/82/8f81081e0d1dad2d81fb745110d9d2c85144cca23b52c7b7da6e879c7a67/click-datetime-0.2.tar.gz#md5=a228eb52f58c8b1ebaa50e38fc81355a Best match: click-datetime 0.2 Processing click-datetime-0.2.tar.gz Writing /tmp/easy_install-7_ehpzp7/click-datetime-0.2/setup.cfg Running click-datetime-0.2/setup.py -q bdist_egg --dist-dir /tmp/easy_install-7_ehpzp7/click-datetime-0.2/egg-dist-tmp-l9nm2d5_ error: [Errno 2] No such file or directory: 'README.md'
Not sure why it happened, but I was able to complete the installation after running 'pip install click-datetime'

I also can reproduce this issue.

It seems an issue in the manual installation of click-datetime: https://github.com/click-contrib/click-datetime/issues/1
Also from a quick search it seems that click-datetime is not used, so maybe it can just be removed  from the dependencies.

Try
pip3 install uptick
and
uptick addkey
before configuring stakemachine. uptick is a requisite https://github.com/xeroc/uptick

try
pip3 install click-datetime


Travis build failing due to broken plugin test

The Travis build is failing due to a broken test.
The cause is:
type":"PluginNotFoundException","errorCode":12002,"message":"Plugin does not exist: 1"
The test assumes a predicable ID for the created plugin but this is not so. Need to update test to use the response of listing plugins to get the right ID.

Fixed in https://github.com/apiman/apiman-cli/commit/b3f5eff97c986cd4a89ffed77f51adfde2693987. CI build: https://travis-ci.org/apiman/apiman-cli/builds/125208509


Crash when loading Tracer Round with Ender IO.

Issue Description:
All I know is Minecraft does not go any further other than halfway through loading when Tracer Round conflicts with Ender IO.
What happens:
Crash before Minecraft fully loads.
What you expected to happen:
Minecraft to load.
Steps to reproduce:

Launch Minecraft.

Affected Versions (Do not use "latest"):

EnderIO: 5.0.29
EnderCore: 0.5.35
Minecraft: 1.12.2
Forge: <IP_ADDRESS>05
Tracer: 0.2

Your most recent log file where the issue was present:
https://pastebin.com/xzFCaUpW

Well they dont have a github... or a place to look at there code... or a way to report issues at all... im going to guess this is on them from the crash report.

Yes, sadly they don't at all. :/ Oh well. Thanks.

https://gyazo.com/8d030cd9427a35dd28384626031d3159

https://gyazo.com/81ba6cf8cd5a5aa7d030f11cf46c9014
ill wait for someone else to chime in here to confirm.. i'm still learning
it seems to me that
They import the old package crazypants.enderio.item.darksteel.ItemDarkSteelBow
The new one is crazypants.enderio.base.item.darksteel.ItemDarkSteelBow
therefore the class is not loaded and results in a Null pointer exception
(i think)

sorry for poking this issue even if it is old
https://github.com/Lunatrius/Tracer/issues
isn't that their git or is this just a similar named mod?

That stuff is in com.github.lunatrius.tracer, the crash is in com.empiricist.tracer, so not the same mod.

yeah i already figured that is why i asked, maybe the mod had switched owner recently because i can not find this particular mod from this particular build anywhere on curse


Model rerun file as a class and add tests - issue #865

Here is a starter for discussion around modelling the rerun file issue #865. See what you think and let me know. Cheers, Matt

Looks great to me!

Thanks @mattwynne - changes made as suggested.

Good work @mcrmfc :bow:

Thanks! @mcrmfc


Add CI infrastructure, fix some nits

Stack builds: https://github.com/slotThe/X11-xft/actions/runs/1458776382
Haskell CI builds: https://github.com/slotThe/X11-xft/actions/runs/1458776381
In order to get https://github.com/xmonad/xmonad-contrib/pull/646 going more quickly, I decided to fudge around with the CI for this repo.  I also used this opportunity to clean things up a little.
Obligatory reminder that I have no idea what I'm doing
Commits
Sync Cabal version with Hackage
The newest version on Hackage is 0.3.1, while this is being declared as
0.3.3 in the cabal file.  This might be confusing to... everyone
involved and so it seems best to sync these.
Add CHANGES.md
Add README.md
Update cabal file

Remove spurious `Hello' executable, since this is strictly a library
and as such this is unused.
Change the source-repository URL to the xmonad project—the repo got
transferred to us by Clemens.
Delete the unused Setup.lhs.

X11-xft.cabal: Add -fpedantic, update default flags

Add -Wall and -fno-warn-unused-binds to the default ghc-options.  This
is to keep this in sync with the X11 library
Much like the rest of the project, introduce a `pedantic' flag that
enables -Werror (and, for now, nothing else).  This will later be used
in the CI to ensure that new pull requests do not introduce any new
warnings.

Add stack.yaml
Add a simple stack.yaml file to make the project easily compilable via
stack.
Silence warnings
With the new default build flags introduced in 1, we now get a lot of
warnings that need to be fixed before enabling the CI; do that.
Add GitHub actions
This is mostly a copy-paste of what X11 does1.
Update gitignore
Ignore the usual suspects when it comes to building with Cabal and
stack.

The fact that we have an empty configure.ac is obviously quite horrible (and just a stupid hack to make haskell-ci happy) and should probably be changed in some way.  I, however, have absolutely no idea what that file even is (nor do I understand what the X11 version does)

configure.ac is needed in the X11 package to find the various X11 extensions or complain if they're not present. If X11-xft doesn't need to do this (which it probably doesn't) then we should adapt the ci-actions to not use configure.ac. (I could look, but I have no idea how github actions works.)

Thanks for taking care of this package. Before we accept contributions, it might make sense to switch the license to BSD3. The library does not create enough value on its own to give future users a license headache. I don't feel strongly about it, but in case somebody else does: "I as the original author support relicensing to BSD3."

Thanks for taking care of this package. Before we accept contributions, it might make sense to switch the license to BSD3. The library does not create enough value on its own to give future users a license headache. I don't feel strongly about it, but in case somebody else does: "I as the original author support relicensing to BSD3."

Indeed, if you still hold all the copyrights to allow relicensing, it's probably best to do it. Very good point, thanks!

Indeed, if you still hold all the copyrights to allow relicensing, it's probably best to do it. Very good point, thanks!

I just review my old darcs repo, and I do hold all the copyright.

It hurts me a little bit to relicense something from copyleft to permissive, but if that's what the majority wants I won't object.
@clefru are you happy with https://github.com/xmonad/X11-xft/pull/1/commits/b3668484b7bed612097dc1060bbcc8726bd38a2b ?

It hurts me a little bit to relicense something from copyleft to permissive, but if that's what the majority wants I won't object.

I do strongly prefer copyleft. For cryptsetup, I long refused GPL->LGPL relicensing, because there is real value in that software. But how much value you does X11-xft bring to the table? X11-xft is a simple wrapper. There are maybe 20 LOC that meet the bar of copyrightable work. If the LGPL license is an obstacle, somebody can rewrite it in half day, and that somebody will be grumpy about it. In this case, I prefer to fit in with the X11 and Xft license.

@clefru are you happy with 1032ad3 ?

Yes, I am. Thank you!


Configure system pre-reqs on beavan cluster

The team want to run the inversion on the beaven cluster,
So that we can test scaling and get some preliminary results on a low-cost MPI cluster
but we're going to need newer software installed there. We need

[ ] java 8 (1.8) JRE on all worker nodes
[ ] latest python3 on all nodes
[ ] java 8 (1.8) JDK (on master) so we can compile in situ

NB if  anyone else is ever confused by this,  java  8 == java 1.8 see https://stackoverflow.com/questions/53642402/why-do-i-see-open-jdk-1-8-instead-of-java-8

Should not need the JDK. If we set up the build to produce runnable artifacts we can just load and run them.
I would suggest using Java 11 as 8 is getting a bit long in the tooth.
It might also be worth looking at building standalone apps that target the cluster architecture. This would mean that we would not require any changes to the servers.

Thanks @ornearius  - agree  Java 11 (since 12 not supported)

scratch the JDK as this will be catered for by the gradle updates (you'll raise a ticket on this)

@ornearius I just spoke to Roger Williams and this is the approach we can take....

[ ] install the java 8 JRE binaries into the /opt/sw/java folder (I'm currently owner of this folder) this path is mapped on all cluster nodes
[X] we can access python 3 in /op/sw also (latest is 3.6)

Also FYI - as our data files will be large we'll use the /shared folder to read/write our datasets. This storage is not backed up but has plenty of spare capacity.

TODO:

[ ] create scripts folder in project for the cluster-specific (PBS) scripts
[ ] add a readme for this stuff


Merge developer to master for 1.0.0 release

Do the merge, tag the release and push the podspec.

Abandon this. Got some extra last minute fixes for the release.


WindowsError

Expected Behavior
Looks like i have successfully done '$ pip2 install -r requirements.txt'
then i blocking with '$ git submodule init'
Actual Behavior
$ pip2 install -r requirements.txt
Requirement already satisfied (use --upgrade to upgrade): numpy==1.11.0 in f:\python27\lib\site-packages (from -r requirements.txt (line 1))
Requirement already satisfied (use --upgrade to upgrade): networkx==1.11 in f:\python27\lib\site-packages (from -r requirements.txt (line 2))
Obtaining pgoapi from git+https://github.com/keyphact/pgoapi.git@249d3be7fbbdabc7f9adea17cbc899d6549e47a2#egg=pgoapi (from -r requirements.txt (line 3))
Skipping because already up-to-date.
Requirement already satisfied (use --upgrade to upgrade): geopy==1.11.0 in f:\python27\lib\site-packages (from -r requirements.txt (line 4))
Requirement already satisfied (use --upgrade to upgrade): protobuf==3.0.0b4 in f:\python27\lib\site-packages (from -r requirements.txt (line 5))
Requirement already satisfied (use --upgrade to upgrade): requests==2.10.0 in f:\python27\lib\site-packages (from -r requirements.txt (line 6))
Requirement already satisfied (use --upgrade to upgrade): s2sphere==0.2.4 in f:\python27\lib\site-packages (from -r requirements.txt (line 7))
Requirement already satisfied (use --upgrade to upgrade): gpsoauth==0.3.0 in f:\python27\lib\site-packages (from -r requirements.txt (line 8))
Collecting protobuf-to-dict==0.1.0 (from -r requirements.txt (line 9))
Collecting googlemaps==2.4.4 (from -r requirements.txt (line 10))
Using cached googlemaps-2.4.4-py2-none-any.whl
Collecting colorama==0.3.7 (from -r requirements.txt (line 11))
Using cached colorama-0.3.7-py2.py3-none-any.whl
Collecting enum34==1.1.6 (from -r requirements.txt (line 12))
Using cached enum34-1.1.6-py2-none-any.whl
Requirement already satisfied (use --upgrade to upgrade): pyyaml==3.11 in f:\python27\lib\site-packages (from -r requirements.txt (line 13))
Collecting haversine==0.4.5 (from -r requirements.txt (line 14))
Collecting polyline==1.3.1 (from -r requirements.txt (line 15))
Using cached polyline-1.3.1-py2.py3-none-any.whl
Collecting python-socketio==1.4.2 (from -r requirements.txt (line 16))
Collecting flask==0.11.1 (from -r requirements.txt (line 17))
Using cached Flask-0.11.1-py2.py3-none-any.whl
Collecting socketIO_client==0.7.0 (from -r requirements.txt (line 18))
Collecting eventlet==0.19.0 (from -r requirements.txt (line 19))
Using cached eventlet-0.19.0-py2.py3-none-any.whl
Collecting gpxpy==1.1.1 (from -r requirements.txt (line 20))
Collecting mock==2.0.0 (from -r requirements.txt (line 21))
Using cached mock-2.0.0-py2.py3-none-any.whl
Collecting timeout-decorator==0.3.2 (from -r requirements.txt (line 22))
Collecting raven==5.23.0 (from -r requirements.txt (line 23))
Using cached raven-5.23.0-py2.py3-none-any.whl
Requirement already satisfied (use --upgrade to upgrade): decorator>=3.4.0 in f:\python27\lib\site-packages (from networkx==1.11->-r requirements.txt (line 2))
Requirement already satisfied (use --upgrade to upgrade): six in f:\python27\lib\site-packages (from pgoapi->-r requirements.txt (line 3))
Collecting xxhash (from pgoapi->-r requirements.txt (line 3))
Using cached xxhash-0.6.1.tar.gz
Requirement already satisfied (use --upgrade to upgrade): setuptools in f:\python27\lib\site-packages (from protobuf==3.0.0b4->-r requirements.txt (line 5))
Requirement already satisfied (use --upgrade to upgrade): future in f:\python27\lib\site-packages (from s2sphere==0.2.4->-r requirements.txt (line 7))
Requirement already satisfied (use --upgrade to upgrade): pycryptodomex>=3.0 in f:\python27\lib\site-packages (from gpsoauth==0.3.0->-r requirements.txt (line 8))
Collecting python-engineio>=0.8.0 (from python-socketio==1.4.2->-r requirements.txt (line 16))
Collecting click>=2.0 (from flask==0.11.1->-r requirements.txt (line 17))
Collecting Jinja2>=2.4 (from flask==0.11.1->-r requirements.txt (line 17))
Using cached Jinja2-2.8-py2.py3-none-any.whl
Collecting Werkzeug>=0.7 (from flask==0.11.1->-r requirements.txt (line 17))
Using cached Werkzeug-0.11.10-py2.py3-none-any.whl
Collecting itsdangerous>=0.21 (from flask==0.11.1->-r requirements.txt (line 17))
Collecting websocket-client (from socketIO_client==0.7.0->-r requirements.txt (line 18))
Collecting greenlet>=0.3 (from eventlet==0.19.0->-r requirements.txt (line 19))
Using cached greenlet-0.4.10-cp27-cp27m-win32.whl
Collecting funcsigs>=1; python_version < "3.3" (from mock==2.0.0->-r requirements.txt (line 21))
Using cached funcsigs-1.0.2-py2.py3-none-any.whl
Collecting pbr>=0.11 (from mock==2.0.0->-r requirements.txt (line 21))
Using cached pbr-1.10.0-py2.py3-none-any.whl
Requirement already satisfied (use --upgrade to upgrade): contextlib2 in f:\python27\lib\site-packages (from raven==5.23.0->-r requirements.txt (line 23))
Collecting MarkupSafe (from Jinja2>=2.4->flask==0.11.1->-r requirements.txt (line 17))
Building wheels for collected packages: xxhash
Running setup.py bdist_wheel for xxhash: started
Running setup.py bdist_wheel for xxhash: finished with status 'done'
Stored in directory: C:\Users\Administrator\AppData\Local\pip\Cache\wheels\01\4b\34\ed020afed2c3a5b5f0ca2384b37b9d529c517dc632ed101666
Successfully built xxhash
Installing collected packages: xxhash, pgoapi, protobuf-to-dict, googlemaps, colorama, enum34, haversine, polyline, python-engineio, python-socketio, click, MarkupSafe, Jinja2, Werkzeug, itsdangerous, flask, websocket-client, socketIO-client, greenlet, eventlet, gpxpy, funcsigs, pbr, mock, timeout-decorator, raven
Running setup.py develop for pgoapi
Found existing installation: raven 5.24.2
Uninstalling raven-5.24.2:
Successfully uninstalled raven-5.24.2
Successfully installed Jinja2-2.8 MarkupSafe-0.23 Werkzeug-0.11.10 click-6.6 colorama-0.3.7 enum34-1.1.6 eventlet-0.19.0 flask-0.11.1 funcsigs-1.0.2 googlemaps-2.4.4 gpxpy-1.1.1 greenlet-0.4.10 haversine-0.4.5 itsdangerous-0.24 mock-2.0.0 pbr-1.10.0 pgoapi polyline-1.3.1 protobuf-to-dict-0.1.0 python-engineio-0.9.2 python-socketio-1.4.2 raven-5.23.0 socketIO-client-0.7.0 timeout-decorator-0.3.2 websocket-client-0.37.0 xxhash-0.6.1
Administrator@UNBEATABLE MINGW32 ~/Desktop/1/PokemonGo-Bot-dev
$ git submodule init
fatal: Not a git repository (or any of the parent directories): .git
Can anyone tell me what i should do next, please?
Other Information
OS: Windows 10
Python Version: Python 2.7.10

Administrator@UNBEATABLE MINGW32 ~/Desktop/1/PokemonGo-Bot-dev
$ git init
Initialized empty Git repository in C:/Users/Administrator/Desktop/1/PokemonGo-Bot-dev/.git/


⚠ Bofrost.lu has degraded performance

In 575ca5b, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1438 ms

Resolved: Bofrost.lu performance has improved in af2e550 after 8 minutes.


Unable to run tests with command line arguments

On some test files, I'm unable to run tests with command line arguments, and recieve an "unknown option" error message for the first argument passed.
I've noticed that it happens in files where the before and after hooks are implemented, but it some of those files do manage to run with command line args.

@roiperlman With above information it's impossible to support you in any way.
Please provide required details to reproduce this issue or close. Thanks.


Remove CDN Link from manifest.

i think we should use our webserver

I think this usage is fine. I just created a PR to use the current version of the icon: https://github.com/lnbits/lnbits/pull/2010


Refactor api spelling

ronseal

I haven't touched the usage of publicAPI because I didn't think it was worth updating the old stuff.