fix: #411

Hi everyone 👋
This PR aims to fix #411.
The solution is simple: instead of compiling all the exposed components together, I compile them one at time writing the output in a dedicated folder.
To avoid collision with the component name, the entry definition of the federated module will be 'index.d.ts'.

Just want to make sure that after compilation, the output structure in @mf-types continues to match the structure defined by the keys in the remotes config.
That way, the consumer of the types still gets type auto completion when using the paths tsconfig option

@hongkiulam That's my same objective!

@ilteoood I'm afraid the change doesn't work for all cases

The compiler seems to infer a root dir based on the import's that occur from the entry point, and in my case it meant that my index.d.ts no longer correctly points to the compiled FooterComponent file.
Also, with the individual compilation there is a lot of duplication of types :/
This is probably again a symptom of treating the exposes files differently and outputting to different locations

Hey @hongkiulam can you post a repro for this?
Without tests is hard to fix this plugin. Any help is appreciated!

@ilteoood I think you will get a similar issue if you expose as './component/button': './src/components/button'

I had also worked on fixing this earlier this week but it's not complete - https://github.com/module-federation/universe/pull/451. Let me know your thoughts :)

Let me know when there's a pr that's working as needed. Then I'll merge and release

closing this as PR #451 addresses fixing the same issue.


Switch to the new Docker Github action in Meshery-linkerd repo

Description
Since last Monday (7th October 2019) the default Docker GitHub action stopped working because the repo was deleted. We have migrated to a different docker GitHub action in the Meshery repo.
We need to replace the entire Docker block in Meshery-linkerd repo's https://github.com/layer5io/meshery-linkerd/blob/master/.github/workflows/ci.yml file with the one from the Meshery repo (https://github.com/layer5io/meshery/blob/master/.github/workflows/ci.yml).
Here is the snippet from the Meshery repo which we want copied over:
https://github.com/layer5io/meshery/blob/82018c54539f3d79eb639109b7c7cf6f67e41b2b/.github/workflows/ci.yml#L139-L173
Here is the snippet which needs to be replaced:
https://github.com/layer5io/meshery-linkerd/blob/f14311abb52ecd9e97590531674e5f65084dde8d/.github/workflows/ci.yml#L106-L158

Already resolved in commit 1588d704f95cfccedca157dc8e5930376c733e57

@girishranganathan let's move this series of issues to their respective repos.


Input Component

Design
Figma Design Document
Implementation
General usage example:
<Component>Example</Component>

Rules
Put some rules about how this component should behave and implemented

Rule 1
Rule 2

API Reference:
Component component
Description
Properties

Property
Description
Default Value

attr (string)
attr desc
-

hello, this issue has been made before.
See: https://github.com/Trendyol/baklava-react-native/issues/13


[SPARK-7619][Python] fix docstring signature

Just realized that we need \ at the end of the docstring. @brkyvz

LGTM

Merged build triggered.

Merged build started.

Test build #32741 has started for   PR 6161 at commit e44495f.

Test build #32741 has finished for   PR 6161 at commit e44495f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

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

Merged build finished. Test PASSed.

Merged into master and branch-1.4. Thanks!


NameError: name 'event' is not defined

When i try to run pygame script it returns a error...
Error only occurs when using hydrogen
---------------------------------------------------------------------------
NameError                                 Traceback (most recent call last)
<ipython-input-1-9b588b7979ea> in <module>
----> 1 event.wait()  # Vai esperar o evento anterior music.play terminar para encerrar o programa

NameError: name 'event' is not defined

My Script:
from pygame import event, init, mixer

mixer.init()  # Inicizaliza o mixer do pygame (Precisa ser inicializado antes dos outros módulos)
init()  # Inicizaliza todos os módulos carregados do pygame
# Linha de comando para carregar o arquivo de áudio
mixer.music.load('./marooned.mp3')
mixer.music.play()  # Função para reproduzir a musica que foi carregada acima
event.wait()  # Vai esperar o evento anterior music.play terminar para encerrar o programa

You aren't importing according to the documentation.

The pygame package represents the top-level package for others to use. Pygame itself is broken into many submodules, but this does not affect programs that use pygame.
As a convenience, most of the top-level variables in pygame have been placed inside a module named pygame.localspygame constants. This is meant to be used with from pygame.locals import *, in addition to import pygame.
When you import pygame all available pygame submodules are automatically imported. Be aware that some of the pygame modules are considered optional, and may not be available. In that case, pygame will provide a placeholder object instead of the module, which can be used to test for availability.

https://www.pygame.org/docs/ref/locals.html#module-pygame.locals


Update README.md

Using the term executor may get the github removed

Github will not remove any project unless it is acting as an immediate threat to some entity. Many tools that can be used illegally are on GitHub, so are many cracking tools, cheats, and leaks.


Added CleanCode and Ruby Book

What does this PR do?
Add Resource(s)
For resources
Description
Books related to software archtecture and Ruby Language
Why is this valuable (or not)
It is important for everyone who's looking for a better understand
How do we know it's really free?
It was provided in my university group of study.
For book lists, is it a book?
Yes
Checklist:

[X] Not a duplicate
[X] Included author(s) if appropriate
[X] Lists are in alphabetical order
[X] Needed indications added (PDF, access notes, under construction)

Hi, we don't host books here.


[question] mini dsl

hi,
I started writing a REPL tool that uses expr for evaluating each entry.
Each entry expression is using/calling Go structs and functions but I want to allow a different syntax for calling functions. Currently, functions need to be exposed (Upcase) and when no arguments are expected, a function call require open/closing brackets to write.
For example, I would like to evaluate this
x.foo.bar

as if it was written using Go syntax like this
x.Foo().Bar()

pre: method Foo exists on x and method Bar exists on the result type of Foo.
I see a few approaches to work on (in a fork?):

add callback function to allow the resolving of unknown fields
make the program return Error objects with information such that an entry can be rewritten
some aliasing feature, e.g. MapFieldToMethod(new(X), "foo", "Foo")

Thoughts?

Hi,
This is a really strange syntax for calling func: x.foo.bar. But if you want to do it anyway I think the best way is to do some patching of AST. Here is an example:
https://github.com/antonmedv/expr/blob/master/compiler/patcher.go
You can find more examples of patching here:
https://github.com/antonmedv/expr/blob/master/optimizer/in_range.go
Use visitor to traverse AST, find property accessor node, replace with the corresponding call method.

Also you can use Reflection to determine correct method names and so on.

Thank you for responding to my question.
I started working with your suggestion to create a patcher.
In order change a step in the Compiler process, I need to decompose the expr.Compile.
First, I created a new function in my package to compile a parser.Tree with this signature
func Compile(tree *parser.Tree, ops ...expr.Option) (*vm.Program, error)

However, because the definition uses the internal/conf package, this does not work.
I prefer not to fork your package so do you see a way for me to make it work? What about adding this to expr:
func BuildConfig(ops ...expr.Option) (*conf.Config, error)

and then I can have
func Compile(tree *parser.Tree, conf *conf.Config) (*vm.Program, error)

hmm , still would not work because I cannot import expr/internal/conf

Yes, I see. This internal package was a bad idea. I think to remove it at all. Make conf a top-level package.

@emicklei I've creaded small PR with new functinality what actially may help.
https://github.com/antonmedv/expr/pull/99

Released in v1.7.0. Now it should be easy to implement your dsl.


Overwrite MARKER_CLICK animation event to another position

I'm submitting a ...

[x] question
[ ] any problem or bug report
[ ] feature request

If you choose 'problem or bug report', please select OS:

[x] Android
[x] iOS

cordova information:
cordova-plugin-googlemaps 2.3.5 "cordova-plugin-googlemaps"

If you use @ionic-native/google-maps, please tell the package.json (only @ionic-native/core and @ionic-native/google-maps are fine mostly)
"@ionic-native/core": "^4.7.0",
"@ionic-native/google-maps": "^4.8.2"

Current behavior:
I'm showing a map card when you click on a marker and the map view is centered in the middle of the screen. Is there any chance to change this behavior and move the screen to another position?
Like a little higher and that the marker is not exactly in the center.
I tried to do that:
markerCluster.on(GoogleMapsEvent.MARKER_CLICK).subscribe( (params) => {
        map.animateCamera(...);
});

But it doesn't behaves as expected, because the camera do an strange movement.
If you have any doubt, let me know.
Thank you.
Screen capture or video record:

https://github.com/mapsplugin/cordova-plugin-googlemaps-doc/blob/master/v2.3.0/class/Marker/README.md#disable-auto-pan

Thank you it's perfect for me. You can close the issue.


There may be issues with selecting multiple coordinates

Thank you for your question. I will fix it as soon as possible

When you select multiple objects, the ruler will not be displayed as one object. Only after combining and synthesizing, there is no logical problem and it will not be fixed


With inference_examples_DICOM.ipynb, it hits: AttributeError: module 'PIL.Image' has no attribute 'LINEAR'

Image.LINEAR is used at:
at https://github.com/MaureenZOU/detectron2-xyz/blob/42121d75e10d9f858f3a91b6a39f5722c02868f0/detectron2/data/transforms/transform.py#L46
it shall be Image.BILINEAR at:
https://github.com/facebookresearch/detectron2/blob/c69939aa85460e8135f40bce908a6cddaa73065f/detectron2/data/transforms/transform.py#L46
Shall https://github.com/MaureenZOU/detectron2-xyz sync with https://github.com/facebookresearch/detectron2 to get the fix:
https://github.com/facebookresearch/detectron2/commit/ff53992b1985b63bd3262b5a36167098e3dada02
I am using https://github.com/facebookresearch/detectron2 for now and the example works.

Thanks for the feedback! The two packages should produce the same model output. The xyz version was adapted from the original facebook version in SEEM, and we used that version for model development. For that reason we keep using this version for consistency. However, we also observed that sometimes one version works on some environment but not others. If the original facebook version works for you then please feel free to use it for your environment. If there is any change that causes continuous dependency problem we will consider changing to the facebook version.

Thanks. I am closing this issue because it is not a blocker.


Fix query failed because of migration

What type of PR is this：

[x] bug
[ ] feature
[ ] enhancement
[ ] others

Which issues of this PR fixes ：

Fixes #5160
Problem Summary(Required) ：

fix query failed because of migration

run starrocks_be_unittest

run starrocks_be_unittest

run starrocks_be_unittest


Html-Formatter file size and inclusion of excluded features

Summary

The new react html formatter includes all features/scenarios/ect in the folder. Even the ones not run because they were excluded by eg. tags
Expected Behavior
A switch or an option would allow you to not include files that were excluded from the run in the html report
Current Behavior
Every feature is included in the report
Possible Solution
A way to not include the files that weren't part of the test run
Context & Motivation
The old html reports were relatively tame in size. The new formatter outputs 15 MB reports from my test collection

In addition, maybe cucumber reports published is not working because of that issue.


WIP Custom Executor Spec

This is a WIP spec for Cook's imminent custom executor.

How does the executor work in relation to running with docker?

How are we going to pass info from executor to cook scheduler? Framework messages? http requests directly to scheduler?

Re: Docker... if a docker container is specified for a job, the executor is launched in that container. This means the container should have python.

Re: passing info from executor to the scheduler... right now, the only information we're sending back to the scheduler (progress, custom failure reason) can be put into the data field of the TaskInfo structure. This has the desirable property of keeping the executor completely decoupled from the scheduler.

Re: Docker... if a docker container is specified for a job, the executor is launched in that container. This means the container should have python.

Does that mean that the executor must be included in the container and that the executor will be tied to the code running?

Does that mean that the executor must be included in the container

No, the agent should download it from a uri on the task before the Docker containerizer mounts it inside the container and runs it.


Attribute(s) Selection

User Story
As a user, I would like to be able to choose the attribute(s) I want so that I may get the data I desire in an excel sheet.
Detailed Description
After selecting the object they want (as in #5 ), user should then get a page that gives them a selection of different attributes that vary depending on what object they chose. They can choose as many attributes that they want. After this, the wizard should go to #7
Acceptance Criteria

[x] Given user has selected an object, then wizard should display a selection of different attributes, along with text that reads "Please choose the Attributes you want from the list below".
[x] Given user selects an attribute, then there should be a text box next to the attribute that allows user to enter an alternate label for the attribute, as well as text that says "If you would like an alternative label, please enter it here".
[x] Given user goes to this page, then there should be a Next button and a Back button near the bottom:

[x] If Next is clicked, go to #7
[x] If Back is clicked, go to #5

Tasks

[x] #50
[x] #51
[x] #52
[x] #53
[x] #54

Done.


change colorCoords variable to vertexColors

vertexColors makes more sense as a variable than colorCoords

Could you also change tanCoord to tangents and uvCoord to either uvs or textureCoords ?

Done


Personal Hole Notes not showing

the personal hole notes do not seem to be displaying all the time.  It seems to be somewhat random when they are visible versus when they do not show up.  I am using Chrome and logging in with a Google Account.  The notes seem to be saving as when I open on my mobile device they appear, but they are not coming up on the same browser that I created the notes from.

I haven't been able to recreate the issue yet but will investigate later when I have some more time. Let me know if you have any more insight into recreating the problem!


Adding Java runtime.

Closes #93
@jthomas - Okay, here is my attempt at adding the Java runtime. Apologies if there are some obvious NodeJS coding issues. Just let me know what you want altered.
I installed it locally and pushed up a simple Java action and was able to call it.

Codecov Report

Merging #94 into master will increase coverage by 0.2%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master      #94     +/-   ##
=========================================
+ Coverage    83.9%   84.11%   +0.2%
=========================================
  Files          40       41      +1
  Lines        1373     1391     +18
  Branches      276      277      +1
=========================================
+ Hits         1152     1170     +18
  Misses        221      221

Impacted Files
Coverage Δ

compile/functions/runtimes/index.js
100% <100%> (ø)
:arrow_up:

compile/functions/runtimes/java.js
100% <100%> (ø)

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 419af45...9e92795. Read the comment docs.

@allen-servedio Fast work on getting this implemented!
I'll code review tomorrow and let you know if I find anything.
Can you add docs to the README for Java support? Follow the style here:
https://github.com/serverless/serverless-openwhisk#writing-functions---php
Once this is ready, we should drop a PR to the main framework project. This will include adding docs which get imported on hosted on their site, a template project for the Java runtime and examples in the serverless/examples project to show people how to use it.
Thanks again for doing this! Congrats on the first PR to this project. Since you know you're way around the code-base now, feel free to open issues and send PRs for other stuff you find!

Okay @jthomas, pushed the docs (sorry I missed them initially). Let me know what changes you want and generally what you want in the PR for the examples, etc...

This PR is looking really good - great doc updates!
Everything looks fine apart from a small change to how we define the main to be consistent with the other runtimes. If you can get that done, I'll merge this and work on a new release to get this great change out asap.
Thanks for the work on this 👍

This looks perfect, thanks for the changes. I'll make a note to get a release out with this in soon.


[RangeInfo] When reporting referenced decls in a given range, exclude those referenced as members.

@swift-ci Please smoke test and merge


Add support for distinct package namespaces

What does this PR do?
Add Distutils support for wheels with multiple top level packages.
Why was it initiated? Any relevant Issues?
Address #571, #527, and makes a compromise for #530
PR Checklist

[x] Correct base branch selected? develop for new features and bug fixes too.
If it's part of a hotfix, it will be moved to master during it.
[x] All tests still pass. Check the developer manual about Running the Tests.
There are Travis tests that cover the most important things however, and you
are welcome to rely on those, but they might not cover enough.
[x] Ideally new features or fixed regressions ought to be covered via new tests.
[ ] Ideally new or changed features have documentation updates.

@kayhayen The current script passes all test cases in distutils (including the new one I added). I also ran some tests in PyPI-pytest and everything seems to work fine. Please let me know if my example test case is wrong.

Updated, still passes all test cases in distutils

@kayhayen Can you review this some time :)


Errors seen in the nginx controller logs Failed to update lock: configmaps "ingress-controller-leader" is forbidden

Rancher Server Setup

Rancher version: v2.6-head 96e2438
Installation option (Docker install/Helm Chart): Docker install

If Helm Chart, Kubernetes Info: k3s
Cluster Type (RKE1, RKE2, k3s, EKS, etc):
Node Setup: 1 node
Version: v1.22.3+k3s1

Proxy/Cert Details: self-signed

Information about the Cluster

Kubernetes version: v1.22.3
Cluster Type (Local/Downstream): Downstream custom 2 worker, 1 etcd, 1 cp RKE1 custom cluster

Describe the bug
Error logs are seen flowing continuously in the nginx-controller pod logs in the downstream clusters created on k8s v1.22.3
To Reproduce
Create a downstream cluster on k8s v1.22.3
From the explore cluster --> nginx-controller daemon set in the namespace ingress-nginx  verify the logs on the pods
Result
Following logs are seen continuously for every few seconds:
E1117 23:44:55.988115 7 leaderelection.go:361] Failed to update lock: configmaps "ingress-controller-leader" is forbidden: User "system:serviceaccount:ingress-nginx:ingress-nginx" cannot update resource "configmaps" in API group "" in the namespace "ingress-nginx"
Wed, Nov 17 2021 3:45:09 pm | E1117 23:45:09.500147 7 leaderelection.go:361] Failed to update lock: configmaps "ingress-controller-leader" is forbidden: User "system:serviceaccount:ingress-nginx:ingress-nginx" cannot update resource "configmaps" in API group "" in the namespace "ingress-nginx"
Wed, Nov 17 2021 3:45:18 pm | E1117 23:45:18.416296 7 leaderelection.go:361] Failed to update lock: configmaps "ingress-controller-leader" is forbidden: User "system:serviceaccount:ingress-nginx:ingress-nginx" cannot update resource "configmaps" in API group "" in the namespace "ingress-nginx"
Wed, Nov 17 2021 3:45:30 pm | E1117 23:45:30.101453 7 leaderelection.go:361] Failed to update lock: configmaps "ingress-controller-leader" is forbidden: User "system:serviceaccount:ingress-nginx:ingress-nginx" cannot update resource "configmaps" in API group "" in the namespace "ingress-nginx"

Expected Result
Expected no error logs in the nginx controller pods.

Fix merged in RKE1, available to test after is merged in Rancher v2.6.3-rc1.

Available to test on v2.6.3-rc1

Verified on v2.6-head 4375161
Created a cluster on v1.22.3-rancher1-1 and verified no error logs mentioned in the ticket are seen from the nginx-controller


F #2940 GOCA - externalize the client and modify the way to access to the resources (Warning: breaking change)

/!\ It's an important breaking change /!\
Externalize the client
Allow to extend the client
Modify the way to access to the resources and add controller notion
Add some documentations
Migrate the tests
Improve http client configuration

OK, there is a mistake on the branch I wanted to merge, my apologies for the error, I open a new pull request here: https://github.com/OpenNebula/one/pull/3006


Add CI support for GHC 9.2

I did not consider windows issues.

so we need a newer unix-compat for windows?

Yeah, I think there is a PR for it: https://github.com/jacobstanley/unix-compat/pull/47

so time to create a cabal-ghc902.project.local with the appropiate source-repo-package and allow-newer's?

We could if we are impatient.

For now superseded by #324


chore: add infrastructure to patch latest version

This PR adds infrastructure to patch the last release. Given that this workflow releases commits that are not on master, we'll have to manually apply those commits' changes to master if the released code doesn't already exist on it.
Besides the release of the package itself, the documentation also gets updated when this scenario occurs.
closes #2245

@arboleya thanks for pointing it out! https://github.com/FuelLabs/fuels-ts/pull/2497/commits/acb4b447cbbd16437050e6a497e9464ed22a6033
There is room possible room for automation here with regards to the point

Update the package versions on master to match the released versions,

but I don't know if it's worth it. I could just comment out this condition to have the step run on all PRs and we'd catch it right away. I'd just have to add an additional check to make sure that cases where the versions don't change are handled:
OLD_VERSION=$(sed -nE 's/^\s*"version": "(.*?)",$/\1/p' packages/fuels/package.json)
pnpm changeset version
VERSION=$(sed -nE 's/^\s*"version": "(.*?)",$/\1/p' packages/fuels/package.json)
git reset --hard

if [ "$OLD_VERSION" = "$VERSION" ]; then
  # the versions didn't change so we won't be releasing it anyways
  exit 0
fi

STATUS_CODE=$(curl -s -w '%{http_code}\n' "https://www.npmjs.com/package/fuels/v/$VERSION" | tail -n1)
if [[ $STATUS_CODE  != 404 ]]; then
  echo "Release for version $VERSION already exists or curl received an unexpected result (result is $STATUS_CODE). Exiting."
  exit 1
else
  exit 0
fi

@petertonysmith94 The actual full workflow would be tested in the trenches after we merge it into master and release a new version of master. We'd then run this workflow on that release/v0.xx.x branch by doing a simple, non-breaking change and verifying that everything works as expected. :sweat_smile:
However, I tested all the added logic in the CI in isolation, e.g. #2529 for PR creation and running the bash scripts in the CI on mock data to verify that there's no failure in them.

@arboleya you're right that these scripts aren't the most readable code. I have created #2581 where we can evolve the discussion and hopefully come to a better CI workflow codebase.


Yaml configuration with map of maps

It seems that figcone has trouble handling a map of maps, e.g the following config structure
struct config_struct
{
	using auth_map = std::unordered_map<std::string, std::string>;
	using servers_map = std::unordered_map<std::string, auth_map>;
	servers_map servers;
};

Generates the following error:
In file included from /usr/local/projects/private/myproj/source/config/config_reader.cpp:5:
/usr/local/include/figcone/configreader.h: In instantiation of ‘void figcone::ConfigReader::loadField(TCfg&, TField&, std::string_view) [with TCfg = config_struct; TField = std::unordered_map<std::__cxx11::basic_string<char>, std::unordered_map<std::__cxx11::basic_string<char>, std::__cxx11::basic_string<char> > >; std::string_view = std::basic_string_view<char>]’:
/usr/local/include/figcone/configreader.h:394:19:   required from ‘void figcone::ConfigReader::loadStructure(TCfg&, std::index_sequence<Ints ...>) [with TCfg = config_struct; long unsigned int ...indices = {0, 1, 2, 3}; std::index_sequence<Ints ...> = std::integer_sequence<long unsigned int, 0, 1, 2, 3>]’
/usr/local/include/figcone/configreader.h:406:22:   required from ‘void figcone::ConfigReader::loadStructure(TCfg&) [with TCfg = config_struct]’
/usr/local/include/figcone/configreader.h:422:26:   required from ‘TCfg figcone::ConfigReader::readConfig(const figcone::TreeNode&) [with TCfg = config_struct]’
/usr/local/include/figcone/configreader.h:311:53:   required from ‘std::conditional_t<(rootType == figcone::RootType::SingleNode), TCfg, std::vector<TCfg> > figcone::ConfigReader::read(std::istream&, figcone::IParser&) [with TCfg = config_struct; figcone::RootType rootType = figcone::RootType::SingleNode; std::conditional_t<(rootType == figcone::RootType::SingleNode), TCfg, std::vector<TCfg> > = config_struct; std::istream = std::basic_istream<char>]’
/usr/local/include/figcone/configreader.h:90:36:   required from ‘std::conditional_t<(rootType == figcone::RootType::SingleNode), TCfg, std::vector<TCfg> > figcone::ConfigReader::readFile(const std::filesystem::__cxx11::path&, figcone::IParser&) [with TCfg = config_struct; figcone::RootType rootType = figcone::RootType::SingleNode; std::conditional_t<(rootType == figcone::RootType::SingleNode), TCfg, std::vector<TCfg> > = config_struct]’
/usr/local/include/figcone/configreader.h:134:40:   required from ‘std::conditional_t<(rootType == figcone::RootType::SingleNode), TCfg, std::vector<TCfg> > figcone::ConfigReader::readYamlFile(const std::filesystem::__cxx11::path&) [with TCfg = config_struct; figcone::RootType rootType = figcone::RootType::SingleNode; std::conditional_t<(rootType == figcone::RootType::SingleNode), TCfg, std::vector<TCfg> > = config_struct]’
/usr/local/projects/private/myproj/source/config/config_reader.cpp:10:53:   required from here
/usr/local/include/figcone/configreader.h:357:100: error: static assertion failed: Dict value type must be readable from stringtream or registered with StringConverter
  357 |                     detail::canBeReadAsParam<typename sfun::remove_optional_t<TField>::mapped_type>(),
      |                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
/usr/local/include/figcone/configreader.h:357:100: note: ‘figcone::detail::canBeReadAsParam<std::unordered_map<std::__cxx11::basic_string<char>, std::__cxx11::basic_string<char> > >()’ evaluates to false

Trying to parse YAML to a map with string keys and structure values fails too.
struct config_struct
{
	struct mystruct
	{
		bool myval;
	};
	std::unordered_map<std::string, mystruct> myval2;
};

The above fails again with
/usr/local/include/figcone/configreader.h:357:100: error: static assertion failed: Dict value type must be readable from stringtream or registered with StringConverter
  357 |                     detail::canBeReadAsParam<typename sfun::remove_optional_t<TField>::mapped_type>(),
      |                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
/usr/local/include/figcone/configreader.h:357:100: note: ‘figcone::detail::canBeReadAsParam<config_struct::mystruct>()’ evaluates to false

Hi, thanks. The second case seems reasonable, I'm not sure how I missed it. To think of it, it makes more sense to support it than the currently supported map of arbitrary parameters (FIGCONE_DICT). It seems that it's not impossible to implement and it should work pretty much the same as FIGCONE_NODELIST.
It's a pretty large feature though, and I'm currently not working much on side projects, so I'm not sure when I'll find time to implement it.
The first case is different, and I doubt that I will support mapping of config structure to nested containers. You can register the value type of a map as a user-defined type with StringConverter<std::unordered_map<std::string, std::string>> and implement its parsing by yourself, but I doubt that it's useful)

currently supported map of arbitrary parameters (FIGCONE_DICT)

Do you mean that currently FIGCONE_DICT supports maps where the value is a structure? Or does it require that value to always be a primitive, like std::string, int, bool, etc.?
Regarding the first case (nested containers), I have a YAML configuration which contains servers, index by server_id (string) and the config entry for each server contains a list of authentication parameters, where each server can have a different list of connection parameters.
A sample config would be:
{
    "server_1": {
        "server_1_param_1": "value",
        "server_1_param_2": "value",
        "server_1_param_3": "value",
    },
    "server_2": {
        "server_2_param_1": "value",
        "server_2_param_2": "value",
    },
    ...
}

So using two nested maps seems like a natural way to handle this kind of configuration.  The outer map has server_id (server_1, server_2, etc.) as keys and inner maps as values. The inner map has auth parameter names as keys and auth parameter values as values.
So is there a simple way to handle this kind of configuration?
For now I work around the problem by changing the config to:
[
    {
        "id": "server_1",
        "auth":
        {
            "server_1_param_1": "value",
             "server_1_param_2": "value",
             "server_1_param_3": "value",
        }
    },
    {
        "id": "server_2",
        "auth":
        {
            "server_2_param_1": "value",
            "server_2_param_2": "value"
        }
    },
    ...
]

So there is no hurry making changes to the library, for me it is good enough the way it is now. It seems more natural to use two nested maps so it would be nice to have some way to use nested maps, but the workaround that I use is fine with me too.

Do you mean that currently FIGCONE_DICT supports maps where the value is a structure? Or does it require the value to always be a primitive, like std::string, int, bool, etc.?

It doesn't need to be a primitive, but it can only be read from a simple string value, by using the registered string conversion. Here's an example based on the "User defined types" README section:
struct Host {
    std::string ip;
    int port;
};

namespace figcone {
template<>
struct StringConverter<Host> {
    static std::optional<Host> fromString(const std::string& data)
    {
        auto delimPos = data.find(':');
        if (delimPos == std::string::npos)
            return {};
        auto host = Host{};
        host.ip = data.substr(0, delimPos);
        host.port = std::stoi(data.substr(delimPos + 1, data.size() - delimPos - 1));
        return host;
    }
};

struct Cfg{
    std::map<std::string, Host> testMap;
}

{
    "testMap" : {
        "foo" : "<IP_ADDRESS>:8080",
        "bar" : "<IP_ADDRESS>:8000"
    }
}

So, with the Host structure as a map value it can't automatically parse the following config:
{
    "testMap" : {
        "foo" : {"ip": "<IP_ADDRESS>", "port":"8080"},
        "bar" : {"ip": "<IP_ADDRESS>:8000", "port":"8080"},
    }
}

but I think it's possible to add support for it in the future.
As for your example
{
    "server_1": {
        "server_1_param_1": "value",
        "server_1_param_2": "value",
        "server_1_param_3": "value",
    },
    "server_2": {
        "server_2_param_1": "value",
        "server_2_param_2": "value",
    },
    ...
}

If "server_N" and "server_N_param_N" are arbitrary, and you cannot register a structure with expected field names, then no, there's no better way than using some combination of a node list and a dictionary, like the one you ended up with.
figcone's design helps to avoid using string-based maps when you have a defined schema configuration. At the same time, this shift away from using maps for storing configuration hurts flexibility when you need to support configurations with arbitrary key names, as in your example.

If "server_N" and "server_N_param_N" are arbitrary, and you cannot register a structure with expected field names, then no, there's no better way than using some combination of a node list and a dictionary, like the one you ended up with.
figcone's design helps to avoid using string-based maps when you have a defined schema configuration. At the same time, this shift away from using maps for storing configuration hurts flexibility when you need to support configurations with arbitrary key names, as in your example.

My configuration is more complex than the example that I provided, because it has both a fixed part, which can be put into nested structures, and a dynamic part which is better suited for nested maps. The dynamic part, which in my case contains the auth data is handled by different plugins, so the main code, which parses the config, does not really know the parameter names of the auth data for each server id, so the best thing it can do is put the auth data into a std::unordered_map<string, string> and pass it to the corresponding plugin.
Anyway, thanks for the explanation. I am OK with the workaround that I use. I will leave the issue open in case you find the time to implement support for maps with string keys and structure values.


Fix tests

See the last commit here

Thanks Paul, cherry-picked https://github.com/pweil-/origin/commit/6e00cd3a2c48f3a5984c99366aabef5305855f6f into my branch.


[FLOC-2119] Temporary workaround for requests timeout

This was two bugs: some sort of race condition involving ThreadPool, and what I believe is a bug fixed in newer versions of requests (or rather urllib3 - https://github.com/shazow/urllib3/pull/520). I was never able to reproduce this bug locally, so I don't think it's worth wasting more time fighting it since it's not a bug in our code AFAICT.
Even if we do want to fix this before 1.0 I still think it's worth skipping for now so it doesn't bottleneck all our other branches with red builders.

The failing builders aren't those which are affected by the issue and I don't think that they could be caused by this change.

Thanks @itamarst . I think that if we have (manual) testing of the API endpoint examples then we can go without this test for now. Please remove the test and make sure that there is an issue which explicitly will add it back (maybe blocked by the requests-py issue) and merge, or explain why you think it is better and to have the test and resubmit.

And check that you also don't think that the failing builders are caused by this.

I left the test being skipped since there were two problems, and I wanted to include a fix for one of them. I can just file an issue pointing to that commit revision though.

I think that is better than having code which doesn't run in the repo (it is kind of like commented out code).


[Sandbox] Copacetic

Application contact emails
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Project Summary
Copacetic (copa) is a tool for patching security vulnerabilities in containers
Project Description
Copa is a CLI tool written in Go and based on buildkit that can be used to directly patch container images given the vulnerability scanning results from popular tools like Trivy.
Copa provides the ability to patch containers quickly without going upstream for a full rebuild. As the window between vulnerability disclosure and active exploitation continues to narrow, there is a growing operational need to patch critical security vulnerabilities in container images so they can be quickly redeployed into production.
Org repo URL
https://github.com/project-copacetic
Project repo URL
https://github.com/project-copacetic/copacetic
Additional repos
No response
Website URL
https://project-copacetic.github.io/copacetic/website/
Roadmap
https://github.com/project-copacetic/copacetic/issues
Roadmap context
Full roadmap is currently in development, and will be hosted on a GitHub project roadmap board. At the moment we've linked the repo's issues, as that's what we're working off of until the roadmap is finished.
Contributing Guide
https://github.com/project-copacetic/copacetic/blob/main/CONTRIBUTING.md
Code of Conduct (CoC)
https://github.com/project-copacetic/copacetic/blob/main/CODE_OF_CONDUCT.md
Adopters
No response
Contributing or Sponsoring Org
Microsoft
Maintainers file
https://github.com/project-copacetic/copacetic/blob/main/CODEOWNERS
IP Policy

[X] If the project is accepted, I agree the project will follow the CNCF IP Policy

Trademark and accounts

[X] If the project is accepted, I agree to donate all project trademarks and accounts to the CNCF

Why CNCF?
The main reason we are pursuing CNCF membership is the community. The first thing is we think that copa could add value for members of the cloud native community. Aside from that, having a strong user group can help the future success of copa through the development of third party integrations.
Benefit to the Landscape
We believe the core benefit to the landscape is helping users more quickly address security vulnerabilities that show up in their images. There isn't anything quite like Copa in the CNCF landscape today, and as the window between vulnerability disclosure and exploitation closes we think a tool like this could really help users.
Cloud Native 'Fit'
Copa best fits in under the 'Security & Compliance' section in the 'Provisioning' area of the landscape as it's primary purpose is addressing security vulnerabilities in container images.
Cloud Native 'Integration'
Copa compliments other tools in the container security space by nature of them all targeting different stages of the full lifecycle. While some tools focus on runtime, copa aims to shift security concerns left and integrate into CI/CD pipelines and find and patch vulnerabilities before deployment. Combining this with other tools in the ecosystem could lead to a good holistic vulnerability strategy.
Cloud Native Overlap
We don't think there's any strong overlap with any existing CNCF projects. The closest would be any project incorporating vulnerability scanning, but I don't know of any specific projects targeting patching.
Similar projects
N/A
Product or Service to Project separation
N/A
Project presentations
The project has been presented to the Kubernetes SIG Security Tooling subproject. There is no recording available at the moment, but I will work on getting that and add it to the open issue.
Project champions
Lachie Evenson
Additional information
No response

@salaxander it would be great if you could present Copa at a TAG Security meeting before the next sandbox vote on Sept 12.

Thanks @nikhita! I'll add it to an upcoming meeting agenda for TAG Security

Hello @nikhita and @PushkarJ ! Just wanted to check in with both of you. We completed the presentation to SIG Security on 08/16, and I was hoping to verify that we're all set for the TOC vote on 09/12.
Thanks!

Recording is here: https://youtu.be/Du7StQBCbbE?si=lwXlOqeINFliwjR8 (starts at 37:40)
@nikhita Please let us know if you are looking for anything else from STAG on this.

/check-vote

/check-vote

/check-vote

/check-vote


document public api and more

project arch
public API
config file (to do)
cli (to do)
how to contribute
FAQ
...

and also forEachChild - the visitor.

@aladdin-add It's important to document that Kataw never throw errors by default.  It has build-in error recovery and reconstruct the AST. Without the callback function as the parsers 3rd argument. No diagnostics will be seen.

@aladdin-add Not sure if there is a point in mention this in the documentation, but Kataw threats keywords differently.
For example this case let for.   In this case the for keyword isn't allowed to be part of the lexical declaration. Instead the loop breaks, and for will be parsed out as forStatement.
It's done like this because Kataw re-construct the AST in all scenarios when it does error recovery.

@aladdin-add  friendly ping. You should mention in the documentation that Kataw can parse type annotations, but differently than TS and Flow. Need to do a 'in-depth' documentation for Kataw types.

@aladdin-add
Need to mention in the documentation how to gain perf with Kataw CST nodes.
For example escaped keywords can be found in Acorn and Babel parser I guess if you are using the raw property
if (x !== x.raw) // escaped

In Kataw you can do:
if (kataw.hasUnicodeEscape(x) // escaped

If you need all Statement nodes in Acorn and Babel parser:
switch (node.type) {
case 'IfStatement': ...

// and 100 more cases
}

In Kataw you can do:
if (kataw.isStatementNode(x) // true if statement node

There are many more examples

@aladdin-add Close this? No progress last 4 months

we'll have to document some of these before release v0.1.0

Some of the .md files in various folder may give you some clues

@aladdin-add Wait with the documentation. Kataw is undergoing a huge refactoring and I'm changing it to something I had zero plans to do :(
Soon as I'm done we need to document the folder structure first.


Table component: horizontal scroll - full width does not display left-most content

In horizontal scroll - full width, if you reduce the width of your browser, you cannot see the left-most content (or right-most with RTL) even when you scroll.
https://beta.carbon-addons-iot-react.com/?path=/story/watson-iot-table--horizontal-scroll-full-width

I would assume, as user, that:

I could always scroll to see the full set of table content
It would default to being scrolled all the way left (or all the way right in RTL).

This issue is no longer present. Closing


[BUG] LoginFaild

Describe the bug
Cookies IMEI UserAgent with EdgeExtendsion
1-3 day login success
it`s error after 3 days
ErrorTip:
The session key was improperly submitted or has reached its timeout. Direct the user to log in again to obtain another key
To Reproduce
Steps to reproduce the behavior:
1 Use 3-5 days cookie
2 do zalo.login()

Did you try updating your cookies again?

expired cookies, so try get new cookies

I am wondering if Zalo's web has the ability to automatically renew cookies

I am wondering if Zalo's web has the ability to automatically renew cookies

Yes, in most cases, making a request updates the cookie. Therefore, if you're using cookies for login, ensure they are updated regularly.


Issue running devtools

Hey!  I just got my application up and running successfully w/ cerebral and tried to get the devtools to work but with no luck.  Nothing appears.  I ran the TodoMVC example successfully in the dev tool.  Further, all libs are updated when running an npm outdated command, so the FAQ suggestion didn't work for me.
The only thing different in the setup from the example TodoMVC is that I'm using react-router (we are at this point pretty code committed to this and making one change at a time :)).  Is there something with that I need to be able to use the tools?  Seems unlikely, but I'm sort of at a loss for why it's not loading.
Here's my package.json dependencies
"dependencies": {
"baobab": "2.1.1",
"baobab-react": "^1.0.0",
"cerebral": "^0.24.0",
"cerebral-baobab": "^0.4.2",
"cerebral-react": "^0.6.0",
"debug": "2.1.3",
"es5-shim": "^4.3.1",
"history": "^1.13.0",
"leaflet": "^0.7.7",
"lodash": "3.10.1",
"moment": "2.10.6",
"moment-range": "2.0.3",
"numeral": "1.5.3",
"pure-render-decorator": "^0.2.0",
"q": "^1.4.1",
"radium": "^0.15.3",
"react": "^0.14.2",
"react-addons-clone-with-props": "^0.14.2",
"react-bootstrap": "0.27.3",
"react-dom": "^0.14.2",
"react-leaflet": "^0.9.0",
"react-motion": "^0.3.1",
"react-router": "^1.0.0"
}
Any suggestions would be great!  Really also appreciate all the work you are doing around baobab and the articles that you have posted.  Spot on!
debugging edit:
The container is calling
  componentDidMount: function () {     this.props.controller.devtools.start();   },
and going into Devtools.js
  return {
    update: update,
    start: function () {
      if (utils.isDeveloping()) {
        var event = new Event('cerebral.dev.cerebralPing');
        window.dispatchEvent(event);
      }
    }

successfully w/ utils.isDeveloping() resolving to true, then dispatching the necessary events.  I do also setup my initial page by sending some signals for default state setup, so would even expect to see something in the Cerebral debugger.
and confirmed an event is firing:
bubbles: false
cancelBubble: false
cancelable: false
currentTarget: null
defaultPrevented: false
detail: "{"signals":[{"name":"pageStateChange","start":1448145412451,"isExecuting":false,"branches":[{"name":"setPageState","input":{"error":"","loading":false},"duration":2,"mutations":[{"name":"set","path":["pageState"],"args":[{"error":"","loading":false}]}],"isAsync":false,"outputPath":null,"isExecuting":false,"hasExecuted":true,"path":[0],"outputs":null,"actionIndex":0}],"duration":0,"input":{"error":"","loading":false}},{"name":"loginStateChange","start":1448145412459,"isExecuting":false,"branches":[{"name":"setLoginState","input":{"username":"","password":""},"duration":0,"mutations":[],"isAsync":false,"outputPath":null,"isExecuting":false,"hasExecuted":true,"path":[0],"outputs":null,"actionIndex":0}],"duration":0,"input":{"username":"","password":""}}],"willKeepState":false,"disableDebugger":false,"currentSignalIndex":1,"isExecutingAsync":false,"isRemembering":false,"computedPaths":[]}"
eventPhase: 0
isTrusted: false
isTrusted: false
path: Array[0]
returnValue: true
srcElement: null
target: null
timeStamp:<PHONE_NUMBER>282
type: "cerebral.dev.update"
__proto__: CustomEvent

Thanks again for help!

Hi there and so sorry for late reply!
This sounds really weird. Would you mind trying out the boilerplate, https://github.com/cerebral/cerebral-boilerplate, just to make sure it is react routers falt? :-)
There has also been an issue with debugger running on multiple pages, which has got a fix now. Just no released quite yet.

Next release is now out, should hit the chrome store very soon :)


Created mkbsd.bat, to download all the wallpapers in a single click.

Added a batch file to run the entire program just by one click in windows. It tells user if python is not installed, installs all dependencies and runs the program so that even a newbie can get access to end product.
Step:
Just clone the repository by typing: git clone https://github.com/nadimkobeissi/mkbsd in terminal/cmd go to repo location on file manager double click on mkbsd.bat and done, all wallpapers downloaded.

Brother 😂 why write a .bat script to install Python and run the script. Just write it directly in .bat.


I think it does not make sense to check coverage for next.config.js. This file is run by the frontend build, which seems sufficient.
If that file has logic in it that is complex enough to warrant testing, it should be broken out into a separate file.

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @paulmelnikow!

  Generated by :no_entry_sign: dangerJS


Suggestion for certificate handling

Hi,
Right now the server pulls the certificate with specific file names from the .signalK directory.
I suggest adding support for letsencrypt certificates and certbot for management of the certificates.
If you use certbot you will have a valid and automatically updated certificate at "the end" of a symbolic link. If you can configure signalK to use a certificate made available via a symbolic link I think this will work and make life a lot easier in terms of certificate management.
When setup this way the check of access rights to the certificate can be skipped as well.

A good idea.
What would the configuration look like? A checkbox use Certbot and text field to specify the hostname?
I have my DNS in Route 53 and I believe I have someplace poc code for a server plugin full solution that would use Certbot with DNS Challenge to update the certificate, but just offloading certificate management totally to Certbot is a better strategy.

Agree I have my DNS at one.com and renew with a DNS challenge as well.
I'm not sure and do not remember if you can influence the symbolic link, mu guess is that you cannot.
So Yes I think a Certbot checkbox and a domain/hostname whatever the cert is issued to.
And some instructions like if you get a *.domain.se cert you need to specify the domain.se as
you domain. but I guess that is all part of certbot.
Alternatively you just have a config where you enter the symbolic link to use for certificate
like /etc/letsencrypt/live/dronten.dahlarna.se and if configured and "target" exists use this as the certificate files there instead of the .*pem files in the .signalK directory.
This is copied from the readme file in the live symbolic link.
The certbot live directory will contain the following files:
This directory contains your keys and certificates.
privkey.pem  : the private key for your certificate.
fullchain.pem: the certificate file used in most server software.
chain.pem    : used for OCSP stapling in Nginx >=1.3.7.
cert.pem     : will break many server configurations, and should not be used
without reading further documentation (see link below).
We recommend not moving these files. For more information, see the Certbot
User Guide at https://certbot.eff.org/docs/using.html#where-are-my-certificates.
The correct files to use is the privkey and fullchain ( I guess this is already known :))
Of course you SignalK box would have to fulfill the requirements to run certbot in an automatic way :)

Thinking a few more minutes...
Why not just have two separate config items for the key and the cert.
If you use certbot you can enter the symbilic linke to the live files...
If you use something else as long as you can point out a valid cert and key file in your config, symbolic or not just use the files configured...

I think that just adding symlinks (or if that doesn't work hard links) to the cert files where the server expects the files to be under .signalk will allow you to use certbot managed keys already today. The strict access check may be a problem.
If we do something to improve certbot usage it should be as user friendly as possible. From a user's point of view the intent is to go tell the servert : Use certbot managed certificate for hostname x.y.z and not care about details.
Supporting arbitrary key locations is another matter, but I don't think that is needed. At least I haven't heard anybody about it.

I hear you, but in that case I guess that certbot should be part of the distribution as well.
And I know off-topic here but still..
If I want to try pointing signalK towards a sym or hardlink now, where can I do that?
Is there a config somwhere?
Or maybe remove the cert and key file and replace the with sym links?

I would put this in a plugin if it were possible, but this is part of the server core. I think it is perfectly ok to add this and just point to their documentation for running it.
I think my certbot setups just copied the relevant files to where the server expects them to be. Please experiment & share your finding. The permission check is easy to find and just manually edit it away if that gives you trouble, then we can devise a plan for a longer term solution.

OK sounds like a plan, can you point me to the relevant parts of the code since I have never been in there :)

Duplicate of #340.


[fidesctl-plus #78] cross app navigation

Closes https://github.com/ethyca/fidesctl-plus/issues/78
Code Changes

The final commit is the crux of what we wanted:

Query /plus/health API to determine if Plus features should be shown
I put this in a "features" slice+hook instead of a "plus" slice because it's more of a feature flagging mechanism than an actual use of the Plus API. The Plus API slice itself can be extracted when we start using it, while the feature toggling could grow to have other kinds of checks.

To get that point, I had to solve Next Zone linking in a generic way. Now we can configure those links in one place.

Steps to Confirm

[ ] list any manual steps taken to confirm the changes

Pre-Merge Checklist

[ ] All CI Pipelines Succeeded
Documentation Updated:

[ ] documentation complete, or draft/outline provided (tag docs-team to complete/review on this branch)
[ ] documentation issue created (tag docs-team to complete issue separately)

[x] Issue Requirements are Met
[ ] Relevant Follow-Up Issues Created
[x] Update CHANGELOG.md

Description Of Changes
Navigating between the two zones in dev:
https://user-images.githubusercontent.com/2236777/187803440-1603bee3-4562-4712-b072-bc390ec5a144.mp4
When the regular server is running the 404 indicates Plus is unavailable.

@allisonking

copy the built docker image name into the docker-compose and comment out the volume mount, then docker-compose up fidesctl-plus. navigate to localhost:8080 and enjoy! is there an easier way

Yeah I did a similar hack when experimenting with building env-vars, except I only copied the the UI files. I bet we could conjure a Dockerfile/docker-compose.yml that would automate your steps to build fctl+ with a locally-built fctl python wheel. Would be handy for testing.


Shortcut conflict of Alt+R

VSCode Version: 1.48.0
OS Version: Manjaro 20.1

Steps to Reproduce:

Open a text file, press Alt+R, expecting the "Run" menu to expand
Regex matching for text search is toggled, although not searching or replacing anything

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

@rebornix this is linux, so the native menus. if they aren't greedily taking the keybind, we will have to scope down when the command applies.
just to confirm @champignoom , other mnemonics are working, such as Alt+F file menu

@sbatten Yes, alt+[FESVGTH] all work.

@rebornix this means it is up to command registration to scope appropriately, the when clause should probably include find widget focus

@sbatten actually we set the when clause to editorFocus intentionally as the find options will affect ctrl+d. This is more or less a keybinding conflict. Users can workaround this issue by changing the keybinding's when expression to editorFocus && findInputFocussed


[core] Review Gamepad support

Review Gamepad support for Raspberry Pi. It doesn't work properly. It seems axis movement is not scaled properly, just raw values are read.
Related functions [core.c]:
static void *GamepadThread(void *arg);
Vector2 GetGamepadMovement(int gamepad);

Just scale read values properly.

Improved gamepad support with commit https://github.com/raysan5/raylib/commit/db4585b3e23cd3c5aa87da21aedc36fd8be21739


GPJax and flexible train/valid losses

Added GPJax and allow train and valid losses to be passed as arguments to ift

Resolves #2
Provides initial implementation for #1.
Fixes the inverse transform missing the epsilon
Adds test for GPJax similar to the existing GP tests
Updates the notebook to use both the original gp and the gpjax.

Comparison
I've run a manual comparison on the notebook by fixing the seed and running the first problem on master and this PR.
Seems that using GPJax deteriorates in performance, either because of the existing GP implementation being so barebones that is faster and/or simply I'm missing some jax jit or performance trick. Qualitatively, pr-gpjax meta-parameter results are close enough with respect to master-gp. Using the flexible train/valid losses doesn't change anything (master vs pr-gp) which was expected.
Performance
master-gp: 2.15it/s
pr-gp:     2.15it/s
pr-gpjax:  1.48it/s
Final meta-params
master-gp: {'c_exp': 0.30767794, 'c_log': -0.11056437, 'c_sqrt': 0.24794468, 'c_x': 0.18069236}
pr-gp:     {'c_exp': 0.30767794, 'c_log': -0.11056437, 'c_sqrt': 0.24794468, 'c_x': 0.18069236}
pr-gpjax:  {'c_exp': 0.30767789, 'c_log': -0.11056453, 'c_sqrt': 0.2479447, 'c_x': 0.18069223}
Discussion
Regarding my concerns about how to customize the GP (e.g. fixed non-learnable params or different kernels), now that the losses become user-defined and passed as arguments, the ift is now agnostic to the GP model completely. It is possible to do plenty of things like: adapt/meta partitions, set non-learnable params or even use a different kernel/model; by a clever use of defining the initial parameters, a combine_func and the losses (inside you can define your own gp_module functional calls).  I think the notebook already covers these cases implicitly.
So right now, providing the gp.py or gpjax.py shouldn't even be needed other than as an example, as in practice you will probably define your own GP (e.g. using a different kernel) to suit your problem.
Another approach is to focus a bit more on GPJax and facilitate its use, as we can take advantage of its initialize method and use the parameter information that is automatically generated (such as learnable params and parameter transformations).

Forgot to put the gpjax dependency. Also I found that there is newer gpjax version (this PR was for 0.5.9), I could try to bump up if needed.


Add name to pandas contributors.

Add name and github link to README.md

Thanks @NamugumyaSandra, good job. Do you mind to fix the conflicts, and in a separate PR leave a blank line before the first username in the list? Thank you!

Closing as stale. @NamugumyaSandra feel free to open a new PR if you're interested in getting this merged.


Add opt-in support for setting the "nonce" attribute on the global cursor style

Resolves #384
import { setNonce } from "react-resizable-panels";

setNonce("whatever");

cc @asual

Published in version 2.1.0

❤ → ☕ givebrian.coffee


Inappropriate ioctl for device

Preliminary Checks

[X] This issue is not a duplicate. Before opening a new issue, please search existing issues.
[X] This issue is not a question, feature request, or anything other than a bug report directly related to this project.

Description
I'm just trying to run the examples after installing this library on a Raspberry Pi 4.
I'm encountering errors specifically when running examples using the cameras. The IMU example (zed_open_capture_sensors_example) runs fine.
It appears to be an error while opening the cameras due to the resolution, but I can't figure out how to solve it.
My problem seemed different enough from #19 as I wasn't experiencing any freezes and the camera seemed to be recognized using lsusb.
I should note I am not using the original USB type-C cable, as I currently don't have access to it. This is the output of lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 008: ID 2b03:f881 STEREOLABS ZED-2i HID INTERFACE
Bus 001 Device 007: ID 2b03:f880 STEREOLABS ZED 2i
Bus 001 Device 006: ID 0424:2512 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Steps to Reproduce
I'm following the install and build instructions in the README.md file.
After that, I try to run the lines zed_open_capture_sync_example and sudo zed_open_capture_video_example unsuccessfully.
Expected Result
I'm expecting the normal behavior of using the library's own examples.behavior
Actual Result
When running sudo zed_open_capture_video_example (I'm using sudo because if I don't, it replies with Permission denied)
[sl_oc::video::VideoCapture] ERROR: Error setting the camera resolution
xioctl: Inappropriate ioctl for device
xioctl: Invalid argument
[sl_oc::video::VideoCapture] ERROR: Cannot set pixel format of '/dev/video1': [22] Invalid argument
Cannot open camera video capture
See verbosity level for more details.
xioctl: Invalid argument

I edited the file zed_oc_sync_example.cpp and set VERBOSITY to INFO and got this result when running zed_open_capture_sync_example (no sudo required this time):
[sl_oc::video::VideoCapture] INFO: ZED Open Capture - Camera module - Version: 0.6.0
[sl_oc::video::VideoCapture] INFO: Camera resolution: 2560x720@30Hz
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video0'
[sl_oc::video::VideoCapture] ERROR: Cannot open '/dev/video0': [13] Permission denied
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video1'
[sl_oc::video::VideoCapture] ERROR: Cannot open '/dev/video1': [13] Permission denied
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video2'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video2/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video2' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video3'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video3/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video3' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video4'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video4/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video4' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video5'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video5/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video5' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video6'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video6/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video6' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video7'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video7/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video7' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video8'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video8/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video8' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video9'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video9/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video9' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video10'
[sl_oc::video::VideoCapture] WARNING:  not a modalias 2
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video10' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video11'
[sl_oc::video::VideoCapture] WARNING:  not a modalias 2
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video11' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video12'
[sl_oc::video::VideoCapture] WARNING:  not a modalias 2
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video12' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video13'
[sl_oc::video::VideoCapture] WARNING:  not a modalias 2
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video13' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video14'
[sl_oc::video::VideoCapture] WARNING:  not a modalias 2
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video14' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video15'
[sl_oc::video::VideoCapture] WARNING:  not a modalias 2
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video15' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video16'
[sl_oc::video::VideoCapture] WARNING:  not a modalias 2
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video16' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video17'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video17/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video17' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video18'
[sl_oc::video::VideoCapture] WARNING:  not a modalias 2
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video18' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video19'
[sl_oc::video::VideoCapture] WARNING:  not a modalias 2
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video19' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video20'
[sl_oc::video::VideoCapture] WARNING:  not a modalias 2
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video20' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video21'
[sl_oc::video::VideoCapture] WARNING:  not a modalias 2
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video21' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video22'
[sl_oc::video::VideoCapture] WARNING:  not a modalias 2
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video22' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video23'
[sl_oc::video::VideoCapture] WARNING:  not a modalias 2
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video23' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video24'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video24/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video24' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video25'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video25/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video25' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video26'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video26/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video26' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video27'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video27/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video27' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video28'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video28/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video28' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video29'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video29/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video29' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video30'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video30/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video30' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video31'
[sl_oc::video::VideoCapture] WARNING:  not a modalias 2
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video31' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video32'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video32/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video32' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video33'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video33/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video33' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video34'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video34/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video34' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video35'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video35/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video35' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video36'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video36/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video36' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video37'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video37/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video37' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video38'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video38/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video38' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video39'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video39/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video39' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video40'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video40/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video40' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video41'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video41/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video41' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video42'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video42/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video42' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video43'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video43/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video43' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video44'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video44/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video44' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video45'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video45/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video45' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video46'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video46/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video46' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video47'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video47/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video47' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video48'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video48/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video48' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video49'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video49/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video49' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video50'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video50/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video50' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video51'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video51/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video51' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video52'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video52/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video52' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video53'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video53/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video53' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video54'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video54/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video54' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video55'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video55/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video55' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video56'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video56/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video56' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video57'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video57/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video57' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video58'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video58/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video58' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video59'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video59/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video59' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video60'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video60/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video60' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video61'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video61/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video61' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video62'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video62/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video62' is not a Stereolabs camera
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video63'
[sl_oc::video::VideoCapture] WARNING:  Not a modalias : /sys/class/video4linux/video63/device/modalias
[sl_oc::video::VideoCapture] WARNING: The device '/dev/video63' is not a Stereolabs camera
Cannot open camera video capture
Try to enable verbose to get more info

ZED Camera model
ZED2i
Environment
Raspberry Pi 4 Model B Rev 1.2
OS: Raspbian 11 (bullseye)
ZED Open Capture - Camera module - Version: 0.6.0

Anything else?
No response

Hi @apnogueira
Did you install the udev rules?

Hi @Myzhar
Yes, I did. When I tried to run the command bash install_udev_rule.sh I got a bunch of Permission denied.
I then changed the command to sudo bash install_udev_rule.sh and it didn't show the Permission denied (As a matter of fact it had no response to the command). I assumed it installed the udev rules

I guess your first issue is caused by a resolution that is too high.
Did you connect the camera to a USB3 or USB2 port?
Try to change the resolution to VGA to see if you can open the camera (please use sudo).
Please also copy and paste the output of the commands lsusb and lsusb -d 2b03: -v -t

Currently the camara is connected to USB3, but I previously tried all ports (both RPi4 USB3 ports and both USB2 ports).
I changed both examples (sync and video_example) to a VGA resolution. The error changed.
When running sudo zed_open_capture_video_example
Connected to camera sn: 39263373[/dev/video0]
No protocol specified
Unable to init server: Could not connect: Connection refused
terminate called after throwing an instance of 'cv::Exception'
  what():  OpenCV(4.5.1) ../modules/highgui/src/window_gtk.cpp:624: error: (-2:Unspecified error) Can't initialize GTK backend in function 'cvInitSystem'

Aborted

When running sudo zed_open_capture_sync_example:
[sl_oc::video::VideoCapture] INFO: ZED Open Capture - Camera module - Version: 0.6.0
[sl_oc::video::VideoCapture] INFO: Camera resolution: 1344x376@30Hz
[sl_oc::video::VideoCapture] INFO: Trying to open the device '/dev/video0'
[sl_oc::video::VideoCapture] INFO: Opened camera with SN: 39263373
[sl_oc::video::VideoCapture] INFO: Device '/dev/video0' opened
Video Capture connected to camera sn: 39263373
[sl_oc::sensors::SensorCapture] INFO: ZED Open Capture - Sensors module - Version: 0.6.0
[sl_oc::sensors::SensorCapture] INFO: Device Found:
  VID: 2b03 PID: f881
  Path: 0001:0005:00
  Serial_number:   39263373
  Manufacturer:   STEREOLABS
  Product:   ZED-2i HID INTERFACE
  Release number:   v3.9
***

[sl_oc::sensors::SensorCapture] INFO: Connected to device with sn 39263373
Sensors Capture connected to camera sn: 39263373
No protocol specified
Unable to init server: Could not connect: Connection refused
terminate called after throwing an instance of 'cv::Exception'
  what():  OpenCV(4.5.1) ../modules/highgui/src/window_gtk.cpp:624: error: (-2:Unspecified error) Can't initialize GTK backend in function 'cvInitSystem'

Aborted

Output of lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 2b03:f881 STEREOLABS ZED-2i HID INTERFACE
Bus 001 Device 004: ID 2b03:f880 STEREOLABS ZED 2i
Bus 001 Device 003: ID 0424:2512 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Output of lsusb -d 2b03: -v -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
        ID 2109:3431 VIA Labs, Inc. Hub
        |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/2p, 480M
            ID 0424:2512 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
            |__ Port 1: Dev 4, If 0, Class=Video, Driver=uvcvideo, 480M
                ID 2b03:f880 STEREOLABS
            |__ Port 1: Dev 4, If 1, Class=Video, Driver=uvcvideo, 480M
                ID 2b03:f880 STEREOLABS
            |__ Port 2: Dev 5, If 0, Class=Human Interface Device, Driver=, 12M
                ID 2b03:f881 STEREOLABS

The camera is now correctly working, but you have problems with OpenCV displaying the images.
I suggest you search the internet for this error:
what():  OpenCV(4.5.1) ../modules/highgui/src/window_gtk.cpp:624: error: (-2:Unspecified error) Can't initialize GTK backend in function 'cvInitSystem

I figured the problem was related with using sudo. However, I had no permission to open the camera without sudo. I had to include my user in the video group in order to run the example without sudo. The command I used was:
sudo usermod -aG video USERNAME

So right now I am able to run all examples on the RPi4, but only with VGA resolution. Any suggestions on how to use HD720 resolution?

Hi @apnogueira
You are using a ZED 2i. Please check that the screws of the connector are strongly strengthened and that you are connecting the camera so a USB3 port.
The camera is detected in USB2 mode for compatibility when there is a connection issue.
If you want to be sure that the camera is working correctly you can try to connect it to a PC, open the video stream with a normal webcam application and try to change the resolution.
If the PC is CUDA-enabled you can install the ZED SDK and run the ZED Diagnostic tool to check that the camera is OK.

Hi @Myzhar
I finally managed to get my hands on the original cable. With it, I no longer have the resolution issue. I was able to run the examples for HD720 resolution. Thank you!
Closing...


Run PyBeacon as service, survive reboots

PyBeacon is AGPL (means each device will need to make available the source or URL to the source). Also might be nice in the spirit of AGPL to commit service back to PyBeacon

Yes. Do you have an appropriate phrase for the readme?

could / should include version numbers too

If we can get all current issues closed I'm happy to close my repo in favour of yours as it seems more sustainable to provision via ansible. Thanks for reaching out! :+1:

set beacon signal strength via ansible, see
https://github.com/nirmankarta/PyBeacon/issues/5


crouton update fails with trusty

I am trying to update trusty from crouton first before I go into the chroot to update it (seems like a good idea).  I deleted crouton and redownloaded a fresh version and it still won't update.
command:
sudo sh ./crouton -u -n trusty
response: /usr/local/chroots/trusty already exists; updating it...
Unable to determine the release in /usr/local/chroots/trusty. Please specify it with -r.
name: trusty
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/trusty...
crouton: version 1-20150827155505~master:edbce112
release: trusty
architecture: amd64
xmethod: xiwi
targets: xiwi,xorg,lxde
host: version 7390.68.0 (Official Build) stable-channel peppy
kernel: Linux localhost 3.8.11 #1 SMP Thu Nov 5 10:53:38 PST 2015 x86_64 x86_64 x86_64 GNU/Linux
freon: yes
Unmounting /mnt/stateful_partition/crouton/chroots/trusty...
Where to next?

Your chroot may not be fully setup, or something has changed.
Maybe just try to get into it first via sudo enter-chroot -n trusty
and see if that succeeds. If it tells you the setup didn't finish and ask if you want to proceed, go for it.
Then, either update your chroot via sudo apt-get update; sudo apt-get upgrade
or exit the chroot and run your crouton update command again.

I'll try that. I know the enter-Chroot works. Just was surprised the update crouton wasn't happy. I'm pretty sure the apt update will work too
Sean

On Dec 7, 2015, at 4:27 PM, DennisL<EMAIL_ADDRESS>wrote:
Your chroot may not be fully setup, or something has changed.
Maybe just try to get into it first via sudo enter-chroot -n trusty
and see if that succeeds. If it tells you the setup didn't finish and ask if you want to proceed, go for it.
Then, either update your chroot via sudo apt-get update; sudo apt-get upgrade
or exit the chroot and run your crouton update command again.
—
Reply to this email directly or view it on GitHub.

Yeah, the message:
Unable to determine the release in /usr/local/chroots/trusty. Please specify it with -r.
seems to indicate something is definitely wrong with the chroot...

Somehow my update list was really hosed up (us.release.ubuntu.com) instead
of us.archive.ubuntu.com.  Wonder if that was from the original crouton
trusty install...
On Mon, Dec 7, 2015 at 4:27 PM, DennisL<EMAIL_ADDRESS>wrote:

Your chroot may not be fully setup, or something has changed.
Maybe just try to get into it first via sudo enter-chroot -n trusty
and see if that succeeds. If it tells you the setup didn't finish and ask
if you want to proceed, go for it.
Then, either update your chroot via sudo apt-get update; sudo apt-get
upgrade
or exit the chroot and run your crouton update command again.
—
Reply to this email directly or view it on GitHub
https://github.com/dnschneid/crouton/issues/2272#issuecomment-162687871.

Yeah, I don't know how 'us.release.ubuntu.com' got in there.
Is the crouton update working for you now?

Yes, after I corrected it, the crouton update worked great. Might be good to cough an error code or something for totally screwy repositories.
Sean

On Dec 9, 2015, at 10:49 PM, DennisL<EMAIL_ADDRESS>wrote:
Yeah, I don't know how 'us.release.ubuntu.com' got in there.
Is the crouton update working for you now?
—
Reply to this email directly or view it on GitHub.

I have this same problem right now.  I've disabled all optional repos and I have archive.canonical.com for all the standard ones.
I've tried enter-chroot and done a manual update/upgrade without issue, I've verified that /etc/lsb-release, /etc/crouton/name, /etc/crouton/release all say trusty.
chronos@localhost / $ sudo sh ~/Downloads/crouton -u -n trusty
/usr/local/chroots/trusty already exists; updating it...
Enter encryption passphrase for trusty:
Unable to determine the release in /usr/local/chroots/trusty. Please specify it with -r.
chronos@localhost / $ sudo sh ~/Downloads/crouton -u -n trusty -r trusty
/usr/local/chroots/trusty already exists; updating it...
Enter encryption passphrase for trusty:
Release doesn't match! Please correct the -r option, or specify a second -u to
change the release, upgrading the chroot (dangerous).
chronos@localhost / $ sudo sh ~/Downloads/crouton -uu -n trusty -r trusty
/usr/local/chroots/trusty already exists; updating it...
Enter encryption passphrase for trusty:
WARNING: Changing the chroot release to trusty.
Press Control-C to abort; upgrade will continue in 5 seconds.
chronos@localhost / $ sudo sh ~/Downloads/crouton -u -n trusty -r trusty
/usr/local/chroots/trusty already exists; updating it...
Enter encryption passphrase for trusty:
Release doesn't match! Please correct the -r option, or specify a second -u to
change the release, upgrading the chroot (dangerous).
So at the very least, the extra -u does not function correctly to set the release.
It would be nice if the script would report what information it disagrees with so that users could take corrective action instead of (probably) giving up and junking their chroot.  I'd really prefer not do that but soon it will be my only option.

Running into the same situation. apt-get works. Changing repo to us.archive.ubuntu.com from archive.ubuntu.com does not help either.


updated package.json for dependabot prs

#670 #677 #678 #680 #681 #685 #687 #688
haven't done the axios and react one because those ones will probably break something and we might need to change how we do things

it works ! ! !


⚠ GreatPosterWall has degraded performance

In cb8c36b, GreatPosterWall ($GPW) experienced degraded performance:

HTTP code: 200
Response time: 16134 ms

Resolved: GreatPosterWall performance has improved in 957f2af.


Added Hello World Program in Assembly and VBScript

Linux x86_64

Thanks! Make sure to give the repository a star and share about it as well! You can tweet about the repository as well using the tweet badge on the Readme file or website!


Please expose git_message_prettify

git_message_prettify takes a buffer and cleans up whitespace and (optionally) comments.

Awesome, thanks!


Log concentrator type in use 1301 or 1302/3 #92

log concentrator type 1301/2/3

Issue

Link: https://github.com/NebraLtd/hm-pktfwd/issues/92
Summary: log concentrator type

How

Screenshots

References

Checklist

[ ] Tests added
[ ] Cleaned up commit history (rebase!)
[ ] Documentation added
[ ] Thought about variable and method names

this is already there in logs, lower down when concentrator starts.


add some completion and lookup for LaTeX: common commands and bibtex lookup

add a basic list of standard high-frequency commands.

inside of \cite{, look for the .bib file and show matching refs.  would only work on downloaded .bib and not live on Zotero, but if they ever get the ability to look up bib keys directly, then we could extend that with a simple web query that could be configured.

this is done -- was pretty easy and will definitely improve productivity with latex.  can't push yet until bibtex package is fixed so it doesn't fatal and crash.