kubeadm: add guide for kubelet serving certs and metrics-server

note: targeting the master branch is accurate for this change.
Include a new section of the kubeadm certificate management page
to talk about kubelet serving certificates and how to make
them signed. Also include a note about using secure connection
with the metrics-server.
fixes https://github.com/kubernetes/kubeadm/issues/1602
/sig cluster-lifecycle

/cc @fabriziopandini @randomvariable

updated to address the review comments.

@neolit123: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Needs a rebase, but assuming the obvious approach to rebasing: LGTM.

rebased.
/cc @fabriziopandini
for tech review / LGTM.

@sftim
updated with your two suggestions above.
tech LGTM already passed by @fabriziopandini

/lgtm


Failed to activate the organized package

Updated to the latest version as of today, restarted Atom per request, got the error below.
Atom: 1.21.1 x64
Electron: 1.6.15
OS: Mac OS X 10.13
Thrown From: organized package 0.8.0
Stack Trace
Failed to activate the organized package
At Cannot read property 'getGrammar' of undefined

TypeError: Cannot read property 'getGrammar' of undefined
    at _findInDirectories (/packages/organized/lib/sidebar-items.coffee:97:36)
    at findInDirectories (/packages/organized/lib/sidebar-items.coffee:60:3)
    at SidebarView.module.exports.SidebarView.populateSidebarItems (/packages/organized/lib/sidebar-view.coffee:166:9)
    at SidebarView.module.exports.SidebarView.refreshAll (/packages/organized/lib/sidebar-view.coffee:125:6)
    at SidebarView.module.exports.SidebarView.activate (/packages/organized/lib/sidebar-view.coffee:80:8)
    at Object.activate (/packages/organized/lib/organized.coffee:169:14)
    at Package.module.exports.Package.activateNow (/Applications/Atom.app/Contents/Resources/app/src/package.js:253:25)
    at /Applications/Atom.app/Contents/Resources/app/src/package.js:225:38
    at Package.module.exports.Package.measure (/Applications/Atom.app/Contents/Resources/app/src/package.js:99:21)
    at /Applications/Atom.app/Contents/Resources/app/src/package.js:218:32
    at Package.module.exports.Package.activate (/Applications/Atom.app/Contents/Resources/app/src/package.js:215:40)
    at PackageManager.activatePackage (/Applications/Atom.app/Contents/Resources/app/src/package-manager.js:690:42)
    at config.transactAsync (/Applications/Atom.app/Contents/Resources/app/src/package-manager.js:665:36)
    at Config.module.exports.Config.transactAsync (/Applications/Atom.app/Contents/Resources/app/src/config.js:367:24)
    at PackageManager.activatePackages (/Applications/Atom.app/Contents/Resources/app/src/package-manager.js:663:23)
    at PackageManager.activate (/Applications/Atom.app/Contents/Resources/app/src/package-manager.js:646:50)
    at /Applications/Atom.app/Contents/Resources/app/src/atom-environment.js:854:36

Commands

Non-Core Packages
busy-signal 1.4.3
intentions 1.1.5
language-docker 1.1.8
language-elixir 0.20.3
language-elm 1.5.0
language-erlang 3.2.0
language-rust 0.4.12
lines 0.13.1
linter 2.2.0
linter-elixirc 1.7.0
linter-elm-make 0.26.2
linter-erlang 0.4.0
linter-js-standard 4.0.2
linter-jshint 3.1.6
linter-python 3.1.2
linter-rust 0.8.0
linter-toml 0.1.1
linter-ui-default 1.6.10
organized 0.8.0
project-manager 3.3.5
standard-formatter 2.8.0
standardjs-snippets 2.6.2

0.8.1 has a fix and has been released, please let me know if you still see the problem.


net/http Client.Do() hangs when StdOut/StdErr redirected

Go Version 1.9.1
Latest
OS: linux/amd64

Using https://github.com/VividCortex/godaemon in an application for daemon support disconnects the StdOut and StdErr.     The application uses https://github.com/bndr/gojenkins , which makes a http request using net/http Client.Do()...    Which hangs and never returns
If the stdout/stderr are captured and stored in a file then the Client.Do() works

@ArcticSnowman, it would help if there you could produce a reduced test case demonstrating what you expect to happen, and what actually happens. My guess is that Do() is hanging because it's trying to read from the io.Reader for the http request body, and that Read() call is blocking.


⚠ gorzdrav.org has degraded performance

In 70bf891, gorzdrav.org (https://gorzdrav.org) experienced degraded performance:

HTTP code: 200
Response time: 2140 ms

Resolved: gorzdrav.org performance has improved in 9e1d052.


[Bug]: Buf linter reports incorrect source line numbers

What happened?
The reported line numbers from running the buf_lint_aspect are always <souce_path>:1:1<messaage>, which adds friction to resolving lint errors especially when the source file is large.
Version
Development (host) and target OS/architectures:
Output of bazel --version: 7.1.1
Version of the Aspect rules, or other relevant rules from your
WORKSPACE or MODULE.bazel file: HEAD
How to reproduce
This can be reproduced with the file.proto source in example/
Via aspect:
bazel build --aspects=//tools/lint:linters.bzl%buf --@aspect_rules_lint//lint:fail_on_violation --output_groups=rules_lint_report //src:foo_proto
INFO: Analyzed target //src:foo_proto (0 packages loaded, 0 targets configured).

Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
--buf-plugin_out: src/file.proto:1:1:Import "src/unused.proto" is unused.
Aspect //tools/lint:linters.bzl%buf of //src:foo_proto failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 0.168s, Critical Path: 0.03s
INFO: 2 processes: 2 internal.
ERROR: Build did NOT complete successfully

Via buf cli
bazel run @rules_buf_toolchains//:buf -- lint --config=buf.yaml src/file.proto
WARNING: Build option --@@aspect_rules_lint~//lint:fail_on_violation has changed, discarding analysis cache (this can be expensive, see https://bazel.build/advanced/performance/iteration-speed).
INFO: Analyzed target @@rules_buf~~buf~rules_buf_toolchains//:buf (0 packages loaded, 1 target configured).
INFO: Found 1 target...
INFO: Elapsed time: 0.224s, Critical Path: 0.00s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action
INFO: Running command line: /home/.cache/bazel/_bazel/d387874fc4e6234b1e2f92e13a10d0a3/external/rules_buf~~buf~rules_buf_toolchains/buf lint '--config=buf.yaml' src/file.proto
src/file.proto:3:1:Import "src/unused.proto" is unused.

As a sanity check aspect lint produces the same output:
aspect lint //src:foo_proto
INFO: Analyzed target //src:foo_proto (232 packages loaded, 9814 targets configured).
INFO: Found 1 target...
Aspect //tools/lint:linters.bzl%buf of //src:foo_proto up-to-date:
  bazel-bin/src/foo_proto.AspectRulesLintBuf.report
  bazel-bin/src/foo_proto.AspectRulesLintBuf.report.exit_code
INFO: Elapsed time: 4.369s, Critical Path: 0.03s
INFO: 2 processes: 1 internal, 1 linux-sandbox.
INFO: Build completed successfully, 2 total actions
Lint results for //src:foo_proto:

--buf-plugin_out: src/file.proto:1:1:Import "src/unused.proto" is unused.

Any other information?
I haven't more than glanced at the source code, but I believe this is a problem with the protoc plugin protoc-gen-but-lint and not rules_lint. The buf cli is a go program that lints the sources directly and not as a protoc plugin. It may be the case that using the protoc plugin also introduces subtle differences in the DX if IDE plugins are integrating with the buf cli directly.

@alexeagle Here's what I see, and I saw the same problem with rules_proto_grpc and their buf lint integration in the past. That makes me thing it's a general problem with the protoc plugin, but I don't know how to square that with the smoke test you performed the other day.

To your earlier point, I do think switching to call buf lint instead of protoc --plugin=some-buf-thing is likely more correct and easier to reproduce or get help from the Buf team. Worth investigation.


Topic/amiga get user name

Since getuid() and getpwuid() exist on NG systems, we might as well use them.

Codecov Report

Merging #4985 into master will increase coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #4985      +/-   ##
==========================================
+ Coverage   81.72%   81.75%   +0.02%
==========================================
  Files         131      131
  Lines      146540   146540
==========================================
+ Hits       119761   119797      +36
+ Misses      26779    26743      -36

Impacted Files
Coverage Δ

src/terminal.c
81.89% <0%> (-0.04%)
:arrow_down:

src/os_unix.c
63.5% <0%> (+0.04%)
:arrow_up:

src/message.c
79.52% <0%> (+0.05%)
:arrow_up:

src/gui_gtk_x11.c
58.21% <0%> (+0.09%)
:arrow_up:

src/sign.c
94.59% <0%> (+0.18%)
:arrow_up:

src/netbeans.c
27.46% <0%> (+0.22%)
:arrow_up:

src/profiler.c
94.67% <0%> (+0.56%)
:arrow_up:

src/gui.c
64.32% <0%> (+0.61%)
:arrow_up:

src/ui.c
70.32% <0%> (+1.25%)
: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 d2c1fb4...91328a8. Read the comment docs.

@yegappan's comment is not forwarded here.
https://groups.google.com/d/msg/vim_dev/Y9Ir9BWdIMU/YZ54udMoBQAJ

It looks like you are building Vim on Amiga. Recently many refactoring
changes were made to the Vim sources. I couldn't verify these changes
on an Amiga platform (as i don't have access to one). Are you able to
build the different Vim variants (tiny, normal, huge) on Amiga successfully
with the latest sources?


feat(dashboards): Filter status indicators

SUMMARY

This adds a new filter indicator which is intended to take the place of the "teeth" style indicators. This indicator is lower profile, and less confusing. If a filter is ineligible for a given chart, that is now displayed on the indicator.
Currently writing tests and applying final tweaks.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

On the left, a chart with 2 filters applied. On the right, a chart indicating that some filters could not be applied.
TEST PLAN

ADDITIONAL INFORMATION

[ ] Has associated issue:
[x] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

Having both dropdown and teeth indicator at the same time? is it a little confusing and duplicated?

yes, the teeth will be gone~

Codecov Report

Merging #10936 into master will decrease coverage by 5.39%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master   #10936      +/-   ##
==========================================
- Coverage   65.77%   60.38%   -5.40%
==========================================
  Files         816      383     -433
  Lines       38395    24172   -14223
  Branches     3607        0    -3607
==========================================
- Hits        25256    14597   -10659
+ Misses      13031     9575    -3456
+ Partials      108        0     -108

Flag
Coverage Δ

#cypress
?

#javascript
?

#python
60.38% <100.00%> (-1.04%)
:arrow_down:

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

Impacted Files
Coverage Δ

superset/connectors/base/models.py
89.43% <ø> (ø)

superset/views/core.py
74.22% <ø> (-0.25%)
:arrow_down:

superset/viz.py
58.07% <100.00%> (+0.17%)
:arrow_up:

superset/db_engines/hive.py
0.00% <0.00%> (-85.72%)
:arrow_down:

superset/databases/commands/create.py
31.91% <0.00%> (-59.58%)
:arrow_down:

superset/db_engine_specs/hive.py
53.90% <0.00%> (-30.08%)
:arrow_down:

superset/views/database/mixins.py
59.64% <0.00%> (-22.81%)
:arrow_down:

superset/db_engine_specs/mysql.py
79.16% <0.00%> (-12.50%)
:arrow_down:

superset/db_engine_specs/presto.py
70.85% <0.00%> (-11.44%)
:arrow_down:

superset/databases/commands/update.py
85.71% <0.00%> (-8.17%)
:arrow_down:

... and 440 more

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 448a41a...45354fc. Read the comment docs.

A personal opinion: I really liked the color part of the filters that allowed to view in a glimpse what filter was where.
The number and details of the filters is interesting too, but don't we loose a part of the info (and the nice colours in the filter box)?

Thanks for the comment, Cory!
As we are slowly moving towards our new design, proposed in SIP34,
https://projects.invisionapp.com/share/BNVBOEJRWQ2#/screens/398392315
we try to create better consistency and cleanness across the product.
During our research, we noticed that when there are too many charts and
filters in a dashboard, the colorful indicators on the side become visually
overwhelming, and the indicators take up lots of space in the dashboard.
we went through multiple phases of research and design exploration to come
up with the new solution. Going forward, our design process will be more
transparent and we will present the finding community wise. @Mihir Chahuan
<EMAIL_ADDRESS>please chime in if you have additional comments.
[image: Screen Shot 2020-09-22 at 2.07.45 PM.png]
[image: Screen Shot 2020-09-22 at 2.07.55 PM.png]
[image: Screen Shot 2020-09-22 at 2.08.18 PM.png]
[image: Screen Shot 2020-09-22 at 2.08.25 PM.png]
[image: Screen Shot 2020-09-22 at 2.08.31 PM.png]
On Tue, Sep 22, 2020 at 12:44 PM CoryChaplin<EMAIL_ADDRESS>wrote:

A personal opinion: I really liked the color part of the filters that
allowed to view in a glimpse what filter was where.
The number and details of the filters is interesting too, but don't we
loose a part of the info (and the nice colours in the filter box)?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-superset/pull/10936#issuecomment-696940350,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQFR5U7VP5EELBSPJYAYCULSHD5DRANCNFSM4RQU4IOA
.

Thanks for the feedback @JunlinC , I get your point. Goodbye colours :)

Once we implement the new dashboard native filter with a filter bar as a
whole, this indicator new design will probably make more sense!
On Wed, Sep 23, 2020 at 9:58 AM CoryChaplin<EMAIL_ADDRESS>wrote:

Thanks for the feedback @JunlinC https://github.com/JunlinC , I get
your point. Goodbye colours :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-superset/pull/10936#issuecomment-697695562,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQFR5U4Q7PPCSR3ROFOYUMTSHISK3ANCNFSM4RQU4IOA
.

@suddjian according to SIP-45 discussion, when one or more filters are not applicable to the chart, we will still show the query results (which has no wrong filter_fields applied). We should not show "No Results"

@suddjian according to SIP-45 discussion, when one or more filters are not applicable to the chart, we will still show the chart with query results, but not applied with wrong filter_fields. We should not show "No Results".

The chart in the screenshot is only showing "No Results" because there genuinely are no results for that query. That is not because of the filters being unapplicable.

I want to raise a usability concern about the new design @junlincc
Before:

when charts are loaded in dashboard, from filter indicators I can tell each chart should be applicable to any dashboard filters or not, even I don't actually apply any filters to this dashboard.
when i focus/interact with any filter field, I can see which charts will be affected by this filter field, even I don't actually apply the filter. This is really useful when user want to double check filter scope is correct.

After:
All these indication functions are lost.
BEFORE:

AFTER:

We're addressing Grace's and a couple other QA concerns. Remaining items:
[ ] Address edge case: title overflow
[ ] Filter icon size/alignment
[ ] Indicator warning color when a filter is invalid
[ ] Display number of invalid filters in indicator when relevant
[ ] Highlight scoped charts when a filter control has focus
[ ] Display the filter indicator when filters are scoped to a chart, but inactive

Okay, concerns should be addressed here. I think it's ready for a re-review. Here's a clip showing the new changes.

Hi @suddjian Thank you for extra work to address my concerns! could you update description section with latest design, so that everyone in the open source community also see what's expected behaviors? Thank you!

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@152315d). Click here to learn what that means.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##             master   #10936   +/-   ##
=========================================
  Coverage          ?   61.35%
=========================================
  Files             ?      391
  Lines             ?    24490
  Branches          ?        0
=========================================
  Hits              ?    15027
  Misses            ?     9463
  Partials          ?        0

Flag
Coverage Δ

#python
61.35% <100.00%> (?)

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

Impacted Files
Coverage Δ

superset/views/core.py
74.30% <ø> (ø)

superset/viz.py
57.62% <100.00%> (ø)

Continue to review full report at Codecov.

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

found a few bugs:

chart header controls:

click on filter field name didn't highlight filter_box:

Thanks for finding those, Grace

@graceguo-supercat fixed those issues. The third issue was tricky, out adding a filter: blur on a component messes up the layering. I think it might actually be a browser bug.

Wow that really pops (!)

Hi @suddjian I found a few new issues to report:

After apply 1 filter, Unset group can not unfold:

Please create a date filter with time column/time granularity control. This feature (and filter indicators) are broken in this feature branch.

Focus/blue filter field behavior is not consistent:
. Charts still be highlighted after user click "APPLY" button.

I had seen these issues when i implemented the last version of filter indicators, but currently some of useful code was removed. The system was a little complicated for a reason :)

dashboard default time range filter is not being applied but sent to Unset

What i observed is dashboard default time-range (and granularity) were applied. Filter indicator show them as Unset, but they should be "Applied".


feat: Adds list entity creation dialog to the lu editor

Description
Adds list entity to LU editor toolbar
Adds list entity creation dialog to the LU editor
Task Item
closes #7930
closes #7931
fixes #8020
Screenshots

Coverage decreased (-0.005%) to 50.03% when pulling 0545db85d2e991a45d6333368c31ac681dd63cf1 on sorgh/7931 into b33471d4038f140b85c60fcd8350cc542f73f7c3 on main.

will create a clean one


CoreHost example doesn't work - Unable to load DLL 'CoreInterop.dll'

Hi,
I'm getting the following error while executing the snippet about the "[CoreHost] (https://github.com/Esri/arcgis-pro-sdk/blob/master/Examples/CoreHost/ProSnippets.cs)" module:
System.DllNotFoundException
  HResult=0x80131524
  Message=System.DllNotFoundException: 'Unable to load DLL 'CoreInterop.dll': The specified module could not be found. (Exception from HRESULT : 0x8007007E)'
  Source=ArcGIS.Core

The error says that the DLL 'CoreInterop.dll' is missing but the documentation doesn't mention that we have to add the reference to this DLL, it only refers to ArcGIS.Core.dll and ArcGIS.CoreHost.dll. And even if I add the reference of the library "CoreInterop.dll", it doesn't work.
I followed all the instructions in this link:
https://github.com/Esri/arcgis-pro-sdk-community-samples/tree/master/CoreHost/CoreHostSample
and here:
https://github.com/esri/arcgis-pro-sdk/wiki/proconcepts-CoreHost
I'm using:

Visual Studio Community 2017 (v15.7.5) with .NET Framework 4.6.1
ArcGIS Pro 2.2.1
ArcGIS Pro SDK for .NET <IP_ADDRESS>13

Am I doing something wrong or missed something? Can anybody help me with this issue please?
Regards,
Fabian

[DUPLICATE]

---> https://github.com/Esri/arcgis-pro-sdk-community-samples/issues/30


The code doesn't work on Windows. SOLVED

Author made mistake, and the code is platform dependend. System path error.
I added this to code and it works:
process.env.PWD = process.cwd();

However since I'm beginner in node.js, I would like someone experienced to add it into code here, permamently.
I just do not want to make any conflict / errors on Mac OS


Add environment.yaml

The project needs an environment file we, as well as any future researchers interested in reproduction, can use

Hi Jesse, can you please add pandas_datareader and wbdata?
I will also prob have a few other data downloader packages to add by Mondy.
Andrew

What's the difference between pandas_datareader.wb.WorldBankReader and wbdata?

The latter was the first thing that came up when I googled how to pull WB data into python ;)
As you were, this makes sense. Some of the data sources I found don't have convenient ways to pull them in. Can I download the raw CSV and upload to a raw data folder? What's best practice here?

Use the requests package to directly download if possible. If we can't do that, we add a data_sources.md file with links. We should archive the pages as well so that our work is robust to changes to the external websites.

We should avoid hosting data on our repo if at all possible, because ideally whenever the external sources update, we can automatically get the newest stuff. If we REALLY can't find a better option we can download CSVs that are "sufficiently small"


fix(mat): Fix MAT swipe navigation

Resolves YOMO-515

While testing this approach
ERROR  Warning: The final argument passed to useEffect changed size between renders. The order and size of this array must remain constant.

Previous: [[object Object], send-edit-amount-_8XoJ4b7GWhJVu1d_ucxg, send-edit-amount]
Incoming: [[object Object], send-edit-amount-_8XoJ4b7GWhJVu1d_ucxg, send-edit-amount, send-list-amounts-to-send]

Router navigation adds some randomness to its keys.


Dynamic tables & error logger feedback

The functional implementation of https://github.com/davidusb-geek/emhass/issues/186 & https://github.com/davidusb-geek/emhass/issues/191
Changes:

new actionLogs.txt is generated in datapath storing sessions app.logger info
on successful html button press, fetch is called to get  html containing latest table data
on html button press, If app.logger ERROR is present, send action log back and present on page.

Note: As of first commit, this PR still needs refining, please wait to merge. Any suggestions appreciated.

@davidusb-geek feel free to test this and see what you think.

Those are some great functionalities!
Ok, will do some testing this week-end.

Ok no problem. Like I said I will only be able to test this week-end

@GeoDerp you are doing some fantastic work in extending the functionality of EMHASS.
Thanks for your assistance! 🎉🎉

Two notes on the error logs side of things:

it only prints app.logger outputs.

If we continue going down this route we will just need to make sure we got app.logger.error for all likely fail cases. (If there isn't already)
else, we can modify it to print all console logs.
personally  I like the idea to get a little info from the webpage and get the rest via the console

it's currently set to app.logger.info but I may change to debug.

I'm hopping that this logger implementation makes sense and can help others send informative information back to the html.

Sorry @davidusb-geek I closed the other PR as I merged those changes into this one as they are kinda related now.
Last things I added

url and key being incorect produces logger.error
sensor being incorect produces logger.error
days_to_retrieve default to 2 if number is under 2. It also produces  logger.warning

@davidusb-geek  I'm sorry in advance for all the testing

Just a heads up @davidusb-geek. The reason why i'm setting returns on the functions back to web_server, is that if there is an uncaught python error it stops the current function and runs the next in the action causing more errors (or just dosn't finish the function at all).
Whereas, if I return a string indicating an error has occurred in that function, I can stop that action and send back the log to the user on the website.
This is just how I would program it. Back when I did C in uni, we used to set returns on every function with 0 (fail) or 1 (pass). We could then check if that function worked every time and move to next. If not print issue.

@davidusb-geek  Im pritty happy with this PR now. It's not perfect but I don't believe there will be any problems.
I'm currently looking now to see how difficult it would be to set True or Fail returns on every logger.error and end of each function.

Ok nice work!
I will at this and test it during the week-end

If you're interested; https://github.com/GeoDerp/emhass/tree/Error-Suppression-Testing is my testing branch for testing returns on all functions and if statements to make sure those functions ran without an issue. (If not, return back to webserver and the user will see the logger.errors)
I literally just pasted responses and if statements everywhere without thinking about it methodically 😅.
But it might be a good idea of what my concept is. 🤔


Support of NTF Files

Hello!
I wanted to start off by saying that I am a fan of the application! Right now, I am in the process of testing it and wondering if it was possible to allow users to select NTF files when creating tasks. I saw that your "media.mimetypes" file contains what looks like all the usable file types. Would it be as simple to just add the line "image/nitf ntf" to add the support? I'm not too versed in NTF, but from what I have read, it is not something that can be simply read without proper conversion software. Overall, my question would be whether or not if you think that CVAT would be capable of having a converter like that implemented into it to support NTF files.
Thank you!

@KevinLe1997 , we support all formats which supported by PIL (http://pillow.readthedocs.io). PIL doesn't support the format.
One way to support the format is to use the patch (which will be merged soon): https://github.com/opencv/cvat/pull/434. Thus you can provide a custom extractor. It seems that https://github.com/OSGeo/GDAL library can read the image format. If you can send us a PR it will be awesome! It should not be a big pain to support it.

@KevinLe1997 , do you have an example file?


[WIP] Fix default title display and search icon styles

@ravichdev could we delete the branch?

@ravichdev could we delete the branch?


Add a "cargo bench --debug" option

It builds the benchmarks in debug mode and then runs them.  It's useful
in a CI context where it's important that the benches aren't broken, but
it's not important how fast they run.
Fixes #6445

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @ehuss (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

Thanks for the PR! I've sort of long wanted to have an inverse to --release across the board on all of Cargo's subcommands, enabled by default if nothing else is passed. I think this flag may best be named --dev, however, as that's what the profile in Cargo.toml is called as well.
I think that I'd personally prefer to see this added across the board rather than just cargo bench if we add it, and I think for other subcommands we'll want to be sure to reject --dev --release but otherwise accept them in isolation.
As another aside, I think it's a longstanding bug that cargo bench also doesn't accept --release!
Would you be willing to help tackle some of these surrounding issues as well?

In fact, I just discovered that cargo test --benches does almost the same thing as what this PR does (but in a workspace, it also runs unit tests; that's a different bug).  So that can satisfy my needs.  But I agree that it would be nice if --debug or --dev were supported across the board.  So are you saying that you want to add the following commands?
cargo bench --dev # build and run benchmarks in debug mode
cargo bench --release # has no effect except to be exclusive with --dev
cargo build --dev # has no effect except to be exclusive with --release
cargo check --dev # has no effect except to be exclusive with --release
cargo doc --dev # has no effect except to be exclusive with --release
cargo run --dev # has no effect except to be exclusive with --release
cargo test --dev # has no effect except to be exclusive with --release
cargo clean --dev # Not sure what to do here?
cargo install --dev # synonym for --debug

cargo clean --dev clearing out just target/debug would be lovely and mirror cargo clean --release as of #6349.

Ok we discussed this at a recent Cargo triage meeting and the conclusion was that we're unlikely to land this as-is for now. Instead @ehuss pointed out that a strategy like https://github.com/rust-lang/rfcs/pull/2678 is likely going to be our best bet where --profile=debug can be passed anywhere. Thanks for the PR though!


Populate Events Page via Backend Instead of Hardcoding

Feature Request:
Background:
The current implementation of the events page involves hardcoded event listings. As our platform grows and the number of events increases, this method becomes unsustainable and inefficient. To streamline the management of events and allow for dynamic updates, we should transition to populating the events page via the backend.
Feature:

Backend Integration: Fetch event data from the backend to display on the events page.
Dynamic Loading: Events should load dynamically.

Benefits:

Scalability: Easier management of events as the platform scales.
Centralized Management: Event data can be managed from a central location (MongoDB database), reducing redundancy and potential inconsistencies.

The current code has static HTML pages for each event. The solution doesn't seem scalable.

The story of every page🥲
Just an idea , maybe use modals which could be reused instead of redirecting them to a whole new page to view event details.

Lets use the matieral Modal itself maybe : https://mui.com/material-ui/react-modal/

Lets use the matieral UI Modal itself maybe : https://mui.com/material-ui/react-modal/

+1 to the above idea

@Diksha-Maurya @sharonjoji99 Thanks!! Will do

Accidentally closed the issue.


[Segment] Attached segments have width greater then 100%

After upgrading to version 2.4.1, one of my coworkers (👋 @lukaszstasiakux) noticed an issue with the ui.attached.segment class. It appeared to be overflowing the space it was previously fitting in. In doing some investigating, I believe there may be a math bug with the following two variables:
https://github.com/Semantic-Org/Semantic-UI/blob/2.4.1/src/themes/default/elements/segment.variables#L105-L106
Which was introduced in the following commit:
https://github.com/Semantic-Org/Semantic-UI/commit/c249b6c88b198e5d9b4694052157001d53b66584
If you closely at the changes in the above commit for the segment.variables file, you can see that were were previous using addition with a negative number. However, with the changes that were made, we were now using subtraction a negative number. Whoops.
Steps

Open .../examples/attached.html in a browser
Inspect the Segment 1 segment

Expected Result
The width and max-width properties should be 98%
Actual Result
The width and max-width properties are 102%
Version
2.4.1
Testcase
https://jsfiddle.net/notfunk/yax4qewz/2/

Proposed solution: https://github.com/Semantic-Org/Semantic-UI/pull/6764


[DRAFT] ERROR: Failed to connect to "/var/run/keyd.socket" (No such file or directory) keyd -m works

ERROR: Failed to connect to "/var/run/keyd.socket", make sure the daemon is running and you have permission to access the socket.
Gnome Wayland Fedora 40
https://github.com/rvaiya/keyd/issues/743
$ cat /var/run/keyd.socket
cat: /var/run/keyd.socket: No such file or directory

[ids]

*

[main]

leftshift = oneshot(shift)

Closed: fixed by reading the README again.
$ sudo systemctl restart keyd
$ sudo reload keyd

Thank you, this just solved my problem too! Btw, the second command is sudo keyd reload, not reload keyd.
Also, to leave a potentially time-saving search result and help for others in my circumstance, I'm used to modifying /usr/share/X11/xkb/symbols/us and /usr/share/X11/xkb/rules/evdev.xml to add my own keyboard layout, but that doesn't work in Bazzite, which is immutable/atomic and based on Fedora Ublue, similar to Silverblue and Kinoite.
Keyd does work, and to make installing it easier, since on these distros dnf is just an alias to rpm-ostree which doesn't on its own support copr, I used rpm-copr:
https://github.com/34N0/rpm-copr
After curling the install command on that repo,
sudo rpm-copr enable alternateved/keyd
sudo rpm-ostree install keyd

Then restart so ostree can layer the package, and follow the config steps from this repo.
sudo mkdir /etc/keyd
sudoedit /etc/keyd/default.conf
sudo systemctl restart keyd
sudo reload keyd


Feat: update add_fk_static_timestamp_column with new match logic

After discussions with OPMI, new rules to match GTFS-RT events to GTFS schedules are as follows:
Matching between a GTFS-RT events and a GTFS-static schedule version will be done on a whole start_date / "service_date" basis. Each distinct start_date / "service_date" of GTFS-RT data will be matched to only one GTFS-static version.
When ingesting live GTFS Schedule files, the feed_active_date will be extracted from the ISO timestamp found in the feed_version field of the FEED_INFO table. This will be the first date that a GTFS-static version can be applied to GTFS-RT events.
GTFS-RT start_date must be between feed_start_date and feed_end_date in FEED_INFO, start_date must also be less than or equal to feed_active_date.  The most recent schedule that meets these criteria will be matched
When processing archived GTFS-static schedules, these rules change because feed_start_date and feed_end_date are retroactively modified in archived schedules so that only one GTFS-static version is applicable per calendar day.
If the initial matching fails, we will drop the requirements of matching on feed_active_date and just match start_date by feed_start_date and feed_end_date.
Asana Task: https://app.asana.com/0/1204389777951216/1204500786018314

could a schedule be added that would require we retroactively update our fk_static_timestamp "key"? it seems like if one is uploaded where the feed activation date is later than the date in some of our trips, we could want to change that?
also, now that i see it and we're doing this adding twice, it makes me wonder if we shouldn't be calling this on the vehicle events data frames after we join the trip updates and vehicle positions dataframes. thats maybe outside of scope here though?

The discussions we had with OPMI resulted in the decision to not retroactively update our fk_static_timestamp keys. When processing live GTFS Schedule files, we will only start applying them on the day there were received, based on the active date included in the feed_version field.
Currently, we can not call this function later, after joining the dataframes, because joining to static data is required to add the parent_station field (for event grouping) and dropping bus events from the dataframes. Calling this later would result in much larger dataframes moving through the rest of the processing pipeline.

is there a link we can post as a comment that documents why we don't want to retroactively reassign schedules? if not, i think we'd want to have a comment to that effect in the code. this feels like the kind of decision that is tough to retroactively recall when refactoring in a year or two.
other than that, LGTM.

lgtm


Fix ABI generator param types for tuple arrays

Locally, this seems to fix the problem described in #455. I also added an isTupleType util to match isTupleArrayType.
Before:
export class BasketManager__getBasketResultBStruct extends ethereum.Tuple {
  get bassets(): Array<ethereum.Tuple> {
    return this[0].toTupleArray<undefined>();

After:
export class BasketManager__getBasketResultBStruct extends ethereum.Tuple {
  get bassets(): Array<BasketManager__getBasketResultBBassetsStruct> {
    return this[0].toTupleArray<BasketManager__getBasketResultBBassetsStruct>(); // This struct was generated, too

Before:
export class BasketManager__getBassetsResult {
  value0: Array<ethereum.Tuple>;

After:
export class BasketManager__getBassetsResult {
  value0: Array<BasketManager__getBassetsResultBAssetsStruct>;

Resolves #455

Superseded by https://github.com/graphprotocol/graph-cli/pull/465.


Remove encryption

Pull Request Test Coverage Report for Build 558

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

Totals

Change from base Build 557:
0.0%

Covered Lines:
2272

Relevant Lines:
2574

💛  - Coveralls


Potential improvement to generated getters for pointer-optionals

Is your feature request related to a problem? Please describe.
I have a proposal that I think would make it easier to take advantage of the useful getter functions this library generates for fields. Consider this simple example, using optional: pointer (or individual pointer: true directives on optional fields):
Schema
type Food {
  name: String!
  # Zero is a valid value if someone really loves celery, so using value optionals isn't appropriate
  calories: Int!
}

type Person {
  name: String!
  # If the Person doesn't have a favourite food, the API returns null for this entire field
  favouriteFood: Food
}

type Query {
  person(name: String): Person
}

Query
query FindPerson($name: String!) {
  person(name: $name) {
    name
    favouriteFood {
      name
    }
  }
}

One of the things genqlient will generate is a getter method for favouriteFood.name:
// GetName returns FindPersonPersonFavouriteFood.Name, and is useful for accessing the field via an interface.
func (v *FindPersonPersonFavouriteFood) GetName() string { return v.Name }

My interpretation of the comment on the getter is that over time, I may find myself with many types having a name field, and might want to start writing functions that can deal with any of them. So, I might want to write something like:
type named interface {
    GetName() string
}

func processName(f named) *string {
    if f == nil { return nil }

    name := f.GetName()

    // Do some processing involving the name

    return &name
}

Of course, I've now shot myself in the foot, because f is a typed nil; the f == nil comparison will return false, and I'll get a nil pointer dereference when I call GetName.
Describe the solution you'd like
I think this could be made smoother if the getters generated for fields of a pointer-optional nested type themselves performed a nil-check and returned pointers (while leaving the actual field in the struct a value, unless it itself was optional). i.e., the generated getter from above would instead be:
// GetName returns FindPersonPersonFavouriteFood.Name, and is useful for accessing the field via an interface.
func (v *FindPersonPersonFavouriteFood) GetName() *string {
    if v == nil { return nil }
    return &v.Name
}

Now, the call to f.GetName() would return a nil pointer instead of panicking, and I could return that from my function directly. I would probably also want to remove the f == nil check as it never really served a purpose anyway:
func processName(f named) *string {
    name := f.GetName()

    // Do some processing involving the name

    return name
}

As far as I can tell, genqlient always generates separate Go types per-query per-type, so I don't believe this would have any negative effects in cases where the nested type is optional in one parent type and non-optional in another.
This would also support the common response when this behaviour of Go is questioned as a design flaw, which is that the implementer of the methods on an interface should be responsible for handling nil pointers. Or, to say it another way, the getter says it can return a string given any pointer to FindPersonPersonFavouriteFood, but currently if that pointer is nil it cannot.
Of course, there's the fairly big caveat that genqclient hasn't said it implements any interfaces; I have 😁 But I believe such a use case was the intent behind the feature?
Describe alternatives you've considered
I appreciate that there are several reasons the maintainers may not want to implement this, for example:

It's 100% a breaking change
The library already supports unmarshalling nulls to a user-provided generic type, which in an ideal world is preferable to the imperfect modelling of missing values using Go nils
Reflection can be used to check if the concrete value is nil rather than == nil
I could nil-check the pointer before I pass it to my function

Nevertheless, because it's perfectly valid in Go to call a method on a (typed) nil pointer, I think my suggestion is overall more type-safe if the getters are pointer receivers rather than value receivers.
Additional context
While Go is not my first language, I would be happy to look into implementing this change if there is any interest in it!

Thanks for writing this up. To make sure I understand, in summary what you are saying is that the following code breaks:
func processName(f named) {
  if f == nil { return } // checks for untyped nil
  f.GetName() // crashes on typed nil
}

p, err := FindPerson(name)
// (check err, p.Person != nil)
processName(p.Person.FavoriteFood)

because p.Person.FavoriteFood is (*FindPersonPersonFavouriteFood)(nil)? I agree that it's reasonable to want that to work.
Unfortunately I'm not sure if changing the return to a pointer automatically is really reasonable; the field isn't optional by the time we get there; and it's a bit weird (and maybe conflicting, in the case where the type is a fragment used in several places?) to have a pointer dependent on the type of the parent field. For example, if you make person required in your query, now name is a pointer in one place and not the other, so you can no longer use a common interface (We'd also have to put it behind an option for compat, which is a bit awkward for something this specific.)
What we might be able to do is: in the generated getter methods, if both the receiver and return are already pointers (receiver probably always is), generate the nil-checks. Then you could at least ask for a pointer there and get what you want. It's a bit of an awkward foot-gun, but it seems like a safe enough change to make (I should hope no one is depending on the fact that that panics) and at least solves part of the problem. Do you want to try a PR to see how that looks?


ValueError: The two structures don't have the same sequence length. Input structure has length 0, while shallow structure has length 9.

Hello, Thanks Furqan for sharing your code. I am facing an issue while training the model with mobilenet_v2

other than that if I trace back, I find that image file's name are not being retrieved. as you can see from the first screen shot. snapshop. Even I cannot find where has tfds.load() downloaded the dataset. I cannot see that. can you please help.

Hi,
Which tensorflow version are you using?

Hi,
Thanks for your reply.
I am using 2.3.0 as 2.0.0 is not available anymore on tensorflow website.
On Thu 6 Aug, 2020, 8:17 PM Furkan Ömerustaoğlu<EMAIL_ADDRESS>wrote:

Hi,
Which tensorflow version are you using?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/FurkanOM/tf-faster-rcnn/issues/6#issuecomment-669784623,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALSUEHPH34Z2UFJA5ZI37FTR7JRKXANCNFSM4PWDFLPQ
.

Hi,
The problem you encounter arises from the structure created when constructing the model.
This structure needs to be updated in versions above 2.0.
But since I am working on another subject now, unfortunately, I cannot update it.
If you want to use this repo, you must either make the necessary updates or use the tensorflow 2.0 version.
Also, no need to be on the website, you can install tensorflow 2.0 with pip or conda.


WIP Sage detection API

Create oauth user for acm before first request
Add code to create oauth user for acm to use before first request.  ACM
needs a oauth client id and secret in order to get the images from
houston.  This adds a static client id and secret which is shared by
houston and acm and it is created before the first request so ACM will
be able to authenticate.

Adjust data sent to wbia detect API

Use urllib.parse.urljoin to create urls
Prepend houston+ to urls that require oauth2 authentication
Change image_uuid_list to a list of asset urls

@mmulich Could you look at the "Create oauth user for acm..." commit and see if that's an acceptable way to share oauth secrets?

@hwindsor I changed the data we're sending to the detection API (and made the changes to wbia in https://github.com/WildMeOrg/wildbook-ia/pull/196).  Does it look ok?

@hwindsor I changed the data we're sending to the detection API (and made the changes to wbia in WildMeOrg/wildbook-ia#196). Does it look ok?

The changes look fine, but please update the section in the IA Pipeline doc that gives an example of the message.
https://docs.google.com/document/d/11TMq1qzaQxva97M3XYwaEYYUawJ5VsrRXnJvTQR_nG0/edit?pli=1#heading=h.eakedinkslxg

@hwindsor I changed the data we're sending to the detection API (and made the changes to wbia in WildMeOrg/wildbook-ia#196). Does it look ok?

The changes look fine, but please update the section in the IA Pipeline doc that gives an example of the message.
https://docs.google.com/document/d/11TMq1qzaQxva97M3XYwaEYYUawJ5VsrRXnJvTQR_nG0/edit?pli=1#heading=h.eakedinkslxg

Updated

/rebase

/rebase


Exporting to pdf

Describe the bug
When exporting to pdf, the pdf does not show the custom stylings.
To Reproduce

Steps to reproduce the behavior:

make a border around any div like normal.
export to pdf
See error, pdf does not reflect css.

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):

Operating System: [e.g. Linux | Android | MacOS | Windows | IOS]
Obsidian version:

Additional context
Add any other context about the problem here.

@mariomui Thanks for this report. I'll invesgate it soon.
Have you any idea about the source of the problem ?
I've never neither faced this problem nor interacted with the PDF export functionnality from a plugin.

Yes. Obsidian doesn't pack in your custom css class if it doesnt see that it's wrapped up in a div or a block quote. I'll look into it/fix it if you want

https://forum.obsidian.md/t/export-to-pdf-does-not-respect-page-level-css/10082/2

After checking the forums, (I like to do this before I work on something) I think the whitenoise promised that this would be fixed in 1.1.15 the version released yesterday. I'll check it and get back to you.

@mariomui I looked a bit on the Obsidian forum too but hadn't found this post, thanks for that !
Let me know, I've the 1.1.15 version and it doesn't seems to fix this issue. I'll be happy to accept your PR if needed :)

the class isn't injected, if it was the border would be red instead of orange.
Basically, i colored all possible elements and exported the pdf.
I'll start work on it but since the solution seems to either be a) it can't be done or b) some async await has to happen with the processing ---> which is more involved.
https://github.com/jamiebrynes7/obsidian-todoist-plugin/issues/98
i'm happy to work on it but I would like to know if the MutationObserver code is where the processing tasks take place (where does the class injection take place)
Current theory is that export is exporting before the plugin code has a chance to render.

@mariomui I had performed a similar test which indeed shows that the custom classes are not inserted.
The details you just gave me made sense to me, and I spent 20 mins trying to ensure that the process() method is awaited, but with no success (I've tried what Licat mentions here).
Indeed, in the MutationObserver the process() method is called which is responsible for the render of the custom classes. I've also tried to remove this MutationObserver with no success too.
To ensure that it is possible I tried with a minimal example that injected a single class to each element of the page and it has been rendered properly in PDF export. So yes it can be done.
So actually I guess that at some point in the process() method an async function is not awaited, but I couldn't find out which one.

@mariomui Any news ? Have you performed some tries on your side ?

could i get the code that you used to ensure that it is possible? It could just be an assumption that the export waits for async. It could just be FAST inserts are okay, but not the high level multi level inserts. I injected som promise sleepers and it doesn't seem to respect waiting for the resolve before processing the print export.

I think I have something with the context promises resolving

could i get the code that you used to ensure that it is possible? It could just be an assumption that the export waits for async. It could just be FAST inserts are okay, but not the high level multi level inserts. I injected som promise sleepers and it doesn't seem to respect waiting for the resolve before processing the print export.

Yeah that could make sense, maybe we could contact Obsidian devs to get precise infos about this ?
To test if applying classes from a plugin is possible in PDF rendering I've simply replaced the customClassReadMode() function of read-mode.ts with something like :
export function customClassReadMode (element: HTMLElement, context: any) {
    element.classList.add("green");
}

and added a CSS snippet with :
.green {
    background-color: green !important;
}

Cool. I did the same thing. I was trying out the promises array in ctx before I had to run errands. In any case , I updated the typescript dependencies as well as the obsidian lib, as well as updated esbuild mjs file, and added a guide on hot loading (so contributors don't have to quit/restart obsidian to see changes), so I have a PR. But let me see what I can do with this undocumented api before I submit tomorrow.

Great, thanks for that !
Have you been able to fix the problem by appending a promise to the promises array of the context ?

I’m still eating lunch with a visiting relative. But that’s where I left off
On Sat, Feb 25, 2023 at 2:51 PM Lila Rest @.***> wrote:

Great, thanks for that !
Have you been able to fix the problem by appending a promise to the
promises array of the context ?
—
Reply to this email directly, view it on GitHub
https://github.com/LilaRest/obsidian-custom-classes/issues/4#issuecomment-1445221674,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHB7EBH3MRR7IZPPFRRRM4LWZKEIHANCNFSM6AAAAAAVE4UMYM
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Full Stack Developer
contact:<PHONE_NUMBER>
resume: zety.com/mycv/mariomui
github: github.com/mariomui
in: linkedin.com/in/mariomui/

Ok let me know if there is anything I can do to help you in this work. Bye !

i think you should leave a comment to the obsidian guys to expose the pdf apis.
I've done it by anchoring to a custom block-language

but i breaks all the other features. While i think it'd be a good thing to have to be able to export to pdf, it seems like its only hacky solutions. i've tested out loadpdjs and i dont think it exposes the pdf api either.   I'm gonna close this bug and attribute it to api limitations.

@mariomui Ok I'll contact them to get more infos about how the PDF exporting works. Thanks for your time :)


Release client

[x] review extant branches and merge to main
[x] check that main not master
[x] write readme
[x] draft release notes
[x] bump version
[ ] add to project site / downloads page
[ ] hand off for testing

@helloCaller There's no sensible package for this repo. So the downloads page on the project site can just link to the repo at https://github.com/jakemoves/cohort-web-client


[Idea/Discussion] "Managed" libp2p node

Version: none, yet
Platform: *
Subsystem: config?

Type: feature

Severity: low/med
Description: "Managed" libp2p node
Basically every time when a project gets created that only uses libp2p and not IPFS the creator has to reinvent a good way to store and read the config, among other things.
In IPFS this is already handled as the config simply gets stored in the repo and additionally gets auto-created, therefore simplifying the process of creating an application on top of IPFS drastically.
For libp2p this process is still manual and involves basically reinventing the wheel of config storage. Sure there are good libraries for this task out there already, but why bother with yet another library if this functionality would be integrated (possibly using one of those libraries). Additionally applications that run in both non-browser and browser environments wouldn't have to worry about creating and testing a config storage mechanism for both.
Example syntax:
const Libp2p = require('libp2p')

const TCP = require('libp2p-tcp')
const SECIO = require('libp2p-secio')
const SPDY = require('libp2p-spdy')
const MPLEX = require('libp2p-mplex')

const modules = {
  transport: [
    new TCP()
  ],
  connection: {
    muxer: [
      SPDY,
      MPLEX
    ],
    crypto: [
      SECIO
    ]
  }
}

const Node = new Libp2p.Managed({
  storage: '$HOME/.my-awesome-app', // this could also be reduced to an 'appID' property based on which the path for the storage folder could be created.
  // appID: 'my-awesome-app', // would set storage on linux to $HOME/.config/libp2p/$appID, win %APPDATA%\Libp2p\%appID%, etc...
  modules: modules, // include the modules. the user-config could allow the user to disable specific modules (e.x. mdns - or some could be off-by-default)
  multiaddrs: ['/ip4/<IP_ADDRESS>/tcp/5343', '/ip4/<IP_ADDRESS>/tcp/5234/ws'], // multiaddrs to listen on (needs to be specified here as the peerId gets created at a later stage, can also be modified via user-config)
  // autoinit/autostart: true // could be added to simplify things even more
})

Node.init({ignoreIfAlreadyExists: true}, err => {
  if (err) throw err
  Node.start(err => {
    if (err) throw err
    Node.peerInfo.multiaddrs.toArray().forEach(a => console.log('Listening on %s', a.toString()))
  })
})

@mkg20001 I believe what you really want is https://github.com/libp2p/libp2p/issues/22

Closing because #22 has further developments on this topic.


Track LLM Model Metadata

Description

This moves the definition of the LLM model into its own Django model, instead of a string defined on the experiment / pipeline / assistant / analysis pipeline.
It allows creating both "global" LLM models (by omitting the team), and "custom" LLM models by associating those with a team.
Currently, this only stores max_token_limit, but it opens the door to adding more metadata alongside these models (e.g. pricing, tool usage, etc.)
I've kept the old data around, and in a followup migration will remove the old columns once this has been deployed stably.
User Impact

Users of "standard" LLM models (e.g. gpt-4o-mini) will now be able to select these from a dropdown, rather than have to know and enter this as a string in all the places that it is required (e.g. creating an experiment).
Demo

https://github.com/user-attachments/assets/64829577-f808-4afb-b00c-14e64763b3f5
Docs

@coderabbitai please do a full review


🌱 provider-kairos +iso target should work with just BASE_IMAGE (no FLAVOR)

If you create an iso with:
earthly -P +iso -BASE_IMAGE=quay.io/kairos/core-ubuntu-22-lts

you get an image that reports this:
debugging-station login: kairos
Password:
Welcome to Ubuntu 22.04.2 LTS (GNU/Linux 5.19.0-35-generic x86_64)

 * Documentation:  https://help.ubuntu.com/
 * Management:     https://landscape.canonical.com/
 * Support:        https://ubuntu.com/advantage

This system has been minimized by removing packages and content that are
not required on a system that users do not log into.

To restore this content, you can run the 'unminimize' command.
Welcome to Kairos!

Refer to https://kairos.io/ for documentation.
kairos@debugging-station:~$ cat /etc/os-release
NAME="kairos-opensuse-leap"

(notice how ubuntu and opensuse is mixed).
This happens because FLAVOR flag was not set. We should infer the FLAVOR from the BASE_IMAGE to simplify how the target should be used and avoid mistakes.

We can also read the os-release file directly, so no need to parse strings from the image name

Can I work on this issue ?

I just realized that while writing my message I went from "sure give it a try" to "I don't think it's worth it" :D. Let's wait for others to chime in.

I think its ok. At least base image could automatically set the FLAVOR and FLAVOR_RELEASE so thats 2 things that we can drop :D


tests badge in README.md makes it look like tests are failing, but they're not

Describe the issue
The tests badge in README.md makes it look like tests are failing, but they're not, as least as of Thursday, February 29, 2024.
Expected behavior
The tests badge in README.md should match the status checks on the most recent commit.
Steps to reproduce
View the README at https://github.com/facebook/stylex.
Test case
No response
Additional comments
No response


rightPriceScale visible:false breaks the procentage mode

Hi,
I like to show two lines as procentage mode and hide the rightPriceScale.
But when I set visible to false the procentage stops working.
Lightweight Charts™ Version:
v4.0.1
Steps/code to reproduce:
Set rightPriceScale visible to false.
The mode:2 and 3 stop working.
The lines are not starting at same value in chart.
https://jsfiddle.net/8xLqz6po/15/

Actual behavior:
For mode:2  (Procentage) I expect two lines to start at same value.
This works when visible: true but stop not when visible: false
CodeSandbox/JSFiddle/etc link:
https://jsfiddle.net/8xLqz6po/15/

If you would like to have a chart without a price scale then you can make use of 'overlay' price scales.
Essentially you set the priceScaleId on the series to a string which is not either left or right. You can set global settings for the overlay price scales with the overlayPriceScales chart option
Overlay price scales are used in this example: https://tradingview.github.io/lightweight-charts/tutorials/how_to/price-and-volume
Updated example: https://jsfiddle.net/msilverwood/cLg3sr7w/


test: jax network components

What?
Unit tests for jax networks components
Why?
Components currently not tested. Needs to be robust for jax Mava release
How?

Test DefaultNetworks component

Extras
Closes #526

Thank you @mmorris44! Looks good, just a few small questions from my side.


Kubernetes Autoscaler

Hi ,
I am new to k8s and have a huge confusion on creating HPA for the below query
we have a prometheus query : (sum(jvm_memory_bytes_used{area="heap"}) ) / (sum(jvm_memory_bytes_max{area="heap"}) )
Problem: Need to get that metrics added to prometheus adapter , so custom metrics can check those and we can implement HPA.
and we are getting those metrics from istio-system prometheus (i dnt know if this information helps)
Kops version : 1.13.1
AWS :provider

Hi, follow this tutorial:
https://github.com/arielb135/HPA-with-prometheus-and-RabbitMQ/blob/master/README.md

@arielb135 thank you so much i will try that and will let u know

@arielb135 just a small confusion where do we need to mention ruleSelector in prometheus helm, is it in value.yaml file?

@Sanjanare I guess you were able to solve you issue?
@DirectXMan12 I guess we can close out this issue.

@arielb135 just a small confusion where do we need to mention ruleSelector in prometheus helm, is it in value.yaml file?

Sorry i missed the question,
the rule selector is indeed in values.yaml file, the exact line is here:
https://github.com/helm/charts/blob/master/stable/prometheus-operator/values.yaml#L853
In order for prometheus operator to actually find your PrometheusRules - the labels must match, meaning - all labels that you give there must be also in your prometheus rule

@s-urbaniak still trying to make it work , will close in a day thank you


[AutoPR mysql/resource-manager] chore: jsonfmt mysql

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/7431

This PR has been merged into https://github.com/Azure/azure-sdk-for-go/pull/5978


Deprecated Numba function "generated_jit"

When importing the module, the following error arises.
Code :

# The algebra of the space
import clifford as cf
layout,blades=cf.Cl(3)

Error:
AttributeError                            Traceback (most recent call last)
AttributeError                            Traceback (most recent call last)
Cell In[15], line 2
1 # The algebra of the space%%capture
----> 2 import clifford as cf
3 layout,blades=cf.Cl(3)
File ~\AppData\Roaming\Python\Python310\site-packages\clifford_init_.py:95
92 from clifford.io import write_ga_file, read_ga_file  # noqa: F401
94 from ._version import version  # noqa: F401
---> 95 from . import _numba_utils
97 from ._settings import pretty, ugly, eps, print_precision  # noqa: F401
98 import clifford.taylor_expansions as taylor_expansions
File ~\AppData\Roaming\Python\Python310\site-packages\clifford_numba_utils.py:85
83 if not DISABLE_JIT:
84     njit = numba.njit
---> 85     generated_jit = numba.generated_jit
86 else:
87     def njit(f=None, **kwargs):
AttributeError: module 'numba' has no attribute 'generated_jit'
It seems the function is deprecated for certain  numba versions (See: https://stackoverflow.com/questions/78252285/attributeerror-module-numba-has-no-attribute-generated-jit)

Realised it was already listed : see this bug


Details grid edit

Ok, as said, it was easy. Now I have 2 questions, don't want to investigate all files until I get it right spending hours (for me learning the internals, and then you testing it).

How to force the panel to use new settings? After editing "metagrid" variable, the panel gets updated some seconds later, so I used a callback.

// I have used the new track callback
// But have to test it when no tracks are being played or nowPlaying returns gargabe
// Is there any other routine?
on_playback_new_track(fb.GetNowPlaying());

To save the values to the file? I see at gr-menu line 2489. Is that the right routine to save them?

themeConfigMenu.addItem('Save settings to config file', false, () => {
...
setThemeSettings(true) // And that's it?
});

Once I get the basics, we can go fancy with a popup showing the current rows and asking which row to edit, etc.

It's in gr-callbacks.js -> metadata grid will be rebuild from function on_metadb_changed(handle_list, fromhook) {
 	str.grid = [];
 	for (let k = 0; k < metadataGrid.length; k++) {
 		let val = $(metadataGrid[k].val);
 		if (val && metadataGrid[k].label) {
 			if (metadataGrid[k].age) {
 				val = $('$date(' + val + ')'); // Never show time
 				const age = calcAgeDateString(val);
 				if (age) {
 					val += ` (${age})`;
 				}
 			}
 			str.grid.push({
 				age: metadataGrid[k].age,
 				label: metadataGrid[k].label,
 				val
 			});
 		}
 	}

And there is also a function clearUIVariables() {  which clears all, used for example on_playback_stop or in initMain()

No but you were right on track, the setThemeSettings() function is to save ( with parameter true ) or load ( with no parameter ) all current using SMP panel properties to the config file BUT NOT ALL are linked to the config file.
If you open the config file ( georgia-reborn-config.jsonc ) each section has a NOTE: in the comment header that starts with:
// * Note: These settings will
Almost all settings are saved but some not:
"title_format_strings": {
"themeStyleCustom": {
"themeCustomFont": {
"metadataGrid": [
"settings": {
These are not saved and only for manual edits, that means user need to manually open the config file and modify them themselves. All others settings will be saved automatically to the config file via top menu Options > Settings > Theme configuration > Save settings to config file -> setThemeSettings(true)

The configuration file is defined via gr-configuration.js with settings from
gr-defaults.js ( const defaultMetadataGrid = [ )
and gr-settings.js ( Line 1180 ).
Hope that helps and thanks for your help!
-Tom

Uhm... 1) solved. I refactored code.

So on on_metadb_changed is reused with lp value.

And the same on the menu, not needing to process all again.

The second took me some time, not sure why Mordred did not add an update function for arrays...
 Was just for you to test it.

details_grid_04_11_2022.zip
So there it is. Unless I missed something, you have to try to break it on purpose, but the same can be done with the config file so...

Thanks, tested and it's working!

@regorxxx,
uploaded WIP Beta 10c for us, contains all your additions.

You should just replace all your javascript files because there were more changes I needed to do when refactored
the top menu code...
Also check latest changelog in the zip file for more information.
Here is the zip.
-Tom

Why don't you use foo_openlyrics Lyrics? (just curiosity)
https://github.com/jacquesh/foo_openlyrics

See this here:
https://github.com/jacquesh/foo_openlyrics/issues/177

@regorxxx,
just released Beta 10c, wanted to let you know we will postpone this for Beta 10d and write it then in the changelog
and make it official.

Hi @regorxxx,
I am now focused on the input popup, added it to some options in the menu.
This is here is the latest version, will be Beta 10e.
I have made a custom popup function const inputBox = (option) => { in gr-menu.js.
Your metadata grid code is now also there.
Now how do we make via utils.InputBox multi input values in one popup window?
Like WilB's htmldialog ( Library > ... > Views > Configure Views ).
I have looked up the SMP docs and there are no examples...
For example, I have made 2 popups when activating the top menu Options > Playlist > Track row > Customize track row.

First popup when playlist header is being displayed ( default )
Second popup when playlist header is deactivated ( Options > Playlist > Album header > Album header )

Don't tell me that we need to make a new popup framework just for that ;-)
-Tom

Will be available in Beta 11, I've implemented a custom menu for the metadata grid and one other surprise.


Removal of Capabilities Annotations parsing logic from the OdcmModel

OdcmModel is designed to be protocol agnostic. Earlier OData concepts like Capabilities annotations parsing were wrongly introduced into the OdcmModel in the spirit of code simplification. But it violated a core principle of the OdcmModel that it should be protocol agnostic. The fix is to abstract away OData Capabilities annotations parsing into the ODataReader.
Fix #60

LGTM


Update SplunkRum#addRumException() according to RUM BE requirements

I've noticed that Android RUM differs in 2 things from what RUM backend expects:

missing component=error attribute;
span name is different than exception.type attribute; in fact, it may be completely custom one.

I've added 2 new methods that do not allow setting custom exception span name and deprecated the old one - @jkwatson please take a look at this, whether this makes sense or not.

Was this a request from the BE team? IIRC, there was some reluctance to make things generally show up as error spans, but I don't remember the details.

Should we also update the usage(s) in the sample app to not use the deprecated method?

Should we also update the usage(s) in the sample app to not use the deprecated method?

Oh, definitely, I missed that one usage.


Fix broken links + add mdbook-linkcheck to make install, closes #558

This should fix all broken links and make CI pass again on other PR's
Basics

[ ] I added a line to /doc/CHANGELOG.md
[ ] The PR is rebased with current master.
[ ] Details of what you changed are in commit messages.
[ ] References to issues, e.g. close #X, are in the commit messages.
[ ] The buildserver is happy.

Checklist

[ ] I have installed and I am using pre-commit hooks
[ ] I fully described what my PR does in the documentation
(not in the PR description)
[ ] I fixed all affected documentation
[ ] I fixed all affected decisions
[ ] I added unit tests for my code
[ ] I added code comments, logging, and assertions as appropriate
[ ] I translated all strings visible to the user
[ ] I mentioned every code or binary not directly written or done by me in reuse syntax
[ ] I created left-over issues for things that are still to be done
[ ] Code is conforming to our Architecture
[ ] Code is conforming to our Guidelines
(exceptions are documented)
[ ] Code is consistent to our Design Decisions

Review

[ ] I've tested the code
[ ] I've read through the whole code
[ ] Examples are well chosen and understandable

I think it is better if we use the git.permaplant.net links once we get them.
#615 is the next step to not add new problems.


[TW#14796] spi_master: spi_bus_add_device() does not allow GPIO_NUM_0 to be used as select pin

in spi_bus_add_device() function the dev_config->spics_io_num is checked for valid GPIO numbers including 0, but the code only accepts dev_config->spics_io_num > 0. If spics_io_num is 0, nothing is done. This should be possible.

thanks for reporting this issue, we will fix this.


feat(register): support hook options

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


[Bug] Infinite error loop

What happened?
Infinite error loops can happens and should be avoided.
Solution
Put a limit on the number of times an error can happen without crashing the bot.
Reproduction
No response
Relevant log output
No response
Code of Conduct

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

Closing the issue as it can't achieve to reproduce any error loop.


Engine API: inform CL with details on validation error

Resolves https://github.com/ethereum/execution-apis/issues/120

@mkalinin I moved the object definition up into the Structures section, could you let me know if this still looks okay? I was also a bit unsure about what error codes might be returned.

Does ValidatorError need a version? -- e.g. ValidationErrorV1

I have removed ValidationError and instead referenced ErrorObject as it is documented in JSON-RPC spec. Thoughts?

I have removed ValidationError and instead referenced ErrorObject as it is documented in JSON-RPC spec. Thoughts?

The object is replaced with String|null


Test and migrate Instana example to 1.9.

Working on this.

@hitekhippy Awesome, thank you!

PR submitted;

Merged https://github.com/dcos/examples/pull/164 for this thanks @hitekhippy!


markusschaberApi

Merci
**[Enter feedback here]

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

ID: 4c461e1d-5771-20f9-c9b3-ac4ee7661ee0
Version Independent ID: e06d8e48-cee4-0c0c-39aa-97abe228c370
Content: ASP.NET Core tutorials
Content Source: aspnetcore/tutorials/index.md
Product: asp.net-core
GitHub Login: @Rick-Anderson
Microsoft Alias: riande**

HiFrom where I can download toufiqElahySPA.js?Thanks
  От: Martin Theriault<EMAIL_ADDRESS>
До: aspnet/Docs<EMAIL_ADDRESS>Копие: Subscribed<EMAIL_ADDRESS>Изпратен: петък, 8 юни 2018 г. 17:04
Тема: [aspnet/Docs] markusschaberApi (#6947)
Merci
**[Enter feedback here]
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 4c461e1d-5771-20f9-c9b3-ac4ee7661ee0
Version Independent ID: e06d8e48-cee4-0c0c-39aa-97abe228c370
Content: ASP.NET Core tutorials
Content Source: aspnetcore/tutorials/index.md
Product: asp.net-core
GitHub Login: @Rick-Anderson
Microsoft Alias: riande**
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@EmilNachev  What file you looking for? I'm not familiar with toufiqElahySPA.js, where did you see that referenced?


Fix several bugs with the installer build processes

Improve handling of version specific distro lists, previous code was inconsistent and causing issues during uploads.
For Riscv upload function, ensure required parameters are passed to the new node.

Holding on merge, as I think this may need a similar fix for the debian uploads  command becoming too long.


Linkage to specific values in requirements.yml?

Hi,
What are the destinations within the requirements.yml file?

src: anthcourtney.cis-amazon-linux
src: dharrisio.aws-cloudwatch-logs-agent

should these be replace?

these are also present in the playbook.yaml
Roles

common
- anthcourtney.cis-amazon-linux

# - dharrisio.aws-cloudwatch-logs-agent

Hi @dgulli - Thanks for opening the issue.
These are Ansible Roles that will be pulled from Galaxy, and will execute their own playbooks - You can read more in the blog post itself: https://aws.amazon.com/blogs/devops/how-to-create-an-ami-builder-with-aws-codebuild-and-hashicorp-packer-part-2/

anthcourtney.cis-amazon-linux

This applies CIS benchmark to Amazon Linux to harden security

dharrisio.aws-cloudwatch-logs-agent

Disabled by default, installs and ships OS logs to CloudWatch Logs

If you wanted to create your own pipeline, you could fork it, and add Ansible Roles that you'd like to use to bootstrap your AMI.
Let me know if you need more details :)

hey @heitorlessa
Great, thank you for the explanation!


Add feature and metric configuration flyouts to model overview

Description
Until now, features and metrics were only selectable via a dropdown (well, technically a ComboBox) in the new model overview experience. Since users may want to know more information about the metrics they're choosing, and about the features they're selecting for the disaggregated analysis (including which groups are part of the analysis), the new configuration flyouts added in this PR bridge this gap. Additionally, so far continuous features were split into 3 evenly sized (by interval length) bins rather than allowing users to adjust it. This PR allows configuring the number of bins for continuous features with a default of 3 bins, a minimum of 2, and a maximum of 10. Less than 2 doesn't make sense since there's no split at that point, and more than 10 would get out of hand for the resulting table and chart.
Metric Configuration Flyout:
https://user-images.githubusercontent.com/10245648/166174435-a86dd1d6-368f-42d6-bb20-cc835dacc697.mp4
Feature Configuration Flyout:
https://user-images.githubusercontent.com/10245648/166174404-16d7bbd5-5e39-4533-adf4-05e53450f13f.mp4
Other changes:

Reorganized the model overview section of en.json a bit to make it more intuitive.
Refactored logic in DisaggregatedAnalysisUtils.ts to be reusable for other purposes. The result of this is the new function generateFeatureBasedFilters.

Caveats:

I'm not quite happy with the complexity of the flyout components. This is largely due to the uncommon way Selection works within DetailsList. There's no reasonable way to just update the selection rather than resetting it every time. We do this in other places in our codebase, too, and at least here we know that there are relatively reasonable bounds on the size of the tables.
The new model overview has become large enough to become its own component IMO. I'll do that in a separate PR unless people have objections (?) @microsoft/responsible-ai-widgets

Checklist
Note that the feature flag is still on and none of this is visible to users at this point. Before it becomes visible we have to add tests!

[x] I have added screenshots above for all UI changes.
[ ] Documentation was updated if it was needed.
[ ] New tests were added or changes were manually verified.

Codecov Report

Merging #1381 (0a80469) into main (56906fb) will decrease coverage by 10.32%.
The diff coverage is n/a.

:exclamation: Current head 0a80469 differs from pull request most recent head 85458ae. Consider uploading reports for the commit 85458ae to get more accurate results

@@             Coverage Diff             @@
##             main    #1381       +/-   ##
===========================================
- Coverage   85.91%   75.58%   -10.33%
===========================================
  Files         100       10       -90
  Lines        4784      258     -4526
===========================================
- Hits         4110      195     -3915
+ Misses        674       63      -611

Flag
Coverage Δ

unittests
75.58% <ø> (-10.33%)
:arrow_down:

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

Impacted Files
Coverage Δ

erroranalysis/erroranalysis/analyzer/__init__.py

raiutils/raiutils/version.py

raiwidgets/raiwidgets/constants.py

...onsibleai/responsibleai/managers/causal_manager.py

...idgets/raiwidgets/responsibleai_dashboard_input.py

raiutils/raiutils/webservice/webservice.py

erroranalysis/erroranalysis/_internal/metrics.py

...ai/responsibleai/rai_insights/rai_base_insights.py

raiutils/raiutils/dataset/__init__.py

...ibleai/_tools/causal/dashboard_schemas/__init__.py

... and 80 more

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 56906fb...85458ae. Read the comment docs.


Add ECDSA support (named curve only, requires OpenSSL 1.1.0)

This commit adds ECDSA support.  Currently, only named curve is
supported.  OpenSSL 1.1.0, which is not released yet, added necessary
functions to support EC_KEY with custom engine, and prior versions
have no workaround over these missing functions, we have to depend on
OpenSSL 1.1.0.  More specifically, we require OpenSSL 1.1.0 pre2.

I've added new commit to compile with OpenSSL 1.1.0pre5.  It contains massive changes, and it broke RSA code in neverbleed.   1.1.0 makes many OpenSSL object struct opaque, and all codes to access field directly break.  This commit fixes this issue.

Since OpenSSL 1.1.0 is around the corner (the OpenSSL dev said that they will release it in August 25, 2016), it is a good time for us to seriously consider to review this PR.

Merged master branch, resolved conflict.

Now we only consider openssl 1.1.0 final version.  I also fixed compiler warnings.

Thank you for the updates. I like how the RSA-related APIs are backported? for 1.0.2.
LGTM aside from my comments i-line (including the issues I found when trying to compile the file using OpenSSL 1.0.2).

Thank you for the changes.
The code looks great, however I left a comment since we might be possible to make it even better.

Thank you for the update! Merged to master.


feat: add migrate UpTo(step)

According to the migrate down I added a UpTo function that takes a step argument and only applies (upto) step migrations. This feature is also added to the soda cli.

This would be really useful for us, because we run tests against our migrations!

It might actually be use full to not only return an error but also how many steps it actually migrated up, should I add that @stanislas-m?

Sure @zepatrik. Sorry for the delay. :)

Thanks!


youtube-dl: wrap with atomicparsley

Otherwise --embed-thumbnail will crash youtube-dl while running.

[x] doesn’t crash anymore

Travis failure look relevant

Apparently some person thought it was funny to pass null into the module. I changed the module to boolean flags.

[x] Tested youtube-dl and youtube-dl-light by looking at the wrappers and trying a download


react_refresh: Rewrite main loop

This turned into an all-in-one commit:

Move the logic to the visit_mut_* functions from VisitMut.
Make atom key names more flexible to support e.g. #26

The largest change is the fact that we perform most of the work directly
in the visitor functions.  For applicable calls to atom (and friends)
we replace the CallExpr right then and there.  This makes it so that
we don't need to deal with export handling, or accidentally replace
entire expressions with erroneous cached atoms (See e.g. the failing
test in #36).  This also solves other open issues, like #26 , #34 , and #35 .
Fixes #26
Fixes #34
Fixes #35

I built this on top of #37, but I suppose technically speaking that's not necessary. This is a pretty large change, so if you think this is a direction to pursue it might make sense to rethink that change in the context of this anyways.
There's still some cleanup I can do, and probably a bunch of edge cases I've missed. I intend to look at these next.

This is cool @martinhath.
I have merged the previous PR. Could you rebase this PR and cleanup the comments, etc.?
I'll take a look then. Thanks.


the resource manager on the left be made into four spaces

Can the directory structure in the resource manager on the left be made into four spaces, otherwise the directory hierarchy is too unclear.

Please try setting a bigger value for workbench.tree.indent
Also, next time you want to report an issue please use Report Issue from the Help menu. That will automatically include version and platform information, which is often relevant.


⚠ Bofrost.at has degraded performance

In 55aad24, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1073 ms

Resolved: Bofrost.at performance has improved in 37566e4.


Overview settings dialog, values are changed incorrectly

some values in settings dialog are changed incorrectly, for example:
After changing "Max concurrent virtual machine migrations" value to 100, the overview shows 50.
This issue is true for the next fields:

Snapshot pooling interval (seconds)
Max concurrent virtual machine migrations

settings_dialog.webm

cc:// @nsimsolo

merged upstream #599
@nsimsolo hi, please move to close after verification


[WIP] Test are coming

Add phpunit tests.

This change is

Can be review, more tests will come after.


What does diagonal red lines/dots mean in interactive plot?

Hi Maria,
I have a hard time to interpret these red lines on interactive plot of Assemblytics.
Could you please tell me what does red dots/lines mean?
Best Regards,
Mehmet

Black is forward alignment, red is reverse.
On Thu, Jul 30, 2020 at 7:07 AM MehmetGoktay<EMAIL_ADDRESS>wrote:

Hi Maria,
I have a hard time to interpret these red lines on interactive plot of
Assemblytics.
Could you please tell me what does red dots/lines mean?
Best Regards,
Mehmet
[image: ss]
https://user-images.githubusercontent.com/8544565/88932694-b73a8780-d27e-11ea-95bd-8f3bc4a6a034.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/MariaNattestad/Assemblytics/issues/36, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB4W4PNBNUEDOT3OQTA7S2TR6F5DTANCNFSM4PN2UFYQ
.

Black is unique alignments, red is repetitive. It means the red alignments are the ones filtered out during the unique anchor filtering step in Assemblytics and is not used to call variants. See the paper for more details on unique anchor filtering.


parallel: 20231222 -> 20240122

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/parallel/versions.
meta.description for parallel is: Shell tool for executing jobs in parallel
meta.homepage for parallel is: https://www.gnu.org/software/parallel/
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 20240122 with grep in /nix/store/mji8vc5bflkb44za2cs3hi4yavbmab9s-parallel-20240122
found 20240122 in filename of file in /nix/store/mji8vc5bflkb44za2cs3hi4yavbmab9s-parallel-20240122

Rebuild report (if merged into master) (click to expand)

20 total rebuild path(s)

20 package rebuild(s)

First fifty rebuilds by attrpath
adapta-gtk-theme
bash-preexec
bats
image_optim
jpeg-archive
kicad
kicad-testing
kicad-unstable
kicadAddons.kikit
kicadAddons.kikit-library
kikit
last
locate-dominating-file
packcc
parallel
parallel-full
plata-theme
profile-cleaner
sonic-pi
tebreak

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/mji8vc5bflkb44za2cs3hi4yavbmab9s-parallel-20240122 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A parallel https://github.com/r-ryantm/nixpkgs/archive/94c2089d5f3db19389f0b0f13c65c875bae90c88.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/94c2089d5f3db19389f0b0f13c65c875bae90c88#parallel

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/mji8vc5bflkb44za2cs3hi4yavbmab9s-parallel-20240122
ls -la /nix/store/mji8vc5bflkb44za2cs3hi4yavbmab9s-parallel-20240122/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package failed to build:

kicad-unstable

19 packages built:

adapta-gtk-theme
bash-preexec
bats
image_optim
jpeg-archive
kicad
kicad-testing
kicadAddons.kikit
kicadAddons.kikit-library
kikit
last
locate-dominating-file
packcc
parallel
parallel-full
plata-theme
profile-cleaner
sonic-pi
tebreak

Maintainer pings
cc @pSub @vrthra @tomberek for testing.

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

2 packages failed to build:

kicad
kicad-unstable

22 packages built:

adapta-gtk-theme
bash-preexec
bats
image_optim
jpeg-archive
kicad-testing
kicadAddons.kikit
kicadAddons.kikit-library
kikit
kikit.dist
last
locate-dominating-file
packcc
parallel
parallel-full
parallel.doc
parallel.man
plata-theme
profile-cleaner
sonic-pi
tebreak
tebreak.dist


Update the transfer command of the Audio module

Description
Since according to #50, the ownerAddress is replaced with creatorAddress and owners list, the ownerAddress is no longer used for transferring the audio NFT. Instead, each owner may individually transfer some or all of their share to another account.

The share may be transferred in integer number from 1 to the current share of the owner. For example, if owner1 share is equal to 25, this account is able to transfer 1 - 25 shares to another account.
CreatorAccount may not apply changes to the owners list after creation of the NFT.
Each owner is able to only and only transfer their own share.

Resolved by #66.


Add version: LuaLS.lua-language-server version 2.6.1

Pull request has been created with Komac v1.9.1 :rocket:
Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/116141&drop=dogfoodAlpha

@wingetbot waivers Add Validation-Executable-Error


How to run

how to run this program? please guide

Better Use : https://github.com/Pymmdrza/BTCHDwallet


Multiple Lights - Raspberry and GPIO

Hello @KhaosT and everyone!
First of all, congrats on the job for making HAP-NodeJS. It's marvelous! Your contribution to Home Automation is certainly accounted for every person that searched for "homekit and raspberry" on Google.
So, I've been sniffing around for a few weeks, and I'm new to JavaScript programming. I'm having some issues, so I can't quite make the setup work at home.
Here's the scenario:
I have one relay board with two relays plugged in the Raspberry's GPIO.  I cannot duplicate the light. One light works fine but I've tried cloning the accessory and changing the username and pincode, but it doesn't work.
So, I used @legotheboss implementation of python codes to access the GPIO. As you can see in the code below, the state "on" points to a python code, and "off" state points to another
Running the scripts manually, Both of them work, but on the "Home" app on my iPhone, I can't detect the second light.
I am using the following code:
Light_accessoryImproved.js
Am I doing something foolish? Can you please help me?
My intention is to make possible turn on 4 Lights via the HomeKit..
Thanks in advance!!
Erik

Anyone? Help?

If you're new to JavaScript I would recommend using Homebridge (https://github.com/nfarina/homebridge) which is a framework for plugins based on hap-nodejs.
The authors of both collaborate on both projekts.
There are several plugins for GPIO switching available, plus hundreds for other hardware and software.
But to your question: Did you actually add the accessory to Homekit? Or are you using bridgedcore.js ?

Hello @snowdd1 , I am currently using the Core.js file.
As a matter of fact, I think the Homebridge recognized somewhat the accessory. But failed to trigger it.
Following a solution provided by @KhaosT in one of the issues, I have changed the pin code and username, but I have no idea if I need to do something else to make it work.

@akiyamaerik - I think you may have the accessory files named incorrectly.
They should be:
Light1_accessory.js
Light2_accessory.js
you can basically name it anything you want but it must end with _accessory.js
I followed @legotheboss youtube relay light tutorial as well and created my own python scripts to work with each light to turn them on and off using a raspberry pi zero and they work fine.
Let me know how you get on.

Oh, I see @jat80.
Ok, I will try to do this as soon as I get back home.
Thanks for the advice!!

@akiyamaerik no problem.  If you need any further assistance let me know.  I'll try and help as best I can.  :)


Camera Light not turn off after CameraPreview.stop() called

Hi @arielhernandezmusa ,
thanks to your capacitor plugin, i can put image overlay when taking picture in PWA, but there's something strange about the camera behaviour.
When i called the CameraPreview.stop(), it did stop the camera but the green light is still on(i'm using mac). Is this a right behaviour ? i'm comparing  itwith Camera PWA and it did stopped the light after i hit a close button.
i'm using Ionic React and the div is inside IonModal. stopCamera function will be called as hook function to App.tsx.
PhotoPreview.tsx
`const stopCamera = async ()=> {
console.log("stop triggered");
const result = await CameraPreview.stop();
console.log(result);
}`
app.tsx
`const showCameraModalDismissHandler = () => {
(stopCamera() as any).then(
setShowCameraModal(false)
)
}`
<IonModal onDidPresent={() => showCameraModalPresentHandler()} onWillDismiss={() => showCameraModalDismissHandler()}  isOpen={showCameraModal}>

       </IonModal>
Appreciate any feedback!

nevermind, i found a workaround, i need to put timeout after capture and stop the camera

Hi @garryalfa ,
Can you share your code ? I have the same problem.
Here's mine :
ngOnInit() {
    CameraPreview.start({ parent: "cameraPreview" });
  }

  async stopCamera() {
    setTimeout(() => CameraPreview.stop(), 1000);
  }

Thanks !

hi @arochet ,
i'm still having the issue :( , it seems the issue happened intermittently, depends on which function run first (either timeout or the stop). i will open this issue again

Hi,
Finally i decide to make my own camera preview. I keep the "tracks" of the stream global and i stop() them. Hope this help the developper to to fix the issue. The camera light turn off.
Html code :
<ion-content>

    <ion-fab vertical="bottom" horizontal="center" slot="fixed">
      <ion-fab-button (click)="capturePhoto()">
        <ion-icon name="camera"></ion-icon>
      </ion-fab-button>
    </ion-fab>

  <canvas id="result"></canvas>

</ion-content>

  <ion-footer>
    <ion-toolbar>
      <ion-buttons slot="secondary">
        <ion-button fill="clear" (click)="start()">
          Reprendre
        </ion-button>
      </ion-buttons>
      <ion-buttons slot="primary">
        <ion-button fill="clear" (click)="dismiss()">
          OK
        </ion-button>
      </ion-buttons>
    </ion-toolbar>
  </ion-footer>

and TypeScript Code
theTracks = [];//List of tracks of stream
  width: number;//Width of the video
  height: number;//Height of the video
  takingPhoto: boolean = true;//Camera is on/off
  video: HTMLVideoElement;//Display the result of camera
  canvas: HTMLCanvasElement;//Display the image the user capture

  constructor(private modalCtrl: ModalController) {
  }

  ngOnInit() {
    this.width = window.screen.width;
    this.height = window.screen.height - 100;

    //Append <video>
    this.video = document.createElement("video");
    this.video.id = "video";
    this.video.setAttribute("style", "-webkit-transform: scaleX(-1); transform: scaleX(-1);");
    const parent = <HTMLElement>document.getElementById("cameraPreview");
    parent.appendChild(this.video);
    this.canvas = <HTMLCanvasElement>document.getElementById("result");

    //Start Camera
    this.start();
  }

  capturePhoto() {
    this.capture().then(() => {
      this.stop();
    });
  }

  displayVideo(dispVideo: boolean) {
    this.takingPhoto = dispVideo;//We are taking video
    this.canvas.hidden = dispVideo;//Canvas of img is hide
    this.video.hidden = !dispVideo;//Video start
  }

  //Plug-in
  async start(): Promise<{}> {
    return new Promise((resolve, reject) => {
      //Display element
      this.takingPhoto = true;
      this.video.hidden = false;
      this.canvas.hidden = true;

      //Start recording
      if (navigator.mediaDevices && navigator.mediaDevices.getUserMedia) {
        navigator.mediaDevices.getUserMedia({ video: { width: this.width, height: this.height } }).then(
          (stream) => {
            this.video.srcObject = stream;
            this.video.play();

            const tracks = stream.getTracks();
            tracks.forEach(track => {
              this.theTracks.push(track);
            });

            resolve();
          },
          err => {
            reject(err);
          }
        );
      }
    });
  }

  stop() {
    //Stop element
    this.takingPhoto = false;
    this.video.hidden = true;
    this.canvas.hidden = false;

    //Stop recording
    this.theTracks.forEach((track) => { track.stop(); });
  }

  async capture(): Promise<any> {
    return new Promise((resolve, _) => {
      const context = this.canvas.getContext("2d");
      this.canvas.width = this.video.videoWidth;
      this.canvas.height = this.video.videoHeight;
      context.drawImage(this.video, 0, 0, this.video.videoWidth, this.video.videoHeight);
      resolve({
        value: this.canvas
          .toDataURL("image/png")
          .replace("data:image/png;base64,", "")
      });
    });
  }

  dismiss() {
    this.modalCtrl.dismiss({
      'dismissed': true
    });
  }

Customize as you want.
I will improve it.
Thank you

i see @arochet,   so you make it as global variable and make stop function become sync, will try it.
thanks for the insight and code! hope @arielhernandezmusa can give comment for it.
thanks

Fixed on https://github.com/arielhernandezmusa/capacitor-camera-preview/commit/3fb8f65ee90472707f87f9c4d7540a01ef5f2135
close #18


iOS issue

Something seems to be wrong with Cordova and Pushwoosh again.
2015-02-13 14:43:06.862 SBCERAApp[433:312254] You've implemented -[<UIApplicationDelegate>
application:didReceiveRemoteNotification:fetchCompletionHandler:], but you still need to add
"remote-    notification" to the list of your supported UIBackgroundModes in your Info.plist.

Here is where it seems to be failing:
onDeviceReady: function() {

app.receivedEvent('deviceready');

initPushwoosh();

},

If I put an alert before app.receivedEvent it fires, if I put it after it does not fire.
Sorry if I'm not presenting the correct info. I realize it seems like deviceready is not firing but I use device ready successfully elsewhere.
Thanks

This warning is harmless. It means your app cannot receive silent pushes. That's fine and regular pushes are not affected.
However it is up to you to make your Javascript code to be correct. We have a sample project for a jump start:
https://github.com/Pushwoosh/phonegap-3-sample-app

I appreciate you pointing me to a sample app but how about adding the link
to where the directions on the website are located. There is a significant
difference with what the website provides and this sample app code.
On Wed, Feb 25, 2015 at 6:04 PM, shaders<EMAIL_ADDRESS>wrote:

This warning is harmless. It means your app cannot receive silent pushes.
That's fine and regular pushes are not affected.
However it is up to you to make your Javascript code to be correct. We
have a sample project for a jump start:
https://github.com/Pushwoosh/phonegap-3-sample-app
—
Reply to this email directly or view it on GitHub
https://github.com/Pushwoosh/pushwoosh-phonegap-3.0-plugin/issues/81#issuecomment-76109094
.

What would be the difference?

The code from the website was not working. I'm not sure why specifically.
The code from this sample seems to be working at least for registration
though I don't seem to be receiving pushes. It could be that my coding is
not good enough to quickly find the problems. Here is what I perceive to be
a challenge for companies like yours though. Applications like Phonegap
have made creating mobile applications somewhat easy for non-coding folks
like me. Unfortunately when things break we come to tech gurus like you to
find a fix. Having consistent, easy to understand code across website
guides, GitHub, etc is important. This is just my opinion though. Pushwoosh
has always been super helpful in solving problems.
On Thu, Mar 12, 2015 at 3:31 AM, shaders<EMAIL_ADDRESS>wrote:

What would be the difference?
—
Reply to this email directly or view it on GitHub
https://github.com/Pushwoosh/pushwoosh-phonegap-3.0-plugin/issues/81#issuecomment-78455977
.

Thank you. Please note this is not support forum. You can contact Pushwoosh support team by using contact form on Pushwoosh website. This place is for SDK discussion, methods, functions, code, etc.