docs: update crate-feature-flags decision

This updates the crate-feature-flags doc, about how we use different cargo feature flags, specifically the alloc/std/no_std feature flags.
This change will make us more compatible with what the ecosystem in general does, and easier for us to move to a workspace (this change somewhat blocks work on that front, although I've sort of assumed something like this would be accepted.).
It includes some background on why it's organized like this, the status quo in the stdlib (and the ecosystem too), and the differences from that with what we're doing.
Obviously, I'm open to changes/suggestions/improvements here.
(Apologies if I left something in that should have been changed, or in the case of any typos/incomplete sentences... I wrote much of this while on cold medicine, and there was a bit of a gap between starting it and completing it, so it's entirely possible I messed up somewhere)

Also, let me know if this should instead be submitted in some other way.

Rebased and merged as https://github.com/ockam-network/ockam/pull/1909 !


Source type modernization

This likely fixes #1355 by not crashing anymore if the source is null, although I have not been able to duplicate the bug (how can a take have no source?)
Deprecates SNM_GetSourceType in favor of the native GetMediaSourceType
Adds actions "SWS/BR: Select all video processor items"
Adds support for subproject and video processor items to contextual toolbars

:white_check_mark: Build sws 324-master completed (commit https://github.com/reaper-oss/sws/commit/70f9237a92 by @cfillion)

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Ubuntu1804, ARCH=armv7l

build/sws-<IP_ADDRESS>-Linux-armv7l-fix-gettaketype-crash-70f9237a.tar.xz

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Visual Studio 2019, ARCH=x86

build/BuildUtils/SWS_Template.ReaperLangPack
build/BuildUtils/whatsnew.html
build/reaper_sws-x86.pdb
build/sws-<IP_ADDRESS>-Windows-x86-fix-gettaketype-crash-70f9237a.exe

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Ubuntu1804, ARCH=aarch64

build/sws-<IP_ADDRESS>-Linux-aarch64-fix-gettaketype-crash-70f9237a.tar.xz

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Ubuntu1804, ARCH=x86_64

build/sws-<IP_ADDRESS>-Linux-x86_64-fix-gettaketype-crash-70f9237a.tar.xz

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Visual Studio 2019, ARCH=x64

build/BuildUtils/SWS_Template.ReaperLangPack
build/BuildUtils/whatsnew.html
build/reaper_sws-x64.pdb
build/sws-<IP_ADDRESS>-Windows-x64-fix-gettaketype-crash-70f9237a.exe

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Ubuntu1804, ARCH=i686

build/sws-<IP_ADDRESS>-Linux-i686-fix-gettaketype-crash-70f9237a.tar.xz

:x: Build sws 325-master failed (commit https://github.com/reaper-oss/sws/commit/e226135cb6 by @cfillion)

:x: Build sws 325-master failed (commit https://github.com/reaper-oss/sws/commit/e226135cb6 by @cfillion)

:white_check_mark: Build sws 325-master completed (commit https://github.com/reaper-oss/sws/commit/e226135cb6 by @cfillion)

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Visual Studio 2019, ARCH=x64

build/BuildUtils/SWS_Template.ReaperLangPack
build/BuildUtils/whatsnew.html
build/reaper_sws-x64.pdb
build/sws-<IP_ADDRESS>-Windows-x64-fix-gettaketype-crash-e226135c.exe

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Ubuntu1804, ARCH=armv7l

build/sws-<IP_ADDRESS>-Linux-armv7l-fix-gettaketype-crash-e226135c.tar.xz

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Ubuntu1804, ARCH=i686

build/sws-<IP_ADDRESS>-Linux-i686-fix-gettaketype-crash-e226135c.tar.xz

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Visual Studio 2019, ARCH=x86

build/BuildUtils/SWS_Template.ReaperLangPack
build/BuildUtils/whatsnew.html
build/reaper_sws-x86.pdb
build/sws-<IP_ADDRESS>-Windows-x86-fix-gettaketype-crash-e226135c.exe

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Ubuntu1804, ARCH=x86_64

build/sws-<IP_ADDRESS>-Linux-x86_64-fix-gettaketype-crash-e226135c.tar.xz

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Ubuntu1804, ARCH=aarch64

build/sws-<IP_ADDRESS>-Linux-aarch64-fix-gettaketype-crash-e226135c.tar.xz

:white_check_mark: Build sws 330-master completed (commit https://github.com/reaper-oss/sws/commit/310ab052e9 by @cfillion)

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Visual Studio 2019, ARCH=x64

build/BuildUtils/SWS_Template.ReaperLangPack
build/BuildUtils/whatsnew.html
build/reaper_sws-x64.pdb
build/sws-<IP_ADDRESS>-Windows-x64-fix-gettaketype-crash-310ab052.exe

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Ubuntu1804, ARCH=x86_64

build/sws-<IP_ADDRESS>-Linux-x86_64-fix-gettaketype-crash-310ab052.tar.xz

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Visual Studio 2019, ARCH=x86

build/BuildUtils/SWS_Template.ReaperLangPack
build/BuildUtils/whatsnew.html
build/reaper_sws-x86.pdb
build/sws-<IP_ADDRESS>-Windows-x86-fix-gettaketype-crash-310ab052.exe

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Ubuntu1804, ARCH=armv7l

build/sws-<IP_ADDRESS>-Linux-armv7l-fix-gettaketype-crash-310ab052.tar.xz

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Ubuntu1804, ARCH=aarch64

build/sws-<IP_ADDRESS>-Linux-aarch64-fix-gettaketype-crash-310ab052.tar.xz

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Ubuntu1804, ARCH=i686

build/sws-<IP_ADDRESS>-Linux-i686-fix-gettaketype-crash-310ab052.tar.xz

:x: Build sws 331-master failed (commit https://github.com/reaper-oss/sws/commit/6e4cbf31e2 by @cfillion)

:white_check_mark: Build sws 331-master completed (commit https://github.com/reaper-oss/sws/commit/6e4cbf31e2 by @cfillion)

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Ubuntu1804, ARCH=i686

build/sws-<IP_ADDRESS>-Linux-i686-fix-gettaketype-crash-6e4cbf31.tar.xz

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Ubuntu1804, ARCH=aarch64

build/sws-<IP_ADDRESS>-Linux-aarch64-fix-gettaketype-crash-6e4cbf31.tar.xz

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Visual Studio 2019, ARCH=x64

build/BuildUtils/SWS_Template.ReaperLangPack
build/BuildUtils/whatsnew.html
build/reaper_sws-x64.pdb
build/sws-<IP_ADDRESS>-Windows-x64-fix-gettaketype-crash-6e4cbf31.exe

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Visual Studio 2019, ARCH=x86

build/BuildUtils/SWS_Template.ReaperLangPack
build/BuildUtils/whatsnew.html
build/reaper_sws-x86.pdb
build/sws-<IP_ADDRESS>-Windows-x86-fix-gettaketype-crash-6e4cbf31.exe

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Ubuntu1804, ARCH=x86_64

build/sws-<IP_ADDRESS>-Linux-x86_64-fix-gettaketype-crash-6e4cbf31.tar.xz

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Ubuntu1804, ARCH=armv7l

build/sws-<IP_ADDRESS>-Linux-armv7l-fix-gettaketype-crash-6e4cbf31.tar.xz


Clean up minor code details

Highlights:

Use Deref / IntoIterator when applicable
Avoid some minor redundant allocation

Hey @tranzystorek-io, well done !


chore(regression): fix regular expression for release branch

Fixed now since I was using an environment variable called TRAVIS_BRANCH which on PRs always points to the branch you want to merge into, i.e. master.
It now works:

Closes #423

:+1:

👍


feat(secrets): add scm host metadata

Fixes

https://issues.redhat.com/browse/HAC-5715
https://issues.redhat.com/browse/HAC-5717
Description

Adds input field for host & repo in AddSecret form.
removes remote secret labels from Secret creation utils.
For source secret adds scm labels and annotation in createSecret utils.
Modifies and adds to related unit tests
Updates Secret List View & related utils to use K8sSecrets instead of Remote Secrets.
Links & unlinks Image pull Secrets to Service accounts on creation and deletion

Type of change

[x] Feature
[ ] Bugfix
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

Screen shots / Gifs for design review

How to test or reproduce?

Browser conformance:

[ ] Chrome
[ ] Firefox
[ ] Safari
[ ] Edge

Inconsistent styling

@sahil143 I dint change the CSS, the image you shared is what the existing form looked like.
I've added a commit to reduce the sizing of the dropdown fields to align with that of our standard input fields. However, the form looks different in 3 different SecretType cases

@abhinandan13jan I will get a quick microcopy review done by the docs team. I am also assuming that the Host and Repository fields are optional, correct?

Secret Type column must map to Key/Value (#) or image, now it shows some random label values.

@abhinandan13jan I will get a quick microcopy review done by the docs team. I am also assuming that the Host and Repository fields are optional, correct?

@pankajshivpuje yes, these are optional

@pankajshivpuje @abhinandan13jan  Since deployment secrets are removed, do we want to update learn more content as well? It still contains deployment secrets section in it.

@karthikjeeyar We are going to replace learn more links with direct links to documentation because they do not work in community distribution installation on Konflux.

Secret Type column must map to Key/Value (#) or image, now it shows some random label values.

@karthikjeeyar there are several other types, only these 3
case SecretType.basicAuth:
case SecretType.sshAuth:
case SecretType.opaque:
return SecretTypeDisplayLabel.keyValue; are part of KeyValue,
We have kubernetes/service-tokewn and managed types. The util for showing types has not been changes.
Perhaps we are noticing this change because we have switched from RemoteSecrets list to SecretsList. In case we only want to show a filtered list of items with type keyvalue and image-pull will be a different use case? WDYT?

Creating a pull secret with dockerconfig auth type is not linking the created secret to appstudio-pipeline SA.

SA not linked to image-pull-secret-test

Updated. Can you please check??

In case we only want to show a filtered list of items with type keyvalue and image-pull will be a different use case? WDYT?

I see these secrets with  type managed-gitops.redhat.com/managed-environment in cli as well.  These secrets might not be user created ones, but lets get this in and based on feedback, we revisit and filter it need.

@pankajshivpuje @abhinandan13jan Since deployment secrets are removed, do we want to update learn more content as well? If yes I think we need to notify the docs team about this.

@karthikjeeyar I will request support from docs team to have this updated. I will let you know when I hear back from them.

@abhinandan13jan My apologies for commenting late for this PR. Just wanted to check the support text for Repository field. Is this the repository where secret will be stored or is this the repository where this secret will be used?


Concurrent map read and map write under Go 1.6.0

Since Go 1.6.0 and the concurrent acces detector, my app crashes under heavy load:
fatal error: concurrent map read and map write

at github.com/go-zoo/bone/route.go:98
Does anybody else is experiencing the same issue ?

map vars has been deleted In the branch beta https://github.com/go-zoo/bone/tree/beta, 11ebbcb7fd8ca4ffa0d1014f5eb385fb386bd082.

Ok cool ;)

New error, even in the branch beta.
I got a fatal error: concurrent map writes on the muxStack[req] = m in ServeHTTP.
func (m *Mux) ServeHTTP(rw http.ResponseWriter, req *http.Request) {
	muxStack[req] = m
	// Check if a route match
	if !m.parse(rw, req) {
		// Check if it's a static ressource
		if !m.staticRoute(rw, req) {
			// Check if the request path doesn't end with /
			if !m.validate(rw, req) {
				m.HandleNotFound(rw, req)
			}
		}
	}
	delete(muxStack, req)
}

I'm already working on this :) should be fix tomorrow

Hahaha awesome :)

It seems that it is still not working.
I still got some fatal error: concurrent map writes at the same place.
Any plans ? Because half of my services crash right now.

It should be done tomorrow, I will notify you when it's ok. Sorry for the delay

No problem, thanks :+1:

it should work on the beta branch now.

Thanks a lot ;)


Shopping List takes serving size into account

Hey,
It would be awesome to be able to parse an argument to the .cook file to let it know how many servings I would like to make and then automatically adapt the amount I need to buy accordingly. I, unfortunately, do not have that much time to make a pull request myself, but if no one has picked up the idea until I find time, I probably will make a pull request.
Anyways, I love the idea, the simplicity and all that!

Nvm I just saw the mile stones 😅


Last Slide - Unknown contact

On the last slide it looks like an unknown identity<EMAIL_ADDRESS>@johndoe
Should this change to one of those mentioned here https://www.parity.io/contact/

Thanks! I'm overhauling this workshop which will resolve this particular issue. Closing this issue for now.


Use opinionated Pint

This removes the pint.json configuration file to use the default settings.

@mabdullahsari happy with this change?
If you're good then we can tag a 2.x version to properly release this.

@dwightwatson
Yup! This is definitely the way to go in a collaborative repository like this. It's my bad that I forgot the remove the customized configuration file! 🙌

Sweet, all good.
Would you like to do the honours of tagging 2.x and doing a release? Otherwise I can take a look tomorrow.

Sure thing!


Move quotes behind other content in the tweet widget with z-index.

Fixes a minor display issue with the tweet widget.
Resolves #240
How to test
Check netlify preview for styles.
Screenshots

LGTM!


Add License information and REUSE status in README

Hi @SebastianWolf-SAP,
I have added the REUSE tool files. Can you please check again?


Add script to run GitHub ginkgo workflow locally

Add a script to unroll the steps from the documentation for running locally the ginkgo tests on Kind, inside of a QEMU VM, to replicate the GitHub workflow.
Commits:

docs: Address minor issues in doc for running ginkgo workflow locally
contrib/scripts: Add script to run GH ginkgo workflow locally

I hear the plan is to move to ACT as soon as we can, to have an easy way to run GitHub Actions locally. So this PR will likely remain a draft until we reach that point.

Now I'm also hearing that some people would like to have it in, so let's go for a round of reviews!

I added docker and qemu-system-x86_64 to the list of commands we check at the beginning of the script, so it will return early with an error message if these commands are not available.
I also remove the check on yq and only use the Docker image, to make sure we run the right tool (see David's comment on conflicting implementations).

@learnitall, would you mind taking a quick look please?

I addressed the comments from Ryan, and rebased on top of https://github.com/cilium/cilium/pull/25217.

Doc-related workflows passed successfully, and the new script is not tested in CI. This is ready to merge.


Create "Hello World" example for dev guide

Describe the Enhancement
Create something akin to "Hello World" that can walk a new developer though setting up a new example code for making contributions. The example should use sys_app library as a base to print out the firmware version and relevant LoRaWAN MAC parameters. The LED should also be turned on as an example for interfacing with the hardware.
Included should be a written walk-through that someone can follow for staring to develop with the board.
Benefits
Help assist new developers with programming the board.
Possible Drawbacks
N/A
Additional Context
N/A

@cjosephson Issue created for "Hello World" example


Dell U3821DW with M1 Mac Mini

Checklist

[x] I have searched for existing issues
[x] I have looked through the Monitor Troubleshooting wiki
[x] I have updated MonitorControl to the latest version

Describe the issue
The Dell U3821DW monitor is not picked up as a compatible monitor in the MonitorControl app.
Expected behaviour
Support for the Dell U3821DW (Dell U3818DW is the predecessor) would be ideal, allowing volume control from the keyboard.
Environment Information (please complete the following information):

macOS version: 11.2.1
MonitorControl version: 2.1.0
Monitor(s): Dell U3821DW
Mac model: 2020 M1 Mac Mini
Monitor Cable(s)/Connection(s): USB-C (display port)

Did you get this working? I have a similar situation...

Nevermind, found #323


Controller tuning for custom robot

I managed to import a Kinova Gen3 robot arm with the Robotiq 2F-85 into the simulation. I also followed the custom robots guide stated below
https://maniskill.readthedocs.io/en/latest/user_guide/tutorials/custom_robots.html
I've verified that my robot with pd_joint_delta_pos controller and random action moves similar to the video shown and also the pd_joint_pos controller maintains the rest keyframe accordingly.
However, when I trained the robot on StackCube-v1 task it approaches the cube but doesn't really grip it and it behaves quite weirdly.
I have attached a video showing the training (step 0 and step 104).
https://github.com/user-attachments/assets/298341ff-dc29-41ef-aa58-982bd7141346
https://github.com/user-attachments/assets/0b17e191-ee85-4d0e-8c85-230bd5c56f21
Do you have some other tips for tuning the P, D, and also force limit values for the arm and the gripper that is more effective e.g tuning the PD values real-time with the simulator interactively? I also realized for all grippers, such as fetch and panda they have the same PD and force limit coefficients, does that mean for my robot it should also be the same?
I also found this issue https://github.com/haosulab/ManiSkill/issues/71 which tried to use robotiq gripper. Can I also check if it was succesfully implemented?

the P, D and force limit values in simulation don't matter that much, you can probably just copy the values for fetch/panda for your implementation. They only matter if you want to do sim2real transfer then you need to system ID by checking if an action in sim corresponds to the same behavior in the real world.
I assume you are using PPO to train. Maybe first start with the PushCube and PickCube tasks. StackCube is actually much harder than it looks (most RL algorithms solve this task slower than most existing robot RL benchmarks).
Another thing, it looks like the robot is initialized at the middle of the table. This might make the task too hard to solve. If you are using the stack cube reward function, it encourage the gripper to move towards the red cube first, then grasp it. However the current position of the robot might make this too hard since the cube is often very close to the robot base.
Another thing is video 3.mp4 the full video? As in at the start of the evaluation episode it looks like that?

Thank you for your suggestion. Indeed, I realized that the PD values are not the issue.
I finally found the culprit and it is due to the end effector (Robotiq-2F-85), it has a peculiar configuration, having 6 actively controlled joints compared to the conventional 2-joint EE such as one's used for Panda.
In Gazebo, I used the joint state publisher gui to control the gripper for open and closing and it works fine. Video below shows manually moving just the finger_joint through the GUI.
https://github.com/user-attachments/assets/426692cb-7e39-48c2-a8a1-18c8ac05cbd5
However, when exporting it from .xacro to urdf and loading the URDF into Maniskill, it behaves weirdly. Video below is again manually moving the finger_joint through the slider, but robot goes haywire.
https://github.com/user-attachments/assets/78010224-d75a-4a9a-85fd-bd974dc9eadd
Note that the finger_joint is a mimic_joint, which moves other joints that have a mimic tag referencing the finger_joint. Perhaps this is what's causing the problem? Here's the URDF if it's helpful to debug.
gen3_robotiq_2f_85_ori.zip
One thing though the robotiq (2f-85) gripper was used in ManiSkill few years back, and I compared my URDF with the one in the repo below:
https://github.com/haosulab/cvpr-tutorial-2022/blob/master/assets/robotiq_2f_85_gripper_visualization/robotiq_85_original.urdf
It's also seem to be using mimic joint, but all the inertial component in the links got removed. I'm afraid disabling this might not translate well for sim-to-real.
Nonetheless,I tried removing the inertial links from the robot, however, still no good results (shown below).
https://github.com/user-attachments/assets/bf251d69-6865-4bb9-9498-aee3be8a56f0
When all joints in the gripper were disabled, the robot could move normally.
https://github.com/user-attachments/assets/cb53c8a2-2ce9-463c-a468-c777c3ea4429
I used Gen3 with all gripper joints disabled and tested it on the PushCube task and initialized the robot closer to the edge of the table, following your suggestion, and it can learn the task by using its arm to push the cube to target destination although not 100% success rate after 10 million steps.
Hope you can give some advice regarding this! Let me know if you need more information, and thank you so much for the help.

Just wanted to check if there's any suggestions regarding this issue, would be greatly appreciated! :)

Will bump this up my TODO list today, thanks for the reminder

For your URDF you will also need to send me the full folder, I am missing the mesh files

Meshes: kortex_description.zip
URDF:
kinovagen3.zip

Hi @StoneT2000,
I'm working on a similar project and encountered the same issues—specifically, the arm motion being affected by changes in the gripper joints. I also struggled to apply the correct constraints to the Robotiq gripper.
I followed the tutorial linked in this comment and implemented debug/robotiq.py using the latest versions of SAPIEN 3. While some behaviors are a bit unusual, it seems mostly correct.
Screencast from 08-20-2024 06:11:51 PM.webm
However, when I used this approach to build a tabletop environment with the Robotiq gripper in ManiSkill 3, I encountered an unexpected issue. Given the success with SAPIEN alone, I'm unsure what’s causing the problem.
Screencast from 08-20-2024 06:17:51 PM.webm
To reproduce this issue, you can use the code in this fork.
mani_skill/examples/debug_robotiq_sapien.py contains my reimplementation of the tutorial code. Run it with python -m mani_skill.examples.debug_robotiq_sapien.py --model_constraint.
Running python -m mani_skill.examples.debug_robotiq_maniskill.py will reproduce my results in ManiSkill 3. The corresponding Robotiq agent is in mani_skill/agents/robots/robotiq/robotiq.py. Unfortunately, I cannot control the gripper correctly with either the PDJointPosMimicController or by directly changing its joint positions via GUI.
Thank you in advance for any advice on resolving this issue!

Ok one issue is the old cvpr tutorial urdf definition is actually outdated/partly wrong. I am fixing it to make it work.
Also after discussing with @fbxiang, to simulate this very specific gripper well/accurately, it requires some complex drive creation code so mimic joints labels in the urdf cannot really be used. I'm hoping we can think of some general way to define complex grippers like this one via drives (which simulate better and are more stable).

Fixed URDF files: https://github.com/haosulab/ManiSkill-Robotiq_2F/tree/v0.1.0 (there's a floating one and a non floating one, feel free to add these to your own robots). Also fixes the visual meshes so its not all gray.
@Nielsencu you should be able to look at the gripper implementation and copy it over to your own custom robot with the kinova setup:

Fixed URDF files: https://github.com/haosulab/ManiSkill-Robotiq_2F/tree/v0.1.0 (there's a floating one and a non floating one, feel free to add these to your own robots). Also fixes the visual meshes so its not all gray.
@Nielsencu you should be able to look at the floating robot iq 2f 85 implementation and copy it over to your own custom robot with the kinova setup. Key thing to do is to add the correct passive/mimic controller configs and define _after_load_articulation function to setup the drives which make the gripper behave like real life.
@UltronAI You can try out the new floating gripper
python mani_skill/examples/demo_robot.py -r "floating_robotiq_2f_85_gripper" --zero-actions -c pd_joint_delta_pos

The drives are setup so only the outer knuckle joints actually control the gripper, the rest are passive. This will open the GUI and you can click the articulation, then the outer knuckle joint and set the position target to see it.

2024年11月30日 屏幕视频 21时15分13秒.webm
hello,I use this urdf and  floating_robotiq_2f_85 congtorller ，、but it's not work

this is my code:
from typing import Dict, Union
import numpy as np
import sapien

from mani_skill import ASSET_DIR, PACKAGE_ASSET_DIR
from mani_skill.agents.base_agent import BaseAgent, DictControllerConfig, Keyframe
from mani_skill.agents.controllers import *
from mani_skill.agents.controllers.base_controller import ControllerConfig
from mani_skill.agents.registration import register_agent
from mani_skill.sensors.camera import CameraConfig
from mani_skill.utils import sapien_utils

@register_agent(asset_download_ids=["robotiq_2f"])
class FloatingRobotiq2F85Gripper(BaseAgent):
    uid = "floating_robotiq_2f_85_gripper"
    urdf_path = f"{ASSET_DIR}/robots/robotiq_2f/floating_robotiq_2f_85.urdf"
    disable_self_collisions = True
    urdf_config = dict(
        _materials=dict(
            gripper=dict(static_friction=2.0, dynamic_friction=2.0, restitution=0.0)
        ),
        link=dict(
            left_inner_finger_pad=dict(
                material="gripper", patch_radius=0.1, min_patch_radius=0.1
            ),
            right_inner_finger_pad=dict(
                material="gripper", patch_radius=0.1, min_patch_radius=0.1
            ),
        ),
    )
    keyframes = dict(
        open_facing_up=Keyframe(
            qpos=[0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0],
            pose=sapien.Pose(p=np.array([0.0, 0.0, 0.5])),
        ),
        open_facing_side=Keyframe(
            qpos=[0, 0, 0, 0, 0, 0],
            pose=sapien.Pose(
                p=np.array([0.0, 0.0, 0.5]), q=np.array([0.7071, 0, 0.7071, 0])
            ),
        ),
    )
    root_joint_names = [
        "root_x_axis_joint",
        "root_y_axis_joint",
        "root_z_axis_joint",
        "root_x_rot_joint",
        "root_y_rot_joint",
        "root_z_rot_joint",
    ]

    @property
    def _controller_configs(
        self,
    ) -> Dict[str, Union[ControllerConfig, DictControllerConfig]]:

        # define a simple controller to control the floating base with XYZ/RPY control.
        base_pd_joint_pos = PDJointPosControllerConfig(
            joint_names=self.root_joint_names,
            lower=None,
            upper=None,
            stiffness=1e3,
            damping=1e2,
            force_limit=100,
            normalize_action=False,
        )
        base_pd_joint_delta_pos = PDJointPosControllerConfig(
            joint_names=self.root_joint_names,
            lower=-0.1,
            upper=0.1,
            stiffness=1e3,
            damping=1e2,
            force_limit=100,
            use_delta=True,
        )

        # define a passive controller config to simply "turn off" other joints from being controlled and set their properties (damping/friction) to 0.
        # these joints are controlled passively by the mimic controller later on.
        passive_finger_joint_names = [
            "left_inner_knuckle_joint",
            "right_inner_knuckle_joint",
            "left_inner_finger_joint",
            "right_inner_finger_joint",
        ]
        passive_finger_joints = PassiveControllerConfig(
            joint_names=passive_finger_joint_names,
            damping=0,
            friction=0,
        )

        finger_joint_names = ["left_outer_knuckle_joint", "right_outer_knuckle_joint"]
        # use a mimic controller config to define one action to control both fingers
        finger_mimic_pd_joint_pos = PDJointPosMimicControllerConfig(
            joint_names=finger_joint_names,
            lower=None,
            upper=None,
            stiffness=1e5,
            damping=1e3,
            force_limit=0.1,
            friction=0.05,
            normalize_action=False,
        )
        finger_mimic_pd_joint_delta_pos = PDJointPosMimicControllerConfig(
            joint_names=finger_joint_names,
            lower=-0.1,
            upper=0.1,
            stiffness=1e5,
            damping=1e3,
            force_limit=0.1,
            normalize_action=True,
            friction=0.05,
            use_delta=True,
        )
        return dict(
            pd_joint_pos=dict(
                base=base_pd_joint_pos,
                finger=finger_mimic_pd_joint_pos,
                passive_finger_joints=passive_finger_joints,
            ),
            pd_joint_delta_pos=dict(
                base=base_pd_joint_delta_pos,
                finger=finger_mimic_pd_joint_delta_pos,
                passive_finger_joints=passive_finger_joints,
            ),
        )

    def _after_loading_articulation(self):
        outer_finger = self.robot.active_joints_map["right_inner_finger_joint"]
        inner_knuckle = self.robot.active_joints_map["right_inner_knuckle_joint"]
        pad = outer_finger.get_child_link()
        lif = inner_knuckle.get_child_link()

        # the next 4 magic arrays come from https://github.com/haosulab/cvpr-tutorial-2022/blob/master/debug/robotiq.py which was
        # used to precompute these poses for drive creation
        p_f_right = [-1.6048949e-08, 3.7600022e-02, 4.3000020e-02]
        p_p_right = [1.3578170e-09, -1.7901104e-02, 6.5159947e-03]
        p_f_left = [-1.8080145e-08, 3.7600014e-02, 4.2999994e-02]
        p_p_left = [-1.4041154e-08, -1.7901093e-02, 6.5159872e-03]

        right_drive = self.scene.create_drive(
            lif, sapien.Pose(p_f_right), pad, sapien.Pose(p_p_right)
        )
        right_drive.set_limit_x(0, 0)
        right_drive.set_limit_y(0, 0)
        right_drive.set_limit_z(0, 0)

        outer_finger = self.robot.active_joints_map["left_inner_finger_joint"]
        inner_knuckle = self.robot.active_joints_map["left_inner_knuckle_joint"]
        pad = outer_finger.get_child_link()
        lif = inner_knuckle.get_child_link()

        left_drive = self.scene.create_drive(
            lif, sapien.Pose(p_f_left), pad, sapien.Pose(p_p_left)
        )
        left_drive.set_limit_x(0, 0)
        left_drive.set_limit_y(0, 0)
        left_drive.set_limit_z(0, 0)


fix: section height bug

Changes:

Fixes bug issue #66.

Note:
This is definitely a better alternative to making widgets scrollable in terms of responsiveness! But note that another reason why I got rid of MediaQuery.of(context).size.height when taking the height needed for the profile sections area was because I tested and noticed that the device_simulator plugin with different device sizes takes the largest available device screen as the screen height. The bug only shows up on that specific simulator and not on other individual simulators and real mobile devices. Make sure to keep that in mind when using MediaQuery and testing on that simulator.
UI

N/A

Wait, are we saying that the simulator is not accurate in showing how responsive our designs are? If that's so, there's an alternative called device_preview that I found recently & is more popular. I can make the switch.

@HelenGezahegn Unfortunately, device_preview has the same issues as device_simulator. 😢 Check out my comment for more info!


[material-ui] v6 changed the injection order

Steps to reproduce
Steps:

Checkout this codesandbox that displays the behaviour for v5: https://codesandbox.io/p/sandbox/mui-5-16-8-qylygf
Checkout this codesandbox that displays the behaviour for v6: https://codesandbox.io/p/sandbox/mui-5-16-8-forked-h5ccxk?workspaceId=42d580f6-8e29-46e7-b91f-43fc4f1f64c5

As a note, although the v6 codesandbox uses the latest v6 version, I also tested with 6.0.0 which has the same behaviour.
As far as I can tell, the behaviour change comes from <StyledEngineProvider injectFirst>, which seems to have changed the injection order between CssBaseline and GlobalStyles
Current behavior
GlobalStyles defined are injected before CssBaseline
Expected behavior
GlobalStyles  should be injected after CssBaseline so that they can take precedence over baseline, and we can avoid having to use !important, as was the behaviour in v5
Context
I need some specific pages in my application to be able to override the defined default body background
Your environment
as provided in the codesandboxes above
Search keywords: globalstyles body cssbaseline

This is a bug but I have to dig down to see if it's from our side or Emotion.

Thank you @siriwatknp! Let me know if I can help in any way.


website can't open by my network!

Context

https://itsjavi.com/bootstrap-colorpicker/

I am sorry, I was getting too much traffic from baidu for some reason


[Admin] Publish

Docs Build status updates of commit 196be66:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.github/fabricbot.json
:white_check_mark:Succeeded

docs/outlook/online-meeting.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Suggest Different Installation Location for Sample Project and Working Folder on Windows 10

Prerequisites

[Y ] Can you reproduce the problem with Debug -> Reload Without Extensions?
[Y ] Did you perform a cursory search to see if your bug or enhancement is already reported?
[Y ] Did you read the Troubleshooting guide?

Description
The closest I found to this is: 13238
The suggested fix was the following:

close brackets
In your appdata directory /roaming/brackets
find a file called state.json
edit with notepad++
find a directory called project directory
change that to your liking.
start brackets

On Windows 10 at least, the Brackets (.exe) program itself is installed in a new folder of "Brackets" under the path "C:\Program Files (x86)" which is correct and typical configuration:
C:\Program Files (x86)\Brackets\   (for the program executable etc.)
However, I would suggest that the "C:\Program Files (x86)\Brackets\Samples" folder be installed to "%USERPROFILE%\Documents\Brackets\Samples" instead.  This installs all the samples docs under the users Documents folder instead which does not require Administrative privileges.  Access to C:\Program Files (x86)\ requires Admin privileges.  When I try to create a new project (by creating a new folder) it defaults to: a path under: "C:\Program Files (x86)\Brackets\samples\root".  Users have to escalate privileges just create a new project under:  "C:\Program Files (x86)"  This is not good security practice having sample and project files under the programs files directory (which is for program files only) by default.
I looked in both state.json and brackets.json in  appdata directory /roaming/brackets.
"project directory" does not appear in either of them.  I think it is missing from your installation and therefore defaulting to "C:\Program Files (x86)".
I would suggest configuring the installation so that the state.json file settings have a samples_directory = "%USERPROFILE%\Documents\Brackets\Samples
and
project_directory = ""%USERPROFILE%\Documents\Brackets\Projects"
and install the samples under that samples folder and default the projects to the projects folder.
Steps to Reproduce
Steps above.
Expected behavior: Expected to see sample folder and project folder configured by installation to be under: "%USERPROFILE%\Documents\Brackets\
Actual behavior: [What actually happened]
The are installed under:  C:\Program Files (x86)\Brackets.  Changes here require admin privileges and this really is not the appropriate default location for sample and project documents.  It is a security risk defaulting them to here.
Versions
Please include the OS and what version of the OS you're running.   Windows 10
Please include the version of Brackets.
Release 1.14 build 1.14.2-17770 (release-1.14.2 f71f00acc)
build timestamp: Tue Mar 31 2020 00:50:40 GMT-0700
Thanks,
Hope this helps.
Todd

I looked at this again a little closer.  I think in the instructions that were given in 13238 need correction.
The suggested fix was the following:

close brackets
In your appdata directory /roaming/brackets
find a file called state.json
edit with notepad++
find a directory called project directory   <<<<<<<< Not project directory
change that to your liking.
start brackets

I think what you are looking for in state.json is "projectPath" not "project directory".  Change that to %USERPROFILE%\Documents\Brackets\Projects\  I think.  I am not sure that is the default base path for all projects or not


conflict with "import json"

I wanted  to use the Pyota library along with the json library and always got an error (AttributeError: 'module' object has no attribute 'dumps' )
Renaming the the json.py file in  /usr/local/lib/python2.7/dist-packages/iota helped to solve that issue.

Hey @MichiKuhl thanks for reporting this issue!
Couple of thoughts:

Could you attach a stack trace, so that I can review the files and code that were involved in the error?

Out of curiosity, if you activate absolute imports in your script, does the error go away?
Put the following code at the top of the Python file in question:
from __future__ import absolute_import

We might still rename the library for compatibility, but this will help to diagnose the issue.

Hey @MichiKuhl it's been awhile; I'm going to go ahead and close this issue.  If you still need help with this issue, just post back and I'll have a look 😺


[Task]: Remove FF4J support

@hetunandu @ginilpg can we move this as part of phase 1.1 or phase 2, as discussed here

Done

@hetunandu @ginilpg can we move this as part of phase 1.1 or phase 2, as discussed here


Check regExp expresssions don't throw syntax errors

Fixes #5927
The important part was that invalid regExp doesn't throw a syntax error.
@hpinkos Can you test this in windows 10?

@ggetz, thanks for the pull request! Maintainers, we have a signed CLA from @ggetz, so you can review this at any time.
I noticed that CHANGES.md has not been updated. If this change updates the public API in any way, fixes a bug, or makes any non-trivial update, please add a bullet point to CHANGES.md and comment on this pull request so we know it was updated. For more info, see the Pull Request Guidelines.

I am a bot who helps you make Cesium awesome! Thanks again.

Are we sure we want to let the SyntaxError bubble up to the user?  Shouldn't we catch it and wrap it in a RuntimeError?  I think our general guidelines are to always expose RuntimeError instances, but I'm having a hard time remembering exactly why.  @shunter any thoughts?

Wrapping in a different error type gives an opportunity to provide a better error message.

@shunter @mramato That's what already happens. The issue is that test wasn't throwing any errors when creating a RegExp with an invalid expression. I couldn't find any documentation about the thrown errors in the docs. So I adjusted the logic to make sure it wasn't throwing a SyntaxError, if it does throw an error.

Thanks for the clarification.  Looks good.


Expose textChanges.ChangeTracker for public API

Suggestion
I'm not sure how such requests as this one suits into TypeScript repo, but I've seen such requests earlier so decided to put another one!
Motivation: Currently it's very unclear for new developers how to contribute new code actions (refactorings / quick fixes: getEditsForRefactor / getCodeFixesAtPosition) with current plugins API. While factory API is exposed AFAICS the only way to convert nodes to actual changes is ts.createPrinter().printNode, which makes passed in formatOptions useless (just always inserting semicolons is already too annoying). I don't see a reason why don't let other developers to build their own code actions in the same way as built-in bulit.
Of course I've already seen a lot of plugins using in our days, most of them are using constructor and with along with these methods: insertNodeAt, replaceNodeRange, delete and a few others. With types exposed it would be easier to use language service methods that receive formatOptions.
🔍 Search Terms
Language Service Plugins API

List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily and help provide feedback.
✅ Viability Checklist

My suggestion meets these guidelines:

[ ] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[ ] This wouldn't change the runtime behavior of existing JavaScript code
[ ] This could be implemented without emitting different JS based on the types of the expressions
[ ] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[ ] This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion

📃 Motivating Example

💻 Use Cases

What's the recommended way to sets of TextChanges from a single refactoring without resorting to internal APIs? I'm working on a plugin to add a couple of refactorings, but my offsets are all over the place, resulting in changes applied not where I intended.


Bug in irq_remove_handler() and/or irq_add_shared_handler()?

I'm still trying to figure out whats going on but the shared handler code looks really complicated and its hard to tell when something goes wrong.
Here is my symptom: I have a few shared DMA handlers, all on the same DMA IRQ. After a round of add/remove-shared-handler one of those handlers is forever called in an endless loop, without any DMA interrupt pending. Looks like one of the shared handlers is just returning to itself over and over again.
After poking around it bit, I've come to the conclusion that the contents of irq_handler_chain_slots look fishy.
The code looks equivalent to:
irq_add_shared_handler(DMA_IRQ_0, handler1, PICO_SHARED_IRQ_HANDLER_DEFAULT_ORDER_PRIORITY);
irq_add_shared_handler(DMA_IRQ_0, handler2, PICO_SHARED_IRQ_HANDLER_DEFAULT_ORDER_PRIORITY);
// do stuff with dma
irq_remove_handler(DMA_IRQ_0, handler1);
irq_remove_handler(DMA_IRQ_0, handler2);
// sleep or do something unrelated
irq_add_shared_handler(DMA_IRQ_0, handler3 /*!!!*/, PICO_SHARED_IRQ_HANDLER_DEFAULT_ORDER_PRIORITY);
irq_add_shared_handler(DMA_IRQ_0, handler2, PICO_SHARED_IRQ_HANDLER_DEFAULT_ORDER_PRIORITY);
// do stuff to trigger dma

At this point handler3 is nowhere to be found in irq_handler_chain_slots. And handler2 is looping on itself.

I'm still trying to figure out whats going on but the shared handler code looks really complicated and its hard to tell when something goes wrong.

Fair; the code was written that way in attempt to minimize the amount of runtime overhead vs raw IRQs, but also with a view to not spending too much memory on tracking lists of handlers, and finally of course avoiding any locking in the IRQ path (particularly with respect to removing an IRQ handler during itself which seemed like a useful feature)

Here is my symptom: I have a few shared DMA handlers, all on the same DMA IRQ. After a round of add/remove-shared-handler one of those handlers is forever called in an endless loop, without any DMA interrupt pending. Looks like one of the shared handlers is just returning to itself over and over again.
After poking around it bit, I've come to the conclusion that the contents of irq_handler_chain_slots look fishy.

Yes, there is a bug - thanks for spotting it. Dynamically adding/removing handlers is evidently not something people do much, and our spot testing of it went down a happy path!. I will fix and add an actual test case!

Thanks!

merged into develop


chore(sdk): Remove file manager sdk

What's the purpose of this pull request?
We are using thumbor/gatsby-image now, we don't need file-manager/arquivos sdk anymore

Closing after the lack of excitement with this PR


Adds pipeline troubleshooting guide

This is the initial version of the KFP troubleshooting guide. As we identify common issues, guidance will be added to this doc.
I am also recommending creating cloud provider specific troubleshooting guides, to address troubleshooting in specific environments. I will add issues for building those guides.

This change is

/assign @SinaChavoshi
@SinaChavoshi, PTAL at the troubleshooting guide

This change can be previewed at:
https://deploy-preview-1759--competent-brattain-de2d6d.netlify.com/docs/pipelines/troubleshooting/

/lgtm
/approve

/lgtm


Update template.examples.ts, typo fix on skeleton

Very small typo fix.
Might not need the all rigour below
Hey, I just made a Pull Request!

:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[ ] All your commits have a Signed-off-by line in the message. (more info)

@ManuInNZ thanks for this, but we're going to need a patch changeset for this package.
See CONTRIBUTING.md for more information about how to add changesets.

Yes boss.
Just need a bit of spare time and I will yarn the change set.
Cheers
Manu

Well at least in the process of fixing a small typo, I learned to fix mines too and hopefully will create a better PR next time.
Cheers

Thanks :tada:


Visual Transformer 46424051

Visual transformer in visual-adni-s4642405

This is an initial inspection, no action is required at this point
Difficulty: Hard
Readme:

No detail model explain in the readme of how ViT works. No algorithm explain.
No test accuracy results evidence.
No training and val data split and loss plots
Vision transformer figure is wrong.

Commit messages: Excellent, detailed.
Code:

Used CNN as model NOT ViT even claimed used VIT, there is no transformer block in the code
No comments
MNIST data in the test.py (Unsure why)

Functionality/Performance:

Test accuracy is 83.7% (No evidence proofing it)
To Shakes: Suggestion further investigation.

I did use a ViT block tho https://github.com/shakes76/PatternAnalysis-2023/pull/95/files#diff-b66ac6637471e951c55d86814740892931970c657886d124c4719251d2bc5942R26

test.py is just that, a test file.

Good code doesn't need comments, I did put comments where they may prove helpful to an uneducated observer, e.g. at the top of code blocks, i ain't finna put one at every twist and turn.

This is an initial inspection, no action is required at this point
Updated version after student's feedback
Difficulty: Hard
Readme:

No detail model explain in the readme of how ViT works. No algorithm explain.
No test accuracy results evidence.
No training and val data split and loss plots
Vision transformer figure is wrong.
Missing reference section.

Commit messages:

Excellent, detailed.
There is no pull request message provided. You will need to provide: "pull-request, with clear description, completed properly"

Code:

Student provided Siamese network and ViT network. I looked into Siamese at the beginning.
Brief comments at the top of code blocks

Functionality/Performance:

Test accuracy is 83.7% (No evidence proofing it)

General comments:
The README is very brief, no algorithm explain and provided wrong ViT figure. Not sure how test accuracy is obtained as no test result evidence is provided. Please remove Siamese network code if you are submitting your work as ViT.

Marking
Good Practice (Design/Commenting, TF/Torch Usage)
Adequate design and implementation
Good spacing and comments
Header blocks missing -1
Recognition Problem
Solves problem, but no testing metrics -1
Driver Script present
File structure present
Shows Usage & Demo & Visualisation & Data usage, testing results -1
Module present
Commenting
No Data leakage, no validation split -1
Difficulty: Hard
Commit Log
Meaningful commit messages
Progressive commits used
Documentation
ReadMe OK, missing refs -1
Model/technical explanation could be better -1, wrong figure -1
Good Description and Comments
Markdown used and PDF submitted
Pull Request
Successful Pull Request (Working Algorithm Delivered on Time in Correct Branch)
Feedback required, move files to project directory, restore repo README -2
Request Description minimal -1

Feedback marks possible +2 if the requested changes are made (see above).

No feedback attempt and no feedback marks granted.


Add Spanish Sentiment dataset

Checklist for adding MMTEB dataset

Reason for dataset addition:

[x] I have tested that the dataset runs with the mteb package.
[x] I have run the following models on the task (adding the results to the pr). These can be run using the mteb run -m {model_name} -t {task_name} command.

[x] sentence-transformers/paraphrase-multilingual-MiniLM-L12-v2
[x] intfloat/multilingual-e5-small

[x] I have checked that the performance is neither trivial (both models gain close to perfect scores) nor random (both models gain close to random scores).
[x] If the dataset is too big (e.g. >2048 examples), considering using self.stratified_subsampling() under dataset_transform()
[x] I have filled out the metadata object in the dataset file (find documentation on it here).
[x] Run tests locally to make sure nothing is broken using make test.
[x] Run the formatter to format the code using make lint.
[x] I have added points for my submission to the points folder using the PR number as the filename (e.g. 438.jsonl).

@isaac-chung @imenelydiaker I saw that there are sentiment datasets already in the repo for different langs like this one but for the Spanish dataset there is no datacard or paper linked so idk how to fill out the TaskMetadata. Do you know how it was filled out for the other similar datasets? Their datacards for the datasets already in this repo are empty on huggingface as well

@isaac-chung @imenelydiaker I saw that there are sentiment datasets already in the repo for different langs like this one but for the Spanish dataset there is no datacard or paper linked so idk how to fill out the TaskMetadata. Do you know how it was filled out for the other similar datasets? Their datacards for the datasets already in this repo are empty on huggingface as well

Actually there's a paper but it was not linked to the HF data card. We're working on integrating all these dataset as one multilingual one.

So should I not add this one?

@isaac-chung @imenelydiaker I saw that there are sentiment datasets already in the repo for different langs like this one but for the Spanish dataset there is no datacard or paper linked so idk how to fill out the TaskMetadata. Do you know how it was filled out for the other similar datasets? Their datacards for the datasets already in this repo are empty on huggingface as well

Actually there's a paper but it was not linked to the HF data card. We're working on integrating all these dataset as one multilingual one.

So should I not add this one?

The PR will remove all existing tasks using this subsets, but we can keep it now and reward you for your contribution 🙂

The PR will remove all existing tasks using these subsets, but we can keep your addition now and reward you for your contribution 🙂. Please fill the required metadata as in other tasks, and add points so the PR can be merged

Thanks, I filled it out. Are there any other datasets you are aware of that need to be added?

@dipam7 can you please update your branch and fix the conflicts so we can merge?


"Transaction parameter is empty" error raised during indexing (7.0.0rc2)

Steps to reproduce:
Some of the entrypoints of the contracts I indexed don't require parameters to work. When operations are caught on them, they crash and return this error:
FrameworkException('Transaction parameter is empty')
I saw that it came from the indexes/tezos_tzkt_operations/matcher.py file.
Line 58:
if not operation_data.parameter_json:
  raise FrameworkException('Transaction parameter is empty')

This exception is raised even if the "parameter_json" attribute exists on the object but is equal to {}.
In order to fix the issue, I replace the condition with:
if operation_data.parameter_json is None:

Doing this fixed the crash on my side but is it what you were trying to check in this file?
Environment

Python version: 3.11.4
DipDup version or commit hash: 7.0.0rc2
Database engine version: Timescale15
Hasura version: 2.30.1
Are you in docker? No
Can you reproduce this issue on next? Yes

Yup, that's exactly what you think it is, an incorrect check. Thanks!


Replacing ResourceTestRule with ResourceExtension in documentation

Problem:
Dropwizard 2.0 deprecated ResourceTestRule in favor of ResourceExtension. The documentation providing examples of testing resources was not updated to reflect this.
Solution:
ResourceTestRule has been removed from the documentation in favor of ResourceExtension.
This work was completed in auth.rst and forms.rst but not testing.rst as that will be handled in #3062
Result:
Documentation is now more up-to-date with reality. :)

I standardized to resourceExtension, per suggestion.

Is this documentation update available in the current documentation on dropwizard.io? I'm struggling to keep track of what version the documentation is given the Getting Started guide says "First, add a dropwizard.version property to your POM with the current version of Dropwizard (which is 2.0.1):" but it appears that the documentation itself is not yet updated?

@cobbce The changes of this PR are published on https://www.dropwizard.io/.
You can find the specific pages here:
https://www.dropwizard.io/en/latest/manual/auth.html
https://www.dropwizard.io/en/latest/manual/forms.html


Unable to open terminal on pod

Noticing the issue after the recent latest update. running on windows 11 with remote SSH onto ubuntu 18.04 vm
Terminal closing with error:
Error from server (BadRequest): container postgres is not valid for pod postgres-89b45d47-h4gvh

I also just ran into this issue. The problem seems to be that the container name is getting some extra whitespace injected in front of it. If you look at the error pop-up, you'll notice that it says ' postgres' instead of just 'postgres' after the container flag.
A short term work around until this gets fixed is to just manually run the CLI command directly in a terminal and remove the extra space.

Indeed even container selection in UI shows extra indentation

Reverting the plugin to v1.3.11 fixes the issue.

@Reilman79 Yep. There seems to be some issue in how the container parameter is getting determined. Looks like a regression caused due to the new container feature added in the latest release. Would really appreciate it if you guys could put out a hotfix!!


Add Mistral provider to config template

Mistral is known for their open models (originally Mistral 7b, then their Mixtral MoE model), but they also have proprietary models that they're offering through their inference API "La Plateforme": https://docs.mistral.ai/deployment/laplateforme/overview/
The original purely proprietary models (small, medium, large) are not SOTA anymore and might get deprecated at some point, but their latest model "Mistral Large 2" is supposedly close to Llama 3.1 405B (as per https://mistral.ai/news/mistral-large-2407/). (And while not entire proprietary, its weights can only be used under their non-commercial "Mistral Research License", while their platform allows commercial use)
The API is OpenAI-compatible, so mods works with it out-of-the-box.

Closes https://github.com/charmbracelet/mods/issues/174

thanks!


Error during commit record creation, when bundlemon runs on master branch / Travis

Hello 👋
Describe the bug
We could not run bundlemon on master branch inside our project, because prNumber is false.
That makes  createCommitRecord fail
Consequence to see in this PR  : Total files change +3.96MB 0% in each PR.
Expected behavior
Same working process that in bundlemon project: inside Github Action last merge commit , it works.
Environment
BundleMon version: v1.3.0
The concerned .bundlemonrc :
https://github.com/cozy/cozy-drive/blob/master/.bundlemonrc
System:

OS: macOS 12.1
CPU: (8) x64 Intel(R) Core(TM) i5-8259U CPU @ 2.30GHz
Memory: 61.59 MB / 16.00 GB
Shell: 5.8 - /bin/zsh

Binaries:

Node: 12.22.9 - ~/.nvm/versions/node/v12.22.9/bin/node
Yarn: 1.22.17 - /usr/local/bin/yarn
npm: 6.14.15 - ~/.nvm/versions/node/v12.22.9/bin/npm
Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman

Additional context
Here is the Travis error:
[ERROR] create commit record: validation failed
{
  "message": "A validation error occurred when validating the body",
  "errors": [
    {
      "keyword": "pattern",
      "dataPath": ".prNumber",
      "schemaPath": "#/properties/prNumber/pattern",
      "params": {
        "pattern": "^[0-9]*$"
      },
      "message": "should match pattern \"^[0-9]*$\""
    }
  ]
}
[ERROR] Failed to create commit record
[ERROR] Unhandled error
Error: Failed to generate report

Capture:

Thank you for reporting this issue, should be fixed in v1.3.1
Please let me know if it didn't work


Sync IaC resources deployed by DataAll & manual deletion of objects from AWS Console

Describe the bug
DataAll is out of sync when user carry out activities within AWS management console, such as delete bucket or folder, the deleted bucket or folder is still appearing in DataAll . Also, user in Datahub still be able to create folder within the deleted bucket.
When dataset is deleted in DA, the associated S3 bucket in AWS management console will need to be deleted manually by user.
How to Reproduce
Delete a bucket in AWS console.
You can still access and create folders within the deleted bucket from DataAll
Expected behavior
No response
Your project
No response
Screenshots
No response
OS
Win
Python version

AWS data.all version
0.9
Additional context
No response

Hi @MATTT-P,
Here there are 3 different topics:

Bug on creation of folders in deleted buckets. I have checked the code and it is not possible that this happens since the boto3 call of creating an S3 prefix would throw an error. I also tested it directly: I deleted the S3 Bucket of a dataset and I tried to create a folder in that dataset. I got the following error: " "An error occurred (NoSuchBucket) when calling the PutObject operation: The specified bucket does not exist"," Try again to see if the error persists or if you are referring to another error.

Sync deleted S3 Bucket. When using Infrastructure as Code to deploy resources (as the Dataset CloudFormation stack) we discourage users to manually edit or edit the resources of the stack. This is not good practice and it removes the advantages of working with IaC, that is why we do not expect users to directly delete the S3 Bucket.

Sync of deleted folders. Yes, this is something that we have thought about. For example in a similar way that there is a syncing tables ECS task that runs on schedule we could implement a sync folders tasks that runs at a defined frequency.  Would this be sufficient for your organisation? Are you thinking of other ways of implementing this?

Bests

Closing stale issue. If needed it will be reopened. In this case the actual feature might not be recommended to implement.


allows caduceus convert old webhook format obtained from scytale

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

Codecov Report

Merging #110 into master will decrease coverage by 0.41%.
The diff coverage is 8%.

@@            Coverage Diff             @@
##           master     #110      +/-   ##
==========================================
- Coverage   84.64%   84.23%   -0.42%
==========================================
  Files          80       81       +1
  Lines        4456     4498      +42
==========================================
+ Hits         3772     3789      +17
- Misses        591      615      +24
- Partials       93       94       +1

Impacted Files
Coverage Δ

webhook/webhook_convertOldFormat.go
0% <0%> (ø)

webhook/start.go
65.74% <40%> (-1.57%)
:arrow_down:

device/device.go
77.5% <0%> (-1.67%)
:arrow_down:

wrp/header_wrp.go
100% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Not clear how to derive the language from the 3 letters code

The documentation for the translation endpoint says language is The RFC 5646 letter language tag that the translation is primarily in. https://bible.helloao.org/docs/reference/#code-example
The language code returned by https://bible.helloao.org/api/available_translations.json are 3 letters codes (eg. "eng") which don't match the RFC 5646 tags (eg. "en" or "en-GB") https://gist.github.com/msikma/8912e62ed866778ff8cd
It seems to be closer to ISO 639 tags (https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes). But many of the language codes returned by the translations endpoint are not in the ISO 639 list (eg. "ikk" or "ixl")

Ah that is a documentation error. It should note that they are ISO 639-3 tags.
Also that list from Wikipedia doesn't list all 3 character language tags. I would recommend using the ISO 639 code tables for looking up information on a particular tag.

Thanks for the clarification and the complete language code list.
Would it possible to add the language name to the translation endpoint?

This is fixed in v1.2.0.


Fix Conflict in semantic-kernel\concepts\vector-store-connectors\out-of-the-box-connectors\index.md

Conflict here because private repo updated the same line Chroma as the public repo updated to add Elasticsearch.

@sophialagerkranspandey Please review


openshift-sdn initialize failed in a restricted network

Describe the bug

openshift-sdn initialize failed in a restricted network
pod sdn-894sj  log:
Message:   I1223 09:34:10.873504    5150 cmd.go:121] Reading proxy configuration from /config/kube-proxy-config.yaml I1223 09:34:10.875223    5150 feature_gate.go:243] feature gates: &{map[]} I1223 09:34:10.875288    5150 cmd.go:216] Watching config file /config/kube-proxy-config.yaml for changes I1223 09:34:10.875337    5150 cmd.go:216] Watching config file /config/..2020_12_23_09_26_36.265581810/kube-proxy-config.yaml for changes F1223 09:34:20.885424    5150 cmd.go:106] Failed to initialize sdn: failed to initialize SDN: could not get ClusterNetwork resource: Get "https://api-int.lab.okd.local:6443/apis/network.openshift.io/v1/clusternetworks/default": net/http: TLS handshake timeout
pod sdn-controller-pthrw log:
Message:   subnets.go:73] Error creating subnet for node fedora, ip <IP_ADDRESS>: error updating subnet  for node fedora: Operation cannot be fulfilled on hostsubnets.network.openshift.io "fedora": the object has been modified; please apply your changes to the latest version and try again I1223 12:11:50.906161       1 subnets.go:120] Updated HostSubnet fedora (host: "fedora", ip: "<IP_ADDRESS>", subnet: "<IP_ADDRESS>/23") E1223 12:12:11.115361       1 leaderelection.go:320] error retrieving resource lock openshift-sdn/openshift-network-controller: an error on the server ("") has prevented the request from succeeding (get configmaps openshift-network-controller) E1223 12:12:33.119866       1 leaderelection.go:320] error retrieving resource lock openshift-sdn/openshift-network-controller: Get "https://api-int.lab.okd.local:6443/api/v1/namespaces/openshift-sdn/configmaps/openshift-network-controller": net/http: TLS handshake timeout E1223 12:12:35.097317       1 event.go:316] Could not construct reference to: '&v1.ConfigMap{TypeMeta:v1.TypeMeta{Kind:"", APIVersion:""}, ObjectMeta:v1.ObjectMeta{Name:"", GenerateName:"", Namespace:"", SelfLink:"", UID:"", ResourceVersion:"", Generation:0, CreationTimestamp:v1.Time{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, DeletionTimestamp:(*v1.Time)(nil), DeletionGracePeriodSeconds:(*int64)(nil), Labels:map[string]string(nil), Annotations:map[string]string(nil), OwnerReferences:[]v1.OwnerReference(nil), Finalizers:[]string(nil), ClusterName:"", ManagedFields:[]v1.ManagedFieldsEntry(nil)}, Immutable:(*bool)(nil), Data:map[string]string(nil), BinaryData:map[string][]uint8(nil)}' due to: 'no kind is registered for the type v1.ConfigMap in scheme "pkg/runtime/scheme.go:101"'. Will not report event: 'Normal' 'LeaderElection' 'fedora stopped leading' I1223 12:12:35.097489       1 leaderelection.go:277] failed to renew lease openshift-sdn/openshift-network-controller: timed out waiting for the condition F1223 12:12:35.097524       1 network_controller.go:97] leaderelection lost
Version

openshift-install 4.6.0-0.okd-2020-12-12-135354
How reproducible

install okd on bare metal
Log bundle

It's hard to get bundle...

I set up the network agenthttp_proxy,https_proxy,no_proxyin install-config.yml, is it related to this?


Minor typo fix: add missing period at the end of some comment sentences

add missing period at the end of some comment sentences.
Signed-off-by: Lei Jitang<EMAIL_ADDRESS>

On Sat, Sep 12, 2015 at 08:21:06PM -0700, Lei Jitang wrote:

add missing period at the end of some comment sentences.

Looks good to me, although a more specific commit summary would be
nice (‘Fix typo’ isn't very specific ;).

besides the doubled-space fix, nothing in this correction looks to be grammatically needed. I'm going to close this for now.

@vbatts  Should I send PR to fix the doubled-space?:)


chore: fix the notion that the roadmap is only for Mayastor

The roadmap incorrectly gave the notion that it is exclusively for Mayastor, though in reality the roadmap includes items for both Local PV and Mayastor. This PR addresses this notion.
In addition, removed the mention of the deprecated engines.

Received majority approvals, merging this PR.


Show the song playing for each station in stations list

Hi,
i want to show the song playing for each station in stations list
how can do it? or is this feature be on the to do list?
thanks.

This would be awesome if possible.

If the stations have a playlist feed (aka a recently played feed - https://github.com/analogcode/Swift-Radio-Pro/issues/91), you could monitor all those. However, that's a lot of calls. You will need to make an API call to each station on your list at a predetermined time interval. A better way might be to build a web service that gathers that info, and just make one call to that web service.


Remove the validate button if there is only one good answer

It would make it faster
Just check if it would not add precipitation errors

Better keep the same UX for every question


Optimized prompt (COPRO) not used when calling the LLM

I'm setting up an LLM (google vertex AI in my case) and phoenix tracing (to have visibility into what my dspy program is actually doing)
lm = configure_dspy_vertex_ai()
phoenix_host = "localhost"
if phoenix_host:
    instrument_dspy_phoenix(phoenix_host)

next I define a simple dspy program
import dspy
from pydantic import BaseModel

class Output(BaseModel):
    result: int

    def items(self):
        return [("result", self.result)]

class MySignature(dspy.Signature):
    function: str = dspy.InputField()
    input: int = dspy.InputField()
    output: Output = dspy.OutputField()

class MyModule(dspy.Module):
    def __init__(self):
        self.predictor = dspy.TypedChainOfThought(MySignature)

    def forward(self, input: int) -> int:
        return self.predictor(input=input, function="fibbonaci").output

I evaluate and optimize the prompt
trainset = [
    dspy.Example(input=1, output=1).with_inputs("input"),
    dspy.Example(input=6, output=8).with_inputs("input"),
]

from random import random
def evaluation_metric(example: dspy.Example, prediction: Output, trace = None) -> bool:
    print(f"Example: {example.input} * 2 = {example.output}, Prediction: {prediction}")
    return example.output == prediction.result and random() > 0.3

from dspy.evaluate import Evaluate

evaluator = Evaluate(
    devset=trainset,
    metric=evaluation_metric,
    num_threads=4,
    display_progress=True,
    display_table=True,
)

evaluator(MyModule())

from dspy.teleprompt import COPRO

teleprompt = COPRO(prompt_model=lm, metric=evaluation_metric)
my_module = MyModule()
my_optimized_module = teleprompt.compile(my_module, trainset=trainset, eval_kwargs={})

The optimizer has created a new prompt
my_optimized_module.dump_state()

{'predictor.predictor': {'lm': None,
'traces': [],
'train': [],
'demos': [],
'signature_instructions': '## Optimized Function Application\n\nBasic Instruction: Given the fields function, input, produce the fields output.\n\nProposed Instruction:  You are a powerful function-executing AI. Your goal is to flawlessly apply the provided function to the given input and return the accurate output. \n\nHere is the function you must execute: <insert function>\n\nHere is the input for this function: <insert input>\n\nNow, please calculate and clearly present:\n\nProposed Prefix For Output Field: Output:',
'signature_prefix': 'This is a great start! Your proposed instruction is much more specific and action-oriented, which can be helpful for large language models. \n\nHere's a slightly modified version that incorporates best practices and addresses potential issues:\n\nBasic Instruction: Given the fields function, input, produce the fields output.\n\nProposed Instruction: \nYou are a powerful function-executing AI. Your goal is to apply the provided function to the given input and return the accurate output.  \n\nFunction:\ntool_code\n<insert function> \n\n\nInput:\njson\n<insert input>\n\n\nOutput: \n\nProposed Prefix For Output Field:  (Leave this blank; let the model format the output naturally)\n\nExplanation of Changes:\n\n* Clear Separation: Using headings like "Function" and "Input" improves readability and helps the model distinguish between instructions and the actual data.\n* Code Blocks: Enclosing the function and input within code blocks (```) further emphasizes their distinct roles and can help with parsing, especially for programming-related tasks.\n* JSON for Input:  Representing the input as a JSON object can be beneficial if the input is structured data. This promotes consistency and makes it easier for the model to process.\n* Flexibility in Output:  Instead of forcing a specific prefix for the output, allow the model to present the result naturally. This avoids unnecessary formatting constraints and allows for more human-like responses.\n\nAdditional Tips:\n\n* Context is Key: If the function or input requires specific domain knowledge, provide a brief explanation or example to guide the model.\n* Test and Iterate: Experiment with different instruction variations and evaluate the model's performance to find the most effective approach.'}}

Using the optimized module however results in
lm.history.clear()
my_optimized_module.forward(3)
print(lm.history)

[{'prompt': 'Given the fields function, input, produce the fields output.\n\n---\n\nFollow the following format.\n\nFunction: ${function}\n\nInput: ${input}\n\nReasoning: Let's think step by step in order to ${produce the output}. We ...\n\nOutput: ${output}. Respond with a single JSON object. JSON Schema: {"properties": {"result": {"title": "Result", "type": "integer"}}, "required": ["result"], "title": "Output", "type": "object"}\n\n---\n\nFunction: fibbonaci\n\nInput: 3\n\nReasoning: Let's think step by step in order to',
'response': {'prompt': 'Given the fields function, input, produce the fields output.\n\n---\n\nFollow the following format.\n\nFunction: ${function}\n\nInput: ${input}\n\nReasoning: Let's think step by step in order to ${produce the output}. We ...\n\nOutput: ${output}. Respond with a single JSON object. JSON Schema: {"properties": {"result": {"title": "Result", "type": "integer"}}, "required": ["result"], "title": "Output", "type": "object"}\n\n---\n\nFunction: fibbonaci\n\nInput: 3\n\nReasoning: Let's think step by step in order to',
'choices': [{'text': 'json\n{\n "result": 2\n}\n\n',
'safetyAttributes': {<HarmCategory.HARM_CATEGORY_HATE_SPEECH: 1>: <HarmProbability.NEGLIGIBLE: 1>,
<HarmCategory.HARM_CATEGORY_DANGEROUS_CONTENT: 2>: <HarmProbability.NEGLIGIBLE: 1>,
<HarmCategory.HARM_CATEGORY_HARASSMENT: 3>: <HarmProbability.NEGLIGIBLE: 1>,
<HarmCategory.HARM_CATEGORY_SEXUALLY_EXPLICIT: 4>: <HarmProbability.NEGLIGIBLE: 1>}}]},
'kwargs': {'top_k': 1,
'temperature': 0.7,
'max_output_tokens': 8192,
'stop_sequences': None,
'top_p': 1.0},
'raw_kwargs': {}},
{'prompt': 'Given the fields function, input, produce the fields output.\n\n---\n\nFollow the following format.\n\nFunction: ${function}\n\nInput: ${input}\n\nReasoning: Let's think step by step in order to ${produce the output}. We ...\n\nOutput: ${output}. Respond with a single JSON object. JSON Schema: {"properties": {"result": {"title": "Result", "type": "integer"}}, "required": ["result"], "title": "Output", "type": "object"}\n\n---\n\nFunction: fibbonaci\n\nInput: 3\n\nReasoning: Let's think step by step in order to\njson\n{\n "result": 2\n}\n\n\nOutput:',
'response': {'prompt': 'Given the fields function, input, produce the fields output.\n\n---\n\nFollow the following format.\n\nFunction: ${function}\n\nInput: ${input}\n\nReasoning: Let's think step by step in order to ${produce the output}. We ...\n\nOutput: ${output}. Respond with a single JSON object. JSON Schema: {"properties": {"result": {"title": "Result", "type": "integer"}}, "required": ["result"], "title": "Output", "type": "object"}\n\n---\n\nFunction: fibbonaci\n\nInput: 3\n\nReasoning: Let's think step by step in order to\njson\n{\n "result": 2\n}\n\n\nOutput:',
'choices': [{'text': 'json\n{\n "result": 2\n}\n',
'safetyAttributes': {<HarmCategory.HARM_CATEGORY_HATE_SPEECH: 1>: <HarmProbability.NEGLIGIBLE: 1>,
<HarmCategory.HARM_CATEGORY_DANGEROUS_CONTENT: 2>: <HarmProbability.NEGLIGIBLE: 1>,
<HarmCategory.HARM_CATEGORY_HARASSMENT: 3>: <HarmProbability.NEGLIGIBLE: 1>,
<HarmCategory.HARM_CATEGORY_SEXUALLY_EXPLICIT: 4>: <HarmProbability.NEGLIGIBLE: 1>}}]},
'kwargs': {'candidate_count': 1,
'top_k': 1,
'temperature': 0.0,
'max_output_tokens': 4096,
'stop_sequences': None,
'top_p': 1.0},
'raw_kwargs': {'max_tokens': 4096, 'n': 1, 'temperature': 0.0}}]

This show the module doesn't use the optimized prompt.
(It also shows 2 calls to the LLM, where there should only be 1 afaict!)
Phoenix confirms the same.
Am I doing something wrong? Or is this a bug in dspy?
I'm using dspy-ai==2.4.12

COPRO is never recommended. It's more of a baseline. (I didn't check the details here but I suspect that COPRO just couldn't do better than your original prompt, so it did the right thing. It stuck to the original prompt.)
Our docs generally recommend that you use random search first, and get it to work, then upgrade to MIPROv2.

Looking more closely, you're using TypedChainOfThought, so you might need to use a Typed optimizer accordingly. I'm not sure that COPRO can handle Typed predictors yet.


Meltano invoke (and more?) not printing stderr from tap (consistently?)

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/3420
Originally created by @vischous on 2022-04-19 22:39:06

(.venv) visch@visch-ubuntu:~/git/tap-toggl$ meltano --version
meltano, version 1.99.0
(.venv) visch@visch-ubuntu:~/git/tap-toggl$ python --version
Python 3.8.12

Clone https://github.com/AutoIDM/tap-toggl/tree/meltano-issue
Create your own venv steps below

python -m venv .venv
source .venv/bin/activate
pip install --upgrade pip
pip install .
#yes a config.json is pushed to that branch, no worries on making a real API token it's not needed for this example
tap-toggl -c config.json
#Notice the failures, this is "good" and what should happen

INFO Hitting https://api.track.toggl.com/api/v8/workspaces                                                                                WARNING Request HTTPError exception caught:  403 Client Error: Forbidden for url: https://api.track.toggl.com/api/v8/workspaces
INFO Hitting https://api.track.toggl.com/api/v8/workspaces
WARNING Request HTTPError exception caught:  403 Client Error: Forbidden for url: https://api.track.toggl.com/api/v8/workspaces
INFO Hitting https://api.track.toggl.com/api/v8/workspaces
WARNING Request HTTPError exception caught:  403 Client Error: Forbidden for url: https://api.track.toggl.com/api/v8/workspaces
INFO Hitting https://api.track.toggl.com/api/v8/workspaces
WARNING Request HTTPError exception caught:  403 Client Error: Forbidden for url: https://api.track.toggl.com/api/v8/workspaces
INFO Hitting https://api.track.toggl.com/api/v8/workspaces
WARNING Request HTTPError exception caught:  403 Client Error: Forbidden for url: https://api.track.toggl.com/api/v8/workspaces

Run meltano install
Run meltano invoke tap-toggl , note there's no error listed and meltano will just run forever

View 5 previous comments from the original issue on GitLab

Still relevant from what I can tell


Fixes #6034

This fixes #6034.
The fix is simple: it just adds getNoImplicit() to the conditions we check to know if we need to update an atom's number of explicit Hs when breaking a bond.

I moved the updatePropertyCache() call into fragmentOnBonds(): even if atoms don't have "No implicit" set, we need to recalculate valences, since we removed one bond, which counts towards the explicit valence. Not updating it would leave the atom with an incorrect valence. I noticed when calculating the molar mass of something I had used fragmentOnBonds() on, and noticed it was one Hydrogen short.

I moved the updatePropertyCache() call into fragmentOnBonds(): even if atoms don't have "No implicit" set, we need to recalculate valences, since we removed one bond, which counts towards the explicit valence. Not updating it would leave the atom with an incorrect valence. I noticed when calculating the molar mass of something I had used fragmentOnBonds() on, and noticed it was one Hydrogen short.

The RDKit has a general pattern of assuming that callers will sanitize molecules after calling operations that change them. This often ends up creating problems since people forget that they need to do that. Adding updatePropertyCache to this function makes sense to me since it will help avoid problems and is computationally inexpensive. Thanks for thinking of that.


Remove repeated comparison of equal substrings in offsets.c.

Each string has prefix "Darwin Kernel Version 16.x.0: ".  Moved it to separate strcmp function call.

Why not keep it simple stupid?

Maybe useful for now

I think this is just to reduce the size of the offset file by a couple of bytes.
This is good, but we don't want to make it more complex than it already is.


Device ON/OFF

Field devices should have a data field for ON/OFF
The value of ON/OFF is primarily in recording that the device was specifically turned 'off' at a specific time rather than guessing that the device is off because it hasn't reported recently.  It is not uncommon for devices to lose the ability to communicate for a number of reasons but the device may still be in the field operating.  Consider an work truck beacon that has been turned on, but drives through a region that has no cell signal.  If it was recorded as being on but hasn't communicated for several minutes it can be reasonably considered to still be on until it communicates that it has been turned off.  The devices that we build will recognize that they have been turned off and will communicate the definitive 'off' state at the first time a successful message has been passed to the server.
We keep the 'OFF' status in the feed for a period of time (one hour) after the 'OFF' message was recorded.  This way it didn't just disappear, the event can be recorded as 'COMPLETE'.

I understand the value of being able to specify this information. It is easy to implement, such as by adding an is_on property to the FieldDeviceCoreDetails. One major question before the implementation can be completed is:
What does it mean for a device to be "on"?
The definition is necessary to be able to add the property and clearly describe how to use it.

For implementation, perhaps augmenting the FieldDeviceStatus to include off would be better than the is_on property I mentioned in the above comment because it avoid having to conflate the value of is_on with the current device_status.

I think it is most important to note that the device has been switched to 'off' which explains why it is not reporting and that the work may be completed.
For instance, the way we wire arrow boards is so that the IoT device is always powered off the 12VDC battery.  Nominally it reports location if moved, location every 15 minutes, and data status every 15 minutes. Once the display is powered it is now 'ON' and the display status is reported as is the UP/DOWN status.  This is repeated every 5 minutes or when something changes.  But, it may be in a bad cell area or it may have a power drop or it may just have the IoT broken so it may not report for a period of minutes or hours.  That doesn't mean that the display isn't working and visible by drivers, it just means something in the comm system isn't working.  This is different than 'OFF' which means the comm system is working fine but the control of the display has been set to no-display.
As you are trouble shooting large numbers of field devices the distinction between 'OFF' and no report becomes important.  And the time-stamp of 'OFF' is rather important.
If the battery power drops (ok we don't have this until the next version) to <6VDC we know the battery is stolen.

Co-chairs discussion on 2022-09-22 led to the decision that the Device Feed is intended to represent real time conditions and that we need more examples of consumers using the Device Feed to decide if it is needed.
Please re-open if this becomes relevant again.


docs: remove an unavailable video link in README.md

Summary
Hi Solidjs Team,
I just came across an unavailable video link while going through README.md, so I took the liberty of removing it.

Thank you. There will be a replacement soon. but until then I agree.


Save Sessions? -Enhancement Request

It be nice to be able to save a Koadic session in the event that someone accidentally ctrl + Cs out

Yeah we could make like a restore file. It wouldn't be able to save zombie connections, those would die when the web server stops, but everything else we could load back in I'm pretty sure. I'll try working on something this week.

YASSSSSsssssssssss!!! Thanks!! friggin awesome! :+1:

I didn't test too extensively, so reopen if you get an exception.

Hey, I finally got around to testing this and it seems like the saved creds and data arent automatically saving to the restore.json file. So when I cat out the restore.json file it's empty.

correction...not empty but has empty placeholders....

My guess is that you're overwriting the restore.json file without knowing it. The following situation would make this happen:

Run Koadic like normally, run jobs, gets creds, etc.
Exit Koadic.
Run Koadic again without specifying the restore file.
Realize that Koadic was not run with the restore file then exit Koadic.
The restore file is now empty.

Here's where all the magic happens:
https://github.com/zerosum0x0/koadic/blob/master/core/commands/exit.py#L31-L62
As you can see, on exit, we overwrite the restore.json file with whatever is populated in the current Koadic instance. Obviously, the current solution isn't ideal because if you forget to run Koadic with the restore file and then forget to move or rename the restore file before exiting, you'll lose all the information in the restore.
Better solution probably entails creating a folder and populating this with restore files that include timestamps in the name. You'll create a new restore on exit every time, but at least all information is retained. I'll reference a pull here when it's done.

Thanks for getting back with me.
So I have my buddy testing this out on his internal assessment as we (I) speak. In his situation someone rebooted his drone and a restore.json file was never created. I also checked to see if he was on the current version of Koadic and he is in which I also confirmed that he had the --restore option. Luckily he created a creds.txt file where he backed up his creds so there wasn't much loss there. But this has been what we've observed so far. Hope that helps.

I also appreciate the initiative in making that process better. I agree that making the unique restore files would make me love this app all the more! :heart:

I hadn't even thought of power loss scenarios. Currently, creating a restore file is only ever triggered when exit gets called. So if the process is killed at all before that happens, the file is never created. The solution there is writing a restore to disk every so often given that a change has occurred, maybe once a minute? I'll get to working on that as well when I get the time.

That's awesome! Thanks for building this out. I guess begging can pay its dividends!? I can have some folks test this out once everything gets ironed out. That sounds like a great solution.

Go ahead and pull now. Koadic will make a 'restores/' dir and place periodic restores in there. Every 60 seconds, if there's been a change, Koadic will write to this new file. I'm keeping the old behavior as well, so whenever you exit, Koadic will write the current state to 'restore.json'. I think it's nice to have that most recent state in there in case you don't wanna go digging through old restores.
https://github.com/zerosum0x0/koadic/commit/fc8ebf9a1935515aecdf3af1b3992faf3d844ae8
Had another idea while writing this update actually. If you have no state, it won't overwrite 'restore.json'!
e28db12
Again, didn't test super extensively, so reopen if you have any issues.

Super, thanks for being so active. I'll try to test this out over the weekend! If i can't get to it I'll have some of my co-workers (Coalfire) give it a go. Thanks man 1000% :muscle:


Error when running ns prepare ios --release

Hi there!
I am actually trying to compile my app for release in order to upload it on TestFlight.
When I run ns prepare ios --release, I am getting this error:
ERROR in<EMAIL_ADDRESS>+ 2 modules
Cannot get final name for export '__esModule' of<EMAIL_ADDRESS>while generating the root export '__esModule' (used name: '__esModule')
Error: Cannot get final name for export '__esModule' of<EMAIL_ADDRESS>while generating the root export '__esModule' (used name: '__esModule')
    at getFinalBinding ([...]/node_modules/webpack/lib/optimize/ConcatenatedModule.js:464:10)
    at getFinalName ([...]/node_modules/webpack/lib/optimize/ConcatenatedModule.js:520:18)
    at [...]/node_modules/webpack/lib/optimize/ConcatenatedModule.js:1384:24
    at ConcatenatedModule.codeGeneration ([...]/node_modules/webpack/lib/optimize/ConcatenatedModule.js:1432:7)
    at [...]/node_modules/webpack/lib/Compilation.js:2712:22
    at [...]/node_modules/webpack/lib/Cache.js:93:5
    at Hook.eval [as callAsync] (eval at create ([...]/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1)
    at Cache.get ([...]/node_modules/webpack/lib/Cache.js:75:18)
    at ItemCacheFacade.get ([...]/node_modules/webpack/lib/CacheFacade.js:117:15)
    at Compilation._codeGenerationModule ([...]/node_modules/webpack/lib/Compilation.js:2705:9)
    at [...]/node_modules/webpack/lib/Compilation.js:2631:10
    at arrayIterator ([...]/node_modules/neo-async/async.js:3467:9)
    at processTicksAndRejections (internal/process/task_queues.js:77:11)

Everything works fine if I remove the --release flag.
Feel free to ask me anything to test, thanks for your help!
EDIT: I am using NS 8 with webpack 5 and all my plugins are on their latest version.

@sebj54 Never seen that error. seems related to your webpack config. you should ask on discord or slack to see if anyone faced such an issue.

I doubt it :( it works great for Android (even with --release) and my webpack config is barely the original one (I just add some constants and a rule to load SVGs with raw-loader.
const webpack = require('@nativescript/webpack')
const dotenv = require('dotenv')
const { resolve } = require('path')
const fs = require('fs')

function parseDotenvValues(env){
    // This function just parses a .env file and returns it as an object
}

module.exports = (env) => {
    const dotenvValues = parseDotenvValues(env)

    webpack.init(env)

    webpack.chainWebpack((config) => {
        config.plugin('DefinePlugin').tap((args) => {
            Object.assign(args[0], {
                TNS_ENV: JSON.stringify(env.production ? 'production' : 'development'),
                ...dotenvValues,
            })
            return args
        })

        config.module
            .rule('svg')
            .test(/\.svg$/)
            .use('raw-loader')
            .loader('raw-loader')
    })

    // Learn how to customize:
    // https://docs.nativescript.org/webpack

    return webpack.resolveConfig()
}

Would it be because this plugin uses<EMAIL_ADDRESS>and not<EMAIL_ADDRESS>I will try to hit Discord or Slack, thanks for the suggestion :)

@sebj54 ok can you try 3.0.25 ? Not sure i never saw that error in any of my apps. But anyway hopefully it will be fixed

It now builds correctly with the latest version! Thanks for the really quick update :)


flamethrower doesnt range check

Fedoraware Version Date:
latest
Config used:
Pyro - Copy.txt
Description:
it doesnt range check when it used to before baan's update
Steps to reproduce the behavior:

load my config
hold the aimbot button
be far away from the target
the flamethrower cant hit the target

Additional context
https://user-images.githubusercontent.com/106420166/174244982-a5b2096d-6318-4956-9273-4a5a356adbba.mp4

Fixed shortly.


Updating vendor for nats streaming

Related to #318
Verification
$ glide cc
$ rm -rf vendor
$ glide install
$ make

@bertrand-quenin Please resubmit as a PR with only the vendor changes. Then, submit another PR with the code changes. Also, I realize we have different styles, but please don't make stylistic changes to my makefile without at least asking me why I did things a certain why or discussing why you prefer to change it, otherwise it just becomes a "style" war. We can coordinate on a makefile style guide if you feel strong about it (I do tend to have strong opinions regarding makefiles myself).
Because the diff is so hard to look at in GitHub (loading and scrolling via GitHub is excruciatingly slow), and because we've encountered so many issues with vendor updates, let's all make a point of making very clear what the change to glide.yaml is in the PR description to help the review.

@subfuzion I did not change anything on our Makefile, you're probably mistaking with the docker Makefile that has been updated

Thanks @bertrand-quenin 👍


Forwarded HTTPS requests should set X-Forwarded-Proto

This is a de-facto standard when a proxy forwards an HTTPS request to an HTTP backend.
If you agree, I'll write a patch.

Sure, didn't know about this header but I'll be happy to merge :+1:


CFY-6724: explicitly set writable permission

Closed: As this PR is more than six months old without having been merged. Please reopen (and rebase if necessary) if it is still relevant.


This PR updates broker command.

Proposed changes
This PR updates broker command.
Types of changes
What types of changes does your code introduce to the project: Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Update only documentation, not any source code.

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of
them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before
merging your code.

[X] I have read the CONTRIBUTING doc
[X] I have signed the CLA
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you
did and what alternatives you considered, etc...

Coverage remained the same at 100.0% when pulling 4e871a7f65cc43e408ec7b8dc5d1f9917d0d1ca1 on fisuda:feature/broker_cmd into cd88e70056075037400ca16bb75c5954348e4939 on lets-fiware:main.

Coverage remained the same at 100.0% when pulling 4e871a7f65cc43e408ec7b8dc5d1f9917d0d1ca1 on fisuda:feature/broker_cmd into cd88e70056075037400ca16bb75c5954348e4939 on lets-fiware:main.


Source Map Comments?

Is there anyway to maintain a fingerprinted source map comment from ember-cli? ie. //# sourceMappingURL=vendor-266f0c0df67fcb9cb0e59bf7beacecf6.map at the bottom of a JS file?
Fingerprinting seems to be hard coded to off for ember-cli-rails, but I'm not sure how to maintain the map comment.

@imackinn this should have been resolved by https://github.com/thoughtbot/ember-cli-rails/commit/bb4b03c58e4387a7914b3b509d689b07f8a9c923.
Could you try master:
# Gemfile

gem "ember-cli-rails", github: "thoughtbot/ember-cli-rails"

Closing this issue.
If you're able to reproduce with master, please ping me here and I'll re-open.

@imackinn on further thought, this will take more than just the master branch of the gem.
Please read and follow https://github.com/thoughtbot/ember-cli-rails/issues/30#issuecomment-154768936, posting back here with your results


the code is wrong but passed

Challenge Name

challenge 78
Issue Description

run it and it should not be correct
Browser Information

Browser Name, Version: chorme
Operating System: win 10
Mobile, Desktop, or Tablet: Desktop

Your Code

<link href="https://fonts.googleapis.com/css?family=Lobster" rel="stylesheet" type="text/css">

CatPhotoApp

      <button class="btn btn-block btn-primary"> Like</button>

      <button class="btn btn-block btn-info"> Info</button>

      <button class="btn btn-block btn-danger"> Delete</button>

Things cats love:

cat nip

laser pointers

lasagna

Top 3 things cats hate:

flea treatment

thunder

other cats

  <form action="/submit-cat-photo">

            <input type="radio" name="indoor-outdoor"> Indoor

      <input type="radio" name="indoor-outdoor"> Outdoor

    <input type="checkbox" name="personality"> Loving
    <input type="checkbox" name="personality"> Lazy
    <input type="checkbox" name="personality"> Crazy
    <input type="text" placeholder="cat photo URL" required>
    <button type="submit">Submit</button>
  </form>

Screenshot

@zhouchenzc0824 thank you for reporting this issue
The test Nest all of your radio buttons inside one div with the class row. is not performing correctly.
The code for this challenge is here
Please be sure to follow CONTRIBUTING.md
Happy Coding!

Hey @Bouncey I'll work on this issue if it's allright with you.

:+1:
On 8 January 2017 at 00:10, Alex Padilla<EMAIL_ADDRESS>wrote:

Hey @Bouncey https://github.com/Bouncey I'll work on this issue if it's
allright with you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FreeCodeCamp/FreeCodeCamp/issues/12426#issuecomment-271119453,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARtk5llEc941liguz1Te_CzpH-O83sM4ks5rQClZgaJpZM4LdjPy
.

Sorry first time contributor here....so I've been trying since last night, but I really don't know what to do. Here's what happens
I set up the app, and it runs fine, but if I run "node seed" at any time - with or without - changes to the challenges code it will break the app. The site will display "something went wrong", and the console will say that can't read value null.
What I've tried...
I tried restarting the whole process from the cloning stage 2 times, and both times the app breaks when I use node seed. (AFTER I set up everything else in the project. So I'm not skipping steps or anything)
I tried dropping the database via the mongo console, and then doing "node seed". This didn't work either.
I've tried node seed with and without changes to the local code, and nothing.
What am I doing wrong? I pretty much know how to apply the fix, but I just can't get past this block. And at this point I have no idea what I'm looking for either.

@alexr101 thanks a lot for helping us out, why don't you jump on the Contributors Chat room, and hit us up, we will love to sort your issues with the setup.

Thanks @raisedadead I was able to fix the problem. I think it had to do with mongo's user permissions.
I sent a pull request.


[BUG] High times on the game's clock cause celestial objects to jitter.

I set the in-game clock to 17,721,480,000 (2023 in-game years), and due to floating point imprecision or something like that, the moon and stars are unable to move smoothly across the sky.
I have no clue why exactly this would be. If I were to hazard a guess, the rotation of the various layers of the skybox (?) takes the in-game timer and does math to it to determine degrees/radians/whatever, but rather than modulo'd into the bounds of 0 to 360/6.283/whatever, it is unbounded. As with many things however, I'm likely wrong.

Sounds like a float problem, I'll try to take a look at what's causing it

Fixed, I guess? At least it should be harder to notice now.


FR: context specific code highlighting (statements)

If the cursor is on an identifier all other uses (including in the comments) of this identifier is "highlighted". That is marvelous (I guess that is [mostly] a vscode feature already) and really useful.
"But"... the same happens on statements, for example when the cursor is at UNTIL then all other UNTIL are highlighted. It would be much more helpful if the PERFORM (and possible) END-PERFORM along with possible other clauses of the current statement would be highlighted (similar for EVALUATE -> mark related WHEN and possible WHEN OTHER+END-EVALUATE.

Sorry, I have no control over this, it appears to be done on text rather than in the context of a language.
I agree it can be annoying but it can also be useful too.


[5.1] Update “unable to load standard library” test

Cherry-picks #23990 to swift-5.1-branch.

One of the subtests of Misc/fatal_error.swift assumes that Swift.swiftmodule is located purely based on the resource directory. It can now also be located in the SDK, so the test needs to be updated. Fixes rdar://problem/49665477.

Original reviewed by @jrose-apple.

@swift-ci please test