[BUG] corner radius isnt rendering on skia svg's

Description
corner radius isnt rendering on skia svg's
Expected Behavior
corner radius is rendering
Actual Behavior
corner radius isnt rendering
Basic Information

Version with issue:  2.88.1
Last known good version:  not known
IDE:  Visual Studio for Mac
Platform Target Frameworks:

Android: 12.1
iOS:  15

This renders correct

This does not render correct

Svg.Skia is a separate project so closing this one so they can track it there.

@mattleibow does Skia.Svg library has still a more complete implementation of Svg document model then SkiaSharp.Extended.Svg?
The issue is also reproduced with SkiaSharp.Extended. Should i open the issue there also instead of here?

Far more complete. Also, the SkiaSharp.Extended.Svg has been abandoned in favour of Svg.Skia for just this reason.

Tks for the quick feedback @mattleibow


Add Mercari to the company list

Dear Airflow maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA
No JIRA ticket related to this PR.
Description
Add Mercari to the company list
Tests
We don't need any test for this PR.

Codecov Report

Merging #2424 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2424   +/-   ##
=======================================
  Coverage   69.24%   69.24%
=======================================
  Files         146      146
  Lines       11230    11230
=======================================
  Hits         7776     7776
  Misses       3454     3454

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 0fc4504...1948a0c. Read the comment docs.

@skudriashev  can you tell me how to execute the travis CI again without commiting anything new.

Please use the alphabetical order. Thanks!

@yu-iskw you can close and reopen PR to restart tests.

@yu-iskw but I think this is not required since you change only README.

@bolkedebruin  Thank you for the feedback! I have modified it.

@skudriashev Thank you for the advice.


Add Ability to Upload Torrents Directly to Google Drive And One Drive

Lets Take It To Next Level

https://sites.google.com/site/gdocs2direct/

Websites like that, can do the trick.

i mean to add backend support

some websites i used in an old Research i did that might be very useful for you
Remote Upload
go4up.com
http://urltocloud.nsspot.net/
https://thoaimedia.com/save/
http://ctrlq.org/save/
https://leech.thoaimedia.com/
http://www.autogeneratelink.com/
http://youtubemultidownloader.com/index.html


Native context menu does not support AnchorAxisAlignment (fix #157881)

Unfortunately this seems to look not ideal on Linux with native menu enabled:

Imho still better than this though:

Pushed a somewhat ugly hack in https://github.com/microsoft/vscode/pull/157882/commits/25521d0b27ff44e41f8d529a6acc84028452ea53 to fix that behaviour, because it also impacts Windows when custom title bar is turned off. The strategy is to offset the position of the menu by the height of the anchor when we think the menu cannot open to the bottom but will open to the top.


Inaccurate Pose/TF Calculation

While converting my system to ROS2 I was glad to find this port, thanks.
However, I noticed that the pose/TF accuracy is not as good as in ROS1. After digging into the code, I saw that a different approach is used here to calculate the pose from the detections. I have tried the solution with pnp-solver (as in the ROS1) and the suggested library function (https://github.com/AprilRobotics/apriltag/wiki/AprilTag-User-Guide#pose-estimation). Both perform much better for my task. See small example (moving the camera on a smooth path).
I am curious if anyone else has experienced this issue, and if there is a particular reason for using the current method?

The issue was already reported by @MihailV1989 in https://github.com/christianrauch/apriltag_ros/issues/11#issuecomment-1310957374, which also compared the current initial implementation with the one from the apriltag library.
Thanks for doing these comparisons (to both of you). But I am not sure how to read your plot. Are you plotting the (x,y)-position of the marker in some frame over time? What about the z-coordinate and rotation? Do you know what the true tag pose is?
If you put a PR together and show that the new implementation is better than the old one, e.g. by comparison with the depth of an RGB-D camera or my ground-truth measurement, then I will be happy to review and likely merge it. I would also be interested in the runtime comparison between both implementations, as you may want to give the user the choice between throughput and accuracy. I think @MihailV1989 already wanted to submit a PR. I am not sure what the status of this is. Maybe you can work on this together?

The issue was already reported by @MihailV1989 in #11 (comment), which also compared the current initial implementation with the one from the apriltag library.

Aha thanks, that is the same problem I have. I have not noticed that because of the mixed topics/title.

Thanks for doing these comparisons (to both of you). But I am not sure how to read your plot. Are you plotting the (x,y)-position of the marker in some frame over time? What about the z-coordinate and rotation? Do you know what the true tag pose is?

Sorry my plot is not ideal / not well explained. Yes, it is the x and y Position in the camera Frame over time. I omitted Z and the rotation for simpler plot (my application is basically 2D, I have a top view camera over a flat ground).
Providing a ground-truth is not so easy, I'll have to think again. Which ground-truth measurement do you use/suggest?

If you put a PR together and show that the new implementation is better than the old one, e.g. by comparison with the depth of an RGB-D camera or my ground-truth measurement, then I will be happy to review and likely merge it. I would also be interested in the runtime comparison between both implementations, as you may want to give the user the choice between throughput and accuracy. I think @MihailV1989 already wanted to submit a PR. I am not sure what the status of this is. Maybe you can work on this together?

Yes, I guess the speed is lower. But I have not measured this yet. May I can do this later.

Which ground-truth measurement do you use/suggest?

I think the simplest is to just keep the camera pose fixed and move the tag around on a table and measure its relative displacement in x and y and the rotation. E.g. move it by 5cm and then check if the pose changes by 5cm. Keep in mind that the origin of those poses is the optical frame. It will therefore be easier if you move the tag axes-parallel to the image plane.

I started looking into this myself and implemented now all three methods using the same interface for comparison. @a-uhlig Could you share your log file (rosbag) to reproduce your results?

I had created my example with a simulation but only recorded the final results.

Great. That means we can compare the results with the ground truth. We could also use the log file for CI to make sure the performance does not degrade.
I started work on this on the pose branch: https://github.com/christianrauch/apriltag_ros/tree/pose
The node now has a parameter pose_method that can be set to either of these:

from_homography (current implementation)
apriltag_orthogonal_iteration (using estimate_tag_pose from apriltag library)
apriltag_homography (using estimate_pose_for_tag_homography from apriltag library)
solve_pnp (using OpenCV's solvePnP as used by the ROS 1 node)

I would be interested in the comparison of estimation performance vs. runtime. If there is a clear winner (best performance and lowest runtime), I would simply use this as the estimation method. If there is a trade-off between some of the implementations, I would keep the method configurable.

Hi Christian,
I am interested in testing your pose branch, can you provide any more info on its use? Is it functional at the moment?
Do you know anything about how https://github.com/NVIDIA-ISAAC-ROS/isaac_ros_apriltag determine the orientation?
The orientation from isaac_ros_apriltag I have found to be good. however, its april tag identification is much worse.

I am interested in testing your pose branch, can you provide any more info on its use?

It's described in the comment above yours (https://github.com/christianrauch/apriltag_ros/issues/14#issuecomment-1548265708): You use it as described in the repo's readme file, after checking out the pose branch. You have to set the ROS parameter pose_method to one of the 4 options I listed above.

What is the current status for pose accuracy, is it fixed?

What is the current status for pose accuracy, is it fixed?

Can you specify which problem you have? Did you try any of the alternative methods from the pose branch? Do they fix the problem for you?

I am having accuracy problem in current implementation detection. Offset in 5cm and it's getting scale up when the tag is getting away.
yes i tried alternative methods but the detection TF is going somewhere far away from actual position or going into the ground.
no those weren't fixed my problem.

I am having accuracy problem in current implementation detection. Offset in 5cm and it's getting scale up when the tag is in long range (as range increase, offset increasing).

Can you provide details on how you compare and get to this error value?

yes i tried alternative methods but the detection TF is going somewhere far away from actual position or going into the ground.

The original issue comment at the top is about comparing the pose estimation of the current implementation (setting pose_method to from_homography) with the one used in the apriltag library (function estimate_tag_pose) that can be used by setting pose_method to apriltag_orthogonal_iteration. If neither of the 4 options improves your results, then I am not sure what we are supposed to do.
What results do you get when using the apriltag library (https://github.com/AprilRobotics/apriltag) without the ROS node?

I'll check with the library alone without ROS node and let you know. Thanks for the update.

Did any of you manage to test the different pose estimation methods on the pose branch and can report some results? Could you also share log files with sequences where you experienced the issues?

Hey @christianrauch,
we still have to migrate our apriltag workflow to ROS2. We greatly appreciate the effort you put into this package. We can't promise anything yet, but if we can manage to spend some time on it, we might collect some data with our gantry system for the different methods you have made available in the pose branch.
That is, if no one else has done this already and is willing to share the results?

Evaluation Setup
I have collected some data using a ignition gazebo simulation depicted below.

The robot has as downward looking camera and the model was declared static to keep it in a defined position during data collection.
An example image of the images capture by the camera is shown below.

instead of moving the camera/robot or an apriltag around, multiple tags in the same image are considered. This way, the result for multiple different tag position can be evaluated for a single image.
The camera is configured without distortion. Hence, the image can be considered as perfectly rectified and no errors due to distortion/rectification effects are induced.
The true tag poses and the pose of the camera are known. Thus, the pose estimations published under the /tf topic can be compared to the ground truth data. The position error is defined as the euclidean distance between the estimated tag position and the true tag position. The angle error is defined as the angle between the true tag's normal vector and the estimated normal vector computed by the apriltag node.
Zero mean gaussian noise with a std deviance of 0.1 was added to the camera.
The experiments were conducted with three different orthogonal distances to the tags: 0.5m, 1.0m and 1.5m.
This way the four pose estimation methods for different pixel sizes in the image can be compared.
The edge length of the tags is 0.075m.
The computation time was measured by calling std::chrono::high_resolution_clock::now() before and after calling the pose estimation function.
For each orthogonal distance to the tags 1000 pose estimation have been evaluated.

Name
Function/Parameter

Method A
"from_homography"

Method B
"apriltag_homography"

Method C
"apriltag_orthogonal_iteration"

Method D
"solve_pnp"

Angle Error Plot
Note the different x-axis scale for each row! We observe similar performance for Method A and Method B. This is most likely explained by the fact that both methods implement the pose estimation via homography and should perform identical in general.
For the larger camera-to-tag-distance in the second and third row, Method C and Method D show superior results. For the orthogonal camera-to-tag distance of 1.5m in the third row, the mean angle error of Method D is only half of Method C's mean angle error.
Performance wise, the methods can be ranked as follows:
D > C > B = A

Position Error Plot
Again, note the differnce in the x-axis scale between the different rows.
For the position error, to put it in a nutshell, C and D perform quite similar and seem to deliver the best results. Method A and B are not quite on par regarding the position error.
The ranking:
D = C > B > A

Computation Time Plot
Everything comes at a cost. The costs regarding the computation times are depicted in the image below. There are quite substiantial differences between the methods.
By far the fasted method is B, followed by A with an average computation time of two times that of B. The computation time for D is roughly four times higher than of B and by far the slowest is C.
The ranking:
B > A > D > C

Conclusion
Method C and D seem to give more precise results but require more computation time. Since C gives better or equally good results as C while having substantially lower computation times, Method D seems to be superior to Method C.
The same can be said for Method A and B. Method B seems to give equally accurate or better results regarding the pose estimation while having lower computation costs. Hence, B seems to be superior to A.
Note that the presented simulation setup used for the evaluation might differ severely from real world examples.  Method A and B are fairly quick, while C and D seem to be more accurate.
I personally prefer Method D, since accuracy is more important than computation time for my application. Besides, I assume the apriltag detection algorithm requires the heavy lifting in contrast to the pose estimation.
I would like to see Method D (solve_pnp) merged into the main branch.
Since Method A and B are part of the apriltag library: what would be a reason against having the pose estimation method configurable via a parameter as in the pose branch?
If it is desired, that the apriltag node implementation stays rather lean, I would tend to have at least Method B and D available. This would align with the suggestion of @christianrauch in https://github.com/christianrauch/apriltag_ros/issues/14#issuecomment-1548265708

@lennartalff Thanks a lot for this evaluation. Regarding the plots, I see that the x-axis is the quantity you measure, but how should I interpret the y-axis? Is this a histogram over the all tags in the image? This doesn't seem to be normalised but the "count" values also seem quite high for the approx. 91 tags in the image.
When you say

Since C gives better or equally good results as C while having substantially lower computation times

Do you mean "Since D gives better ..."?
Since there is no clear winner that performs best in accuracy and runtime, it definitely makes sense to have this as an option. From the averages of the graphs above, I would also conclude that B (apriltag_homography, i.e. AprilTag's estimate_pose_for_tag_homography) and D (solve_pnp, i.e. OpenCV's solvePnP) would be good options, with D as the default.
In fact, solvePnP is the same method used by the original ROS 1 version of apriltag_ros. However, solvePnP itself again has a lot of options (estimation method) and variants (such as cv::solvePnPRansac()) that will have an effect on the runtime and accuracy.

I updated my text introducing the histogram plots to avoid misunderstandings and also corrected the C/D typo.

For each orthogonal distance to the tags, N=1000 pose estimation have been evaluated. Since there are not 1000 tags visible in a single image, the simulated camera stream is evaluated until the total count of detections equals the desired number of pose estimations. Note that the relative pose between tags and camera stays the same over the series of evaluated camera images. The only difference between successive images is the gaussian noise applied to the simulated camera. Hence, the 'robustness' against noise will be reflected in the results.

The results are displayed as histograms. The respective x-axis displays the evaluated quantity (angle error, position error, computation time). Each y-axis represents how often (in absolute terms, with a sum of N=1000) the measured quantity occured in the results.

In https://github.com/christianrauch/apriltag_ros/issues/21#issuecomment-1817918398 you considered splitting up the detection and the pose estimation part in two separate components. I think that this is quite an attractive option. The apriltag node's main taks is to use the apriltag library, detect the corner points and publish a corresponding ROS message.
The secondary task of estimating the pose is not as straight forward to implement, as there is a plethora of approaches/algorithms/tuning knobs to accomplish this task. Still I guess, that most people will consider pose estimation useful/required for their applications. Therefore, I would suggest to implement a reference node component providing Method B and Method D. If more control or other algorithms are required by users, they could replace the pose estimation component by their own implementation. This way "power users" are not limited by the methods implemented in this package. For all other users the combination of the apriltag detection component and the  pose estimation component provides a "batteries included" setup to get started with a fully functional pose estimation pipeline right away.
Let me know what you think about this. I would be happy to provide a PR If you think that it makes sense to adopt some of my suggestions.
P.S.: What is the reasoning behind the rotation of the apriltag's coordinate system by 180° around the x-axis? To me it was quite counter intuative to not use the coordinate system as defined in the apriltag library

@lennartalff I reduced the options in the original branch and created a PR for it: https://github.com/christianrauch/apriltag_ros/pull/24. As discussed, there are now only two options for the parameter pose_estimation_method: pnp and homography. Thanks again for your evaluation.
@MihailV1989, @a-uhlig, @TomGrimwood, @KatoROSTeam, @lennartalff Can you test if the PR with the default pnp option improves the pose estimation accuracy for you and report back?

The apriltag node's main taks is to use the apriltag library, detect the corner points and publish a corresponding ROS message.

I would say the apriltag library's main function is to estimate the pose of AprilTags.

Therefore, I would suggest to implement a reference node component providing Method B and Method D. If more control or other algorithms are required by users, they could replace the pose estimation component by their own implementation.

You can already do that. The raw detections are published in any case and you can subscribe to them and the camera intrinsics to use an alternative method for pose estimation.
I think splitting the tag detection and pose estimation functionality into two separate nodes creates too much overhead. Both functionalities only take a couple of lines of code. If you look at the current implementation of the node, you will see that there is more code related to the framework (topics, callbacks, parameters, ...) than the actual tag detection and pose estimation functionality. The node is merely a wrapper around those libraries. Further separating the calls to library functions into nodes will further increase the overhead in maintaining the code. And even if the nodes are implemented as composable nodes, you will have runtime overhead and the overhead of managing two nodes instead of one in launch files etc. I guess that there are more people interested in extracting the pose of a tag than just the tag corners. At the moment you can access both from this single node without the hassle of managing two composable nodes. Did you envision that a dedicated "pose estimation from tag detection" node would be used independently of the tag detection? What would the interface look like? And why would this be easier (and more efficient) than just using OpenCV's cv::solvePnP, or your method of choice, directly via an API?
Overall I think that there are not many use cases for a dedicated "pose estimation from tag detection" node and that such a node would just create overhead to merit this split.

What is the reasoning behind the rotation of the apriltag's coordinate system by 180° around the x-axis? To me it was quite counter intuative to not use the coordinate system as defined in the apriltag library

If I am not mistaken, this is done in the pose estimation methods in the apriltag library function estimate_pose_for_tag_homography and in the ROS 1 node. In estimate_pose_for_tag_homography, a transformation fix is applied to the originally estimated pose M_H. The initial_pose coordinate frame's z-axis should point away from the front side of the tag. In the ROS 1 node with cv::solvePnP, the orientation of the coordinate frame is defined by the coordinates of the "object points" and their correspondence to the 2D coordinates on the unit tag frame with the counterclockwise order.
IMHO, this is more intuitive as tags are mostly attached to the surface of an object, with the z-axis pointing away from this object, just like the world frame on a ground plane.


Cannot find the neccesary img files

Hey hey @istadem2077
We noticed that the link to the latest archive in the README leads to 404 github page. We tried to take another archive from 24 release but couldn't find recovery.img and system.img in there that are neccesary to install ubunto according to the Install section in the README
https://github.com/ubports-dipper/xiaomi-dipper/releases/tag/v24
Could you please point me out to some release with zip file where all of these .img files are available
Thanks in advance

Hey hey @istadem2077
We noticed that the link to the latest archive in the README leads to 404 github page. We tried to take another archive from 24 release but couldn't find recovery.img and system.img in there that are neccesary to install ubunto according to the Install section in the README
https://github.com/ubports-dipper/xiaomi-dipper/releases/tag/v24
Could you please point me out to some release with zip file where all of these .img files are available
Thanks in advance

Hi, .img files mentioned in README no longer exist. You gotta install the zip files through TWRP, and then install boot.img from here.
My boot images appear to be broken. I no longer have the phone, so I can't really support it anymore unfortunately.


Feature/add hosts

Solution for issue https://github.com/portainer/portainer/issues/556
Included a button similar to add environment variables.

Hi,
@deviantony Thanks for the info. I've rebased the code also, unfortunately I did a mistake while rebasing so I had to reset things and start again, hope it didn't mess with the rest of changes since my first commit. If that's the case I can reopen this PR.

Hi @resilva87, yes the PR is in bad state. Could you re-open a new one?

@deviantony Yeah, sorry about that. Reopened as https://github.com/portainer/portainer/pull/604.
Tks


use a custom directive for admin ui tabs icon

... instead of a hack :-)

not relevant anymore after libs update.


Enhancement: Dev-8931 Hide Markup Include on null values

Enhancement: Dev-8931 Hide Markup Include on null values
https://websupport.cdc.gov/projects/DEV/issues/DEV-8931
Added ability to display/hide markup include depending on if there are values with null values.
Testing Steps
Testing Instructions
Scenario: Upload dev-8931-hide-markup-include.json, Click on Dashboard Preview
Expected: There is a Dashboard Filter and a Markup Include with text

Choose Normal Weight from the dropdown.
Expected: Markup Include is shown with no value next to Percentage(s).

Choose Not Checked in past 5 Years
Expected: Markup Include is shown with no value next to Class(es).

Click Dashboard Description

Click the tools icon on the Markup Include

Open Content Editor

Click the checkbox next to Hide section on null

Open Dashboard Preview

Expected: When Normal Weight or Not Checked in past 5 years is chosen, there shouldn't be any Markup Include showing. If you choose any other option that has values for both variables then the Markup Include will show.
Self Review

I have added testing steps for reviewers
My changes generate no new warnings

Additional Notes
In the EditorPanel.tsx file, the only changes I made are on Line 26 and 199-221. The rest of the changes are linter changes.

I also changed the code that was adding commas to the variable. The old code was only displaying one value that had the comma and not the whole array. This allowed me to remove the let variable, too.


UIMA SimpleServer is not compatible with the latest Ruta feature (relation annotation)

Describe the bug
SimpleServer does not recognize relation annotation as mentioned in Apache UIMA Ruta™ Guide and Reference. It will throw error when recognizing any such annotation.
HTTP Status 500 - XML output failed
type Exception report
message XML output failed
description The server encountered an internal error that prevented it from fulfilling this request.
exception
java.lang.RuntimeException: XML output failed
	org.apache.uima.simpleserver.output.ResultConverter.getXMLString(ResultConverter.java:88)
	org.apache.uima.simpleserver.servlet.SimpleServerServlet.transformResult(SimpleServerServlet.java:296)
	org.apache.uima.simpleserver.servlet.SimpleServerServlet.analyze(SimpleServerServlet.java:213)
	org.apache.uima.simpleserver.servlet.SimpleServerServlet.doPost(SimpleServerServlet.java:190)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:643)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:723)
root cause
java.lang.NullPointerException: Cannot invoke "org.apache.uima.simpleserver.output.Result.getResultEntries()" because "result" is null
	org.apache.uima.simpleserver.output.ResultConverter.getXMLString(ResultConverter.java:60)
	org.apache.uima.simpleserver.servlet.SimpleServerServlet.transformResult(SimpleServerServlet.java:296)
	org.apache.uima.simpleserver.servlet.SimpleServerServlet.analyze(SimpleServerServlet.java:213)
	org.apache.uima.simpleserver.servlet.SimpleServerServlet.doPost(SimpleServerServlet.java:190)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:643)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:723)

To Reproduce
Steps to reproduce the behavior:

Clone the repo https://e.coding.net/cvd-bioinformatics/transdifferentiation/reprogramming-uima-tomcat.git in Eclipse
In Eclipse, right click on pom.xml > Run as > maven install (Make sure you have installed M2Eclipse)
Right click on the project root, Run As > Run on Server (Make sure you have installed Eclipse Java EE Developer Tools,Eclipse Java Web Developer Tools,Eclipse Web Developer Tools,Eclipse XML Editors and Tools,JST Server Adapters Extensions and JST Server Adapters Extensions (Apache Tomcat), configured at least one available Tomcat server in Eclipse and add the server runtime into the project classpath.)
In the browser, visit http://localhost:8080/UIMADemo/?mode=form and enter Neurog2 is downstream of Pax6. Click "Submit Query".

Expected behavior
The server should return an xml response about the text analysis result instead of error messages.
Please complete the following information:
Versions:

OS: Windows 10 Professional (version: 21H2)
Eclipse: 2022-06 (4.24.0) (Build id: 20220609-1112)
Java: Eclipse Adoptium jdk-<IP_ADDRESS>-hotspot
Maven: Eclipse Embedded 3.8.4/<IP_ADDRESS>20227-1319
Apache Tomcat: 6.0.37
org.apache.uima.uimaj-core: 3.3.1
org.apache.uima.SimpleServer: 2.3.1

@reckart The issue is the replicate of that on UIMA Jira.

Thanks. Unfortunately, it appears that the simple server is swallowing the root exception. In the debugger, I can unearth it:
java.lang.IllegalArgumentException: Not able to resolve type: Sentence in script SoMeRutaPear

Indeed, I do not find a type ...Sentence in the type system that is contained in the PEAR.
Note that I had to install a Tomcat 9 to test this. When trying with Tomcat 10, I got a different set of exceptions indicating that the simple server is not compatible with the Servlet API version of Tomcat 10.

Thanks. Unfortunately, it appears that the simple server is swallowing the root exception. In the debugger, I can unearth it:
java.lang.IllegalArgumentException: Not able to resolve type: Sentence in script SoMeRutaPear

Indeed, I do not find a type ...Sentence in the type system that is contained in the PEAR.
Note that I had to install a Tomcat 9 to test this. When trying with Tomcat 10, I got a different set of exceptions indicating that the simple server is not compatible with the Servlet API version of Tomcat 10.

@reckart Yeah, you are right! My negligence caused this error! After deleting the undefined Sentence, the server works fine now! You are so helpful! Thank you!


Upgrade to InfluxDB OSS v2.0.rc0 URL 404

Upgrade to InfluxDB OSS v2.0.rc0 URL 404
Relevant URLs
Upgrade to InfluxDB OSS v2.0.rc0
https://docs.influxdata.com/influxdb/v2.0/reference/rc0-upgrade-guide/
What products and version are you using?

Thank you, @danielwilson654!


Bugs on tapered eval inside the BoardEvaluator

There is some strange behavior around the interpolation function, we should at least fix it and possibly refine the formula

@pietraldo we need a fast fix

on it

but first i have to somehow compile it


change management port to 7626

see https://github.com/apache/incubator-pekko-management/issues/49

@pjfanning Did you randomly pick the 6262 port or was it agreed upon somewhere?

@pjfanning Did you randomly pick the 6262 port or was it agreed upon somewhere?

I made one up myself - 6262 in based on 'MANA' on a telephone keypad.

I made one up myself - 6262 in based on 'MANA' on a telephone keypad.

How about 6468 which is based on MGMT (i.e. management)? According to https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers its also free

Both 6262 and 6468 are clashes (Sybase and Discord, respectively)
I changed to 6458 inadvertently, I will choose another value though.

@mdedetrich how about 7626 for PMAN (Pekko MANagement)?

I have an affinity for MGMT because of the music band but I am also happy with PMAN, in either case PR looks good.
You can ask some others if they have any preference but we shouldn't bike shed over this

@nvollmar @He-Pin @mdedetrich @jrudolph is this port ok?

It's hard for me to choose a port, so leave to others, the overall pr looking good.

5885 might be a good choice

I nominate 6666. In Chinese, this number has a metaphor of smooth sailing and awesomeness.

I nominate 6666. In Chinese, this number has a metaphor of smooth sailing and awesomeness.

This is problematic. Christians associate 666 with the devil. I don't think we can pick port numbers based on cultural terms, it's safer to avoid numbers that can be offensive to oversensitive people.


Make const_reference_proxy assignable to reference_proxy

const_reference_proxy should also be constructible from reference_proxy.

@JohanMabille https://github.com/man-group/sparrow/pull/132

@JohanMabille  do we need constructible  just assignable?

const_reference_proxy should also be constructible from reference_proxy.

do you mean the other way round or really this way?

This is not needed anymore thanks to #135 and #136


Create a Quickstart guide Template and Quickstart Section for the Safe Core SDK

This PR introduces a standard template that all quickstart docs should follow as part of the Developer Docs Status Update: 2023-02-22.
The previous commits and comments for this PR can be found at #163.
The goal of each quickstart is to provide the "minimum viable code" that a developer needs to complete a task using a given package or library. Any additional functionality can go into a separate "Detailed Guide" doc as seen in this example: Guide: Integrating the Safe Core SDK.
This quickstart shows the "minimum viable code" needed to create a Safe and propose and execute a multi-sig transaction using the Safe Core SDK.
Each quick start guide should include the following:

[ ] About the tool:

[ ] This tool allows you to... Some examples of things you can do with this tool include...

[ ] Quicsktart

[ ]  This quickstart will show you how to...

[ ] Prerequisites:

[ ] what to install, existing accounts, ETH/tokens required to complete this, any API keys required, etc.

[ ] Copy-paste code snippets to complete the task
[ ] Make example compatible for running in Goerli testnet

Style Guide

Put code snippets inside triple backticks instead of single backticks to enable the copy-paste button
Include the language in your code snippets so that syntax highlighting is enabled

Project Management

Closes #164
This PR is step 2 of the Documentation Revamp.
See Step 1 Changes.

I've addressed @germartinez comments:

https://github.com/safe-global/safe-docs/pull/163#pullrequestreview-1310991767
https://github.com/safe-global/safe-docs/pull/163#issuecomment-1441659112

In commits from https://github.com/safe-global/safe-docs/pull/165/commits/f62e57dadd9a6b05d20350e71e15257f55c1da2f to https://github.com/safe-global/safe-docs/pull/165/commits/e0a7ae375281d26dc16cfbede7af42952f281014

Ran the script and confirmed it's working:

[Before Transaction] Treasury Balance: 0.1 ETH
Transaction executed:
https://goerli.etherscan.io/tx/0x47a5a2923ba771347b8343b1093e11833e9a0727b9f9fb1c7526c9ef2b7fe081
[After Transaction] Treasury Balance: 0.05 ETH

I'm approving this PR, but please check the last suggestions I left before merging :wink:


Configure extensions from server CLI.

This idea was raised in jupyterlab/jupyterlab#6451.
Problem: the classic notebook can configure both the server and the frontend from the CLI. This is helpful for scenarios where you are deploying jupyter servers from scripts. JupyterHub, for example, launches single-user server using the CLI entry points. Those running notebook or lab as server extensions cannot configure those frontends from the jupyter server CLI.
Soluton: I propose we add functionality to Jupyter Server that enables the jupyter server CLI to configure extensions (assuming they are configurable objects). This would require ServerApp to look for enabled, configurable extensions and dynamically add those classes to the ServerApp's classes trait.

Could you describe what is the user/consumer experience here? I believe @kevin-bates and I were talking about similar scenario for integrating EG on JupyterServer Phase 2.

For example, passing a spawner argument for JupyterLab in a JupyterHub deployment.  (E.g. static_url if using a cdn).

cf https://jupyterhub.readthedocs.io/en/stable/getting-started/spawners-basics.html

cc @ian-r-rose

For example, imagine a user launches a jupyter_server with notebook and jupyterlab extensions enabled. They could configure those extensions from the CLI using:
jupyter server \
    --ServerApp.default_url='/lab' \
    --NotebookApp.enable_mathjax=False \
    --LabApp.workspaces_dir='/path/to/workspaces'

Any extension that's configurable and enabled could be configured from the CLI.

For example, imagine a user launches a jupyter_server with notebook and jupyterlab extensions enabled. They could configure those extensions from the CLI using:
jupyter server \
    --ServerApp.default_url='/lab' \
    --NotebookApp.enable_mathjax=False \
    --LabApp.workspaces_dir='/path/to/workspaces'

Any extension that's configurable and enabled could be configured from the CLI.

This works in #180. All CLI arguments are parsed by the ServerApp and stored in a general traitlets Config object. For example, the above command will create a config object that looks like:
Config({
    "ServerApp": {
        "default_url": "/lab"
    },
    "NotebookApp: {
        "enable_mathjax: False
    },
    "LabApp": {
        "workspaces_dir": "/path/to/workspace"
    }
})

This object is then passed to and shared by all the extensions. Each extension will update it's config with the piece that's relevant to its config.

This is added in #180 and documented here.


Changes to the paper

This is part of review at https://github.com/openjournals/joss-reviews/issues/6953
Some small change recommendations to the paper:

[x] - authors: please add ORCids
[x] - line 11: could be strengthened with a citation
[x] - line 15-16: please add citations/links for NGSI-v2, Orion Content Broker, QuantumLeap
[x] - table 1: could be nice to have the name of the library along with citation
[x] - line 48: 'does not' -> 'do not'
[x] - line 50: 'continue to' -> 'continues to'
[x] - line 75: is _ needed in conversion factor?
[x] - line 118: Is PID mentioned before? please check
[x] - line 148: missing year in reference
[x] - line 169: journal abbreviation, some our full names. Please choose one for consistency.

Thanks a lot for your efforts!

Merged into JOSS_submission


Add possibility to assign Rules and ManagedruleGroups to (preProcessRuleGroups and postProcessRuleGroups)

{
  "PreProcessRuleGroups": {
    "Custom": [

    ],
   "Managed":  [

   ]
  },
  "PostProcessRuleGroups": {
    "Custom": [

    ],
   "Managed":  [

   ]
  }
}

Done in https://github.com/globaldatanet/aws-firewall-factory/tree/v2.0.0


Scala hello world.

Your pull request needs further work because of the following reason(s):

Your file is not in a project folder ("Friends", "Games", "BSoD"). This may be intentional, but most likely not. If it is intentional please tag a maintainer.

Once you have resolved the issues, comment on this request to be re-judged
This is an automated response, beep boop.
if you think there is a mistake, contact a maintainer

5c8618878e24f7f9439787363a0fbd6480d05969

You are not following the exact template.
Your final result to STDOUT&STDERR should be
Enter your name :
Hello {name}!

Ok, I think is done.
Sorry dude.

Your pull request needs further work because of the following reason(s):

Your file is not in a project folder ("Friends", "Games", "BSoD"). This may be intentional, but most likely not. If it is intentional please tag a maintainer.

Once you have resolved the issues, comment on this request to be re-judged
This is an automated response, beep boop.
if you think there is a mistake, contact a maintainer

2c482a9a2d3158d9e12b8d9d0b5df7c1143e66c7

Hello {name}!. Not Hello{name}!.

Ok, I think is done (almost sure)
Sorry dude.

Your pull request needs further work because of the following reason(s):

Your file is not in a project folder ("Friends", "Games", "BSoD"). This may be intentional, but most likely not. If it is intentional please tag a maintainer.

Once you have resolved the issues, comment on this request to be re-judged
This is an automated response, beep boop.
if you think there is a mistake, contact a maintainer

ce34fee1d8059614f2002ea0a994ff670f8416bb

This PR has been idle for more than 24 hours, and will now be closed. Feel free to re-open.
This is an automated response, beep boop.
if you think there is a mistake, contact a maintainer

ce34fee1d8059614f2002ea0a994ff670f8416bb

Your pull request seems good, but must be checked by a human maintainer for the following reason(s):

An error occured while marking your code. The error should be addressed by a maintainer eventually The error is: That language is not supported!.
These submissions must be checked manually because of the potential complexity of submissions, if you've reached this point in the process you're most likely a valid submission.

Please be patient until a maintainer has time to look over your contribution.
This is an automated response, beep boop.
if you think there is a mistake, contact a maintainer

ce34fee1d8059614f2002ea0a994ff670f8416bb


(Mac OSX) Unable to transfer a folder of files to KBFS

Copied a directory of photos and videos to /keybase/private/masterroot24 and got a few files transferred, then lots of errors like:

cp: failed to close '/keybase/private/masterroot24/filename.txt': Input/output error

The directory has a total size of 27mb and each file is no bigger than 10mb.
my log id: 1376c7369d000e81e233511c

Thanks for the report.  It looks to me like it took a long time to upload data over your internet connection -- nearly a minute to upload a ~5MB file.  Previous uploads didn't take this long, so maybe it was a temporary fluctuation in your network?  Does this sound possible?  Sorry for the inconvenience, we're currently working on background uploads that won't result in user-visible timeout errors like this.

No worries, thanks for the prompt reply!
That may well have been the case. I don't have a super fast connection, so it's possible it just timed out. I'll try the same operation again on a faster connection and report back here.

Just tried this same upload again on a faster connection and it completed ok.
I still expect to be able to perform this operation on the internet connection I was using yesterday (~7mbps). Therefore, I still feel there's an issue here, so I'm looking forward to seeing the improvements that you're making to background uploads 👍


Decrease ps write latency

What problem does this PR solve?
Issue Number: ref #6827
Problem Summary: We need to decrease ps write latency.
What is changed and how it works?
Make apply to PageDirectory a pipeline so that we can batch the incoming edit when doing IO.
Before optimization

After optimization

The 99-latency decrease from 40ms to 12ms.
Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/run-all-tests

/hold

The code for handling exception is not ready.

/rebuild

/run-all-tests

/unhold

@flowbehappy @CalvinNeo @JaySon-Huang Add some new code for handling exception, PTAL again

/run-all-tests

/merge

/run-unit-test

/run-cherry-picker


Update README

I've added :

contributors and downloads counters
Summary
Debugging section if people wants to see logs

How does the download counter work?
It shows 136 downloads for me, but Home Assistant analytics shows already 366 installations (and lots of people don't have analytics enabled).
So the number seems kind of random, I would like to understand what it is showing. Is it "forever" downloads? Or like last month? Or per version? If the number does not make sense I would prefer not to include it.
The other changes are fine 👍

/total.svg represent the total of all downloads
If you want specific version, you can edit the link and add v1.21.1 just before /total.svg
it will be something like that : https://img.shields.io/github/downloads/mvdwetering/huesyncbox/v1.21.1/total.svg
Or if you want always the latest version : https://img.shields.io/github/downloads/mvdwetering/huesyncbox/latest/total.svg
But I can remove it if you want :)

Lets leave the downloads out as it does not seem to represent the usage and not really sure why it would be useful otherwise.

All checks are ok, and I've removed the downloads line !


Adding extension for using gl_BaseInstance

Adding the extension is not required. We are using vulkan 1.1 on the code, and in that version that extension is built-in and no longer really an extension. Still, might be a good idea to add the feature flag for it.

Ok, I got it. ☺


Replacement Occurs in strings

Example
Put "Say a" into p
becomes
P = "print(a")

I'm pretty sure this was recently fixed in 1.3.2 (see dac88d17eb65ff9b648c81b49980c28fb57b745c), could you try and reproduce this after updating?
pip install rockstar-py --upgrade

It was fixed :)


Create config console man page

The configuration console has a placeholder man page at snapshinazfs-config-console(8).
This should be fleshed out at some point.

This is completed and is in RC1.


Noted the name change on config.origin

This was formerly config.origin and was updated to config.origins so I wanted to point that out

Fixed with 421a454


Just get global changes

#562
I seriously don't know why this won't auto-merge. Maybe it's because I reverted a change for this commit

:+1:


Configs

[ ] Define configs folder.
[ ] Define a global configs variable.
[ ] Store all the variables auto-exported from the configs folder.

Config folder can have a development port in a start config file.
Like:
const Config = {
   development: {
      port: 3000,
   },
}

export default Config;


Fix the time pointer bug, #63.

OMG, so much time I spent on it. Now it could be considered sloved.
Fix #63.

Now it is marked as solved, but I don't know it's me or it really has a small delay after triggering the pause event. I couldn't compare it with Audacity app because its timeline display style felt laggy and just don't know if my program still has the bug. But I think the overall performance is acceptable.


FE: Adjust button states w/ r/o mode

There is a cluster read-only mode. Not all the altering actions on the frontend are unavailable when a cluster is r/o.
Fix this, perhaps add a check on button/other component level.
Related:

https://github.com/provectus/kafka-ui/issues/4374

Hi! I'd like to try this one out.

Is this what you had in mind? I mean, all the edits are disabled in ro mode.

Is this what you had in mind? I mean, all the edits are disabled in ro mode.

Yeah, but across the whole app :)


[Break Change] Remove endpoint name in the trace query condition.

[ ] If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #.
[x] Update the CHANGES log.

Hello developer,
when I use skywalking, I added the search term endpointName to the page named “trace”. Then I found that skywalking used to have this function, and it was removed in this version. I would take the liberty to ask, is it because there is a major bug or is it better to deal with it? Because I think searching by endpointName on the page is a good function.

Hello developer,
when I use skywalking, I added the search term endpointName to the page named “trace”. Then I found that skywalking used to have this function, and it was removed in this version. I would take the liberty to ask, is it because there is a major bug or is it better to deal with it? Because I think searching by endpointName on the page is a good function.

Read the discussion page, it is there.

Hello developer,
when I use skywalking, I added the search term endpointName to the page named “trace”. Then I found that skywalking used to have this function, and it was removed in this version. I would take the liberty to ask, is it because there is a major bug or is it better to deal with it? Because I think searching by endpointName on the page is a good function.

Read the discussion page, it is there.

I found it! thanks for your reply.


proto/generic/cast.go: let Value struct func  support Enum…

A new optimization
What type of PR is this?
optimize: A new optimization
Check the PR title.

[x] This PR title match the format: (optional scope):
[x] The description of this PR title is user-oriented and clear enough for others to understand.
[x] Attach the PR updating the user documentation if the current PR requires user awareness at the usage level. User docs repo

(Optional) Translate the PR title into Chinese.
一个新的优化
(Optional) More detailed description for this PR(en: English/zh: Chinese).
en: This PR adds support for extracting the int value contained by an ENUM node.
zh(optional): 本PR新增了对提取ENUM节点并返回int32值的支持。
(Optional) Which issue(s) this PR fixes:
N/A
(optional) The PR that updates user documentation:
N/A

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.shibaoshun seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@sbs-copilot please sign CLA


Refresh layer does not work

refresh stopped working layer.
before
var tmpSource = LayerOl.getSource (); tmpSource.setTileUrlFunction (tmpSource.getTileUrlFunction ());
It led to clear your cache and re-load layer
now there is no.
is there another way to reset the layer?

how about to use
getSource().refresh()

Thank you already saw. the previous version was not well that we decided to introduce this approach and the various workarounds were not.


Timezone of time entries?

The contribution guidelines mention that time entries should be as accurate as possible, but which timezone is not mentioned.
Should it be the native timezone of the (merge) commit or UTC?

native timezone of the (merge) commit

this is quite vague as it is not clear which timezone that actually is unless it is specified.
The current description does not allow adding a timezone so I assume it should be UTC.

Thanks for clarification!
I suspected that it would be UTC, but as it was not mentioned explicitly I thought it should be documented.


When is msal-angular 2.0 scheduled for live release?

We are eagerly waiting for msal angular 2.0 live release to implement auth code flow in our SPA application.
Will be very helpful to know the release date for stable version.

@SaviChinnadurai We are currently planning to have the public preview available next month, and general availability sometime not too long after that. We'll update our roadmap.

Great, Thanks jason.


fix: cannot read properties of null (reading 'cancelDrop')

This ignore a rare fatal issue that happen when a draggable item is removed before the container is unmounted
Cannot read properties of null (reading 'cancelDrop')

hey @stafyniaksacha , sorry for the late answer your changes have been published with the v0.0.6 release.
Thank you for your support!


Add "Save to address book" checkbox

Acceptance criteria

"Save in address book" checkbox should be shown only for logged-in users.
"Save in address book" checkbox should be shown only for a new address being edited.
"Save in address book" checkbox is applicable for both billing and shipping addresses.
"Save in address book" checkbox should NOT be shown if the user does not possess any default billing/shipping address and the user fills the address for the first time in the checkout.
In the case of 4, even though the checkbox is not shown, the address filled must be saved against the customer and need to be set as the default billing/shipping address.
if the "Save in address book" checkbox is NOT ticked, then that new address should NOT be saved against the customer.
If the "Save in address book" checkbox is ticked, then that new address must be saved against the customer.


Visualization problem

when I try to visualize the SPLOCS components, I'm receiving this error:
  File "view_splocs.py", line 86, in main
    visualization = Visualization(Xmean, tris, components)
  File "view_splocs.py", line 40, in __init__
    self.pd.point_data.normals = compute_normals(self.pd) # compute normals once for rest-shape (faster)
  File "view_splocs.py", line 18, in compute_normals
    n = tvtk.PolyDataNormals(input=pd, splitting=False)
  File "tvtk_classes/poly_data_normals.py", line 58, in __init__
  File "/usr/local/lib/python2.7/dist-packages/tvtk/tvtk_base.py", line 307, in __init__
    super(TVTKBase, self).__init__(**traits)
  File "/usr/lib/python2.7/dist-packages/traits/trait_handlers.py", line 104, in _read_only
    name, class_of( object ) )
traits.trait_errors.TraitError: The 'input' trait of a PolyDataNormals instance is 'read only'.

Thanks for reporting that, this has to do with the new TVTK pipeline. Should be fixed with the newest commit.


Expand DomEventSpec.js on and off tests

Based on #7438
Adds test cases for the following use cases:
** on(<HTMLElement> el, <String> types, <Function> fn, <Object> context?) (where types has several events)
** on(<HTMLElement> el, <Object> eventMap, <Object> context?)
** off(<HTMLElement> el, <String> types, <Function> fn, <Object> context?) (where types has several events)
** off(<HTMLElement> el, <Object> eventMap, <Object> context?)

Obsolete through #8088

@Crimson-riot very sorry that this got overlooked, won't happen again!


ffi gem breaking on osx GHA

This has hit quite suddenly, 2 hours ago:
https://github.com/metanorma/metanorma-itu/actions/runs/353863151
https://github.com/metanorma/metanorma-nist/actions/runs/353868442
https://github.com/metanorma/metanorma-ogc/actions/runs/353869297
https://github.com/metanorma/metanorma-cc/actions/runs/353865502
These are breaking OSX GHA. I am not getting this breakage in my local environment. The complaint is that sassc is not finding the local gem 2.x/ffi, where 2.x is the Ruby version
This issue is reported in:
https://medium.com/@hisa_py/jekyll-with-asdf-ruby-fix-ruby-ffi-loaderror-on-macos-high-sierra-c302f0567e9b , https://talk.jekyllrb.com/t/help-with-jekyll-error/3828/8 ,
https://talk.jekyllrb.com/t/jekyll-fails-on-macos-catalina/3765/8 > https://github.com/sass/sassc-ruby/issues/146

@opoudjis it looks like the issue is gone, I propose to close it if there now cases for this issue


Flickering looping ripple bug

https://user-images.githubusercontent.com/4672627/197250574-dbc734d6-de38-4911-a168-9d307310f86b.mp4
repro here:
https://github.com/AvaloniaUI/Calc

Seems like this is an Avalonia bug, and fixed now (in nightly Avalonia at least). Closing.
P.S. Also here is bug, where on mobile ripple remains pressed, I'll try to fix that.


How to use React Native to prohibit screenshots?

How to use React Native to prohibit screenshots?
I use the method of prohibiting screenshots in React Native, The entire page of the app has turned black and cannot be used normally.
Can you give an example of how to use the method of prohibiting screenshots in RN? Can I freely control whether screenshots are allowed on a certain page in RN?

How to use React Native to prohibit screenshots? I use the method of prohibiting screenshots in React Native, The entire page of the app has turned black and cannot be used normally. Can you give an example of how to use the method of prohibiting screenshots in RN? Can I freely control whether screenshots are allowed on a certain page in RN?

@YinWeiLF The codebase includes the most code to support prevent-screencapture for React Native but need to be a little modification, I know how to make it work(I have use it in my own React Native App).
I can take a PR to add necessary code & documentation for this repository,but I'm too busy recently. If you're not eager for that, I will mention this issue in the PR after it complete.

@YinWeiLF , As mentioned by @richardo2016 , the README has been updated with the necessary guidance on how to prevent screenshots in React Native. This should help you implement the feature properly without any issues. Therefore, we're closing this issue. Thank you!


bug: finding distinct values from a unnested array doesn't work

Describe the bug
The behavior of RisingWave:
dev=> select distinct unnest(array[1,1,2,3,1]) as x;
 x
---
 3
 1
 2
 1
 1
(5 rows)

The behavior of Postgres:
postgres=# select distinct unnest(array[1,1,2,3,1]) as x;
 x
---
 1
 3
 2
(3 rows)

To Reproduce
No response
Expected behavior
The same as PG.
Additional context
The following workaround is returning correct result:
dev=> select distinct * from unnest(array[1,1,2,3,1]) as x;
 unnest
--------
      1
      3
      2
(3 rows)

So it looks like distinct is not working properly after ProjectSet. The workaround puts unnest as part of from rather than select list, so no ProjectSet is involved.

unnest should not be inside hashagg
dev=> explain(logical) select distinct unnest(array[1,1,2,3,1]) as x;
                                                     QUERY PLAN
--------------------------------------------------------------------------------------------------------------------
 LogicalAgg { group_key: [projected_row_id, Unnest(Array(1:Int32, 1:Int32, 2:Int32, 3:Int32, 1:Int32))], aggs: [] }
 └─LogicalProjectSet { select_list: [Unnest(Array(1:Int32, 1:Int32, 2:Int32, 3:Int32, 1:Int32))] }
   └─LogicalValues { rows: [[]], schema: Schema { fields: [] } }
(3 rows)


Add HomeKit control for fan position for Falcon S DR-HAF004S

Is your feature request related to a problem? Please describe:
Hi - this fan works quite well with the plugin, and I'm very grateful for your work. The iOS Dreo app gives "PTZ"-like capabilities (similar to an IP camera) to put the fan at a particular place in its range of motion by sliding the blue dot around in the "3D" control as shown in the attached screenshot. I have no idea if HomeKit exposes this kind of functionality, but if it can move cameras, maybe it can do the fan?
Describe the solution you'd like:
It would be very helpful to be able to tell Siri to "place the fan at 45 Left 5 Up" or something like that without having to open the app.
Describe alternatives you've considered:
The Dreo Alexa functionality does allow you to turn on horizontal and vertical oscillation to move the fan and you can watch it and stop it where you want it if you're good at timing your command, but it is not true "put the fan here please" kind of functionality.

Are there any other fans that have this kind of control with homekit? I'm trying to figure out if this is possible.

Hi - I found this one, but I don't know if it's positionable like the Dreo, or just on and off. It also appears to not be released yet. https://eu.smartmiglobal.com/de/pages/smartmi-circulating-fan. I honestly don't know if this is even worth your time, what I found is that the fan loses track of where it is pointed pretty quickly and has to be recalibrated often. This may be one of those things where it's easier to just get up and move it. I looked and it looks like even PTZ IP cameras have to be controlled through their apps - HomeKit just doesn't expose that functionality I guess. A feature for the next version of the API I hope...


Support Cisco notation

Cisco (a dominant network device notation) uses a non-conventional notation
Switch# show mac-address-table
          Mac Address Table
—————————————————————-

Vlan    Mac Address       Type        Ports
——    —————-       ————    ——-
 All    0014.1c40.b080    STATIC      CPU
 All    0100.0ccc.cccc    STATIC      CPU
 All    0100.0ccc.cccd    STATIC      CPU
 All    0100.0cdd.dddd    STATIC      CPU
   1    000f.1fd3.d85a    DYNAMIC     Fa0/14

Given their clout over the market, what do you think about supporting it?

What kind of support are you looking for?  This is trivial to parse in the MacAddress constructor.  Are you looking for output formatting as well?

Hey @martylamb I would say parse. output IMHO is always better served by standards (i.e. EUI-48)


Terminal and Sidebar background colour

I noticed that Noctis and Noctis Sereno have slightly different colour / tone to the background in the terminal and sidebar area, whereas Noctis Azureus and Obscuro don't. Just wondering if this could be changed so that those two variants have slightly different backgrounds to those areas too?

Hey Trevor thanks for your feedback. The different color lightness was initially implemented so that the theme would suit different tastes. Lately I found myself using Noctis Azureus as my main theme and I realized that I actually liked it better to have a visual separation of the terminal and sidebar of the original Noctis. So I'm thinking of giving this a go.

Done. I'd appreciate if you would give it a go and leave a feedback.

Awesome! I tried it and it's perfect! I especially like the terminal colour for Azureus. Actually, could be cool if one day you add an additional variant where the editor bg is swapped with terminal bg, kind of like how Noctis and Noctis Sereno are. But I'm get getting greedy. :)
BTW, I didn't mention it before. but technically Noctis Lux terminal area background could use a slight contrast too if we are keeping everything consistent. But whatever. I think this can be closed. Thanks again!

You are right about Noctis Lux. I'll get on to it. In regards to a new variant I would leave it as it is for now. In future I might add another variant with a new background color altogether.


VIM-2773: Prevent viewport displacement on undo

Small bug fix for VIM-2773 which I raised on YouTrack.
Fixes viewport displacement when undoing deletion of lines or blocks that are immediately followed by a space character.
Before:

After:

This looks good for me. @citizenmatt Could you please also take a look, I know you like scrolling?

LGTM. I'd like to understand why it's necessary, to see if we're doing something wrong, or if it's a quirk of IntelliJ's undo system. More importantly, I'd like to know if it's something we should be guarding against elsewhere, but I can look into that separately.
(It appears to be related to caret positioning. The behaviour shows if the caret is moved to a column when it's moved away from the deleted line. If we :set nostartofline, so the caret column is maintained, and the caret column on the deleted line was 0, then we don't see the scrolling behaviour. If the caret is moved to any other column, then we see scrolling on undo)

Hmm. I've just seen the same behaviour if you use Ctrl+z to undo a dd operation, so we should probably look deeper into what's going on here. I think this is still a worthwhile change, though.

Oh, and forgot to say thanks @dominicpalmer! Nice work 😁


Adds highlighting to dbt Cloud job run URL

Summary

Adds highlighting to dbt Cloud job run URL
Adds run status logging while polling for job run status

Screenshots
Terminal

Orion UI

Relevant Issue(s)

Checklist

[ ] Summarized PR's changes in CHANGELOG.md

How does this look on Prefect UI?

I assume the UI will show the literal backslashes?

I checked this works well locally in my terminal

Looks like the syntax looks funky in the orion UI

So perhaps even if it looks funky, we can add a space in between? So at least it's easily copy/paste-able
\033[1;34;40m https://{dbt_cloud_credentials.domain}/#/accounts/"

But I do agree with @sungchun12 about "it gets lost in a sea of un-user-friendly logs." I feel like the logs can be too verbose + no coloring = hard to really discern without looking at UI.
Some discussion about it here: https://discourse.prefect.io/t/feedback-on-cleaner-logs/550

Most people will open the URL from their local terminal first and look at the orion UI later for historical runs in practice.

If users are running this task in a flow that's on a schedule via an Orion server or Prefect Cloud, then they would go to the UI first because they may not have access to the terminal logs. We don't currently have the ability to color the logs in the UI, but I'm working on finding a solution that allows terminal color without extra cruft in the UI.

Good call out. Having the logs look color-coded and polished in the UI may be the priority rather than the nice to have!

Most people will open the URL from their local terminal first and look at the orion UI later for historical runs in practice.

If users are running this task in a flow that's on a schedule via an Orion server or Prefect Cloud, then they would go to the UI first because they may not have access to the terminal logs. We don't currently have the ability to color the logs in the UI, but I'm working on finding a solution that allows terminal color without extra cruft in the UI.

After some internal conversations, I've learned that adding color to the logs will be a bigger lift than I initially thought. We'll need some development within the core Prefect library and platform to enable color coded logs in a polished way. I've created #21 to make sure we don't loose sight of this need, but right now this development is blocked.


Mismatched CodePipeline CloudWatch fields

Hi all, thanks for your support on this library. I was recently trying to replace our homemade structs for CodePipeline events with the ones defined in this package but I'm running into the following errors unmarshalling the version fields in CodePipelineEventDetail and CodePipelineEventDetail:
json: cannot unmarshal number 2.0 into Go struct field CodePipelineEventDetail.detail.version of type int64: errorString null

json: cannot unmarshal string into Go struct field CodePipelineEventDetailType.detail.type.version of type int64: errorString null

The unmarshalling works when CodePipelineEventDetail.detail.version is a float64 and CodePipelineEventDetailType.detail.type.version is a string (using our own structs). Would y'all mind taking another look at the types for the two versions fields?
Based on the comments for each of them, it sounds like there's some mismatch in the schema/documentation:
https://github.com/aws/aws-lambda-go/blob/96ab249f3eb7644ebc3bb7a190d268184fdd9f4e/events/codepipeline_cloudwatch.go#L82-L83
https://github.com/aws/aws-lambda-go/blob/96ab249f3eb7644ebc3bb7a190d268184fdd9f4e/events/codepipeline_cloudwatch.go#L105-L106
Thanks!

I just encountered the same issue. I'm currently using my own event structs with json.RawMessage for the Version fields.


WindowsVersionList Outdated

I suspect that the WindowsVersionList table may be outdated; the latest thing on there is 10_19H1_x64

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0afbc04b-349a-57ed-eeb0-3d2cd28e359c
Version Independent ID: de61f684-31d7-2de5-d66c-a3319f5198d9
Content: Inf2Cat - Windows drivers
Content Source: windows-driver-docs-pr/devtest/inf2cat.md
Product: windows-hardware
Technology: devtest
GitHub Login: @DOMARS
Microsoft Alias: domars

@DOMARS I am going to  change the location path.

@druske - Thanks for filing this issue and pointing out the need to update the version list for current day versions of Windows. This list has been updated, including Windows 11.


[HUDI-990] Timeline API : filterCompletedAndCompactionInstants needs to handle requested state correctly

This is a PR against 0.5.3 Release branch. The master changes is tracked under test flakiness.
Contains:

Code changes to fix HUDI-990 and
Fallback for remote file-system view disabled for tests. Unit tests have been made to fail when they cannot get response from remote file system view calls.

cc @vinothchandar @nsivabalan

Codecov Report

Merging #1701 into release-0.5.3 will decrease coverage by 0.07%.
The diff coverage is 100.00%.

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

@nsivabalan : You can use 2 master commits mentioned in the link below to pull in this change.
https://issues.apache.org/jira/browse/HUDI-890?focusedCommentId=17126054&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17126054
I will close this PR as it is against the release branch and does not contain both  commits


[libjpeg-turbo] build failure (arm64 target)

Host Environment

OS: Windows 10 x64
Compiler: Visual Studio 2017

To Reproduce
Steps to reproduce the behavior:
vcpkg.exe install libjpeg-turbo:arm64-windows
Failure logs
-Cut and paste the appropriate build messages from the console output.
-Please attach any additional failure logs mentioned in the console output.
`C:\Users\user\Code\vcpkg>vcpkg.exe install libjpeg-turbo:arm64-windows
Computing installation plan...
The following packages will be built and installed:
libjpeg-turbo[core]:arm64-windows -> 2.1.3#3
Detecting compiler hash for triplet arm64-windows...
Restored 0 package(s) from C:\Users\user\AppData\Local\vcpkg\archives in 284.7 us. Use --debug to see more details.
Installing 1/1 libjpeg-turbo:arm64-windows...
Building libjpeg-turbo[core]:arm64-windows...
-- Using cached libjpeg-turbo-libjpeg-turbo-c5f269eb9665435271c05fbcaf8721fa58e9eafa.tar.gz.
-- Cleaning sources at C:/Users/user/Code/vcpkg/buildtrees/libjpeg-turbo/src/fa58e9eafa-51b986428d.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source C:/Users/user/Code/vcpkg/downloads/libjpeg-turbo-libjpeg-turbo-c5f269eb9665435271c05fbcaf8721fa58e9eafa.tar.gz
-- Applying patch add-options-for-exes-docs-headers.patch
-- Applying patch workaround_cmake_system_processor.patch
-- Using source at C:/Users/user/Code/vcpkg/buildtrees/libjpeg-turbo/src/fa58e9eafa-51b986428d.clean
-- Configuring arm64-windows
-- Building arm64-windows-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:129 (message):
Command failed: C:/Users/user/Code/vcpkg/downloads/tools/cmake-3.24.0-windows/cmake-3.24.0-windows-i386/bin/cmake.exe --build . --config Debug --target install -- -v -j5
Working Directory: C:/Users/user/Code/vcpkg/buildtrees/libjpeg-turbo/arm64-windows-dbg
See logs for more information:
C:\Users\user\Code\vcpkg\buildtrees\libjpeg-turbo\install-arm64-windows-dbg-out.log
Call Stack (most recent call first):
installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_build.cmake:74 (vcpkg_execute_build_process)
installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_install.cmake:16 (vcpkg_cmake_build)
ports/libjpeg-turbo/portfile.cmake:56 (vcpkg_cmake_install)
scripts/ports.cmake:147 (include)
error: building libjpeg-turbo:arm64-windows failed with: BUILD_FAILED
Please ensure you're using the latest port files with git pull and vcpkg update.
Then check for known issues at:
https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+libjpeg-turbo
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?template=report-package-build-failure.md&title=[libjpeg-turbo]+Build+error
Include '[libjpeg-turbo] Build error' in your bug report title, the following version information in your bug description, and attach any relevant failure logs from above.
vcpkg-tool version: 2022-07-21-a0e87e227afb536c62188c11ad029954f28fdb22
vcpkg-scripts version: d293ac220 2022-08-12 (2 days ago)
You can also use the prefilled template from C:\Users\user\Code\vcpkg\installed\vcpkg\issue_body.md.
C:\Users\user\Code\vcpkg>`
Additional context
Add any other context about the problem here, such as what you have already tried to resolve the issue.
install-arm64-windows-dbg-out.log

This issue should be fixed in VS2019 or VS2022.

Thanks for posting this issue. Please reopen this issue if this is still a problem for you.


Unauthorized usage of your api

Notifying you about the existence of: https://github.com/EnigmaticaModpacks/Enigmatica6/pull/4870
Please consent or disapprove to the usage of your api endpoint for purposes under the enigmatica umbrella, as long as neither option is chosen the endpoint will not be used in production and will stay un-merged until an option that is legally sound is found.

No problem, but the data is not up to date.

oh? is it cached (updates every = ?) or a snapshot (will never update)?

snapshot, snapshot of https://addons-ecs.forgesvc.net

allrighty, probably not useful for the checking purpose i had in mind, but i appreciate being allowed to use it regardless :) 👌


fix for #89

Apply the fix to the src folder and then run npm start to generate the dist folder.

Hi @aksonov please resolve the conflict so I can proceed with merging your pull request, thanks!


alignment dashboard graphs not correct

The allignment of the graphs on the dashboard page isn't correct. This problem only concerns FireFox, when opened in Chrome the alignment is correct.
See image.

That is strange. I never noticed it. Can you please clear browser's cache and restart the browser? Also check that you haven't put any wrong code into extensions?
This video-screencast will shows that it can't be reproduced on my side:
rostovtsev.ru/pub/src/authentic/15.51/issue_233_dashboard_charts.webm

I have cleared the cache, disabled all browser plugins and the problem still isn't over.
The only difference is the browser, I said that is was in Firefox, I need to say that it is in Firefox Developer edition (42.0a2 (2015-09-02)) when I open webmin in the normal Firefox then the problem isn't there

Then don't worry about that!


Timeout for streaming API calls needed

We are trying to use gRPC for streaming between systems, however we need to assume the "other side" may misbehave.  As a specific example:

A server is streaming measurement data to a client.  The stream is expected to run for a long time (minutes to hours).  The data is coming from a DAQ task so we need to keep up with the task rate.  In this example the DAQ data is both being send to a client and used locally.
The client establishes a connection to the server and the server starts streaming the data.
The client starts to run behind in reading data from the streaming API.  This causes the buffer on the server to fill.
Once the buffer is full the server side will block in the dll and wait for room in the buffer.  This will cause the LV loop to be blocked.  In a worst case situation where the client has hung, the only way I have found to stop the loop is to have a parallel loop that aborts the entire gRPC server, obviously not ideal.

A similar problem exists on the client side if the server hangs.  The exposed timeout for the client is for the lifetime of the connection, not for an individual read call.  Since this is a long duration stream (minutes to hours) I need to set that timeout to very long or -1.  On the client since it is blocked in LabVIEW waiting on an occurance I can modify the client code to set a timeout for the occurance wait.
The server code is blocked in the dll so I can't work around the issue in LabVIEW.  I need a way to either know that my buffer is filling so I can stop sending data or (better yet) a timeout on the streaming write call so I can handle the full buffer.  This is similar to the TCP functions in LabVIEW.

AB#2837407

I think this would involve implementing a custom C++ interceptor which could monitor each outgoing message which would check if the timeout for each sent message had passed and cancel the message and/or close the stream.
There is a test for interceptors (which adds logging for each message) in the grpc repo to give you an idea of what would be involved - this would be a good chunk of C++ development and testing and require on-going maintenance as the C++ interceptor API stablizes (it is currently experimental)
https://github.com/grpc/grpc/blob/v1.44.0/test/cpp/end2end/server_interceptors_end2end_test.cc

@j-medland From your comments I'm guessing you are not a fan of that option.  :)
Is there a simpl(er) way to monitor how much room remains in the buffer so we know when a block is coming and we can pause ourselves?
Right now the best option I've come up with is to try to implement another stream back from the client showing what message number they last received and manually manage backpressure that way but it adds a lot of complexity since the return stream will be asynchronous.

I am open to anything but I am just a library user not a maintainer
Your suggestion of checking if there is room in the buffer helped me to stumble across this in the user guide which eludes to some concepts of controlling the flow and it links to some notes on how you can check if the underlying layer is ready to send the next message in the Java version of GRPC but nothing for the C++ version.
There is some discussion of backpressure and C++ GRPC in this stack overflow post and my naive understanding is that by choking the sender, the system is sort of working - its just that the way the LabVIEW service is architected, it blocks the whole service.
It might be possible to add an asyncronous wrapper around the send call (either on the C++ or LabVIEW side) with a timeout and I assume that if the spawned thread is blocked by a send-call then another thread cancelling the stream will allow that blocked spawned-thread call to fail and thus be unblocked so you can release resources gracefully. On second thoughts - I don't know if you can asyncronously launch a .vim so it would probably be best to handle it in the C++ code. Hmmmm
So, I am afraid I don't have an answer but it is certainly an interesting topic.


Release version that is built against Cats 0.2

I see it’s already in master, but not released yet.

0.2.0 snapshots (which depend on cats 0.2) are available now from Sonatype:
scalaVersion := "2.11.7"
resolvers += Resolver.sonatypeRepo("snapshots")

addCompilerPlugin("org.scalamacros" % "paradise" % "2.1.0-M5" cross CrossVersion.full)

libraryDependencies ++= Seq(
  "io.circe" %% "circe-core" % "0.2.0-SNAPSHOT",
  "io.circe" %% "circe-generic" % "0.2.0-SNAPSHOT",
  "io.circe" %% "circe-jawn" % "0.2.0-SNAPSHOT"
)

There are other changes in 0.2.0 that depend on recent work in the upcoming Shapeless 2.3.0, and as soon as that's published I'll release it.


Add qlog default tracer which writes to QLOGDIR if set

Issue #4189
Split from #4201

We can also simplify the qlog instructions in the README: https://github.com/quic-go/quic-go?tab=readme-ov-file#quic-event-logging-using-qlog


More precise $insertBlockNode

Currently adding a block element like TweetNode or YouTube node will need the next best insertion point. While this is OK we can do better.
We can split the tree nodes to add the block immediately at that position (probably based on  https://github.com/facebook/lexical/pull/2322)
Caveat: We can't split table cells!

Follow up: you paste a, supposedly, top-level node like TweetNode, the HTML maps to it at least. The node is supposed to be top-level but is inserted at an arbitrary place in the tree. We should automatically fix/prevent this.

other things to consider:

current insertion ignores (range) selection

usually pre selected text gets removed when inserting something new over it

for table cells, etc. insertation nearest possible would be great

ex. walk to next possible split point and insert there

@zurfyx Is this still an issue we want to consider?


Fix SwiftUI item view onAppear not getting called

Details
This fixes onAppear not getting called when SwiftUI item views were reused. The core issue is that, due to views being reused under the hood, updating the rootView of a hosting controller from ReusedHostingController_ofViewType_DayView(3) to ReusedHostingController_ofViewType_DayView(19) would only trigger a content / data update (the text changing from 3 to 19), not an identity update, which is what's really happening here. View reuse is an implementation detail, but it is critical for performance.
To demonstrate the issue, I've made a simple SwiftUI day view that reproduces the problem. Here, we update a a local store in onAppear, and use that value as a text overlay, making it easy to compare that value vs. the expected value. If there's a reuse issue, the numbers don't match, and we make the overlaid text red.

Reuse issue
After fix

private final class Store: ObservableObject {
  @Published var value: Int?
}

struct SwiftUIDayView: View {

  let dayNumber: Int

  @StateObject private var store = Store()

  var body: some View {
    ZStack(alignment: .center) {
      Text("\(dayNumber)")

      if let storeValue = store.value {
        Text("\(storeValue)")
          .foregroundColor((storeValue == dayNumber ? Color.green : Color.red).opacity(0.5))
      }
    }
    .onAppear {
      store.value = dayNumber
    }
  }
}

Unfortunately, we need an API change here. The .calendarItemModel extension on SwiftUI.View needs to take in an AnyHashable ID, which we internally use to give the view a stable identifier, even when reused across hosting controllers. For simple cases, one can simply pass a Day or a Month (both of which are Hashable) as the identifier.
We might also consider providing an API that looks like this in the future:
CalendarViewRepresentable(...)
  .dayView { dayComponents in
    Text(dayComponents.day)
  }

This closure is a view builder, and leaves the conversion to a CalendarItemModel<SwiftUIWrapperView<SwiftUI.View>> as an implementation detail (which also means we would handle applying IDs to views internally). I haven't fully thought through if this is possible, but it'd be a nice improvement.
Related Issue
https://github.com/airbnb/HorizonCalendar/issues/256
Motivation and Context
Bug fix, make SwiftUI integration better
How Has This Been Tested
Example app
Types of changes

[x] Docs change / refactoring / dependency upgrade
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.

@bryn no rush on a review - I'm actually going to revise this a bit to see if I can make this API change purely additive. I think there's a way to manage these IDs internally so that consumers don't need to specify them in their item provider closures.


Hermann/dev

Boost of dds2mqtt.

made  varibles readable & slove the .conf file hard coding problem.

Upate ddsproxy helper.


Sync Bill's calendar w/ Max.gov

Description
Definition of done

[ ]
[ ]
[ ]

Attachments
title

should be completed


Sort facet rows

Codecov Report

Merging #149 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master   #149   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files         122    122
  Lines        2730   2734    +4
  Branches      596    596
=====================================
+ Hits         2730   2734    +4

Impacted Files
Coverage Δ

src/components/facets/Facet.tsx
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Add "unresolvable configurations" to the breaking changes section of the release notes of 3.4

… changes section of the Release Notes
See discussion in https://discuss.gradle.org/t/3-4-rc-1-3-3-resolving-configurations-may-be-disallowed-and-throw-illegalstateexception/21470
Any of the checked boxes below indicate that I took action:

[x] Reviewed the Contribution Guidelines.
[x] Signed the Gradle CLA.
[x] Ensured that basic checks pass: ./gradlew quickCheck

For all non-trivial changes that modify the behavior or public API:

[x] Before submitting a pull request, I started a discussion on the Gradle developer list,
the forum or can reference a JIRA issue.
[ ] I considered writing a design document. A design document can be
brief but explains the use case or problem you are trying to solve,
touches on the planned implementation approach as well as the test cases
that verify the behavior. Optimally, design documents should be submitted
as a separate pull request. Samples
can be found in the Gradle GitHub repository. Please let us know if you need help with
creating the design document. We are happy to help!
[ ] The pull request contains an appropriate level of unit and integration
test coverage to verify the behavior. Before submitting the pull request
I ran a build on your local machine via the command
./gradlew quickCheck <impacted-subproject>:check.
[ ] The pull request updates the Gradle documentation like user guide,
DSL reference and Javadocs where applicable.

@CedricChampeau See discussion in Gradle forum.

Thanks for your contribution, I merged this into the release branch, it will therefore be visible in rc3.


[FEATURE] - Expanding syntax

Is your feature request related to a problem? Please describe.
I use Leanpub Markdown for authoring my books. It's a small extension on top of regular Markdown. One of the main features it supports are insertions and deletions like this:
// You might see insertions
leanpub-start-insert
const webpack = require("webpack");
leanpub-end-insert

// You might see deletions as well
leanpub-start-delete
const { MiniHtmlWebpackPlugin } = require("mini-html-webpack-plugin");
leanpub-end-delete

// Or combinations of both
leanpub-start-delete
const { MiniHtmlWebpackPlugin } = require("mini-html-webpack-plugin");
leanpub-end-delete
leanpub-start-insert
const webpack = require("webpack");
leanpub-end-insert

// If content has been omitted, then ellipsis is used
...

Note the Leanpub specific syntax that's sitting on top of the rest.
Describe the solution you'd like
It would be great to have a way to overlay an extension on top of a language in order to parse those custom sections. My current solution looks like this: https://github.com/survivejs/site/blob/master/utils/highlight.js .
Describe alternatives you've considered
As mentioned, I've implemented this in illuminate.js and thought to bring up the idea as there's value in having an API for extensions.

Hello, I have implemented the leanpub-markdown 77d93fc9b428db2266f44455da613c5fa5e6d4b2 with my understanding of leanpub-markdown, I hope this will fill up your needs. To use leanpub-markdown you just have to set the language to leanpub-md. If you want to see how it was implemented you can go checkout src/languages/leanpub-md.
Mathias

Awesome, thanks. 👍

Can you tag the release so I can pull it easily from deno.land? Thanks again.


feature request: add uv_fs_lseek()

Idea: add uv_fs_lseek(), implemented in terms of lseek64() and _lseeki64().
Motivation: General purpose file system stuff. My specific use case is to implement __wasi_fd_seek(), __wasi_fd_tell(), and __wasi_whence_t in terms of libuv.
I volunteer to do the work.

An oldie but a goodie on why lseek is a bad idea: https://github.com/joyent/libuv/pull/664
It's been six years but I haven't changed my mind. :-)

That's unfortunate, but OK. Thanks for the link.

Since this function is required by the libuv test suite, I'd be in favor of adding it. Despite the reasons given that it may be a bad idea to actually use it in complicated multi-threaded code, I hypothesize that most IO code (esp. code that wants to make use of this) is very straightforward.
OT: fwiw, the last statement in that thread ("Posix operating systems won't let you seek past the end of file") is false (as is the statement it was responding to). The actual behavior is to do exactly as told and sets the position to the given value. From the top of the linux man page: "lseek() allows the file offset to be set beyond the end of the file".


feat: add comment about other providers to next-auth API handler

✅ Checklist

[x] I have followed every step in the contributing guide (updated 2022-10-06).
[x] The PR title follows the convention we established conventional-commit
[ ] I performed a functional test on my final commit

Changelog
We frequently get questions on Discord and other places from people who swap the Discord provider for GitHub or some other one, and then don't understand why their auth is broken. Adding a comment to tell them that they need to look up how each provider works.
No changeset bc no change to functionality
💯

Conflicts

probably easier to just close this and make a new branch


Adding new versions of broccoli soruce & plugin

Sad to see this so out of date. When we release these related projects (broccoli-source, broccoli-plugin, broccoli, broccoli-node-info, etc) we need to ensure that the various projects are updated and testing properly against each other.


feat: Migrate env.mjs to .ts

Is your feature request related to a problem? Please describe.
It currently doesn't stop us from defining non-NEXT_PUBLIC_ key as part of the client env.
Describe the solution you'd like to see
If we migrate the .env.mjs to .env.ts, we can utilize the satisfies keyword to enforce the NEXT_PUBLIC_${string} as the client env key, without affecting the zod infer type.
However, I'm actually pretty curious why .mjs for env.mjs? It would be good if someone can answer this🙏
I personally have the working solution in my personal project, and I am more than happy to help.
Describe alternate solutions

Additional information
No response

I am very curious to see your solution. Perhaps a link to a repository might encourage the assignment of the feat?
From my limited experience, the env.mjs is not a typescript file as it is loaded by the next app inside next.config.mjs. At the moment there seem to not be any plans to support next.config.ts by the nextjs team.
As to possible solutions I messed around with, ts-import could be used to load an env.ts file inside the config. There is also the option to pre-compile env.ts before nextjs starts, but that might be too messy.

From my limited experience, the env.mjs is not a typescript file as it is loaded by the next app inside next.config.mjs.

Right, I completely missed that one. I'm actually working on a vanilla NextJS template instead of create-t3-app template, and I basically borrowed the env implementation from here with some minor improvement, and thinking about contributing back.
Having to install extra tools for importing a single ts file into next.confit.js seems a bit too much IMO. But I just realized that JSDoc do support 'satisfies' now, so I think I can just port my implementation to js instead. Will try to create a PR once I get to my computer.


Update is-svg dependency to >=4.2.2

Ah, looks like this triggered the new Validate Assets CI job after merging to master. Rebuilt assets with 35b7a82.


st_folium cannot support folium.plugins.TimestampedGeoJson

While folium_static renders the map properly with timestamped geojson data on it, st_folium fails with the following error code: "Cannot compute bounds of non-embedded GeoJSON." I did only change the map rendering mechanism between two runs, and I was able to reproduce the problem multiple times.

Hi @lpeti69 -
Please provide both code and sample data so that we can try to understand the issue.
Best,
Randy

Hi Randy,
sure!
I changed the GeoJson to the example one provided on the folium page:
I no longer receive the error code, however the map still does not render.
Screenshot attached of the error.
`import folium
from streamlit_folium import (
st_folium,
folium_static
)
m = folium.Map(location=[35.68159659061569,<PHONE_NUMBER>6151428], zoom_start=16)
Lon, Lat order.
lines = [
{
"coordinates": [
[139.76451516151428, 35.68159659061569],
[139.75964426994324, 35.682590062684206],
],
"dates": ["2017-06-02T00:00:00", "2017-06-02T00:10:00"],
"color": "red",
},
{
"coordinates": [
[139.75964426994324, 35.682590062684206],
[139.7575843334198, 35.679505030038506],
],
"dates": ["2017-06-02T00:10:00", "2017-06-02T00:20:00"],
"color": "blue",
},
{
"coordinates": [
[139.7575843334198, 35.679505030038506],
[139.76337790489197, 35.678040905014065],
],
"dates": ["2017-06-02T00:20:00", "2017-06-02T00:30:00"],
"color": "green",
"weight": 15,
},
{
"coordinates": [
[139.76337790489197, 35.678040905014065],
[139.76451516151428, 35.68159659061569],
],
"dates": ["2017-06-02T00:30:00", "2017-06-02T00:40:00"],
"color": "#FFFFFF",
},
]
features = [
{
"type": "Feature",
"geometry": {
"type": "LineString",
"coordinates": line["coordinates"],
},
"properties": {
"times": line["dates"],
"style": {
"color": line["color"],
"weight": line["weight"] if "weight" in line else 5,
},
},
}
for line in lines
]
folium.plugins.TimestampedGeoJson(
{
"type": "FeatureCollection",
"features": features,
},
period="PT1M",
add_last_point=True,
).add_to(m)
st_folium_map = st_folium(
m,
width=1280,
height=720
)`

Best,
Peter

Update: I discovereed that original error ValueError: Cannot compute bounds of non-embedded GeoJSON. was due to the first argument passed to folium.plugins.TimestampedGeoJson.
NO ERROR
folium.plugins.TimestampedGeoJson(
    {"type": "FeatureCollection", "features": features},
    period="P1M",
    add_last_point=True,
    auto_play=False,
    loop=False,
    max_speed=1,
    loop_button=True,
    date_options="YYYY/MM/DD",
    time_slider_drag_update=True,
    duration="P2M",
).add_to(m)

ERROR
folium.plugins.TimestampedGeoJson(
    features,
    period="P1M",
    add_last_point=True,
    auto_play=False,
    loop=False,
    max_speed=1,
    loop_button=True,
    date_options="YYYY/MM/DD",
    time_slider_drag_update=True,
    duration="P2M",
).add_to(m)

However, I still face the map loading problem, only static maps (with st_folium are rendered.)


[backport] Changes citation to new KDD paper

Backport of #7994

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit dd87bde2bc470f6fad189da3a4197ed572fe192b, target branch v6) succeeded!

Errors look unrelated. Merging.


Calendar

PyData theme has messed up the calendar's design a bit (especially the calendar date borders and the filter), would be great to get it to look the same as before! Let me know if you need more specifications! Also, there was some discussion on whether we could / should still use the React-based calendar library ... we may want to wait with this one until we know more on that front!
https://github.com/napari/napari.github.io/issues/271
What it looks like now in the PyData demo:

This is looking much better! There are just a few things that need updated:

[ ] Some places are using a default san serif font instead of Barlow:

filter options

filter label on narrow screens

"Copy to calendar" above main calendar

"Copy to calendar" within individual meeting info box

[ ] Filter dropdown on narrow screens is too wide, it should be same width as calendar itself

[ ] Calendar at all sizes should have blue (#80D1FF) 1px border
Currently:

Should be:

[ ] Month + year heading (within blue top bar of calendar) should be black but is #333333

Nice job on this one! There is still one issue I found initially that is still happening, and one new one I found:

The filter dropdown on narrower screens is still too wide; it should be only as wide as the calendar itself (Let me know if this is something beyond out control and / or too much trouble for the effort to implement it right now, we don't have to fix this for the first iteration if that's the case)
Currently looks like:

One other thing I noticed now that the filter options are using Barlow (thanks!): the filter options (with checkboxes) should be horizontally aligned with the label that says "show:". So they should be resting on the same baseline.
Currently looks like:

The fixes look so good! I did notice a couple of new things, though (sorry! 😖):

[ ] the font weight for "filter events" should be Regular / 400 (right now it is Medium / 500)
[ ] There should be a little more space between the bottom of the check box list of filters on narrow view, and the edge of the filter pane
[ ]
Currently:

Should be:

Spectacular work! Looks great to me! ⛱⛵


Update to show how to deploy the examples to kubernetes

Update to show how to deploy the examples to kubernetes
This MR will add some k8s scripts and show how to deploy the examples to kubernetes.
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[x] Created/updated tests
[x] Extended the documentation

@BodhiHu - mind opening a PR to our quickstarts or samples repos and linking to it here, per Artur's comment ^? I think this would be a great addition


upgrade to .NET 6

Fixes #43

@syahnur197 I upgraded to .NET 6. You may need to upgrade your dotnet-sdk version.


Wrong version of elasticsearch?

Hi,
I have deployed using the command below but had previously used repo 1.4. I have changed it to 1.7 now but I still seem to be getting the old version? Have I done something wrong? I am new to puppet so if I have done something obvious please forgive me.
   class { 'elasticsearch':
      manage_repo => true,
      repo_version => '1.7',
      autoupgrade => true,
    }
      elasticsearch::instance { 'es-01': }

curl localhost:9200
{
"status" : 200,
"name" : "app1-es-01",
"cluster_name" : "elasticsearch",
"version" : {
"number" : "1.4.5",
"build_hash" : "2aaf797f2a571dcb779a3b61180afe8390ab61f9",
"build_timestamp" : "2015-04-27T08:06:06Z",
"build_snapshot" : false,
"lucene_version" : "4.10.4"
},
"tagline" : "You Know, for Search"
}

Have you restarted elasticsearch after the upgrade? I think the module doesn't do it by itself.

Hi,
Only when setting the version number it will process the upgrade correctly.
because with the auto upgrade it sets it to latest but never changes the ensure value. Due this it doesn't notify the service.

Ok, I have changed the config to below, how to I force the update? I tried to stop the service but says it can't find it? Sorry, like I said, new to puppet and ES
  class { 'elasticsearch':
      manage_repo => true,
      repo_version => '1.7',
      version => '1.7.1',
    }
      elasticsearch::instance { 'es-01': }

Hi,
The service would be called 'elasticsearch-es-01'

Perfect! Thanks for your help!


Incorrect translation of integers to Alloy

Version: 0.0.3
For a model:
A
   x : integer
   [ x >= 0 ]

the resulting Alloy model is correct:
one sig c1_A
{ r_c2_x : one Int }
{ all  cl0 : this.@r_c2_x | cl0 >= 0 }

However, for a Clafer model
A
   x : integer
       [ this >= 0 ]

the resulting Alloy model is incorrect:
one sig c1_A
{ r_c2_x : one c2_x }
one sig c2_x
{ ref : one Int }
{ this >= 0 }

Reported error:
A type error has occured:
This must be an integer expression. Instead, it has the following possible type(s): {this/c2_x}
the correct code for the constraint should be
...
{ ref >= 0 }
...

Actually, x is translated incorrectly, since it does not have any children (the constraint does not require making x a signature). The code generated for the first example is correct as well.

I'm aware of this problem, but thanks for reporting. I was trying to fix it today, but I'm still not done.

Ok, I submitted a quick & dirty fix. It should work, but disables one integer optimization. Doing this properly requires coupling code generator with name resolver. I don't have time to do this one, and it's probably not that important for now.

the problem occurs when name resolver is not used

the translator resolves names by default. Should be fixed.