Feature/refactor example default

Fill default values for properties on application of patch/modules
Fix #3480

Had to add a test case for deprecated method, my assumption was its ignored from Codecov.

Good job here. cc @pascalgrimaud I think this deserve a Bounty :)


feat: Add ipParser for Ipmatch function

Signed-off-by: xiaobeiswift<EMAIL_ADDRESS>

lgtm

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add !Severity option - Discord Employees only

I honestly am not happy with how the case switch is happening, but I personally can't figure out a better way at this very moment
Spoken to you, Logiz, and you're free to make changes/edits or ask me to if necessary.

Make a module for the new BB kthx


new #132: include submitter id and name in .csv.zip export.

adds them at the very end.
if we cannot find submitter information we omit the data for the row.
resolves #132.

oh i see; i can leave a clarifying comment on that.
On Mon, Dec 31, 2018 at 15:46 Matthew White<EMAIL_ADDRESS>wrote:

@matthew-white approved this pull request.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/opendatakit/central-backend/pull/169#pullrequestreview-188543058,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHMAg__imoeEx3K3T2PKgVsxQOykWUJks5u-qHagaJpZM4ZbVq1
.


Nixie Tubes mod linked improperly

Mod source
PyAE Beta
Which mod are you having an issue with?

[ ] pyalienlife
[X] pyalternativeenergy
[ ] pycoalprocessing
[ ] pyfusionenergy
[ ] pyhightech
[ ] pyindustry
[ ] pypetroleumhandling
[ ] pypostprocessing
[ ] pyrawores

Operating system

=Windows 10

What kind of issue is this?

[X] Compatibility
[ ] Locale (names, descriptions, unknown keys)
[ ] Graphical
[ ] Crash
[ ] Progression
[ ] Balance
[ ] Pypostprocessing failure
[ ] Other

What is the problem?
Placement of the Nixie Tubes mod is not tuned for the current tech tree.
It currently uses 'Advanced Electronics' as its pre-requisite.
It should have Circuit Network as its pre-requisite, and probably doesn't need logistics science. Cost should be on par with circuit network, and component costs should be on par with a constant combinator.

Steps to reproduce
Mod is nixie-tubes 1.1.3
https://mods.factorio.com/mod/nixie-tubes
Additional context
No response
Log file
No response

@ShadowGlass0 Mind confirming if this is the domain of postprocess changes or if it should be filed elsewhere?

Yeah, I have an idea for a generic solution for this type of issue (I assume nixie tubes don't actually use advanced circuits)


knowledge embedding

Hello, I want to ask how to use other embedding methods except complEx? Like Rotate.

First pretrain the right embeddings. Then modify the scoring function used in the QA models, for example, see this line
https://github.com/malllabiisc/EmbedKGQA/blob/b2a33674a0a6653745e55a3da53cc2d7e00c372d/KGQA/LSTM/model.py#L24
and change the function to your choice


Add hostname resolution

Add hostname resolution

Sorry, that's bad.
Maybe it's my personal preferences but using dynamic in Dart should be avoided as much as possible.
Also I will look at different approach to achieve basically same functions. (Should update in next week)
Sorry if that feature required now but newer dart version have broken significant part of code used in this library.


Delete element using delete button from the keyboard

Can we add a possibility to delete an element using the delete button on the keyboard? Right now if you want to delete an element, you select that element and click "Delete element" button on the UI of shinyuieditor but I think it will be useful to also have a possibility to delete it by pressing delete button from the keyboard .

Hi @shahronak47 ,
Sorry for the delay on responding to this -- holidays have me behind!
This is a great idea and I find myself trying to delete elements with the keyboard, too. Probably a good sign it's a necessary feature.
One fear I have is it will make it easy to accidentally delete something, do you think there should be a confirm prompt or is the ability to use the undo button enough to keep it safe?

If I'm able to delete the element from the keyboard I would also expect to undo the operation from the keyboard using Command + Z (Ctrl + Z).

We think alike! I've got a PR up for the dev branch (#135) that implements both delete, undo, and redo as keyboard shortcuts. Early next week I should have a release with the new dev branch features. Once it's all merged I'll update here.

Sorry for the delay! We were waiting on getting credentials to publish to the visual studio code marketplace on that PR. Now it's done and merged with main in #138 so keyboard extensions are available! Thanks for the feedback!


Requesting the addition of a timeout parameter in the api functions

It would be great if a user could adjust the timeout parameter for Httr GET requests from within the Rnssp api functions like get_api_data.
For example, something like below:
api_data <- get_api_data("url", timeout = 100)

Thank you @jedevies  for your contribution.
The timeout argument has been added across to the function and methods accordingly. The enhancements are pushed to the dev branch and will be available in the upcoming version 0.3.1.


[Error] sj does not work properly when an argument is used before the command.

Describe the bug
When running sj with an argument before the command, the tool is not working properly.
To Reproduce
A code block containing the command executed with output:
$ sj -a 'Mozilla/5.0 (X11; U; CrOS i686 0.9.128; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.341 Safari/534.10' automate -u 'https://petstore.swagger.io/v2/swagger.json' -T https://petstore.swagger.io/v2

INFO[0000] Gathering API details.

INFO[0000] Available authentication mechanisms:
    - api_key
INFO[0000] An API key can be provided via the header api_key. Would you like to apply one? (y/N)

    - petstore_auth

Title: Swagger Petstore
Description: This is a sample server Petstore server.  You can find out more about Swagger at [http://swagger.io](http://swagger.io) or on [irc.freenode.net, #swagger](http://swagger.io/irc/).  For this sample, you can use the api key `special-key` to test the authorization filters.

$ sj -a 'Mozilla/5.0 (X11; U; CrOS i686 0.9.128; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.341 Safari/534.10' automate -u 'https://petstore.swagger.io/v2/swagger.json' -T https://petstore.swagger.io/v2

INFO[0000] Gathering API details.

INFO[0000] Available authentication mechanisms:
    - api_key
INFO[0000] An API key can be provided via the header api_key. Would you like to apply one? (y/N)
y
What value would you like to use for the API key (api_key)?special_key
    - petstore_auth

Title: Swagger Petstore
Description: This is a sample server Petstore server.  You can find out more about Swagger at [http://swagger.io](http://swagger.io) or on [irc.freenode.net, #swagger](http://swagger.io/irc/).  For this sample, you can use the api key `special-key` to test the authorization filters.

Expected behavior
Run the command even if the argument is placed first.
Screenshots

Desktop (please complete the following information):

OS: ArchLinux
Browser: Firefox
Version: 1.9.0 (last, built from github)

Additional context
As seen in the "Usage" of the --help, it seems we can use the flags (or arguments) before the command :

But it's not the case at the moment.
Thanks.

Hey @s7x, this won't be implemented at the time. The highlighted portion of your screenshot shows that you can provide either flags or commands, but if you execute the help command for one of the sub-commands you will see that they each have their own unique flags. Example:
$ sj automate -h
The automate command sends a request to each discovered endpoint and returns the status code of the result.
This enables the user to get a quick look at which endpoints require authentication and which ones do not. If a request
responds in an abnormal way, manual testing should be conducted (prepare manual tests using the "prepare" command).

Usage:
  sj automate [flags]

Flags:
      --get-accessible-endpoints   Only output the accessible endpoints (those that return a 200 status code).
  -h, --help                       help for automate
  -F, --output-format string       The output format. Only 'console' (default) and 'json' are supported at the moment. (default "console")

Global Flags:
  -a, --agent string            Set the User-Agent string. (default "Swagger Jacker (github.com/BishopFox/sj)")
  -b, --base-path string        Set the API base path if not defined in the definition file (i.e. /V2/).
  -f, --format string           Declare the format of the definition file (json/yaml/yml/js). (default "json")
  -H, --headers stringArray     Add custom headers, separated by a colon ("Name: Value"). Multiple flags are accepted.
  -i, --insecure                Ignores server certificate validation.
  -l, --local-file string       Loads the documentation from a local file.
  -o, --outfile string          Output the results to a file. Only supported for the 'automate' and 'brute' commands at this time.
  -p, --proxy string            Proxy host and port. Example: http://<IP_ADDRESS>:8080 (default "NOPROXY")
  -q, --quiet                   Do not prompt for user input - uses default values for all requests.
  -r, --randomize-user-agent    Randomizes the user agent string. Default is 'false'.
  -s, --safe-word stringArray   Avoids 'dangerous word' check for the specified word(s). Multiple flags are accepted.
  -T, --target string           Manually set a target for the requests to be made if separate from the host the documentation resides on.
  -t, --timeout int             Set the request timeout period. (default 30)
  -u, --url string              Loads the documentation file from a URL

The "Global Flags" above can be used with all sub-commands, while the "Flags" can only be used with the automate command.
In any case, the sub-command is intended to be provided as the first argument as shown in the example commands and in the README file:
$ sj -h
...SNIP...
Example usage:

Perform a quick check of endpoints which require authentication:
$ sj automate -u https://petstore.swagger.io/v2/swagger.json

Generate a list of commands to use for manual testing:
$ sj prepare -u https://petstore.swagger.io/v2/swagger.json

Generate a list of raw API routes for use with custom scripts:
$ sj endpoints -u https://petstore.swagger.io/v2/swagger.json

Perform a brute-force attack against the target to identify hidden definition files:
$ sj brute -u https://petstore.swagger.io


Leverage openstack-ansible to setup caching

The current deploy variables for standing up keystone with openstack-ansible don't tell openstack-ansible to setup caching.
We should add those variables/roles to our deployment for performance since we recommend people run with caching enable. This would make performance runs on patches in review more realistic when compared to real-world deployments.

thanks dolph


Support [x] check box to indicate completion

There isn't a single agreed standard about notating tasks in Markdown, but many tools now support something like
- [ ] incomplete task
* [x] complete task

You have % completion. In order to improve interoperability with markdown used in other editors and task systems (e.g. NotePlan), please consider supporting at least the [x] syntax to indicate 100% completion.

I was deliberately starting with the simplest suggestion here, but this would be great.


Add gpu_type and device count to metrics

Clone of PR #30 with syntax fix.
Results:
# HELP dcgm_device_count Device count.
# TYPE dcgm_device_count gauge
dcgm_device_count 1
# HELP dcgm_sm_clock SM clock frequency (in MHz).
# TYPE dcgm_sm_clock gauge
dcgm_sm_clock{gpu="0",uuid="GPU-deecc6f6-2684-6d54-00fa-b419a8a56a56",gpu_type="Tesla-V100-SXM2-16GB"} 135
# HELP dcgm_memory_clock Memory clock frequency (in MHz).
# TYPE dcgm_memory_clock gauge
dcgm_memory_clock{gpu="0",uuid="GPU-deecc6f6-2684-6d54-00fa-b419a8a56a56",gpu_type="Tesla-V100-SXM2-16GB"} 877

When I build my image and try to run on a GPU machine, there's some error message but seems the metrics are fine
docker run --runtime=nvidia --rm --name=nvidia-dcgm-exporter ${my_image}

Failed to get unit file state for nvidia-fabricmanager.service: Unknown error<PHONE_NUMBER>
Starting NVIDIA host engine...
Collecting metrics at /run/prometheus/dcgm.prom every 1000ms...

Does anyone have clue on Failed to get unit file state for nvidia-fabricmanager.service

@guptaNswati

The fabric manager error is happening because its trying to find nvidia-fabricmanager.service. Whats the output of
systemctl status nvidai-fabricmanager? but it should not impact you if you are running the exporter inside the container

The fabric manager error is happening because its trying to find nvidia-fabricmanager.service. Whats the output of
systemctl status nvidai-fabricmanager? but it should not impact you if you are running the exporter inside the container

I can not find fabricmanager inside my container. It's a little bit weird, I try to build master changes without this PR and get similar issue.
If I use nvidia/dcgm-exporter from nvidia, I don't see the error message. I am guessing if I build the image in a wrong way.
$ cd gpu-monitoring-tools/exporters/prometheus-dcgm/dcgm-exporter
$ docker build -t <my_docker_hub>/gpu-monitoring-tools:191126

Verified this PR is working, can you help review the code?

Hello!
With version 2.0 you can now easily add these fields by changing the CSV file and adding the field you care about :)
Hope this helps!


Link to file issue with PackageEvaluator for developers

Now clicking on any of the links, e.g. to see the test log, will reveal a link to file an issue with PackageEvaluator. It otherwise remains invisible.


Is Chadburn discontinued?

Hello,
I noticed on
https://www.libhunt.com/r/chadburn
that Chadburn is considered as "DISCONTINUED"
What is your opinion?
Kind regards

That's a lie. They could have reached out to me first, but they did not.

Thanks for prompt answer. So closing. But I think you should probably ask them.

Thank you for alerting me to this.
I'm having legal look at this.


[FEATURE] Moving logout button

Description
As the new Nav bar is created and profile option already on the nav I dont see why we still need it on the top right, I think it would be better to remove it and also I think we should move the log out button to the nav as well and delete previous profile and logout options completely.
Screenshots

Additional information
I would like to work on this issue

You can work on cleaning this up :) and on logout button, keep font colour red with an icon of logout. Put this button at the bottom


[v1.1][ISSUE-274]update Readme

What changes were proposed in this pull request?
Final update for v1.1 documents

@Jian-Zhang , this PR is indented to do final document fix for 1.1 release

LGTM.


Increment GraalVM version in the SDKMan docs

Fixes #926

@sdelamo  is this ok to merge?  I just saw it was you who set it to draft?


Example configuration issues with td-agent 3

Just wanted to let you know I had some issues getting this plugin to run with the config example because the fluentd config parser (td-agent 3) failed to parse the matches field.
To resolve the issue I had to escape the quotes, so my configuration ended up looking like this
matches "[{ \"_SYSTEMD_UNIT\": \"consul.service\" }]"
In addition, I had trouble getting the storage configuration used in the example to work. I was only able to get it running once I changed <storage in-systemd-consul> to <storage>.

Thanks for the info ... you are indeed correct about the storage configuration...
For the matches config I think the problem is just because you are surrounding the config with quotes ...
matches [{ "_SYSTEMD_UNIT": "consul.service" }]"

Should work as expected ...


feat: Allow specifying formik status type

Closes #2153

This looks great! Just a few merge conflicts remaining. Is there anything I can do to help complete this?

@hboylan Resolved conflicts

Hey @doniyor2109 can you run yarn changeset and commit the changeset

@maddhruv Done

What's the status of this PR? I would love to see it merged :smile:

I like this in concept, but I don't know that the status and other sort of externalities that aren't shapes we have control of should be formalized into the Core Formik API. Personally, I'd rather see something like this:
// Plugins would automatically be typed like [FormikStatusPlugin<YourType>, FormikYupValidatorPlugin<Values>],
// and add the relevant bits to Formik's return value, manipulate Formik's reducer, and
// expose their own hooks like `useFormikStatus<YourType>();`.
// I have no idea if this is possible with current TypeScript version
const myFormik: FormikInitializer<Values, Plugins> = createFormik()
  .addPlugin(new FormikStatusPlugin<YourType>())
  .addPlugin(new FormikYupValidatorPlugin());

const MyForm = () => {
  const formik = useFormik(myFormik, { ...formikProps });
  // or
  return <Formik initializer={myFormik} {...formikprops} />
};

I've actually never used Status and I think it would be odd to fix the second type parameter of Formik to be this value, when there are a million other "things" that type parameter could be as we expand the TypeScript definitions.


Make RabbitMQ heartbeats messages respect noop mode.

When queue publishing is disabled, nothing should be connecting/writing
to RabbitMQ. We therefore want the heartbeats not to be sent in this
case.
The heartbeats rake task was constructing its own QueuePublisher
instance, and therefore wasn't picking up the logic for disabling it in
the initializer.

Test fail:
Failures:

  1) sending a heartbeat message on the queue should place a heartbeat message on the queue
     Failure/Error: delivery_info, properties, payload = wait_for_message_on(@queue)
     RuntimeError:
       No message found on queue
     # ./spec/support/message_queue_helpers.rb:14:in `wait_for_message_on'
     # ./spec/integration/heartbeat_message_publishing_spec.rb:24:in `block (2 levels) in <top (required)>'
     # ./spec/integration/heartbeat_message_publishing_spec.rb:15:in `block (2 levels) in <top (required)>'

Finished in 10.76 seconds (files took 5.78 seconds to load)
303 examples, 1 failure

Failed examples:

rspec ./spec/integration/heartbeat_message_publishing_spec.rb:20 # sending a heartbeat message on the queue should place a heartbeat message on the queue

Doh!  I missed a detail.  Updated.


config: per-repo configuration support

Resolves: https://github.com/pkgcore/pkgdev/issues/89

@gyakovlev Could I request you to verify this patch if it works for you?

seems to be working.
funny, I'm on another system and [DEFAULT] no longer works here at all (neither does [gentoo] without patch), but with the patch [gentoo] works =)
this system is a bit special because it explicitly defines some XDG_ variables (i was trying to cleanup some dotfile cruft from ~), so maybe it's related?

env | grep XDG
XDG_CONFIG_DIRS=/etc/xdg
XDG_MENU_PREFIX=gnome-
XDG_DATA_HOME=/home/ya/.local/share
XDG_CONFIG_HOME=/home/ya/.config
XDG_SESSION_DESKTOP=gnome
XDG_SESSION_TYPE=wayland
XDG_CURRENT_DESKTOP=GNOME
XDG_CACHE_HOME=/home/ya/.cache
XDG_SESSION_CLASS=user
XDG_STATE_HOME=/home/ya/.local/state
XDG_RUNTIME_DIR=/run/user/1111
XDG_DATA_DIRS=/usr/local/share:/usr/share:/usr/share/gdm

cat ~/.config/environment.d/*
XDG_CONFIG_HOME="${XDG_CONFIG_HOME:-${HOME}/.config}"
XDG_CACHE_HOME="${XDG_CACHE_HOME:-${HOME}/.cache}"
XDG_DATA_HOME="${XDG_DATA_HOME:-${HOME}/.local/share}"
XDG_STATE_HOME="${XDG_STATE_HOME:-${HOME}/.local/state}"
XDG_RUNTIME_DIR="${XDG_RUNTIME_DIR:-/run/user/${UID}}"
#LESSHISTFILE="${XDG_DATA_HOME}/lesshst"

BOGOFILTER_DIR="${XDG_DATA_HOME}/bogofilter"
CARGO_HOME="${XDG_DATA_HOME}/cargo"
INPUTRC="${XDG_CONFIG_HOME}/inputrc"
NMBGIT="${XDG_CONFIG_HOME}/notmuch/nmbug"
NOTMUCH_CONFIG="${XDG_CONFIG_HOME}/mutt/notmuch-config"
PASSWORD_STORE_DIR="${XDG_DATA_HOME}/pass"
RUSTUP_HOME="${XDG_DATA_HOME}/rustup"
VIMINIT="set nocp | source ${XDG_CONFIG_HOME}/vim/vimrc"
WEECHAT_HOME="${XDG_CONFIG_HOME}/weechat"
WGETRC="${XDG_CONFIG_HOME}/wgetrc"
XAUTHORITY="${XDG_RUNTIME_DIR}/Xauthority"

here's testcase with [DEFAULT] only
ya@hydra ~/src/gentoo/gentoo/dev-util/pkgdev $ cat ~/.config/pkgdev/pkgdev.conf
[DEFAULT]
commit.scan = true
commit.ask = true
commit.signoff = true
push.ask = true
ya@hydra ~/src/gentoo/gentoo/dev-util/pkgdev $ git rm pk
pkgdev-0.2.1-r1.ebuild  pkgdev-0.2.1-r2.ebuild  pkgdev-0.2.1-r3.ebuild  pkgdev-9999.ebuild
ya@hydra ~/src/gentoo/gentoo/dev-util/pkgdev $ git rm pkgdev-9999.ebuild
rm 'dev-util/pkgdev/pkgdev-9999.ebuild'
ya@hydra ~/src/gentoo/gentoo/dev-util/pkgdev $ pkgdev commit
[master 222886eba39a] dev-util/pkgdev: drop 9999
 1 file changed, 84 deletions(-)
 delete mode 100644 dev-util/pkgdev/pkgdev-9999.ebuild
commit 222886eba39a68cf5a4da4712e8ffb13eaa97a65
Author: Georgy Yakovlev<EMAIL_ADDRESS>Date:   Mon Sep 19 23:17:52 2022 -0700

    dev-util/pkgdev: drop 9999

ya@hydra ~/src/gentoo/gentoo/dev-util/pkgdev $ git show HEAD | less
diff --git a/dev-util/pkgdev/pkgdev-9999.ebuild b/dev-util/pkgdev/pkgdev-9999.ebuild
deleted file mode 100644
index 5172a308d58..00000000000
--- a/dev-util/pkgdev/pkgdev-9999.ebuild
+++ /dev/null
@@ -1,84 +0,0 @@
-# Copyright 1999-2022 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=8
...snip...

seems to be working.
funny, I'm on another system and [DEFAULT] no longer works here at all (neither does [gentoo] without patch), but with the patch [gentoo] works =) this system is a bit special because it explicitly defines some XDG_ variables (i was trying to cleanup some dotfile cruft from ~), so maybe it's related?

Does this commit helps?
https://github.com/pkgcore/pkgdev/commit/9f60576753da4cbe5cd0afe660d49a22e34e3cf1
(I need to create a realese very soon - important fixes are in queue)

testcase with [gentoo]
ya@hydra ~/src/gentoo/gentoo/dev-util/pkgdev $ cat ~/.config/pkgdev/pkgdev.conf
[gentoo]
commit.scan = true
commit.ask = true
commit.signoff = true
push.ask = true
ya@hydra ~/src/gentoo/gentoo/dev-util/pkgdev $ git rm pk
pkgdev-0.2.1-r1.ebuild  pkgdev-0.2.1-r2.ebuild  pkgdev-0.2.1-r3.ebuild  pkgdev-9999.ebuild
ya@hydra ~/src/gentoo/gentoo/dev-util/pkgdev $ git rm pkgdev-9999.ebuild
rm 'dev-util/pkgdev/pkgdev-9999.ebuild'
ya@hydra ~/src/gentoo/gentoo/dev-util/pkgdev $ pkgdev commit
[master 330db433dc6a] dev-util/pkgdev: drop 9999
 1 file changed, 84 deletions(-)
 delete mode 100644 dev-util/pkgdev/pkgdev-9999.ebuild

ya@hydra ~/src/gentoo/gentoo/dev-util/pkgdev $ git show HEAD

commit 330db433dc6a02dba83195dd1fc9847fdf54a08b
Author: Georgy Yakovlev<EMAIL_ADDRESS>Date:   Mon Sep 19 23:21:08 2022 -0700

    dev-util/pkgdev: drop 9999

diff --git a/dev-util/pkgdev/pkgdev-9999.ebuild b/dev-util/pkgdev/pkgdev-9999.ebuild
deleted file mode 100644
index 5172a308d58..00000000000
--- a/dev-util/pkgdev/pkgdev-9999.ebuild
+++ /dev/null
@@ -1,84 +0,0 @@
....

now it does not work....
idk what's going on, but it also never asks me too.

ok with this patch + https://github.com/pkgcore/pkgdev/commit/9f60576753da4cbe5cd0afe660d49a22e34e3cf1
everything now works
it actually started running pkgcheck, and sign-offs with both DEFAULT and [gentoo]

also tested with ask options in [DEFAULT] and signoff option only in [gentoo]
works as intended.


Clear Logging Error for broken ubiquibot-config.yml

The bot does not show any visible errors for when it has an issue loading in a new config. The bot was down for about 14 hours on this repository until we identified the fix. Apparently it was the broken config.
There were no logs to verify this, we just changed it because the bot was working on other repositories.

https://github.com/ubiquity/ubiquibot/pull/677/files

Context: https://t.me/c/1588400061/3250/4436
The business problem to solve is that we need to know as soon as possible if the config is valid.

[ ] Clearly log error while the bot tries to load the config in the Supabase.
[ ] We should consider some type of special event that when the config is updated, the bot immediately validates it and lets the user know via a pull request comment, or a comment directly on the commit.

We should consider some type of special event that when the config is updated, the bot immediately validates it and lets the user know via a pull request comment, or a comment directly on the commit.

@whilefoo you expressed interest in this. Can you provide input on the second subtask?

We should consider some type of special event that when the config is updated, the bot immediately validates it and lets the user know via a pull request comment, or a comment directly on the commit.

The second subtask is doable. We already handle push events on the bot, so we just need to retrieve the content of the config at specific commit hash, parse it and validate it and if it fails it will post a commit comment. This will also work for partners when they change the config.

Permit generation skipped because bounty amount after penalty is 0
If you've enjoyed your experience in the DevPool, we'd appreciate your support. Follow Ubiquity on GitHub and star this repo. Your endorsement means the world to us and helps us grow!
We are excited to announce that the DevPool and UbiquiBot are now available to partners! Our ideal collaborators are globally distributed crypto-native organizations, who actively work on open source on GitHub, and excel in research & development. If you can introduce us to the repository maintainers in these types of companies, we have a special bonus in store for you!

I don't think I have any penalties?

Permit generation skipped because bounty amount after penalty is 0
If you've enjoyed your experience in the DevPool, we'd appreciate your support. Follow Ubiquity on GitHub and star this repo. Your endorsement means the world to us and helps us grow!
We are excited to announce that the DevPool and UbiquiBot are now available to partners! Our ideal collaborators are globally distributed crypto-native organizations, who actively work on open source on GitHub, and excel in research & development. If you can introduce us to the repository maintainers in these types of companies, we have a special bonus in store for you!

I don't think I have any penalties?

I guess it would make sense to link back to the re-opened issue that you were penalized for. I'm glad that I saw this because this is the first time I've seen a penalty work. I'm checking the database to get more info here.

/query @whilefoo

Permit generation skipped because bounty amount after penalty is 0
If you've enjoyed your experience in the DevPool, we'd appreciate your support. Follow Ubiquity on GitHub and star this repo. Your endorsement means the world to us and helps us grow!
We are excited to announce that the DevPool and UbiquiBot are now available to partners! Our ideal collaborators are globally distributed crypto-native organizations, who actively work on open source on GitHub, and excel in research & development. If you can introduce us to the repository maintainers in these types of companies, we have a special bonus in store for you!

https://gnosisscan.io/tx/0x87d8703ab5d690bb549f6813f84bbea3b5966d27b8b7150ebcc269673735b979

I guess it would make sense to link back to the re-opened issue that you were penalized for. I'm glad that I saw this because this is the first time I've seen a penalty work. I'm checking the database to get more info here.

I'd guess that is hard to do in current state because penalties seem to add up from different issues and get deducted when new issues are closed so it acts like a debt balance and we can't accurately link back a PR unless we redesign the system

unless we redesign the system

We'll probably need to change the schema to support a new table that has all the debt information. Basically a ledger of credits and debits which links the issue.


update Description to provide path to config - chain archway

Overview
Update description to provide path to config as mentioned in other chain commands
Steps to Reproduce
Steps to reproduce the behavior:

dive chain archway -h
Observe description for config flag

Expected Behavior
To update description to provide path to config file

#146  fixes this issues

closing this issue as fixed


Support providing Salesforce passwords and security tokens as SecureStrings or as secrets in Azure Key Vault

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[ ] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ ] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] The spec follows the guidelines described in the Swagger checklist document.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

This PR has been internally reviewed and the corresponding release item is approved.

No modification for AutorestCI/azure-sdk-for-node

 https://github.com/Azure/azure-sdk-for-python/pull/1572

No modification for AutorestCI/azure-sdk-for-ruby


Update Coos County, Oregon

It looks like these aren't pulling in attributes for addresses. Can you see if they updated attribute names on the source?

Looks like they're still using the same fields. Around a third of the parcels don't have an address:

Ah I didn't see that they were sourced from parcels 👍🏻


Reordering column - updated scores not reflecting

When a column is drag-n-dropped, only the first row reflects the new ordering. Rows 2+ remain fixed, showing the scores for the existing item placement.
Ordering does not appear to save either.

Ah yep.. the first issue is a bug in the drag and drop javascript.  The plugin we use for dragging columns doesn't support having hidden columns so I had to get creative and a little bit hacky.  I'll look into implementing our own drag and drop... that'll be fun :joy_cat:
Regarding the save... will investigate further as it seems to be throwing an error:  https://gist.github.com/payten/df19bc1b904a7e3dc152

@steveswinsburg on Sandbox1 we're seeing the null pointer exception (in the gist above) deep in the gradebook service org.sakaiproject.component.gradebook.GradebookServiceHibernateImpl.updateAssignmentOrder.  I have a feeling it's because we've frozen the Sakai build version at commit 3b5cb7d63c8024e544a450eb09752e27a5573201 from Sat Apr 18 07:48:23 2015 +1000.  Do we need to upgrade Sakai on Sandbox1?  And I'm guessing we'll need to push on with Tomcat8 and Java8 too?

Hm I'm wrong... the latest Sakai build is throwing the same NPE.  I'll dig into it...

This method is one I wrote, it was working previously, I wondering if
something recent has changed it/caused a regression. I haven't updated
trunk yet as I haven't had a chance to upgrade Java/Tomcat. I can certainly
fix this one if you haven't found the issue already.
On Fri, May 8, 2015 at 4:46 PM, Payten Giles<EMAIL_ADDRESS>wrote:

Hm I'm wrong... the latest Sakai build is throwing the same NPE. I'll dig
into it...
—
Reply to this email directly or view it on GitHub
https://github.com/steveswinsburg/gradebookNG/issues/70#issuecomment-100123211
.

Ok I've found the problem and will be pushing a fix up shortly.

Hey @Payten, I have found a bug that appears to be in the JS relating to this. It seems to be always sending the same assignment Id for updating the order. I had a look at the network requests in the browser and this appears to be the case. I've fixed the backend bug, it should be merged shortly.

Just investigating the "same assignment ID" issue and I'm not seeing it happen in the latest version.  I'm wondering if my refactor of the drag and drop code fixed it? I'll take it! :trophy:


Add audio looping example (and a shorter track to loop)

Objective
The first step in learning Bevy for me was getting some audio to loop as an overworld theme. The existing audio example set me on the right path, but in order to loop / repeat my audio for an endless effect, I needed to figure out a number of other things about Bevy. I'm glad for figuring them out, but would also have been appreciative of an example of how to loop audio out the gate.
When I looked for other examples of how to loop audio with Bevy, all I found were people using the third party lib bevy_kira_audio and not native Bevy so I figured I'd take a shot at it :)
I fully expect there are plenty of ways to go about repeating audio, and I know there are blindspots in what I learned vs what the appropriate/efficient/idiomatic way to do things are. I tried to guide my solution according to other example's  approaches, but if there's a better way to go about repeating/looping audio I'd be very happy to learn of it!
Solution
An example was added to the suite that uses a Timer and the FromWorld trait to repeat a single track of audio to produce an endless track effect.
The audio committed is a 13-second loop example of what I hope feels a bit like a shape of "overworld theme". It was created by me, on an OP-1 and converted from .aif to .mp3 with ffmpeg. ffmpeg was also used to edit the volume level.
Thank you for taking a look ❤

bors try

@alice-i-cecile thanks for this awesome review feedback 🤩 🤩  🙏 🙏
I'd be glad to tackle the initial_elapsed parameter too! but I expect addressing it will take me into the weekend (I'm new to the codebase 😄) so no problem if you want to tackle it a bit sooner.
I also wonder if I might be able to take a look at what the recommended cargo run -p ci is doing and see if I can get it to catch the error on README omission locally along with the other helpful stuff it caught before pushing?

I'd be glad to tackle the initial_elapsed parameter too! but I expect addressing it will take me into the weekend (I'm new to the codebase 😄) so no problem if you want to tackle it a bit sooner.

I'll let you take it :) There's no rush, and I have plenty of other tasks on my plate.

I also wonder if I might be able to take a look at what the recommended cargo run -p ci is doing and see if I can get it to catch the error on README omission locally along with the other helpful stuff it caught before pushing?

@mockersf do you know where this might be found? There's some excellent CI advice in this draft PR (thanks to everyone who helped with that...), but it doesn't cover the Github Actions CI.

cargo run -p ci just runs the ci crate declared in the workspace, which can be found here. It's just rustfmt and clippy. You can run cargo run -p ci locally.
The example checking is done in another action which can be found Weibye/action-internal-link-consistency. This will be harder to run on your system...

I've ended up getting wrapped up in the audio duration bit of this PR review rather than inital_elapsed stuff for Timer and tbh am feeling a bit timid about changing the signature of Timer::new and Timer::from_seconds. Once I started looking closer at the code though, I realized I could do something like this to get us down to a single system.
let track_duration = Duration::from_secs(13);
let mut timer_with_initial_elapsed = Timer::new(track_duration, true);
timer_with_initial_elapsed.set_elapsed(track_duration);

Think that'd be an okay approach for this example?

That sounds like a perfectly fine approach; let's go with that for now :)

Thank you for working on this!
I am wondering though whether this is an approach we want to put in an example. Audio is very sensitive to timing and sending the handle from the systems thread to the audio thread based on a timer feels a bit wrong. Rodio has very simple functionality to loop a source, which might just be worth a small extension of the audio crate.

Hey @NiklasEi 😄 Hah I think it's your bevy_kira_audio crate I've been trying to live without 😬 😆
I think I'm on same page as you about this example now, after looking into exposing Rodio's the total_duration in AudioSource I did spot a repeat_infinite that seemed like, on the example side would be really clean. As far as the implementation side goes, I'm heartened to hear you say it could just be a small extension to the audio crate, I wasn't sure from looking if a track set to repeat_infinite had any especially tricky implications for the existing Audio queue implementation. But I'd be glad to take a swing at extending the audio crate withrepeat_infinite if you and @alice-i-cecile  think it'd be appropriate. I'd be glad for the functionality on the other side of the changes too.
Also @alice-i-cecile it has been incredibly educational! I couldn't have asked for a better path to figuring out how to use some of the Bevy basics 😄 😄 Also also I can't thank you enough for being so responsive to my questions 🙏 🙏

repeat_infinite sounds like a great extension here :) @NiklasEi's points about the precise nature of the timing involved are very valid.

Hey all, thanks a ton for the conversation here! I've created a PR with an approach to extending the bevy_audio crate that also includes a revised version of this looping example to illustrate how the changes work from my perpective so I'm going to close this one. Since it's basically duplicated while this is around, I'll close this one to favor conversation over there #2586.
Again, thank you!


Use 'Bearer' in Authorization HTTP Header

Changes 'OAuth2' to 'Bearer'.
Fixes https://github.com/RestKit/RestKit/issues/643

@blakewatters Your suggestion is of great help to me!!


Minor Updates - Naming Conventions and CancellationToken for Async Calls

Description
Minor updates to fix naming conventions. Also updated async calls by passing in cancellation token.
Testing
All the existing tests are passing.

It looks like all changes from 64274cb are included in this PR 👍

It looks like all changes from 64274cb are included in this PR 👍

Sweet! Thanks for verifying.


[DOCFIX] Doc fix for Chinese version for multiple file

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/14723/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/14724/
Test PASSed.

Hi @Popeye13 thanks for the PR!
Mostly looks good, can you please resolve the conflicts?

Hi @Popeye13 , have you got a chance to resolve the merge conflicts in this PR? thanks

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15058/
Test PASSed.

Merged build finished. Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15249/Failed Tests: 1org.alluxio:alluxio-tests: 1alluxio.master.file.FileSystemMasterIntegrationTest.concurrentRename
Test FAILed.

Jenkins, test this please

LGTM

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15253/
Test PASSed.


Prepare scenarios for and conduct regression tests

User story

As a User
I want / need to use an app that runs without bugs
So that I enjoy using the app and are not annoyed by occurring bugs

Further description

We want to make 100 % sure, that the final app runs without any bugs. Keep Marcus´ words in mind: "Stop Starting - Start Finishing". That´s why we want to take care of this concern early

Acceptance criteria

[ ] Write test scenarios for the usage of the entire app
[ ] Each test scenario should have a title, a short description what to do, an expected behavior and an actual behavior
[ ] Create an excel file with all the test scenarios and various columns for "actual behavior"
[ ] For each column "actual behavior", prepare a cell where the test taker can enter his name, date and time of test execution, description of used hard- and software
[ ] Upload Excel-File to GitHub
[ ] If "expected behavior" is unclear, contact POs
[ ] Make sure to run one test run

Definition of done (DoD)

It builds without errors
code has been reviewed
Build has been made and deployed on a testing environment
Code coverage >75%
All acceptance criteria were met
Documentation updated whenever needed within planning documents (Tabs: Bill of materials, Documentations)
Branch/feature was merged into dev and then main

DoD general criteria

Feature has been fully implemented
Feature has been merged into the mainline
All acceptance criteria were met
Product owner approved features
All tests are passing
Developers agreed to release

@codingwithelijah @Meisterlu Please don't ask for an excel file, because it is a binary file format.
Alternatives would be a markdown file (containing a table) or, if you really want nothing except a table, a csv file.


Reorganization of Sensory-property tree

This is a separation of discussion of issue #269 specifically about the Sensory-property tree.  We (@smakeig @dungscout96 @VisLab) had a lengthy discussion 7/27/2021 about the difference between Visual-property and Optical-property (as well as Auditory-property versus Acoustic-property).
The key idea is that in psychology experiments Loudness doesn't mean the max amplitude of the sound wave, but rather how the subject perceives the sound.  Thus, we want Auditory-property rather than Acoustic-property.
A second point of discussion was the confusion about using the word Visual rather than Visual-modality.  We have gone back to Visual-modality.
The agreed reorganization is:
Sensory-property

Sensory-modularity

Auditory-modality
Visual-modality

Auditory-property
Visual-property

Color
Luminance
Opacity
View-type

Note  This doesn't do well with alphabetization.

Discussion of 7/29 agreed that the reorganization of 7/27 (above) does not work.  Besides the ugly alphabetization issue there is the problem of separating presentation modality from property. Here is a new proposal which I think solves the problem:
Sensory-property

Sensory-attribute

Auditory-attribute

Pitch

. . .
Visual-attribute

Color
Luminance
Opacity

Sensory-presentation

Auditory-presentation
. . .
Visual-presentation

View-type

This was accepted as a revision 8/2/2021 meeting of @smakeig @dungscout96 @VisLab


Signals v2

@alexsdutton I've decided to drop signature check at all, at least for now.

Also I have strong feeling we need two special signals for every signal call: first before the call and second after signal processing finished.
Those debug signals are extremely useful for tools like aiohttp_toolbar for displaying:

What signals was affected by HTTP request.
What time these signals consume.

So web.Application from now has .debug property for raising debug-only signals.
And every regular signal should be constructed with mandatory app parameter (web.Application instance).
The current PR is final from my perspective, I'll push it into master if no objections will appear until Friday.
After that I'd like to publish next 0.18 release


How HTML works with web browsers

I would like to work on this issue under GSSoC'24. Please assign me this task.


[Search] Hide tab bar

It’s not an immediate issue, as pretty much everybody will have the keyboard shown on top of the tab bar, but for the few that use an external keyboard, this could be a slight UI issue.

@sarahscott this is also still an issue for our current version of the app, maybe something you can look into post works for you work?

@katarinabatina it does still exist in the current app version, but only for users who use external keyboards. I can take a look after WFU stuff.


models no init is no problem?

models no init is no problem? in the pycharm import matchzoo call  No module named models,please tell me how to solve?

Could you explain clearly what your problem is ? You can paste the error message you got.

@cap3396g It has been solved in #115 .
I'll close this issue for now, best!


Add match stmt support to python.lark

Based on the PR of the same name by MegaIng (PR #1016), but now with tests!

Thanks for contributing!

I assure you, my motives were entirely selfish. Thanks for your help!

Benevolent selfishness is the driver of civilization ;)


Prepared ops_agent_policy for inclusion in C.G.C. documentation

Description
Fixes #254515347
Note: If you are not associated with Google, open an issue for discussion before submitting a pull request.
Checklist
Readiness

[x] Yes, merge this PR after it is approved
[ ] No, don't merge this PR after it is approved

Style

[x] My sample follows the rules described for Terraform in the Effective Samples style guide

Testing

[x] I have performed tests described in the Contributing guide:

[x] Tests pass: terraform apply (see Test Environment Setup
[x] Lint pass: terraform fmt check. See Linting and Formatting

Intended location

[x] Yes, this sample will be (or already is) included on cloud.google.com
Location(s): https://cloud.google.com/logging/docs/agent/ops-agent/managing-agent-policies

[ ] No, this sample won't be included on cloud.google.com
Reason:

API enablement

[ ] If the sample needs an API enabled to pass testing, I have added the service to the Test setup file

Review

[ ] If this sample adds a new directory, I have added codeowners to the CODEOWNERS file

Needs project_id field and tf init to pass tf validate

/gcbrun

Terraform does not currently have a resource type for ops agent policies. Will close this until we have something. Thanks!


The package stops at para-slot-registration

Overview
The package doesn't work on kubernetes due to the start and stop service used for one-off task used in https://github.com/HugoByte/polkadot-kurtosis-package/blob/main/package_io/build-spec.star#L30
Steps to Reproduce
Steps to reproduce the behavior:

Setup kurtosis in kubernetes
Run the package using

kurtosis run github.com/hugobyte/polkadot-kurtosis-package '{ "chain_type": "localnet", "relaychain": { "name": "rococo-local", "nodes": [ { "name": "alice", "node_type": "validator", "prometheus": false }, { "name": "bob", "node_type": "full", "prometheus": true } ] }, "parachains": [ { "name":"frequency", "nodes": [ { "name": "alice", "node_type": "validator", "prometheus": false } ] } ], "explorer": true }'

The execution stops with error

DEBU[2024-01-26T04:39:57Z][api_container_service.go:runStarlark] Received response line from Starlark runner: 'error:{execution_error:{error_message:"An error occurred executing instruction (number 8) at github.com/hugobyte/polkadot-kurtosis-package/package_io/build-spec.star[19:31]:\nadd_service(name=\"para-slot-registration\", config=ServiceConfig(image=\"hugobyte/parachain-node-modules\", files={\"/app\": \"configs\", \"/build\": \"javascript\"}, entrypoint=[\"/bin/sh\"]))\n --- at /home/circleci/project/core/server/api_container/server/startosis_engine/startosis_executor.go:157 (sendErrorAndFail) ---\nCaused by: Unexpected error occurred starting service 'para-slot-registration'\n --- at /home/circleci/project/core/server/api_container/server/startosis_engine/kurtosis_instruction/add_service/add_service.go:163 (AddServiceCapabilities.Execute) ---\nCaused by: An error occurred creating pod 'para-slot-registration' using image 'hugobyte/parachain-node-modules'\n --- at /home/circleci/project/container-engine-lib/lib/backend_impls/kubernetes/kubernetes_kurtosis_backend/user_services_functions/start_user_services.go:421 (createStartServiceOperation.func1) ---\nCaused by: An error occurred waiting for pod 'para-slot-registration' to become available\n --- at /home/circleci/project/container-engine-lib/lib/backend_impls/kubernetes/kubernetes_manager/kubernetes_manager.go:1159 (KubernetesManager.CreatePod) ---\nCaused by: Expected state of pod 'para-slot-registration' to arrive at 'Running' but the pod instead landed in 'Succeeded' with the following state:\n>>>>>>>>>>>>>>>>>>>>>>>>>> Pod para-slot-registration <<<<<<<<<<<<<<<<<<<<<<<<<<\nContainer Statuses: - user-service-container (docker.io/hugobyte/parachain-node-modules:latest): TERMINATED with exit code 0 - \n\n-------------------- Container user-service-container Logs --------------------\n\n------------------ End Container user-service-container Logs ---------------------\n>>>>>>>>>>>>>>>>>>>>>>>> End Pod para-slot-registration <<<<<<<<<<<<<<<<<<<<<<<<<<<\n --- at /home/circleci/project/container-engine-lib/lib/backend_impls/kubernetes/kubernetes_manager/kubernetes_manager.go:1871 (KubernetesManager.waitForPodAvailability) ---"}}'

Expected Behavior
The execution should complete without the error.
Additional Context
The issue can be due to use of plan.add_service for one-off task instead of plan.run_sh as discussed in https://github.com/kurtosis-tech/kurtosis/issues/2089

Hi @MuhammedIrfan, the issue is resolve in PR #198


--resources and --resource-group  flags not recognised for azure import

Hi,
I am trying to import azure resources and want to filter it by resource group. I tried below command:
./terraformer import azure --resources=disk --resource-group=rg1_
but it gives error:
azurerm error importing disk --resource-group=rg1,
err: azurerm: disk --resource-group=rg1 not supported service
Looks like it is considering everything from 'disk' till end of the command as a single resource and hence failing with error 'not supported service'
Terraformer version : v0.8.17
I have also tried using shorthand -R and -r flags, but in that case it does not recognise the -R flag and returns all disks, from all resource groups without filtering it for the specified resource group.
Can you please provide some inputs?

Closed the query as this issue is not with the Terraformer tool


Add restriction-notice to the EventType Enumerated Type

Add New Event Type:  restriction-notice
Adding a restriction-notice to the EventType Enumerated Type enables State DOTs to warn drivers of hazardous restrictions such as low-clearances beneath bridges.
Benefits

Helps mitigate loss of life, personal injury, infrastructure damage, lost time and money, unnecessary emissions, and all the other ill effects of bridge and tunnel strikes.
Fosters in-vehicle warnings about hazards to navigation.
Establishes the WZDx specification can be leveraged to make transportation safer by extending it beyond its original purpose.
Extending the specification may draw more agencies into using the Work Zone components of the specification.

Costs

Diversifying the specification is off scope.

Support

The New York State DOT has committed to developing a prototype feed.
Other State DOTs have expressed interests.
Google and Here have committed to consuming and testing NYSDOT's feed
The National States Geographic Information Council endorses the project.

Example

An example of the restriction-notice EventType.

I like this addition. It is simple, backwards compatible, flexible, and allows using the WZDx model to represent any kind of restriction on the roadway.
Note a restriction-notice road event can represent a permanent restriction unrelated to road work or a work zone, such as reduced height due to an overhead structure, reduced width on a bridge, etc.

After the creation of #191 and spec extension subgroup meeting, it was decided that the restriction notice is better addressed in a new feed rather than the WZDxFeed, which should stay focused on work zones and similar or related road events (e.g. detour).

This should be contingent on issue #203

Completed by adding the RoadRestrictionFeed and RestrictionRoadEvent in #205 (WZDx v4.0).


[ISSUE] Link not working!

https://pocketkit.herokuapp.com gives 404 Not Found (nginx error)

Its resolved!


Open Source License Verification

Include Open Source License Verification

Is documented: stages/01-build/README.md


e6f273c

So you added an empty file named www.paypal.com. Care to explain the reasoning behind this?


Only LAN.

Hello!
I have a question that I couldn't find on internet.:
Is there a way to share, only on LAN?

Would you mind elaborating on your use case a little?
By default it'll share both on your local network and over the internet, but if you don't share the read key for your dat archive over the internet, there's no way that anyone can get access to it.

I'm going to do a proof of concept, using Vagrant and a notebook, I want to make 2 DAT directories, one that is available only inside the Vagrant machine network, as if it were a corporate network and another directory that is available on the internet.
But your comment has solved what I need :)

That sounds pretty interesting! :D
Is there anything else you'd like to discuss in this issue, or should it be closed?

We can close :)
Thank You!


Allow struct serialization from array input

Change Description
eosio::chain::abi_serializer in libchain allows serialization of struct from array, but eosjs only serializes object to struct.
When sending a transaction with transaction_extensions, the abi of transaction in eosjs defines transaction_extensions as extension[], and extension is a struct with two fields, type (uint16) and data (bytes). However, during calling transact(), it calls /v1/chain/get_required_keys RPC, but in libchain, transaction_extensions is defined by std::vector<std::pair<uint16_t,vector<char>>>, so get_required_keys will be aborted, because libchain will fail to convert the parameters in json to eosio::chain::transaction.
At this time, there is no way to send a transaction with transaction extensions by transact() of eosjs-api. This PR will provide a way to serialize structs from array in the same manner as eosio::chain::abi_serializer and user experience of cleos. Moreover, user can send a transaction with transaction_extensions by setting them in array like:
const tx = {
  actions: [{
  ...
  }],
  transaction_extensions: [[1, [1]], [2, [1, 2, 3, 4]]]
};

API Changes

[x] API Changes

User will be able to pass action parameters by array instead of object.
Documentation Additions

[x] Documentation Additions

User can pass an array to transact() of eosjs-api.

transaction_extensions must always be empty

@tbfleming Interesting. Can you explain what the intended usage of transaction_extensions is?
I can understand there can be a planned way to use transaction_extensions in EOS mainnet in the future, but what about EOSIO-variants, called sister chains? They might utilize transaction_extensions fields not to modify libchain too much, but implement their own special features by parsing transaction_extensions in wasm-side.
Even if the emptiness of transaction_extensions is mandatory, this PR still has meaning, because this adopts the exisitng way  to serialize struct like eosio::chain::abi_serializer does.

The intended use is to allow future hard forks to upgrade the transaction format. For now, the JSON representation requires either the field be absent or it be an empty array. The binary form requires a single 0 byte (this is how empty arrays are encoded).
If forks of eosio modify the transaction format, then we can't guarantee any compatibility with versions we maintain. Chances are high they'd conflict.
We were once considering supporting array syntax for objects in eosjs. I thought we had implemented that, but I could be remembering wrong.

@tbfleming Thank you. :)


fix(test): invalid assignment type in test mode

:tada: This PR is included in version 2.130.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Support multiple Chargebee Sites

It's possible to have multiple chargebee sites in a single application.
I suggest implementing a per-site configuration struct, similar to how ecto databases can be handled. I'm highly ambivalent about the ergonomics here.
defmodule MyChargebeeSite do
   use Chargebeex.Site
end

config :chargebeex, MyChargebeeSite,
	namespace: "my_namespace",
    api_key: "myapi_key"

# option 1
customers =  Chargebeex.Customer.retrieve(MyChargebeeSite, "foobar")

# option 2
customers = MyChargebeeSite.Customer.retrieve("foobar")

#option 3
customers = MyChargebeeSite.exec(Chargebeex.Customer.retrieve("foobar")

Option 2 is probably the least disruptive to existing usage of Chargebeex

Hi @gerbal ! Thanks for your issue, I also think the option 2 is the best solution. I don't have many time at the moment, feel free to start a PR ;)


Translate test/data YAML files into in-code specs

With the bundle end to end tests, a prototype style build and buildrun spec definition was introduced: https://github.com/shipwright-io/build/blob/main/test/e2e/e2e_bundle_test.go#L60-L69
Migrate the existing YAML files in test/data into the prototype definitions so that the actual test code and the spec are done in the same place. This should also reduce the overall amount of YAML files in the repository.

Accepting this into the general backlog. Marking this as a good first issue for new contributors.

/assign @aryaman02

/assign @aryaman02


Create a new branch for fast forward

https://github.com/istio/istio-testing/issues/113

Jenkins job istio-testing/pr-master passed

This is a test.

Jenkins job istio-testing/pr-master passed

This is a test.

Jenkins job istio-testing/pr-master passed

This is a test.

Jenkins job istio-testing/pr-master passed

This is a test.

Jenkins job istio-testing/pr-master passed


docs(material/stepper): misleading default icon documentation

Fixes the default stepper icon documentation.
Fixes #22498

@googlebot I signed it!

Closing since there hasn't been any activity in a while.


Ship Disappearing post Edit

Multiple times now, Anytime I edit a ship and finish building, my ship will not load on the landing pad at all. Additionally, this would disable Fast Travel/flying to other planets. "you cannot fast travel at this time." Swapping parts, swapping ships, moving instances, nothing rectifies the issue. Only option is revert to previous save.

Details
Occurs/Can occur on any platform, notably for me occurred on Hopetech, personal and New Atlantis landing pads
Game Version
<IP_ADDRESS>
New Game
Yes
Reproduction Steps
Edit the ship at a station numerous times as you play, it will eventually happen.

https://www.reddit.com/r/Starfield/comments/16c7asb/help_ship_disappeared/ video of what i mean

Can confirm this happened to me as well. Current theory is this only happens when you modify a "captured" enemy ship. It's not clear but it seems like even moderate changes like upgraded weapons, shields etc... can trigger this bug. In my case I captured an enemy ship, completely tore it down refunding all existing parts for a small starting budget.
After completing the ship and setting it as my home ship, I was unable to see it on the launch pad. I tried swapping home ship with other ships that were visible in several different places: staryard, outpost, New Atlantis. Nothing worked. Also tried various actions that should make the game reset and render the entire ship such as changing parts, moving parts etc... Nothing has worked. Additional discussion on this issue here:
https://steamcommunity.com/app/1716740/discussions/0/3824174193423630546/?ctp=2
Absolutely frustrating bug. I spent ~800k or more on the ship I cannot now use. Primary suggestion to avoid this bug seems to be to only modify and build new custom ships on a ship you have purchased.

I'll buy you drinks all night for this alone !!!!

I had the same experience as THeFireBirdMan, I was forced to roll back to a much earlier save.   I have another captured ship in respect of which I fixed the invisible problem by simple editing. But ever since then, when I make that not my home ship I get glitches like the inventory has disappeared ,  I dont have the "R Cockpit" option at the entry hatch,  and when I return to the "Modify My Ships" screen the modded stolen ship is still shown as my home ship.  So captured ships have lots of issues.

This would be an engine issue. Unfortunately, out of the scope of the SFCP to fix.


Feature: Move branch_key and branch_app_domain to the JS side

@jdee I've been making my rounds to the various React Native plugins with this request. It'd be great to move the branch_key and branch_app_domain that is put in the Info.plist for iOS and that is put AndroidManifest.xml for Android to the JS side.
Moving the keys to the JS side has several advantages:

We only have to put it in one place. This will reduce bugs (and issues for you guys!) and steps during the installation.

By using 12 Factor best practices, having it in the JS is very easy because we can generate one env.js file and have ALL of our JS files import that file and grab keys like we needed.

If changes to the underlying iOS or Android code is ever made, this protects that as it's agnostic to what happens under the hood.

For example, it could look like this:
import {
  subscribe
  setKey,
  setAppDomain
} from 'react-native-branch';

import {
  BRANCH_KEY,
  BRANCH_APP_DOMAIN
} from '../../../env.js'; // this file is not in the repo!

export function init() {
    setKey(BRANCH_KEY);
    setAppDomain(BRANCH_APP_DOMAIN);

    subscribe(bundle => {
        console.log('bundle', bundle);

        if (bundle && bundle.params) {
            runAction(bundle.params);
        }
    });
}

@dwilt Thanks. This is a good idea. Actually, one of my to-dos is to produce a script to do the integration one way or another, and I was thinking of something along these lines.

Cool. Also, is subscribe able to be destrutured as I've shown in the example above? In your main example it's not but others (AddToWishlistEvent,PurchasedEvent,PurchaseInitiatedEvent,RegisterViewEvent,ShareCompletedEvent,ShareInitiatedEvent) are.

Also, any idea on a timeline when you think you'd be able to implement this? Right now we have a pretty hacky way to ensure that our key_test and key_live are in the appropriate builds.

@dwilt First, subscribe doesn't seem to be destructurable. I tried just now and got "undefined is not a function." I think the reason is that index.js exports a new Branch object, and when you import branch from 'react-native-branch', branch is just a reference to that object, and subscribe is a property on that exported object, not something that is exported itself. The constants you mention are just export consts so you can destructure them. It would be nice to make this work though. I don't think it's much trouble to change that though.
Regarding the Branch configuration:
The Branch keys can be set in code, and that will be in the react-native-branch module. This also applies to the branch_universal_link_domains key in the Info.plist on iOS. That's not much work.
But there are some realities that can't be coded around. For example, you always need intent-filters for Android and the Associated Domains entitlement/URI scheme for iOS. Some settings changes are always needed to let the OS know that this app supports a certain URI scheme or Universal Links/App Links from a certain domain.
I'd like to be able to customize react-native link and have it make these changes after it runs. For now, a script reading from a config file would be an improvement: one more command you run after react-native link and you're done. But at any rate, JS in the react-native-branch module will never be the whole solution.
But generally this is a one-time configuration setup. I'm not sure why you'd need to automate this when you do builds. I'm sure there's a good reason though. I don't suppose you're using Fastlane? It wouldn't be that hard to provide a Fastlane plugin to do your Branch setup. That might not be a bad idea anyway, if there's a significant need out there to automate this beyond initial setup.
Can you remind me what version of RN and react-native-branch you're using? I think you might still be using RN 0.39. I don't really want to introduce new features into the 0.9 branch. In fact, it's getting harder to support RN 0.39 for certain reasons (mainly setting up a test environment isn't straightforward). At worst, for the time being you could pull the script from the master branch to try it out.
If you can live with a Ruby script or a Fastlane plugin, I can get something done in the next week or two, say. If you need something more polished and integrated with RN/JS, it will require a little research and take a bit longer.

"react-native": "0.41.2",
"react-native-branch": "^2.0.0-beta.1"

Destructuring subscribe: - yep, that's the struggle when it's a method on a class and not just an export const. Probably would be better as an export const. You'd have you rip the methods off the class and then replaces all the this references with local variables/functions.

Branch config:

Some settings changes are always needed to let the OS know that this app supports a certain URI scheme or Universal Links/App Links from a certain domain.

Yep, totally understand. And it would be awesome, as you realize, to make that part of the react-native link script.
And we're using BuddyBuild - not Fastlane - same thing though. I wonder if you're trying to bite off more than you should chew? I think it should be just your plugin's job to expose the key/app_domain setters and leave the way we get those keys in the JS up to the developer.
For the record, I'm not really saying there is a problem with your install steps. I realize there are lots of things to do it in - adding the intent filters, URI Schemes, Associated Domains in Xcode, etc.. I personally think moving those keys to the JS is a higher priority and then optimizing the install process would be second. Developers can get the plugin installed because you have good documentation on how to do it. What we need is for a way to be able to configure the plugin from the JS side. Just my two cents 👍

There is actually a much bigger problem with setting the Branch key in JS: It has to be set before the native layer is initialized, and that happens before the JS is loaded. For the same reason, e.g., setDebug() does not work in JS.
That means this requires a pretty big architectural change to the module, and that means it's not going to happen right away. I'd like to change that for other reasons. Since this is important to you, I'll prioritize it and do some research into what is required and what the impact will be. Until now, it's just been something to look into. One definite consequence will be potential delays in getting back any initial link at launch, since the call to the Branch API will not occur until after the JS loads. Currently, these two things happen in parallel.
But maybe there's a simpler way for you to make your life easier without this better solution. I suspect what you're doing is just trying to use the correct Branch key for each build, maybe just use the test key for debug builds and the live key for release builds.
That's pretty simple:
iOS
Add both keys to your Info.plist as described here. (Make the value a dictionary and add both a "test" key and a "live" key.)
Then in AppDelegate.m, in application:didFinishLaunchingWithOptions:, before calling [RNBranch initSessionWithLaunchOptions:isReferrable:], just add:
#ifdef DEBUG
    [RNBranch useTestInstance];
#endif

Android
Add both keys to your AndroidManifest.xml as described here. (Add another meta-data for io.branch.sdk.BranchKey.test.)
Which key is used is controlled by another metadata key:
<meta-data android:name="io.branch.sdk.TestMode" android:value="true" /> <!-- Set to true to use Branch_Test_Key -->

To set this flag for certain builds, add it to the manifest for that build type or flavor. For example, you can add that flag to android/app/src/debug/AndroidManifest.xml if you have a buildType called debug in your app's build.gradle. RN defines a release buildType by default, so you can also set the flag to true in the main manifest and set it to false in android/app/src/release/AndroidManifest.xml.
Maybe this isn't exactly what you're trying to do, but you can probably accomplish it using this sort of approach.
If this doesn't help, I'm sure I can provide a script soonish.

@jdee Thanks for the response. Glad you are trying to find a workaround for us. That being said..
#ifdef DEBUG
    [RNBranch useTestInstance];
#endif

What is this DEBUG variable we're checking. If it's the Build Configuration:

this won't work because when we do our builds for our users to test, they get "archived" before being sent to iTunesConnect and when a project is archived, it uses the Release (for performance reasons) config:

What we define as a "dev" build is what data server the build is pointing at - not the build configuration. Make sense?

DEBUG is a C preprocessor macro that is automatically defined in an Xcode project for the Debug configuration. This is to be found in the build settings:

You can add your own if you like. You can add USE_BRANCH_TEST_INSTANCE=1 and then in your AppDelegate.m change it to
#ifdef USE_BRANCH_TEST_INSTANCE
    [RNBranch useTestInstance];
#endif

How are you telling the build what the server is? I imagine you have it in your env.js, which is probably not available until the RN app loads. But at the moment you're doing something "hacky," so you must be modifying the Info.plist in the iOS app.
Unfortunately for iOS I may not be able to come up with anything less hacky. The right answer in a native iOS app is to use a custom build configuration and scheme. For example, to archive a build that points to a staging server, you could copy the Release configuration, call it Release-Staging and then create a new scheme called GreatJonesStreet-Staging that would use that configuration in the archive step instead of Release. Then you'd set USE_BRANCH_TEST_INSTANCE in Release-Staging but not in Release.
Then when you archive GreatJonesStreet-Staging, you get a Release build that points to the test environment.
Unfortunately, RN itself doesn't support this on iOS. See #104. People hack up their own support for adding custom build configurations to RN Xcode projects, but that's probably no less hacky than than whatever you're currently doing. The only benefit might be that eventually RN has to support custom configurations, so the hackiness might disappear on its own eventually.
You can certainly do this on Android using productFlavors in Gradle instead of buildTypes. I haven't done that with Android and Gradle myself, but I can advise if you want to try it.

@jdee Why don't we do a Google Hangout and then I can follow-up and right up our solution here? Might be easier to show you what we're doing/trying to do. Shoot me an email to setup a time<EMAIL_ADDRESS>

@dwilt Good news. I was wrong. Took me a while to recall you're using CocoaPods, so what you want to do on iOS is easy. See PR #166 and the webview_example_native_ios, which also uses the React pod. There's now a separate WebViewExample-Test scheme that uses the Branch test key, while the WebViewExample scheme uses the live key. This is independent of whether you're doing a Debug or Release build, so you can archive both ways.

We can go over the details Monday. Have a good weekend.

@dwilt I've added a document with detailed instructions for what I was talking about.
https://github.com/BranchMetrics/react-native-branch-deep-linking/blob/master/docs/branch-environments.md
Option 2 (Advanced) is what I was recommending. The Xcode setup is a little involved, but you do it once, and then you don't have to do anything to the project configuration at build time to choose the key you want. This might simplify your life a bit, or maybe you'll prefer to stick with what you're doing until we can provide JS support.
I also did some work on the Fastlane plugin I talked about. See https://github.com/BranchMetrics/react-native-branch-deep-linking/tree/master/examples#automatically-set-up-ios-branch-configuration-experimental.
That plugin could also eventually offer some automated support for setting up custom flavors and schemes.

I was wondering if what discussed in the very first comment cannot be achieved using react-native-config?

@fabriziomoscon Thanks for the suggestion. If it's possible to read the configuration in the native code before the JS is initialized, that might be a good solution. I'll investigate.

Hi @jdee!  Has any progress been made on this?  I'd love to be able to set these values in JS for the reason @dwilt suggested above:

having it in the JS is very easy because we can generate one env.js file

I actually use react-native-config, which as suggested by @fabriziomoscon.  If we can get Branch to work with react-native-config, that would be fantastic.


Circular JSON error crashes dev tools

Hi!  Getting a crash in v1.1.5.
The minimum repro seems to be:
(1)
  return useQuery(['a'], async () => {
    const a = { a: undefined }
    a.a = a
    return a
  })

(2) Click that query to inspect in devtools

Devtools crashes

As a little more context, I came across this crash when I was using react-query to load a pdf into pdf-lib's PDFDocument, and then returning that document.  I don't actually have any need to inspect the contents of that object in devtools, just wanted access to the other query info.
Thanks for the amazing library!

Yeah... we'll have to find a way around this. Darn circular references... ;)

I actually seem to get this error from it trying to serialise the query itself. I've definitely don't have any recursive data in my request/response
    --> starting at object with constructor 'Object'
    |     property 'cache' -> object with constructor 'Object'
    |     property 'queries' -> object with constructor 'Object'
    --- property '["@@ux/accounts-client/ACCOUNT","my"]' closes the circle

I don't know if something's changed recently to make this problem even worse?

I'm seeing this error too, don't think its my query but rather this line:
https://github.com/tannerlinsley/react-query-devtools/blob/d2b880fa96daa85565bf85576e59bf5c2e126e7a/src/index.js#L210
The activeQuery object has a cache property that references itself, causing the circular reference exception.
I fixed it locally by deleting the cache property before the JSON.stringify.
      if (activeQuery) delete activeQuery.cache;
      return [activeQuery, activeQuery ? JSON.parse(JSON.stringify(activeQuery)) : null];

Happy to send a pull request but not sure what problems deleting the cache will have!
It does however work on my machine™

Rather than deleting the active query from your actual code, you could use the replacer function of JSON.stringify to just exclude it during stringification...

Good Idea @jackmellis, mine was just a quick bodge to get it working 😄

Hello ! I also have the same issue from recently when using useInfiniteQuery and i don't have any circular dependencies in the data i get from the API.
Here is the error:
--> starting at object with constructor 'Object'     |     property 'queries' -> object with constructor 'Object'     |     property '["products",{"predicates":[{"attribute":"recipe","comparison":"equals","type":"boolean","value":false}],"sortBy":"name","sortDirection":"ASC"}]' -> object with constructor 'Object'     --- property 'cache' closes the circle
Am i missing something when configuring my call?
Thanks a lot for your hard work !

We have the same issue and wondering if its something in react-query itself?
With react-query 1.4.4 its working with and with react-query >= 1.5.0 its broken and we get even for the simplest query this error

Hi @tannerlinsley
I just got the same error.
TypeError: Converting circular structure to JSON
    --> starting at object with constructor 'Object'
    |     property 'cache' -> object with constructor 'Object'
    |     property 'queries' -> object with constructor 'Object'
    --- property '["locations"]' closes the circle

same issue.

Have it as well (data structure is flat)

@tannerlinsley I've created a PR #27 with @jackmellis proposal of using replace callback of JSON.stringify().

npm package hasn't been updated yet.

I got the same error with<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

I got the same error with<EMAIL_ADDRESS>and<EMAIL_ADDRESS>seems like it fixed in 2.4.2! Cool.

I still get the error with<EMAIL_ADDRESS>and<EMAIL_ADDRESS>


what version of pytorch-lightning should be used?

attempts to read the models.ckpt fail with
KeyError: 'pytorch-lightning_version'  ... using 2.3.3 of lightning and pytorch-lightning

Hi,
We use pytorch in our model, can you try to use pytorch for loading?

hello，sorry to bother you，but i cannot load the models.ckpt with torch in python.If possible,could you tell me what version of the torch do you use.I would be very grateful❤


[SPARK-20013][SQL]merge renameTable to alterTable in ExternalCatalog

What changes were proposed in this pull request?
merge renameTable to alterTable in ExternalCatalog has some reasons:
In Hive, we rename a Table by alterTable
Currently when we create / rename a managed table, we should get the defaultTablePath for them in ExternalCatalog, then we have two defaultTablePath logic in its two subclass HiveExternalCatalog and InMemoryCatalog, additionally there is also a defaultTablePath in SessionCatalog, so till now we have three defaultTablePath in three classes.
we'd better to unify them up to SessionCatalog
To unify them, we should move some logic from ExternalCatalog to SessionCatalog, renameTable is one of this.
while limit to the simple parameters in renameTable
  def renameTable(db: String, oldName: String, newName: String): Unit

even if we move the defaultTablePath logic to SessionCatalog, we can not pass it to renameTable.
So we can merge the renameTable to alterTable, and rename it in alterTable.
How was this patch tested?
delete some tests in ExternalCatalogSuite which already existed in SessionCatalogSuite,
and move some other tests in ExternalCatalogSuite which does not exist in SessionCatalogSuite

Test build #76038 has started for PR 17721 at commit 2ea645c.

Test build #76038 has finished for PR 17721 at commit 2ea645c.

This patch fails Scala style tests.
This patch does not merge cleanly.
This patch adds no public classes.

Build finished. Test FAILed.

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

@windpiger could you make sure that the freshly added events still work after this change.

ping @windpiger

We are closing it due to inactivity. please do reopen if you want to push it forward. Thanks!


Create CONTRIBUTING.md

Added a document containing the contributing guidelines

Thanks @dianzrong ! What do you think about following an example from a well known open source project?

@abrichr I went with a similar format to Python Fire and Puppet, the latter being mentioned on the github blog as being a good example

Thanks @dianzrong ! Those examples in the links you provided seem much more comprehensive. Can you please add the following:

testing
PR description requirements / template
Issue requirements / template

Thank you!


Move parameter docs to separate page, add package params docs

(original ticket against IBM Cloud Functions docs: https://github.com/IBM-Bluemix-Docs/openwhisk/issues/19)
The parameters documentation was mostly under the "JavaScript" section, and the use of package parameters wasn't covered.  This moves the parameters documentation to its own page, links to it from each language section in the actions page, and adds some documentation for package parameters.
I've sent the ICLA through, but just now this moment so I won't be listed yet.

What a lovely thorough review!  Changes made as requested.

Im wondering if we should leave a short blurb in the actions.md about passing parameters to an action under JS, and defer the rest to the new doc. This is because later in actions.md there are uses of -p

I thought I had linked to the parameters doc from everywhere where there already was (or I thought there should be) mention of parameters.  @rabbah is there somewhere in particular where you feel this information belongs and is missing?  I can add it but I'm not sure where.  Thanks for the other comments as well, I'll revisit.

You did but I thought a quick one liner: here’s how you invoke and pass a parameter. For more go to this link.

Some really good review comments here, can we review ALL the docs like this? :)  I think we're really improving what's there.  I've taken all the comments above into account, tried to improve the introduction and head off some common confusion about parameters, and moved the file parameter stuff to its own section.  Also linked to the other language examples from the parameters page, and to the parameters page in the first location that parameters are used on the main actions page.

Submit more PRs :)

Great PR!

Am I blocking this?  I think I've answered all the comments and this PR is ripe for another review, but please let me know if there's anything I should be doing at this end

Thanks @lornajane for the contribution.


💡[Feature]: Feedback form show Thank you message after submit form

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
I will add Thank you for your feedback message under form after submition of the form.
Use Case
Better feel to User
Benefits
User satisfaction
Add ScreenShots
NA
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@sk66641 Please assign me this task !
I will finish it as soon as possible
Thank You !


Remove calls to apt-get update

calls to apt-get update should be avoided (those are handled in the apt task to begin with)

I think this has been dealt with in the travis build branch as one of the measures taken to speed up deploy?


Admin must approve potential users

Add logic for admins to approve profiles to avoid spam accounts

I don't think admins should have to approve new account, rather a Captcha or similar mechanism. We want to make it easy for legit users to register
think about and propose a solution here and discuss with client too before implementing


ESP32s not sending/recieving

I have uploaded the software to both gloves and have connected them to my computer over Bluetooth. The opengloves driver is able to track their position but I have no button inputs, finger tracking or haptic feedback. I am able to perform auto-calibration in the driver but not extend/retract the servos fully, I'm just told the command could not be added to the pipeline.
The configuration in the opengloves driver is as follows:
Both gloves enabled
Communication method Bluetooth serial
Right name: lucidgloves-right (same for firmware and serial number)
Left name: lucidgloves-left (same for firmware and serial number)
Driver emulation: lucid glove
Encoding protocol: Alpha
Any fixes?

Are you able to check the bluetooth output in arduino IDE over bluetooth serial port numbers?

Change your comms method to usb serial and use the serial monitor(in arduino ide go to tools>serial monitor and then change baud rate to 115200) to see if your pots are actually sending positional data to the Esp32s and then to the computer. then, make sure you have the comms method changed back to btserial when you have verified the positional tracking works. Make sure opengloves is enabled in steam, and try flipping your pot values if you think you may have wired them backwards.

In addition to this, SteamVR must be open for those functions to work. In a later release, this won't be needed.


Add SCB to the SDK

Fetch is on channel creation and store it locally
Expose API to retrieve it
Document how to use it from a cln node

Docs are ready at https://sdk-doc.breez.technology/guide/static_channel_backup.html


Local services requested for signal page

This issue closely mirrors https://github.com/dxos/dashboard/issues/45; the raw services URL is being used rather than one that matches the Apache routes:
https://github.com/dxos/dashboard/blob/523db3f958c4348a38e8b1be3d26022367dad8be/src/pages/console/signal.js#L47

https://github.com/dxos/dashboard/pull/47


Add model unit tests imaging & family-info

Changes proposed in this pull request:

Add model unit tests imaging
Add model unit tests family-info

cc @HospitalRun/core-maintainers

Should be moving to some more interesting stuff soon. A bit new to Ember in general so using the tests as a guide to get myself up to speed. :tropical_drink:

This passes locally so I'm going to look into what might be different about travis and the date time string.

Just re-running travis. Ignore


Feature: Add swift/obj-c bindings for filteredSearch

Describe what you are looking for
There are C++ and Rust bindings for filtered search, but they don't yet exist for Swift.
Would love to call this into Swift!  Happy to provide a patch for this.
Can you contribute to the implementation?

[X] I can contribute

Is your feature request specific to a certain interface?
Other bindings
Contact Details
<EMAIL_ADDRESS>Is there an existing issue for this?

[X] I have searched the existing issues

Code of Conduct

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

@ashvardanian would love your review when you get a chance! https://github.com/unum-cloud/usearch/pull/471


sl.coffee: minor translations

Hello, @lynxlynxlynx! Thank you for contributing. Could you sign our CLA so that I can merge your pull request?

done.

Thanks.


Create a new repository for the language specification of Brain-Flak

I've been toying with the idea of writing an interpreter for Brain-Flak in C. I feel it would be nice to create a thorough language specification to aid the in the creation of interpreters (a javascript interpreter would be quite nice).

It's funny that you mention that, because I have actually been thinking about writing a javascript interpreter for a while now. :) I agree that it would be nice to have a specification, but I don't know if it's worth making a separate repository for it. Is the description in the README not precise enough? I suppose one thing I can think of that the current version does that is left unspecified in the README is how the value of the {} is not reset after each loop. (which is why {{}} can sum the stack). Beyond that, there are some things I don't think we necessarily should specify, and instead leave that up to the interpreter. For example, I think ASCII mode is worth specifying, but I'm not sure if we should inlcude things like

File input VS command line args

Alternate overflow/underflow modes

Debug flags

Unicode mode

Separate input and output formats (To allow for decimal in ASCII out, or vice versa).

Not that any of these are bad features, I just view them as interpreter perks.

Actually the differentiation between specifications and interpreter perks was the main thing I was interested in seeing in the specification. Namely how overflow/underflow should work and what the minimum maximum height of the stack should be.
As for about being in a separate repository, I felt that commits that tweaked the specification would create clutter when looking through the history of the repository as updates to the example programs have done (one of the things I have been meaning to do for a while is to migrate the example programs out of the README and into this repository's wiki). Speaking of the wiki, I was taking a look back at how it works and I was thinking that it might be the ideal place for such a thing (I had previously overlooked the wiki because I thought that it did not give you the ability to leave a description attached to your change like a commit message, but it turns out I was mistaken).


Footnote back-references

It would be nice if the footnotes linked back to the source, like here.

I came here to open the same request, since I would really like this in Zola.
Has anything like this been implemented, or do you need help? I'm happy to offer to do it, maybe with some pointers to the right place in the code, since I'm not a Rust programmer.

This is a tricky one. On the one hand, the value of back-references are immediately apparent.
On the other, implementing does not play well with the two-phase design of pulldown. One would have to go through all the events and capture the footnote references before you could emit a footnote itself. Usually, when footnotes are where they are supposed to be --at the bottom-- that's ok. But it's also valid to have footnotes at the top, like this:
[note]: we'll be referring to this later!

See the [^note] above.

Adding support for this not only brings some extra user complexity, but also a big hit to performance. The pulldown html parser is meant to provide a lean and performant reference implementation, which does not lend itself well to this feature.
The reality is that many users of the library do not write their own renderers and there seems to be an appetite for more features like this. We may have to re-evaluate whether we want to keep a lean implement or rather provide something more featureful.

Personally I use this exclusively for scanning to see what Markdown features are used where in source files; and it was hands down the best choice for that because of the raw speed. If things like this get implemented at all I would like to see them relegated to the renderer, not the parser. Personally I would have like to have just a parsing library with a separate renderer based on it, but in any even I would still appreciate being able to parse without being slowed down by features like this.

That makes sense, thanks for the thoughtful reply @marcusklaas . I don't have a clever suggestion, since I'm not familiar with the parser. But would you necessarily need to capture strictly valid back-references? If the renderer emits a #note link, and I don't have a target for it, that's sort of my problem, no? But maybe I don't have the right mental model, I'm assuming the parser wants to traverse the entire document just once.
I agree with both you and @alerque that taking a performance hit for this feature is not desirable.

Hi, I have hit the same issue and here are my thoughts on it: as @2mol said, if we don't care about generating dangling backlinks for footnotes that are never referenced, then this is simply a matter of adding the right id to the reference. Except that there is not guarantee that there will only be one reference to a given definition.
A possible solution is to generate "sub-ids" for each reference of a given footnote (storing them in a hashmap) and use them to generate multiple backlinks as Wikipedia does. The problem becomes that you'll only generate backlinks to reference that were above the definition.
What are you thoughts about this? I think that for the many indirect users of pulldown-cmark through zola or cobalt this is a quite needed feature, but it is not obvious which direction to take.

Slightly changing syntax of footnotes from:
Text[^footnote]

[footnote]: Text

to
Text[^footnote]

[^footnote]: Text

would allow to emit back-links inplace (if each footnote has only one associated link).

For what it's worth, I experimented a bit with changing the rendering pass as part of trying to see how far I could get on the "standard" footnotes style with the current parser. (The answer is: pretty close, but as noted in the discussion in #20, the fact that footnotes are treated as single-block elements means a lot of existing footnotes out there won't parse.) As part of that I confirmed that you can quite easily build backlinks in a renderer given what pulldown-cmark already does.
While it's totally possible to end up with cases where you have a footnote reference with no definition or vice versa, that's an authoring concern (and a place where a renderer could choose to warn!). What's more, that's common in other Markdown implementation.
For example, if you drop this Markdown source into the pandoc demo (or just run pandoc --from markdown --to html5):
A paragraph of text. This demo has a valid footnote reference.[^valid] It also has a invalid footnote reference.[^invalid] And the document also has an orphaned definition, which is not referenced anywhere.

[^valid]: This one is valid.

[^orphan]: This is an orphan footnote definition.

This is the HTML it will generate:

A paragraph of text. This demo has a valid footnote reference.1 It also has a invalid footnote reference.[^invalid] And the document also has an orphaned definition, which is not referenced anywhere.

This one is valid.↩

There are two extra bits of data required to make that work the same way in a renderer:

a list of footnote definitions which are actually referenced at least once (so e.g. a HashSet seems reasonable here)
a similar list of footnote definitions which actually exist

If you pass both of those to a renderer along with the events, then it's straightforward when emitting the footnote events to do the same thing as pandoc and similar. The existing renderer doesn't support this, of course, and given it simply consumes an Iterator<Item = Event> it’s not clear to me that it could even be made to do so easily, but a fork of that renderer could do it easily enough.

This is actually quite encouraging for my purposes. The only serious blocker I see for conformance to the “standard” footnote format is having a scan/parse mode which supports multiple block children in the footnote and then having that lightly-tweaked renderer available (whether in-tree or not!).
While that unfortunately cannot be implemented backwards-compatibly with the current options (it changes the meaning of an indented block after a footnote definition block), I think it could be implemented with a new option. I am going to see if I can make progress on that. (Could be slow going: I don’t have a ton of time.)

Apologies if bumps are unwelcome, but I am just commenting to add that this would be a really good feature to have. Personally, I consider this a key requirement for any Markdown implementation. Footnotes should be in the foot of the document with back-links, regardless of where they're defined in the text itself.

It seems like backlinks are also needed for the footnotes to render correctly in some (/many?) RSS readers: https://css-tricks.com/footnotes-that-work-in-rss-readers/


Import values from quick fix

https://user-images.githubusercontent.com/72190/114414125-d8de6380-9bae-11eb-98c6-0221748fc135.mp4

Failures is because of dead urls at Jetbrains


Allow commands from pr description

Allow merge commands to be part of the pull request description by handling the description of the pull request as an added comment.
resolves #239

I believe if a user would close a PR (that had a merge command in its description) before it was merged and reopen it again, it would still initiate the same merge command. This is probably fine, but it would be good to make this behavior explicit in a test.

I think it would be better to avoid that, since at that point someone is already manually interacting with the PR anyway, and this indeed sounds quite surprising. There's probably a way of distinguishing PR creations from PR re-openings, right?

@OpsBotPrime merge

Pull request approved for merge by @musicismyalibi, rebasing now.

Rebased as 75c74664cb3c92c452bffd52b412ab40da648adc, waiting for CI …

CI job :yellow_circle: started.


Fabric 1.17 Port

This ports the mod to Fabric 1.17 fully along with a massive clean up to match the Forge version. Closes #1

Wow.  Thanks so much man!
Hope this is useful to you on your server or in your modpack.
I'll use it as a guide to under stand 1.17 better.
I'll try to get out 1.18 immediately.   And now that me and lupicus are both healthy again, I'll try to keep a closer watch on git issues again.

I'll try and build this and test this by wednesday night and make it available for download.
MacTso

Thanks! I updated it to the latest Loom as well so it should make 1.18 porting a lot easier for you!

Wonderful.  I'll try to get the 1.17 environment set up tomorrow.


Apr SL release notes

this pr sets to add all the SL and MF updates for apr via a release note.  It also updates the tableau page saying we're going deprecate the metrics and dimension data source soon.
Notion draft

Thank you so much @runleonarun - merging this now!


unable to execute "kamel run" in secure mode

I used simple java code and i executed this code by using "kamel run" command, I have taken the reference of
https://camel.apache.org/camel-k/next/installation/platform/docker-desktop.html and it was working fine.
But this is Unsecure method, so now I want to implement secured method then I removed
{ "insecure-registries": ["host.docker.internal:5000"] }  from daemon.json file and I have installed camel-k by using below command
kamel install --registry docker.io --registry-auth-username your-user-id --registry-auth-password your-user-password
(i have used my docker hub credentials here)
after the installation I have executed below command but every time it is failing.
Kamel run sample.java --dev
how to execute my kamel code in secure method?

Thank you @squakez, I have used kamel install --registry docker.io --organization your-user-id-or-org --registry-auth-username your-user-id --registry-auth-password your-password  instead of above mentioned command and it started working.


feat: add syria to Country Maps

🏆 Enhancements
Add Syria map, to be used in the CountrMap visualization.

@ktmud / @rusackas
This is my first contribution to open source, would you please take a look at the PR, and give me some guidelines.
Thanks :grinning:

The preview shows that the map file does not work.

@ktmud I've updated the PR description, also, I updated the map.
@kristw Thanks for your note, I wasn't aware it wasn't working. I updated the map now and tested on storybook, and it's working now :)

@villebro could you please take a look at this PR :grinning:
Thanks :pray:


fixed receive modal not showing

Thank you a lot for contributing to Cosmos Voyager!

Issue

closes: #690
❤ Thank you!

I think your linter altered the Stylus when it shouldn’t have. I prefer the no commas no brackets style, but we can discuss that later.

fixed