Connection timed out

I've been able to setup localtunnel-server on my digitalOcean droplet successfully running LAMP stack. I've setup the app behind apache proxy (not a dev ops person; just know the basics of setting up a server). I could also get url for my client when I run
lt -h sub.domain.com -p 9292 for server running on my client. However, when I open the URL in my browser, it keeps loading and then gives connection timed out.
My lt-server runs on port 6000 behind proxied port 80.
Wondering if someone can help me understand the problem?
I could get status successfully as below, if I run sub.domain.com/api/status:
{"tunnels":0,"mem":{"rss":32759808,"heapTotal":31981568,"heapUsed":16313712,"external":236228}}

You solved it?? I have the same problem

@eternalsayed You solved it?? I have the same problem

No. The problem was never fixed. I tried to setup the server on my mac and it worked fine. Probably something to do with my VM config. I'll try it on my Raspberry pi and see if it works. Will update when I'll do that.


ImPlot Flags

Hello, i am experiencing a problem that i can not click or change any flag in ImPlot. I even used the real example from the "implot demo" to assure that i did not make any mistake.
But on the demo LinePlots it is also not working.

Thanks.

Hello,
I cannot reproduce your issue. See video below, where I launch demo_implot.py.
https://github.com/user-attachments/assets/0507c84f-e1b2-4585-9c2c-ca43738873fe
(It also works correctly with demo_implot.cpp)
Can you post an example of code where the issue is present?

Hello and thanks for the respond.
Here is the code on the template added Demo_LinePlots:

void Demo_LinePlots(){
static float xs1[1001],ys1[1001];
for (int i=0;i<1001;++i){
xs1[i] = i * 0.001;
ys1[i] = 0.5f + 0.5f * sin(50xs1[i]+(float)ImGui::GetTime()/10);
}
static double xs2[20],ys2[20];
for (int i=0;i<20;++i){
xs2[i] = i1/19.0f;
ys2[i] = xs2[i]*xs2[i];
}
if(ImPlot::BeginPlot("Line Plots))")){
ImPlot::SetupAxes("x","y");
ImPlot::PlotLine("f(x)",xs1,ys1,1001);
ImPlot::SetNextMarkerStyle(ImPlotMarker_Circle);
ImPlot::PlotLine("g(x)",xs2,ys2,20,ImPlotLineFlags_Segments);
ImPlot::EndPlot();
}
}
int main(int , char *[])
{
auto guiFunction =  {
ImGui::Text("Hello, ");                    // Display a simple label
HelloImGui::ImageFromAsset("world.jpg");   // Display a static image
if (ImGui::Button("Bye!"))                 // Display a button
// and immediately handle its action if it is clicked!
HelloImGui::GetRunnerParams()->appShallExit = true;
ImPlot::CreateContext();
Demo_LinePlots();
ImPlot::DestroyContext();
};
HelloImGui::Run(guiFunction, "Hello, globe", true);
return 0;
}

You should not create an implot context at each frame

Thank you very much. It is solved.


Provide unique product_uuid for container

Required information

Distribution: Ubuntu
Distribution version: 18.04
The output of "lxc info":

config: {}
api_extensions:
- storage_zfs_remove_snapshots
- container_host_shutdown_timeout
- container_stop_priority
- container_syscall_filtering
- auth_pki
- container_last_used_at
- etag
- patch
- usb_devices
- https_allowed_credentials
- image_compression_algorithm
- directory_manipulation
- container_cpu_time
- storage_zfs_use_refquota
- storage_lvm_mount_options
- network
- profile_usedby
- container_push
- container_exec_recording
- certificate_update
- container_exec_signal_handling
- gpu_devices
- container_image_properties
- migration_progress
- id_map
- network_firewall_filtering
- network_routes
- storage
- file_delete
- file_append
- network_dhcp_expiry
- storage_lvm_vg_rename
- storage_lvm_thinpool_rename
- network_vlan
- image_create_aliases
- container_stateless_copy
- container_only_migration
- storage_zfs_clone_copy
- unix_device_rename
- storage_lvm_use_thinpool
- storage_rsync_bwlimit
- network_vxlan_interface
- storage_btrfs_mount_options
- entity_description
- image_force_refresh
- storage_lvm_lv_resizing
- id_map_base
- file_symlinks
- container_push_target
- network_vlan_physical
- storage_images_delete
- container_edit_metadata
- container_snapshot_stateful_migration
- storage_driver_ceph
- storage_ceph_user_name
- resource_limits
- storage_volatile_initial_source
- storage_ceph_force_osd_reuse
- storage_block_filesystem_btrfs
- resources
- kernel_limits
- storage_api_volume_rename
- macaroon_authentication
- network_sriov
- console
- restrict_devlxd
- migration_pre_copy
- infiniband
- maas_network
- devlxd_events
- proxy
- network_dhcp_gateway
- file_get_symlink
- network_leases
- unix_device_hotplug
- storage_api_local_volume_handling
- operation_description
- clustering
- event_lifecycle
- storage_api_remote_volume_handling
- nvidia_runtime
api_status: stable
api_version: "1.0"
auth: trusted
public: false
auth_methods:
- tls
environment:
  addresses: []
  architectures:
  - x86_64
  - i686
  certificate: |
    -----BEGIN CERTIFICATE-----
...
    -----END CERTIFICATE-----
  certificate_fingerprint: ...
  driver: lxc
  driver_version: 3.0.1
  kernel: Linux
  kernel_architecture: x86_64
  kernel_version: 4.15.0-23-generic
  server: lxd
  server_pid: 17558
  server_version: 3.0.1
  storage: btrfs
  storage_version: 4.15.1
  server_clustered: false
  server_name: ubnt-srv

Issue description
The UUID available at /sys/class/dmi/id/product_uuid (and /sys/devices/virtual/dmi/id/product_uuid) is sometimes used to identify the node (most notable by Kubernetes), and is supposed to be unique to each machine (or in this instance, container). In LXD containers, the UUID is the same on all containers on the same host, and seem to be the same as the host's. It is also only available in containers running in privileged mode.
This UUID should be generated at container creation, so that it is unique for each container. Or it could be specified as a container configuration. KVM, for example, has the --uuid option that sets this uuid. It should also be available to non-privileged containers.
Steps to reproduce

Start two containers (tested with ubuntu 18.04)

lxc launch ubuntu:18.04 c1
lxc launch ubuntu:18.04 c2

Display product UUID:

lxc exec c1 cat /sys/class/dmi/id/product_uuid
will display cat: /sys/class/dmi/id/product_uuid: Permission denied

Enable privileged:

lxc config set c1 security.privileged true && lxc restart c1
lxc config set c2 security.privileged true && lxc restart c2

Again, display product UUID:

lxc exec c1 cat /sys/class/dmi/id/product_uuid
lxc exec c2 cat /sys/class/dmi/id/product_uuid
sudo cat /sys/class/dmi/id/product_uuid
All of these will display the same UUID.

This is a non-namespaced file meaning it is unique per physical host not per container. Changing this even with a privileged container should be a no-no. Some of this information is very much tied to the bios and actual hardware so I expect any argument that we can make upstream to namespace this to result in a metaphorical slap in the face.

For virtual machines this case is different since they can fake devices and also run a different kernel.


Remove version: Jackett.Jackett version 0.20.2916

404 - release deleted
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/Jackett/Jackett/releases/download/v0.20.2916/Jackett.Installer.Windows.exe
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 918)


[20] - Add grum

Issue

Resolves #20

Solution

[x] Install grum (composer require --dev phpro/grumphp)
[x] Install PHPMD (composer require --dev phpmd/phpmd)
[x] Install PHPCS (composer require --dev squizlabs/php_codesniffer)
[x] Configure grumphp.yml (PHPCS with PSR12) (PHPMD with 'cleancode', 'naming', 'codesize') (fixer enabled)

Concerns

Must we update the README explaining how to install grum?

The grum errors are already fixed in the whole project, there are some PHPMD warnings that I have removed, such as TooManyPublicMethods in ClassesKoans, since each public method refers to a koan, on the other hand, we have realized that we don't need the KoanPrinter since we don't execute the koans using the ContemplateKoans so I have opened an issue to delete it and see what you think about it.

Okay my mistake, we use KoanPrinter to run the tests 😅


Print calls and errors are swallowed

In Jupyter lab:

Any prints and errors in handle_event are shown in the special log output.
Any prints in get_frame are shown in the special log output, errors are swallowed.

In Jupyter notebook:

Any prints and errors in handle_event are shown.
Any errors in get_frame are shown, but prints are swallowed (except when there is an error (??)).

The difference in behavior between handle_event and get_frame can be explained by the fact that handle_event is processed during a com event, while get_frame is called in a fresh asyncio task.
This result surprises me quite a bit, since this is about basic prints and errors, and "Errors should never pass silently.". I guess async code is hard ... ?
I'm wondering whether this is something we should document or try to fix.

If I make the widget call these methods using with self._output where the context is an ipywidgets.Output, I can fix it for the notebook. For Jupyter Lab it makes prints and errors appear in-line for handle_event, but for get_frame everything is swallowed ...

I agree it could be documented and that'd be a great first start. Would it be worth it to have the widget output include some option for including a stdout/stderr log in like a separate sub-widget or something? Eh probably not.


Pcengines

@macpijan decided to split up the README into separate files, as it's grown in size quite a bit. I'll be adding the docs for adding new mainboards to a separate document.


Update the ring crate to 0.17

Currently jwts depends on ring 0.16.20, which was released more than 3 years ago. ring 0.17 was then released 7 months ago and popular projects like rustls have switched to 0.17. Maybe it's a good time to switch to 0.17 in jwts too.
Looking at the code briefly there's at least one obstacle to solve: ring::error::KeyRejected no longer provides &'static str as a description of the error. So it'd need a breaking change at least unless we request the upstream to provide it.
What do you think?

I prefer to use aws-lc-rs since rustls defaults to it, but it will bring more breaking changes. Fortunately, it is feasible because few people use this library.

The latest version of jwts with aws-lc-rs worked for me. Thanks!


non-Buf body chunks

Is your feature request related to a problem? Please describe.
I'd like hyper to be able to support more advanced/efficient IO operations that don't use an intermediary &[u8]:

ask the kernel to directly copy bytes from an input fd into an output fd (sendfile(2), splice(2), copy_file_range(2), IO_URING_OP_SPLICE, chains of io_uring read and write operations, etc.)
maybe a more safe and/or efficient use of mmap->write than the status quo (but see caveat below):

callers can implement the current API by providing a reference directly to the mmaped region, but this is unsound if the underlying bytes can change, and it has a latency problem. Particularly when the backing file is on spinning disk (and not in page cache), it's really bad to make an async IO thread wait for a major page fault (10+ ms). (I used to use this approach in a server where I know the underlying bytes don't change, but I stopped because there's no good way around the major page fault problem.)
callers can implement the current API by providing a reference to a copy done ahead of time on the thread of their choice (avoiding both those problems), but this is inefficient/unnecessary when the memory access is done from the kernel by write/writev/IO_URING_WRITEV. (My server does this now, but it'd be nice to avoid the copy.)
maybe better: passing a raw pointer and length to the syscall doesn't actually require copying or guaranteeing that nothing else is changing the backing file. caveat: I think the thread still stalls with a major page fault within the syscall, just as it would on userspace read. so maybe this approach isn't that great anyway, as compared to copying ahead of time or using the fd-to-fd APIs mentioned above.

(One might point out that a userspace TLS implementation needs the bytes in userspace anyway. But at least on Linux, kTLS is possible, and there's been recent movement on using it from Rust: https://github.com/rustls/rustls/issues/198. And sometimes people don't use TLS or handle it in an external proxy server.)
My half-baked trait below might have another benefit of allow a caller-supplied IO to control memory allocation more by providing chunks from a pool or something rather than fresh allocations done within hyper.
In terms of hyper's vision, I think this aligns with Fast and Flexible.
This has been in the back of my mind for a while, but the hyper v1.0.0-rc.1 post yesterday made me realize the clock might be ticking. The vision doc says "If it is determined necessary to make breaking changes to the API, we'll save them for after the 3 years." I fear this needs a breaking API change, and I'd be sad to miss the boat if it'll be that long before the next one.
If you consider API changes to support this to be too complex to maintain or that they'd introduce too much work/delay to design/implement before reaching hyper 1.0, that's one thing, but I'd rather at least bring it up first!
Describe the solution you'd like
My thought is that hyper::body::Body::Data needs to provide:

the (remaining) length, so hyper's proto layers can frame things properly
a way for the IO to actually provide a chunk or consume the next bytes from one. IIUC, users are supposed to be able to bring their own transport, so this part is really a contract between two parts that can be provided by the user. Buf is one such contract, but it's not suitable when you want to defer the actual read because it promises that the bytes can be produced immediately (not async) and infallibly.

and then some users will use a chunk type that allows them to splice from one file descriptor straight to the output file descriptor, encrypting with kTLS. And an IO to match it.
The current IO bounds of I: AsyncRead + AsyncWrite + Unpin for the io passed to e.g. hyper::server::conn::http2::Builder::serve_connection can still be provided, but the advanced users will also want hyper to use some way of sending/receiving chunks without going through those traits. Half-baked sketch:
trait Data {
    /// Remaining length in bytes.
    fn len(&self) -> usize;
}

trait Io : AsyncRead + AsyncWrite + Unpin {
    type Data : Data;

    fn poll_write_data(...) -> Poll<Result<usize, Error>>;
    fn poll_read_data(...) -> Poll<Result<Self::Data, Error>>;
}

(For Chunk = Bytes, poll_write_chunk and poll_read_chunk should be implementable in terms of poll_write and poll_read, respectively.)
Lots I don't know:
There might be a lot to consider in those ... bytes above: hyper at least needs a way to tell it the max bytes it's expecting in the next chunk based on framing.
The proto layers need to plumb that through. Maybe this can be done without breaking compatibility with the existing API via default trait bounds and a "simple" methods that require Data: Buf and provide poll_write_chunk and poll_read_chunk in terms of poll_write and poll_read vs an "extended" methods that don't. Maybe it can't. I'm not sure!
I see the hyper::body::Incoming interface uses Data = Bytes. It'd be nice to support more flexibility on the incoming side as well as the outgoing side.
I haven't looked at how this would intersect with http3/UDP support.
Describe alternatives you've considered

Convince ourselves that it's possible to do this later without an API break.
Accept that there's performance wins out of reach with the current API.
Maybe somewhere between: current API can be extended for this for outgoing stuff but not for incoming stuff (hyper::body::Incoming)

I did read and think about this when you wrote it up, but otherwise have not been able to make any progress. I was hopeful some other motivated individual would want to push on it before we hit 1.0, but seems not. I don't think that means this can't happen. Rather, I do think this can be added later. It might be a little but trickier, but I suspect doable with some cleverness.
So, I'll leave this up as a desirable feature, but more discussion and proposal is needed (thus still b-rfc). However, I'm removing it from the 1.0 milestone.

Thanks. I appreciate the explicit consideration, and I hope you're right that it can be added later without an API break.

I’d be interested in being able to serve static files with hyper but using the sendfile system call (there are crates for portable usage of it): is there a way to implement this without modifying the current hyper source code, e.g by providing some specific implementation of Body and using tokio::spawn_blocking so as not to block the reactor? Or maybe that is just not feasible without modifications of hyper?


GH-575 Correctly focus script on editor breakpoints

Fixes #575

Applied to main (=2.1) and branch 2.0.


[data-table]: radio buttons should not include check all option and selecting individual rows does not trigger toolbar

Description
When radio buttons are used, the check all option should not be available as only one per group is selectable. Additionally, selecting radio buttons does not activate the table toolbar.

Component(s) impacted
data-table
Browser
Chrome, Safari, Firefox, Microsoft Edge
Carbon for IBM.com version
v2.5.0
Severity
Severity 2 = Aspects of design is broken, and impedes users in a significant way, but there is a way to complete their tasks. Affects major functionality, has a workaround.
Application/website
@carbon/web-components
Package
@carbon/web-components
CodeSandbox example
https://web-components.carbondesignsystem.com/?path=/story/components-datatable-selection--with-radio-selection
Steps to reproduce the issue (if applicable)
No response
Release date (if applicable)
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate issues

Table toolbar is needed only when we are choosing multiple rows and with radio button we can only choose one row at a time, hence the batch action toolbar is not needed here. The same behaviour can be seen in the carbon/react data table also with radio button option.
The select all option is now being hidden with hide-checkbox attribute added manually to the element in storybook, this can be updated if needed.

I've just had this same problem again (I think Kenny created this issue based on what I reported on the slack channel) and I think this still needs more work.
With regards to the above comment, firstly, yes you can add hide-checkbox to the table header row to prevent the "bug" of it allowing multiple radio buttons to be checked - but that is a workaround not a fix, you shouldn't need the user to do that. By default the select all checkbox should NOT appear if you are using the radio button option here.
Secondly, I disagree that the batch action buttons are not required if you are only selecting 1 item in the table.  I need this feature all the time.  I have a table of items, I want the user to select the radio button for a row and an action button should then appear allowing the user to Edit or Delete the item.  Yes, a single item.
Because the batch action buttons don't appear when you use radio buttons, then I'm going to be forced to use checkboxes, and code the extra check to make sure the user has only checked 1 row.  Surely it's not too much to ask to have the batch action buttons appear with radio! It would make my life easier.
These 2 items have been outstanding for months now - would it be possible to get this looked at? Thanks.


Resize canvas width and height to match backgroundImage dimensions

Thanks for a great package! Is there a way to resize automatically the canvas when a background image is loaded, so that the dimensions of the canvas (width and height) match the ones of the background image? One solution I can see is to retrieve the content using the toJSON method, and then accessing the width and height of the background image. Or is there another recommended way to do this?

Hi,
You have to set OriginX and OriginY to false:
reader.addEventListener('load', () => sketch.setBackgroundFromDataUrl(reader.result, {                 			stretched: stretched,             stretchedX: stretchedX,             stretchedY: stretchedY,             originX: false,             originY: false 		}), false);
Hope its helping you,
Have a good day !


Update links to Docker Hub

All Submissions:

[X] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[X] Have you added an explanation of what problem you are trying to solve with this PR?
[X] Have you added information on what your changes do and why you chose this as your solution?
[ ] Have you written new tests for your changes?
[ ] Does your submission pass tests?
[ ] This project follows PEP8 style guide. Have you run your code against the 'flake8' linter?

thank you!


Expiring daemon: Overall build fails and stops

Whiles running tests on Jenkins my builds stops abruptly in between tests some times due to below:
Daemon registry /home/user/.gradle/daemon became unreadable. Expiring daemon. Cannot nest operations in the same thread. Each nested operation must run in its own thread. java.lang.UnsupportedOperationException: Cannot nest operations in the same thread. Each nested operation must run in its own thread. 	at org.gradle.internal.operations.DefaultBuildOperationWorkerRegistry.doStartOperation(DefaultBuildOperationWorkerRegistry.java:65) 	at org.gradle.internal.operations.DefaultBuildOperationWorkerRegistry.access$400(DefaultBuildOperationWorkerRegistry.java:30) 	at org.gradle.internal.operations.DefaultBuildOperationWorkerRegistry$DefaultOperation.operationStart(DefaultBuildOperationWorkerRegistry.java:163) 	at org.gradle.api.internal.tasks.testing.worker.ForkingTestClassProcessor.processTestClass(ForkingTestClassProcessor.java:68) 	at org.gradle.api.internal.tasks.testing.processors.RestartEveryNTestClassProcessor.processTestClass(RestartEveryNTestClassProcessor.java:47) 	at sun.reflect.GeneratedMethodAccessor154.invoke(Unknown Source) 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 	at java.lang.reflect.Method.invoke(Method.java:498) 	at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) 	at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) 	at org.gradle.internal.dispatch.FailureHandlingDispatch.dispatch(FailureHandlingDispatch.java:29) 	at org.gradle.internal.dispatch.AsyncDispatch.dispatchMessages(AsyncDispatch.java:132) 	at org.gradle.internal.dispatch.AsyncDispatch.access$000(AsyncDispatch.java:33) 	at org.gradle.internal.dispatch.AsyncDispatch$1.run(AsyncDispatch.java:72) 	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54) 	at org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40) 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 	at java.lang.Thread.run(Thread.java:745)
Expected Behavior

I suspect this relates to https://github.com/gradle/gradle/issues/897
I'm using gradle-3.2.1 wrapper.
I also see this in logs:
Starting a Gradle Daemon, 1 busy and 1 stopped Daemons could not be reused, use --status for details
Current Behavior

Context

Steps to Reproduce (for bugs)

Your Environment

Build scan URL:

It might be the same issue as https://github.com/gradle/gradle/issues/897. Can you please upgrade to at least version 3.3 that fixes the issue?


new format for beer_MolBioSystems2014

No observableParameters/noiseParameters/preequilibrationConditions yet

libSBML Error (SBML component consistency): Any <compartment>, <species>, <parameter>, or (in Level 3) <speciesReference> whose identifier is the value of a 'variable' attribute in an <assignmentRule>, must have a value of 'false' for 'constant'.
Reference: L2V4 Section 4.11.3
 The parameter with id 'sigma_Bacnorm' should have a constant value of 'false'.

libSBML Error (SBML component consistency): Any <compartment>, <species>, <parameter>, or (in Level 3) <speciesReference> whose identifier is the value of a 'variable' attribute in an <assignmentRule>, must have a value of 'false' for 'constant'.
Reference: L2V4 Section 4.11.3
 The parameter with id 'sigma_IndconcNormRange' should have a constant value of 'false'.

When running importer.create_objective(), I get:
Traceback (most recent call last):
  File "/Applications/PyCharm CE.app/Contents/helpers/pydev/pydevd.py", line 1664, in <module>
    main()
  File "/Applications/PyCharm CE.app/Contents/helpers/pydev/pydevd.py", line 1658, in main
    globals = debugger.run(setup['file'], None, None, is_module)
  File "/Applications/PyCharm CE.app/Contents/helpers/pydev/pydevd.py", line 1068, in run
    pydev_imports.execfile(file, globals, locals)  # execute the script
  File "/Applications/PyCharm CE.app/Contents/helpers/pydev/_pydev_imps/_pydev_execfile.py", line 18, in execfile
    exec(compile(contents+"\n", file, 'exec'), glob, loc)
  File "/Users/paulstapor/Documents/Promotion/ami/AMICI/python/examples/example_steadystate/examples_petab.py", line 35, in <module>
    obj = importer.create_objective()
  File "/usr/local/lib/python3.7/site-packages/pypesto/objective/petab_import.py", line 357, in create_objective
    mapping_par_opt_to_par_sim=parameter_mapping
  File "/usr/local/lib/python3.7/site-packages/petab/core.py", line 588, in get_optimization_to_simulation_scale_mapping
    scale = par_opt_scales_from_df[par_opt_ids_from_df.index(val)]
ValueError: 'sigma' is not in list

when running checkBenchmarkModels.py, I get:
Model parameter 'sigma_Bacnorm' is target of AssignmentRule, and thus, must not be present in condition table or in parameter table. Not OK

fixed


Decode normal maps on export instead of trying to access pixels.

Reading raw texture pixels from disk is, in general, not a good idea given the wealth of texture formats Unity supports internally. A Texture2D could come from anywhere -

embedded in an FBX file
PSD file
RenderTexture
stored as .asset file on disk
procedurally generated, only living in memory

One case where that is a problem in the sketchfab exporter is NormalMap exporting - their pixels would only be correct if the normal on disk is already in tangent space (sometimes, but rather rarely the case).
A solution (for the normal maps, but a similar approach would work in general) is to decode the actual texture and convert the necessary data to a PNG or JPEG file which is then stored for glTF usage.
A shader is used to convert into the right encoded normals format (tangent space).
This works for all normal maps, no matter how they were created (greyscale/bumpmap/RenderTex)...

Hi @soraryu,
Thanks a lot for this PR and the explanations 👍
Please note that we are not active anymore on this code, as we switched to https://github.com/sketchfab/UnityGLTF.
I'll take a look at this PR ASAP and probably report and adapt these changes to the new repository.

Yes, I would make sense to mention this in the Readme, I'm adding a note, and you're right, we have the same problems with the new code.
We actually diverged from the official Khronos Group repo since our only goal was to build a Sketchfab to Unity plugin around glTF. The structure of UnityGLTF was much more interesting and maintainable so we moved both our importer and our exporter.
The official repo has been updated since we worked on our version so they probably went further that us (as we stopped when we had enough features to support for our usecase).


account.c: uric: unescape: illegal '^'

Hi Alfred,
I see this issue: https://github.com/alfredh/baresip/issues/273 and this commit: https://github.com/alfredh/baresip/commit/5b1f3237c1cc181d216a02ce604614adb792aa17
Does this commit support escaping the caret sign (^)? Interestingly, baresip doesn't have an issue with the & sign.

the caret sign ('^') must now be escaped, try to use %5e instead.
given that escaping passwords is cumbersome for users and that the
password field in a SIP uri is deprecated, I will add a new parameter
;auth_pass=xxx for this.

I will add a new parameter ;auth_pass=xxx for this.

That would be very welcomed!

@jungle-boogie could you please test this commit:
https://github.com/alfredh/baresip/commit/19e66aa85ac3cbc610ed2280064495ae66a7bdb2
try to change your SIP account line to something like:
<sip:username@domain.com>;auth_pass="xxxxxx"

(double quotes around xxxxxx are optional)
/Alfred

This is all better! Thank you!


Impossible to export PDF of a ~240 slides deck

Describe the bug
Exporting PDF of my ~240 slides deck result in crashing
To Reproduce
Steps to reproduce the behavior:

Create a big deck with images (~50) and code
Export it to PDF
Crash

Same when exporting a small range of slides (slidev export --range 1,2)
Desktop (please complete the following information):

OS: ArchLinux
Browser: playwright
Slidev version: 0.37.1 (same in 0.34.3 and all between)

Logs
<--- Last few GCs --->                                                                                │
│                                                                                │
│[572644:0x55bbfa77a510]   349700 ms: Scavenge 4081.3 (4091.9) -> 4081.3 (4096.9) MB, 36.1 / 0.0 ms  (average mu = 0.493, current mu = 0.400) allocation failure                     │
│[572644:0x55bbfa77a510]   350227 ms: Mark-sweep 4130.8 (4143.6) -> 4099.6 (4112.5) MB, 453.5 / 0.0 ms  (average mu = 0.394, current mu = 0.296) allocation failure scavenge might no│
│                                                                                │
│                                                                                │
│<--- JS stacktrace --->                                                                                │
│                                                                                │
│FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory                                                                                │
│ 1: 0x55bbf77832a5 node::Abort() [/usr/bin/node]                                                                                │
│ 2: 0x55bbf762a8ea node::OOMErrorHandler(char const*, bool) [/usr/bin/node]                                                                                │
│ 3: 0x55bbf7962414 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/usr/bin/node]                                                                           │
│ 4: 0x55bbf7962808 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/usr/bin/node]                                                             │
│ 5: 0x55bbf7b0367a  [/usr/bin/node]                                                                                │
│ 6: 0x55bbf7b1aadf v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/bin/node]                    │
│ 7: 0x55bbf7b1cf1b v8::internal::Heap::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr│
│ 8: 0x55bbf7b1cfac v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/us│
│ 9: 0x55bbf7ae2514 v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [/usr/bin/node]                                  │
│10: 0x55bbf7e1f5f7 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [/usr/bin/node]                                                     │
│11: 0x55bbf81dd759  [/usr/bin/node]                                                                                │
│error Command failed with signal "SIGABRT".                                                                                │
│info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Does it crash when you view it in your browser? e.g. http://localhost:3030/print
And with the overview?

@twitwi On firefox, http://localhost:3030/print does not crash. Neither the overview.
On Chromium, http://localhost:3030/print does not crash, but if I open the printing dialog, the printing preview is hanging, not crashing. The overview does not crash.
I hope it could help to find the origin of the issue

@welcoMattic node seems limited to 4GB of heap size by default, you might try to increase it, I'd say with e.g. NODE_OPTIONS="--max-old-space-size=8192" slidev export

After a long execution, it fails, even with 16GB.

Hi, I think there is an issue with --range that is being ignored.
Maybe we should split this issue into an issue with range being ignored and a discussion about exporting huge decks (probably exporting subparts and then merging).
@tonai if you feel like looking at "range" being ignored when exporting, don't hesitate.

Yes, --range is totally ignored here https://github.com/slidevjs/slidev/blob/main/packages/slidev/node/export.ts#L147

@welcoMattic should be ok (the range) with 0.38.1

I'm closing. For the merging (in post-production) after exporting subparts, pdftk or pdfarranger are good candidates.


Feature Request: The ability to add extra metadata to a bullet.

What is your use-case ?
In my game, I want to have multiple kinds of enemies where each enemy can shoot different bullets. I want these bullets to have different stats that the player node can react to when it collides with a bullet.
Describe the feature you'd like
I want to be able to add metadata to bullets, be it damage, the node who shot the bullet, or anything else.
Describe alternatives you've considered
I don't think there's any alternatives.
Idea on how to make your feature
Additional context

Looks like I forgot to close this issue. This feature request has been implemented for a while now.


As difficult as this is, I've finally removed Carolyn's access

As difficult as this is, I've finally removed Carolyn's access from the CNCF repos in case her GitHub account is compromised at some point in the future and so that she isn't the suggested reviewer for new PRs 😿

😢


memory leak when using zmq.asyncio with asyncqt qeventloop

I'm trying to use zmq.asyncio with asyncqt and it looks like zmq is leaking around ~40 - 60mb/sec. I think the leak is coming from zmq as I've tried asyncqt using asyncio streams and did not see any leak, however when I run this example using the standard asyncio event loop instead of a QEventLoop everything seems to work as well. Additionally, I found putting a time.sleep() in the worker loop and limiting the rate at which messages are sent also seemed to stop the leak. If I send smaller arrays the leak also seems to stop.
import os
import asyncio
import zmq
import zmq.asyncio
import time
import numpy as np
from multiprocessing import Process
from PyQt5 import QtWidgets
from asyncqt import QEventLoop

def run_worker():
    ctx = zmq.Context()
    socket = ctx.socket(zmq.PUB)
    socket.bind("tcp://<IP_ADDRESS>:5557")
    timestamp = 0

    while True:
        try:
            topic = 'view:graph:_auto_Projection.0.Out'
            msg = np.random.randn(1024, 1024)
            socket.send_string(topic, zmq.SNDMORE)
            socket.send_pyobj(timestamp, zmq.SNDMORE)
            socket.send_pyobj(msg)
            timestamp += 1
            #time.sleep(1)
        except KeyboardInterrupt:
            break

    ctx.destroy()

async def update():
    ctx = zmq.asyncio.Context()
    sock = ctx.socket(zmq.SUB)
    sock.setsockopt_string(zmq.SUBSCRIBE, 'view:graph:_auto_Projection.0.Out')
    sock.connect("tcp://<IP_ADDRESS>:5557")
    while True:
        try:
            topic = await sock.recv_string()
            heartbeat = await sock.recv_pyobj()
            reply = await sock.recv_pyobj()
            print(os.getpid(), reply)
        except KeyboardInterrupt:
            print("INTERRUPT")
            break

    ctx.destroy()

if __name__ == "__main__":

    worker = Process(target=run_worker)
    worker.start()

    app = QtWidgets.QApplication([])
    loop = QEventLoop(app)
    asyncio.set_event_loop(loop)
    loop.run_until_complete(update())

    # asyncio.run(update())

This is with zeromq 4.3.2, pyzmq 19.0.2, python 3.7.7.

I've narrowed this down to being a problem with recv_pyobj() . I tried a few other things, like sending a numpy tobytes and using frombuffer with recv(copy=False) as well as pyarrow with recv_serialized(copy=False) and neither of those seem to leak as well.

recv_pyobj is probably only relevant insofar as it's quite slow relative to other mechanisms. Switching recv_pyobj to just recv shows that the issue still occurs, but at a slightly lower rate.
I ran this code adding a log of progress, and it doesn't appear to be a memory leak, but rather a performance problem. Adding print(f"sent {timestamp}") and print(f"rcvd {heartbeat}") to the sender and receiver, respectively, I see that the sender is sending ~10 messages for each one the receiver processes:
sent 341
rcvd 39
sent 342
sent 343
sent 344
sent 345
sent 346
sent 347
sent 348
sent 349
sent 350
sent 22 msgs/sec
rcvd 40
rcvd 2 msgs/sec

On my machine, that's only processing 2 messages per second on the receiving side, to 22 on the sender, which is itself not very high.
whereas it keeps up just fine with asyncio.run:
sent 674
rcvd 673
sent 675
rcvd 674
sent 676
rcvd 675
sent 677
rcvd 676
sent 678
rcvd 677

The asyncqt eventloop seems to be much more costly for each socket wakeup. One way to improve that is to use recv_multipart to have only one await per multipart message and do deserialization after receiving the whole message, but that's likely not going to be enough to keep up (I only get up to ~10 msgs/sec with that change).
The fact that asyncio.run keeps up just fine does suggest there's something awry in how asyncqt and/or qt implements waking on socket reads and not something in pyzmq.


revamp initialize module, currenty if permissions are added / modified, redeploying does not consider those

Briefly describe the feature
Current State

Initialize module of paralus is used to apply seed data for paralus application during first time installation.

Problem Statement

Adding / updating permissions or any changes related to seed data would not be applied during redeploy and initialize fails with below
resource permissions already exists! cannot invoke initialize again

What problem does this feature solve? Please link any relevant documentation or Issues

Redeploying should be able to apply deltas so that user does not have a run any script - mainly for existing paralus users

(optional) What is your current workaround?

Run a script provided

We need to update script that initialize data:
https://github.com/paralus/paralus/blob/main/scripts/initialize/main.go


Running ./gradlew wrapper overwrites the distribution URL from all.zip  to bin.zip

Running ./gradlew wrapper --gradle-version 4.3.1 on any project (you can quickly try https://github.com/mvysny/karibu-dsl ) will always change gradle/wrapper/gradle-wrapper.properties distributionUrl from gradle-x.y.z-all.zip to gradle-4.3.1-bin.zip (changes all to bin).
Expected Behavior
The wrapper plugin should recognize that I'm using gradle distro with sources and should preserve the all classifier.
Current Behavior
The wrapper plugin overwrites entire .properties file and always changes the URL classifier from all to bin
Context

Steps to Reproduce (for bugs)
git clone https://github.com/mvysny/karibu-dsl
cd karibu-dsl
./gradlew wrapper --gradle-version 4.2.1

Your Environment
Should be reproducible in any environment.

Thanks for reporting. You can use --distribution-type to specify the distribution type. See https://docs.gradle.org/current/userguide/gradle_wrapper.html#sec:wrapper_generation for more details.

@blindpirate Even though --distribution-type is available I think there's still merit to the idea of making the wrapper task smarter and preserve the distribution type when only --gradle-version is given.

@bamboo OK, let's keep it open.

It's not quite the same, but you can set the distribution type in the build script, so the wrapper task will always use the all distribution:
https://docs.gradle.org/current/dsl/org.gradle.api.tasks.wrapper.Wrapper.html#org.gradle.api.tasks.wrapper.Wrapper:distributionType
wrapper {
   distributionType = "all"
}

Closing, as @big-guy's answer is the recommended way to ensure a distribution type in your project.


[Windows10] Firefly dont work in Windows 10 Sandbox

Issue description
When trying to open Firefly in the Windows Sandbox, the following error message appears.

Apparently, the Sandbox Windows cannot open app.asar.
The Windows 10 Sandbox is only available to Windows 10 Pro / Business users. The sandbox must be enabled separately and the bug should only affect a minimal number of users.
https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-sandbox/windows-sandbox-overview
Wallet version
Alpha 0.0.1
System specification
Windows 10 Pro Build 21327
Is it a repeatable issue?
Y
Steps To reproduce the issue
Explain how the maintainer can reproduce the issue.

Start Firefly in a Windows Sandbox

Expected behaviour
That Firefly opens.
Actual behaviour
Firefly does not open
Errors
Screenshot is above.

Could you try installing the VC++ runtime and see if this fixes the issue https://www.microsoft.com/en-us/download/details.aspx?id=53840

These versions are installed on my system.

are they installed in the sandbox ?

good point :-D
Now it works.


Build an apk or ios within a website

I don't speak english, sorry if the translation is wrong
I'm trying to build a website that users can build their apps (android & ios) in low code, but I have no idea how build these apps in apk or ios?
do you have a plan to do this using Flutter?

Hi @semnomeflutter
This issue doesn't seem to describe a bug or a feature request. Please see https://flutter.dev/community for resources and asking questions like this, you may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp/
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you


Labels inside nodes

Closes #57
Test and docs are missing, will follow soon.

I've re-run CI on the last commit. One refimage needs updating.
This PR unintentionally breaks 7 more refimages. For debugging I added the last commit. It fixes those regressions, but breaks the feature of that PR.
I don't understand why.

The reftests are just normal package tests, so if you run ] test locally you should be able to see what changed in those plots for debug purposes. Reftest img #12 is broken on master, maybe this should be fixed in a separate PR so all open stuff can rebause on it.

I think I discovered the problem.
https://github.com/MakieOrg/GraphMakie.jl/blob/791014b461ee90425bd8486c0a01f2b90d630891/src/recipes.jl#L230
update_arrow_shift uses node_size and node_marker. So the code needs to be rearranged a bit.

Codecov Report
Patch coverage: 95.83% and project coverage change: -0.63 :warning:

Comparison is base (813aa93) 80.39% compared to head (4346fd9) 79.76%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #128      +/-   ##
==========================================
- Coverage   80.39%   79.76%   -0.63%
==========================================
  Files           4        4
  Lines         663      682      +19
==========================================
+ Hits          533      544      +11
- Misses        130      138       +8

Impacted Files
Coverage Δ

src/recipes.jl
93.85% <95.83%> (-2.86%)
:arrow_down:

... and 1 file with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

@hexaeder this is ready for your review.
I wasn't sure if that feature should be shown in the feature walk-through instead of (or in addition to) the reftests.


riemann_c_client: 1.10.2 -> 1.10.3

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/riemann-c-client/versions.
meta.description for riemann_c_client is: '"A C client library for the Riemann monitoring system"'.
Release on GitHub
Compare changes on GitHub

Checks done (click to expand)

built on NixOS
/nix/store/4z6fs4gpm2da163aj3g156ac9hhav6n2-riemann-c-client-1.10.3/bin/riemann-client passed the binary check.
1 of 1 passed binary check by having a zero exit code.
1 of 1 passed binary check by having the new version present in output.
found 1.10.3 with grep in /nix/store/4z6fs4gpm2da163aj3g156ac9hhav6n2-riemann-c-client-1.10.3
directory tree listing: https://gist.github.com/ba3e67f33bbe0c1de0962a3da62cf4e1
du listing: https://gist.github.com/593b98937376d6eecce434f9d3392e04

Test this build with Cachix (click to expand)

One time setup in nixpkgs Git checkout:
cachix use r-ryantm
git remote add r-ryantm https://github.com/r-ryantm/nixpkgs.git

Test this build:
git fetch r-ryantm && git checkout aaf448ec50d423525231728e3e7790c96a51c474 && nix-shell --pure -I nixpkgs=. -p riemann_c_client

cc @rickynils @pradeepchhetri for testing.

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: riemann_c_client
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: riemann_c_client
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/4z6fs4gpm2da163aj3g156ac9hhav6n2-riemann-c-client-1.10.3
shrinking /nix/store/4z6fs4gpm2da163aj3g156ac9hhav6n2-riemann-c-client-1.10.3/bin/riemann-client
shrinking /nix/store/4z6fs4gpm2da163aj3g156ac9hhav6n2-riemann-c-client-1.10.3/lib/libriemann-client.so.0.10.3
gzipping man pages under /nix/store/4z6fs4gpm2da163aj3g156ac9hhav6n2-riemann-c-client-1.10.3/share/man/
/nix/store/vp40my263xk32f07788srrgl59rycsna-binutils-2.30/bin/strip is /nix/store/vp40my263xk32f07788srrgl59rycsna-binutils-2.30/bin/strip
stripping (with command /nix/store/vp40my263xk32f07788srrgl59rycsna-binutils-2.30/bin/strip and flags -S) in /nix/store/4z6fs4gpm2da163aj3g156ac9hhav6n2-riemann-c-client-1.10.3/lib  /nix/store/4z6fs4gpm2da163aj3g156ac9hhav6n2-riemann-c-client-1.10.3/bin
patching script interpreter paths in /nix/store/4z6fs4gpm2da163aj3g156ac9hhav6n2-riemann-c-client-1.10.3
checking for references to /build in /nix/store/4z6fs4gpm2da163aj3g156ac9hhav6n2-riemann-c-client-1.10.3...
/nix/store/4z6fs4gpm2da163aj3g156ac9hhav6n2-riemann-c-client-1.10.3

Success on aarch64-linux (full log)
Attempted: riemann_c_client
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/ci8xkfmp4qk0amd09ri1asfdgw60b0m0-riemann-c-client-1.10.3
shrinking /nix/store/ci8xkfmp4qk0amd09ri1asfdgw60b0m0-riemann-c-client-1.10.3/bin/riemann-client
shrinking /nix/store/ci8xkfmp4qk0amd09ri1asfdgw60b0m0-riemann-c-client-1.10.3/lib/libriemann-client.so.0.10.3
gzipping man pages under /nix/store/ci8xkfmp4qk0amd09ri1asfdgw60b0m0-riemann-c-client-1.10.3/share/man/
/nix/store/8wl4dykwswy42wxj671b6k7vk2ydxg86-binutils-2.30/bin/strip is /nix/store/8wl4dykwswy42wxj671b6k7vk2ydxg86-binutils-2.30/bin/strip
stripping (with command /nix/store/8wl4dykwswy42wxj671b6k7vk2ydxg86-binutils-2.30/bin/strip and flags -S) in /nix/store/ci8xkfmp4qk0amd09ri1asfdgw60b0m0-riemann-c-client-1.10.3/lib  /nix/store/ci8xkfmp4qk0amd09ri1asfdgw60b0m0-riemann-c-client-1.10.3/bin
patching script interpreter paths in /nix/store/ci8xkfmp4qk0amd09ri1asfdgw60b0m0-riemann-c-client-1.10.3
checking for references to /build in /nix/store/ci8xkfmp4qk0amd09ri1asfdgw60b0m0-riemann-c-client-1.10.3...
/nix/store/ci8xkfmp4qk0amd09ri1asfdgw60b0m0-riemann-c-client-1.10.3


[polyfill] Unwatch is very slow

Trying to make preact signals flavored adapter based on signal-polyfill, found one perf bottleneck.
I am using basic effect implementation (tbh watcher part looks confusing to me atm, mb I am just heavy):
let pending = false;

let watcher = new Watcher(() => {
  if (!pending) {
    pending = true;
    queueMicrotask(() => {
      pending = false;
      for (const signal of watcher.getPending()) {
        signal.get();
        watcher.watch(signal);
      }
    });
  }
});

export function effect(cb) {
  let destructor;
  let c = new Signal.Computed(() => { typeof destructor === 'function' && destructor(); destructor = cb(); });
  watcher.watch(c);
  c.get();
  return () => { typeof destructor === 'function' && destructor(); watcher.unwatch(c) };
}

After measuring performance in js-framework-benchmark, I found unwatch method to be very slow.
Is there any perspective of optimization?
I attempted making simple batch for disposing effects, but there seems to be implicit bug causing index.js:407 Uncaught TypeError: Cannot read properties of undefined (reading 'wrapper') and subsequent TypeError: Cannot read properties of undefined (reading 'liveConsumerNode'). Test case is a bit tricky to reproduce.
It makes me wondering - if implementing effect on user side is so fragile and complicated, why not including it in proposal? I am sure there can be more optimal way than creating a Computed.
Signals like uslignal, preact/signals or @webreflection/signal didn't have problem with having a class for effects.

I think you're running in to the same thing i did, the fix is this: https://github.com/NullVoxPopuli/signal-utils/blob/ef3d29f2dd2ff943714c5f7c1bfd0c89af529ad7/src/subtle/microtask-effect.ts#L24
for (const signal of watcher.getPending()) {
    signal.get();
  }

  // No args
  watcher.watch();

@NullVoxPopuli thanks, it works, but I wish I could understand what't going on here and why. Now it looks like some magic code to me, so it makes me wondering if that's only me or if not then why's that magic is left up to users to implement, not part of the standard.
Do you possibly know an efficient way to organize unwatch?
I did this:

// destructor batches signals to unwatch
let toUnwatch = new Set
function unwatch(s) {
  if (!toUnwatch.size) {
    queueMicrotask(flushUnwatch);
  }
  toUnwatch.add(s)
}

const flushUnwatch = () => {
  let u = [...toUnwatch]
  toUnwatch.clear()
  watcher.unwatch(...u)
}

and it seems to produce abovementioned errors

Thanks for filing this issue. Note that we're considering changing the getPending/rewatch patterns as described in #77 ; we should keep performance in mind during that change (and I hope that it will also make it easier to get the usage right). Great idea to use other signal implementations; the one in this repo is unstable and not suitable for production, in addition to whatever performance issues exist.


v1.0.1  chatgpt-vscode-plugin.setUpGPT not found

Config issue in release, fixed in latest version


Networking switching not working after switching from ParaTimes tab to Wallet tab

Here is a reproducer (sorry for the poor video quality):

Related code: https://github.com/oasisprotocol/oasis-wallet-ext/commit/b3009dde569d14e3096b678c2ad0eead16d16bc1

is that in a branch somewhere?

oh it was in #168


Variable name mayhem...

The last few SNAPSHOT versions has changed the sensor variable legends...
Screenshot shows a set of MQTT sensors, MySensors and RFLink.
Those enormously long legend names including everything is just confusing and impossible to read.
Please make it possible to customize what should be displayed, both in dashboard, rooms details and basically everywhere for each sensor.

@Redferne Changed this feature bit different. we have to enable  Enable unique name checkbox to get unique chart name. Otherwise looks as we had earlier.

Nice!  Still believe that it should be possible to customize the display even further. See below screenshot. I've redmarked some areas available for improvement. The Title and Legend of each display should be customizable. It is probably easiest to support variables here in addition to the text string. The variables could be any of the column headings in the sensor list such as; $Network, $Gateway,  $Node, $EUI, $Sensor, $Name, $Type, $Variable, $Room,  $Lastseen.
Looking at screenshot, Porchlights is single graph and the complete Variable Details should be removed since we already see Name and % Values in the graph.
Goodnight buttons should also not display any Variable Details in this example. Intention is to turn off all lights in a group for bedtime. (How to send the on/off to a group from custom widget? The group button available is 'always' in the wrong state so I need to turn on all lights and then turn them off :-(  )
Outside Temperature: Here it would be prudent to maybe show $Room + $Lastseen as Varable Legend.
Voltages; Here is Enable unique name ticked and Legend is truncated and half invisible. The data is MQTT from a UPS and here it would nice to have $Node + " ( " + $EUI + " ) " in the Title and only $Name as Variable Legend.
If these parameters were customizable it would be so awesome.

@Redferne I guess this is somewhat duplicate request of https://github.com/mycontroller-org/mycontroller/issues/342
I will find a way to customise most of the things.

Yes. Thank you for considering these improvements. There is so much potential in MyController!


Chore/Update packages

Both frontend and backend packages need to be upgraded. Need to add proper test coverage first.

#158


Add customizable Max Threads

Enabling #14
To be honest, I don't like setting this by env var, but setting it in code would require quire a change in code I believe, so I'm following the recommendation from #14.

Do we want to have max value limit?

Perhaps BLOCKING_THREADS would be more explicity that this is for the blocking thread pool.

@mmstick BLOCKING_THREADS being {crate_name}_{feature} would be great, but is little unfortunate considering crate being named blocking.
I agree though on including crate name as part of env var.
Maybe BLOCKING_MAX_THREADS ?

Thanks for the PR! I would like to set the lower max value limit to 1 and the upper max value limit to 10000 (for now). (The 10000 limit comes from the thread limit of go, but if the user frequently reaches 10000 threads and if it becomes a real problem, the user is likely using blocking in places where the use of blocking is not appropriate.)

@taiki-e Ok, I will add those to the PR.

@taiki-e added min and max values.
I'm pretty sure it can be done prettier in Rust though (just starting with the language).

Could you add crate-level docs about this env var?


Added Starter README + Changed to Apache 2.0 License

Closes #10 #8

Otherwise LGTM!

Okay should be good now


Enable binary compatibility

Once 1.0.0 is out, we need to enable binary compatibility by removing this
https://github.com/micronaut-projects/micronaut-chatbots/blob/c2c23e3c5fa143b99a0629f27e9e3ef0b4b313ab/buildSrc/src/main/groovy/io.micronaut.build.internal.chatbots-module.gradle#L12-L16

@timyates can this be closed? If it can, close it.

Done in https://github.com/micronaut-projects/micronaut-chatbots/pull/169


Fix French translation.

This commit basically reverts the locale name change done in #561. The pattern with other locales has been to use the longer-form IETF language tag for a given language (i.e. "en-US" vs. "en"). This leaves the door open for translations in non-majority dialects, and is generally more future-friendly. The reasoning given for moving from "fr-FR" to "fr" was that the change is consistent with Mozilla policy, but I think that the more important consistency is consistency with the rest of the Rust site.

r? @brson
(rust_highfive has picked a reviewer for you, use r? to override)

For further background, here is the original discussion on using the full IETF language tags for locale names.

@AndrewBrinker 👍 , would you mind rebasing this?

Okay, I did not do that correctly. Just a minute.
Also, it looks like the Spanish translation now has the same problem as the French translation. If we're going to use the full language codes, we shouldn't accept PRs that don't.

If we're going to use the full language codes, we shouldn't accept PRs that don't.

This is a good call; we shouldn't, and I should pay attention to that when reviewing. Thanks.

I'm going to close this. I've opened #682 which addresses the fr and es language codes.

Side note: thanks for taking translations so seriously! :smile:


Broken docs link in generated manifest

This link does not appear to actually exist:
https://github.com/aws/amazon-ecs-cli-v2/blob/2f40a264e5cff191bb4a8b8d34585c09f31e16ec/templates/lb-fargate-service/manifest.yml#L1-L3

Should be all fixed now :D


sysbox-in-docker does not work on ubuntu-focal without some Dockerfile changes

Create a GitHub issue with the label "Bug"
Don't have permissions
Add a label corresponding to the Sysbox release
Again, don't have permissions but this happened on master at 620453973fcb20f7cd9ca37d7e623ba91fdc663f
Describe the issue as clearly and completely as possible.
I was trying to use sysbox-in-docker following the instructions here but running make -C <path_to_sysbox> sysbox-in-docker ubuntu-focal gave me the following error
make: Entering directory '<path_to_sysbox> '

** Building the test container **

[+] Building 0.8s (17/30)                                                                                docker:default
 => [internal] load build definition from Dockerfile.ubuntu-focal                                                                                0.0s
 => => transferring dockerfile: 8.53kB                                                                                0.0s
 => WARN: LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 114)                                                                                0.0s
 => WARN: LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 115)                                                                                0.0s
 => WARN: JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals (line 221)                                                                             0.0s
 => [internal] load metadata for docker.io/library/ubuntu:focal                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load build context                                                                                0.0s
 => => transferring context: 268B                                                                                0.0s
 => [ 9/25] ADD https://raw.githubusercontent.com/docker/docker-ce/master/components/cli/contrib/completion/bash/docker /etc/bash_completion.d/docker.sh                                                      0.2s
 => [ 1/25] FROM docker.io/library/ubuntu:focal                                                                                0.0s
 => CACHED [ 2/25] RUN apt-get update && apt-get install -y     acl     build-essential     gcc-x86-64-linux-gnu     libc6-dev-amd64-cross     linux-libc-dev-amd64-cross     gcc-aarch64-linux-gnu     libc  0.0s
 => CACHED [ 3/25] RUN wget https://go.dev/dl/go1.21.3.linux-amd64.tar.gz &&     tar -C /usr/local -xzf go1.21.3.linux-amd64.tar.gz &&     /usr/local/go/bin/go env -w GONOSUMDB=/root/nestybox               0.0s
 => CACHED [ 4/25] RUN go env -w GONOSUMDB=/root/nestybox &&     mkdir -p "/go/src" "/go/bin" &&     chmod -R 777 "/go"                                                                                0.0s
 => CACHED [ 5/25] RUN useradd -u1000 -m -d/home/rootless -s/bin/bash rootless                                                                                0.0s
 => CACHED [ 6/25] RUN cd /tmp     && git clone https://github.com/sstephenson/bats.git     && cd bats     && git reset --hard 03608115df2071fff4eaaff1605768c275e5f81f     && ./install.sh /usr/local     &  0.0s
 => CACHED [ 7/25] RUN if [ "amd64" = "amd64" ] ; then arch_str="x86_64";     elif [ "amd64" = "arm64" ]; then arch_str="aarch_64";     else echo "Unsupported platform: amd64"; exit; fi     && curl -LO ht  0.0s
 => CACHED [ 8/25] RUN curl -fsSL https://get.docker.com -o get-docker.sh     && sh get-docker.sh                                                                                0.0s
 => CACHED [ 9/25] ADD https://raw.githubusercontent.com/docker/docker-ce/master/components/cli/contrib/completion/bash/docker /etc/bash_completion.d/docker.sh                                               0.0s
 => CACHED [10/25] RUN go install github.com/go-delve/delve/cmd/dlv@latest                                                                                0.0s
 => CACHED [11/25] RUN cd /tmp && curl -LO "https://dl.k8s.io/release/v1.28.2/bin/linux/amd64/kubectl"     && install -o root -g root -m 0755 kubectl /usr/local/bin/kubectl     && rm /tmp/kubectl           0.0s
 => ERROR [12/25] RUN echo "deb [signed-by=/usr/share/keyrings/libcontainers-archive-keyring.gpg] https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_22.04/ /" > /etc/ap  0.5s
------
 > [12/25] RUN echo "deb [signed-by=/usr/share/keyrings/libcontainers-archive-keyring.gpg] https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_22.04/ /" > /etc/apt/sources.list.d/devel:kubic:libcontainers:stable.list     && echo "deb [signed-by=/usr/share/keyrings/libcontainers-crio-archive-keyring.gpg] https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/1.28/xUbuntu_22.04/ /" > /etc/apt/sources.list.d/devel:kubic:libcontainers:stable:cri-o:$VERSION.list     && mkdir -p /usr/share/keyrings     && curl -L https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_22.04/Release.key | gpg --dearmor -o /usr/share/keyrings/libcontainers-archive-keyring.gpg     && curl -L https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/1.28/xUbuntu_22.04/Release.key | gpg --dearmor -o /usr/share/keyrings/libcontainers-crio-archive-keyring.gpg     && apt-get update     && apt-get install -y cri-o cri-o-runc:
0.334 /bin/sh: 1: gpg: not found
0.350   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
0.350                                  Dload  Upload   Total   Spent    Left  Speed
100  1093  100  1093    0     0  11268      0 --:--:-- --:--:-- --:--:-- 11385
0.447 (23) Failed writing body
------

 3 warnings found (use --debug to expand):
 - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 114)
 - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 115)
 - JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals (line 221)
Dockerfile.ubuntu-focal:160
--------------------
 159 |     # works with Sysbox.
 160 | >>> RUN echo "deb [signed-by=/usr/share/keyrings/libcontainers-archive-keyring.gpg] https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/${crio_os}/ /" > /etc/apt/sources.list.d/devel:kubic:libcontainers:stable.list \
 161 | >>>     && echo "deb [signed-by=/usr/share/keyrings/libcontainers-crio-archive-keyring.gpg] https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/${crio_version}/${crio_os}/ /" > /etc/apt/sources.list.d/devel:kubic:libcontainers:stable:cri-o:$VERSION.list \
 162 | >>>     && mkdir -p /usr/share/keyrings \
 163 | >>>     && curl -L https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/${crio_os}/Release.key | gpg --dearmor -o /usr/share/keyrings/libcontainers-archive-keyring.gpg \
 164 | >>>     && curl -L https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/${crio_version}/${crio_os}/Release.key | gpg --dearmor -o /usr/share/keyrings/libcontainers-crio-archive-keyring.gpg \
 165 | >>>     && apt-get update \
 166 | >>>     && apt-get install -y cri-o cri-o-runc
 167 |
--------------------
ERROR: failed to solve: process "/bin/sh -c echo \"deb [signed-by=/usr/share/keyrings/libcontainers-archive-keyring.gpg] https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/${crio_os}/ /\" > /etc/apt/sources.list.d/devel:kubic:libcontainers:stable.list     && echo \"deb [signed-by=/usr/share/keyrings/libcontainers-crio-archive-keyring.gpg] https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/${crio_version}/${crio_os}/ /\" > /etc/apt/sources.list.d/devel:kubic:libcontainers:stable:cri-o:$VERSION.list     && mkdir -p /usr/share/keyrings     && curl -L https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/${crio_os}/Release.key | gpg --dearmor -o /usr/share/keyrings/libcontainers-archive-keyring.gpg     && curl -L https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/${crio_version}/${crio_os}/Release.key | gpg --dearmor -o /usr/share/keyrings/libcontainers-crio-archive-keyring.gpg     && apt-get update     && apt-get install -y cri-o cri-o-runc" did not complete successfully: exit code: 127
make: *** [Makefile:463: test-img] Error 1
make: Leaving directory '<path_to_sysbox>'

Describe how to best reproduce it.
git clone --recurse-submodules https://github.com/nestybox/sysbox.git nestybox/sysbox
make -C nestybox/sysbox sysbox-in-docker ubuntu-focal

Include information about the host's Linux version (e.g., lsb_release, uname -a).
                            ....               ****@*******************
              .',:clooo:  .:looooo:.           ------------------------
           .;looooooooc  .oooooooooo'          OS: Ubuntu focal 20.04 x86_64
        .;looooool:,''.  :ooooooooooc          Host: Precision 5570
       ;looool;.         'oooooooooo,          Kernel: 5.15.0-88-generic
      ;clool'             .cooooooc.  ,,       Uptime: 3 days, 6 hours, 4 mins
         ...                ......  .:oo,      Packages: 2206 (dpkg), 15 (snap), 197 (brew)
  .;clol:,.                        .loooo'     Shell: zsh 5.9
 :ooooooooo,                        'ooool     Display (LG HDR 4K): 3840x2160 @ 60Hz *
'ooooooooooo.                        loooo.    Display (SHP1515): 1920x1200 @ 60Hz
'ooooooooool                         coooo.    Display (ARZOPA): 1920x1080 @ 30Hz
 ,loooooooc.                        .loooo.    Display (SyncMaster): 1920x1200 @ 60Hz
   .,;;;'.                          ;ooooc     DE: Gnome 3.36.9
       ...                         ,ooool.     WM: Mutter (X11)
    .cooooc.              ..',,'.  .cooo.      WM Theme: Yaru
      ;ooooo:.           ;oooooooc.  :l.       Theme: Yaru [GTK2/3/4]
       .coooooc,..      coooooooooo.           Icons: Yaru [GTK2/3/4]
         .:ooooooolc:. .ooooooooooo'           Font: Ubuntu (11pt) [GTK2/3/4]
           .':loooooo;  ,oooooooooc            Cursor: Yaru (24px)
               ..';::c'  .;loooo:'             Terminal: tmux 3.0a
                             .                 CPU: 12th Gen Intel(R) Core(TM) i9-12900H (20) @ 5.00 GHz
                                               GPU 1: NVIDIA Device 25BA (3D)
                                               GPU 2: Intel Device 46A6 (VGA compatible)
                                               Memory: 14.64 GiB / 62.47 GiB (23%)
                                               Swap: 1.50 GiB / 2.00 GiB (75%)
                                               Disk (/): 650.19 GiB / 929.04 GiB (70%) - ext4
                                               Local IP (enx349971e7b9cf): <IP_ADDRESS>/24 *
                                               Battery: 100% [AC Connected]
                                               Locale: en_US.UTF-8

Workaround
I managed to get past the above error by adding gpg to tests/Dockerfile.ubuntu-focal but then I got the following error
** Building the test container **

[+] Building 8.5s (17/30)                                                                                docker:default
 => [internal] load build definition from Dockerfile.ubuntu-focal                                                                                0.0s
 => => transferring dockerfile: 8.54kB                                                                                0.0s
 => WARN: LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 115)                                                                                0.0s
 => WARN: LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 116)                                                                                0.0s
 => WARN: JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals (line 222)                                                                             0.0s
 => [internal] load metadata for docker.io/library/ubuntu:focal                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [ 1/25] FROM docker.io/library/ubuntu:focal                                                                                0.0s
 => [internal] load build context                                                                                0.0s
 => => transferring context: 268B                                                                                0.0s
 => [ 9/25] ADD https://raw.githubusercontent.com/docker/docker-ce/master/components/cli/contrib/completion/bash/docker /etc/bash_completion.d/docker.sh                                                      0.1s
 => CACHED [ 2/25] RUN apt-get update && apt-get install -y     acl     build-essential     gcc-x86-64-linux-gnu     libc6-dev-amd64-cross     linux-libc-dev-amd64-cross     gcc-aarch64-linux-gnu     libc  0.0s
 => CACHED [ 3/25] RUN wget https://go.dev/dl/go1.21.3.linux-amd64.tar.gz &&     tar -C /usr/local -xzf go1.21.3.linux-amd64.tar.gz &&     /usr/local/go/bin/go env -w GONOSUMDB=/root/nestybox               0.0s
 => CACHED [ 4/25] RUN go env -w GONOSUMDB=/root/nestybox &&     mkdir -p "/go/src" "/go/bin" &&     chmod -R 777 "/go"                                                                                0.0s
 => CACHED [ 5/25] RUN useradd -u1000 -m -d/home/rootless -s/bin/bash rootless                                                                                0.0s
 => CACHED [ 6/25] RUN cd /tmp     && git clone https://github.com/sstephenson/bats.git     && cd bats     && git reset --hard 03608115df2071fff4eaaff1605768c275e5f81f     && ./install.sh /usr/local     &  0.0s
 => CACHED [ 7/25] RUN if [ "amd64" = "amd64" ] ; then arch_str="x86_64";     elif [ "amd64" = "arm64" ]; then arch_str="aarch_64";     else echo "Unsupported platform: amd64"; exit; fi     && curl -LO ht  0.0s
 => CACHED [ 8/25] RUN curl -fsSL https://get.docker.com -o get-docker.sh     && sh get-docker.sh                                                                                0.0s
 => CACHED [ 9/25] ADD https://raw.githubusercontent.com/docker/docker-ce/master/components/cli/contrib/completion/bash/docker /etc/bash_completion.d/docker.sh                                               0.0s
 => CACHED [10/25] RUN go install github.com/go-delve/delve/cmd/dlv@latest                                                                                0.0s
 => CACHED [11/25] RUN cd /tmp && curl -LO "https://dl.k8s.io/release/v1.28.2/bin/linux/amd64/kubectl"     && install -o root -g root -m 0755 kubectl /usr/local/bin/kubectl     && rm /tmp/kubectl           0.0s
 => ERROR [12/25] RUN echo "deb [signed-by=/usr/share/keyrings/libcontainers-archive-keyring.gpg] https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_22.04/ /" > /etc/ap  8.4s
------
 > [12/25] RUN echo "deb [signed-by=/usr/share/keyrings/libcontainers-archive-keyring.gpg] https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_22.04/ /" > /etc/apt/sources.list.d/devel:kubic:libcontainers:stable.list     && echo "deb [signed-by=/usr/share/keyrings/libcontainers-crio-archive-keyring.gpg] https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/1.28/xUbuntu_22.04/ /" > /etc/apt/sources.list.d/devel:kubic:libcontainers:stable:cri-o:$VERSION.list     && mkdir -p /usr/share/keyrings     && curl -L https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_22.04/Release.key | gpg --dearmor -o /usr/share/keyrings/libcontainers-archive-keyring.gpg     && curl -L https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/1.28/xUbuntu_22.04/Release.key | gpg --dearmor -o /usr/share/keyrings/libcontainers-crio-archive-keyring.gpg     && apt-get update     && apt-get install -y cri-o cri-o-runc:
0.358   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
0.358                                  Dload  Upload   Total   Spent    Left  Speed
100  1093  100  1093    0     0  13011      0 --:--:-- --:--:-- --:--:-- 12858
0.469   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
0.469                                  Dload  Upload   Total   Spent    Left  Speed
100  1093  100  1093    0     0  10821      0 --:--:-- --:--:-- --:--:-- 10821
0.866 Get:1 https://download.docker.com/linux/ubuntu focal InRelease [57.7 kB]
0.964 Hit:2 http://archive.ubuntu.com/ubuntu focal InRelease
1.042 Get:3 http://security.ubuntu.com/ubuntu focal-security InRelease [128 kB]
1.061 Get:4 http://archive.ubuntu.com/ubuntu focal-updates InRelease [128 kB]
1.113 Get:5 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages [57.5 kB]
1.472 Hit:6 http://archive.ubuntu.com/ubuntu focal-backports InRelease
1.679 Get:7 https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_22.04  InRelease [1639 B]
1.703 Get:8 https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/1.28/xUbuntu_22.04  InRelease [1632 B]
1.763 Get:9 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages [3836 kB]
1.873 Get:10 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [4302 kB]
2.551 Get:11 https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_22.04  Packages [8832 B]
2.694 Get:12 https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/1.28/xUbuntu_22.04  Packages [1802 B]
2.937 Get:13 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages [1252 kB]
3.211 Get:14 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages [3805 kB]
3.908 Get:15 http://archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages [3957 kB]
4.665 Get:16 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages [1539 kB]
5.090 Fetched 19.1 MB in 4s (4384 kB/s)
5.090 Reading package lists...
6.577 Reading package lists...
7.903 Building dependency tree...
8.148 Reading state information...
8.244 Some packages could not be installed. This may mean that you have
8.244 requested an impossible situation or if you are using the unstable
8.244 distribution that some required packages have not yet been created
8.244 or been moved out of Incoming.
8.244 The following information may help to resolve the situation:
8.244
8.244 The following packages have unmet dependencies:
8.347  cri-o-runc : Depends: libc6 (>= 2.34) but 2.31-0ubuntu9.16 is to be installed
8.366 E: Unable to correct problems, you have held broken packages.
------

 3 warnings found (use --debug to expand):
 - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 115)
 - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 116)
 - JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals (line 222)
Dockerfile.ubuntu-focal:161
--------------------
 160 |     # works with Sysbox.
 161 | >>> RUN echo "deb [signed-by=/usr/share/keyrings/libcontainers-archive-keyring.gpg] https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/${crio_os}/ /" > /etc/apt/sources.list.d/devel:kubic:libcontainers:stable.list \
 162 | >>>     && echo "deb [signed-by=/usr/share/keyrings/libcontainers-crio-archive-keyring.gpg] https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/${crio_version}/${crio_os}/ /" > /etc/apt/sources.list.d/devel:kubic:libcontainers:stable:cri-o:$VERSION.list \
 163 | >>>     && mkdir -p /usr/share/keyrings \
 164 | >>>     && curl -L https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/${crio_os}/Release.key | gpg --dearmor -o /usr/share/keyrings/libcontainers-archive-keyring.gpg \
 165 | >>>     && curl -L https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/${crio_version}/${crio_os}/Release.key | gpg --dearmor -o /usr/share/keyrings/libcontainers-crio-archive-keyring.gpg \
 166 | >>>     && apt-get update \
 167 | >>>     && apt-get install -y cri-o cri-o-runc
 168 |
--------------------
ERROR: failed to solve: process "/bin/sh -c echo \"deb [signed-by=/usr/share/keyrings/libcontainers-archive-keyring.gpg] https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/${crio_os}/ /\" > /etc/apt/sources.list.d/devel:kubic:libcontainers:stable.list     && echo \"deb [signed-by=/usr/share/keyrings/libcontainers-crio-archive-keyring.gpg] https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/${crio_version}/${crio_os}/ /\" > /etc/apt/sources.list.d/devel:kubic:libcontainers:stable:cri-o:$VERSION.list     && mkdir -p /usr/share/keyrings     && curl -L https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/${crio_os}/Release.key | gpg --dearmor -o /usr/share/keyrings/libcontainers-archive-keyring.gpg     && curl -L https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/${crio_version}/${crio_os}/Release.key | gpg --dearmor -o /usr/share/keyrings/libcontainers-crio-archive-keyring.gpg     && apt-get update     && apt-get install -y cri-o cri-o-runc" did not complete successfully: exit code: 100
make: *** [Makefile:463: test-img] Error 1

I also got past the above by changing ARG crio_os=xUbuntu_22.04 to ARG crio_os=xUbuntu_20.04 but then I encountered another error (which I cannot reproduce now) and switched to tag v0.6.3 before I finally got sysbox-in-docker working
I guess it should be fine on master at 620453973fcb20f7cd9ca37d7e623ba91fdc663f with the above changes

Hi @tan-wei-xin-alez, unfortunately Sysbox-in-Docker hasn't been maintained in a while, so it's currently not working. We will likely deprecate it.
For an example of how to run Sysbox in Docker, refer to the Sysbox test container (e.g., tests/Dockerfile.ubuntu-jammy) and how it's launched by the Sysbox Makefile (see Makefile target test-shell).


Can you create a patch for Moto E condor?

The patching is not working for kernel 3.04 for condor.
patching file drivers/usb/gadget/Makefile
patching file drivers/usb/gadget/android.c
Hunk #2 succeeded at 2253 (offset 21 lines).
Hunk #3 succeeded at 2321 (offset 21 lines).
Hunk #4 succeeded at 2650 (offset 21 lines).
patching file drivers/usb/gadget/f_hid.c
Hunk #3 FAILED at 179.
Hunk #4 FAILED at 233.
Hunk #5 FAILED at 247.
Hunk #6 succeeded at 298 (offset 11 lines).
Hunk #7 succeeded at 399 (offset 11 lines).
Hunk #8 succeeded at 418 (offset 11 lines).
Hunk #9 succeeded at 522 (offset 11 lines).
Hunk #10 succeeded at 594 (offset 11 lines).
Hunk #11 succeeded at 616 (offset 11 lines).
Hunk #12 succeeded at 666 (offset 11 lines).
Hunk #13 succeeded at 717 (offset 11 lines).
3 out of 13 hunks FAILED -- saving rejects to file drivers/usb/gadget/f_hid.c.rej
patching file drivers/usb/gadget/f_hid.h
patching file drivers/usb/gadget/f_hid_android_keyboard.c
patching file drivers/usb/gadget/f_hid_android_mouse.c

Please try to fix the patch errors manually.

Find every file $FILE that also has a $FILE.rej
Compare $FILE and $FILE.rej and find out, which patches are necessary.


Error in Alpine

I'm trying to install this inside a Docker container based in Alpine, and I get this error:
[Sys::Lastlog] lastloghelper.c: In function 'lastlog_path':
[Sys::Lastlog] lastloghelper.c:109:11: error: '_PATH_LASTLOG' undeclared (first use in this function)
[Sys::Lastlog]     return _PATH_LASTLOG;
[Sys::Lastlog]            ^~~~~~~~~~~~~
[Sys::Lastlog] lastloghelper.c:109:11: note: each undeclared identifier is reported only once for each function it appears in
[Sys::Lastlog] lastloghelper.c: In function 'll2p':
[Sys::Lastlog] lastloghelper.c:142:41: warning: argument to 'sizeof' in 'strncpy' call is the same expression as the source; did you mean to use the size of the destination? [-Wsizeof-pointer-memaccess]
[Sys::Lastlog]    strncpy(ll_line,llent->ll_line, sizeof(llent->ll_line));
[Sys::Lastlog]                                          ^
[Sys::Lastlog] lastloghelper.c:145:41: warning: argument to 'sizeof' in 'strncpy' call is the same expression as the source; did you mean to use the size of the destination? [-Wsizeof-pointer-memaccess]
[Sys::Lastlog]    strncpy(ll_host,llent->ll_host, sizeof(llent->ll_host));
[Sys::Lastlog]                                          ^
[Sys::Lastlog] lastloghelper.c: In function 'lastlog_path':
[Sys::Lastlog] lastloghelper.c:110:1: warning: control reaches end of non-void function [-Wreturn-type]
[Sys::Lastlog]  }
[Sys::Lastlog]  ^
[Sys::Lastlog] make: *** [Makefile:7: lastloghelper.o] Error 1
[Sys::Lastlog] The spawned command 'make' exited unsuccessfully (exit code: 2, signal: 0)
[Sys::Lastlog]   in method build at /root/.zef/store/Sys-Lastlog-0.0.11.tar.gz/Sys-Lastlog-0.0.11/Build.pm line 27
[Sys::Lastlog]   in block <unit> at -e line 1
===> Building [FAIL]: Sys::Lastlog:ver<0.0.11>:auth<github:jonathanstowe>:api<1.0>

Any idea of what could it be?

Alpine does not support lastlog: sez here

In which case it should do something more sane rather than just blowing up.

Thanks for reopening. It would really be great to have some compiler-issued warning to the tune of "Hey, don't bother, it's not gonna work" I got this answer in SO, I don't know how helpful it will be.

I don't suppose there's something in $*DISTRO or $*KERNEL that indicates the Alpine Linux.

I've fixed it to bail without even trying to build on Alpine Linux for the time being, as the whole wtmp/lastlog functionality is intentionally omitted (thus making it not fully POSIX iirc, but hey.)


Auto-activating environment does not work when --name argument was passed to environment activation

I use the following commands to specify a name for an environment that I want to create using a .yml file:
    - name: setup micromamba and solve environment
      uses: mamba-org/setup-micromamba@v1
      with:
        environment-file: environment.yml
        create-args: --name test_micromamba

The .yml file already has a name: csp_surname_name attribute that I explicitly want to overwrite using the --name argument in create-args:. Everything works fine and the name gets overwritten, but when the workflow reaches the "auto-activation" step it seems to not be aware of the new name but uses the one in .yml file. Of course, an environment with this name does not exist at this point so the workflow crashes here:

Maybe we can parse the micromamba output to read the environment name/path

I'll close this issue. Feel free to reopen if you have further questions.


jpegli creates too bright output from input HDR JXL

Describe the bug
cjpegli creates too bright output from input HDR JXL.
To Reproduce
Sample image

Found here: https://github.com/d2phap/ImageGlass/issues/1677#issuecomment-1819045271
JXL file: https://github.com/gwy15/hdr/raw/main/IMG01623-HDR.jxl

Encoded with cjpegli from v0.9.1 ( https://github.com/libjxl/libjxl/releases/download/v0.9.1/jxl-x64-windows-static.zip ).

With XYB: ".\libjxl-v0.9.1\cjpegli.exe" ".\cat.jxl" ".\cat_xyb.jpg" --quality=90 --xyb --chroma_subsampling=444
Without XYB: ".\libjxl-v0.9.1\cjpegli.exe" ".\cat.jxl" ".\cat.jpg" --quality=90 --chroma_subsampling=444

Both results in a JPG image looking brighter / washed out vs. original JXL file, where the XYB variant looks the worst.
Screenshot from XnView MP v1.6.4 with ICC enabled (Settings -> General -> Color profile).

Screenshot from IrfanView v4.66 with ICC enabled (Options -> Properties/Settings -> Color management -> Enable color management).

Expected behavior
Colors and brightness should look the same on the output JPG file.
Environment

Windows 11 23H2, 22631.3007
x86_64

Something somewhere is not tonemapping properly. cjpegli is decoding to pixels with an ICC profile: ColorSync color profile 4.4, type jxl, RGB/Lab-mntr device by jxl, 4344 bytes, 1-12-2019, 0xde06c4e002fc07e4 MD5 'RGB_D65_202_Per_PeQ' and then attaching that same profile to the JPEG.
For what it's worth, the resulting jpeg does look correct with lcms2, so it's possible IrfanView is doing something incorrect with its color management.
The XYB jpeg is just incorrect in all accounts though.

Arguments against doing 1 might include the fact that it could make the user fail to realise that the result is not HDR, and that they have more flexibility in creating the SDR version if they do it themselves.


:bug: removing awscli docker image

Summary
We are using using amazon/aws-cli image from hub.docker.io instead
Related issue(s)
Fixes #

/approve


Set up CI build check

Set up GitHub Actions to check that the project builds successfully upon every commit.

Build is currently also tested as part of running package specs, but adding this job will be useful in the future to allow linting and formatting jobs to be run only after build passes.

Note: Running CI after every commit is not possible (as of 2021-02-21, see the GitHub Actions reference). Running after every push (and pull request) seems to be the best alternative. This shouldn't be much of an issue.


Update auth to 2.17.179

Updates software.amazon.awssdk:auth from 2.17.159 to 2.17.179.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk", artifactId = "auth" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequest = { frequency = "@monthly" },
  dependency = { groupId = "software.amazon.awssdk", artifactId = "auth" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #906.


suppress blank nav

Reviewer: Mia
Asana: https://app.asana.com/0/0/402612726718857/f
CC:
Description:
After some investigation, there appears to be no official way to detect apps being launched as a result of universal links.
I've worked around this by observing a policy decision request (which still comes through for the destination URL).  If the app is backgrounded before any of the delegate methods are called (i.e. the web view has not processed the URL), then it assumes an app has been launched as a result of a universal link and tells the view to 'go back' to the previous page.
Steps to test this PR:
Test 1 - launch app via universal link

Install twitter
Open the DuckDuckGo app and search for something that will give you a twitter links
Tap on a twitter link
Twitter will launch (unless you've previously suppressed this!)
When you return to the app it is on a blank page

Test 2 - standard browsing

Search for something that will not open in Twitter
Tap on a link
Observe the page loading in the app
Navigate to another app via pressing the home button
Return to the DuckDuckGo app and observe the same page is still displayed

Reviewer Checklist:

[ ] Ensure the PR solves the problem
[ ] Review every line of code
[ ] Ensure the PR does no harm by testing the changes thoroughly
[ ] Get help if you're uncomfortable with any of the above!
[ ] Determine if there are any quick wins that improve the implementation

PR DRI Checklist:

[ ] Get advice or leverage existing code
[ ] Agree on technical approach with reviewer (if the changes are nuanced)
[ ] Ensure that there is a testing strategy (and documented non-automated tests)
[ ] Ensure there is a documented monitoring strategy (if necessary)
[ ] Consider systems implications (Database connections, Grafana stats, CPU)

Great work finding a workaround for this. I had assumed it was a issue with our code but I can see from your investigation that it's really an ios bug. I think the bug  is annoying but not really that bad and I'm wondering if we should just leave it until it gets fixed by apple rather than putting in a workaround that we're unhappy with. What do you think?

Given this isn't a crashing issue and is likely to be fixed in iOS in the future, I would take the hardline of less code is better, so let's park it for now. I'll move it to a spike branch.


python310Packages.pysigma-backend-splunk: 0.3.3 -> 0.3.4

Description of changes
https://github.com/SigmaHQ/pySigma-backend-splunk/releases/tag/v0.3.4

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 178984 run on x86_64-linux 1

3 packages built:

python310Packages.pysigma-backend-splunk
python39Packages.pysigma-backend-splunk
sigma-cli


[Bug] mesa_git not cached in binary cache server

What happens?
Summary
I recently found out that the mesa_git package is not accessible from the binary cache server.
What is expected to happen?
mesa_git should be able to fetched from the default nyx binary cache server.
If possible, please attach logs
⯁ flake git:(master) ✗ ❯❯❯ just b
warning: Git tree '/home/kev/flake' is dirty
building the system configuration...
warning: Git tree '/home/kev/flake' is dirty
trace: evaluation warning: The ‘gnome.gnome-themes-extra’ was moved to top-level. Please use ‘pkgs.gnome-themes-extra’ directly.
[2/13/28 built, 2 copied (10.6/10.6 MiB), 2.6 MiB DL] building mesa-3a962a (buildPhase): [2010/4587] Compiling C object src/gallium/auxiliary/libgalliumvlwinsys.a.p/vl_vl_winsys_kopper.c.o

More information
# configuration.nix
{
  overlays = [
    inputs.chaotic.overlays.default
  ];

  chaotic.mesa-git.enable = true;
}

# flake.nix
{
  ...
  inputs = {
    chaotic.url = "github:chaotic-cx/nyx/nyxpkgs-unstable";
  }
}

It is in cache. Proof:

The drivers output, as in use in a NixOS:

nix-repl> :lf /etc/nixos

nix-repl> nixosConfigurations.desktop.config.hardware.graphics.package
«derivation /nix/store/8pq6677c9irdwvjlvbliw08himh90fyw-mesa-3a962a.drv»

nix-repl> nixosConfigurations.desktop.config.hardware.graphics.package.outPath
"/nix/store/ga889ppm4vxnxj6zv1rapwcjpgs9y61m-mesa-3a962a-drivers"

╰─λ curl -L 'https://chaotic-nyx.cachix.org/ga889ppm4vxnxj6zv1rapwcjpgs9y61m.narinfo'
StorePath: /nix/store/ga889ppm4vxnxj6zv1rapwcjpgs9y61m-mesa-3a962a-drivers
URL: nar/551e338fc11ada48e9c47262fd634a5ac366c13411350e46e0292962eba97bbd.nar.zst
Compression: zstd
FileHash: sha256:551e338fc11ada48e9c47262fd634a5ac366c13411350e46e0292962eba97bbd
FileSize: 41464365
NarHash: sha256:13nzlg4gkkzp2id98qspwxx65xsp02a403irb77whly6msbwv438
NarSize: 165124272

The out output, as seen from the flake:

╰─λ nix build 'github:chaotic-cx/nyx#mesa_git' --no-link --print-out-paths
/nix/store/2lixwvj0rqd71k1hx9vg8k8c1x9bbcra-mesa-3a962a

╰─λ curl -L 'https://chaotic-nyx.cachix.org/2lixwvj0rqd71k1hx9vg8k8c1x9bbcra.narinfo'
StorePath: /nix/store/2lixwvj0rqd71k1hx9vg8k8c1x9bbcra-mesa-3a962a
URL: nar/000db02ff8e36cfddc3e2bb85d5337a1580d6a3eb64203fc2092b1d93d2f892a.nar.zst
Compression: zstd
FileHash: sha256:000db02ff8e36cfddc3e2bb85d5337a1580d6a3eb64203fc2092b1d93d2f892a
FileSize: 16060941
NarHash: sha256:1l5mqpv686av744pjb8lslzdiphfbjg7w211h4yf4vckbcv23q31
NarSize: 49995576

If your hash in nixosConfigurations.$(hostname).config.hardware.graphics.package does not match the one from above, either:
(1) you have overlays;
(2) you are using chaotic.inputs.nixpkgs.follows, which we don't suppport;
(3) you are mixing nixpkgs (like stable+unstable, or two different revisions of unstable for tapping bugs), which we don't endorse.


Implement API call in Java to download transcript data.

Create code that can make calls to the Voiceflow API for a specific chatbot and download the transcript data. This data should be formatted into a JSON format.

Call has been implemented (see getJsonContent under TranscriptService). Returns an three-tiered ArrayList  (i.e., ArrayList<ArrayList<ArrayList>>) with the following format:
Outermost Layer ArrayList<...>: Outer container to store the overall results for each transcript.
Middle Layer ArrayList<>: Each element represents one full transcript that was parsed.
Inner layer ArrayList<>: Each element represents a pair of turns from the given transcript; the first string represents a message from the chatbot, and the subsequent string represents the intent given by the user in response. Note that if there is only one string, it is a termination message when the chatbot ends.
Updated to use gson library and reformat turns into pairs to better match with tree creation function.


RegSetValue -> RegSetValueEx

RegSetValue is for 16-bit compatibility. Documentation should correctly point to Ex version
/windows/desktop/api/winreg path redirects to /windows/win32/api/winreg, hence win32 path component is more appropriate.

@AjayVV : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@mcleanbyron : Thanks for your contribution! The author(s) have been notified to review your proposed change.


feat: configure Whisper model for APIs

Specifically, I'd like to be able to try distill-whisper-large on Groq to trade off a little accuracy for a significant speedup.

Maye Whisper-Zero by Gladia would be worth a try as well?


update starter repo url

automated

@sherubthakur fyi, we're still working towards resolving these test failures here - should be done this week


feat(ccstate): remove default distinct behavior

Pull Request Test Coverage Report for Build<PHONE_NUMBER>8
Details

5 of 5 (100.0%)  changed or added relevant lines in 1 file are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.2%) to 99.818%

Files with Coverage Reduction
New Missed Lines
%

packages/ccstate/src/core/signal-manager.ts
2
99.36%

Totals

Change from base Build<PHONE_NUMBER>0:
-0.2%

Covered Lines:
1277

Relevant Lines:
1279

💛  - Coveralls


ova import error,vmware worksation

remnux-v7-focal.ova
Unzip the file show data error.

Thanks for reporting this issue, @smartzh. Looks like the file on SourceForge is corrupted. I'll supply a new version of the file and let you know once it's there.

@smartzh, I've re-uploaded the OVA file to SourceForge, then downloaded and confirmed that the file has the expected SHA256 hash. Please give it another try. I'm wondering whether SourceForge consistently servers the file correctly or whether it sometimes corrupts the file.

@lennyzeltser it worked,thanks for your great support.


Parser module codereview

This PR contains updates that pertain to code review discussions on PR #3 (which got merged already by accident)
I have not figured out a great way to update either comment about the AbstractParser yet, and would like to spend a little more time figuring that out. I'll open an issue for those comments to make sure they don't get forgotten about.
Could @connojd please merge this if/when @cpavlina approves?

@connojd 👍 to merge


fix the llm organization parameter is ineffective during queries

Description
fix the llm organization parameter is ineffective during queries
Related Issues

none

Proposed Changes

graphrag/query/factories.py  pass organization parameter

Checklist

[x] I have tested these changes locally.
[x] I have reviewed the code changes.
[x] I have updated the documentation (if necessary).
[x] I have added appropriate unit tests (if applicable).

Additional Notes
[Add any additional notes or context that may be helpful for the reviewer(s).]

@microsoft-github-policy-service agree

@microsoft-github-policy-service agree


Adding Question and Difficulty along with Discussion

Added Question: so that we don't have to see the solution first
Added Difficulty and sorted by difficulty

VS CODE:

GITHUB:

Good stuff @sandipsubedi !