Faster vm creation: Can we start a vm without desktop?

Hi the team,
thanks a lot for your great work. We now can support tests in our project. The problem we're facing is that the vm creation + tests take so much time, and as @mondeja has pointed out  the vm create takes 17 minutes [1]
Is that an option we have a vm without desktop support? Just a base installation where we can start to install stuff we need? I suspect that's be faster.
Thanks for your reading.
[1] https://github.com/icy/pacapt/pull/194#issuecomment-877384452
[2] https://github.com/icy/pacapt/pull/194#issuecomment-877421468

Yes, I also noticed that the vm is slow to start.
Most of the time is costed in booting the VM.
I will check if we can speed up the booting time later.
Thanks.

Solaris 11 vm = 3.3 GB
https://www.oracle.com/solaris/solaris11/downloads/solaris-downloads.html
I wonder if it's possible to support Solaris 10 = 2.1 GB
https://www.oracle.com/solaris/solaris11/downloads/solaris11-vmtemplates-vmvirtualbox-downloads.html
Perhaps it takes less than 20 minutes to load

This probably works with the new libvirt/kvm/ssh-based system, should close.
But @wdlkmpx maybe make a separate feature request to also support older releases? (I wouldn’t mind 8 and even older ones *iff there are compilers for those.)


Trading issue on live for kraken

Unhandeld AddOrder error:
Error: Kraken API returned error: General:Invalid arguments:volume
at Request._callback (/app/node_modules/kraken-api/kraken.js:155:34)
at Request.self.callback (/app/node_modules/request/request.js:188:22)
at emitTwo (events.js:125:13)
at Request.emit (events.js:213:7)
at Request. (/app/node_modules/request/request.js:1171:10)
at emitOne (events.js:115:13)
at Request.emit (events.js:210:7)
at IncomingMessage. (/app/node_modules/request/request.js:1091:12)
at Object.onceWrapper (events.js:314:30)
at emitNone (events.js:110:20)
at IncomingMessage.emit (events.js:207:7)
at endReadableNT (_stream_readable.js:1047:12)
at _combinedTickCallback (internal/process/next_tick.js:102:11)
at process._tickCallback (internal/process/next_tick.js:161:9)
{ Error: order rejected
at /app/lib/engine.js:229:23
at KrakenClient. (/app/extensions/exchanges/kraken/exchange.js:253:20)
at Request._callback (/app/node_modules/kraken-api/kraken.js:155:23)
at Request.self.callback (/app/node_modules/request/request.js:188:22)
at emitTwo (events.js:125:13)
at Request.emit (events.js:213:7)
at Request. (/app/node_modules/request/request.js:1171:10)
at emitOne (events.js:115:13)
at Request.emit (events.js:210:7)
at IncomingMessage. (/app/node_modules/request/request.js:1091:12)
at Object.onceWrapper (events.js:314:30)
at emitNone (events.js:110:20)
at IncomingMessage.emit (events.js:207:7)
at endReadableNT (_stream_readable.js:1047:12)
at _combinedTickCallback (internal/process/next_tick.js:102:11)
at process._tickCallback (internal/process/next_tick.js:161:9)
order:
{ id: null,
status: 'rejected',
price: '40.55017050',
size: '0.05056425',
created_at:<PHONE_NUMBER>995,
filled_size: '0',
post_only: true,
reject_reason: 'Kraken API returned error: General:Invalid arguments:volume' },
desc: 'could not execute buy: error placing order' }

It runs and works on kraken its just every few hours Im getting this.

Googling around for that problem didn't yield too many results for me, you might be better off opening a support ticket with Kraken and asking them what it means- when you report back with what they said we might be able to update our code for it.

Posted a request at support.kraken.com, will let you know what they tell me.

They replied:

Please make sure that you submit order volume as a string with up to 8 decimals precision. Also please check if you fit into the minimum order volume here:
https://support.kraken.com/hc/en-us/articles/205893708-What-is-the-minimum-order-size-

At least we have an explanation now!

So it means that an order size is too little? Is possible to avoid it?

I guess it requires ZenBot to test if the order size is not too small. I don't think they make the list available through the API, though.

Dear issue reporter,
We have slightly changed our github issue policy and would now kindly request folks that have questions that they ask them in our zenbot subreddit.
You can find it here: https://reddit.com/r/zenbot
This issue will be closed, but if you disagree with your ticket being marked as a question feel free to leave a comment defending your case.
Thanks for contributing time and effort!
Greetings,
🤖


Separate the linter and test check

Summary
Separate the linter and the test check due to the following reason

We processed another flake8 check in the GitHub Action workflow
The have issues from pytest-flake8 https://github.com/tholo/pytest-flake8/issues/87
The community between flake8 and pytest might not fix this short-term https://github.com/PyCQA/flake8/issues/1652

Compare to the former pytest result, reduce the failed case
before
https://github.com/bluet/proxybroker2/runs/7930513586?check_suite_focus=true#step:6:9230
================== 46 failed, 35 passed, 56 warnings in 2.33s ==================

after
https://github.com/bluet/proxybroker2/runs/7931186420?check_suite_focus=true
================== 18 failed, 35 passed, 56 warnings in 0.97s ==================

Moreover, the Python 3.6 and 3.7 pass the test

Cool


TypeError: Cannot read property 'string' of undefined

Hey,
when trying to run the app i get the issue below:

Sorry @rumenandreev01 - For some reason I didn't get a notification for this.
I realise that you've likely moved on from this, but for anyone else that runs into this, this error is telling you that on line 14, React.PropTypes is undefined.
It's been a while since I've looked at this repo, but if you're still after an answer, let me know and I'll try to look into it for you.

how to import this package in es6 or 7?

The problem still exists as of now.

Facing the same problem...

Same issue here

2021, same issue

Apologies all - I have now deprecated this package and will not be making any future changes, as it would be easier to start from scratch than try to refactor this.
CC: @darklight147

Good luuck 😀


Support adding CSI based volumes to pods

in azure, in order to load secrets from the keyvault the following volume + volumemounts are required:
    spec:
      containers:
        volumeMounts:
        - name: secrets-store-inline
          mountPath: "/mnt/secrets-store"
          readOnly: true
      volumes:
      - name: secrets-store-inline
        csi:
          driver: secrets-store.csi.k8s.io
          readOnly: true
          volumeAttributes:
            secretProviderClass: "azure-vault"

additional volumes are supported according to the documentation  - https://github.com/Opster/opensearch-k8s-operator/blob/main/docs/userguide/main.md  but only limted to configmaps and secrets

Hi @anubisg1. Thank you for your suggestion. I've marked this issue as an enhacement request.
If you feel up to it and want to give it a shot, PRs are always welcome.

Hi @swoehrl-mw ,
I would like to give this a try. I will send a PR


Feature Request: List Helm releases filtered by labels

I'd want to label "helm releases" to efficiently retrieve only part of helm releases.
To achieve that, I'm imagining at least one enhancement to helm list. That is to accept --selector key1=val1 or -l key1=val1 like kubectl get RESOURCE -l key1=val1 does. helm list -l key1=val shows helm releases that matches the selector. In this case it means those labeled key1: val1 onto their underlying configmaps(or secrets) that tiller created to store the releases info.
Initial U/X
Today what tiller creates for a helm release named httpserver looks like this:
  kind: ConfigMap
  metadata:
    creationTimestamp: 2018-09-09T05:44:08Z
    labels:
      MODIFIED_AT: "1536471850"
      NAME: httpserver
      OWNER: TILLER
      STATUS: DEPLOYED
      VERSION: "1"
    name: httpserver.v1

You can label the configmap by:
kubectl label configmap httpserver.v1 tier=web

So that, with the new -l flag added to helm list, I can list only web related releases:
helm list -l tier=web

Detailed Specs
How release labels are implemented in release configmaps/escrets
Note that I intentionally opted to not add a UPPSER_CASE prefixes to labels.
Instead of the below:
  kind: ConfigMap
  metadata:
    creationTimestamp: 2018-09-09T05:44:08Z
    labels:
      MODIFIED_AT: "1536471850"
      NAME: httpserver
      OWNER: TILLER
      STATUS: DEPLOYED
      VERSION: "1"
      RELEASE_LABEL_tier: web
    name: httpserver.v1

I would see:
  kind: ConfigMap
  metadata:
    creationTimestamp: 2018-09-09T05:44:08Z
    labels:
      MODIFIED_AT: "1536471850"
      NAME: httpserver
      OWNER: TILLER
      STATUS: DEPLOYED
      VERSION: "1"
      tier: web
    name: httpserver.v1

So that we can use the same infrastructure to implement features like https://github.com/helm/helm/issues/4143#issuecomment-393226417 (cc/ @rcorre). That is, helm helm ls --namespace MYNS becomes equivalent to helm list -l NAMESPACE=MYNS.
Future Works
Personally I'm ok with also implementing ways to add labels to the release at installation time. helm install mycharts/httpserver -l tier=web, and helm upgrade --install mycharts/httpserver -l tier=web.
For feature parity with kubernetes labels, helm label RELEASE K=V would also make sense.
Also, kubectl label allows you to remove labels by using - suffix, e.g. kubectl label configmap NAME K-. If we get to implement the helm label command, it would be nice to also add support for removing label.
However, I intentionally leave these as future works for now, to make the scope of this feature request minimum, and ease implementing the MVP.

Hey @mumoshu - Thanks for this proposal. This looks like a useful feature and it's not the first time I've heard this request (cc/ @mikelorant. At the moment, we are not accepting any major features for Helm v2. I am adding the v3 label to this so that we can consider it for helm v3.

+1 on this. Release name is limited to specific amount of chars and it really does not describe anything. We need a way to add metainfo based on labels so that we can select releases using some specific selectors. I'd also love to see something like "description" or "comment" for the release that woud make entries in helm ls listing more descriptive.

Is anyone able to actually use this in their releases and filtering with helm list -l key=value?
I currently have a release with the following configmap and when using the -l flag I get no results at all.
apiVersion: v1
data:
  TEST_1: "1"
  TEST_2: two
kind: ConfigMap
metadata:
  labels:
    app.kubernetes.io/managed-by: Helm
    name: test-config
    namespace: test

I've tried the following commands but neither finds any results.
$ helm list -l "app.kubernetes.io/managed-by=Helm" -n test
$ helm list -l app.kubernetes.io/managed-by=Helm -n test
$ helm list -l "app.kubernetes.io/managed-by==Helm" -n test
$ helm list -l app.kubernetes.io/managed-by==Helm -n test

What am I doing wrong?


About pre-trained model

If I use a backbond(such as resnet101) which use this inplace abn, I must use the pre-trained model' weight that you give?

@asfavdfqefc no, you can use inplace ABN in any architecture, you just need to properly replace BN+Activation with Inplace ABN. We provide a pre-trained resnet101 to show that we can reproduce the scores of the original models and allow to use it directly via our repository.

ok  I see, Thank you very much


ensure rename does not change index type

[x] Closes #3522
[x] Tests added
[x] Passes black . && mypy . && flake8
[x] Fully documented, including whats-new.rst for all changes and api.rst for new API

FWIW I think we can replace https://github.com/pydata/xarray/pull/3532/files#diff-921db548d18a549f6381818ed08298c9R2662-R2667 also with .rename, but it's minor and doesn't need to be in this PR

I have to look how this is done in the  MultiIndex.

I think the current code will mutate the existing index name, is that correct?

Currently the index is recreated with the same name (even if it does not change it's name). We could change the following lines
https://github.com/pydata/xarray/blob/40588dc38ddc2d573e3dc8c63b2e6533eb978656/xarray/core/dataset.py#L2649-L2651
 new_name = name_dict.get(k, None)
 if new_name not in dims_set or new_name is None:
     continue

to skip doing this.

No, this probably does not work if only one of the names of a MultiIndex changes...

Currently the index is recreated with the same name (even if it does not change it's name). We could change the following lines

I was unclear when I wrote "current code"; I was referring to proposed code in this PR. I don't think the code on master mutates the existing index, because it's making a copy. But I think this does:
                index = v
                index.name = new_name

Thanks, yes my approach was indeed wrong. I updated the code and the tests. I was confused for a while because orig.rename_dims(time="time_new") drops indexes while orig.rename_dims() does not.

Fine for me. I think MultiIndex could be treated the same. However, it does conserve CFTimeIndex already, and the test would require a bit of thinking, so let's leave that for now.

Perfect, thanks again @mathause


[BUG]

Describe the bug
Loading stuck at 0%
Steps to Reproduce
I go into the Hydra launcher and try to download the game, the download gets stuck
Expected behavior
Help me with the problem
Screenshots
No response
Operating System
Windows 10
Hydra Version
2.0.3
Additional Information
firewall doesn't help

Facing the same issue man

Faz 2 semanas que estou com o mesmo problema, achei até que era minha maquina kkk

Try downgrading for an older version.

Real Debrid or Torrent downloads?
If possible, upload your logs files, they are located on %appdata%/hydra/logs

No response in a long time. Closing issue.
If any of you is still facing this issue, please open a new one after updating to 2.1.7


Update README on Docker Hub to point to new repository infra

TODO: update the README on Docker Hub to redirect to the new place we host the images.
Originally posted by @lopopolo in https://github.com/artichoke/docker-artichoke-nightly/issues/141#issuecomment-1480738194
The README is stored here: https://github.com/artichoke/docker-artichoke-nightly/blob/trunk/doc/docker-hub-image-readme.md
Send a PR and then update on Docker Hub.

Docker walked back its changes to sunset the free tier, which means this work is no longer required.

https://github.com/artichoke/docker-artichoke-nightly/issues/141#issuecomment-1869117383


@pinia/nuxt@npm:0.4.11 doesn't provide vue (p95b2b), requested by pinia

I'm unable to compile when running yarn install. I'm using Node v18.16.1. I'm getting:
➤ YN0000: ┌ Resolution step
➤ YN0002: │ @pinia/nuxt@npm:0.4.11 doesn't provide vue (p95b2b), requested by pinia
➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements  for details, where  is the six-letter p-prefixed code
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
➤ YN0000: └ Completed
➤ YN0000: ┌ Link step
➤ YN0000: │ ESM support for PnP uses the experimental loader API and is therefore experimental
➤ YN0007: │ nuxt-app@workspace:. must be built because it never has been before or the last one failed
➤ YN0009: │ nuxt-app@workspace:. couldn't be built successfully (exit code 1, logs can be found here: /private/var/folders/cq/vrndzcns4sx76h_l6m5y2y340000gn/T/xfs-8a4c597f/build.log)
➤ YN0000: └ Completed in 0s 597ms
➤ YN0000: Failed with errors in 0s 806ms
I tried installing vue directly but the error persists.

Funny, that's the same issue I mentioned I had with yarn. I just tried to install things with node 18.16.1 and had no issues. Also was your package-lock.json modified by all these attempts?

I tried deleting package-lock.json and node_modules but still see the same error.


Uart Async: Improve interrupt handling and irq<-->future communication

Thank you!
Thank you for your contribution.
Please make sure that your submission includes the following:
Must

[yes with esp32s3 embassy serial example] The code compiles without errors or warnings.
[not tested] All examples work.
[yes] cargo fmt was run.
[yes] Your changes were added to the CHANGELOG.md in the proper section.
[n/a] You updated existing examples or added examples (if applicable).
[n/a] Added examples are checked in CI

Nice to have

[No] You add a description of your work to this PR.
[No] You added proper docs for your newly added features and code.

Ok, will switch to enumset and post a new issue regarding overflow!


Train 195

High Level Description
#1751 "1.9.2 should report its version as 1.9.2 😸"
#1758 "Update the DC/OS UI package to include the latest fixes and improvements."
Related Issues

@mesosphere-mergebot bump-ee

Any reason not to include other 1.9.x PRs with Ship-Its?
https://github.com/dcos/dcos/pull/1742
https://github.com/dcos/dcos/pull/1757
Why have them wait for 1.9.3 when they're ready now?

@adam-mesos Both of those had comments saying to wait til 1.9.3. I'm under the impression that 1.9.2 was supposed to be 'done' after the version bump, but in that case it'd make more sense to also defer the UI update to 1.9.3 😕❓ @lingmann

@adam-mesos @margaret that is correct, we started a soak a few days ago for releasing 1.9.2 and there is a specific desire to not destabilize anything that has been soaked. The PR's on this train are the only ones that were deemed safe to add (would not reset soak time) per discussions with Cathy. Once this lands we will release 1.9.2, create the 1.9 "next" branch, and everyone's 1.9 PR's can start targeting that.

Tests failing on the Enterprise PR are Custom-CA which is not meant to work until 1.10, and test_networking.test_vip which is unfortunately flaky.

Thank you!

@mesosphere-mergebot bump-ee


support for elixir exunit tests

I'll update the pr to prepend the 'test'

appended test+describe to the names+modified the comments


HL-321 | Integrate YRTTI API

Description :sparkles:
Issues :bug:
Testing :alembic:
Screenshots :camera_flash:
Additional notes :spiral_notepad:

Codecov Report

Merging #516 (12f9f42) into develop (5017aee) will increase coverage by 0.24%.
The diff coverage is 41.37%.

@@             Coverage Diff             @@
##           develop     #516      +/-   ##
===========================================
+ Coverage    94.39%   94.63%   +0.24%
===========================================
  Files          161       87      -74
  Lines         6406     2966    -3440
===========================================
- Hits          6047     2807    -3240
+ Misses         359      159     -200

Impacted Files
Coverage Δ

backend/shared/shared/yrtti/yrtti_client.py
41.37% <41.37%> (ø)

backend/benefit/companies/api/v1/views.py

backend/benefit/companies/services.py

backend/benefit/companies/tests/conftest.py

...ckend/benefit/companies/tests/data/company_data.py

backend/benefit/companies/tests/test_api.py

backend/benefit/helsinkibenefit/settings.py

backend/benefit/helsinkibenefit/urls.py

backend/benefit/users/utils.py

.../benefit/messages/migrations/0003_add_seen_flag.py

... and 173 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 5017aee...12f9f42. Read the comment docs.


How can I catch the moment when card will be swipped?

Hi devs! I want to determine moment when tindercard will be swipped. When I move card to left on 20px and untouch my finger the card go to initial place. When I move card to left on 60px card animatedly swipped to left. How can I determine when card will be swipped. I want that to implement this feature to app

And when I swipe to right. Right button should be outlined.

@ShaunRain Any feedback?

@RomanSoviak Working on it :)

@RomanSoviak Check the new version and example, two feature added :)

@ShaunRain Awesome fix! Thanks a lot.


Standalone JS pkg

The custom DataTable Mosaic client should be published to npm and usable without the Python-based db.

@manzt Absolutely loving quak and would really like to see it available as a standalone JS package.  If you pursue this option, would it be possible to add an option filterBy similar to mosaic/vgplot so that we can tie together DataTable with mosaic inputs?

In other words, make quak a mosaic component that satisfies the component interface?

@domoritz yes, would be a really nice addition to the components.

And while I originally was only thinking the DataTable it would also be even nicer if each of the filters in the column headings would be available as well as input components.

Yes! This is my intention. I think DataTable is a mosaic component (it extends from MosaicClient). Right now you could access the filterBy with:
import { coordinator } from "@uwdata/mosaic-core";
import { datatable } from "./lib/clients/DataTable.ts";

// setup df table in database...

const dt = await datatable("df", { coordinator: coordinator() });
const filterBy = dt.filterBy; // use with other clients

Originally I'd had this lifted up one level, where you could create and pass in the crossfilter selection (filterBy) yourself, but I don't see much of a difference between the APIs (and also potential to pass in a Selection that wasn't a crossfilter felt like a poor API design). Open to reverting to:
import { coordinator, Selection } from "@uwdata/mosaic-core";
import { datatable } from "./lib/clients/DataTable.ts";

// setup df table in database...
const filterBy = Selection.crossfilter();
const dt = await datatable("df", { coordinator: coordinator(), filterBy: filterBy });

if there are things I'm missing!

Here is a really, really ugly example (please excuse my foolish ignorance of Typescript and lots of other things) stackblitz.com/~/github.com/timelyportfolio/quak.

wow, totally love that we can share ideas with stackblitz this way. thanks for sharing, @timelyportfolio  :)


Update for v12

The plugin is incompatible with Foundry V12

Alright, thanks for the update :+1:

Hi there, any news about when a V12 update is coming?

V12 is still too risky of an upgrade but the timeframe in which I devise v12 branch being release is around mid Sept. Help is always welcomed.

Do you know anywhere I can start to help with? I have some knolege with developing, so maybe I can help with something

Hi! Any update on the V12 compatibility?


graphical prompt for password

This would be very useful. Alternative, reading password from stdin could be used, and scripted around.

I wonder if it would be best to use an external tool for that. e.g. bemenu

Also, using -passwd ~/.vnc/passwd`, which keeps the password encrypted and created by the VNC server if called by non root, then one copies it over to the client.  That client option is available on tigervnc for example.

For me the gui password prompt is the best, particularly if wlvncc is not called through CLI on a terminal, but rather from a *.desktop and wofi for example.  Alternatively providing a vncpasswd utility/script to create the ~/.vnc/passwd file with the password somehow obfuscated, and supporting something like -passwd to allow using the created ~/.vnc/passd file, can be an option .  But for security it's way better a GUI prompt for the password.

this is what i currently use:
  expect -c "
spawn wlvncc ${HOST}
expect Password:
send ${PASSWD}\r
interact
"

...still, i would prefer if there was a way without the "except" trickery.

I don't even get a prompt, just the "Unknown Authentication" error. I guess this is a different issue.

Well, I'm calling it done.


Fix Website Formatting Issues

The AutoGluon website has several major formatting issues, likely tied to how it is compiled / built. Generic sphinx looks fine, but our website differs from what generic sphinx would render.
Expected reason for issues

We are using a forked version of d2l-book from 2019 to compile docs.
These are the other dependencies we use for doc builds, some may be outdated or not what we want:

ipykernel>=4.5.1,<6.0.0
jupyter-sphinx>=0.3.2
portalocker
nose
docutils<0.16
mu-notedown
awscli>=1.18.140
sphinx==3.2.0
sphinxcontrib-applehelp==1.0.2
sphinxcontrib-bibtex==1.0.0
sphinxcontrib-devhelp==1.0.2
sphinxcontrib-htmlhelp==1.0.3
sphinxcontrib-jsmath==1.0.1
sphinxcontrib-qthelp==1.0.3
sphinxcontrib-serializinghtml==1.1.4
sphinxcontrib-svg2pdfconverter==1.1.0

Tables
Tables are strangely formatted, lacking line separators, forcing centering of cells, and forcing right-alignment of column names. Beyond this there are even stranger issues such as random spaces between letters and single words being split between multiple lines.
Example table showcasing all issues
Source code of table:
| Optimization                      |                                          Inference Speedup                                           | Cost                              | Notes                                                                                |
|:----------------------------------|:----------------------------------------------------------------------------------------------------:|:----------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| refit_full                        |                             At least 8x+, up to 160x (requires bagging)                              | -Quality, +FitTime                | Only provides speedup with bagging enabled.                                                                                |
| persist_models                    |                                    Up to 10x in online-inference                                     | ++MemoryUsage                     | If memory is not sufficient to persist model, speedup is not gained. Speedup is most effective in online-inference and is not relevant in batch inference.                             |
| infer_limit                       |                                       Configurable, ~up to 50x                                       | -Quality (Relative to speedup)    | If bagging is enabled, always use refit_full if using infer_limit.                                                                                |
| distill                           |             ~Equals combined speedup of refit_full and infer_limit set to extreme values             | --Quality, ++FitTime              | Not compatible with refit_full and infer_limit.                                                                                |
| feature pruning                   |               Typically at most 1.5x. More if willing to lower quality significantly.                | -Quality?, ++FitTime              | Dependent on the existence of unimportant features in data. Call `predictor.feature_importance(test_data)` to gauge which features could be removed.                                   |
| use faster hardware               |                       Usually at most 3x. Depends on hardware (ignoring GPU).                        | +Hardware                         | As an example, an EC2 c6i.2xlarge is ~1.6x faster than an m5.2xlarge for a similar price. Laptops in particular might be slow compared to cloud instances.                             |
| manual hyperparameters adjustment |                    Usually at most 2x assuming infer_limit is already specified.                     | ---Quality?, +++UserMLExpertise   | Can be very complicated and is not recommended. Potential ways to get speedups this way is to reduce the number of trees in LightGBM, XGBoost, CatBoost, RandomForest, and ExtraTrees. |
| manual data preprocessing         | Usually at most 1.2x assuming all other optimizations are specified and setting is online-inference. | ++++UserMLExpertise, ++++UserCode | Only relevant for online-inference. This is not recommended as AutoGluon's default preprocessing is highly optimized.                                                                  |

Badges
Badges when attempted to be all on one row are instead vertically stacked.
Example of badges issue
Source code of badges:
.. |ReleaseVersion| image:: https://img.shields.io/badge/doc%20release-v0.4.0-blue
.. _ReleaseVersion: https://auto.gluon.ai/dev/versions.html
.. |StableVersion| image:: https://img.shields.io/github/v/release/awslabs/autogluon?color=blue&label=stable%20release&sort=semver
.. _StableVersion: https://auto.gluon.ai/stable/index.html
.. |PythonVersion| image:: https://img.shields.io/badge/python-3.7%20%7C%203.8%20%7C%203.9-blue
.. _PythonVersion: https://pypi.org/project/autogluon/
.. |GitHub| image:: https://img.shields.io/github/stars/awslabs/autogluon?style=social
.. _GitHub: https://github.com/awslabs/autogluon/stargazers
.. |Twitter| image:: https://img.shields.io/twitter/follow/autogluon?style=social
.. _Twitter: https://twitter.com/autogluon
.. |Downloads| image:: https://pepy.tech/badge/autogluon/month
.. _Downloads: https://pepy.tech/project/autogluon
.. |License| image:: https://img.shields.io/github/license/awslabs/autogluon?color=blue
.. _License: https://github.com/awslabs/autogluon/blob/master/LICENSE

|ReleaseVersion|_ |StableVersion|_ |PythonVersion|_ |License|_ |Downloads|_ |GitHub|_ |Twitter|_

Doc Strings
Doc strings ignore line breaks and are formatted very strangely compared to their source code:
Example of strange doc string formatting
Source code of doc strings

Fixed in the website refactor


Adding BookCatering

Adding BookCatering which allows user to book catering for required events.

@sunny0625 please assign me this issue

@sunny0625


Add debugger instructions for lens

In zipkin-js, we have an easy way to use a debugger for tests. Let's have one for lens, also!
https://github.com/openzipkin/zipkin-js#debugging

pasting this seems to work:
"test:debug": "react-scripts --inspect-brk test --runInBand --no-cache",
then.. npm run test:debug -- src/zipkin/span-node.test.js
see https://create-react-app.dev/docs/debugging-tests/

@mrajah-twttr want to give a try at first PR by trying these instructions, then adding to lens README?

ack!


Add import statement to make example runnable

Currently, this example fails on the first line as sprand and I haven't been imported.  I discussed this in this Discourse comment: https://discourse.julialang.org/t/non-friendly-documentation/38109/112

Thanks, @GregVernon! I fixed the import statements and added the relevant part to the doctests in #285. That PR will supersede this PR.


Instanced scene child nodes are not displayed when selecting a NodePath

Godot version:
3.1alpha5
Issue description:
NodePath selection dialog does not allow to select a child of an instanced scene unless "editable children" is turned on.
In my case, i need to reference a special camera that belongs to an instanced scene.
My levels have a fairly similar structure, but in order to keep the project more solid and flexible I use NodePath and not direct referencing (with $Object).
Every time i create a level and i want to reference that camera i need to

Tick on editable children for the camera
Assign the nodepath to the camera
Tick off editable children.

If every node would be selectable in the NodePath dialog, I could spare quite some clicking and scrolling (expecially when the camera and the nodes i want to assign it to are far away in the level hierarchy)
Proposal:
Show also child nodes of inherited scenes in some way (by default, add a checkbox, etc...)

Feature and improvement proposals for the Godot Engine are now being discussed and reviewed in a dedicated Godot Improvement Proposals (GIP) (godotengine/godot-proposals) issue tracker. The GIP tracker has a detailed issue template designed so that proposals include all the relevant information to start a productive discussion and help the community assess the validity of the proposal for the engine.
The main (godotengine/godot) tracker is now solely dedicated to bug reports and Pull Requests, enabling contributors to have a better focus on bug fixing work. Therefore, we are now closing all older feature proposals on the main issue tracker.
If you are interested in this feature proposal, please open a new proposal on the GIP tracker following the given issue template (after checking that it doesn't exist already). Be sure to reference this closed issue if it includes any relevant discussion (which you are also encouraged to summarize in the new proposal). Thanks in advance!


Add VisionOS support

This PR adds support or VisionOS by:

Adding the visionOS platform to the Package.swift file
Adding a visionOS target, test target, test plan, and scheme to the Xcode Project

When running the tests on visionOS, there is a single failing test. I'm not familiar enough with the library to know what could be causing that failure. If someone is able to point me in the right direction, I'd be happy to get the test passing so this can be merged in.

It looks like this test failure is unrelated to this PR, as it was also failing in this other PR.

@nathanfallet, any chance we could get some eyes on this? We've got users of our SDK asking for VisionOS support, and we are waiting on support in this library to make that work.

Awesome thank you! Looks like the just that one broken test that is failing still.

Yes I need to check why; I don't think it's related to visionOS addition, but I don't want to merge if it's failing 😅

Last thing to fix:
-> SQLite.swift/standalone (0.14.1)
    - ERROR | [SQLite.swift/standalone] xcodebuild: Returned an unsuccessful exit code. You can use `--verbose` for more information.
    - NOTE  | [SQLite.swift/standalone] xcodebuild:  note: Using codesigning identity override: -
    - NOTE  | [SQLite.swift/standalone] xcodebuild:  note: Building targets in dependency order
    - NOTE  | [iOS] [SQLite.swift/standalone] xcodebuild:  note: Target dependency graph (4 targets)
    - NOTE  | [SQLite.swift/standalone] xcodebuild:  clang: error: SDK does not contain 'libarclite' at the path '/Applications/Xcode_15.0.1.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/arc/libarclite_iphonesimulator.a'; try increasing the minimum deployment target
    - NOTE  | [SQLite.swift/standalone] xcodebuild:  Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 12.0 to 17.0.99. (in target 'sqlite3' from project 'Pods')
    - NOTE  | [iOS] [SQLite.swift/standalone] xcodebuild:  note: Target dependency graph (3 targets)

[!] SQLite.swift did not pass validation, due to 1 error.

I had the warning for IPHONEOS_DEPLOYMENT_TARGET 3 times (the two other ones were from 11.0, I updated it in the podspec) but I'm unable to get rid of this last one. (it's a warning but I read the missing libarclite was linked to this)

Last thing to fix

It's probably https://github.com/CocoaPods/CocoaPods/issues/11839. If you manage to fix it, I'll be happy to know your solution :-)

@nathanfallet - where are we on getting this resolved and merged?

@calvincestari I'm trying to find a solution with cocoapods that currently breaks the project. When that will be fixed, we'll be able to merge it.

@nathanfallet Any luck or insight on the cocoapods breaking the VisionOS support?

Thanks for getting this merged @nathanfallet, much appreciated!

@nathanfallet, another question for this: will the podspec be updated to declare support for visionOS too? When I try push our updated podspec I get an error about incompatibility with SQLite.swift and visionOS. I believe it requires another deployment target.

- ERROR | [visionOS] [Apollo/SQLite] unknown: Encountered an unknown error (The platform of the target `App` (visionOS 1.0) is not compatible with `SQLite.swift (0.15.1)`, which does not support `visionOS`.) during validation.

@calvincestari I'll have a look at that, it might have been missing in the PR


KAFKA-6949; alterReplicaLogDirs() should grab partition lock when accessing log of the future replica

NoSuchElementException will be thrown if ReplicaAlterDirThread replaces the current replica with future replica right before the request handler thread executes futureReplica.log.get.dir.getParent in the ReplicaManager.alterReplicaLogDirs(). The solution is to grab the partition lock when request handler thread attempts to check the destination log directory of the future replica.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@hachikuji Thanks for catching the issue! This patch should fix the problem. I still need to think more and add test for this bug.

@hachikuji The test is added now. Thanks!

retest this please

@hachikuji Thanks for the review! The PR has been updated to address all comments.

@junrao Thanks for the comment! I have updated the patch as suggested.

retest this please

@junrao Thanks for the review! Merged to trunk. I will later merge it to 2.0.


mountOptions in storageClass ignored

Description
I create a storageClass with mountOptions for noatime but it is mounted with relatime:
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  annotations:
    cas.openebs.io/config: |
      - name: StorageType
        value: "device"
      - name: FSType
        value: "xfs"
    k8s.inky.com/type: storage-definitions
    openebs.io/cas-type: local
  creationTimestamp: "2023-10-25T18:19:33Z"
  labels:
    kustomize.toolkit.fluxcd.io/name: storageclasses
    kustomize.toolkit.fluxcd.io/namespace: flux-system
  name: openebs-device-xfs
  resourceVersion: "95634991"
  uid: 64d0034c-b0cb-4d5f-be10-5af3161cdedc
mountOptions:
- rw
- noatime
provisioner: openebs.io/local
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer

Expected Behavior
the volume is mounted with noatime
Current Behavior
the volume is mounted with relatime:
$ mount | grep data
/dev/nvme1n1 on /usr/share/elasticsearch/data type xfs (rw,relatime,attr2,inode64,logbufs=8,logbsize=32k,noquota)
note other mount points are mounted with noatime, with no user supplied configuration, such as:
$ mount |grep noatime
/dev/nvme0n1p1 on /mnt/elastic-internal/scripts type xfs (ro,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota)
Possible Solution

Steps to Reproduce

Screenshots

Your Environment
This is EKS 1.27 with Elastic Operator 2.9.
Labels:            openebs.io/cas-type=local-device
Annotations:       local.openebs.io/blockdeviceclaim: bdc-pvc-4fc79c72-73c7-4afe-986d-8955ed5ba384
                   pv.kubernetes.io/provisioned-by: openebs.io/local
Finalizers:        [kubernetes.io/pv-protection]
StorageClass:      openebs-device-xfs
Status:            Bound
Claim:             prod-es-api/elasticsearch-data-elastic-es-data-im4gn-0
Reclaim Policy:    Delete
Access Modes:      RWO
VolumeMode:        Filesystem
Capacity:          6480Gi
Node Affinity:
  Required Terms:
    Term 0:        kubernetes.io/hostname in [ip-10-1-1-1.ec2.internal]
Message:
Source:
    Type:  LocalVolume (a persistent volume backed by local storage on a node)
    Path:  /dev/disk/by-id/nvme-Amazon_EC2_NVMe_Instance_Storage_AWS2237581B2AD77D83C
Events:    <none>

and the PVC:
Namespace:     prod-es-api
StorageClass:  openebs-device-xfs
Status:        Bound
Volume:        pvc-4fc79c72-73c7-4afe-986d-8955ed5ba384
Labels:        common.k8s.elastic.co/type=elasticsearch
               elasticsearch.k8s.elastic.co/cluster-name=elastic
               elasticsearch.k8s.elastic.co/statefulset-name=elastic-es-data-im4gn
Annotations:   pv.kubernetes.io/bind-completed: yes
               pv.kubernetes.io/bound-by-controller: yes
               volume.beta.kubernetes.io/storage-provisioner: openebs.io/local
               volume.kubernetes.io/selected-node: ip-10-1-1-1.ec2.internal
               volume.kubernetes.io/storage-provisioner: openebs.io/local
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:      6480Gi
Access Modes:  RWO
VolumeMode:    Filesystem
Used By:       elastic-es-data-im4gn-0
Events:
  Type    Reason                 Age                   From                                                                                Message
  ----    ------                 ----                  ----                                                                                -------
  Normal  WaitForPodScheduled    34m (x321 over 114m)  persistentvolume-controller                                                                         waiting for pod elastic-es-data-im4gn-0 to be scheduled
  Normal  Provisioning           32m                   openebs.io/local_openebs-localpv-provisioner-7c8d9f689f-6gfl2_6a76a399-7ab8-4cb0-a6e6-66edfad57585  External provisioner is provisioning volume for claim "prod-es-api/elasticsearch-data-elastic-es-data-im4gn-0"
  Normal  ProvisioningSucceeded  32m                   openebs.io/local_openebs-localpv-provisioner-7c8d9f689f-6gfl2_6a76a399-7ab8-4cb0-a6e6-66edfad57585  Successfully provisioned volume pvc-4fc79c72-73c7-4afe-986d-8955ed5ba384

kernel: 5.10.186-179.751.amzn2.aarch64
Linux ip-10-1-1-1.ec2.internal 5.10.192-183.736.amzn2.aarch64 #1 SMP Wed Sep 6 21:15:30 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux
santized NDM logs:
I1025 23:10:14.108899       7 eventhandler.go:69] Processing details for /dev/nvme1n1
I1025 23:10:14.109031       7 udevprobe.go:294] device: /dev/nvme1n1, Model: Amazon EC2 NVMe Instance Storage filled by udev probe
I1025 23:10:14.109041       7 udevprobe.go:298] device: /dev/nvme1n1, WWN: nvme.1d0f-4157533232333735383142324144373744383343-416d617a6f6e20454332204e564d6520496e7374616e63652053746f72
616765-00000001 filled by udev probe
I1025 23:10:14.109045       7 udevprobe.go:302] device: /dev/nvme1n1, Serial: AWS22<seria>L filled by udev probe
I1025 23:10:14.109054       7 probe.go:119] details filled by udev probe
I1025 23:10:14.109110       7 sysfsprobe.go:97] blockdevice path: /dev/nvme1n1 capacity :7500000000000 filled by sysfs probe.
I1025 23:10:14.109143       7 sysfsprobe.go:125] blockdevice path: /dev/nvme1n1 logical block size :512 filled by sysfs probe.
I1025 23:10:14.109171       7 sysfsprobe.go:137] blockdevice path: /dev/nvme1n1 physical block size :512 filled by sysfs probe.
I1025 23:10:14.109199       7 sysfsprobe.go:149] blockdevice path: /dev/nvme1n1 hardware sector size :512 filled by sysfs probe.
I1025 23:10:14.109230       7 sysfsprobe.go:160] blockdevice path: /dev/nvme1n1 drive type :SSD filled by sysfs probe.
I1025 23:10:14.109237       7 probe.go:119] details filled by sysfs probe
E1025 23:10:14.109264       7 smartprobe.go:101] map[errorCheckingConditions:the device type is not supported yet, device type: "NVMe"]
I1025 23:10:14.109277       7 probe.go:119] details filled by smart probe
I1025 23:10:14.109435       7 mountprobe.go:134] no mount point found for /dev/nvme1n1. clearing mount points if any
I1025 23:10:14.109444       7 probe.go:119] details filled by mount probe
I1025 23:10:14.116009       7 probe.go:119] details filled by blkid probe
I1025 23:10:14.116031       7 usedbyprobe.go:122] device: /dev/nvme1n1 is not having any zfs partitions
I1025 23:10:14.116111       7 probe.go:119] details filled by used-by probe
I1025 23:10:14.116120       7 probe.go:119] details filled by Custom Tag Probe
I1025 23:10:14.116127       7 addhandler.go:53] device: /dev/nvme1n1 does not exist in cache, the device is now connected to this node
I1025 23:10:14.116146       7 osdiskexcludefilter.go:129] applying os-filter regex ^/dev/nvme0n1(p[0-9]+)?$ on /dev/nvme1n1
I1025 23:10:14.116178       7 osdiskexcludefilter.go:129] applying os-filter regex ^/dev/nvme0n1(p[0-9]+)?$ on /dev/nvme1n1
I1025 23:10:14.116202       7 eventhandler.go:82] Processed details for /dev/nvme1n1
I1025 23:10:14.116211       7 addhandler.go:106] checking if device: /dev/nvme1n1 can be uniquely identified
I1025 23:10:14.116218       7 uuid.go:78] device(/dev/nvme1n1) has a WWN, using WWN: nvme.1d0f-4157533232333735383142324144373744383343-416d617a6f6e20454332204e564d6520496e7374616e6365
2053746f72616765-00000001 and Serial: AWS22<serial_id>
I1025 23:10:14.116228       7 uuid.go:101] generated uuid: blockdevice-<uuid> for device: /dev/nvme1n1
I1025 23:10:14.116234       7 addhandler.go:141] uuid: blockdevice-<uuid>  has been generated for device: /dev/nvme1n1
I1025 23:10:14.116238       7 addhandler.go:47] device: /dev/nvme1n1 already exists in cache, the event was likely generated by a partition table re-read or a change in some of the dev
ices was detected
E1025 23:10:14.120697       7 blockdevicestore.go:143] Unable to get blockdevice object : blockdevices.openebs.io "blockdevice-e1f2aeeae9fb6815dddc93c1d810ca84" not found
I1025 23:10:14.120716       7 addhandler.go:147] device: /dev/nvme1n1, uuid: blockdevice-e1f2aeeae9fb6815dddc93c1d810ca84 not found in etcd
I1025 23:10:14.120721       7 addhandler.go:271] creating block device resource for device: /dev/nvme1n1 with uuid: blockdevice-e1f2aeeae9fb6815dddc93c1d810ca84
I1025 23:10:14.131932       7 blockdevicestore.go:45] eventcode=ndm.blockdevice.create.success msg=Created blockdevice object in etcd rname=blockdevice-e1f2aeeae9fb6815dddc93c1d810ca84

@niladrih please take a look at this .

Hey @bdols - are you still having this issue ? or did you figure out a solution?

I'm trying to bring some attention to this... if it's needed. Please let me know ?

still seeing this issue, but I'm still running openebs-3.7.0 and haven't followed the release notes.

This issue still exists on OpenEBS v4.0.1 (dynamic-localpv-provisioner v4.0.0). This requires an enhancement where the PV is built with the mountOptions collected from the StorageClass (here).

We could take this up for v4.2 of OpenEBS.

support for this would be for StorageType=hostpath instead of StorageType=device, then?

Seems a low hanging fruit considering similar functionality exists in the archived project dynamic-nfs-provisioner project. Easy to port the changes.


Fix python 3.12 (upgrade versioneer, add GHA)

replace https://github.com/warner/python-spake2/pull/17 with a branch from this repo so that GHA will run.

This upgrades "versioneer", still using the "vendored" method.
Also adds GitHub Actions matrix (on top of the existing AppVeyor CI) to test more configurations.
(Could consider moving to the "unvendored" versioneer option too, in future)


editDefect fails  (  suds.TypeNotFound: Type not found: 'value'  )

Is possible to get data, users, projects etc.. but not possible to edit defects.
It always fails with that message:
suds.TypeNotFound: Type not found: 'value'
I am using python 2.6.6x64, suds :0.4.1 and testtrackpro 1.01
Would be great to have this working

Same issue here. Any workaround/fix for this?


Acer V30 Help and Questions

I can't send a Ctrl+Alt+Esc to the Acer V30 from the Actions menu. I have 1.7.0 installed.
Just curious, why is the V30 classified as a Socket 7 HX machine? It's definitely Socket 5 FX.

Hi,
Acer V30 should not have been in it [yet], its still 'in test'.
the ctrl-alt-esc is one reason.
The socket thing... yes, good point, will change that.  Expect an 1.7.1 update
soon... :P
--fred

On Wed, 5/1/19, headsetguy37<EMAIL_ADDRESS>wrote:
Subject: [VARCem/VARCem] Acer V30 Help and Questions (#74)
To: "VARCem/VARCem"<EMAIL_ADDRESS>Cc: "Subscribed"<EMAIL_ADDRESS>Date: Wednesday, May 1, 2019, 10:31 PM
I can't send a Ctrl+Alt+Esc to the Acer V30 from the
Actions menu. I have 1.7.0 installed.
Just curious, why is the V30 classified as a Socket 7 HX
machine? It's definitely Socket 5 FX.
—
You are receiving this because you are subscribed to this
thread.
Reply to this email directly, view it on
GitHub, or mute
the thread.

Still working on it.


Bypass auth interceptor if not needed

Need a way to bypass auth interceptor when a http call is made without tubular context.

Thanks for a quick fix!


fix: broken links

| COCUS Portugal :rocket: | COCUS is all about People! We are proud to deliver skilled services and products developed by great talent, with attitude and ambition to work in innovative IT solutions. . | ´Matosinhos |

| COCUS Portugal 🚀 | COCUS is all about People! We are proud to deliver skilled services and products developed by great talent, with attitude and ambition to work in innovative IT solutions. . | Matosinhos |

:confused: You have a pull request with someone else's commit and a description with something completely different.
You can open an issue instead of a pull request if you more comfortable.


Supporting GDeflate in numcodecs

Problem description
GDeflate is a new compression format that is designed to match zlib/gzip/deflate compression ratio but decompress very fast on the GPU (see some benchmarks here). This is currently a standard in Microsoft DirectCompute for gaming applications, but it would be very useful for zarr as well since the ideal use case for this would be compress once, decompress multiple times. Here is the GDeflate spec that is released: https://github.com/microsoft/DirectStorage/blob/main/GDeflate/GDeflate/README.md
The GPU codecs for GDeflate are currently being shipped through kvikIO. But this is only for GPU compression and decompression. This essentially means that compressing on the GPU would mean you need a GPU to decompress as well. We do have CPU routines for GDeflate as well and it would be good to wrap those and expose them through numcodecs too so there is a CPU fallback.
The main question is where should this CPU GDeflate codec go? It can also be packaged in kvikIO, but given that kvikIO is a GPU focused library, it might not be the most natural place for a CPU codec to go. Would it be acceptable to add that codec to numcodecs directly? Would appreciate some guidance on this.

@rabernat Thanks, I'll work on a PR for it then. Might have some questions about packaging which I'll post here if that's okay.


Add salt configuration to remove cadvisor.manifest from master. cadvisor...

... is now part of kubelet
@vmarmol
@dchen1107
@thockin

LGTM, thanks @ArtfulCoder! Will merge on green.

LGTM. Great!


rollup-plugin-babel can not understand "..." in es6

I've put my .babelrc file in the src folder like this:
{
  "presets": [
    [
      "latest",
      {
        "es2015": {
          "modules": false
        }
      }
    ]
  ],
  "plugins": [
    "external-helpers"
  ]
}

And next, i put my rollup.config.js file in the root of the project like this:
import resolve from 'rollup-plugin-node-resolve'
import babel from 'rollup-plugin-babel'

export default {
  // entry: 'dist-loose/index.js',
  entry: 'src/index.js',
  format: 'es',
  plugins: [
      resolve(),
      babel({
        plugins: ['external-helpers'],
        externalHelpers: true,
        exclude: 'node_modules/**'
      })
    ],
  dest: 'dist/bundle.js',
  sourceMap: true
}

And next, i write a line of words in the package.json file's scripts like this:
"scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "build-loose": "babel src --out-dir ./dist-loose --plugins=transform-runtime --presets=es2016,stage-2",
    "build": "babel src --out-file ./dist/ecg.js --plugins=transform-runtime --presets=es2015,stage-2",
    "compile": "rollup -c"
  }

finally, when i run npm run compile, something went wrong and the error info is:
><EMAIL_ADDRESS>compile /Users/taoxin/Downloads/ecg
> rollup -c

🚨   (babel plugin) /Users/taoxin/Downloads/ecg/src/index.js: Unexpected token (7:4)
undefined (7:4)

npm ERR! Darwin 16.5.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "compile"
npm ERR! node v7.2.0
npm ERR! npm  v3.10.9
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>compile: `rollup -c`
npm ERR! Exit status 1
...

The content in the line 7  in the file/Users/taoxin/Downloads/ecg/src/index.js is:
export default {
    $methods: {
        ...obj
    }
}

I've checked that the rollup-plugin-babel can transform "``" into es5, but why it can not understand "..." in es6, and how could i resolve this problem?
I've read the document of the rollup-plugin-babel, but there is no more information about how to sovle this problem and there is no more settings for rollup-plugin-babel in rollup.config.js file.
Sorry for my English.

The Object Rest/Spread Properties proposal is still in stage 3 which means its not yet part of the ECMAScript standard. So to use it you need to either add babel's stage-3 preset or babel's transform-object-rest-spread plugin to your .babelrc.
And BTW, babel's latest preset has been deprecated and replaced by env.

What @zaygraveyard said 😉


Saving readings to SD card

Hi, was wondering if there was any way to save my readings I am getting to a file on the SD card while using aws iot sdk?
THanks

Hi @OtisHarrison24 ,
Thank you very much for your interest in AWS IoT Arduino Yun SDK.
The Yun SDK utilizes the Serial1 connection between ATmega32u4 and AR9331 to translate user sketch commands to Python commands and send them over Serial1 to be executed on embedded Linux.
This mechanism is also used by native Arduino Bridge library, which provides a way to write to a file on Linux. However, since the SDK and Bridge library are using the same Serial1 channel, they cannot be used together otherwise different protocols will be interfering with each other. For more details, please check out this issue.
One work-around you can do is, add your own serial commands that basically executes the write to file action on Linux. You can use the existing serial commands as a reference:
https://github.com/aws/aws-iot-device-sdk-arduino-yun/tree/master/AWS-IoT-Python-Runtime/lib/command
You will also need to come with your own protocol code to map your new sketch APIs to the command you create in Python runtime. You can use the existing sketch commands as a reference as well:
https://github.com/aws/aws-iot-device-sdk-arduino-yun/blob/master/AWS-IoT-Arduino-Yun-Library/aws_iot_mqtt.cpp#L256
Another work-around you can do is, instead of writing the data you read to a local file on Linux, set up an IoT Rule that filters out the data published to one topic and writes to a file in S3 bucket. For more details, you can check out the following documentation:
http://docs.aws.amazon.com/iot/latest/developerguide/s3-rule.html
Hope the above helps.
Thanks,
Liusu

already pushing to S3 but what if there is any internet and the still want to save the data to sd just in case

Hi @OtisHarrison24 ,
In this case, you will need to add your own serial commands that executes write command on Linux/Python like I mentioned in the previous posts, since you cannot use the Bridge library APIs for file access.
This could potentially be a feature request to add customized command support into the SDK. Sorry that I cannot give you a more positive answer for now.
Thanks,
Liusu

Was looking at the serial command. It look like python I could just add a streamwriter to lets say publish serial command and it should write to a file each time it publishes to a topic?


Add TypeScript definitions for React

Hi, thanks for all your work on this awesome library!
This PR adds TypeScript support for the React subproject. I've added a Rollup plugin to copy the type definitions to dist, where they are referenced by package.json.
All tests are passing and the build succeeds.

Hi Chris,
That's awesome, good job.
Do you think the "right way" of doing this wouldn't be to do a PR to https://github.com/DefinitelyTyped/DefinitelyTyped instead of having the typings directly in here? I think that's how the TS community used to do. What do you think?

Thanks, in my experience there's a split between libraries that contain their own type definitions and ones that use DefinitelyTyped.
For my current project, I'm using DefinitelyTyped for Jest, Lodash and React. Other libraries (Axios, Material UI, PIXI etc.) contain their own typings.
From an org member of DefinitelyTyped: "In an ideal world the definitions would be maintained by the library authors, but alas many do not care for TypeScript"
So for me, the ideal is to have the typings directly in the repo (which also means one less NPM dependency), but I'm totally happy to put them in DefinitelyTyped if you'd prefer they go there!

Ok thanks for your explanation. I'm on vacations right now but will take a look when I'm back.
Good job!

Thanks, enjoy your vacation!

Thanks, much appreciated! Hope you had a nice holiday.


Difference between menu and menus ?

https://github.com/callemall/material-ui/tree/master/src/menu
https://github.com/callemall/material-ui/tree/master/src/menus
The doc all uses menus/, but index.js actually exports menu/
https://github.com/callemall/material-ui/blob/master/src/index.js#L35
Also, DropDownMenu and LeftNav components use menu/, and IconMenu (the exported one) uses menus/.
If we want to reproduce http://material-ui.com/#/components/icon-menus, we need to do
const MenuItem = require('material-ui/lib/menus/menu-item');
in userland to do what is written in the docs. require('material-ui').MenuItem is not the right one.

It looks like /menus is the new menu implementation, and /menu is the old one.
//We're working on migrating some of our components to use a new implementation of menus.
//If you'd like to use the new menu before our migration is complete, please directly
//require them like this:

let MenuItem = require('material-ui/lib/menus/menu-item');
let MenuDivider = require('material-ui/lib/menus/menu-divider');

Wow, I'm blind.
Though, I think that the same comment should appear in the other components that use it. (AppBar and List in this case).
Thanks.

@vizath We are deprecating menu folder soon.


Fix py27 vs2015 build and add patch mgmt

@dzenanz @adamrankin Thanks to your outstanding investigative work, we are able to put together a collection of patches.
These patches are directly managed by python-cmake-buildsystem. This means we will not have to explicitly patch Python sources from within Slicer.

Cc: @msmolens

Merging. VS2013 and VS2015 build are successful, all linux build are successful, only osx is lagging behind.


Still getting "Success: Created 0 files" in version 2.3.0 (latest i18n)

Bug Report
wp i18n make-json my-lang-de_DE.po /tmp/ --no-purge --debug
Debug (bootstrap): Loading packages from: /root/.wp-cli/packages/vendor/autoload.php (0.014s)
Debug (bootstrap): Loading detected autoloader: /root/.wp-cli/packages/vendor/autoload.php (0.029s)
Debug (commands): Adding command: i18n (0.032s)
Debug (commands): Adding command: make-pot in i18n Namespace (0.035s)
Debug (commands): Adding command: make-json in i18n Namespace (0.035s)
Debug (bootstrap): Fallback autoloader paths: phar://wp-cli.phar/vendor/autoload.php (0.035s)
Debug (bootstrap): Loading detected autoloader: phar://wp-cli.phar/vendor/autoload.php (0.035s)
Debug (commands): Adding command: cache (0.037s)
Debug (commands): Adding command: transient (0.039s)
Debug (commands): Adding command: comment (0.041s)
Debug (commands): Adding command: meta in comment Namespace (0.042s)
Debug (commands): Adding command: menu (0.042s)
Debug (commands): Adding command: item in menu Namespace (0.043s)
Debug (commands): Adding command: location in menu Namespace (0.043s)
Debug (commands): Deferring command: network meta (0.044s)
Debug (commands): Adding command: option (0.045s)
Debug (commands): Adding command: post (0.046s)
Debug (commands): Adding command: meta in post Namespace (0.046s)
Debug (commands): Adding command: term in post Namespace (0.047s)
Debug (commands): Adding command: post-type (0.047s)
Debug (commands): Adding command: site (0.049s)
Debug (commands): Adding command: meta in site Namespace (0.049s)
Debug (commands): Adding command: option in site Namespace (0.05s)
Debug (commands): Adding command: taxonomy (0.05s)
Debug (commands): Adding command: term (0.052s)
Debug (commands): Adding command: meta in term Namespace (0.053s)
Debug (commands): Adding command: user (0.07s)
Debug (commands): Adding command: meta in user Namespace (0.071s)
Debug (commands): Adding command: session in user Namespace (0.071s)
Debug (commands): Adding command: term in user Namespace (0.072s)
Debug (commands): Adding command: network (0.072s)
Debug (hooks): Processing hook "after_add_command:network" with 1 callbacks (0.072s)
Debug (hooks): On hook "after_add_command:network": Closure in file phar:///home/clients/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/class-wp-cli.php at line 634 (0.072s)
Debug (commands): Adding command: meta in network Namespace (0.072s)
Debug (commands): Adding command: db (0.075s)
Debug (commands): Adding command: plugin (0.079s)
Debug (commands): Adding command: theme (0.082s)
Debug (commands): Adding command: mod in theme Namespace (0.084s)
Debug (commands): Adding command: scaffold (0.087s)
Debug (commands): Adding command: core (0.087s)
Debug (commands): Adding command: verify-checksums in core Namespace (0.09s)
Debug (commands): Adding command: verify-checksums in plugin Namespace (0.091s)
Debug (commands): Adding command: export (0.091s)
Debug (commands): Adding command: config (0.105s)
Debug (commands): Adding command: core (0.113s)
Debug (commands): Adding command: eval (0.115s)
Debug (commands): Adding command: eval-file (0.115s)
Debug (commands): Adding command: import (0.116s)
Debug (commands): Adding command: media (0.14s)
Debug (commands): Adding command: package (0.143s)
Debug (commands): Adding command: cron (0.143s)
Debug (commands): Adding command: event in cron Namespace (0.144s)
Debug (commands): Adding command: schedule in cron Namespace (0.145s)
Debug (commands): Adding command: embed (0.145s)
Debug (commands): Adding command: fetch in embed Namespace (0.146s)
Debug (commands): Adding command: provider in embed Namespace (0.146s)
Debug (commands): Adding command: handler in embed Namespace (0.146s)
Debug (commands): Adding command: cache in embed Namespace (0.147s)
Debug (commands): Deferring command: language core (0.148s)
Debug (commands): Deferring command: language plugin (0.148s)
Debug (commands): Deferring command: language theme (0.15s)
Debug (hooks): Immediately invoking on passed hook "after_add_command:site": Closure in file phar:///home/clients/wp-cli/wp-cli.phar/vendor/wp-cli/language-command/language-command.php at line 39 (0.15s)
Debug (commands): Adding command: switch-language in site Namespace (0.15s)
Debug (commands): Adding command: language (0.15s)
Debug (hooks): Processing hook "after_add_command:language" with 3 callbacks (0.15s)
Debug (hooks): On hook "after_add_command:language": Closure in file phar:///home/clients/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/class-wp-cli.php at line 634 (0.15s)
Debug (commands): Adding command: core in language Namespace (0.15s)
Debug (hooks): On hook "after_add_command:language": Closure in file phar:///home/clients/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/class-wp-cli.php at line 634 (0.15s)
Debug (commands): Adding command: plugin in language Namespace (0.15s)
Debug (hooks): On hook "after_add_command:language": Closure in file phar:///home/clients/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/class-wp-cli.php at line 634 (0.15s)
Debug (commands): Adding command: theme in language Namespace (0.151s)
Debug (commands): Adding command: maintenance-mode (0.151s)
Debug (commands): Adding command: rewrite (0.152s)
Debug (commands): Adding command: rewrite (0.152s)
Debug (commands): Adding command: cap (0.153s)
Debug (commands): Adding command: role (0.154s)
Debug (commands): Adding command: search-replace (0.156s)
Debug (commands): Adding command: server (0.157s)
Debug (commands): Adding command: shell (0.162s)
Debug (commands): Adding command: super-admin (0.162s)
Debug (commands): Adding command: widget (0.163s)
Debug (commands): Adding command: sidebar (0.163s)
Debug (bootstrap): Adding framework command: phar://wp-cli.phar/vendor/wp-cli/wp-cli/php/commands/cli.php (0.164s)
Debug (commands): Adding command: cli (0.166s)
Debug (commands): Adding command: cache in cli Namespace (0.166s)
Debug (commands): Adding command: alias in cli Namespace (0.166s)
Debug (bootstrap): Adding framework command: phar://wp-cli.phar/vendor/wp-cli/wp-cli/php/commands/help.php (0.166s)
Debug (commands): Adding command: help (0.167s)
Debug (bootstrap): No readable global config found (0.167s)
Debug (bootstrap): No project config found (0.167s)
Debug (bootstrap): argv: /home/clients/wp-cli/wp-cli.phar --allow-root i18n make-json wp-ispconfig3-block-de_DE.po /tmp/ --no-purge --debug (0.167s)
Debug (bootstrap): ABSPATH defined: /home/clients/client42/web45/web/ (0.167s)
Debug (hooks): Processing hook "before_run_command" with 1 callbacks (0.167s)
Debug (hooks): On hook "before_run_command": WP_CLI\Bootstrap\RegisterDeferredCommands->add_deferred_commands() (0.167s)
Debug (bootstrap): Running command: i18n make-json (0.167s)
Success: Created 0 files.

Could you share the relevant translation file so we can test this ourselves?

@ole1986
make2json extracts only strings that are found in .js files. It uses the Reference comment of the .po files.
Therefore you have these references in your .po file.
For Example
#: example.js:9
msgid "domain_name"
msgstr "Domain name"

With the default command make-json extracts these values to the json file. if you want that the messages in your po file are not removed, use the --no-purge flag.
Hope that helps.

--no-purge parameter does not work as expected


collapse depth 1

Hi, is it possible to make the collapsed folders displayed when installing collapseDepth:1?

Hello, Thank you for using the vitepress-sidebar plugin.
In the current version, collapseDepth was also affecting the root content (table of content).
As a result, i've released version 1.9.0 which manages the root content with a separate option called rootGroupCollapsed and fixes collapseDepth to display correctly.
See: https://github.com/jooy2/vitepress-sidebar/blob/master/CHANGELOG.md
After upgrading to version 1.9.0, please check if the menu expands on the intended step.
If you also need to display folders where no files exist, please set the includeEmptyFolder option to true.
Thanks!

Thank you! Works great


Support invoice adjustments

This library should support invoice adjustments (for accepting overpayments and underpayments) but looks like this hasn't been implemented yet?

Thanks for your feedback, @mfb.  We've got this on our roadmap for upcoming versions of the library!

Great, thanks! Is there a pubilc roadmap online somewhere?

No, sorry @mfb.  Some of our planning for future products is super top secret and, therefore, black vans would show up outside my house if I shared them. ;)
Seriously though, we'd like to do a lot of improvements - this possibly being one but we are limited on resources at the moment.  It's on the to do list, however!

6 months later and nothing has been done.


[suggestion] add semilog y-axis plots

A suggestion- if you add semilog-y plots, that might be very helpful
For example, see https://www.ft.com/content/a26fbf7e-48f8-11ea-aeb3-955839e06441

great suggestion. I'll add it to my list. I tried to do that one point, but it did't work. I'm using the ReChart.org's widget. If you can tell me how to add it, I will do it right the way.

I think this would probably help: https://github.com/recharts/recharts/issues/575
Sorry I don't have much experience with JS-based plotting/charting, I've been using Tableau for years. Also I did a mini-writeup that you might find helpful for framing: https://docs.google.com/document/d/17YnG3RBeHqJSYT3YE1PzcfXb2E6YuAhrObmoVOKFwbY/edit#

this is helpful. let me try that.

https://imgur.com/a/iiX8RkW it works. now I need to figure out how to add a button in the chart to change it.

Awesome! One useful thing about semilog plots is ability to compare slopes- potentially think about adding a compare regions feature down the road?

just added the log scale. Thanks for the suggestion


Limit the number of map revisions to return at once

Fetching map revisions can be quite.... slow.
Let's help clients not time out.

Travis is failing due to impl/integration/env.go:182: not enough arguments in call to keyserver.New

Green again -- sorry for that bit of faff.


Removed additionalArguments while validation step

There are multiple parameters in additionalArguments which are not available for validate step. This leads to unnecessary warnings in the logs.
This PR will create separate validataeParameters and azDeployParameters for their respective steps ensuring the success of validate step.

@t-dedah can you please provide link to an issue where this was reported. I Need to understand the error better.

@bishal-pdMSFT Link to the issue comment https://github.com/Azure/arm-deploy/issues/71#issuecomment-977697831


adds support for raw key instead of hashed key

Fixes https://github.com/celestiaorg/smt/issues/40.
It adds a keySize field to all SMT related structs and uses it to access values in smt.values map.

Maybe we should add more checks on the keySize so that the treeHasher, SparseMerkleProof, SparseMerkleTree etc, have all the same key size.
Or, we can keep the keySize only inside the treeHasher and no checks will be required:
Pros
Simpler codebase
Cons
keySize is more related to the trees themselves than the hasher...
Also, other checks would be needed when doing operations like Get(key) checking if the key has the correct size.

Update:
The keySize is now part of the MapStore and it is being passed around as parameter wherever needed.

@adlerjohn Please take a look and let me know if this is what is needed so I continue fixing the other tests etc.
Currently, only the TestSparseMerkleTreeUpdateBasic is working

Codecov Report

Merging #64 (6445e18) into master (5f13c0f) will decrease coverage by 5.94%.
The diff coverage is 60.22%.

@@            Coverage Diff             @@
##           master      #64      +/-   ##
==========================================
- Coverage   85.62%   79.67%   -5.95%
==========================================
  Files           6        6
  Lines         466      492      +26
==========================================
- Hits          399      392       -7
- Misses         39       54      +15
- Partials       28       46      +18

Impacted Files
Coverage Δ

smt.go
73.12% <50.98%> (-7.67%)
:arrow_down:

deepsubtree.go
57.89% <58.33%> (-3.22%)
:arrow_down:

proofs.go
94.17% <68.75%> (-5.83%)
:arrow_down:

treehasher.go
100.00% <100.00%> (ø)

utils.go
100.00% <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 225e28d...6445e18. Read the comment docs.

Question: Should the ErrWrongKeySize be also a struct ? So the error message also contains the wrong key. Or no need for that ?

I left some comments in the code.
In general, I think that default behavior of the library should be preserved (enable users to use arbitrary keys), and raw keys support should be actually added (instead of replacing current way of operation).
This can be added as an Option, that changes the behavior of treeHasher.path method to no-op.

Thanks for the comments, will address them tomorrow.
For the functionality, I think the issue states replacing that behaviour, it's a breaking change, I believe.
Additionally, I think that the tree hasher should no longer be passed to these structures, as it is only hashing everything internally... What can be done is using a default hasher that can be changed using options, for example, but no longer be necessary.
What do you think ?

Just for clarification: I totally agree, that raw keys can be very useful, I understand the logic behind this change. But IMHO it's a low hanging fruit, to be able to use SMT with both raw (advanced use, turned on by option) and hashed keys (by default).
This way, library can be more general-purpose, more developer/user friendly.

@tzdybal sounds good to have both, yes. I can start digging into it as soon as I get the green light :+1:

Having the option for both modes isn't bad IMO. Having the option for raw keys is a must, beyond that extra features are gravy on top.

@adlerjohn should I get going with the implementation ? in // with the explorer stuff ?
Which one should be the default behaviour ? raw keys or hashed keys ?
Also, what do you think about these ?

Questions:

Should the ErrWrongKeySize be also a struct ? So the error message also contains the wrong key. Or no need for that ?
Should we update the fuzz test or we no longer need it ? since it will always be a constant size key... What about generating tons of constant sized strings ?
I think that the tree hasher should no longer be passed to these structures, as it is only hashing everything internally... What can be done is using a default hasher that can be changed using options, for example, but no longer be necessary.

Stopping work on this for now. Will pick it up later.


Tests fail with pandas==1.4.1

Tests in test_backed_sparse.py, test_hdf5_backing.py, test_inplace_subset.py, test_views.py fail with pandas 1.4

I can't reproduce locally, could you share some more about your environment?

Attached output from conda env export. Thanks.
environment.yml.txt

We’re far past pandas 1.4, so I’m closing this.


Package breaks if on windows (Powershell)

Hi, I happen to be using NPM over PowerShell, and the postscript install fails due to the '&&'.
Can you please fix this?
Cheers

Hello @shyamshi, thanks for filing an issue. Will be fixed soon in v1.3.7

Fix was merged and published -<EMAIL_ADDRESS>@shyamshi does it work ok for you?

This solution doesn't work on windows, I opened the issue #78

Added a review on Pull Request #67


Eagle build cleanup

While working on the RPi2 port, I found the Snapdragon build system to be quite confusing, so I decided to do some cleanup.
This PR removes the Toolchain-arm-linux-gnueabihf.cmake from cmake/toolchains and sets the build system to use it from cmake_hexagon (https://github.com/ATLFlight/cmake_hexagon/pull/1), as proposed by @mcharleb in https://github.com/PX4/Firmware/issues/4203
While not strictly required, this makes things a lot easier to understand, since "arm-linux-gnueabihf" encompasses any ARM build like Odroid / RPi / Eagle.
Another alternative, if you don't want this would be to rename the current one to "Toolchain-arm-linux-gnueabihf-linaro" and add separate ones like "Toolchain-arm-linux-gnueabihf-raspbian".

Related work to bring up RPi2 again : https://github.com/mhkabir/Firmware/tree/rpi2_bringup

@mcharleb @jywilson Can you please review?

@mhkabir I merged your changes to cmake_hexagon, and DriverFramework. This should now pass the CI test. @LorenzMeier how do we kick off the CI test again?

See #4467


Deepstream Analytics Source Code Review

The Application code at the source directory does not contain sufficient documentation in order to develop. Providing documentation on this program starting with the Code entry point .
Dod

[ ] deepstream_app_main.c
[ ] deepstream_nvdsanalytics_meta.cpp
[ ] deepstream_nvdsanalytics_test.cpp
[ ] initScript.sh
[ ] setup-peoplenet.sh

Blocker: The base application source code has less comments. A thorough review is needed to progress.

Created a fork of the Repo here. We shall be improving the documentation and making our changes here which can later be merged with the main repository if approved.

The code review analysis is given below:
Docker directory

The build.sh script is used to build a docker container with an Image called deepstream-nvdsanalytics-docker. As we run our application on the Jetson nano, the docker build uses the Dockerfile.Jetson for configuration
Dockerfile.Jetson consists of the necessary packages used to build the application source files, it uses CUDA version 10.2 and calls Makefile.ds to build the executable. The docker container starts with an entry point by using a initScript.sh present in the src file.
The run.sh script checks for a data mount and runs the docker container with the host(Jetson) network stack

SRC Directory
cfg-deepstream-default
cfg-deepstream-default directory consists of multiple txt files which are used for configuration.

bai_config_nvdsanalytics.txt: This file is used to set properties on the stream. It gives details on the type of filtering done. There are multiple streams present, only one ROI filtering stream is active which detects all classes. Th overcrowding stream is disabled. A line crossing stream is used, which allows us to set a line on the frame based on which some useful analysis can be performed. This would be crucial for over next sprints.
The direction detection stream present is for detection of the direction for class-id 0 (person), and it is disabled
bai_deepstream.txt: This file is used to configure the multiple settings for the application, the display, the GPU selected, the source and sink configurations. This file is essential for the next sprints as it will gives us the flexibility to change our source and sink which is part of the future work.

This file uses the tracker_config.yml for tracker properties and sets the config file (bai_config_nvdsanalytics.txt) for analytics which was analyzed earlier.

tracker_config.yml: This yaml file contains informations about the way the AI model works. The weights for necessary feature extraction computation, data association, state estimator is present in this file.

cfg-model-default

This directory consists of a file called labels.txt which gives a list of Objects which can be analyzed as part of this deepstream application. This file is used while performing stream filtering.

Makefile.ds

This makefile consists of the all the required sources. libraries, packages required to build the application "deepstream-app".

initScript.sh

This script checks for an input video in the /input directory, if its not found it copies a sample video and sets the ouput directory and runs the deepstream-app with necessary configurations for the application.

deepstream_app_main.c

This c file serves as the main application for the deepstream application being built. It has additional functions for handling meta-deta, performance metrics printing, interrupt handling.


Compilation error

Hello,
When I am doing "sbt compile" I am getting a compilation error as below,
[error] /home/krishna/my-applications/java/deepdive/src/main/scala/org/deepdive/datastore/PostgresDataStore.scala:23: object dbcp is not a member of package org.apache.commons
[error]       val del = new org.apache.commons.dbcp.DelegatingConnection(connection)
[error]                                        ^
[error] one error found
[error] (compile:compile) Compilation failed

Can you see what is going on? Thanks in advance.

This is fixed in v0.7.x branch as 49c0bd478d22fc26ae4913c0add94ca3577311d7.  Duplicate of #443.


Documented field security.istio.io/v1beta1 AuthorizationPolicy/spec.rules.from.source.host does not exist

Bug description
In the documentation https://istio.io/latest/docs/ops/configuration/security/security-policy-examples/ , there is an example
apiVersion: security.istio.io/v1beta1
kind: AuthorizationPolicy
metadata:
  name: jwt-per-host
  namespace: istio-system
spec:
  selector:
    matchLabels:
      istio: ingressgateway
  action: ALLOW
  rules:
  - from:
    - source:
        hosts: ["example.com", "*.example.com"]
        # the JWT token must have issuer with suffix<EMAIL_ADDRESS>        requestPrincipals<EMAIL_ADDRESS>    - source:
        hosts: [".another.org", "*.another.org"]
        # the JWT token must have issuer with suffix<EMAIL_ADDRESS>        requestPrincipals<EMAIL_ADDRESS>
Though, the hosts field does not seem to exist in the CRD. https://github.com/istio/istio/blob/d50c9dfa5181ff0926ef4173db9ccb44f5c18fa8/manifests/charts/base/crds/crd-all.gen.yaml#L5462
[X ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade

thanks for the report! it should be fixed by https://github.com/istio/istio.io/pull/9431.


AcceptRequests

Depends on #8

Feature is complete except handling of list updating after request is accepted

@icydusk your expertise with recycler views would be appreciated here

Waiting on bug fix for recycler view but is currently demoable

Need to check with TA if having the user manually update the view is viable because elastic search is horrible

@icydusk @JesseFarebro Thank you both for your bug fixing!


What is the prompt for the LLM to summarize?

Technically, we employ the lightweight image captioning model Tag2Text [59] for the finer scale, which describes videos at low fps in a frame-by-frame manner. These individual image captions are then synthesized into a comprehensive video description using a pretrained language model [60, 61].

We use a pretrained T5 for summarize without any prompt.

We use a pretrained T5 for summarize without any prompt.

What dataset did you use to train T5, or did you use the official T5-base directly?

We use the offical T5-summary without further finetuning, accessible at this URL.


[FEATURE] Allow setting of a relative endtime

This patch introduces the possibility to set a milliseconds
value that will be added to the current date for the endtime
value that is stored in the index.

Will create a new request with a dedicated branch.


[REQ]  Rename Mapping to Sensors and Sensor Groups

I translated the language files into German. It struck me that the term mapping is very unwieldy.
It is easier for a user to understand that these are sensors or sensor groups which can subsequently be assigned to individual zones.
I would like to suggest replacing the term mapping with sensors and sensor groups.

Happy with any term that makes sense, but not sure I agree with sensor groups. That is not what this is. This is a map of where to find what value. So, a mapping. If we can come up with another short word for this, I am all for it but sensor groups it is not

What's about sensors and sensor set?
Set (abstract data type)

Maybe. @dlindnegm care to weigh in?

Something like this:

How about Connections instead?

I would consider OWM no different than my Ambient Weather Station.  Both are Integrations in HA, both report sensor data (rain, wind, etc) into HA as sensors.  Both get their data from physical sensors in the field. I can mix and match those sensors into a group, and Smart Irrigation uses that group to determine evapotranspiration rate.  And a static value would be considered a virtual sensor in HA.  So we are mapping/grouping/configuring sensors for use by a zone.

I would like to sugest again. sensor set.

OK, let's go with sensor group instead of mapping. I don't like sensor set.

In the english and german language files I changed mapping to sensor group(s) but no  literals.


feature: header graphics

Did you check the docs?

[X] I have read all the snacks.nvim docs

Is your feature request related to a problem? Please describe.
I added header = [[ "foo"]] to my header sections but it only ever renders the default Neovim text.
Describe the solution you'd like
I was wondering if we could use any old art like the alpha.lua plugin uses.
Describe alternatives you've considered
Have not considered anything. just curious as to how one might override the default.
Additional context
[[                                                                       ]],
[[                                                                     ]],
[[       ████ ██████           █████      ██                     ]],
[[      ███████████             █████                             ]],
[[      █████████ ███████████████████ ███   ███████████   ]],
[[     █████████  ███    █████████████ █████ ██████████████   ]],
[[    █████████ ██████████ █████████ █████ █████ ████ █████   ]],
[[  ███████████ ███    ███ █████████ █████ █████ ████ █████  ]],
[[ ██████  █████████████████████ ████ █████ █████ ████ ██████ ]],
[[                                                                       ]],

Yes of course you can. Please check the docs or ask in discussions.

https://github.com/folke/snacks.nvim/discussions/341 i found an answer to this question in this discussion post


Update aws-java-sdk-core to 1.12.515

About this PR
📦 Updates com.amazonaws:aws-java-sdk-core from 1.12.459 to 1.12.515
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.amazonaws", artifactId = "aws-java-sdk-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.amazonaws", artifactId = "aws-java-sdk-core" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #586.


⚠ ClamAV has degraded performance

In dd80590, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 464 ms

Resolved: ClamAV performance has improved in a34e3b2.


analog-input-every-n-samples.py can cancel acquisition before reading all samples

If you turn the SampClk rate up high enough (15000-20000 for me) the read_data loop often gets cancelled before acquiring the last batch of samples.
I was hoping that grpc queueing would be able to preserve ordering:

Events fired in order
messages enqueued on server in order
messages sent in order
messages received and enqueued in order
messages not necessarily processed in order BUT cancel enqueued on same queue as above
data processed before cancel

But somewhere that's not working.

I have a prototype that seems to work with the code snippet below.
Basically there's a unary-unary API that allows creating a named stream (tied to the Task lifetime) and registering for events on that stream. Then you read both events from the same stream. This allows us to preserve ordering. And separating out a unary-unary API for create/register also gets rid of the wait_for_initial_metadata.
I'll work with @harsha-bhushan on whether we like this API and how we want to prioritize this. This is a fairly different implementation, so we'll likely have some of the same problems getting all of the synchronization ironed out.
Notice the slightly different method/message names (this is  a new API on the existing service):
service NiDAQmx {
[...]
  rpc CreateEventStream(CreateEventStreamRequest) returns (CreateEventStreamResponse);
  rpc RegisterDoneEventStream(RegisterDoneEventStreamRequest) returns (RegisterDoneEventStreamResponse);
  rpc RegisterEveryNSamplesEventStream(RegisterEveryNSamplesEventStreamRequest) returns (RegisterEveryNSamplesEventStreamResponse);
  rpc ReadEventStream(ReadEventStreamRequest) returns (stream ReadEventStreamResponse);
[...]
}
message ReadEventStreamResponse {
  oneof event_data {
    DoneResponse done_response = 1;
    EveryNSamplesResponse every_n_samples_response = 2;
  }
}

Sample client code:

await raise_if_error_async(
    client.CreateEventStream(
        nidaqmx_types.CreateEventStreamRequest(
            task=task, stream_name="STREAM"
        )
    )
)

await raise_if_error_async(
    client.RegisterEveryNSamplesEventStream(
        nidaqmx_types.RegisterEveryNSamplesEventStreamRequest(
            task=task,
            stream_name="STREAM",
            n_samples=100,
            every_n_samples_event_type=nidaqmx_types.EVERY_N_SAMPLES_EVENT_TYPE_ACQUIRED_INTO_BUFFER,
        )
    )
)

await raise_if_error_async(
    client.RegisterDoneEventStream(
        nidaqmx_types.RegisterDoneEventStreamRequest(
            task=task, stream_name="STREAM"
        )
    )
)

await raise_if_error_async(
    client.StartTask(nidaqmx_types.StartTaskRequest(task=task))
)

event_stream = client.ReadEventStream(
    nidaqmx_types.ReadEventStreamRequest(task=task, stream_name="STREAM")
)

async def read_data():
    read_count = 0
    event_stream_response: nidaqmx_types.ReadEventStreamResponse
    async for event_stream_response in event_stream:
        which_oneof = event_stream_response.WhichOneof("event_data")
        if which_oneof == "every_n_samples_response":
            every_n_samples_response = (
                event_stream_response.every_n_samples_response
            )
            await raise_if_error(every_n_samples_response)
            read_response: nidaqmx_types.ReadAnalogF64Response = await raise_if_error_async(
                client.ReadAnalogF64(
                    nidaqmx_types.ReadAnalogF64Request(
                        task=task,
                        num_samps_per_chan=100,
                        fill_mode=nidaqmx_types.GroupBy.GROUP_BY_GROUP_BY_CHANNEL,
                        array_size_in_samps=number_of_channels * 100,
                    )
                )
            )
            print("Read Data:", read_response.read_array[:10])
            read_count = read_count + 1
            print(read_count)
        elif which_oneof == "done_response":
            done_response = event_stream_response.done_response
            event_stream.cancel()
            await raise_if_error(done_response)

await read_data()


API listing UX

Suggestion for layout in API listing / catalogue

This is actualyl what the front page should look like and in that case change the topic to something like "APIKA - avoimien rajapintojen hallinta"

This UI seems to imply several features, which may not yet be in our backlog. Specifically, I notice the following features that need planning:

API Search
API Categorization
API Metadata

Description

API Sandbox

We agreed to use Swagger UI for sandboxing
We will need to continue work on the Swagger UI documentation upload feature

@baijat, lets create this as a 'meta' feature, so that we can track the progress of all related components.

@brylie I agree with you that is not a trivial task. It has quite a lot of items that are either captured in the backlog, but not yet implemented, or are not even planned.

Also, it looks like the Liityntakatalogi is powered by CKAN. Since CKAN is open-source, we can either borrow code or provide an integration via its API.

@kyyberi @brylie @bajiat @preriasusi This is a significant change to UI. Can we split to different milestones like APIKA1, APIKA2...based on the realistic estimation?

@elnzv will you please also help us understand the design changes? E.g. how the new design elements could be added or factored in to the existing front-end design.

Btw, with sandbox at this point I refer to live swagger documentation.

@kyyberi "This is actualyl what the front page" Can you clarify front page? Is the proposed view available when user is logged in or not logged in? If not logged in, then sandboxing has to happen without API key. Also, as far as I have understood testing in Swagger always makes a real request so it not sandboxing in the true sense.
@ccsr (@kyyberi @brylie @preriasusi) What are the milestones you had in mind? Splitting current APIKA project into milestones?

Relatedly, CKAN are testing packaging for Ubuntu 14.04 LTS. May we spin up a VM and help test the packaging?

Perhaps th term sandbox is not the right one. Anything with what you can fool around with the api, it can use dummy data or whatever.

For you to know I met swagger people at apistrat and I'm organizing webinar for the Finnish developer community about the latest tools around swagger. It might interest you too.

@brylie, need more details on this page. Let's plan this and discuss it and then I will provide my ideas and thoughts.

@kyyberi Currently we are only using Swagger for testing APIs and the API calls Swagger makes are real calls direct to the API. And we are working on rerouting them to our proxy. Other than that, we don't have any sandboxing functionality and have no such plans in APIKA timeframe.

Well, replace the word "sandbox" to "live docs" or something :) I would not use "swagger" as other options should occur in the future.

Ah, nice. OK, we will use generic language. Swagger UI is a good API UI for the time being, but we are definitely open to new options. :+1:

I was browsing the web and it lead to thought or requirement that when we have listing of APIs in the frontpage, we need to offer clear sing of APIs which do not require auth or API-key. Those so called free APIs can be utilized without registering to APIKA. That user registration to get API-key is a barrier for some open data enthusiasts. https://opendata.stackexchange.com/questions/774/should-data-apis-require-registration-and-api-keys

Great suggestion. Lets create a new enhancement request based on this idea. That way we can discuss and track its implementation.
On 29 November 2015 20:38:58 EET, Jarkko Moilanen<EMAIL_ADDRESS>wrote:

I was browsing the web and it lead to thought or requirement that when
we have listing of APIs in the frontpage, we need to offer clear sing
of APIs which do not require auth or API-key. Those so called free APIs
can be utilized without registering to APIKA. That user registration to
get API-key is a barrier for some open data enthusiasts.
https://opendata.stackexchange.com/questions/774/should-data-apis-require-registration-and-api-keys

Reply to this email directly or view it on GitHub:
https://github.com/apinf/api-umbrella-dashboard/issues/629#issuecomment-160446434

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Stumbled upon this pretty good idea of providing for ways to get started. This could be under the title of frontpage

Added also featured apps, which refers to application profile containing information of used APIs, description, links to shared Swagger specs etc, creator name and contact. IT's s show window for developers.

Closing, the most relevant front page modifications were implemented in #756 and have been deployed to Apika.


Stop the block locator at the reorg limit

Don't request blocks that are past the reorg limit, because we won't accept forks
beyond that limit.
This change reduces the number of duplicate blocks, particularly from low-height side
chains.

See #819 and #835 for analysis and alternative fixes.


msodbcsql for Debian 11 (bullseye)

The stable release of Debian 11 has been out for a while, but there is still no msodbcsql package available?
Any ETA on that?
https://packages.microsoft.com/debian/11/prod/pool/main/m/

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

ID: 0fc3da20-7ab2-d20f-4d29-4664d3183b57
Version Independent ID: 986d25d9-5d2e-5154-39ea-3b683faf2264
Content: Install the Microsoft ODBC driver for SQL Server (Linux) - ODBC Driver for SQL Server
Content Source: docs/connect/odbc/linux-mac/installing-the-microsoft-odbc-driver-for-sql-server.md
Product: sql
Technology: connectivity
GitHub Login: @David-Engel
Microsoft Alias: v-daenge

We can't make any public promises about future releases, but if you look at the release notes for past releases, you can see that support for new Debian/Ubuntu/Red Hat/SUSE/Apple OS versions have historically been added to the ODBC driver GA release following the GA release of those OS versions. You can also see the historical 6-month ODBC GA release cadence of Jan/July.
Regards,
David
#please-close


python312Packages.vxi11: drop nose dependency

Description of changes
part of:

https://github.com/NixOS/nixpkgs/issues/326513
Thanks to @matt-loft work (https://github.com/python-ivi/python-vxi11/pull/47), this was a breathe

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

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

[X] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

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

4 packages built:

python311Packages.vxi11
python311Packages.vxi11.dist
python312Packages.vxi11
python312Packages.vxi11.dist


Related process

Coverage increased (+0.08%) to 82.289% when pulling ccaebeef289d32bf7220cae6c836fb20b694affc on bdmbdsm:related-process into a58ef2796cf7500a96f9b237d9bbbd33ce18cb07 on openprocurement:master.

Coverage increased (+0.08%) to 82.289% when pulling ccaebeef289d32bf7220cae6c836fb20b694affc on bdmbdsm:related-process into a58ef2796cf7500a96f9b237d9bbbd33ce18cb07 on openprocurement:master.


Project metadata update

Rename the following fields, these labels could be non exclusive (we could have a project with both green and brown colors).
User terms

Sequestration type → Project type

forest
mangrove
agroforestry
sustainable agriculture

Sequestration color → Project color

blue
green
brown

Sequestration category → Project category

regeneration
conservation

Business terms

Sequestration type → NbS type

reforestation
mangrove
agroforestry
sustainable agriculture

Sequestration color → NbS color

blue
green
brown
soil

Sequestration category → NbS category

removal
avoidance
mixed

It is not possible to have multi values of a single traits based on OpenSea standards I guess.
So 3 scenarios to manage the non exclusive property that we expect:

Create mix colors and categories w/o modifying trait names:

Project color: Green - Brown
Project type: Regeneration - Conservation

Change trait names without touching trait values (I guess it messes up the marketplaces filter feature)

Project color 1 : Green
Project color 2 : Brown
Project type 1 : Regeneration
Project type 2 : Conservation

Remove these properties from metadata and insert it as an information in the token image, doing this will make the filter features impossible to process on these properties.

URI have been updated:

0x05a5edd84bdac11540f411b91acd1ade068f1b77c3047979c58fef3de39a8db2
0x0245c415c2e4be8ca181b438dfdd59f783fa36d586bc85d023be389d63da3379