Widget ID clashes

I am using the WorldInspectorPlugin like this:
    #[cfg(debug_assertions)]
    app.add_plugins(WorldInspectorPlugin::new());

Started seeing these errors:

Could this be related to my code?

I also started seeing these after upgrading a random old toy project from bevy 0.7.
Super simple cargo
[dependencies]
bevy = {version = "0.12.0"}
bevy_egui = "0.23"
bevy-inspector-egui = "0.21"
rand = "0.8.5"

I'm spawning a grid of entities under a parent entity and it seems that the inspector id clashes only start to show up when the grid is >= 13*13


Check connectivity of graph generated by probabilistic_graph_builder

The number of nodes in graph generated by probabilistic_graph_builder is given as an input by the user or computed automatically based on the workspace size. In case of complex workspaces, a graph generated in such a manner might not be connected and therefore a path cannot be found. Fix this by checking connectivity of the graph and adding more nodes if required.

Issue fixed. Refer to commit d96edda


[WIP] Prototype for image crop

How to test this feature

create a news item.
select the image field.
you are able to see the crop image feature just select the area which you needed and click on save.

@iFlameing looks good! Can you set an image ratio of 4:3? Saving the image currently does not work but I guess you are aware of this.

@tisto I am unable to fix the eslint error regarding
 missing dependency warning when using useEffect React Hook?

I found the problem because we are passing prop function to useEffect.
I tried to disable it but somehow I am unable to do so
// eslint-disable-next-line react-hooks/exhaustive-deps

@tisto fixed :)

@iFlameing Please use loadables for the image crop lib

@plone/volto-team to preserve the uncropped original image, we need an additional field for the uncropped image on every single image that we have in Volto/Plone. I created a PR for the preview_image in kitconcept.volto:
https://github.com/kitconcept/kitconcept.volto/pull/11
The question here is "do we want to bake in image cropping into Volto/Plone core or not"?

@plone/volto-team to preserve the uncropped original image, we need an additional field for the uncropped image on every single image that we have in Volto/Plone. I created a PR for the preview_image in kitconcept.volto:
https://github.com/kitconcept/kitconcept.volto/pull/11
The question here is "do we want to bake in image cropping into Volto/Plone core or not"?

Closing this PR and marking as "Abandoned".
This feature became uninteresting for the community.
If someone is interested in rescuing it, you can take it as a reference and open a new PR.

@sneridagh I think image cropping is an essential feature for a CMS and should be one of our top priorities. However, I agree that we might have to start over again.


tf.lite.experimental.load_delegate throws exception with try except block

Please make sure that this is a bug. As per our
GitHub Policy,
we only address code/doc bugs, performance issues, feature requests and
build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): ubuntu 18.04, macOS 10.14.6
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:NA
TensorFlow installed from (source or binary):binary
TensorFlow version (use command below): v2.1.0-rc2-17-ge5bf8de 2.1.0 & v2.2.0-0-g2b96f3662b 2.2.0
Python version:3.7.6
Bazel version (if compiling from source):NA
GCC/Compiler version (if compiling from source):NA
CUDA/cuDNN version:NA
GPU model and memory:NA

You can collect some of this information using our environment capture
script
You can also obtain the TensorFlow version with:

TF 1.0: python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
TF 2.0: python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"

Describe the current behavior
Currently tf.lite.experimental.load_delegate throws OSError when the passed in library doesn't exist. However when use it with try except block, it will throw

Exception ignored in: <bound method Delegate.del of <tensorflow.lite.python.interpreter.Delegate object at 0x7f6fc561db00>>
Traceback (most recent call last):
File "/usr/local/lib/python3.6/dist-packages/tensorflow/lite/python/interpreter.py", line 125, in del
if self._library is not None:
AttributeError: 'Delegate' object has no attribute '_library'

Describe the expected behavior
Exception should be caught with try except block.
Standalone code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate
the problem. If possible, please share a link to Colab/Jupyter/any notebook.
Without try except block, the behavior looks fine
import tensorflow as tf

tf.lite.experimental.load_delegate('some invalid lib')  # expect an exception

With try except block, it throws an exception which can't be caught.
import tensorflow as tf
try:
    tf.lite.experimental.load_delegate('some invalid lib')
except Exception as e:
    # do something to handle exception
    pass

Exception ignored in: <bound method Delegate.del of <tensorflow.lite.python.interpreter.Delegate object at 0x7f6fc561d518>>
Traceback (most recent call last):
File "/usr/local/lib/python3.6/dist-packages/tensorflow/lite/python/interpreter.py", line 125, in del
if self._library is not None:
AttributeError: 'Delegate' object has no attribute '_library'

Other info / logs Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached.

I am able to replicate this issue, please find the gist here

Nupur, could you take a look?

You may try with;
import tensorflow as tf
try:
    tf.lite.experimental.load_delegate('some invalid lib')
except tf.errors.InvalidArgumentError as e:
    # do something to handle exception
    pass


Creating a Oceananigas Utils package or using LESbrary

So, I've been meaning to clean up some of my scripts and possibly creating some utilities for Oceananigans. I'm not sure if I need to do this somewhere else or if I can use LESbrary.jl, though.
I'm not sure because LESbrary.jl has some of those utilities already and it would make sense to use an already-existing repo for that, but supposedly everything here is focused on LES, which is just part of what Oceananigans can do.
For example the nice progress messenger in LESbrary is great. All I have to do to make it general is to change the ν_e line. Other things that would be nice to have stored somewhere are simple common sponge layer options (we could even move the gaussian mask from Oceananigans to avoid code clutter). But these are things that don't necessarily pertain to LES.
Anyway, I was wondering what your thoughts are.
CC: @ali-ramadhan @glwagner

There's some precedent for a Utils.jl package, e.g. https://github.com/fonsp/PlutoUtils.jl and https://github.com/JuliaML/MLDataUtils.jl.
I definitely wouldn't be opposed to an OceananigansUtils.jl package to collect user-contributed niceties. I guess right now I can only think of the progress messenger going in there to start, but it could grow organically to include lots of useful stuff.


Revert "Use macos to run the rc workflow"

Goal

Testing

Release Notes

WHAT:
WHY:
WHO:

#792  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @bidetofevil and the rest of your teammates on  Graphite


Question: How can I make a completion for filetype A  available for different filetype B?

Telekasten uses markdown files, but has its own fileteype and hence the markdown snippets are unavailable. How can i make snippets for md available for telekaten filetype ?

You can use ls.filetype_extend, in your case probably ls.filetype_extend("telekasten_filetype", {"markdown"})


feat(web): Integrate trusted types into Vue

Trusted Types
Trusted Types (spec, introductory article) is a new experimental DOM API implemented within the WICG , with a working Chrome implementation.
The API creates a few new objects available on the global object in the browser, like most other web APIs (impl in TS and in Closure compiler).
Under certain conditions, controlled by a HTTP header (analogous to Content-Security-Policy behavior), the API can enable the enforcement - then it changes the signature of several DOM API functions and property setters, such that they accept specific object types, and reject strings. Colloquially, DOM API becomes strongly typed.
For example, with Trusted Types Element.innerHTML property setter accepts a TrustedHTML object.
Trusted Type objects stringify to their inner value. This API shape is a deliberate choice that enables existing web applications and libraries to gradually migrate from strings to Trusted Types without breaking functionality. In our example, it makes it possible to write the following:
const policy = TrustedTypes.createPolicy('foo', {
  createHTML: (s) => { /* some validation*/; return s}
});

const trustedHTML = policy.createHTML('bar');
anElement.innerHTML = trustedHTML

anElement.innerHTML === 'bar'

The above code works regardless if the Trusted Types enforcement is enabled or not.
Reading from the DOM is unaffected, so Element.innerHTML getter returns a string. That's for practical reasons -- web applications read from DOM more often than they write to it, and only writing exposes the application to DOM XSS risks. Typing only the setters allows us to secure web applications with minimal code changes.
Integrating Trusted Types to Vue
The integration is fairly simple as there are not many places which break when using Vue with Trusted Types. There one place though, which I am not sure if it's even called (couldn't trigger it myself). It's marked in a code with TT_TODO: ... comment. I hope someone can clarify this for me. The PR doesn't introduce any breaking changes. All of the code is applied only when the trustedTypes API is available in the global object.
What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[x] Feature
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[x] It's submitted to the dev branch for v2.x (or to a previous version branch), not the master branch
[x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[x] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
[x] New/updated tests are included

If adding a new feature, the PR's description includes:

[x] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:
The PR adds support for Trusted Types only on client side, but it might be beneficial to use them also on server side. There is no DOM on server side, however we can check if the values are trusted before creating markup with dangerous attributes. This also makes the applications render the same thing on the server and on client. There is already a similar PR for this for React.
If you would like to try this change there is a really simple application with the instructions how to setup vue locally in which you can play with Trusted Types. Vue cli uses webpack for development which provides features like hot-reloading. This currently breaks, but the PR is already fired and we are waiting for review.

@yyx990803 Are the broken tests caused by my feature? They seems pretty unrelated...

Are there any plans to integrate this into vue?

@Siegrift Is it still in progress?
I arrived at this PR from the following description.
https://github.com/w3c/trusted-types/wiki/Integrations#:~:text=jQuery%3A bug-,VueJS%3A Pull request,-Next.js%3A

Hi, thanks for the interesest.
This PR got quite stale since I first opened it. The integration implementation would likely need to be revisited now. I am not sure whether Vue is interested in having this change merged.

I think it's best to close this PR and re-implement it.

No idea, sorry.


Implement Component for WASM FakeTask

Objective

WASM users cannot place async task futures into a component for detaching.
This example does not work for WASM due to this issue: https://github.com/bevyengine/bevy/blob/latest/examples/async_tasks/async_compute.rs
Although in the WASM case, there is no result in the task future's output. Instead, it provides a detach() function.
See: https://discord.com/channels/691052431525675048/937158127491633152/947323394515410946
...with the CI error here: https://github.com/Earthmark/nothing_moves/runs/5346983870?check_suite_focus=true

Solution

Like Task, implement Component for FakeTask on the wasm32 target.

I agree, neither Task or FakeTask should be component, and the example should use a wrapper type 👍

Closing this out, following the direction taken in #2982.


[Storage][File] Api listing

File api: storage-file.api.ts
Generated models: generated/models/index.ts

/cc @bterlson

Closing this PR as the corresponding package has been released to GA.


Button text color adopts background color after upgrading to Angular Material 18

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
After upgrading to Angular and Angular Material version 18.0.0, the button text color incorrectly takes on the button's background color, making the text unreadable. This issue did not exist in version 17.0.0.

Reproduction
StackBlitz link:  https://stackblitz.com/edit/stackblitz-starters-xswcad?file=src%2Fcustom-theme.scss,src%2Fcolor.scss,src%2Fmain.ts,src%2Fglobal_styles.css
Steps to Reproduce:

Set up a new Angular project with Angular 18 and Angular Material 18.
Implement a button using Angular Material components.
Apply a custom theme to the button with specific text and background colors.
Observe that the button text color adopts the background color instead of the specified text color.

Expected Behavior
The button text color should remain distinct from the background color as specified in the theme settings.
Actual Behavior
The button text color adopts the button's background color, making the text difficult to read.
Environment

Angular: 18.0.0
CDK/Material: 18.0.2
Browser(s): chrome
Operating System (e.g. Windows, macOS, Ubuntu): Window

See https://stackoverflow.com/a/78617559/5470544
In your custom palettes, you are using the same colors for hue and contrast. You should choose either black or white as contrast color, depending on which color gives best contrast. This is not an issue with Angular Material.

Closing since it looks like the palette wasn't defined correctly. Note that you can also generate a custom theme by running ng generate @angular/material:m3-theme.


upgrade: block upgrade when rgw multisite is active

With this commit, upgrading a cluster from Nautilus to Pacific with
active rgw multisite replication will be blocked.
This is because a lot of bugs are currently present in Pacific regarding
RGW multisite.
Closes: https://bugzilla.redhat.com/show_bug.cgi?id=2063702
Signed-off-by: Guillaume Abrioux<EMAIL_ADDRESS>

jenkins test centos-container-update

jenkins test centos-non_container-update

jenkins test centos-non_container-all_daemons

jenkins test centos-container-update

jenkins test centos-non_container-all_in_one

jenkins test centos-container-all_in_one

Hi @guits
Are these pacific multisite bugs still open ?
Are they specific to cephadm ?
Is it using ceph-ansible rolling_update from nautilus to octopus and then to pacific then a better approach?
Thanks in advance.
Cheers
Francois

Hi @guits
Are these pacific multisite bugs still open ?

Reverting this in #7214

Are they specific to cephadm ?

Not that I know.

Is it using ceph-ansible rolling_update from nautilus to octopus and then to pacific then a better approach?

"is" = what?
Not sure I'm understanding your question but yeh the common upgrade path looks like this (N to O, O to P, P to Q...)
Thanks!


Use login credential for deployment

How-to:

Get a credential by new GoogleLoginService().getActiveCredential().
This may require exporting classes in the .login bundle (by changing MANIFEST.MF) and adding a jar in .login/lib in the .deploy project setting.
This can open a login browser. (We can change this behavior if desired.)
Check if the returned credential is null.
Write the credential to a file.
Use the GoogleLoginService.getJsonCredential() helper method first to get a JSON in String.
GoogleLoginTemporaryTester has an example of writing it to a file.
When calling gcloud, give the option --credential-file-override=<credential file>
In app-tools-lib, this is done by calling CloudSdk.Builder.appCommandCredentialFile().

To do actual testing, we need to set a client ID and a client secret. I've been doing it with IntellJ's ID and secret.


Support installing executables from PIP package

This is v2 of #27.
Changes from v1 is:

avoid failing to build .rpm when there is no /usr/bin symlink (which means --pip-symlinks did not passed)

Currently, PIP module implementation does not support installing
executables which usually installed at /usr/local/bin/.
To implement installing PIP executables, adding following features:

rewrite shebang to #!/usr/bin/env python3
generate python thunk for the executable
create symlink to /usr/bin

See scylladb/scylla-machine-image#340
Signed-off-by: Takuya ASADA<EMAIL_ADDRESS>

Note that we also need to merge https://github.com/scylladb/scylla/pull/10748
to add /usr/bin/scylla-api-client symlink.

@avikivity ping


Full Design for Container/SpaceView/Entity default+override rules

The original plan for entity overrides only covered overriding of components for visualizers.
We would like to expand this design to also include defaults and/or overrides not just of visualizers, but also of space-view properties, possible sourced from containers.
For example: set the default view coordinates for all space-views to Z-up.
This issue should include:

Clearly articulated description of the different mechanims of override and how they interact
Python API concept for all mechanisms of override
Figma UI concept for all mechanisms of override

This issue does not cover implementation .

I think we figured all these things out quite well by now and even implemented a fair chunk. It's a bit scattered accross figma documents and issues, but it's there.
The only thing we haven't fully formulated is doing overrides/defaults on contains, but that doesn't seem super challenging from where we are (but also we deprioritized this part)


How can I input this symbol?

I have a tiny question at this point. How can I input a symbol like this?

Thanks very much!

I couldn't find it in the #sym general symbols library, so this is a hacky way of achieving a similar result with the help of limits()_lower^upper. There might be better ways to achieve this.
#let implies_star = $limits(arrow.r.double) ^ ast.op$
$ x #implies_star y $

As far as I'm aware, this is not a unicode symbol, so @Az-21 solution is the best you'll get


Set CeloDEX fee to 0.2%

See https://github.com/polydex-fi/polydex-swap-core/blob/main/contracts/PolydexPair.sol#L180-L181
https://polydex.medium.com/introducing-polydex-6298cd17fb42

I have tried this before and 0.998 is throwing errors. I don't think they have deployed same contracts to Celo as they have on Polygon. Unfortunately contracts aren't verified so we cant tell what they have deployed.
Setting it to 0.998 causes errors, you can test using cli:

yarn ts-node ./src/cli/cli.ts --input CELO --output cUSD --registries celodex --amount 1 --max-slippage 0.999999

Deployed contracts not source verified feels like a huge red flag if they're also not using the same fee rates.
Who knows what other modifications were made to the CeloDEX version...

I tried to talk to the CeloDEX people asking about what fee percentage, and asking them to verify their deployed contracts.
They're clueless AF and don't even know what contract verification is, either straight up playing dumb, or trying to hide something.

I tried to talk to the CeloDEX people on discord about the fee percentage, and asking them to verify their deployed contracts.
They're clueless and don't even know what contract verification is, either straight up playing dumb, or trying to hide something.

I tried to talk to the CeloDEX people on discord about the fee percentage, and asking them to verify their deployed contracts.
They're clueless and don't even know what contract verification is, either straight up playing dumb, or trying to hide something.

Yeah, I wouldnt provide liquidity to a pool that doesnt have contract verified. But it should still be more or less safe for swapping since output is always checked in swappa router at the end.


Not allowed to reboot system like normal after update

Do you have any of the following that you could give?

Logs
Version numbers
Detailed description
System information

Sounds like the same issue I had when updating a Lenovo IdeaPad Flex 3 to Chrome OS v91.0.4472.165 (64bit) a few days ago (on a machine with Crouton installed where all had been working well before - Crouton was installed only a few weeks ago using the current version with manual fixes for the CRAS audio problem:, as per Issues #4506 #4507).
After allowing the Chrome OS update to download a notification indicated that the system needed to reboot to complete installation, which I accepted.
When I tried 'Ctrl-D' in the boot menu, the machine froze on a white screen with the Chrome logo.
After 10+ min pauses, I tried restarting several times (using power button) with the same result.
I then left it overnight on the frozen screen, but it did not resolve.
I eventually had to take the 'Space key' boot menu option to revert the machine to factory settings (then set up Chrome OS from scratch, back in non-developer mode).
(I haven't been game to reinstall Crouton yet - I'm waiting to see how wide-spread the problem is, and whether a fresh install of Crouton will work).
There are no logs to report - everything was wiped in the factory reset.

Closing. OP not responding, no follow-up (needed) at this time.
-DennisLfromGA


gopass get should show command does not exist

Summary
gopass get shows that a secret is not found which is misleading as this command does not exists at all.
Steps To Reproduce
$ gopass get apikey
⚠ Entry "get" not found. Starting search...
[ 0] test1/apikey
[ 1] test2/apikey

Found secrets - Please select an entry (q to abort) [0]: 0
0
test1/apikey

Error: key not found in entry

$ gopass show apikey
⚠ Entry "apikey" not found. Starting search...
[0] test1/apikey
[1] test2/apikey

Found secrets - Please select an entry (q to abort) [0]:
0
test1/apikey
Secret: test1/apikey

*** ACTUAL SECRET VALUE ***

Expected behavior
gopass get should render gopass help
Environment
$ gopaas version
 gopass 1.12.5 (2021-03-27 22:25:42) go1.16.2 darwin amd64
<root>     - gpg 2.2.27 - git 2.31.1
Available Crypto Backends: age, gpgcli, plain
Available Storage Backends: fs, gitfs

That a consequence of allowing to use of gopass entryname as a shortcut for gopass show entryname.
We could create a deny-list  of invalid commands that show the help, but where to stop? Not sure it's really needed.

Well, if it's a shortcut then this is a bug as you can see it does not work.
It displayed the list of matching entries and even though 0 option was selected, it said the secret did not exist.

No, this is working as intended.
I did try to remove this shortcut, that got a lot of backlash and then we agreed to keep the shortcut.
But that means we can't fix your issue.

I'm sorry but I don't understand.
You are saying that it is shortcut for gopass show entryname - I just showed you above it does not work.
It seems to behave like it, but it does NOT find the secret, while when using gopass show entryname directly in the first place - THEN it works.

Yes, that's because get doesn't exist, it's not a shortcut.
The shortcut is using gopass alone. So here, what's happening is that gopass thinks your are running:
gopass show get entryname, so it is showing you the key "entryname" of the secret named "get", but you don't have any entry named "get" so it doesn't work.

@AnomalRoil almost, but still wrong. Take a look at what exactly the output looks like.

gopass get whatever
it says: ⚠ Entry "get" not found. Starting search... - that is fine
then it shows you a list of secrets it found and asks you for selection
then I select "enter" (or 0)

even though I selected an existing secret, it said secret not found - still a bug.

Actually no, look at the error it gave you at the end:
"Error: key not found in entry"
It didn't find the key "apikey" in the entry "test1/apikey" it used after
you chose it.
Run gopass show get apikey and you'll see it has the same behaviour.
Here is what gopass tries to do:

it parses the input "get apikey", sees no known command since "get" is
not a command, so it uses the default "show" command, and runs "gopass show
get apikey" instead.
"gopass show get apikey" is a command with a command, "show", followed by
an entryname "get", and an optional "key" parameter, to be able to use the
key-value feature. Here, since that optional parameters seems set to
"apikey", gopass will attempt to parse the content of your secret "get"
according to our doc:
https://github.com/gopasspw/gopass/blob/master/docs/commands/show.md#parsing-and-secrets
since gopass didn't find an entry named "get", it prompts you with an
interactive search, but it didn't forget about the fact that you requested
the value of the key-value named "apikey" in that entry, so once you
selected the "test1/apikey" entry instead of the "get" entry, gopass goes
on trying to access the value of the key "apikey" in that entry.
But since your entry does not contain a line with "apikey: something", it
fails to find the key "apikey" in that entry "test1/apikey" you selected,
and gives you the error message you had, saying it didn't find the key in
the entry.

Wow... that's very unintuitive behaviour, at least for me.
If you consider this to be 'as designed' then let it be, but I wouldn't be surprise when someone else has the same feeling as me in the future :-)
I appreciate your time and effort taken for your explanation though!

You should try using the key value feature, it is useful and it helps making sense of the behaviour:
gopass generate lets/test
gopass insert lets/test user
gopass generate lets/test recovery

gopass lets/test
gopass lets/test user
gopass show -C lets/test recovery

My point is: I understand your confusion and was once trying to resolve that by removing the "shortcut", i.e. the implicit "show" when running gopass <entry>.
Unfortunately that means we'll have to keep the confusing status quo.
I'm not saying we can't improve the error messages. I'm happy to take suggestions on that. But the behaviour itself won't change (most likely).

Sure, I get that, thanks a lot for the background.
I actually was not aware of the key/value feature inside a secret (aka path) - and that shortcut transforms it silently to a lookup for key what is confusing.
No idea how to improve the message though..., the only thing I can think of is:  Couldn't find key "get" in "test1/apikey"


Update incorrect version in description

The problem of $? being reset to true after parentheses occurs in
PowerShell version 6 and earlier, not 5 and earlier.

This is probably a good chance to test if my PR settings are right too lol


Fixed the issue for gesture's being added twice

1.Fixed the issue for gesture's being added twice:
When a push behaviour happens, the toVC add a gesture; when a pop behaviour happens, the toVC should remove the added gesture first, then add a new one. The old code just added gesture twice.
2.Removed unnecessary variable and dealloc  method:
UIView will remove all its gestures when dealloc automatically, so it's no need to remove the added gestures. Furthermore, the CEBaseInteractionController is used as a singleton, its dealloc  method will never get called.

Great fixes - thanks


Couldn't acquire D-Bus name.

Problem
using the latest bluealsa.service file from the repo I cannot get it to run as bluealsa
I get this in the log and it fails to run:
bluealsa: W: Couldn't create storage directory: No such file or directory
bluealsa[10982]: bluealsa: E: Couldn't acquire D-Bus name. Please check D-Bus configuration. Requested name: org.bluealsa

If I change the user to root, it runs
bluealsa[11757]: bluealsa: W: Couldn't create storage directory: No such file or directory
systemd[1]: Started BlueALSA service.

Are there any changes that need to be made to the journalctl config file?
Setup
Running on an Rpi running armhf binaries on armv6 hardware the OS distribution and version
# uname -a
Linux kitchenrune 6.1.21+ #1642 Mon Apr  3 17:19:14 BST 2023 armv6l GNU/Linux
# bluealsa -V
6837b54
# bluetoothd --version
5.55
# aplay --version
aplay: version 1.2.4 by Jaroslav Kysela<EMAIL_ADDRESS>

bluealsa: W: Couldn't create storage directory: No such file or directory

looks like some issue with build configuration, perhaps the service unit file needs the storage directory configured to account for $prefix.
From the issue template Setup section (my emphasis in bold italics):

if self-built from source, please state the branch, commit and used configure options

Then we can try to reproduce this error to understand it properly

bluealsa[10982]: bluealsa: E: Couldn't acquire D-Bus name. Please check D-Bus configuration. Requested name: org.bluealsa

your installation is either incomplete or broken. Maybe related to the above, maybe not.

The error message lacks path information (I will add such info, so it will be easier to resolve such issues in the future). But you can use strace to check which syscall has failed - you will see the path in the strace output. Most likely there is no "base" directory for bluealsa's mkdir().

When using the latest systemd service unit file, the storage directory should have been created, with appropriate permissions, by systemd. That's why I suspect the unit file may not be configured correctly to match the path required by the bluealsa daemon.
Relying on bluealsa to create its own storage directory would require it to have root privileges, which is something I think we should try to avoid.

Looking at the systemd docs,  I see that the environment variable $STATE_DIRECTORY is set for the main process to find the runtime parent directory that systemd has used for its state files. Perhaps the bluealsa daemon should use that environment variable if set, overriding the value given at configuration time?

@gearhead I've just re-read your question, and I noticed the wording used here:

using the latest bluealsa.service file from the repo

Does that mean you are using a systemd unit file and D-Bus policy file from an OS distribution repository, or are you using the ones from this project source code repository? If the former then you really need to seek help from the OS - this project has no control over what files or config options are used by distributions.

Looking at the systemd docs, I see that the environment variable $STATE_DIRECTORY is set for the main process...

I've just pushed a change which will check STATE_DIRECTORY in case when bluez-alsa was configured with --enable-systemd. I hope this will solve this issue.

@arkq Sorry for being incomplete. I am building from source. I am using the examples here in this source code repo for the service files and D-Bus policy. The configure options I use are:
  flags=(--with-libopenaptx
         --enable-ldac
         --enable-mp3lame
         --enable-cli
         --enable-aac
         --enable-manpages
         --enable-systemd
         --enable-aptx-hd
         --enable-faststream)
  ./configure --prefix=/usr \
      --sysconfdir=/etc \
      "${flags[@]}"

I am using the service file from here as a guide but made a couple additions:
https://github.com/arkq/bluez-alsa/blob/master/misc/systemd/bluealsa-aplay.service.in
[Unit]
Description=BlueALSA service
Documentation=man:bluealsa(8)
Requisite=dbus.service
After=bluetooth.service

# In order to customize BlueALSA D-Bus service one should create an override
# for this systemd unit file. Please note, that in the override file one will
# have to explicitly clear the ExecStart before setting it again. See the
# bluez-alsa wiki for more options.
#
# $ sudo systemctl edit bluealsa
# [Service]
# ExecStart=
# ExecStart=@bindir@/bluealsa -S --keep-alive=5 -p a2dp-sink

[Service]
Type=dbus
BusName=org.bluealsa
User=root
EnvironmentFile=-/etc/default/bluealsa
ExecStart=/usr/bin/bluealsa $OPTIONS
Restart=on-failure

# Sandboxing
AmbientCapabilities=CAP_NET_RAW
CapabilityBoundingSet=CAP_NET_RAW
IPAddressDeny=any
LockPersonality=true
MemoryDenyWriteExecute=true
NoNewPrivileges=true
PrivateDevices=true
PrivateTmp=true
PrivateUsers=false
ProtectClock=true
ProtectControlGroups=true
ProtectHome=true
ProtectHostname=true
ProtectKernelLogs=true
ProtectKernelModules=true
ProtectKernelTunables=true
ProtectProc=invisible
ProtectSystem=strict
RemoveIPC=true
RestrictAddressFamilies=AF_UNIX AF_BLUETOOTH
RestrictNamespaces=true
RestrictRealtime=true
RestrictSUIDSGID=true
SystemCallArchitectures=native
SystemCallErrorNumber=EPERM
SystemCallFilter=@system-service
SystemCallFilter=~@resources @privileged
UMask=0077

# Setup state directory for persistent storage
ReadWritePaths=/var/lib/bluealsa
StateDirectory=bluealsa

[Install]
WantedBy=bluetooth.target

I've just tried configuring with your options, and I find:
$ grep localstoragedir config.log
localstoragedir='/usr/var/lib'

So that explains why bluealsa is not finding its storage directory. I'm thinking that is probably an error in the configure.ac file, but will need to read up on it a bit more to be sure of how these standard directories are supposed to relate to a given $prefix.
However, as you are configuring with --enable-systemd, @arkq has now made a change (see comment https://github.com/arkq/bluez-alsa/issues/633#issuecomment-1519142510) so that systemd will override the compiled-in storage path and you will find that the latest code in Master will always use /var/lib/bluealsa/ when used with systemd.
As for the error

bluealsa[10982]: bluealsa: E: Couldn't acquire D-Bus name. Please check D-Bus configuration. Requested name: org.bluealsa

That is one of the common errors mentioned in the README, please read the troubleshhooting section in that for the possible causes. I suspect in your case it is the D-Bus policy file that is the problem. Had you used the configure option --with-bluealsauser=USER when configuring instead of editing the systemd service unit file by hand, then configure would have taken care of this. I am currently preparing updated installation and troubleshooting guides (PR #630) which contain instructions on how to configure D-Bus policy by hand, in the meantime there are several past issues which contain example D-Bus policy files, for example https://github.com/arkq/bluez-alsa/issues/629#issuecomment-1510150973

unless you want to modify configure.ac to remove the anomaly

I think that we should follow BlueZ project on that matter. The bluetoothd service also uses persistent storage, and also uses autotools. Since bluez-alsa is an "adjacent" project to bluez.org, I think that we should be consistent. I think that I've "copied" (I hope, correctly) the logic from bluez, so in that case I'll go with doc update.

I think I followed your instructions. I changed my build config:
flags=(--with-libopenaptx
         --with-bluealsauser=bluealsa
         --with-bluealsaaplayuser=bluealsa
         --enable-ldac
         --enable-mp3lame
         --enable-cli
         --enable-aac
         --enable-manpages
         --enable-systemd
         --enable-aptx-hd
         --enable-faststream)
  ./configure \
      "${flags[@]}"

and now it will run as bluealsa user.
I had already looked and traced and retraced my steps with the README instructions on the dbus-1 config, but did not get that it needed to be user=bluealsa, but now it all works. Thanks for the help!

I'm closing this issue as resolved, then.


support /lgtm in comment

Feature Request

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Describe the feature you'd like:
https://book.prow.tidb.io/#/plugins/lgtm?id=为什么我在使用-github-的-review-功能中的-comment-时填写-lgtm-无效？
I want /lgtm in the review comment identified. It's weird that we can /lgtm in a comment but can't in a review comment.
Do you have any ideas on how to implement it?(Optional)

@lichunzhu here is a proposal that revert this change and prefer native review approval action. https://github.com/ti-community-infra/tichi/issues/561


Migrating to pyproject.toml

#102
I have created and populated a pyproject.toml file. Existing configuration files have been preserved, though I did see fit to comment out the metadata in setup.py to ensure the generated installation is getting that information from the intended source. Similarly, workflows have been updated to reference the toml rather than setup.py or requirements files - e.g. installing dependencies using the dev option I created in project.optional-dependencies.
The new justbuild.yml served only to allow me to verify the generated build within GA since I obviously couldn't publish from my fork. Probably should just remove that before merging but preserved in case inspection of the generated dists are desired (uploaded as an artifact).

@cerrussell shall we remove setup.py instead of commenting out all lines? Would there be any issues with removing the file or leaving it unmodified?

@prabhu I don't see an issue with either of those options for this project. I will note that the tool.setuptools table within pyproject.toml is still beta. The significance of that here is that we have to specify the packages to include under tool.setuptools due to the project layout. Otherwise the setuptools backend attempts to auto-discover packages - which is another beta feature and did not work correctly when I tried it.
So basically using pyproject.toml depends on beta functionality and that gives me pause despite having no issues even when I remove the setup.py file.

@prabhu I removed setup.py. I'm happy to take a look at the vulnerability repo.

Thank you so much!


[Feature]: add imagePullSecret to k8sgpt crd spec

Checklist

[X] I've searched for similar issues and couldn't find anything matching
[X] I've discussed this feature request in the K8sGPT Slack and got positive feedback

Is this feature request related to a problem?
No
Problem Description
from this pr users can use other repositories (e.g. their own image) but imagePullSecrets does not added, so that user cannot use private repository.
Solution Description
add imagePullSecret name. and if it is given, add it k8sgpt serviceaccount imagePullSecret.
Benefits
users can use private repository
Potential Drawbacks
No response
Additional Information
No response

hey @AlexsJones I'd like to pick this up if possible. I can't join the slack channel to discuss using my email, if you could send over an invite that would be great!

@hfiorillo this is on review
https://github.com/k8sgpt-ai/k8sgpt-operator/pull/282


Auto created groups not displayed within an attendance item

In a site, create a manual group and a couple automatically created groups
In the Attendance tool, add a new item
Select that item
In the view drop down, select the manually added group
Participants display properly
In the view drop down, select one of the automatically created groups
No users display

Are you confirming that the auto-created group has members (outside of the Attendance tool)? Is there a step where the users get added? Clearing caches via Administration Workspace -> Memory?

I've confirmed the auto created groups do have members listed in them.  I cleared by cache via Admin Workspace->Memory and reloaded the Attendance tool.  The groups that were auto created still do not show in the tool.


Gitlab projects as DefectDojo products

Is your feature request related to a problem? Please describe
It is now possible to use Gitlab for authentication. It would be great to use it for allowing a user to find on DefectDojo a list of products matching his list of Gitlab projects, so that reports imported into DefectDojo can be related to the right product.
Describe the solution you'd like
As a user, when I log with Gitlab, I would like :

To find my Gitlab projects as DefectDojo products (products being created automatically)
Have the same visibility on DefectDojo products as on Gitlab projects, i.e.:

If I am authorized to see a Gitlab project, I see the matching DefectDojo product
If I am not authorized anymore to see a Gitlab project, I do not see the matching DefectDojo product

Describe alternatives you've considered
With Gitlab authentication, I get a Gitlab access token in DefectDojo social_auth_usersocialauth table, extra_data field. It is possible to use this token to interact with Gitlab API to get the list of projects I have access to. Here is an example of a social_auth_usersocialauth record :
+----+----------+-------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------+
| id | provider | uid   | extra_data                                                                                | user_id |
+----+----------+-------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------+
|  1 | gitlab   | 12345 | {"auth_time":<PHONE_NUMBER>, "access_token": "8f5989a2889eab91c816e1ef1f038f94e1bafa6ba42c9430ab526852341e056", "refresh_token": "24214b057580f67f9704f96f1ccb3e20cd3e140ad7998080354c12e2e722ac8d", "expires": null, "id": 12345, "token_type": "bearer"} |       2 |
+----+----------+-------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------+

This issue is linked with PR 2211, which is under review after recent commit

Can someone reopen this issue ? It should be fixed with https://github.com/DefectDojo/django-DefectDojo/pull/2211


BIP-70 Payment protocol: random address

BIP-70 says:

Merchant generates a unique payment address ...

But in this example merchant's address is hardcoded. Could you please point me the [right] way to do this?

Indeed, you need to manage private keys. There are a few ways to do it, you definitely don't want them on the same machine as your payment page. A HD wallet would do the trick here.
Your payment page would know the extended public key, and derive a new address for every request. You then watch for payment (it's probably best to have the payment requests expire) somehow, and act accordingly. You need to ensure your server is secure, lest someone replace the payment page with their static address, or change the xpub to one they control.
You would need to keep the extended private key elsewhere, perhaps just generating the private keys you know you received payment on, and moving the funds to a different wallet.

Did you get this sorted?

Thanks, @afk11! So, am I getting it right?

first of all I need to generate the private key with PrivateKeyFactory
then from PrivateKey instance I can get the public key and generate the address with AddressFactory
repeat for each request

I presume it's impossible to fetch the transactions history using this lib?

Not quite, read over BIP32 to some of it's features: you need to avoid creating private keys on your payments server.
Re fetching transaction history, it's not done in the library. I do have something written that can query electrum servers for this: https://github.com/Bit-Wasp/stratum-php or else you could use a block explorer API. Blocktrail has an API for creating webhooks for payments to an address, you can set the number of confirmations too IIRC.
Preparation:

Derive a HD root key, keeping the secret key material offline.
Put the HD master-public-key on the server

Accepting payments:

Generate next HierarchcalKey in sequence, incrementing a counter saved somewhere.
Take the address of your HierarchicalKey, pass to BIP70 stuff.

Person pays:

Your script gets notification somehow about a payment.
It emails you the address and counter.
Derive the private key from master private key and counter, and use a wallet to move the funds elsewhere.

Ok, thank you for the clarification!


Additional timeseries csv file validation

Pull Request Checklist:

[x] Positive Test Case Written by Dev

[x] Automated Testing

[ ] Sufficient User and Developer Documentation

[x] Passing Jenkins Build

[ ] Peer Code review and approval

Positive Test Case

Minimum data rows test: Create a composite resource. Upload a timeseries CSV file that has at least two rows of data. Create a timeseries aggregation from this uploaded CSV file. You should see a timeseries aggregation got created.
Date data format test: Upload a timeseries CSV file (to the composite resource you created above) which has none of the data values for the date/time column (1st column) in numeric format (e.g. of date in numeric format: '20180330'). Create a timeseries aggregation from this uploaded CSV file. You should see a timeseries aggregation got created.

@pkdash could you please e-mail me some CSV files that meet the Positive Test Case, so I may run the branch and review?

@cuahsimarko You can use this file: https://github.com/hydroshare/hydroshare/blob/3119-timeseries-csv-file-validation/hs_file_types/tests/data/valid_two_data_rows.csv


Fix linting

Please be as descriptive as possible, including: what is expected, why is this feature needed, what is the objective, etc.
What is the feature being requested?
Fix linting configuration to allow linting to pass and ignore the long lines we want to keep long

Some FYI information.
To run pylint, on the command line at top of qiskit-metal.
$ pylint qiskit_metal | tee  hold_output.txt
Metal repo has the .pylint file at
qiskit-metal/.pylint
A good file to compare Metal's pylint to is the pylint with Qiskit Terra.
https://github.com/Qiskit/qiskit-terra/blob/master/.pylintrc

There is a branch called "linting"

Fixed linting errors in the test module.

Everything has not been linted, but we have been linting as merging has been happening.


Napari progress throws if a description is set and it is disabled

🐛 Bug
napari.utils.progress throws an AttributeError if a description is set and it is disabled. This works in tqdm.
To Reproduce
To reproduce it:
# from tqdm import tqdm
from napari.utils import progress as tqdm

for z in tqdm(range(10), total=10, desc="Count to 10", disable=True):
    pass

This fails with:
Traceback (most recent call last):
  File "/home/pape/Work/playground/napari-prog/progress_napari.py", line 6, in <module>
    for z in tqdm(range(10), total=10, desc="Count to 10 again", disable=True):
  File "/home/pape/software/conda/miniconda3/envs/sam/lib/python3.10/site-packages/napari/utils/progress.py", line 88, in __init__
    if not self.desc:
AttributeError: 'progress' object has no attribute 'desc'

It works when using normal tqdm.
Expected behavior
The code should not throw the exception.
Environment
The napari and tqdm versions are (omitting the rest because irrelevant):

napari                    0.4.17          pyh275ddea_0_pyqt    conda-forge
tqdm                      4.65.0             pyhd8ed1ab_1    conda-forge

Additional context
This should be easy to fix here.
For example, one could add the lines
if self.disable:
  self.desc = ""

beforehand. I checked that locally and it fixes the issue.
I am happy to open a PR for this.

@constantinpape thanks for raising! I think your identified fix is correct, so please feel free to open the PR :blush:


view raw error

org.eclipse.jgit.errors.LargeObjectException: ae71c886bc48faa455c591f5199d059be01231b0 exceeds size limit
	at org.eclipse.jgit.internal.storage.file.LargePackedWholeObject.getCachedBytes(LargePackedWholeObject.java:98)

maybe this is same as #933

Merged with #933

yes， same as #933.
i need store release version. binaries over 100MB


User not setup (ERROR: No users found)

When I start the docker container, the user isn't being setup, resulting in error:
        ERROR: No users found. You need to create at least one user to log in.
        It is recommended to have at least one user with role Admin.
        FIX: create a user by running 'openvasmd --create-user=<name> --role=Admin && openvasmd --user=<name> --new-password=<password>'

I've found that in start script the instruction   echo "Setting up user" isn't being called so obviously the user is not present.
However, I've checked the tasks.db file (post-installation) and it is present.
Who creates tasks.db? Is it possible that we need to wait some time or move the check below after services have been started?

This should be resolved now. Please reopen if you still face this issue!


How to reset an in-memory database?

I'm creating tests for my app and before every test I need to reset the database to its initial form, since I have autogenerated PK columns.
Currently I'm doing this:
database = await $FloorAppDatabase.inMemoryDatabaseBuilder().build();
But the database I get is the same that I had before. Is there a way I can do this?

The obvious workaround would be a dao function which drops all data... But we should definitely look into why the in-memory db is not a new one. I'll try later.

We also have integration tests, e.g. here:
https://github.com/vitusortner/floor/blob/6209163750ed80c6f3a8ecd0401f1d51fdcbd41b/floor/test/integration/blob/blob_test.dart#L12-L35
As you can see we're also using an inMemoryDatabase and everything works as expected. This is of course only a simple case, we also have files with more than one test, everything works there, too.
So your use-case seems to be special(in the sense that it does not work :smile:). Could you share a bit more code if you still have problems, e.g. the important parts of your test?

Thanks for the response! Indeed, the tests of Floor really works.
I think is not a bug of Floor, so if you don't think this problem is related to this awesome plugin, please close the issue. Thanks.
I'm using GetIt and even tho the build method is called, the DB is the same.

GetIt locator = GetIt.instance;

const bool USE_TEST_IMPLEMENTATION = true;

void setupLocator() {
  locator.registerLazySingleton<LocatorDatabase>(() => LocatorDatabase());
}

void main(){
    setUp(() {
      setupLocator();
    });

    tearDown(() {
      locator.reset();
    });

   // my tests
}

class LocatorDatabase {
  bool _isInstanciated = false;
  AppDatabase _database;

  Future<AppDatabase> getDatabase() async {
    if (!_isInstanciated) {
      if (USE_TEST_IMPLEMENTATION) {
        _database = await $FloorAppDatabase.inMemoryDatabaseBuilder().build();
        List<dynamic> a = await _database.database.rawQuery('SELECT * FROM approach');
        //
        print('db created');
        a.forEach((e) {
          print(e);
        });
      } else {
        _database = await $FloorAppDatabase
            .databaseBuilder('app_database.db')
            .addCallback(callback)
            .build();
      }
      _isInstanciated = true;
    }
    return _database;
  }
}

Here's my output:

db created
{id: 2, name: Harry Potter}
{id: 3, name: Joana Dark}

This really doesn't look like a bug on our side, but I also can't make out why it would not work in your case.
But I'm not 100% sure. Do you have a minimal example which reproduces the behaviour? If not I can try to reproduce it myself but it might take a bit longer.

I noticed a difference: our integration tests close the database afterwards, your code snippet doesn't seem to do that.

Yeah it was that easy. hahaha... I thought the act of resetting get_it, and consequently the object that had the DB would re-create from 0.
Thanks a lot for your work on the plugin and your help!


Broken on Elixir 1.6

I'm seeing the following fails:
  1) test enqueue_in/2 with valid parameters (Sidewalk.ClientTest)
     test/sidewalk/client_test.exs:61
     ** (MatchError) no match of right hand side value: {:error, "Job must be a Sidewalk.Job with at least 'class' and 'args' set: %Sidewalk.Job{class: 'SomeWorker', args: ['bob', 1, %{foo: 'bar'}]} and a valid 'enqueue at' formated as unix timestamp"}
     code: {:ok, jid} = Sidewalk.Client.enqueue_in(%Sidewalk.Job{class: "MyWorker", args: [1,2,3]}, 120)
     stacktrace:
       test/sidewalk/client_test.exs:62: (test)

.....

  2) test enqueue_in/2 to write data correctly to redis (Sidewalk.ClientTest)
     test/sidewalk/client_test.exs:92
     match (=) failed
     code:  assert {:ok, _} = Sidewalk.Client.enqueue_in(%Sidewalk.Job{class: "MyWorker", args: [1, 2, 3], retry: false, queue: "foo"}, 60)
     right: {:error,
             "Job must be a Sidewalk.Job with at least 'class' and 'args' set: %Sidewalk.Job{class: 'SomeWorker', args: ['bob', 1, %{foo: 'bar'}]} and a valid 'enqueue at' formated as unix timestamp"}
     stacktrace:
       test/sidewalk/client_test.exs:93: (test)

It looks like this guard is failing: https://github.com/railsmechanic/sidewalk/blob/3f1a08a3d4d643016633cd0ba97d0241ae310e99/lib/sidewalk/client.ex#L64. Specifically enqueue_at_timestamp > 1_000_000_000.
What's special about this 1_000_000_000 number? Is it simply to see if a date is in the past?

1_000_000_000 is used in order to "filter" invalid timestamps

The error originates from getting an invalid the OS timestamp.


[Feature Request] Throw an error when calling characteristic.write*() functions without a properly encoded string

I know this is kinda dumb but I just spent more time than I'd like to admit having an issue with a device, where the only error was that I did this:
    const buffer = Buffer.alloc(1)
    buffer.writeUInt8(130, 0)
    await manager.writeCharacteristicWithResponseForDevice(
      deviceId,
      ServiceUUID,
      CharacteristicUUID,
      buffer.toString(),
    )

when the correct implementation was:
    const buffer = Buffer.alloc(1)
    buffer.writeUInt8(130, 0)
    await manager.writeCharacteristicWithResponseForDevice(
      deviceId,
      ServiceUUID,
      CharacteristicUUID,
      buffer.toString('base64'),
    )

I know how dumb that looks, and I'm so mad at myself for not noticing it earlier, but I believe that since the library needs to use Base64-encoded strings(due to limitations of RN I believe?), it should throw an error when it tried to write a non-base64 string. Hopefully that'd save time for future developers to not fall into the same trap I fell.
Thank you for your time, and thank you for your library by the way. It's great.

The documentation mentions that. Additionally, if you have Flowtype configured in your IDE it hints you about that as well. I'm not sure what can I do more about it.
Thanks for kind words :)


Invalid definitions

According to http://online.swagger.io/validator

http://online.swagger.io/validator/debug?url=https://apis-guru.github.io/api-models/trello.com/1.0/swagger.json
http://online.swagger.io/validator/debug?url=https://apis-guru.github.io/api-models/googleapis.com/storagetransfer/v1/swagger.json
http://online.swagger.io/validator/debug?url=https://apis-guru.github.io/api-models/watchful.li/1.0.0/swagger.json
http://online.swagger.io/validator/debug?url=https://apis-guru.github.io/api-models/plenigo.com/2.0.0/swagger.json
http://online.swagger.io/validator/debug?url=https://apis-guru.github.io/api-models/reactome.org/1.0/swagger.json
http://online.swagger.io/validator/debug?url=https://apis-guru.github.io/api-models/bbryiot.com/1.0.0/swagger.json

Trello has malformed url: "authorizationUrl": "https:\\/\\/trello.com\\/1\\/appKey\\/generate",

http://online.swagger.io/validator/debug?url=https://apis-guru.github.io/api-models/googleapis.com/cloudtrace/v1/swagger.json

adding validator badge to list view at http://darosh.github.io/angular-swagger-ui-material/hub.html

@darosh Thank you for reporting this issue. I need feedback in order to make this project better.
It's a problem with validator-badge.
Because properties isn't mandatory field, and it looks like this already fixed: https://github.com/swagger-api/swagger-parser/pull/165
So it will be fixed in the next release.
To valid specs I use sway because it provide a lot of additional validations.

@darosh I fixed trello locally and also notified its author.

@darosh By the way you can add logo for each API.
For example of how to implement it see this: http://apis-guru.github.io/
Here is source code: https://github.com/APIs-guru/APIs-guru.github.io

@IvanGoncharov thanks for crystal clear explanation, it is always good to know you have some validation in place
Regarding logos and hub:

they have various size, ratio and quality and in my opinion they would need some preprocessing not to be scaled in browser and perhaps merging into single CSS sprite image might be a good idea too
Google Books logo is outdated for example
hub.html
has no final design but I will probably prefer to keep it simple without logos, using the :rainbow: generator based on logo colors,
right now I just need the links to the Swagger UI I work on, maybe later I will change the cards into something expandable showing more metadata you provide in the list.json including logos...

@darosh

it is always good to know you have some validation in place

It's bigger showstopper I have for adding new APIs. I need to manually fix them before adding into the collection. You can see fixup patches here.

they have various size, ratio and quality and in my opinion they would need some preprocessing

If you use my API you actually using caching logos from here. So I already have mechanism for doing preprocessing, so I can scale non-svg images and provide them in couple of sizes.

single CSS sprite image

One image for all collection will be huge.
So right now you page is rendered from up to bottom and user don't care that some logo at botom of page still downloading. In case of packed logos user need to wait for all of them to download.
All my images are served from cache on github so browser reuse same connections and it's pretty efective already.

has no final design but I will probably prefer to keep it simple without logos

If you have some idea how I can make situations with logo better, feel free to suggest it here.
Obviously I can't manually process each logo, but I can make some preprocessing steps.


Resize inlined images

Following up on https://github.com/ascoderu/opwen-cloudserver/issues/3
We should resize the images that we inline in order to protect against people linking to super huge images and having the Lokole client consume too much bandwidth. We can just chose one reasonable dimension (e.g. 200px width) and then scale images to fit into that.
The image transformations can be done with the Pillow package (article).

NB: this should not only be applied to inline images but also to attached images. Ideally we'd write it in a modularized way so that we can cleanly add other space-saving optimizations in the future (e.g. for PDF or DOCX attachments).


Docker cannot run project

Hello, thank you very much for your work, but when I download docker image according to the instructions, some files will be missing,
python: can't open file 'reina. py': [Errno 2] No such file or directory

Thank you for your interest in our work!
Looks like there's a space in 'reina. py'. And could you double check ${PWD}/REINA in the command line is the right path for the repo?
Thanks!


release/v3.10.1 canary

deploy: update templates to v3.10.0
ci: update pr-commentor rules matrix
revert: revert to 3.10-canary
helm: add default false value for --enable-read-affinity
helm: update node plugin cluster role
rbd: updated node labels fetching logic
cephfs: fix network fencing admin id
deploy: use release repository for csi-resizer
build: create /etc/selinux/config in case it is missing
cephfs: fix fetchIP to support more formats
deploy: update templates to v3.10.1
revert: use v3.10-canary as work-in-progress version again

argh, gh command didnt pickup the right base branch automatically :disappointed:


[BugFix] Fix multi cross join can not extract best plan

What type of PR is this：

[x] bug
[ ] feature
[ ] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #6701
Problem Summary(Required) ：

Cross join only support broadcast join, the cost of its child which is broadcast enforcer could be infnite if it's output size exceed the MaxExecMemByte.

run starrocks_fe_unittest

run starrocks_fe_unittest

[FE PR Coverage check]
:heart_eyes: pass : 4 / 4 (100.00%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/sql/optimizer/cost/CostModel.java
4
4
100.00%


Added WePay blog post

This was authored by @criccomini and appeared originally on the WePay Engineering blog, and Chris agreed to cross-post on Debezium.

LGTM!

Nice!!
On Wed, Feb 22, 2017 at 3:35 PM, Randall Hauch<EMAIL_ADDRESS>wrote:

Merged #37 https://github.com/debezium/debezium.github.io/pull/37.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/debezium/debezium.github.io/pull/37#event-973445880,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADP0fFQh3Bv9sabJf7gjSfl99gxvmVLks5rfLgzgaJpZM4MJQh5
.

--
Christian Posta
twitter: @christianposta
http://www.christianposta.com/blog
http://fabric8.io


internal MQTT

Hi,
I´m using the internal Rhasspy MQTT Server without having a user/password but the App requires username/password.
Any Ideas?

user: user
pass: pass

I'm not able to connect to internal MQTT from the app at all - it should be running on 12883 - but i just get failed to connect.
any pointers?


Missing train.py

Thank you for your excellent work. I am very interested in your project. Can you upload the train.py file?

Thank you for your attention. We train all the models through the paddleseg framework from Baidu, so you can refer to here.

Thank your reply. I have another question: Can the concrete3k dataset be converted to coco data format?


Code update

What an excellent work!
May I ask when the train/eval code and pretrained models of the paper will be made available?

I apologize for the late response. The pre-trained models and the train/eval process have been updated, please refer to the README file for details. If you have any other questions, feel free to ask them here. However, please forgive me if my replies are sometimes delayed as I have a full-time job.

What an excellent work!
May I ask when the train/eval code and pretrained models of the paper will be made available?

I apologize for the late response. The pre-trained models and the train/eval process have been updated, please refer to the README file for details. If you have any other questions, feel free to ask them here. However, please forgive me if my replies are sometimes delayed as I have a full-time job.


complex option arguments

not sure what would be better, but I have arguments on an option of this nature:
--interval begin:end
where begin and end could be numbers, or an enum, or whatever. so it makes some sense to let parse convert the arguments to whatever by setting ":" as the separator.
Thus allowing
--interval :end
or
--interval begin:
if begin and end have default values (not necessarily managed by jopt).
so, for this to work, we need to detect the lone ":" and its position.
I'm happy with raw access to the argument string, and then manually testing for startsWith or endsWith.
optionally, allowing null valued arguments if the separator is detected seems ok.
and this opens up the opportunity for max arguments, as min arguments is toggled by #withOptionalArg and #withRequiredArg.
chris

Would value converters help you here?
public class IntervalArgumentTest {
    static class Interval<T extends Comparable<? super T>> {
        private final T from;
        private final T to;

        Interval(T from, T to) {
            this.from = from;
            this.to = to;
        }

        @Override
        public int hashCode() {
            return Arrays.hashCode(new Object[] { from, to });
        }

        @Override
        public boolean equals(Object o) {
            if (this == o)
                return true;
            if (o == null || !getClass().equals(o.getClass()))
                return false;

            Interval<?> other = (Interval<?>) o;
            return Objects.equal(from, other.from) && Objects.equal(to, other.to);
        }

        @Override
        public String toString() {
            return String.format("[%s, %s]", from, to);
        }
    }

    static class IntervalConverter<T extends Comparable<? super T>>
        implements ValueConverter<Interval> {

        private final Class<T> endpointType;
        private final Constructor ctor;

        static <C extends Comparable<? super C>> IntervalConverter<C> forType(
            Class<C> endpointType) throws NoSuchMethodException {

            return new IntervalConverter<C>(endpointType);
        }

        private IntervalConverter(Class<T> endpointType) throws NoSuchMethodException {
             this.endpointType = endpointType;
             ctor = endpointType.getConstructor(String.class);
        }

        public Interval<T> convert(String value) {
            String[] pieces = value.split(":", 2);

            try {
                return new Interval<T>(endpointFrom(pieces[0]), endpointFrom(pieces[1]));
            } catch (InstantiationException e) {
                throw new IllegalStateException(e);
            } catch (IllegalAccessException e) {
                throw new IllegalStateException(e);
            } catch (InvocationTargetException e) {
                throw new IllegalStateException(e);
            }
        }

        private T endpointFrom(String raw) throws InvocationTargetException,
            IllegalAccessException, InstantiationException {

            return endpointType.cast(ctor.newInstance(raw));
        }

        public Class<Interval> valueType() {
            return Interval.class;
        }

        public String valuePattern() {
            return null;
        }
    }

    @Test
    public void tryingOutValueConverterForIntervalArguments() throws Exception {
        OptionParser parser = new OptionParser() {
            {
                accepts("interval").withRequiredArg()
                    .withValuesConvertedBy(IntervalConverter.forType(Integer.class));
            }
        };

        OptionSet detected = parser.parse("--interval=2:4");

        assertEquals(new Interval<Integer>(2, 4), detected.valueOf("interval"));
    }
}

I recognize I could write a ValueConverter here, but the elements of the intervals already have ValueConverters, so it seemed logical to just use the result of OptionSet.valuesOf() as the interval container without writing any more code.
I also recognize this is a slight hack, but my thoughts having access to the raw arguments string would be widely useable, say in error messages etc.
Also didn't think it inconceivable that parsed argument arrays would have null values (or empty), in the same fashion String#split() works.
No worries otherwise, can definitely write another ValueConverter.

I think your best bet here would be to use an interval converter, with the endpoint converters plugged in if needed, and let it create intervals bounded on both ends or only one end based on the position of the colon in the arg (maybe a String#indexOf(':') check instead of String#split(":")). ValueConverters are the opportunity JOpt Simple affords to take raw string args and massage them into value objects of other types.
I think I see where you're going with having OptionSet#valuesOf() being able to, by convention or configuration, produce intervals. To my mind, it seems a case unusual enough to justify excluding it from the library.

My cli option/argument model isn't one-to-one with my internal model, so wrapping things in intermediate things (like a fabricated Interval object via a new ValueConverter) is just busy work to some degree.
Not arguing, just saying.
Once I sort out "intervals" are the right thing for this feature, i'll bang out more code to fine tune it, vs using the #valuesOf() result set for now. (you are probably seeing a trend here where I gravitate towards simple collections of things I can simply interrogate)
thanks!


404 Command not found

after installing  cleanup. when i run cleanup, i got /usr/local/bin/cleanup: line 1: 404:: command not found error. i had to download repo update this line sudo mv cleanup /usr/local/bin/cleanup to sudo mv cleanup.sh /usr/local/bin/cleanup in installer.sh and run the installer.sh. then it worked. hope this help if someone face similar error. Thanks!

curl -o cleanup https://raw.githubusercontent.com/fwartner/homebrew-mac-cleanup/master/mac-cleanup
chmod +x cleanup
sudo mv cleanup /usr/local/bin/cleanup

Fixed! Thank you!


[Docs] mesheryctl pages with subcommands are limited in the help they offer

Current State
Take this doc page as an example - https://docs.meshery.io/reference/mesheryctl/registry. The registry command doesn't perform any task unto its own. The power of this command lie within its subcommands, which are not listed or linked on this page, leaving the reader to go hunting for the real power of the command (its subcommands) back in the CLI index page - https://docs.meshery.io/reference/mesheryctl#meshery-registry-management
Desired State
List and link to each subcommand on each top-level command page.

Contributor Guides and Handbook

📚 Instructions for contributing to documentation

Meshery documentation site and source

🛠 Meshery Build & Release Strategy
🎨 Wireframes and designs for Meshery UI in Figma (open invite)
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

@alphaX86 do you mind undertaking this enhancement request?

@leecalcote ,can you please assign this issue to me?


TS incorrectly infers .map return type a chained transform is inlined

This is definitely a TS bug. Unfortunately haven't created a minimal repro yet, but I'm sure people will run into this when using the .map API.
import { type } from "arktype";

const original = type({
  bar: "number",
});

// correctly adds null to bar's value
const variableNullable = original.map((prop) => {
  //     ^?
  const nullableValue = prop.value.or("null");
  return {
    key: prop.key,
    value: nullableValue,
  };
});

// ignores the .or("null") and returns the original value
const inlinedNullable = original.map((prop) => ({
  //    ^?
  key: prop.key,
  value: prop.value.or("null"),
}));

Was able to work around this by adding NoInfer to chained type method returns per @Andarist's recommendation 🎉
See updated return types in https://github.com/arktypeio/arktype/pull/1133


Make authentication simpler

What we do today:
final KeyStore keystore = KeyStore.getInstance("PKCS12");
final FileInputStream fis = new FileInputStream("/path/to/key.p12");
keystore.load(fis, "password".toCharArray());
final PrivateKey key = (PrivateKey) keystore.getKey("privatekey", "password".toCharArray());

final AuthConfig ac =<EMAIL_ADDRESS>key);

final DatastoreServiceOptions options = DatastoreServiceOptions.builder()
    .dataset(datasetId)
    .authConfig(ac)
    .build();

final DatastoreService datastore = DatastoreServiceFactory.getDefault(options);

What we'd like to do:
final Credential credential = DatastoreHelper.getServiceAccountCredential(
<EMAIL_ADDRESS>"/path/to/key.p12");
final DatastoreOptions options = DatastoreHelper.getOptionsfromEnv()
  .dataset(datasetId)
  .credential(credential)
  .build();
final Datastore datastore = DatastoreFactory.get().create(options);

It is much simpler when running in GCP (AE or CE) when we "auto-detect" the dataset and use the instance credentials.
Though we should provide "helpers" for typical boilerplate code I am a little hesitant to add code that will work in some environment but not in other (e.g. The use of files (and providing a full path) is not going to work on App Engine). An alternative that may work for all would be to load the key bytes as a resource.
Also, the suggestion above is only going to work when the password for that keystore is fixed (e.g. "notasecret") so I think the helper should provide a way to supply a different password.
As for "getDatastoreFromEnv()" it is already partially imlemented, though in an implicit way. When DatastoreServiceOptions.Builder#build is called if a dataset was not provided the
"DATASTORE_DATASET" System property or Environment variable will  be considered. We should probably do that also for DATASTORE_NAMESPACE,
SERVICE_ACCOUNT, PRIVATE_KEY_FILE, PRIVATE_KEY_PASSWORD (looks like this could be generic for all gcloud services and not tied to datastore).
Also, env/property settings need to be documented (probably in the matching builder's setter or getter..).
BTW, if providing a way to configure auth via system/env properties do you still find much value in the programmatic helper (which is basically a "PrivateKey" helper...)

Commit https://github.com/GoogleCloudPlatform/gcloud-java/commit/a6cae121d3b1b713369ebc37caed919a8839324c is using now the new authkit library and when default are used (no explicit auth config settings) we will follow the gcloud authentication standard which includes using a file referenced by GOOGLE_APPLICATION_CREDENTIALS environment variable. jgeewax do you still think we need a helper for reading PK12 files in this case?

ping.

Now that we're using a JSON keyfile (right?), I think the simplest and happiest way to get a Datastore instance would be...
final Datastore datastore = DatastoreHelper.getOptionsfromEnv()
  .dataset(datasetId)
  .keyFile("/path/to/keyfile.json") // Optional if you are in GCE or GAE
  .buildDatastore();

Or something similar. Is that crazy?

Not necessarily. Do you mandate accept only json file in the other Veneer libraries (rather than also accepting a p12 key file as well)?
I was trying to see if I can extract the service email from the key (some information is there) but wasn't able to do it using the Java APis.
Using a path for a file is nice but java File is not accessible on all platform and also does not cover all options (e.g. it could be provided as a bundled resource). This is why I leave it for the user to construct the Key (as described above - we could actually have that as snippet as an example in the specific Auth config class javadoc).
Another option instead of File would be to accept a stream which is likely to support all various input type.
In that case these questions are still open:

Do we only support json file (for getting the service email) or should we support both file types.
Do we only work with keys that uses the default, notasecret, password?

I think we should keep discussion the other suggestion of creating the service directly from the options in #54.

Not necessarily. Do we mandate/accept only json file in the other Veneer libraries (rather than also accepting a p12 key file as well)?

Other libraries accept all of the options. Is it crazy to look up the file and check the extension, and then operate differently based on that? If so, then we could offer ... .p12Key('...') and jsonKey('...') right?

I was trying to see if I can extract the service email from the key (some information is there) but wasn't able to do it using the Java APis.

I was under the impression that you can't get the service account e-mail from a p12 key, which was the point of the JSON keyfile (it includes all the information needed).

Using a path for a file is nice but java File is not accessible on all platform and also does not cover all options (e.g. it could be provided as a bundled resource). This is why I leave it for the user to construct the Key (as described above - we could actually have that as snippet as an example in the specific Auth config class javadoc).

That makes sense. So can we simplify the "get a key" process? Maybe a fromFile() method? My concern is that the following piece is super long.
final KeyStore keystore = KeyStore.getInstance("PKCS12");
final FileInputStream fis = new FileInputStream("/path/to/key.p12");
keystore.load(fis, "password".toCharArray());
final PrivateKey key = (PrivateKey) keystore.getKey("privatekey", "password".toCharArray());
final AuthConfig ac =<EMAIL_ADDRESS>key);

Another option instead of File would be to accept a stream which is likely to support all various input type.

I really like that idea! See my note above about the different forms of auth. The most common will be JSON, the next would be p12 -- nothing stopping us from having multiple "set the key for this builder" methods where the user tells us what kind of key is in the stream.

Do we only work with keys that uses the default, notasecret, password?

I believe so. Currently (AFAIK) there's no way to create a key with a custom password.

@jgeewax do you think we can close this issue now?
Change #180 does not make it easier to load a pkcs12 file but does make it simpler to work with a json file. See #179 for more details about why we chose only to simplify the json way.

@mziccard Can you summarize for me what the auth experience is like in gcloud-java world?
For example, if I want to be explicit about my keyfile and project ID, and get an entity from Datastore in gcloud-node, I do:
var config = {
  projectId: 'grape-spaceship-123',
  keyFilename: '/path/to/keyfile.json'
};

var gcloud = require('gcloud')(config);
var dataset = gcloud.datastore.dataset();
var entity = dataset.get(dataset.key(['Product', 123]));

(see http://googlecloudplatform.github.io/gcloud-node/#/authentication)
If I wanted to do similarly with Java (let's say I just wanted to get an entity from Datastore), what would that code look like (the explicit version)?

@jgeewax Now you can do something like:
DatastoreOptions options = DatastoreOptions.builder()
    .projectId("grape-spaceship-123")
    .authCredentials(AuthCredentials.createForJson(
        new FileInputStream("/path/to/keyfile.json")))
    .build();
Datastore datastore = DatastoreFactory.instance().get(options);
KeyFactory keyFactory = datastore.newKeyFactory().kind(KIND);
Key key = keyFactory.newKey(keyName);
Entity entity = datastore.get(key);

This looks great ! Thanks guys !


Budget discussion and propositions

The new budget feature seems very useful for time and budget tracking. I don't know yet how to use that in my projects, but I have the feeling that it may be useful.
I understand that this feature is a work in progress, and I am willing to discuss it if it may help to improve it. Here are my questions...
Why all computations are only done on subtasks? Having a task without subtasks does not seem to be a bad practice. A task by itself is time and budget consuming.
I like the idea of computing automatically the time spent on a subtask. However, sometimes it may cause issues for 2 reasons:

someone can forget to change the status of the subtask, and that will break all computation.
even if there is timetable per user, it is common to leave work before or after the schedule, or to be interrupt by someone during a task. Yes, it is possible to add overtime or timeoff, or to click on "Terminate" (to pause the subtask) and reclick on "in progress", but it is really time consuming.

Therefore, I am wondering, if the "Time spent" can't be used in place of the computed time spent. Something like:

If a manual "Time spent" is filled: use it
Otherwise, use the computed "Time spent".

The budget feature and the subtask time tracking have been developed for a specific company to fit their workflow. They pay for that and they accepted to give the source code of this feature to the community.
However, it can be improved like you said.

Having a start/stop button to record the time spent (mentioned in another ticket)
Override the calculated time spent with the value entered in the form

Eh, that's great.

timeoff doesn't work for me.. Is something wrong with my installation or else?


[BUG-7962] Fix global params cannot transport into sub_process

related issue #7962

This pr also need to cherry-pick into dev.

Codecov Report

:exclamation: No coverage uploaded for pull request base (2.0.3-prepare@7b1744b). Click here to learn what that means.
The diff coverage is n/a.

@@               Coverage Diff                @@
##             2.0.3-prepare    #7969   +/-   ##
================================================
  Coverage                 ?   31.24%
  Complexity               ?     1571
================================================
  Files                    ?      440
  Lines                    ?    15058
  Branches                 ?     1508
================================================
  Hits                     ?     4705
  Misses                   ?     9879
  Partials                 ?      474

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7b1744b...a64065b. Read the comment docs.

@ruanwenjun Do you need to fix it on dev too?

good job

OK, I will submit a pr to dev.


Improve snapshot failure messages and stack trace printing.

Use @dmitriiabramov's new diff feature for snapshot comparisons. This greatly improves what Jest looks like when something goes wrong:

cc @kentaromiura @dmitriiabramov @kyldvs

@dmitriiabramov can we get rid of - expected + actual? To me, that line is so confusing – I feel like we can expect people to know that red means old and green means new.
That said, for snapshots it might be confusing because we throw. Should we say - snapshot + actual value?

(´・ω・) Aww This looks great! Do we get rid of the snapshot index though (eg: snapshot no. 2)? That was very helpful to me to understand which snapshot was failing when you've multiple in the same it` block.

We can add it back if you'd like. I just figured this looks cleaner but there is no reason I removed it.

@cpojer agree.. i added expected/actual just because other frameworks use it, but it's super confusing.
I was thinking about renaming them into missing/extra. what do you think?

or removed/added


Bandaged BD just making my discord font bigger

I ran the installer, and when I restart discord, the discord opens without the top toolbar with the minimize fullscreen and the exit buttons. I uninstall it, and it is back to normal. I am not sure if anyone else is facing the same issue, if you know how to fix, let me know

a lot of ppl had the same issue, zerebos already know that issue and he is fixing it, please be patient
also pretty accurate name for the issue


Edits needed to Heirarchical DI page

Here's some suggested edits.

The first few paragraphs are a bit redundant. the first 3 and then the second 3 say the same thing.

the last diagram under the heading "the injector tree" and the paragraphs above it are confusing. I think it's mostly the diagram. The paragraphs talk about components labeled as A, B, and C but only the instances are labeled.

in the last paragraph, the first sentence is missing a word.
"If we had only defined a binding for RestoreService on the root component, we would have exactly one instance of the across the entire applicatoin."

That chapter is slated for a thorough review. Would you mind sending your comments to Christophe? He'll pick that up when he gets back from vacation shortly.

This is still an issue.  We need to fold it into DI chapter I think


Filling in empty doc comments.

This is a quick pass over all of our docs trying to fill in some blanks. There are more for sure but this is a start.
Microsoft Reviewers: Open in CodeFlow

cc @normj


apx: 1.8.2 -> 2.0.0

Description of changes

Updated from 1.8.2 to 2.0.0 (https://github.com/Vanilla-OS/apx/releases/tag/v2.0.0)
Changed from docker to podman
Changed default config to match upstream
Added myself to maintainers
Closes #265938 & #249727

Ping @LennyLizowzskiy for testing

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.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

[x] Fits CONTRIBUTING.md.

overall LGTM, still missing a fix for https://github.com/NixOS/nixpkgs/issues/249727 though.

overall LGTM, still missing a fix for #249727 though.

I only got that error with the previous version (1.8.2) which seemed to be broken. I don't know what the issue was, but upgrading to 2.0.0 seems to fix it. At least I haven't encountered it since.

I can partly reproduce the issue on my system:
/result/bin/apx --version
Unable to read config file:
        Config File "apx" Not Found in "[/home/nickcao/Projects/nixpkgs/config /home/nickcao/Projects/config /home/nickcao/.config/apx /etc/apx /usr/share/apx]"

Maybe you have some leftover configuration files?

This helps:
--- a/pkgs/tools/package-management/apx/default.nix
+++ b/pkgs/tools/package-management/apx/default.nix
@@ -23,10 +23,13 @@ buildGoModule rec {
     substituteInPlace config/apx.json \
     --replace "/usr/share/apx/distrobox" "${distrobox}/bin/distrobox" \
     --replace "/usr/share/apx" "$out/bin/apx"
+
+    substituteInPlace settings/config.go \
+    --replace "/usr/share/apx/" "$out/share/apx/"
   '';

   postInstall = ''
-    install -D config/apx.json -t $out/etc/apx/
+    install -D config/apx.json -t $out/share/apx/
     install -D man/man1/apx.1 -t $out/man/man1/
   '';

And the command outputs also looks strange
./result/bin/apx --help
apx.description

Usage:
  apx [command]

Available Commands:
  completion  Generate the autocompletion script for the specified shell
  help        Help about any command
  pkgmanagers pkgmanagers.description
  stacks      stacks.description
  subsystems  subsystems.description

Flags:
  -h, --help      help for apx
  -v, --version   version for apx

Use "apx [command] --help" for more information about a command.

Notice all the placeholders.

This helps:

Thanks.  Thanks for the fix - that works well! Have pushed the changes.


Improving logic for install script

This is how it will look!

I really like the looks and organization of the script, I'd just like to clarify something: What would be the install instructions using this script? To install the scripts people would need to clone the repo?

Yeah, that's how github repos work.. I can see you that wanted a script which will be self-sufficient in itself, right?
I prefer this way of installation over the other, because the user has atleast somewhat control over the process, can read the installation script; which is not the case with this approach of installation.

I was trying to make installation as easy as possible for people that aren't that familiar with the cli, git, etc. But I think it's very unlikely that someone that isn't familiar with the CLI will use this, and this method has some advantages, so I'm merging it. Thanks for the contribution.

Great.


NSCameraUsageDescription for PhoneGap Build

Expected Behaviour
Successful publishing of app via iTunes Connect
Actual Behaviour
iTunes Connect complains about missing NSCameraUsageDescription when building with PhoneGap Build, and there's no mention of a workaround for PhoneGap Build. Changing info.plist is not an option and a config-file setting (via cordova-custom-config) doesn't work.
Reproduce Scenario (including but not limited to)
Simply not providing any NSCameraUsageDescription
Platform and Version (eg. Android 5.0 or iOS 9.2.1)
iOS 10
Cordova CLI version and cordova platform version
cli-6.5.0 (4.3.1 / 6.1.2 / 4.4.3) (iOS / Android / Windows)
Plugin version
6.0.5 (as I don't state it)

http://stackoverflow.com/questions/41525725/phonegap-missing-plist-key/41692078#41692078

Will add that to the documentation


How to install?

gem install kubernetes
Fetching kubernetes-0.0.2.gem
Successfully installed kubernetes-0.0.2
1 gem installed

It installs version from 2014 https://rubygems.org/gems/kubernetes/versions/0.0.2

Sorry for the delay. The gem is here:
https://rubygems.org/gems/kubernetes-io


Fix/define custom elements

fixes https://github.com/blockstack/connect/issues/118

This fixes #118 for me.


Fix aux-mute feedback

Aux mute feedback was missed when internal IDs were updated to be more consistent.
Also updates companion base libraries.
Adds subscriptions to feedback to optimize latency.

Fix for #103


Error at generating UnitTest MSTest "System.NullReferenceException"

Installed product versions

Visual Studio: enterprise 2019
This extension: 2.0.0

Description
http://prntscr.com/oqsuqx
Steps to recreate

Right Click on Controller
Click on Generate Unite Test Boilerplate
Click on Create Unit Test Class
Opens a modal window with lines about the exception

Can you post the code you were trying to create a test for?

I have the same issue.
It comes from parameter attribute in my case. In the exemple below, it works if I remove FromBody attribute.
public async Task<IHttpActionResult> MettreAJourPersonneRessource(int numeroPersonneRessource, [FromBody]PersonneRessource personneRessource)

Thanks for the reports and the bug details. This is fixed in 2.0.1.
Please leave a review if you like the extension!


Edited the about.md

I edited the about.md. We probably need to include the program timeline on the about page, but not so sure. Do you think that is necessary?

@bebatut, thanks for your guidance. I have made changes to the about.md.


scoop cleanup --cache cleans also installed applications

I tried to remove keepassxc from scoop's cache only:
scoop cleanup --cache keepassxc
To my surprise it also uninstalled all the previous versions I had:
Removing keepassxc: _backup_2.6.4 2.5.4 2.6.1 2.6.2 2.6.4
What I would expect is that when entering the --cache parameter only files in cache are removed.

The idea of the --cache parameter from the cleanup command is to additionally (not only) remove the outdated download cache.
To only remove the download cache, use the command cache (see scoop help cache).

@dwettstein I see. I have tried the scoop cache rm <app>.   This cleans all the downloaded versions.
Is there a way to cleanup only the older versions but keep the newest version only?

@tukanos, with scoop I think not. But you can just delete the old files in path $SCOOP\cache\ manually as a workaround.

@dwettstein I see.  Yes I did that manually and I wanted to update my workflow :).  I guess it has to wait till scoop will support it.


Prb with encoding of accents

Hi
I have used this beautiful piece of code and I am really astonished how easy it is to use.
Now, I have a problem. When generating a docx containing accents (french, spanish, german.... any!), wrong characters are printed. I am encoding in UTF8 before fetching the strings to add_run, but this does not work... Is this a bug?
Thanks for the answer
cheers

Thank you @scanny very much. It helps me solve the same problem when working with japanese too!


Fixisgcs

Updated PR to fix FileData to handle isGCS correctly for old projects

@afmckinney Here is the new PR

MERGED


Refactor tests

Use drf client instead of django client in api tests module

Also django 5.0 released, maybe add it to matrix?

Also django 5.0 released, maybe add it to matrix?

Great idea! Added in #26 since we start changing testing matrix there


Create SECURITY_POLICY.txt

This adds a link to the security policy.
Depends on: https://github.com/maplibre/maplibre/pull/141

@ovivoda @louwers Can you merge this one? The issue in https://github.com/maplibre/maplibre/pull/141 was approved and merged.

Could you make it a Markdown file instead?
All other text files in the repo are Markdown.

Hm, the first PRs have already been merged in other repositories. I would say it's too late by now because these files are also referenced by this file: https://github.com/maplibre/maplibre/blob/main/.github/ISSUE_TEMPLATE/new-repo-checklist.md
So changing it now would mean to redo everything.

The checklist is for new repos and the other repos can change it to a Markdown file at their own pace if they want. A link in a text file is just not very convenient because it is not clickable.

We probably also need a workflow for handling security issues specifically for maplibre-gl-native

It is roughly outlined in the document in the maplibre repo. I think as a start it is fine. Though there are Github features which allow the submission of reports I think.
As a start it is good to have at least something. Later we can ofc iterate on it.

The security policy states that vulnerabilities of 'services' should be reported to the e-mail provided. I don't know what these 'services' are in the context of MapLibre or MapLibre GL Native.
Vulnerabilities related to 'used open source software' need to be handled through bug reports. Since MapLibre GL Native iself is open source, does that mean that when someone discovers a critical security vulnerability in MapLibre GL Native, it should be reported through a bug report? I am not sure if that is a good idea, we need to think about that and discuss it.

It is roughly outlined in the document in the maplibre repo. I think as a start it is fine. Though there are Github features which allow the submission of reports I think.

I don't know who can read the e-mails sent to<EMAIL_ADDRESS>but we (@ovivoda and I) cannot at this point. We also need to think about agility in terms of informing users of MapLibre GL Native when a security vulnerability has been found, and pushing out new releases.
I appreciate the initiative, but instead of just merging this security policy, I want to put some more thought into how to handle secutity vulnerabilities in the context of MapLibre GL Native specifically.

We already have the reporting through GitHub enabled for this repo.

Let's discuss this tonight during the TSC meeting, but this seems like a much better option than an e-mail address.

Yes indeed, I totally forgot about that feature. Let's change it and use this feature!

Email could be a good fallback though to include.

@maxammann I thought about it and I want to include just one way to report an security issue, because otherwise it is more easy to miss a report.


Compatibility check to js-controller 3.3 and Admin5 React UI

Dear Adapter developer,
with js-controller 3.2 and js-controller 3.3 some additional checks were added to make sure that created objects match to the specifications and also written state values match to the object definition.
If something is not correct this is logged as 'warning' or 'info' log.
Please take the time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn log there from these checks please adjust the adapter and fix the relevant cases.
For questions please refer to https://github.com/ioBroker/ioBroker.js-controller/issues/1301
Additionally we are preparing Admin 5 which will have a completely rewritten UI. Please install Admin 5, activate that new UI and verify that the configuration of you adapter works as expected also there.
More informations on Admin 5 can be found in Forum https://forum.iobroker.net/topic/44282/test-adapter-admin-5-0-x-alpha-der-neuen-ui
Please close the issue after you checked it.
Thank you very much for your support!

Here is an example of this info:

chromecast.0
2021-06-11 12:33:13.828
info
(29933) State value to set for "chromecast.0.Google_Home.port" has to be type "string" but received type "number"

chromecast.0
2021-06-11 12:33:13.543
info
(29933) State value to set for "chromecast.0.Google_Home_mini.port" has to be type "string" but received type "number"


Update stdlib.ring

This branch has conflicts that must be resolved
Write the function again while using the last version of the file.


Add/Edit/Delete Category UI

Done https://github.com/TheanYeeSin/TickTock-Clock-To-Do-App/commit/94ba068126c57ade87545668d582ecb6235f3b94


Rule keyword support for cucumber

I have read that Rule keyword has been part of Gherkin since v6. Rule is used to group together several scenarios that belong to this business rule and it could contain one or more scenarios that illustrate the particular rule.
Current behavior
I am using the latest version (4.0.0)  of cypress-cucumber-processor and seems like Rule keyword is not supported. (might be due to the associated cucumber js version is 4.2.1? )
Desired behavior
It would be nice to have the Rule keyword support, since we can group scenarios and even provide a different Background section within the Rule
Versions

Cypress version: 6.2.1
Preprocessor version:  4.0.0
Node version: 14.15.3

Duplicate of https://github.com/TheBrainFamily/cypress-cucumber-preprocessor/issues/143.

Duplicate of https://github.com/TheBrainFamily/cypress-cucumber-preprocessor/issues/143.

I think it's worth to add though that with merging https://github.com/badeball/cypress-cucumber-preprocessor in here Rule keyword will be available. We might not be far from doing so :)

I think it's worth to add though that with merging https://github.com/badeball/cypress-cucumber-preprocessor in here Rule keyword will be available. We might not be far from doing so :)

Thanks @lgandecki. Please let us know once you have merged it to the main path. Could not use the forked version as some important aspects are missing like "All.features" support

Thanks @lgandecki. Please let us know once you have merged it to the main path. Could not use the forked version as some important aspects are missing like "All.features" support

Hey @lgandecki , any expected date for merging this new cool feature?