Failed Install Debian 8

I've been trying to install jupyter-rs-vtk and -radia on debian 8 under python 3.7.  I gathered that vtk was a prerequisite, and it looks like nodejs (npm) as well?
I've tried this using nodejs 13.0.1 and 13.6.0.  When I attempt
pip install . --user
the install proceeds without issue (but of course it's not usable without the extensions enabled).  However if I do this using sudo I get the error message copied below.
Is there some config step or package I may be missing on this?
Best Regards
Processing /root/jupyter-rs-vtk
ERROR: Command errored out with exit status 1:
command: /opt/apps/python/3.7.3/bin/python -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-req-build-_8kbxun0/setup.py'"'"'; file='"'"'/tmp/pip-req-build-_8kbxun0/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' egg_info --egg-base /tmp/pip-req-build-_8kbxun0/pip-egg-info
cwd: /tmp/pip-req-build-_8kbxun0/
Complete output (41 lines):
setup.py entered
$PATH=/opt/apps/nodejs/13.6.0/bin:/opt/apps/gcc-7_4/openssl/1.1.1c/bin:/opt/apps/gcc/7.4/bin:/opt/apps/python/3.7.3/bin:/root/.local/3.7.3/bin:/opt/apps/slurm/19.05.0/bin:/opt/apps/slurm/19.05.0/sbin:/opt/conda/condabin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/lpp/mmfs/bin
running egg_info
running jsdeps
6.13.4
6.13.4
Installing build dependencies with npm.  This may take a while...
npm WARN prepublish-on-install As of npm@5, prepublish scripts are deprecated.
npm WARN prepublish-on-install Use prepare for build steps and prepublishOnly for upload-only.
npm WARN prepublish-on-install See the deprecation note in npm help scripts for more information.
npm WARN lifecycle<EMAIL_ADDRESS>cannot run in wd<EMAIL_ADDRESS>webpack (wd=/tmp/pip-req-build-_8kbxun0/js)
npm WARN<EMAIL_ADDRESS>No license field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
audited 3494 packages in 2.107s
found 1 low severity vulnerability
  run `npm audit fix` to fix them, or `npm audit` for details
rebuilding js and css failed
missing files: ['/tmp/pip-req-build-_8kbxun0/jupyter_rs_vtk/static/extension.js', '/tmp/pip-req-build-_8kbxun0/jupyter_rs_vtk/static/index.js']
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/tmp/pip-req-build-_8kbxun0/setup.py", line 181, in <module>
    setup(**setup_args)
  File "/opt/apps/python/3.7.3/lib/python3.7/site-packages/setuptools/__init__.py", line 145, in setup
    return distutils.core.setup(**attrs)
  File "/opt/apps/python/3.7.3/lib/python3.7/distutils/core.py", line 148, in setup
    dist.run_commands()
  File "/opt/apps/python/3.7.3/lib/python3.7/distutils/dist.py", line 966, in run_commands
    self.run_command(cmd)
  File "/opt/apps/python/3.7.3/lib/python3.7/distutils/dist.py", line 985, in run_command
    cmd_obj.run()
  File "/tmp/pip-req-build-_8kbxun0/setup.py", line 45, in run
    raise e
  File "/tmp/pip-req-build-_8kbxun0/setup.py", line 38, in run
    self.distribution.run_command('jsdeps')
  File "/opt/apps/python/3.7.3/lib/python3.7/distutils/dist.py", line 985, in run_command
    cmd_obj.run()
  File "/tmp/pip-req-build-_8kbxun0/setup.py", line 118, in run
    raise ValueError(msg)
ValueError: Missing file: /tmp/pip-req-build-_8kbxun0/jupyter_rs_vtk/static/extension.js
----------------------------------------

ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.

Did something change on jupyter.radiasoft.org?  I am now getting the following error.  I would like to get back to trying to get this up on debian8, but haven't looked at it for a while..
import ipywidgets
import radia as rad
import numpy as np
import time
import matplotlib.pyplot as plt
import ipywidgets
from jupyter_rs_radia import radia_viewer
define radia viewer
rv = radia_viewer.RadiaViewer()
from jupyter_rs_radia import radia_viewer

define radia viewer
rv = radia_viewer.RadiaViewer()
FileNotFoundError                         Traceback (most recent call last)
 in
2
3 # define radia viewer
----> 4 rv = radia_viewer.RadiaViewer()
~/.pyenv/versions/py3/lib/python3.7/site-packages/jupyter_rs_radia/radia_viewer.py in init(self, mgr)
217         #TODO(mvk): build view from this schema
218         self.schema = PKDict(json.JSONDecoder().decode(
--> 219             resources.read_text(rsjson, 'schema.json')
220         ))
221
~/.pyenv/versions/3.7.2/lib/python3.7/importlib/resources.py in read_text(package, resource, encoding, errors)
167     resource = _normalize_path(resource)
168     package = _get_package(package)
--> 169     with open_text(package, resource, encoding, errors) as fp:
170         return fp.read()
171
~/.pyenv/versions/3.7.2/lib/python3.7/importlib/resources.py in open_text(package, resource, encoding, errors)
123     reader = _get_resource_reader(package)
124     if reader is not None:
--> 125         return TextIOWrapper(reader.open_resource(resource), encoding, errors)
126     _check_location(package)
127     absolute_package_path = os.path.abspath(package.spec.origin)
~/.pyenv/versions/3.7.2/lib/python3.7/importlib/_bootstrap_external.py in open_resource(self, resource)
FileNotFoundError: [Errno 2] No such file or directory: '/home/vagrant/.pyenv/versions/py3/lib/python3.7/site-packages/jupyter_rs_radia/json/schema.json'

@dhidas https://github.com/radiasoft/jupyter-rs-radia/issues/34 is fixed in master and in beta right now. Maybe do a pull and a rebuild?

@robnagler The above was on jupyter.radiasoft.org I think in the default config that was available.

Ah yes, I was confused by the issue title. Production release happening now, see #84. You will need to restart your Jupyter server when it is done.

fixed


OnChange element can't catch element?

I'm trying to do something like this
const onChange(image, e)=>
{
 //"e" is undefined;
}

<ImageUploading defaultValue={[{dataURL:Image}]} onChange={(e)=>onChange(e)} multiple={false} />

Any thoughts? why I can't get the element ? to do something like e.target.?

Hi @TRUEND why you need event attribute? Do you want to catch new selected images?

I needed to catch attributes data-* , but I figured it out in another way, I put the event on the buttons to upload new image and everything worked just fine. but it'd be nicer if I had event. thanks for you help, and really good job on this package 👍 .


feat: add list version

:tada: This PR is included in version 2.19.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


minSdkVersion 15 => 14

Hey, it's me again.
I didn't scan through the code but is there a reason for targetting sdk version 15 instead of 14? Both are ICS. Taking a quick look at the release notes I didn't see a difference in APIs.
I was targeting minSdkVersion 14 in my project. When I switch to msa-auth (0.8.2) I can't compile anymore. It's complaining that I can't have minSdkVersion 14 because msa-auth has 15. Although the difference is small I'd rather like not to raise my minSdkVersion.
Could you check if there's troublesome code that won't work on 14 and:

if yes, outline that code (so I can file a PR)
if no, lower the requirement?

I started using the auth-part from the android picker example before it switched to msa-auth. I was using it on API level 14 without issues.

@black-snow I'm comfortable with accepting a pull request that changes the gradle build files to support API14.  The versioning target of this library was arbitrary.

Alright. Tomorrow I'll check if there are any incompatibilities and then file a PR.

PR filed here: https://github.com/MSOpenTech/msa-auth-for-android/pull/16


change react to be peer dependency, resolves #33

@mridgway  Changing this ahead the refactoring PR so that people not migrating to the new package can still benefit.

CLA is valid!

Changes Unknown when pulling a73906119cb8b0202dfc3b6e969eef37c1c57437 on peer into ** on master**.

We'll probably need to add this to devDependencies so it will install for tests.

Changes Unknown when pulling cf80d36d13ccc08e30ef33da189817e41b7579b3 on peer into ** on master**.

:shipit:


fromevent.js causes frame rate drop

https://github.com/cyclejs/cycle-dom/blob/master/src/fromevent.js#L37 causes a massive drop in frame rate in the time the script is running (on a fairly decent desktop 7-26 FPS).
Imagine an app, e.g., a game, that requires the user to click a lot on different items; this will cause the whole experience to slow down.

I’ll try to see if I can fix this.

Is it because of event listener detachment/reattachment? If so, then we're talking about issue #11

I don’t know yet. I have only looked at the call stack and it’s a lot of Rx.

Okay, so one place that affects this is when actions from intent() that use DOM.select(selector).events(event) are combined with props$ in model(). The event listeners are created multiple of the Observables combined.

Also, if the DOM element changes signature, e.g., an added class, the event listeners are removed and re-attached.

Sounds like #11.

We can also consider doing event delegation like in React but I'm not excited to have a custom event system above the DOM.

Neither am I, but I am less interested in performance degradation.

However, it might actually prove to increase performance by creating event delegation like React.

First let's attempt #11 and then see how bearable performance is.

Agreed.


Tracker: Project Module Refactor

Target Use case

project module is the heart of deck.gl
currently quite complicated
internal assumptions not clearly documented
very hard to change

Proposed Feature

[ ] Collect current known limitations and issues with project module
[ ] Define how a projectV2 module should work, including changes to interpretation of various coordinate system modes if needed.

Limitations

[ ] World pixel scale in shaders variable
[ ] Hard to match external sources (e.g. lights) to internal shader coords.
[ ] Pixels in COORDINATE_SYSTEM.IDENTITY: #2824
[ ] Fix application of model matrices to vertices in e.g. hexagon layer in lnglat mode.
[ ] Support rotation model matrices in LNGLAT Mode, based on coordinate origin?
...

To Do List

[ ] Add label and assign to milestone
[ ] Coding
[ ] Doc update
[ ] What’s new update
[ ] Test

Related enough to #2151 to consolidate?

Closing this as work in favor of project system refactor work done in 8.0 milestone covered by #3831


Update README.md: .Net version + example code

The default LoginAsync method doesn't work for me. I get a permissions error with Trackmania date=2024-03-18_16_00 git=126882-1ec72453936 GameVersion=3.3.0
This updates the readme example to use a more verbose connect/auth flow but it works for me (and evo csharp controller does things in this order too)
Unhandled exception. GbxRemoteNet.Exceptions.XmlRpcFaultException: (-1000) Permission denied.
   at GbxRemoteNet.GbxRemoteClient.CallOrFaultAsync(String method, Object[] args)
   at GbxRemoteNet.GbxRemoteClient.SetApiVersionAsync(String version)
   at GbxRemoteNet.GbxRemoteClient.LoginAsync(String login, String password)

It is correct that the readme uses LoginAsync, the AuthenticateAsync is a direct XMLRPC method and only really used for more custom implementations. If LoginAsync doesn't work, it is a bug.


Chapter01 fails

get "ConfigureServices returning an System.IServiceProvider isn't supported." exception error on Chapter01 !
These URLs shows breaking changes in .NET CORE v3.x
https://autofaccn.readthedocs.io/en/latest/integration/aspnetcore.html#asp-net-core-3-0-and-generic-hosting
https://stackoverflow.com/questions/58133507/configureservices-returning-a-system-iserviceprovider-isnt-supported
ASP.NET CORE 3.0 was released 2019-09-23 as per https://devblogs.microsoft.com/dotnet/announcing-net-core-3-0/
but this Packt title was released 2020-06, so it is obvious that the download code was not tested in interim 9 months or  immediately prior to book release as one might expect for a professional process. Why no checks by the reviewers or the Packt publisher ?
Do the subsequent chapters have the same blight (in which case the whole book is doomed) or is this just an unfortunate bloopa trying to show that other DI frameworks (Autofac in this case) could be used ?
Unimpressed alas !

Hi. This chapter was written almost two years ago. Yes, this change in 3.1 went unnoticed, both to me and the tech reviewers. I do think that the rest of the code does not suffer from this kind of problems. Thanks for your contribution.


Fixed a bug in getTextureCoordinates()

Here is a example of the fix: http://www.babylonjs-playground.com/#9U086#1
Without it: http://www.babylonjs-playground.com/#9U086#2

Checked with a Box and A Sphere as well. Merging.


closes #32, Support Kafka as an audit log

Coverage remained the same at 89.485% when pulling 58f5b35fa32ffb0b436347476d10341e6200ad6d on 32 into cc57d97be07d59756c47804910beda5e09ef740e on master.

Coverage remained the same at 89.485% when pulling fe7c3c4fafc845e23f4ca0dba8b1ed9abf333dc6 on 32 into cc57d97be07d59756c47804910beda5e09ef740e on master.


xRegistry: Unable to create binary registry value with data '0x00'

Description
I want to create binary registry value with data '0x00', but xRegistry resource set none value.
Detail
I want to create binary reg value with data zero

For that, write and exec psdsc configuration like...
xRegistry Zero_RegBinary
{
    Ensure = "Present"
    Key = "HKEY_LOCAL_MACHINE\SYSTEM\Tests"
    ValueName = "TestValue"
    ValueData = "0x00"    # same result if you set ValueData="0",
    ValueType = "Binary"
}

Then, sadly, xRegistry resource create a reg value that has 'zero-length binary value'

I confirmed the issue also have the In-box Regisrtry resource in Windows 10 1607.
How to fix
I've discovered the issue caused by this code.
$val = $Data[0].TrimStart('0x')

Apparently the code is intended to remove the first '0x' of $Data[0].
but if $Data[0] = '0' or '0x00', empty value is set in $val.
Perhaps this is undesired behavior.
I would like to propose to modify the code like...
if($Data[0].StartsWith('0x')) {
   $val = $Data[0].Substring(2)
}
else {
   $val = $Data[0]
}

It's a little redundant, but I think it is easy to understand and behave properly.

Hey @Amedama96, well done with finding this. I don't think the issue is as simple as taking a sub string of the string value. A value with '0x' as a prefix means that the value is a Hexadecimal value (0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D, E, F), so if the value contained any hexadecimal letters, [Int]::TryParse('F') would fail, and you would be in the same situation. The only way I know of getting round this is to use [System.Convert]::ToInt32() and specifying the base.
Binary is Base 2, Integer (denary) is base 10, and Hexadecimal is base 16, so to convert a value of '0xF' to a base 10 integer you would use:
[System.Convert]::ToInt32('0xF', 16)
This will give you the true value of the integer! Hope this helps, let me know if you need any more help.
Liam

Hey @Amedama96, well done for finding this. After a little investigation, I found the real issue is that you can't assign a RegistryKey from a hexadecimal value. [System.Int32]::TryParse requires a string representation of an integer value. "0x00" is a string representation of a hexadecimal value. Fixing the parsing to allow for hexadecimal values would fix your problem. I've commented on the PR on how to fix this. Let me know if you need any help.

This issue fixed and merged #299 by @kwirkykat


Bug: Talent Factor is incorrectly spelt

Describe the bug
Title
Steps to reproduce
Creative > Umapyoi tab > Wishes > Talent 5th from last
Expected behavior

Screenshots

Versions

OS:  WIN10
Launcher:  Modrinth/Forge
Java version:  17.0.9 64b
Minecraft version:  1.20.1
Umapyoi version:  1.4.23

Additional context
No response

BUG FIXED IN 1.4.25-1.20.1


Remove open-targets-staging project

There is a GCP project open-targets-staging that is no longer needed in the updated platform infrastructure. This should be confirmed and then removed.

Assigning to @mkarmona because I have insufficient permissions


Define policy for which header name constants to include

We include many standard header names as constants in http::header. The exact criteria has not been defined, and it would be wise to do so. This stops it from being an unwritten rule in a few people's heads. The policy likely should consider the pros of adding any name versus the costs of adding a name.

Thanks for listing those, it may be worth considering quicker if we should chop out some of the obscure ones that are currently in the crate before 1.0 (which is coming soon!).

A good place to start is the IANA Field Name Registry. The registry itself is here, and the specification of the registry is here in RFC 9110.
In this gist I compared the names in the registry vs the names defined as constants in http. There are quite a few more in the registry than we currently have as constants. I'm in favor of including any registry headers that aren't provisional as constants in this crate, as they are very unlikely to ever go away.
There are three sets that I think are more debatable.
provisional headers in the IANA registry
amp-cache-transform
configuration-context
ediint-features
isolation
repeatability-client-id
repeatability-first-sent
repeatability-request-id
repeatability-result
sec-gpc
timing-allow-origin

I'm inclined to not proactively make constants for these given their lack of stability, but we should be open to their inclusion if folks request them and it appears they're on track to standardize.
Header constants currently in http but not the registry
dnt
referrer-policy
upgrade-insecure-requests
x-dns-prefetch-control
x-xss-protection

These probably need to be handled on a case-by-case basis, as they might be referenced in other specs. For example, dnt is part of the Fetch standard.
Headers in neither the registry nor http
...but present in widely-cited sources such as MDN. For example, Accept-CH-Lifetime. These probably also need to be treated on a case-by-case basis.

Hm, even the MDN DNT page says the header is deprecated. Perhaps it's worth just removing the non-standard ones entirely.
Could we get away with removing all the deprecated/obsolete headers even if in the registry?

I'm in favor of including any registry headers that aren't provisional as constants in this crate, as they are very unlikely to ever go away.

It's a fair position to take. If many others prefer it, we can do that.
I'm personally skeptical of adding obscure names even if they are in the registry. They seem like a potential distraction in the docs. But I can't really articulate a good reason otherwise. Perhaps at least I'd wait to add the odd ones until someone really asked?

Could we get away with removing all the deprecated/obsolete headers even if in the registry?

I'm definitely coming from a biased perspective as an implementer of a reverse proxy. We don't control the nature of requests from clients or the responses from origins, so we try to accept as much actual existing HTTP traffic as possible without compromising security.
It's also common for current, active specs to refer to deprecated and obsolete headers. This is often in MAY or SHOULD contexts, but nonetheless comprehensive, modern implementations frequently need to at least refer to and understand the cruft even if they don't produce the cruft themselves.

I'm personally skeptical of adding obscure names even if they are in the registry. They seem like a potential distraction in the docs.

This raises a higher-level question: what is our goal for including these constants? For me, the value comes from being able to avoid repeating HeaderName::from_static() invocations for standardized headers across my different crates. And while that is less painful since that method became const, there are still some odd limitations that crop up (particularly around static references) that the crate-defined constants avoid. I don't personally come to the http rustdoc for information about the semantics of the headers, but I know I am not the typical user in that regard, and therefore am probably not a good judge about the level of distraction imposed by additional definitions in the docs.

Perhaps at least I'd wait to add the odd ones until someone really asked?

I think being proactive about adding registered names would help us avoid a trickle of one-off PRs and requests for releases (like I am doing now in #583 😬). And while I doubt we want to impose a proc macro dependency for http, we could also consider automatically generating the constants based on the IANA registry's CSV, which I got IANA and IETF to license as CC0.

What if a core, standard, forward-looking set of constants were included by default, but then the rest of the obscure/deprecated/provisional/nonstandard-but-in-use ones were hidden behind a feature flag, like extra-headers?

@d2718 the complexity of wrangling a Cargo feature would outweigh the benefit of less clutter in the namespace, in my opinion.
I suppose we could add some namespacing via child modules of http::header: IANA permanent header names could stay in http::header, but we could stash other categories in http::header::obsolete, http::header::provisional, etc. I kinda like that as a quick signal to the user that they're straying off the beaten path.

Another thing that came to my mind today was that now that from_static is a const fn, we could potentially provide constants that don't require being in the internal StandardHeader enum. A small concern I had had before was around growing that enum and match statements. But since they can also be from a static string, it does feel like we could include all easily.
Then I suppose a last question is how to determine whether something should be in StandardHeader, or if it should be from a string. A value in StandardHeader will mean that hashing and comparing it will be faster than a static string, but growing the enum may mean the match in hash and cmp (and as_str) will be more code, and could be miss optimizations. Probably worth measuring or determining some heuristic? I think most people would prefer that the most common headers are as fast as possible.

Then I suppose a last question is how to determine whether something should be in StandardHeader, or if it should be from a string.

I think we should start with a larger set in StandardHeader, since we should be able to "demote" them to from_static invocations without semver breakage if it turns out performance is a problem. We can check the microbenchmarks right away to have some idea of impact, but concerns about missed optimizations are hard to definitively disprove.

Would you be open for me to make a PR for Client Hint headers, or do these count as provisional, even if browsers do all support them now a days (the most common type of user agent among them all).

https://datatracker.ietf.org/doc/html/rfc8942
https://wicg.github.io/client-hints-infrastructure/

I would understand if you do not want it yet though, even though servers and proxies do need these for content negotiation. It also impacts other aspects such as Caching.


Use signature in request

Fixes #1

@manycoding Added changelog (up to v0.1.13). Once this gets merged, I will release as v1.0.0 and generate the latest one.


Created CODE_OF_CONDUCT.md

I have added the code of contributor.md file.
fixes. #3

Hi @iamkanhaiyakumar, can you please give gssoc-extd, hacktoberfest-accepted and level 1 label to this PR.


bug: Theme Inconsistency in Package Version 4 on Firefox v119

What version of daisyUI are you using?
4.4.2
Which browsers are you seeing the problem on?
Firefox
Reproduction URL
https://daisyui.com/docs/themes/
Describe your issue
I've identified an issue related to theme changing within version 4 of the package. Specifically, when attempting to change the theme, I noticed that the border radius of elements and fonts dynamically adjusts as expected; however, the color changes are not reflected. This behavior is unique to Firefox Version 119, as the issue is not replicated in Chrome during testing.
It's important to highlight that this issue is specific to Version 4 of the package. Additionally, I tested this behavior not only on a personal application but also on your official website of the package using firefox. The website exhibits the same inconsistency in theme adjustments, and for your reference, I've provided the link to daisyui page without disclosing the link to my project.

Looks like it is fixed already.
Here's a video from Firefox 119:
https://github.com/saadeghi/daisyui/assets/7342023/1284440d-9981-45c2-a176-4980b93d5cc6


Not realy an issue - request.

Hi. Thanks for the gerat work!
Any chanse to add those conditions?
/cast [button:1] spell
/cast [button:2] spell
And add /use for macro like this:
/use [button:1] item
/use [button:2] item
Im NOT a clicker, But it would be nice to have those options.
TY.

 Live and let live!
Regarding your /use request:
I was just thinking about adding /use alongside with /equip the other day, but I wasn't sure about how useful these would be. But since at least one of these have been requested, I'll add them in the future! But before that, I have to complete one or two other things first, so don't expect them in the next few days or so. :)
Regarding the button Conditional:
I don't see a way of implementing this as of right now because the Addon is waiting for chat commands instead of action bar button presses. So I don't know if there is a way to do this without rewriting the entire thing. But I'll look into it once I find the time to.

You are such a great man. TY in andavance. :)

Implemented!


Add BONSAI as the default storage engine for besu

--data-storage-format=BONSAI, besu will probably update their default in a future release but we should be using bonsai as our default

IMO, we should keep whatever besu decides as their default. So I wouldn't bake this into the defaults, but instead add it as an extra arg on whatever deployments we need it.

Besu said they wanted to change the default and didn't get to it so far, so in the devs opinion this should've been the "Default" all along. Main reason to add it here is that we then don't have to think about it for each and every testnet.

+1 to change the default to Bonsai. Caused too much trouble already when we did not use Bonsai.

BONSAI is now default on Besu


[GIT PULL] man/io_uring_setup: Add missing feat, fmt etc.

This adds:

Docs for IORING_FEAT_RECVSEND_BUNDLE
A missing error code
A remark for attach wq that the sq poll thread is also shared
fmt fixes

to the man page of io_uring_setup.

git request-pull output:
The following changes since commit 66e7618a900b172f464cde132548fecbfc09f8cd:

  test/linked-defer-close: ignore argument passed in (2024-09-20 02:47:51 -0600)

are available in the Git repository at:

  https://github.com/CPestka/liburing io_uring_setup_man

for you to fetch changes up to 571ad06dc8e931747c8d65326212e3ae1d3ffb6f:

  man/io_uring_setup: Add doc for IORING_FEAT_RECVSEND_BUNDLE (2024-09-20 13:25:44 +0200)

----------------------------------------------------------------
CPestka (4):
      man/io_uring_setup: Add remark about SQ poll thread with ATTACH_WQ
      man/io_uring_setup: Fix formatting errors/inconsistencies
      man/io_uring_setup: Add missing error code
      man/io_uring_setup: Add doc for IORING_FEAT_RECVSEND_BUNDLE

 man/io_uring_setup.2 | 79 ++++++++++++++++++++++++++++++++++++++++++++++---------------------------------
 1 file changed, 46 insertions(+), 33 deletions(-)

Click to show/hide pull request guidelines
Pull Request Guidelines

To make everyone easily filter pull request from the email
notification, use [GIT PULL] as a prefix in your PR title.

[GIT PULL] Your Pull Request Title

Follow the commit message format rules below.
Follow the Linux kernel coding style (see: https://github.com/torvalds/linux/blob/master/Documentation/process/coding-style.rst).

Commit message format rules:

The first line is title (don't be more than 72 chars if possible).
Then an empty line.
Then a description (may be omitted for truly trivial changes).
Then an empty line again (if it has a description).
Then a Signed-off-by tag with your real name and email. For example:

Signed-off-by: Foo Bar<EMAIL_ADDRESS>
The description should be word-wrapped at 72 chars. Some things should
not be word-wrapped. They may be some kind of quoted text - long
compiler error messages, oops reports, Link, etc. (things that have a
certain specific format).
Note that all of this goes in the commit message, not in the pull
request text. The pull request text should introduce what this pull
request does, and each commit message should explain the rationale for
why that particular change was made. The git tree is canonical source
of truth, not github.
Each patch should do one thing, and one thing only. If you find yourself
writing an explanation for why a patch is fixing multiple issues, that's
a good indication that the change should be split into separate patches.
If the commit is a fix for an issue, add a Fixes tag with the issue
URL.
Don't use GitHub anonymous email like this as the commit author:
<EMAIL_ADDRESS>
Use a real email address!
Commit message example:
src/queue: don't flush SQ ring for new wait interface

If we have IORING_FEAT_EXT_ARG, then timeouts are done through the
syscall instead of by posting an internal timeout. This was done
to be both more efficient, but also to enable multi-threaded use
the wait side. If we touch the SQ state by flushing it, that isn't
safe without synchronization.

Fixes: https://github.com/axboe/liburing/issues/402
Signed-off-by: Jens Axboe<EMAIL_ADDRESS>

By submitting this pull request, I acknowledge that:

I have followed the above pull request guidelines.
I have the rights to submit this work under the same license.
I agree to a Developer Certificate of Origin (see https://developercertificate.org for more information).

Ah, btw i just noticed that there is no link to the contributing.md, that was added recently, in the pr template. Would probably be a nice addition.

Just one minor comment, rest looks good to go.

Ah, btw i just noticed that there is no link to the contributing.md, that was added recently, in the pr template. Would probably be a nice addition.

Agree, just wasn't quite sure where to link it from...


Docstrings for all epimodel types and generate_latent_infs plus named arguments for constructors

This is a draft PR for on going work on documenting AbstractEpiModel subtypes and methods that dispatch on them.
Current focus and decisions:

As recommended here I am focusing documentation at the highest/most abstract level. This means that I'm going to give the example usages and most extensive documentation to generate_latent_infs dispatch on generic AbstractEpiModel.
I don't think the METHODLIST was useful in our doc template and has been removed.
Example usage of a DirectInfections goes beyond just constructing the struct, but also its main usage with generate_latent_infs.
Example usage is not a doc test; it has a complicated output that works ok with a spread of testitems. However, a next step could be to combine as per discussed in #48.

This is aimed at addressing #137 which is part of #35 and #97 . It sets my current expectation of docstrings #135 and #126 .
Extra activity

When it is absolutely straightforward to create a default constructor with named arguments using @kwdef I am doing it, because this also makes example usage easier. This moves towards addressing #133 , but won't close this issue.
Advantage of above is that default priors are added directly aiming to address #131 .

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 97.61%. Comparing base (649567f) to head (fe20c7c).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #138   +/-   ##
=======================================
  Coverage   97.61%   97.61%
=======================================
  Files          13       13
  Lines         168      168
=======================================
  Hits          164      164
  Misses          4        4

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

I've done everything in the opening description except for the example usage of the EpiModels and generate_latent_infs is not a doctest.
The reason for this is that the pattern of doc testing against an expected result didn't seem to meet what we want from the examples and might lead into complexity around different random seed implementation on different OS etc. An alternative approach which just checks the examples run didn't seem to do anything that our testing CI doesn't do anyway.
Happy to get pushed back on this.


Add Oceananigans compat + tweaks 1D diffusion + internal tide

I'm tempted to utilize the Makie extension.

of course re: extension

dang, maybe we should use literate for the notebooks cause i can't see diffs

Yes. We need to change that.


Explain Workflows

I currently try to migrate pyiron_base to the new actions, but for the workflows I struggle to understand what they are doing. At least from their names https://github.com/pyiron/pyiron_base/pull/994

@liamhuber I started to do this now for pyiron_experimental https://github.com/pyiron/pyiron_experimental/pull/119


python3Packages.spacy_models: 3.0.0 -> 3.3.0

Description of changes
Updates all spacy models to version 3.3.0, thereby fixes the build issues of the models (Closes #180155) and adds some new models.

Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

@ofborg build python310Packages.spacy_models


Update Jekyll Site-Wide Settings

Fixes #53.
Change title and repository link of Jekyll site.

Codecov Report

Merging #54 (e180530) into master (1a12d2e) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #54   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Missing regmap documentation at the documentation page

Description:
The "robotframework-construct" link in the README points to a documentation page where the regmap and reflector sections are identical. As a result, the regmap documentation is missing.
Steps to Reproduce:

Go to the README file of this repository.
Click on the "robotframework-construct" link under "What is robotframework-construct?" section.
Observe that the regmap and reflector sections in the documentation are identical.

Expected Behavior:
The regmap section should contain the correct documentation for regmap keywords.
URL:
https://marketsquare.github.io/robotframework-construct/
Regmap:

Reflector:

Thank you!

Hi bencej98
Thanks for noting this, this is now fixed with PR.:
https://github.com/MarketSquare/robotframework-construct/pull/17
Best regards,
Franz


Change find_link_by API and add functionality to Elements

Fixes #419 and #575
This adds the find_link_by functionality to elements in the form of Element.links.find_by_
The Browser behaves the same way, ie: Browser.links.find_by_href however the original API is preserved. Browser.find_link_by_href still works.
If this PR is accepted, I'll follow it up with changing the documentation and adding a deprecation notice for the Browser.find_link_by methods.
If the API change is rejected, I'll add the older method names to the Element. Regardless, I think this pattern of using a parent object, even if hidden, still reduces code duplication.

@jsfehler thank you


Add properties to control the rendering of times and other types

Only some of the type rendering configuration defaults are exposed via properties.  For example, there is no property to set the default time rendering format.

We actually do have the dateTimeFormat property in community for default time format: https://github.com/deephaven/web-client-ui/blob/e1b4562585fd6ea07efe085fe7ae5128a689ce37/packages/code-studio/src/storage/LocalWorkspaceStorage.ts#L62
The other props we have are:

dateTimeFormat: default date and time format
timeZone: default time zone
showTimeZone: Whether to show the time zone in date cells or not
showTSeparator: Whether to show the T separate in date cells or not
decimalFormat: Default decimal format
integerFormat: Default integer format
truncateNumbersWithPound: Whether to display ### when a number is truncated instead of the truncated number
isMinimapEnabled: Whether to display the minimap in notebook editors or not

There's a docs ticket logged, closing this.


Terminal v1.5.10271.0 crashes on startup due to settings.json load bug

Environment
Windows build number: 10.0.19041.0
Windows Terminal version (if applicable): 1.5.10271.0

Steps to reproduce

Add an empty object to the schemes option list
As an example I've picked the default configuration and only changed "schemes": [] into "schemes": [{}]"
// This file was initially generated by Windows Terminal 1.1.2021.0
// It should still be usable in newer versions, but newer versions might have additional
// settings, help text, or changes that you will not see unless you clear this file
// and let us generate a new one for you.

// To view the default settings, hold "alt" while clicking on the "Settings" button.
// For documentation on these settings, see: https://aka.ms/terminal-documentation
{
    "$schema": "https://aka.ms/terminal-profiles-schema",

    "defaultProfile": "{07b52e3e-de2c-5db4-bd2d-ba144ed6c273}",

    // You can add more global application settings here.
    // To learn more about global settings, visit https://aka.ms/terminal-global-settings

    // If enabled, selections are automatically copied to your clipboard.
    "copyOnSelect": false,

    // If enabled, formatted data is also copied to your clipboard
    "copyFormatting": false,

    "theme": "dark",

    // A profile specifies a command to execute paired with information about how it should look and feel.
    // Each one of them will appear in the 'New Tab' dropdown,
    //   and can be invoked from the commandline with `wt.exe -p xxx`
    // To learn more about profiles, visit https://aka.ms/terminal-profile-settings
    "profiles":
    {
        "defaults":
        {
            // Put settings here that you want to apply to all profiles.
        },
        "list":
        [
            {
                "guid": "{07b52e3e-de2c-5db4-bd2d-ba144ed6c273}",
                "hidden": false,
                "name": "Ubuntu-20.04",
                "source": "Windows.Terminal.Wsl",
                "colorScheme": "Solarized Dark",
                "fontFace": "Droid Sans Mono for Powerline",
                "fontSize": 11,
                "fontWeight": "light",
                "antialiasingMode": "cleartype",
                "startingDirectory": "//wsl$/Ubuntu-20.04/home/baskiers/",
                "historySize": 99001
            },
            {
                // Make changes here to the powershell.exe profile.
                "guid": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",
                "name": "Windows PowerShell",
                "commandline": "powershell.exe",
                "hidden": false
            },
            {
                // Make changes here to the cmd.exe profile.
                "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
                "name": "Command Prompt",
                "commandline": "cmd.exe",
                "hidden": false
            },
            {
                "guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}",
                "hidden": false,
                "name": "Azure Cloud Shell",
                "source": "Windows.Terminal.Azure"
            }
        ]
    },

    // Add custom color schemes to this array.
    // To learn more about color schemes, visit https://aka.ms/terminal-color-schemes
    "schemes": [{}],

    // Add custom keybindings to this array.
    // To unbind a key combination from your defaults.json, set the command to "unbound".
    // To learn more about keybindings, visit https://aka.ms/terminal-keybindings
    "keybindings":
    [
        // Copy and paste are bound to Ctrl+Shift+C and Ctrl+Shift+V in your defaults.json.
        // These two lines additionally bind them to Ctrl+C and Ctrl+V.
        // To learn more about selection, visit https://aka.ms/terminal-selection
        { "command": {"action": "copy", "singleLine": false }, "keys": "ctrl+c" },
        { "command": "paste", "keys": "ctrl+v" },

        // Press Ctrl+F to open the search box
        { "command": "find", "keys": "ctrl+f" },

        { "command": { "action": "newTab", "index": 0 }, "keys": "ctrl+t" },
        // Press Alt+Shift+D to open a new pane.
        // - "split": "auto" makes this pane open in the direction that provides the most surface area.
        // - "splitMode": "duplicate" makes the new pane use the focused pane's profile.
        // To learn more about panes, visit https://aka.ms/terminal-panes
        { "command": { "action": "splitPane", "split": "auto", "splitMode": "duplicate" }, "keys": "ctrl+shift+d" },

        // Unbound
        { "command": "unbound", "keys": "alt+shift+esc" }
    ]
}

Expected behavior

Terminal starts up.
The schema does validate on the JSON Schema definition (https://aka.ms/terminal-profiles-schema). If this configuration is invalid the schema definition should reflect that.
Actual behavior

The terminal instantly crashes on startup.
I've used this configuration for around half a year without issues.
This issue could be a subset of #8358, although I started experiencing this bug only in the latest version of the Terminal.

Curious. I wouldn't have expected "schemes": [{}]" to crash 1.5. If anything, I'd expect it to crash 1.6, but in reality is shouldn't crash at all.
I'll leave the "should we service this" decision to @DHowett

We absolutely should. I wonder what changed (1.5? doesn't even have SUI stuff.)
@zadjii-msft could this be Srdjan's issue?

No idea yet. Spinning up a main build to see if this has a similar stack trace now. Methinks it won't. Srdjan's  stack looks like it's in either CalcSnappedDimension or CommandPalette::InitializeComponent - the bug's listed as the first frame, but then is linked to cabs with stacks pointing at the second frame? Maybe I just misclicked somewhere.

@miniksa this is the one I was talking about

Oh no,
    IMap<winrt::hstring, Command> TerminalPage::_ExpandCommands(IMapView<winrt::hstring, Command> commandsToExpand,
                                                                IVectorView<Profile> profiles,
                                                                IMapView<winrt::hstring, ColorScheme> schemes)
    {
        IVector<SettingsLoadWarnings> warnings;

That warnings right there isn't getting initialized to anything.  Probs because the original vector didn't need to be initialized, the default ctor for a std::vector actually makes something. Not so for a winrt::IVector. Oops.


New Container App routes not being served

I'm following the guides, and i'm having trouble creating a new container app with
lotus generate app admin
When I create the new app, everything is good. When I visit the newly generated route /admin it shows the bootstrapped screen.
If I make a new action under this app using
lotus generate action app home#index
all potential routes I could think of would not work
 ::1 - - [02/Jul/2015:00:40:09 -0500] "GET /admin/home HTTP/1.1" 404 - 0.2267 ::1 - - [02/Jul/2015:00:40:14 -0500] "GET /admin/home/ HTTP/1.1" 404 - 0.2213 ::1 - - [02/Jul/2015:00:40:28 -0500] "GET /home/ HTTP/1.1" 404 - 0.2177 ::1 - - [02/Jul/2015:00:40:40 -0500] "GET /home HTTP/1.1" 404 - 0.2230
I've reproduced this several times with a fresh install and following the instructions above.
EDIT:
potentially related to #262
my config/environment.rb that is autogenerated by lotus
Lotus::Container.configure do
  mount Admin::Application, at: '/admin'
  mount Web::Application, at: '/'
end

Lotus 0.4.0
ruby 2.2.1p85 (2015-02-26 revision 49769) [x86_64-darwin14]
OSX Yosemite 10.10.2

I followed the steps you stated and this is what I got:
::1 - - [02/Jul/2015:09:19:22 +0200] "GET / HTTP/1.1" 500 - 0.1697
::1 - - [02/Jul/2015:09:19:22 +0200] "GET /favicon.ico HTTP/1.1" 500 - 0.1102
::1 - - [02/Jul/2015:09:20:12 +0200] "GET / HTTP/1.1" 500 - 0.2046
::1 - - [02/Jul/2015:09:20:27 +0200] "GET / HTTP/1.1" 404 - 0.1687
::1 - - [02/Jul/2015:09:20:33 +0200] "GET /home HTTP/1.1" 200 - 0.1429
::1 - - [02/Jul/2015:09:20:38 +0200] "GET /admin/home HTTP/1.1" 200 - 0.1370

Lotus found my route and sent a 200 status.
Running lotus 0.4.0 and ruby 2.2.2p95 (2015-04-13 revision 50295) [x86_64-darwin14] on OS X Yosemite 10.10.4.

@Eein we also found a regression with version 0.4.0, this issue will be addressed in the next 0.5.0. For the time being, you could live on-edge with:
# Gemfile
gem 'lotusrb', github: 'lotus/lotus'
gem 'lotus-model', github: 'lotus/model'
gem 'lotus-controller', github: 'lotus/controller'
gem 'lotus-view', github: 'lotus/view'
gem 'lotus-helpers', github: 'lotus/helpers'
gem 'lotus-validations', github: 'lotus/validations'
gem 'lotus-router', github: 'lotus/router'

@Eein Not in 0.5.0, but in a upcoming v0.4.1. /cc @joneslee85 @lotus/core-team


problem with input focusing/opening dropdown (when using $animate)

Problem occures when we click on input - it should be focused and i should be able to write something in input, but i cant - and what more - dropdown with suggestions becoming opened.
latest $animate is not working with ui-select, problem is here:
     if (ctrl.$animate && ctrl.$animate.on && ctrl.$animate.enabled(container[0])) {
//I CAN GO INHERE
        ctrl.$animate.on('enter', container[0], function (elem, phase) {
//BUT THIS BLOCK IS NOT REACHED
          if (phase === 'close') {
            // Only focus input after the animation has finished
            $timeout(function () {
              ctrl.focusSearchInput(initSearchValue);
            });
          }
        });

temporary fix that i made is commented block with if/else conditions replaced by:
        $timeout(function () {
          ctrl.focusSearchInput(initSearchValue);
          if(!ctrl.tagging.isActivated && ctrl.items.length > 1) {
            _ensureHighlightVisible();
          }
        });

Im working with angular 1.5.3 and latest version of ui-select.

This looks like a duplicate of #1306 and/or #1436 - can you confirm if that is the case?

No, its not. I can focus input but not on first click and dropdown shouldn't be opened without any available suggestions inside

Can you create a plunkr that demonstrates this? (Helpful starting point: http://angular-ui.github.io/ui-select/#examples)

Having the same issue, will report back if I can reproduce in a plunkr. In my case I have $animate.enabled(false) in my controller. If I set it to true then it works, however I need it set to false for other reasons.

I've created a new plunker that demonstates my issue (first dropdown, regular ui select):
http://plnkr.co/edit/X6eD7W2LwYG5j2yDdSme?p=preview

Hey,
The problem occurs also for selectize theme and ngAnimate when $animateProvider is configured.
app.config(function($animateProvider) {
  $animateProvider.classNameFilter(/my-animate/);
});

plnkr - http://plnkr.co/edit/mcFa2NyYsbULrTPsLr99?p=preview

having the same issue

Hey,
in our application we also have this problem.
Has someone found a workaround or is there already any progress in solving this problem with the next version?

I'm currently monkey-patching the $animate.enabled method.
And I'm using $animateProvider.classNameFilter to enable animations on specific elements.
var animationClassNameFilter = /vnd-animated/
angular.module('something').config(function ($animateProvider) {
    $animateProvider.classNameFilter(animationClassNameFilter)
})

angular.module('ui-select').run(function($animate) {
  var origEnabled = $animate.enabled
  $animate.enabled = function (elem) {
    if (arguments.length !== 1) {
      return origEnabled.apply($animate, arguments)
    } else if (origEnabled(elem)) {
      return animationClassNameFilter.test(elem.classNames)
    }
    return false
  }
})

This div uses animations

I'm facing a similar issue if the dropdown has no content and append-to-body are used together. I think the dropdown is created and destroyed when there are no items in dropdown list, which is resulting focusing the body element.
End result: A click on input field, is focusing the body element for the first time. It works fine when the input field is clicked again.


Change volumes database name should not be fixed

- What I did
Change the volumes database name from "metadata.db" to "metadata-[hostname].db",
So it can be use docker 1.11.x+ with GlusterFS brick that mount to /var/lib/docker/volumes
- How I did it
I get a hostname from os.Hostname() then add as suffix of old name.
- How to verify it
metadata.db in /var/lib/docker/volumes changed to metadata-[hostname].db
- Description for the changelog
Change volumes database name should not be fixed.
- A picture of a cute animal (not mandatory but encouraged)
Sadly, I don't have this.
Signed-off-by: Surachate Sangtongrum<EMAIL_ADDRESS>

NOTLGTM
Why is this a problem?

Before docker 1.11.0 docker volumes have no metadata.db file,
So I managed to mount GlusterFS to /var/lib/docker/volumes across the cluster to share volume across instances.
At this point I can attach more space without touching docker.
Why I don't use volume plugin, Because volume plugin of GlusterFS is unreliable.
The problem is if I use docker in a single instance, It's OK.
But if it is clustered, It's not.
metadata.db block another docker daemon to start, can run only first one.

I'm sorry, but this is not a supported setup.
The engine expects exclusive access to it's root dir (/var/lib/docker).
Even so, shharing the volumes across a cluster like that but splitting the metadata db will lead to inconsistencies.
I'm sorry but going to close this because this is not something we can support.
If the glusterfs driver is not working well, that'd be the place I'd look at improving.
Thanks for the contribution!


error when calling picotts service

Hi,
on Home Assistant 0.115.2 running on Raspberry 4 I am getting the following error when calling picotts service:
Logger: homeassistant.components.websocket_api.http.connection.547602550496
Source: components/tts/__init__.py:470
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 17:50:01 (1 occurrences)
Last logged: 17:50:01

'en-US' not a Frame instance
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 137, in handle_call_service
    await hass.services.async_call(
  File "/usr/src/homeassistant/homeassistant/core.py", line 1315, in async_call
    task.result()
  File "/usr/src/homeassistant/homeassistant/core.py", line 1350, in _execute_service
    await handler.func(service_call)
  File "/usr/src/homeassistant/homeassistant/components/tts/__init__.py", line 167, in async_say_handle
    url = await tts.async_get_url(
  File "/usr/src/homeassistant/homeassistant/components/tts/__init__.py", line 340, in async_get_url
    filename = await self.async_get_tts_audio(
  File "/usr/src/homeassistant/homeassistant/components/tts/__init__.py", line 367, in async_get_tts_audio
    data = self.write_tags(filename, data, provider, message, language, options)
  File "/usr/src/homeassistant/homeassistant/components/tts/__init__.py", line 470, in write_tags
    tts_file["artist"] = artist
  File "/usr/local/lib/python3.8/site-packages/mutagen/_file.py", line 74, in __setitem__
    self.tags[key] = value
  File "/usr/local/lib/python3.8/site-packages/mutagen/id3/_tags.py", line 339, in __setitem__
    raise TypeError("%r not a Frame instance" % tag)
TypeError: 'en-US' not a Frame instance

I installed the supervisor addon from here: https://github.com/Poeschl/Hassio-Addons
...then this custom component via HACS.
I am calling the service like this:
service: tts.picotts_remote_say
data:
message: hi!
entity_id: media_player.google_home

Am I doing something wrong?
Thanks!

I can confirm this behavior on 115.3 x64 on a RPi4 with the following configs:
(1)
tts:
  - platform: picotts_remote

(2)
tts:
  - platform: picotts_remote
    language: "en-US"

Thank you for bringing local tts to HA! 👍

My component config is the following:
tts:
  - platform: picotts_remote
    language: "en-US"

Thanks!

Related to this: https://github.com/home-assistant/core/issues/40244

I confirm this issue is solved by https://github.com/home-assistant/core/issues/40244
PicoTTS works in Home Assistant 0.115.5.
Thanks!


Incompatibility with ActiveStorage

Rails Version: 5.2.1
Ruby Version: 2.3.7
Server stops responding on loading multiple images on any view page
<% @meal.images.each do |image| %>   <%= image_tag image %> <% end %>
On debugging, found the following error:

Footnotes Footnotes::Notes::ViewNote Exception: undefined method `[]' for nil:NilClass

Had to remove the gem eventually

I fixed this in my fork, which you can use with gem "rails6-footnotes", "~> 5.0".

I've released v5 of rails-footnotes, which fixes this problem.


Currency for Gift

Check the last comment

The amount entry field only shows sats option, no other option. Gift cards kits show value in sats no matter the currency on the Home Screen.

Put back the currency switch for Gits (both when creating and in Manage Gift screen)
The gifts should have no relation to the switch in the accounts
Both the switches (Create and Manage) should be linked - be the same
The details on the Manage screen should reflect the currency chosen
The currency on the Create screen should be used for all details used on that screen and going forward.
The receiver should see the gift in the amount sent. For this we may need to pass the amount at that time as text. It will be shown in the card only. Once it is accepted and in the Gift list, the currency there will work according to the above. The amount sent ($5, £10 or 100k sats) can show exactly like that on the receiver side ignoring the receiver side currency or the exchange rate at that time. So a simple text as Amount should suffice.

6th point is still pending.So filing a new issue for this and closing this one.


Restore governance commands under byron command

Restore backwards compatibility with governance commands previously under byron command.

bors r+


Consider: bubbling select event when clicking with a pointer device

Pointer device support in this lib is, admittedly, a bit less solid than keyboard support. Atm it looks like the onSelected event doesn't bubble when clicking on a FocusNode.
Todo:

[x] Verify that this is true
[x] Decide if it should bubble or not in this situation
[ ] Make any necessary changes based on the above

It's true (CodeSandbox), as it is triggered inside the FocusNode itself via an bound onClick function handler onto the elementType (Here)

Thanks for looking into this!

To make this work, it should rely upon bubbleKey(store, 'select'); passing some other params maybe to identify the source of event(?) (maybe could be useful to receive this information inside the callback)

👍 Re: source, see #66

In my opinion, if the onSelected gets triggered I assume that so happens despite of the event that triggers the selection. Otherwise, a new specialized "onClicked" callback should be added.

Hmmm, I'm not sure I follow. Would you mind rephrasing this sentence?

Currently this library mimics DOM event's behavior (Thanks @giankd for the demo HERE) so it appears to me that every event, despite of its source bubbles the dom tree up to the document

👍

In my opinion, if the onSelected gets triggered I assume that so happens despite of the event that triggers the selection. Otherwise, a new specialized "onClicked" callback should be added.

Hmmm, I'm not sure I follow. Would you mind rephrasing this sentence?

Sure!
When (as a library user) i implement my custom onSelected on a specific node i expect that it will be called when a FocusNode, or one of its children gets selected.
Now, assume that i read about the pointerEvents prop inside the FocusRoot's docs.
"Cool stuff! I'll just pop this boolean inside the focus root and i'm set!"
In my DOM composition (as per @giankd sandbox) this may lead to trigger only the specific node that implements onSelected to be called, without bubbling, making the lib behavior different from using pointer event or key events
I hope I've made myself clear now
I'm sorry, my english is not that good 😞

Super clear. That does make sense :+1: Thank you for elaborating!

Update: the reason that I manually did this rn is that the current bubbleKey bases it off of what's in focus. This works for remote input, because when you press Enter the source is always the leaf focused node.
However, you can click anywhere on the screen, so the source could be different.
Supporting this will require:

a function to generate an arbitrary hierarchy from a focus node
being able to optionally pass the hierarchy into bubbleKey, to bubble events up an arbitrary hierarchy
calling this in onClick


docs: fix README link to OpenTelemetry document

This PR, generated from an upstream Generator tweak, fixes our README link to the mis-cased, generated OpenTelemetry documentation.
Description

References

Review Checklist

[x] I have clicked on "allow edits by maintainers".
[ ] I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
[x] The correct base branch is being used, if not main
[ ] I have added tests to validate that the change in functionality is working as expected

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 30.88%. Comparing base (caf4586) to head (8e615d1).

Additional details and impacted files
@@            Coverage Diff            @@
##               main     #106   +/-   ##
=========================================
  Coverage     30.88%   30.88%
  Complexity      842      842
=========================================
  Files           168      168
  Lines          6185     6185
  Branches        679      679
=========================================
  Hits           1910     1910
  Misses         4177     4177
  Partials         98       98

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


ended up with two chats, to the same user, with totally different threads.

@nobitagit and I have two duplicate chats. Each with different threads.
I think because I added him as a Github user, then invited him as a keybase user?

Thanks for the report, CC @maxtaco or @strib

Passing my cc onto @mmaxim

This appears to be the SBS conflict case, which we have on the roadmap to fix. Sorry about that, but look for a fix in the coming releases.

Can you link me to the issue about SBS conflict?

Same problem here.


[Proposal] Add Platforms editing to Project Configuration

Description
This PR proposes to add support to edit all localComponents default supported platforms. The use case for this arises with the deprecation of a platform version where you want to update all packages supported platforms. For example, we deprecated iOS .v14 recently in our project, and we would like to update all packages to iOS .v15. You can easily do this in Xcode doing a find and replace; however, it is not as trivial while using Phoenix as you would need to go and edit each Component manually. To make Phoenix better, some trivial tasks as this one should be as easy as doing it on Xcode.
Would love to hear thoughts and feedback, and maybe any build up on this idea.
Changes
There are a couple of major changes done in the project that may or may not be necessary:

We extracted the platforms from being individual properties into a struct called Platforms. This was done to expose the same properties into ProjectConfiguration without much duplication.
We extracted the platforms selection menu to its own view called PlatformsEditingView. This was done to reuse the same menus in the ProjectConfigiration edit view and Component edit view
Decoding and Encoding. With Platforms being its own struct we made the Decoding and Encoding of Component backwards compatible to adapt these. However, Project Configuration uses the plain Platforms nesting and adds the new properties

Resources
I already have this PR working and edits to all local components are working. A preview of the change looks like this:

If I understood correctly from the code, your approach makes the change you make in the project configuration apply to all the components in the project. So when you update the iOS Version in Project Configuration, all components will have this new iOS Version set to them.
That's correct currently, we set the default to all of them.

I understand the requirements, basically to achieve this we would need to the following:

Add PlatformsEditingView to also in the Family Configuration
Add projectDefault to platforms iOSVersion, macOSVersion, tvOSVersion etc..

I'm just not clear on the nil value. I'm guessing we want to use nil to ignore the ProjectConfiguration value. Maybe instead of nil we can have ignoreProjectDefault so it is a little bit more clear?
Moreover, instead of adding the projectDefault or ignoreProjectDefault. I might suggested to make it into a checkbox as part of the platforms. Where you have three checkbox on the Component
[] Use Project Configuration Default
[] Use Family Configuration Default
[] Ignore Default Values
When tapping on Ignore Default Value we enable / show the PlatformsEditingView. That might result into a more straightforward UI/UX. What do you think?
Let me know if I understood the ideas correctly.

No I don't think we need the have platforms defined in the family also. I just meant that the project configuration platforms should override the component platforms in case the component doesn't have values for them.
And as an extra, it would be amazing if we could allow the components to choose to ignore the project configuration even if they have a nil value.

Maybe instead of making the values in the Platforms struct Optional, we could use something like the following:
fileprivate enum OptionalOverrideConstant {
    static let ignoreProjectValue: String = "ignoreProjectConfiguration"
}

public enum OptionalOverride<Value: RawRepresentable>: Codable where Value.RawValue: Codable {
    case projectDefault
    case ignoreProjectConfiguration
    case some(Value)

    public init(from decoder: Decoder) throws {
        let container = try decoder.singleValueContainer()

        if container.decodeNil() {
            self = .projectDefault
        } else if (try container.decode(String.self)) == OptionalOverrideConstant.ignoreProjectValue {
            self = .ignoreProjectConfiguration
        } else {
            let rawValue = try container.decode(Value.RawValue.self)
            let value = Value(rawValue: rawValue)
            self = value.flatMap(Self.some) ?? .projectDefault
        }
    }

    public func encode(to encoder: Encoder) throws {
        var container = encoder.singleValueContainer()

        switch self {
        case .projectDefault:
            try container.encodeNil()
        case .ignoreProjectConfiguration:
            try container.encode(OptionalOverrideConstant.ignoreProjectValue)
        case .some(let value):
            try container.encode(value.rawValue)
        }
    }
}

And then we could disable the option to choose ignoreProjectConfiguration from the Project Confirugation View.
This is just an idea, you don't have to implement it in this PR. I think for not, simply making the component use the project configuration in case it doesn't have a value should be enough for your use case.


point-to-point type interface address error

The address read by the point-to-point type interface mptcpd is the address of the peer.
For example, int <IP_ADDRESS> peer <IP_ADDRESS>/32
The address read by MPTCP is <IP_ADDRESS>

Can you provide some more context?

The value of the ppp type interface is wrong, the example above


Ton coin transfer not working

I imported a private key 64 characters long and then deposit

my wallet balance by 500ton  when I tried to transfer them I started to get a signature error
ton does not transfer anywhere, and illegal input
what should I do?


script to discover the dead pubsub subscriptions

Hi there, I am currently facing an issue while attempting to discover dead subscriptions in Google Cloud Pub/Sub using Node.js scripts.
Background:
I recently set up an alert system on a Pub/Sub topic to send a notification to Slack if the backlog ever exceeds 50 messages. However, I encountered a situation where the message backlog reached over 200K messages. To address this, I am now trying to create a script that can identify and clean up dead Pub/Sub subscriptions.
Issue:
While I am not very familiar with Node.js, I attempted to create a scripts using the @google-cloud/pubsub library. Unfortunately, neither of these scripts seems to be working as expected.
script:
const { PubSub } = require('@google-cloud/pubsub');

// Replace 'your-project-id' with your actual Google Cloud Project ID
const projectId = 'your-project-id';

// Creates a PubSub client
const pubsub = new PubSub({ projectId });

async function discoverDeadSubscriptions() {
 try {
   // List all subscriptions in the project
   const [subscriptions] = await pubsub.getSubscriptions();

   // Check each subscription for activity
   for (const subscription of subscriptions) {
     const [messages] = await pubsub
       .topic(subscription.metadata.topic)
       .subscription(subscription.name)
       .seekToTime('2023-01-01T00:00:00Z') // Seek to the beginning of time
       .get();

     if (messages.length === 0) {
       console.log(`Subscription ${subscription.name} is empty (no messages). It may be a candidate for cleanup.`);
       // You can add code here to perform cleanup actions for dead subscriptions
     } else {
       console.log(`Subscription ${subscription.name} has messages and is active.`);
     }
   }
 } catch (error) {
    console.error(`Error discovering dead subscriptions: ${error.message}`);
 }
}

// Run the function to discover dead subscriptions
discoverDeadSubscriptions();

another:
const { PubSub } = require('@google-cloud/pubsub');
const pubsub = new PubSub();
const projectName = 'YOUR_PROJECT_ID';

const checkDeadSubscriptions = async () => {
  const subscriptions = await pubsub.getSubscriptions();

  for (const subscription of subscriptions) {
    const subscriptionName = subscription.name;
    const subscriptionData = await pubsub.subscriptionMetadata(subscriptionName);
    const lastAcknowledged = subscriptionData.ackId;
    const lastPublished = subscriptionData.pubsubMessage.publishTime;
    const timeSinceLastMessage = Date.now() - lastPublished;

    // Check if it has been more than one month since the last message was published
    if (timeSinceLastMessage ><PHONE_NUMBER>) { // 1 month in milliseconds
      console.log(`Potentially dead subscription: ${subscriptionName}`);
    }
  }
};
checkDeadSubscriptions();

I'd greatly appreciate your help in resolving the issues with these scripts.
Thanks a bunch for your time and assistance.
Best regards,

I can't really help with code writing but I do think it's worth asking, why do those subscriptions go dark? Is it something you expect in your app, or do messages just quit being delivered, or what?

Hello, thank you for your response. I would like to delete a message backlog that has accumulated to over 200K messages. To achieve this, I need to identify and remove old, inactive subscriptions among the 130 pubsub subscriptions I have.


make build-resources does not work on Windows

The build on Windows fails because the build-resources target fails. The package name computed in the following location is not correct:
https://github.com/apache/camel-k/blob/8fcf47c258c00ae3671929ba018ba8aeee79772d/cmd/util/vfs-gen/main.go#L117

I was experiencing the same issue and looking for solutions; I'd want to address this because my primary development environment is on a Windows PC.
@astefanutti, could you kindly offer a brief description of the prospective solution you want, as well as any references?

@SubhasmitaSw I can see two possible work-around that I'd like to be confirmed:

Copy the script/Makefile into the project root directory and try to run from there
Overwrite the Makefile symlink at the project root directory with one created by mklink: https://docs.microsoft.com/fr-fr/windows-server/administration/windows-commands/mklink

Another option would be to run the commands from the script directory, but that requires to make all the paths relative to the location of the Makefile, which may not be straightfoward: https://stackoverflow.com/questions/18136918/how-to-get-current-relative-directory-of-your-makefile

@astefanutti could you please assign this to me, I'd start working on it.

@SubhasmitaSw great, assigned :)

@astefanutti this issue description should now be changed to address the major problem, isn't it?

@SubhasmitaSw I've updated the issue title and description. Let me know if that's correct.

@astefanutti  Yes, It looks good now. One things, is this still to be considered a good-first-issue?

@astefanutti Yes, It looks good now. One things, is this still to be considered a good-first-issue?

@SubhasmitaSw I was inclined to be optimistic, but I infer from your comment that you suggest it may not qualify :) I trust your feedback and let's remove the label 👍🏼.

/lifecycle frozen

@SubhasmitaSw Do you mean status/never-stale?

@tadayosi yes

Fixing this issue while looking into #3364

https://github.com/apache/camel-k/pull/3823

According to the last comment, this is solved. Closing.


feat(ucd-1270): appeals-api-behalf-appellant-validation

Ticket Number

UCD-1270
Description of change

Appeals api - validation of behalf appellant
Checklist

[ ] Requires infrastructure changes
[ ] If adding or remove environment variables (e.g. in docker-compose.yaml) then I have updated the appropriate Helm chart
[x] I have updated the documentation accordingly
[ ] My commit history in this PR is linear
[x] New features have tests
[ ] Breaking change (team conversation required)

Important
Please do not merge from master (please only rebase). This keeps the history linear and easier to debug.

Some of this work is duplicated under 1279.


Task/uod 1054 propagate correlation

Add correlation id into the message when correlate action is added
Add support of avro codec

Not ready


Fix TestWebhook to work under non-default revisions

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[x] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[x] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

@Monkeyanator: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
cbf804144eb7c8dfd57ba7cdcd50a6231de0bc1b
link
/test integ-security-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-security-k8s-tests_istio


pronto crashes with simple command

I just installed pronto to try it, and when running I get:
$ pronto run
/Users/pt/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/pronto-0.5.3/lib/pronto/git/patches.rb:11:in `each_patch': illegal byte sequence (Rugged::RegexError)
        from /Users/pt/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/pronto-0.5.3/lib/pronto/git/patches.rb:11:in `map'
        from /Users/pt/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/pronto-0.5.3/lib/pronto/git/patches.rb:11:in `initialize'
        from /Users/pt/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/pronto-0.5.3/lib/pronto/git/repository.rb:17:in `new'
        from /Users/pt/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/pronto-0.5.3/lib/pronto/git/repository.rb:17:in `diff'
        from /Users/pt/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/pronto-0.5.3/lib/pronto.rb:37:in `run'
        from /Users/pt/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/pronto-0.5.3/lib/pronto/cli.rb:52:in `run'
        from /Users/pt/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/command.rb:27:in `run'
        from /Users/pt/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/invocation.rb:126:in `invoke_command'
        from /Users/pt/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor.rb:359:in `dispatch'
        from /Users/pt/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/base.rb:440:in `start'
        from /Users/pt/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/pronto-0.5.3/bin/pronto:6:in `<top (required)>'
        from /Users/pt/.rbenv/versions/2.1/bin/pronto:23:in `load'
        from /Users/pt/.rbenv/versions/2.1/bin/pronto:23:in `<main>'

And the same thing when trying the second command
$ pronto run --commit=$(git log --pretty=format:%H | tail -1)
/Users/pt/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/pronto-0.5.3/lib/pronto/git/patches.rb:11:in `each_patch': illegal byte sequence (Rugged::RegexError)
        from /Users/pt/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/pronto-0.5.3/lib/pronto/git/patches.rb:11:in `map'
        from /Users/pt/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/pronto-0.5.3/lib/pronto/git/patches.rb:11:in `initialize'
        from /Users/pt/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/pronto-0.5.3/lib/pronto/git/repository.rb:17:in `new'
        from /Users/pt/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/pronto-0.5.3/lib/pronto/git/repository.rb:17:in `diff'
        from /Users/pt/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/pronto-0.5.3/lib/pronto.rb:37:in `run'
        from /Users/pt/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/pronto-0.5.3/lib/pronto/cli.rb:52:in `run'
        from /Users/pt/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/command.rb:27:in `run'
        from /Users/pt/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/invocation.rb:126:in `invoke_command'
        from /Users/pt/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor.rb:359:in `dispatch'
        from /Users/pt/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/base.rb:440:in `start'
        from /Users/pt/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/pronto-0.5.3/bin/pronto:6:in `<top (required)>'
        from /Users/pt/.rbenv/versions/2.1/bin/pronto:23:in `load'
        from /Users/pt/.rbenv/versions/2.1/bin/pronto:23:in `<main>'

These work:
$ pronto list
flay
rubocop

$ pronto version
Pronto version 0.5.3

@ptarjan weird. Since it raises a Rugged error (a git library used by pronto), could you try running it on a different repo and report the results?

I work with and (probably) have a similar machine to @ptarjan, but ran into the same issue.
Running on this repo, it succeeds:
> git clone git@github.com:mmozuras/pronto.git
> cd pronto
> pronto version
0.6.0
> pronto list
[no output]
> pronto run
[no output, no error code]

# [installs gem install pronto-flay pronto-rubocop]
> pronto list
flay
rubocop
> pronto run
[no output, no error code]

What's the next thing I should look at?

I resolved this for myself:

Ran git fsck --full --strict on the repo. Other than dangling commits, it reported no issues.
Looks like pronto run raises somewhere in this method
Rugged::RegexError maps to GITERR_REGEX
Reading a StackOverflow post about the topic, it suggests setting export LC_CTYPE=C.

That works, what.

@shalecraig @ptarjan not sure if that's something that should be handled with pronto. But could either of you create a repo on GitHub, which could be used to reproduce the issue?

Closing this issue. It's not something that should be handled by pronto. In case you do encounter it, please try the fix suggested by @shalecraig.


Minor issue with the curl command in creating_actions.md

Expected Behaviour
Curl command listed on this page to invoke web actions should execute successfully.
Actual Behaviour
Running curl command as listed on this page gives error:
curl: (5) Could not resolve proxy: GET
Reproduce Scenario (including but not limited to)
Create and invoke any web action using curl command as listed on the page.
Steps to Reproduce
Platform and Version
Sample Code that illustrates the problem
Logs taken while reproducing problem

fixed in #29


Adding Resume model

Adding the Resume model
Adding related tests

fix #26
Please merge that PR only after merging #47

Fixed Nati's notes,
and also changed the test method name to more informative names.
@natifridman


Load and parse embedded resources more efficiently

Motivation
The current approach of a string replace incurs some additional allocation overhead.
Modifications
Process the string replacement as UTF8 against the raw bytes of the manifest resource stream rather than deserializing to a string and then generating another string with the namespace replaced.

/merge


add Web.Scotty.Cookie

addresses #253
cc @chessai ^^

this LGTM
Can you add tests?

I don't understand why is CI failing ; I've built thir PR successfully with GHC 9.2.7

I was afraid I would have to pull webdriver out but we have hspec-wai :)

Tests added @chessai ^^ LMK

@fumieval  we now import 'cookie' and re-export some of its definitions.

Hi @fumieval , could you merge this if there are no more questions?

Just triggered CI, if it passed I'll merge

CI failures are most puzzling. I did introduce two new dependencies in this PR (cookie and time), and perhaps the lower bounds need to be relaxed. I've only tested this PR with stack, I don't use cabal

@fumieval I've gotten rid of some unnecessary imports in one of the example binaries. Hopefully now CI will be green at least for the recent GHCs. I really don't know why don't older GHCs work

The CI failure for 8.6.5 seems to be due to a change in a recent version of 'wai-extra' which now imports 'crypton-x509' instead of 'x509'
https://github.com/scotty-web/scotty/actions/runs/5282948607/jobs/9564762917?pr=293#step:17:61
The failures on GHC <= 8.0.2 are still mysterious to me

I think it's fine to drop support for GHC < 8.10 (there's #289 too). Thoughts? @chessai @RyanGlScott

Can I do something to get this PR across the finish line?

I think it's fine to drop support for GHC < 8.10 (there's #289 too). Thoughts? @chessai @RyanGlScott

Fine by me


chore: update mplex

Needs:

[ ] https://github.com/libp2p/js-libp2p-mplex/pull/122
[ ] https://github.com/libp2p/js-libp2p-interfaces/pull/92

Superseded by #1221


Fix Create Dashboard popup form

Codecov Report
Patch and project coverage have no change.

Comparison is base (c8b484c) 65.85% compared to head (df042ff) 65.85%.

:exclamation: Current head df042ff differs from pull request most recent head 4181ae5. Consider uploading reports for the commit 4181ae5 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #121   +/-   ##
=======================================
  Coverage   65.85%   65.85%
=======================================
  Files         166      166
  Lines        1845     1845
=======================================
  Hits         1215     1215
  Misses        630      630

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


[MacOS/Darwin] Emulating Futex behaviour

Issue
Currently I use linux futex and windows waitonaddress to manage backpressure when using Wards and Loony as a threadpool queue.
Mac/Darwin do not have primitives or APIs that are similar.
Solutions
At the moment, I can only think of using conditions and locks.

Have decided on using Darwin ulock primitives which are basically futexes.
Issue being they are private functions.


[] build failure

PS D:\vcpkgmanage\vcpkg> .\vcpkg.exe install influxdb-cxx:x64-windows
Computing installation plan...
The following packages will be built and installed:
influxdb-cxx[core]:x64-windows -> 0.6.7
Detecting compiler hash for triplet x64-windows...
Restored 0 packages from C:\Users\q8718tiny\AppData\Local\vcpkg\archives in 251.1 us. Use --debug to see more details.
Starting package 1/1: influxdb-cxx:x64-windows
Building package influxdb-cxx[core]:x64-windows...
-- Using cached offa-influxdb-cxx-v0.6.7.tar.gz.
-- Cleaning sources at D:/vcpkgmanage/vcpkg/buildtrees/influxdb-cxx/src/v0.6.7-1d6a39a436.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source D:/vcpkgmanage/vcpkg/downloads/offa-influxdb-cxx-v0.6.7.tar.gz
-- Using source at D:/vcpkgmanage/vcpkg/buildtrees/influxdb-cxx/src/v0.6.7-1d6a39a436.clean
-- Configuring x64-windows
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:127 (message):
Command failed: ninja -v
Working Directory: D:/vcpkgmanage/vcpkg/buildtrees/influxdb-cxx/x64-windows-rel/vcpkg-parallel-configure
Error code: 1
See logs for more information:
D:\vcpkgmanage\vcpkg\buildtrees\influxdb-cxx\config-x64-windows-out.log
Call Stack (most recent call first):
installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_configure.cmake:411 (vcpkg_execute_required_process)
ports/influxdb-cxx/portfile.cmake:14 (vcpkg_cmake_configure)
scripts/ports.cmake:142 (include)
Error: Building package influxdb-cxx:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with git pull and .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
package: influxdb-cxx[core]:x64-windows -> 0.6.7
vcpkg version: cbc22a396 2021-11-17 (30 hours ago)
vcpkg-tool version: 2021-11-15-ec76affcc987efbf172b7da0b05df711b48fa535
Additionally, attach any relevant sections from the log files above.

@MlovehebeE ,Thanks for posting this issue, could you please provide the error log:
D:\vcpkgmanage\vcpkg\buildtrees\influxdb-cxx\config-x64-windows-out.log

@MlovehebeE ,Can you install this port successfully?

@MlovehebeE ,Has this problem been sloved?

Thanks for posting this issue. Please reopen this issue if it still be a problem for you.


Add new Solidus/ReimbursementHookDeprecated cop

Add new Solidus/ReimbursementHookDeprecated cop

Closed PR with discussion https://github.com/nebulab/rubocop-solidus/pull/8

Hi @piyushswain I had to close the other PR since I messed up the fork sync. I looked at the notes on Solidus and the usage is treated as an array with :

reimbursement_success_hooks.any?
reimbursement_success_hooks.each

Please add these statements into the spec and check if the cop is working or not


Allow specifying envelope_ids in get_envelope_statuses

The API allows querying a list of specified envelope IDs. This needs to be specified to the slice arguments list.

Thanks for this PR! I'll try to take a look at it in the next few days and get it merged in.

Merged, thanks @amit !


[Suggestion] Option to Show Window While UI is Hidden

This suggestion proposes a checkbox that would allow Customize+ to stay open even when the UI is hidden (such as when you press Scroll Lock). This checkbox would probably go in the Interface section of the Settings tab.
This would make it easier to observe adjustments to your body without the UI (e.g. your hotbars) obscuring the changes.

Implemented in current testing build.


feat: add settings page

add settings page
move api keys to it
reuse nav and navlink where possible

fixes FTD-1768

📝 Changed routes:

/dashboard/api-keys
/dashboard/contracts

(view full size)
(view full size)

/dashboard/wallet
/settings/api-keys

(view full size)
(view full size)

/settings

(view full size)

Commit a4fe3973be9e7e800e7731fa3e52e086b37abd5a (https://thirdweb-hxc0cstvh.thirdweb-preview.com).


Corruption of SD card on "erase all"

Original report by Brian Calder (Bitbucket: brian_r_calder, ).

If the code attempts to erase all of the log files on the SD card, it can occasionally cause some damage to the file system that results in the card appearing to work (e.g., in a computer), but stops the logger from booting for some reason.  This needs not to be the case!

Original comment by Brian Calder (Bitbucket: brian_r_calder, ).

Resolved in 1.3.0


Add cropped_image control support

Closing to #806

I'm going to rebase my branch

Looks good to me!
Merging. :+1: