AssertExistsAndLoadBean not works well?

Description
I don't know whether I have missed something, but it seems that AssertExistsAndLoadBean will return same result in sometimes?

Gitea Version
latest
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
build
Database
None

The dark side of Go and XORM
Model { Field: 0 } (any zero-value) won't be put in the WHERE clause. Unfortunately, UserTypeIndividual is 0

Yes, so you can use unittest.AssertExistsAndLoadBean(t, &user_model.User{}, builder.Eq{"visibility":structs.VisibleTypePrivate, "type":user_model.UserTypeOrganization}) to avoid the zero problem.

I saw there is a condition parameter, but I didn’t understand why we don’t use it.
So it is used to avoid the zero problem.
Thanks for the answers.


Feature: remember last position per file

I'm currently translating GCC 10, which has around 14000 messages to translate. I have configured Poedit so that the messages are listed in the same order as in the .po file. After opening the .po file, I usually press Ctrl+Enter to reach the next untranslated message. Since I have enabled View > Warnings, pressing Ctrl+Enter doesn't bring me to the next untranslated message but to the next one that has a warning. Pressing Ctrl+Shift+Down has the same effect.
To avoid having to navigate to the last visited position in the file, Poedit should remember that position and scroll to that position after opening the file. I think this feature is generally useful, not only for skipping the warnings on startup.

Since I have enabled View > Warnings, pressing Ctrl+Enter doesn't bring me to the next untranslated message but to the next one that has a warning.

The rationale being that they are items that require further work. I can see how that rationale is less than solid.
Do you think it would be more reasonable to iterate through remaining work in a more structured manner instead of the current behavior where the entries are taken in order, regardless about whether they are with warning, needs work, or untranslated? I.e. would it make more sense to

First go through untranslated strings.
Only if there are none left, let Ctrl+Enter go through "needs work" ones.
Only if there are none left of either, iterate through QA warnings

?

First go through untranslated strings.
Only if there are none left, let Ctrl+Enter go through "needs work" ones.
Only if there are none left of either, iterate through QA warnings

I would merge cases 1 and 2. Both of them are not yet translated, and when I have the file sorted by message ID, processing these messages from top to bottom in a single pass makes sense to have them grouped by topic.
Fixing the QA warnings in a separate pass makes sense to me.


Dw/hero text section

Adjusted the font size of hero text and footer, clean up some unnecessary code

@demiwu96 Just fix the changes as Rishi suggests and we are good to go.

Small spacing changes. Only thing to note is in the bottom line section. In my first of two PRs, i refactored this section to make it more generic. Not sure if we need the background-image here

LGTM!

?

This is good. Approved.

@demiwu96 Can you update the branch again it seem out of date.


added KianV RISC-V marchID

Can you alter the PR to get rid of the formatting changes, only including the one additional line?


chore(e2e): add end to end tests

Coverage remained the same at 82.911% when pulling f409cf933fd0c47855ca0613a4392ca75d72790a on chore/end-to-end-test into 99ac4be26cc17959908d6ef141fbad5590397b1b on chore/test.


"Cannot find module '(...)\node_modules\jsr\dist\bin.js'"

I've installed JSR to my project using npm install --save-dev jsr, which worked fine, and I could then run npx jsr --help to get the JSR help menu:
PS C:\Users\Administrator\Documents\Programming\Projects\Public\dexonline-scraper> npm install --save-dev jsr

added 3 packages, and audited 121 packages in 2s

34 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
PS C:\Users\Administrator\Documents\Programming\Projects\Public\dexonline-scraper> npx jsr --help
jsr.io cli for node

Usage:
     jsr add @std/log  Install the "@std/log" package from jsr.io.
  jsr remove @std/log  Remove the "@std/log" package from the project.

Commands:
       i, install, add  Install one or more JSR packages.
  r, uninstall, remove  Remove one or more JSR packages.
               publish  Publish a package to the JSR registry.

Options:
      -P, --save-prod  Package will be added to dependencies. This is the default.
       -D, --save-dev  Package will be added to devDependencies.
  -O, --save-optional  Package will be added to optionalDependencies.
                --npm  Use npm to remove and install packages.
               --yarn  Use yarn to remove and install packages.
               --pnpm  Use pnpm to remove and install packages.
                --bun  Use bun to remove and install packages.
            --verbose  Show additional debugging information.
           -h, --help  Show this help text.
        -v, --version  Print the version number.

Publish Options:
     --token <Token>  The API token to use when publishing. If unset, interactive authentication will be used.
           --dry-run  Prepare the package for publishing performing all checks and validations without uploading.
  --allow-slow-types  Allow publishing with slow types.
        --provenance  From CI/CD system, publicly links the package to where it was built and published from.

Environment variables:
        JSR_URL  Use a different registry URL for the publish command.
  DENO_BIN_PATH  Use specified Deno binary instead of local downloaded one.

However, upon running npx jsr publish, I get the following error:
PS C:\Users\Administrator\Documents\Programming\Projects\Public\dexonline-scraper> npx jsr publish
Downloading JSR binary...
[00:01] [#################################################>] 35.3 MiB/35.5 MiB
Warning Sloppy module resolution (hint: update .js extension to .ts)
    at file:///C:/Users/Administrator/Documents/Programming/Projects/Public/dexonline-scraper/src/index.ts:2:19
Warning Sloppy module resolution (hint: update .js extension to .ts)
    at file:///C:/Users/Administrator/Documents/Programming/Projects/Public/dexonline-scraper/src/index.ts:3:86
Warning Sloppy module resolution (hint: update .js extension to .ts)
    at file:///C:/Users/Administrator/Documents/Programming/Projects/Public/dexonline-scraper/src/index.ts:4:29
Warning Sloppy module resolution (hint: update .js extension to .ts)
    at file:///C:/Users/Administrator/Documents/Programming/Projects/Public/dexonline-scraper/src/index.ts:5:28
Warning Sloppy module resolution (hint: update .js extension to .ts)
    at file:///C:/Users/Administrator/Documents/Programming/Projects/Public/dexonline-scraper/src/tabs/inflection.ts:2:25
Warning Sloppy module resolution (hint: update .js extension to .ts)
    at file:///C:/Users/Administrator/Documents/Programming/Projects/Public/dexonline-scraper/src/tabs/inflection.ts:3:23
Warning Sloppy module resolution (hint: update .js extension to .ts)
    at file:///C:/Users/Administrator/Documents/Programming/Projects/Public/dexonline-scraper/src/tabs/inflection.ts:4:52
Warning Sloppy module resolution (hint: update .js extension to .ts)
    at file:///C:/Users/Administrator/Documents/Programming/Projects/Public/dexonline-scraper/src/tabs/synthesis.ts:2:25
Warning Sloppy module resolution (hint: update .js extension to .ts)
    at file:///C:/Users/Administrator/Documents/Programming/Projects/Public/dexonline-scraper/src/tabs/synthesis.ts:3:23
Warning Sloppy module resolution (hint: update .js extension to .ts)
    at file:///C:/Users/Administrator/Documents/Programming/Projects/Public/dexonline-scraper/src/tabs/synthesis.ts:4:67
Warning Sloppy module resolution (hint: update .js extension to .ts)
    at file:///C:/Users/Administrator/Documents/Programming/Projects/Public/dexonline-scraper/src/tabs/synthesis.ts:5:21
Warning Sloppy module resolution (hint: update .js extension to .ts)
    at file:///C:/Users/Administrator/Documents/Programming/Projects/Public/dexonline-scraper/src/tabs/synthesis.ts:6:22
Warning Sloppy module resolution (hint: update .js extension to .ts)
    at file:///C:/Users/Administrator/Documents/Programming/Projects/Public/dexonline-scraper/src/constants/selectors.ts:1:29
Warning Sloppy module resolution (hint: update .js extension to .ts)
    at file:///C:/Users/Administrator/Documents/Programming/Projects/Public/dexonline-scraper/src/tabs/synthesis/row.ts:2:37
Warning Sloppy module resolution (hint: update .js extension to .ts)
    at file:///C:/Users/Administrator/Documents/Programming/Projects/Public/dexonline-scraper/src/tabs/synthesis/row.ts:3:23
Warning Sloppy module resolution (hint: update .js extension to .ts)
    at file:///C:/Users/Administrator/Documents/Programming/Projects/Public/dexonline-scraper/src/tabs/synthesis/row.ts:4:31
error: Failed creating junction and fallback symlink in node_modules folder.

Cannot create a file when that file already exists. (os error 183)

Cannot create a file when that file already exists. (os error 183), symlink<EMAIL_ADDRESS>-> 'C:\Users\Administrator\Documents\Programming\Projects\Public\dexonline-scraper\node_modules\jsr'

After which, npx jsr becomes unavailable:
PS C:\Users\Administrator\Documents\Programming\Projects\Public\dexonline-scraper> npx jsr
node:internal/modules/cjs/loader:1051
  throw err;
  ^

Error: Cannot find module 'C:\Users\Administrator\Documents\Programming\Projects\Public\dexonline-scraper\node_modules\jsr\dist\bin.js'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1048:15)
    at Module._load (node:internal/modules/cjs/loader:901:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:83:12)
    at node:internal/main/run_main_module:23:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v20.6.1

Installing jsr as a global package works just fine, however.
Installation information
NPM version: 10.1.0
Node.js version: 20.6.1
Operating system: Windows 10
Package/repository: https://github.com/vxern/dexonline-scraper

Just tested this and I cannot reproduce the described issue anymore (tested macOS + windows 11). Not sure which change fixed it, but it seems resolved.


(1.5) Form Fields without Label, it's possible ?

I need to leave blank, the LABEL in some FIELDS
I can do that?

Simply set caption to a single space (or a non-breaking space).
html: { caption: " ", ...}  or html: { caption: " ", ...}

I thought there was a special configuration for it
OK, Thanks


Improve manual CP workflow

Problem
When we cherry-pick PRs, we have OSBotify attempt to automatically cherry-pick the code (and resolve certain conflicts automatically). When he can successfully do that, it works great because he can push that code straight to staging without the need for a pull request.
However, in cases where we need to manually resolve conflicts, OSBotify will commit the conflict markers (weird, right?) then open a PR, and assign it to the person who triggered the CP to resolve the conflicts and get the PR reviewed and merged.
However, PRs created by OSBotify, imgbot, and other bots have tests and lint skipped, so we lose that bit of security on manual CPs.
Solution
Two parts:

First, update the cherry pick workflow such that, if there are conflicts, the PR is automatically opened not by OSBotify but by the Expensify employee who triggered the CP. That way, tests and lint run as normal.
if possible, find a way to open the PR without committing conflict markers, such that the PR appears with the conflicts as a normal PR would if it was created normally and then conflicts occurred after-the-fact.

cc @francoisl since we talked about this yesterday

the PR is automatically opened not by OSBotify but by the Expensify employee who triggered the CP. That way, tests and lint run as normal.

I dealt with this on GH Actions, basically if you create a PR in a GH Action, it will not run tests.


Updates to match Parser functionality

Added BSON and MSGPack support
Added AutoDetect support (via Accept header)
Added ResponderException and made most types throw it (QueryStr doesn't throw any in Parser, so it also doesn't in Responder)
Updated composer.json to use the same package versions as Parser
Updated Travis test matrix to match Parser
Various minor/cosmetic changes to bring Responder up to date with Parser

The idea here was to be able to use Parser and Responder together to build APIs that accept and return data in the same variety of formats.  This is useful because API clients can then communicate using whichever format(s) they are most comfortable using, in both directions, bypassing the need to include their own extra parser(s)/formatter(s) to handle extraneous formats.

Coverage decreased (-25.3%) to 74.747% when pulling eea2f630c49c259e73ee497a546f18224ce128ec on danhunsaker:parser-match-update into 0d0f57453529f18ee580e4986a29d98bd3327934 on nathanmac:master.

Coverage decreased (-30.2%) to 69.811% when pulling db95a035a1e7d43c9eb4c5a74dc91165693801b7 on danhunsaker:parser-match-update into 0d0f57453529f18ee580e4986a29d98bd3327934 on nathanmac:master.

Coverage decreased (-29.4%) to 70.642% when pulling 6a6bc976117bb5513da6180f23fb9d14fd5cd9fe on danhunsaker:parser-match-update into 0d0f57453529f18ee580e4986a29d98bd3327934 on nathanmac:master.

Coverage decreased (-29.4%) to 70.642% when pulling 63fac5779f0374efdb776af1cbd37c5df025164d on danhunsaker:parser-match-update into 0d0f57453529f18ee580e4986a29d98bd3327934 on nathanmac:master.

With the merging of nathanmac/Parser#30, this PR is now out of date.  I'll work on adding the registration feature here, as well, over the weekend (assuming my kids will give me the chance).
If this PR gets merged before then, I'll happily add the registration feature in a new branch/PR instead.

Coverage decreased (-24.1%) to 75.862% when pulling 48fe486221182002726c9bb1ca94440b14f729d7 on danhunsaker:parser-match-update into 0d0f57453529f18ee580e4986a29d98bd3327934 on nathanmac:master.

Coverage decreased (-24.5%) to 75.472% when pulling e8e1e2ea8f64b597b379d24d145b8793358bdec2 on danhunsaker:parser-match-update into 0d0f57453529f18ee580e4986a29d98bd3327934 on nathanmac:master.

There we go.  Up to date again.  Though this PR actually includes some fixes that Parser doesn't have yet; I'll be pushing those to a new PR there shortly.

Coverage decreased (-17.9%) to 82.051% when pulling fbd272f9d041aaece9c27e9ddad3d54d2daa28f0 on danhunsaker:parser-match-update into 0d0f57453529f18ee580e4986a29d98bd3327934 on nathanmac:master.

Coverage decreased (-17.9%) to 82.051% when pulling 173fc9cc53324635235995a3287687d99e1d75db on danhunsaker:parser-match-update into 0d0f57453529f18ee580e4986a29d98bd3327934 on nathanmac:master.

Coverage decreased (-7.7%) to 92.308% when pulling ad16349804643ea161399a9f389bc56682461cdc on danhunsaker:parser-match-update into 0d0f57453529f18ee580e4986a29d98bd3327934 on nathanmac:master.

Coverage decreased (-7.7%) to 92.308% when pulling ad16349804643ea161399a9f389bc56682461cdc on danhunsaker:parser-match-update into 0d0f57453529f18ee580e4986a29d98bd3327934 on nathanmac:master.

Thanks again 👍


fix: fixed security hall of fame list hyperlink

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #50907

I think @gikf is correct with the comment on the issue @AnonSar. I opened this PR and clicked on the hall of fame link in the docs and got a 404:

So we shouldn't do this. We could change it to https://contribute.freecodecamp.org/#/security-hall-of-fame which should make both links go to the correct place - the down side is that the link in the docs opens the hall of fame in a new tab. I'm not sure which is better. I think I would be fine changing it to that - it's either that or leave it how it is I think. So you could probably change it to that on this PR and we can let reviewers discuss if we want it like that or not.

I would leave it how it is. I'd rather have a broken link on the GitHub view than have it break the i18n links on the hosted docs site.

Yea, good call @naomi-lgbt - I didn't think of that. I would vote to leave it as-is then as well.

I changed this to blocked while we discuss a solution on the issue.

The behavior is intentional. The docs are not supposed to be used via GitHub. They have special formating and markup.


Add diagram type specific icon for tabs in model editor

This can take quite some time to implement.
Problems;

VSCode API is not powerful enough (for now)
modelserver/glspserver would need to handle multiple different file associations (im not sure how easily we can change it)


tf.gradients(loss, x) returns None. Is CleverHans asking me to implement the gradient for a newly defined operation?

I'm using tf.py_func to wrap a Python function and build a new operation. That is wrapped by a Keras layer that's the first one of a Keras Sequential model - it should perform a filtering task.
I've reproduced the problem on a script that should be easier to follow.
     1  import tensorflow as tf
     2  from keras.models import Sequential
     3  from keras.layers import Dense, Activation
     4  from keras.engine.topology import Layer
     5  from cleverhans.utils_keras import KerasModelWrapper
     6  from cleverhans.attacks import FastGradientMethod
     7
     8  class MyLayer(Layer):
     9      def __init__(self, **kwargs):
    10          super(MyLayer, self).__init__(**kwargs)
    11
    12      def build(self, input_shape):
    13          super(MyLayer, self).build(input_shape)
    14
    15      def call(self, X):
    16          def __function(X): return np.sinh(X)
    17          return tf.reshape(tf.py_func(__function, [X], tf.float32), shape=(-1, *X.shape[1:]))
    18          # tf.reshape() is needed to enforce shape of output
    19
    20  kerasmodel = Sequential([
    21      # Dense(10, batch_input_shape=(None, 4)),
    22      # Activation('softmax'),
    23      MyLayer(batch_input_shape=(None, 4)),
    24      Activation('softmax'),
    25  ])
    26  kerasmodel.compile(optimizer='adagrad', loss='mse', metrics=['accuracy']) # randomly chosen params
    27
    28  cleverhansmodel = KerasModelWrapper(kerasmodel)
    29  attack = FastGradientMethod(cleverhansmodel)
    30
    31  Xsym = tf.placeholder(tf.float32, shape=(None, 4))
    32  attack.generate(Xsym)

If I run the above script,
$ python example.py
Using TensorFlow backend.
WARNING:tensorflow:From /home/g/.local/share/virtualenvs/cleverhansexample-iTqMYa-7/src/cleverhans/cleverhans/attacks.py:216: calling reduce_max (from tensorflow.python.ops.math_ops) with keep_dims is deprecated and will be removed in a future version.
Instructions for updating:
keep_dims is deprecated, use keepdims instead
WARNING:tensorflow:From /home/g/.local/share/virtualenvs/cleverhansexample-iTqMYa-7/src/cleverhans/cleverhans/attacks_tf.py:62: calling reduce_sum (from tensorflow.python.ops.math_ops) with keep_dims is deprecated and will be removed in a future version.
Instructions for updating:
keep_dims is deprecated, use keepdims instead
WARNING:tensorflow:From /home/g/.local/share/virtualenvs/cleverhansexample-iTqMYa-7/src/cleverhans/cleverhans/utils_tf.py:37: softmax_cross_entropy_with_logits (from tensorflow.python.ops.nn_ops) is deprecated and will be removed in a future version.
Instructions for updating:

Future major versions of TensorFlow will allow gradients to flow
into the labels input on backprop by default.

See @{tf.nn.softmax_cross_entropy_with_logits_v2}.

Traceback (most recent call last):
  File "/home/g/.local/share/virtualenvs/cleverhansexample-iTqMYa-7/lib/python3.6/site-packages/tensorflow/python/framework/op_def_library.py", line 510, in _apply_op_helper
    preferred_dtype=default_dtype)
  File "/home/g/.local/share/virtualenvs/cleverhansexample-iTqMYa-7/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 1104, in internal_convert_to_tensor
    ret = conversion_func(value, dtype=dtype, name=name, as_ref=as_ref)
  File "/home/g/.local/share/virtualenvs/cleverhansexample-iTqMYa-7/lib/python3.6/site-packages/tensorflow/python/framework/constant_op.py", line 235, in _constant_tensor_conversion_function
    return constant(v, dtype=dtype, name=name)
  File "/home/g/.local/share/virtualenvs/cleverhansexample-iTqMYa-7/lib/python3.6/site-packages/tensorflow/python/framework/constant_op.py", line 214, in constant
    value, dtype=dtype, shape=shape, verify_shape=verify_shape))
  File "/home/g/.local/share/virtualenvs/cleverhansexample-iTqMYa-7/lib/python3.6/site-packages/tensorflow/python/framework/tensor_util.py", line 420, in make_tensor_proto
    raise ValueError("None values not supported.")
ValueError: None values not supported.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/g/.local/share/virtualenvs/cleverhansexample-iTqMYa-7/lib/python3.6/site-packages/tensorflow/python/framework/op_def_library.py", line 524, in _apply_op_helper
    values, as_ref=input_arg.is_ref).dtype.name
  File "/home/g/.local/share/virtualenvs/cleverhansexample-iTqMYa-7/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 1104, in internal_convert_to_tensor
    ret = conversion_func(value, dtype=dtype, name=name, as_ref=as_ref)
  File "/home/g/.local/share/virtualenvs/cleverhansexample-iTqMYa-7/lib/python3.6/site-packages/tensorflow/python/framework/constant_op.py", line 235, in _constant_tensor_conversion_function
    return constant(v, dtype=dtype, name=name)
  File "/home/g/.local/share/virtualenvs/cleverhansexample-iTqMYa-7/lib/python3.6/site-packages/tensorflow/python/framework/constant_op.py", line 214, in constant
    value, dtype=dtype, shape=shape, verify_shape=verify_shape))
  File "/home/g/.local/share/virtualenvs/cleverhansexample-iTqMYa-7/lib/python3.6/site-packages/tensorflow/python/framework/tensor_util.py", line 420, in make_tensor_proto
    raise ValueError("None values not supported.")
ValueError: None values not supported.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "example.py", line 32, in <module>
    attack.generate(Xsym)
  File "/home/g/.local/share/virtualenvs/cleverhansexample-iTqMYa-7/src/cleverhans/cleverhans/attacks.py", line 294, in generate
    targeted=(self.y_target is not None))
  File "/home/g/.local/share/virtualenvs/cleverhansexample-iTqMYa-7/src/cleverhans/cleverhans/attacks_tf.py", line 74, in fgm
    normalized_grad = tf.sign(grad)
  File "/home/g/.local/share/virtualenvs/cleverhansexample-iTqMYa-7/lib/python3.6/site-packages/tensorflow/python/ops/math_ops.py", line 453, in sign
    return gen_math_ops.sign(x, name=name)
  File "/home/g/.local/share/virtualenvs/cleverhansexample-iTqMYa-7/lib/python3.6/site-packages/tensorflow/python/ops/gen_math_ops.py", line 6877, in sign
    "Sign", x=x, name=name)
  File "/home/g/.local/share/virtualenvs/cleverhansexample-iTqMYa-7/lib/python3.6/site-packages/tensorflow/python/framework/op_def_library.py", line 528, in _apply_op_helper
    (input_name, err))
ValueError: Tried to convert 'x' to a tensor and failed. Error: None values not supported

What's triggering the error is https://github.com/tensorflow/cleverhans/blob/29e7e3b5ca1ca8fb1481c17d0875df2a323e3ae0/cleverhans/attacks_tf.py#L70-L74 It seems like CleverHans requires me to compute the gradient for the newly defined operation. But in the original case I don't know how to compute the gradient. The original function wrapped by tf.py_func is rather complex. Also I'm planning to wrap a variety of functions and understanding what the gradient is for all of them is a pain.
Note that decommenting lines 21, 22 of the above script makes CleverHans quite again.

In  __function, why not use tf.sinh instead of np.sinh?

that's unrelated to the issue.
By the way, the point of using tf.py_func is building new operators without using TensorFlow operators but a Python function.

On 23 Jun 2018, at 20:36, Gokula Krishnan<EMAIL_ADDRESS>wrote:
In __function, why not use tf.sinh instead of np.sinh?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

If you use a gradient-based attack, the gradient does need to be defined. That's going to be true regardless of software framework.


pip for dapr-client still in version 0.1, need to publish 0.2 and then 0.3

Expected Behavior
pip install dapr-client should install the latest version (0.2 now)
Actual Behavior
installs the first version 0.1
Steps to Reproduce the Problem
pip search dapr-client
or
open https://pypi.org/project/dapr-client/

0.1 is the latest version, python sdk hasn't been updated yet, to do a next release.


Implement support for wlr_keyboard_group

Hi,
OK, so this is my first pull request, so bear with me ;).
Some time back, wlroots introduced the wlr_keyboard_group feature which groups multiple keyboards together to a single logical keyboard. This is useful since often a single physical keyboard may advertise itself as multiple keyboards which may lead to problems with compositor-defined keybindings. (e.g. if cage where to be run with a keyboard on which Alt and Escape were advertised on different keyboards, this would prevent the keybinding from working)
As of today, this is unlikely to concern  many people since the provided keybinding will be rarely used and it many cases Alt and Escape will be on the same keyboard. Nevertheless, I think that it is worth the extra code as it facilates the extension of cage with more keybindings and, in addition, I find the concept of keyboard groups to be more elegant than the current solution. Furthermore, the way I have implemented this allows users to attach multiple keyboards and run keybindings even when pressing the keys on different keyboards.
More technically, this pull request implements support for wlr_keyboard_group by adding all attached keyboards to as few groups as possible (only keyboards with the same keymap and repeat_info can be put in the same group). It extends the cg_seat structure by a keyboard_groups member and takes care of initializing and removing the required data.
I do not currently have an external keyboard with which I could try hot-plugging, so if someone would have the possibility to do so, I would be glad to hear about the outcome!
So yeah, that's about it! I actually ran into an issue in a project based on cage that I'm working on which prompted me to implement this, so the issues described above actually occur in production. The code is heavily borrowed from sway and adapted to fit the way cage works.
Hope I didn't mess up too badly on my first PR ;)!
cheers,
project-repo

Thanks! I'll take a look at the code over the weekend, but on a first glance it looks good :)

I actually ran into an issue in a project based on cage that I'm working on which prompted me to implement this

If you can, please do share some details :) It's always satisfying to hear how Cage is being used!

Thanks! I'll take a look at the code over the weekend, but on a first glance it looks good :)
Cool, thanks!

If you can, please do share some details :) It's always satisfying to hear how Cage is being used!
So, after trying many different wayland compositors, I decided that there was, in fact, no usable and activly developed alternative to the xorg wm "ratpoison" for wayland. So, for the last month or so, I have been working on extending cage to be a tiling compositor that could work as a  more or less drop in replacement for ratpoison (hopefully with some additional features I would like to add). Anyway, the whole project is based on a clone of cage and I can still actually merge all of the updates you do to the original project, even if I have to resolve many of the conflicts manually (It took me quite some time to merge the implementation of output_layout ;)).

It's already functional to the point at which I could probably use it in production, but there are still some tests I would like to do, READMEs to write, etc. before I share it...

OK, so this is my attempt on removing cg_keyboard. Definitly read this through carefully and make sure if it makes sense! Once again, I don't have the hardware to test hot-plugging keyboards so the best I could do was compile with asan, which didn't report any errors or memory leaks. If this pans out, we can drop around 80 lines of code!

@Hjdskes What do you think will be the rough timeline for this PR to be merged? Please, there's no rush on my side, I'm just asking as I am working on a time schedule for my project I told you about earlier and I wanted to phase in the time until this is merged!

I don't have hardware currently to test additional keyboards, so if someone that reads this with multiple keyboards can take this for a test that'd be highly appreciated!

Sorry, I'm still rather new to creating/managing pull requests... What do you mean with rebase to master exactly? What I have locally is an outdated git repo (e.g. missing clang-format information) which I would have to update somehow so I can fix the formatting issues as you mentioned. I guess, after that I would have to rebase my feature branch to my fork's master?

Here's a nice page about rebasing: https://git-rebase.io/
Essentially, what you'll be doing is grabbing your commits and applying them on top of the latest master branch. Indeed, like you say you currently have an outdated master branch, which you'll need to update. When you've done this, you can rebase your feature branch on top of the updated master branch.
First, ensure you have my repository as a remote with git remote -v. This should print two lines with git@github.com:Hjdskes/cage.git, one for fetching and one for pushing. For me, it looks like this:
 > git remote -v
origin	git@github.com:Hjdskes/cage.git (fetch)
origin	git@github.com:Hjdskes/cage.git (push)

If it's missing, run git remote add upstream git@github.com:Hjdskes/cage.git.
Now you can fetch my master branch with git fetch upstream, and rebase your branch on top of my master branch: git rebase upstream/master. You'll get some conflicts that you'll need to resolve (as GitHub is indicating), which you can list with git status. Edit the conflicting files and then git add them. When done adding files, run git rebase --continue and force push your changes with git push -f after you confirm it's all good.
That's it! :)

I've just been able to test this with two keyboards. It works fine, even when removing and adding the second keyboard again. Nice work!

Thanks for the awesome instructions on how to rebase! I just pushed the changes you asked for and it looks like all tests are passing. It's good to hear that it works with a second keyboard too, I wasn't so sure on that part!

OK, fixed that! What do you think?


Limit to one interrupt per rx packet

This prevents multiple interrupts while draining the FIFO. If you are happy then please delete this donor branch.

I request that this pull request remains in play until @jcw decides its future.

As I understand it, the master branch has some problems in RF69_COMPAT mode. Is this part of it, anything else I could adopt from your RFxConsole branch or other to improve things?

This one change will make a big improvement to master and has no
other dependencies. There are rather a lot of other changes, some
that aren't in your style and if you see any value in them perhaps
we could bring them into line with your house style. I am currently
tweaking classic RF69.cpp to pass native as well as classic packets.
Once I get that working perhaps we can diff master and that library
to get a list of what has changed and consider them point by point -
it has been a long time now and I don't recall all the changes
specifically.

On 31/05/2015 12:44, Jean-Claude
  Wippler wrote:

  As I understand it, the master branch has some problems in RF69_COMPAT
    mode. Is this part of it, anything else I could adopt from your
    RFxConsole branch or other to improve things?
  —
    Reply to this email directly or view
      it on GitHub.

Perfect, thanks - I'll merge this one in and close the issue. Please re-open or create a new one for further changes.


bug: vscode extras - comment in typescript

Did you check docs and existing issues?

[X] I have read all the LazyVim docs
[X] I have searched the existing issues of LazyVim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
0.0.9
Operating system/version
MacOS 13.3.1
Describe the bug
Thanks to your fix in #798, I can successfully use neovim in vscode.
I stumble upon a bug when I tried to comment some code in a Typescript file.
The following error appeared in neovim-vscode output :
E5108: Error executing lua vim/_editor.lua:0: nvim_exec2(): Vim(lua):E5108: Error executing lua ...l/share/nvim/lazy/LazyVim/lua/lazyvim/plugins/coding.lua:143: module 'ts_context_commentstring.internal' not found:
	no field package.preload['ts_context_commentstring.internal']
cache_loader: module ts_context_commentstring.internal not found
cache_loader_lib: module ts_context_commentstring.internal not found
	no file './ts_context_commentstring/internal.lua'
	no file '/opt/homebrew/share/luajit-2.1.0-beta3/ts_context_commentstring/internal.lua'
	no file '/usr/local/share/lua/5.1/ts_context_commentstring/internal.lua'
	no file '/usr/local/share/lua/5.1/ts_context_commentstring/internal/init.lua'
	no file '/opt/homebrew/share/lua/5.1/ts_context_commentstring/internal.lua'
	no file '/opt/homebrew/share/lua/5.1/ts_context_commentstring/internal/init.lua'
	no file './ts_context_commentstring/internal.so'
	no file '/usr/local/lib/lua/5.1/ts_context_commentstring/internal.so'
	no file '/opt/homebrew/lib/lua/5.1/ts_context_commentstring/internal.so'
	no file '/usr/local/lib/lua/5.1/loadall.so'
	no file './ts_context_commentstring.so'
	no file '/usr/local/lib/lua/5.1/ts_context_commentstring.so'
	no file '/opt/homebrew/lib/lua/5.1/ts_context_commentstring.so'
	no file '/usr/local/lib/lua/5.1/loadall.so'
stack traceback:
	[C]: in function 'require'
	...l/share/nvim/lazy/LazyVim/lua/lazyvim/plugins/coding.lua:143: in function 'get_commentstring'
	....local/share/nvim/lazy/mini.comment/lua/mini/comment.lua:345: in function 'make_comment_parts'
	....local/share/nvim/lazy/mini.comment/lua/mini/comment.lua:215: in function 'toggle_lines'
	[string ":lua"]:1: in main chunk
	[C]: in function 'nvim_exec2'
	vim/_editor.lua: in function 'cmd'
	....local/share/nvim/lazy/mini.comment/lua/mini/comment.lua:160: in function 'operator'
	[string ":lua"]:1: in main chunk
stack traceback:
	[C]: in function 'nvim_exec2'
	vim/_editor.lua: in function 'cmd'
	....local/share/nvim/lazy/mini.comment/lua/mini/comment.lua:160: in function 'operator'
	[string ":lua"]:1: in main chunk

Steps To Reproduce

Add vscode extra plugin in LazyVim config.
Install and setup neovim-vscode in vscode.
Open a file and highlight a line in visual line mode (I got the issue with a Typescript as well as a json file)
Enter gc to comment.

Expected Behavior
The lines should be commented and no error should appear in the output.
Repro
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  "folke/LazyVim",
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

Right, I added that back again. Will fix!

Fixed!

Come on, you can't be that fast @folke 🤯

@baker221 just double checked and all plugins related to comments are loaded inside vscode. Must be the filetype of the specific file

Sorry I don't really understand the meaning. The file I work on is written in Python. The default behavior of vscode command+/ can work well. I read the doc of mini-comments. I guess the problem happens because my server doesn't have treesitter?

@baker221 just double checked and all plugins related to comments are loaded inside vscode. Must be the filetype of the specific file

Sorry I don't really understand the meaning. The file I work on is written in Python. The default behavior of vscode command+/ can work well. I read the doc of mini-comments. I guess the problem happens because my server doesn't have treesitter?

@baker221 just double checked and all plugins related to comments are loaded inside vscode. Must be the filetype of the specific file

OIC. When I use .py file, the gcc command can work, but in .ipynb file cannot. This is not the reason of server or local. Sorry about that.

probably because .ipynb files don't have commentstring or treesitter commentstrings set

Then is there any method solving this? At this moment I have to select the text by mouse (because in vscode the visual mode selection and mouse selection is different) and use command+/

That filetype just needs a proper :h 'commentstring'

I tried set cms="# %s", but still the following:
(mini.comment) Option 'commentstring' is empty

Are you sure?
In that buffer, what do the following two return?
require("ts_context_commentstring.internal").calculate_commentstring()
vim.bo.commentstring

The first:
E492: Not an editor command: require("ts_context_commentstring.internal").calculate_commentstring()

The second is weird because I actually typed "commentstring".
"ommentstring" [New]
Cannot open file "ommentstring"
E480: No match: bo

You need to execute both commands prepended with :=

Then the first is nil and the second didn't print anything.

then you did not set the commenstring correctly


alias Astro City pads to "saturn"

Should this go into LTS too?

mm walking this back. the commonality is mfr (sega) and layout (6 button) but they shouldn't be conflated.


Using local API to retrieve current track

Hey,
I made first version of changing API for retrieving current track to use local system api for spotify player as was suggested here: https://github.com/emilioastarita/lyricfier/issues/103 by @patrolez.
I only tested it on Linux but clients are for the most part taken from this project:
https://github.com/panz3r/hyper-spotify/tree/master/src/lib
Please take a look and let me know what you think.

I am not a TypeScript developer, but I can only say well done! :+1:
It works under Linux for me also!

I've tried this in macOS Mojave and it's not working for me 😢

Thank for testing! I will take a look and see what I can do about it

Not working for me on Windows 10. In the cmd prompt, when clicking Try Again I get this
[10628:1012/232907.571:INFO:CONSOLE(6)] "Uncaught TypeError: Spotilocal is not a constructor", source: C:\Users\myles\lyricfier\render\spotify\SpotifyWindows.js (6)
I have spotify version <IP_ADDRESS>.g259b84fa, but I also use Spicetify to customize my Spotify a bit. Could that be why this isn't working?
Thanks!

I fixed issue on macOs Mohave so linux+macOs should work now.
Unfortunately, I had to remove support for windows as i have no idea how to do it locally. As MPRIS does not exists on windows and it seems SystemMediaTransportControls is not alternative that would allow accessing currently played track. I vote for dropping windows support until we find working alternative and in the meantime have working app for other platforms. What shall we do @emilioastarita?

It works now! Thank you so much!
Is there a way you could put together a release so that it's easier to launch the app (not requiring the command line)?

Here is release in my forked repo: https://github.com/jakub-tucek/lyricfier/releases/tag/v0.3.0

Is windows support a priority, because all other lyric apps for Spotify are abandoned

(electron:15339): Pango-ERROR **: 22:07:44.628: Harfbuzz version too old (1.4.2)
I just done quick googling and find out that it's probably common electron problem.


[firestore-bigquery-export] TypeError: Cannot read property 'seconds' of undefined

Extension name: firestore-bigquery-export`
Extension version: 0.1.16

I have setup this extension to sync a collection in Firestore to Bigquery. It works really well for the most time, but sometimes all data doesn't get synced, and I see this error in Logs:
TypeError: Cannot read property 'seconds' of undefined
    at Function.fromProto (/workspace/node_modules/@google-cloud/firestore/build/src/timestamp.js:135:47)
    at Firestore.snapshot_ (/workspace/node_modules/@google-cloud/firestore/build/src/index.js:575:57)
    at beforeSnapshotConstructor (/workspace/node_modules/firebase-functions/lib/providers/firestore.js:139:30)
    at changeConstructor (/workspace/node_modules/firebase-functions/lib/providers/firestore.js:143:49)
    at cloudFunction (/workspace/node_modules/firebase-functions/lib/cloud-functions.js:133:34)

When that has happened, if I go into the record in Firestore and update any property, that triggers a successful sync of the document over to BigQuery, so the issue is intermittent and I'm not sure how to reproduce.
A typical document in Firestore can contain the following data, broken into individual properties for each JSON field:
{     "orderDisplayNumber": 2575,     "status": "Delivered",     "statusHistory":     {         "orderCreated": "2021-07-28T17:58:48.000Z",         "orderDelivered": "2021-07-28T18:06:56.000Z"     },     "statusMessage": "Your order has been delivered!",     "userId": "abc123" }
The error message complains about "seconds", but worth noting could be that orderCreated and orderDelivered are both string fields in Firestore.

I started having this same problem today (2021-07-29) at 19:52
Extension name: firestore-bigquery-export
Extension version: 0.1.13

Same problem here.
Extension name: firestore-bigquery-export
Extension version: 0.1.13

Thanks @peter-kavall @nmf2
I've added this to our project board.

Just wanted to report I'm seeing this on version 0.1.9 also

Some info that might help understand the problem.
It happened to me as well during a period where we were doing a massive update on thousands of documents at the same time. Perhaps this has something to do with a bottleneck somewhere?

It seems this was due to the GCF issue mentioned here https://github.com/firebase/firebase-functions/issues/922 and is now resolved


feature/multi-element-action

Summary

delete all selected elements #456
copy and paste all selected elements [attention]
fix email type on signup page

Copy and paste allowed only on conceptual module.
Logic relations have deep internal connections (AKA foreign key), to copy and paste elements we have to update all these references and although not impossible, it is very complex and could lead to bugs.
In order to inform users about this limitation, the following message is now visible when users try to copy + paste elements in a logic model

Close #456
Close #473

Éx um monxtro!

I did some tests here and it's working smoothly.
Do you want to go above and beyond?

Once only one element is selected, show the selection mark too (The one with green border)
Allow user to select multiple elements one-by-one when holding cmd / ctrl and clicking in each element.

Éx um monxtro!

I did some tests here and it's working smoothly. Do you want to go above and beyond?

Once only one element is selected, show the selection mark too (The one with green border)
Allow user to select multiple elements one-by-one when holding cmd / ctrl and clicking in each element.

could not do it because the both action conflict
I tried but did not work after spending good amount of time. Will try more but wont hold the PR

@miltonbsn  regarding the limitation to copy + paste in Logic models, I have the following question:
Considering Foreign key as the limitation factor, can we enable c+p if a table still don't have stablished relationships yet?
Meaning, should we enable user co c+p tables that dont have a connection with any other table?

On more thing...
Is this branch mixing two different fixes?
Branch name is feature/validate-mail and I also see some changes related to that... 😓

@miltonbsn regarding the limitation to copy + paste in Logic models, I have the following question:
Considering Foreign key as the limitation factor, can we enable c+p if a table still don't have stablished relationships yet? Meaning, should we enable user co c+p tables that dont have a connection with any other table?

Yesss, I was a bit lazy but will do it :sweat_smile:

On more thing... Is this branch mixing two different fixes?
Branch name is feature/validate-mail and I also see some changes related to that... 😓

Yes, I started doing one thing and had this idea and delivered two. Sorry and forgive me this time :pray:

Yes, I started doing one thing and had this idea and delivered two. Sorry and forgive me this time 🙏

@idmarjr we are good to go again. I did a mistake on rebase process but i will fix when merging this PR/

@idmarjr wait, it is worst than I expected, i will open another PR


i3: don't assume no-startup-id

https://github.com/rycee/home-manager/blob/d2572315ca14f225ff3b41c03b0c0b670dffa3a8/modules/services/window-managers/i3.nix#L483
Hi, I was asking why do you assume that every command wants "no-startup-id". I'd have a bool to set it up
thanks, nicolò

Good point, created PR which fixes that. Thank you for the feedback!


Mediators and Reparenting

Background: the Robotlegs 1 'wait one frame' strategy
In Robotlegs 1, the MediatorMap employed a strategy of 'waiting for 1 frame' to check that a view really had been removed from the display list, before cleaning up its mediators.
In addition, when a view was passed to the mediatorMap to be mediated, we first checked that it wasn't one with a mediator marked for removal by the system. In this way, if a view was added and removed within a frame - usually by being reparented - its mediator would persist.
The reason for this was primarily that Flex 3 Scrollable Containers can do reparenting behind your back (they secretly remove and add items when you cross the threshold for needing the scrolling to be activated).
The Flash TileList component also does this sneaky reparenting during scrolling. Items still in view can be reparented when any other item is introduced to the view area.
There was a small but important bug in the RL1 process - it was possible to get false positives on the eventMap when your mediator was loitering for a frame. We now have a robust workaround for this bug: suspending / resuming eventMap activity within the mediator itself when the view is removed / added.
What should happen when a view is reparented?
Let's assume for a moment that it's possible to employ a much more specific bug-fix for the known scrollable container problems, and that we can provide fixes for any similar problems emerging future. Or that we exclude those components from the game completely - perhaps by specifying Flex 4, and saying that contents of TileLists can't be mediated.
Are there scenarios in which reparenting shouldn't cause the mediator to be destroyed and a new one created?
A use case: a column-based UI in which the user can drag parts of the UI from one column to another.
It's common to have to attach a component to a higher 'layer' during dragging and then snap it back to the lower layer in which it normally lives when the drag is complete. If the initialize function in your Mediator also populates it in some way, you might not want that process to be repeated.
Are there scenarios in which reparenting should cause the mediator to be destroyed and a new one created?
1. Switching 'context'
In Robotlegs 2, rather than having one enormous context view, you can target specific DisplayObjectContainers to be monitored for added / removed events. If you reparented the view in question into a DOC which has a different set of MediatorMap rules applied, or is outside of the scope of the current MediatorMap, your mediator should probably be cleaned up.
In the case of moving to a new 'context view', that context may have a different eventDispatcher to the one referenced in the eventMap inside your mediator and so on.
2. Same context, but simple state inconsistencies
I'm a 'mediators-don't-hold-state' person myself, but let's assume for a moment that you've got a reason to hold a reference to the view's parent in the mediator. When the view is reparented, that parent might change.
Guards and hooks make things more complicated
Should your mediator persist or vanish if your view would no longer pass your guards, and all you've done is drag it around? Possibly you've even dragged the item and returned it to the place where it was originally.
Of course this would probably be a sign that you've written your guards in a strange way, but - leaving guards aside - should any hooks be reapplied? You could write all your hooks with their own internal guard clauses (and in many cases this will be necessary - you'll need to cache which views you've already skinned so that you don't keep reskinning them over and over). But all of this is potentially inefficient.
The crux: what's the most common 'least surprising' strategy for managing reparenting?
Here's a proposal - to which we'd like your responses. It really is only a draft attempt to figure out the least annoying strategy to employ. Inevitably any strategy will sometimes be incorrect - so the aim is to make it right more often that it's wrong, and ensure it can be overridden in those cases.
The most important thing is that the strategy is easy to understand - developers need to know what to expect from the framework.

The default behaviour is that if a view item is reparented and remains within the contextView that it was originally mediated in, nothing will happen. This is a 'local' reparenting. The mediator(s) will persist.

If a view item is reparented outside of the contextView that it was originally mediated in, the mediator(s) will be destroyed and new mediators will be created, guards permitting, and hooks will be reapplied. This cannot be overridden by the mediator because the scope of the eventMap and other injections may no longer be valid.

If you want guards/hooks to be reapplied during local reparenting, or you want your mediator to be cleaned up and re-initialised during local reparenting, specify this in your mediator by setting destroyOnReparent = true;.

We'll abstract the reparenting strategy itself into a class (whoop! strategy pattern!) so that if you want to dictate your own very specific strategy, there's a simple entry-point to do that.

Please share your reactions, questions and thoughts - thanks!

A detail: is it more appropriate to specify that you want to destroyOnReparent in the Mediator class or in the mapping?

I think there is one good basic argument and two supporting ones to be
made for keeping the delayed mediator destruction from RL 1:
The main argument is that it works and in cases of frequent
reparenting can save lots of cycles. I know: This isn't too much of a
concern and people doing much reparenting of mediated views should
stop doing that, but that's not a good reason against an
optimization.
The first, and most important, supporting argument is that, as far as
I remember, we've never had even one complaint about the current
behavior. And that's with lots of people using stateful mediators. To
me, that strongly implies that it is, in fact, not surprising at all.
The second supporting argument is that Robotlegs should encourage a
type of view handling that's based on what role the view has in the
system, not where it is. Meaning that it just shouldn't matter if the
view is moved around in the display list. Now obviously there are
valid scenarios where that's not true anymore, but I guess those can
be dealt with by using appropriate guards: mediators or whatever other
view handlers should be torn down as soon as we can be certain that
their guards don't match anymore. Just as in RL 1, I think the least
surprising definition of that entails waiting until any reparenting
might have occurred.
Reparenting between contexts seems to fall out of this nicely: if a
view is moved out of one context, that context's handling conditions
can't possibly be met anymore. Another context's conditions might
start being met, though.
Summed up, I think we should stop after point 2 of your proposal with
the addition of a mediator maybe being destroyed even within one
context if its new position doesn't fulfill all guards anymore. The
rest seems overly complicated and flexible in a place where people
don't need it to be.

Very good point - nobody every complained about the RL1 strategy.
What do you think about hooks - do they re-run? Or do we just check the validity of the context, and if it's the same context then re-run the guards, and then leave it at that? And if it's a new context then you get the whole-shebang of whatever you mapped in that context?

IIUC, you can have different guards being satisfied within one
context, right? So you might get another mediator for the same view
even within one context.
I think the guards should be run and if the old ones match, the
mediator is kept as-is, whereas it is destroyed if they don't.
Whatever happens in addition to that doesn't enter the equation,
meaning a new mediator might be created within the same context or in
another one, but we don't care about that when dealing with the old
one.


Bugfix/issue 1443 zero size array sum

Summary:
Fix issue with sum() segfaulting when given array of size zero.
Improve efficiency of fwd-mode sum by calling sum() for value and tangent calculations.
Intended Effect:
Fix bug and speed up.
How to Verify:
Many more unit tests added, including tests for gradients.
Side Effects:
Includes get a little more complicated as there are now even more sum() implementations flying around (six files named sum.hpp, I believe)
Documentation:
Added in code.  No user-facing doc necessary.
Reviewer Suggestions:
Anyone.

Looks good. We'll just wait for tests to pass.


Fix SvelteComponentWithConstructor type

Hi there! Really like the concept of your library!
This small PR fixes a type issue with SvelteComponentWithConstructor. In the current version you get type errors if you try to use it.

Hi, thanks for the PR!
Unfortunately this PR causes another error:
src-ts/stack-router.ts:280:41 - error TS2339: Property 'guards' does not exist on type 'SvelteComponentWithConstructor'.
To solve this, I just improved the typings for Routes (they were a bit loose) and pushed it to 44ac74a96d948f9b327444d66fd8042f2811e147
Can you try this version? If you still get a type error, can you copy-paste so that I can have a full picture of what's going on?
Thanks in advance!

New commit: 0877bdfc637ca71284a24fef3519d0a177808451 (just edited the previous comment).
I added a RouteDescriptor interface and used it in the prepareCacheEntryToActivate function. Now it works with your PR too.
I'm not sure which type we should use. The old union type is more explicit, but in reality any constructor that returns a SvelteComponent is enough. Any opinions on this?

I don't know the internals of the library too much, but according to the typings you expect a component constructor which you need to instantiate in some way. If that's the case, the current typings if this PR shouldn't be loosened.
Looking at the other types of RouteDescriptor, it seems that there's the same type mismatch. The typings semantically tell users to provide the instance of a component, but what you want to have is the constructor which returns a component, right?
Feel free to go ahead rewiring the types as you need them, this was more of a quick "this type does not match what the docs tell me to do" PR.

Oh now I understand the problem.
I got somehow convinced that SvelteComponent represented the class and not the instance type. My bad.
It should all be consistent with the documentation now. You deduced correctly: what should be provided are component constructors, not instances, as also shown in the example.
This is the commit: 45b71da56909cc54e27e272a5c8a0db488422c7b
I replaced the type with the one in this PR and renamed the type in SvelteComponentConstructor (and not WithConstructor), that's all that is needed to operate.
Thanks again!

Great work, thank you for the quick response! I'll close this one and reopen another one because it seems GitHub doesn't want to add the commits to this PR for some reason.


[ShortTopMenu] Unreadable menu

https://image.prntscr.com/image/ky7aSQFTQL2d09gc6su4XQ.png   - In my opinion Menu bar on Short Top Menu template doesn't looks good, is unreadable.
It's hard to say, Is that "Notification", "Templates" or "Notification templates".

@dawid-g Fixed!

verified as fixed.


The webpage displays "This HTTP triggered function executed successfully..." when debugging the "angular-basic" project

OS: Win10
Build Version: 20220128.1
Regression: Not a regression
Repro Steps:

Clone https://github.com/staticwebdev/angular-basic -> Open the project in VS Code.
Open VS Code terminal and run "npm install" -> Create a TypeScript HTTP endpoint, named "message".
Go to the "Run and Debug" menu -> Select "Azure Static Web Apps…" -> Select "SWA: Run angular-basic" -> Click the "Run" button.
Navigate to "http://localhost:4280/api/message" in the Chrome window.
Check whether the webpage displays "Hello World".

Expect:
The webpage displays "Hello World".

Actual:
The webpage displays "This HTTP triggered function executed successfully...".

It looks like the screenshot in our docs were inaccurate - we'll get that fixed. Good find 👍


[skrifa] replace todo! with None for color bbox

Fixes abort caused by todo!() and caught by fuzzing.
ref
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=71277 and https://oss-fuzz.com/testcase?key=5794538109599744
JMM if happy

Perhaps I thought it was too obvious :)
I'll go ahead and add before merging.


fix: update schema utils to fix browser issue

fixes #227

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


add 3 samples to Windows Universal Samples in GitHub

The 3 samples {Bookstore1, QuizGame, Bookstore2} that are linked to herein should also appear in Windows Universal Samples on GitHub.  Please add them for both C# and C++/CX (so that the C++/WinRT variant is then added there too).
https://github.com/Microsoft/Windows-universal-samples

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

ID: 918404cb-28b0-1624-da04-c992bfca4395
Version Independent ID: 20df39b5-a4db-3065-a172-5a90d27909fb
Content: Data binding in depth - UWP app developer
Content Source: windows-apps-src/data-binding/data-binding-in-depth.md
Service: unspecified
GitHub Login: @mcleblanc
Microsoft Alias: markl

(sigh)  Microsoft's commitment to C++/WinRT is not appreciably more (yet) than to C++/CX.  C# is never the poor orphan step child.  C++ developers don't ask for every educational material in C# to be ported to C++/WinRT (or back in the day, C++/CX or even further back C++/CLI), but the educational material for C++/* should minimally cover all the bases.  Kenny Kerr's team tends to cherry pick their examples a little bit.  I'd like to see examples that go one increment beyond what Kenny Kerr's team cherry picks.  (Obviously no one wants to air out dirty laundry to showcase an area where C++/WinRT is lackluster or worse cannot do at all, but Microsoft shouldn't let that duty fall to the public to wander aimlessly trying to figure it out.)
Specifically there are areas where C#'s "as" clause comes in mighty handy that I have not fully understood in C++/WinRT.  C++/CX has slightly fewer of these lost-in-translation areas.
I don't mind you closing this one individual issue, but I do very much mind Microsoft as a collective failing to itemize the 100 or so commonplace programming idioms in C# that need to have analogous idioms in C++/WinRT (or in an earlier era, C++/CX or C++/CLI).  Say, 88 of the 100 are well-covered by examples provided by Kenny Kerr's team.  Say, 5 of the remaining 12 are able to be guessed by adequately-experienced developers, even if they have never seen that topic before in textbook-esque examples.  That leaves, say, 7 out of the 100 C# idioms that C# developers take for granted that C++/WinRT developers are left pondering and pondering and pondering what clever C++-ish trick to do because neither C++ nor C++/WinRT have a direct equivalent.  Something in the vicinity of the "as" clause and typecasting in C# is a recurring pain for me in C++/WinRT development.  Instead of learning some idiom, I radically redesign the UI to no longer need that "as" clause if it were C# instead of C++/WinRT.  This is incredibly inefficient and disheartening.
We don't need the Bookstore app example for C++/WinRT per se, but we need some way of teaching the, say, 7 C# idioms that Kenny Kerr's team haven't cherry picked in their examples (likely for a reason) that C++ lacks a direct equivalent or C++/WinRT lacks a direct equivalent (that works in all C#-UI cases instead of cherry-picked cases).

@optikos, regarding the "examples cherry-picked by Kenny Kerr's team", are you referring to the code examples that appear on GitHub, and Kenny's blog? I'm hoping to understand where the gaps are, and what they are.
If there's anything I can add to the official C++/WinRT docs, whether conceptual or API reference, then it would be great if you could leave a GitHub issue on a topic in one of those content sets, and let me know what's missing. If you do so, then I'll automatically see it. Those content sets are the ones that are currently officially supported when it comes to C++/WinRT documentation.
There's documentation for as and try_as in Instantiating and returning projected types and interfaces, the as function, and the try_as function. As those docs say, the notion of as is essentially that of IUnknown::QueryInterface. You can think of it as a cast (similar to C#'s as), but it's probably best to think of it as performing a QueryInterface, because that is actually how it's implemented. Please let me know whether this info helps and, if not, what's missing from the info. For example, are you needing to cast between projected and implementation types? For that, a topic such as winrt::get_self would be helpful. That topic in turn links to conceptual content around casting in both directions, as well as in-depth docs around the distinction between, and purpose of, implementation types and projected types.
~Steve

(sigh) Yes, I am aware of try_as.  I don't know what it is that I don't know (or else I might perhaps have the insight to provide the solution to my own gap of knowledge):  a chick & egg problem.  There is something in the vicinity of try_as that I don't get.  The cherry-picked examples from Kenny Kerr's team seem to pick only the low-hanging fruit.  They don't seem to take something substantial like this Bookstore app in C# and really dig deep to transliterate every C# idiom utilized in this Bookstore app to C++/WinRT.  That is why I requested that this Bookstore app would be a wonderful demonstration of transliterating C# idioms directly or indirectly into whatever the mapping to C++/WinRT would be, without skipping any UI-functionality portion of this Bookstore app.
I learn new tech best when I see a direct before-&-after comparison of the prior tech to the new tech for the same topic.  So far both your closing of this issue and the cherry-picking of low-hanging-fruit examples in GitHub by Kenny Kerr's team are obstructing my ability to learn the 100-ish C++/WinRT idioms that are the analogue of the 100-ish C# idioms that C# programmers take for granted.
I am rather frustrated by road-blockage after road-blockage after road-blockage from various portions of Microsoft on revealing/teaching this information.  I don't know what I don't know.  It is in the vicinity of using try_as to port the C# Bookstore app to C++/WinRT.  It is also somewhere in the vicinity of C++/WinRT types for UWP .winMD types not quite being full-fledged C++ types.  My lack of understanding falls somewhere in the vicinity of 1) C#'s as, C++/WinRT's try_as, 2) the UWP DLL ASP types, 3) C++/WinRT's disconnect with full-fledged C++ types, and 4) C++ typecasting being a no-no on this topic but being at the heart of C#'s as mechanism.  The C# community doesn't suffer such road-blockages on all fronts from all departments at Microsoft.  But C++/CLI then C++/CX and now C++/WinRT repeatedly does suffer from such road-blockages.
If even one of the various departments (and this isn't the first/only GitHub issue for request to port existing C# or C++/CX app to C++/WinRT outside of Kenny Kerr's cherry-picking-examples team) would expend as much effort in actually porting an entire already-existing substantial C# example/sample app to C++/WinRT as they expend in rejecting my requests, we would have had a not-cherry-picked C++/WinRT example/sample app by now.  But instead of actually learning what I don't understand regarding C++/WinRT's try_as (or learning where C++/WinRT has an overt lack of feature that I keep butting my head into), I learn to be the best GitHub reply-commentator to rejected GitHub issues.  Which would Microsoft rather I be:

a C++/WinRT programmer who gets past my try_as obstacle via one of these request to port an already-existing C# example/sample app to C++/WinRT, or

forever be a professional reply-commentator to rejected reasonable-request GitHub issues.

It gets quite old having multiple Microsoft departments reject my GitHub issue requests to port an already-existing C# example/sample app to C++/WinRT so that I can compare not-cherry-picked substantial set of C# idioms mapped into analogous C++/WinRT idioms.  But I am a patient man.  Someday I will find the Microsoft employee who works for the right manager who doesn't reject my reasonable-request GitHub issues that request the C#-to-C++/WinRT port of a substantial example/sample app.
Normally, in the face of repeated road-blocks for learning a topic directly from the source, I would just give up on direct-from-the-source learning and go buy a multihundred-page textbook from which to absorb the whole topic.  But for C++/WinRT, there is absolutely no book available on Amazon.com.  So I keep coming back here to GitHub issues (and radically redesigning my UIs to bypass the need for try_as).  Perhaps the reason for this is that the authors who try to write such a book for C++/WinRT are having the same roadblocks as I am.

I hear you, @optikos, and I'll see what I can do regarding providing C++/WinRT code examples for this topic. It's definitely on my list, and your feedback helps me to prioritize it.
~Steve

Thank you.  Even listening to me this far is further than I have gotten on other similar GitHub issues on this topic.

Hi, @optikos, I've made some progress porting Bookstore2 to C++/WinRT. On the to which this issue is attached, the Bookstore2 link (under the heading "Sample apps that demonstrate {Binding}") now downloads a zip that contains both cs and cppwinrt folders, each folder containing a functionally identical app in the respective language projection. One caveat is that I'm still getting the C++/WinRT version code-reviewed. But I didn't want that to block me publishing this preliminary version in case it unblocks you in any way. I'll post a follow-up here when this version's code-reviewed and final. Thanks for your patience! ~Steve


Feature Request: Support for modal pane mode and Hover Editor

The Manage forms pane currently supports only the sidebar pane view.
I tried to use the Hover Editor plugin to detach it, which works, but one cannot create a new form or edit an existing one. Closing the HE instance reverts to the sidebar showing the chosen action.
I suggest supporting a modal opening of the pane and possibly supporting the HE functionality.

Hey, thanks fot your feedback.
This is my first plugin for Obsidian and I am not yet very familiar with the different type of views.
How do you want to specify the opening mode? Through settings? Using a specific command?
For usability reasons the plugin opens by default in the sidebar in desktop and in a normal pane (the place where the editor is) in mobile.
I don't know what is required for the HE though

Look at the standard Obsidian setup, where you can open a note in a new tab, new tab group (horizontal and vertical split), or new window.
The Floating Search plugin (https://github.com/Quorafind/Obsidian-Float-Search) does exactly what I have in mind: it takes the core Search plugin and displays it as a modal and adds some additional features.
For the accessibility with the Hover Editor plugin I would contact "nothingislost" -- I believe he is the maintainer -- and ask him how to go about it.
I would offer respective options in the settings section with one to name as the default and register all commands to disclose them in the command pallet -- the users could then define their shortcuts.

I added a settings option to decide where it should open (for now, left, right or in the main view). Does that alleviate the issue?

It would, for a starter 😉. Do you still need to release the new version? I tried to update via BRAT, but the latest version is 1.4.0.

Oh, the modal option should not appear because I didn't implemented it yet.
I'm trying to keep this little side project focused so it doesn't take much time. I will keep this issue open to investigate how to do the modal thing properly


chore(deps): update kongponents to v6

Updates all @kongponents/* packages to the latest version.
Replaces @kongponents/ktable with @kongponents/ktablelegacy for the sake of an easier upgrade path.
Regenerates all component snapshots because they were created with the kongponents components rendered and due to their changes, they’re expected to be different now.
Implements a custom Jest snapshopt serializer in src/jest-replace-attribute-snapshot-serializer.ts in order to gain control over attribute values. Since Kongponents v6, a lot of them are generated UUIDs which change with every test run make snapshot testing impossible.
Implements #347.
Signed-off-by: Philipp Rudloff<EMAIL_ADDRESS>

Some nits after clicking around. Not sure if they are directly correlated with the upgrade. It can be done in separate PRs if needed
Button looks weird (notification bell -> click on the mesh)
The items are short and are changed to be longer after the click.

Fonts are a bit weird overall

Fonts on the tabs seems to be larger than anything other

I think we need spaces here

@jakubdyszkiewicz
Notifications modal → single mesh view
I’ve moved the button to its own line and actually made it a button. For some reason it was a badge before.
I also made sure the modal content takes up the full width by default. This is a spacing behavior of KModal which tries to generate space to the right of the content which I’m not sure why it’s done.
Weird fonts for the breadcrumbs menu
I’ve lowered the font weight for the breadcrumbs menu. This is also caused by the default style of the underlying Krumbs component.
Relatively large font size in tabs
This also a default style. Personally, I feel like most other things got smaller, but relatively speaking, that’s of course the same. Not sure, yet, how to deal with this the best because we use this component in many different places.
Card with weird word wrapping
I made sure the content in the card wraps at the slash characters.


Lesson 6 Abstractions I

After learning about {ni} and {du’u}, I have noticed other abstractions such as {za'i} or “state of”. After talking to a member in #ckule, it has come to my attention that {za’i} would be a better abstraction for gleki instead of {nu}. Part of the reason I (and many others) were confused was because of one example for each abstraction. If we had two examples for each abstraction, we could greatly expand on the flashcards and make abstractions much easier to understand. What do you think?

Strongly agree, having two or more examples for each abstraction would help significantly!
Regarding "za'i" specifically, I would prefer to cover it in a future lesson. According to CLL 11.3: Types of event abstractions, "za'i" is a more specific type of "nu", so I think it makes sense to teach nu/du'u/sedu'u in Abstractions 1 and then cover the subtypes of nu in Abstractions N.
Perhaps you could add 3-4 examples for the subtypes mentioned in CLL 11.3 (point-event abstractor, process abstractor, activity abstractor and state abstractor) and hint that there exist separate words for each of those, but mention that they will be covered only in a later lesson?
I think this would make abstractions much easier to understand, as you mentioned, and would not place too much of a cognitive burden on the reader (no need to memorize all sub-event-abstractors initially).

Okay. I will hint at subtype abstractions for a later lesson, and I will mention that more than one abstraction can be included in a sentence. I will most likely show an example of this. Thank you.

Thank you!


nsd-control-setup recreate certificates

The current behavior do not recreate private keys, but the script recreate certificate. I propose to not recreate the certificate (like private key) when certificate already exist.
If you are ok with the patch, i will open the same patch on unbound.

Not a bad idea, but the resign is so that it is again valid for $DAYS.  The change would make it so people cannot resign.  Not sure why to have it then?

The intent is to make nsd-control-setup idempotent, which allows to run it again and again without to have to reload or restart NSD. You right with this patch we can't resign and it's an important feature; I add a flag like -f or -r to resign certificate. Are you ok with this solution?

Sure that would work fine.  Why do you need it to be idempotent, then?  What needs to run this script again and again?  Trying to understand what you need from it, the solution looks fine (or an option for that use case, if that is somehow different from create certificates or resign certificates).

I need idempotent script, because I have script idempotent script to bootstrap my servers, and scripts exec this command, the script is use for create new server from scratch and to update existing server configuration.

Some context, I have add -r flag to recreate generated certificates.


Unity ads plugin not working on Android

With the latest unity ads plugin there is a bug. First load of app, init fires and there is a response so I load the waterfall.
This is reported in console  plugin.unityads.v4: 1.0.0 (SDK: 4.5.0)
Restart the app and ads do not work at all.
This is reported in console ERROR: unityads.setPersonalizedAds( bool ), init() should only be called once
This is repeatable and exists on all devices with different versions of Android.  So far this problem is on 9, 10, 12 and 13 (I don't have an Android 11 device)

This is fixed with new update

So what was the problem and why is it such a battle to get you to understand the bug?

I am not that familiar native.systemExit(). But it’s not the same force closing the app/putting it into a cold state or suspending the app. For the record I don’t regularly use an android phone, and mostly deep in the Apple iOS Ecosystem. So would never and million years thought to test native.systemExit. I don’t want to battle and I don’t think of that way but you should never assume people just know what your talking about especially without posting code and/or being “clear” about how to reproduce the issue

You got a very clear use case with videos... just because you don't read what I put that is not my fault.
You have got to get a bit more professional with your testing/updates.

Please be constructive and respectful. This is neither.

You have no idea how frustrating it is trying to explain to players why something doesn't work.  Try to see the other side of things.
If I say there is a bug, I mean there is a bug.... I don't expect to have to battle this.  We are all on the same side surely?


Request : remove dependency to pedantic

The pedantic library is considered deprecated : see https://github.com/google/pedantic#readme .
There are migration instructions here : https://github.com/dart-lang/lints#migrating-from-packagepedantic .
unawaited is now available natively as part of dart:async so we could maybe rely on it instead, and remove the pedantoc dependency all together ?
Thanks !

Thanks @tsimbalar! Good to know! Happy to receive a PR is someone is up to the task! Adding Good first issue label just in case want to tackle this.

here you go :

https://github.com/koa-health/horizontal_blocked_scroll_physics/pull/9


When install is completed caused a very serious bug.

Microsoft PowerToys version
0.57.2
Running as admin

[ ] Yes

Area(s) with issue?
PowerToys Run
Steps to reproduce

Download a software
Install it
Cause a problem: the PowerToys.Runner process auto recreate itself out of mind😮.

✔ Expected Behavior
No response
❌ Actual Behavior
No response
Other Software
No response

When I reboot my computer the error has disappeared.

/dup #17720


Prevent calling Index#delete with an empty string

Bug introduced with #735
ES client return an Elasticsearch::Transport::Transport::Errors::BadRequest error, which is not rescued. To keep the same behaviour, I simply call the ES client with the index_name.

@Bhacaz Thank you very much!
Could you please describe how to reproduce this bug in a little bit more detailed way?
Or add a spec, that would fail without changes in lib/chewy/index/actions.rb. Added in this PR spec successfully passes on master.

@Bhacaz Thank you very much!
Could you please describe how to reproduce this bug in a little bit more detailed way?
Or add a spec, that would fail without changes in lib/chewy/index/actions.rb. Added in this PR spec successfully passes on master.

I didn’t dig enough about the error. An Elasticsearch::Transport::Transport::Errors::BadRequest will only occurs in ES 1.X (which is the version I currently working to upgrade). Here what I found just to keep it this PR well documented.
If the index doesn't exists (or already destroyed)
ES 1.X

get_alias return {}
{}.keys.join('') # => ''
delete(index: '') throw Elasticsearch::Transport::Transport::Errors::BadRequest
raise the error because it's not rescued

ES 5.X and above

get_alias throw Elasticsearch::Transport::Transport::Errors::NotFound
Elasticsearch::Transport::Transport::Errors::NotFound is rescued

May I suggest 2 options:

Closing the PR, because it's a problem only in ES 1.X.
Adding a safe guard at the beginning of Chewy::Index::Actions::ClassMethods#delete to return false if the index doesn't existe.

I didn’t dig enough about the error. An Elasticsearch::Transport::Transport::Errors::BadRequest will only occurs in ES 1.X (which is the version I currently working to upgrade). Here what I found just to keep it this PR well documented.
If the index doesn't exists (or already destroyed)
ES 1.X

get_alias return {}
{}.keys.join('') # => ''
delete(index: '') throw Elasticsearch::Transport::Transport::Errors::BadRequest
raise the error because it's not rescued

ES 5.X and above

get_alias throw Elasticsearch::Transport::Transport::Errors::NotFound
Elasticsearch::Transport::Transport::Errors::NotFound is rescued

May I suggest 2 options:

Closing the PR, because it's a problem only in ES 1.X.
Adding a safe guard at the beginning of Chewy::Index::Actions::ClassMethods#delete to return false if the index doesn't existe.

@Bhacaz Thanks, let's close this for now.


add font

What type of PR is this? (check all applicable)

[X] Feature
[ ] Refactor
[ ] Bug Fix
[ ] Optimization
[ ] Documentation Update
[ ] Other (please specify here: )

Description of what this Pull Request does
Update font, kept color theme already in place
Related Tickets & Documents

Closes #22
Related Issues: (enter ticket numbers here)

QA Instructions, Screenshots, Recordings
Check that font is aesthetically pleasing
Added/updated tests?

[ ] Yes
[ ] Not Yet, and here is why: explain here
[ ] I need help with tests
[X] No, and here is why: no tests required

Nice, I like it!


Feat: add PipelineListener interface

Hi , related pull requests (#901) , (#878) for implementing an ActiveMQ listener interface :) .

Since no objection, I am merging this to continue working  :) .


[Improve] Improve streampark-test-utils module based on [3.10 Pre-Conditions Checking]

Search before asking

[X] I had searched in the feature and found no similar feature requirement.

Description
[Improve] Improve streampark-test-utils module based on 3.10 Pre-Conditions Checking
Usage Scenario
No response
Related issues
#2986
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

N.A


Fix polygon_to_mask_array return mask shape

Fixes #267

General comment, why move a polygon to a rectangle for the mask array operation? @alessiamarcolini can you give me a rationale of this choice?

I changed the naming because a polygon can have more than 4 vertices and we explicitly require a CoordinatePair which corresponds to 4 vertices. Probably a more appropriate name would be "quadrilateral" but to me it's a bit ugly... @ernestoarbitrio what do you think?

I changed the naming because a polygon can have more than 4 vertices and we explicitly require a CoordinatePair which corresponds to 4 vertices. Probably a more appropriate name would be "quadrilateral" but to me it's a bit ugly... @ernestoarbitrio what do you think?

gotcha , I would say that your name is absolutely appropriate. So let's keep it


[refactor] #1249: Remove structopt from iroha_core.

Description of the Change
Remove structopt from iroha_core. Should be merged after #1739.
Issue
Closes #1249.

Benefits
Structopt wasn't doing much in iroha_core beyond making compilation take longer.
Possible Drawbacks
None
Usage Examples or Tests [optional]
by setting the environment variables, anywhere in the iroha git folder.
cargo run --bin iroha -- --submit

for a short override and same effect,
IROHA2_GENESIS_PATH="/home/app/Git/iroha/configs/peer/genesis.json" IROHA2_CONFIG_PATH="/home/app/Git/iroha/configs/peer/config.json" cargo run --bin iroha -- --submit

we could also consider using pico-args which is super lightweight if it would provide a little more stability to development process.
Also it seems that structopt is out the window soon


Fix issue #434 - bad reference for argo-controller charm

fixed reference for charmhub
added formatting to envoy line

Thanks @paulomach . By default, the bundle points to Charmhub, there's no need to prefix the charm name withch. I'll take a look at #434 to see if I can reproduce the issue.

There was an issue with argo-controller during the migration from Charmstore to Charmhub, this was fixed by the Charmhub team yesterday. Therefore it should not be an issue anymore.


TTS Feature: Read track titles aloud for non-display phonieboxes

One idea i've had a while ago:
Track title will be read aloud before the track starts playing.
Use-case:

One folder with a lot of children audiobooks linked to one single rfid card

example: Benjamin Blümchen, 15 stories. My kids have to wait a while to figure out which story is currently playing to find a particular track without display (especially if they are still too young to read).
the annoncement of the track title would help them to know this in a few seconds
this prevents the usage of 15 rfid cards for 15 tracks

It's possible, there are text to speech encoders for open source / linux. They are a bit CPU heavy. And language sensitive. So you need to decide english or german. I have not worked with such software for a decade :) but let's just float the ticket here, a nice idea.

It's possible, there are text to speech encoders for open source / linux. They are a bit CPU heavy. And language sensitive. So you need to decide english or german. I have not worked with such software for a decade :) but let's just float the ticket here, a nice idea.

I did a first test yesterday with pyttsx3.
It seems to be the best approach in terms of voice quality and avoiding proprietary code like google tts.
As i did not work on this project since years, could anybody help me to find the right place to call my text2voice function if a new track starts playing?

Implemented in V3 (see here).

We have Text-to-Speech implemented, but it does not read the song out loud. This should be implemented in V3 as an option.


Updating tests that failed in CI

Description
These are failing in CI due to an error from the OWS. I think we'll need @valpesendorfer help figuring out why they're failing in CI but not when the test is run locally. Skipping until then.
The tests are failing due to a 500 from https://api.earthobservation.vam.wfp.org/ows/?service=WCS&request=GetCoverage&version=2.0.0&coverageId=wp_pop_cicunadj&subset=Long(95.71,96.68)&subset=Lat(19.42,20.33)
How to test the feature:

[ ]
[ ]

Checklist - did you ...

Test your changes with

[ ] REACT_APP_COUNTRY=rbd yarn start
[ ] REACT_APP_COUNTRY=cambodia yarn start
[ ] REACT_APP_COUNTRY=mozambique yarn start
[ ] Add / update necessary tests?
[ ] Add / update outdated documentation?

Screenshot/video of feature:

@gislawill I think it would be better to update this test instead to not use a WCS request

Thanks Eric. This update looks good to me. One thought, could we use the server in our test suite (the locally running test server) rather than the production server? Would rather rely on a the functionality already in our test suite than introducing a production dependency.
Also, I'm currently in the middle of a move but can test that suggestion out later this week


The api overwrites font and color

I used to be able to set forecolor to Color.Red, however it now errors.
I used to be able to do New Font("Arial", 20), but now it errors.
Is there a way to make it not use the common namespaces, or a way to retrieve the original color and font stuff?
I'm using visual basic.

You are supposed to use the builtin types. i don't want to include windows forms or wpf dependencies.
you can use the helper methods to create brushes and fonts https://github.com/michel-pi/GameOverlay.Net/blob/master/source/GameOverlay/Drawing/Graphics.cs#L271
Also, there is no such constructor for a Font in my library.


bug: Countdown does not work in cdn versions

What version of daisyUI are you using?
4.4.24
Which browsers are you seeing the problem on?
Chrome, Firefox
Reproduction URL
https://play.tailwindcss.com/Bjca0H4e8p
Describe your issue
I am using the cdn version of the daisy ui, but this problem exists in the codepen and tailwind play version too (which are the cdn version i suppose).
Essentially, the countdown numbers are not changing when i put them on the screen. I suppose there is a javascript code doing that which does not exist in the cdn version.

Please read the docs:

Countdown
Countdown gives you a transition effect of changing numbers.
You need to change to --value CSS variable using JS. Value must be a number between 0 and 99.


Underline in the back button of the quiz game

There is an underline in the back button(in the Quiz Game Page) as it is a button created by Hyperlink .
The underline under the text of the Back Button can be removed .
If you think that needs to be changed  please assign this issue under the LGMSOC'21

@Amit-45 can you assign me this issue

Assigned @Amit-45


fix missing requirements.txt in dockerfile

was failing on docker image curation due to a missing requirements.txt file, which is now being pulled in.
was previously failing to build

Of course! Awesome tool, wanna help how I can!


No Windows version

Add windows version

Doesn't work

Windows prebuilts are available at https://github.com/google/perfetto/releases/download/v38.0/windows-amd64.zip
If you are using x86, we have not and have no plans on supporting Windows versions of those prebuilts as Microsoft has been x64 only since Windows 11 in any case.


No space after number in relativeTime for zh-cn and zh-tw

While using the relativeTime method, there is no spacing after the number for locales zh-cn and zh-tw
*zh-cn : https://github.com/moment/moment/blob/develop/src/locale/zh-cn.js#L81
zh-tw : https://github.com/moment/moment/blob/develop/src/locale/zh-tw.js#L79*
Examples: Chrome 50+on Windows 10, Internet Explorer 10+ on Windows 10

@ben-lin @hehachris @suupic @zenozeng ?

The code looks fine. It takes the entire argument including the unit, meaning 10天 is what you passed to the lib. @MananS77 do you have the actual code how you used it?


Assignment

TITLE: UofT-DSI | Shell - Assignment 1
What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
I have updated the assignment answers
What did you learn from the changes you have made?
I have learn the basic Git & shell commands
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
This was the basic straightforward solution
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
I have not face any major challenges in completing this assignment.
How were these changes tested?
I have locally tested, running the script.
A reference to a related issue in your repository (if applicable)
Checklist

[ X ] I can confirm that my changes are working as intended

@devangi-hub Please make sure you have completed part 2 of the assignment (you may see it in the assignment_instruction file)

Great job! It's perfect!

closing this


Feature request: Option to provide device ID to the scan devices API so it can complete as soon as that device has been found.

I'm using tinytuya in a home assistant integration to find the IP address (and protocol version) of Tuya devices enumerated initially from the cloud API but utilizing the smart life app to get them instead of needing a Tuya IOT account. The user chooses the device they want to add and then there's currently an 18s wait while I use deviceScan to try to find the local devices to try to get the IP address of the one they chose. It'd be great if I could pass a device filter in up front so the scan completes as soon as it sees that device.

That's a great suggestion @AdrianGarside. Can you share the code on how you are currently running the scan?
I think we could add a simple scan_id() function to https://github.com/jasonacox/tinytuya/blob/master/tinytuya/scanner.py that simply returns the IP address as soon as it detects the broadcast from that device.

It's still in progress but it's pretty basic:
https://github.com/make-all/tuya-local/pull/1881/files#diff-a0269ebba252310e431b95b4cde30017584df7088b8243db81413ab92af8331b
I'm just calling:
tinytuya.deviceScan(verbose=False, byID = True)
And then looking for the device by ID in the returned dictionary. Although as I write this it occurs to me that I could be running this in the background from the moment the user starts the config flow so by the time I know which device they are adding I already have the results. I could increase the timeout if I do that too. Oh... except having the app open tends to block the discovery from succeeding and having the app open is required for the QR based authentication flow.

This is already implemented in both core and scanner.
Core:
https://github.com/jasonacox/tinytuya/blob/master/tinytuya/core.py#L619
def find_device(dev_id=None, address=None):
    """Scans network for Tuya devices with either ID = dev_id or IP = address

    Parameters:
        dev_id = The specific Device ID you are looking for
        address = The IP address you are tring to find the Device ID for

    Response:
        {'ip':<ip>, 'version':<version>, 'id':<id>, 'product_id':<product_id>, 'data':<broadcast data>}
    """

result = tinytuya.find_device(dev_id='abc123')
Scanner:
https://github.com/jasonacox/tinytuya/blob/master/tinytuya/scanner.py#L973
def devices(verbose=False, scantime=None, color=True, poll=True, forcescan=False, byID=False, show_timer=None, discover=True, wantips=None, wantids=None, snapshot=None, assume_yes=False, tuyadevices=[], maxdevices=0):
    """Scans your network for Tuya devices and returns dictionary of devices discovered
        devices = tinytuya.deviceScan(verbose)
...
        wantids = A list of Device IDs we want.  Scan will stop early if all are found

result = tinytuya.scanner.devices( poll=False, wantids=['abc123', 'def456'] )

🤣 I'm blind!  Thanks @uzlonewolf .... There you go @AdrianGarside  - find_device() is even documented in the core header.
https://github.com/jasonacox/tinytuya/blob/62c7f13fe814cbabcd752e2201036e1b12a41742/tinytuya/core.py#L19-L28
I always wanted to create a good API doc to go with the project. I think this proves we (at least I) need it. 😊

Thanks. I did look at the docs and code but I missed that entirely.

Well, that makes two of us... and to be fair, the main API notes in the README haven't been updated in quite some time and didn't include the great additions by @uzlonewolf that you were looking for. Hopefully this doc update will help others.
I'm still going to work on getting a better API doc... if anyone has advice on a good tool/trick to do that, let me know. :)
Thanks for opening this issue!

@jasonacox @uzlonewolf now that I have my Tuya devices finally integrated into home assistant working locally, I want to move them to my IOT vlan. That will presumably break the newly added discovery since that vlan is blocked from sending anything to my real network. I can adjust my rules to allow the broadcast ports to be allowed through. Will that be sufficient for the scanning to then find them or are there other requirements? If I have to I can workaround the lack of scanning and add the IP address manually but I'd like to make life easier for myself in the future by allowing future new tuya devices on my IOT network to be discoverable in the automated way.
I ran into a similar problem in that my WSL install that I use for my test Home Assistant instance gets a 172.xxx IP address while my real network is 192.168.0.x. It couldn't detect any of the devices either since it couldn't see the broadcasts. I had to test on my production instance which was a pain. I'm planning to see if I can solve that too but it'll be a different solution needed.

Thanks for the update @AdrianGarside . Have you considered dual-homing your home assistant system to allow it to hear/control the Tuya devices while giving you access to the portal? It has its own security risks, if you are looking for strict isolation but could be an option.

I really don’t want to do that. I think it’s an inevitability that iot devices will be hacked so I try to keep all I can off my main network - discovery is usually where I run into blockers for that. The new gateway is running fine on my IOT network so I wouldn’t want to take a permanent security hit just to make initial one time addition a bit easier.
Since wireshark can see the broadcasts I’ve been trying to work out why tinytuya can’t. The VM that’s hosting my home assistant on Debian is on my main network so it ought to be able to see the broadcasts too but I’m not sure of any good linux tools to let me confirm that it can, especially since it’s running without a GUI.
Maybe it’s time to bite the bullet and move that entire VM over to the untrusted network and start treating it as untrusted too. I could get all my esphome devices off my main network then too (same discovery issue with those). That could be an involved migration though.

tpcdump on the debian VM doesn't seem to be seeing the broadcasts from <IP_ADDRESS>:
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
22:19:50.674960 IP <IP_ADDRESS>.49154 > <IP_ADDRESS>.6667: UDP, length 188
22:19:51.203399 IP <IP_ADDRESS>.50044 > <IP_ADDRESS>.6667: UDP, length 268
22:19:55.675267 IP <IP_ADDRESS>.49154 > <IP_ADDRESS>.6667: UDP, length 188
22:19:56.210967 IP <IP_ADDRESS>.50044 > <IP_ADDRESS>.6667: UDP, length 268

Understood! Thank's for sharing and the additional context. If you figure it out, let us know!

tshark (command line wireshark) for linux also doesn't show the 10.10.10.x originated broadcasts. Maybe that's a linux routing difference to Windows, maybe it's a host VM networking difference (my HA runs in Debian in a VM on a Windows 10 host PC).


Upgrade to Camel 2.23.0

(when released)

check positions are now more accurate for validation (tests might need to be adjusted) (see https://issues.apache.org/jira/browse/CAMEL-12640 )

verified with master branch


Not listed yet: speakerinnen.org

The website at this url is unlisted: https://speakerinnen.org/

We appreciate the help, this website is now on its way to being listed!


[Map] MH-(DaV)-BoomBoomBridge-2023

Your description here
Hi hello , i have  put this map with all files, but i look only .unr files. i have put complete map on mediafire , please add a files if you have possibility. thanks for all
Map download link : https://www.mediafire.com/file/7095devscriklgm/MH-%2528DaV%2529-BoomBoomBridge2023.rar/file
my Email<EMAIL_ADDRESS>if you have a request :)
URL: https://unrealarchive.org/maps/unreal-tournament/monster-hunt/D/mh-dav-boomboombridge-2023_d7c0286b.html
Hash: d7c0286bd4a71c618cc399eeda21e2e818e41409
Current name: MH-(DaV)-BoomBoomBridge-2023

fixed: https://unrealarchive.org/maps/unreal-tournament/monster-hunt/D/mh-dav-boomboombridge-2023_fd9a8052.html


Give a script for pellet eating function for bots

Any help regarding this is appreciated

got skype?

cupidstunts have you the script ? my skype : iTwiGXDev

i have it yeah :)

Cupid stunts Skype me at -piyush2510001

cupid add me again i canceled the request skype  : iTwiGXDev

added you both.. i think

Yup

@gamer2510 have dude :)

fun

Ur the Cupid stunts

@gamer2510  lol. is that an insult or a compliment?


Correct Markdown Syntax

Small change to correct formatting of one line.

Thanks, we'd appreciate help improving and debugging the new docs if you feel like it :)
They're at https://github.com/petkaantonov/bluebird/tree/3.0docs/docs/docs some parts are missing but most should be there :)

You're welcome! I'm having a look at them as we speak. Just got started on Promises with node... looks promising :stuck_out_tongue_winking_eye: