ODH 2.18 Release Tracker

Links to tracker issues for components planning updates in this.  Please update you manifests before Sept 13th.
Release Date: Sept 16th
Comment Template for automation
#Release#
- component_name|release-branch/release-tag|release-notes

List of component_name:

[ ] modelregistry
[ ] notebook-controller
[ ] notebooks
[ ] codeflare
[ ] ray
[ ] kueue
[ ] trainingoperator
[ ] trustyai
[ ] odh-dashboard
[ ] data-science-pipelines-operator
[ ] model-mesh
[ ] kserve
[ ] model-mesh-serving
[ ] odh-model-controller

NOTE: The automation now supports a release-tag or release-branch as [2] argument.
If [2] equals [3] the entry can be shortened to - component_name | release-branch/release-tag else(in cases where the teams prefer to use a release-branch) it can be separate entries as done before.
ref:
- component_name[1]|release-branch/release-tag[2]|release-tag-url[3]```
 - Please add the `#Release#` for the automation to read the entries.
 - A space can be added before or after the delimiter '|' which prevents github from making the URL malformed.
 - Please add the correct `release-branch` and `release-notes` URL
 - Multiple component releases of the same team can use the `-` to add multiple entries
   eg:

   #Release#
    - component_name|release-branch/release-tag|release-notes
    - component_name|release-branch/release-tag|release-notes
    - component_name|release-branch/release-tag|release-notes

Please feel free to reach out to me in case of any confusion :)

#Release#

codeflare|https://github.com/opendatahub-io/codeflare-operator/tree/v1.8.0-odh | https://github.com/opendatahub-io/codeflare-operator/releases/tag/v1.8.0-odh
ray|https://github.com/opendatahub-io/kuberay/tree/v1.1.1-08-14-2024 | https://github.com/opendatahub-io/kuberay/releases/tag/v1.1.1-08-14-2024
kueue|https://github.com/opendatahub-io/kueue/tree/v0.7.0-odh-1 | https://github.com/opendatahub-io/kueue/releases/tag/v0.7.0-odh-1
trainingoperator|https://github.com/opendatahub-io/training-operator/tree/v1.8.0-odh-1 | https://github.com/opendatahub-io/training-operator/releases/tag/v1.8.0-odh-1

#Release#
notebooks| https://github.com/opendatahub-io/notebooks/tree/v1.22.0 | https://github.com/opendatahub-io/notebooks/releases/tag/v1.22.0
notebook-controller| https://github.com/opendatahub-io/kubeflow/tree/v1.7.0-15 | https://github.com/opendatahub-io/kubeflow/releases/tag/v1.7.0-15

#Release#
- Kserve  | https://github.com/opendatahub-io/kserve/tree/v<IP_ADDRESS> | https://github.com/opendatahub-io/kserve/releases/tag/v<IP_ADDRESS>
- Model Mesh | https://github.com/opendatahub-io/modelmesh-serving/tree/v<IP_ADDRESS>-rc0 | https://github.com/opendatahub-io/modelmesh-serving/releases/tag/v<IP_ADDRESS>-rc0
- ODH Model Controller | https://github.com/opendatahub-io/odh-model-controller/tree/v<IP_ADDRESS> | https://github.com/opendatahub-io/odh-model-controller/releases/tag/v<IP_ADDRESS>

#Release#
modelregistry | https://github.com/opendatahub-io/model-registry-operator/tree/release/v0.2.6 | https://github.com/opendatahub-io/model-registry-operator/releases/tag/v0.2.6

#Release#
trustyai | https://github.com/trustyai-explainability/trustyai-service-operator/tree/release/1.26.0 | https://github.com/trustyai-explainability/trustyai-service-operator/releases/tag/v1.26.0
@AjayJagan @VaishnaviHire @zdtsw This is the first release of TrustyAI where ODH configuration is at the odh overlay. This means that base will start pointing at latest images and the ODH overlay to the correct ODH image releases.
I'm assuming the ODH operator already includes the appropriate changes. If not, please let us know and we'll ammend the ODH release branch so that base points to the ODH images as well.

#Release#

kserve | https://github.com/opendatahub-io/kserve/tree/v<IP_ADDRESS> | https://github.com/opendatahub-io/kserve/releases/tag/v<IP_ADDRESS>
model-mesh | https://github.com/opendatahub-io/modelmesh-serving/tree/v<IP_ADDRESS>-rc0 | https://github.com/opendatahub-io/modelmesh-serving/releases/tag/v<IP_ADDRESS>-rc0
odh-model-controller | https://github.com/opendatahub-io/odh-model-controller/tree/v<IP_ADDRESS> | https://github.com/opendatahub-io/odh-model-controller/releases/tag/v<IP_ADDRESS>

#Release#
trustyai | https://github.com/trustyai-explainability/trustyai-service-operator/tree/release/1.26.0 | https://github.com/trustyai-explainability/trustyai-service-operator/releases/tag/v1.26.0
@AjayJagan @VaishnaviHire @zdtsw This is the first release of TrustyAI where ODH configuration is at the odh overlay. This means that base will start pointing at latest images and the ODH overlay to the correct ODH image releases. I'm assuming the ODH operator already includes the appropriate changes. If not, please let us know and we'll ammend the ODH release branch so that base points to the ODH images as well.

yep, ODH 2.18 should included changes from https://github.com/opendatahub-io/opendatahub-operator/pull/1218 from Operator side

#Release# - Kserve | https://github.com/opendatahub-io/kserve/tree/v<IP_ADDRESS> | https://github.com/opendatahub-io/kserve/releases/tag/v<IP_ADDRESS> - Model Mesh | https://github.com/opendatahub-io/modelmesh-serving/tree/v<IP_ADDRESS>-rc0 | https://github.com/opendatahub-io/modelmesh-serving/releases/tag/v<IP_ADDRESS>-rc0 - ODH Model Controller | https://github.com/opendatahub-io/odh-model-controller/tree/v<IP_ADDRESS> | https://github.com/opendatahub-io/odh-model-controller/releases/tag/v<IP_ADDRESS>

#Release#

kserve | https://github.com/opendatahub-io/kserve/tree/v<IP_ADDRESS> | https://github.com/opendatahub-io/kserve/releases/tag/v<IP_ADDRESS>
model-mesh | https://github.com/opendatahub-io/modelmesh-serving/tree/v<IP_ADDRESS>-rc0 | https://github.com/opendatahub-io/modelmesh-serving/releases/tag/v<IP_ADDRESS>-rc0
odh-model-controller | https://github.com/opendatahub-io/odh-model-controller/tree/v<IP_ADDRESS> | https://github.com/opendatahub-io/odh-model-controller/releases/tag/v<IP_ADDRESS>

why need this one if @VedantMahabaleshwarkar already provided #158 (comment)

the component names provided dont match the list provided in the component_name this will make the automation fail, so I created the correct ones.

#Release# - Kserve | https://github.com/opendatahub-io/kserve/tree/v<IP_ADDRESS> | https://github.com/opendatahub-io/kserve/releases/tag/v<IP_ADDRESS> - Model Mesh | https://github.com/opendatahub-io/modelmesh-serving/tree/v<IP_ADDRESS>-rc0 | https://github.com/opendatahub-io/modelmesh-serving/releases/tag/v<IP_ADDRESS>-rc0 - ODH Model Controller | https://github.com/opendatahub-io/odh-model-controller/tree/v<IP_ADDRESS> | https://github.com/opendatahub-io/odh-model-controller/releases/tag/v<IP_ADDRESS>

#Release#

kserve | https://github.com/opendatahub-io/kserve/tree/v<IP_ADDRESS> | https://github.com/opendatahub-io/kserve/releases/tag/v<IP_ADDRESS>
model-mesh | https://github.com/opendatahub-io/modelmesh-serving/tree/v<IP_ADDRESS>-rc0 | https://github.com/opendatahub-io/modelmesh-serving/releases/tag/v<IP_ADDRESS>-rc0
odh-model-controller | https://github.com/opendatahub-io/odh-model-controller/tree/v<IP_ADDRESS> | https://github.com/opendatahub-io/odh-model-controller/releases/tag/v<IP_ADDRESS>

why need this one if @VedantMahabaleshwarkar already provided #158 (comment)

the component names provided dont match the entries provided in the component_name this will make the automation fail, so I created the correct ones.

better bring component team's attention, aovid happening again in the next release cycle.

#Release#
odh-dashboard | https://github.com/opendatahub-io/odh-dashboard/tree/v2.26.1-odh-release | https://github.com/opendatahub-io/odh-dashboard/releases/tag/v2.26.1-odh


US MBON map of activities map

https://marinebon.github.io/map-of-activities/

migrated to new website tracker https://github.com/marinebon/marinebon_wordpress_website/issues/29


chore: only use shady-render when using ShadyCSS

Closes https://github.com/Polymer/lit-element/issues/641
shady-render is used also on browsers which don't have ShadyCSS loaded. This is wasteful, as shady-render does some additional work. This change conditionally picks which render method to use based on whether ShadyCSS is loaded.
This is a non-breaking change, as shady-render does not do any functional work on browsers which doesn't have ShadyCSS loaded. It will also still work for people who want to use ShadyCSS on browsers with native shadow dom (for example, to use @apply).

Obsolete now that 3.0 drastically changes how Shady CSS support is loaded.


pantera project

Grant Application Checklist

[x] The application template has been copied, renamed (pantera.md`) and updated.
[x] A BTC or Ethereum (DAI) address for the payment of the milestones is provided inside the application.
[x] I have read and acknowledged the Terms and Conditions.
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The total funding amount of the project is below USD $30k for initial grant applications and $100k for follow-up grants.
[x] The initial PR contains only one commit (squash if needed before submitting your PR).
[x] The grant will only be announced once the first milestone has been accepted.

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

Grant Application Checklist

[x]  The application template has been copied, renamed (pantera.md`) and updated.
[x]  A BTC or Ethereum (DAI) address for the payment of the milestones is provided inside the application.
[x]  I have read and acknowledged the Terms and Conditions.
[x]  The software delivered for this grant will be released under an open-source license specified in the application.
[x]  The total funding amount of the project is below USD $30k for initial grant applications and $100k for follow-up grants.
[x]  The initial PR contains only one commit (squash if needed before submitting your PR).
[x]  The grant will only be announced once the first milestone has been accepted.

Thank you for the application @pantera612. I'm sorry to say that your application does not meet our standards and hence I'm closing the PR. The technical documentation you provide is simply an overview of a few Substrate/Rust components and the application itself is generally poor and hardly conveys any information about what you intend to achieve. The Web3 Foundation grants programs focus on technical grants and hence we expect that our grantees have a considerable level of technical expertise. I hope you're indeed able to find a solution for this pressing issue with the help of Substrate, but please understand that we unfortunately won't be able to support you.

Just to add something here. Feel free to reapply with an improved application. The provides concrete technical details and not just “Substrate module: X”


Java Compatibility

I want to use it with Java.
How I can use it?

You can add kotlin support to your existing project in order to use it.


Andy

create builder patterns for material

This is really helpful. Thank you!

I'll review in an hour or so

Related - #31

Can bors format source code automatically before merging? I hate to dismiss PRs because of formatting issues.

@alteous we can do that if we'll use cargo-fmt, I think.

@alteous

Can bors format source code automatically before merging? I hate to dismiss PRs because of formatting issues.

I don't think we should make bors do anything about the source. Instead, we could have the rustfmt config here in the repo and just ask the PR author to run rustfmt once.

@kvark you raised a good point. I think we need RFC for new material design, it's not going to be so straitforward.

Now that #128 has been merged, perhaps this PR could be updated to the new strategy? All the boilerplate code is there; it should just be a matter of renaming things.

Do we need builders now?

It does seem a bit overkill now to include builders.

Agreed. I'm closing it now due to lack of response and not obvious profit


width issue

sometimes the switch input width does not fully expand , it is very small. A page refresh will fix, but the issue come up very often.

<?= $form->field($model, 'is_billable', [ 'options' => ['class' => 'col-md-2']])
->widget(SwitchInput::classname(), [
      'type' => SwitchInput::CHECKBOX,
       'pluginOptions' => [
            'size' => 'large',
             'onColor' => 'success',
             'offColor' => 'danger',
       ]
]); ?>

Is there any fix for this yet?

I'm having this issue as well - for me it appears almost every time (first load) when loading in modal something that has SwitchInput.

Same for me, strange thing is I have one switchinput in a modal form since a year and that one always works, I added two new ones and those don't. In rare cases they do, no idea what's triggering this. Basically something is calculating the width too narrow.

seems to be some css calculation issue by the plugin... if you have an use case, can you report it to the plugin author and see if there is a fix?

This issue always occurs on Chrome 53.0.2785.143 64 bit. Not sure about other versions.

This issue still persists.
1st try:

2nd:

All up-to-date, would be great if this gets addressed.
Sample Code:
	[
		'attribute' =>'status',
		'type' => DetailView::INPUT_SWITCH,
		'format' => 'raw',
		'value' => $model->status ?
			'Active' :
			'Inactive',
		'widgetOptions' => [
			'pluginOptions' => [
				'onText' => 'Active',
				'offText' => 'Inactive',
				],
		],
	],

Fix this bug
I add new parameters: handleWidth,labelWidth,staticWidth
Example use in widget:
'handleWidth'=>'53',
'labelWidth'=>'77',
'staticWidth'=>'53'

I solved it with SwitchInputAsset
use kartik\switchinput\SwitchInputAsset;
And at the end of the file:
SwitchInputAsset::register($this);
If the SwitchInput is on a Modal you have to register the asset on the main view (the modal container view)

I solved it with SwitchInputAsset
use kartik\switchinput\SwitchInputAsset;
And at the end of the file:
SwitchInputAsset::register($this);
If the SwitchInput is on a Modal you have to register the asset on the main view (the modal container view)

Perfect answer!


GPU accelerartion is unavailable

Graphics Feature Status

Canvas: Software only, hardware acceleration unavailable
Canvas out-of-process rasterization: Disabled
Custo Wallpaper Animation: Disabled
Direct Rendering Display Compositor: Disabled
Compositing: Software only. Hardware acceleration disabled
Multiple Raster Threads: Enabled
OpenGL: Disabled
Rasterization: Software only. Hardware acceleration disabled
Raw Draw: Disabled
Skia Graphite: Disabled
Video Decode: Software only. Hardware acceleration disabled
Video Encode: Software only. Hardware acceleration disabled
Vulkan: Disabled
WebGL: Software only, hardware acceleration unavailable
WebGL2: Software only, hardware acceleration unavailable
WebGPU: Disabled

For some reason Yandex Browser is unable to use most of GPU acceleration features ignoring the flags. Here is the detailed report: about-gpu-2024-01-31T19-58-21-789Z.txt
In the console this error can be seen
[31754:31754:0131/225912.620743:ERROR:gl_factory.cc(120)] Requested GL implementation (gl=none,angle=none) not found in allowed implementations: [(gl=egl-angle,angle=default),(gl=egl-gles2,angle=none)].

On the same machine and system Brave is using GPU acceleration. Yandex Browser is also able to use GPU acceleration on other OSes.
Model: Thinkpad X1 Carbon 14-th gen
CPU: Intel 7 155h

Try with nixGL

nixGLIntel yandex-browser-stable
Found ffmpeg: /nix/store/rwa2l5qd11sscjdrgbbwnvw1in40srpv-yandex-browser-stable-<IP_ADDRESS>5-1/opt/yandex/browser/libffmpeg.so
        avcodec: 3937892
        avformat: 3934820
        avutil: 3804772
Ffmpeg version is OK! Let's use it.
[80790:80790:0202/124846.143954:ERROR:brand_package_util.cc(110)] Failed to verify partner_config signature, config will be ignored
[80790:80790:0202/124846.215290:ERROR:isolated_origin_util.cc(74)] Ignoring port number in isolated origin: chrome://custo
[80790:80790:0202/124846.215308:ERROR:child_process_security_policy_impl.cc(2137)] Invalid isolated origin:
[80790:80790:0202/124846.217256:ERROR:policy_logger.cc(154)] :chrome_browser_cloud_management_controller.cc(299) Cloud management controller initialization aborted as CBCM is not enabled.
[80833:80833:0202/124846.219857:ERROR:gl_factory.cc(120)] Requested GL implementation (gl=none,angle=none) not found in allowed implementations: [(gl=egl-angle,angle=default),(gl=egl-gles2,angle=none)].
[80833:80833:0202/124846.220809:ERROR:viz_main_impl.cc(196)] Exiting GPU process due to errors during initialization
[80790:80815:0202/124846.255253:ERROR:cprocsp_api.cc(847)] Failed to load library /opt/cprocsp/lib/amd64/libcapi20.so: /opt/cprocsp/lib/amd64/libcapi20.so: cannot open shared object file: No such file or directory
[80867:80867:0202/124846.284819:ERROR:gl_factory.cc(120)] Requested GL implementation (gl=none,angle=none) not found in allowed implementations: [(gl=egl-angle,angle=default),(gl=egl-gles2,angle=none)].
[80867:80867:0202/124846.286045:ERROR:viz_main_impl.cc(196)] Exiting GPU process due to errors during initialization
[80834:80856:0202/124846.300218:ERROR:cprocsp_api.cc(847)] Failed to load library /opt/cprocsp/lib/amd64/libcapi20.so: /opt/cprocsp/lib/amd64/libcapi20.so: cannot open shared object file: No such file or directory
[80884:80884:0202/124846.307730:ERROR:gl_factory.cc(120)] Requested GL implementation (gl=none,angle=none) not found in allowed implementations: [(gl=egl-angle,angle=default),(gl=egl-gles2,angle=none)].
[80884:80884:0202/124846.308823:ERROR:viz_main_impl.cc(196)] Exiting GPU process due to errors during initialization
[80881:80881:0202/124846.325560:ERROR:cprocsp_api.cc(847)] Failed to load library /opt/cprocsp/lib/amd64/libcapi20.so: /opt/cprocsp/lib/amd64/libcapi20.so: cannot open shared object file: No such file or directory
[80909:80909:0202/124846.332028:ERROR:gl_factory.cc(120)] Requested GL implementation (gl=none,angle=none) not found in allowed implementations: [(gl=egl-angle,angle=default),(gl=egl-gles2,angle=none)].
[80909:80909:0202/124846.333840:ERROR:viz_main_impl.cc(196)] Exiting GPU process due to errors during initialization
[80947:80947:0202/124846.384751:ERROR:gl_factory.cc(120)] Requested GL implementation (gl=none,angle=none) not found in allowed implementations: [(gl=egl-angle,angle=default),(gl=egl-gles2,angle=none)].
[80947:80947:0202/124846.386187:ERROR:viz_main_impl.cc(196)] Exiting GPU process due to errors during initialization
[80978:80978:0202/124846.406508:ERROR:gl_factory.cc(120)] Requested GL implementation (gl=none,angle=none) not found in allowed implementations: [(gl=egl-angle,angle=default),(gl=egl-gles2,angle=none)].
[80978:80978:0202/124846.408010:ERROR:viz_main_impl.cc(196)] Exiting GPU process due to errors during initialization
flutter: !!!!!!! LoadTimeData: {"brandId":"yandex","flutterSuggestResizeAlgo":"","smartboxDeleteSuggestItem":"Remove suggestion","smartboxSuggestAdLabelText":"advertisement","smartboxSuggestAdsEnabled":false,"smartboxSuggestMaxMatchesCount":10,"smartboxSuggestRichFactEnabled":false,"smartboxSuggestSwitchToTabButtonShortText":"Tab","smartboxSuggestSwitchToTabButtonText":"Switch to tab","smartboxSuggestYandexZenMatchTitle":"Yandex Search, Zen, News","smartboxTabManagerButtonEnabled":false,"smartboxUiConfigEnabled":false,"smartboxYandexZenLogoChangeEnabled":false,"smartboxYandexZenLogoEnabled":true,"smartboxYandexZenTitleEnabled":true}
flutter: Send pageReady: null
flutter: "SmartboxClient@157255132 incoming message: update-search-panel-keywords"
Warning: vkCreateInstance: Found no drivers!
Warning: vkCreateInstance failed with VK_ERROR_INCOMPATIBLE_DRIVER
    at CheckVkSuccessImpl (../../third_party/dawn/src/dawn/native/vulkan/VulkanError.cpp:88)
    at CreateVkInstance (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:458)
    at Initialize (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:344)
    at Create (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:266)
    at operator() (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:521)

Attempted to use various nixGL wrappers, didn't work

Not fixed


[Bug]: Adding Zooz ZSE44 keeps failing (incomplete/multiple nodes added, all not working)

Checklist

[X]  I am not using Home Assistant. Or: a developer has told me to come here.
[X] I have checked the troubleshooting section and my problem is not described there.
[X] I have read the changelog and my problem is not mentioned there.

Deploy method
Docker
Zwavejs2Mqtt version
6.15.2
ZwaveJS version
9.6.2
Describe the bug
Sorry, it is always very unclear where the issue needs to be created. I use Home Assistant OS with ZwaveJS2MQTT installed as an add-on (so it is running in its own docker) but on their github there is no option for this integration... or should I be filing it under ZwaveJS?
I have 3 Zooz ZSE44 battery operated temperature/humidity sensors and am having an really hard time including. To eliminate battery charge related issues, the sensor is powered by a workbench power supply during inclusion / setup.
I provisioned the sensor but that actually seems to be part of the issue.
The sensor goes to sleep fast so to complete inclusion I have to press the zwave button 3x to initiate inclusion again. This may be leading to multiple non functional nodes being added but I believe Z2M should prevent this. Part of the issue may be that the sensor is provisioned and I am starting the inclusion manually.
In this specific case, I reset the sensor while looking at the logs and noticed that "smart start" was doing its thing. So I let it work but then saw it stalled so I pressed the button on the sensor 4 times (not 3!) which awakes the sensor. I believe I did so a few times, and I may also have triggered an interview as I saw something say it skipped it because the sensor was asleep. Regardless the setup is incomplete. This is just one of lots of failed attempts, but since I captured logs I wanted to share them.
This is what the device looks like:

No multiple nodes as I did not triple press the button this time as I saw it was doing something right after I reset the sensor.
While I have always struggled with these sensors, including them with provisioning has actually made it quite a bit harder. In a few cases I managed to add them, but they added without S2 security, or even asked me for the 5 digits even though they were provisioned. The provisioning also caused confusion as I was trying to include them manually, but apparently there was another process in the background doing the same and likely the two were interfering with each other. I realize there is some user error here, but I am guessing I am not the only one... is there a way to streamline the process guiding the user on what to do / not to do?
To Reproduce
Reset ZSE44
Awake sensor pressing button 4x
Expected behavior
Sensor is added properly
Additional context
{
"id": 114,
"name": "",
"loc": "",
"values": [
{
"id": "114-132-0-wakeUpInterval",
"nodeId": 114,
"commandClass": 132,
"commandClassName": "Wake Up",
"endpoint": 0,
"property": "wakeUpInterval",
"propertyName": "wakeUpInterval",
"type": "number",
"readable": true,
"writeable": true,
"label": "Wake Up interval",
"stateless": false,
"commandClassVersion": 1,
"min": 0,
"max": 16777215,
"list": false,
"lastUpdate":<PHONE_NUMBER>970
},
{
"id": "114-132-0-controllerNodeId",
"nodeId": 114,
"commandClass": 132,
"commandClassName": "Wake Up",
"endpoint": 0,
"property": "controllerNodeId",
"propertyName": "controllerNodeId",
"type": "any",
"readable": true,
"writeable": false,
"label": "Node ID of the controller",
"stateless": false,
"commandClassVersion": 1,
"list": false,
"lastUpdate":<PHONE_NUMBER>970
}
],
"groups": [],
"neighbors": [],
"ready": true,
"available": true,
"hassDevices": {},
"failed": false,
"inited": true,
"eventsQueue": [
{
"time": "2022-08-13T16:06:35.674Z",
"event": "wake up",
"args": [
4
]
},
{
"time": "2022-08-13T16:06:35.674Z",
"event": "interview stage completed",
"args": [
"ProtocolInfo"
]
},
{
"time": "2022-08-13T16:06:35.724Z",
"event": "interview stage completed",
"args": [
"NodeInfo"
]
},
{
"time": "2022-08-13T16:06:36.353Z",
"event": "value added",
"args": [
{
"commandClassName": "Multilevel Sensor",
"commandClass": 49,
"endpoint": 0,
"property": "Air temperature",
"newValue": 81.6,
"propertyName": "Air temperature"
}
]
},
{
"time": "2022-08-13T16:06:36.888Z",
"event": "value updated",
"args": [
{
"commandClassName": "Multilevel Sensor",
"commandClass": 49,
"endpoint": 0,
"property": "Air temperature",
"newValue": 82.4,
"prevValue": 81.6,
"propertyName": "Air temperature"
}
]
},
{
"time": "2022-08-13T16:06:37.418Z",
"event": "value added",
"args": [
{
"commandClassName": "Multilevel Sensor",
"commandClass": 49,
"endpoint": 0,
"property": "Humidity",
"newValue": 42,
"propertyName": "Humidity"
}
]
},
{
"time": "2022-08-13T16:06:37.945Z",
"event": "value added",
"args": [
{
"commandClassName": "Battery",
"commandClass": 128,
"endpoint": 0,
"property": "level",
"newValue": 100,
"propertyName": "level"
}
]
},
{
"time": "2022-08-13T16:06:37.946Z",
"event": "value added",
"args": [
{
"commandClassName": "Battery",
"commandClass": 128,
"endpoint": 0,
"property": "isLow",
"newValue": false,
"propertyName": "isLow"
}
]
},
{
"time": "2022-08-13T16:06:38.367Z",
"event": "value added",
"args": [
{
"commandClassName": "Version",
"commandClass": 134,
"endpoint": 0,
"property": "libraryType",
"newValue": 3,
"propertyName": "libraryType"
}
]
},
{
"time": "2022-08-13T16:06:38.368Z",
"event": "value added",
"args": [
{
"commandClassName": "Version",
"commandClass": 134,
"endpoint": 0,
"property": "protocolVersion",
"newValue": "7.13",
"propertyName": "protocolVersion"
}
]
},
{
"time": "2022-08-13T16:06:38.368Z",
"event": "value added",
"args": [
{
"commandClassName": "Version",
"commandClass": 134,
"endpoint": 0,
"property": "firmwareVersions",
"newValue": [
"1.20"
],
"propertyName": "firmwareVersions"
}
]
},
{
"time": "2022-08-13T16:06:38.368Z",
"event": "value added",
"args": [
{
"commandClassName": "Version",
"commandClass": 134,
"endpoint": 0,
"property": "hardwareVersion",
"newValue": 1,
"propertyName": "hardwareVersion"
}
]
},
{
"time": "2022-08-13T16:06:38.983Z",
"event": "value added",
"args": [
{
"commandClassName": "Version",
"commandClass": 134,
"endpoint": 0,
"property": "sdkVersion",
"newValue": "7.13.10",
"propertyName": "sdkVersion"
}
]
},
{
"time": "2022-08-13T16:06:38.983Z",
"event": "value added",
"args": [
{
"commandClassName": "Version",
"commandClass": 134,
"endpoint": 0,
"property": "applicationFrameworkAPIVersion",
"newValue": "10.13.10",
"propertyName": "applicationFrameworkAPIVersion"
}
]
},
{
"time": "2022-08-13T16:06:38.984Z",
"event": "value added",
"args": [
{
"commandClassName": "Version",
"commandClass": 134,
"endpoint": 0,
"property": "applicationFrameworkBuildNumber",
"newValue": 423,
"propertyName": "applicationFrameworkBuildNumber"
}
]
},
{
"time": "2022-08-13T16:06:38.984Z",
"event": "value added",
"args": [
{
"commandClassName": "Version",
"commandClass": 134,
"endpoint": 0,
"property": "hostInterfaceVersion",
"newValue": "unused",
"propertyName": "hostInterfaceVersion"
}
]
},
{
"time": "2022-08-13T16:06:38.984Z",
"event": "value added",
"args": [
{
"commandClassName": "Version",
"commandClass": 134,
"endpoint": 0,
"property": "hostInterfaceBuildNumber",
"newValue": 0,
"propertyName": "hostInterfaceBuildNumber"
}
]
},
{
"time": "2022-08-13T16:06:38.984Z",
"event": "value added",
"args": [
{
"commandClassName": "Version",
"commandClass": 134,
"endpoint": 0,
"property": "zWaveProtocolVersion",
"newValue": "7.13.10",
"propertyName": "zWaveProtocolVersion"
}
]
},
{
"time": "2022-08-13T16:06:38.985Z",
"event": "value added",
"args": [
{
"commandClassName": "Version",
"commandClass": 134,
"endpoint": 0,
"property": "zWaveProtocolBuildNumber",
"newValue": 423,
"propertyName": "zWaveProtocolBuildNumber"
}
]
},
{
"time": "2022-08-13T16:06:38.985Z",
"event": "value added",
"args": [
{
"commandClassName": "Version",
"commandClass": 134,
"endpoint": 0,
"property": "applicationVersion",
"newValue": "1.20.1",
"propertyName": "applicationVersion"
}
]
},
{
"time": "2022-08-13T16:06:38.985Z",
"event": "value added",
"args": [
{
"commandClassName": "Version",
"commandClass": 134,
"endpoint": 0,
"property": "applicationBuildNumber",
"newValue": 43707,
"propertyName": "applicationBuildNumber"
}
]
},
{
"time": "2022-08-13T16:07:18.577Z",
"event": "sleep",
"args": [
2
]
},
{
"time": "2022-08-13T16:07:50.220Z",
"event": "value updated",
"args": [
{
"commandClassName": "Multilevel Sensor",
"commandClass": 49,
"endpoint": 0,
"property": "Air temperature",
"newValue": 82.1,
"prevValue": 82.4,
"propertyName": "Air temperature"
}
]
},
{
"time": "2022-08-13T16:07:50.753Z",
"event": "value updated",
"args": [
{
"commandClassName": "Multilevel Sensor",
"commandClass": 49,
"endpoint": 0,
"property": "Humidity",
"newValue": 42,
"prevValue": 42,
"propertyName": "Humidity"
}
]
},
{
"time": "2022-08-13T16:08:48.933Z",
"event": "value updated",
"args": [
{
"commandClassName": "Multilevel Sensor",
"commandClass": 49,
"endpoint": 0,
"property": "Humidity",
"newValue": 60,
"prevValue": 42,
"propertyName": "Humidity"
}
]
},
{
"time": "2022-08-13T16:08:50.787Z",
"event": "wake up",
"args": [
1
]
},
{
"time": "2022-08-13T16:08:56.610Z",
"event": "value updated",
"args": [
{
"commandClassName": "Multilevel Sensor",
"commandClass": 49,
"endpoint": 0,
"property": "Humidity",
"newValue": 49,
"prevValue": 60,
"propertyName": "Humidity"
}
]
},
{
"time": "2022-08-13T16:08:59.256Z",
"event": "interview stage completed",
"args": [
"CommandClasses"
]
},
{
"time": "2022-08-13T16:08:59.256Z",
"event": "interview stage completed",
"args": [
"OverwriteConfig"
]
},
{
"time": "2022-08-13T16:08:59.256Z",
"event": "interview stage completed",
"args": [
"Complete"
]
},
{
"time": "2022-08-13T16:08:59.264Z",
"event": "ready",
"args": []
},
{
"time": "2022-08-13T16:08:59.266Z",
"event": "interview completed",
"args": []
},
{
"time": "2022-08-13T16:09:00.296Z",
"event": "sleep",
"args": [
2
]
},
{
"time": "2022-08-13T16:09:04.369Z",
"event": "value updated",
"args": [
{
"commandClassName": "Multilevel Sensor",
"commandClass": 49,
"endpoint": 0,
"property": "Air temperature",
"newValue": 82.3,
"prevValue": 82.1,
"propertyName": "Air temperature"
}
]
},
{
"time": "2022-08-13T16:09:04.904Z",
"event": "value updated",
"args": [
{
"commandClassName": "Multilevel Sensor",
"commandClass": 49,
"endpoint": 0,
"property": "Humidity",
"newValue": 44,
"prevValue": 49,
"propertyName": "Humidity"
}
]
},
{
"time": "2022-08-13T16:09:27.992Z",
"event": "wake up",
"args": [
1
]
},
{
"time": "2022-08-13T16:09:29.023Z",
"event": "sleep",
"args": [
2
]
},
{
"time": "2022-08-13T16:09:31.946Z",
"event": "wake up",
"args": [
1
]
},
{
"time": "2022-08-13T16:09:31.949Z",
"event": "interview started",
"args": []
},
{
"time": "2022-08-13T16:09:31.961Z",
"event": "sleep",
"args": [
2
]
},
{
"time": "2022-08-13T16:09:31.961Z",
"event": "interview stage completed",
"args": [
"ProtocolInfo"
]
},
{
"time": "2022-08-13T16:09:34.811Z",
"event": "interview started",
"args": []
},
{
"time": "2022-08-13T16:09:34.821Z",
"event": "interview stage completed",
"args": [
"ProtocolInfo"
]
},
{
"time": "2022-08-13T16:09:40.764Z",
"event": "wake up",
"args": [
1
]
},
{
"time": "2022-08-13T16:09:40.797Z",
"event": "interview stage completed",
"args": [
"NodeInfo"
]
},
{
"time": "2022-08-13T16:09:41.968Z",
"event": "interview stage completed",
"args": [
"CommandClasses"
]
},
{
"time": "2022-08-13T16:09:41.969Z",
"event": "interview stage completed",
"args": [
"OverwriteConfig"
]
},
{
"time": "2022-08-13T16:09:41.969Z",
"event": "interview stage completed",
"args": [
"Complete"
]
},
{
"time": "2022-08-13T16:09:41.971Z",
"event": "ready",
"args": []
},
{
"time": "2022-08-13T16:09:41.971Z",
"event": "interview completed",
"args": []
},
{
"time": "2022-08-13T16:09:42.999Z",
"event": "sleep",
"args": [
2
]
}
],
"hexId": "0xXXXX-0xXXXX-0xXXXX",
"dbLink": "https://devices.zwave-js.io/?jumpTo=0xXXXX:0xXXXX:0xXXXX:0.0",
"productLabel": "Unknown product 0xXXXX",
"productDescription": "0xXXXX",
"manufacturer": "Unknown manufacturer 0xXXXX",
"protocolVersion": 3,
"zwavePlusVersion": 2,
"zwavePlusNodeType": 0,
"zwavePlusRoleType": 6,
"nodeType": 1,
"endpointsCount": 0,
"endpointIndizes": [],
"isSecure": false,
"security": "None",
"supportsSecurity": false,
"supportsBeaming": true,
"isControllerNode": false,
"isListening": false,
"isFrequentListening": false,
"isRouting": true,
"keepAwake": false,
"maxDataRate": 100000,
"deviceClass": {
"basic": 4,
"generic": 7,
"specific": 1
},
"deviceId": "undefined-undefined-undefined",
"status": "Asleep",
"interviewStage": "Complete",
"statistics": {
"commandsTX": 81,
"commandsRX": 67,
"commandsDroppedRX": 16,
"commandsDroppedTX": 1,
"timeoutResponse": 24,
"rtt": 24.5,
"rssi": -92,
"lwr": {
"protocolDataRate": 2,
"repeaters": [],
"rssi": -93,
"repeaterRSSI": []
}
},
"lastActive":<PHONE_NUMBER>433,
"minBatteryLevel": 100,
"batteryLevels": [
100
],
"_name": "NodeID_114",
"lastReceive":<PHONE_NUMBER>433,
"errorReceive": true,
"errorTransmit": false
}

Zwave Debug Logs that did not 'fit' in the issue above (couldn't add file or paste logs):
Adding ZSE44 zwave debug logs.log

First things first: If you provision the node with SmartStart, power it on, then just let it do its thing. If the node was included before, it might need a factory reset.
During the inclusion attempt you logged, the controller was still busy communicating with Node 112, so it couldn't handle the inclusion request immediately. After a few seconds, that worked too and node 114 got included without issues. You should have seen a notification pop up that the node was added with S2_Authenticated.
For some reason I need to investigate, the driver starts requesting the security classes again during the following interview and thats where things went wrong. The response to one of these requests came before the confirmation that the request was received. Z-Wave JS currently doesn't match the response to the request correctly in these cases. Afterwards it attempted insecure communication which times out. Interestingly I always seem to link there from Zooz device issues.
Try re-interviewing the device and set the checkbox for "reset security classes".


Some users don't have a join_date

Is this normal? See https://participedia.xyz/users/134860

Fixed in PR #256 by using real user data.


Sample config: update LOCAL_ROOT_URL description for PROTOCOL = 'unix' case

Update the sample configuration description for the LOCAL_ROOT_URL
configuration variable to mention the special case required if PROTOCOL
is set to 'unix'.
Fixes #3741.

Updated and rebased on master.

Re-updated with a slightly simpler formulation more in line with other doc comments.

Typo fix for 'unix' -> unix and re-updated my repo as something strange happened.


docs: Add dynaconf API to docs with mkdocstrings

Introduces automatic generation of the API reference for dyanconf using mkdocstrings.
By simply including a markdown file with:
::: dynaconf

... and adding this to the navigation, it autogenerated the API from everything listed in the API in the __init__.py:
https://github.com/dynaconf/dynaconf/blob/0390393c27a7ef27104bbda2426b3382dcc7fb9f/dynaconf/__init__.py#L30-L42
This is a lot simpler than what was generated in the attempted PR: #1057 which was following a recipe to build out a reference for all modules within the package. Although it was good learning, I suggest that this one is closed.
From the generated docs, there are probably some follow up changes that can be made to the docstrings to improve the appearance in the API reference. Open to guidance on this.
Resolves: #997

These are the features of the Python handler for mkdocstrings. Also the look and feel can be tailored in lots of ways with these options. Let me know if there's anything worth exploring.

I think it's worth it to get the type hinting consistent and all docstrings following Google style for the current top level API

Yeah, that would be awesome.

Do you want the dynaconf mod listed at the top of the TOC? This can be switched off if desired.

I would omit that as it does not point to any content.

Is the full path desired or is that unnecessary clutter?

I'm not 100% sure about this, but I slightly prefer the full path because it's more explicit. We can revisit it later if we feel like its cluttering the view.

Also, for the css style to work you have to include it using mkdocs.yml: https://squidfunk.github.io/mkdocs-material/customization/#additional-css

Thanks again for the feedback, I've made a couple more changes.

I think it's worth it to get the type hinting consistent and all docstrings following Google style for the current top level API

Yeah, that would be awesome.

Do you want me to try and get this in shape for the top level API on this ticket so that it looks good when merged in? It can form part of the discussion on #1060.

@pedro-psb , there is a typo dyanconf API instead of the dynaconf API.
Also when it's this supposed to appear on https://dynaconf.com ? I don't see it yet.

@pedro-psb , there is a typo dyanconf API instead of the dynaconf API.
Also when it's this supposed to appear on https://dynaconf.com ? I don't see it yet.

Well spotted, I will fix it on #1062.
I think a new release version needs to be published before dynaconf.com is updated.
typos may be worth looking at in the near future to prevent spelling errors creeping in.

I think a new release version needs to be published before dynaconf.com is updated.
Last release was on  2023-10-30 according to  https://github.com/dynaconf/dynaconf/blob/master/CHANGELOG.md

Almost 4 months ago, do we know when is the next planned release?

@ecerulm Thanks for catching that. There is not a fixed date but we are planning to do it soon, maybe in the next week or so.

I've just started a blog and I wrote up on my learnings completing this PR. Here it is for future reference!
https://mitches-got-glitches.github.io/developer_blog/

@mitches-got-glitches I've just read it, that's a great storytelling flow! I'm glad this was a valuable learning experience for you.
I feel like knowing this kind of skill (doc tooling) makes someone able to contribute to so many projects that require that kind of improvement.
And it is good to hear that the "good first issue" works :sweat_smile:


Refactoring Token

Fixes #280
Description
This is just a proposal for better implementation of the Token concept, currently represented as a couple of interfaces with repeated concepts in different attributes like address-contract, amount-balance, decimals-precision or logo-logoURI
This PR implements a simple class hierarchy merging all source formats into one unified class, which can be enhanced with as many utility functions as we need in the process of developing this new platform.
This is a diagram of the new classes to represent tokens and balances.

Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have cleaned up the code in the areas my change touches
[x] My changes generate no new warnings
[x] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings
[x] I have removed any unnecessary console messages
[x] I have included all english text to the translation file
[x] I have created a new issue with the required translations for the currently supported languages
[ ] I have added appropriate test coverage

This PR is actually blocked because it was developed on top of the last not-merged-yet @EJSG's PR.
It would be a good thing to wait until that PR gets approved and merged.

Questions on the graph, where is the dimension of the price kept so what fiat is it, USD, ETH, PESO whatever? Shouldn't there be many prices for each token, one in each possible currency (not only fiat but every other currency out there eth, btc ...)?

What a nice question!!! because I can extract a hidden requirement for the following function:
TokenPrice.getAmountInThisToken(amount, targetToken): BN

and with this new function, I can answer your question:
All Tokens have a unique price and that price can be expressed in any other currency/token.
In this implementation, the information about the token price is hidden behind the TokenMarketData.info so it can be anything (currently covers the indexer response). Once we have that info for the token, the token.price.isAvailable variable becomes true and then you would be able to ask the following:
const otherToken = await this.getToken('ETH');
const converted = balance.token.price.getAmountInThisToken(
   balance.amount,
   otherToken,
);
// converted is a BigNumber containing the amount of ETH the balance is worth

I will add this function right now !!

I'm closing this PR in favor of this other new PR because it was easy that rebase with the current develop branch
https://github.com/telosnetwork/telos-wallet/pull/362


fix(comment): update URL

[x] I have read CONTRIBUTING.md
[x] I have read CODE_OF_CONDUCT.md

Thanks for the PR!
I decided to circumvent the problem entirely and refer to :h commenting directly. Should be resolved on latest main.


SW551920 : Updates to Memory Throttling and Error Thresholds per Thermal Team request

Change are
MEMCTRL_THROTTLE_TEMP_DEG_C    82-->84
MEMCTRL_ERROR_TEMP_DEG_C       85-->89
DIMM_THROTTLE_TEMP_DEG_C       76-->77
DIMM_ERROR_TEMP_DEG_C          79-->82
PMIC_THROTTLE_TEMP_DEG_C       62-->68
PMIC_ERROR_TEMP_DEG_C          65-->73

Can one of the admins verify this patch?

I will ask Brian Werneke to review and comment. This is a requirement change specific for Everest.

Reviewed these edits, and all desired changes are correct.


Fix macOS binary releases

Depends on src-d/ci, though, since we depend on cgo.

This is already done


Serve updates

Remove usage of DOCKER_BUILDKIT for compatibility with older versions of docker.
Minor fixes (https://github.com/open-mmlab/mmdetection/pull/4810#issuecomment-813928693)

Thank you for your contribution！


Create Median of 2 sorted Arrays in CPP

Please assign this to me under hacktober fest.

I am assigning you but before this please let me know how you are going to contrbute in this issue?

I have added a pull request for the following code in C++.

median.txt

median.txt

#https://github.com/UzairHussain193/Get_Start_with_OpenSource_Contributions/files/12837600/median.txt

i have added the pull request please merge it

Please assign me this task


boards: b_u585i_iot02a: Add a non-secure target

Provide a _ns target for b_u585i_iot02a board.
Tested using tfm_ipc sample.

I tried building this on OS X, but had to make the following modification to https://github.com/zephyrproject-rtos/trusted-firmware-m/blob/master/platform/ext/target/stm/common/scripts/postbuild.sh to point to the GNU version of readlink installed via brew install coreutils:
if [[ "$OSTYPE" == "darwin"* ]]; then
SCRIPT=$(greadlink -f $0)
else
SCRIPT=$(readlink -f $0)
fi

This then builds and runs the post build scripts, but when I run west flash it only seems to be flashing the NS binary:
$ west build -p auto -b b_u585i_iot02a_ns zephyr/samples/tfm_integration/tfm_ipc
...
[162/162] Linking C executable zephyr/zephyr.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:       19224 B       512 KB      3.67%
            SRAM:       11304 B       786 KB      1.40%
        IDT_LIST:          0 GB         2 KB      0.00%
preprocess bl2 file
 updated
 updated
 updated
 updated
 updated
 updated
 updated
 updated
 updated

$ west flash
-- west flash: rebuilding
[0/14] Performing build step for 'tfm'
ninja: no work to do.
-- west flash: using runner stm32cubeprogrammer
-- runners.stm32cubeprogrammer: mass erase requested
      -------------------------------------------------------------------
                        STM32CubeProgrammer v2.9.0
      -------------------------------------------------------------------

ST-LINK SN  : 002A00363156501320323443
ST-LINK FW  : V3J7M3
Board       : B-U585I-IOT02A
Voltage     : 3.28V
SWD freq    : 24000 KHz
Connect mode: Under Reset
Reset mode  : Hardware reset
Device ID   : 0x482
Revision ID : Rev B
Device name : STM32U575/STM32U585
Flash size  : 2 MBytes
Device type : MCU
Device CPU  : Cortex-M33
BL Version  : 0x92
Debug in Low Power mode enabled

Mass erase ...

Mass erase successfully achieved
      -------------------------------------------------------------------
                        STM32CubeProgrammer v2.9.0
      -------------------------------------------------------------------

ST-LINK SN  : 002A00363156501320323443
ST-LINK FW  : V3J7M3
Board       : B-U585I-IOT02A
Voltage     : 3.28V
SWD freq    : 24000 KHz
Connect mode: Under Reset
Reset mode  : Hardware reset
Device ID   : 0x482
Revision ID : Rev B
Device name : STM32U575/STM32U585
Flash size  : 2 MBytes
Device type : MCU
Device CPU  : Cortex-M33
BL Version  : 0x92
Debug in Low Power mode enabled

Memory Programming ...
Opening and parsing file: zephyr.hex
  File          : zephyr.hex
  Size          : 19224 Bytes
  Address       : 0x08074000

Erasing memory corresponding to segment 0:
Erasing internal memory sectors [58 60]
Download in Progress:
[==================================================] 100%

File download complete
Time elapsed during download operation: 00:00:00.227

RUNNING Program ...
  Address:      : 0x8000000
Warning: The core is locked up
Start operation achieved successfully

This should be flashing tfm_merged.hex.

This should be flashing ``

This is what I documented in board doc:
west flash --hex-file build/tfm_merged.hex

This should be flashing tfm_merged.hex

This is what I documented in board doc:
west flash --hex-file build/tfm_merged.hex

Missed that, thanks. Looks good other than the CI failures, presumably due to the script hard-coding the toolchain, which should be arm-zephyr-eabi-gcc for the Zephyr SDK: https://github.com/zephyrproject-rtos/trusted-firmware-m/blob/master/platform/ext/target/stm/common/scripts/gcc/preprocess.sh#L23

Missed that, thanks. Looks good other than the CI failures, presumably due to the script hard-coding the toolchain, which should be arm-zephyr-eabi-gcc for the Zephyr SDK: https://github.com/zephyrproject-rtos/trusted-firmware-m/blob/master/platform/ext/target/stm/common/scripts/gcc/preprocess.sh#L23

Ahhh, now I know what these CMake lines were supposed to do... Fixed.

I noticed after flashing TF-M that you are unable to go back to a normal non TF-M application doing some variation of:
$ west build -p auto -b b_u585i_iot02a zephyr/samples/hello_world
$ west flash

The standard ST debug tool is unable to erase the flash memory from the secure region, and the previous TF-M image will continue to execute when you reset.
In order to 'recover' the TF-M device, you need to run 'build/tfm/regression.sh' once, and then you can rebuild the non-TFM image and flash it.
This should probably be added as a note to the board.rst file, or the correct command to erase the entire chip should be added if there is an alternative to running 'regression.sh', which is only available as a build artifact of a 'ns' application, and may not be obvious to new users testing out TF-M and going back to a non TF-M app.

@microbuilder I've updated board configuration and documentation, taking into account your suggestions. Please let me know if this is fine and I'll then update other STM32 TFM targets.

Doc build error should likely be fixed with https://github.com/zephyrproject-rtos/zephyr/pull/41865


[terra-brand-footer] FATAL ERROR: JavaScript heap out of memory

Bug Report
Description

Running a yarn install on project which includes the terra-brand-footer results in FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory  on Mac-Sierra. Works fine on Mac-High Sierra
Steps to Reproduce

Terra component 'terra-brand-footer' was added to an existing app. (OS used - mac, high sierra)
A user with mac-sierra pulled the code, but is not able to do a  yarn install
User gets the error as mentioned in the gist link

Additional Context / Screenshots

Gist: https://gist.github.com/Trupti-Baliga/742b2e935d615fc2192064864b1029dc
Expected Behavior

Terra-brand-footer should be visible on the page.
Possible Solution

Environment

Component Name and Version: Terra Brand Footer, v1.4.0
Browser Name and Version: Google Chrome
Node/npm Version: [e.g. Node 8/npm 5] Node v6.9.4/npm 3.10.10
Webpack Version: ^2.6.1 , webpack-manifest-plugin: ^1.1.0
Operating System and version (desktop or mobile): Mac Sierra

@bjankord : https://github.cerner.com/hisubmissionsdev/submissions/tree/HISUBDEV-119-Terra-Brand-Footer
This is a link to the branch in which we are implementing the Terra-Brand-Footer.

@bjankord : Is there any update on this issue?

@Trupti-Baliga  I am looking at the dependencies you pull into your project and your project is still on React 15. The terra-brand-footer required React 16. This component was developed after our React 16 upgrade, so a react 15 version is not available for consumption.

@Trupti-Baliga Please upgrade to react 16 and test again.

@emilyrohrbough @bjankord : Updated the react version to 16. Still facing the same issue.
Branch : https://github.cerner.com/hisubmissionsdev/submissions/tree/HISUBDEV-119-Footer-with-Updated-React

@Trupti-Baliga  You still need to bump your terra depenedencies to the correct versions to prevent mixing v15 and v16 of react. For example, you have defined terra-button v1.14.0, however to be on a react 16 compatible version, this needs to be bumped to a minimum of v2.0.0. Please check the Changelogs of the components your project uses to find the minimum version that supports react 16.

@bjankord : This issue can be closed. It has been solved.


changing design

after changing design gui looks good and user play this

hey can  you assign this issue to me, would love to work on this.


Graphql

Created GraphQL plugin for Javalin.

[X] Create GraphQL example in Kotlin
[x] Add Test

GraphQL feature for me is closed.

Thanks, that's really cool @7agustibm. Review might take some time. We're considering if we should move plugins to separate modules.

Do you want me to create some proof of concept?

Proof of concept for what?

Create GraphQL plugin for Javalin.
For example
import io.javalin.Javalin
import io.javalin.GraphQL

fun main(args: Array<String>) {
  val app = Javalin.create().start(7000)
  app.get("/") { ctx -> ctx.result("Hello World") }

  JavalinGraphql.addPackage("io.javalin.graphql")
    .register(QueryExample(message))
    .register(MutationExample(message))
    .register(SubscriptionExample(message))
    .build("/graphql", app)
}

Sure!

Hi! Here is the PoC: https://github.com/7agustibm/javalin-graphql-plugin

Great, I will have a look soon!

@tipsy Can’t we split javalin into modules after merging this? It looks good and I would love to use it.

@JStumpp I guess it's a bit late to answer you now, but we just finished the module split, so no 😅
@7agustibm Sorry for the delay! Could you rebase thiss and add it as a module?

Yes, I'm working for creating a graphql plugin. I am going to use javalin-graphql as an example.

Great, looking forward to it!

View #940


[SPARK-38127][SQL][TESTS] Fix bug of EnumTypeSetBenchmark and update benchmark result

What changes were proposed in this pull request?
EnumTypeSetBenchmark  use to compare the create and contains performance of EnumSet and HashSet.Before this PR, there are some logical errors in the bench case, for example testContainsOperation :
https://github.com/apache/spark/blob/9d0563733bacc39ffbb7a07e5d3fc6de71d0cfb3/sql/catalyst/src/test/scala/org/apache/spark/sql/connector/catalog/EnumTypeSetBenchmark.scala#L102-L110
Use HashSet circulates 100000 times(valuesPerIteration is 100000) and  Use EnumSet circulates only once.
So this pr fix this bug and update benchmark result.
Why are the changes needed?
Bug fix.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass GA

cc @srowen

Is the idea simply that the benchmark was run on substantially different hardware before?

Is the idea simply that the benchmark was run on substantially different hardware before?

No, this pr focuses on bug fix, for example testContainsOperation:
https://github.com/apache/spark/blob/9d0563733bacc39ffbb7a07e5d3fc6de71d0cfb3/sql/catalyst/src/test/scala/org/apache/spark/sql/connector/catalog/EnumTypeSetBenchmark.scala#L102-L110
Use HashSet circulates 100000 times(valuesPerIteration is 100000) and  Use EnumSet circulates only once.
It's my bad, I made a mistake in writing this case before.

Thanks all


ERROE %1 Not windows 32 applications

Two possibilities:

A precompiled version of the addon is being used on the wrong platform
Npcap is not installed

I can install Npcap. But I was not solved :/ Please help me. I was trying maybe 48 hours.

How did you install cap? If you simply copied an existing node_modules directory to another system, that may cause this error. Additionally, if you did actually execute 'npm install cap' on this particular system, can you post the actual console output?

My mac :

Try windows pc :

I use electronjs.

Yeah solved win32 problem but this new problem :


Connection management in express

What is the preferred method of managing connections in express.js? one connection at startup? Looking through the code, I couldn't see any connection pool management, but may have missed it.

arangojs manages the connection using an HTTP agent. By default it creates the agent for you and sets the maximum number of sockets it can use. You can either modify the options it uses to create the agent or create an agent yourself.
You can share an HTTP agent between multiple clients but arangojs internally creates an additional queue to prevent the agent from being flooded when a large number of new requests are made (this sounds inefficient but has drastically improved the performance).
Personally, I would just create one Database (the class exported by arangojs) instance at startup and inject it into your express app.
If you don't find the default configuration to work for you, you should try adjusting the maxSockets setting in agentOptions and make sure it aligns with the number of V8 threads of your ArangoDB installation.
The recently published benchmarks were performed using arangojs with the default settings (except for maxSockets), so that should give you an idea of the general characteristics.


Can kylemanna/openvpn run as OpenVPN client?

I have a machine running CoreOS, it is a container OS, all application ran as docker containers.
I generate inline OpenVPN client configuration file with kylemanna/openvp's ovpn_getclient.  I copy the configuration file to the machine running CoreOS and try to run kylemanna/openvp's openvpn as client:
docker run -v $PWD:/etc/openvpn -w /etc/openvpn --rm -it --net host --cap-add=NET_ADMIN kylemanna/openvpn openvpn --config victor.wong-hko.ovpn --verb 11
And got TLS error:

Tue Sep 26 05:32:36 2017 us=285081 TLS: control channel, op=P_CONTROL_V1, IP=[AF_INET]<IP_ADDRESS>:1194
Tue Sep 26 05:32:36 2017 us=285209 TLS: initial packet test, i=0 state=S_SENT_KEY, mysid=735e7cf6 65f36b6a, rec-sid=89a1c4ac 27739f32, rec-ip=[AF_INET]<IP_ADDRESS>:1194, stored-sid=89a1c4ac 27739f32, stored-ip=[AF_INET]<IP_ADDRESS>:1194
Tue Sep 26 05:32:36 2017 us=285291 TLS: found match, session[0], sid=89a1c4ac 27739f32
Tue Sep 26 05:32:36 2017 us=286553 DECRYPT FROM: 2a7251d3 5d1d2ecc 4c0c2dd9 32d0516a f3bcfff7 00000002 59ca8f3a 2089a1c[more...]
Tue Sep 26 05:32:36 2017 us=286685 PID_TEST [0] [TLS_WRAP-0] [0]<PHONE_NUMBER>:1<PHONE_NUMBER>:2 t=1506403956[0] r=[0,64,15,0,1] sl=[63,1,64,528]
Tue Sep 26 05:32:36 2017 us=286775 TLS: received control channel packet s#=0 sid=89a1c4ac 27739f32
Tue Sep 26 05:32:36 2017 us=286936 ACK received for pid 1, deleting from send buffer
Tue Sep 26 05:32:36 2017 us=287023 ACK read ID 1 (buf->len=1118)
Tue Sep 26 05:32:36 2017 us=287095 ACK RWBS rel->size=8 rel->packet_id=00000001 id=00000001 ret=1
Tue Sep 26 05:32:36 2017 us=287210 ACK mark active incoming ID 1
Tue Sep 26 05:32:36 2017 us=287277 ACK acknowledge ID 1 (ack->len=1)
Tue Sep 26 05:32:36 2017 us=287384 TLS: tls_multi_process: i=0 state=S_SENT_KEY, mysid=735e7cf6 65f36b6a, stored-sid=89a1c4ac 27739f32, stored-ip=[AF_INET]<IP_ADDRESS>:1194
Tue Sep 26 05:32:36 2017 us=287458 TLS: tls_process: chg=0 ks=S_SENT_KEY lame=S_UNDEF to_link->len=0 wakeup=604800
Tue Sep 26 05:32:36 2017 us=287528 ACK reliable_can_send active=0 current=0 : [2]
Tue Sep 26 05:32:36 2017 us=287620 BIO write tls_write_ciphertext 1118 bytes
Tue Sep 26 05:32:36 2017 us=287694 Incoming Ciphertext -> TLS
Tue Sep 26 05:32:36 2017 us=287826 SSL state (connect): SSLv3 read server hello A
Tue Sep 26 05:32:36 2017 us=288305 VERIFY ERROR: depth=0, error=self signed certificate: CN=<IP_ADDRESS>
Tue Sep 26 05:32:36 2017 us=288419 SSL alert (write): fatal: unknown CA
Tue Sep 26 05:32:36 2017 us=288534 OpenSSL: error:14007086:SSL routines:CONNECT_CR_CERT:certificate verify failed

The same configuration file works well with OpenVPN client in windows and CentOS 6.
Since CA is inline in client configuration file, I have no idea why there is unknown CA error.

After research, it is openvpn package issue.
I create another docker image from alpine with openvpn package installed. It has the same issue. While it works well with image of debian with openvpn package installed.

Alpine is pretty ahead of the curve - you may also be experiencing version or encryption suite mismatches. What do the server logs say?


MSID: 99303 Version: 2 DOI: 10.1101/2<IP_ADDRESS>8866

MSID: 99303
Version: 2
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>8866
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=99303
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>8866

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/99303v2
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>8866
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/99303/v2/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

@acollings, Could you assist with tweaking the assessment, to avoid using compellingly? Thanks!

Thanks @fred-atherden -- should be sorted

Thanks!


Create automated tests

What feature would you like to have?
We don't run any automated test on our components, or on the website as a whole.
I think we would benefit from having some basic tests (even if it's just to confirm that a certain text actually shows on a rendered page), or that our comparator actually works.
What problem will be solved by having the feature?
Reduce manual review work, improve confidence we're not breaking things when we update dependencies, or update our code.
Do you want to help making the feature?
I'm willing to help out, but I don't know how get to Jest or Cypress set up for use with our Next.js app.
Also I need some "templates" or basic tests that I can then try enhancing.

I had this in mind and have implemented tons of tests with both Jest and Cypress for Next.js projects in the past. It was just a matter of time, but definitely I still interested in implementing them.
There are tons of examples within Next.js repo, so you can find some references there about how to set it up with Jest. This is an example with Jest + TS: https://github.com/vercel/next.js/blob/canary/examples/with-typescript-eslint-jest/README.md

Do we still want to add more tests, or are we happy with having just the Cypress tests for now? I'm not able to work on any Jest tests, as I've not really written any new Jest tests ever.

I think we can consider this ticket done.
There are more things related to testing we can address in other tickets tho:

Stubbing requests in Cypress (already has a ticket)
Unit/integration tests with Jest + Testing Library
Visual diff testing

I've created issues for the remaining items, see:

#510
#511

Closing this issue now. 😄


Ability to add other app's (such as a document library) and assoicate with hub site

Is it possible somehow to add other app's such as a document library to the hierarchy.json file and associate them with the hub site  or is this only currently possible with team sites?

hiearchy.json is used only to describe what sites to auto provision when running the starter kit deploy.ps1 PS script.
If you want to add other apps, recommended approaches including updating one of the included PnP Provisioning templates, creating a new provisioning template and applying that to your specific sites, or you could create an additional site script / site design and using SPO management shell and PS, apply the site design over the site(s) you create.
There are additional options including creating a site design and site script first, then allowing the site creation process to run, and I am sure others can come up with yet more approaches. Any of these techniques would require that you customize the starter kit to meet your needs.

Has anyone out there got any sample PS Script of how to provision a site page, name it, add an app such as a document library and associate it with the hub site that I can use as a reference? Hopefully that I can simply insert into this solution :)

@nicholas-morris this starter kit has the scaffolding you need. The provisioning template to do much of what you need may be found here:
https://github.com/SharePoint/sp-starter-kit/blob/master/provisioning/hubsite.xml
Review line's 39 onward to add a page, add content, add components, libraries, etc. To provision this template to a site, you will want to review the general process here:
https://github.com/SharePoint/sp-starter-kit/blob/master/provisioning/deploy.ps1


internal/modules/cjs/loader.js:589

Just a problem with my devs configuration keys in my case.

I took the npm folder in the installation directory of nodejs "\node_modules\npm" copy them to "C:\Users% User%\AppData\Roaming\npm\node_modules\npm " So the problem is solved =))

These don't work for me. I even reinstalled node

Try this works on my end.
* rm -rf  node_modules

* rm package-lock.json

* npm install

* npm start

Thanks a lot. 👍

This doesn't work on my end .

rm -rf  node_modules

rm package-lock.json

npm install

npm start

node index.js
This gives this error because the file and path cannot be found. It becomes an idea for friends who will experience this problem in the future.


V2.2 cannot enter the OC boot interface. It's black.

V2.2 cannot enter the OC boot interface. It's black.
I need your help！

Please do not post duplicates #88


Add support for optional anonymous ID

Adding an extra provider specific setup method for this just didn’t sit well with me.

Segment: Uses new anonymous ID support https://github.com/segmentio/analytics-ios/pull/485
Others: Assigns the anonymous ID as a user property with the key anonymous_id.

Made the tests green :+1:

Awesome, thanks!

Turns out that there is some more breakage, will send a PR for that in a sec.

:+1:


Support /mermaid in threads

I tried to use /mermaid in a thread today but Slackbot let me know that it doesn't work in threads. Is this easy to implement?

Sadly this is a Slack limitation:

Slash commands created by developers cannot, however, be invoked in message threads.

https://api.slack.com/interactivity/slash-commands
There is no way around this.
I'm wondering about your usage, is there some other way mermaid could help in a thread? 👀

Ah, that's too bad.
We're heavy users of Slack threads at work. I had a case where I wanted to explain something on a thread and a quick mermaid diagram was just the ticket. I typically use mermaid live to build the diagram initially -- due to the live preview -- but wanted to share it in Slack with your app so it would be easy to share both the markup and the image.


HTTP Error 500

I have successfully run spark pi example in sparkoscope and I can see all the custom metrics in the UI.
But for my own spark application which I have written in java for spark 2.0.0 is showing an error.
I later built my application for spark 2.1.0 yet same error is thrown. I am not sure what is wrong (my application can successfully complete, only I cant see all the custom metrics in the UI).
I have attached the screenshot of the error below:

Hi, so I didn't manage to recreate the issue on my setup.
Can you send me the spark-defaults.conf and metrics.properties files to have a look?
Are the metrics stored successfully on HDFS?

It was solved later, mostly probably machine issues, sorry for late reply.


[File Explorer] Feature Suggestion: Instant & atomic non-permanent deletion of directories (to Recycle Bin) by first moving to temp

Description of the new feature / enhancement
It's difficult to delete large (and deeply nested) directories, for example caches of package managers (e.g. node_modules of npm), using Explorer directly, because you need to wait for the entire operation to complete before you can reuse the same filename. There are also common issues like some filenames making the path too long for Explorer, any file access/lock issues (when the move works but deletion doesn't, i.e. sometimes we have to wait or kill the process, other times the file can be removed on startup). In addition to wanting this action to be fast, sometimes we prefer not to remove the files permanently in order to keep the option of recovering the files.
Interestingly, one of the fastest solutions how to "get rid of the files" is to move the directory instead of deleting it directly. This also doesn't require us to make the decision to permanently remove the files (without going to the Recycle Bin). My suggestion is to use a similar or better technique, using any temp directory to hold the remaining files until they are deleted (moved to Recycle Bin), so that the existing file path is empty as soon as possible and user can re-use it. This would also enable atomic deletion, removing risks of anything new being added to the directory during its removal. It could be effectively a script that's executed instead of the action of deletion to Recycle Bin, making it transparent to the user, but it'd need to integrate with the existing "Deleting" UI in Explorer, so this scope depends on what's reasonable for PowerToys to implement (this could be also implemented in Explorer after all, but it likely won't be). Because this is a power tool configuration, the edge case scenarios like cancellation in the middle of the process, access failures after the directory has been moved, or the cleanup of files after failure (including OS crash) likely don't need to be perfect, but they should be consistent from user's perspective, and especially not done as a black-box. For example, if the temporary recycle bin cache is a well-known location, PowerToys could notify (on startup?) about any unfinished operations and let us choose the course of action.
I don't know about a direct way to move files to Recycle Bin using command line, but there seem to be some solutions based on:

https://superuser.com/questions/24662/what-is-the-command-line-way-of-sending-files-to-the-recycle-bin

However, as the deletion would be performed from a different location, the Original Location in Recycle Bin must be changed to point towards the correct place (not to a temp directory) to make the user experience safe and consistent. The Explorer actions of Undo/Redo thus also need to be supported (preferably with their safety improvement https://github.com/microsoft/PowerToys/issues/16337) (though Redo could optionally use the old slow deletion behavior), consistency being the primary advantage over random scripts.

There are also various third party solutions for deleting large files more efficiently without going through Recycle Bin, for example rimraf. It'd be great if we also agreed on one such solution for power users (consensus on anything open-source?) that PowerToys could officially support and integrate with Explorer (e.g. to be used on Shift+Delete?). This fast permanent deletion is tracked at https://github.com/microsoft/PowerToys/issues/1643.
Scenario when this would be used?
We're often dealing with large directories, especially as software developers when using third party tools that bloat our hard drive.
We usually prefer to prioritize our productivity by making actions like deletion instant whenever possible.
If there are popular workarounds out there, it's preferable to have them standardized and integrated with shell in a way where trash can keep going to Recycle Bin, rather than having us come up with ad-hoc scripts, installing random third party apps, or manually creating dozens of temporary directories that we have to keep in mind for cleanup at later time.
Supporting information

https://spblog.net/post/2020/06/10/how-to-effectively-delete-node-modules-on-windows
https://stackoverflow.com/questions/186737/whats-the-fastest-way-to-delete-a-large-folder-in-windows
https://www.quora.com/Whats-better-Moving-items-Or-copying-them-then-deleting-the-old-one

"Within a filesystem, when you move an item, you are just changing the name of it. No data bits on disk are moved at all."

https://stackoverflow.com/questions/28175200/how-to-delete-node-modules-deep-nested-folder-in-windows

@Jay-o-Way Renaming the folder is pretty much the same as moving it, but the key here is that it should be no longer available near the original location during the deletion. The most common example would be using a Git version control over a project, in which case any "renamed folder" will conflict with .gitignore and further with actions like reset / checkout. On the other hand, when you manage personal data, your intention would be not to forget to clean the directory even if the process crashes and you forget to complete the workflow, leaving your data in inconsistent state with redundant files. The current state of process must be intuitively tracked so that you can keep it out of your mind, e.g. imagine deleting 10 directories at once, and then having your drive disconnect or files being locked.
Unlike https://github.com/microsoft/PowerToys/issues/1643, this feature is explicitly concerned with moving the data to Recycle Bin, because that's the Windows-specific default behavior that users expect when they want to keep the option of recovery from any mistake (even after a long time), and it's way more difficult (if not impossible) to automate from command line. The case of "deleting large files more efficiently without going through Recycle Bin" can be surely tracked in the existing issue.

To me, you are asking for fast delete at the end of the day. Anything temp folder gets dangerous for it existing in a long term also. This is implementation details that go beyond the core issue of delete is too slow unless I’m missing something.
I would dup this against #1643. /needinfo

I've re-phrased the scope of this feature to be specifically related to non-permanent deletion, so that https://github.com/microsoft/PowerToys/issues/1643 can be explicitly focused on the permanent one. (From users' perspective, this is the difference between default behavior of Delete vs. Shift+Delete). We can surely merge the issues if the other one includes this as part of its scope, because for now it merely suggests del.
And about the "dangers" of a temp folder, I'd like to see any points being discussed against this process of "move" being an objectively superior choice compared to waiting for enumeration of all files before starting a long non-atomic process, which even leaves behind inconsistent state if it ever crashes. As I view it, the risks are primarily that of users forgetting to clean up the temp folder after any crash, however, this is supposed to be a power user tool, meaning we enable it intentionally and are aware of the location of this temp folder (unlike the trillions of applications in %userprofile% or %appdata%, especially the \Cache of any electron app that never gets cleaned up because these developers are just evil). By trying to avoid this silly idea of a black-box behavior, Power Toys could instead focus on transparency since the first moment we enable this feature (it doesn't even need to be enabled by default), and as I previously mentioned, it could be stateful, thus displaying any unfinished process whenever the app gets restarted and the temp isn't empty. Thus the only risk is of us intentionally installing this app, starting a large delete process, crashing OS, and then deleting the app without ever running it again (without even going through uninstaller).
(Another funny detail/bug to illustrate how we're slowly losing the sane defaults which I'd like to improve rather than give up: if the entire Recycle Bin is manually turned off, Shift+Delete doesn't display any confirmation dialog regardless of this dialog being enabled or disabled: https://superuser.com/a/1705032)

Yes, moving to recycle bin isn't instant and isn't atomically safe. Permanent deletion of files is unacceptable by default, except for very specific scenarios where we are 100% certain there is no risk of data loss and we already have redundant backups. (There's a UX reason why default Delete behavior isn't irrecoverable, and it doesn't disappear just because we are software developers.)
We can also analyze whether "move to temp can be used in combination with permanent deletion", because the "Fast Delete" solution still isn't instant despite filesystem supporting this by moving/renaming first.

/feedbackhub


Quest Helper Causing Stuttering in Client

For some reason, the quest helper now causes a persistent stuttering within the Runelite client when a quest is selected. When the quest is deselected, the stutter immediately goes away. This is a new problem, popped up in the past two weeks or so. Unable to figure out a solve.

It’s any quest. It disappeared yesterday but is back today, making me think it’s an issue with my computer not being able to handle that plug-in plus OBS running at the same time. But I’m happy to share my runelite logs, how do I go about doing that?On Jan 18, 2023, at 12:17 PM, Zoinkwiz @.***> wrote:
Hey @YeetViberson , does this happen for a specific quest, or all quests? Could you also please share your Runelite logs so I can see if anything is happening there.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

On Windows, open your file explorer and in the bar where it says 'Quick Access' or 'Documents' along the top, simply paste in:
%userprofile%.runelite\logs
On Linux and Mac OS, you can use cd:
cd $HOME/.runelite/logs