Starts torbrowser in the 'wrong' language

System: Debian testing/sid/experimental on amd64 with KDE Plasma 5 as DE
torbrowser-launcher version 0.2.0-2
I am from NL but I want my software to be/operate in English.
When I start torbrowser-launcher I get the first screen in English, but then it downloads the NL version of the torbrowser ... which is NOT what I want.
When I first encountered this issue, I made sure that all my locale settings were correct:
$ locale
LANG=en_US.UTF-8
LANGUAGE=en_US:en
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

I purged the torbrowser-launcher package from my system and did a rm -rf ~/.local/share/torbrowser to make sure everything related to it was removed from my system.
I then reinstalled the package, but the problem persists.
I have no idea how torbrowser-launcher determines the language version to install, but I find the current behavior highly undesirable.

I've located the source of my issue and it is related to KDE Plasma 5 combined with Firefox.
In System Settings -> Regional Settings -> Formats -> Region I had specified 'Nederland (nl_NL)' since that would set Numbers/Time/Currency/Measurement Units/Collation and Sorting to the Dutch values. That appeared to be the reason that torbrowser downloaded the Dutch version.
Changing the Region to en_US (but all the individual components to nl_NL) made torbrowser download the English version.
The odd thing is that this behavior seems to be specific to Firefox/Iceweasel/TorBrowser ... which are not KDE/QT applications.
I noticed that since I had to completely wipe Iceweasel (including cache/config) from my system (for some reason) and when I reinstalled it after that I saw some Dutch (and even German ... ugh) things in Iceweasel. That's when I decided to try to change the Region settings and that 'fixed' this issue.


Add Sorbet extractor

Extractor implemented here: https://github.com/fcsonline/codemonitor/commit/9c8b154aafafa0bd301559116e2f8ffc0fc47cea


ci: adds tooling to sync values file

What problem does this PR solve?:
This tooling syncs the helm values configmaps in charts/templates from hack/addons/kustomize
part of the changes here also include some file organization fixes so that we have similar structures in hack and in addons.
Which issue(s) this PR fixes:
Fixes #
How Has This Been Tested?:

Special notes for your reviewer:

I wanted to see how this worked, but the sync fails:
> go run /home/dlipovetsky/nutanix/cluster-api-runtime-extensions-nutanix/hack/tools/sync-helm-values/sync-values.go
failed to sync err: failed to open /home/dlipovetsky/nutanix/cluster-api-runtime-extensions-nutanix/hack/addons/kustomize/ccm/aws/manifests/helm-addon-installation.yaml with error open /home/dlipovetsky/nutanix/cluster-api-runtime-extensions-nutanix/hack/addons/kustomize/ccm/aws/manifests/helm-addon-installation.yaml: no such file or directory

I ran make sync-helm-values and found the license header removed from these files:
charts/cluster-api-runtime-extensions-nutanix/templates/ccm/aws/manifests/helm-addon-installation.yaml
charts/cluster-api-runtime-extensions-nutanix/templates/ccm/nutanix/manifests/helm-addon-installation.yaml
charts/cluster-api-runtime-extensions-nutanix/templates/cluster-autoscaler/manifests/helm-addon-installation.yaml
charts/cluster-api-runtime-extensions-nutanix/templates/cni/calico/manifests/aws/helm-addon-installation.yaml
charts/cluster-api-runtime-extensions-nutanix/templates/cni/calico/manifests/docker/helm-addon-installation.yaml
charts/cluster-api-runtime-extensions-nutanix/templates/cni/calico/manifests/nutanix/helm-addon-installation.yaml
charts/cluster-api-runtime-extensions-nutanix/templates/cni/cilium/manifests/helm-addon-installation.yaml
charts/cluster-api-runtime-extensions-nutanix/templates/csi/aws-ebs/manifests/helm-addon-installation.yaml
charts/cluster-api-runtime-extensions-nutanix/templates/csi/local-path/manifests/helm-addon-installation.yaml
charts/cluster-api-runtime-extensions-nutanix/templates/csi/snapshot-controller/manifests/helm-addon-installation.yaml
charts/cluster-api-runtime-extensions-nutanix/templates/nfd/manifests/helm-addon-installation.yaml

We can't modify files tracked by git, unless we intend to commit the changes. Do these changes need to be added to this PR, or does the behavior need to change?

We can't modify files tracked by git, unless we intend to commit the changes. Do these changes need to be added to this PR, or does the behavior need to change?

The license headers are added by another pre-commit hook. I can add it as part of the tool, but I'd rather have the separate tool handle it

The license headers are added by another pre-commit hook. I can add it as part of the tool, but I'd rather have the separate tool handle it

If I run make sync-helm-values, and it modifies files, am I expected to run something after? What is it?

If I run make sync-helm-values, and it removes license headers, am I expected to run something to add them back? What is it?

make sync-helm-values now adds license headers.

Thanks @faiq! I tried locally, no files changed. This seems fine to me, but I'm curious what you think about Jimmi's request.

I'm closing this and reopening a PR that should accomplish similar goals based on the changes in #809


[bspwm] some bug with eww??

when i click for example the shutdown button the whole screen blacks out and only that window is shown. animations also bug. happens after some time after the computer is turned on.
MISC: the only modifications i applied were about my second screen to turn on and also have a polybar there. that's basically it.

Try to disable the animations
sudo pacman -S picom to install the normal picom
For the shutdown thing, can you try to shutdown from the terminal to see if that works?

all the ui elements are working kinda properly. problem showcase:

also there is a issue with the showcased menu: when i click on stuff it works but the ui elements don't update their visuals. (i should probably modify it after it gets fixed to remove some stuff and change some icons because this is a pc instance and not a laptop)
the screen shouldn't be black when i open this window should it be

The screen goes black because you aren't running any compositor. Also, please install all the dependencies, it seems like some of them are missing.
bluez is required for the Bluetooth to work.
rfkill for airplane mode.
wireless-tools for the Wi-Fi to work
redshift for the night light to work, that's the reason the buttons do nothing.

The pc doesn't have a wifi module nor a bluetooth one. I modified the wifi module in the polybar so it shows up for my ethernet cable. That's why i removed such packages. Also idk whats about the compositor, what shall i add into the bspwmrc so it works.

I've manually ran picom and it is full of errors

perhaps it crashes when it is ran by the bspwmrc?

also i've explicitly enabled compositing in the x server config via:
Section "Extensions"
    Option "Composite" "Enable"
EndSection

but it still doesn't fix it.

You can ignore those errors, happens to me as well. Is the compositor running regardless?

Says its running

looks like picom crashes/stops working for some weird reason because of this:

before doing any change to this everything worked fine except again the eww windows: they were opening correctly, but no data was correct about them. for example the spotify player didn't display any information whatsoever

update: the spotify window issue has resolved itself. but there's still a problem with these 2:

they're not working at all properly.

What is your distro?

Can you share me eww logs?
killall eww
eww daemon
eww logs
Then open any widget and see any red things popping up

It seems like everything is fine, I am not sure if your dual monitor is causing the problem

I literally did no modifications to eww whatsoever. For my 2nd monitor the only modification i did was to create a polybar with it showing the time and the layout change button.

update: looks like eww bugs only when I open that window:

if I click on the spotify window before I open this one everything works as expected.

I think the scripts are acting weird because of missing dependencies


table!() allows for swapping two fields of the same type

Setup
Versions

Rust:rustc 1.30.1 (1433507eb 2018-11-07)
Diesel: 1.3.3
Database: SQLite 3.25.3 2018-11-05 20:37:38 9e099fbe5e13c33e683bef07361231ca525b88f7907be7092058007b75036f2
Operating SystemArch Linux, 4.19.4-arch1-1-ARCH

Feature Flags

diesel: N/A

Problem Description
This struct:
#[derive(Queryable, Debug, Clone, PartialEq, Eq, Default)]
pub struct ChannelStateRecord {
    pub id: i64,
    pub channel_id: Vec<u8>,
    pub address_a: Vec<u8>,
    pub address_b: Vec<u8>,
    pub nonce: Vec<u8>,

    pub balance_a: Vec<u8>,
    pub balance_b: Vec<u8>,

    pub sig_a_v: Option<Vec<u8>>,
    pub sig_a_r: Option<Vec<u8>>,
    pub sig_a_s: Option<Vec<u8>>,

    pub sig_b_v: Option<Vec<u8>>,
    pub sig_b_r: Option<Vec<u8>>,
    pub sig_b_s: Option<Vec<u8>>,
}

...works with this schema:
table! {
    states (id) {
        id -> Bigint,
        address_a -> Binary,
        address_b -> Binary,
        channel_id -> Binary,
        nonce -> Binary,
        balance_a -> Binary,
        balance_b -> Binary,
        sig_a_v -> Nullable<Binary>,
        sig_a_r -> Nullable<Binary>,
        sig_a_s -> Nullable<Binary>,
        sig_b_v -> Nullable<Binary>,
        sig_b_r -> Nullable<Binary>,
        sig_b_s -> Nullable<Binary>,
    }
}

What are you trying to accomplish?
Hook my struct up with the database
What is the expected output?
The schema has a couple fields swapped (channel_id comes before the addresses in ChannelStateRecord). And yet it compiles. Everything should be golden. BUT it's not, even though it compiles, the table!() macro appears to rely on field order and swapping any two of the same type seems to be enough to fool compile-time checks. As a result, my program reads/writes wrong fields off/to wrong columns. I'd expect Diesel to either be smart enough to point the problem out or to be able to use the schema correctly anyway. I realize this looks an awful lot like forgetting to migrate the DB properly, but I did write a script that reproduces this and I would have records coming back wrong from the freshly migrated database.
What is the actual output?
It builds and then uses what it built wrong.
Steps to reproduce
I'm using the above two structs and a NewChannelStateRecord as my auto-ID'd new record helper:
#[derive(AsChangeset, Insertable, Clone, Debug, Eq, PartialEq)]
#[table_name = "states"]
pub struct NewChannelStateRecord {
    pub channel_id: Vec<u8>,
    pub address_a: Vec<u8>,
    pub address_b: Vec<u8>,
    pub nonce: Vec<u8>,

    pub balance_a: Vec<u8>,
    pub balance_b: Vec<u8>,

    pub sig_a_v: Option<Vec<u8>>,
    pub sig_a_r: Option<Vec<u8>>,
    pub sig_a_s: Option<Vec<u8>>,

    pub sig_b_v: Option<Vec<u8>>,
    pub sig_b_r: Option<Vec<u8>>,
    pub sig_b_s: Option<Vec<u8>>,
}

My migration:
-- Your SQL goes here
CREATE TABLE states (
  id INTEGER NOT NULL PRIMARY KEY,
  channel_id BLOB NOT NULL UNIQUE,
  address_a BLOB NOT NULL,
  address_b BLOB NOT NULL,
  nonce BLOB NOT NULL,
  balance_a BLOB NOT NULL,
  balance_b BLOB NOT NULL,
  sig_a_v BLOB,
  sig_a_r BLOB,
  sig_a_s BLOB,
  sig_b_v BLOB,
  sig_b_r BLOB,
  sig_b_s BLOB
);

CREATE INDEX addresses_idx ON states (address_a, address_b);

Checklist

[x] I have already looked over the issue tracker for similar issues.
[x] This issue can be reproduced on Rust's stable channel. (Your issue will be
closed if this is not the case)

Full context
Clone this and checkout at diesel-bug-reproduction. cd into bounty_hunter and run reproduce_no_retrieve.sh. See test.json and you'll observe how the record that comes back from the DB is different and causes deserialization to fail on a field with not enough bytes that came from another field (channel_id).


In nvim version 0.7.0 the function is invalid

Default configuration underscore not working

Thank you for the report! Can you tell me a little more?

i using packer
use {
  'yamatsum/nvim-cursorline',
  config = function()
    require('nvim-cursorline').setup()
  end
}

When I upgraded nvim to 0.7.0, underscore didn't work

fxxx, it works again now


⚠ Processors has degraded performance

In 661f3d7, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 45 ms

Resolved: Processors performance has improved in 1aa7aa6.


feat: pulsar oauth

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?

use pulsar API for enumerator
support pulsar oauth

integration with stream native cloud
Checklist For Contributors

[x] I have written necessary rustdoc comments
- [ ] I have added necessary unit tests and integration tests
- [ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[x] I have demonstrated that backward compatibility is not broken by breaking changes and created issues to track deprecated features to be removed in the future. (Please refer to the issue)
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Checklist For Reviewers

[ ] I have requested macro/micro-benchmarks as this PR can affect performance substantially, and the results are shown.

Documentation
- [ ] My PR DOES NOT contain user-facing changes.

Click here for Documentation
Types of user-facing changes
Please keep the types that apply to your changes, and remove the others.

Connector (sources & sinks)

Release note

it involves auth part, manually tested on stream native cloud


Channel closed, on-chain empty

Hi, same as others have experienced, I received 50k sats to open a channel, paid 10k fee, 15 minutes later the channel closed. Now the remaining 40k sats seem to be in limbo.
mutiny-logs.txt

Hey sorry about this, your funds should show up in a couple of days at most. Let us know if they don't.
2023-09-10 07:27:18.017 ERROR [lightning::ln::channelmanager:8344] A ChannelManager is stale compared to the current ChannelMonitor!
2023-09-10 07:27:18.017 ERROR [lightning::ln::channelmanager:8345]  The channel will be force-closed and the latest commitment transaction from the ChannelMonitor broadcast.

Looks like this is the stale channel manager bug. We're still tracking down the exact reason this happens but we suspect this happens when you close the app/page too quickly after an invoice has been paid. Waiting a couple seconds after a payment to close the app should help prevent this in the future.

For reference:
closing txid: d4392807df939e794535ad43ea4d5a4680aa588d28bb0321b5bd17fe009cd394
node id: 02158c97406ca9b97f43fee03cda088ae7873d3247ec5b920a050136803e4af7a6

Yep it worked. Thank you!


Add support for including fast-rsa-engine as a no-op dependency on MRI

This will allow users of this gem to include it as a dependency, even if all of
their use-cases aren't on the JVM. Obviating the need for if statements all
over the place just to get faster RSA ops

Well, this is annoying. I suppose Travis is running these tests faster than they are running locally causing failures >_<


[Theming] Apply distinct secondary Display, Heading, and Title font

We use larssiet for all the styles in src/shared-components/typography/index.ts. However, we want to use a different font for Display, Heading, and Title for our secondary theme:

These changes set the font-family on the class, giving it higher precedence than body.
This also removes the direct TYPOGRAPHY_CONSTANTS import in injectGlobalStyles, which has no impact on output.

cool, You can release 13.X with this change if you want

It's not an urgent item so it can go out with v14! 🙂


Bug: running npm/yarn install when an install is already in progress can break the in progress deps install

Bug description
We have seen this on our CI machines and for @sleaper even on his local machine.
Here's how it looks like with pnpm:

here's an example output of stuck install with yarn:

My suggestions would be to remove the whole https://github.com/YassinEldeeb/prisma-tgql-types-gen/blob/26bc06ebd6540776410fd4da172c46251181ba57/packages/generator/src/generator.ts#L29
because generators often run inside a yarn install already.
It would be simpler and more robust to just let the use install this manually.
To Reproduce
Steps to reproduce the behavior:

run yarn install with a schema which wants to install graphql-scalars
wait for the install to get stuck

Expected behavior
yarn install does not get stuck
Screenshots
:arrow_double_up:
Prisma information
add the used schema.prisma file
Environment & setup
we have seen this on ubuntu 20 and 22 with any nodejs version.
Prisma  Version
4.0.0

Interesting! Can you provide me with further information?

running npm/yarn install when an install is already in progress can break the in progress deps install
I can't fully understand what that means.  Not sure why.

@prisma/client runs prisma generate in its postinstall script. Not sure why.

Yes, It was a requested feature from the community. Cause they often forget to generate the client after installing the dependencies. So it runs the prisma generate command runs automatically after installing the dependencies.

when yarn/npm/pnpm runs postinstall script, the process is not finished yet. Lockfile is not yet written out to the file system. Running another install at this moment is running two install commands in paralel.
Package managers are not built to handle this usecase so they fail.

when yarn/npm/pnpm runs postinstall script, the process is not finished yet. Lockfile is not yet written out to the file system. Running another install at this moment is running two install commands in paralel.
Package managers are not built to handle this usecase so they fail or get stuck.

Oh, I got what you mean. But there's something very strange about it. As you can see here in the installPackage helper function, I only install graphql-scalars after you've changed your schema and ran prisma generate locally(manually). So if you run in a CI environment or even someone else got your codebase. It'll already have the package in package.json and It'll skip installing it.
const installPackage = (useYarn: string, pkgName: string) => {
  const packageManager = useYarn ? 'yarn add' : 'npm i'

+ const hasGraphQLScalars = fs
+   .readFileSync(path.join(process.cwd(), './package.json'), 'utf-8')
+   .includes(`"${pkgName}"`)

+ if (hasGraphQLScalars) return

  logger.info(`${GENERATOR_NAME}:Installing ${pkgName}`)
  spawn(`${packageManager} ${pkgName}`, [], {
    shell: true,
    stdio: 'inherit',
  })
}

In that case this bug is probably not that important to fix, but would be worth checking out a bit more, because it is certainly happenning and it is very maddening.

ALternative cause for this stuck generation I suspect is having npx in the generator name
That's what I've also thought of. When I was developing this generator I ran into all sorts of issues when adding the provider. It gets stuck for whatever reason. Sometimes it works with npx, sometimes without it. It's getting crazier and crazier. My best route to go about it now is adding the path to the bin directly like this for example node ../node_modules/.bin/prisma-typegraphql-types-generator/bin.js

In that case this bug is probably not that important to fix, but would be worth checking out a bit more, because it is certainly happenning and it is very maddening.

Agree. It has been bothering me for so long even in development. But I guess it's a prisma thing that we have nothing to do about it as they're saying and will be saying that this is all can fall apart in any moment.

Might have to ping Prisma about it. The provider just works perfectly with @prisma/client but for the community generators, it's just super unreliable.


add selectedCard to modelManager

Pull Request Test Coverage Report for Build 246

5 of 8 (62.5%) changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.09%) to 85.01%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/main/java/seedu/address/logic/parser/AddressBookParser.java
0
1
0.0%

src/main/java/seedu/address/model/ModelManager.java
2
4
50.0%

Totals

Change from base Build 241:
-0.09%

Covered Lines:
1775

Relevant Lines:
2088

💛  - Coveralls

#125
#126


TypeScript (and emmet) suggestions show up in the wrong order

Does this issue occur when all extensions are disabled?: Yes/No

Version: 1.65.2
Commit: c722ca6c7eed3d7987c0d5c3df5c45f6b15e77d1
Date: 2022-03-10T14:33:49.188Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin x64 20.6.0
When using import statement completions the suggestions which come back are not always in a great order, meaning I need to cycle down a couple of times until i get what I need. This makes the development process a bit degraded compared to others IDEs.
An example is this:

In the image above, i want ContentType but the suggestions I get back are ContentTypeHeaderStories and an emmet suggestion. The one i want is on the 3rd row down.
I don't want to swtich emmet off but I don't think emmet should be prioritised so high above TypeScript suggestions, especially when (in this case) it's being used as a "catch all".
Secondly (and this may be more for @andrewbranch) I would expect the default export ContentTypeHeaderStories to be below ContentType and only be higher when I type ContentTypeH...
Steps to Reproduce:

Clone https://github.com/jasonwilliams/autocomplete-testcase
follow steps in readme

Thanks for the repo  @jasonwilliams!
@jrieken I believe the suggestions are sorted like this due to the prefix match. contentTypeHeaderStories has an insert text of import contentTypeHeaderStories ... so it matches the text already on the line
However for ContentType, the insert text is import { ContentType } which does not match the existing text as well
This behavior makes sense once I understood it but feels confusing as a user. Any ideas on how we can work around this?

The insert text doesn't matter but the filter text does. Emmet is using the line text as filter text and therefore matches fairly strong. You can see scores when pressing cmd+/ while IntelliSense shows:
prefix is the text value that's selected with the completion items range, word is the filterText

Emmet shouldn't be showing up there.
Though I feel that the most thorough fix for Emmet in this case would involve adding on a JSX parser (rather than just an HTML one), I realized the other day that I might be able to reduce the locations where Emmet suggestions show up.
For example, see https://github.com/microsoft/vscode/pull/146757

I find in recent updated vscode, the emmet suggestion is always on the top.

This seems to be getting worse. When I'm creating an object and I want to see what fields are available in the type, they always show at the bottom of the list. So I have to scroll down past a large number of suggestions that don't even make sense in the context. It's very frustrating and annoying.

@jodymgustafson I think in your case those completions are from another extension, meaning you'll have to file a separate issue at that extension's GitHub repository.

I believe the worst offender here is the Emmet suggestion, and will close this issue in favour of the Emmet-specific issue https://github.com/microsoft/vscode/issues/51537


[backport] Fix pod condition tag

What does this PR do?
Backport  #16119 to 7.44

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

replaced with https://github.com/DataDog/datadog-agent/pull/16140


review eth support

I have merged the pull request to dev branch. (https://github.com/btccom/btcpool/pull/64)
Discussion about the pull request is still here but this pull request will not be merged.

We moved to deveth branch and it could not be merged into master for a long time.
Bitcoin support is incomplete within the deveth branch.
I will close this pull request. When we are ready for the new version, we will merge it into master.


completion with non-dash-options (positionals)

I trying to write a script with various sub-commands that execute different actions. For example remote managing a server and debugging connectivity isssues or enable/disable services.
   server
       - test                 # sub-command 1
           - ping            # sub-sub-command 1.1
           - mtr             # sub-sub-command 1.2
       - config             # sub-command 2
           - apache       # sub-sub-commands 2.1
               - enable    # sub-sub-sub-commands 2.1.1
               - disable   # sub-sub-sub-command 2.1.2

What i would like to have is the auto-completion of all sub-*-commands so a user does not have to know all the sub-commands by heart.
Example usage woud be:
    server<space><TAB>
    test config            # auto-completion prints available sub-commands
    server test<space><TAB>
    ping mtr               # autocompletion prints test-sub-commands
    server test ping <servername>

The sub-commands shall not start with dashes as they are not actual switches. I guessing this could be done with a custom completer? So far i could not get argcomplete to auto-complete anything that has no dashes in it.
Can this be done with argcomplete?

I'm seeing the same problem. Default does not work for options without dashes.

Thanks for the report. Can you please paste a test use case that you expect to work?

Thank you for the quick response. I got it working. If you add the argument to the main parser like in the following snippet it does not work:
parser = argparse.ArgumentParser(description='description')
parser.add_argument("option", dest="option", help="positional option help")
argcomplete.autocomplete(parser)
args = parser.parse_args()

If you add the argument as a subparser then the code works as intended. Example snippet:
parser = argparse.ArgumentParser(description='description')
subparsers = parser.add_subparsers()
parser_option = subparsers.add_parser("option", help="positional option help")
parser_option.add_argument("--optional_option", dest="optional_option", help="optional option under option help")
argcomplete.autocomplete(parser)
args = parser.parse_args()

I was expecting argcomplete to work with the first snippet. Hope that help :+1:

Argcomplete can not possibly know what the possible values are in the first case.
If you specify the possible option choices like follows the first method should also work:
parser.add_argument('move', choices=['rock', 'paper', 'scissors'])

The second option is however the preferred way to achieve this result in my opinion.

The confusion arises from the fact that this works:
parser = argparse.ArgumentParser(description='description')
parser.add_argument("--option", dest="option", help="optional option help")
argcomplete.autocomplete(parser)
args = parser.parse_args()

but this does not:
parser = argparse.ArgumentParser(description='description')
parser.add_argument("option", dest="option", help="positional option help")
argcomplete.autocomplete(parser)
args = parser.parse_args()

A positional argument may not necessarily have "choices". So if there were no choices I would still have to create a subparser to autocomplete the positional argument. That, to me, is less intuitive. Following demonstrates how to autocomplete a positional argument that doesn't have "choices"
parser = argparse.ArgumentParser(description='description')
subparsers = parser.add_subparsers()
parser_option = subparsers.add_parser("option", help="positional option help")
argcomplete.autocomplete(parser)
args = parser.parse_args()

Your last example does have 'choices'. The only valid thing a user can type is literally option because that is the name of your subparser. This can be easily visualized by running the example and letting argparse do its job:
$ python test.py
usage: test.py [-h] {option} ...
test.py: error: too few arguments

$ python test.py foobar
usage: test.py [-h] {option} ...
test.py: error: invalid choice: 'foobar' (choose from 'option')

In general you can't expect argcomplete to complete stuff that it doesn't know the valid values for. In the first example the only valid value is ---option in the third it's option. But the positional argument in the second example will accept any user-supplied value and therefor can't be completed.

I would suggest an explicit mention for that in the doc.

@shehzadi, I think you're a bit confused about how argparse works. The rule of thumb for argcomplete is that it won't generate an invalid completion (one that causes the argparse parser to throw an error). If we were to complete anything on a positional that we don't have any choices information for, the completions would not be valid (to our best knowledge, anyway). There is nothing to complete on a positional with no completion information. However, once you declare a subparser, we do have the ability to complete on the subparser name.
The main thing you need to do is just look at the form of arguments that you supply to your program, and look at how you can inform argcomplete about what to suggest at any point in the command line.
Ultimately, what you might be looking for is out-of-band help information for completions: in other words, in addition to suggesting completions to your command line, the tab completion driver would also print - not into the command line! - help information for the option currently under the cursor. I know Zsh has this capability, but unfortunately I'm not aware of any way for bash to support it (though perhaps I could try printing to stderr).
If you have any specific wording for a warning that you want me to insert into the doc (including examples), please feel free to paste it here.

@felskrone, please let us know if the discussion (and examples with the "choices" parameters) above also answer your questions.

Yeah, this would be good if the positionals were autocompleted like

foocommand foosubcommand foosubsubcommand {positional_param_1} {positional_param_2}
</code
that seems ultimately reasonable

@gnydick The consensus from this discussion is that completion of subcommands works if your argument parser is built using subparsers. If you're not able to get this working the way you want, please open a new issue and include a code example.


feat: enable local proxy configuration in maven plugin configuration

Relates to Issue #5040
Description of Change
CICD-SEC-03 recommends:

... packages are pulled through an internal proxy rather than directly from the internet ...
... pull packages from internal repositories ...

We have solved (2), trust our developers, they trust the developers of the third party libraries in use, and those trust the developers of dependent fourth party libraries ...
Nevertheless, we would like to go one step further and completely disable access to the Internet in our CI/CD pipeline.
Therefore, we need to configure a proxy for the dependency-check-maven plugin.
Currently, you can define a proxy to use in the dependency-check-maven plugin via the Maven settings or the system property http.proxyHost.
However, in both cases, the configured proxy is used not only for loading data for analysis, but potentially for dependency resolution as well:

https://maven.apache.org/guides/mini/guide-proxies.html "... configure a proxy to use for some or all of your HTTP requests with Maven ..."
https://www.baeldung.com/maven-behind-proxy

With the proposed change, a local proxy can be configured for the dependency-check-maven plugin, which is then used exclusively for loading the analysis data:
<configuration>
	...
	<proxy>
		<host>myproxy</host>
		<port>1234</port>
	</proxy>
	...
</configuration>

Have test cases been added to cover the new functionality?
no

@jeremylong : is there anything else I can do here to get the PR accepted?

Sorry about the delay - thanks for the PR!


[gearswap-1.9.4-1.2.6] Empty slots still gets cleared.

When an inventory slot is set to be left alone, on swap it still gets cleared. Setting a slot to "Clear" works how it should.
No other mods installed.
Minecraft version: 1.9.4
Forge version: 1.9.4-<IP_ADDRESS>0
I hope this is the right repository, because the one from the Curse Page had a last commit in 2015 December.

Can you show a screenshot of your the gear swapper setup?

Sure. This is my setup:

And this is what I get after pressing any of the rectangles.


Cloud-save user data

Sync user's data to a remote database regularly so that they can carry over their data to another device. Depends on #12

Scrapped.


Conflict with react-infinite-scroller

I tried to use this boilerplate with react-infinite-scroller but this error popup

I think it has some problem with ES6 config but cannot trace where it is
If someone has found a way to resolve this problem. Can you post it here

See here to have babel transform individual packages in node_modules.

It works 👍  thank you a lots


Vastloadtimeout not work

I test this with case vast loadtimeout but it not fire the error, can you check it

Hello, can you please give me more information about your issue ?
Are you talking about vastLoadTimeout in adsRequestOptions ?

Yep, I use your config example, and set time for vastLoadTimeout in adsRequestOptions, then I try with low internet connect, ImaAdPlayer only fire ad_request then ad_end after timeout, not an ad_error I want

Yep, I use your config example, and set time for vastLoadTimeout in
adsRequestOptions, then I try with low internet connect, ImaAdPlayer only
fire ad_request then ad_end after timeout, not an ad_error I want
Vào Th 5, 23 thg 11, 2023 vào lúc 02:21 kslimani @.***>
đã viết:

Hello, can you please give me more information about your issue ?
Are you talking about vastLoadTimeout in adsRequestOptions ?
—
Reply to this email directly, view it on GitHub
https://github.com/kslimani/ima-ad-player/issues/36#issuecomment-1823372236,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXOQQC4LVAU2SMO4JX6TBYLYFZGDLAVCNFSM6AAAAAA7UFN7W2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRTGM3TEMRTGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

i have done some tests and it work as expected for me :
// [...]
ImaAdPlayer({
  // [...]
  adsRequestOptions: {
    vastLoadTimeout: 10000, // Set VAST XML load timeout to ten seconds
  },
}, function(player, error) {
  // [...]
  player.on('ad_error', function(o) {
    // Should be dispatched on XML VAST load timeout (ie: response took more than 10 seconds)
  });
});

Please note this timeout apply ONLY to the HTTP request which attempt to load the VAST XML ad response. It does NOT affect the video ad playback part. (refer to IMA documentation for more details)

I do a retest and it work perfectly now, many thanks for your help <3
Vào Th 7, 25 thg 11, 2023 vào lúc 17:09 kslimani @.***>
đã viết:

i have done some tests and it work as expected for me :
// [...]ImaAdPlayer({
// [...]
adsRequestOptions: {
vastLoadTimeout: 10000, // Set VAST XML load timeout to ten seconds
},}, function(player, error) {
// [...]
player.on('ad_error', function(o) {
// Should be dispatched on XML VAST load timeout (ie: response took more than 10 seconds)
});});
Please note this timeout apply ONLY to the HTTP request which attempt to
load the VAST XML ad response. It does NOT affect the video ad playback
part. (refer to IMA documentation for more details)
—
Reply to this email directly, view it on GitHub
https://github.com/kslimani/ima-ad-player/issues/36#issuecomment-1826271787,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXOQQCZRA77RSHNB4LFIBOTYGG7V5AVCNFSM6AAAAAA7UFN7W2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRWGI3TCNZYG4
.
You are receiving this because you authored the thread.Message ID:
@.***>


Add IBC rate limiting protection system

Summary
Add the Osmosis IBC rate limiting protection to the Provenance project
Problem Definition
The IBC Rate Limit module is responsible for adding a governance-configurable rate limit to IBC transfers. This is a safety control, intended to protect assets on osmosis in event of:

a bug/hack on osmosis
a bug/hack on the counter-party chain
a bug/hack in IBC itself

This is done in exchange for a potential (one-way) bridge liveness tradeoff, in periods of high deposits or withdrawals.
Proposal
Wire in the Osmosis IBC rate limiting system.  Ensure that the chain functions normally when the smart contract referenced is not available.  Prepare a smart contract implementation for subsequent governance inclusion into Provenance to configure these limits.

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

The stride team was inspired by Osmosis and created their own implementation. They do all their logic in their ratelimit module rather than passing it to a smart contract.
https://github.com/Stride-Labs/stride/tree/main/x/ratelimit

Also, Axelar has their own implementation https://github.com/axelarnetwork/axelar-core/tree/main/x/axelarnet

Very interesting. The smart contract version should be more mutable for responding to future configuration needs… but an in protocol version is likely more efficient.
@Taztingo have you done any testing on these approaches? What is your preference (if any) so far?

I haven't tested any of them yet, and just happened to stumble across them. The Osmosis one is listed as an official ibc-app, which is making me lean towards that solution. https://github.com/cosmos/ibc-apps#ecosystem-apps

Putting this in hold until we get a good solution. We will either have to manage our own module(s) that are a replica of the other solutions or wait until an existing solution can be imported.


Update mattermost extension

Description

I corrected the error that occurred when authorizing via login / password.
with such authorization, a temporary token is created and it can be invalidated some time later.
I added a 401 check and re-login to refresh the token
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Hi @Ernest0-Production 👋
Thanks for your contribution 💯
Could you look into this CI error here?

Hi! Planned to do this over the weekend

Awesome @Ernest0-Production

Awesome @Ernest0-Production

Hi! I fix all errors)


fix(BLE): ME18 PHY + PAL UART + clean.cordio

Description
ME18 PHY
The ME18 PHY was showing some issues in stability. This build is the most up to date and stable PHY we have.
PAL UART
PAL UART triggers an assertion by default anytime an error occurs. Now if it is in on the console or the HCI UART, the FIFO is flushed and we continue. Cordio has no mechanism to bubble the error back up, so if an error occurs on HCI, two errors will always occur unless extremely lucky.
The first error is the actual error from reported by the hardware. The second error is Cordio not being able to recreate an HCI packet since, the packet is incomplete as the previous partial segment is being added to the new segment.
After this error it starts over and goes back to normal.
The error always seems to be an overflow error. The best solution for this is to enable HW flow control.
clean.cordio
Fixed clean.cordio recipe in libCordio.mk. The MAXIM_PATH is not properly being passed down, so if you do not have the MAXIM_PATH set as an environment variable, clean.cordio does not work. CMSIS_PATH is set so I just used a relative path from that.

/clang-format-run

Not sure if disabling the terminal echo will help with our test automation. I can't tell if the tests now are failing because of the UART in general, the echo, or BLE disconnects.
diff --git a/Libraries/Cordio/wsf/sources/util/terminal.c b/Libraries/Cordio/wsf/sources/util/terminal.c
index 7d97f548ff..85a8e10ade 100644
--- a/Libraries/Cordio/wsf/sources/util/terminal.c
+++ b/Libraries/Cordio/wsf/sources/util/terminal.c
@@ -101,7 +101,7 @@ void TerminalInit(wsfHandlerId_t handlerId)
   terminalCb.handlerId     = handlerId;
   terminalCb.pFirstCommand = NULL;
   terminalCb.isExecuting   = FALSE;
-  terminalCb.doEcho        = TRUE;
+  terminalCb.doEcho        = FALSE;
   terminalCb.bufOffset     = 0;

   TerminalRegisterCommand(&terminalCommandHelp);

/clang-format-run

/clang-format-run


Unique Ingress Host sample policy will always validate/deny

The precondition requires any of two opposite checks which will always be true:
any:
  - key: "{{ request.object.spec.rules[].host }}"
    operator: In
    value: "{{ hosts }}"
  - key: "{{ request.object.spec.rules[].host }}"
    operator: NotIn
    value: "{{ hosts }}"

As we have a deny rule here, the second condition is the one to be removed.

@thorstenhuhn apologies for letting this drop off. Have been covered up at work.
The problem that I was attempting to solve with the latter any statement was when a single Ingress manifest was submitted that contained at least one colliding host. For example, if you started with the following hosts defined as Ingress resources
$ k get --raw /apis/networking.k8s.io/v1/ingresses | jp "items[].spec.rules[].host"
[
  "foo.bar.com",
  "www.foo.com"
]

and a user submitted the following manifest
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: ingress-wildcard-bad
spec:
  rules:
  - host: "www.github.com"
    http:
      paths:
      - pathType: Prefix
        path: "/git"
        backend:
          service:
            name: service11
            port:
              number: 80
  - host: "www.foo.com"
    http:
      paths:
      - pathType: Prefix
        path: "/asdf"
        backend:
          service:
            name: service22
            port:
              number: 80

without that second any statement the request would be allowed and it shouldn't be because www.foo.com is already present in the cluster. The error I made was in NOT testing a good resource defining a single host. Removing the defective second any statement will again re-open up the case where a multi-host Ingress containing a colliding entry is allowed.
I think the best way to fix this policy is to probably use a JMESPath expression with contains() but we need the fix in https://github.com/kyverno/kyverno/pull/2346 which should land in 1.4.3. I will try and model a fix using the latest upstream code in hopes of updating the policy for 1.4.3.

Now that 1.4.3 is out, the contains() issue has been solved, but I'm still not yet sure about the search capabilities. I have a question out to the community.

@chipzoller - can you please elaborate more on " the search capabilities"? Can we use context.APICall to fetch existing hosts?

I should have clarified. By "the search capabilities" I was referring to the abilities of the contains() function in the JMESPath library. After speaking with a member of the JMESPath community, it seems likely there isn't a way to compare a sourcearray of strings to a destination array of strings and return true if any of those in the source are found in the destination.
I was thinking I could solve this by creating separate Kyverno rules and using the NotIn operator, but I was thinking about it incorrectly. I think I've exhausted all possibilities at this point in modifying this rule to catch situations in which a single Ingress manifest is submitted with multiple hosts. I think what's needed here are two new operators: AnyIn and AllNotIn. Additionally, if these were to be implemented, the existing NotIn operator name would need to be changed to AnyNotIn to reflect its true behavior.
@realshuting, I'd like your confirmation on the above paragraph before I open a feature request to add these operators and potentially to modify the existing one.

Looks like we already have one for AnyIn and AllNotIn: https://github.com/kyverno/kyverno/issues/1837. Can you please link this issue to that one?

Doh. I specifically searched for this and turned up nothing. It even references this. I'll elaborate later.

Going to close this for now as a workaround has been pushed to the repo whereby only a single Ingress host is allowed in a given resource request.


Add GitHub Actions workflow for automated testing

This PR introduces a GitHub Actions workflow for automated testing, addressing part of Issue #32. The workflow is configured to run unit tests on pushes and pull requests to specified branches.

I tested the workflow on my own fork, and it functions as expected.

Out of curiosity, what are the includes for cstring and climits for?
Is there a way to run the actions on your fork to watch that the unit tests pass? I see a blue check mark next to the action, but I thought the check mark was suppose to be green when the action is "passing".

On my local machine, the compilation worked fine without explicitly including headers like cstring, even though we used functions like memcpy and constants from climits. However, GitHub Actions flagged errors, such as "memcpy is undefined," which you can see in this example run. Adding these headers resolved the issue in the CI environment.
As for the Actions status, it’s green on my fork, as shown here:

Thanks for this mirzaim! This was an issue that I was gonna keep on delaying, so I appreciate you picking it up. This is a big improvement to Gestalt!
Sorry for the delay, I had to leave for a bit. I also wanted to do a bit more research into how the GitHub actions worked to make sure I understood it.


collecter's thread blocked

pinpoint version:1.5.2
i found many collecter's theads is blocked.
thread stack(jvisualvm dump):
"Pinpoint-UDP-Stat-Io(20-5)" - Thread t@272
java.lang.Thread.State: BLOCKED
at java.net.DatagramSocket.receive(DatagramSocket.java:712)
- waiting to lock <1f0501a9> (a java.net.DatagramSocket) owned by "Pinpoint-UDP-Stat-Io(20-1)" t@268
at com.navercorp.pinpoint.collector.receiver.udp.UDPReceiver.read0(UDPReceiver.java:200)
at com.navercorp.pinpoint.collector.receiver.udp.UDPReceiver.receive(UDPReceiver.java:138)
at com.navercorp.pinpoint.collector.receiver.udp.UDPReceiver.access$300(UDPReceiver.java:47)
at com.navercorp.pinpoint.collector.receiver.udp.UDPReceiver$2.run(UDPReceiver.java:276)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Locked ownable synchronizers:
- locked <1cdf7251> (a java.util.concurrent.ThreadPoolExecutor$Worker)
"Pinpoint-UDP-Stat-Io(20-4)" - Thread t@271
java.lang.Thread.State: BLOCKED
at java.net.DatagramSocket.receive(DatagramSocket.java:712)
- waiting to lock <1f0501a9> (a java.net.DatagramSocket) owned by "Pinpoint-UDP-Stat-Io(20-1)" t@268
at com.navercorp.pinpoint.collector.receiver.udp.UDPReceiver.read0(UDPReceiver.java:200)
at com.navercorp.pinpoint.collector.receiver.udp.UDPReceiver.receive(UDPReceiver.java:138)
at com.navercorp.pinpoint.collector.receiver.udp.UDPReceiver.access$300(UDPReceiver.java:47)
at com.navercorp.pinpoint.collector.receiver.udp.UDPReceiver$2.run(UDPReceiver.java:276)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Locked ownable synchronizers:
- locked  (a java.util.concurrent.ThreadPoolExecutor$Worker)
"Pinpoint-UDP-Stat-Io(20-3)" - Thread t@270
java.lang.Thread.State: BLOCKED
at java.net.DatagramSocket.receive(DatagramSocket.java:712)
- waiting to lock <1f0501a9> (a java.net.DatagramSocket) owned by "Pinpoint-UDP-Stat-Io(20-1)" t@268
at com.navercorp.pinpoint.collector.receiver.udp.UDPReceiver.read0(UDPReceiver.java:200)
at com.navercorp.pinpoint.collector.receiver.udp.UDPReceiver.receive(UDPReceiver.java:138)
at com.navercorp.pinpoint.collector.receiver.udp.UDPReceiver.access$300(UDPReceiver.java:47)
at com.navercorp.pinpoint.collector.receiver.udp.UDPReceiver$2.run(UDPReceiver.java:276)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Locked ownable synchronizers:
- locked <771c2b0c> (a java.util.concurrent.ThreadPoolExecutor$Worker)
"Pinpoint-UDP-Stat-Io(20-2)" - Thread t@269
java.lang.Thread.State: BLOCKED
at java.net.DatagramSocket.receive(DatagramSocket.java:712)
- waiting to lock <1f0501a9> (a java.net.DatagramSocket) owned by "Pinpoint-UDP-Stat-Io(20-1)" t@268
at com.navercorp.pinpoint.collector.receiver.udp.UDPReceiver.read0(UDPReceiver.java:200)
at com.navercorp.pinpoint.collector.receiver.udp.UDPReceiver.receive(UDPReceiver.java:138)
at com.navercorp.pinpoint.collector.receiver.udp.UDPReceiver.access$300(UDPReceiver.java:47)
at com.navercorp.pinpoint.collector.receiver.udp.UDPReceiver$2.run(UDPReceiver.java:276)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Locked ownable synchronizers:
- locked <46df04d4> (a java.util.concurrent.ThreadPoolExecutor$Worker)
except this thread is running, all of the other "Pinpoint-UDP-Stat-Io" thread is blocked!!
"Pinpoint-UDP-Stat-Io(20-1)" - Thread t@268
java.lang.Thread.State: RUNNABLE
at java.net.PlainDatagramSocketImpl.receive0(Native Method)
- locked <7e828346> (a java.net.PlainDatagramSocketImpl)
at java.net.AbstractPlainDatagramSocketImpl.receive(AbstractPlainDatagramSocketImpl.java:145)
- locked <7e828346> (a java.net.PlainDatagramSocketImpl)
at java.net.DatagramSocket.receive(DatagramSocket.java:786)
- locked <57c37dc3> (a java.net.DatagramPacket)
- locked <1f0501a9> (a java.net.DatagramSocket)
at com.navercorp.pinpoint.collector.receiver.udp.UDPReceiver.read0(UDPReceiver.java:200)
at com.navercorp.pinpoint.collector.receiver.udp.UDPReceiver.receive(UDPReceiver.java:138)
at com.navercorp.pinpoint.collector.receiver.udp.UDPReceiver.access$300(UDPReceiver.java:47)
at com.navercorp.pinpoint.collector.receiver.udp.UDPReceiver$2.run(UDPReceiver.java:276)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Locked ownable synchronizers:
- locked <6700aa37> (a java.util.concurrent.ThreadPoolExecutor$Worker)

Hi wahaha001.
The conclusion first, This is normal situation.
Socket will continue to wait when there is no message(especially 'Pinpoint-UDP-Stat-Io' threads are receiving small messages).
In this case, other threads  are blocked state.
thanks.

OK。。。thanks  :)


You can deploy VPN gateway in Dual Stack VNET only using Azure PowerShell/CLI

Additional reference- https://learn.microsoft.com/en-us/answers/questions/1011462/index.html

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

ID: 08a5c04b-b0f3-fd22-68f4-b2f68ca9d7bb
Version Independent ID: 48de6009-8c23-ecc5-ef7a-730d9534de52
Content: Overview of IPv6 for Azure Virtual Network
Content Source: articles/virtual-network/ip-services/ipv6-overview.md
Service: virtual-network
GitHub Login: @asudbring
Microsoft Alias: allensu

Working on a PR.


Dev

Release 0.5.1:
Fixed compatibility with nodes 7 caused by missing String.padStart function.

Bug found by adding more nodes versions to travis config file


Add Doreen (Treasurer) back to the global leadership team

In #614 - We implemented a data model that has the officers listed.
Doreen Nangira (our treasurer) was not listed.
Please add her to the _data/leadership.yaml

Hey. If no one has been assigned to this, I could give it a go.


Mypy fixes

Continuation on #85 fixing

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

84 of 84 (100.0%)  changed or added relevant lines in 8 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 81.189%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
2322

Relevant Lines:
2860

💛  - Coveralls


Generate non-generic Response classes for output models

Any model that is an output model (either output-only or input-output) will end up having Response. Headers are somewhat problematic for this in the REST client, but the public surface (non-Rest client) can expose these classes just fine.

Has to be decided before we GA

Closing this for now.


Switch from Coverlet to Microsoft.CodeCoverage for better performance and less dependencies

https://devblogs.microsoft.com/dotnet/whats-new-in-our-code-coverage-tooling/

Not worth it, Microsoft.CodeCoverage bring too much hassle for a small performance benefit.


python3Packages.gudhi: 3.4.1 -> 3.8.0

Description of changes

This updates GUDHI to the latest version. Changes since 3.4.1:

3.5.0
3.6.0
3.7.0
3.7.1
3.8.0

Notably for me, 3.4.1 doesn't build on macOS 12.6.
Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 236864 run on x86_64-linux 1

4 packages built:

python310Packages.gudhi
python310Packages.gudhi.dist
python311Packages.gudhi
python311Packages.gudhi.dist


typo fix

resouces -> resources
on this page https://setuptools.pypa.io/en/latest/userguide/development_mode.html#limitations

Thabk you very much @wimglenn


Add personal configuration vision to the wiki

Add personal configuration vision to the wiki

Added quick vision to https://github.com/calestar/computer-manager/wiki/Vision


Updating webroots to have the same defaults

Caddy, NGINX and Apache2 should have the same default application paths. The public/ path suffix is now added in the dotenv file to be able to use Laradock for non-laravel projects as well. Also, updated the documentation.
This should fix issue #849.
Update: I can't spell today. Apologies for changing the title two times. 🔢

@winfried-van-loon Can you please address the (new) merge conflicts?  I will get this merged as soon as it is clean :-)


The Netherlight upgrade is not possible for weapons or armor covered by this mode.

Minecraft Version
1.20.x
Mod Loader Version
1.0.0
Mod Version
TieredZ 1.3.2
Describe the Issue
The Netherlight upgrade is not possible for weapons or armor covered by this mode.
latest.log

Do you use any other mods except the required ones?
No response

Try with only this mod. Can not reproduce this.


cap deploy:symlink doesn't work now

Yeah, after last issue ( https://github.com/flowdock/flowdock-api/issues/4 ) this was quite obvious :)
So i'm not sure where it should be handled normally. But in generally I would want that flowdock would never create errors in my capistrano excecutements. Especially it should never stop my deploying scripts. If I break my production server, i want to be able to use the commants as excected, then I don't really care if flow gets notified or not, I'm in a hurry...
It should just pass and log some errors etc.  In https://github.com/flowdock/flowdock-api/blob/master/lib/flowdock/capistrano.rb#L36  something like
unless defined?(current_branch)
   your code
else
   puts "Flowdock could not be informed, no branch set, debug or contact support"
end

Some trace:

    command finished in 738ms
    triggering after callbacks for `deploy:symlink'
  * executing `flowdock:notify_deploy_finished'
    triggering before callbacks for `flowdock:notify_deploy_finished'
  * executing `flowdock:set_flowdock_api'
    triggering before callbacks for `flowdock:set_flowdock_api'
/home/ohu/.rvm/gems/ree-1.8.7-2011.03/gems/capistrano-2.9.0/lib/capistrano/configuration/namespaces.rb:188:in `method_missing': undefined local variable or method `current_branch' for #<Capistrano::Configuration::Namespaces::Namespace:0x24fbe68> (NameError)

That's true, change from after deploy:restart to deploy:symlink made deployment process more brittle. Originally the idea was to suite both deploy and deploy:migrations tasks using the last common task. I changed the tasks to be run after both these, but we should do something to handle exceptions.


MQTT - "Connection failed, retrying" from "paho.mqtt.client" Logger.

Running Master sebirdman/hass_traeger V0.0.3 integration
Home Assistant 2021.4.3
OS 5.13
Added:
self.mqtt_client.on_log = on_log
to Traeger.py (get_mqtt_client)
And pointed the OnLog to:
def mqtt_log(self, client, userdata, level, buf):
      _LOGGER.info("MQTT Log Level: %s, MQTT Log BUF: %s", level, buf)
      _LOGGER.info(f"MQTT Logger Token Time Remaining:{self.token_remaining()} MQTT Time Remaining:{self.mqtt_url_remaining()}")

After Rebooting HomeAssistant everything works as expected and log displayed consistant connections via the x thread:

2021-08-29 12:47:37 INFO (Thread-7) [custom_components.traeger] MQTT Log Level: 16, MQTT Log BUF: Sending PINGREQ
2021-08-29 12:47:37 INFO (Thread-7) [custom_components.traeger] MQTT Logger Token Time Remaining:3174.30845785141 MQTT Time Remaining:3175.812364578247
2021-08-29 12:47:37 INFO (Thread-7) [custom_components.traeger] MQTT Log Level: 16, MQTT Log BUF: Received PINGRESP
2021-08-29 12:47:37 INFO (Thread-7) [custom_components.traeger] MQTT Logger Token Time Remaining:3174.2152893543243 MQTT Time Remaining:3175.7191982269287
2021-08-29 12:47:47 INFO (Thread-7) [custom_components.traeger] grill_message: message.topic = prod/thing/update/xxxxxxxxxxxxx, message.payload = b'{"thingName":"xxxxxxxxxxx","............................

Depending on how long self.mqtt_url_expires lasts, the self.mqtt_client.loop_forever() will stop responding after 82800 seconds (23 hours) after the expiration.

2021-08-30 12:41:25 INFO (Thread-7) [custom_components.traeger] MQTT Log Level: 16, MQTT Log BUF: Sending PINGREQ
2021-08-30 12:41:25 INFO (Thread-7) [custom_components.traeger] MQTT Logger Token Time Remaining:-72224.53583312035 MQTT Time Remaining:-82852.89551663399
2021-08-30 12:41:27 INFO (Thread-7) [custom_components.traeger] MQTT Log Level: 16, MQTT Log BUF: Connection failed, retrying
2021-08-30 12:41:27 INFO (Thread-7) [custom_components.traeger] MQTT Logger Token Time Remaining:-72226.03751516342 MQTT Time Remaining:-82854.39719057083

The Token will refresh if you send a self.send_command but there is currently nothing I see that will refresh the self.mqtt_url.
What I'd expect is that the self.mqtt_client.loop_forever() be disconnected via self.mqtt_client.disconnect() and then set self.mqtt_client = None then reinitiate the MQTT_client again. Ideally this would happen once the self.mqtt_url_remaining is negative.
With the added logger above, it is constantly scanning every minute or so and could initiate this MQTT Re-Init but a logger isn't really a good home for this type of code IMO. Can't put it in a self.grill_message either as there is possibility that wouldn't be called for over the expiration period either.
A simple Reboot will fix the above problem and Re-Init the MQTT_URL

Possibly the same as #5


problem when running the code

NameError: name 'img' is not defined

Codecov Report

Merging #85 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #85   +/-   ##
=======================================
  Coverage   82.15%   82.15%
=======================================
  Files           6        6
  Lines         409      409
  Branches       95       95
=======================================
  Hits          336      336
  Misses         51       51
  Partials       22       22

Continue to review full report at Codecov.

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


DVC data size query

Hi,
I have a query from data size perspective. If my input data is 100 GB. Considering dvc creates multiple version of this input data based on the modification, does it mean that i do need a very huge local disk space? Do we have any archive feature in dvc.
I am trying to integrate my pipeline with jenkins where I probably will be running dvc repro a lot.

Hi @rahulguptajss !
If you need all the previous versions of that file then yes, you will have to provide the huge amounts of storage. But if you don't need older versions, you could simply run dvc gc that will remove all the old unused versions and will only leave the currently used ones.

Thanks this will help. I can keep older versions in cloud.


Add logs to api removeVpnUser

Description
We verified that sometimes the command removeVpnUser fails, but we can't find the reason because there is no clear log message.
This PR intends to improve logging by adding the stack trace in case of fail of removeVpnUser command.
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] Enhancement (improves an existing feature and functioanlity)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[x] Minor

How Has This Been Tested?
It has been tested locally on a test lab, calling the api.

I am more interested the reason and the fix. do you have clue ?

I am more interested the reason and the fix. do you have clue ?

I agree with @weizhouapache , @GutoVeronezi . Did you implement this locally and did you find a root cause?

I agree with @weizhouapache , @GutoVeronezi . Did you implement this locally and did you find a root cause?

I have tested locally and couldn't found the root cause yet. Anyway, there is a lack of logs in this process.

I have tested locally and couldn't found the root cause yet. Anyway, there is a lack of logs in this process.

hope you can build locally because before this is in a release we are all a few months older ;)

hope you can build locally because before this is in a release we are all a few months older ;)

Guys, this is an interesting improvement in logging. Sadly, this has not been reproduced anymore. That is why we proposed an improvement for the logging here, to help others to better troubleshoot this if it ever happens with other people.

Is this a known issue? Can anyone else attest/reproduce it?
I am not a VPN user, the last time I have played with it was a long time ago. What I can say is that I agree with you all.
@DaanHoogland @weizhouapache I totally agree with the preference for looking into a fix.
However, on the other hand, it seems to be a corner case and the contributor had no conditions to catch a propper log neither to reproduce it. Improving logs seems logical to me as well as a very necessary first step.
It can be really tricky to debug/reproduce issues and sometimes we get into a limbo where we cannot properly debug nor monitor issues. Is this the case @rafaelweingartner @GutoVeronezi?

@DaanHoogland @GabrielBrascher @weizhouapache until now we did not reproduce the mentioned error; However, improve logging may help others to better troubleshoot this if it ever happens. Any update about this PR?

@DaanHoogland @GabrielBrascher @weizhouapache @sureshanaparti is there anything else to do?

Yes there are no tests
@blueorangutan package

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: centos7 :heavy_check_mark: centos8 :heavy_check_mark: debian.

@DaanHoogland @GabrielBrascher @weizhouapache @sureshanaparti @rhtyd is there anything else to do?

@blueorangutan package

@nvazquez a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: debian. SL-JID 652

@nvazquez a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian test result (tid-1376)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 33912 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr4616-t1376-kvm-centos7.zip
Smoke tests completed. 89 look OK, 0 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File


Creating a one to one video call Android app with Agora SDK using Kotlin

This fixes #4752

Plagiarism check done ✅

Hello @Ericgacoki
I have fixed the requested changes

jumping on this one

Overall very nice work 👍


v1.14 backports 2024-04-11

https://github.com/cilium/cilium/pull/31214

Once this PR is merged, a GitHub action will update the labels of these PRs:
 31214

/test-backport-v1.14

/test-backport-1.14


feat: Added parameter bring_to_front and bring_to_back to tile layer and tile layer wms component

I am not sure wether adding log as additional dependency fits your requirements, but I always find it very useful to add as much information as possible to the log for debugging purposes and bug findings.
But I am also happy to remove this dependency again if desired.

I don't mind the use of log crate, but prefer tracing crate (mostly do backend and mobile/desktop apps), which can add much more interesting information if some one wants. For simple logging, leptos already as that included. If you could switch to the leptos::logging::warn! which does the same thing, and avoids adding a extra crate.
Thank you for the PR.

Thanks for the hint! I updated the branch accordingly.

Thanks again for the PR @emirror-de.


[firebase_dynamic_links] Add support of expanding from short links

Description
Add support of expanding to full links from short links.
Related Issues
#1380
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] If the pull request affects only one plugin, the PR title starts with the name of the plugin in brackets (e.g. [cloud_firestore])
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[ ] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[ ] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[ ] I updated CHANGELOG.md to add a description of the change.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

Thanks for the update.
Please also update the pubspec.yaml file (increment version) and update CHANGELOG.


update_index for Elasticsearch throwing an error

Just installed and playing with Wagtail on my windows pc - looks and works great though pages not working out of the box as on mezzanine.
When trying to connect Elasticsearch and doing update_index command in console it throwing an error:
elasticsearch.exceptions.RequestError: TransportError(400, u'mapper_parsing_exception', u'Mapping definition for [title] has unsupported parameters: [index_analyzer : endengram_analyzer]')
I believe [title] here is page's title...

It looks like you're using Elasticsearch 2.x Wagtail currently only supports Elasticsearch 1.x.
Support for ES 2.x is coming soon though, see https://github.com/torchbox/wagtail/issues/1734 for progress.

Oh yeah it was the latest 2.3 now installed the 1.7 and it seems to work well. Thank you!


Code inconsistency issues

In generate_pyg_data.py
Line 10: from utils import knowledge_augmentation, compute_pca_with_whitening, bert_whitening
However, compute_pca_with_whitening, bert_whitening does not exist in utils.py
Thanks for your help!

Hi, these lines are not relevant to the topic discussed in the paper, so you can safely delete them. It's related to strategies shown in https://arxiv.org/abs/2103.15316.

Thanks for your quick reply.
I have some other questions:

How is cora_fixed_sbert(ada, google, …).pt generated? Is "data.raw_text" the original text attribute from cora or the text attribute after using LLM?
The know_inp(sep)_sb.pt file is missing in lmfinetune.py. How to generate them?
The implementation of Iterative structure seems not to be found in the project.

Best wishes!

these embeddings are generated by api provided by openai and google, you may find endpoints at api.py. Personally, I don't recommend re-generating them since they perform poorly considering the price. 'raw_text' is the original text attribute.
check generate_pyg_data.py
We follow https://github.com/AndyJZhao/GLEM and write data interface. Since the original codebase is too complicated, we don't integrate them there. If you need them, I can upload them later

Regarding "perform poorly considering the price", do you mean that only pre-training with abundant computing resources can achieve good performance? If so, how many resources are needed to ensure it?
In generate_pyg_data.py
Lines 180 and 189 "know_inp_ft" and "know_sep_ft" do not appear to explain how to obtain "_inp_finetune_XXX.emb". Am I missing something?
Please upload them, this is very helpful to me, thanks a lot.


Common module

It was really tedious duplicating updates across resource files for the Kotlin & Java projects, so I extracted the common resources & dependencies to a common module. If we don't want to do this, we can kill this PR.
(won't build on CI until https://github.com/GetStream/stream-chat-android/pull/1229 is merged and stream dependency is updated)

I'm not sure if we should do that - copying resources is annoying but I think that most of the users expect that tutorial is as easy and straightforward as possible (so they can open a project and copy everything from one module). We also had a common dependencies configuration for both modules but we get rid of it to simplify things.

I'm not sure if we should do that - copying resources is annoying but I think that most of the users expect that tutorial is as easy and straightforward as possible (so they can open a project and copy everything from one module). We also had a common dependencies configuration for both modules but we get rid of it to simplify things.

I'm not sure if we should do that - copying resources is annoying but I think that most of the users expect that tutorial is as easy and straightforward as possible (so they can open a project and copy everything from one module). We also had a common dependencies configuration for both modules but we get rid of it to simplify things.

That's fair - do we ever link to the tutorial github anywhere? I'm under the impression that this is a repository for us, and we use its contents to curate the tutorial since I can't find a link to this repo anywhere on the tutorial page.

I'm not sure if we should do that - copying resources is annoying but I think that most of the users expect that tutorial is as easy and straightforward as possible (so they can open a project and copy everything from one module). We also had a common dependencies configuration for both modules but we get rid of it to simplify things.

That's fair - do we ever link to the tutorial github anywhere? I'm under the impression that this is a repository for us, and we use its contents to curate the tutorial since I can't find a link to this repo anywhere on the tutorial page.

If we don't link it anywhere, it's time to add a link to the start and end of the tutorial so that people can check out a working project if they want to 😉

If we don't link it anywhere, it's time to add a link to the start and end of the tutorial so that people can check out a working project if they want to 😉

I thought it's linked 🙈  We should definitely add it

I thought it's linked 🙈  We should definitely add it


[FEATURE] Community page (separate page)

Detailed description
We have to build a community page.

A little bit about community
Discord link
Twitter about our community

Context
The community page will help user to know more about the community
and will be able to join the community through the community page.
Possible implementation
Example page:

Additional information
If you need any help or have any doubts, can ask below.
Thanks
sourcecode: https://github.com/thecyberworld/thecyberhub.org
Code of Conduct

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

@kabir0x23 I'd like to go for this task
Also, I want to know what things I need to write about the community on this page.

@kabir0x23 I'd like to go for this task Also, I want to know what things I need to write about the community on this page.

Nice.
instead of hacker you can write, developers
cyber security -> web3


fix: CI not running cargo test --doc

Codecov Report
Base: 62.07% // Head: 62.17% // Increases project coverage by +0.09% :tada:

Coverage data is based on head (d47fcfd) compared to base (22fe0d5).
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1753      +/-   ##
==========================================
+ Coverage   62.07%   62.17%   +0.09%
==========================================
  Files         130      130
  Lines       25063    25126      +63
==========================================
+ Hits        15558    15622      +64
+ Misses       9505     9504       -1

Impacted Files
Coverage Δ

fedimint-core/src/task.rs
61.71% <ø> (ø)

fedimintd/src/fedimintd.rs
0.00% <ø> (ø)

fedimint-server/src/multiplexed.rs
88.75% <0.00%> (-2.50%)
:arrow_down:

fedimint-core/src/core.rs
93.18% <0.00%> (-0.25%)
:arrow_down:

fedimint-server/src/net/connect.rs
94.40% <0.00%> (-0.25%)
:arrow_down:

fedimint-server/src/net/peers.rs
89.42% <0.00%> (ø)

fedimint-server/src/consensus/mod.rs
80.95% <0.00%> (ø)

modules/fedimint-mint/src/lib.rs
77.95% <0.00%> (+0.11%)
:arrow_up:

crypto/tbs/src/poly.rs
24.43% <0.00%> (+0.20%)
:arrow_up:

modules/fedimint-wallet/src/lib.rs
78.64% <0.00%> (+1.31%)
:arrow_up:

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

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


Request: Trigger output option instead of gates

Would there be a way to be able to output triggers instead of gates (as an option) as 12.5% of gate length is still too long for some of my envelopes/drum modules?

I guess a trigger mode would be a reasonable thing to add. Will have to think about where to add it.

Ok thanks

On 6 Jun 2020, at 21:14, Simon Kallweit<EMAIL_ADDRESS>wrote:
I guess a trigger mode would be a reasonable thing to add. Will have to think about where to add it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/westlicht/performer/issues/200#issuecomment-640112685, or unsubscribe https://github.com/notifications/unsubscribe-auth/APKKXSTOS7T2CTXA7YVAMV3RVKPTZANCNFSM4NRXWGOA.

Would it be possible to sync Pocket Operators via this? (2 PPQ, max 5 VPP)

@HammyHavoc that should already be possible to setup using the main clock output. You can freely choose the divisor and the clock output is 5VPP (0..5V)


PowerShell 7 has removed the alias and an error occurs when running the ni command

The fault is rectified and the node version is faulty. You need to update the node version 16 or later


Tree-sitter "execute current form" / get-form not always working correctly

For example in Fennel with (foo.bar :baz) and cursor over bar, -ee returns #<function: 0xdeadbeef> because it only evaluates the foo.bar.
tree-sitter-fennel got an upgrade recently and foo.bar is parsed as multi_symbol which does have child elements, so conjure.tree-sitter.get-form stops its walk up the tree there.
For Fennel, the "(" and ")" anonymous nodes are also parsed so the node can be queried with (_ . "(" ")" .) @foo, but I have no idea if the same goes for the other supported languages.
Instead of a query, maybe the tree could be walked up and check that the first and last children are the parenthesis. But yet again the language's treesitter has to support those anonymous nodes...
Here's something I came up with when fooling around with Treesitter and Fennel:
(module treesitter-foo
 {require {a aniseed.core
           tsu nvim-treesitter.ts_utils
           tsq vim.treesitter.query
           queries nvim-treesitter.query}})

(tsq.set_query "fennel" "foo" "(_ . \"(\" \")\" .) @foo"))

(defn get-form-node [node]
  (let [matches (queries.get_capture_matches bufnr "@foo" "foo" node)]
    (if (a.empty? matches)
      (get-form-node (node:parent))
      node)))

Generally I've been treating tree-sitter as something I walk up until I find the appropriate level so far. There may be better ways using queries like you've shown though, I just haven't looked into them yet. Thanks for the detailed report, I'll try to have a look very soon unless someone beats me to it 😄 I need to get the develop changes released ASAP, so many unreleased commits and improvements.

Well, it seems that at the moment Clojure is the only other supported language that has tree-sitter available. And it also has the parenthesis as first and last anonymous nodes! \o/

(defn- get-form-node [node]
  (when node
    (let [first-child (node:child 0)]
      (if (and
            first-child
            (= (first-child:type) "("))
        node
        (get-form-node (node:parent))))))

Fixed in the latest release!


Use consistent proto file naming convention

@rstento commented on Thu Jul 08 2021
@mckeeh3 commented on Mon Jun 07 2021
In the Writing gRPC descriptors section of the docs, the proto file naming convention is inconsistent with other parts of the documentation.
Use "API" and "domain" suffixes for proto file names. Also, use dash versus underscore in file names.
Examples

shopping-cart-api.proto
shopping-cart-domain.proto

According to the style guide https://developers.google.com/protocol-buffers/docs/style:

Files should be named lower_snake_case.proto

I confirmed that this has been fixed in the doc, probably as part of another PR.


Add irc-dcc

I opened this pull request to early as Travis picked up version 1.2.0 instead of the recently uploaded 1.2.1.
What's the best way to trigger a rerun of Travis?

You can either:

close and re-open the PR
ask and someone with permission will do it
I started a rerun

Closed and reopened to trigger rebuild.
Both packages do not transitively depend on pipes, so I'm not sure why Travis complained about
pipes-4.2.0 (Gabriel Gonzalez<EMAIL_ADDRESS>is out of bounds for:
- [ ] pipes-attoparsec-<IP_ADDRESS> (==4.1.*). Renzo Carbonara<EMAIL_ADDRESS>@k0001. @k0001
- [ ] pipes-bgzf-<IP_ADDRESS> (==4.1.*). No maintainer. @rcallahan
- [ ] pipes-concurrency-2.0.5 (>=4.0.0 && < 4.2). Gabriel Gonzalez<EMAIL_ADDRESS>@Gabriel439
- [ ] pipes-parse-3.0.6 (==4.1.*). Gabriel Gonzalez<EMAIL_ADDRESS>@Gabriel439


Collapse all fluctuating pattern variations into a single row

Near the beginning of the week they add a lot of noise to the table. I think most people would get more useful information from a single row than from screens full of possible variations at minute probabilities.
Here are some exceptions where it may still be worthwhile listing all the variations:

If the user has opted-in to seeing them through some UI element.
If every other pattern is ruled out.
If there would be few (<12?) rows in the table anyway.
If a price near the end of the week has been entered. (With limited opportunities left to sell it could be useful to provide more information to the user.)

I suppose the ideal implementation would be to have every pattern type expandable/collapsible dynamically, with the fluctuating pattern collapsed by default.

I can definitely understand the value in removing clutter from the UI, but this proposal, at least as it's documented, seems like it would introduce quite a bit of complexity to both the app code and the user experience.
There may be a way to refine the proposal and make it simpler overall. Perhaps a single toggle that can hide predictions below a preset probability, as opposed to collapsing specific patterns.
We already see a substantial number of issue reports from users unable to find matching patterns where the reason can be attributed to confusion around how to use the app. We have work to do already to simplify things, so I am hesitant to add functionality that adds complexity.
#my2cents

Thank you for your reply! I understand the concerns about complexity. Allow me to present the simplest version of this request:

The fluctuating pattern variations are aggregated on to one row. Individual variations are hidden and there is no option to display them.

Considering there is already an "All patterns" row in the table which aggregates every variation of every pattern it doesn't seem like it would take much additional code to do the same but only for the variations of a single pattern.
I added the caveats to the issue originally because I anticipated someone being unhappy that information would be hidden and I wanted to account for that. Personally I don't need or particularly care about any of those things.
Just to explain my reason for this proposal - I want to recommend this price tracker to my friends because, out of the various options available, this one seems the best at providing accurate probabilities of being on each pattern. However I am reluctant to do so because I expect them to see this and wonder WTF they are looking at:

The problem with hiding those rows is we don't have a way of knowing which predictions are valid... You are seeing that many because at that moment every one of them is potentially valid. As you add more data, the ones that no longer work are automatically removed.
There are already a number of features meant to help summarize the information for people who only care about the basic stuff.
We have the visual graph above the table as the simplest view. The we have the aggregate probability, so that you can make a decision on what is most likely to be a real result.
And for those, such as myself, who want the granular view, we have the individual prediction probability.
All that is to say, after adding just 2 periods worth of data, the list is short and easy to digest.

I realise the table will usually be reduced to a manageable size fairly early in the week, though with certain values it will still be quite bloated on Monday afternoon (or even later with the fudge factor in effect).
I do think there are some users who would like to check the site on Monday mornings and at that point the table often isn't very readable. The aggregate probabilities of each pattern are probably the most important bits of information on the table at that stage of the week. If those were broken out to a more prominent location that would certainly help, in lieu of making changes to the table itself.

We talked about putting the aggregate probabilities into a pie chart. At this point it's a matter of finding a good location for it.
Perhaps that will help with streamlining the summary a bit better.

Hmm, yeah a pie chart sounds good! :)

@mikebryant do you have any thoughts on optionally hiding low probability rows?
I'm thinking something simple such as the following might be a decent compromise.

A toggle switch to hide rows below some predefined probability.
Default behavior shows all rows.
While enablee, show a message at the bottom of the table indicating some rows are hidden.

The risk here I think is that probabilities can swing pretty dramatically as more sell prices are provided. This could lead to patterns which were previously hidden popping up seemingly out of nowhere because they were previously below the "show" threshold.

That would be a reasonable thing. If it's opt-in that makes it more acceptable to me. I really like the table being the detailed view.
A more complicated alternative that would be to have the whole table be a tree structure, where you can expand first the patterns etc, and if not expanded they present the aggregate for that subset. Not sure if that's worth the complexity.
I'm open to making the aggregated probabilities more prominent

I've summarized the proposal into a new issue in #192 to refocus the discussion. Going to close this for now. Thank you @doopl for the suggestion!


[Bug]: Could not pass event PlayerTeleportEvent to Multiverse-Core v4.3.12

/mv version -p output
https://paste.gg/p/anonymous/8ff149fd62f54269b14bf6c5ef0be4c2
Server logs
https://paste.gg/p/anonymous/e6f7b57204b44180a8dbd3b74c850aaa
Server Version
Checking version, please wait...
This server is running Paper version 1.21-119-master@100d75a (2024-07-29T16:00:13Z) (Implementing API version 1.21-R0.1-SNAPSHOT)
You are running the latest version
Previous version: 1.21-113-f82bea6 (MC: 1.21)

Bug Description
Error occurs when players teleport.
Steps to reproduce
See Bug Description
Agreements

[X] I have searched for and ensured there isn't already an open or resolved issue(s) regarding this.
[X] I was able to reproduce my issue on a freshly setup and up-to-date server with the latest version of Multiverse plugins with no other plugins and with no kinds of other server or client mods.

Would need to see more of the logs, and not just a snippet. What command/method is used to change worlds? Does it happen with everyone, or just certain players? Also might be a good idea to change to Paper....https://papermc.io/software/paper

As you can already see, I use Paper. Therefore, this is no longer necessary. In addition, only one command was entered to change the world. /mvtp . Nothing more.
The error occurs regardless of which player enters the command.

We'll need more detailed reproduction instructions than that. Just using /mvtp world_2 perfectly fine for me in 1.21 paper with only MV plugins installed. Ensure your instructions are clear and tested.

The PaperMC github has an open issue for this bug too (however it seems they think the plugins need to be updated):
https://github.com/PaperMC/Paper/issues/11137
I've run into the same issue myself when I have PaperMC 1.21 with both Multiverse and Worldguard.
Just PaperMC + Multiverse has no issues for me. It's when I have WorldGuard installed too that I get non-stop NPE's. PaperMC + WorldGuard and no Multiverse has no issues. As someone mentioned in the PaperMC issue, there might be some sort of issue with the combination of the three.


Prepare certificate for use with VM: keyvault name and resource group are required for az vm secret format

In "Prepare certificate for use with VM" section:
For az vm secret format --secret "$secret" --output json to work, keyvault name and resource group (or keyvault ID, which isn't intuitive, even without resource group) must be added. Otherwise, it'll end up with something like: "ERROR: unable to find vault 'yourVault' in current subscription."
Full command should be: vm_secret=$(az vm secret format -s "$secret" --resource-group <YourResourceGroupName> --keyvault $keyvault_name --output json)

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

ID: 0d3da20d-57c3-1dcf-ada6-e9ded556e028
Version Independent ID: bc6f80e2-38c9-aafe-cbe9-2eaf94117474
Content: Tutorial - Customize a Linux VM with cloud-init in Azure - Azure Virtual Machines
Content Source: articles/virtual-machines/linux/tutorial-automate-vm-deployment.md
Service: virtual-machines
GitHub Login: @cynthn
Microsoft Alias: cynthn

@moshem-pangea - Thanks again for bringing this to our attention. We have updated the Doc and it will be live once its merged.  We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


New version: ViGEm.HidHide version 1.4.181

Description

Resolve https://github.com/microsoft/winget-pkgs/issues/124286

Checks

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Hey, @Dragon1573 please update to latest version and remove this version, it got nuked.

Hey, @Dragon1573 please update to latest version and remove this version, it got nuked.

Could you please open a new [Update Request] issue and mention me? I'm glad to help.


Update syntax highlighting theme in docs

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/3496
Originally created by @afolson on 2022-05-17 00:50:43

The current syntax highlighter theme doesn't fit the brand guidelines and looks a little out of place. It would be nice to update this to match the rest of the site at some point.

Sorted with our upcoming move to docusaurus.


Landing page viewport

Here I am again to talk about sizes hahahaha

Decrease the viewport a little bit :dancers:

Thanks one more time Matheus kkkk, I corrected the sizes, it's working perfectly


Add small improvements in catalog chart

Description
Add small improvements in catalog chart:

better support for update strategy

by switching type from NodePort to ClusterIP we get such error:
UPGRADE FAILED
Error: Service "test-svc" is invalid: spec.ports[0].nodePort: Forbidden: may not be used when `type` is 'ClusterIP'
Error: UPGRADE FAILED: Service "test-svc" is invalid: spec.ports[0].nodePort: Forbidden: may not be used when `type` is 'ClusterIP'

to fix that problem we just need to set the nodePort to null when using ClusterIP type

use the ClusterIP for webhook Service, as a default one (using NodePort is not a good approach in the released chart) ( we already using that for controller manager so we make that consistent)

/test pull-service-catalog-test-integration

/test pull-service-catalog-test-integration

/test pull-service-catalog-test-integration

/retest

/retest

/reopen

/test pull-service-catalog-test-integration

/lgtm

/approve


Get Parsl/Swift-T running on BW

Run Parsl with Swift/T on Bluewaters with swift-T driving compute tasks and visualization on a GPU cluster.
The Swift/T Python interface has not been tested recently and needs some rework and testing.

👋 @kylechard - Can we close this now?


govendor fetch github.com/go-redis/redis/v7 get empty folder

hi, i'm trying to connect redis using go-redis, but I dont know where the ctx come from, most instructions to use go-redis didn't mention this parameter, when I'm trying to use a older version v7, with a command "govendor fetch github.com/go-redis/redis/v7", i just got an empty folder. I'm wondering do you still support v7 edition, or am I doing something wrong?any help would be appreciate.

As govendor recommends - you have to use go modules - https://github.com/golang/go/wiki/Modules#how-do-i-use-vendoring-with-modules-is-vendoring-going-away


Update Explorer link on Sandbox page

Thanks @robbibt . I missed that cross ref.

All good, am just tidying up a few things!


Truncated Stack Trace

When I run tests through the web-based runner, Mocha will take a stack trace like this:
Uncaught Error: expected undefined to equal 'base:Sample' expect.js:99
Assertion.assert expect.js:99
Assertion.be.Assertion.equal expect.js:200
Assertion.(anonymous function) expect.js:73
(anonymous function) ConstraintSelectorTests.js:88
jQuery.event.dispatch jquery.js:3332
elemData.handle.eventHandle jquery.js:2941
jQuery.event.trigger jquery.js:3210
jQuery.fn.extend.triggerHandler jquery.js:3874
func.apply.$.extend.__callback jquery.jstree.js:237
$.jstree.plugin._fn.loaded jquery.jstree.js:539
$.jstree._fn.(anonymous function) jquery.jstree.js:234
(anonymous function) jquery.jstree.js:410
(anonymous function) jquery.jstree.js:1653
$.jstree.plugin._fn.load_node_json jquery.jstree.js:1724
$.jstree._fn.(anonymous function) jquery.jstree.js:234
$.jstree.plugin._fn.load_node jquery.jstree.js:1653
$.jstree._fn.(anonymous function) jquery.jstree.js:234
$.jstree._fn.(anonymous function) jquery.jstree.js:234
$.jstree.plugin._fn.init jquery.jstree.js:410
$.jstree._fn.(anonymous function) jquery.jstree.js:234
(anonymous function) jquery.jstree.js:162

and reduce it to:
Error: Uncaught Error: expected undefined to equal 'base:Sample' (file:///home/jeremy/workspace/syapse/src/syapse/static/js/ext/expect.js:99)
at window.onerror (file:///home/jeremy/workspace/syapse/src/syapse/static/js/ext/mocha/mocha.js:5286:10)

Is this just an inherent limit of the fact that Mocha uses onerror to catch exceptions, or is there any way that Mocha could display the real stack trace instead?   Because while I can get the real trace from the console, having it in the browser window would be awfully convenient.

@andrew-luhring @keyvanfatehi Shorter stack traces were added in https://github.com/mochajs/mocha/pull/1564 :)

So the only problem left here is being able to log a stack in browser that don't have a stack on their errors. (?)

I think this is no longer an issue, @dasilvacontin. Please correct me if I'm wrong.

I still have this problem. If I'm understanding the article linked in #958 correctly, it looks like the latest version of mocha (2.3.3) does not use the fifth argument of onerror. Incidentally, if I change it like so:
    global.onerror = function(err, url, line, col, errobj){
      fn(errobj || new Error(err + ' (' + url + ':' + line + ')'));
      return !mocha.allowUncaught;
    };

I get a full stack trace from Chrome, but not phantomjs. I'm not sure if it has something to do with the version of phantomjs or node I'm using? Or maybe I have something misconfigured? At any rate, here's a slightly less elegant solution that works:
/**
 * Report full stack trace on async callback error
 *
 * Wrap async callback functions with this function
 * to report the full stack trace if they fail.
 *
 * Usage:
 *
 *  it("will always fail", function (done) {
 *      someAsyncFunction(asyncatch(function (arg) {
 *          doSomethingThatThrowsAnError();
 *          done();
 *      }));
 *  });
 */
function asyncatch(fn) {
    return function () {
        try {
            var args = Array.prototype.slice.call(arguments);
            return fn.apply(this, args);
        } catch (err) {
            throw err && err.stack ? new Error(err.stack) : err;
        }
    };
}

I've opened #2403 to address the previous comment. Maybe discussion on this should continue in issue #958 as that one is specific to async errors.


Default file extension for new files when saving without one

For new, plain text files, it is sometimes convenient to not have to type ".txt" as the filename extension when saving. Many editors, such as Atom and Sublime, already support having a default extension when none is supplied at save-time.

Unfortunately, setting "files.defaultLanguage": "txt" did not save my new file with .txt extension.


Nuxt 3 default is not a constructor

Describe the bug
Related to https://github.com/BetterTyped/hyper-fetch/issues/37
I still getting default is not a constructor. Example here https://stackblitz.com/edit/hyperfetch-nuxt-demo?file=pages%2Findex.vue
Updated the hyper-fetch to 3.3.0
Any idea ?
Any help would be much appreciated. Thank you.
To Reproduce
Steps to reproduce the behavior:

Go to hyperfetch-nuxt-demo
See error on the preview

Expected behavior
No error should happen.
Screenshots
see hyperfetch-nuxt-demo
Desktop (please complete the following information):
N/A
Smartphone (please complete the following information):
N/A
Additional context
N/A

@johngerome Found the issue! I see that Nuxt is not providing "events" node module. When I added it as dependency like: `'events': '3.3.0' it worked. I will add it as dependency for such cases. You can try it out by adding it there, I will deploy fix today or tomorrow with this dependency.
Thanks for the support!

@prc5  It worked as well on my end 🥳. Thank you so much.

@johngerome Update is out 👍🏻 I'm looking forward to some feedback! 😄 If you have any ideas for improvements for better implementation with Vue/Nuxt let me know. Thanks!