Horizontal menu component

Is your feature request related to a problem? Please describe.
There is a need to be able to support web applications which are publicly facing rather than simply admin portals, As is common on many public portals, the main navigation is placed horizontally below the header. In contrast the current main menu for the Admin Portal is rendered vertically with fairly fixed styling.
Describe the solution you'd like

A new horizontal menu component should be provided that provides sufficient flexibility in terms of styling so as to be suitable for a publicly facing web-site
Configuration of the menu structure should be similar to any other menu or button group in the admin portal
To provide flexibility in terms of look and feel we should perhaps support the following custom styling options:

CustomStyling
CustomStylingOnHover
CustomStylingSelected

Additionally, a range of configuration options should be provided that allow fairly custom look & feel to be achieved (see examples below).
There should be a clearly documented set of CSS class names that could be overridden at the CSS level

Some screenshots of common publicly facing navigation menu structures
The solution should ideally allow the following types of styling to be supported

Hi @Lukeybooi, with the current implementation, I'm unable to test this item because the requirements are not complete

Hey @Lukeybooi, Hey
It’s very difficult to use the custom style to meet the criteria. We need to focus on implementing the remaining requirements.

Hi @Tshepiso-R I've added a color picker to change the menu item and selected menu. This should meet your criteria.

@Lukeybooi

There is still a need for custom styling properties for onHover and onSelect. This should be a code styling editor that allows a user to add CSS styling.
The "Selected Item Background" and "Selected Item Color" properties should be renamed to "Hover Background Color" and "Hover Item Color," respectively, as these properties currently work when you hover.
Add "Selected Item Background Color" and "Selected Item Color" properties.
Currently, the "Selected Item Background Color" and "Selected Item Color" properties only apply to grouped menu items. This implementation should also be extended to menu items.

@Lukeybooi as per our discussion, please see the pointer below:

Scroll Overflow shows a line underneath when selected.

When scroll overflow is selected, a line appears underneath/ above the menu items depending on the browser you are using.
Expected Behaviour:  No line should appear underneath when scroll overflow is selected by default.

Scroll icons need improvement.

The scroll icons currently have a background color that should be removed.

Inconsistent Hover Item color transitioning.

The hover effect on individual items shows a noticeable transition, but when applied to a menu group, the color changes instantly.

Active color does not work for the Active group.

The color for active items is not being applied to the active group.

Custom Styling not applied for hover and active states.

Custom styling is not functioning as expected for both hover and active items.

Expected Results

No line should appear underneath when scroll overflow is selected.
Scroll icons should have a clean appearance without background color.
Hover color transitions should be consistent across individual items and menu groups.
Active color should be correctly applied to the active group.
Custom styling should be effective for both hover and active states.

Environment

[Mention the environment details, e.g., Browser, Operating System, Device type, etc.]

Attachments

[Attach the image or any other relevant files]


Visual input delay when running exclusive fullscreen with vsync on

Godot version
v4.0.3.stable.official [5222a99f5]
System information
Windows 11, GTX 3070ti
(Note: I have experienced similar behavior on a laptop running Windows 10 and a GTX 1050ti)
Issue description
When running a project in exclusive fullscreen mode with vsync enabled, I experience a notable delay in my inputs - feels like a couple of frames. This is most obvious when having an object follow the mouse cursor - the object lags behind the cursor - but it's perceptible with all visual responses to input. I've also done some superficial tests with audio, and there seems to be no perceptible delay there, so I suspect this is a rendering issue rather than an input issue.
The most responsive mode seems to be exclusive fullscreen with vsync off.
When not in exclusive fullscreen mode, vsync appears to have no perceptible difference for me, which is slightly curious.
Possibly related to #35220?
Steps to reproduce
Setting the window to exclusive fullscreen and enabling vsync is all that seems to be required, but this may be heavily platform dependent, so I've included an MRP.
Minimal reproduction project
vsync_delay.zip

This is a duplicate of another issue, but I can't find it right now.
I wonder if this is related to the NVIDIA driver automatically using DXGI for Vulkan applications. Can you try opening the NVIDIA Control Panel, going to Manage 3D Settings then change the Vulkan window mode to prefer native Vulkan? It should be towards the end of the list of options.

Note that in general, some delay is expected when making a sprite follow the mouse cursor, especially with V-Sync enabled. See https://docs.godotengine.org/en/stable/tutorials/rendering/jitter_stutter.html#input-lag for guidance on reducing input lag.

True, but this isn't stuttering or the kind of delay I'd expect from a standard vsync. This is an actively perceptible delay of a couple of frames. Actually, maybe I should boot up Unity and see if it also has the weird vsync delay.. For that matter, I should check on an exported project to see if maybe it's some weird editor issue.

I wonder if this is related to the NVIDIA driver automatically using DXGI for Vulkan applications.

Nope. Cycled through the settings, no impact.

Also, can you reproduce this after switching to the Compatibility rendering method in the top-right corner of the editor?

Yep, persists in compatibility rendering mode. Actually tried that before posting, should have mentioned it. Is that still running on OpenGL? I didn't keep close track of the migration.
.. Actually, I wonder if this is reproducible on 3.6?

When not in exclusive fullscreen mode, vsync appears to have no perceptible difference for me, which is slightly curious.

Does input lag feel comparable to fullscreen + V-Sync in windowed mode without V-Sync?

Nope, input lag severity can be neatly summarized as:
Exclusive Vsync > Windowed Vsync == Windowed non-vsync > Exclusive non-vsync
That is, I get worse input delay in exclusive vsync than I get in windowed mode, and windowed mode's input delay is both minor (slightly worse than exclusive non-vsync but otherwise passable) and seemingly unaffected by vsync (both windowed vsync and windowed non-vsync are equivalent). Exclusive vsync is anomalously worse. Maybe I should try to test for screen tearing, actually...
Oh, and I am running two monitors, but that doesn't seem to be impacting it either.
If you have more ideas for tests let me know, but I might also do some more testing of my own.

Did some testing, windowed mode with vsync off has no tearing, which is curious. It makes me wonder if Godot is doing something like triple buffering in fullscreen, and windowed mode is just forcing standard vsync for some inexplicable reason?
I wonder how much of this is caused by modern Windows trying to be ~Helpful~.

So I did some basic testing in Godot, and the issue exists in export builds and in version 3.5.2 with both GLES 2 and GLES 3. This was about what I expected and told me very little (except that this is a longstanding issue, whatever it is) and so I decided to try and see what would happen if I attempted to recreate the behavior in Unity.
In my initial testing, Unity gave mixed results: Lag felt ever so slightly worse than it did in Godot windowed, but was consistent in exclusive fullscreen. Where things got interesting was when I decided to change Graphics APIs. By default, Unity used D3D11. But when I switched the renderer to OpenGL or Vulkan, I got the exact same input delay that I got in Godot. That is, it was generally fine outside of exclusive fullscreen, but exclusive fullscreen made it lag. This makes me wonder if it's a strange NVidia issue, because I've seen this behavior on two separate machines, and the only link is that they both had NVidia GPUs running recent (10/11) versions of windows.
I still have no idea what the hell is going on here, but since I'm cursed to be afflicted by anomalous bugs, I might as well keep digging. I'll post more if info if I uncover any.

Is that still running on OpenGL? I didn't keep close track of the migration.

Yes 🙂

I have managed to reproduce this issue a third time.
In SDL.
Hell, in SDL, the delay was just as bad in windowed mode as it was in fullscreen, which makes me think that OpenGL and Vulkan, for whatever reason, has this delay as standard behavior on some systems, and the only reason it lags less in windowed mode in Godot is because windowed mode isn't vsyncing properly, which would align somewhat with the odd stuttering I've been experiencing... but I digress.
In any event, while there may be some esoteric workaround for whatever the hell it is I'm experiencing, I suspect this is most likely some ass-backwards driver issue with no clean fix. If I ever get to the bottom of this in a productive manner, I'll post an update. Until then, I'm flagging this as "Not Planned".
My sympathies to the poor bastard seven years in the future reading through this in the desperate hopes that it'll solve his obscure input latency problem. May you find the peace you seek.

For anybody who stumbles across this at some point: I seem to have solved this problem by setting the vsync type to mailbox and manually limiting the FPS to my monitor's refresh rate. This not only eliminated the latency issues I was having but also cleaned up some stuttering I was running into. I have no idea why this works, and at this point I don't especially care. YMMV.


fix(pin.cid()): fixing type that was preventing return of z-hash

:tada: This PR is included in version 2.4.1 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


Full Windows Support Needed

Issue
Windows compatibility is incomplete.
Goal
Achieve full functionality on Windows OS.
Tasks

[ ] Test current build on Windows
[ ] Identify non-working features
[ ] Fix compatibility issues
[ ] Document Windows-specific instructions

Environment

Windows version: Windows 10

FYI for anyone waiting for Windows compatibility - you can easily build/run shog from Ubuntu using WSL.

fixed by v1.0.2


Typo in link ...

[Enter feedback here]
There is a typo in this link ...
Screen.pdf

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

ID: 1feb89e6-c5e0-693e-425e-8fd8b0198001
Version Independent ID: 7b683879-67a9-299a-73e9-6e3654846fdf
Content: Set up file storage and sharing - Microsoft 365 admin
Content Source: microsoft-365/admin/setup/set-up-file-storage-and-sharing.md
Service: o365-administration
GitHub Login: @SKjerland
Microsoft Alias: sharik

@shungite Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/5674
Thanks
Sri

@msbemba Thank you very much for the contribution and updating the documentation with PR. @shungite Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


[release/0.5.0] Update dependency package version

This commit updates the dependency package versions.

eslint : 7.15.0 -> 8.52.0
vscode : 2.7.0 -> 2.21.1 The latest eslint generates more warning than before. So it temporarily turned off the options related to this.

ONE-vscode-DCO-1.0-Signed-off-by: Jiyoung Yun<EMAIL_ADDRESS>

This change has no need to the release. So I closed this pull request and merged the same commit to the main branch.


Task completion outside root project directory

Currently this is not supported yet in bash or zsh.
This would require searching parent directories until a root project is found as is done in https://github.com/ywelsch/gradle-bash-tools/blob/master/gradle-bash-tools.sh
Workaround is to install gdub

Closing as complete


Added Avro example

Hi,
I've added an Avro serialization example to your repo. This documentation names Avro as possible solution for IDL serialization, however it does not provide an example (and I did not find one). If you agree I would add my example to yours. I've tried to use the same style you used, there are just little differences on the tests. I did not use generators).
I've tried to reuse code in serializers but, since avro4s uses macro, it did not work.
The Readme just names Avro as third format in the examples.

Great work! Thanks for your contribution. Now that leaves only Thrift :)

You're welcome. Maybe you want to change the project description :) ATM you have only protobuf

Good idea! I have changed the project description.

Thanks for the mention :)
2016-06-09 12:26 GMT+02:00 Dennis Vriend<EMAIL_ADDRESS>
Good idea! I have changed the project description.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dnvriend/akka-serialization-test/pull/1#issuecomment-224856913,
or mute the thread
https://github.com/notifications/unsubscribe/AHUgPGOov6deJ_Oj0F4EWLb8XoENMckLks5qJ-o4gaJpZM4IxXW7
.


Add support for drop_all

What it says on the tin. I'm unable to get drop_all to delete views, and I don't see the method mentioned in the documentation, so I'm assuming this needs to be plumbed still.

Indeed, this is not plumbed. I'm curious what your usecase is? My only personal reason for create_all is tests, where I've simply never had the need.
I expect it will be very straightfoward to add. basically just register a on before_drop or whatever, and compare_* with a desired metadata state of a MetaData() with nothing registered on it.

Yeah, my use case is development workflow on a remote server, where I can't easily trash the entire database instance and start over. I'm also considering whether I want these in alembic at all. Currently, when I register views for alembic, they are re-created for every migration, and it's getting annoying editing every migration to remove redundant ones that haven't changed, but create_all issues a drop-create cycle, which is good enough for even production.

I expect it will be very straightfoward to add. basically just register a on before_drop or whatever, and compare_* with a desired metadata state of a MetaData() with nothing registered on it.

I thought the same thing, but this only deletes two of my views, which seems odd.
event.listen(
            metadata,
            "before_drop",
            view_ddl(concrete_views, view_filter),
        )

Any guess on what I could be missing?

erm, why are they changing? i dont really understand lol.

lol I'm lost too. The only thing I realized is that two of the views were deleted from the codebase and I forgot, and those are the only two being deleted. I unfortunately have to pause on this issue, but hope to investigate further in a few weeks.

Well whether or not you ultimately need it, like i said, it was straightforward to support.

Tested locally and can confirm. All views dropped. I'll try to report back when I test with Procedures and Triggers. Thanks again!!


Add tests for unsupported qos checks on initialize

Signed-off-by: Ross Desmond<EMAIL_ADDRESS>Issue #, if available:
Description of changes:
Modify tests for checking unsupported.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Mostly looks fine - nitpicking around

@emersonknapp requested changes complete


sidecar and query performance loss problem

Recently experienced performance loss problems, 12 hours of data on prometheus is still very fast. But after connecting to onos sidecar and query. Only one hour of data can be checked through the query. Is the performance loss so big?
version: 0.7.0
query config:
./thanos query
--http-address <IP_ADDRESS>:19192
--store        x.x.x.x:19090
--store        x.x.x.x:19090
--store        x.x.x.x:19090
--query.timeout 5m
--store.response-timeout 5m
--store.sd-interval 30m
--query.max-concurrent 500
--query.default-evaluation-interval 3s
sidecar config:
./thanos sidecar
--tsdb.path /data/database/prometheus
--prometheus.url http://localhost:9090
--reloader.config-envsubst-file /data/prometheus/prometheus.yml
--http-address <IP_ADDRESS>:19090
--grpc-address <IP_ADDRESS>:19090

Hi, are you running Thanos Compact on your remote object storage?

Hi, are you running Thanos Compact on your remote object storage? Plus, don't forget that you need Thanos Store. And the performance has been improved by a lot recently, try out the master version of Prometheus with Thanos 0.7.0.

prometheus, version 2.12.0
thanos 0.7.0
Thank you! I am trying to run Compact and Store to see.

Hi, are you running Thanos Compact on your remote object storage? Plus, don't forget that you need Thanos Store. And the performance has been improved by a lot recently, try out the master version of Prometheus with Thanos 0.7.0.

Can thanos store use local ssd for storage?

Hi, are you running Thanos Compact on your remote object storage? Plus, don't forget that you need Thanos Store. And the performance has been improved by a lot recently, try out the master version of Prometheus with Thanos 0.7.0.

I feel that even if I don't need a store and a compact, I only use the three rounds and the query performance is not so bad.

upstream Prometheus 2.12 doesn't include the remote read streaming(it will be added in 2.13) so to use the optimizations right now can use: quay.io/thanos/prometheus:v2.12.0-rc.0-rr-streaming

Hi, are you running Thanos Compact on your remote object storage? Plus, don't forget that you need Thanos Store. And the performance has been improved by a lot recently, try out the master version of Prometheus with Thanos 0.7.0.

Can thanos store use local ssd for storage?

It can but it's only used for storing the cache of blocks that you have in your remote object storage. AFAICT you have solved this problem @hhy5861?

Hi, are you running Thanos Compact on your remote object storage? Plus, don't forget that you need Thanos Store. And the performance has been improved by a lot recently, try out the master version of Prometheus with Thanos 0.7.0.

Can thanos store use local ssd for storage?

It can but it's only used for storing the cache of blocks that you have in your remote object storage. AFAICT you have solved this problem @hhy5861?

problem is not solved! But I added a new problem with store and compact. If you query for 1 hour, you will still lose some of the indicators of the node. However, the 3-hour job indicator can be checked, but the last two hours of data will be lost. Very strange. I am going to find a problem from the source code.

@hhy5861 Could you see the stores page in your Query UI? Are the status of all of sidecars and stores UP?

@hhy5861 Could you see the stores page in your Query UI? Are the status of all of sidecars and stores UP?

store can be queried normally.
the store server is normal. There is always a lack of 2 hours of data.

@hhy5861 is your sidecar healthy? The last 2 hours metrics normally from sidecar(Prometheus instances) by remote read api.

@hhy5861 is your sidecar healthy? The last 2 hours metrics normally from sidecar(Prometheus instances) by remote read api.

Sidecar is normal. The strange thing is that only after 3 hours of data is checked, the last 2 hours of data is not available.

@hhy5861 is your sidecar healthy? The last 2 hours metrics normally from sidecar(Prometheus instances) by remote read api.

probably the problem should be to check the store for 3 hours, and not to go to prometheus for nearly 2 hours.
this question should be a query question. Still in the process of investigation


Yep, pip install --upgrade catt.


🚀 Feature Request: CLI to add Environment Variables on Pages

Describe the solution
Need to add/set/update the Environment variables on Cloudflare Pages projects.

Thanks for opening an issue! You can do this via the command line for Pages projects using Wrangler with the --binding flag:
npx wrangler pages dev --binding VAR=VALUE ./folder


"Unsupported version number [51.0] for class format". How to change target bytecode version?

When I execute android:package-debug I get "Unsupported version number [51.0] for class format"
How can I change this?

android:package-debug
[info] Wrote C:\Users\Dave\android-test\target\src_managed\main\scala\androidtes
t\TR.scala
ProGuard, version 4.6
ProGuard is released under the GNU General Public License. You therefore
must ensure that programs that link to it (scala, ...)
carry the GNU General Public License as well. Alternatively, you can
apply for an exception with the author of ProGuard.
Reading program directory [C:\Users\Dave\android-test\target\scala-2.9.1\classes
]
[error] {file:/C:/Users/Dave/android-test/}Android Test/android:proguard: java.i
o.IOException: Can't read [C:\Users\Dave\android-test\target\scala-2.9.1\classes
] (Can't process class [androidtest/R$attr.class] (Unsupported version number [5
1.0] for class format))
[error] Total time: 3 s, completed 12-dec-2011 2:32:08

I know the answer: Proguard 4.6 does not work with jdk7.
Made a new issue.


New Page Layouts

We're finding a need for a couple new page templates.

A list page template that automatically generates links to subpages, like in the example below.

A single page that has last/next pagination links, for reading pages in a sequential order.

@MBishop17 do we still need these?

No longer needed. Closing issue.


Add the rest of a channels content to the file page

The Issue
It would be great to show some of a channels videos on the file page
Steps to Reproduce

Go to content posted under a channel
You have to navigate to their channel to view other content

Expected Behaviour
There should be some recommended content on the file page
Suggested Solutions
This will most likely be just calling the channels first page of videos, and adding them at the bottom of the page.
Second (wouldn't be needed right away) to add "load more" at the bottom to view sequential pages
This would use the <FileList /> component
Ugly rough screenshot

This channel fetching should be straight forward. Most of the time will be spent styling this. I am thinking this will be similar to youtube.

test comment


Broken link

Chagne this
https://github.com/dotnet/AspNetCore.Docs/tree/master/aspnetcore/security/authorization/simple/samples/3.1/PageHandlerAuth/AuthorizePageHandlerFilter.cs
for this
https://github.com/dotnet/AspNetCore.Docs/blob/master/aspnetcore/security/authorization/simple/samples/3.1/PageHandlerAuth/AuthorizeIndexPageHandlerFilter.cs
and this description
AuthorizePageHandlerFilter
for this one
AuthorizeIndexPageHandlerFilter

@i-duarte Thank you for fixing the link.


svc-import

New svc-import sub command to import services (partner to svc-export) - thanks

@xmlisnotaprotocol - this has been added to the latest versions of workloader.


[Docs] adds to Control API -- describe when C++ Viewport::gui.mouse_focus blocks other Controls from receiving signals and events [undocumented]

API clarification, doc-bug fixes, & added undocumented features.
Closes https://github.com/godotengine/godot-docs/issues/4266
Changes :
Specified how holding mouse button down blocks other controls until release.
Corrected 2 false statements in _gui_input().
Added more precise details to

_gui_input(),
signal mouse_entered,
signal mouse_exited,
enum MouseFilter.

Added InputEvent tutorial to Tutorial section.
Why is this Pull Request so detailed? :
The commit itself is not very long, but this is my first contribution. So I thought it would be nice to detail my thought processes and to show my research to justify these additions. Perhaps this is unnecessary, but I figure revealing too much of the backstory here is better than explaining too little.
Feel free to skip any detailed meta-descriptions, unless you plan to revise or add to these sections. I mainly wish to show that these changes are needed, and that the additions are correct. (Also, being a new contributor, I wanted to prove that I am not recklessly altering the API docs =).
Conversely, about the changes I'm submitting :
I've tried very hard to keep the actual changes brief, comprehensive, and correct. I've gone through several revisions to condense it into something that should make sense in as few words as possible. I have verified each added line of text by experimenting with projects in Godot, and I've traced the C++ code for all the changes to make sure (1) what I describe is correct (2) there is nothing vital (within scope) which I've omitted.
Thematically most of the changes in this Pull Request are related to mouse events and mouse filters. However there are a few things out of scope I fixed and corrected while I was in the area (particularly, this Pull Request fixes 2 inaccurate descriptions in Control._gui_input, and there were 2 minor typos elsewhere).

What API will look like after this commit :

Explanation & points changed :
enum MouseFilter

Now describes why signals sometimes fail to emit and why events fail to fire (when another control is hogging mouse input by design) even though the MouseFilter is set up to recognize mouse entry.
It is intuitive based on the current API that MOUSE_FILTER_IGNORE will result in no signals being emitted, however it is not apparent that MOUSE_FILTER_PASS and MOUSE_FILTER_STOP do not guarantee that mouse motion events will always be routed to the Control.
For the following, assume a setup where a Control has mouse_filter set to MOUSE_FILTER_STOP or MOUSE_FILTER_PASS and assume that it normally receives events and signals and _gui_input() when the mouse clicks, enters, or exits it.
These signals will not emit and func _gui_input() will not fire if the mouse was clicked on another Control (which can receive mouse input) and has not been released yet. This applies to signals mouse_entered and mouse_exited, signal gui_event(e), and virtual _gui_input(), all will be blocked and all events are routed up through the clicked Control instead.
See ~line 1809 in viewport.cpp function Viewport::_gui_input_event(..) which is called when regular Node._input() calls do not handle an event. All gui input signals and scripted func _gui_input(event) events originate here.
Now look at ~lines 1821, 1872, 1897 in viewport.cpp function Viewport::_gui_input_event(..)
1821 -- if (gui.mouse_focus_mask) {
1872 -- if (mb->get_button_index() == BUTTON_LEFT) { //assign focus
1897 -- if (gui.mouse_focus && gui.mouse_focus->can_process()) {
When a Control which can receive mouse input is clicked, it remains in mouse focus until release. Even when the mouse hovers over other Controls, the event will be passed to the Control which the mouse initially clicked via (Control *control) gui.mouse_focus. See viewport.cpp's same _gui_input_event(..) in the branch for InputEventMouseMotion around lines 2009, 2057, and 2063 to see why events are called on the Control which was clicked (and not released) instead of the Control which is now under the mouse:
2009 -- if (!gui.drag_attempted && gui.mouse_focus && mm->get_button_mask() & ..
2057 -- if (gui.mouse_focus) {
2063 -- if (over != gui.mouse_over) {
Also added detail emphasizing that MOUSE_FILTER_PASS passes the event straight up, whereas MOUSE_FILTER_IGNORE will look for nodes outside of ancestor branches.
When looking for the Control under the mouse, Godot will find any node in the Viewport which is visually below (aka higher in the tree than) the one with MOUSE_FILTER_IGNORE, it doesn't have to be a parent or a parent of a parent; Godot searches whole tree in reverse order.
See  viewport.cpp the functions Viewport::_gui_find_control(..) and Viewport::_gui_find_control_at_pos(..) around ~line 1703 to see it in the code.

Explanation & points changed :
signal mouse_entered
signal mouse_exited

These signals were minimally documented.
I spent a lot of time debugging a personal project until I discovered that the unexpected behavior of my GDScripts was due to the mouse-hogging behavior of clicked Controls, and not due to a bug in my code. Then I discovered that this mouse-hogging behavior was undocumented (see my previous section of this Pull Request for more details, also see doc bug report @ https://github.com/godotengine/godot-docs/issues/4266).
Note: this is desired functionality. When you click and drag on a scroll bar's handle, it's standard that other Controls will not display a hover animation, and will similarly be blocked until mouse button release.
This was my entry point in researching everything that led to this Pull Request.
Fun fact.
Changes to mouse_entered and mouse_exited :

Added links to Control.has_point() and Control.get_rect(), as Rect has its own section in the Inspector Dock, but it does not have a dedicated section in the API. Referring the reader to Control.get_rect() will make it apparent what this line is referencing with the word Rect (and exactly where to read more).
Added undocumented detail : if you parent a Button control under another Button control, then set the child's mouse_filter to MOUSE_FILTER_PASS:hovering on the child will hover the parent (and emit mouse_entered for the child then the parent) and clicking the child Button will click the child and the parent Button.
You can do this with any Control type and MOUSE_FILTER_PASS, but this is the simplest example to visualize.
This is not intuitive (unless you look at the code for viewport.cpp) and I thought it aught to be documented. Look in viewport.cpp around line 1604 for the method Viewport._gui_call_input(..). This is called for all gui events (mouse button, mouse motion, touch, drag, gesture) which are not keypress and joypad events from Viewport::_gui_input_event(..)'s c++ code. All gui mouse events flow through here.
Added details about how a control will hog mouse focus and hog signals/events/_gui_input until mouse release. Upon mouse button release, if the mouse is now under a Control different than the one that was clicked, the clicked control will emit mouse_exited and the Control actually under the mouse will emit mouse_entered and propagate the signal upwards if appropriate (these will both happen during the same InputEventMouseButton or InputEventMouseMotion event in Viewport::_gui_input_event()
1983 -- _gui_call_notification(gui.mouse_over, Control::NOTIFICATION_MOUSE_EXIT);
2065 -- _gui_call_notification(gui.mouse_over, Control::NOTIFICATION_MOUSE_EXIT);
For this Pull Request's additions to these signals, mouse_entered uses [code]mouse_entered[/code] and [signal mouse_exited] andmouse_exited uses [code]mouse_exited[/code] and [signal mouse_entered]so they do not link to themselves. (Also this gives a visual cue which one you are currently reading; Not the main reason, but a fun side-effect).

Explanation & points changed :
func _gui_input(e)

Added reference to the InputEvent tutorial : https://docs.godotengine.org/en/3.2/tutorials/inputs/inputevent.html I added this to the tutorials section at the top of the Control API page (see the first picture in this post). But I also wanted to refer the reader to it here specifically. It's vitally important to understand that tutorial in conjunction with the following description of _gui_input() in Control's API.
I am unaware of a way to directly link to this tutorial's webpage in the online docs from the XML file. Further, I am unaware if this addition this breaches any conventions. This is the one non-strictly-technical point I've added which I'm unsure about, feel free to accept it or not, but I think it would be very beneficial to many.
The existing documentation for _gui_input() made it seem possible that keypress events were dependent on mouse_filter. I added a bullet point that keypress events and joypad events will only fire for the Control with key focus. This is briefly mentioned in the Intro section of Control's current API, but this section is not comprehensive without mentioning it.
Likewise, I added a phrase specifying that Control gui events are dependent on mouse_filter if they are mouse or touch events.
[DOC-BUG FIX] The current API for Godot 3 and Godot 4 both incorrectly state that parents pass events down to children unless they have MOUSE_FILTER_STOP. The current implementation passes all events (which are not joypad nor keypress events) up through the tree (see the while loop where this happens in the picture below). I corrected this phrase. See the first red outline in the picture below.
[DOC-BUG FIX] rect_clip_content does not clip input. Specified this, but largely left this line untouched. Demonstration :

Add a Button to a Panel,

clip input in the panel (you can do this from the Inspector Dock),

don't override _clips_input() in a script,

offset the Button to where part of it is invisible

run the scene and observe that you can still click the invisible parts of the Button

add a script, add func _clips_input(){ return true }

run scene, observe that you can no longer clickthe invisible parts of the Button.

Added details about mouse-hogging behavior (see the previous section of this Pull Request)
Added an important nuance : _gui_input() is not called if a node marks an event as handled in func _input(). This is outlined in the InputEvent tutorial, but will not be apparent without a lot of cross-referencing for beginners. This is an effort to make this method's documentation complete. Perhaps out of scope, but it's brief + more important than my main scope.

Concluding remarks :
Again, the changes are much smaller than these explanations.
If in the future anyone wants to reword or expand on this contribution, I wanted to lay out all the details in one place. Hopefully someday this will help someone who is exploring this area of the API + engine code for the first time.
I plan on contributing fairly regularly to the Documentation. But since I haven't issued a Pull Request before, I wanted to back up my work with reasons.
I took notes on several other changes which were out of scope, and will submit bug reports to the godot-docs project and issue Pull Requests for those separately in the future.
If I need to issue multiple Pull Requests for the changes in this one, feel free to let me know and I will break it up into chunks.
I'll rebase my fork every 12 hours or so to keep it up to date.
Thanks to all who contribute their time and efforts to Godot.

I'll rebase my fork every 12 hours or so to keep it up to date.

You don't need to rebase your fork unless there are merge conflicts (which GitHub will tell you about at the bottom of a pull request).

Oh wow, thanks. That makes sense. Read the Godot PR articles, but haven't read the Git book yet. Appreciate it!

This PR needs to be updated against the current master version, as the documentation for Control nodes has changed a lot.


Add policyViolationContextLimit on GRC Ansible automation UI

Signed-off-by: Chunxi Luo<EMAIL_ADDRESS>https://github.com/stolostron/backlog/issues/26436
Depends on https://github.com/stolostron/multiclusterhub-operator/pull/886

/cc @willkutler @mprahl

/cc @willkutler @mprahl @JustinKuli @dhaiducek

@dockerymick could you please review this help text?

/cc @dockerymick

/cc @dockerymick

Thanks for pulling me in ! @ChunxiAlexLuo I left a suggestion

Done^^

FYI @RobDolares You'll need to externalize this one when you perform your merge/rebase.

/approve


Lambda Otel Layer Adding Too Many SQS MessageAttributes?

I've got a lambda which places messages on an SQS queue, and which is instrumented with open-telemetry. When the lambda places a message on the queue, it attaches two MessageAttributes to the message, but whenever the lambda calls sendMessage(), the lambda otel layer logs the following:
aws-sdk instrumentation: cannot set context propagation on SQS/SNS message due to maximum amount of MessageAttributes
Note: the traces are not being dropped and the messages are successfully placed on the SQS queue.
What's confusing me here is that I know SQS has a limit of 10 MessageAttributes on a message when raw message delivery is enabled (which it is in this case), but I don't understand how I'm getting anywhere near that limit considering that at the point the lambda calls sendMessage(), the message it passes in only has 2 MessageAttributes. I've also checked the message again once it's been put on the queue, and I can't see any new attributes that have been added. Is the otel lambda layer trying to add 8+ MessageAttributes to the message before it's placed on the SQS queue?
Context:
I'm using lambda otel layer arn:aws:lambda:us-east-1:901920570463:layer:aws-otel-nodejs-amd64-ver-1-5-0:2, but I have also tested downgrading to arn:aws:lambda:us-east-1:901920570463:layer:aws-otel-nodejs-amd64-ver-1-5-0:2 and experienced the same issue.

Do you have a configured propagator or using the defaults?
I'm not very familiar with JS or TS but maybe something is off with this check it is doing before adding the attributes, https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/plugins/node/opentelemetry-instrumentation-aws-sdk/src/services/MessageAttributes.ts#L75

Also note this appears to be an issue with the SQS instrumentation and unrelated to Lambda. You should open an issue with https://github.com/open-telemetry/opentelemetry-js-contrib.
We'll need to update the dependency in the layer if this is a bug in the AWS SDK instrumentation there, so good to still have this open.

Linking the same issue opened in contrib - just to save time from others.
https://github.com/open-telemetry/opentelemetry-js-contrib/issues/1455


Handle tasks with multiple resource files

CipherSwarm currently allows you to create attacks that have multiple rules or multiple word lists, but hashcat won't allow that. We should add functionality to the client to either concat the wordlists or perform them as multiple tasks sequentially. This could be done on the server side, but it could just as easily be done by the client.

This is no longer an issue as of version v0.5 with 2bb6d3fca8ffc6c4ccf3198acc51d3108f0535e5


Groups mentors can be update via update route

Describe the bug
The group update path doesn't sanitize the params. If mentor_id is one of the parameters, then the mentor of the group is updated, transferring the ownership of the group.
To Reproduce
Steps to reproduce the behaviour:

Make a put request at /users/user_id/groups/group_id with mentor_id in the body
The mentor will be updated. There are appropriate checks that ensure that only the mentor of the group can do this operation.

Expected behaviour
There are two possible ways out of this -

The mentor should not be updatable.
The feature to transfer ownership of the group can be implemented.

Screenshots
N.A
Desktop (please complete the following information):
Platform agnostic
Additional context
To achieve the first way - separate update_params and create_params will have to be implemented and for the latter, the new feature will have to be implemented.
Are you working on this issue? (Yes/No)
I can work on this post discussion on the approach we use to solve this issue.

The mentor should not be updatable. This is a simple way to go.

The group update path doesn't sanitize the params

Though I agree this is a bug, it is not a serious one as only the group owner can exploit it and will achieve very little by doing so.

The feature to transfer ownership of the group can be implemented.

Just collaborated projects, maybe we can have multiple mentors instead? Just a thought.

Just collaborated projects, maybe we can have multiple mentors instead? Just a thought.

Multiple mentors for the group would be a nice functionality to add. Several times there is more than one TA for a subject and also multiple mentors will make grading the assignments faster.


Style clinic index page

I rule and have completed some work on Case Manager that's ready for review!
Minor tidying from @SamuelLangenfeld 's excellent work in #1011 so we can get the important parts of this in front of Baltimore. (Thanks a ton for plugging away at this @SamuelLangenfeld !)
This pull request makes the following changes:

Some styling cleanup, pretty much

It relates to the following issue #s:

stems from #1011
Bumps #947

Codecov Report

Merging #1078 into master will decrease coverage by 6.11%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1078      +/-   ##
==========================================
- Coverage    96.5%   90.39%   -6.12%
==========================================
  Files          50       50
  Lines        1031     1051      +20
==========================================
- Hits          995      950      -45
- Misses         36      101      +65

Impacted Files
Coverage Δ

app/helpers/dashboards_helper.rb
88.88% <0%> (-11.12%)
:arrow_down:

app/controllers/calls_controller.rb
95.83% <0%> (-0.6%)
:arrow_down:

app/models/patient.rb
99% <0%> (ø)
:arrow_up:

app/controllers/application_controller.rb
100% <0%> (ø)
:arrow_up:

app/controllers/patients_controller.rb
100% <0%> (ø)
:arrow_up:

app/models/concerns/exportable.rb

app/helpers/users_helper.rb

app/models/pregnancy.rb
0% <0%> (ø)

app/helpers/status_helper.rb
38.46% <0%> (ø)

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 4cd68d2...9baad11. Read the comment docs.


Front end

TODO for Jason: Make sure to delete comments once everything works. I'll approve for now.


Added a function to send a request to openAI model to generate a response for a given instruction.

Description
Added a function for a completion task that send a request to OpenAI model to generate a response based on a given instruction.
Resolves #(issue)

Do we have examples that this works as intended? Do we have examples of successful query -> response pairs? Where is this documented?

Do we have examples that this works as intended? Do we have examples of successful query -> response pairs? Where is this documented?

Here's one of the working examples I've tried

from gollm.openai.tool_utils import generate_response
query = """
... The following sections describe the input and output of an optimization process for a epidemilogy model.
...
...           }
...
...  }
...
... Provide a summary in 100 words or less."""
generate_response(query)
'The optimization process for the epidemiology model, identified by "a28314b2-c000-4c60-9bee-ce72eb4aef22," successfully completed with no minimization failures. The process involved adjusting the parameter "beta" over a timespan of 10 units, with a focus on minimizing the number of infected individuals. The final result achieved a function value of 1e-05 after 99 function evaluations and 5 iterations. The optimization was successful, with the best parameter value found being 0.0001. The process utilized the CIEMSS engine and various solver options, completing on May 28, 2024.'

As I mentioned though I'm expecting this function to be used to request very generic llm query from the user.


Spike: How to Embed Configurators without using an iframe or a sub-domain.

Description
Find a way to embed configurators such as the MT Configurator without using an iframe or subdomain. The ideal scenario is that the outcome of the spike serves both Volvo and MT.
The idea is to create a variation of the embed block and to find out where this application will be taken.

We tested the "my assets functionality" in tickets #204

Kamino cloned this issue to hlxsites/vg-macktrucks-com


Add more checks to /healthcheck

At the time of writing, https://server.fission.dev/healthcheck reports {"database_connected":true,"database_up_to_date":true}, but it's not actually all fine.
Here's some tests to make sure DNS is configured correctly:

origin_correct: Check if the request's domain matches our origin configured in the settings
origin_ns_resolvable: Check if NS <origin> at <IP_ADDRESS> or <IP_ADDRESS> or the system-based DNS resolver resolves to our IP address. This makes sure our DNS service is running and set up correctly.
users_origin_ns_resolvable: Check if we can DNS-resolve NS <users_origin> (with <IP_ADDRESS> etc.) to make sure it resolves to our IP address.

I'm not 100% sure yet if these checks are the correct ones. E.g. what if we don't know our own IP address? Or if there's some forwarding going on.
Perhaps it makes more sense to try to resolve _did.<origin> to see if it resolves as our own DID?
But what if there's two accidentally deploys with the same DID? Or an old deploy with the same DID is still cached?
Also, we don't have any TXT records on <users_origin> by default. Perhaps we should add one? And call it _healthcheck, make sure that it's set to an in-memory random variable and see if it resolves correctly?

Another thing we could add to /healthcheck is just printing out the environment: "environment": "prod" / "environment": "staging", etc.

Also information about the connection status of ipfs.peers that were configured?


How use this with ES6?

Hi!
I try next
import Calendar from 'sm-calendar'
/*...*/
<Calendar onChange={input.onChange} />

but in console error:
TypeError: Can't add property time, object is not extensible
at Calendar (Calendar.js:10)
at eval (ReactCompositeComponent.js:306)

Calendar and datepicker use the properties object that you pass and make changes to it, you are passing the properties as a freeze object that's why the module can't change it

How i can use calendar with React redux? This posible?

i think there is a rect.cloneElement, sorry but since i dont know your code or versions it's hard for me to help out, if you can create a pastebin or similar with an example i can help you figure it out

Were you able to make it work?

No.
I try something like this:

import React from 'react'
import {render} from 'react-dom'
import {Calendar} from 'sm-datepicker'

render(
    <Calendar/>,
    document.getElementById('app')
);


Propagate parser-settings to HelpText (fix #414 and #455)

This fixes issues #414 and #455 (value of AutoHelp and AutoVersion are ignored by HelpText)
This fix does not change the public interface. It is achieved by overloading HelpText.AutoBuild. If a ParameterSettings object is passed, the values it contains are used. If no ParameterSettings are passed to AutoBuild, help and version are always displayed.

Looks like we were heading in similar directions. Still waiting to hear back on my PR https://github.com/commandlineparser/commandline/pull/458 but would be sensible to merge these at some point.

Thanks @x789  for your effort on this PR.
This help in fixing the issues: #414 and #455 without Breaking Change.

******* PLEASE DO NOT MERGE ******
This change has been merged into #458

@x789
I test the  custom help in v2.5.0 with  AutoVersion = false and `AutoHelp=false' and Version /Help are not displayed.
This means that it works fine in v2.5.0
Can you check this online Demo

@moh-hassan,
setting AutoVersion and AutoHelp directly on HelpText works fine.
#414 and #455 describe a different issue: The settings of a Parser are
not regarded when the help-text is automatically generated.
Thus, if you create a Parser and set its AutoHelp to false, it will be
displayed on the auto-generated help-text. Please check out
https://dotnetfiddle.net/UacitX for a demonstration of these issues. You
will see that the ‘help’ option is still displayed if the help text is
generated automatically (when using v2.5.0).
Best regards,
x789
------ Originalnachricht ------
Von: "Mohamed Hassan"<EMAIL_ADDRESS>An: "commandlineparser/commandline"<EMAIL_ADDRESS>Cc: "x789"<EMAIL_ADDRESS>"Mention"<EMAIL_ADDRESS>Gesendet: 23.06.2019 23:45:38
Betreff: Re: [commandlineparser/commandline] Propagate parser-settings
to HelpText (fix #414 and #455) (#461)

@x789 https://github.com/x789
I test the custom help in v2.5.0 with AutoVersion = false and
`AutoHelp=false' and Version /Help are not displayed.
This means that it works fine in v2.5.0
Can you check this online Demo https://dotnetfiddle.net/vk7WEO
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/commandlineparser/commandline/pull/461?email_source=notifications&email_token=ADSNMRNSMYIS22AZTFEBCRTP37VIFA5CNFSM4HYWJILKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYLHXBY#issuecomment-504789895,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADSNMRI4KT4XOKKG2JMRCZTP37VIFANCNFSM4HYWJILA.

@moh-hassan,
setting AutoVersion and AutoHelp directly on HelpText works fine.
#414 and #455 describe a different issue: The settings of a Parser are not regarded when the help-text is automatically generated.
Thus, if you create a Parser and set its AutoHelp to false, it will be displayed on the auto-generated help-text. Please check out this code for a demonstration of these issues. You will see that the ‘help’ option is still displayed if the help text is generated automatically (when using v2.5.0).

That is true as you said.
Based on your example, It seems that in v2.4.3 and above, configuring parser with AutoHelp = false, cause other error and the help screen show twice ERROR(S) and it's supposed to show help without errors.

ERROR(S):
Required option 'i, input-file' is missing.

I forked  your test case to show 4 different behavior
The valid behaviour is by avoiding configuring parser with AutoHelp
I think it's better to fix this bug and  unify the generation of help either from parser setting or help setting.
I found that you fix the bug by using an overloading of AutoBuild
        var settings = new ParserSettings() { AutoHelp = false, AutoVersion = false };
        var helpText = HelpText.AutoBuild(parserResult, settings);

Can you modify your PR to fix the bug described above and  unify the generation of help either from parser setting or help setting for all AutoBuild overloads.
Note: , There are 18 test cases for HelpText have been added.

@moh-hassan   @x789 This PR has already been merged into my PR #458 (as you suggested).  Making further modifications on this branch seems a bit pointless assuming you are willing to accept my PR ! ;-)

@NeilMacMullen
As your PR #458  is based on this PR, there is still a bug as described above.
We can avoid the modification of PR #461 and concentrate for the fix in your PR.
Can you migrate that example  that configure both parser and HelpText by using your PR.
This can help developers to have a clean migration path from current help system to yours, specially most open issues are related to Help System.
As you know there was not a clean migration path from help system in v1.9.x to v2.x and we are in need to avoid this in the next V3.

@moh-hassan   that bug is not present on my branch.  I have added a test to verify that.

@NeilMacMullen , Good that the  bug is not present in your PR.
Just, i want to try the migration to your PR, can you migrate that example and post here as an attach file.
I use your new package in CI server to run the migrated code.

@moh-hassan
Ok I think the 'new' version would look like this.  There's no need to call SetTextWriter if you're happy for HelpText to go to the console

                new Parser(c =>
                {
                    c.EnableDashDash = true;
                    c.CaseInsensitiveEnumValues = false;
                    c.IgnoreUnknownArguments = true;
                })
                .SetAutoHelp(false)
                .SetAutoVersion(false)
                .SetHelpTextConfiguration(c => { c.AdditionalNewLineAfterOption = false; })
                .ParseArguments<Options>(args)
                .WithParsed<Options>(options => Run(options));

Sweet Fluent interface Code :)
It's better for redirecting errors to Console.Error and others to Console.Out with user configuration. That  is one of the needs for most developers.

:-) Yes - you can just add a .SetTextWriter(Console.Error) to the chain if you want to do that

                new Parser(c =>
                {
                    c.EnableDashDash = true;
                    c.CaseInsensitiveEnumValues = false;
                    c.IgnoreUnknownArguments = true;
                })
                .SetAutoHelp(false)
                .SetAutoVersion(false)
                .SetHelpTextConfiguration(c => { c.AdditionalNewLineAfterOption = false; })
                .ParseArguments<Options>(args)
                .WithParsed<Options>(options => Run(options));

@NeilMacMullen, please don't get me wrong. I admire your commitment to this project and your approach.
I personally like 'fluent' interfaces. But for me, the configuration quoted above is not symmetric. I'm afraid that users can get confused because they have to use two different types of configuration, an Action<ParserSettings> and methods like SetAutoHelp. What happens if I configure Parser to disable auto-help and configure HelpText to display auto-help?

  new Parser(c => { c.AutoHelp = false })
    .SetAutoHelp(true)
    [...]

But maybe I have wrong expectations for the class Parser. When I use it, I don't want to have to deal with help text options. I expect an automatically generated help to take the parser settings into account without having to worry about it.

@789  Actually  I agree with you and had decided to provide fluent modifiers for the parser settings.
I'm not particularly happy that SetHelpTextConfiguration is required but that's an unfortunate consequence of "burying" a bunch of useful formatting flags in the HelpText class.  In the ideal world, these would be hoisted up and the Parser class would be the only thing that users would have to know about.  I'm open to ideas on better ways to expose these.
Your point about contradictory configurations is good but 1) it's also a problem (actually worse) in the original design and 2) only exists in the new design because of the desire to allow backwards compatibility.  I've actually marked all the old methods as Obsolete in my PR but would be quite happy to remove them and call this a breaking change.

@moh-hassan Maybe I'm missing something but I don't think the behaviour obtained with the latest changes differs from that desired in #256?   In the latest changes, if you specify AutoHelp/AutoVersion=false then:

the help/version verbs are not added to the parseable list and are treated as unrecognised items
help/version is not listed in the helptext.

Are you suggesting that something else should happen?

https://github.com/commandlineparser/commandline/pull/256#issuecomment-505529152

@NeilMacMullen

I want to confirm that we have a common understanding for the AutoHelp/AutoVersion feature and it should be used as given in PR #256.
It's nice to get  the consideration mentioned  @x789 into account.
The Fluent Interface API (FI) is a good enhancement and can be other API of using the library and it's best to be built  in the same common public API in HelpText without the need to be obsolete.  Any bugs in HelpText can be fixed in its place without the effect of FI.
I try to understand the intent of the change in the issues #414 and #455 and I'll feedback.

There is a need for displaying help text with fluent syntax? #39

@x789
@NeilMacMullen
I have added a wiki documentation page  in my fork  to explain the usage of AutoHelp / AutoVersion properties of the parser with code example and four fiddle demos.
I hope It can help in understanding the PR #256

I think that #414 and #455 are now  a new feature of hiding Version/help option and are not considered as a bug.
Is't right?

#256 describes the possibility to automatically add a 'help' and 'version' verb/option to the parser. This works as far as only the parser is considered. I think when #256 was integrated, it was not considered that there will also be applications without 'help' and 'version' (see #294, #414 and #455).
@NeilMacMullen, @moh-hassan I do not want to stop the discussion about the fluent interface. But we should discuss it as part of #458. I am also confident that we will find a way to introduce a new API without breaking the old one.
@moh-hassan The wiki page looks okay to me. It describes the status quo. But it does not cover applications without 'help' and 'version' verbs/options.
I consider #414 and #455 to be bugs since the auto-generated help displays verbs/options that are not available. This is confusing and avoids that we can use the auto-help text in applications that do not have 'help' or 'version' verbs/options. If I interpret #294 correctly, others have come across this aspect as well.
v2.5.0 behaves as described in section 'Reproduction Steps' of #455:

2. Execute your program with `--help`
   > ERROR(S):
   > Verb '--help' is not recognized.
   > --help       Display this help screen.
   > --version    Display version information.

@x789  - yes I agree that most of this discussion should move to #458 - the only relevance here is that #458 aims to remove the requirement for the user ever to use or know about AutoBuild and therefore uses your changes in a slightly modified version.  (Hence I'm keen to know which direction we are going with this - if this PR is merged then I'll just end up having to redo changes.)
@moh-hassan
I'm pretty sure that both this PR and #458 are correctly interpreting the original intention behind introducing the AutoHelp and AutoVersion  flags which was to treat these as flags which suppress the automatic generation of the associated commands and options.  The hypothetical user of AutoHelp=false would be expected to

Supply their own "help" verb (assuming the wanted one)
Suppress the standard AutoBuild "verb not recognised" command by setting TextWriter to null and/or using WithNotParsed to output their own first level help screen.

On you wiki you seem to be implying that the suppression of AutoBuild output might happen automatically if AutoHelp was set to false.  Personally I think that is a step too far and undesirable for users who want the automatically generated basic usage but who want to supply their own "help" behaviour.
I tried your Fiddle and couldn't get to output anything sensible.    For example, I commented out the "with.AutoVersion=false;" line and the WithNotParsed line and got absolutely no output.  Is that based on the current state of the develop branch?

@moh-hassan   Played some more with your Fiddle and I think 2.5 is broken in some ways that have nothing to do with AutoHelp…

https://dotnetfiddle.net/uTUhKc - dual error line (nothing to do with AutoHelp)
https://dotnetfiddle.net/BZgB4M - missing autobuild output when not setting config flags
https://dotnetfiddle.net/gz1Rej - missing autobuild output even when AutoHelp set to true explicitly

It looks more like the explicit Parser configuration mechanism is broken in this release.

@NeilMacMullen

I think 2.5 is broken in some ways that have nothing to do with AutoHelp…

The  AutoHelp/AutoVersion feature  is added  in v2.4.3 as described here and no break in v2.5.
You can try v2.4.3 and you get the same result.
Can you point me to a commit that may cause a break of that feature.
The feature is working as intended and tested based on the requirement of @nemec (one of the Authors of the library)
@nemec commented on Mar 26, 2018

I think this solves the issues nicely. Can you add a few tests to help us prevent regressions? I think the >following should cover things, but if you think of any other scenarios feel free to include them:
AutoHelp = false and invoking --help returns an error.
AutoVersion = false and invoking --version returns an error.
AutoHelp = false, a flag for --help added manually by the user to the Options class, and it can be invoked successfully.
AutoVersion = false, a flag for --version added manually by the user to the Options class, and it can be invoked successfully.

The tests in the original commit here  and in v2.5.0 here
For fiddle, there is a problem in redirection of  console.Error and duplicate the errors
I run your fiddle cases in Linqpad  and there is no duplication of errors.
For custom Parser, HelpWriter = null by default so you get no output, this is working
            var parser = new CommandLine.Parser(c=>{c.HelpWriter=Console.Out;});

So AutoHelp/AutoVersion is working as intended and approved by the @nemec.
If something wrong in this feature we can discuss it and provide a solution.

@moh-hassan I must admit I am very confused ;-) You were the one who suggested using Fiddle to try and explore the behaviour, with the implication that this PR (and therefore mine) were somehow getting it wrong.  Since  regression tests are passing on both PRs I'm not really sure what you think should be changed!  Perhaps if you could point to a failing test case it would be clearer?  (Maybe there is one in an unmerged PR?)  Otherwise we just seem to be going round in circles....
The fact that the "default" new Parser constructor behaviour is different from Parser.Default is confusing and something I think should be considered a bug (or at least a poor design decision) but is not directly relevant to how AutoHelp should behave except in as much that it just reveals that the current implementation has too many inconsistencies and it's therefore difficult to use it to establish the "desired" behaviour.   I still think the actual behaviour of this PR (and #458) is sensible and desired.  Can you explain where you think it isn't?

@nemec commented on Mar 26, 2018

I think this solves the issues nicely. Can you add a few tests to help us prevent regressions? I think the >following should cover things, but if you think of any other scenarios feel free to include them:
AutoHelp = false and invoking --help returns an error.
AutoVersion = false and invoking --version returns an error.
AutoHelp = false, a flag for --help added manually by the user to the Options class, and it can be invoked successfully.
AutoVersion = false, a flag for --version added manually by the user to the Options class, and it can be invoked successfully.

The requirements stated above are correctly implemented in CommandLineParser v2.5.0. But in my (and others, see #294 and #414) opinion two important scenarios are missing:

AutoHelp = false and there is no manually added verb/option called 'help'
AutoVersion = false and there is no manually added verb/option called 'version'

I suspect that if these requirements had been considered in #256, it would have been noticed that the automatically generated HelpText does not match the parser configuration.

two important scenarios are missing

Indeed, and worth adding there are now unit tests that explicitly check this scenario.... see line 681

@NeilMacMullen
I use fiddle as a way of simple quick online demenstoration even with  this small bug of redirection :)
For deep debug I go to Vs2017 or Linqpad.
My concerns is that the  intention of the original issues #87 and #200 (disable help/version generation by building their own custom HelpText) which is fixed by Pr #256 are  different than the intention of the issues #414 and #455 (which simply hide help/version option from auto generated help) and therefore should have different resolution.
BTW, --version and --help are  LNX/POSIX standard in all commandLine utilities (this library respect and implement this standard ) and the requirement of the issues #414 and #455 for hiding them may violate this standard.
Are we ready to violate this standard?!
Any enhancement or Fluent interface API to HelpText is welcome and it's needed in #39 and can be completed with this  PR and yours  without Breaking Change or obsolete AutoBuild.
AutoBuild is the engine of generating help for Parser.Default.

My concerns is that the intention of the original issues #87 and #200 (disable help/version generation by building their own custom HelpText) which is fixed by Pr #256 are different than the intention of the issues #414 and #455 (which simply hide help/version option from auto generated help) and therefore should have different resolution.

I think this is a misunderstanding. This pull request #461 has nothing to do with the configuration of HelpText. It simply hides 'help' and 'version' if these verbs/options are not understood by the current parser configuration. Nothing else.

BTW, --version and --help are LNX/POSIX standard in all commandLine utilities (this library respect and implement this standard ) and the requirement of the issues #414 and #455 for hiding them may violate this standard.
Are we ready to violate this standard?!

Unfortunately, CommandLineParser violates the POSIX standard by allowing multi-character options, double-dashes and verbs. Chapter 12.2 is very precise.
I wasn't aware that CommandLineParser 'enforces' the presence of help and version. Had it been visible at a glance, the component would have dropped out of our evaluation and we wouldn't have used it.

@x789
I was evaluating CommandLineParser against POSIX standard in this comment
The Readme link this Getopt ref
Can you give me an example of the violation of the multi-character options?

@x789

two important scenarios are missing:
AutoHelp = false and there is no manually added verb/option called 'help'
AutoVersion = false and there is no manually added verb/option called 'version'

These two scenarios are described in the wiki  in
Example1: Disabling AutoVersion
Example2: Disabling Help
In these scenarios, parser consider --help and --version an unknown option and raise an error
and consequently no help/version screen are generated.
Developers can handle these cases (if needed) in:
                 parserResult.WithNotParsed(ShowError);

and show their own custom help/version or custom error screen

@moh-hassan
You type faster than I do :-). I hope to catch up...

I was evaluating CommandLineParser against POSIX standard in this comment
The Readme link this Getopt ref

Thank you for referring to the getopt-documentation. I can understand your point of view now.
However, I think that a 'long option' is against the POSIX standard. According to POSIX, an option may only be designated by a single character. (This is the first item on the list.) In contrast, the 'GNU option characteristics' allow multiple characters.
But for me the crucial question is whether CommandLineParser is based on the constraint that a program must always have 'help' and 'version'. If it does, then #414 and #455 are no bugs and the auto-generated HelpText is fine. I would then treat them as feature requests which I would reject with reference to that constraint.

With the knowledge gathered in this discussion, I have once again read through the complete documentation of the module.
@moh-hassan I can now completely understand your argumentation. Some points are hidden between the lines in the documentation. In my experience, however, it is normal for a developer documentation not to contain and explain every (implicit) decision made.
Here's my suggestion on how to proceed:

This PR and Issues #294, #414 and #455 are closed. This is because the automatisms in Parser assume that the verbs/options 'help' and 'version' are present. (Regardless of whether they are created by the user or by the parser.)
@moh-hassan's new wiki page "Adding of implicit Help and Version screen and disabling auto generation" will be added to the official wiki.

I suggest that the first note be changed to "This feature control the generation of version/help verbs/options and it is not hiding help/version options in the auto generated help."

The reference to GNU getopt is more prominent in the ReadMe. It is moved from "Resources for NewComers" to "At a Glance".
We create a new feature request for HelpText.AutoBuild. This describes that you can specify whether 'help' or 'version' should be displayed. You can set this property for instances of HelpText, but not when calling AutoBuild().

@x789
Thanks for your suggestions.
I'll convert your words into action plan.
The  feature request for HelpText.AutoBuild to hide/show help/version option  as a property in the HelpText is the exact solution.

Closed based on @x789 in his comment

@moh-hassan

My concerns is that the intention of the original issues #87 and #200 (disable help/version generation by building their own custom HelpText) which is fixed by Pr #256 are different than the intention of the issues #414 and #455 (which simply hide help/version option from auto generated help) and therefore should have different resolution.

#414 and #455 don't look like "simply hiding" for me. Hiding an unavailable command is correct. Hiding an available command is a bug. So the main problem is that the pull request #256 didn't test generation of error message help properly.
@x789's suggestion of completely separating availability as a command and availability on the help screen sounds really weird to me, to be frank. Maybe I'm missing something or I'm unaware of technical limitations, but that's not what users of command line programs would ever expect.

BTW, --version and --help are LNX/POSIX standard in all commandLine utilities (this library respect and implement this standard ) and the requirement of the issues #414 and #455 for hiding them may violate this standard.
Are we ready to violate this standard?!

Removing "version" and "help" completely is bad, but I think it should be allowed. The library is not standards police.

These two scenarios are described in the wiki

I can't access wiki for some reason, GitHub keeps redirecting me to the front page of the fork.


createVerificationRequest is not a function

Hi, after some debugging, it seems that the email sign-in "magic link" does not work because the createVerificationRequest seems to be missing in the adapter.
Adapter Example
Sanity Adapter:
This Repo
Future Sanity Adapter

@Fedeya I have a fork  with this included.

adapter.ts
queries.ts

I also found a little issue with the id not being set from _id on the account and user calls, here is the commit showing the diffs.
I can move this to a new branch and create a pull request if this will help.
I am under a time constraint so had to un-ignore the build folder so that I can npm install the package from my fork.


Better error response

Codecov Report

Merging #77 into master will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master       #77   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines          650       652    +2
  Branches       121       121
=========================================
+ Hits           650       652    +2

Impacted Files
Coverage Δ

turbot/__init__.py
100.00% <100.00%> (ø)

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 38c4b1e...9b27538. Read the comment docs.


jwt.exceptions.DecodeError: It is required that you pass in a value for the "algorithms"

(base) jwt-pwn $ python3 jwt-mimicker.py "token_here"
Traceback (most recent call last):
  File "jwt-mimicker.py", line 33, in <module>
    main()
  File "jwt-mimicker.py", line 21, in main
    jwt_token_value = jwt.decode(jwt_token, verify=False)
  File "/opt/anaconda3/lib/python3.7/site-packages/jwt/api_jwt.py", line 113, in decode
    decoded = self.decode_complete(jwt, key, algorithms, options, **kwargs)
  File "/opt/anaconda3/lib/python3.7/site-packages/jwt/api_jwt.py", line 80, in decode_complete
    'It is required that you pass in a value for the "algorithms" argument when calling decode().'
jwt.exceptions.DecodeError: It is required that you pass in a value for the "algorithms" argument when calling decode().

This is because pyjwt has updated to 2.0 with many breaking changes.
https://github.com/jpadilla/pyjwt/blob/master/CHANGELOG.rst#require-explicit-algorithms-in-jwtdecode-by-default
Fast solution:
pip install pyJWT==1.7.1

Hi @Bankde
I tried explicitly specifying the algorithm and set verification to False, but it's still disallowed because of the new restrictions.
I pushed an update to requirements.txt to pin version 1.7.1 for pyJWT - this should be suitable for the current time.
Thanks again for reporting!


Check for compatibility with Panels

Curse this idea! It's got be thinking now!
https://devblog.cadinbatrack.com/2022/03/02/panels-for-playdate/

Checked compatibility with Panels. Unfortunately Panels is not currently setup for for use in other projects. Panels is a separate framework only useable as Panels. Hopefully that will change in the future!

Ticket on the Panels repo had been closed with reason: out of scope. So for now it's out of scope.
Closing this ticket As well.

Experimental support is now added!
https://github.com/cadin/panels/issues/4#issuecomment-1236409057
Also created a wiki page for support:
https://github.com/unbelievableflavour/Cotton/wiki/How-to:-Integrate-Panels-(Beta)


Update files of learn/program-flow for i18n

https://p5js-i18n-ja.pages.dev/ja/learn/program-flow
see sample: https://github.com/processing/p5.js-website/pull/1346

After the original has been addressed we will Japaneseize it.


Feature: go1.11 module feature supported

#14 fixed

In fact, the purpose (one of) of go module is to abandon the vendor mechanism.
However, keeping the vendor directory included in current repo has two purposes:

compatible with older versions of Go.
speed up the build process. (Some packages cannot be downloaded for GFW reasons 😞 ).


Files under www directory are not world-readable

Have to manually change the files to be world-readable under the www directory. This is a pain - The permissions should be automatically set by the chemdyg scripts.

Fixed by #18


improve the plugin for integration

Here are the updates I with @sasha240100 made after I tried to connect this plugin to our project.

Can you please bump the version of the package as well?

Can you please bump the version of the package as well?

I updated to 0.1.1

If @sasha240100 is fine with it, we can merge and release a new version of the npm package. From my side it looks good


Nativescript 6.2: Type 'typeof Video' is not assignable to type 'ViewClass'

Hello,
I've tried to update to NS 6.2 but I can't because I get this error:
ERROR in src/main.tns.ts(45,38): error TS2322: Type 'typeof Video' is not assignable to type 'ViewClass'.
  Type 'Video' is missing the following properties from type 'View': _setupAsRootView, callLoaded, callUnloaded

When I try to register the element:
registerElement('VideoPlayer', () => Video);

Is there a workaround for it?

anyone?


Resume

I accidently exited auto GPT by giving the 'n' command when it asked me if I had anything else to add and don't know the command to have it start back up to resume tasks. Any guidance would be greatly appreciated. This tool is amazing!
Is there anything else you would like me to help you with regarding this goal?
Attempting to fix JSON by finding outermost brackets
Error: Invalid JSON, setting it to empty JSON now.
JARVIS THOUGHTS:
REASONING:
CRITICISM:
Attempting to fix JSON by finding outermost brackets
Error: Invalid JSON, setting it to empty JSON now.
NEXT ACTION:  COMMAND = Error: ARGUMENTS = 'dict' object has no attribute 'replace'
Enter 'y' to authorise command, 'y -N' to run N continuous commands, 'n' to exit program, or enter feedback for Jarvis...
Input:N
Exiting...
PS C:\Users\19132\Downloads\Auto-GPT>

@sekomike910 This seems to be a GPT-3 related issue. It has appeared many times during my tests since I'm on GPT-3 as well. Can you confirm you're running on GPT-3.5-turbo and not on GPT-4? Have you selected GPT-3 during setup?

@rgalloni I was using GPT 4 but don't recall seeing an option to choose during setup. Also, because I have little brain syndrome and new to this, I really struggled to understand the docker containers. It kept creating new ones and would stop running so now I am using it outside of the container. Thank you for what you put together, it's truly amazing!

I have been receiving this same error. Upon setting it up, it did not give me the option to select which Chat GPT.

This issue seems to be related to an old version of Auto-GPT.


Implement sibling protocol for Typescript.

Though there are various worker thread libraries in Node.js, the lack of a shared memory model makes it difficult to share caches, negating most of the benefit of trying to run multiple threads in the same process. In addition, having multiple independent workers connect to the control service is simpler (and possibly more efficient) than adding a proxying service within the javascript process.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @pskevin

Ping?

Thanks for the nudge! LGTM.


How does Godot 3.0  write 2D shader

Operating system or device - Godot version:
How does Godot 3.0  write 2D shader? Where does the new shader syntax get help documentation?

No documentation yet (as explained in the post about the alpha) but you can look here:
https://github.com/godotengine/godot/blob/772485cdb3a0b0003da6e174157680559fa2a59e/servers/visual/shader_types.cpp#L153
And maybe here too:
https://github.com/godotengine/godot/blob/e577c5b0705168177943fcdf9a0b66c1f8f864f3/drivers/gles3/shader_compiler_gles3.cpp
The error messages are better than on 2.x and has code completion too.
Basically, the shaders are now like:
shader_type canvas_item;

void vertex() {
}

void fragment() {
}

void light() {
}

in the same place.
You can find some examples in the demos repository (I think "screen space shaders" is working).

i've created a reference based on the sources (there are 3 sheets in doc)
https://docs.google.com/spreadsheets/d/1hBpkNor5-WUTKuiEP3Myo4wzleCWvqPqn1OLgOwFsmU/edit#gid=1226435562


show certain fields on show action only

I have some fields that I only want to show for the show action, not the index action, is there's a way to do that?

One way to do this (the preferred way as far as I know) is with fetchable_fields. You can override it on your resource and remove some fields from the list depending on the current action. You can read about it here. Let me know if you need any help.

@tommy-russoniello I thought about using fetchable_fields, but I don't know how to get the current action. Should I pass it to the context?

I would recommend putting the action in the context, yes. In can be very useful to have easily accessible. In my own app, I just memoize the initial context data (the action as well as other things like the current user) in my base controller for every action. Then it can be accessed anywhere in the controller or resource.

That makes sense. Thank you so much!

It's possible to use action: :show on attribute or attributes list, seems more straightforward way
attribute :large_field, action: :show
attributes :content, :description, action: :show


[BACKLOG-36816] UI code cleanup and recentring and Database and File …

…repository dialogs completed

:x: Build failed in 1m 51s
Build command:
mvn clean verify -B -e -Daudit -amd -pl plugins/repositories/core

:exclamation: No tests found!
Errors:
Filtered log (click to expand)

script returned exit code 1

:information_source:  This is an automatic message

:x: Build failed in 1m 46s
Build command:
mvn clean verify -B -e -Daudit -amd -pl plugins/repositories/core

:exclamation: No tests found!
Errors:
Filtered log (click to expand)

script returned exit code 1

:information_source:  This is an automatic message


Make default search to contains instead of startwith

This would make end user experience much better, especially those who are new to linux, my cousin who was used to using pamac was suggested by me to use this, he had trouble searching for packages cause he was used to pamac's method of searching with contain. I know this can be changed easily through the setting but a gui program should be simplified for new users & i think this is one of the changes needed. If its just me thinking this, just ignore my suggestion. Thank you for making such an amazing replacement to pamac.

Hi @MiyeonLin
Thanks for your feedback.
Actually the main reason is pretty much to not stress the server too much.
Those API calls are way less resource intensive than the contains search.
I'll think about it though. I see that it might be confusing for first time users.

I changed the default to "Contains" now.
Note that this app does not try to replace pamac or any other package manager.
The main goal is just to allow searching (and hopefully finding :rofl: ) packages from the terminal.
The install / upgrade / removal task is left to more capable applications. :wink:
I'm glad you like it though.


Unrecognized token error

Hi,
I'm testing the linter on my current project.
In this project I have the following step:
            <Step>                 <Name>JS-ValidateClientCN</Name>                 <Condition>{environment.name="sandbox"} or {environment.name="prod"}</Condition>             </Step>
Running the Linter gives me this error:
PS C:\Workspaces\bundle-linter-master> node .\cli.js -s C:\bitbucket_folders\prx_mortgages-t-and-t\apiproxy -f html.js >testme2.html Error: Unrecognized token "}" on position 2.     at unrecognizedToken (C:\Workspaces\bundle-linter-master\lib\package\TruthTable.js:406:11)     at TruthTable.getTokens (C:\Workspaces\bundle-linter-master\lib\package\TruthTable.js:535:13)     at TruthTable.getAST (C:\Workspaces\bundle-linter-master\lib\package\TruthTable.js:734:32)     at onCondition (C:\Workspaces\bundle-linter-master\lib\package\plugins\checkConditionComplexity.js:14:29)     at C:\Workspaces\bundle-linter-master\lib\package\Step.js:114:11     at C:\Workspaces\bundle-linter-master\node_modules\async\dist\async.js:3866:24     at eachOfArrayLike (C:\Workspaces\bundle-linter-master\node_modules\async\dist\async.js:1055:9)     at eachOf (C:\Workspaces\bundle-linter-master\node_modules\async\dist\async.js:1103:5)     at _parallel (C:\Workspaces\bundle-linter-master\node_modules\async\dist\async.js:3865:5)     at Object.parallelLimit [as parallel] (C:\LogFiles\Workspaces\bundle-linter-master\node_modules\async\dist\async.js:3948:5) {environment.name="sandbox"} or {environment.name="prod"}

Hi @EddyVos
Can you please change the condition to
<Step>
    <Name>JS-ValidateClientCN</Name>
    <Condition>(environment.name="sandbox") or (environment.name="prod"})</Condition>
</Step>

Usage of {} is not permitted for Conditions

A new linter rule perhaps?
On Mon, Mar 19, 2018, 9:48 AM Sai Saran Vaidyanathan <
<EMAIL_ADDRESS>wrote:

Hi @EddyVos https://github.com/eddyvos
Can you please change the condition to

JS-ValidateClientCN
(environment.name="sandbox") or (environment.name="prod"})

Usage of {} is not permitted for Conditions
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/apigeecs/bundle-linter/issues/106#issuecomment-374282616,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHuRi1-XqmSBOjSFUrIz21Zh26RouP6yks5tf-FcgaJpZM4SvxV1
.

Hi @ssvaidyanathan ,
Will change this but maybe, like @davidwallen also suggest, is a new linter rule better then exiting with an exception?

@davidwallen I've created new rule description here https://github.com/apigeecs/bundle-linter/issues/107
@EddyVos thanks for your feedback!

Closing this ticket and picking up #107


[Doc] Would best have more demo on how to load/use model via native Python API

📚 Documentation
Suggestion
Having a short code demo on using ChatModule to initiate and call for a response.
Bug

Link to the buggy documentation/tutorial: https://mlc.ai/mlc-llm/docs/deploy/python.html
Description of the bug: The "API reference" section. I have been checking the website for native Python API to call and run LLM. Only found the introduction of mlc_chat.ChatModule and its method.

cc @CharlieRuan0130 @Kathryn-cat

Also CC @sudeepag @MasterJH5574 lets get python docs done neat this week!

Hi @Chrisz236, thanks for the suggestion! We are having an overhaul on Python API and its documentation this week, and hopefully it will be clearer and more user-friendly afterward.
Meanwhile, you could look at two Jupyter notebooks (runnable on Colab) on the Python API: Getting Started with ChatModule, Compiling with MLC-LLM in Python.

Thank you! I will try this.

Hi @Chrisz236 , thanks for the issue! I've opened up a tracking issue with linked PR to demonstrate our progress. We'll introduce high-level functions for the chat module with getting started examples in the doc as well :)

Hi @Chrisz236 , we have updated the Python API doc with demos: https://mlc.ai/mlc-llm/docs/deploy/python.html . Let us know if you have any more questions!

resolved.


Provide changelog

The version.json changes frequently, but there is fast no commit ahead or only small typo fix.
Please provide a changelog and do not change version if no changes are made in the main code.
Regards

When the version.json changes it's because there is a new release of deconz beta or stable.

When the version.json changes it's because there is a new release of deconz beta or stable.

That is certainly true, but a change in version.json does not explain what has changed. Some release notes or change log or whatever you would like to call it would be very helpful. Please think about this. Thank you.

Release notes can be found in upstream - https://github.com/dresden-elektronik/deconz-rest-plugin/releases


Delete temp VNC files that can cause bootloop

See #100

One last addition to the names of the lock files.
If you use a different DECONZ_VNC_PORT the VNC will create a different display number and with it also different lock files. I.e. using Port 5909 will lead to the files /tmp/.X9-lock and /tmp/.X11-unix/X9.
So using wildcards is the right thing to do if you want to delete the files manually.

@MDXDave can you please implement the changes that @Jo-Be-Co recommends?

If need I could implement these in my own fork ... but I don't want to hijack this improvement.

If needed I could implement these in my own fork ... but I don't want to hijack this improvement.

@Jo-Be-Co  Considering we're seeing reports from more and more users that would be helped by implementation, I vote for getting this change out in a separate PR. You can always credit @MDXDave for highlighting the issue and starting the discussion :)

Superseded by https://github.com/deconz-community/deconz-docker/pull/107

Hello,
I still have the problem with VNC.
Latest version is installed.
Deleting the lockfiles X10-lock and /tmp/.X11-unix/X10 does not bring success.
I have set port 5910.
Also changing to another one does not bring success.
Does anyone else have a suggestion?
My version is 2.15.03, Synology Docker.
With version 2.14.01 everything works.
Thanks

My 2.15.03 is doing find on DSM7 ... could you show us your startup log?
You also could try to start with DECONZ_UID=0 and DECONZ_GID=0.

mit uid 0 zund gid 0 habe ich es schon versucht.
Anbei das Log wenn ich VNC aktiviere. Ohne Vnc funktioniert es.
_deconzcommunity_deconz_logs.txt


build: publish npm module to public by default

Codecov Report

Merging #5 (0ac53ac) into main (6ec77b1) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main        #5   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines            2         2
=========================================
  Hits             2         2

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 6ec77b1...0ac53ac. Read the comment docs.


karate-core dependency armeria CVE-2023-44487 security vulnerability

Would it be possible to get the dependency on armeria updated to latest version 1.29.2+.
See https://github.com/line/armeria/pull/5232 for more details.

@brentryan yes, we've made a release of 1.5.0.RC5 so you can verify: https://github.com/karatelabs/karate/releases/tag/v1.5.0.RC5
do let us know if this works

1.5.0 released


V3 monitoring job should have its own user agent

The V3 monitoring job intentionally hits non-hijacked queries.
dependencies
| where timestamp > ago(1d)
| where type == "SQL"
| where operation_Name contains " ODataV2Feed"
| where operation_Name !contains "/GetUpdates"
| where operation_Id != ""
| join kind=inner (
    requests
    | where timestamp > ago(1d)
) on $left.operation_Id == $right.operation_Id
| extend clientInformation = tostring(customDimensions1.ClientInformation)
| where clientInformation contains "nuget"
| summarize sum(itemCount), max(operation_Id), min(operation_Id), min(url) by name1, clientInformation
| order by sum_itemCount desc

It appears as NuGet Client V3/4.3.0 in clientInformation. This is confusing as it suggests that official clients are making weird, non-hijacked queries.
/cc @scottbommarito

@scottbommarito , how difficult is it to fix this?

@skofman1 - very simple, already discussed a fix with @joelverhagen offline


Rime Ore/Gem/Blocks Lack OreDict

Running NetherEx-1.11.2-<IP_ADDRESS> (haven't tested latest, yet), I noticed that Rime lacks oredict entries for the ore, gems, and blocks.
Additionally, as there's also no furnace recipes for it (or for Amethyst Ore!), silk-touching the blocks gives you an effectively 'useless block' you have to place down and mine again to get Rime from. (Amethyst Ore is slightly better here, as Thermal Etc/Immersive Engineering both generate Pulverizer/Crusher recipes from the oredict entries, meaning the blocks can be turned into two Amethyst.)
As Amethyst has ore entries, and the blocks page on the wiki lists both of them as Ores, I assume it's unintentional that Rime's missing?

All of these issue have been fixed in the latest version. I didn't originally add Ore Dictionary entries for the Rime Ore, Block, and Item because it is a unique ore and I didn't expect anyone else to create a similar ore.


taking keys out of headset in a container does not update its ui

Description
screwdriving a headset in a container doesn't update its ui
Reproduction

put headset in bag
screwdrive it
no key.... right?
put screwdriver in bag, updating the ui
appears!

Screenshots
eeeeeeee

This might be old and fixed already but it applies to labeling things in your bag too

also happens when screwing your own headset... makes it "disappear"
putting key in "ear"

but its actually a headset!

Seems fixed?

yeah, fixed
https://github.com/space-wizards/space-station-14/assets/124214523/e787faf0-aab8-485c-ac61-242ad3afa16b


Use the default locale when initializing SimpleDateFormat.

If we pass Locale.ENGLISH to SimpleDateFormat on Android, it causes a significant slowdown (old phones freeze while Twitter4J is parsing data).
Taking a look at the log, we can see a lot of:
I/global  (25155): Loaded time zone names for en in 5729ms.
I/global  (25155): Loaded time zone names for en in 6015ms.
I/global  (25155): Loaded time zone names for en in 6051ms.
I/global  (25155): Loaded time zone names for en in 6010ms.
I/global  (25155): Loaded time zone names for en in 6130ms.
I/global  (25155): Loaded time zone names for en in 6429ms.
I/global  (25155): Loaded time zone names for en in 6476ms.
I/global  (25155): Loaded time zone names for en in 6541ms.
I/global  (25155): Loaded time zone names for en in 6767ms.
I/global  (25155): Loaded time zone names for en in 6916ms.
I/global  (25155): Loaded time zone names for en in 7333ms.
I/global  (25155): Loaded time zone names for en in 7615ms.
I/global  (25155): Loaded time zone names for en in 8929ms.
I/global  (25155): Loaded time zone names for en in 5125ms.
I/global  (25155): Loaded time zone names for en in 5080ms.
I/global  (25155): Loaded time zone names for en in 5805ms.
I/global  (25155): Loaded time zone names for en in 5702ms.
I/global  (25155): Loaded time zone names for en in 5353ms.
I/global  (25155): Loaded time zone names for en in 6353ms.
I/global  (25155): Loaded time zone names for en in 5243ms.
I/global  (25155): Loaded time zone names for en in 5758ms.
I/global  (25155): Loaded time zone names for en in 6565ms.
I/global  (25155): Loaded time zone names for en in 6604ms.
I/global  (25155): Loaded time zone names for en in 5487ms.
I/global  (25155): Loaded time zone names for en in 6069ms.
I/global  (25155): Loaded time zone names for en in 6632ms.
I/global  (25155): Loaded time zone names for en in 4415ms.

Allowing SimpleDateFormat to use the default locale (by not passing in Locale.ENGLIGH fixes this problem, making Twitter4J noticeably faster.
Could this be included in the next release?
We should also consider alternatives into caching df. There are only a few possible formats and it might speed things up as well.
Thanks.

My first patch clearly introduces a bug on devices whose language is not set in English. Using Locale.US instead of Locale.ENGLISH seems to prevent these slowdowns and fixes the issue.


Linux Bot Emulator on Ubuntu 14 Returns InternalError to Every Message

Emulator version: 3.5.31
Node version: 6.3.1
OS: Ubuntu 14.04
I'm trying to get started with the bot emulator, but I can't seem to get it to work.
I am sending it a POST message and it is replying with a 500 internal server error.
I'm able to repeat the error outside of my code from the command line in curl:
curl -k -X POST localhost:44347/v3/conversations/1c2jbheg4egf/activities/044g77l59nf6m -d @payload.txt --header "Authorization: Bearer <MICROSOFT_APP_ID>"
Here is the JSON content of the payload.txt file:
{"conversation":{"id":"1c2jbheg4egf"},"from":{"id":"0kmhi11ge90k9","name":"Bot"},"locale":"en-GB","recipient":{"id":"default-user","name":"User"},"rep
lyTold":"044g77l59nf6m","type":"message","text":"Normally I wouldnt say this but...","speak":"You aren't working!","textFormat":"plain"}

Here is the exact response I am receiving from the emulator:
{"code":"InternalError","message":"Cannot read property 'header' of null"}
I've searched this error message and haven't found this exact case.  I've also tested this in a live environment and the message is coming through properly there.
I'd really like to get going with the framework in my development environment, but this has brought progress to a stop.  If anyone can provide insight in how to get past this I would appreciate it.

I recommend simplifying the scenario as much as possible, just to get your bot and the emulator talking. Take a look at this auth troubleshooting guide that can walk you through the steps: Troubleshooting Bot Framework authentication. Please follow the steps in the section titled Step 1: Disable security and test on localhost, then report back here if you're still having trouble.

Hi @eanders-MS !
Thank you for responding.  I have already disabled authentication and am using localhost.

Hi @eanders-MS !
Thanks for the reply.  I have already disabled security and I am testing on localhost.
My script is receiving conversation updates and messages from the emulator, but when my script sends a message to the emulator the situation is as described above.

Thanks for the response!  Okay!
I removed the App ID and password from the emulator, and I stopped sending the emulator an Authorization header.
Now it works. :)

Glad it worked! The troubleshooting guide may also prove helpful once you're ready to add auth back in.


Report type parameter resolving hibernate metamodel bug

Hibernate currently fails to fully resolve type parameters when building its metamodel. This results in missing embeddable types in the metamodel which then leads to problems in blaze-persistence.
Until this issue is resolved in Hibernate, we use CTE entity classes containing explicit references to all embeddables as a workaround.

Maybe we can use the hibernate native metamodel to workaround this in older versions.

Working on this right now: https://hibernate.atlassian.net/browse/HHH-10690

I implemented a fix in Hibernate for this, let's see when it get's applied.