Set the camera sensor mode in Raspberry Pi

Is it possible to select a sensor mode (https://picamera.readthedocs.io/en/release-1.13/fov.html#sensor-modes) explicitly when using V4L2? If so, I would like to request that the option be added to v42rtspserver.
This would be equivalent to the -md option in raspivid.
(P.S. thank you for writing this software)

Hi paol,
This software aims to be as standard as possible, then adding specific control for raspberry is not a way I'd like to follow.
You can probably use v4l2-ctl to set this option before startting v4l2rtspserver.
Best Regards,
Michel.

adding specific control for raspberry is not a way I'd like to follow

Fair enough. I'll close this request then.
Do you know whether this operation is possible via v4l2-ctl? I went over the options (there are a lot of them) and couldn't find it.

Hi,
I looked to v4l2-ctl -L and did not find it, probably it is not supported by the V4L2 driver, it need to look at that.
Regards,
Michel.


Resource specification

Job resource limits are currently either non-existent or hard-coded (e.g. available memory, available CPUs, max fd and processes).
Expanding on #1230, it should be easy for users to specify values for resource limits, including (but not limited to):

available memory
available swap
available CPUs
CPU time (either hard limit or relative share)
block I/O time (either hard limit or weighted)
max file descriptor
max number of processes

As well as providing a hard upper limit, it would also be useful to provide similar values which can be used by the scheduler to decide where to place jobs based on available resources across the cluster (and also act as a soft limit for rlimit style limits).
With this in mind, I propose a structure similar to the Kubernetes Resource Specification:
type Spec struct {
	// Request is the amount of resource a job expects to consume, so the
	// job should only be placed on a host with at least this amount of
	// resource available, and once scheduled this amount of resource
	// should then be unavailable on the given host.
	Request int64

	// Limit is an upper limit on the amount of resource a job can consume,
	// the outcome of hitting this limit being implementation defined (e.g.
	// a system error, throttling, catchable / uncatchable signals etc.)
	Limit int64
}

There would be a hard-coded list of resources with default specs, e.g.:
type Type string

const (
	TypeMemory  Type = "memory"
	TypeNumCPUs Type = "num_cpus"
	TypeMaxFD   Type = "max_fd"
	...
)

var Defaults = map[Type]Spec{
	TypeMemory:  {Request: 1*GB, Limit: 2*GB},
	TypeNumCPUs: {Request: 1,    Limit: 2},
	...
}

In the controller, resource specs would be declared at the individual process level, e.g.:
type ProcessType struct {
	...
	Resources map[resource.Type]resource.Spec
}

and these would be transferred to the job, which the container runner would use to impose the limits:
type Job struct {
	...
	Resources map[resource.Type]resource.Spec
}

Hosts would also expose their available resources to aid in scheduling decisions:
type Host struct {
	...
	AvailableResources map[resource.Type]int64
}

This description is intentionally vague on the implementation of the limits, but should provide an adequate level of abstraction to accommodate the limits mentioned above.
The ability to handle user-defined limits is not supported, with the idea that tag based filtering will give users enough flexibility to handle custom scheduling decisions.

Here is a concrete implementation of this proposal: https://github.com/flynn/flynn/compare/resource-specification
/cc @titanous

I believe this was implemented.


@ExplicitNull is not recognized

How to use @ExplicitNull?
I need an attribute to be saved even with a null value.
I found in the documentation, a brief comment about @ExplicitNull.
But I can't use it, if I put it in my variable, XCode doesn't recognize it.
Look:
import FirebaseCore
import FirebaseFirestore
import FirebaseDatabase
import CodableFirebase

class Test: Entity, Codable {
    var id: String?
     @ExplicitNull var branch_id: String?

}

This @ExplicitNull gets an error, it appears:
Unknown attribute 'ExplicitNull'

I discovered.
To use @ExplicitNull you must have FirebaseFirestoreSwift in your project.
So I added it to my Pod and added an import and it worked.
It's weird, zero documentation explaining this, but it worked.


Support iOS 8

I in debug console my app prompt next message:
So its don't support iOS 8?
<Google:HTML>
You are currently using version 6.12.0 of the SDK, which doesn't officially support iOS 8. Please consider updating your SDK to the most recent sdk version, 6.12.2, to get iOS 8 support, including a fix for smart banner rendering in landscape mode. The latest SDK can be downloaded from http://goo.gl/iGzfsP. A full list of release notes is available at https://developers.google.com/mobile-ads-sdk/docs/admob/ios/rel-notes.

It has been upgraded to v6.12.2 in Nov 2014, see commit:
https://github.com/floatinghotpot/cordova-admob-pro/commit/a73b11f94be257d7a77206aaa490fab001a7a1b8
I double checked the binary .a file, it's same size: 13,403,052 bytes.
are you using an old version?

Hey I just downloaded this plugin and am getting this warning:
You are currently using version 7.0.0 of the SDK, which doesn't officially support iOS 8. Please consider updating your SDK to the most recent sdk version, 7.1.0, to get iOS 8 support, including a fix for smart banner rendering in landscape mode. The latest SDK can be downloaded from http://goo.gl/iGzfsP. A full list of release notes is available at https://developers.google.com/mobile-ads-sdk/docs/admob/ios/rel-notes.

Is it not updated?

but it's already upgraded to v7.1.0, see: 30817fac8f80993bb38a24d97b94214ff5c26fe4

Weird, is the version in the Cordova registry outdated? I could try adding the plugin directly from GitHub if that'll work.

you are correct, i forgot to publish it to cordova registry... now it's being published as v2.7.5

wait a few minutes ...

Wahoo! Thanks :smile:

done.

Hey @floatinghotpot, I just tried this morning with
cordova plugin rm com.google.cordova.admob
cordova plugin add com.google.cordova.admob

But I'm still getting the same message when I launch Admob in my app about it not being compatible with iOS 8.

Opening the plugin.xml shows that it is still version="2.7.4".

i've tried to install the admob plugin and the plugin.xml is 2.7.5
try:

remove the cache from your home: ~/.plugman/cache
type "cordova plugin remove xxx", instead of "plugman plugin rm xxx", though i am not quite sure...

Hey @floatinghotpot! Good news. After clearing the plugman cache, the plugin installed the latest. Thanks! Silly caches... :smile:


Feat: Add a sample silverback/profile.toml to the README

Overview
Provide a simple overview of what you wish to see added. Please include:
~/.silverback/profile.toml is important part of getting this to work.
Can we add a section describing this?
default-profile = "NAME-cluster"

[auth.default]
host = "https://account.apeworx.io"
client_id = "KEY_HERE"

[profile.default]
host = "https://silverback.apeworx.io"
auth = "default"

[profile.NAME-cluster]
api-key = "KEY_HERE"
host = "AWS_URL_HERE"

Specification
Dependencies
Include links to any open issues that must be resolved before this feature can be implemented.

it is out of scope, so we redefine it under contributing


Added container sinon stub for the 'authenticator:test' argument

Fixes failing tests for simplabs/ember-simple-auth#822

thanks!


[SPARK-20449][ML] Upgrade breeze version to 0.13.1

What changes were proposed in this pull request?
Upgrade breeze version to 0.13.1, which fixed some critical bugs of L-BFGS-B.
How was this patch tested?
Existing unit tests.

Test build #76110 has started for PR 17746 at commit aeb7eb5.

cc @dbtsai

Test build #76110 has finished for PR 17746 at commit aeb7eb5.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76110/
Test PASSed.

LGTM. Merged into master and branch 2.2

Many thanks for @WeichenXu123 helping to fix this bug in breeze!

Not that I have any specific concern, but did anyone look at the changes from 0.12 to 0.13 to see if anything might be breaking? probably not, but it does leak into the user classpath

@srowen Couple APIs changes in Breeze 0.13 are not source code compatible with 0.12. We should tell users about that in the release note, and they need to do their migration if they are using Breeze in their application. FYI, we only use optimization package in Breeze now, and we have a plan to move the optimization code into Spark to reduce the 3rd party dependencies brought by Breeze.

Can I ask how we decided merging this dependency change after the cut of the release branch (especially this change affects user code)?

+10 for not merging major changes like this so close to the release, especially after an RC has been cut, unless it's for blocker bugs.  Same for new APIs such as https://github.com/apache/spark/pull/17715
I guess it's OK not to revert them, but let's definitely avoid doing this in the future.

The motivation to have this one merged in Spark 2.2 is not only just for #17715 but also because Breeze 0.13.x fixes many bugs in upstream. Since Spark was tightened to 0.12, many users (including my company) have difficulty to upgrade Breeze alone by themselves, which forces people to have a copy of implements with fixes in the application code.
In the long term, because we only use Breeze's optimizer in Spark, we should have our optimizer implementation in mllib-local to remove the heavy external dependencies.
In retrospect, we started to work on the fix we want to have in upstream too late, so we had the upstream to release the fixes right after the 2.2 branch was cut. We should definitely plan it earlier in the future.

@dbtsai Thanks for the explanation and the context :)

Hello, are there any plans to backport this into 2.1 branch? The LBFGS and other fixex in 0.13.1 seem important enough.

@superbobry see the discussion above? doesn't seem safe to do so

@srowen thanks! I've missed the point that 0.13.1 was intentionally merged into the upcoming release.
@dbtsai could you give an example of the breaking API change between 0.12 and 0.13.1? I'm sure I've missed it as well, but from the commit log it seems it's all bug fixes or backward-compatible changes.

@superbobry As you can see in this PR, one of them is
-    override def link(mu: Double): Double = dist.Gaussian(0.0, 1.0).icdf(mu)
+    override def link(mu: Double): Double = dist.Gaussian(0.0, 1.0).inverseCdf(mu)

Thank you.


Could not find the SWI-Prolog library in this platform.

I've installed swipl with snap refering https://www.swi-prolog.org/build/snap.html.
But when I import pyswip in python, it raises Could not find the SWI-Prolog library in this platform. If you are sure it is installed, please open an issue..
Also, I found after I run swipl --dump-runtime-variables, it shows:
PLBASE="/snap/swi-prolog/68/usr/lib/swipl";
PLARCH="x86_64-linux";
PLBITS="64";
PLVERSION="90003";
PLSOEXT="so";
PLSOPATH="LD_LIBRARY_PATH";
PLLIBDIR="/snap/swi-prolog/68/usr/lib/swipl/lib/x86_64-linux";
PLLIB="-lswipl";
PLLIBSWIPL="/snap/swi-prolog/68/usr/lib/libswipl.so.9";
PLSHARED="yes";
PLTHREADS="yes";

But I do not find libswipl.so:

Any helps and thanks in advance.

Btw, this is the system info:
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

What is the version of swipl? PySwip is currently incompatible with SWI-Prolog 9.x.

If somebody else has this issue, a while back I opened a PR that addresses this(#106). It's a simple fix you can make to the version of pyswip you have running

The recently released PySwip v0.3.0 should solve this issue when SWI-Prolog is installed using the recommended ways mentioned at https://pyswip.org/get-started.html


any plans for websys-webRTC transport?

Vince, very cool library for the browser.
I was wondering if there are any plans in the works to also make one for WebRTC transport via web-sys?

Thank you @DougAnderson444, the libp2p team has it as a plan here, I think they have already implemented the server part maybe @mxinden can comment.

@DougAnderson444 going to close this, if you are not in a hurry probably the best thing to do is to wait for the libp2p team to work their magic, you can follow the progress on the specs here.

Ok, thanks Vince!

Vince, very cool library for the browser.

Great to see more implementations of Transport @vincev!

I think they have already implemented the server part maybe @mxinden can comment.

Correct. See https://github.com/libp2p/rust-libp2p/tree/master/transports/webrtc
There are two libp2p WebRTCs:

browser-to-server https://github.com/libp2p/specs/blob/master/webrtc/README.md

Implemented in rust-libp2p as a server
Implemented in js-libp2p as a client

browser-to-browser (or private-to-private) https://github.com/libp2p/specs/pull/497

Implemented in js-libp2p https://github.com/libp2p/js-libp2p-webrtc/pull/90

While the server part of browser-to-server is already released as an alpha in rust-libp2p, I would very much like to see the browser side (via WASM) in rust-libp2p as well.
Once that is in place, I don't think implementing the browser-to-browser specification for rust-libp2p is a big endeavor.

to wait for the libp2p team to work their magic

I don't think we (rust-libp2p maintainers) will get to either of the above planned implementations in Q1 or Q2. Help would be very much appreciated. It opens a hole new use-case for rust-libp2p. Happy to support in any way I can.

Happy to meet and discuss this further in one of the upcoming rust-libp2p open maintainer calls with @thomaseizinger and me.
https://github.com/libp2p/rust-libp2p/discussions/3604


Removed tenant ID's

I have found and removed two tenant ID's from URL links.
These links would have caused issues for users who click on them and try to sign in as the tenant ID would most likely not be their one and therefore give a signing error.

@microsoft-github-policy-service agree


docs: update roadmap with appc->oci projects

This commit updates the roadmap with more references and details related
to current appc->oci projects.

/cc @philips

LGTM


Make EventSub a Closer

Using a [pkg/sync] Closer makes the EventSub.Close() call idempotent and easier to use.
Closes #161

While checking the tests of another MR, i saw this log message which is introduced by this MR:
msg="could not close EventSub" error="<nil>"
It seems that IsAlreadyClosedError does also return true for certain nil errors, this seems like a bug.


Terminal Doesn't Show Current Directory When Initialization

Issue Type: Bug
New Terminal
VS Code version: Code 1.33.1 (51b0b28134d51361cf996d2f0a1c698247aeabd8, 2019-04-11T08:27:14.102Z)
OS version: Windows_NT x64 10.0.17763

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (8 x 4008)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
15.95GB (10.77GB free)

Process Argv
.

Screen Reader
no

VM
0%

Extensions (1)

Extension
Author (truncated)
Version

csharp
ms-
1.19.0

Following -- seeing the same issue

Same issue here. Cursor also does not work well. Does not respect blinking configuration and suffers from lag.
Version: 1.33.1 (user setup)
Commit: 51b0b28134d51361cf996d2f0a1c698247aeabd8
Date: 2019-04-11T08:27:14.102Z
Electron: 3.1.6
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17763

Me too
After update the windows to 1809 version

Me too after update the windows version to 1809

Me too

This is a bug in Windows 10 1809, unfortunately we have no way to work around the issue so you will need to wait until you get the next version of Windows 10 (1903).
/duplicate https://github.com/Microsoft/vscode/issues/57803


Drop support for HSM

Hardware Security Module is not used in the codebase. Let's simplify the code by removing it.
https://github.com/zeta-chain/node/blob/b516a46959a730bb1dd04dd6a8c0b8b6e05714c4/cmd/zetaclientd/hsm.go#L16

I don't think "not used in the codebase" is necessarily accurate, it is definitely could be used for signing in zetaclient.
But regardless I asked the observer signers yesterday in slack if anyone was using this and I didn't get any responses. So I think it's safe to remove.

The HSM signing logic was specifically requested to be added to zetaclient before the mainnet launch.
It would be a good idea to confirm the reason behind the original request before removing it.
I think the original request was from devops team ? Not sure,
tagging @CharlieMc0 to get more clarity

Removing it is fine. No one used the functionality and the implementation is probably riskier because of the unmaintained dependency. We wanted to use HSM but it ended up not working well in practice


nz-table nzVirtualScroll table header not aligned

Reproduction link
https://stackblitz.com/edit/angular-ewptrz?file=src/app/app.component.ts
Steps to reproduce
scroll left/right and the header does not align with its corresponding column
Scroll up/down and the alignment is off even more if the column content is long
What is expected?
table header aligns with its column
What is actually happening?
table header not aligned

Environment
Info

ng-zorro-antd
8.3.0

Browser
Chrome Version 76.0.3809.132

https://stackblitz.com/edit/angular-ewptrz-yxoqzr?file=src/app/app.component.ts
you have to add
td{
word-break:break-all;
}
to break all words


Tensor-Core support for convolutions

This PR adds Tensor-Core support for convolutions.
With this PR, Tensor-Core is automatically used in convolution layers when Tensor-Core is available. You can also manually enable/disable use of Tensor-Core by setting global configuration variable cudnn_use_tensor_core to True/False like below
from chainer import configuration
configuration.config.cudnn_use_tensor_core = [True|False]

Please note that https://github.com/cupy/cupy/pull/494 needs to be used in order to test this PR.
Also I would suggest that you apply #3386 first.

The code LGTM. Could you write a brief explanation of chainer.config.cudnn_use_tensor_core to docs/source/reference/core/configuration.rst?

Jenkins, test this please

Jenkins, test this please

CI passed. I will merge after the documentation is made ready.

@beam2d Thank you for your review.
I've just added the brief explanation of chainer.config.cudnn_use_tensor_core to docs/source/reference/core/configuration.rst.

LGTM

Thank you!


feat: website redesign with html, css and tailwind

Make the webpage responsive #15
I have completely redesigned the website with html, js and tailwind.
I have deployed the changes in my netlify for your reference - https://653cae0b7e108051fea99667--phenomenal-bubblegum-f0e69f.netlify.app/

Thank you @vctc  this looks amazing. However, you have changed the theme, layout, and design.
I would request you to make the current design responsive. Instead of redesigning the page.
I can later open a new issue for redesigning the webpage


FEAT: Provide the functionality to query information on various cached models hosted on the query node.

To learn how to use it via command line, run the command xinference cached --help;

for usage via RESTful calls, refer to the associated function list_model_cahced .

The running result is similar to the following image:

Could you add some tests?

Run Supervisor on device A：

Then, run Worker on device A:

Next, run cmdline xinference-cached, get this output:

And, run Worker on device B:

Next, run cmdline xinference-cached again, get this output:

device A's cache was lost, please check it. i guess it was because device A and device B has the same model_name, and device A model was covered by device B.


Use [variablename] instead of %%variablename%%

[variablename] seems to be the standard for webpack, so replacing the weird %%variablename%% syntax with that might make sense for newcomers to the codebase.

@jantimon any objections?

good idea to change it. %%name%% was just the first approach to get it working
[variablename] is valid javascript and might replace "real" javascript of entry.js so we should probably look for something else.

agreed @jantimon - any suggestions?

In the end the entry.js is a template - maybe we could precompile it with a lightweight template engine to increase the readability and it's easier to understand that it's just a template for the component entry point.

What about something like this: http://ejohn.org/blog/javascript-micro-templating/

Can we use with together with webpack 2.0?

What would you use it for here?

The microtemplating and the lodash template (which is based on johns micro templating) use it


[cxx-interop] Extract libstdc++ installation path from Clang

To inject a modulemap into the libstdc++ directory, Swift needs to know the path of the libstdc++ installation. Previously it was assumed to be /usr/include/c++, however, this might not be the case. For example, on CentOS the stdlib is located at /opt/rh/devtoolset-{version}/root/usr/include/c++/{version}.
This change teaches Swift to extract the libstdc++ include paths from the Clang driver, and fixes C++ stdlib lookup on CentOS.
rdar://93341210

@swift-ci please smoke test

I think this pull broke several tests on the Android CI, as many now report this new warning (13 of those 31 were already failing for unrelated reasons before).
This change will probably need to be modified for the Android NDK, which doesn't use a standard toolchain layout of usr/bin/clang and usr/include/c++/, which the clang Driver function you're calling here expects.

Hmm, since Android uses libc++, this logic shouldn't run. Submitted https://github.com/apple/swift/pull/59156.


Docker version of waterrower-ble now available

Installation of waterrower-ble on the Raspberry Pi can be challenging. I have made a docker version to make the WaterRower BLE functionality available to all.
The docker container simplifies running waterrower-ble on a Raspberry Pi 3 (B+). Just follow the instructions on docker-waterrower-ble.
Happy Rowing!

Cross posting from the DataBreach repository: I was able to figure out last night that it looks like the docker container has the same issue of an incomplete ant-plus library install as I documented here: olympum/waterrower-ble#4
Which means that it won't broadcast ant+ power/cadence with the BLE.
I'm still trying to learn enough about docker containers to figure out how to get typings installed and/or move the files to the right place in the container, so any help is appreciated. (I got the olympum ant-plus git repository moved into the container but can't do the install/build without "typings" and ran out of time last night...


Make y, z optional arguments forFunctionParameters that depend on space

Some FunctionParameters depend on space and time (e.g. ambient temperature) but it doesn't always make sense to allow these to depend on space, for example if the thermal model is lumped then the temperature cannot depend on space. For the user, this can be confusing (see https://github.com/pybamm-team/PyBaMM/issues/3630).
Is there a nice way to be able to define these functions differently depending on the model options? Then for lumped models users can pass T(t) and if they try to pass T(y,z,t) we can catch it and throw an informative error.

From @ejfdickinson

I'd feel it's most Pythonic to put optional arguments last, and explicitly allow them to be optional. In general we don't want to have to write functions whose return values don't depend on their arguments, right?

What's happened here is that you've enabled complicated behaviour by requiring simple behaviour to have a complicated calling pattern!
Yes, this should work. Let's do that

In the actual model definitions, we will need to update the calls from (y,z,t) to (t, y=y, z=z) (best to be explicit in the latter in anticipation of other coordinate systems).

Hi! I would like to take this on.


[Bug]: NullPointerException in hop/registerPipeline Rest API when log_file flag is enabled

Apache Hop version?
2.7.0
Java version?
22.0.2
Operating system
Windows
What happened?
When invoking the hop/registerPipeline REST API with the payload provided below, the API throws a NullPointerException if the log_file flag is set to Y and a log_filename is specified.
The specified log file gets created in the container, but the exception occurs afterward, halting further execution.
Error Details:
Exception Message:
java.lang.NullPointerException
at java.base/java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1011)
at java.base/java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1006)
at org.apache.hop.core.logging.LoggingRegistry.registerLogChannelFileWriterBuffer(LoggingRegistry.java:261)
at org.apache.hop.core.logging.LogChannelFileWriter.(LogChannelFileWriter.java:74)
at org.apache.hop.core.logging.LogChannelFileWriter.(LogChannelFileWriter.java:87)
at org.apache.hop.www.BaseWorkflowServlet.createPipeline(BaseWorkflowServlet.java:146)
at org.apache.hop.www.RegisterPipelineServlet.generateBody(RegisterPipelineServlet.java:56)
Steps to Reproduce:

Start the Apache Hop server using the provided Docker script:
docker run -it --rm
--env HOP_SERVER_USER=admin
--env HOP_SERVER_PASS=admin
--env HOP_SERVER_SHUTDOWNPORT=8080
--env HOP_SERVER_PORT=8181
--env HOP_SERVER_HOSTNAME=<IP_ADDRESS>
-p 8080:8080
-p 8181:8181
--name my-hop-server-container
apache/hop:2.7.0

Make a POST request to hop/registerPipeline REST API with the following payload:
<pipeline_configuration>
...
<log_file>Y</log_file>
<log_filename>/tmp/generateRowsLog.log</log_filename>
...
</pipeline_configuration>

Observe that the log file is created inside the container, but a NullPointerException is thrown during the pipeline registration process.

Attached full xml payload
payload.txt
Expected Behavior:
The pipeline should register successfully, and logs should be written to the specified file without errors.

Issue Priority
Priority: 3
Issue Component
Component: Hop Server

In BaseWorkflowServlet.java, SimpleLoggingObject is created at line 118

Which further creating LogChannelFileWriter at line 143, serveletLoggingObject is used to get log channel Id which is of type SimpleLoggingObject.

SimpleLoggingObject class return LogChannelId as null at line 88

Above LogChannelFileWriter if furter send to registerLogChannelFileWriterBuffer which is using Log Channel Id as key thus further throwing null pointer exception at line 261


Docker

Create a Dockerfile that includes all of the dependencies so we can make 'install' and use easier for those who want to use docker.

As per the pull request from the other day, I have done a little work on dockerising this application, I'll push some of my work up later on for you to have a look through.
I'm liking the idea to put all the scripts into a rakefile, this will make the docker workflow much simpler for end user types :-)

Thanks man, I just merged the new Rakefile. Running it will spit out how to use it and what commands do what etc.
The next major hurdle (for me) before I feel comfortable tackling the Docker build is issue #2 / finding a way to have good FREE LaTeX fallback fonts for those without expensive ass Adobe fonts installed.

Ok, as of commit 3515506 there's a working docker branch. It's rough but it works. I'll be working on removing a LOT of cruft to shrink the size down before I merge to master.


Feature Request: custom card component lovelace-theme-maker

Hi,
I use multiple custom components on Home Assistant. At the moment this one is not supported in the Android App.
Thanks.

I'm afraid CSS styling can't be supported by native app.


Experimentally Rewrite RageTimer Implementation

This is done with the hope of fixing some stutter, drift, or inconsistency issues.
More testing is needed, and I have no idea what I'm doing here.
RageTimer hasn't been touched for many years, and it's looking a bit outdated (and with outdated comments). Some discussion may need to take place as for what to do with it exactly. What I've done to RageTimer here is change its internal time-keeping stuff with a std chrono duration to hopefully make things both more precise and more consistent. However, I don't know if that has actually done anything. All I do know is that it didn't break anything. (and for the things it did break, I fixed)
Some decisions I made in working on this (for example removing the bAccuracy parameter) are based on the fact that some of these comments and practices are pointing to things that are relevant for many years ago, and shouldn't be an issue in my opinion.

Essentially ready for review. No notable performance improvements or resulting visible fixes.
Not sure if this fixes sync drifting over long periods of time. That's the last thing I haven't tested which I have been able to test.

For anyone else reviewing this: I think everything above this (https://github.com/etternagame/etterna/pull/591/files#diff-f0fecd00f9c471e049460a811391bd9dR1) line is just formatting changes, removing an unused ragetimer from characters, and renaming function calls and is safe to ignore.


Update windows-autopatch-register-devices.md

Why
The menu names and structures have changed in Microsoft Intune.
Changes
The updated text reflects the new naming convention in the Intune - Device blade
The general text is also tuned to be more concise and clear.

Hi @SimonSkotheimsvik Thank you for providing feedback. I've verified with the team and have made updates to this article outside of your/this PR. Will be closing this one :).

Hi @SimonSkotheimsvik, due to unification being rolled out in phases, you might not have the latest GA version yet which would explain the differences between what the team sees and what you're seeing. Do you still see the Windows Autopatch blade and devices? If you do, you haven't yet received the unified experience yet.


Header logo & color changes

Updated logo in header
Changed background color of header, footer, and links to maroon
Changed default font to Lucida Sans (the one used by Medium)

Preferably the logo should be flush with the left side of the blog post text & titles. I think probably the best way is cropping the image a little on the left/right. Can we do that directly with the included svg or do we need to modify the original file?

The move of the logo a little to the left looks nice. It seems to not always stay in the same place when there's less horizontal space though.

I think if we reverted to whatever the old css but reduced the padding/margins of the svg (I think we might be able to crop this way?) that might solve this problem but I'm not certain.
The menu button also doesn't seem to be working for me here and the logo still gets incredibly small some reason.
After seeing what the logo looks like on the grey background I agree we do need a different header/footer highlight color although I'm not certain what would be best. Perhaps we should rope some others in for color suggestions?


[MINOR][DOCS] Fix the link to the pickle module page in RDD Programming Guide

What changes were proposed in this pull request?
This pull request changes the link to the pickle module page from https://docs.python.org/2/library/pickle.html to https://docs.python.org/3/library/pickle.html in RDD Programming Guide.
Why are the changes needed?
Since Python 2 is no longer supported and it is preferable to refer to the pickle module page of Python 3.
Does this PR introduce any user-facing change?
Yes.
Before: the Pickle link's destination page was https://docs.python.org/2/library/pickle.html
After: the Pickle link's destination page is https://docs.python.org/3/library/pickle.html
How was this patch tested?
By building the documentation site and check the link's destination page is changed correctly in the local environment.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Merged to master.


Is it possible that enumerates the currently available FontFamilys

Use case

I want to make users can choose fonts by themselves. But i didn't find any way to enumerate fonts available in flutter engine.
Proposal

Will a feature to do it? Or i should do it myself in native plugin

Hi @youmu129, Thanks for filing the issue. Flutter doesn't provide any such list of available fonts, However, you can always  maintain the list of font names since they are basically a  List and then apply the desired font globally as below
 Theme.of(context).textTheme.apply(
          fontFamily: 'myfontfamily',
        );

Closing as this is neither  a bug nor a feature request.


Trying to learn ... controllers seem unintuative

When running the below I get the following error yet I don't quite understand why.  I have a class defined with methods.
! there must be a 'class' or 'controller' or 'service' with an 'container'

Note, that error message should read "a 'container'".

lib/Controller/Users.pm6
unit class Controller::Users;
method get(Str:D $email!) { }
method delete(Str:D $email!) { }
method post(Str:D $email!) { }
method list(Str:D $email!) { }
app.bailador
use lib <lib>;
use Bailador;
use Controller::Users;
my $user-controller = Controller::Users.new();
get    '/data/:id'       => { :$user-controller, to => 'get'};
delete '/data/:id'       => { :$user-controller, to => 'delete'};
post   '/data/:id' => { :$user-controller, to => 'post'};
get    '/data'           => { :$user-controller, to => 'list'};
baile();

I am dumb.  This is what happens when you are programming late at night.


Support Chrome --use-file-for-fake-video-capture flag

Any idea how much work it would be to support the --use-file-for-fake-video-capture flag?  We do a lot of webcam stuff and it would be awesome for testing purposes to be able to use this flag.
I would be happy to help, just may need some direction on where the work would need to be done.

I think it is already in our code.

Oh it is?  I just didn't see it here
Is it documented somewhere else?

Not all command line switches are listed in that page, because there are just too much of them (I think there are hundreds).
Electron is reusing Chromium's content module, when a command line switch is implemented in content module, we inherit it for free.


Add songs to favorites/rejects playlist when they get 3? up (or down) votes

https://github.com/labzero/hedwig_mopidy/pull/23


Roll Flutter Engine from 122c3b382012 to 267f2481e1a8 (3 revisions)

https://github.com/flutter/engine/compare/122c3b382012...267f2481e1a8
2023-04-21<EMAIL_ADDRESS>Update xcode to 14c18 (flutter/engine#41370)
2023-04-21<EMAIL_ADDRESS>Revert "[Impeller] Turned on wide gamut support by default." (flutter/engine#41382)
2023-04-21<EMAIL_ADDRESS>Revert "Manual roll skia to d5b4acfb4" (flutter/engine#41381)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC chinmaygarde@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Closing to trigger a roll with a more up-to-date Skia.

Commit queue failed; closing this roll.


Can this PR be pulled into update?

There is a bug in zwave js that fixes an issue with some inovelli light switches. Can this be pulled into this plugin also? https://github.com/zwave-js/node-zwave-js/pull/2167

The addon follows upstream releases.

I'll be releasing 7.0.1 this weekend


Update Compatability Information for 1.19.3 on Modrinth (And curseforge?)

Similar to #1
I was able to use it with 1.19.3 (and the mixing is relatively generic, unless they change method parameters due to signing again)

Done


Creating a middleware for checking if user is authenticated as student or not

In the middlewares > student.middleware.js create a function with arguments: (req, res, next) and export as default export of the file.
Working of the function:
Check if there is an Authorization header present in the request. If there is, its format should be Bearer <token>.
Absence of this header means the request is unauthorized.
Extract the token from the Authorization header and verify this token if it is valid and has not expired yet.
If the token is verified and user role is set as Student set req.isAuthenticated = true otherwise set req.isAuthenticated = false.
The User's details will be available in the payload, you will have to find the user in the database using these details and save it to req.user.
Make sure to pull before starting your work.
For any doubts or difficulty, you can ping me on discord, I'll try to help you out as soon as possible.
All the Best!!

Claim

Assigned to @priyankasharma2823


Automation: No matching clusters msg fix

Summary
Fixes #9683

Occurred changes and/or fixed issues
Technical notes summary

Added tests
Added several fallbacks

Removed conditional chaining in some styling
SortBy() utility if missing argument
filterOnlyKubernetesClusters() if missing mgmt Clusters
Several cases in the sidebar

Changed getter map flavor due issues while mocking method
Added comments to the markup to match to the UI

Areas or cases that should be tested

Areas which could experience regressions

Screenshot/Video

I have no idea why we have searchActive as extra variable given the search term, nor why we filter clusters if no search.
Same why we have 3 clusters when we could just have 1 and sort them, then add a CSS class for the last pinned followed by another cluster.

@cnotv , @scures Can you make sure all PRs have milestones?

@richard-cox the issue had no milestone.


Label extension schema requires label:classes property even when not using categorical data

The Label extension says that the label:classes property is "REQUIRED if using categorical data." and the schema for the extension says that the property is always required. STAC Validator currently fails when validating a label item does not contain that property in the case of non-categorical labels since it's reading the schema file and expecting that all items implementing the label extension must have that property no matter what. Not sure what the best solution here is, maybe just remove label:classes from the required properties in the schema?

Is there a way to determine from the JSON that data is categorical? If yes, we can make it happen that the field is required only for categorical data. Otherwise we'll likely have problems with a proper JSON Schema that models the written docs.

From what I can tell, no. Simply the absence of that property indicates that the data isn't categorical.

Okay, then we should remove the requirement from the JSON Schema. Are you up to make a PR? :-)

Just put it in!

Closed by #905


Update cast to OpeningHoursModel

The cast should be to a OpeningHoursModel sinces the changes of the model.

I think this was because the class was renamed at one point. Thanks for the fix ;)


Are all scripts loaded as root

Hello,
I can use forever-service and thanks for that but I need some server script not to be runned as root but as www-data user. How can I acheive this ?
I've tried to install forever-service as non root user but it does not work, certainly because for creating linux service, we need to be root ...

+100 on this feature.

+1

+100 from me as well.

+1

I have added support for run as user in 0.5.0. (-r user)
NOTE: This is still experimental, I need some volunteers to test this in various environments.
This is functional only for init.d scripts. Upstart script for Ubuntu is not yet supported for runasuser.

@arvind-agarwal I owe you some time, and the least I can do is providing some testing feedback on this nice feature.
I am testing this on Amazon Linux AMI FWIW, and will provide some feedback after a few restarts.
Installing went fine for the first service I'm testing with and it shows up for the ec2-user so all seems to be good so far.

After more testing including some reboots, I can confirm that running with the -r option for the ec2-user on Amazon Linux works completely as expected.

@houmark I am now looking for volunteers from other platforms (Amazon Linux) seems to be working well.

I would rather have forever-service use systemd instead of upstart if that's what it takes to get the -r option to work on Ubuntu.

Ubuntu 14.04 doesn't support systemd and Ubuntu 15.04 doesn't support upstart. It says here that you can switch, which will probably break your system. Does anybody know if you can use them side by side?
I've been playing around with Ubuntu 14.04 and forever-service after reading http://upstart.ubuntu.com/cookbook/#ensure-a-directory-exists-before-starting-a-job and http://upstart.ubuntu.com/cookbook/#run-a-job-as-a-different-user.
So far nothing successful but for Ubuntu 14.04 this should be the way to go:

create the log file, chmod and chown it with the correct user:group and file permissions on pre-start
exec all commands trough the correct user

@arvind-agarwal do you have any tips on how to debug the upstart script?


Tf documentation

@timzaman @gheinrich for review, or should we have a meeting and discuss about this? Thanks

Why does the travis build fail?

numpy updated to v 1.13 and it broke stuff, it's fixed on master. The other is just linting

Make sure to keep the CI happy - even the linter.


After building APK i get INSTALL_PARSE_FAILED_NO_CERTIFICATES error

I built the apk using apktools, and tried to install it, but it resulted in an error! Any ideas how to fix that?

you also need to sign the apk file

you also need to sign the apk file

After signing it says "Targeting R+ requires the resources.arsc of installed APKs to be stored uncompressed and aligned on a 4-byte boundary". I am not great in mobile development, how to fix that?

you may need to zipalign the apk before signing. If you used jarsigner, you should use apksigner instead.

you may need to zipalign the apk before signing. If you used jarsigner, you should use apksigner instead.

Thanks for the quick reply, I'll use apksigner!

you may need to zipalign the apk before signing. If you used jarsigner, you should use apksigner instead.

I managed to do it!!! Thank you


Stop a container in a foolproof way for a virtualized container runtime

I'd like to discuss the way CRI-containerd handles a container stop.
First, let me give some context here. I am working on Kata Containers and I'd like to make sure we integrate properly with higher layers like CRI-containerd and CRI-O. In case of CRI-O, I have discovered few weeks ago that it was unmounting things related to the container after the container was stopped (translating into a kill for OCI), instead of doing this after the delete returned.
Because in case of virtualized containers, we mount and plug things through the VM, relying on the container process to determine if it has been properly stopped is not enough. Indeed, it'd be more foolproof to rely on the container state being returned as 'stopped' to be able to say that things can be properly unmounted.
I have submitted a patch to CRI-O because we were having a real issue with that, which got recently merged here: https://github.com/kubernetes-incubator/cri-o/pull/1334
Now, about CRI-containerd, @jcvenegas and I have taken a look at the code and I can say that we have no problem so far with StopContainer() since it doesn't trigger any unmount, which is great. But let's say that someday someone needs to move the unmount part to the stop/kill stage for performance optimizations reasons, we would end up in the same wrong situation that we were having with CRI-O.
Basically, the code stops the container and then waits for the event handler to receive a TaskExit from containerd-shim, based on the container init process.
I would like to get some feedback about the idea of checking the container state by calling into the runtime to get this info from the runtime itself, instead of relying on the termination of the container process.
This could be a simple function being added to waitContainerStop(). This function calling into "runtime state" in a loop until it gets the appropriate stopped state.
Notice that in case of runc, this would add only one extra call since the container state will be directly switched to stopped by runc.

cc @Random-Liu @mikebrow

@containerd/containerd-maintainers
Here is the problem for katacontainers:

Because in case of virtualized containers, we mount and plug things through the VM, relying on the container process to determine if it has been properly stopped is not enough. Indeed, it'd be more foolproof to rely on the container state being returned as 'stopped' to be able to say that things can be properly unmounted.

And to support it, we have 2 options:
Option 1: Let containerd generate TaskExit event based on container state instead of init process exit.
Option 2: We add logic in cri plugin to check container state after we receive the TaskExit event.
Which is the preferred option? Is there other options?

@sboeuf After thinking about this more, I think this should be handled in cri-containerd. TaskExit event from containerd simply mean the init process exits, it doesn't necessarily implies that the container state is changed.
As for cri-containerd, actually we've already supported your use case today. Let's say we use StopContainer to stop a container:

StopContainer stops the container, and wait for internal container state to transit to "stopped".
events.go receives the TaskExit event, and try to Delete the task.
Delete checks whether the task is in stopped state but returns error, because container state is still running for kata containers.
events.go requeue the event, and will deal with the event again with an exponential backoff. The backoff increases from 1s to 5 min.
When events.go handles the event again, it is able to Delete the task and update internal container state, because the state become stopped.
StopContainer see the internal container state change and return.

If we found the backoff log is too spammy we can improve it. But I think the functionality is in place. :)

@sboeuf Let's close this one, and move the discussion to https://github.com/containerd/cri/issues/687


Firrtl deduplication pass does not work

See the firrtl file at /nscratch/colins/hwacha-broken-dedupe.fir
Arbiter_23 and Arbiter_15
as well as many other things have no difference in their body but have different names. This chains up the hierarchy to break de-duplication throughout the design.

Closed via #375


match StdTypes.Void as well

Sometimes there's StdTypes.Void instead of plain Void in the syntax, which in Haxe 3.3 leads to a compile-time error somewhere in the remoting code.

Thanks!

Ooh you have access to ufront? That's good news!

The problem is, I only have access to ufront-mvc


any document to explain deployment by k8s?

Hi u,
First thank u for the great projict of free5GC。
I have readed carefully on free5gmano/kube5gnfvo,and I have setup a k8s cluster for test,I have deploy the mano in k8s and tested,I can visit the 30888 port to access mano。Is  there a detail document to explain how to deploy 5GC via k8s? I plan to deploy amf、ausf、smf、nrf、pcf、udm、udr、upf，free5gmano/free5gmano tell the docker image，but I don‘t know how the docker image created，and the requirement （such as net and netcard）of  image to run，I think I can deploy this by mano，the example is deploy a nssi，Is there a example to show use mano to deploy amf(or other F)?
Thx。

Hello,
I'm free5gmano member.
You can refer to free5gmano#getting-started and step by step, you can get a free5gc NSSI.
We have build free5gc docker image and uploaded on docker hub.
free5gmano#docker-repository
If you want to build free5gc docker image by yourself. Please refer this link.
free5gmano-docker
If you have any other questions for deploying free5gc on k8s, you can also comment issue on free5gmano or kube5gnfvo.
Thanks.


Add rules for model name and tags

For the model name and tags, we should add some rules such that it display nicely on the website.. For example, the maximum number of letters, character set, the name should be human readable, capitalization of tags etc.

these rules make sense for all RDFs, we should add them in 'general RDF 0.3.0'


Updated code with latest openapi

Codecov Report

Merging #184 into master will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #184      +/-   ##
==========================================
+ Coverage   89.56%   89.58%   +0.01%
==========================================
  Files         113      113
  Lines        2290     2294       +4
  Branches      410      410
==========================================
+ Hits         2051     2055       +4
  Misses        237      237
  Partials        2        2

Impacted Files
Coverage Δ

src/generated/ActionCreators.ts
92.68% <100.00%> (+0.37%)
:arrow_up:


RTN18a

LGTM

It is important to merge #169 first, rebase with master and check if it is ok.

@tcard I run the complete test suite and it's failing with:
RestClient__initializer__should_accept_a_token_UsersricardopereiraRepositoriesWhitesmithablyiosablySpecRestClientswift_48, failed - Got error 'Error Domain=io.ably.cocoa Code=40100 "" UserInfo={ARTErrorStatusCode=401, NSLocalizedDescription=, NSLocalizedFailureReason=invalid credentials}'
/Users/ricardopereira/Repositories/Whitesmith/ably-ios/ablySpec/TestUtilities.swift:215

RestClient__initializer__should_accept_a_token_UsersricardopereiraRepositoriesWhitesmithablyiosablySpecRestClientswift_48, failed - expected to eventually be nil, got <Error Domain=io.ably.cocoa Code=40100 "" UserInfo={ARTErrorStatusCode=401, NSLocalizedDescription=, NSLocalizedFailureReason=invalid credentials}>
/Users/ricardopereira/Repositories/Whitesmith/ably-ios/ablySpec/RestClient.swift:51

The tests were passing when you implemented the initWithToken? Or are they missing the pending?

The tests were passing when you implemented the initWithToken?

On my machine, yes. I run them again against master and it's still happily passing. Weird...


Cross compilation support

Related to #9 and #26 cross compilation with gb should always just work.
Right now it does not and there are a few parts to solving this

The first is is #28 because not only does the toolchain change between go 1.4 and go 1.5, but so does the procedure for creating a cross compilation capable toolchain.

The second is related to the first. Specifically in Go 1.5 we removed the requirement to do the ./make.bash --no-clean dance by letting the go tool rebuild all the way back to runtime if necessary.

For gb, I never intended it to be a tool that would compile the Go standard lib itself, so any package which is considered to be the standard library is assumed to be up to date and never recompiled, with Go 1.5, this won't be sufficient.
Actions needed are at least

icky interaction between gb.gcToolchain and the package selection logic to determine if it needs to rebuild a std lib package
decide on #28
enhancements to gb to build, but not install into the toolchains' $GOROOT, packages.

#37 is a prerequisite of this issue.

Cross compilation is explicitly disabled in d5a861b6f83f06511871144e1759553d4e67e877 and now you get an error telling you why
% env GOOS=darwin gb build ./...
FATAL unable to construct context: cross compilation from host linux/amd64 to target darwin/amd64 not supported. See issue #31


undefined method `each' for #String:0x0000000001df20e0 (NoMethodError)

When processing the first playbook at hands, ansible-viz runs into a No MethodError at some point.
Loading ...
Postprocessing ...
Traceback (most recent call last):
	11: from bin/ansible-viz.rb:17:in `<main>'
	10: from bin/ansible-viz.rb:10:in `main'
	9: from /home/yala/src/github.com/aspiers/ansible-viz/lib/ansible_viz/cli.rb:96:in `graph_from_data'
	8: from /home/yala/src/github.com/aspiers/ansible-viz/lib/ansible_viz/postprocessor.rb:15:in `process'
	7: from /home/yala/src/github.com/aspiers/ansible-viz/lib/ansible_viz/postprocessor.rb:15:in `each'
	6: from /home/yala/src/github.com/aspiers/ansible-viz/lib/ansible_viz/postprocessor.rb:15:in `block in process'
	5: from /home/yala/src/github.com/aspiers/ansible-viz/lib/ansible_viz/postprocessor.rb:26:in `process_role'
	4: from /home/yala/src/github.com/aspiers/ansible-viz/lib/ansible_viz/postprocessor.rb:26:in `each'
	3: from /home/yala/src/github.com/aspiers/ansible-viz/lib/ansible_viz/postprocessor.rb:28:in `block in process_role'
	2: from /home/yala/src/github.com/aspiers/ansible-viz/lib/ansible_viz/postprocessor.rb:28:in `each'
	1: from /home/yala/src/github.com/aspiers/ansible-viz/lib/ansible_viz/postprocessor.rb:28:in `block (2 levels) in process_role'
/home/yala/src/github.com/aspiers/ansible-viz/lib/ansible_viz/postprocessor.rb:36:in `process_vars': undefined method `each' for #<String:0x0000000001056530> (NoMethodError)

How would I debug this further?

I'm running into the same error, I thought it was to do with subdirs, so I sed those in all .yml in root dir but to no avail.
funnily, it ran with the subdirs but it didn't find any relations except for one


Add new UnsafePhysFrame type and use it in Mapper::map_to

Fixes #88
This pull request adds a new UnsafePhysFrame type that wraps a PhysFrame. The type is unsafe to construct and the caller must guarantee that the frame is not mapped already. This type allows to make the map_to and identity_map methods of the Mapper trait safe. This PR also adjust the FrameAllocator to use the new type.
This is a breaking change.

There were no objections in the last months, so I think we can merge this.
bors r+

bors r-


Ionic apps fail with "Error Unable to load app"

I followed the instructions and some issues (switch to Swift 5, update SnapshotHelper) to get this set up.  I was able to run fastlane screenshots and it worked for half of the shots, but failed with a screenshot of "Error Unable to load app" for about half of them.   Looking up this error I found it can happen if multiple instances run concurrently as that can cause contention for the port ionic uses to serve up the web content.
From that, I found that adding concurrent_simulators(false) to my Snapfile (or, I would suspect using the corresponding CLI parameter or option in Fastfile) fixed this issue.
I'm actually not sure if this is an Ionic or Cordova issue, but regardless I hope this helps someone and it may be worth adding to the documentation.

Can you share a screenshot of the error you got? That might enable me to pinpoint the problem a bit.

To be clear, the error is in the ionic or cordova app, not in this plugin per se.  If you don't have any asserts or navigation and are just screenshotting the ionic app's launch page, and you have the default concurrent_simulators=true,  and you have multiple devices, then you will get this error for some screenshots.  I think this is port contention in the ionic app, though I'm a little fuzzy on how that works.  In my case concurrent_simulators(false) in the Snapfile (or equivalent) is a fine fix.  I'm just thinking it may be worth documenting, or at least having in this issue thread for a month from now when I forget ;)

Yeah, that definitely looks like something inside the app is failing - never seen that before. What webview (plugin name and version) is your app using?

This is cordova-plugin-ionic-webview, but an older version.  It looks like I need to update and try concurrent_simulators:true with that.   Will update this issue once I get a chance to do that.


Disable RC4 and prefer server cipher order

Automated message from Dropbox CLA bot
@alex, thanks for the pull request! It looks like you haven't yet signed the Dropbox CLA. Please sign it here.

(CLA signed)

Automated message from Dropbox CLA bot
@alex, thanks for signing the CLA!

Thanks for the PR @alex!  Definitely agree we should turn off RC4.  To what extent have you researched that this is all we need to update in our SSL config?
E.g. https://raymii.org/s/tutorials/Strong_SSL_Security_On_nginx.html suggests ssl_session_cache shared:SSL:10m; in addition to ssl_prefer_server_ciphers on;.

@timabbott ssl_session_cache is an optimization, it configures the serverside cache for SSL sessions (that particularly incantation means to created a shared memory segment named "SSL" which can be up to 10 megabytes); I can enable it if you'd like.

Yeah, that seems worth doing.  Looks like we should also think about:

Enabling OCSP stapling
using a stronger DHE parameter
Both look like they'll involve installing some new cert-related files, so probably we should just stick with just adding that for now.

Applied those changes to my test server and now it's SSL state looks good according to this scanner:
https://www.ssllabs.com/ssltest/analyze.html?d=zulip.tabbott.net
So I think that should suffice for now (we might want to do another pass of removing older ciphers at some point).

I just added an additional commit for the session cache and merged this.  Thanks @alex!


add button for submit

closed with https://github.com/jcstein/multichain-gallery-ankr/commit/908bbb1d990d51db1fa85a932c0081457e87b8f2 🚀


⚠ ClamAV has degraded performance

In e74db9e, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 216 ms

Resolved: ClamAV performance has improved in 510934a.


Don't use images for text docs!

It's super annoying to have textual documentation rendered in image format, e.g.
https://docs.microsoft.com/en-us/azure/genomics/media/quickstart-run-genomics-workflow-portal/genomics-config.png
I went to cut and paste the list of reference genome ids to send to a colleague and found I couldn't but had to retype them instead. That's a waste of time. It also means the information isn't searchable.
Generally the lack of reference documentation for the various API options is very unhelpful. There are bits and pieces scattered throughout, but apparently the only canonical reference is the msgen CLI source repo on Github which isn't even linked here.

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

ID: 8fcb147c-ad94-4926-6cec-da6013c6006a
Version Independent ID: a2a1e627-0b49-4757-51b3-9a1e3ddd432e
Content: Quickstart: Run a workflow through Microsoft Genomics
Content Source: articles/genomics/quickstart-run-genomics-workflow-portal.md
Service: genomics
GitHub Login: @grhuynh
Microsoft Alias: grhuynh

Hello, you can find the list of available reference genomes, searchable and copyable, at the following link, under "What genome references can I use?". In addition, the link also details how you can learn more about all possible commands for the msgen client, under "Where can I find a list of all possible commands and arguments for the msgen client" and "What are the most commonly used commands for the msgen client".
https://docs.microsoft.com/en-us/azure/genomics/frequently-asked-questions-genomics

@tfmorris, we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly reopen the issue and continue the discussion


plugin idea: OpenGTS plugin

create new plugin which adds marker for player positions gathered from an opengts (http://www.opengts.org/) server.

User needs to add own authentication data for the server
User needs to add url for opengts server of his/her group
(both saved to a cookie and read from it at next browser start?)
Marker are shown similar to the player tracker plugin: opponent team is shown from ingress intel data only, but own team from opengts data as well

Suggestion not implemented in 3+ years, can issue be closed?

@nhamer most likely, yes. I don't think this will be needed by anyone after that long time.

Just want to note some alternatives:

Glympse
OwnTracks


[BUG] hyprland-autoname-workspace crashes when new workspace/client name includes character '/'

Describe the bug
When I try to change name of client to include forward slash '/', hyprland-autoname-workspace crashes.
Goal is to add colors dynamically to waybar, something like hyprctl dispatch renameworkspace 6 '6' works.
To Reproduce
Steps to reproduce the behavior:

Add to your config something like: "(?i)Kitty" = '/'
run hyprland-autoname-workspaces
crash

Expected behavior
Rename the client to /, do not crash
Linux Distro (please complete the following information):
Arch
**Program version?
tag 0.4.4, commit 09a64e38ccf0b7ba2a1501faf8794432c9ab97be
Additional context
> RUST_BACKTRACE=full cargo run
    Finished dev [unoptimized + debuginfo] target(s) in 0.08s
     Running `target/debug/hyprland-autoname-workspaces`
thread 'main' panicked at 'App can't rename workspaces on st   0:     0x55d058a6153a - std::backtrace_rs::backtrace::libstack backtrace:
98507f1fe0ce10a2b8dbc/library/std/src/panicking.rs:692:13
unwind::trace::h38953cd7b82c38d3
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/../../backtrace/src/backtrace/libunwind.rs:93:5
   1:     0x55d058a6153a - std::backtrace_rs::backtrace::trace_unsynchronized::h53802a8b087ae509
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
   2:     0x55d058a6153a - std::sys_common::backtrace::_print_fmt::h0806bc2b3dfbb06c
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/sys_common/backtrace.rs:65:5
   3:     0x55d058a6153a - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h6bd42fa772461846
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/sys_common/backtrace.rs:44:22
   4:     0x55d058a828be - core::fmt::write::h086d90dd8e1b1a3f
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/core/src/fmt/mod.rs:1232:17
   5:     0x55d058a5e845 - std::io::Write::write_fmt::h18f12173b1839b43
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/io/mod.rs:1684:15
   6:     0x55d058a61305 - std::sys_common::backtrace::_print::hfeb1e373746d03b6
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/sys_common/backtrace.rs:47:5
   7:     0x55d058a61305 - std::sys_common::backtrace::print::h9dc79345d5a578b2
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/sys_common/backtrace.rs:34:9
   8:     0x55d058a62abf - std::panicking::default_hook::{{closure}}::h45526a9efda640f6
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/panicking.rs:271:22
   9:     0x55d058a627fb - std::panicking::default_hook::h3e08227c1528c168
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/panicking.rs:290:9
  10:     0x55d058a63068 - std::panicking::rust_panic_with_hook::he81c02edd7e7b80e
                               at /rustc/84c898d65adf2f39a5aer::{{closure}}::h98331a6e5528817d
  11:     0x55d058a62f69 - std::panicking::begin_panic_handl  23:     0x55d058a5963c - std::panicking::try::h5074e9976b1                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/panicking.rs:583:13
  12:     0x55d058a619a6 - std::sys_common::backtrace::__rust_end_short_backtrace::h83c0d32dd2d13f12
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/sys_common/backtrace.rs:150:18
  13:     0x55d058a62c72 - rust_begin_unwind
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/panicking.rs:579:5
  14:     0x55d0585c9aa3 - core::panicking::panic_fmt::h9ad38cbb8980e66e
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/core/src/panicking.rs:64:14
  15:     0x55d0585c9f53 - core::result::unwrap_failed::h6787e69082462417
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/core/src/result.rs:1750:5
  16:     0x55d0585f59be - core::result::Result<T,E>::expect::h7a233c435d697425
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/core/src/result.rs:1047:23
  17:     0x55d0586201b9 - hyprland_autoname_workspaces::main::h539590fcc564dce9
                               at /home/psimovec/test/hyprland-autoname-workspaces/src/main.rs:20:5
  18:     0x55d05862228b - core::ops::function::FnOnce::call_once::h839c23dcd80ffa6e
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/core/src/ops/function.rs:250:5
  19:     0x55d05860646e - std::sys_common::backtrace::__rust_begin_short_backtrace::h0def45c3f2f047f3
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/sys_common/backtrace.rs:134:18
  20:     0x55d058608ea1 - std::rt::lang_start::{{closure}}::h5feba351e3d9119c
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/rt.rs:166:18
  21:     0x55d058a5963c - core::ops::function::impls::<impl core::ops::function::FnOnce for &F>::call_once::h814f0ad687ab2f92
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/core/src/ops/function.rs:287:13
  22:     0x55d058a5963c - std::panicking::try::do_call::had9b6a5cabf2fdc8
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/panicking.rs:487:40
                               at /rustc/84c898d65adf2f39a5a3e92c
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/panicking.rs:451:19
  24:     0x55d058a5963c - std::panic::catch_unwind::he1669253985d4352
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/panic.rs:140:14
  25:     0x55d058a5963c - std::rt::lang_start_internal::{{closure}}::hd778e2099ecb758e
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/rt.rs:148:48
  26:     0x55d058a5963c - std::panicking::try::do_call::h1ce263ca927523fa
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/panicking.rs:487:40
  27:     0x55d058a5963c - std::panicking::try::he3d901a7a8ca0bfd
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/panicking.rs:451:19
  28:     0x55d058a5963c - std::panic::catch_unwind::hb9e5b8ae73c93b8f
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/panic.rs:140:14
  29:     0x55d058a5963c - std::rt::lang_start_internal::h2947494479068ade
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/rt.rs:148:20
  30:     0x55d058608e7a - std::rt::lang_start::he46f5779c6465a34
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/rt.rs:165:17
  31:     0x55d0586203be - main
  32:     0x7f1bca3cb790 - <unknown>
  33:     0x7f1bca3cb84a - __libc_start_main
  34:     0x55d0585ca135 - _start
  35:                0x0 - <unknown>```

Are you QA engineer? Thansk 😄

Are you QA engineer? Thanks smile

I used to be QE intern for 2 years :smile:

Can you try to escape the / with \/ ? (didn't try)

I tried that and it didn't work, but I tried it again with full debug and the error message is different - Invalid escape
RUST_BACKTRACE=full cargo run
    Finished dev [unoptimized + debuginfo] target(s) in 0.08s
     Running `target/debug/hyprland-autoname-workspaces`
thread 'main' panicked at 'Unable to read config: "Unable to parse: Error { inner: ErrorInner { kind: InvalidEscape('/'), line: Some(11), col: 16, at: Some(330), message: \"\", key: [] } }"', src/main.rs:16:29
stack backtrace:
   0:     0x5555b961453a - std::backtrace_rs::backtrace::libunwind::trace::h38953cd7b82c38d3
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/../../backtrace/src/backtrace/libunwind.rs:93:5
   1:     0x5555b961453a - std::backtrace_rs::backtrace::tra98507f1fe0ce10a2b8dbc/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
98507f1fe0ce10a2b8dbc/library/std/src/sys_common/backtrace.rs:150:18
   2:     0x5555b961453a - std::sys_common::backtrace::_print_fmt::h0806bc2b3dfbb06c
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/sys_common/backtrace.rs:65:5
   3:     0x5555b961453a - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h6bd42fa772461846
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/sys_common/backtrace.rs:44:22
   4:     0x5555b96358be - core::fmt::write::h086d90dd8e1b1a3f
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/core/src/fmt/mod.rs:1232:17
   5:     0x5555b9611845 - std::io::Write::write_fmt::h18f12173b1839b43
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/io/mod.rs:1684:15
   6:     0x5555b9614305 - std::sys_common::backtrace::_print::hfeb1e373746d03b6
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/sys_common/backtrace.rs:47:5
   7:     0x5555b9614305 - std::sys_common::backtrace::print::h9dc79345d5a578b2
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/sys_common/backtrace.rs:34:9
   8:     0x5555b9615abf - std::panicking::default_hook::{{closure}}::h45526a9efda640f6
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/panicking.rs:271:22
   9:     0x5555b96157fb - std::panicking::default_hook::h3e08227c1528c168
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/panicking.rs:290:9
  10:     0x5555b9616068 - std::panicking::rust_panic_with_hook::he81c02edd7e7b80e
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/panicking.rs:692:13
  11:     0x5555b9615f69 - std::panicking::begin_panic_handler::{{closure}}::h98331a6e5528817d
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/panicking.rs:583:13
  12:     0x5555b96149a6 - std::sys_common::backtrace::__rust_end_short_backtrace::h83c0d32dd2d13f12
                               at /rustc/84c898d65adf2f39a5a  13:     0x5555b9615c72 - rust_begin_unwind
                               at /rustc/84c898d65adf2f39a5a  25:     0x5555b960c63c - std::rt::lang_start_internal::{{closure}}::hd778e2099ecb758e
98507f1fe0ce10a2b8dbc/library/std/src/panicking.rs:579:5
  14:     0x5555b917caa3 - core::panicking::panic_fmt::h9ad38cbb8980e66e
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/core/src/panicking.rs:64:14
  15:     0x5555b917cf53 - core::result::unwrap_failed::h6787e69082462417
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/core/src/result.rs:1750:5
  16:     0x5555b91a8c49 - core::result::Result<T,E>::expect::he04abbcc0b0fdde7
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/core/src/result.rs:1047:23
  17:     0x5555b91d04ea - hyprland_autoname_workspaces::main::h539590fcc564dce9
                               at /home/psimovec/test/hyprland-autoname-workspaces/src/main.rs:16:15
  18:     0x5555b91d528b - core::ops::function::FnOnce::call_once::h839c23dcd80ffa6e
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/core/src/ops/function.rs:250:5
  19:     0x5555b91b946e - std::sys_common::backtrace::__rust_begin_short_backtrace::h0def45c3f2f047f3
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/sys_common/backtrace.rs:134:18
  20:     0x5555b91bbea1 - std::rt::lang_start::{{closure}}::h5feba351e3d9119c
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/rt.rs:166:18
  21:     0x5555b960c63c - core::ops::function::impls::<impl core::ops::function::FnOnce for &F>::call_once::h814f0ad687ab2f92
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/core/src/ops/function.rs:287:13
  22:     0x5555b960c63c - std::panicking::try::do_call::had9b6a5cabf2fdc8
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/panicking.rs:487:40
  23:     0x5555b960c63c - std::panicking::try::h5074e9976b13e92c
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/panicking.rs:451:19
  24:     0x5555b960c63c - std::panic::catch_unwind::he1669253985d4352
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/panic.rs:140:14
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/rt.rs:148:48
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/rt.rs:148:48
  26:     0x5555b960c63c - std::panicking::try::do_call::h1ce263ca927523fa
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/panicking.rs:487:40
  27:     0x5555b960c63c - std::panicking::try::he3d901a7a8ca0bfd
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/panicking.rs:451:19
  28:     0x5555b960c63c - std::panic::catch_unwind::hb9e5b8ae73c93b8f
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/panic.rs:140:14
  29:     0x5555b960c63c - std::rt::lang_start_internal::h2947494479068ade
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/rt.rs:148:20
  30:     0x5555b91bbe7a - std::rt::lang_start::he46f5779c6465a34
                               at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/rt.rs:165:17
  31:     0x5555b91d33be - main
  32:     0x7f551131f790 - <unknown>
  33:     0x7f551131f84a - __libc_start_main
  34:     0x5555b917d135 - _start
  35:                0x0 - <unknown>

Interesting 🤔 I search the good rust regex syntax.

Interesting thinking I search the good rust regex syntax.

I found somewhere that '/' is just a normal character in Rust regex, so it doesn't need to be escaped. So I guess the question is why it crashes for not escaped '/'

Yeah I read the same, in the same time, why are we regexing here. Do you confirm you well want '/' as "instead" of an icon for example here?

What about "(?i)Kitty" = "/" ?

Yeah I read the same, in the same time, why are we regexing here. Do you confirm you well want '/' as "instead" of an icon for example here?

Yes, I want something in style
"[Ff]irefox" = '  '

Is this working for this case ? "[Ff]irefox" = " " ?

What about "(?i)Kitty" = "/" ?

tried that already, the error looks the same for me
thread 'main' panicked at 'App can't rename workspaces on start: NotOkDispatch("unknown request")', src/main.rs:22:10

NotOkDispatch

No this looks like a valid toml syntax now but maybe another bug in the hyrland-rs lib. I will dig more.

Is this working for this case ? "[Ff]irefox" = " " ? (I'm not yet toml expert)

Unfortunately it does not work.
I didn't notice any toml yet before seeing this project :D
Just in case, I have tried to rename hyprctl dispatch renameworkspace 6 '/', the workspace disappears from the waybar, but the hyprctl workspace is correctly renamed.
workspace ID 6 (/) on monitor eDP-1:
	windows: 1
	hasfullscreen: 0
	lastwindow: 0x562825962c70
	lastwindowtitle: psimovec@bramborka:~

just to keep in mind when debugging

@psimovec for now if you like we can do this tricks https://github.com/cyrinux/hyprland-autoname-workspaces/pull/42

@psimovec for now if you like we can do this tricks https://github.com/cyrinux/hyprland-autoname-workspaces/pull/42 to prevent the crash and draw a kindof slash. But we can't use  for the moment so. This is maybe a hyprland-rs issue but I can't put the finger on for the moment.
@yavko do you have an idea an idea about the problem ? We try to be able to use hyprland-rs rename dispatcher to pass some special char like / at least, and maybe <>.

I just need to clarify that <> characters work as expected.

Super @maximbaz come to the help

@psimovec You will also like to fix your waybar, see here https://aur.archlinux.org/packages/waybar-hyprland-git#comment-912717

@yavko do you have an idea an idea about the problem ? We try to be able to use hyprland-rs rename dispatcher to pass some special char like / at least, and maybe <>.

No clue, hyprland-rs doesn't do anything with slashes afaik

Fixed in https://github.com/hyprland-community/hyprland-autoname-workspaces/releases/tag/0.5.1


Fix revert evaluation order test name

What ❔
Running evm semantic tests with
cargo run --verbose --release --bin compiler-tester -- --path solidity/test/libsolidity/semanticTests/ --target evm --mode 'Y+ 0.8.26'

would yield an invalid test with the message
INVALID solidity/test/libsolidity/semanticTests/errors/require_evaluation_order.sol No such file or directory (os error 2)

This fixes that by fixing the name of the test file to be the correct one. Looking into it, it seems to be this test, which in the solidity original repo is this one.
With this change the tests no longer give the INVALID message and they pass
Why ❔

Checklist

[ ] PR title corresponds to the body of PR.
[ ] Tests for the changes have been added / updated.
[ ] Documentation comments have been added / updated.
[ ] Code has been formatted via cargo fmt and checked with cargo clippy.

Hey @jrchatruc, thanks for pointing this out.
I've probably not updated the index for upstream Solidity tests, but only updated the submodule where they renamed the test you mentioned.
They added more tests than just that. Need to call cargo run --verbose --release --bin tests-updater -- --index-only .... I will do that.


[CNVS Upgrade: Stylelint 3 of 3] Add stylelint npm script

Depends on #1092.
This PR separates the lint script into two separate scripts; an eslint script and stylelint script, so that both JS and LESS lint warnings will fail the build script.

For only adding 2 new npm dependencies our Shrinkwrap has inflated ~6k. I think something is awry

I noticed the many dependencies. Unfortunately there is no way of excluding them for the style linter. It is all or nothing. Meaning that it includes e.g. both postcss support and the lodash library :(
Not sure what we can do about it


Apps: move configuration into the full screen visualization view

Move app configuration into the fullscreen viz as shown below.
Notes:

The intent is to have app parameters look just like viz parameters, but be on their own line with the heading "{app display name} paramters". Please excuse my rushed attempt at making the mesa select button :)
For the foreseeable future, all app parameters are required for the visualizations (unlike strata

please note those buttons in the screenshot are my lazy attempt at remaking the standard mesa buttons that we currently use for visualization variable selections

Closing and assigning to dan for QA


Use keystone-manage to bootstrap a cloud

This obviates the need for admin_token usage, which we've never liked. It also removes a keystone service restart when doing the boot strapping. Everything is nice and idemotent.
This cherry picks (with modifications) a few commits that were used to implement this from another dev team.

LGTM :+1:


Update your-name.txt

I'm playing with this to get an idea of how to work with GitHub.

Welcome to Github! Glad I could help.


Add pre-stable support for create on Windows

Description
Adds initial support for flutter create of apps and plugins. This is derived from the current FDE example app and sample plugin, adding template values where relevant.
Since the APIs/tooling/template aren't stable yet, the app template includes a version marker, which will be updated each time there's a breaking change. The build now checks that the template version matches the version known by that version of the tool, and gives a specific error message when there's a mismatch, which improves over the current breaking change experience of hitting whatever build failure the breaking change causes and having to figure out that the problem is that the runner is out of date. It also adds a warning to the create output about the fact that it won't be stable.
Plugins don't currently have a version marker since in practice this is not a significant problem for plugins yet the way it is for runners; we can add it later if that changes.
Related Issues
#30704
Tests
I added the following tests:

Checks that the app and plugin templates include windows when requested, and don't when not requested.
Error message tests for mismatches of template version.

Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[x] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change.

I still need to do the manual tests on this one, but it should be good to review as-is.

The non UTF files need an exception added in dev/bots/test.dart . This is mostly to prevent us from accidentally adding large binaries or images, should be okay for templates

The non UTF files need an exception added in dev/bots/test.dart .

Added an exception for the .ico. It looks like the rc file can be UTF-8 in VS 2019, so I've pushed a version with that. I need to double-check when I'm at my Windows machine though since it sounds like the exact behavior changed during the development of VS 2019 so I'm not 100% sure it will preserve UTF-8 on edit+save, and if it doesn't I'll switch it back to UTF-16.

I'm not 100% sure it will preserve UTF-8 on edit+save

Tested adding a resource via VS 2019 and it still saved out in UTF-8, so it looks like that's fine to change!

Added an exception for the .ico.

Turns out I was looking at the wrong check.
@Hixie, the code I would actually need to change to allow adding the icon for this new template has multiple comments saying not to change it, but don't point to any suggestions about what to do instead and only say to talk to you.

What is the right way to have an icon in a new template now?
Can we have a more scalable solution in the documentation than "talk to one specific person who might not be in the office when you encounter this problem"?

@jonahwilliams PTAL; this now includes the new code to use flutter_template_images. Requires https://github.com/flutter/packages/pull/118 to land and be published before it'll work, but it can be reviewed in parallel.
Unit test coverage of template.dart is currently poor, but I did add a new unit test for the new functionality. I also de-global.fs'd it in support of that test.

flutter_template_images has been published; this now works end to end.

Can you do me a favour and add a comment to the place that verifies that there's no binaries saying that if anyone wants to add or change images in the templates, they should do it via your package and pointing to the logic for how to do it?
Thanks for setting this logic up, this is great. I'm glad we have a real solution for avoiding images in the templates now.

Can you do me a favour and add a comment to the place that verifies that there's no binaries saying that if anyone wants to add or change images in the templates, they should do it via your package and pointing to the logic for how to do it?

Done. I meant to do that once I had something working, thanks for the reminder.

For reasons I don't understand adding a new dependency made me run update-packages --force-upgrade, which made a ton of changes, but none of them related to the package that I added. Is that normal?

For reasons I don't understand adding a new dependency made me run update-packages --force-upgrade, which made a ton of changes, but none of them related to the package that I added. Is that normal?

This is normal. When you add a dependency, we have to recalculate the full dependency chart so that we can make sure all the packages in the repo use the same versions of each package.

(ideally we'd have a bot that does this daily so it would never be a lot of changes at once)


[Request]:

Prerequisites

[X] I have searched all issues/PRs to ensure it has not already been reported or fixed.

Criteria

[X] Reasonably well-known and widely used (e.g. if it's a GitHub project, it should have at least 100 stars and/or 50 forks)
[X] English interface (or at least English documentation)
[X] Latest stable version
[X] Full version (i.e. not a trial version)
[X] Fairly standard install (e.g. uses a version-specific download URL, no elaborate pre/post install scripts)

Name
RimSort
Description
A mod manager and updater for RimWorld.
Homepage
https://github.com/RimSort/RimSort
Download Link(s)
https://github.com/RimSort/RimSort/releases/tag/v1.0.8
Some Indication of Popularity/Repute
Hello, making a request for RimSort to be added to scoop extras.
It is a mod manager for a game named RimWorld. It does fulfill the requirements of the bucket (i.e. over 200 stars).
{
    "version": "1.0.8",
    "description": "Mod manager for RimWorld",
    "homepage": "https://github.com/RimSort/RimSort",
    "license": "GPL-3.0-or-later",
    "architecture": {
        "64bit": {
            "url": "https://github.com/RimSort/RimSort/releases/download/v1.0.8/RimSort-v1.0.8-Windows_x86_64.zip",
            "hash": "935c021bcc26f5156a8f6d69a6e95de7c9bc463e788d337887b85792202659f2"
        },
        "32bit": {
            "url": "https://github.com/RimSort/RimSort/releases/download/v1.0.8/RimSort-v1.0.8-Windows_x86_64.zip",
            "hash": "935c021bcc26f5156a8f6d69a6e95de7c9bc463e788d337887b85792202659f2"
        }
    },
    "shortcuts": [
        [
            "RimSort/RimSort.exe",
            "RimSort"
        ]
    ],
    "persist": [
        "User Files"
    ],
    "checkver": {
        "github": "https://github.com/RimSort/RimSort"
    },
    "autoupdate": {
        "url": "https://github.com/RimSort/RimSort/releases/download/v$version/RimSort-v$version-Windows_x86_64.zip"
    }
}

I made this by reading the wiki on scoop. It may contain errors that need polishing.
For example:
Currently it is not following the usual scoop installation protocol where you have a version then the installation folder proper. To better explain, it installs the app as:
Scoop/Apps/RimSort/1.0.8/RimSort/RimSort.exe
Instead of
Scoop/Apps/RimSort/1.0.8/RimSort.exe
The releases themselves on the rimsort page are actually portable installations.
On the other hand, scoop rm RimSort won't do a complete cleanup since the userfiles and config from RimSort are installed in AppData/Local/ which is desirable so RimSort user setting persist but may be annoying from Scoop perspective. So I created a persist but I don't know if on the scoop side it can be used or I have to make a request at the rimsort side.
Can you recommend me a bucket where I can make a request for help putting together a pre-release version manifest? They are very active so I find it useful and desirable.

The above snippet is tested working on my scoop installation.

Belongs to the games bucket.


Feature Support join hint.

Proposed changes
Support join hint for nereids planner.  Hints for broadcast and shuffle are supported by this PR.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[ ] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[ ] No

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

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 34.4 seconds
load time: 441 seconds
storage size:<PHONE_NUMBER>2 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20221115113631_clickbench_pr_46389.html


[Bug] Topic "peek" (admin/v2/persistent/{tenant}/{namespace}/{topic}/ledger/{ledgerId}/entry/{entryId}) management API returns undocumented and inconsistent data when batch messages are accessed

Search before asking

[X] I searched in the issues and found nothing similar.

Version
2.10.3
Minimal reproduce step

Produce a message containing a bytes-schema payload abc123 to a persistent topic with a non-batched (batchingEnabled=false) producer.
Retrieve that message from the topic using the v2 admin API's GET admin/v2/persistent/{tenant}/{namespace}/{topic}/ledger/{ledgerId}/entry/{entryId} functionality.
Observe that the returned payload exactly matches the string abc123.
Produce the exact same message with batchingEnabled=true.
Repeat step 2.
Observe that the returned payload no longer matches abc123.

What did you expect to see?
Something I can use to extract individual messages from a batch. That could include any of the below ideas, or something totally different:

(Easiest) documentation on how to parse a batch of messages client-side such that I can extract an individual message. I checked PulsarApi.proto against the batch data and nothing added up, so I suspect this is something internal, but may be wrong.
A change to the API to support a parameter indicating batch message index, such that only messages with that index would be returned.
Variable length HTTP headers indicating where each message content lies (offset and length) within the returned batch blob.
A change to the API to return multipart HTTP responses, one per batch message.

What did you see instead?
An undocumented blob of binary (I think this is a raw chunk of message data from the ledger) that looks like it contains some info re: properties/etc. up front, and then concatenated message+metadata entries for each message in the batch.
Anything else?
Many of my proposed fixes break backwards compatibility, so this may be better suited as a feature request.
However, in the short term, I'd love to find a  reference on how to extract individual messages from the batch in a non-Java environment. I control all my admin API accesses in my environment, so I can add parsing logic to those wrappers--I just need to know how to parse the data.
Are you willing to submit a PR?

[X] I'm willing to submit a PR!

You're right. This API was introduced in https://github.com/apache/pulsar/pull/6331, at that moment the Pulsar community is not as active as it is currently, no PIP and discussion was required for such a new API. This API is really bad designed.

I just need to know how to parse the data.

Unfortunately, it needs much code work. We need to implement the same logic with https://github.com/apache/pulsar/blob/4678c36d4023a2bb8361e0a70673b96de33f06ac/pulsar-client-admin/src/main/java/org/apache/pulsar/client/admin/internal/TopicsImpl.java#L1237
and
https://github.com/apache/pulsar/blob/4678c36d4023a2bb8361e0a70673b96de33f06ac/pulsar-client-admin/src/main/java/org/apache/pulsar/client/admin/internal/TopicsImpl.java#L1424-L1425
In the short term, I suggest creating a reader and seek to a specific position that is specified by (ledger id, entry id, batch index) instead of depending on this admin API if you're using non-Java clients.


Django 1.10 support release ?

Hi !
Thanks for this project !
Is there any release planned soon to enable support for Django 1.10 ? (Not necessarily the 3.0 release, just a release including 56f4e912cd9a which prevent to use Django 1.10)

Hello @noirbizarre
I didn't plan it, but could be made, you point me the right commit so...
I think 3.0 will be here very soon,
Just need some check.
Can't you wait for it ?

Hi @ZuluPro !
Thanks for responding so fast :+1:
Yes I can wait if release 3.0 is coming, it's fine to me !

Hello @noirbizarre ,
DBBackup v3.0.0 is here !

Thanks @ZuluPro !!!
I'm going to instal and test it right now !!


New Device: Taloya Ceiling Light

An LED ceiling light with a changeable RGB back ring
https://www.amazon.com/gp/product/B08L11JN8Y/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1
{
"type": "RGBTWLight",
"name": "Ceiling Light",
"id": "eb5bd06216ca6e6dbfyugg",
"key": "68f5f20653a91e56",
"manufacturer": "Taloya",
"dpPower": 20,
"dpBrightness": 22,
"dpColorTemperature": 23,
"minWhiteColor": 0,
"maxWhiteColor": 1000,
"dpMode": 21,
"dpColor": 24,
"colorFunction": "HSB",
"scaleBrightness": 1000,
"scaleWhiteColor": 1000
}
Everything Works

DUDE!! Yes! I just spent an hour on the Tuya IoT platform sending commands trying to figure it out, getting frustrated and here is this amazing post! THANK YOU! This is awesome.

I was able to set this up using the above config. The instructions for getting the device ID and key are outdated and not working. I followed this guid: https://github.com/iRayanKhan/homebridge-tuya/wiki/Get-Local-Keys-for-Your-Devices
They've changed a few things in the tuya web platform but it was easy enough to follow.


[DNM][WIP] Implement Windows toolchain

Hello everyone, I'm back!
Sorry for absence for the past months. Now, WindowsToolchain has been:

[x] Updated according to the latest layout;
[x] Tested on real Windows machines.

The following commands are currently supported and tested:

[x] swiftc
[ ] swift
[ ] SwiftPM (swift-build, swift-run, swift-test and any new ones to come)
[ ] REPL (swift-repl)
[ ] make-options

Some other things to do:

[ ] Prove compatibility with various linkers;
[ ] Prove support for statical linking;
[ ] Fix unit tests for the toolchain;
[ ] Fix compatibility with non-Unicode encoding (eg. GB2312);
[ ] Fit into swift-build pipeline;
[x] Fix building swift-driver with SwiftPM on Windows (SR-14259);
[ ] Test cross-compilation with Android and Linux;
[x] Try to implement commandLineFitsWithinSystemLimits and tokenizeResponseFile for Windows.

Hopefully landing by Swift 5.5 :)

Opening apple/swift-tools-support-core#191 to solve some bugs of TSC on Windows. Some tests will function correctly after that patch.

@stevapple really awesome to see this coming along!
Could you please re-base this PR so that it is a bit easier to look at the specific changes?

CC @artemcm

@stevapple this is now quite stale with respect to a lot of recent work in this area by @compnerd.
If you'd like to further contribute with the Windows toolchain bringup, please take a look at the progress done since this PR.


Need replace angle-bracket form to quoted form for #includes with relative paths

It is common practice for libraries. It provides an easy way to place the library as a folder to the source of own project, modify to suit your needs and it will not conflict with library in a common includes folder

I agree with this. The whole #include <Box2D/XXX/YYY/ZZZ.h> is quite odd actually: we usually see #include "ZZZ.h" within the same project, and when including from other projects we'd call #include <Box2D/ZZZ.h>. But it's a choice the dev made, and it works. And I've seen worse.

https://github.com/erincatto/Box2D/commit/71a6079b5fa717b8b56aad6a1130b74232989183