Dependencies from a fresh conda environment

Hi! Thanks for the amazing dataset, paper, and baseline. I just had a couple of dependency issues when installing it on a fresh conda environment (CUDA Linux machine with Slurm) and wanted to post what worked for me (simply pip install -r requirements.txt did not work because the GPU wasn't found by Keras-TF):
Create the environment and explicitly install GPU-enabled libraries:
conda create --name dcase21_t2 python=3.6
conda install numpy==1.18.1
conda install tensorflow-gpu==1.15.0
conda install -c anaconda keras-gpu==2.3.1

Then run pip install -r requirements_lite.txt with the following contents:
Keras-Applications==1.0.8
Keras-Preprocessing==1.0.5
matplotlib==3.0.3
scikit-learn==0.22.2.post1
numba==0.48
librosa==0.6.0
audioread==2.1.5
tqdm==4.43.0

Note the added numba dependency (needed by librosa, needs to be below 0.49). This was inspired by 2020 Task1 readme which has different instructions for pip and conda (similar issue as above).
Cheers!
Andres

Closing unless someone has something to add


List Multi-Line wrong presentation ?

i do not get a correct presentation of my multi-line list.
here my code and a screen picture.
Any ideas ?
`<template>
  <quasar-layout>

Primary

            assignment_ind

Icon as Primary

            mail

Avatar as Primary

test 2nd

            assignment_ind

Thumbnail as Primary

Q

One character as Primary

</quasar-layout>
</template>`

You're using one-line items there. Any particular CSS breaking Quasar's one?

Couple of things to fix on your template:

Remove 'has-secondary' from all your items. You don't have secondaries.

Add 'two-lines' class to the following two-lines item:

            mail

Avatar as Primary

test 2nd

And make your you don't have any CSS in your app interfering with Quasar's one regarding lists and items. Please reopen if problem persists. Thanks!

Also, are you using v0.7 or v0.6. I have a hunch you're on v0.6. Lists have been completely redesigned in v0.7.

Thanks for your help. Everything is working now.
I figured out that my old npm didn't updated quasar-framework.
Updated npm and quasar. Everything fine.
Great Work !
brgds pici

Great! Glad I could help.


Adding cupti library and header files to IREE. Implementation of dynamic_cupti_test for library.

Integration of CUPTI library into IREE for collecting CUDA runtime trace information.
This cl adds a subset of the NVidia CUPTI header libraries to the build by looking them up from the system CUPTI and CUDA include folders. CUDA and the CUPTI library must be installed to build tracing for the cuda backend. Dynamic library loading of CUDA is enabled with IREE_TRACING_FEATURES.
dynamic_cupti_tests.cc tests the CUPTI api on an capable machine if the CUPTI libraries are successfully loaded.
All CUPTI related code is guarded with defines to prevent building unless IREE_TRACING_FEATURES and the CUDA backend are enabled. Bazel builds aren't supported for tracing.
Followup changes:

CUDA tracing implementation

There's also #8374 for some reason. Closing this older one.


Bad looking of correct answer and wrong answer alert

In dark mode the correct answer and the wrong answer alerts look bad, because they are to light. Maybe why can also add a little icon to make the alert fancier in general.

The issues in the Flutter Rewrite version of the app, look better than the old from the only android version. So this issue is solved.


We need Chinese, can you come up with a Chinese language?

Is your feature request related to a problem? Please describe.
My friends are not very good at English, I want to share this extension program with them, but they will be confused when they see the English interface, so please translate into Chinese.
Describe the solution you'd like
translate .
Describe alternatives you've considered
no.

Hi @luosaidage ,
we would be very happy to add a new language to our project. But we dont have knowledge of same. If you could help here it would be great help. all our languages are here in below repo. You can create a copy of english and translate same in chinese.
https://github.com/Dhruv-Techapps/acf-i18n/tree/main/locales

Hello, I have finished the translation work and submitted a pull request.

@luosaidage  - we have deployed changes on DEV env you can check on https://dev.getautoclicker.com

Ok,very nice!


Add quickstart steps for installation via POM file dependency

The docs only include steps to build the library locally, but not on how to download it from Maven Central via a POM file dependency. From what I can tell, this set of packages is the correct one, but I'm hesitant to import it until official documentation confirms that it is legitimate.
In particular, I'd like to verify the authenticity of this package.

@jpblair Since Java is still in preview, the samples are setup using the same package version as the libraries, which means it only works if you do a "mvn install", then build your sample.
If you want to modify the POM for a sample to use a released packages from Maven, then "4.6.0-preview7" is the version you'd need.
When Java is GA in mid-May, this won't be the case as the Samples will be relocated to the botframework-sample GitHub repo with the other samples, and build against released packages on Maven.

@jpblair Please note that using the released packages on Maven won't work for every sample though.  For example, any sample that uses the bot-dialogs package requires 4.6.0-preview8, which is what is in the main branch (not released on Maven yet).

@tracyboehrer Thanks for the reply. To be clear, I'm not looking to run the samples. I just want to use the Maven-released version of the packages (with the understanding that they are not GA yet), so I was looking to confirm that the link I provided in my original post is legitimate and from Microsoft.


Make grid overview link use correct filename

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


linux service changes using nodejs

This is only the service side code changes. Its not integrated with agent command line yet.
Next PR would contain Agent.Listener changes to hook this service into systemd.

OK - looks good enough for now.  I may have more thoughts after I consume the changes and start running.


Update README.md

This pull request introduces several improvements to the DevDocsHub documentation, aiming to enhance user experience and clarity:
Key Changes:
Enhanced Introduction: A more compelling introduction highlights the benefits of using DevDocsHub and its value proposition.
Improved Readability: The documentation employs clearer language and a more user-friendly structure, making it easier to understand and navigate.
Detailed Installation Instructions: The installation instructions are now more comprehensive, providing step-by-step guidance for different operating systems.
Emphasis on Community Contributions: The documentation explicitly encourages community involvement and outlines the steps for contributing to the project.
I'm submitting this pull request as part of the Girls Script Summer of Code program. I believe these enhancements align with the goals of the program and contribute to the overall improvement of DevDocsHub.
Request:
I kindly request that this pull request be accepted and the "GSSOC" label be added to acknowledge my participation in the program.
Thank you for your time and consideration!

Thank you for your contribution! A couple of issues I noticed:

The installation process seems incorrect, specifically in the step regarding activating the environment on Linux/macOS. Please review and correct this section.
There is no requirements.txt file included to install the necessary dependencies. So, please remove or change the way of installing the dependencies.
Please remove the last line, "I hope this improved documentation serves you well!"
Once these changes are addressed, the documentation will be more consistent and clear. Please request for a review after these changes are done.

Thank you for merging, @andoriyaprashant !


fix regex test

Signed-off-by: Joshua Fernandes<EMAIL_ADDRESS>

this looks ok but why is the test failing?

I got no idea :( its very consistent though ..


bazel: Fix rules_go release date

Signed-off-by: Ryan Northey<EMAIL_ADDRESS>Commit Message: bazel: Fix rules_go release date
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Deprecated:]
[Optional API Considerations:]

cc @mattklein123 @ggreenway @moderation


Make the repo URL on the frontpage point to RTD

I experimentally discovered that https://pep517.rtfd.io exists but there's no pointer to that place in docs so it'd be great if somebody could fix that.
cc @takluyver @pradyunsg

Thanks, good idea. I've put it in the repo info.


Fix package pattern in json schema configuration registry

Fix microsoft/vcpkg/issues/39259 for package pattern with an optional trailing *.
Change

Add definitions/reserved-name for reuse

Vcpkg reserved name by ^core|default$
Win32 filesystem reserved name by a loose pattern ^(con|prn|aux|nul|com[0-9]|lpt[0-9])(\\.[^.]+)*$, which include COM0 and LPT0. See documents

Add definitions/package-pattern to fix optional trailing *

Pattern of ^[a-z0-9]+(-[a-z0-9]+)*(-?\*)*$ to match ‘boost*’ and ‘boost-*’

Replace definitions/port-name with definitions/identifier

Pattern of port-name matches 'dot-separated identifier'. No relevant documents found, remove this definition.
Pattern of identifier matches 'lowercase with digits and dashes'

Append # to $schema

https://github.com/PowerShell/PowerShell/issues/20743#issuecomment-1821384204

Test
Schema files test pass with following cases:

true for {"registries":[{"kind":"git","repository":"","baseline":"0000000000000000000000000000000000000000","packages":["a"]}]}
true for {"registries":[{"kind":"git","repository":"","baseline":"0000000000000000000000000000000000000000","packages":["a*"]}]}
true for {"registries":[{"kind":"git","repository":"","baseline":"0000000000000000000000000000000000000000","packages":["a*","b"]}]}
false for {"registries":[{"kind":"git","repository":"","baseline":"0000000000000000000000000000000000000000","packages":["a*b"]}]}

Format failures fixed in https://github.com/microsoft/vcpkg-tool/pull/1433

Test script:
$TempWorkDir = (New-Item -ItemType Directory Temp:/$(New-Guid)).FullName
# Write-Host $TempWorkDir
$VcpkgToolDir = $PSScriptRoot

$VcpkgJsonSchema = @{
    Artifact      = 'artifact.schema.json'
    Configuration = 'vcpkg-configuration.schema.json'
    Definitions   = 'vcpkg-schema-definitions.schema.json'
    Port          = 'vcpkg.schema.json'
}

# remove `$id` in schema for error 'Test-Json: Cannot parse the JSON schema.'
$VcpkgJsonSchema.Values
| ForEach-Object {
    Copy-Item -Path (Join-path $VcpkgToolDir 'docs' $_) -Destination $TempWorkDir
    Join-Path $TempWorkDir $_
}
| ForEach-Object { (Get-Content -Raw -Path $_) -replace '(?s)\n  "\$id".+?\n', "`n" | Set-Content -NoNewline -Path $_ }

@{
    $VcpkgJsonSchema.Configuration =
    @{
        'packages: a'           = $true, @{registries = @([pscustomobject]@{kind = 'git'; repository = ''; baseline = '0' * 40; packages = @('a') }) }
        'packages: baseline 39' = $false, @{registries = @([pscustomobject]@{kind = 'git'; repository = ''; baseline = '0' * 39; packages = @('a') }) }
        'packages: wildcard a*' = $true, @{registries = @([pscustomobject]@{kind = 'git'; repository = ''; baseline = '0' * 40; packages = @('a*') }) }
        'packages: array a*,b'  = $true, @{registries = @([pscustomobject]@{kind = 'git'; repository = ''; baseline = '0' * 40; packages = @('a*', 'b') }) }
        'packages: mid a*b'     = $false, @{registries = @([pscustomobject]@{kind = 'git'; repository = ''; baseline = '0' * 40; packages = @('a*b') }) }
    }
    $VcpkgJsonSchema.Port          =
    @{
        'port name: a'   = $true, @{name = 'a' }
        'port name: a.'  = $false, @{name = 'a.' }
        'port name: a-b' = $true, @{name = 'a-b' }
    }
}.GetEnumerator()
| ForEach-Object {
    @{
        SchemaName = $_.Key
        JsonCases  = $_.Value.GetEnumerator() | ForEach-Object { @{Title = $_.Key; Expected = $_.Value[0]; Json = ConvertTo-Json -InputObject $_.Value[1] -Depth 5 -Compress } }
    }
}
| ForEach-Object {
    $_SchemaName = $_.SchemaName
    $_SchemaPath = Join-Path $TempWorkDir $_SchemaName
    $_.JsonCases | ForEach-Object {
        $_Title = $_.Title
        $_Expected = $_.Expected

        $_Actual = Test-Json -Json $_.Json -SchemaFile $_SchemaPath 2>$null
        $_Result = $_.Expected -eq $_Actual ? 'Pass':'Fail'
        if ($_Result -eq 'Fail') {
            throw "$_SchemaName validate fail with $_Title, expected $_Expected"
        }
        [pscustomobject]@{
            SchemaName = $_SchemaName
            Title      = $_Title
            Expected   = $_Expected
            Actual     = $_Actual
            Result     = $_Result
        }
    }
}
| Format-Table -AutoSize

Remove-Item -Recurse -Force $TempWorkDir

Tested pass in PowerShell 7.4.2

$TempWorkDir = (New-Item -ItemType Directory Temp:/$(New-Guid)).FullName
# Write-Host $TempWorkDir
$VcpkgToolDir = $PSScriptRoot

$VcpkgJsonSchema = @{
    Artifact      = 'artifact.schema.json'
    Configuration = 'vcpkg-configuration.schema.json'
    Definitions   = 'vcpkg-schema-definitions.schema.json'
    Port          = 'vcpkg.schema.json'
}

# remove `$id` in schema for error 'Test-Json: Cannot parse the JSON schema.'
$VcpkgJsonSchema.Values
| ForEach-Object {
    Copy-Item -Path (Join-path $VcpkgToolDir 'docs' $_) -Destination $TempWorkDir
    Join-Path $TempWorkDir $_
}
| ForEach-Object { (Get-Content -Raw -Path $_) -replace '(?s)\n  "\$id".+?\n', "`n" | Set-Content -NoNewline -Path $_ }

@{
    $VcpkgJsonSchema.Configuration =
    @{
        'packages: a'           = $true, @{registries = @([pscustomobject]@{kind = 'git'; repository = ''; baseline = '0' * 40; packages = @('a') }) }
        'packages: baseline 39' = $false, @{registries = @([pscustomobject]@{kind = 'git'; repository = ''; baseline = '0' * 39; packages = @('a') }) }
        'packages: wildcard a*' = $true, @{registries = @([pscustomobject]@{kind = 'git'; repository = ''; baseline = '0' * 40; packages = @('a*') }) }
        'packages: array a*,b'  = $true, @{registries = @([pscustomobject]@{kind = 'git'; repository = ''; baseline = '0' * 40; packages = @('a*', 'b') }) }
        'packages: mid a*b'     = $false, @{registries = @([pscustomobject]@{kind = 'git'; repository = ''; baseline = '0' * 40; packages = @('a*b') }) }
    }
    $VcpkgJsonSchema.Port          =
    @{
        'port name: a'   = $true, @{name = 'a' }
        'port name: a.'  = $false, @{name = 'a.' }
        'port name: a-b' = $true, @{name = 'a-b' }
    }
}.GetEnumerator()
| ForEach-Object {
    @{
        SchemaName = $_.Key
        JsonCases  = $_.Value.GetEnumerator() | ForEach-Object { @{Title = $_.Key; Expected = $_.Value[0]; Json = ConvertTo-Json -InputObject $_.Value[1] -Depth 5 -Compress } }
    }
}
| ForEach-Object {
    $_SchemaName = $_.SchemaName
    $_SchemaPath = Join-Path $TempWorkDir $_SchemaName
    $_.JsonCases | ForEach-Object {
        $_Title = $_.Title
        $_Expected = $_.Expected

        $_Actual = Test-Json -Json $_.Json -SchemaFile $_SchemaPath 2>$null
        $_Result = $_.Expected -eq $_Actual ? 'Pass':'Fail'
        if ($_Result -eq 'Fail') {
            throw "$_SchemaName validate fail with $_Title, expected $_Expected"
        }
        [pscustomobject]@{
            SchemaName = $_SchemaName
            Title      = $_Title
            Expected   = $_Expected
            Actual     = $_Actual
            Result     = $_Result
        }
    }
}
| Format-Table -AutoSize

Remove-Item -Recurse -Force $TempWorkDir

Add definitions/package-pattern to fix optional trailing *

Pattern of ^[a-z0-9]+(-[a-z0-9]+)*(-?\*)*$ to match ‘boost*’ and ‘boost-*’

Is this actually accepted by the product code?

Pattern of port-name matches 'dot-separated identifier'. No relevant documents found, remove this definition.

This was done to give better intellisense behavior / descriptive text. But I think it's fine to remove it.

match ‘boost*’ and ‘boost-*’

Is this actually accepted by the product code?

There are some places to parse the pattern:

src/vcpkg/configuration.cpp#L1016 is_package_pattern
src/vcpkg/registries.cpp#L1474 package_pattern_match

And there are some test cases covering it:

src/vcpkg-test/registries.cpp#L155 CHECK(is_package_pattern("boost-*"));
src/vcpkg-test/registries.cpp#L188 rs.push_back(make_registry(4, {"boost-*"}));

Oh, and thanks for the fixes!


Add support of "pagination" of tracker results

Just an theoretical idea: it would be nice to have support of "pagination" (when tracker show several pages with results).
It is quite optional feature since usually we use search URLs with sort by seeds and usually number of results on the first page is larger than burst setting about "maximum results from provider".
But i guess for some trackers (the ones that show small number of results per page) this feature could be useful.

@antonsoroko Usually we have limits per-provider to avoid bombing websites requesting Torrent files or subpages.
To implement paging we need to have another html selector for pages and implement a loop through pages somehow, knowing where we visited.


Please add option to ec2 provider to provision with private ip only

Rancher is awesome, but I am unable to use it until I can provision hosts in EC2 VPC with private IPs only.
The option already exists on the driver --amazonec2-private-address-only. Exposing this as a checkbox in the VPC/Subnet section should be a good place for this.
Thanks for the awesome product, can't wait to see what you come up with next.

Was this one implemented in v0.28.0 ?

Yup, thanks @flaccid

Cool thought so was just checking so maybe this is good to close now?

Verified Fixed in v0.30.0-rc2. The UI has the option and it's set in the logs in the docker-machine command.


Reassigning current_tree to FoldingPanel is generating temporary freezes when updating folding

While testing PR #13864, I found the problem I fixed on PR #14607 and then the one I'm reporting here.
After a couple of hours of tying to understand the source of the issue, I found it's caused by this method:
https://github.com/spyder-ide/spyder/blob/549d525c4c03f5a88d67ffb30434077efaa62ee5/spyder/plugins/editor/panels/codefolding.py#L195-L203
Specifically, by reassigning current_tree there. After removing that assignment (the others are fine), the freezes disappear.
@andfoy, please take a look at this one.

This no longer applies, so closing.


Linkify project descriptions [OSF-6626]

Purpose
Replaces #6030
Allow uses to include links in their project descriptions.
Changes
Uses linkify.js to allow html links in otherwise sanitized content.
To avoid built-in sanitization this will only apply to descriptions when users can't edit them.
Side effects
None apparent
Ticket
https://openscience.atlassian.net/browse/OSF-6626

One more change, then should be ready. When it's done and tests pass, just move the jira ticket to Code Review. Pass done. 🐧

Looks great! 🎉 🐧 🎉


Ui Controls for next and previous are switched

I wondered why I couldn't switch to the next slide with n. It is because the controls are switched for ui_next and ui_previous as can be seen here:

I was wondering the same. It was like this since the initial release as far as I remember so maybe it's intended.

No it's not, feel free to fix it!


Add InvokeContract to JsonRpc

Purpose
The common-sdk is missing invokeContract method.
Changes
I've added invokeContract method to the RPC client.
Checklist

[x] My code follows the style of this project.
[x] The code compiles without warnings.
[x] I have performed a self-review of the changes.
[x] I have documented my code, in particular the intent of the
hard-to-understand areas.
[ ] (If necessary) I have updated the CHANGELOG.

CLA acceptance
By submitting the contribution I accept the terms and conditions of the
Contributor License Agreement v1.0

link: https://developers.concordium.com/CLAs/Contributor-License-Agreement-v1.0.pdf

[X] I accept the above linked CLA.

Thank you for the PR.
However, this was actually already implemented, but it was 'stuck' in an open PR. :upside_down_face:
That has now been merged and I've released a new version of the common/web-sdk with it.


sched/kconfig: add INITIAL_PID_LIMIT

Summary
sched/Kconfig: add INITIAL_PID_LIMIT option
This adds the flexibility to configure pid hash table length. It allows to
provision the table right at once for cases where number of threads are
known at design time.
Impact
None
Testing

Local test with rv-virt/nsh and rv-virt/nsh64
CI checking

@xiaoxiang781216 and @acassis
Looks like CI system breaks?
Configuration/Tool: smartl-c906/sotest
------------------------------------------------------------------------------------
  Cleaning...
  Configuring...
  Building NuttX...
riscv-none-elf-ld: dynload.o: ABI is incompatible with that of the selected emulation:
  target emulation `elf64-littleriscv' does not match `elf32-littleriscv'
riscv-none-elf-ld: failed to merge target specific data of file dynload.o
riscv-none-elf-ld: warning: cannot find entry symbol _start; defaulting to 00010074
make[4]: *** [Makefile:45: dynload] Error 1

With stock toolchain gcc-riscv64-unknown-elf on Ubuntu 22.04, this config can be built with makefile system.

please rebase, that PR was reverted

@yf13 How about restore the restrictions of CONFIG_MAX_TASKS?
#4117
There are two benefits:

avoid accessing memory allocators
same benefits as PIDHASH_INITIAL_LENGTH, and CONFIG_MAX_TASKS is more concise and easy to understand

@yf13 How about restore the restrictions of CONFIG_MAX_TASKS? #4117
There are two benefits:

avoid accessing memory allocators
same benefits as PIDHASH_INITIAL_LENGTH, and CONFIG_MAX_TASKS is more concise and easy to understand

but not all products can easily predicate the accuracy number of threads required by runtime. PIDHASH_INITIAL_LENGTH plus the static array could satisfy both usages.

@anchao as current approach already supports both static and dyanmic pid ranges, maybe we can stick with it and just see if there are better names?
Other names I can tell are: INITIAL_PID_LIMIT, INITIAL_PID_RANGE etc. For cases where max pid is known at design time, simply set it in INITIAL_PID_LIMIT.

@anchao as current approach already supports both static and dyanmic pid ranges, maybe we can stick with it and just see if there are better names?
Other names I can tell are: INITIAL_PID_LIMIT, INITIAL_PID_RANGE etc. For cases where max pid is known at design time, simply set it in INITIAL_PID_LIMIT.

@yf13 Let's keep this name for now, I mainly want to eliminate allocator access, but which should not be implemented in this PR. Please address @xiaoxiang781216 comments.

@anchao, eliminating allocator use during boot time is a large topic that be discussed separately. my purpose is just to achieve leakless ostest.
@xiaoxiang781216, I don't quite what you mean by "the static array"? can you be more explicit? As the pid table is backed by an array for quick index based access, the approach we used for linked list seems improver for this case.

@anchao, eliminating allocator use during boot time is a large topic that be discussed separately. my purpose is just to achieve leakless ostest.
@xiaoxiang781216, I don't get what you mean by "the static array"? can you be more explicit? As the pid table is backed by an array for quick index based access, the approach we used for linked list seems improver for this case.

@anchao, how do you find out patch 4117 from commit 00cf12b? I don't see a method in gh pr command.

Looks like CI is broken? Got below from Linux (arm-01):
Configuration/Tool: ntosd-dm320/udp,CONFIG_ARM_TOOLCHAIN_GNU_EABI
------------------------------------------------------------------------------------
  Cleaning...
  Configuring...
  Disabling CONFIG_ARM_TOOLCHAIN_GNU_EABI
  Enabling CONFIG_ARM_TOOLCHAIN_GNU_EABI
  Building NuttX...
make[1]: *** No rule to make target '/github/workspace/sources/nuttx/.config'.
make[1]: Failed to remake makefile '/github/workspace/sources/nuttx/.config'.
make: *** [tools/Unix.mk:268: tools/cnvwindeps] Error 2

@anchao, how do you find out patch 4117 from commit 00cf12b? I don't see a method in gh pr command.

@yf13  You could type .patch at the end of the URL and refresh the URL or press enter to go the URL if you just want the patch file:
https://github.com/apache/nuttx/pull/4117.patch

@anchao, thanks for teach this URL rule.
If I get commit id 00cf12b from my local repo (e.g. via git blame), how can I find the PR number 4117 which includes that commit from Github?

@yf13   I'm not familiar with how to search the PR in the CLI, for website maybe you can search for commit id in nuttx repo to get out  the corresponding PR:

@anchao, many thanks! I tried the web search, now both 4117 and this PR are returned.

Unfortunately I can't access wordpress in China, will check them later when there are chances.


[$500] Desktop - BA - An endless spinner appears when user connects BA with Plaid

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.40-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:

Open Desktop App
Log in with expensifail account
Create workspace or go to existing one
Go to WS settings > Bank Account
Select "Connect online with Plaid"

Expected Result:
User can continue connecting BA with Plaid
Actual Result:
An endless spinner appears when user connects BA with Plaid
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/ab13d541-965d-4419-8169-b5fffb6d28ef
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~013293255e0be91802
Upwork Job ID:<PHONE_NUMBER>890064384
Last Price Increase: 2024-02-12

Does the issue persist in 1.4.40-1?

Thanks for giving that a try, @hoangzinh! In that case, let's go ahead and close this one.


cdn.embedly.com

This is for embedded images and videos and is not malicious
a CDN is a content distribution network
example https://www.reddit.com/r/MechanicalKeyboards/comments/5acqca/one_key_is_more_than_enough_3d_printed_digispark/

thanks! fixed


[FLINK-15101][connector/common] Add SourceCoordinator implementation.

What is the purpose of the change
This patch is a part of FLIP-27. It adds the implementation for SourceCoordinator which extends OperatorCoordinator.
Brief change log
The following major classes are added:

SourceCoordinator
SourceCoordinatorContext
SourceCoordinatorProvider
SplitAssignmentTracker

Verifying this change
This change added related unit tests.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes)
The serializers: (yes)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (yes)
If yes, how is the feature documented? (JavaDocs)

@StephanEwen This is the patch for SourceCoordinator implementation. Do you have time to take a look? Thanks.

@flinkbot run azure

@flinkbot run travis

Thank you for addressing the changes. Looks good to me with two remarks:
(1) Can we wrap the ByteArrayOutputStream into a DataOutputStream instead of using the SerdeUtils? It looks both simpler and more efficient and is also what other parts of the Flink code typically do.
(2) About the "Fatal Error Handler": Virtually all of the really critical issues in Flink have fallen into the following category: An exception happens that we try to handle "fine grained" but it actually leaves something in an inconsistent state that is not recognized. Had we simply handled it "coarse grained" (fail process, rely on recovery) it would have been fine.
That is why I think the default should be to escalate. If we feel that we are completely sure we can handle this more fine-grained, then it is fine.
This issue is somewhat connected with the "closing" of the coordinator.
How about the following approach:

We add a "process killing" uncaught exception handler, as the safety net.
We catch the exceptions in the runnables ourselves and cause a global job failure upon exception, unless the SourceCoordinator is closed already
The global job failure will close() the current coordinator re-create the coordinator from latest checkpoint (we need to still implement this)
closing the source coordinator gets the following changes

we call shutdownNow() on the executor to make sure all queued tasks do not get executed
we make sure the SourceCoordinator does not forward events from the Enumerator any more, so that a long-running task that is still being executed in the enumerator cannot affect anything any more

From my side, (1) looks like a nice to have (consistent way of doing thins in the code base) and for (2) we could for now just to the FatalErrorHandler (be on the safe side) and make error handling more fie grained in a follow-up.

Thanks for the review @StephanEwen. I just updated the patch.
Re: (1) Yes, keeping the code style consistent make sense. I did not find DataOutputStream, though. Do you mean DataOutputViewStreamWrapper?
Re: (2) Sounds good to me.

@flinkbot run azure

To expedite the merge a bit, how about just (1) switching to DataOutputStream (that is a JDK class, not a Flink class, I assume you searched for it in the Flink codebase?) and (2) doing the fatal error handler?
I would be up for taking a patch to make failure handling more fine grained as a next step (it is not a strict must-have, just a nice-to-have).

My updated patch did exactly what you said. I will merge the patch once the CI passes.

@flinkbot run azure

Sadly, Flinkbot does not re-run the CI if the last status is "UNKNOWN". You need to do another push to the branch (empty commit, rebase).

@rmetzger  Thanks for the help. I just tried to do a rebase as well as an empty commit. But it seems the CI test was still not triggered.

The bot needs quite some time to update. I notified Chesnay already to look into it.

merged to master:
ed400497e56ea272722ac71697edf830b2d682ae


Document how to disable Actions in GitHub

Yes, you can disable Actions in GitHub.
For an organization:
https://docs.github.com/en/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#managing-github-actions-permissions-for-your-organization
For a repository:
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#managing-github-actions-permissions-for-your-repository
I'll make this into a documentation issue too, thanks!

Originally posted by @plocket in https://github.com/SuffolkLITLab/ALKiln/issues/433#issuecomment-992596977
Edit: disabling just that particular workflow will help people who want to be able to run other actions:

You can also keep your other actions running and disable just that workflow: https://docs.github.com/en/actions/managing-workflow-runs/disabling-and-enabling-a-workflow

Closed by https://github.com/SuffolkLITLab/docassemble-AssemblyLine-documentation/issues/184


Language Extensibility: Add quick fix support

Need to figure out what the UI would look like. The quick fix might make sense in both insert and normal mode. In both modes, maybe we could re-use the quick info paradigm? Or, if there is both quickinfo + a fix, show the fix listed in the quickinfo box?

Tracked this also in #474 , and that has more info - closing this as a dup.

Was just looking at the bountysource website, looks like there is a bounty pointing at this issue, should probably update it to point at the newer issue?


Support IJ 2018.1

com.google.idea.blaze.base.command.info.BlazeInfoException: blaze info failed with exit code: -1
java.util.concurrent.ExecutionException: com.google.idea.blaze.base.command.info.BlazeInfoException: blaze info failed with exit code: -1
	at com.google.common.util.concurrent.AbstractFuture.getDoneValue(AbstractFuture.java:502)
	at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:481)
	at com.google.common.util.concurrent.AbstractFuture$TrustedFuture.get(AbstractFuture.java:78)
	at com.google.idea.blaze.base.async.FutureUtil$Builder.lambda$run$0(FutureUtil.java:96)
	at com.google.idea.blaze.base.scope.Scope.push(Scope.java:37)
	at com.google.idea.blaze.base.async.FutureUtil$Builder.run(FutureUtil.java:86)
	at com.google.idea.blaze.base.sync.BlazeSyncTask.doSyncProject(BlazeSyncTask.java:311)
	at com.google.idea.blaze.base.sync.BlazeSyncTask.syncProject(BlazeSyncTask.java:228)
	at com.google.idea.blaze.base.sync.BlazeSyncTask.lambda$run$0(BlazeSyncTask.java:189)
	at com.google.idea.blaze.base.scope.Scope.push(Scope.java:60)
	at com.google.idea.blaze.base.scope.Scope.root(Scope.java:52)
	at com.google.idea.blaze.base.sync.BlazeSyncTask.run(BlazeSyncTask.java:163)
	at com.google.idea.blaze.base.async.executor.ProgressiveTaskWithProgressIndicator.lambda$submitTask$0(ProgressiveTaskWithProgressIndicator.java:79)
	at com.google.idea.blaze.base.async.executor.ProgressiveTaskWithProgressIndicator.lambda$submitTaskWithResult$2(ProgressiveTaskWithProgressIndicator.java:113)
	at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$2(CoreProgressManager.java:173)
	at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$1(CoreProgressManager.java:157)
	at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:580)
	at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:525)
	at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:85)
	at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:144)
	at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:173)
	at com.google.idea.blaze.base.async.executor.ProgressiveTaskWithProgressIndicator.lambda$submitTaskWithResult$3(ProgressiveTaskWithProgressIndicator.java:113)
	at com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:111)
	at com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:58)
	at com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:75)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
Caused by: com.google.idea.blaze.base.command.info.BlazeInfoException: blaze info failed with exit code: -1
	at com.google.idea.blaze.base.command.info.BlazeInfoRunnerImpl.runBlazeInfo(BlazeInfoRunnerImpl.java:102)
	at com.google.idea.blaze.base.command.info.BlazeInfoRunnerImpl.lambda$runBlazeInfo$2(BlazeInfoRunnerImpl.java:72)
	... 6 more

Console output:
Error:Cannot run program "bazel" (in directory "/Volumes/work/src/github.com/hsyed/rules_kotlin"): error=2, No such file or directory

@brendandouglas is 2018.1 working in general ?

Do you have the absolute path for bazel set in your settings?

Hi!
Thank you for great plugin.
Do you have any estimate when support will be available?

As a rough estimate, I expect we'll upload a 2018.1-compatible plugin around late May.

Any incomplete work that could be shared to let others help with the effort?

We've switched to 2018.1 for the next release (in 3 weeks time). Most of the work involved is tracking down the many edge cases where things stop working in a new release, which can't really be shared.

verified, works, thank you!

@excavador Where'd you get the working plugin? I tried downloading it from here and the latest version (2<IP_ADDRESS>.2) doesn't work.

@ricelid what problems are you having with that plugin version? Could you include:

your IDE + IDE version
any exceptions coming from the problem and/or else expected vs actual results

IntelliJ IDEA 2018.1 (Ultimate Edition)
Build #IU-181.4203.550, built on March 26, 2018
Licensed to Google
JRE: 1.8.0_152-release-1136-b20 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.13.4
Problem 1:
The Bazel plugin doesn't show up in the search results within "Browse Repositories".
Problem 2:
When I download the zip file from here and "install plugin from disk", I get "Plugin 'Bazel' is incompatible with this installation".

That's an old version of IJ 2018.1, which the plugin isn't compatible with (the version compatibility information is listed in the JetBrains plugin repo site you linked).

@ricelid I download new IDEA (2018.1.3) and new bazel plugins.
Works fine for golang, python, javascript


Add Inspector section highlight during drag and drop

Revamped #39650.
Better user feedback while waiting for the drop unfold timer.

Seems something went wrong with the artifact upload... I think resetting might fix it.

@hinlopen You can force-push a commit with no changes (git commit --amend --no-edit && git push -f) to re-run CI.

I re-ran the failed CI builds already.

This is actually already implemented.


Support Narc

As title.

https://github.com/owo-lang/narc-rs/blob/master/src/syntax/surf/grammar.pest

Test


Phone number is not approve

A phone number has been added and confirmed, but in the form of an airdrop, there is still a message about the need to add !
Keybase GUI Version: 5.0.0-20191114143658+f73f97dac6

Do yo live in an accepted country?
"You must verify a phone number in a country that hasn't attacked us with fake accounts. The current list of acceptable countries is: Argentina, Australia, Austria, Belgium, Belize, Bermuda, Bolivia, Brazil, Bulgaria, Chile, Croatia, Costa Rica, Dominican Republic, Ecuador, El Salvador, Republic of Cyprus, Czech Republic, Denmark, Estonia, Finland, France, French Guiana, Germany, Greece, Guatemala, Guyana, Haiti, Honduras, Hungary, Iceland, Ireland, Israel, Italy, Japan, Kenya, Latvia, Lithuania, Luxembourg, Malta, Mexico, Netherlands, Nicaragua, Nigeria, New Zealand, Norway, Panama, Paraguay, Peru, Poland, Portugal, Romania, Slovakia, Slovenia, South Africa, Spain, Sweden, Switzerland, United Kingdom, United States, Venezuela."
Excerpt from https://keybase.io/airdrop

What do I do if this list states a country that does not seem to work? In my case the Republic of Cyprus ?


Bug fixes 1.18.2

Okay some notes
custom task is already a PR so no need to have it here
this also includes a fix for @equip
Fixes #285
Fixes #286

Merge once checks compelte


No CVE-2023 in csv file

Hello
CVE-2023 are present in the KVE source file https://www.cisa.gov/sites/default/files/csv/known_exploited_vulnerabilities.csv but i can't find them in the generated csv file.

Sorry,  I was missing pulling the NVD data for 2023 via GIthub actions.  It is done now and all CVEs are in the file.

I confirm , it's working, thanks again


feat(wash)!: update wash to 1.0 control interface

This PR updates wash to the latest control interface, including changes in wash-lib, the wash-cli code and CLI, and the unit/integration tests.
As I work through validating the commands work well, I renamed actor to component where I can 😄 for every command, with backwards compatible actor aliases where possible.
Feature or Problem
This PR updates wash-lib and wash-cli to update to the latest control interface client that's present in this repository but not-yet published to crates.io. I expect for tests to fail as wash integration tests work by using a published version of the wasmCloud host.
This PR grew in scope to accommodate the above changes, and I've attempted to consolidate commits where possible. In addition to updating the control interface, this PR:

Renames actor to component where possible
Removes deprecated commands like reg push and ctl start
Updates spy and capture to work with wrpc invocations
Fixes a bug with putting new links with differing interfaces
Fixes a bug with component update where we would deadlock 100% of the time
Changes component update to be a "fast ack" operation as it involves OCI downloads.

Related Issues
~It would be nice for #1636 to merge before this comes out of draft so we can validate tests work well.~
Release Information

Consumer Impact

Testing

Unit Test(s)
CLI tests were modified as necessary to either remove outdated commands or update with the latest command line arguments.
Acceptance or Integration
I disabled two integration tests get_claims and update_actor in wash for now. Once we cut the next alpha version of wasmcloud these can be reenabled (I verified both work with the unreleased version in this PR).
Additionally, integration tests now depend on fetching a component from my GHCR, because we don't have a published one yet 😬
Manual Verification
I made sure that each command at the very least works with the 1.0 alpha 😄 We've got many planned improvements to dev in #1594 and we need to add a config command, but I'll do that as a followup to this PR.

All the integration tests pass locally for me so I'll have to take another look at what's going on


java.io.IOException: unable to create directory: /tokens

Drive Api Quickstart
I tried creating token folder as instructed in quickstart.
public static final String TOKENS_DIRECTORY_PATH = "tokens";
GoogleAuthorizationCodeFlow flow = new GoogleAuthorizationCodeFlow.Builder(
HTTP_TRANSPORT, JSON_FACTORY, clientSecrets, SCOPES)
.setDataStoreFactory(new FileDataStoreFactory(new java.io.File(TOKENS_DIRECTORY_PATH)))
.setAccessType("offline")
.build();
It returns an error saying java.io.IOException: unable to create directory: /tokens

Can you confirm that the account running the Java code has write permissions to the file system? It should create the tokens directory in the same directory where the application is run.

Closing due to inactivity.

i am also getting the same error can you please reopen this issue

yes my code is having read and write permissions

I got the same error when I was trying to implement the code to use in Android Studio environment.
This is the error I got
05-02 02:05:17.139 10580-10580/com.cricket.mannual.driveuploaddemo I/System.out: Current working directory : /
05-02 02:05:17.256 10580-10580/com.cricket.mannual.driveuploaddemo W/System.err: java.io.IOException: unable to create directory: /storage/emulated/0/tokens
My Code
java.io.File tokenFolder = new java.io.File(Environment.getExternalStorageDirectory() + java.io.File.separator + TOKENS_DIRECTORY_PATH);
if (!tokenFolder.exists()) {
tokenFolder.mkdirs();
}
    // Build flow and trigger user authorization request.
    GoogleAuthorizationCodeFlow flow = new GoogleAuthorizationCodeFlow.Builder(
            HTTP_TRANSPORT, JSON_FACTORY, clientSecrets, SCOPES)
            .setDataStoreFactory(new FileDataStoreFactory(tokenFolder))
            .setAccessType("offline")
            .build();

As mentioned at the top of the quickstart instructions, this sample is for the command line, where creating files to store tokens is possible. On android you need to use a different authorization flow:
https://developers.google.com/api-client-library/java/google-api-java-client/oauth2#android


Adding a jhipster

Would https://www.jhipster.tech/ fit into this list ?
JHipster is a development platform to generate, develop and deploy Spring Boot + Angular / React / Vue Web applications and Spring microservices.
If so i'll make a pull request with it.

If you have an Awesome list for it, sure. This repo is a list of Awesome lists.


[1.11.2] Upgrading from 1.1.6 to 1.1.7 seems to crash the game

Crash report: https://pastebin.com/eAVWzdck
To confirm i made a new pack with just BwM 1.1.6, placed some turn tables and filtered hoppers, saved, updated to 1.1.7 and loaded the world again. That's when i get the crash.
Once in a while it managed to load and turned the turn tables (oh the irony!) into filtered hoppers. But it still crashes sometimes afterwards.
Let me know if you need any other info!
-SC

There may be some hope, but Internal changes in 1.1.7 might have ruined the world. You should be able to load in 1.1.6 again, break all machine blocks, including Filtered Hoppers, Turntables, Cauldron, Crucible and Millstones and try to load in 1.1.7 without them. Once you load the items will not be the same, Cauldron and Crucible were separated into their own block and that changed the item ids for the rest.
So give this a shot if not maybe worldedit could save it, not sure. My fault for making a breaking change in the middle of a version because we have put it off too long and really needed it.

Yeah, I'll have to agree with that. Better to get it over with before all the other tech mods catch up than have to wait until the 1.12 port to do it. Especially when we don't know how long that will take.

Makes sense! It seems like loading that world in 1.1.6 again will work too but it crashes once for every turntable/hopper. After that it's okay.
Reason i asked is cause i was using it in my modpack and it would probably break worlds of many people (that mod is crucial in making any progress, so it's very likely everyone has BwM blocks placed).
Do  you have any plans for other big changes or additions for the 1.11 version? I may just keep the modpack version at 1.1.6 for now then.
I think a little warning on the 1.1.7 file changelog that upgrading from 1.1.6 causes some issues might be useful.
Thanks for getting back to me so quickly!
-SC

All the major internal changes that need to be made have been for now. If you want to keep compatibility with old worlds staying 1.1.6 is probably the best option, there were a few bug fixes in 1.1.7 that hopefully won't affect many people but not much I can do about that.
Again, my bad for not saying anything about the breaking change, guess I didn't communicate that to @BeetoGuy well enough.

I'll put a warning up on the CurseForge download page.

Will keep it on 1.1.6 then, should be fine. Thanks! :D


[Suggestion] Drag-and-drop uploading

It would be nice to be able to just drag and drop files directly onto the submission page for uploading new submissions and fixed versions, similar to the old upload endpoints.

done


Error with flutter_outline enabled

Hi,
with the option flutter_outline enabled, I have this error message that shows up when I insert a new line under a widget for example:
Error executing vim.schedule lua callback: ...s/start/flutter-tools.nvim/lua/flutter-tools/outline.lua:484: attempt to perform arithmetic on local 'index' (a nil value)

Here's my configuration for flutter-tools:
local capabilities = vim.lsp.protocol.make_client_capabilities()
capabilities.textDocument.completion.completionItem.snippetSupport = true

require("flutter-tools").setup {
  flutter_outline = {
    enabled = true
  },
  lsp = {
    capabilities = capabilities
  }
}

This message only appears if I edit lines where the outline is visually set.
I used the starter flutter project to test it.
Thanks!

Hi @BenoitPingris thanks for trying out the plugin and reporting the issue 👍🏿. Yep can easily reproduce it and have a fix for it.


How to retain only the STRUCTURE VARIATION for pangenie

Dear developer
We want to only make use of pangenie for group typing from the result of Minigraph-cactus.
How do we delete snp and indel, because we feel that adding a large amount of snp and inde variation information will make the time of genotypeing.
Best yours!

PanGenie needs information from SNPs+indels for the imputation of genotypes in regions not well covered by k-mers. Therefore, it is not recommended to remove any of these variants prior to genotyping.

Thank you for your help and relpy!


Some normalized names show as "Unknown"

There's a user with two ENS names that are normalized, but the metadata service returns "Unknown ENS name" - this has persisted for at least a few days:

ENS Name
Links

dinaz.eth
[Metadata] [Manager App]

immersant.eth
[Metadata] [Manager App]

Thank you for the issue! I realized that, there was an issue with the resolver condition in avatar text record check, shipping a fix now.


Handle nested levels of spread properties (Fixes #771)

Also no longer breaks for ...rest properties.

Merged. Thanks!

just got bit by this, awesome!, waiting for next npm version, thanks!


chore(deps): update webpack example version

This PR updates webpack to 5.76.1 motivated by a dependabot warning.

This PR conflicts with PR https://github.com/cypress-io/github-action/pull/830, so which ever one is merged first will necessitate rebasing the other one. I will follow up on that action as necessary.

Squashed and rebased after merge of https://github.com/cypress-io/github-action/pull/830

Looks good, needs one more ✅ , maybe @AtofStryker ?

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: MikeMcC399:x: lmiller1990You have signed the CLA already but the status is still pending? Let us recheck it.


Fixing the yaml syntax which is currently being lost

The first example is currently showing online as:
steps:

task: Bash@3
inputs:
targetType: 'inline'
script: echo $MYSECRET
env:
MySecret: $(Foo)

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: james-portman-contino sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Unique edge in Resource Tracker Graph

#225

Thanks @a-belhadj

This PR is now outdated and will need a complete refactor if we still want to merge it.
On my side I haven't add the bug again.


.open always causes an abort event to be dispatched

this.abort has always been called whenever .open is called https://github.com/driverdan/node-XMLHttpRequest/blob/554280a7c509c1ce4d7ad9516b46d182739e8026/lib/XMLHttpRequest.js#L157
More recently this.abort was changed to emit the abort event. A side effect being that open always causes an abort, https://github.com/driverdan/node-XMLHttpRequest/blob/554280a7c509c1ce4d7ad9516b46d182739e8026/lib/XMLHttpRequest.js#L559
Is this the expected behavior?

It's my guess that this logic in the abort method should be wrapped in its own private helper of sorts and gets called by both .open and .abort:
https://github.com/driverdan/node-XMLHttpRequest/blob/554280a7c509c1ce4d7ad9516b46d182739e8026/lib/XMLHttpRequest.js#L540


Can't edit sources on Gene edit page

A new box should be added to allow users to edit the sources portion of the gene description. These are currently imported from the spreadsheet but not otherwise accessible.

At the moment I'm working on the multi-input-with-typeahead-search UI component(s) that will enable this kind of feature, should have it working soon. The component currently working (on the client side) for variant group variants.


Frontmatter lacks documentation

I'm about to give up on Grav, because I'm trying to edit my pages in expert mode, but when wanting to edit the "frontmatter" there is no information about the "tags" i need to use.
I want to change the "logo" in the Antimatter theme, can't do it. I want to add a big background image, can't do it.
You need to create documentation, or some way to display the what kind of tags to use so I't intuitive to work with

It should be changeable by editing config.site.title which should show in Admin under config, site tab.
Changing appearance will depend on theme, for antimatter look at lines 45-47
https://github.com/getgrav/grav-theme-antimatter/blob/develop/templates/partials/base.html.twig

I can change the site's name under that config location.
The lines of code indicate that i could use "header_image", or more likely "header_image_file", however, they do nothing.
Would be just super if the admin-panel just presented all the possible options for the given theme's page template

It's up to the theme provider to document what can be set, and that really means that they need to provide an appropriate blueprint.yaml to define those fields.


Bug: No response with numpy 1.26.4, python 3.12.3, nuitka 2.3rc5 and --standalone

Update: It seems to work with numpy 1.26.3 but not with 1.26.4

My Environment
Running python 3.12.3 on windows 11 23H2

installed python from https://www.python.org/ftp/python/3.12.3/python-3.12.3-amd64.exe and created a virtual environment from it using python -m venv venv-312-test
installed nuitka with python.exe -m pip install https://github.com/Nuitka/Nuitka/archive/develop.zip

Nuitka version (used with mingw64)
2.3rc5
Commercial: None
Python: 3.12.3 (tags/v3.12.3:f6650f9, Apr  9 2024, 14:05:25) [MSC v.1938 64 bit (AMD64)]
Flavor: CPython Official
Executable: C:\Users\shapingview\Desktop\repos\venv-312-test\Scripts\python.exe
OS: Windows
Arch: x86_64
WindowsRelease: 11
Nuitka-Scons:WARNING: Windows SDK must be installed in Visual Studio for it to be usable with Nuitka. Use the Visual Studio installer for adding
Nuitka-Scons:WARNING: it.
Version C compiler: ~\AppData\Local\Nuitka\Nuitka\Cache\DOWNLO~1\gcc\x86_64\13.2.0-16.0.6-11.0.1-msvcrt-r1\mingw64\bin\gcc.exe (gcc 13.2.0).

python environment:
pip freeze
Nuitka @ https://github.com/Nuitka/Nuitka/archive/develop.zip#sha256=e972d115ec23c2e61236cf15eeb96e95e1c7fad5355e29abdc9f131859b05a29
numpy==1.26.4
ordered-set==4.1.0
zstandard==0.22.0

Script
Compiling this script (hw.py) does not work
import time
import numpy as np

def f(inp):
    print("Hello " + inp)

def main():
    time.sleep(np.random.uniform())
    f("nuitka!")

if __name__ == "__main__":
    main()

Version without numpy works
import time

def f(inp):
    print("Hello " + inp)

def main():
    time.sleep(.5)
    f("nuitka!")

if __name__ == "__main__":
    main()

Behavior
Running this script with python works fine, but after compilation with nutika it doesnt
> python .\hw.py  # works fine
Hello nuitka!

Remark:

I am also using --mingw64 because I currently can't install newer MSVC versions. Not sure if that is relevant for this issue
Without --standalone it works

>  python.exe -m nuitka --mingw64 --standalone hw.py
Nuitka-Options: Used command line options: --mingw64 --standalone hw.py
Nuitka: Starting Python compilation with Nuitka '2.3rc5' on Python '3.12' commercial grade 'not installed'.
Nuitka: Completed Python level compilation and optimization.
Nuitka: Generating source code for C backend compiler.
Nuitka: Running data composer tool for optimal constant value handling.
Nuitka: Running C compilation via Scons.
Nuitka-Scons: Backend C compiler: gcc (gcc 13.2.0).
Nuitka-Scons: Backend linking program with 99 files (no progress information available for this stage).
Nuitka-Scons: Compiled 99 C files using ccache.
Nuitka-Scons: Cached C files (using ccache) with result 'cache hit': 99
Nuitka: Keeping build directory 'hw.build'.
Nuitka: Successfully created 'hw.dist\hw.exe'.

running > .\hw.dist\hw.exe does not return anything.
Thanks for your help! I'm looking forward to your feedback

I just tried it, and it works fine with the current factory branch, at least. We also ran large parts of Nuitka-Watch against that and it should be good. There will be a pre-release of it soon too.

The bug I have fixed might be one that shows only in certain malloc situations, on every n-th run, maybe that is why you found another version to work.


Deleted duplicate text

PR Checklist

[ ] Does the coding style conform to our guidelines? Are there any flake8 errors?
[ ] Are user-facing changes documented?
[ ] Is there an entry for new features or dependencies in CHANGELOG.rst?
[ ] Are you the patch author? Are you listed in AUTHORS.rst?

Just fixing grammar.

Thanks! Apologies for the delay here.


fix: insufficient permission for ingestion server

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license
Summary
close #226
Implementation highlights
(describe how the merge request does for feature changes, share the RFC link if it has)
Test checklist

[x] add new test cases
[ ] all code changes are covered by unit tests
[ ] end-to-end tests

[ ] deploy web console with CloudFront + S3 + API gateway
[ ] deploy web console within VPC
[ ] deploy ingestion server

[ ] with MSK sink
[ ] with KDS sink
[ ] with S3 sink

[ ] deploy data processing
[ ] deploy data modeling

[ ] new Redshift Serverless
[ ] provisioned Redshift
[ ] Athena

[ ] deploy with reporting

Is it a breaking change

[ ] add parameters without default value in stack
[ ] introduce new service permission in stack
[ ] introduce new top level stack module

Miscellaneous

[ ] introduce new symbol link source file(s) to be shared among infra code, web console frontend, and web console backend

fixed in https://github.com/awslabs/clickstream-analytics-on-aws/pull/253

#253 only resolved the insufficient permissions for creating data processing stack, not ingestion server stack.


Fixed warnings associated with using gcc -Wextra

This simply fixes warnings produced by projects that use GCC with the -Wextra flag.

I would prefer to have the "FALLTROUGH" macro definition in one file, not in every one that does a falltrough...
Should we place that inside the driver (or compiler specific) file?

I agree. I was thinking about where I could centralize that definition, but there's no common header file included by everything other than maybe CO_driver.h. I guess we could do that, or maybe it would be a good idea to create a new common code implementation and header file (byte swapping code and other commonly used support functions could go in there as well maybe? And if we did this, maybe in the future it can check for different compiler provided functionality like GCC's __builtin_swap functions in order to optimize certain operations.)

Ok, ideally what we should do is a central cc.h header file that includes a specific header file (cc_gcc.h, cc_clang.h, etc) that defines all compiler-specific macros. Just have to figure out how we can specify that for custom drivers. If I remember correctly lwIP does this in a clean way.

Should I close this PR and instead open an issue (maybe with the Enhancement tag or something) to collaborate a solution with you all?

I'd say that you could create the common header and put the definition there, and improvements will follow. Do you agree @martinwag ?

The thing is, this is endless.  You willl need a compiler version specific file at some point, because you are stuck with GCC3.x on your hardware. You will need general and version specific files for the drivers too, as controller manufacturers change their driver API. Don't even think about CPU architecture and OS specific stuff.
I would be fine adding this to the template driver file and implement it in the specific drivers. Most of the drivers are bound to a specific compiler anyway... (Linux -> GCC, ST -> GCC, Microchip -> Microchip, ...). But we can add a compiler definition file also.

Basically did the same, just without any additonal headers, just by writing clean code, see #130
Didn't know others were already on the way to address this.

I'm going to close this since a couple of the fixes got incorporated through other pull requests, and the fallthrough thing could be figured out later.


Qdrant Access Web UI

When I launch qdrant, I can't access the dashboard.
I'm on Linux Mint
My firewall "ufw" is inastive.
I don't use docker because I couldn't install it (docker desktop). So I downloaded qdrant from "https://github.com/qdrant/qdrant/releases/tag/v1.7.4" the file "qdrant-x86_64-unknown-linux-gnu.tar.gz"
I was try with 1.5.1 but it's does the same.
Screen of my Memoir folder :

Screen of my qdrant terminal when I lunch then try to access the dashboard :

My computer informations :

In fact, the URL returns qdrant but not /dashboard
Maybe it's because I didn't use docker?

I use this script "https://raw.githubusercontent.com/qdrant/qdrant/v1.7.3/tools/sync-web-ui.sh"
And now I have static folder and the /dashboard works. I think the manual download of qdrant need an installation script for the webui or something like this.


Look into replacing iptables rules by firewalld rules

Suggested by @Miciah

I just submitted https://github.com/GoogleCloudPlatform/kubernetes/pull/12396 to make kube's util/iptables be firewalld-aware. Assuming that is accepted, the easy fix here would then be to make openshift-sdn do its iptables setup from go using that, rather than from a shell script like it does now.


fix Ignore uninit cloud delta writers

Proposed changes
Issue Number: close #xxx
The strict mode means strict filtering of column type conversions during import. Sometimes all inputs are filtered, but the partition ID is still set, and the writer is not initialized. This PR will skip those cloud delta writers when they close the tablets channel.
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


How to segment image or video by click as demo shows?

How to segment image or video by click as demo shows? I don't want to use prompt, and I think click is more useful than prompt.

Sorry. I find it in the notebooks


can't work in docker-alpine image

can't work in docker-alpine image .version is V3

This is not enough information to do anything about. Please describe your issue in more detail.
How are you using the package? How are you starting the application?
Some source code and perhaps a Dockerfile would be useful in this situation.


Support for HTTP -> HTTPS redirects

Now that https://issuetracker.google.com/issues/35904733 has finally shipped it would be neat if an HTTP->HTTPS redirect could be a simple option

https://cloud.google.com/load-balancing/docs/https/traffic-management
this should be implemented first on google terraform provider?
I would like this asap.
thanks :)

I think is not implemented yet
https://github.com/terraform-providers/terraform-provider-google/issues/6205

This is now unblocked via provider v3.20.0
https://www.terraform.io/docs/providers/google/r/compute_url_map.html#url_redirect-1
https://www.terraform.io/docs/providers/google/r/compute_url_map.html#default_url_redirect

This must only be set for UrlMaps used in TargetHttpProxys. Setting this true for TargetHttpsProxy is not permitted.

Example:
https://www.terraform.io/docs/providers/google/r/compute_target_http_proxy.html#example-usage-target-http-proxy-https-redirect
This should be a breaking release since we need to move away from a single url_map and instead use url_map_http/url_map_https either as inputs or managed inside the module.

thanks @morgante :+1:


[BUG] Transaction view and Filter issues

Applicable for Payments, Refunds, Disputes and Payouts.
Transaction view
If custom combination of connector status is selected All should not be highlighted

When All is selected clear filter button should be hidden
https://github.com/user-attachments/assets/a35d37cc-645c-41a6-9743-e995efb312f4
Filters
Can select same filters multiple times (Payments, Refunds, Disputes and Payouts)
https://github.com/user-attachments/assets/a2da3f4b-9dbc-4ccc-9712-17e8564dc4f1
No Connector Label filter in Payouts

Connector Label filter should be shown in the list always OR should be selected as soon as Connector filter is selected.

Can select same filters multiple times (Payments, Refunds, Disputes and Payouts)
Screen.Recording.2024-10-07.at.9.38.39.PM.mov

can you let me know how can I replicate this issue ??

No Connector Label filter in Payouts

we are not getting connector label data from backend for payouts

@gitanjli525 can you please check this issue as well.

Select a different filter, First filter should not be applied

https://github.com/user-attachments/assets/bb16f4cb-68a6-474b-9b3c-54bf752f0d12


First attempt at RasPi support

This is a first draft commit and a work in progress PR.
It cross compiles fine using cross build but I am having some issues with getting cargo-deb to work properly for packaging the deb file. Perhaps might be a better idea to package the .deb file manually like is done with the .ipk
Some other things to note:

For cargo-deb to work I had to install cmake and gcc-arm-linux-gnueabihf and rustup target add armv7-unknown-linux-gnueabihf
The ci.yml for github actions is a mess - need to fix

Let me know if you spot any issues or have any suggestions.

Just for reference, the error I am getting with cargo deb is as follows:
          /usr/bin/ld: /home/GitHub/gateway-rs/target/arm-unknown-linux-gnueabihf/release/deps/helium_gateway-0a4717c34b6d41e2.helium_gateway.1o693kuq-cgu.0.rcgu.o: relocations in generic ELF (EM: 40)
          /usr/bin/ld: /home/GitHub/gateway-rs/target/arm-unknown-linux-gnueabihf/release/deps/helium_gateway-0a4717c34b6d41e2.helium_gateway.1o693kuq-cgu.0.rcgu.o: error adding symbols: file in wrong format
          collect2: error: ld returned 1 exit status

Cargo-deb is basically ignoring the .config/config.toml due to the file extension...
As per the docs here the preferred config is .config/config.toml instead of .config/config but due to the code here:
https://github.com/mmstick/cargo-deb/blob/b5e4f398545a42ecbfdae7175f47c09cde103655/src/config.rs#L38
It is only looking at .config/config
See issue on cargo-deb here https://github.com/mmstick/cargo-deb/issues/157

@madninja the fix in cargo-deb is in and so in future versions it should be ok with a config.toml.
Are you happy with the config being .config/config without the toml extension for now, until the new cargo-deb package is in the repos? Just want to make sure it doesn't break anything.

@shawaj ok, I think we're ready to look at how this gets merged, if you're still interested?
Does the config vs config.toml work for the non cargo-deb platforms?

Thanks for your efforts here @shawaj! I'm going to close this in favor of: https://github.com/helium/gateway-rs/pull/37 which takes your initial constructs and fits it more into the cargo-make approach while making packaging consistent across ipk/deb targets

Thanks @madninja
Cc @ryanteck


k3s: init at 1.0.0

Motivation for this change
Package k3s. I was not able to build it from source, as there are too many variables, and would probably need to fork a source, but statically linked binaries work just fine.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

LGTM, also tested running this on NixOS. As you said, it's unfortunate that the upstream build process is as impure (downloading lots of stuff via curl).

I've been running using an updated version on x86_64 for a bit now, no difficulties but still impure (and only pulling one arch):
    pname = "k3s";
    version = "1.17.2+k3s1";

    src =  fetchurl {
      url = "https://github.com/rancher/k3s/releases/download/v${version}/k3s";
      sha256 = "0zxkw7daq3v8j2x7dwxadc1rjxy2d2sn63acpfakpwx874kxrdrv";
    };

    preferLocalBuild = true;
    dontUnpack = true;
    installPhase = "install -Dm755 $src $out/bin/k3s";

Can we get this PR either updated & merged, or merged & update in a separate PR?

Hey, I've managed to get a pure (I think) k3s derivation written (and merged too!).
I'm hopeful that I've got it building correctly so it can replace patchelfing the upstream binary. If you want to either improve the derivation or use it and make sure I didn't mess anything up, both of those things would be appreciated!

@euank great to hear, I am closing this one then 🙂


Make resource path based on chaiseBasePath property

For both boolean-search and heatmap, the chaiseConfig.js that is used and all the rest of the chaise resources, are hardcoded to be /chaise/.... This means that the ones installed at the root of the server will be used.
This is fine for the general deployments, but doesn't allow for testing of the integration between the chaise code and deriva-webapps code. The chaiseConfig should be fetched relative to the user's current directory (as well as the rest of the chaise assets).
This is going to be tricky, because the chaiseBasePath property is defined in the chaiseConfig, which is also in the /chaise/ folder. So we need to think of how to make this path relative to get the chaiseBasePath from the chaiseConfig, then rely on the base path value for the rest of the chaise assets.

To accomplish this, the deriva-webapps should follow a similar structure to this block of code in navbar.app.js in the chaise repo.
https://github.com/informatics-isi-edu/chaise/blob/master/lib/navbar/navbar.app.js#L66-L134

During migration of both heatmap and boolean search to reactJS, this is solved by how we are using chaise AppWrapper


Switching back to using revid in labels #trivial

The docker label (used to collect information about the image)
now uses the git commit id (i.e. the revision SHA) again.

          1 Error

:no_entry_sign:
Please include a CHANGELOG entry.

  Generated by :no_entry_sign: Danger

Codecov Report

Merging #728 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #728      +/-   ##
==========================================
+ Coverage   55.77%   55.79%   +0.01%
==========================================
  Files         259      259
  Lines       14899    14900       +1
==========================================
+ Hits         8310     8313       +3
+ Misses       5895     5893       -2
  Partials      694      694

Impacted Files
Coverage Δ

ext/docker/builder.go
73.97% <100%> (ø)
:arrow_up:

lib/buildpack.go
62.85% <100%> (+1.09%)
:arrow_up:

lib/build_context.go
100% <0%> (+50%)
:arrow_up:

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 dc44b7b...fde1f76. Read the comment docs.


Broken "Async suggestions" demo

The Loading.... message never shows up, tried also on my project and it looks like that the changed prop does not trigger component re-render.
const noOptionsText =
    state.isBusy && !state.suggestions.length ? 'Loading...' : 'No breweries found'`

https://i-like-robots.github.io/react-tag-autocomplete/
Thanks

I find out a workaround by adding disabled option with the text Loading, however it works I think that we should have an option to choose the newOption position, it should be either start on end. What do you think?

Thanks for the report and for your suggestions. I've had a look into this now and I can see that the newTagOption and noTagsOption methods are not being updated within the main manager state. I can make changes to fix this but I've always felt the internal options had quite a crude solution that I've never been happy with so I'll have a think how this may be better implemented.

I've merged a refactor of the state manager to avoid copying props into state and derive values for options on the fly. This resolves the bug reported but the demo could still be improved in a number of ways.


Add Travis-CI again (or remove button in README)

GH Actions Node CI logs expire much sooner that Travis-CI for one thing, and we seem to be having trouble with CI atm, so it would be nice to have those logs.
GH Node CI log for first failed commit: https://github.com/redux-saga/redux-saga/runs/267504349
^ not there
Travis CI logs from before switch to GH Actions CI: https://travis-ci.org/github/redux-saga/redux-saga/builds
^ still there
There is no reason not to have both running afaict.

Thanks for submitting this issue.  We have resolved the CI issues and don't intent on using travis anymore.


proposal for v3 auth

We have a role based auth system for v2. We are pretty happy about its simplicity and flexibility.
For v3, we will probably adopt the similar role based system. But we need to solve a few things:

the auth should be connection based, not request based. We want to use gRPC handshake or cert to solve this.

the auth API management API should always return the detailed view of roles and users.

/cc @mitake

the auth should be connection based, not request based. We want to use gRPC handshake or cert to solve this.

Correct me if I'm wrong, I think this will partially solve the current performance issue with etcd auth mentioned here https://github.com/coreos/etcd/issues/3223
If it doesn't, then what is the plan to solve this issue for v3?

If it doesn't, then what is the plan to solve this issue for v3?

It will be almost the same, just at gRPC layer.

@xiang90 I have a question about non quorum read in v2 protocol. Will it provided in v3?
It is important for auth, because the non quorum read allows stale read result but improve performance. It is hard to integrate such a functionality with auth. Because auth information should also be stored in the raft storage and checking the information in consistent manner will sacrifices the benefit of the stale read.
IIUC, the lease mechanism can provide consistent and low cost read in v3. Therefore non quorum read will not be required. It is an important point of the new auth mechanism so I want to confirm it first.

@mitake v3 enabled q-read by default. https://github.com/coreos/etcd/blob/master/etcdserver/etcdserverpb/rpc.proto#L121-L126

@xiang90 I didn't notice the flag, thanks!
Because of the reason I described in the above, it is difficult for non quorum read to coexist with the auth mechanism. For simplicity, rejecting non quorum read when auth is enabled would be safer. Is it acceptable?

Because of the reason I described in the above, it is difficult for non quorum read to coexist with the auth mechanism. For simplicity, rejecting non quorum read when auth is enabled would be safer. Is it acceptable?

As we discussed:

admin should first blacklist all requests and then add role/perms to whitelist.
auth is not designed for frequent role/perm changes.

What you mentioned might make sense, but it is not what we want to ensure with from the very beginning.
If you have a specific use case that requires it, please share it with us. Then we can reconsider it.

admin should first blacklist all requests and then add role/perms to whitelist.
auth is not designed for frequent role/perm changes.

Should these restriction of operation be introduced in v3, too? I thought

the auth API management API should always return the detailed view of roles and users.

means the inconsistent state isn't allowed in v3. Am I misunderstanding?

@mitake to be clear, does this describe the auth problem?

A requests role change to deny B's access to "k"; quorum
A receives role change response; revision = n
B requests data for "k", non-quorum
B receives data for "k"; revision < n

@heyitsanthony yes. I'm thinking about the case you described.

@mitake OK, is there a threat that's handled with consistent auth? I don't think it fixes stale reads. For example, B can still set up a proxy that watches on "k" which would serve a stale "k" even after the access denial goes through.

@heyitsanthony of course proxies will introduce a chance of inconsistency. But I don't understand how proxy will interact with other features in v3 protocol (it will be redesigned for v3, right? https://github.com/coreos/etcd/issues/4318).
I was thinking that lease and watch provide consistent client side caching for improving read performance. Therefore I still don't understand the benefit of serializable range in v3. So I'd like to separate it from the auth problem at first.
Of course I might be missing something. I'm happy if you could point out my misunderstanding kindly :)

@mitake I was talking about a rogue proxy with B's credentials which ignores auth. My point is that any data available prior to the denial revision is already as good as leaked to the client; read consistency with auth can't take it back.

@heyitsanthony OK, I understand your point, thanks for your explanation. It seems reasonable because newly created values (after enabling auth) cannot be read without auth. The commit message of auth enabling must be received by followers' state machine before arrival of the newly created values (I needed a time for understanding it, sorry!).
I have a next question (sorry for frequent questions): if v3 auth provides per connection auth (as described in the first message of this issue), the inconsistent state would be matter because even once a connection is authorized, it will be invalid after auth configuration change. How should we provide the efficient auth mechanism?
I'm thinking that using authentication mechanism of gRPC (as current implementation does) and letting messages from clientv3 have permission information (user ID, password) would be the simplest way. Permission check is done at every read write request processing by etcd servers. Is it ok, @xiang90 ?

@xiang90 @heyitsanthony I'm writing a design doc for the v3 auth and ACL here: https://docs.google.com/document/d/1Zs5lc4H8kHr4sgoniKlL6YRsLKFNy8m-1pyGhkCmmO4/edit?usp=sharing
I'm really glad if you can review and comment on it.

@mitake took a look, left some comments. Thanks for taking the time to write the doc.

@xiang90 @heyitsanthony thanks for your comments on the doc.
It seems that the consensus on the design is almost achieved. I'd like to have a clear consensus on this point:

every request requires permission check
a leader node checks permission for linearizable read and write
both of leader and followers check permission for non linearizable read

Is this ok for you?

@mitake Authentication per connection. Re-Authentication when the password of a user is changed.

@xiang90 yes, I agree with your points. How do you think about the design of the permission check?

@xiang90 @heyitsanthony updated the doc for a plan of implementation. Could you take a look?

@xiang90 listed RPCs in the doc. Could you review? Can I start implementation?

@mitake RPC looks good. Let's write the proto and send a pull request?

@xiang90 thanks, I'll send a PR later.

It seems to me that it's only possible to set a plaintext passwords via API v2. Is that correct? If so, I propose to allow setting passwords using hash.

@rominf Even in v2 API, passwords are stored in etcd store after hashing. Do you want to hash passwords in client side?

@mitake Yes, I do. I'm talking about changing:
Change password
PUT /v2/security/users/charlie/password

Sent Headers:
    Authorization: Basic <BasicAuthString>
Put Body:
    {"user": "charlie", "password": "newCharliePassword"}
Possible Status Codes:
    200 OK
    403 Forbidden
    404 Not Found
200 Headers:
    ETag: "users/charlie:<tzNow>"
200 Body:
    JSON user struct, updated

to
Change password
PUT /v2/security/users/charlie/password

Sent Headers:
    Authorization: Basic <BasicAuthString>
Put Body:
    {"user": "charlie", "password": "newCharliePassword"}
    OR using SHA512 hashed with salt password:
    {"user": "charlie", "password": "$6$ke3amfbPHV0WalYF$df2lVawKuP4gc.gpZuGMlmA27R4bvuKgf.YO/0bRR1tQZEIQ1kpXVxPmQyZ31.ieGFuJvU7UtXyibVRZtGamT/"}
Possible Status Codes:
    200 OK
    403 Forbidden
    404 Not Found
200 Headers:
    ETag: "users/charlie:<tzNow>"
200 Body:
    JSON user struct, updated

@rominf I understand. @xiang90 @heyitsanthony how do you think about the idea of client side password hashing? I think it is reasonable.

@mitake I'm not sure if it really improves security; the hashed password can still be used in a replay attack unless the server provides a nonce for the hash salt.

What's the purpose of of nested dictionary for permissions? Why:
 { "role" : "fleet", "permissions" : { "kv" : { "read" : [ "/fleet/" ], "write": [ "/fleet/" ] } }, "grant" : {"kv": {...}}, "revoke": {"kv": {...}} }

but not:
 { "role" : "fleet", "permissions" : { "read" : [ "/fleet/" ], "write": [ "/fleet/" ] }, "grant" : {...}, "revoke": {...} }

?

@xiang90 @heyitsanthony I'd like to use JWT (https://jwt.io/) for the token of v3 auth. JWT seems to be a simple and mature token format. In addition, it enables verifying tokens based with the RSA key mechanism. So it would be friendly for the new proxy of v3 API. Proxies will be able to verify requests from clients, it would be a great help for reducing read traffic.
I'd like to have a consensus about using JWT (it will introduce a new vendor). Can I hear your opinion?

@mitake What do you want to put inside JWT? What benefits JWT will bring us in our use case besides proxy (Proxy should either terminate TLS/Auth or just be transparent in my opinion)? I would image a simple obscure random token will do the work.

@xiang90 The main benefits from JWT are like below:

It can provide a signed token that cannot be created illegally. So the token is helpful for protecting data from malicious or buggy clients. At first I also thought random token would be enough for the purpose (as described in the doc). However, it is hard to analyze how much randomness is required for preventing the problems of the malicious or buggy clients. JWT is built on proven technique, so using it is safer than using ad-hoc my own solution.
With JWT, a server can verify a token sent from a client with its RSA public key. If proxies share a common key with servers, proxies can verify requests from clients by themselves. It will contribute to reducing get request traffic from proxy to server (the most important feature of proxy I think).

It can provide a signed token that cannot be created illegally. So the token is helpful for protecting data from malicious or buggy clients. At first I also thought random token would be enough for the purpose (as described in the doc). However, it is hard to analyze how much randomness is required for preventing the problems of the malicious or buggy clients. JWT is built on proven technique, so using it is safer than using ad-hoc my own solution.

As long as the token space and sign key space are the same, I feel the problem is pretty much equivalent unless when you have a significant amount of tokens compared to the token space . A client can guess a token, and a client can guess a sign key too.

With JWT, a server can verify a token sent from a client with its RSA public key. If proxies share a common key with servers, proxies can verify requests from clients by themselves. It will contribute to reducing get request traffic from proxy to server (the most important feature of proxy I think).

This is the benefit I could see since JTW actually provides since it contains the auth info and the info verifiable by both parities.  However, the proxy issue you mentioned is different from what we are trying to solve right now. Token Invalidation can be complicated. I feel we should first finish the simplest solution. Then we can explore more about a better token mechanism.

A client can guess a token, and a client can guess a sign key too.

JWT's token space is limited with RSA based sign. So guessing it is harder than just a random number.

Token Invalidation can be complicated.

JWT allows tokens to have various metadata. So we can let the a token to have a revision of storage when its client was authorized. We can check the authentication is obsolete or not based on the numbers. It doesn't require a heavy invalidation mechanism.

I feel we should first finish the simplest solution. Then we can explore more about a better token mechanism.

Actually I want to use JWT for simplifying auth package without reinventing the wheel. My handmade token mechanism will make the package bloat and it will be abandoned in the near future. Using well designed and reviewed methodology will make the package simpler and will minimize API change, I think.

Actually I want to use JWT for simplifying auth package without reinventing the wheel.

What does JWT provide use than a obscure token right now?

My handmade token mechanism

I feel it should be just a getToken method that randomly generate a fixed length token. It wont take a lot of effort and it allows us to evaluate what the token should be in the future aside from the auth implementation.

JWT's token space is limited with RSA based sign. So guessing it is harder than just a random number.

I mean the attacker can guess the private key of the RSA anyway. I do not feel there is a big win. A long enough true random token would be equally safe.

JWT allows tokens to have various metadata.

By invalidation, I mean at proxy side. If we do not want the token to have any meaningful information to be validated against, then we do not need JTW.

OK, then I'll implement the simple methodology first. Anyway, it would be useful for easy trial that doesn't require public/private keys.
But,

I mean the attacker can guess the private key of the RSA anyway.

I don't think this is a realistic assumption. It would mean public key encryption methodologies cannot be used. And the random number methodologies always have a problem of exhausting entropy in machines.

@mitake ACLs seem to be a part of the v3 auth design (they're already documented as a feature on the etcd home page!), but I don't think they're yet implemented -- correct me if I'm wrong. Is there a timeline for that part of the implementation? We'd really like to make use of path-based restrictions on users.

Hi @aarondav , thanks for your interest. As you found, the feature is already implemented in v2 API. We are working on auth and ACL in v3 API. The feature of v3 API will be finished in May. Will you use v3 API? If so, could you wait for a while? I'll let you know about the progress.
Just curious: will you use etcd in Spark?

Ahh, gotcha! Great, didn't realize that distinction between the v2 and v3 APIs.
We are actually using etcd via flannel in Kubernetes, and are experimenting with an architecture with multiple isolated networks sharing the same etcd, which requires that each network has access to only its sub-tree of etcd.

@aarondav I see, thanks. Flannel seems to be using v2 API, so you can use the feature with etcd v2.3.0 or newer.

@mitake Anything left here for 3.0? Or we can close it?

@xiang90 yes, though there are still remaining tasks e.g. jwt token and handling revision, the basic functionalities are already implemented. I agree to closing it.

@mitake Probably create issues for the things we want to do for the next steps: jwt + revision in token.


Integrate CodeClimate for Test coverage and code analysis

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Get client program working, add --wait option.

Get client program working by adding missing modules, removing browser
subcommand (doesn't make sense for this jobs-only server), updating
default port.
Also add --wait argument that can be used with run --path to get
immediate output instead of getting the output over the websocket.
@go-oleg @VladVega @demmer

lgtm


Create block header validation rule for CMS on extraData field

Description

When running on PKI-enabled mode, when validating the block header, the node must check if the CMS message is present in the extraData field (reject empty CMS messages).
The node should not validate the CMS content as part of the header validation, it should just check if it exists.

We can use the factory QbftBlockHeaderValidationRulesetFactory to conditionally add the rule when PKI is enabled.

This isn't needed as the block can’t be created with an empty CMS due the CMS validation in the payload validation rule. And the CMS can’t be changed after the block is proposed as it is now included the block header hash.


Support Changing Method Inflectors

We should be able to support changing the method Inflector to use.
tactician:
    default:
        method_inflector: "tactician.handler.inflector.handle"

So this actually needs to be on the top level, so:
tactician:
        method_inflector: "tactician.handler.inflector.handle"

Currently it's not possible to specify a custom inflector. As this feature is implemented at a Service Container extension level, it can only see its own registered services.
https://github.com/thephpleague/tactician-bundle/blob/master/DependencyInjection/TacticianExtension.php#L70
So then it's only possible to change the inflector strategy by one defined by the bundle. In order to be able to define a custom inflector strategy provided by other bundles I think this should be moved from the bundle extension to a compiler pass.
If you're OK with this, I can do it myself and open a PR.
Thanks!
Christian.

That would be great! @rdohms and I are both at a conference this weekend so
we might be a little slower responding but a PR would be excellent :)
On Jun 26, 2015 11:48 AM, "tλeUniC"<EMAIL_ADDRESS>wrote:

Currently it's not possible to specify a custom inflector. As this feature
is implemented at a Service Container extension level, it can only see its
own registered services.
https://github.com/thephpleague/tactician-bundle/blob/master/DependencyInjection/TacticianExtension.php#L70
https://github.com/thephpleague/tactician-bundle/blob/master/DependencyInjection/TacticianExtension.php#L70
So then it's only possible to change the inflector strategy by one defined
by the bundle. In order to be able to define a custom inflector strategy
provided by other bundles I think this should be moved from the bundle
extension to a compiler pass.
If you're OK with this, I can do it myself and open a PR.
Thanks!
Christian.
—
Reply to this email directly or view it on GitHub
https://github.com/thephpleague/tactician-bundle/issues/3#issuecomment-115615009
.

Are you sure a custom compiler pass is the best solution here? Since the problem that I see is that the $container->has should not be used since the DI compile step will take care of checking if the service exists.
So currently I see one bug in this issue and one enhancement.

The bug being a unneeded en disrupting container has service check (mentioned by @theUniC)
The enchantment being that [method_inflector](https://github.com/thephpleague/tactician-bundle/blob/adad4ce89371b18997519bbc9580f45a8e43ba59/DependencyInjection/Configuration.php#L56) should be moved to [commandbus.<name>.method_inflector](https://github.com/thephpleague/tactician-bundle/blob/adad4ce89371b18997519bbc9580f45a8e43ba59/DependencyInjection/Configuration.php#L31)

Personally I see no reason for a compiler pass.

Agreed. Indeed a CompilerPass for this is unnecessary and it would just be a matter of removing the check.

Closed by #15


Bump MSRV to 1.40.0

memchr-2.4.0 used non_exhaustive, which is only available from 1.40.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @reitermarkus (or someone else) soon.
Please see the contribution instructions for more information.

Thanks for this PR! Annoyingly it seems like object now requires 1.42... it's kind of a shame the ecosystem never really worked out whether an MSRV bump should require a semver-breaking release but it sure makes it harder for us to make these promises.
I guess try 1.42 and see if the CI passes, or you could run it locally with something like rustup install 1.42.0 and then cargo +1.42.0 build.

Thanks @adamgreig. I build locally with 1.42 this time as you suggested. Fortunately it built this time.

Looks like the workflow file itself is still on 1.40.

Oops, looks like didn't save one of the files, sorry. Pushed again. This time for sure!


Convert native compile/link tasks to be parallel by default

Use internal APIs to make compile/link tasks safely parallel by default.
Test cases:

Link executable tasks execute in parallel by default
Link shared library tasks execute in parallel by default
Create static library tasks execute in parallel by default

PR: https://github.com/gradle/gradle/pull/2628
Note that I'm going to pull making install tasks parallel out into a separate story.  That work is sufficiently different (and this story is big enough as is) that I think it warrants being handled separately.

New PR for this: https://github.com/gradle/gradle/pull/2656
Much simpler with @adammurdoch's recommendations.  Note that the problem with #70 needs to be fixed before this should be merged, but the changes for that should not have an effect on these changes at all, so it can be reviewed as is.

Also, with the simpler approach, it's actually simpler to just make all compile/link tasks parallel rather than treat them as separate stories.

@eljobe This shouldn't be closed - it's still under review.  I'm assuming this was closed due to some confusion around moving issues around and not on purpose, so I'm going to reopen it.

This has been merged.

Don't forget release notes. This is a really fantastic improvement and our first parallel by default tasks.

How do I disable the added parallel support. Upgrading from gradle 4.1 to 4.6 has almost doubled my compile times, and profiling shows most of this is from the parallel compilation. I can't find a way to disable this, and there really needs to be.

@ThadHouse This only restored behavior that was lost in Gradle 4.0-4.1 and refers to parallel compilation/linking within a project.  Native compile/link tasks have always been able to run in parallel from separate projects.
I suspect you may be actually seeing #502, which is something we've been chipping away at since a performance regression was introduced in 4.3.  You can probably confirm this by building a subset of your build with 4.1 and 4.6 (or 4.7-rc-1) with --max-workers=1.  This disables all parallelism essentially. If you still see a large difference, you're probably seeing the same problem.


Fix form markup on the 'Frame Source' popup

As pointed out by @stuartnelson3.

looks good :+1:
will merge once tests pass


Single-command install / depend on watchexec automatically

To make v5 installable properly using the normal cargo install cargo-watch, we probably need to figure out how to either:

embed watchexec (preferred, as it will make sure we don't break if watchexec's interface changes)
install watchexec as a dependency

This is an exciting development. If there's any way I can help please let me know.

This is now ready to release as soon as we watchexec's next release get onto crates.io :)

This is up on crates.io now as 1.8.1.
One caveat: because watchexec is an app first and foremost, it will be hard to continue to evolve and guarantee I won't break semver via changes to to Args. Thus, in your shoes, I'd pin it to an exact version and bump it only as necessary. (I'm not looking to break the Args struct anytime soon, mind you.)

No problem :) I'll tighten the version specifier, the advantage of this
method of embed is also that I can bind to versions tightly.
On Thu, 27 Apr 2017, 02:26 Matt Green<EMAIL_ADDRESS>wrote:

This is up on crates.io now as 1.8.1.
One caveat: because watchexec is an app first and foremost, it will be
hard to continue to evolve and guarantee I won't break semver via changes
to to Args. Thus, in your shoes, I'd pin it to an exact version and bump
it only as necessary. (I'm not looking to break the Args struct anytime
soon, mind you.)
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/passcod/cargo-watch/issues/65#issuecomment-297425366,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJgi7D7rXKsqxCDPbschgNtio_i-ukbks5rz1QEgaJpZM4NFQKN
.

Done in 5.0.0.

Note: you'll want to bump to watchexec 1.8.3 to avoid a dumb bug relating to file changes being triggered in .git dirs that 1.8.1 had.

Ah, that's not really an issue given I build my own Args — I'd already added .git ignoring — but ooops, I just noticed a bug/typo with that commit, so I'll fix that.
(Also, you can avoid repetition by using format!("*{s}.git{s}*", s=MAIN_SEPARATOR)