drivers: sensor: Add sensor info iterable section and shell command

Adds an iterable section in ROM to hold constant information, such as vendor and model name, for all enabled sensor driver instances and a corresponding sensor shell command. Vendor and model names are extracted from devicetree compatibles (see #49489 and #50015), and friendly names are extracted from an optional base sensor devicetree property (see #50929).
Example 1: reel_board
$ west build -b reel_board -p auto samples/sensor/sensor_shell/

uart:~$ sensor info
0xbeec: device: 0xbcb8, vendor: Avago Technologies, model: apds9960, friendly name:
0xbefc: device: 0xbcd0, vendor: NXP Semiconductors, model: fxos8700, friendly name:
0xbf0c: device: 0xbce8, vendor: Texas Instruments, model: hdc, friendly name:
0xbf1c: device: 0xbd00, vendor: Nordic Semiconductor, model: nrf-temp, friendly name:

Example 2: frdm_k64f with x_nucleo_iks01a3 sensor shield
$ west build -b frdm_k64f -p auto samples/sensor/sensor_shell/ -- -DSHIELD=x_nucleo_iks01a3

uart:~$ sensor info
0xc92c: device: 0xc500, vendor: STMicroelectronics, model: hts221, friendly name:
0xc93c: device: 0xc518, vendor: STMicroelectronics, model: lis2dw12, friendly name:
0xc94c: device: 0xc530, vendor: STMicroelectronics, model: lis2mdl, friendly name:
0xc95c: device: 0xc548, vendor: STMicroelectronics, model: lps22hh, friendly name:
0xc96c: device: 0xc560, vendor: STMicroelectronics, model: lsm6dso, friendly name:
0xc97c: device: 0xc578, vendor: STMicroelectronics, model: stts751, friendly name:
0xc98c: device: 0xc4e8, vendor: NXP Semiconductors, model: fxos8700, friendly name:

cc: @huhebo

the output a few comments on the output, not sure how we can improve this:
0xc92c: device: 0xc500, vendor: STMicroelectronics, model: hts221, friendly name:

Its unclear what the first number printed even means w/o looking at the code -- is this value meaningful?
Not sure if tweaking 'device' to 'device pointer' would be more clear?
I wonder about putting brackets around the strings to make it maybe a bit more obvious when a string is empty/NULL:

0xc92c: device pointer: 0xc500, vendor: [STMicroelectronics], model: [hts221], friendly name: []

a few comments on the output, not sure how we can improve this: 0xc92c: device: 0xc500, vendor: STMicroelectronics, model: hts221, friendly name:

Its unclear what the first number printed even means w/o looking at the code -- is this value meaningful?

Not really, no. Removed.

Not sure if tweaking 'device' to 'device pointer' would be more clear?

Replaced with "device name", which is also used as an argument to the sensor get shell command

I wonder about putting brackets around the strings to make it maybe a bit more obvious when a string is empty/NULL:

So maybe: device pointer: 0xc500, vendor: [STMicroelectronics], model: [hts221], friendly name: []

Not sure I love it, but added the brackets.

a few comments on the output, not sure how we can improve this: 0xc92c: device: 0xc500, vendor: STMicroelectronics, model: hts221, friendly name:

Its unclear what the first number printed even means w/o looking at the code -- is this value meaningful?

Not really, no. Removed.

Not sure if tweaking 'device' to 'device pointer' would be more clear?

Replaced with "device name", which is also used as an argument to the sensor get shell command

I wonder about putting brackets around the strings to make it maybe a bit more obvious when a string is empty/NULL:

So maybe: device pointer: 0xc500, vendor: [STMicroelectronics], model: [hts221], friendly name: []

Not sure I love it, but added the brackets.

Whats wrong with using quotes here in place of the brackets? The brackets make me think there's going to be an array of these things which I don't think is the case here right?

3. I wonder about putting brackets around the strings to make it maybe a bit more obvious when a string is empty/NULL:

Why not just print (null), (none) or (empty) when a string is empty instead of putting (arguably confusing) brackets everywhere?
device pointer: 0xc500, vendor: STMicroelectronics, model: hts221, friendly name: (null)

The fundamentals are there, we can bike shed about the output in a follow-up PR.

The fundamentals are there, we can bike shed about the output in a follow-up PR.

Follow up PR: #51864


Generate data set for Tree LSTM

Is the code for generating the data set "tree_lstm_dataset-3d85a6c4.cPickle" (used in chapter09) available?
I would like to generate the parse tree for my own text, and build a similar model.
Thanks a lot.

@szha please help! Thanks :)

The script can be found in https://github.com/apache/incubator-mxnet/tree/master/example/gluon/tree_lstm. Check the shell script for downloading and parsing trees, and main.py for loading and pickling.

Hi Zack & Sheng,
Thank you both very much for the quick responses. This is really helpful!
-Sean


Xaml Islands: ZoomText 2020 Accessibility software breaks all mouse input over islands

Describe the bug

Expand: Snippet excerpted from Terminal bug
Environment
Windows build number: 10.0.18363.0
Windows Terminal version (if applicable): 0.9.433.0

Any other software?
ZoomText 2020

Steps to reproduce

Launch ZoomText 2020 (typically at system startup)
Launch Windows Terminal
Observe:

Clicking on the '+' for a new tab does not work
Clicking the dropdown for the options menu does not work
Clicking and dragging to select text does not work

Press [CapsLock]+[Control]+[Enter] to suspend the Zoom functionality of ZoomText
Observe that all features work as expected
Re-enable ZoomText's Zoom functionality
Observe that features as described in step 3 no longer work

Expected behavior
Windows Terminal's functions should all work correctly when using assistive software such as ZoomText.
Actual behavior
Windows Terminal's functions do not work correctly - none of the buttons on the 'titlebar' work (including system buttons such as maximise, minimise or close), the new tab button does not work, the menu drop-down does not work, clicking and dragging to select text does not work.

Reported in microsoft/terminal#4889. ZoomText seems to be a systemwide magnification application used for accessibility, and when it's in use no mouse clicks work in Xaml Islands applications. This was tested with Terminal and PerceptionSimulationInput.
Steps to reproduce the bug
Steps to reproduce the behavior:

Install ZoomText 2020 (consider licensing before doing so)
Use it
Launch PerceptionSimulation or Terminal

Expected behavior
All input works.
Version Info

Windows 10 version
Saw the problem?

Insider Build (xxxxx)
Untested

November 2019 Update (18363)
Yes

May 2019 Update (18362)
Yes

October 2018 Update (17763)
Untested

April 2018 Update (17134)
No Islands

Fall Creators Update (16299)
No Islands

Creators Update (15063)
No Islands

Device form factor
Saw the problem?

Desktop
Yes

Mobile

Xbox

Surface Hub

IoT

Are there any updates on this?  I opened the original issue on the Windows Terminal repository, and am having the same issue with the new Windows PowerToys.  Also, this affects other areas, such as results of search in the Start Menu.  This is a pretty major defect to still have, especially given public statements made by senior Microsoft execs about being an "accessibility first" organisation - I think this pretty much demonstrates the opposite.

bump
It's a shame when a major accessibility issue cannot be fixed for over 1.5 years.
Any software that uses XAML Islands does not work with Windows Magnifier or Zoomtext.

This is still a bug.


Unable to deploy Laravel app on Google app engine with bitfumes/laravel-multiauth package

Describe the bug
This package work fine on localhost, but not get deploy on Google Cloud app engine.
ERROR: build step 1 "gcr.io/gae-runtimes/php73_app_builder:php73_20200223_7_3_14_RC00" failed: step exited with non-zero status: 1
ERROR
Finished Step #1 - "builder"
Step #1 - "builder": IOError: [Errno 2] No such file or directory: '""/output'
Step #1 - "builder":   File "/usr/local/bin/ftl.par/__main__/ftl/common/ftl_error.py", line 58, in UserErrorHandler
Step #1 - "builder":   File "/usr/local/bin/ftl.par/__main__.py", line 57, in main
Step #1 - "builder":   File "/usr/local/bin/ftl.par/__main__.py", line 65, in <module>
Step #1 - "builder":     exec code in run_globals
Step #1 - "builder":   File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
Step #1 - "builder":     "__main__", fname, loader, pkg_name)
Step #1 - "builder":   File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main
Step #1 - "builder": Traceback (most recent call last):
Step #1 - "builder": error: `composer_install` returned code: 1
Step #1 - "builder":
Step #1 - "builder": Script @php artisan package:discover --ansi handling the post-autoload-dump event returned with error code 1
Step #1 - "builder": > @php artisan package:discover --ansi
Step #1 - "builder": > Illuminate\Foundation\ComposerScripts::postAutoloadDump
Step #1 - "builder": Generating optimized autoload files
Step #1 - "builder":   - Installing nunomaduro/collision (v4.1.3): Downloading (100%)
Step #1 - "builder":   - Installing facade/ignition-contracts (1.0.0): Downloading (100%)
Step #1 - "builder":   - Installing filp/whoops (2.7.1): Downloading (100%)
Step #1 - "builder":   - Installing laravel/tinker (v2.3.0): Downloading (100%)
Step #1 - "builder":   - Installing psy/psysh (v0.10.2): Downloading (100%)
....
....

Laravel Version
Tried on laravel 5.8, 6.0, and 7 as well
To Reproduce
Steps to reproduce the behavior:

composer install bitfumes/laravel-multiauth
gcloud app deploy

Expected behavior
It should deploy
Screenshots
Desktop (please complete the following information):

Google App Engine

Additional context

Hey, your error doesn't tell anything about this package!


Merge feature-redesign into dev

I will not be squashing commits. There will be a standard merge commit, due to the size of the merge.

Too big to review, will just trust you on this :)
:shipit:


[menu-item]: Clicking on disabled menu-item closes the menu

Reproduction
https://material.angular.io/components/menu/examples
Steps to reproduce:

Click on the disabled mat-menu item.

Expected Behavior
The menu should not be closed if the menu-item is disabled
I believe below is the code for this but still, the menu gets closed
https://github.com/angular/components/blob/master/src/material/menu/menu-item.ts#L145-L146
Actual Behavior
The menu gets closed when we click.

Angular:
CDK/Material: latest
Browser(s): Google Chrome
Operating System (Ubuntu):

Looks like it's due to https://github.com/angular/components/pull/16696 which was put in place to normalize some browser inconsistencies.


How to visualize DocRED

Hello!
In what tool did you make visualizations of the dataset? I tried SpaCy NER visualization and it works fine, but it can't make entities and dependencies in the same time.

Sorry, we don't have a tool for visualization.

Them how did you make the picture in the 1st page of the paper?

By Microsoft PowerPoint manually.


Add math functionality to attribute values

Whenever getting a multi-dimensional attribute we may want to add math functionality to it,
I.e. transform.worldMatrix0 can return an MMatrix, transform.translate() can return an MVector.
Therefore the plan is simply checking the returned value and if it is a multi-dimensional float we cast it to the right class.
The goal of the class is to work 100% identical to the returned value (i.e. a tuple of 3 floats should be indistinguishable from a Vec3 instance when used in code), but add MVector / MPoint / MQuaternion / MMatrix features on top where applicable.
Notes:
We considered is another approach to this, being transform.tx() returns a float, and python's math module has
functions to manipulate that float. In this fashion we could create functions like "def normalize(vec):", but overriding max() and abs() to also support MVector seems invasive in builtin Python features so we should opt not to.
We considered using cmds.getAttr(type=True) to see if something is a double3, but cmds.xform does not work like that for example.
We considered using explicit functions, especially for MQuaternion, like transform.getR(), but some node attributes simply return 4 floats and we want to use quaternion funcionality with them, so again return-value-type is more important than any other contextual information we can assume from node name / type and attribute name / type.

has been merged into main


Icon Buttons

I had kinda expected JFoenix to have this, but there doesn't seem to be any kind of button like this with just an image and a circular ripple:

Does this exist and I'm unable to find what it's called?
For my current project I have thrown together a crude one for myself, and if it doesn't exist in JFoenix I may make a nicer one and PR it in

Hello,
can you clarify the issue?
you can simply create such a button by adding an icon and a border radius to JFXButton
Regards,

Ah yes, of course.


Fix test

This PR try to fix the deadlock on sqlite test on CI.

Codecov Report

Merging #10363 into master will increase coverage by 0.02%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master   #10363      +/-   ##
==========================================
+ Coverage   43.74%   43.76%   +0.02%
==========================================
  Files         585      585
  Lines       81023    81024       +1
==========================================
+ Hits        35440    35460      +20
+ Misses      41202    41169      -33
- Partials     4381     4395      +14

Impacted Files
Coverage Δ

models/repo.go
51.32% <0%> (-0.04%)
:arrow_down:

modules/indexer/stats/queue.go
62.5% <0%> (-18.75%)
:arrow_down:

modules/indexer/stats/db.go
40.62% <0%> (-9.38%)
:arrow_down:

modules/process/manager.go
74.69% <0%> (-3.62%)
:arrow_down:

models/notification.go
64.13% <0%> (-1.06%)
:arrow_down:

models/pull.go
42.37% <0%> (+0.55%)
:arrow_up:

services/mirror/mirror.go
19.4% <0%> (+0.65%)
:arrow_up:

models/repo_mirror.go
12.76% <0%> (+10.63%)
:arrow_up:

services/pull/check.go
53.04% <0%> (+14.63%)
:arrow_up:

Continue to review full report at Codecov.

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


Tests will sometimes fail on CircleCI but show as passed

https://circleci.com/gh/CoNarrative/precept/295?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link
Previously the test runner setup will show a failure if any of our tests fail, despite the last result (of the test runner itself) showing 0 tests, 0 failures. Because this appears to happen inconsistently we should revisit the test runner setup. We might want to consider CLJS tests #61 in conjunction with this, perhaps borrowing from Clara. The test runner setup came about due to inconsistencies between running tests with macroexpand on CircleCI vs locally (they would pass locally but fail on CircleCI).

I wonder if this is because you're using lein do syntax, and lein's exit code reflects the lein uberjar task, not the lein test one? Possibly splitting this into two - run: lines in the circle config would help.

Thanks! That makes perfect sense.
That may ultimately be causing a false positive but it looks like we get one before that.
Running lein test :only precept.test-runner with a failing test:
... other tests...
Testing precept.listeners-test

FAIL in (listeners-state-transitions) (listeners_test.cljc:161)
I fail
expected: (= 0 1)
  actual: (not (= 0 1))

Ran 2 tests containing 23 assertions.
1 failures, 0 errors.

lein test precept.test-runner

Ran 0 tests containing 0 assertions.
0 failures, 0 errors.

$ echo $?
0

I added this test runner namespace to get the test output to agree with what I was seeing in the REPL for macro tests that assert the equality of what our DSL expands to against Clara's. Running lein test alone gives failures for these. The main thing they have in common is that they call macroexpand. The expansion doesn't appear to take place the same way with lein test. E.g.
FAIL in (rule-test) (rule_test.cljc:290)
With :test op
expected: (= (macroexpand (quote (rule my-rule [?fact <- [_ :my-attribute _ ?t]] [:test (> ?t ?fact)] => (insert! "RHS")))) (clojure.core/seq (clojure.core/concat (clojure.core/list (quote do)) (clojure.core/list (macroexpand (quote (defrule my-rule [?fact <- :my-attribute (= ?t (:t this))] [:test (> ?t ?fact)] => (insert! "RHS"))))))))
  actual: (not (= (rule my-rule [?fact <- [_ :my-attribute _ ?t]] [:test (> ?t ?fact)] => (insert! "RHS")) (do (defrule my-rule [?fact <- :my-attribute (= ?t (:t this))] [:test (> ?t ?fact)] => (insert! "RHS")))))


Make NetDaemonApp.cs an abstract class

The problem

Environment

NetDaemon release with the issue: . 35 alpha
Last working NetDaemon release (if known): n/a
Operating environment (Home assistant Add-on/Docker/Dev setup): docker
Link to integration documentation on our website:

Link to or paste code that causes the issue

Traceback/Error logs

Additional information
Talked about this in discord awhile back and @helto4real agreed that this class should be abstract, since all app daemons that inherit must override InitializeAsync(). Little nuances like this make it a lot easier for the end-user to make netdaemons :)

Agree, lets put it on the "todolist" :) Thanks for the reminder


Change the internal parse-tree to be regular classes

They are record-classes currently, which is dangerous, given that they are not written with value-semantics in mind. For that we can provide comparers later, but referential equality should be fine.
We can keep the records if there's a simple way to reintroduce referential equality for all nodes. Otherwise, we'll need classes, which means explicit constructors.

Otherwise, we'll need classes, which means explicit constructors.

required properties from C# 11 are also an option.


Add Open Liberty stack tutorial

Add a new tutorial showing how to use the Open Liberty stack

Thanks @helenmasters.  I made the suggested changes except for the endpoint links.  These are showing up as clickable links for me both in my Atom preview editor and out in git (via Chrome). Do these need to be explicitly made clickable for the website?

Thanks @helenmasters. I made the suggested changes except for the endpoint links. These are showing up as clickable links for me both in my Atom preview editor and out in git (via Chrome). Do these need to be explicitly made clickable for the website?

@awisniew90 that is correct, you'll need to make them explicitly clickable for them to be converted to links in the website. The plugin we're using converts Markdown to HTML, so for us to have a link on the website it will need to be a link in Markdown:
[http://localhost:9080/starter/resource](http://localhost:9080/starter/resource)

I hope this helps :)

Thanks @ddunn2 !  All should be clickable links now.

@awisniew90 the site now has tutorials pages, so I think we can work on getting this into master now :)

Adam, you'll need to move your Markdown file into /content/tutorials/. I'll walk through the wording now to see if there are any other edits required and make comments as appropriate. Thanks!

@neeraj-laad - if you are happy with this, please can you merge


GitHub actions

This PR aims to setup continuous integration (CI) for ixdat via [Github Actions[(https://docs.github.com/en/actions).
Github Actions is a framework for having certain actions done automatically on certain events. It is heavily used for CI, but it is by no means exclusive to that. It is e.g. possible to setup actions to e.g. make releases triggered by a tag, or to do certain things when PRs are opened, like having a bot comment if the CI fails or similar. But for now I setup just the CI. The CI checks the same items as invoke checks does, which now is:

That the tests pass
That code and tests passes flake8
That code, tests and development scripts are black formatted

The checking of black formatted code was added in this PR along with another task for black formatting everything.

Looks good!
I would be worried about it slowing down a push, since I think it's good practice to push often to back up local work, and that there should be no barrier at all to doing so on a feature branch. So long as the push is instant and these CI tools happen on github without making the user wait (for all but the main branch), I'm happy.

Well this does satisfy your opinion on this, but I think I would object slightly to the idea, since that would definitely get in the way of something like git hooks. The way I view it, HD fails happens, but are infrequent, so the major thing that version control systems should guard against, if we are talking about backup, is user induced losses i.e. Error 40. For that reason, I think commit (which guards against that) should be fast, but push (which guards against HD failure) should be allowed to take seconds. This will likely mean that commit is suitable for all the time and push some times per day, possible at natural breaks, lunch, coffee run etc. etc. which I think is a reasonable compromise between what pre-commits adds of value and the risk of losing what you worked on the last few hours due to HD failure once every few years.

@ScottSoren I consider this ready to merge, but will leave it open for you to merge, to maintain proper workflow and allow you to see answers to certain questions.

Yes. Looks good!
I'll just answer that the philosophy of frequent seamless pushing is not so much out of concern for HD failure, but more HD unavailability. If I work at home today and pushing isn't an instinctive twitch, there's a good chance that tomorrow I'll be at work and not be able to do what I wanted since I left my laptop at home and my git repositories are (unlike everything else) not in dropbox. So I'm glad that push will still be seamless for the user :)


check inference indicator bar

Something seems to be off with the inference indicators: I encountered some cases where the bar was indeed completely filled. The first assumption is that the underlying confidence value for some inferences is higher than 1.0 although we assumed that this would not happen. This would either need some investigation of the confidence value computation or the way the progress bar is computed.

fixed with commit 07e0639


Instrument row query also

Some queries that generate from Count() functions are captured by row_query. Hence, instrumenting it.

Not needed.


feat(manifest) reduce maintenance amount of PWA files by using a plug…

reduce maintenance amount of PWA files by using a plugin to cut icons and generate manifest.json
fix majority of potential issues with adding to home screens across devices

Also renders #3103 's approach redundant

Thanks!


argocd: 2.2.5 -> 2.3.1

Description of changes
Drop packr (https://github.com/argoproj/argo-cd/commit/3f32a750a014ba818301b3e99e94be619eb18b1f), helm and kustomize as it does not seem necessary to use cli only
maintain commit and add todo for updatescript
add cmd to subpackage per  https://github.com/argoproj/argo-cd/blob/master/Makefile#L222
since it builds only cmd, doCheck = false is not needed anymore, also the fix for it is only in master at the current time
note, we only build the cli from now on as i think the other componentes are a bit irelevant to nixos
drop makewrapper
reorganize phases based on https://nixos.org/manual/nixpkgs/stable/#ssec-controlling-phases
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

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

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

note, we only build the cli from now on as i think the other componentes are a bit irelevant to nixos

What if someone is running the server from NixOS? This will be a breaking change for them. Should we split the package into -cli, -server etc..?

note, we only build the cli from now on as i think the other componentes are a bit irelevant to nixos

What if someone is running the server from NixOS? This will be a breaking change for them. Should we split the package into -cli, -server etc..?

At first, I did consider that. But the service is meant to be running inside the kubernetes cluster. I don't know of a case of running it outside the Kubernetes cluster. Still if it ever makes sense the person that finds the need can propose a new PR and validate everything as expected.

LGTM.
Is there any other issue with the current package? If not, I am going to merge it.

Go ahead. It is fine.

Also I am not using ArgoCD daily anymore because of autopilot, but I make sure to test at least the https://argo-cd.readthedocs.io/en/stable/getting_started/ after a update.


As a [end user], I want to see my balance on both chains (send/receive) in order to make it easier to chose an amount

Problem
Difficulty/extra work at deciding the amount to transfer; having to open a wallet to see amounts on receiver end
Proposed Solution
We should show balance on both chains (send/receive) to solve this problem.

[ ] See Slingshot's  solution

Acceptance Criteria
From an end tester and/or user perspective, the below criteria must be met to consider this done:

[ ] Adding actual balance for sender/receiver chains

suggested by BM#8089

I think we can consider this better if with go forward flipping the horizontal chain alignment to the vertical swap/bridge alignment.  Looking at this

Yeah I think that may be the way to go. Always liked Slingshot's approach despite it being just a DEX

Fair feedback i think will fix if we switch to the swap styel UI

@nrsirapop Per convo in discord I didnt mean for us to pull out of backlog yet, but we might as well update in staging since we started. Can you revert and put this in a staging state but make the below updates as well?

Balances are is top right above the boxes. Font is slightly brighter for numeric amount
#A5A5A5
#F0F0F0/*
Balance: 124 ETH */
position: absolute;
left: 72.98%;
right: 0%;
top: 0%;
bottom: 80.23%;

font-family: 'Manrope';
font-style: normal;
font-weight: 600;
font-size: 12px;
line-height: 140%;
/* identical to box height, or 17px */

The outline of the 'Receive' box is darker color to signal it is not editable
Receive
border: 1px solid #292929;
border-radius: 3px;
vs. the Pay with
border: 1px solid #3E3E3E;
border-radius: 3px;

Fees are slightly darker follow this formatting

Following this design https://www.figma.com/file/Z3iq2LOM12K1BeSGQc1Dal/Connext-Concept?node-id=190%3A500&t=rCyfDPIVJCGG1sGg-0

I love it! Lets ship it

Implemented, nice work @nrsirapop. Closing it.


New layout

Thanks for the contribution of a new style @Heleme !! .. could you please remove the changes from index.md and all the back files? Otherwise your personal information will enter the main repo.

Sorry, I'm new to Github and that request was an mistake on my side !
I closed the pull request.
Have a great day,
Best,
Le jeu. 8 juin 2017 à 11:50, elipapa<EMAIL_ADDRESS>a écrit :

Thanks for the contribution of a new style @Heleme
https://github.com/heleme !! .. could you please remove the changes
from index.md and all the back files? Otherwise your personal information
will enter the main repo.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/elipapa/markdown-cv/pull/8#issuecomment-307145564,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AL3pjDar9o-2AeFLAst9H0FK6y5CEhZoks5sCBhdgaJpZM4NmcEt
.

--
Louis-Marie de Langlois
US :<PHONE_NUMBER>
FR : 06 50 48 53 68

Will that be enough to hide my personal info ? It seems to be online still.
Le jeu. 8 juin 2017 à 12:32, Louis-Marie de Langlois<EMAIL_ADDRESS>a
écrit :

Sorry, I'm new to Github and that request was an mistake on my side !
I closed the pull request.
Have a great day,
Best,
Le jeu. 8 juin 2017 à 11:50, elipapa<EMAIL_ADDRESS>a écrit :

Thanks for the contribution of a new style @Heleme
https://github.com/heleme !! .. could you please remove the changes
from index.md and all the back files? Otherwise your personal
information will enter the main repo.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/elipapa/markdown-cv/pull/8#issuecomment-307145564,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AL3pjDar9o-2AeFLAst9H0FK6y5CEhZoks5sCBhdgaJpZM4NmcEt
.

--
Louis-Marie de Langlois
US :<PHONE_NUMBER> <(860)%20218-0821>
FR : 06 50 48 53 68

--
Louis-Marie de Langlois
US :<PHONE_NUMBER>
FR : 06 50 48 53 68


Carthage support

Hi,
Thank you for sharing with us this library.
Would it be possible to have Carthage support for it?
Thanks!

Hi! That's certainly something I can look into. I don't have a timeline but next time we have some free time, I can try to make that happen.

Many thanks, @klundberg !

Hi,
As well as @SSenocico I need carthage support to use this library, so I've created a PR which adds it https://github.com/StarryInternet/CombineCoreBluetooth/pull/4
@klundberg please take a look 🙏 👁

Fixed with #4


uMatrix: solved [changes to scope selection]

@gorhill - am I doing something wrong here?
FF56, uM 1.1.10
default rules
* * * block
* * cookie block
* * css allow
* * frame block
* * image allow
* * other block
* * script block
* 1st-party * allow
github.com * script inherit
github.com github-production-user-asset-6210df.s3.amazonaws.com xhr allow

Step1: I'm on github, flick up uM - looks all good to me

Step2: I flick to scope * - looks all good to me (I think, I'm not sure)

Step3: I flick back to scope github - it's all fubared as in it no longer matches pic 1 above, also the blue scope square is not all blue

Thanks for your time if you can quickly confirm or deny an issue :)

OK .. a penny is dropping here There are three scopes

global (*)
site
domain

We used to have a dropdown, now the global (*) is a click on the main navbar, AND .. it seems there are two click areas where the domain/site text is shown. This is not very clear, unless I missed the memo. I'm also not sure which is which since the test displayed doesn't change (in this example - trying to find one where it does)

OK .. seems the last few hours has produced the following
https://github.com/gorhill/uMatrix/issues/  844
https://github.com/gorhill/uMatrix/issues/  842
https://github.com/gorhill/uMatrix/issues/  840

nice... can effectively block ccTLD's now :) eg .ru


Tag feature releases?

@joshspicer @samruddhikhandale Should feature releases be tagged in the Git repo? I don't see how I would currently navigate from an OCI artifact to the commit it was created from. We usually use tags for that. What do you think?

We're currently releasing each feature independently by bumping the version in the feature's devcontainer-feature.json.
We could do something like v0.0.5-ruby when creating the release.  Would that make sense?

Make it ruby-v0.0.5 to avoid collision with semver's pre-release/build labels. 👍

@samruddhikhandale , this could be introduced in addition to the versioning github action we discussed

I introduced this change to the CLI in order to hand GitHub action the appropriate tags that were pushed
https://github.com/devcontainers/cli/pull/305

This has been complete and rolled out for some time.  Tagging is done by the github action we publish (devcontainers/action)


Abstracted family sort & added preset and platform sort

For issue 1180
sort.webm

I got the updates to the sorting to work for API fetchs on my local build. I think that because the vercel build uses the live DB that the changes aren't showing. If that is the case the current build does sort the scratches on the backend it just doesn't show here.

I believe this also resolves #955

This pr should be all set to go unless anyone has anymore reviews they'd like to give

This change works for non-anonymous users..
diff --git a/frontend/src/app/(navfooter)/u/[username]/page.tsx b/frontend/src/app/(navfooter)/u/[username]/page.tsx
index 7c970205..8b6d38df 100644
--- a/frontend/src/app/(navfooter)/u/[username]/page.tsx
+++ b/frontend/src/app/(navfooter)/u/[username]/page.tsx
@@ -66,8 +66,9 @@ export default async function Page({ params }: { params: { username: string } })

Scratches

             <ScratchList
-                url={userUrl(user) + "/scratches?page_size=20"}
+                url={`/scratch?user=${user}&page_size=20`}
                 item={ScratchItemNoOwner}
+                isSortable={true}
             />

@mkst I don't think this change does work, as it's showing all scratches now. I tried using owner too since that'd the name of the db field but it didn't work. maybe I'm missing something though and this is a red herring

This change works for non-anonymous users..
diff --git a/frontend/src/app/(navfooter)/u/[username]/page.tsx b/frontend/src/app/(navfooter)/u/[username]/page.tsx
index 7c970205..8b6d38df 100644
--- a/frontend/src/app/(navfooter)/u/[username]/page.tsx
+++ b/frontend/src/app/(navfooter)/u/[username]/page.tsx
@@ -66,8 +66,9 @@ export default async function Page({ params }: { params: { username: string } })

Scratches

             <ScratchList
-                url={userUrl(user) + "/scratches?page_size=20"}
+                url={`/scratch?user=${user}&page_size=20`}
                 item={ScratchItemNoOwner}
+                isSortable={true}
             />

@mkst I don't think this change does work, as it's showing all scratches now. I tried using owner too since that'd the name of the db field but it didn't work. maybe I'm missing something though and this is a red herring

Sorry committing the user scratch change was arrogant of me because I had assumed that it was tested and hadn't tested it myself. My bad, I'll look into the appropriate change to get it working as intended.

Oh, that's strange. It was a while ago now but I thought that worked for me locally - I definitely had a sortable drop-down for my own scratches, but I'm sorry that it doesn't actually seem to work for anyone else 😔


Copying from Microsoft Word into Engagement Details removes the rich text formatting

The rich text formatting (e.g. bold, underline, font size) is lost when copying from Microsoft Word into the Engagement Details data field.  The same is true for the Sensitive Information data field and the Biography data field.
At one point copying rich text from Word was available.
I found other similar rich text issues, but not quite this issue.
#1114
#1567
#1729
#1606
#1950
#1955

unfortunately, this is a problem with IE11. It is too difficult to work around it to make it work on IE11, and as we are about to drop support for IE11 we will leave this unresolved


Setup Apache Iceberg

To store sensor data long term, Apache Iceberg can be used.
This would require setup of a S3-like file store such as minio.
The data could be backed up to Iceberg on a daily basis for long term storage and analytics.

Also take not that some form of catalog might be required


Breaking changes in 1.3.3

Because of escaping values inside the dropdownAddItem method I can't use integer values (instead of strings) neither HTML in the item's text anymore
Could you make escaping optional?

Can you give me an example of your code, because I don't understand in what case it's a problem.

Thank you for taking the time to respond.
For the first case I show a default list on focus which is an array like this where the values are ids:
{value: 50, text: "FC Barcelona"}
These are added with triggering a 'tokenize:dropdown:fill' event.
Also for some advances use cases I do highlighting on the backend so I use a dataSource url.
An example result is an array with values like this:
{value: 47310, text: "FC Metz"}
Here the text's value is escaped since 1.3.3


Add important to editions

This commit adds an important flag to the edition doctype. It will be
used by the Whitehall editor to set documents as being important.

I thought the plan was to use a less-generic name than important

Oh yeah. I totally forgot we had that chat. What should I name this then? Didn't we agree on important_to_policy?

That seems a good name, to me.

@rboulton Updated it to use important_to_policy.


Update scala-library, scala-reflect to 2.13.6

Updates

org.scala-lang:scala-library
org.scala-lang:scala-reflect

from 2.13.5 to 2.13.6.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang" } ]

labels: library-update, semver-patch

Codecov Report

Merging #150 (7d6c669) into master (be99a97) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #150   +/-   ##
=======================================
  Coverage   87.13%   87.13%
=======================================
  Files          28       28
  Lines         832      832
  Branches       31       31
=======================================
  Hits          725      725
  Misses        107      107

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 be99a97...7d6c669. Read the comment docs.


NTP_OFFSET how to adjust the Time Zones

actually i m playing around with this really good stuff but i can t change the time zone.

Time zones are defined according to the time zone library, so you can refer to that documentation for more detailed information.
For the quick version, take a look at the lines in the sketch that determine the time change rules. That's where you define the offset from GMT. For example, in the following two lines, daylight time is defined as -240 minutes offset, and standard time is defined as -300 minutes offset.
TimeChangeRule myDST = {"EDT", Second, Sun, Mar, 2, -240};    //Daylight time = UTC - 4 hours
TimeChangeRule mySTD = {"EST", First, Sun, Nov, 2, -300};     //Standard time = UTC - 5 hours

works perfect. thanks


gRIBI MPLS compliance test for popping N labels from stack.

* (M) feature/gribi/mplsutil:
  - Add compliance test for popping N labels from an incoming packet
    programmed by gRIBI.
 * (M) feature/gribi/otg_tests/mpls_compliance:
  - Add test with no traffic verification for validating gRIBI
    programming API.

Pull Request Functional Test Report for #2178 / 38e37d62ad7dd5940066bddc592bb0572e1b869a
Virtual Devices

Device
Test
Test Documentation
Job
Raw Log

Arista cEOS

TE-9: gRIBI MPLS ComplianceTE-10: gRIBI MPLS Forwarding
ef68c6ba
Log

Cisco 8000E

TE-9: gRIBI MPLS ComplianceTE-10: gRIBI MPLS Forwarding
183302cc
Log

Cisco XRd

TE-9: gRIBI MPLS ComplianceTE-10: gRIBI MPLS Forwarding
5d459504
Log

Juniper cPTX

TE-9: gRIBI MPLS ComplianceTE-10: gRIBI MPLS Forwarding
f913b8b8
Log

Nokia SR Linux

TE-9: gRIBI MPLS ComplianceTE-10: gRIBI MPLS Forwarding
6338875e
Log

Openconfig Lemming

TE-9: gRIBI MPLS ComplianceTE-10: gRIBI MPLS Forwarding
84e12fc5
Log

Hardware Devices

Device
Test
Test Documentation
Raw Log

Arista 7808

TE-9: gRIBI MPLS ComplianceTE-10: gRIBI MPLS Forwarding

Cisco 8808

TE-9: gRIBI MPLS ComplianceTE-10: gRIBI MPLS Forwarding

Juniper PTX10008

TE-9: gRIBI MPLS ComplianceTE-10: gRIBI MPLS Forwarding

Nokia 7250 IXR-10e

TE-9: gRIBI MPLS ComplianceTE-10: gRIBI MPLS Forwarding

Help

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 45.707%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1347

Relevant Lines:
2947

💛  - Coveralls


Add ConfigMap for Persistent Plugin File Values

Description
This pull request introduces a ConfigMap to manage plugin file configurations effectively and refactors the directory structure within the repository for improved organization and maintainability.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

Checklist:

[ ] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Hey @hamedsalim1999,
Any updates here?


Use ComposeTestRule interface instead of concrete AndroidComposeTestRule class

This restores Roborazzi's compatibility with customized test rules.

Thanks a lot for the quick review.
Would it be possible to backport this change to the latest stable version?

@GisoBartels I don't consider it a serious bug, so would it be okay to include it in version 1.8.0-rc-2?

Yes, that's fine. Thanks.

Thank you for understanding. I'll make sure we can release it today.

@GisoBartels I've released it. Could you check it out?

Works flawlessly. Thanks for the quick release 👍


Added ServiceAccountName to VMI spec

What this PR does / why we need it:
Added ServiceAccountName to VMI spec.
When filled, the given service account token will be provided to the pod and VM (via a filesystem device).
Which issue(s) this PR fixes :
Fixes #1541
Special notes for your reviewer:
Functional test is missing, would like to get feedback if this is the right approach first.
In the VM you need to mount the provided directory:
$ sudo mkdir /mnt/serviceAccount
$ sudo mount -t 9p -o trans=virtio k8sServiceAccount /mnt/serviceAccount
$ ls /mnt/serviceAccount
ca.crt	namespace  token

Release note:
Provide service account token to the VM

ci test please

@fabiand how should the API look like? Atm I just added a "serviceAccountName" field to the VMI: when it's given, it will be mounted, else not. So no automount of the default account. Is that ok? Or should I always mount the default account? Or should this be a new VolumeSource type?

so ... a little bit of a good question.
I initially assumed to take the pod's serviceAccount token.
But it doesn't make much sense to change the serviceAccount of the pod, as it's usually set by kubevirt.
I actually wonder if we could leave it to the user to set the pod/VM ServiceAccount. It sounds reasonable, but I am not sure about any side effects atm.

I initially assumed to take the pod's serviceAccount token.
But it doesn't make much sense to change the serviceAccount of the pod, as it's usually set by kubevirt.

Kubevirt currently doesn't set a service account, so we just get the default one. But it's not used/needed (virt-launcher doesn't use the k8s client)

I actually wonder if we could leave it to the user to set the pod/VM ServiceAccount. It sounds reasonable, but I am not sure about any side effects atm.

That was my idea: let the user decide. If no account is set, also the pod won't get the default anymore. If an account is set, might be the default one or any other, that one will be configured for the pod and vm. I'm not aware of side effetcs (as virt-launcher doesn't use the account itself).

That was my idea: let the user decide. If no account is set, also the pod won't get the default anymore. If an account is set, might be the default one or any other, that one will be configured for the pod and vm. I'm not aware of side effetcs (as virt-launcher doesn't use the account itself).

:+1:  that should be fine. Virt-launcher is designed to never need k8s api access and we have no plans to ever require k8s api access for virt-launcher.

please update the user guide with a brief explanation of how to use this feature.

will do, and thx for review :)

Amazing!


Controls speed issue

Hi,
I have a problem with the controls speed because when the framerate is low it moves faster. At least when using keyboard controls and contrained to a navigation mesh. I think the issue is that velocity is multiplied twice by the delta.
At updateVelocity():
          vector2.setLength(factor * this.data.speed * dt);
And later at tick():
        end           .copy(velocity)           .multiplyScalar(dt / 1000)           .add(start);
If I replace the dt in updateVelocity() by a constant I get the same speed independently of the framerate.
Thanks!
Pau

Thanks, and sorry for the late reply — would you be able to open a PR?

Merged #267


veeam-status    add an option switch to "WarningVmLastestState" for an integer value of tolerated VM warnings

Is your feature request related to a problem? Please describe.
We have 2 blackbox appliance VM that always quit the backupjob with an warning. But the backup is without anny issuses.
The warnige by this Icinga plugin is with evry check. We don't wan to use the --always ok switch because we dont see other issues in the monitoring.
I have changed :
"
val = result['overview']['WarningVmLastestStates']
if val > 2:
"
in the code.
So the check runs perfect:-)
It would be nice when there would be a switch like "--ignore_VM_WARNINGS_count" or similar.
Thank you
Describe the solution you'd like
"--ignore_VM_WARNINGS_count" or similar name.
Alternatives
i have to hack the code by my self evry update ...
Additional context
No response

Makes sense if these values additionally become configurable:

FailedVmLastestStates (default: 0)
WarningVmLastestStates (default: 0)
FailedJobRuns (default: 0)
WarningsJobRuns (default: 0)
MaxBackupJobDuration (default: 86400)
MaxReplicaJobDuration (default: 86400)


Add setters for CodecContext.max_bit_rate and CodecContext.min_bit_rate

I'm not convinced we should merge this, initial testing shows you can get very far with the options.


api: define an API breaking change grace period.

Also, update other cases for when breaking changes are permitted.
Signed-off-by: Harvey Tuch<EMAIL_ADDRESS>

@envoyproxy/api-shepherds (since RK has an outage)


inventory extract windows tool

Tool for extract inventory directory from EVE installer for Windows OS
To list numbers of drives and help: inventory-extract-windows.exe
To extract Inventory from drive N to directory DIR: inventory-extract-windows.exe -drive N -dir DIR
Signed-off-by: Petr Fedchenkov<EMAIL_ADDRESS>

I open another PR for this #2156


Replace JSValueConst with JSValue

JSValueConst was only used for the now removed CONFIG_CHECK_JSVALUE build mode. It is kept around as an alias for JSValue in quickjs.h to avoid breaking everyone's source builds but remove it everywhere else.

If you're wondering if this was a perl -i -pe 's/JSValueConst/JSValue/g' oneliner - yes :)

Removing JSValueConst discards ownership semantics. JSValue takes ownership while JSValueConst not.

In normal builds it was equivalent.
Or are you talking about the implied semantics?


Refactor wishlists service to use Flask-RESTX

As a [role]
I need [function]
So that [benefit]
Details and Assumptions

[document what you know]

Acceptance Criteria

Refactor your micro service to use Flask-RESTX following the file layout outlined in lab-flask-restplus-swagger.
Make sure that all HTTP errors return json error messages and not html (note: You will actually be able to delete most of the error_handlers.py file because Flask-RESTX will handle most of these errors for you).
Run your test cases and make sure that your Flask-RESTX implementation still works like the original.
Add Swagger annotations to your service to document your REST API using Flask-RESTX as shown in class.

Given [some context]
When [action taken]
Then [outcome observed]

Based on effort and level of testing required - Changing pointer for this story from 5 to 8


DNS resolve issue

I don't know, seems I hit a long existing issue of alpine:
https://github.com/kubernetes/kubernetes/issues/30215
I installed microk8s from snap:
microk8s  v1.14.1  522   stable    canonical✓  classic
I checked the pod of microk8s' dns, it's:
NAME="Alpine Linux"
ID=alpine
VERSION_ID=3.6.2
PRETTY_NAME="Alpine Linux v3.6"
HOME_URL="http://alpinelinux.org"
BUG_REPORT_URL="http://bugs.alpinelinux.org"

Also, I have another cluster not mircok8s, it's kube-dns is also based on alpine, but:
VERSION_ID=3.8.2
No such issue.
So could anyone give suggestion, thanks a a lot

@vincent-pli CoreDNS will soon replace kubedns as the default dns. This is coming in the next 1.15 release (there is already a PR up). In the meantime can you try the fix suggested on this comment: https://github.com/ubuntu/microk8s/issues/271#issuecomment-480814676 ?

@ktsakalozos
Thanks very much, I works.
I struggled for the issue for 3 days 😭

@ktsakalozos
Seems my pod terminating:
coredns-55f46dd959-mpqmq    0/1     Running       0          14m
coredns-55f46dd959-pfz7l    0/1     Running       0          14m
kube-dns-6bfbdd666c-4cm8j   3/3     Terminating   0          14m

When I describe kube-dns-6bfbdd666c-4cm8j I get this:
  Warning  FailedKillPod  8m4s  kubelet, monacid1.fyre.ibm.com  error killing pod: [failed to "KillContainer" for "sidecar" with KillContainerError: "rpc error: code = Unknown desc = failed to stop contai
ner \"99dcde7d66ef313013523bcfbdf96258517f150066d82f06f28cfa65d36d5f34\": unknown error after kill: runc did not terminate sucessfully: container_linux.go:388: signaling init process caused \"permission d
enied\"\n: unknown"
, failed to "KillContainer" for "dnsmasq" with KillContainerError: "rpc error: code = Unknown desc = failed to stop container \"99892aa10e3a3fc936f6afeacba29f6a89807f01925a517861f0ee7334e181ef\": unknown
error after kill: runc did not terminate sucessfully: container_linux.go:388: signaling init process caused \"permission denied\"\n: unknown"
, failed to "KillContainer" for "kubedns" with KillContainerError: "rpc error: code = Unknown desc = failed to stop container \"b7ee15c42c231c22d6b107be96804c4f025f6c8efbc35a68af95fec78b895a27\": unknown
error after kill: runc did not terminate sucessfully: container_linux.go:388: signaling init process caused \"permission denied\"\n: unknown"
, failed to "KillPodSandbox" for "ecc995c7-85cd-11e9-a9d7-00163e01e6ab" with KillPodSandboxError: "rpc error: code = Unknown desc = failed to stop container \"b7ee15c42c231c22d6b107be96804c4f025f6c8efbc35
a68af95fec78b895a27\": failed to kill container \"b7ee15c42c231c22d6b107be96804c4f025f6c8efbc35a68af95fec78b895a27\": unknown error after kill: runc did not terminate sucessfully: container_linux.go:388:
signaling init process caused \"permission denied\"\n: unknown"
]
  Warning  FailedKillPod  7m50s  kubelet, monacid1.fyre.ibm.com  error killing pod: [failed to "KillContainer" for "dnsmasq" with KillContainerError: "rpc error: code = Unknown desc = failed to stop conta
iner \"99892aa10e3a3fc936f6afeacba29f6a89807f01925a517861f0ee7334e181ef\": unknown error after kill: runc did not terminate sucessfully: container_linux.go:388: signaling init process caused \"permission
denied\"\n: unknown"
, failed to "KillContainer" for "sidecar" with KillContainerError: "rpc error: code = Unknown desc = failed to stop container \"99dcde7d66ef313013523bcfbdf96258517f150066d82f06f28cfa65d36d5f34\": unknown
error after kill: runc did not terminate sucessfully: container_linux.go:388: signaling init process caused \"permission denied\"\n: unknown"
, failed to "KillContainer" for "kubedns" with KillContainerError: "rpc error: code = Unknown desc = failed to stop container \"b7ee15c42c231c22d6b107be96804c4f025f6c8efbc35a68af95fec78b895a27\": unknown
error after kill: runc did not terminate sucessfully: container_linux.go:388: signaling init process caused \"permission denied\"\n: unknown"
, failed to "KillPodSandbox" for "ecc995c7-85cd-11e9-a9d7-00163e01e6ab" with KillPodSandboxError: "rpc error: code = Unknown desc = failed to stop container \"b7ee15c42c231c22d6b107be96804c4f025f6c8efbc35
a68af95fec78b895a27\": failed to kill container \"b7ee15c42c231c22d6b107be96804c4f025f6c8efbc35a68af95fec78b895a27\": unknown error after kill: runc did not terminate sucessfully: container_linux.go:388:
signaling init process caused \"permission denied\"\n: unknown"
]
  Warning  FailedKillPod  7m36s  kubelet, monacid1.fyre.ibm.com  error killing pod: [failed to "KillContainer" for "sidecar" with KillContainerError: "rpc error: code = Unknown desc = failed to stop conta
iner \"99dcde7d66ef313013523bcfbdf96258517f150066d82f06f28cfa65d36d5f34\": unknown error after kill: runc did not terminate sucessfully: container_linux.go:388: signaling init process caused \"permission
denied\"\n: unknown"

And, it's not work again 😢

What distribution are you on?
Can you attach the tarball produced by microk8s.inspect?
Can you describe in detail how I can reproduce the error you are seeing in a clean system?
It is strange that the containers of the coredns pods are not running either. Do you see and errors/denials in dmesg. Anything interesting in the containerd logs? journalctl -u snap.microk8s.daemon-containerd.service

inspection-report-20190603_003619.tar.gz
My cluster is almost a clean one, only installed tekton, I follow this:
microk8s.disable dns
git clone https://github.com/coredns/deployment.git
cd deployment/kubernetes
./deploy.sh | kubectl apply -f -

it tells me the dns service is not existed, so I use -i to set a IP
it works at the very first, then failed.

If you do a dmesg you will see a number of AppArmor denials. We apply the right aa profile in https://github.com/ubuntu/microk8s/blob/master/microk8s-resources/wrappers/run-containerd-with-args . Could try microk8s.stop and microk8s.start so the profile gets reapplied?
Can you think of any reason why this profile misalignment would happen? Anything special about that machine?

Stop - Start resolve the issue, thanks.

Good to hear. I would very much be interested to understand why this happened so we can guard against such cases.


Compilation failed

I did:
svn checkout http://glfx.googlecode.com/svn/trunk/ libglfx #On 01 June 2013
cd libglfx
./configure
make

As advised per : http://ogldev.atspace.co.uk/www/tutorial34/tutorial34.html

Make exited with error 2. It failed to find "include/glfx.h".

The file "glfx.h" is actually located in "include/gl/" and not in "include/".
Simply changing "libglfx/Makefile" and "libglfx/src/Makefile" to look for it in
"include/gl/glfx.h" fixed the problem.

I am using Ubuntu 12.10 with up to date make and GCC.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 1 Jun 2013 at 7:56

Hi,
Just hit the same thing, it would be good to remove the old scripts scripts as it's confusing seeing ./configure etc too.
S

Thanks for the report! I see this is becoming an issue. I'll find some time to clean up the old stuff soon.
Max
-----Original Message-----
From: "Stuart Axon"<EMAIL_ADDRESS>Sent: 7/31/2015 16:20
To: "maizensh/glfx"<EMAIL_ADDRESS>Subject: Re: [glfx] Compilation failed (#14)
Hi,
Just hit the same thing, it would be good to remove the old scripts scripts as it's confusing seeing ./configure etc too.
S
—
Reply to this email directly or view it on GitHub.

BW - If I want to use this, e.g. with the examples at http://ogldev.atspace.co.uk/ do I need to copy glfx.h to /usr/include as well?
I manually copied libglfx.so to /usr/local/lib - should make install do this ?

Oops, just noticed it does copy the .h file


Add withdrawal support

Game mechanics: https://docs.google.com/document/d/11gHsSREitfHmrXP-DvFkNJ8X1oTtV8zo0EdQBeEzUKU/edit?usp=sharing
Thanks @ngmachado for the work.


TRG 5.04 CPU / MEM resource requests and limits and are properly set

Limits are not set within values.yaml for the portal chart
https://eclipse-tractusx.github.io/docs/release/trg-5/trg-5-04
https://github.com/eclipse-tractusx/portal/blob/b1b2336f5a37af2dd0f86bf71300b2842905edaf/charts/portal/values.yaml#L326-L328

I'm really not convinced about setting limits in the default values.yaml, this should a conscious choice.

Hmm just following our own rules.
And sure in case of memory ressource i agree a bit, because of MEM Limit

Memory is not a 'stretchable' resource and kubernetes will delete a pod if it starts using more memory than expected.

but on CPU level your chart will consume more CPU even when it is available.

To have the CPU Limit higher than the request allows the pod to use more CPU when available and utilizes a node resources better

And as far as i know it is a good practice to have ressource limits to our pods
https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#requests-and-limits

@FaGru3n I'm really not convinced about setting limits in the default values.yaml, this should a conscious choice.

Hi @evegufy, we set this TRG in place, because we as teams potentially have the best insights in memory and CPU consumption based on our tests. That's why defining it in default values will give other users a glimpse in what to expect.
Of course everyone else can overwrite it to match their needs. Setting defaults won't break anything.
Especially the consortia infra tooling should provide good insights historical values that we could use here

Hi @evegufy,
does that mean, you won't do that for this release? I don't see any reason not doing that. As I said, it does not break anything, since it can always be overwritten for each deployment.
This is definitely non-compliant with our release guidelines

Hi @SebastianBezold, I won't do it for this release as I want to properly test it. Even if this change might not be breaking, I also don't see any reason why to force it into the release without proper testing. Please mark is as a finding to be addressed with the next release.

Clarification: CPU and memory requests are set. CPU and memory requests limits are configured but commented out in the values.yaml but can be set at all times when using the chart. Setting the limits in the values.yaml will be addressed in the next release.

Hi @evegufy,
thanks for info should we leave this issue open or will this taken over for the next release (24.05)?
Thanks in advance.


Question regarding Seq2Seq  input data

Hello, I'm having a question reading the input of Seq2Seq model. In the paper you mentioned that "The features of nodes are added as the additional inputs." From my understanding on the last dimension the input should have a size of: 9 (node features) + 8 (neighbors) * 2 (x,y coordinates). I searched everywhere in the MyGRUCell and I can not find such shape, furthermore I can see that the features are not used in the cell.
Thank you in advance and looking forward to hearing from you.

Hi, The seq2seq.py file refers to the seq2seq architectures in ST-MetaNet.
The codes of original baselines (including Seq2Seq) are not included because they tackle features in a different way.
For simplicity, this repository includes the major codes of ST-MetaNet and a variant of Seq2Seq, to present the improvement.
If you want to reproduce our original baselines, you can directly modify dataloader.py to concatenate static features with the dynamic temporal readings (all static features and dynamic readings are provided in dataloader.py).


Are you interested in creating a PR about this work for mmtracking?

Wonderful work!
We're very interested in your work.  VIS is a future key development direction in mmtracking. We'll appreciate it if you can create a PR about this work in mmtracking.

Hi, @JingweiZhang12! Thanks for your interest in our work!
As a MMDetection based project, our work benefits a lot from OpenMMLab community, thanks for your and your team's efforts.
And once time is available, I will try to integrate our TeViT to the mmtracking project.


Add tutorial on how to access a screen without login

Opening an anonymous screen before login may be a common use case. I find this answer very useful:
https://forum.jmix.io/t/how-can-i-verify-and-use-the-anonymous-user-functionality/938/3
Why not adding it to the docs?

Fixed in #385

Add a note about anonymous side menu, see https://github.com/jmix-framework/jmix/issues/690


Support Helm's NS creation for TargetNamespace

This adds support for creating the target release namespace if it is not
present which can be be useful in certain scenarios.
Note that when the release is uninstalled, the namespace is not removed
and remains on the cluster, and managing your namespace outside of
the HelmRelease is advised.
Fixes: #130

This feature is useful. Please review this PR. Thanks!


Tesla stopped working

Suddenly my Tesla integration is not working. All entities are unavailable.  I am able to get on the Tesla website without issues. I also deleted the integration and set it up again.  Still does not wrk.
Log Details (ERROR)
Tue Feb 18 2020 17:21:28 GMT-0500 (EST)
Error setting up entry<EMAIL_ADDRESS>for tesla
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 936, in _wrap_create_connection
return await self._loop.create_connection(*args, **kwargs)  # type: ignore  # noqa
File "/usr/local/lib/python3.7/asyncio/base_events.py", line 985, in create_connection
ssl_handshake_timeout=ssl_handshake_timeout)
File "/usr/local/lib/python3.7/asyncio/base_events.py", line 1013, in _create_connection_transport
await waiter
File "/usr/local/lib/python3.7/asyncio/selector_events.py", line 870, in write
n = self._sock.send(data)
ConnectionResetError: [Errno 104] Connection reset by peer
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 215, in async_setup
hass, self
File "/usr/src/homeassistant/homeassistant/components/tesla/init.py", line 125, in async_setup_entry
(refresh_token, access_token) = await controller.connect()
File "/usr/local/lib/python3.7/site-packages/teslajsonpy/controller.py", line 80, in connect
cars = await self.get_vehicles()
File "/usr/local/lib/python3.7/site-packages/teslajsonpy/controller.py", line 300, in get_vehicles
return (await self.__connection.get("vehicles"))["response"]
File "/usr/local/lib/python3.7/site-packages/teslajsonpy/connection.py", line 92, in get
return await self.post(command, "get", None)
File "/usr/local/lib/python3.7/site-packages/teslajsonpy/connection.py", line 107, in post
f"{self.api}{command}", method=method, headers=self.head, data=data
File "/usr/local/lib/python3.7/site-packages/teslajsonpy/connection.py", line 138, in __open
url, headers=headers, data=data
File "/usr/local/lib/python3.7/site-packages/aiohttp/client.py", line 483, in _request
timeout=real_timeout
File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 523, in connect
proto = await self._create_connection(req, traces, timeout)
File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 859, in _create_connection
req, traces, timeout)
File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 1004, in _create_direct_connection
raise last_exc
File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 986, in _create_direct_connection
req=req, client_error=client_error)
File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 943, in _wrap_create_connection
raise client_error(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host owner-api.teslamotors.com:443 ssl:None [Connection reset by peer]

Duplicate of #30443