Improve Teleop Driving

Change drivetrain to DcMotorEx class objects, then setVelocityPIDFCoefficients(), and only setVelocity() to command.
"squared" curve to joystick inputs for improved precision maneuvering at slow speeds. For example: joystick_fwd = gamepad1.left_stick_y * Math.abs(gamepad1.left_stick_y);
If testing is still "twitchy", filter the joystick input commands. The smooth_delay "class" here is what I'd recommend for drivetrain, since it is easy to adapt to (as a driver) and takes off rough edges rather then outright preventing extreme inputs.

Change drivetrain to DcMotorEx class objects, then setVelocityPIDFCoefficients(), and only setVelocity() to command.

Velocity control would be good for consistency and predictability, but I'm not sure how well the drivers would be able to get used to the new system.

"squared" curve to joystick inputs for improved precision maneuvering at slow speeds. For example: joystick_fwd = gamepad1.left_stick_y * Math.abs(gamepad1.left_stick_y);

Again, I feel this would be helpful, but I'm not sure if the drivers will be able to get used to it. Perhaps we could try different functions or maybe even use piecewise functions (some curve, some linear).

If testing is still "twitchy", filter the joystick input commands. The smooth_delay "class" here is what I'd recommend for drivetrain, since it is easy to adapt to (as a driver) and takes off rough edges rather then outright preventing extreme inputs.

This will be very useful if we need to smooth some rough edges/transitions. I will first need to port the C code into Java to use it though.
Thank you so much for your input and ideas. I really appreciate it.

I can all but guarantee that drivers will immediately like a change to a velocity feedback controlled drivetrain. There is less "fighting with the controls" to get the robot to do what you want.
Curving the joystick input can be more subjective/preference based, but it's easy enough to do I'd still recommend trying it out.

Of all the proposed changes, this is one of the easiest wins/adjustments. At least try it out @ToothbrushB

The new joystick curves (EnhancedTeleOp.java : 109 and 110) are losing the sign of the joystick input. My go-to solution is x*abs(x) instead.
Then lines 112,113 you are scaling. From 2 to the maximum motor rpm. The result is that if the driver command full forwards, the robot will only move at 50% speed (but you'll have lots of steering authority available). I'd recommend changing so that maximum forward is maximum speed (saturate to 1, then map from 1 to 165), and at maximum speed accept that turns will be more gradual.

Java port of smooth delay looks functional. (code readability opinion - I would have everything in just the SmoothDelay class in SmoothDelay.java and not have separate files and extending classes. The extra abstraction doesn't seem to buy you anything here).
Your teleop loop time (dt) we looked at today was ~12 ms (nice!!). So the "calling loop to operate at constant frequency" is good enough. The step value is all driver preference. Probably values below 5 are not useful, and values above 20 too sluggish. Remember that the goal is not to eliminate extreme/sudden behaviors, but to force the driver to be really intentional about triggering them.

Potential feature: Drive the Claw
Purpose: avoid claw collisions when raising/lowering in close proximity to obstacles
double armRadius = [measure it, m];
double theta = [arm angle, radians, horizontal=0, increasing down];
double thetadot = [arm velocity, radians/second];
// then with drive converted to m/s...
drive -= -armRadius*sin(theta)*thetadot; // double negative intentional; cancel out body relative motion
My first instinct is to use armTargetSmooth and trap.current_velocity instead of measured encoder values as the data source to calculate theta and thetadot to avoid latency issues (best synchronization by not wait for confirmed arm motion to even start trying to get the drivetrain to move).

Java port of smooth delay looks functional. (code readability opinion - I would have everything in just the SmoothDelay class in SmoothDelay.java and not have separate files and extending classes. The extra abstraction doesn't seem to buy you anything here).

I know the abstraction doesn’t really make too much sense, but I wanted to model the .h and .c files as closely as possible and didn’t know how else to model the .h file. I will definitely combine the two when I have the time.

Potential feature: Drive the Claw Purpose: avoid claw collisions when raising/lowering in close proximity to obstacles double armRadius = [measure it, m]; double theta = [arm angle, radians, horizontal=0, increasing down]; double thetadot = [arm velocity, radians/second]; // then with drive converted to m/s... drive -= -armRadius*sin(theta)*thetadot; // double negative intentional; cancel out body relative motion
My first instinct is to use armTargetSmooth and trap.current_velocity instead of measured encoder values as the data source to calculate theta and thetadot to avoid latency issues (best synchronization by not wait for confirmed arm motion to even start trying to get the drivetrain to move).

I am a little confused as to what the purpose of this is. I can see that you’re trying to figure out where the arm is/how it’s moving by finding radius, angle, etc. However, I don’t understand how that can help us avoid collisions when raising/lowering. How would the robot know that there is an obstacle in its path by just knowing where the arm is/how it’s moving? I am also confused as to whether you are trying to avoid collisions when raising/lowering or when driving (you used the variable “drive”). My misunderstanding and confusion might come from me not knowing what math you are writing at the bottom; I should probably brush up on/learn more trigonometry.
It makes sense to use values provided by the profiler, but I don’t think it will harm loop time, synchronization, or latency if we use the encoder values. The loop time we calculated today included getting the encoder values for the arm at the very beginning (before any driving), and since that loop time was pretty fast, I don’t believe using the encoder values will hurt us.

I know the abstraction doesn’t really make too much sense, but I wanted to model the .h and .c files as closely as possible and didn’t know how else to model the .h file. I will definitely combine the two when I have the time.
The .h file is an artifact of C and how its compiling/linking system works that as far as I'm aware doesn't apply to Java.

However, I don’t understand how that can help us avoid collisions when raising/lowering. How would the robot know that there is an obstacle in its path by just knowing where the arm is/how it’s moving? I am also confused as to whether you are trying to avoid collisions when raising/lowering or when driving (you used the variable “drive”).
You are correct, the robot doesn't know if there is an obstacle in its path or not. But the human driver does. So currently, if the robot pulls up close to an obstacle and tries to raise its arm, the driver will have to backup first (read: drive the robot, thus modifying the drive variable; the robot's commanded speed) to make sure the arm doesn't collide with the obstacle. My proposed enhancement will automatically modify the drive speed command to compensate for arm movement. So the effect is that the driver can really focus on just the claw and has (as much as possible) independent control inputs to move it forward/backward, rotate, and up/down (previously, foward/backward and up/down were coupled). Will this mess with the driver too much when not near anything? TBD, it's simple enough that I think it's worth trying out.

It makes sense to use values provided by the profiler, but I don’t think it will harm loop time, synchronization, or latency if we use the encoder values.
If using the encoder values, then the response time of the electromechanical system (mass moving, encoder mechanical design) becomes part of the feedback loop. The mechanics are very sluggish relative to the electrical speeds, and your low count encoder has low velocity bandwidth (slow to detect changes in velocity). So my hunch is that waiting for these systems to respond to start commanding drive motors (which have to get through their own mechanical latency) is a worse problem than using ideal (profiler output) data instead of real (encoder measured) data.

Need to have separate smoothDelay objects for each variable being smoothed.

I implemented the drive with claw feature in EnhancedDecoupledTeleOp.java, but I'm not sure if I did it correctly. Could you please check my code?
Notes:

Line 52 is used to convert the angle difference between the tower and the resting position of the arm (the angle offset) to ticks
The 15 on line 52 is the placeholder angle offset and should be in radians, I just forgot to convert it
The arm length on line 53 needs to be adjusted
I chose to use trap.current_position instead of keeping track of armTargetSmooth. It should output the same number though.
I know there are many expressions that can be simplified, I will keep them in this "verbose" form to make troubleshooting easier.

I implemented the drive with claw feature in EnhancedDecoupledTeleOp.java, but I'm not sure if I did it correctly. Could you please check my code?
Notes:

Line 52 is used to convert the angle difference between the tower and the resting position of the arm (the angle offset) to ticks
The 15 on line 52 is the placeholder angle offset and should be in radians, I just forgot to convert it
The arm length on line 53 needs to be adjusted
I chose to use trap.current_position instead of keeping track of armTargetSmooth. It should output the same number though.
I know there are many expressions that can be simplified, I will keep them in this "verbose" form to make troubleshooting easier.

Only have time for a quick glance now.

The 'driveMetersPerSec' alteration for arm movement should NOT be affected in any way by fastMode scaling.
Move the drivetrain code to after the arm code so you have the latest arm commands (only saving one loop, which is not much, but it's an easy change).
ARM_ENCODER_OFFSET I think can just be a measured value; put a level on top of the arm, print out the tics when the level reads 0 degrees. Probably something like -500 or -600 tics? based on the other arm setpoints.
I'm not familiar with the angleUnit and distanceUnit systems, so

A comment on "style" - it is a better practice to convert values into engineering units "meters, radians, seconds, etc." as soon as they are input, perform all calculations in those units, and then only convert to required output units at the last possible point.
Verbose for easier debugging is perfect.

I think that fast mode scaling is necessary in order to calculate the "real velocity" that gets sent to the motors. If we just subtract from the non-scaled velocity, we wouldn't move at the right speed because the velocity would be scaled down.

Move the drivetrain code to after the arm code so you have the latest arm commands (only saving one loop, which is not much, but it's an easy change).

Done

ARM_ENCODER_OFFSET I think can just be a measured value; put a level on top of the arm, print out the tics when the level reads 0 degrees. Probably something like -500 or -600 tics? based on the other arm setpoints.

I might try both methods and see if they come up with around the same answer. Although, the measurement option probably is more accurate than trying to measure lengths and angles, it would still be a good learning experience to play with trigonometry in the real world.

I'm not familiar with the angleUnit and distanceUnit systems, so

They are just utility enums that help you convert between different units. The angle unit enum has methods like fromRadians(), toDegrees(), etc. The distance unit enum has methods that convert distances. It wouldn't be hard to implement these methods by hand, but since the rest of the SDK uses AngleUnit and DistanceUnit, I was inclined to use them too.

A comment on "style" - it is a better practice to convert values into engineering units "meters, radians, seconds, etc." as soon as they are input, perform all calculations in those units, and then only convert to required output units at the last possible point.

Drive and turn are now in m/s from the very beginning. They get scaled by fast mode too so that they accurately resemble the velocity in real life. They get converted back into tics/s when calculating the combined velocity (drive and turn).

Looking great, nice work! Grab a side view video when you try it out.


Emit BeforeLineItemQuantityChangedEvent before line item modification

1. Why is this change necessary?
BeforeLineItemQuantityChangedEvent should be emitted before lineItem quantity gets changed, to allow plugins to handle the information effectively before the quantity is modified.
2. What does this change do, exactly?
Emits the BeforeLineItemQuantityChangedEvent  before lineItems change.
Adds a new contructor paramenter to BeforeLineItemQuantityChangedEvent to allow plugins to understand if quantity is being increased or decreased
3. Describe each step to reproduce the issue or behaviour.
4. Please link to the relevant issues (if any).
5. Checklist

[x ] I have rebased my changes to remove merge conflicts
[ ] I have written tests and verified that they fail without my change
[x ] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x ] I have read the contribution requirements and fulfil them.

While I understand the purpose of this change, this will break all plugins which rely on the fact, that $lineItem->getQuantity() will yield the changed quantity.

While I understand the purpose of this change, this will break all plugins which rely on the fact, that $lineItem->getQuantity() will yield the changed quantity.

Thanks a lot for sharing your view on my first PR! You're right.
The event dispatch could remain unmodified, I could add a beforeUpdateQuantity to the event to keep the desired functionality. What do you think?

I reverted part of the code, and added a beforeUpdateQuantity property to let plugins handle the delta: $event->getBeforeUpdateQuantity() - $event->getLineItem()->getQuantity()

@luminalpark Thanks for opening the PR.
Could you also write tests for your changes?


This error

The validator seems to fail when trying to validate code with a 'this' expression.

Hi @dyedgreen, can you please be more specific about your problem and provide your .eslintrc config file along side a code sample that trigger the error. Thanks

Thanks for the fast reply @Adezandee :)
This is the .eslintrc file
// Use this file as a starting point for your project's .eslintrc.
// Copy this file, and add rule overrides as needed.
{
  "extends": "airbnb"
}

However the problem went away after restarting the validator. It might have been just something random or it might have been a very specific problem with the following code (due to missing the super() statement perhaps?)
'use strict';

class SomeClass extends SomeOtherClass {
  constructor(someOption) {
    // No super() call here!
    this._someOption = someOption === undefined ? false : someOption;
  }

  // Some function
  function() {
    setInterval(() => {
      // Here is where the error occurred
      this._someOption = true;
    }, 1000);
  }
}

@dyedgreen indeed after updating fast-eslint or updating your .eslintrc, if you experience unexpected errors try to restart atom. This solve most of conflicting memory loaded/updated code with eslint.


help?

I need some help working with this plugin.
I set up .env variables, then call:
$user = app('meli_api')->userShowMe();
And "The User ID must match the consultant's" Errors shows up.

Dou you resolved? I have de same problem i think that it's for the token

Well 2 years laters i have the same problem!


[SUGGESTION] (your title goes here)

Hello,
First of all, great project.
I wonder if you will be interested in exploring an integration option with Galaxy protocol?
https://docs.galaxy.eco/1-hello-galaxy

Thanks for the feedback. What kind of integration did you have in mind?

Closing for now! Feel free to reach back out


current build incorrectly installing aicsimageio version and dependencies

Hi @haesleinhuepf ,
Back again. CZIreader from AICSImageIO does not work in current conda build.
conda create -name new-env -c conda-forge devbio-napari. I have found the reason is due to 1) lacking install of xmlschema module and 2) some other weirdness... older forges result in aicsimageio 4.7.0 and aicspylibczi 3.0.5, consistent with the current versions installed by conda forge. Installing the missing xmlschema module does not fix the issue, so not sure what tangles are back there.
Solution: conda install aicsimageio solves this by installing aicsimageio 4.9.1, aicspylibczi 3.0.5 and additionally installs xmlschema 1.4.1. Alternatively I had success with conda create --name new-env -c conda-forge aicsimageio devbio-napari
Is the way to solve this just by putting aicsimageio>=4.9.1 in the requirements.txt?

Thanks for the explanation @TimMonko ! So your problem seems solved? If not feel free to reopen this issue and let me know how I can help.
Cheers! 😃


mac-11 lost external connection from phone device.

Type of Request
bug
Infrastructure Environment
LUCI, Github, Cocoon scheduler, Autosubmit, etc...
What is happening?
mac-11 lost external connection from phone device.

Steps to reproduce
Step 1:
Step 2:
..
Step n:
Expected results
I expect to see X when Y is finished.

Rebooting machine to restore external connection.


Minor bugfix to remove trashcan from selectMetadata

Fixes #724 (Remove trashcan when there is only one metadata column remaining)
Includes minor re-organization of file structure to isolate the files and data associated with the selectMetadata dialog out of browse.js and into selectMetadata.js.

Also, can you only remove the trash can on the first item in the list? Right now you can see the icon on the second element disappear before the animation starts to remove the whole line and it looks awkward.

Issues address; also fixed a bug in widgets that caused menu items in select metadata to be highlighted when they were only present in widgets but not in select metadata


Add fixture

Issue#1171 has been much embroiled...
There are basically 2 cases mentionned:

object with an items property : covered with fixture for issue#1238 (more or less a duplicate of #1171, only clearer)
items missing in array. This case specifically covered by the present fixture.

Together with issue#1238, both cases discussed are covered by UT (new exerciser for cmd/swagger/validate).

Of course, merge issue...

Thanks Ivan.
Now I believe we can close #1171 and move on further.


Other surveys list doesn't scroll, handle short windows

Added a scroll feature to the dropdown menu.


YOLO-NAS save prediction under same file name or filename +pred, IMAGES :question:

💡 Your Question
Is it possible in model.prediction to use the original file name to store ?
when accessing prediction results and something was predicted I want to save to same file name.
https://github.com/Deci-AI/super-gradients/blob/classification_predict/documentation/source/ModelPredictions.md
out.save()
they are stored with new names pred_1.jpg etc.
access original file name as well here!:
`for image_prediction in images_predictions:
class_names = image_prediction.class_names
labels = image_prediction.prediction.labels
confidence = image_prediction.prediction.confidence
bboxes = image_prediction.prediction.bboxes_xyxy
for i, (label, conf, bbox) in enumerate(zip(labels, confidence, bboxes)):
    print("prediction: ", i)
    print("label_id: ", label)
    print("label_name: ", class_names[int(label)])
    print("confidence: ", conf)
    print("bbox: ", bbox)
    print("--" * 10)

    # You can use the detection results for various tasks, such as:
    # - Filtering objects based on confidence scores or labels
    # - Analyzing object distributions within the images
    # - Calculating object dimensions or areas
    # - Implementing custom visualization techniques
    # - ...`

Thank you for your help and time.
Versions
No response

I tested with some images by referring to the Using Pretrained Models for Predictions.
Take a look at this and let me know if it helps:
from super_gradients.common.object_names import Models
from super_gradients.training import models
import ntpath

model = models.get(Models.YOLO_NAS_L, pretrained_weights="coco")

IMAGES = [
    "D:/super-gradients/images/image_person.bmp",
    "D:/super-gradients/images/image_bus.jpg",
    "D:/super-gradients/images/122021417432646.bmp",
]

images_predictions = model.predict(IMAGES, iou=0.5, conf=0.7)

for i, prediction in enumerate(images_predictions):
    image_output_path = ntpath.join("output_folder", f"{ntpath.basename(IMAGES[i])}")
    prediction.save(output_path=image_output_path)

Thank you very much, that's how it works.


Please provide more Diagram examples of Firewall setup mentioned on this page

Please provide more Diagram examples of Firewall setup mentioned on this page. When you talk about outbound and inbound addresses, I am not sure what are you talking about. What is direction of communication? Does the inbound means traffic coming into Azure Logic Apps and Outbound means traffic leaving Logic Apps . What does mean outbound and inbound ip addressed in terms of managed and custom connectors. I think Picture says 1000 words with networking setups. Please do not assume that reader should use his/her imagination to determine direction of communication when talking about inbound and outbound.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 845c4db9-1f3a-26d1-5061-c018cb1fe336
Version Independent ID: c2a03981-a0aa-64a5-2659-e10202e5bb14
Content: Limits and configuration reference guide - Azure Logic Apps
Content Source: articles/logic-apps/logic-apps-limits-and-config.md
Service: logic-apps
GitHub Login: @ecfan
Microsoft Alias: estfan

Hello @sarabsandhu - Thank you for your feedback! We will review and update as appropriate.

@sarabsandhu Thanks for the feedback! The terms Inbound and Outbound are relative to the component in question, i.e., logic app, connector, etc.
We have assigned this issue to the content author for further review.

@sarabsandhu & @PramodValavala-MSFT: Thanks for the suggestions! Apologies as I've been on vacation. I've added a work item for this request to our backlog for triage and prioritization.

@sarabsandhu: A doc update will go live later today to provide more description about what inbound and outbound mean.


Update name to PromptGuard

[x] Change name in package.json
[ ] Change name in documentation
[ ] Change name in code
[ ] update image in Canva
[ ] update publishing workflow yaml

resolves #28


cancel task when task is pending, scheduled, error,

cancel task when task is pending, scheduled, error,  msg, will lost.  scheduler did not handle cancel.
worker will run a task which canceled.
only can cancel running task?

🤔 interesting, tasks should be cancelled regardless of state.

@lorentz-wu can you try again using the latest release

Closing due to inactivity.


Add extra .aspx page

When I add an extra .aspx page to the project, I can't access it.  Is this a configuration issue or something else, i.e. does it need to be configured somewhere like the logon.aspx page is configured in the web.config in the reportserver directory (as below):
<authentication mode="Forms">
 <forms loginUrl="logon.aspx" name="sqlAuthCookie" timeout="60" path="/">    </forms>
</authentication>

Can an extra .aspx be added and accessed or not?

Anyone?


Next round updates to documentation

maybe we should have a tutorial for installing docker

@Burhan-Q comments on branches, closing issues and these (copied from chat):
1 - we're trying to write out and follow a new procedure while we're sprinting to make changes, it gets tough to manage
2 - The [hardware] Testing, Review, and Approval steps are in need of some fine tuning still (I think)
3 - Some tickets don't have a Pull Request associated (as an example #108), perhaps we need to address this?
4 - The Pull Request process can be painful from a hardware point of view, which is why I've been letting people know they can pass along the files to me to upload (if they want), I've been moving cards that are 'finished' without files uploaded to the Closed bucket of the project, but not closing the Issue.
5 - Reviewing one of the issues I closed, I noticed that the part was reviewed, printed, tested, approved, but no additional part was needed to be printed so I (preemptively) closed it. I need to go back and reopen so the file can be properly Pushed before closing.

I see potential for scope creep in this issue. Is the issue to create a tutorial for installing docker or an alternative workflow for opening/closing issues in GitHub? These are two very separate issues.

lets focus on accessibility and readability for this issue @thehannahfink brought up good points


Dark theme

https://github.com/DevilXD/TwitchDropsMiner/pull/486

Basically, 90% of this is wrong, and needs a heavy rewrite. Things to note:

match-case usage is forbidden, as it was only added in Python 3.10, while TDM supports 3.8+
In-place changing of the entire GUI isn't needed, as it complicates the entire thing. It's better to implement this like the language changing, where each GUI element gets to read the currently selected theme (internally: style value), and you have to restart the application to see the effect.
Styles have to be pre-defined before the GUI is build, using the TTK styles guide that can be found here: https://tkdocs.com/shipman/ttk-style-layer.html

I'll change the match to elif.
I intentionally wrote it in a way, that would allow other styles in the future, only requiring a change of the checkbox. Especially with that in mind, I think it's useful to change the elements in place, so that people can try stuff out and find what they like. Additionally, this way it's all in one place and doesn't require adding additional variables all throughout the gui code for new styles.

I don't really know anything about anything, but I know Windows made a dark theme that was wonderful. I would absolutely love for this to exist. Sorry, I'm a complete noob and don't know if this is going to be a thing, or wont be.

I did research TKinter styles, but as you mention, there is no way to change them in-place. I find this an unnecessary annoyance for the user, which is why I chose to change them in place.

I did research TKinter styles, but as you mention, there is no way to change them in-place. I find this an unnecessary annoyance for the user, which is why I chose to change them in place.

But is there anyway that this could just make it into the Devil build? I feel like it's so insanely useful and literally saves my eyes. I'm not trying to make waves or drama, I just can't stress how important Dark Themes are, at least for me.

Unfortunately, that information is incorrect. I told you that the styles have to be predefined at launch, instead of "manually" changing every single GUI element at runtime. Doing that is not scalable nor maintainable in any efficient way. I knew that Tkinter had a whole setup for changing styles of all widgets with just a little bit of code, and even tried telling you, but you were affixed to it (supposedly) sacrificing the no-restart "feature" of it.
I spent exactly one day yesterday on researching how to actually define a style in Tkinter, and this is actually all you need to change the "theme" (mostly just background color for now) of 99% of the GUI:

No-restart isn't a requirement for this feature, but the above can change the theme dynamically, without having to restart. It's not like I don't want to make it a no-restart feature, it's just that I'm not willing to sacrifice potentially increased complexity and maintenance cost, over just having to restart to see a theme that everyone is gonna set once and pretty much forget about. And since this PR carries a significant maintenance cost right now, I won't be merging it, and I'll instead do it "the right way".
The current in-dev version struggles with Tkinter widgets not really liking having to redraw themselves in an controlled manner, but then again, I'm still working on it. No ETA on this, just me tinkering around like usual.

I unfortunately still don't have much time, and it is too long ago to remember exactly, but I do remember trying ttk styles and it not working out. I also remember running into complications with the background of the Inventory tab, include/exclude lists and other more complicated parts, tho I'm not sure whether that related to styles or whether I moved on from styles at that point. Maybe you manage to do it.

@DevilXD
As all the other pull requests are closed now, I'll put it here:
I still don't really have time, I'll just keep fixing critical issues on my fork for people that want to use it for now.
As for the changes, eventually, I'll look at the diff and probably just copy and paste stuff for each feature into a new commit, as, except for the new priority option, everything was done by me anyway.

I mean, I'm working on this feature right in this very moment, so you don't have to do anything here. I don't mind you keeping a personal fork. Unless you're talking about merging your entire fork into this project, in which case it'd be best to either make a relevant PR, or open a separate issue for discussion. This PR is all about dark mode support, and I'd kinda prefer to not litter it with seemingly-unrelated talk.


Support Go modules

It would beneficial for projects consuming this library and already using Go modules, that the project supports Go modules.

Subscribed to the issue. Thanks for the heads-up!


Fix 'repetetive' typo

What type of PR is this?

documentation

What this PR does / why we need it:
This is a documentation typo fix, also created so I can test that CI is green on the tip of main.
Which issue(s) this PR fixes:
(none)
Release Notes
NONE

The "Run Tests / test-docs" failure looks unrelated.

@dearchap I'd be hpapy to see such a tihng introdcued 👍🏼


FieldArray shouldComponentUpdate fixes

see #1975

Current coverage is 99.91% (diff: 87.50%)

Merging #1976 into master will decrease coverage by 0.08%

@@           master      #1976   diff @@
========================================
  Files          54         54
  Lines        1194       1201     +7
  Methods         0          0
  Messages        0          0
  Branches        0          0
========================================
+ Hits         1194       1200     +6
- Misses          0          1     +1
  Partials        0          0

Powered by Codecov. Last update 8c43de8...2dcf287

Issue claims this was already fixed.


Missing command interface when launching the ROS2 driver

Affected ROS2 Driver version(s)
Humble master
Used ROS distribution.
Humble
Which combination of platform is the ROS driver running on.
Docker
How is the UR ROS2 Driver installed.
Build both the ROS driver and UR Client Library from source
Which robot platform is the driver connected to.
URSim in docker
Robot SW / URSim version(s)
5.14.1
How is the ROS driver used.
Through the robot teach pendant using External Control URCap
Issue details
Summary
When building the ROS2 Driver from the humble branch and launching the ROS2 driver, the ur_ros2_control_node dies as the command interface force_mode is missing. Se log output below.
Issue details
The force_mode command interface is part of the Universal_Robots_ROS2_Description on the ros2 branch. The ros2 branch is checked out when cloning the Universal_Robots_ROS2_Description using VCS import on the required repos or the not released repos. However, the force_mode command interface is not yet supported in the driver and therefore the error occurs.
Steps to Reproduce
Build the ROS2 driver from the humble branch and try to launch the driver.
Workaround Suggestion
I will add a pull request with a fix later today, where the humble branch is checked out instead of the ros2 branch.
Relevant log output
root@ur-li-95qgtn2:/workspace/ros_ws_ur_driver# ros2 launch ur_robot_driver ur_control.launch.py ur_type:=ur5e robot_ip:=<IP_ADDRESS>
[INFO] [launch]: All log files can be found below /root/.ros/log/2023-09-15-11-12-28-492646-ur-li-95qgtn2.unirobotts.local-193
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [dashboard_client-2]: process started with pid [198]
[INFO] [controller_stopper_node-3]: process started with pid [200]
[INFO] [ur_ros2_control_node-1]: process started with pid [196]
[INFO] [urscript_interface-4]: process started with pid [202]
[INFO] [robot_state_publisher-5]: process started with pid [204]
[INFO] [rviz2-6]: process started with pid [206]
[INFO] [spawner-7]: process started with pid [208]
[INFO] [spawner-8]: process started with pid [210]
[INFO] [spawner-9]: process started with pid [221]
[INFO] [spawner-10]: process started with pid [253]
[INFO] [spawner-11]: process started with pid [255]
[INFO] [spawner-12]: process started with pid [262]
[rviz2-6] qt.qpa.xcb: could not connect to display
[rviz2-6] qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
[rviz2-6] This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
[rviz2-6]
[rviz2-6] Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
[rviz2-6]
[dashboard_client-2] [INFO] [1694776349.855177240] [UR_Client_Library:]: Connected: Universal Robots Dashboard Server
[dashboard_client-2]
[controller_stopper_node-3] [INFO] [1694776349.935935560] [Controller stopper]: Waiting for switch controller service to come up on controller_manager/switch_controller
[ur_ros2_control_node-1] text not specified in the tf_prefix tag
[ur_ros2_control_node-1] [INFO] [1694776349.942745800] [resource_manager]: Loading hardware 'ur5e'
[ur_ros2_control_node-1] [INFO] [1694776349.946935475] [resource_manager]: Initialize hardware 'ur5e'
[ur_ros2_control_node-1] [INFO] [1694776349.947084685] [resource_manager]: Successful initialization of hardware 'ur5e'
[ur_ros2_control_node-1] terminate called after throwing an instance of 'std::runtime_error'
[ur_ros2_control_node-1]   what():  Wrong state or command interface configuration.
[ur_ros2_control_node-1] missing state interfaces:
[ur_ros2_control_node-1]
[ur_ros2_control_node-1] missing command interfaces:
[ur_ros2_control_node-1] ' force_mode/task_frame_x '	' force_mode/task_frame_y '	' force_mode/task_frame_z '	' force_mode/task_frame_rx '	' force_mode/task_frame_ry '	' force_mode/task_frame_rz '	' force_mode/selection_vector_x '	' force_mode/selection_vector_y '	' force_mode/selection_vector_z '	' force_mode/selection_vector_rx '	' force_mode/selection_vector_ry '	' force_mode/selection_vector_rz '	' force_mode/wrench_x '	' force_mode/wrench_y '	' force_mode/wrench_z '	' force_mode/wrench_rx '	' force_mode/wrench_ry '	' force_mode/wrench_rz '	' force_mode/limits_x '	' force_mode/limits_y '	' force_mode/limits_z '	' force_mode/limits_rx '	' force_mode/limits_ry '	' force_mode/limits_rz '	' force_mode/type '	' force_mode/disable_cmd '	' force_mode/force_mode_async_success '	' force_mode/damping '	' force_mode/gain_scaling '
[robot_state_publisher-5] [INFO] [1694776349.969780941] [robot_state_publisher]: got segment base
[robot_state_publisher-5] [INFO] [1694776349.972263852] [robot_state_publisher]: got segment base_link
[robot_state_publisher-5] [INFO] [1694776349.973768817] [robot_state_publisher]: got segment base_link_inertia
[robot_state_publisher-5] [INFO] [1694776349.975891055] [robot_state_publisher]: got segment flange
[robot_state_publisher-5] [INFO] [1694776349.975927767] [robot_state_publisher]: got segment forearm_link
[robot_state_publisher-5] [INFO] [1694776349.975951133] [robot_state_publisher]: got segment ft_frame
[robot_state_publisher-5] [INFO] [1694776349.975968136] [robot_state_publisher]: got segment shoulder_link
[robot_state_publisher-5] [INFO] [1694776349.975980562] [robot_state_publisher]: got segment tool0
[robot_state_publisher-5] [INFO] [1694776349.975991146] [robot_state_publisher]: got segment upper_arm_link
[robot_state_publisher-5] [INFO] [1694776349.976002979] [robot_state_publisher]: got segment world
[robot_state_publisher-5] [INFO] [1694776349.976014429] [robot_state_publisher]: got segment wrist_1_link
[robot_state_publisher-5] [INFO] [1694776349.976025884] [robot_state_publisher]: got segment wrist_2_link
[robot_state_publisher-5] [INFO] [1694776349.976044511] [robot_state_publisher]: got segment wrist_3_link
[ERROR] [rviz2-6]: process has died [pid 206, exit code -6, cmd '/opt/ros/humble/lib/rviz2/rviz2 -d /workspace/ros_ws_ur_driver/install/ur_description/share/ur_description/rviz/view_robot.rviz --ros-args -r __node:=rviz2'].
[ERROR] [ur_ros2_control_node-1]: process has died [pid 196, exit code -6, cmd '/workspace/ros_ws_ur_driver/install/ur_robot_driver/lib/ur_robot_driver/ur_ros2_control_node --ros-args --params-file /tmp/launch_params_mjn77s9q --params-file /workspace/ros_ws_ur_driver/install/ur_robot_driver/share/ur_robot_driver/config/ur5e_update_rate.yaml --params-file /tmp/launch_params_1hzy1xfp'].
[spawner-8] [INFO] [1694776352.580198848] [spawner_joint_state_broadcaster]: Waiting for '/controller_manager' node to exist
[spawner-9] [INFO] [1694776352.702013811] [spawner_io_and_status_controller]: Waiting for '/controller_manager' node to exist
[spawner-7] [INFO] [1694776352.804029969] [spawner_scaled_joint_trajectory_controller]: Waiting for '/controller_manager' node to exist
[spawner-10] [INFO] [1694776352.832444689] [spawner_speed_scaling_state_broadcaster]: Waiting for '/controller_manager' node to exist
[spawner-12] [INFO] [1694776352.839343608] [spawner_forward_position_controller]: Waiting for '/controller_manager' node to exist
[spawner-11] [INFO] [1694776352.854625189] [spawner_force_torque_sensor_broadcaster]: Waiting for '/controller_manager' node to exist

Accept Public visibility

[X] I agree to make this context public

yes, thanks for notifying!
Apart from this being a problem, obviously, the repos files need updates, since we use the humble branch of the description for humble.

This has been fixed in #802 -> closing.


Remove expired collaborator from Terraform file/s for emileswarts

Hi there
This is the GitHub-Collaborator repository bot.
The collaborator emileswarts review date has expired for the file/s contained in this pull request.
Either approve this pull request, modify it or delete it if it is no longer necessary.

Will be replaced by a new PR to update review dates.


Parcelable support

It will be cool to support Parcelable
I'm using https://github.com/nsk-mironov/smuggler and do not want to write serialization by myself

Hi.
Thanks for feature proposal. I will investigate this, but yes, right now I'm not have any solution to solve this kind of thing.
Regards.


Remove input queue from branch - unnecessary, as first component will have its own input queue.

merged into the v0.30.alpha dev branch


Port singleton stores over to Postgres

Description
Create a new singleton store pattern in Postgres and port over the 3 singleton stores from Bolt over
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
CI, plus unit tests, plus manual

No, they are just copied from the singleton store, but I guess I could actually just modify the generator now that I think about it (facepalm). Will do that

These are Bolt stores, I don't think it's a big deal tbh


Cache hashcode for TypeSignature class

Fix #5780
This improves the cpu cost of building hashmaps and hashsets of
objects that depend on AbstractType#hashCode, by caching the hash
value for TypeSignature objects which is expensive to compute
repeatedly.

Unrelated failure: https://github.com/prestosql/presto/issues/5928


Bump browserslist so that the latest NodeJS versions are available

Description
When getting @shopify/polaris ready for v11. I noticed that browserslist could not find NodeJS ^v16.17. This PR updates browserslist so that it hopefully bumps the node-releases npm package and support.
After doing some investigation I don't think this is blocking our NodeJS upgrade.  This has no effect on packages that depend upon browserslist-config. Thus it doesn't warrant any changelogs either because the config you've touched is local just to this repository.
As it sounds like you've already discovered, Polaris is free to update the versions of browserslist/node-releases by modifying its own yarn.lock.
I'm going to close this as the change isn't required.


Updated to 1.4.0 format!

Russ language for love. <3

Btw Martin, i have one question, how about to add @KiskaUWU in credits? He rearranged the right words, and very helped me, so, like this people can be added in credits in mod?


Add cognizant.com in the list looking for an Incident Manager

Guideline for CONTRIBUTING
https://www.linkedin.com/jobs/view/2918121287/?refId=VGChBerPRc2q7N7UQFC5zA%3D%3D

Hey @icaman, you can open a PR to add a new company. Read the https://github.com/italiaremote/awesome-italia-remote/blob/main/CONTRIBUTING.md for more info.


Update navBarStyle to include borderBottomWidth & borderBottomColor

Please allow for the borderBottomWidth & the borderBottomColor to be set in the navBarStyle property, including renderNavBarStyle(navBarStyle)

This is not natively supported... There are several workarounds, but none of them conquered me.

Sounds good 👍

hidesShadow: Indicates whether to hide the navigation 1px hairline shadow. (Default false) (iOS Only)
added hidesShadow


Errors when attempting to use GCS volumes in cloud-run-v2

Describe the bug
Cannot use the new support for GCS volumes in cloud-run-v2.  Is it broken, or am I doing it wrong?
It was added:
https://github.com/GoogleCloudPlatform/cloud-foundation-fabric/pull/2638
Environment
output from `terraform -version`

❯ terraform -version
OpenTofu v1.8.4
on darwin_amd64
+ provider registry.opentofu.org/hashicorp/google v6.11.1
+ provider registry.opentofu.org/hashicorp/google-beta v6.11.1

output from `git rev-parse --short HEAD`

❯ git rev-parse --short HEAD
f1b074b5

To Reproduce
Steps to reproduce the behavior
Add a "volumes" stanza to a cloud-run-v2 module-resource in terraform:
  volumes = {
    xxx = {
      gcs = {
        bucket = "my-bucket-name"
        is_read_only = false
      }
    }
  }

Expected behavior
A clear and concise description of what you expected to happen.
Cloudrun to be created with this volume.
It works fine with the underlying provider:
# WORKS
resource "google_cloud_run_v2_service" "spam" {
  name = "dummy1"
  location     = "us-central1"
  launch_stage = "BETA"
  project = var.project_id

  template {
    execution_environment = "EXECUTION_ENVIRONMENT_GEN2"

    containers {
      image = "us-docker.pkg.dev/cloudrun/container/hello"
      volume_mounts {
        name       = "bucket"
        mount_path = "/var/www"
      }
    }

    volumes {
      name = "bucket"
      gcs {
        bucket = "my-bucket-name"
        read_only = false
      }
    }
  }
}

So problem seems to be in service.tf https://github.com/GoogleCloudPlatform/cloud-foundation-fabric/blob/master/modules/cloud-run-v2/service.tf#L208 which may be generating incorrect dynamic content??  I don't know how to debug this.
    dynamic "volumes" {
      for_each = var.volumes
      content {
        name = volumes.key
        dynamic "gcs" {
          for_each = volumes.value.gcs == null ? [] : [""]
          content {
            bucket    = volumes.value.bucket
            read_only = volumes.value.is_read_only
          }
        }
      }
    }
  }

Result
Terraform output and/or error messages
Plan: 1 to add, 1 to change, 1 to destroy.
╷
│ Error: Unsupported attribute
│
│   on ../../../modules/cloud-run-v2/service.tf line 211, in resource "google_cloud_run_v2_service" "service":
│  211:             bucket    = volumes.value.bucket
│     ├────────────────
│     │ volumes.value is object with 5 attributes
│
│ This object does not have an attribute named "bucket".
╵
╷
│ Error: Unsupported attribute
│
│   on ../../../modules/cloud-run-v2/service.tf line 212, in resource "google_cloud_run_v2_service" "service":
│  212:             read_only = volumes.value.is_read_only
│     ├────────────────
│     │ volumes.value is object with 5 attributes
│
│ This object does not have an attribute named "is_read_only".
╵```

**Additional context**
Add any other context about the problem here

This looks like a bug, let me take a loog at it.

Should it be using each.key and each.value rather than volumes.key and volumes.value?    #noob

Should it be using each.key and each.value rather than volumes.key and volumes.value? #noob

Close :-)

Cool! Will try that in the morning.

The fix (mostly) worked for me. Needed to add gen2_execution_environment = true also (which isn't in the example code)

Thank you!


Add render test for the dashboard

Not resource-related; consider using a different command for this (or combination; ask question for type of test)


[android] Linking.getInitialURL() throws error

Description
On android when trying to call Linking.getInitialURL() I always get [Error: Could not get the initial URL : Attempt to invoke virtual method 'java.lang.String android.content.Intent.getAction()' on a null object reference] error on android. On iOS it works.
The code:
import { Linking } from 'react-native';

try {
  const res = await Linking.getInitialURL();
    console.log(res);
  } catch (e) {
    console.log(e);
}

I mention that I added the following intent-filter to AndroidManifest.xml:
        <intent-filter>
          <action android:name="android.intent.action.VIEW" />
          <category android:name="android.intent.category.DEFAULT" />
          <category android:name="android.intent.category.BROWSABLE" />
          <data android:scheme="myapp" />
        </intent-filter>

Version
0.68.2
Output of npx react-native info
System:
OS: macOS 12.3.1
CPU: (12) x64 Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz
Memory: 413.03 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 16.15.0 - /usr/local/bin/node
Yarn: 1.22.18 - /usr/local/bin/yarn
npm: 8.5.5 - /usr/local/bin/npm
Watchman: Not Found
Managers:
CocoaPods: 1.11.3 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.4, iOS 15.4, macOS 12.3, tvOS 15.4, watchOS 8.5
Android SDK: Not Found
IDEs:
Android Studio: 2021.1 AI-211.7628.21.2111.8193401
Xcode: 13.3.1/13E500a - /usr/bin/xcodebuild
Languages:
Java: 11.0.2 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: 0.68.2 => 0.68.2
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce

Create a bare react-native project
Try to run:

import { Linking } from 'react-native';

try {
  const res = await Linking.getInitialURL();
    console.log(res);
  } catch (e) {
    console.log(e);
}

for example inside useEffect hook.

Run the app on android

Snack, code example, screenshot, or link to a repository
https://snack.expo.dev/8OiPWgvkM

Hey, I am having the same issue, did you find any fix to this? Thanks

I managed to fix the issue. I was using the https://github.com/ajith-ab/react-native-receive-sharing-intent library. I fixed it using this comment, which was setting the intent to null. Hope it helps somebody.

@Yooooomi We also use the same library, thank you for sharing your findings, we'll try it out and update in this thread 😄

@Yooooomi can you post your work somewhere with demo app? I'm attempting to use that library but it is hanging on splash screen

This is the version we use: https://github.com/kraaft-co/react-native-receive-sharing-intent.
Application stays on splash screen if I have hermes disabled.

@Yooooomi thanks I'll try that out

@Yooooomi Thank you so much, that was the issue for us as well

Hello, I'm also facing the same, any solution so far?


Update testing instructions for Datastore.

Coverage decreased (-0.004%) to 80.937% when pulling 211dfd2592021b12a5cadd9e31ae70bf4b2199f2 on shinfan:dev into a27d8c7ff24c282b2a7bf943dfec039d7ef02f72 on GoogleCloudPlatform:master.

LGTM


[offline test] reorganize to use less RAM

done in https://github.com/water111/jak-project/pull/895


[DC-3175] Update the vocabulary QC notebook

Replacing this PR and branch with #1585

Closing this PR. Another replaces it.


Config.php not found

Hello all,
I seem to be stuck getting nginx to display my YOURLS page. The nginx error.log reads:
*1 directory index of "/var/www/site/" is forbidden, client: IP.IP.IP.IP, server: site.com, request: "GET / HTTP/1.1", host: "site.com"
I've altered some information for privacy.
When I head to my site, I get a 403 message. However, if I enable autoindex in /etc/nginx/sites-available/myYOURLS.com (which is symlinked to /sites-enabled/), everything shows up.
The permissions are 755 on /var/www/site and www-data:www-data owns var/www.
My /sites-available/ config is this:
server {
listen 80;
server_name site.com;
root /var/www/site.com;
#index index.php;
location / {
try_files $uri $uri/ /yourls-loader.php;
#autoindex on;
expires 14d;
add_header Cache-Control 'public';
}
location ~ \.php$ {
  try_files $uri =404;
  fastcgi_split_path_info ^(.+\.php)(/.+)$;
  fastcgi_pass unix:/var/run/php/php7.0-fpm-ubuntu.sock;
  fastcgi_index index.php;
  fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
  include fastcgi_params;

}
}
Ubuntu 16.04.3
nginx 1.12.1

YOURLS version: Latest. I cloned it (again) today.

Plugins enabled: None

PHP version: 7.0

Most of the above config came from the YOURLS wiki. I've tried explicitly specifying the yourls-loader.php location to no avail. Although I'm honestly not quite sure what the does. I'm sure I'm missing something simple, but this I'm very new to this.
No quite sure where I need to go from here. Thanks in advance!

Duplicate of #2311
Definitely something wrong with #2294, ping @ozh for review.

Rereading your issue and catch that line:
  fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;

You need to change SCRIPT_FILENAME  here to point to your yourls-loader.php.
BTW, testing and everything works perfectly for me, even from scratch. Sorry to ping for nothing @ozh 😇 😉

+1

On windows, this error is not present.
On Linux, I changed this file
includes/YOURLS/Config/Config.php
here are the changes
public function __construct($config = false) {         $this->set_root(realpath(dirname(dirname(dirname(dirname(__FILE__))))) );         //$this->fix_win32_path(realpath(__DIR__ . '../../../..')) //This does not work on linux but on windows         $this->set_config($config);     }
This now works for me.
Hope this will helps in the bug correction during next update....

@KabataMacharia Good catch, thanks for your feedback! 👍
Can you submit a pull request with this change? Thx!

Update.
I pulled the latest update but am still having issues. I stopped nginx and installed Apache2 today. I get a 403 forbidden error on the page and this output in the Apache2 error.log:
AH01276: Cannot serve directory /var/www/site.com/: No matching DirectoryIndex (index.php,index.html) found, and server-generated directory index forbidden by Options directive
If I go to /admin in a browser, (or anywhere besides the root)m, the index.php displays as plain text.
I've purged and reinstalled PHP as well in case there was an issue there.
sites-enabled config:
<VirtualHost *:80>
   ServerName urls.magicmemories.com
   DocumentRoot /var/www/site.com
   DirectoryIndex index.php index.html
   <Directory /var/www/site.com/>
      AllowOverride All
      Order Deny,Allow
      Allow from all
   </Directory>
</VirtualHost>

.htaccess:
#BEGIN YOURLS
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^.*$ /yourls-loader.php [L]
</IfModule>
#END YOURLS
#BEGIN INDEX-FIX
Options -Indexes
DirectoryIndex index.php index.html
#END INDEX-FIX

I pulled the latest version today, and am having this issue too:
2017/11/03 19:51:30 [error] 5750#5750: *1990 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Uncaught exception 'YOURLS\Exceptions\ConfigException' with message 'Cannot find config.php. Please read the readme.html to learn how to install YOURLS' in /var/www/YOURLS/includes/YOURLS/Config/Config.php:89
Stack trace:
#0 /var/www/YOURLS/includes/load-yourls.php(18): YOURLS\Config\Config->find_config()
#1 /var/www/YOURLS/admin/index.php(3): require_once('/var/www/YOURLS...')
#2 {main}
  thrown in /var/www/YOURLS/includes/YOURLS/Config/Config.php on line 89" while reading response header from upstream, client: REDACTED, server: ln.demu.red, request: "GET /admin/ HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "ln.demu.red"

I'm also having this same issue
nginx version: nginx/1.13.6 built by gcc 6.3.0 20170516 (Debian 6.3.0-18) built with OpenSSL 1.1.0f  25 May 2017 TLS SNI support enabled configure arguments: --prefix=/etc/nginx --sbin-path=/usr/sbin/nginx --modules-path=/usr/lib/nginx/modules --conf-path=/etc/nginx/nginx.conf --error-log-path=/var/log/nginx/error.log --http-log-path=/var/log/nginx/access.log --pid-path=/var/run/nginx.pid --lock-path=/var/run/nginx.lock --http-client-body-temp-path=/var/cache/nginx/client_temp --http-proxy-temp-path=/var/cache/nginx/proxy_temp --http-fastcgi-temp-path=/var/cache/nginx/fastcgi_temp --http-uwsgi-temp-path=/var/cache/nginx/uwsgi_temp --http-scgi-temp-path=/var/cache/nginx/scgi_temp --user=nginx --group=nginx --with-compat --with-file-aio --with-threads --with-http_addition_module --with-http_auth_request_module --with-http_dav_module --with-http_flv_module --with-http_gunzip_module --with-http_gzip_static_module --with-http_mp4_module --with-http_random_index_module --with-http_realip_module --with-http_secure_link_module --with-http_slice_module --with-http_ssl_module --with-http_stub_status_module --with-http_sub_module --with-http_v2_module --with-mail --with-mail_ssl_module --with-stream --with-stream_realip_module --with-stream_ssl_module --with-stream_ssl_preread_module --with-cc-opt='-g -O2 -fdebug-prefix-map=/data/builder/debuild/nginx-1.13.6/debian/debuild-base/nginx-1.13.6=. -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fPIC' --with-ld-opt='-specs=/usr/share/dpkg/no-pie-link.specs -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -pie'
$ php7.0 -v PHP 7.0.19-1 (cli) (built: May 11 2017 14:04:47) ( NTS ) Copyright (c) 1997-2017 The PHP Group Zend Engine v3.0.0, Copyright (c) 1998-2017 Zend Technologies     with Zend OPcache v7.0.19-1, Copyright (c) 1999-2017, by Zend Technologies
$ mysql -V mysql  Ver 15.1 Distrib 10.1.26-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2

Guys, this issue is a mess. There are nginx problems and then "config not found" problems, all mixed.
nginx : is it working with 1.7.2 downloaded from the archive?
Config not found: please try patch from PR 2314
Closing this. Feel free to submit another precise issue with one clearly described problem. Thanks all.

The git pull I did today has restored functionality. Thanks.

Regarding the original issue, I know this is closed but I finally got it working.
I ended up changing:
public function __construct($config = false) {         $this->set_root(realpath(dirname(dirname(dirname(dirname(__FILE__))))) );         //$this->fix_win32_path(realpath(__DIR__ . '../../../..')) //This does not work on linux but on windows         $this->set_config($config);  }
To this:
public function __construct($config = false) {         **$this->set_root('/path/to/doc/root');**         //$this->fix_win32_path(realpath(__DIR__ . '../../../..')) //This does not work on linux but on windows         $this->set_config($config);  }
Now it's working!


Bug of "version"

Describe the bug
A clear and concise description of what the bug is.
version field can not input "0"

@lxt302 Thanks for reporting this. This behavior was reported already in issue #14 and will be addressed in the next release.


Reflect current state of properties in readme.

Remove security.oauth2.admin.* properties, rename security.oauth2.pivotal-cla.token to security.oauth2.pivotal-cla.tokenSecret.

Thanks for the PR! This is now merged into master


Add GoogleTagManager support

What does this do?
This adds Google Tag Manager support to Canopy. Implementers can now add a container id through the vendor.googleTagManager.gtmId property. This is then rendered at the app level through the Next.js _app.tsx and will be present on all pages.
{
  "collection": "https://iiif.io/api/cookbook/recipe/0032-collection/collection.json",
  "vendor": {
    "googleTagManager": {
      "gtmId": "GTM-XXXXXXXX"
    }
  }
}

Users can also opt for direct Google Analytics support:
{
  "collection": "https://iiif.io/api/cookbook/recipe/0032-collection/collection.json",
  "vendor": {
    "googleAnalytics": {
      "gaId": "G-XXXXXXXXXX"
    }
  }
}

What type of change is this?

[ ] 🐛 Bug fix (non-breaking change addressing an issue)
[x] ✨ New feature or enhancement (non-breaking change which adds functionality)
[ ] 🧨 Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] 🚧 **Maintenance or refinement of codebase structure (ex: dependency updates)
[ ] 📘 Documentation update

Additional Notes
Please include any extra notes here.

Just wondering: do you think we should document vendor stuff in the readme or in the sample or default configs? Or are you thinking about adding a how to to docs? Seems like the sort of thing that people might look for.

Was planning to document fully in the docs repo. A bit two-phasey but seems like the right spot for it.


Fix small memory leak

When I ran the memory leaks tool in Instruments, dragging the clock face was sometimes leaking memory. I don't really understand why — possibly a bug in the OS doing event processing. Anyway, I re-wrote a small amount of code to just manually track whether a drag has occurred and use that information on mouseUp. There should be no change in user-visible behavior.

💯


Sorin ionescu master

Please be sure to check out our contributing guidelines
before submitting your pull request.
Fixes #
Proposed Changes

I'm sorry. I made a mistake


removing args on rhel9/redis-6 image

Related to same issue behind https://github.com/securesign/scaffolding/pull/125 and depends on it.
Dependency of certified helm charts (only use certified images check). If the implementation strategy gets approved by lance, then we will swap out the image that gets build from RHTAP once scaffolding #125 gets merged. Because of that ...
/hold

/unhold


Updated docs page

fixes #1156
Thank you for your contribution to the IC Developer Portal.
Before submitting your Pull Request, please make sure that:

[X] You have updated the .github/CODEOWNERS file according to your changes.
[X] You have registered new documents to /sidebars.js if any.

Thank you very much!


Please migrate your plugin to Nativescript 7

Is it someone working in migrate the project to NS7.
I've tried to migrate, but always an error on  this class
@NativeClass()
class BluetoothManagerDelegate extends NSObject implements CBCentralManagerDelegate {
// Note: This ObjCProtocols is needed.
public static ObjCProtocols = [CBCentralManagerDelegate];
private resolve: any;
static new(): BluetoothManagerDelegate {
return super.new();
}
initWithResolverCallback(resolve: any) {
this.resolve = resolve;
return this;
}
The error is
error TS2304: Cannot find name 'NativeClass'.
I migrated other 7 plugins, but I don't have this error

same problem here :( any hope?

Hi guys. I am running busy with other projects these days. I would like to support you all. I do not promise anything, but I will try.

@mm-psymbl @limux82 I have upgraded the plugin to NS 7.0. Please note that I have not tested on iOS and Android devices. The latest version is 3.0.0. The code is also updated as well.
I appreciate if you could spare some time in testing the plugin.
Have a great morning and Sunday :)

Hey, thanks a lot of making this awesome plugin and updating to NS 7. Unfortunately we are still running into this error on the latest package version 3.3.1 on iOS 14.3.
***** Fatal JavaScript exception - application has been terminated. *****
2021-03-04 15:45:16.278662-0600
NativeScript encountered a fatal error: Uncaught ReferenceError: NativeClass is not defined
at
	../node_modules/nativescript-dna-deviceinfo/deviceinfo.js

@neil-119  I am glad to know that you are using the plugin. The problem which you have described is not reproducible
at my end.
I have a demo repository that you can try out and check if the same problem persists at your end. The link to the repo is: https://github.com/DeepakArora76/JSDeviceInfoDemo
It is really hard for me to see the problem. Supplementary information will help me diagnose the hidden issue.

What is the framework that you are targeting?
What does your development env look like?

In the meanwhile, I like you to update your toolchain, and the OS and Xcode.
I have Xcode 12.4, Build version 12D4e. The OS is MacOS Big Sur Version 11.2.1.
Below is the output of the  ns doctor command.
Deepak$ ns doctor
You have both a nativescript.config.js and nativescript.config.ts file. Defaulting to nativescript.config.ts.
✔ Getting environment information
No issues were detected.
✔ Your ANDROID_HOME environment variable is set and points to correct directory.
✔ Your adb from the Android SDK is correctly installed.
✔ The Android SDK is installed.
✔ A compatible Android SDK for compilation is found.
✔ Javac is installed and is configured properly.
✔ The Java Development Kit (JDK) is installed and is configured properly.
✔ Xcode is installed and is configured properly.
✔ xcodeproj is installed and is configured properly.
✔ CocoaPods are installed.
✔ CocoaPods update is not required.
✔ CocoaPods are configured properly.
✔ Your current CocoaPods version is newer than 1.0.0.
✔ Python installed and configured correctly.
✔ The Python 'six' package is found.
✔ Xcode version 12.4.0 satisfies minimum required version 10.
✔ Getting NativeScript components versions information...
I will be looking forward to your reply.

@neil-119  Any update on your progress?

@neil-119 Hi, I can see the problem with my sample app. I am looking into it.
***** Fatal JavaScript exception - application has been terminated. *****
NativeScript encountered a fatal error: Uncaught Error: Building UI from XML. @app-root.xml:1:1

NativeClass is not defined

@neil-119 Hi :) Thank you for reporting the issue. The problem was my end while building the plugin. I missed the setup that patches TS. There is a command that I must run before packing and publish the plugin. The command is "npm run setup", and I missed to fire that :)
I have released a new plugin:  3.5.0: Fixed runtime errors related to "NativeClass is not defined" observed on NativeScript Version 7 apps. The fix will likely benefit iOS apps.
I hope that this release fixes the problem.
Please test and post your feedback.


Use forward entry setup

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 96.116%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2425

Relevant Lines:
2523

💛  - Coveralls


Static Language Levels

Is your feature request related to a problem? Please describe.
Language Levels are static and do not need to be managed in the DB.
Describe the solution you'd like
Replace with an ENUM
Describe alternatives you've considered
None
Additional context
None
References

https://app.forecast.it/project/P-223/scoping/T3549

Estimations:
API: 3-4h, Frontend: 3-4h
Total: 6-8h, CHF 1’080 – CHF 1’440


[Template]: Charts Generator

Title
Chaarts Generator for Appsmith Custom Charts
Objective
This app generates the JSON data for custom chart types, based on the user inputs.
It is meant to be used as a quick way to get started with a custom chart, with all options outlined. This allows users to quickly see how these options are processed, and they can easily copy/paste or build their own functions.
It has a single page, with a select / list of available charts, and the pre-populated fields for it.
Users can pick a chart type, and its respective fields will be visible and pre-populated.
Then, users can add their own data to these fields, or they can use some demo data.
When users click on "Get JSON", a modal opens. In it there is a preview of that chart along with the entire JSON code ready for copy/paste.
Wireframes
https://app.appsmith.com/applications/6279532b0b47255c280c2037/pages/6279532b0b47255c280c203d
Validation criteria

User should be able to pick a chart style from the select or from the list
User should be able to add their own data in the JSON form element
User should have their chart JSON code generated when they click on "Get JSON"

Use case
Software Development
Industry
Technology
Data sources
Any

This template request has been moved here - https://app.appsmith.com/app/request-templates/request-list-6241c12fc99df2369931a714


Query role

Fixes #200 or at least implements the last of the requested handlers/rest methods in that issue.
Depends on #208 which after merge into unstable will make this PR comprised of just one commit.

/cc @ethanfrey

Addressed your comments @ebuchman, however as spoken with and examined with @ethanfrey offline, some is up when we try to do node.ABCIQuery("/key", key, true) so this can hold off until renaming is done.

@ethanfrey could we add more context as to why we close PRs while doing them? I ask for this so that in the future when revisiting them, we can know what's up and why we closed them.

Sorry for the confusion.  I think this happened during the rename.
You are more than welcome to rebase and update all imports to Sdk and reopen it.

Oh, yeah, I deleted the unstable branch in this repo after merging it into develop. That would have auto-closed it.


Support the expanded change_t_via_interpolation! interface

Checklist

[ ] Appropriate tests were added
[ ] Any code changes were done in a way that does not break public API
[ ] All documentation related to code changes were updated
[ ] The new code follows the
contributor guidelines, in particular the SciML Style Guide and
COLPRAC.
[ ] Any new documentation only uses public API

Additional context
Add any other context about the problem here.

@oscardssmith can you look into what happened in the preconditioner test?


Add accesslog async writer

What does this PR do?
Add a async log writer for access logs.

Motivation
On my current project, we use traefik and recently we activate access logs. When i checked the overhead this functionality, i realize that we lost a lot! So i tried to figure why and i found that we use sync io.Writer.
Small benchs:
Base configuration:
[entryPoints]
    [entryPoints.http]
       address = ":8080"
[accessLog]
filePath = 'test'

Without accesslogs from hey:
$ hey -n 200000 http://<IP_ADDRESS>:8080/test
Summary:
  Total:	6.4238 secs
  Slowest:	0.0333 secs
  Fastest:	0.0002 secs
  Average:	0.0016 secs
  Requests/sec:	31134.0972

  Total data:	3800000 bytes
  Size/request:	19 bytes

Response time histogram:
  0.000 [1]	|
  0.003 [192996]	|∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎
  0.007 [6398]	|∎
  0.010 [446]	|
  0.013 [107]	|
  0.017 [39]	|
  0.020 [9]	|
  0.023 [2]	|
  0.027 [0]	|
  0.030 [0]	|
  0.033 [2]	|

Latency distribution:
  10% in 0.0008 secs
  25% in 0.0011 secs
  50% in 0.0014 secs
  75% in 0.0018 secs
  90% in 0.0024 secs
  95% in 0.0030 secs
  99% in 0.0052 secs

Details (average, fastest, slowest):
  DNS+dialup:	0.0000 secs, 0.0002 secs, 0.0333 secs
  DNS-lookup:	0.0000 secs, 0.0000 secs, 0.0000 secs
  req write:	0.0000 secs, 0.0000 secs, 0.0191 secs
  resp wait:	0.0013 secs, 0.0001 secs, 0.0232 secs
  resp read:	0.0001 secs, 0.0000 secs, 0.0299 secs

With accesslogs:
$ hey -n 200000 http://<IP_ADDRESS>:8080/test
Summary:
  Total:	20.0173 secs
  Slowest:	0.0261 secs
  Fastest:	0.0002 secs
  Average:	0.0050 secs
  Requests/sec:	9991.3647

  Total data:	3800000 bytes
  Size/request:	19 bytes

Response time histogram:
  0.000 [1]	|
  0.003 [2732]	|∎
  0.005 [154054]	|∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎
  0.008 [32652]	|∎∎∎∎∎∎∎∎
  0.011 [7629]	|∎∎
  0.013 [2026]	|∎
  0.016 [556]	|
  0.018 [177]	|
  0.021 [148]	|
  0.024 [19]	|
  0.026 [6]	|

Latency distribution:
  10% in 0.0041 secs
  25% in 0.0042 secs
  50% in 0.0045 secs
  75% in 0.0053 secs
  90% in 0.0063 secs
  95% in 0.0081 secs
  99% in 0.0115 secs

Details (average, fastest, slowest):
  DNS+dialup:	0.0000 secs, 0.0002 secs, 0.0261 secs
  DNS-lookup:	0.0000 secs, 0.0000 secs, 0.0000 secs
  req write:	0.0000 secs, 0.0000 secs, 0.0023 secs
  resp wait:	0.0049 secs, 0.0002 secs, 0.0260 secs
  resp read:	0.0000 secs, 0.0000 secs, 0.0038 secs

With async log writer:
$ hey -n 200000 http://<IP_ADDRESS>:8080/test
Summary:
  Total:	15.1209 secs
  Slowest:	0.0769 secs
  Fastest:	0.0002 secs
  Average:	0.0038 secs
  Requests/sec:	13226.7404

  Total data:	3800000 bytes
  Size/request:	19 bytes

Response time histogram:
  0.000 [1]	|
  0.008 [197458]	|∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎
  0.016 [2258]	|
  0.023 [236]	|
  0.031 [22]	|
  0.039 [17]	|
  0.046 [6]	|
  0.054 [1]	|
  0.062 [0]	|
  0.069 [0]	|
  0.077 [1]	|

Latency distribution:
  10% in 0.0032 secs
  25% in 0.0033 secs
  50% in 0.0034 secs
  75% in 0.0042 secs
  90% in 0.0048 secs
  95% in 0.0053 secs
  99% in 0.0084 secs

Details (average, fastest, slowest):
  DNS+dialup:	0.0000 secs, 0.0002 secs, 0.0769 secs
  DNS-lookup:	0.0000 secs, 0.0000 secs, 0.0000 secs
  req write:	0.0000 secs, 0.0000 secs, 0.0205 secs
  resp wait:	0.0037 secs, 0.0002 secs, 0.0767 secs
  resp read:	0.0000 secs, 0.0000 secs, 0.0297 secs

More

[ ] Added/updated tests
[x] Added/updated documentation: Access Logs

Additional Notes

I think that there is more to do to optimize access logs overhead but it's a first step.

Replaced with https://github.com/containous/traefik/pull/3152


Match alternate spellings of ꝡ in head

This makes a query for wao or vao or yao bring up ꝡao.

Thanks for this patch as well :) Been thinking how to implement this the most ergonomic way and this seems to be it.
Closes #28.


GPU kLoop fusion fully vectorization optimization.

vectorizes both load and store.
vectorizes some fp16 computation instructions.
interleaves computation instructions that are not vectorized.

Another question, vectorization increases pressure on register usage, will it bring regression in some case?

Another question, vectorization increases pressure on register usage, will it bring regression in some case?

No worry for register pressure of kLoop fusion. Even given a high vector-size, it will use a very small set of registers due to the short lift time of each register.


ERROR: error loading package 'paxml'

I'm trying to run the PAX code in this repo:
I installed the prerequisites as mentioned in the repo:
python3 -m pip install -U pip
python3 -m pip install paxml praxis
cd paxml
bazel run -c opt --define=pax_task=lm \
    main -- \
    --exp=lm.decoder.ptb.PTBCharTransformerSmallSgd \
    --job_log_dir=/tmp/jax_log_dir/exp01 --alsologtostderr

To start training, I got the command line from here: https://github.com/google/paxml/blob/main/paxml/main.py#L19-L22
bazel run -c opt \
  third_party/py/paxml/tasks/lm/params:main -- \
  --exp=bert.BertAdamL4H128 \
  --job_log_dir=/tmp/jax_log_dir/exp01 --alsologtostderr

I'm encountering the following issue:
ERROR: Skipping 'paxml': error loading package 'paxml': Every .bzl file must have a corresponding package, but '//praxis:build-visibility.bzl' does not have one. Please create a BUILD file in the same or any parent directory. Note that this
BUILD file does not need to do anything except exist.
WARNING: Target pattern parsing failed.
ERROR: error loading package 'paxml': Every .bzl file must have a corresponding package, but '//praxis:build-visibility.bzl' does not have one. Please create a BUILD file in the same or any parent directory. Note that this BUILD file does not need to do anything except exist.
INFO: Elapsed time: 0.750s
INFO: 0 processes.

Though I see the BUILD is present here: https://github.com/google/paxml/blob/main/paxml/BUILD
Is there anything I'm doing wrong? Any suggestions to get it running?

Hi,
Thanks for the report.
We haven't pushed any library content on PyPi yet, so I doubt you've installed the library that way.
I'm not sure why you're getting this error message.
But as a temporary workaround and until we deploy proper packages and instructions, could you:

remove the problematic file build-visibility.bzl and any reference to it in the BUILD file.
update the visibility to a default value such as "//visibility:public"

We haven't pushed any library content on PyPi yet, so I doubt you've installed the library that way.

Interesting, the readme says to do that ...
https://github.com/google/paxml/blob/93715a13f4f034959b8e7ac1353dda789e785402/README.md?plain=1#L29-L32
@laurentes is there instructions written somewhere on how we can build and run PAX?

@laurentes
re: "remove the problematic file build-visibility.bzl and any reference to it in the BUILD file."

I commented out all lines here: Is this right?

paxml/BUILD:#load("//praxis:build-visibility.bzl", "JAX_VISIBILITY")
paxml/tools/BUILD:load("//praxis:build-visibility.bzl", "JAX_VISIBILITY")
paxml/tasks/test/params/BUILD:load("//praxis:build-visibility.bzl", "JAX_VISIBILITY")
paxml/tasks/BUILD:load("//praxis:build-visibility.bzl", "JAX_VISIBILITY")
paxml/tasks/lm/BUILD:load("//praxis:build-visibility.bzl", "JAX_VISIBILITY")
paxml/tasks/lm/params/BUILD:load("//praxis:build-visibility.bzl", "JAX_VISIBILITY")

re: "update the visibility to a default value such as "//visibility:public""

Where do I need to add this? Could be provide me with the snippet/example? Thanks!

@sharathts I was replying to the specific error message that @mjsML was referencing above.
I assume the BUILD file(s) has something like the following:
load("//praxis:build-visibility.bzl", "JAX_VISIBILITY")

package(default_visibility = JAX_VISIBILITY)

If build-visibility.bzl is the problem, I would remove it and update such snippet into just this line:
package(default_visibility = ["//visibility:public"])

like here:
https://github.com/bazelbuild/bazel/blob/master/examples/cpp/BUILD#L1

Thanks for the suggestion. I did this with all BUILD files:
-load("//praxis:build-visibility.bzl", "JAX_VISIBILITY")
+#load("//praxis:build-visibility.bzl", "JAX_VISIBILITY")

-package(default_visibility = JAX_VISIBILITY)
+#package(default_visibility = JAX_VISIBILITY)
+package(default_visibility = ["//visibility:public"])

Now I get the following error:
ERROR: /workspace/pax/paxml/BUILD:232:22: no such package 'praxis': BUILD file not found in any of the following directories. Add a BUILD file to a directory to mark it as a package.
 - /workspace/pax/praxis and referenced by '//paxml:main_lib'
ERROR: Analysis of target '//paxml:main' failed; build aborted:
INFO: Elapsed time: 1.387s
INFO: 0 processes.
 Knowing that would be helpful to reproduce the issue you are facing. Thanks.

The targeted accelerator is a GPU.


Add peek and prettyPeek to JsonPath

From<EMAIL_ADDRESS>on November 21, 2013 16:41:20
Should print the value to the console but return an instance of JsonPath
Original issue: http://code.google.com/p/rest-assured/issues/detail?id=272

From<EMAIL_ADDRESS>on November 21, 2013 22:51:22
Status: Fixed


Using passwordless with Express & Mongoose

So I'm using Express & Mongoose for my application and I wanted to do the authentication myself but Passwordless seems the way to go. I love tokens:)!
But is it possible to just store the tokens in my already existing database?
Thanks

Hi! Yes, absolutely. Just connect to the existing MongoDB database using passwordless-mongostore. As long as you choose a collection that isn't in use yet it will just amend the database.

Florian, thanks for your response. Having a hard time installing bcrypt on Windows though. I wonder why this "passwordless" thing isn't used much more. Looks so convenient.

Thanks! You can use
https://www.npmjs.com/package/passwordless-mongostore-bcrypt-node which is
closer but doesn't need bcrypt
Florian
On Thu, May 7, 2015 at 9:15 AM Jessestr<EMAIL_ADDRESS>wrote:

Florian, thanks for your response. Having a hard time installing bcrypt on
Windows though. I wonder why this "passwordless" thing isn't used much
more. Looks so convenient.
—
Reply to this email directly or view it on GitHub
https://github.com/florianheinemann/passwordless/issues/54#issuecomment-99860352
.


Example project esp_zigbee_ota is not working (TZ-641)

Answers checklist.

[X] I have read the documentation ESP Zigbee SDK Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) and ESP Zigbee libs (esp-zboss-lib and esp-zigbee-lib) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
v5.2
esp-zigbee-lib version.
1.1.1
esp-zboss-lib version.
1.1.1
Espressif SoC revision.
ESP32-c6
What is the expected behavior?
I expected to run the example project and get a result similar to that described in the attached readme file. In particular, that between two devices firmware as client and server, a connection will be established and a file will be transferred.
What is the actual behavior?
The connection is not established, the file is not transferred.
Screenshot of the client log:

Screenshot of the server log:

Other projects using zigbee such as esp_zigbee_HA_sample and esp_zigbee_customized_devices work fine on these devices.
Steps to reproduce.

Git clone (https://github.com/espressif/esp-zigbee-sdk) repository
Open folder as a project
Run

More Information.
No response

@makkssim
Based on the server log you provided, it indicates that the server device has not been factory reset. This is likely because the device may have run other Zigbee examples, causing other network parameters to exist.
Therefore, please erase both the server and client devices. You can use the following commands to erase the devices before downloading the code:
idf.py -p <port>  erase-flash flash monitor

For more details, you can refer to ota_server/README

Did as you said. Nothing has changed. I am attaching a screenshot from cmd.

You forgot the "flash" and "monitor" after erase-flash
On Mon, 19 Feb 2024, 3:21 am makkssim, @.***> wrote:

Did as you said. Nothing has changed. I am attaching a screenshot from cmd.
image.png (view on web)
https://github.com/espressif/esp-zigbee-sdk/assets/70913058/12fa2135-1e3a-48ff-b6e3-e998cbdc69f9
—
Reply to this email directly, view it on GitHub
https://github.com/espressif/esp-zigbee-sdk/issues/249#issuecomment-1951375579,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABLYS3M6WP5GS2SNWEHT5L3YUITAFAVCNFSM6AAAAABDNQDZD2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJRGM3TKNJXHE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Nothing has changed, the log was just output to cmd instead of vs code in the terminal

thanks for the help


Bump Gradle FileEvents

This version uses SLF4J instead of JUL for logging.
Fixes #17396.
Reviewing cheatsheet
Before merging the PR, comments starting with

❌ ❓must be fixed
🤔 💅 should be fixed
💭 may be fixed
🎉 celebrate happy things

The merge queue build has failed. Click here to see all failures.


xgboost model predicts based on row indices of input data set when trained using gpu

Something strange happened when I was training an xgboost binary classification model using the gpu. After fitting on the training data set, it would make positive predictions based on the row indices of the input data set. So let's say making positive predictions on rows 1, 3, and 5 on the training set gives perfect precision (i.e. all true positives). If i feed in any other data set, the model would always make positive predictions on rows 1, 3, and 5. Below is a minimal working example to replicate the problem using the iris data set (multi-classification):
from xgboost import XGBClassifier
import sklearn.datasets
import numpy as np

kwargs = {'tree_method': 'gpu_exact'}
model = XGBClassifier(**kwargs)
X = sklearn.datasets.load_iris().data
Y = sklearn.datasets.load_iris().target
model.fit(X, Y)

#Predictions using the training data as input matrix
print('Training Data')
pred = model.predict(X)
p = np.array([round(x) for x in pred])
print('Predicted true positive indices (veriscolour): ' + str([i for i, x in enumerate((p==Y) & (p==1)) if x]))
print('Precision (veriscolour): ' + str(sum((p==1) & (p==Y))/float(sum(Y==1))))

#Now predict on an input zero-matrix
print('Zero-Matrix')
pred = model.predict(np.zeros(np.shape(X)))
p = np.array([round(x) for x in pred])
print('Predicted true positive indices (veriscolour): ' + str([i for i, x in enumerate((p==Y) & (p==1)) if x]))
print('Precision (veriscolour): ' + str(sum((p==1) & (p==Y))/float(sum(Y==1))))

#Now predict on the shuffled training data set
print('Shuffled training dataset')
indices = range(len(Y))
np.random.shuffle(indices)
X = X[indices, :]
Y = Y[indices]
pred = model.predict(X)
p = np.array([round(x) for x in pred])
print('Predicted true positive indices (veriscolour): ' + str([i for i, x in enumerate((p==Y) & (p==1)) if x]))
print('Precision (veriscolour): ' + str(sum((p==1) & (p==Y))/float(sum(Y==1))))

As you can see from the output, the indices of the predicted positives (veriscolour) in the first two data sets are the same, while the shuffled training data set returns a different (smaller) set of positives. However, if I change it to the 'exact' method instead of the 'gpu-exact' method, the problem seems to resolve. I am pretty certain I have installed CUDA correctly so I am wondering if my version of xgboost is out of date or if this is a known issue (I can't seem to find any information on this)? I installed xgboost with pip in a conda environment. Version is 0.6 and python version is 2.7.13.

May be related to #2759

I am unable to reproduce this on my machine. Are you sure you have installed the XGBoost GPU version correctly? You will need to build from source you should not be able to install from pip.


Store Request/Response Templates as Strings

Currently, I think request/response templates are parsed from the YAML file as structured objects, and stored in the DB as the same. My expectation was that we would store these templates/examples as strings so that we can have more control over the exact payload that the simulators send. Here are some example payloads that I think we can't achieve with the current setup:
Inject a numeric value
Input:
{
  "first": 1, "second": 2, "third": {{ 1 + 2 }}
}

Expected Output:
{
  "first": 1, "second": 2, "third": 3
}

Problem: Testcase will fail to parse because {{ 1 + 2 }} is not valid JSON.
Inject a non-primitive value
Input:
{
  "status": "received",
  "body": {{ test_steps[0].request.body }}
}

Expected Output:
{
  "status": "received",
  "body": { "amount": 100, "currency": "GBP" }
}

Problem: Testcase will fail to parse because {{ test_steps[0].request.body }} is not valid JSON.
Inject a variable into key position
Input:
{
  "{{ environment.RESULT_KEY }}": "accepted"
}

Expected Output:
{
  "my_custom_result": "accepted"
}

Problem: JSON keys are not currently examined for variable substitution, so the output will contain {{ environment.RESULT_KEY }}
Create empty request body
Input:

Expected Output:

Problem: Testcase will fail to parse because "" is not valid JSON (and cannot be created through a visual JSON editor)
Create malformed JSON (e.g. to test graceful response to errors)
Input:
{ comment: "no quote marks around the comment field, and there is no closing brace"

Expected Output:
{ comment: "no quote marks around the comment field, and there is no closing brace"

Problem: Testcase will fail to parse because the document is not valid JSON (and cannot be created through a visual JSON editor)
Create non-JSON payload (e.g. an XML response for a future API)
The problem here is that we won't be able to parse the testcase when we import it (or create it through the JSON editor), if the template is expecting a valid JSON object.
Input:
<Status>Accepted</Status>

Expected Output:
<Status>Accepted</Status>

Problem: Testcase will fail to parse because the document is not valid JSON (and cannot be created through a visual JSON editor)

N.B. if the template is stored as a string, we cannot manipulate it very easily (e.g. to retrieve body.foo.bar inside the JSON document). In places where we need to do such manipulation, I suggest that we parse the JSON document on-demand (after applying twig substitutions) instead of "pre-parsing" it and storing the structured object in the database.
JSON is the expected format for most of our payloads, so it makes sense that we have prioritised it, but we should not force the payloads to always be JSON (e.g. in the common case of an empty response).
I think the visual JSON editor as part of the test case editor is nice, but it is less important to me than supporting the patterns above. So if that means that it is necessary to remove the JSON editor, then I'm happy to stick with a plaintext textarea.

Hi Christopher, @cjol
Just wanted to check if our previous work on #343 still makes sense.
Variables support branch contains the next features:
1. Inject a numeric value

{ "first": 1, "second": 2, "third": "{{ 1 + 2 }}"}

2. Inject a non-primitive value

{"body": {"amount": "{{ 1 + ${ENV_VALUE} }}" }} - calculations using env. variables
{"body": {"amount": "{{ 1 + steps.2.request.body.amount} }}" }} - calculations using Test Step variables
{"body": {"amount": "{{ ${ENV_VALUE} + steps.2.request.body.amount} }}" }} - calculations using both, env. and Test Step, variables
{"body": {"transactionRequestId": "{{ uuidv4() }}" }} - a custom function that generates uuid v4 (if need more functions e.g. to generate someOtherOrRandomValue() - they are to be written additionally)

Notes to 1 and 2:

They are applicable for test_request_scripts, test_response_scripts, request, and response.
They are not applicable for TC main fields (e.g. description or components) and TS main fields (e.g. pattern, source or trigger).
{ "body": {{ test_steps[0].request.body }} } is not supported as right now we can't get objects/arrays using Twig. Only 'values' can be withdrawn e.g. if body.amount = 1, we can get it using test_steps[0].request.body.amount.
The example of TC that uses new variables is attached here. Envs, to be set up in session are: FEE = 2, fee = 1, AMOUNT = 1, and amount = 1

3. Inject a variable into key position:
It's not there, but should be possible to be developed pretty fast (e.g. <1d)
4. Create empty request body:
It's not there, but should be possible to be developed pretty fast (e.g. ~1-2d).
Maybe we are to add some syntax for YAML and for the existing TC edit UI
Notes to 3 and 4:
Looks like both options can be added pretty quickly w/o global changes to the existing backend and UI.

5. Create malformed JSON (e.g. to test graceful response to errors):
Not there and need to think about it as it requires pretty big changes to the way of data storing (now we store JSONs in db).
6. Create non-JSON payload (e.g. an XML response for a future API):
Same as 5.
Notes to 5 and 6:
Seems like, from the technical perspective, 'not valid JSON' and 'non-JSON payload' are almost the same - i.e. require adding some way to handle non-JSON data, as Postman does. We need to investigate how much work is it, but it looks like a bit slice of existing code to be changed... These features are to be used in request.body and response.body only, right?

Suggestions:

If the way items 1-2 works is fine, items 3-4 development timeline is acceptable, and delay for items 5-6 is ok - we may deliver the next version of Variables early next week.
If the actual state of Variables support and our suggestion above is not sufficient, please let us know and we'll try to find another solution.

Please let us know if this works. Thank you!

Hi Anton,
I'm a little bit disappointed because I did anticipate these problems - but it looks like I didn't get my concerns across at the right time. Quoting from #343:

Define one big template string for the request body in the YAML
Store the template as a string in the database

In terms of moving forward, there are still some oustanding practical problems with 1-2, which I will add detail to below. 4 is also a practical problem, but we can add a workaround as you describe it. 3, 5 & 6 are lower in importance because they are "theoretical" problems that we can avoid in our current test case roadmap.
I am a little bit surprised that supporting non-JSON payloads is a big change because I didn't think we did any processing to the payload (I thought we just read it from the test case and dump it into the request). But you all know the codebase better than I do, so I will defer to your judgement!
For now, let's add a workaround to allow us to construct empty bodies (4), and I can tolerate the remaining problems for now. I would also be thankful if you can find some time to do the investigation of work required for supporting non-JSON payloads so that I can think about when to include it in our roadmap.

Detail on outstanding problems

Inject a numeric value
{ "first": 1, "second": 2, "third": "{{ 1 + 2 }}"}

This is not actually injecting a numeric value, - the result will be "third": "3" instead of "third": 3. Note that the result contains quote marks that are undesirable. I think for the current testcases, we can work around this issue but we will need to fix it eventually.

{ "body": {{ test_steps[0].request.body }} } is not supported as right now we can't get objects/arrays using Twig.

This is actually specifically what I meant with the phrase "non-primitive" values. I'm not sure this is a Twig problem because we can get an object in Twig and convert it into a JSON string: { "body": {{ test_steps[0].request.body | json_encode() }} }. The problem is actually the same as the numeric value - if we inject the JSON string using the current system, there will be undesirable quote marks around the result.
It's a common pattern in the MM API to "repeat" a payload from a previous message as part of the confirmation. Again, I think we can work around this issue for the current testcases by writing out the individual values inside the object one-by-one.

Another note: it looks like we are preserving the old syntax for injecting environment variables and the new syntax (amount: '{{ ${FEE} + ${AMOUNT} + ${fee} + ${amount} }}'). That seems redundant - we can simplify things by only supporting the new syntax:
 amount: '{{ process.env.FEE + process.env.AMOUNT + process.env.fee + process.env.amount }}'


Literal Initializer does not show up

The widgets are installed correctly, as I can insert them. However, the Literal Initializer is not available when creating an activity. It seems it does not install completely.

It's part of the test project in this github project. There is no seperate module in the appstore. It's just an example.


Update Helm release kured to v4.0.3

This PR contains the following updates:

Package
Update
Change

kured (source)
patch
4.0.2 -> 4.0.3

⚠ Dependency Lookup Warnings ⚠
Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.

Release Notes

kubereboot/charts
v4.0.3
Compare Source
A Helm chart for kured

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

Renovate Ignore Notification
As this PR has been closed unmerged, Renovate will now ignore this update (4.0.3). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.
If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.


Run tests selectively

This PR enables running only tests that have a description containing the substring specified in
fpm test -- --contains <substring>

for the following tests:

[x] bin_test.f90
[x] formats_test.f90
[x] string_test.F90
[x] command_line_test.f90
[x] test_result_test.F90
[x] data_partition_test.F90
[x] object_m_test.f90
[x] user_defined_collectives_test.f90

@ktras I updated the build instructions for the NAG compiler in the README.md so this PR is ready for review and merge.

@ktras I've now addressed the source code bug that I previously thought was a compiler bug. You saw the new functionality via screen share and all tests pass so I'm going to merge this and mint a new release.


nvim crashing with GitBranch provider

version
NVIM v0.5.0-767-g0f590ae2a
Lua 5.4.1
LuaJIT 2.1.0-beta3
issue
using the following provider will crash nvim if opening a session, file etc. in a non .git directory.
gls.left[6] = {
  GitBranch = {
    provider = 'GitBranch',
    condition = empty_buffer,
    highlight = {colors.grey,colors.purple},
  }
}

(as an example) pwd = $HOME
then cd ~ && nvim some_new_file_which_is_not_in_a_git_repo will hang nvim.

should be fixed.

Thanks!
maybe i am wrong - but I think we need to check if the path is a git repo in a different way?
though commit b544f1c fixes the issue for $HOME. -> When using nvim for general tasks all over the system directory -just as normal usage with sudo or via sudoedit this is still at problem. try nvim something_random in /home/ or /etc/ then heavy cpu usage and nvim/terminal hanging/crashing is still an issue. If i am not mistaking.
here echo $EDITOR is nvim - i use it everywhere.
so this git branch checking should somehow be "non-aggressive"

--?
not a fix of the "Provider" (vcs) in galaxyline but a related question.
how would I use FugitiveHead() ('tpope/vim-fugitive') in the same way i would use it in lets say lightline?

local api = vim.api
local gl = require('galaxyline')
local gls = gl.section

local empty_buffer = function()
	if vim.fn.empty(vim.fn.expand('%:t')) ~= 1 then
		return true
	end
	return false
end

gls.right[1] = {
  GitHead = {
    provider = function()
		local branch = api.nvim_command(':call FugitiveHead()')
		return branch
	end,
    condition = empty_buffer,
    highlight = { '#0087d7','#d16d9e'},
  }
}

yes. I only check the path equal $HOME .. so if you edit some /etc it will cause some problem.
you should use vim.fn.FugitiveHead() get the result.

nice - thanks. I am basically learning lua as we speak :) porting my init.vim to lua.

Should be rewrite find_git_root function .

I had rewrite it. can you test it?

cool. just updated. now nvim with galaxyline.nvim using the default provider 'GitBranch' works everywhere and with sudoedit.
i just edited sudoedit /etc/pulse/default.pa succesfully using statusline.lua.  :-)
great work!


Draggable Legend

Suggestion:
It would be really neat if the legend could be movable by the end user.
My applicaiton will be plotting data and I can't predict which area of the graph will be clearest for legend placement. I don't want to hide important results,  so allowing the user to move the legend to the most appropriate area would be really powerful. Perhaps snapping to one of the corners.
The work by @NicolasLairNET in PR #3650 that is nearing completion looks like it might be similar?

@KroMignon Thankyou! I look forward to trying this.


MakeFile: nmake support

Please add support for nmake.
Apparently the "wildcard" parameter does not exist in nmake.

+1
You delivered a .sln but we cannot make from Visual Studio.
And in the meantime if you could specify what make version to use on Windows it would be helpful. Tried some make/cmake versions for Windows but nothing worked !

If you can use Visual Studio you can use that to build VulkanSharp. All you need to do is put the latest vk.xml spec document in the output folder then build the projects through VS.

Thank you Jimmacle, that worked !

I made it easier to build on Windows. VS should now download the vk.xml before generating the source.
https://github.com/mono/VulkanSharp/commit/f9f44258740f41db30344c14c097de0a39022594

@michidk do you still need to use the nmake now when the solution/csproj downloads the dependencies (vk.xml)? If not, I will close this issue.
Alternatively we can rename the Makefile to GNUmakefile and create simple Makefile compatible with nmake. Or just have Makefile.nmake so that we don't run into issues when GNU makefile is not available on *nix systems.

No response, so closing the issue. Feel free to reopen if nmake support is still desired.


[WIP] Cleanup workspace if exist on workspace creation

Signed-off-by: denis-tingajkin<EMAIL_ADDRESS>
Description
This fix can solve some problems when in new workspace exist some outdated content.
Motivation and Context
How Has This Been Tested?

[ ] Covered by existing integration testing
[ ] Added integration testing to cover
[X] Tested locally
[ ] Have not tested

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

WIP reason: waiting for CI results


fix: update SFML and fix build on Linux

Applied changes according to @Rahix discussion:
https://github.com/JoshParnell/ltheory-old/discussions/3
Switched to SFML 2.5.1.
Added a build.bash script.
Note: gentoo required media-libs/libpng-compat:1.2

Just to have it mentioned, there is a good chance that these changes break the windows build.  I would rather add the modifications into the conditional for non-windows build.