Implement space deletion job endpoint

Is there a related GitHub Issue?
#2604
What is this change about?
Return the status of space deletion based on the underlying CFSpace resource state.
Does this PR introduce a breaking change?
No.
Acceptance Steps
See issue.
Tag your pair, your PM, and/or team
Paired with @acosta11

I'm concerned about the new dynamic client here. If you're concerned about caching, I believe this is just another non-caching client, as the privileged and user clients here are already not using a cache.

We are pretty sure that both clients are actually uncached. We tried to put GetOrg back in and see if we could make cf delete-org by running in a loop, but without success.
Maybe the condition you caught is not due to caching but just general etcd eventual consistency? In that case maybe we should do retries?
I would avoid introducing a new client unless we can prove that it makes a difference.

Thank you both for taking a look at this. 🙏

I believe this is just another non-caching client, as the privileged and user clients here are already not using a cache.

That was our understanding as well.

Maybe the condition you caught is not due to caching but just general etcd eventual consistency? In that case maybe we should do retries?

The thing that led us to believe that the client used by the API was using a cache was that @matt-royal consistently encountered an issue when testing on a KinD cluster on his M1 Mac where the first GET call to /v3/jobs that the CF CLI makes immediately after the delete request was returning a 404 error which only happens if the deletion timestamp of the specified org is empty. I was not able to reproduce this on my i9 Mac, but @clintyoshimura and I were able to reproduce this on an AKS cluster. I just deployed from the main branch onto a KinD cluster and was finally able to reproduce it locally:
$ cf delete-org o -v; kubectl get -n cf cforg/cf-org-f00abc7c-e09b-4ee6-a9e5-891859f79f76 -o yaml
...
Deleting org o as cf-admin...
REQUEST: [2023-06-30T13:58:24-07:00]
GET /v3/organizations?names=o HTTP/1.1
Host: localhost
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/json
User-Agent: cf/8.7.1+9c81242.2023-06-15 (go1.20.5; amd64 darwin)
[application/json Content Hidden]

RESPONSE: [2023-06-30T13:58:24-07:00]
HTTP/1.1 200 OK
Content-Type: application/json
Date: Fri, 30 Jun 2023 20:58:24 GMT
Server: envoy
Vary: Accept-Encoding
X-Correlation-Id: 81578357-659d-44ff-a2db-aedf9a12948f
X-Envoy-Upstream-Service-Time: 9
{
  "pagination": {
    "first": {
      "href": "https://localhost/v3/organizations?names=o"
    },
    "last": {
      "href": "https://localhost/v3/organizations?names=o"
    },
    "next": null,
    "previous": null,
    "total_pages": 1,
    "total_results": 1
  },
  "resources": [
    {
      "created_at": "2023-06-30T20:57:36Z",
      "guid": "cf-org-f00abc7c-e09b-4ee6-a9e5-891859f79f76",
      "links": {
        "self": {
          "href": "https://localhost/v3/organizations/cf-org-f00abc7c-e09b-4ee6-a9e5-891859f79f76"
        }
      },
      "metadata": {
        "annotations": {
          "korifi.cloudfoundry.org/creation-version": "v0.7.2-271-ga6fff152"
        },
        "labels": {}
      },
      "name": "o",
      "relationships": {},
      "suspended": false,
      "updated_at": "2023-06-30T20:57:36Z"
    }
  ]
}

REQUEST: [2023-06-30T13:58:24-07:00]
DELETE /v3/organizations/cf-org-f00abc7c-e09b-4ee6-a9e5-891859f79f76 HTTP/1.1
Host: localhost
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/json
User-Agent: cf/8.7.1+9c81242.2023-06-15 (go1.20.5; amd64 darwin)
[application/json Content Hidden]

RESPONSE: [2023-06-30T13:58:24-07:00]
HTTP/1.1 202 Accepted
Content-Length: 0
Date: Fri, 30 Jun 2023 20:58:24 GMT
Location: https://localhost/v3/jobs/org.delete~cf-org-f00abc7c-e09b-4ee6-a9e5-891859f79f76
Server: envoy
X-Correlation-Id: 0b708888-d59e-402e-a072-07511a855f52
X-Envoy-Upstream-Service-Time: 11

REQUEST: [2023-06-30T13:58:24-07:00]
GET /v3/jobs/org.delete~cf-org-f00abc7c-e09b-4ee6-a9e5-891859f79f76 HTTP/1.1
Host: localhost
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/json
User-Agent: cf/8.7.1+9c81242.2023-06-15 (go1.20.5; amd64 darwin)
[application/json Content Hidden]

RESPONSE: [2023-06-30T13:58:24-07:00]
HTTP/1.1 404 Not Found
Content-Type: application/json
Date: Fri, 30 Jun 2023 20:58:24 GMT
Server: envoy
Vary: Accept-Encoding
X-Correlation-Id: 6ae99bec-1e6a-47c1-975f-8c86eb0cd0b9
X-Envoy-Upstream-Service-Time: 9
{
  "errors": [
    {
      "code": 10010,
      "detail": "Job not found. Ensure it exists and you have access to it.",
      "title": "CF-ResourceNotFound"
    }
  ]
}

Job not found. Ensure it exists and you have access to it.
FAILED

apiVersion: korifi.cloudfoundry.org/v1alpha1
kind: CFOrg
metadata:
  annotations:
    korifi.cloudfoundry.org/creation-version: v0.7.2-271-ga6fff152
  creationTimestamp: "2023-06-30T20:57:36Z"
  deletionGracePeriodSeconds: 0
  deletionTimestamp: "2023-06-30T20:58:24Z"
  finalizers:
  - cfOrg.korifi.cloudfoundry.org
  generation: 2
  name: cf-org-f00abc7c-e09b-4ee6-a9e5-891859f79f76
  namespace: cf
  resourceVersion: "2297"
  uid: ff51f747-dc2c-4760-bbfb-902e700c4c88
spec:
  displayName: o
status:
  conditions:
  - lastTransitionTime: "2023-06-30T20:57:36Z"
    message: ""
    observedGeneration: 1
    reason: Ready
    status: "True"
    type: Ready
  guid: cf-org-f00abc7c-e09b-4ee6-a9e5-891859f79f76
  observedGeneration: 2

I tried again with a new org with a space and an app pushed to check the API logs. When I deleted the org, I received the same output as above, and saw this in the logs:
{"severity":"INFO","timestamp":"2023-06-30T21:06:05.457200276Z","logger":"handlers.job.get.handleOrgDelete","caller":"errors/errors.go:33","message":"org not marked for deletion","correlation-id":"c48fbf91-69c5-48f0-a4b6-4c94312c8947","OrgGUID":"cf-org-9579b6a8-d39d-427e-a90e-0d3ac1
0f0095","reason":"job \"org.delete~cf-org-9579b6a8-d39d-427e-a90e-0d3ac10f0095\" not found"}

This could be an etcd eventual consistency problem, but it seemed to be happening too consistently for that.
The other issue I ran into while testing the org deletion job was that the API would return a "COMPLETED" status in the response to (normally) the third call, which would make the CLI stop polling and print OK. However, when we retrieved a list of CFOrg resources with kubectl or watched it in another window with k9s, we could still see the org that had been deleted for about a minute afterward. Switching to the dynamic user client resulted in the /v3/jobs endpoint correctly returning a "PROCESSING" status until after the CFOrg resource disappeared from k9s. The strange was that space deletion did not act the same way. Instead, it would return a "PROCESSING" status until the space disappeared from k9s and then return the "COMPLETED" status.

I would avoid introducing a new client unless we can prove that it makes a difference.

I agree that adding the new client feels unnecessary. The strange thing is that the new dynamic client seems to eliminate both of the behaviours I described above when testing on the AKS cluster. I just tried an alternative approach, which is to update the org's delete handler to wait for up to 5 seconds until it can confirm that the deletion timestamp is set. This appears to solve the problem of the first call to /v3/jobs returning a 404 error but does not solve the problem of the third call returning a "COMPLETED" status even though the org is still visible in k9s.

This appears to solve the problem of the first call to /v3/jobs returning a 404 error but does not solve the problem of the third call returning a "COMPLETED" status even though the org is still visible in k9s.

I wouldn't worry about resources still visible in k9s: there's no cache issue that can make things invisible even if they still exist, only make things visible even if they don't exist anymore, so it's probably due to k9s's cache.
If we know for a fact that both clients are uncached, then we shouldn't be calling only one of the two "uncached". We should understand why the dynamic client succeeds where the regular client fails, but it might just be because it's slower. If this is the case, then I'd just add some retries and get rid of the dynamic client altogether.

Julian and I figured out what was causing the /v3/jobs endpoint to return "COMPLETED" early; it corresponded to the deletion of the role binding in the namespace. We ended up creating a new GetOrgForDeletion function in the repository to allow the job handler to wait for the org to actually be deleted.
We also decided to remove the new user client and go with the retry loop to wait for the deletion timestamp to be set in the org/space.

I just confirmed that both cf delete-space and cf delete-org work as expected on this PR branch


Codemod

This is great, but it feels silly to have both libs in production. If someone has some free time and wants to write a jscodeshift codemod for this, that'd be amazing.

Hey! I'm not quite sure what you mean. Like, what exactly would you want to have transformed by a codemod?

closing due to inactivity


Moving all versions into the parent project

Per @hansjoachim's recommendation to move all dependency versions into the parent dependencyManagement section. In core, I've kept the test dependencies which are used for guinnea pigs at their versions in the core pom - should we consider making a separate project for these dependencies?

I'm not sure what to do with the "test-dependencies". It has been mentioned a couple of times, but @jeremylong has a suggestion towards the end of #252 which might work.


feat(AMBER-551): Update Artwork information panel (Mobile)

This PR resolves []
Description
As part of the private artworks project, we want to ensure that collectors know which artworks are private. The collector facing terminology that we are using is exclusive access and we want to update this across artsy wherever a private artwork is being viewed.
We want to update this for the artwork panel which is used across the website. An example being on the saved artworks page, or the recently viewed Rail.

PR Checklist

[ ] I have tested my changes on iOS and Android.
[ ] I hid my changes behind a [feature flag], or they don't need one.
[ ] I have included screenshots or videos, or I have not changed the UI.
[ ] I have added tests, or my changes don't require any.
[ ] I added an [app state migration], or my changes do not require one.
[ ] I have documented any follow-up work that this PR will require, or it does not require any.
[ ] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates
#nochangelog

Warnings

:warning:

✅ No changelog changes

  Generated by :no_entry_sign: dangerJS against a4a99b743e7339c73920e793e1da539e93fdcc99

@JanaeHijaz  - unless you have any comments feel free to hit the 🍏 since yr assigned!


can't use task: translate_lev

Hello,
I'm following the recipe for Levenshtein-Transformer (https://github.com/pytorch/fairseq/tree/master/examples/nonautoregressive_translation)
But it can't work with -
--task translation_lev
--criterion nat_loss
Please help!
Thanks!

solved


Fix RocksDB core

Codecov Report

Merging #197 into release-rc2 will decrease coverage by 0.09%.
The diff coverage is 0.00%.

@@                Coverage Diff                @@
##             release-rc2     #197      +/-   ##
=================================================
- Coverage          29.00%   28.90%   -0.10%
  Complexity           329      329
=================================================
  Files                110      110
  Lines               3499     3511      +12
  Branches             246      246
=================================================
  Hits                1015     1015
- Misses              2404     2416      +12
  Partials              80       80

Impacted Files
Coverage Δ
Complexity Δ

...ank/wecross/storage/RocksDBBlockHeaderStorage.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)


Update survey module and notebook

Codecov Report

Merging #221 (1a985c7) into master (7eb214d) will decrease coverage by 0.07%.
The diff coverage is 38.46%.

@@            Coverage Diff             @@
##           master     #221      +/-   ##
==========================================
- Coverage   85.16%   85.08%   -0.08%
==========================================
  Files          43       43
  Lines        2724     2723       -1
==========================================
- Hits         2320     2317       -3
- Misses        404      406       +2

Impacted Files
Coverage Δ

niimpy/preprocessing/tracker.py
86.53% <ø> (ø)

tests/preprocessing/test_survey.py
100.00% <ø> (ø)

niimpy/preprocessing/survey.py
24.21% <38.46%> (-2.11%)
:arrow_down:

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


Adds scala-tutorial Library

DO NOT MERGE YET
Fixes #603 and #616

Hi @julienrf, I've deployed in this stage env the new library. Everything looks good, however, I can see how in the first chapter, in the second exercise, the expected types are interchanged:
https://scala-exercises-pr-617.herokuapp.com/scala_tutorial/terms_and_types
Please, correct me if I'm missing something. Thanks.

Oh, good catch! Indeed, it seems that I can not use res1 before using res0, here: https://github.com/scala-exercises/exercises-scalatutorial/blob/master/src/main/scala/scalatutorial/sections/TermsAndTypes.scala#L123-L124
It might be an issue of scala-exercise?
Anyway, I’ll fix the exercise definition by swapping the arguments order.

So, I went through all the other exercises and they are fine, excepted that we can not run an exercise that takes no parameters. I have an exercise that does not take parameters (ie. where users have nothing to fill in) in order to show the output of the compilation. Also, sometimes I don’t end a section with an exercise, so I put a dummy function instead, but this function is not runnable from the UI.
Do you think it would be possible to make these no-args functions runnable from the UI?

BTW, I just pushed this commit to the scalatutorial repo.

It might be possible if we modify the UI, activating the Run button for those exercises that contains code but don't have any exercise.

@juanpedromoreno I’m not sure it will be enough: these disabled exercises must also not be taken into account by the progress bar:

Right @julienrf That's an issue.

Closing and creating a new PR in order to re-deploy Heroku.
https://github.com/scala-exercises/scala-exercises/pull/618

I've submitted the issue: https://github.com/scala-exercises/scala-exercises/issues/619


Migrating routeless apps to Diego doesn't disable health-check

As described in https://github.com/cloudfoundry/diego-design-notes/blob/master/migrating-to-diego.md#running-route-less-applications-such-as-workers-and-schedulers, a DEA --no-route is analogous to a Diego --no-route --set-health-check none
cf-migrate-apps diego should disable the health check on routeless DEA applications
Thanks,
-David

@socalnic @ematpl Wdyt? Kinda relates to the discussion we had a while back about whether cf push --no-route should imply health-check none.

/cc @SocalNick

If the plugin can properly determine whether or not to add --set-health-check none, would make it more useful.

My principal concern would be that there could be a stopped app that when started and routable should have a port-based health-check, but when migrated doesn't happen to have a route mapped to it right then (maybe it's the inactive half of a blue-green deploy pair, and the blue-green deploy technique is being parsimonious with route mappings). The health-check inference on cf push has a similar issue. An appropriate mitigation for that concern might be for the migration commands to report warnings about all apps with their health-checks set to none, so that the migrator can more easily discover the subset of apps for which to verify that this is the correct health-check type.
Also, can we use the clearer process instead of none for this?
Thanks,
Eric

Hi all, thanks for considering this.
I can offer that as a user, I wouldn't have had any problem with it dropping me into an interactive (yes/no/yes-to-all/no-to-all) mode to quickly set the appropriate health-checks per app/space. It's essentially what I had to end up doing.
Thanks,
-David

On Oct 7, 2016, at 20:37, Eric Malm<EMAIL_ADDRESS>wrote:
My principal concern would be that there could be a stopped app that when started and routable should have a port-based health-check, but when migrated doesn't happen to have a route mapped to it right then (maybe it's the inactive half of a blue-green deploy pair, and the blue-green deploy technique is being parsimonious with route mappings). The health-check inference on cf push has a similar issue. An appropriate mitigation for that concern might be for the migration commands to report warnings about all apps with their health-checks set to none, so that the migrator can more easily discover the subset of apps for which to verify that this is the correct health-check type.
Also, can we use the clearer process instead of none for this?
Thanks,
Eric
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

We explored interactive prompts when previously enhancing this plugin, but gave up because of its technical complexity (the plugin itself runs in a separate process).  We'll need a lot more demand before we'd want to revisit that.
So it seems the safest solution would be to display a warning for each app being migrated to Diego that has no mapped routes that health-check-type is set to none.
(Will look at the stories to support process for the cf CLI and app manifest separately):
WARNING: Assuming process health check (type "none") for app with no mapped routes; use `cf set-health-check` to change this: App my-app to Diego/DEA in space myspace / org myorg as diesk

@dmarmugi We have released v1.2.3 of the plugin with the warning as described above.
Thanks for bringing it up!


[DOCU-2400] Release: Gateway <IP_ADDRESS>

Summary
Changelog and any doc updates for the Gateway <IP_ADDRESS> patch release.
⚠ Important: ⚠  We have two potential issues here, both listed under "Features" in the changelog:

I couldn't find the AWS Lambda plugin update in the kong-ee next/2.8.x.x branch. The change was originally made in open-source Kong and was merged there, with plans to GA in 3.0. Is this change actually going into <IP_ADDRESS>? I see that Fel's last question on the ticket was also not answered.

If the answer is yes, it goes into <IP_ADDRESS>, we will need to make sure the changes in this doc PR get pulled into main:  https://github.com/Kong/docs.konghq.com/pull/3996

GCP integration support for the secrets manager: this is undocumented, and first we are aware of it. It will need to be added to the secrets manager doc:  https://docs.konghq.com/gateway/latest/plan-and-deploy/security/secrets-management/backends/

Reason
Upcoming patch release.
https://konghq.atlassian.net/browse/DOCU-2400
Testing
https://deploy-preview-4142--kongdocs.netlify.app/gateway/changelog/
I set a release date, but need to verify that this is actually when the release comes out.

The GCP work will be addressed in this PR:
https://github.com/Kong/docs.konghq.com/pull/4144


Can't you just provide a powershell that does all these settings?

Instead of making every admin go through a few 100 settings to make on the master VHD provide a PowerShell script that just does this, or provide a VHD that we can deploy with these settings configured.

Documentdetails
⚠ Dit gedeelte niet bewerken. Het is vereist om problemen te koppelen tussen docs.microsoft.com en GitHub.

ID: a83e1751-011c-9add-2c0a-63159fef97da
Version Independent ID: 119b5192-3775-f71e-579d-9ead105ed1b0
Content: Recommended configuration for VDI desktops
Content Source: WindowsServerDocs/remote/remote-desktop-services/rds-vdi-recommendations.md
Product: windows-server-threshold
GitHub Login: @jaimeo
Microsoft Alias: elizapo

It's not clear in what context you are using VHD. Are you talking about creating a VHD(x) for a virtual machine, or are you talking about boot to VHD or are you using VHD as an iSCSI target?  Or did you want to load the VHD into the local filestore?
And I am not sure that you mean by 100 settings. If you look at the cmdlets, there are only 10 cmdlets in the Hyper-V module which cover the core usage of VHDs in Windows and Hyper-V VMs.
Storage can get pretty complex, particularly in a virtualised environment where your storage and compute capability do not live on the same physical host.
Seems to me that if I had an uber script that could create a master VHD, it would have hundreds of parameters to enable those 100 settings to be overridden or specified differently.  The '100 settings' are all there for a reason. And while I've not counted, I am not sure 100 is an accurate number. But no matter how many., each setting allows you to manage the VHD just the way you need to - in your environment.
For an example of how I've used these cmdlets to deploy VMs and VHDXs inside, see my Reskit Build Lab scripts, over on: https://github.com/doctordns/ReskitBuildScripts

In the Group Policy Settings section you are advising:
Click Recovery, and then double-click Allow restore of system to default state. Select the radio button for Enabled, and then click the OK button to save.
Is this a typo? I'm thinking that it is not likely for a VDI user to reset the VDI in the Default Configuration state, isn't it?

#please-close


Rotate scene about camera Z

Would it be possible to use a two finger twist gesture to rotate along the camera view z, like the "pinch + rotate" example here http://alloyteam.github.io/AlloyFinger/. So in a plane parallel to the screen plane, and the rotate in x,y about z only.

Actually, the center of rotation would probably be the center between your two fingers, or the last rotation center point if no point was hit on an object between your two fingers.

I dig it.
Keep this up, we get the full Google Maps touch action going.

Does this work with an Orthographic camera?


fix: count task database apps bind name

Codecov Report

Merging #767 (0b7e238) into dev (d0ff10b) will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##              dev     #767      +/-   ##
==========================================
- Coverage   41.31%   41.31%   -0.01%
==========================================
  Files         341      341
  Lines       25448    25449       +1
==========================================
  Hits        10513    10513
- Misses      14935    14936       +1

Flag
Coverage Δ

unittests
41.31% <0.00%> (-0.01%)
:arrow_down:

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

Impacted Files
Coverage Δ

dbaas/notification/tasks.py
25.71% <0.00%> (-0.02%)
:arrow_down:

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


[FileNotFoundError] While more than 60 train data lines

When I run train.py, it only works when I have less than 60 lines in my training txt but when it is more it gives some random line:
FileNotFoundError: [Errno 2] No such file or directory: 'audio/22.wav'
But that audio/22.wav was no problem when there were less lines in the training txt
What is this mystery? Thanks beforehand.

I have encountered this an error similar to this before, it keep reporting a file in one exactly line in filelist  is causing problem. It take me a whole morning debug, found out nothing, so I go out for lunch, and when I return, it suddenly worked. Really confusing.

I've imitated exactly how the default LJ Speech dataset folders sits: ljs_dataset_folder/wavs structure (folder names, file names... everything)
Now it works, but I don't know why.


[requirements/] Add pytest and decorator to requirements.txt

📌 Checklist before creating the PR

[x] I have created an issue for this PR for traceability
[x] The title follows the standard format: [doc/gemini/tensor/...]: A concise description
[] I have added relevant tags if possible for us to better distinguish different PRs

🚨 Issue number

Link this PR to your issue with words like fixed to automatically close the linked issue upon merge
e.g. fixed #1234, closed #1234, resolved #1234

fixed https://github.com/hpcaitech/ColossalAI/issues/3962
📝 What does this PR do?

Summarize your work here.
if you have any plots/diagrams/screenshots/tables, please attach them here.

Add pytest and decorator to requirements.txt
💥 Checklist before requesting a review

[x] I have linked my PR to an issue (instruction)
[x] My issue clearly describes the problem/feature/proposal, with diagrams/charts/table/code if possible
[x] I have performed a self-review of my code
[ ] I have added thorough tests.
[ ] I have added docstrings for all the functions/methods I implemented

⭐ Do you enjoy contributing to Colossal-AI?

[ ] 🌝 Yes, I do.
[ ] 🌚 No, I don't.

Tell us more if you don't enjoy contributing to Colossal-AI.

hi, let me try to reproduce this bug, ideally we should have pytest for this library, pytest is only needed when running testing.

Hi @MEllis-github , I think decorator will be installed as a dependency of fabric. May I know which version of fabric you have installed?

As for the pytest error report, you can just move this line in the colossalai.testing.pytest_wrapper.py.
import os
- import pytest

def run_on_environment_flag(name: str):
    ...

+   import pytest
    assert isinstance(name, str)

I will check.
In the meantime, to be clear, this was triggered by running colossalai -i check in/using docker.io/hpcaitech/colossalai:0.3.0.
The only additional dependencies installed were the following for autoparallel
RUN pip install --no-cache-dir "transformers>=4.23.1" "pulp>=2.7.0" && \
    conda install -y -c conda-forge coin-or-cbc && \
...

Fixed by #4087


Support tan-stack column isVisible

material-react-table version
2.0.6
react & react-dom versions
18.2.0
Describe the bug and the steps to reproduce it
https://github.com/TanStack/table/blob/v7/docs/src/pages/docs/api/useTable.md#column-properties
TanStack table have a property on column to show/hidde them on first render directly from the column attributes
It's very practical when you want to hide everything except a few cherry-picked columns, vs doing the opposite of having to cherry-pick all the one you don't want when you want 4 on 40 by default
Minimal, Reproducible Example - (Optional, but Recommended)
const columns = [
    {
        accessorKey: "properties.lastName",
        header: "Last Name",
        isVisible: false,
      }
]

export default myComponent = () {
  return  <MaterialReactTable table={{
    columns: columns, // lastName is visible
    data: [],
  }} />

Screenshots or Videos (Optional)
No response
Do you intend to try to help solve this bug with your own PR?
No, because I do not have time to dig into it
Terms

[X] I understand that if my bug cannot be reliably reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.

This does not exist on TanStack Table v8, and for good reason. Use initialState instead. Just read the column hiding docs to see how to do it properly.

my bad 🙇
For some reason I was persuaded v7 was the last one


Added verifier interface

Added SdJwtVerifier to allow dynamic creation of  a JWSVerifier based on the already parsed but unverified SD-JWT. This mechanism replaces the old iss to JWK map. A default implementation to use the old mechanism is provided as TrustedIssuersSdJwtVerifier.
Closes #7

Looks good. Thank you very much for your contribution!


cannot read netCDF with more than one unlimited dimension

import numpy as np
import xarray as xr
import h5netcdf
import h5netcdf.legacyapi as netCDF4

# create a netCDF file with more than one unlimited dimension

x = np.arange(10.0)
ds = xr.Dataset({'data': ('dim0', x)},
             {'dim0': ('dim0', x), 'dim1': ('dim1', x)})

ds.to_netcdf('tst.nc', unlimited_dims=['dim0', 'dim1'])

# try to read it with h5netcdf

h5netcdf.File('tst.nc', 'r')
netCDF4.Dataset('tst.nc', 'r')

# works when using netCDF4
xr.Dataset('tst.nc', engine='netcdf4')

This yields ValueError: Each dimension with an actual length must have a 'REFERENCE_LIST' attribute. I think this should work.
 I'm marking this as a bug -- any interest in trying to figure this out?

I just checked and this no longer raises an error in master. So #40 seems to have fixed the issue.

I looked a bit deeper and I think the problem was that my 'dim1' did not belong to anything. So I think this is actually the same issue as #39. Thus this should be covered by
https://github.com/shoyer/h5netcdf/blob/master/h5netcdf/tests/test_h5netcdf.py#L742-L749
So I think we can actually close this.

OK, thanks for looking into it. I issued the v0.5.1 release, which should be up on pypi now.


pip update

I would like to use this commit in my work, but it is not distributed through pip yet. Can we get a version bump and new version on pip?
Thanks!

Hi Bram, yes Ill do it tomorrow. thanks!

Hi Bram,
Sorry for taking a bit more time than expected. Can you check if version 1.1.3 is working well on your end?
I had to also bump the python version. Python 3.7 is not compatible with new pandas versions and old pandas versions do not work on new Apple M1 computers.
From version 1.1.3 forward we will only support python >=3.8.

if everything is working feel free to close the issue.
Thanks for contributing!


add linters

Add linter, config, small refactoring

It seems everything should be ok, so I merge the PR and will test it locally


[HOLD]Add staging deploy to web and desktop

Please review @roryabraham
Details
On hold for https://github.com/Expensify/Expensify/issues/155119
Adds staging deploy environments for staging for both web and desktop. This does not yet deploy anything different to those environments, but is a first step 👣
Fixed Issues
Fixes https://github.com/Expensify/Expensify/issues/155195
Fixes https://github.com/Expensify/Expensify/issues/155196
Tests

Merge this PR
Go to staging.expensify.cash and verify it loads 👍

This logic makes total sense to me, however, I was prioritizing getting staging up and running ASAP. While I agree it's not the most elegant for the long term, I thought it was fine to have staging mirror production for a while, then add this logic when we know that logic is in place. Does that make sense?

Sure, we can do that as a follow-up PR.

Once this is off hold we can test a deploy to the new S3 bucket

Taking off hold, @rafecolton is going to merge when AWS is configured.


Please check this with your instructor if you are taking the course at UW-Madison. Otherwise, you don't have access.

excuse me，is there any other ways to reproduce this experiment，i do not have the access to this course？
Please check this with your instructor if you are taking the course at UW-Madison. Otherwise, you don't have access.
Originally posted by @edydfang in https://github.com/edydfang/Bourbon/issues/2#issuecomment-1005328006

excuse me，is there any other ways to reproduce this experiment，i do not have the access to this course？
Please check this with your instructor if you are taking the course at UW-Madison. Otherwise, you don't have access.
Originally posted by @edydfang in #2 (comment)

I would assume you can run the project on any Linux machine. Any specific issue you met?


Update the Apache-2.0 license string

The standard has the - in it

Per the SPDX standard formats, I agree.

If you are going by that list, probably need to update the GNU one's as well

@shortdudey123 We just discussed the need to update all of these actually

Ah, sounds good :)


Add the #[inline] attribute to public (including hidden) functions in gdnative-core

Without LTO (or ThinLTO), only functions with #[inline] can be inlined across crates. There are a lot of short functions that are simple wrappers in gdnative_core, and cross-crate inlining may be profitable, so adding #[inline] to them should make sense.
We may #[deny(clippy::missing_inline_in_public_items)] to maintain this in CI.
This issue is only about the regular #[inline] attribute. Do not add #[inline(always)] everywhere.

Fixed in #398.


New version Jenkins 2.340 not ok

What feature do you want to see added?
I do the configurations, but the theme is not ok.
Upstream changes
No response

I also have issues
updated to 2.341
some of the elements stay black intead of whatever color I choose


Publish on npm

Hi,
I'm looking to see if you can publish this module into npm as I have just recently developed this app which is made to be compatible with existing alfy workflows. Right now it works with my own alfy module but would like to see if become fully compatible with other alfy modules.

Yes, will be done very soon. See: https://github.com/sindresorhus/alfred-npms/pull/5


Segger RTT using j-link doesn't work on NXP i.MX RT

Describe the bug
Debug output, and logging using Segger RTT and j-link hardware doesn't work on i.MX RT SOCs from NXP. More info about the RTT subsystem here: RTT
To Reproduce
Steps to reproduce the behavior:

Select any sample application that runs on iMX RT 1020 EVK board.
Add the following to prj.conf:
CONFIG_UART_RTT=y CONFIG_UART_CONSOLE=n CONFIG_USE_SEGGER_RTT=y
Build and flash the sample application.
Start the j-link logger using the following command:
JLinkRTTLogger -device MIMXRT1021xxx5A -if SWD -speed 4000 -rttchannel 0 /dev/stdout

Expected behavior
JLinkRTTLogger automatically finds the ring buffers required for its operation in the device's memory, and the Zephyr startup output can be seen in the terminal.
Actual behavior
JLinkRTTLogger doesn't find the ring buffer and no output can be seen from the device.
Impact
Debug printouts using RTT is impossible.
Environment:

Any OS

Cause
The linker will place the ring buffer in external SRAM, but JLinkRTTLogger will only scan internal RAM segments (as it seems) for the buffers.
Workaround
The map file can be scanned for a symbol called _SEGGER_RTT and the exact adress can be fed
to JLinkRTTLogger executable. A better solution would be to to use CODE_DATA_RELOCATION to force this ring buffer into internal memory

@arvid-r is this something you'd consider sending a PR for?

Yes! I have a fix. I just need to figure out some details. Can I submit a PR targeting the Segger repo for example? And then, how do I make sure that the CODE_DATA_RELOCATION dependency is handled. I can't find any Kconfig files for the Segger repo.

You can send a PR against https://github.com/zephyrproject-rtos/segger @arvid-r


k3s-apiserver-lb-controller watches endpoints for etcd-only nodes even when etcd is not enabled

Seeing this when updating Kubernetes to 1.24.0-beta.0. Not sure why it's not showing up on master builds with 1.23; perhaps the current grpc version is swallowing the error.
{"level":"warn","ts":"2022-04-05T22:56:04.629Z","logger":"etcd-client","caller":"v3@v3.5.1-k3s1/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc002337340/kine.sock","attempt":0,"error":"rpc error: code = Unknown desc = put is not supported"}
ERRO[0076] error syncing 'default/kubernetes': handler k3s-apiserver-lb-controller: rpc error: code = Unknown desc = put is not supported, requeuing

The error somewhat expected since Kine doesn't support the Put operation. On the other hand, this controller shouldn't be running at all when not using embedded etcd, as there are no etcd-only nodes without etcd.

I don't see "managed etcd" in the logs even on v1.23.5+k3s1. I'm validating with the following steps:
$ curl -sfL https://get.k3s.io | INSTALL_K3S_VERSION=v1.23.6-rc1+k3s1  INSTALL_K3S_EXEC="server --write-kubeconfig-mode 644" sh -
...
$ journalctl -eu k3s | grep -i "managed etcd"

Note that when using managed etcd (via adding in the --cluster-init flag in the install exec args) this returns something.
I did confirm that this still does not show anything on v1.23.6-rc1+k3s1, but I think I'm doing something wrong in my validation since it is the same behavior for me as in v1.23.5. @brandond If that looks fine to you we can close this, otherwise I need input on how to proceed here.


Changes in Readme

Changed few words in README

Changed few words in README

Thank You @sourav7274  for your valuable contribution  , I am merging the change please give the  star to repository


provisioning: add DPU-HW-Components diagram

This is a decent enough start to merge.

can Intel edit/contribute @mestery ?


New @ruby/wasm-wasi package without .wasm?

I just spotted the deprecation warning:
DEPRECATED(ruby-3_2-wasm-wasi): "browser.esm.js" will be moved to "@ruby/wasm-wasi" in the next major release.Please replace your `import * from 'ruby-3_2-wasm-wasi/dist/browser.esm.js';` with `import * from '@ruby/wasm-wasi/dist/browser.esm.js';`

However, it's not clear to me why I need one CDN to grab @ruby/wasm-wasi/dist/browser.esm.js and another CDN url to grab its<EMAIL_ADDRESS>counterpart.
Your documentation is also a bit off around this deprecation.
Is there by any chance a will to move per version the ruby.wasm file within the main package? We pin the version and resolve the URL with ease this way, keeping track of versioning and 2 different URLs looks a bit unnecessary to me, or surely not ideal or user friendly, thank you!

Thanks for your detail report and sorry for my late response (I couldn't participate any OSS work for a while due to some contracts)
I'm very happy to hear that polyscript supports Ruby!

why I need one CDN to grab @ruby/wasm-wasi/dist/browser.esm.js and another CDN url to grab its<EMAIL_ADDRESS>counterpart.

The main reason for splitting into different packages is to share browser.esm.js among multiple Ruby versions.
Version specific packages (e.g. ruby-3_2-wasm-wasi) will contain only .wasm file and short script just for <script> tag soon and core @ruby/wasm-wasi package contains Ruby version independent things.

Your documentation is also a bit off around this deprecation.

Thank you for pointing out. That's my bad. Will update it soon.

Is there by any chance a will to move per version the ruby.wasm file within the main package?
Unfortunately, embedding .wasm files for all Ruby versions in the @ruby/wasm-wasi is unrealistic due to package size limit of jsdelivr CDN.

I know it's not ideal for your use case and it would be non-trivial cost to maintain two versions of the packages. One of the mitigations would be reading dependencies field of package.json at runtime and extracting the dependent @ruby/wasm-wasi version.
I'm still exploring a way to satisfy the multi Ruby version requirement and user friendliness at the same time.

I had a closer look at your case. It looks like you are importing the browser.esm.js with dynamic import, so your case might be able to be mitigated by just putting export * from 'https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>as browser.esm.js in version-specific package. (I still need to figure out a way to make it work with static bundler tools...)

as polyscript supports Lua (wasmoon), Python (pyodide + micropython), PHP (experimental), QuickJS (experimental), WebR (experimental) and whatnot, we'd love to fully support Ruby (half-experimental, it works great already for some use case) and we inevitably load interpreters and related code lazily, otherwise the project would die behind 50MB download to start with :sweat_smile:
I appreciate you looking into it, we can always pin-point default versions ourselves, the thing is that in polyscript one can explicitly define a Ruby version indeed, and we've no idea where to grab its WASM related counterpart to make it work ... the default can work fine, but users opting for another version would be hard for us to track.
If the dance out of a specific version can be bound to the very same URL, everything would be fine, as it's been until now, thank you!

Let me summarize the problem here:
First, there are several library consumer use cases.

Static bundler using ES Module
require() in Node.js using CJS
Dynamic import using ES Module
<script> tag using IIFE and UMD

In 1 and 2, they can simply replace their import "ruby-3_2-wasm-wasi/dist/browser" or require("ruby-3_2-wasm-wasi/dist/browser") statement with new @ruby/wasm-wasi version since the corresponding @ruby/wasm-wasi version is already resolved and installed under node_modules directory.
But 3 and 4 cannot easily grab the corresponding @ruby/wasm-wasi since there is no npm install phase or something like that.
So I decided to keep placing ES Module and UMD shims only for 3 and 4 use cases. My deprecation plan is:

Next minor release:

Remove deprecation messages from dist/browser.esm.js and dist/browser.umd.js in per-version packages.
Show warning when loading two different version of dist/browser.*.js in per-version packages for use case 3 and 4.
Create a new ES Module shim used only for use case 1 and show deprecation message.

Next major release:

Remove shims of all .cjs.js and .d.ts and dist/node.*.js.

@kateinoigakukun I am not sure I am following but ESM is the only way forward for JS. On the web, our issue is that we don't know where to find the .wasm file because it's in a different module. We can hard-code that but it will play badly for users' custom versions for testing purpose or whatnot.
To us, like it is for every other project we deal with until now, we expect the following:

import * from 'https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>is the ESM module
`import * from 'https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>is the related WASM engine

UMD is a dead standard, it breaks with ECMAScript standard modules and it's been abandoned by everyone.
CJS is still used in Node but ultimately both bun and deno and every browser uses ESM so it's less interesting as a target and node deals very well with ESM too since version 16+.
Is there by any chance the will to provide such simple approach so that both versioning of the module and the WASM file are always in sync and we need to deal only with one pre-resolved CDN URL instead?
Thanks!

@kateinoigakukun awesome, thanks for that!


Add verified config to scenario documentation

I have been noticing that certain commands in some scenarios are experiencing different results depending on the source/target operating system selection.  For example, I have been attempting the AzSHCI and Kubernetes and AzSHCI Deployment scenarios and experienced different results with the following two OS combinations:

WS 2019 DC for Scenario.ps1 executing against AzSHCI, version 21H2 cluster node VMs.
WS 2022 DC for Scenario.ps1 executing against AzSHCI, version 21H2 cluster node VMs.

I haven't had an opportunity to go command-by-command and organize my varying results yet.  However, it might be helpful to specify the exact environment that has been verified in the scenario documentation.  For example, note in the documentation that you experienced no issues with the code running on a WS 2022 DC against 21H2 nodes.

Hmm, the idea is to have LabConfig for each scenario (except DC, there are all VMs defined with OS I was testing last). Assuming everyone will use the same. I did not face any issue so far with different update level of certain server. What I recently faced with for example Kubernetes scenario are different issues with az. modules. I tried to document all issues as reference to GitHub issue I created for each az. module


microphone not working

IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide.
Briefly summarize your issue:

What is the expected behavior?

What behavior are you observing?

Provide the steps to reproduce the issue, if applicable:

Tell us about your environment:

What version of the AVS Device SDK are you using?
  <x.y.z>

Tell us what hardware you're using:

[ ] Desktop / Laptop
[x] Raspberry Pi
[ ] Other - tell us more:

Tell us about your OS (Type & version):

[ ] Linux
[ ] MacOS
[ ] Raspbian Stretch
[ ] Raspbian Jessy
[x] Other - tell us more:

Hello,
I'm facing the following issue:
After installing the the 'alexa smart screen sdk' on a raspberry pi 3B+, compiling and verfying it with
cd $HOME/sdk_folder/sdk-build
PA_ALSA_PLUGHW=1 ./SampleApp/src/SampleApp ./Integration/AlexaClientSDKConfig.json DEBUG9
I can talk to Alexa without any problem.
But after compiling the second part aof the instructions starting at step 7, the compilation ends completely, and, when I start Alexa with
cd $HOME/sdk_folder/ss-build
PA_ALSA_PLUGHW=1 ./modules/Alexa/SampleApp/src/SampleApp -C
$HOME/sdk_folder/sdk-build/Integration/AlexaClientSDKConfig.json -C
$HOME/sdk_folder/alexa-smart-screen-sdk/modules/GUI/config/SmartScreenSDKConfig.json -L INFO
all seems to be ok, opening a browser window is ok, and after pressing the 'A' key the reference changes from 'Idle' to 'listening'. That's all.
There is no change to 'thinking' and so I don't get any answer from Alexa. It seems that the microphone isn't working.
The settings concerning Audio seem to be ok, because if I test them with:

arecord --device=hw:2,0 --format S16_LE --rate 44100 -c1 test.wav
and
aplay --device=plughw:1,0 test.wav

I can hear the record.
The --device:hw:2,0 is ok, because 'arecord -l' is showing me
**** Liste der Hardware-Geräte (CAPTURE) ****
Karte 2: Device [USB PnP Sound Device], Gerät 0: USB Audio [USB Audio]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0
The '.asoundrc'-settings are the same as described in the tutorial, except the change to 'hw:2,0' instead of 'hw:1,0.
So, do I miss to make other settings? The only changes I made in the AlexClientSDK.json are those concerning
"serial number"
"manufacturer name"
"device description"
and entering the gstreamer-statement.
The 'clientId' and 'productId' are the same as in the 'config.jason'.
So, what could be the problem? Here, in the forum I only found several issues similar to my problem, but not the same.
I installed everything several times from scratch, but it's everytime the same behaviour.

Hi @kurol1 thanks for posting.
Have you looked at our quickstart guide for raspberry pi and followed the steps for setting up a microphone?
https://developer.amazon.com/en-US/docs/alexa/avs-device-sdk/raspberry-pi.html#set-up-the-microphone

Hi Gaetano,
please excuse my late reply.
Your hints I've already tried in vain.
The situation now is the following:
Normal desktop screen, no software started:
I enter (in a terminal)
arecord test.wav
aplay test.wav
test.wav is recorded and played back the right way, with a good quality.
I start Alexa with the script in the installation guide, I get the notification that Alexa is running in 'Idle'-state.
I start the Browser (Firefox) and open the index-page. I can see the gray screen, after pressing 'A' the state changes for 'idle' to 'listening'. If I talk to Alexa (no matter if in English or German) nothing happens, Alexa doesn't go into the 'thinking' state. After releasing the 'A' Alexa goes back to 'idle'. No sound at all.
But then, and that's confusing me:
I open a terminal and enter
arecord test1.wav
aplay test1.wav
test1.wav is recorded and played back in a good quality. (Alexa is still running).
Do you have any other idea? I've installed the SDK several times in a very exact accordance to the guide, it's everytime the same.
Thank you in advance
Regards
Roland

hi @kurol1 - can you please try the alexa client SDK directly (without smart screen) - https://github.com/alexa/avs-device-sdk ?
As a short-cut, can you try the following:
https://developer.amazon.com/en-US/docs/alexa/avs-device-sdk/raspberry-pi.html#set-up-the-microphone
 pcm.!default {
   type asym
    playback.pcm {
      type plug
      slave.pcm "hw:0,0"
    }
    capture.pcm {
      type plug
      slave.pcm "hw:1,0"
    }
 }

Hi Ravi,
thanks for your reply.
When I install the SDK in accordance to
<https://developer.amazon.com/en-US/docs/alexa/alexa-voice-service/set-up-ra
spberry-pi.html>
https://developer.amazon.com/en-US/docs/alexa/alexa-voice-service/set-up-ras
pberry-pi.html (the setup procedure without scteen), all is working
perfectly.
If I install it as decribed here
<https://developer.amazon.com/en-US/docs/alexa/alexa-smart-screen-sdk/raspbe
rry-pi.html>
https://developer.amazon.com/en-US/docs/alexa/alexa-smart-screen-sdk/raspber
ry-pi.html,
and check the installation accordiing to  Step 6: Verify the AVS Device SDK
build, I can talk to Alexa without any problems., all is working fine, too.
After finishing the installation with step Step 10: Test the Alexa Smart
Screen SDK sample app, all seems to be ok, after pressing the 'A'-key the
notification on the screen changes from 'idle' to 'listening' and back again
(after releasing the key), but there's no further action from Alexa.
The changes in the 'asoundrc'-file are ok, I tried several modifications.
I find it strange, that (as described in my previous comment), recording and
playing back is working fine, even if Alexa is running.  So, I suppose, the
reason for the problem is not due to a faulty installation.
If you have an idea or if you need further informations please let me know.
Thank you in advance.
Von: Ravi Chemudugunta<EMAIL_ADDRESS>Gesendet: Donnerstag, 12. November 2020 23:50
An: alexa/avs-device-sdk<EMAIL_ADDRESS>Cc: kurol1<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Betreff: Re: [alexa/avs-device-sdk] microphone not working (#1814)
hi @kurol1 https://github.com/kurol1  - can you please try the alexa
client SDK directly (without smart screen) -
https://github.com/alexa/avs-device-sdk ?
As a short-cut, can you try the following:
https://developer.amazon.com/en-US/docs/alexa/avs-device-sdk/raspberry-pi.ht
ml#set-up-the-microphone
pcm.!default {
type asym
playback.pcm {
type plug
slave.pcm "hw:0,0"
}
capture.pcm {
type plug
slave.pcm "hw:1,0"
}
}

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/alexa/avs-device-sdk/issues/1814#issuecomment-726389086
, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AICS3N6F3TRE7CDTRKSSMYLSP
RRBVANCNFSM4S4FORLQ> .
<https://github.com/notifications/beacon/AICS3N2MWCK6SRRUFHRRRETSPRRBVA5CNFS
M4S4FORL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFNF5CXQ
.gif>

@kurol1  are you holding down 'A' key?
It's a hold to talk mode, so you need to keep it pressed while you communicate.
You can change the behaviour here:
https://github.com/alexa/alexa-smart-screen-sdk/blob/9878cafa35df05d862b3bfc027aa6b1b463ef9c1/modules/GUI/config/guiConfigSamples/GuiConfigSample_TvFullscreen.json#L8
Valid values are listed here:
https://github.com/alexa/alexa-smart-screen-sdk/blob/9878cafa35df05d862b3bfc027aa6b1b463ef9c1/modules/GUI/js/src/lib/config/IDeviceAppConfig.ts#L16

Hi Ravi,
thank you very muchr your help and hints.
In the meantime I randomly(!) figured out how to get Alexa to communicate
with me:
In 'idle'.mode, I need to press and hold the 'A' key for app. 2 seconds,
then press the 'Enter'-key simultaneously and then release both keys.  Now
Alexa goes permanently into 'listening'-mode. Then I can ask her my
question. After finishing the question I need to press the 'A'-key again
(without 'Enter'). Alexa switches into 'thinking'-mode and shortly
afterwards is giving me the answer. Then she switches back to 'Idle'-mode.
I don't know the reason for that behaviour, but it's working fine.
As it seems,that you are an expert concerning Alexa, could you please answer
me the following questions:
How can I change triggering Alexa from 'push-to-talk' to 'wakeword', because
always pressing one or two keys is not a satisfying solution?
How can I change the screen settings, for example the color?
As the screen is started in a web-browser, I see the menubar of the browser
and the Linux menu at top of the screen. Is it possible to switch to
full-screen mode?
I searched the forum, but couldn't find any answers. Maybe you can help me.
Thank you very much in advance.
I case you have any questions, please contact me.
Best regards
Roland
Von: Ravi Chemudugunta<EMAIL_ADDRESS>Gesendet: Dienstag, 17. November 2020 22:39
An: alexa/avs-device-sdk<EMAIL_ADDRESS>Cc: kurol1<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Betreff: Re: [alexa/avs-device-sdk] microphone not working (#1814)
@kurol1 https://github.com/kurol1  are you holding down 'A' key?
It's a hold to talk mode, so you need to keep it pressed while you
communicate.
You can change the behaviour here:
https://github.com/alexa/alexa-smart-screen-sdk/blob/9878cafa35df05d862b3bfc
027aa6b1b463ef9c1/modules/GUI/config/guiConfigSamples/GuiConfigSample_TvFull
screen.json#L8
Valid values are listed here:
https://github.com/alexa/alexa-smart-screen-sdk/blob/9878cafa35df05d862b3bfc
027aa6b1b463ef9c1/modules/GUI/js/src/lib/config/IDeviceAppConfig.ts#L16

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/alexa/avs-device-sdk/issues/1814#issuecomment-729229682
, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AICS3NY6XSGOW6OGUWUAO43SQ
LUPPANCNFSM4S4FORLQ> .
<https://github.com/notifications/beacon/AICS3N6JHZ332FX6DPLVDJDSQLUPPA5CNFS
M4S4FORL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFN3SS4Q
.gif>

Hi @kurol1,
To enable wake word, you will need to integrate and compile wake word engine to avs-device-sdk. Here is a link that explains the steps.
Once you can validate wake word engine works with avs-device-sdk, you will need to compile alexa-smart-screen-sdk with same extra wake word engine cmake flags. Once completed, you can modify SmartScreenSDKConfig.json and change setting audioInputInitiator": "WAKEWORD.
Other GUI options and configurable settings can also be found in this json file. Please explore the code to modify GUI behavior. Sample web application should work in full screen mode.
Thank you for your contribution to the Alexa Smart Screen SDK and avs-device-sdk!
Thanks,
Varun

Hi Varun,
thank you very much for your help.
I followed the instructions in the link you attached in the email and
succeeded in compiling the SDK. Alexa answered my questions. All OK.
But now I'd be glad, if you would help me again:
After compiling as described I proceeded with step 7 of the instructions
here:
https://developer.amazon.com/en-US/docs/alexa/alexa-smart-screen-sdk/raspber
ry-pi.html. Was that right to proceed with this step?

I think, I did something wrong, as my Linux-knowledge is rather poor. Was it
right what I did?
You wrote that I would need to use the wake word engine flags when compiling
alexa smart screen sdk.
Would the cmake-command look like this with the appended flags?
cmake -DCMAKE_PREFIX_PATH=$HOME/sdk_folder/sdk-install \
-DSENSORY_KEY_WORD_DETECTOR=ON \
-DSENSORY_KEY_WORD_DETECTOR_LIB_PATH=/home/pi/sdk-folder/third-party/alexa-r
pi/lib/libsnsr.a \
-DSENSORY_KEY_WORD_DETECTOR_INCLUDE_DIR=/home/pi/sdk-folder/third-party/alex
a-rpi/include \
-DWEBSOCKETPP_INCLUDE_DIR=$HOME/sdk_folder/third-party/websocketpp-0.8.1 \
-DDISABLE_WEBSOCKET_SSL=ON \
-DGSTREAMER_MEDIA_PLAYER=ON \
-DCMAKE_BUILD_TYPE=DEBUG \
-DPORTAUDIO=ON
-DPORTAUDIO_LIB_PATH=$HOME/sdk_folder/third-party/portaudio/lib/.libs/libpor
taudio.a \
-DPORTAUDIO_INCLUDE_DIR=$HOME/sdk_folder/third-party/portaudio/include/ \
-DAPL_CORE=ON \
-DAPLCORE_INCLUDE_DIR=$HOME/sdk_folder/apl-core-library/aplcore/include \
-DAPLCORE_LIB_DIR=$HOME/sdk_folder/apl-core-library/build/aplcore \
-DAPLCORE_RAPIDJSON_INCLUDE_DIR=$HOME/sdk_folder/apl-core-library/build/rapi
djson-prefix/src/rapidjson/include \
-DYOGA_INCLUDE_DIR=$HOME/sdk_folder/apl-core-library/build/yoga-prefix/src/y
oga \
-DYOGA_LIB_DIR=$HOME/sdk_folder/apl-core-library/build/lib \
../alexa-smart-screen-sdk
As I mentioned already above, my Linux knowledge is not very good, so you
would do me a great favour if you would explain to me the steps to be taken
in detail.
Thank you very much in advance.
Best regards
Roland
Von: Varun Pandey<EMAIL_ADDRESS>Gesendet: Samstag, 21. November 2020 01:08
An: alexa/avs-device-sdk<EMAIL_ADDRESS>Cc: kurol1<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Betreff: Re: [alexa/avs-device-sdk] microphone not working (#1814)
Hi @kurol1 https://github.com/kurol1 ,
To enable wake word, you will need to integrate and compile wake word engine
to avs-device-sdk. Here is a link
<https://developer.amazon.com/en-US/docs/alexa/avs-device-sdk/raspberry-pi.h
tml#download-the-avs-device-sdk-and-the-sensory-wake-word-engine>  that
explains the steps.
Once you can validate wake word engine works with avs-device-sdk, you will
need to compile alexa-smart-screen-sdk with same extra wake word engine
cmake flags. Once completed, you can modify SmartScreenSDKConfig.json and
change setting audioInputInitiator": "WAKEWORD.
Other GUI options and configurable settings can also be found in this json
file. Please explore the code to modify GUI behavior. Sample web application
should work in full screen mode.
Thank you for your contribution to the Alexa Smart Screen SDK and
avs-device-sdk!
Thanks,
Varun

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/alexa/avs-device-sdk/issues/1814#issuecomment-731469156
, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AICS3N7YXX6V44BOZ2EIX3LSQ
4AF3ANCNFSM4S4FORLQ> .
<https://github.com/notifications/beacon/AICS3NZ73ZKXC3O3OMMN5W3SQ4AF3A5CNFS
M4S4FORL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFOMVKZA
.gif>

@kurol1, the cmake cmd looks good. Ensure that you have performed make install for the avs-device-sdk and the $HOME/sdk_folder/sdk-install has all the generated binaries and includes. This is mentioned as STEP 3.3 from the setup guide.
Thanks,
Varun

Hi Varun,
thanks for your reply. I think it's getting better.
Please tell me, if it's the right way I try to get Alexa screen to work
properly.
1:) I install everything in accordance to
https://developer.amazon.com/en-US/docs/alexa/alexa-smart-screen-sdk/raspber
ry-pi.html.
Alexa is working fine with the ptt function.

2: As the above installation only works with ptt, I install the following
parts according to
https://developer.amazon.com/en-US/docs/alexa/avs-device-sdk/raspberry-pi.ht
ml.

Clone the Sensory wake word engine into the third-party folder.
cd /home/pi/sdk-folder/sdk-source
git clone --single-branch git://github.com/alexa/avs-device-sdk.git
cd /home/pi/sdk_folder/third-party
git clone git://github.com/Sensory/alexa-rpi.git
Run the licensing script to view the Sensory licensing agreement.
You must accept this license agreement to use the Sensory wake word engine
and enable the "Alexa" wake word.
cd /home/pi/sdk_folder/third-party/alexa-rpi/bin/
./license.sh
and then build the SampleAPP with:
cd /home/pi/sdk_folder/sdk-build
cmake /home/pi/sdk_folder/sdk-source/avs-device-sdk \
-DSENSORY_KEY_WORD_DETECTOR=ON \
-DSENSORY_KEY_WORD_DETECTOR_LIB_PATH=/home/pi/sdk_folder/third-party/alexa-r
pi/lib/libsnsr.a \
-DSENSORY_KEY_WORD_DETECTOR_INCLUDE_DIR=/home/pi/sdk_folder/third-party/alex
a-rpi/include \
-DGSTREAMER_MEDIA_PLAYER=ON \
-DPORTAUDIO=ON \
-DPORTAUDIO_LIB_PATH=/home/pi/sdk_folder/third-party/portaudio/lib/.libs/lib
portaudio.a \
-DPORTAUDIO_INCLUDE_DIR=/home/pi/sdk_folder/third-party/portaudio/include
and
then run 'make SampleApp'.

Now I can communicate with Alex by ptt
cd /home/pi/sdk_folder/sdk-build
PA_ALSA_PLUGHW=1 ./SampleApp/src/SampleApp
./Integration/AlexaClientSDKConfig.json DEBUG9
or with Wakeword:
cd /home/pi/sdk-folder/sdk-build
PA_ALSA_PLUGHW=1 ./SampleApp/src/SampleApp
./Integration/AlexaClientSDKConfig.json ../third-party/alexa-rpi/models
Both Version work perfectly.
To work with ptt and screen
cd $HOME/sdk_folder/ss-build
PA_ALSA_PLUGHW=1 ./modules/Alexa/SampleApp/src/SampleApp -C \
$HOME/sdk_folder/sdk-build/Integration/AlexaClientSDKConfig.json -C \
$HOME/sdk_folder/alexa-smart-screen-sdk/modules/GUI/config/SmartScreenSDKCon
fig.json -L INFO
I think, to show the screen and start Alexa by wakeword I need to enter this
statement
            PA_ALSA_PLUGHW=1 ./SampleApp/src/SampleApp

./Integration/AlexaClientSDKConfig.json  ../third-party/alexa-rpi/models
followed by the statement to start the screen-module:
$HOME/sdk_folder/alexa-smart-screen-sdk/modules/GUI/config/SmartScreenSDKCon
fig.json -L INFO
I mean, it should be somting like this:
cd $HOME/sdk_folder/ss-build
PA_ALSA_PLUGHW=1 ./modules/Alexa/SampleApp/src/SampleApp
../third-party/alexa-rpi/models  -C \
$HOME/sdk_folder/sdk-build/Integration/AlexaClientSDKConfig.json -C \
$HOME/sdk_folder/alexa-smart-screen-sdk/modules/GUI/config/SmartScreenSDKCon
fig.json -L INFO
Here is my problem, the above statement doesn't work and I cannot figure out
why.
I get the answer:
pi@raspberrypi:~/sdk_folder/ss-build $  PA_ALSA_PLUGHW=1
./modules/Alexa/SampleApp/src/SampleApp  ../third-party/alexa-rpi/models -C
\

$HOME/sdk_folder/sdk-build/Integration/AlexaClientSDKConfig.json -C \

$HOME/sdk_folder/alexa-smart-screen-sdk/modules/GUI/config/SmartScreenSDKCon
fig.json -L INFO
SmartScreenSDKVersion 2.4
USAGE: ./modules/Alexa/SampleApp/src/SampleApp -C <config1.json> -C
<config2.json> ... -C <configN.json>  -K <path_to_inputs_folder> -L
<log_level>
So I suppose, the fault is in my self-made statement.
Could you please tell me the fault? Do I need to compile anything else?
Thank you very much in advance.
Best regards
Roland
Von: Varun Pandey<EMAIL_ADDRESS>Gesendet: Montag, 23. November 2020 17:14
An: alexa/avs-device-sdk<EMAIL_ADDRESS>Cc: kurol1<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Betreff: Re: [alexa/avs-device-sdk] microphone not working (#1814)
@kurol1 https://github.com/kurol1 , the cmake cmd looks good. Ensure that
you have performed make install for the avs-device-sdk and the
$HOME/sdk_folder/sdk-install has all the generated binaries and includes.
This is mentioned as STEP 3.3 from the setup guide
<https://developer.amazon.com/en-US/docs/alexa/alexa-smart-screen-sdk/raspbe
rry-pi.html#step-3> .
Thanks,
Varun

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/alexa/avs-device-sdk/issues/1814#issuecomment-732263334
, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AICS3N3TCUKIECKWYNEXNG3SR
KC5HANCNFSM4S4FORLQ> .
<https://github.com/notifications/beacon/AICS3N3ES6A75E4NT5INU23SRKC5HA5CNFS
M4S4FORL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFOSXHJQ
.gif>

@kurol1
Can you please try to run again with this command?
PA_ALSA_PLUGHW=1 ./modules/Alexa/SampleApp/src/SampleApp
-K ./third-party/alexa-rpi/models
-C $HOME/sdk_folder/sdk-build/Integration/AlexaClientSDKConfig.json
-C $HOME/sdk_folder/alexa-smart-screen-sdk/modules/GUI/config/SmartScreenSDKConfig.json
-L INFO
Thanks,
Mike

I'm going to close this due to inactivity. Please open a new issue if I've closed this in error, or if you have more questions. Thanks!

I'm going to close this due to inactivity. Please open a new issue if I've closed this in error, or if you have more questions. Thanks!


Fix:Its allowed to set step_result twice[EOA-7342]

wrong commit message it's or it is not its

Mustn't be merged before 'add_step' functionality is done and merged.


docs: add a section about useRequestFetch and event.$fetch

🔗 Linked issue
resolves https://github.com/nuxt/nuxt/issues/19815

📚 Description

This PR adds brief documentation for useRequestFetch and event.$fetch

@CernyMatej Thanks for the contribution 🔥
I'm curious: did you watch the video with the "call to contribution before ☺

@manniL Yes I did 😄
Great video as always btw

Could we cherry pick this commit to 3.x somehow @danielroe ?

thanks for spotting!


No administrator account found inside the database

Problem/Motivation
I noticed today that the portainer addon wasn't running. After restarting it it took me to the "create an admin user" screen.
Expected behavior
It used to do some kind of SSO, signing me in automatically if via HA.
Actual behavior
It shows the new portainer installation setup wizard.
Steps to reproduce
Not  sure
Logs
2021/09/03 12:07:30 [DEBUG] [internal,init] [message: start initialization monitor ]
2021/09/03 12:07:46 http error: No administrator account found inside the database (err=Object not found inside the database) (code=404)
2021/09/03 12:07:46 http error: No administrator account found inside the database (err=Object not found inside the database) (code=404)
2021/09/03 12:08:10 http error: No administrator account found inside the database (err=Object not found inside the database) (code=404)
2021/09/03 12:08:10 http error: No administrator account found inside the database (err=Object not found inside the database) (code=404)

nvm, it was in the changelog


Is there urdf file avaialbe for ranger mini

Hi, I've seen urdf files in the description foler for scout, just wonder if there is a one for ranger mini?

需要ranger mini 2的URDF或者STL文件


Convert a.run() to a proper synchronization system

Summary
There is a real contention point with how the current synchronization is implemented. a.run() creates a single worker queue in order to do "pseudo locking" and to synchronize execution inside of the ice library. Unfortunately this is a really challenging design and creates a lot of issues. E.g. Bad perf benchmark, pool locking capabilities.
It would be nice to change this to improve performance and synchronization issues.
Describe alternatives you've considered
Did not consider any alternatives but the best solution would be something that does not require locking at all. Here is one really good place to draw ideas from:
https://drive.google.com/file/d/1nPdvhB0PutEJzdCq5ms6UI58dp50fcAN/view

I have cleaned this up a bit, and now pion/ice isn't in the top 25. I am not going to work on this further.
I didn't end up removing .run, it is more then simple mutual exclusion it also allows cancellation of queued locks. I tried replacing things with a simple mutex, but ended up being more messy then I thought it would be.
For the cases where we want to return values from .run I have updated things to use atomics (instead of channels). .run itself is now blocking, and doesn't push the task across the channel. It instead calls the function directly.


Support std aggregation in reduction

This adds support for std (i.e., stddev_samp) aggregation in reduction context, completing https://github.com/NVIDIA/spark-rapids/issues/62.
Closes https://github.com/NVIDIA/spark-rapids/issues/7891 and closes https://github.com/NVIDIA/spark-rapids/issues/62.

Benchmark time running on a column of 1M rows randomly generated:
CPU:
scala> val result = df.selectExpr("std(value)")
result: org.apache.spark.sql.DataFrame = [std(CAST(value AS DOUBLE)): double]

scala> spark.time(result.collect)
Time taken: 1780 ms
res0: Array[org.apache.spark.sql.Row] = Array([2888.906172169368])

scala> spark.time(result.collect)
Time taken: 40 ms
res1: Array[org.apache.spark.sql.Row] = Array([2888.906172169368])

scala> spark.time(result.collect)
Time taken: 38 ms
res2: Array[org.apache.spark.sql.Row] = Array([2888.906172169368])

....

CPU with 1 partition:
scala> val result = df.repartition(1).selectExpr("std(value)")
result: org.apache.spark.sql.DataFrame = [std(CAST(value AS DOUBLE)): double]

scala> spark.time(result.collect)
Time taken: 682 ms
res3: Array[org.apache.spark.sql.Row] = Array([2888.906172169392])

scala> spark.time(result.collect)
Time taken: 146 ms
res4: Array[org.apache.spark.sql.Row] = Array([2888.906172169392])

scala> spark.time(result.collect)
Time taken: 146 ms
res5: Array[org.apache.spark.sql.Row] = Array([2888.906172169392])

...

GPU:
scala> val result = df.selectExpr("std(value)")
result: org.apache.spark.sql.DataFrame = [std(CAST(value AS DOUBLE)): double]

scala> spark.time(result.collect)
23/04/28 21:05:13 WARN GpuOverrides:
*Exec <HashAggregateExec> will run on GPU
  *Expression <AggregateExpression> std(cast(value#0 as double)) will run on GPU
    *Expression <StddevSamp> std(cast(value#0 as double)) will run on GPU
      *Expression <Cast> cast(value#0 as double) will run on GPU
  *Expression <Alias> std(cast(value#0 as double))#10 AS std(CAST(value AS DOUBLE))#27 will run on GPU
  *Exec <ShuffleExchangeExec> will run on GPU
    *Partitioning <SinglePartition$> will run on GPU
    *Exec <HashAggregateExec> will run on GPU
      *Expression <AggregateExpression> partial_std(cast(value#0 as double)) will run on GPU
        *Expression <StddevSamp> std(cast(value#0 as double)) will run on GPU
          *Expression <Cast> cast(value#0 as double) will run on GPU
      *Exec <FileSourceScanExec> will run on GPU

Time taken: 1915 ms
res0: Array[org.apache.spark.sql.Row] = Array([2888.9061721694384])

scala> spark.time(result.collect)
Time taken: 54 ms
res1: Array[org.apache.spark.sql.Row] = Array([2888.9061721694384])

scala> spark.time(result.collect)
Time taken: 43 ms
res2: Array[org.apache.spark.sql.Row] = Array([2888.9061721694384])

...

GPU with 1 partition:
scala> val result = df.repartition(1).selectExpr("std(value)")
result: org.apache.spark.sql.DataFrame = [std(CAST(value AS DOUBLE)): double]

scala> spark.time(result.collect)
23/04/28 21:17:09 WARN GpuOverrides:
*Exec <HashAggregateExec> will run on GPU
  *Expression <AggregateExpression> std(cast(value#0 as double)) will run on GPU
    *Expression <StddevSamp> std(cast(value#0 as double)) will run on GPU
      *Expression <Cast> cast(value#0 as double) will run on GPU
  *Expression <Alias> std(cast(value#0 as double))#10 AS std(CAST(value AS DOUBLE))#27 will run on GPU
  *Exec <HashAggregateExec> will run on GPU
    *Expression <AggregateExpression> partial_std(cast(value#0 as double)) will run on GPU
      *Expression <StddevSamp> std(cast(value#0 as double)) will run on GPU
        *Expression <Cast> cast(value#0 as double) will run on GPU
    *Exec <ShuffleExchangeExec> will run on GPU
      *Partitioning <RoundRobinPartitioning> will run on GPU
      *Exec <FileSourceScanExec> will run on GPU

Time taken: 1899 ms
res0: Array[org.apache.spark.sql.Row] = Array([2888.9061721694393])

scala> spark.time(result.collect)
Time taken: 71 ms
res1: Array[org.apache.spark.sql.Row] = Array([2888.9061721694393])

scala> spark.time(result.collect)
Time taken: 65 ms
res2: Array[org.apache.spark.sql.Row] = Array([2888.9061721694393])

...

build

build

build


Possible null access check needs to be added

A possible null access check needs to be added for program nullmapref.

Added support for null checks for shared ptrs in commit


osgi import is broken for kryo

Hi all,
You still refer to the < 3.0 version of kryo in your osgi import statement - even if you have kryo 3.0 in your dependencies:
com.esotericsoftware.kryo*;version="[2.24.0,3.0)",
It would be great if you could fix this - i'll use a manually patched version in the meantime.
Thanks,
Mathias

Good catch, thanks for the report! Do you want to submit a pull request? This would speed things up :-)

would be great if you could publish a new version with the fix

Thanks for the pull request, released as 0.37 to maven central.


"SELF_SIGNED_CERT_IN_CHAIN" in packages and themes tab of settings

Hello,
I've been using Atom now as my main code editor for months and I love it. However, I've noticed in the last couple of versions that there seems to be a problem with accessing the packages and Themes tab of the settings. Whenever I search for something, I get this error come up:
SELF_SIGNED_CERT_IN_CHAIN
I have tried uninstalling Atom and reinstalling it, and the same problem comes up.
Is this an Atom problem, or more likely something to do with my laptop, and if so, what?
I'm running a MacBook Air on Mac OSX 10.10 Yosemite with Atom version 0.144.0.
Any help would be most appreciated, since I don't seem to be able to add extensions any more.
Many thanks,
Dominic Ross,

This error is really sinister for me.  I'm on version 0.169.0 for Windows.  I'm behind a proxy at work.
I was able to create a ~/.atom/.apmrc file and add strict-ssl = false to solve the issue with apm.  However, I have no idea how to tell atom itself to allow self-signed certs.  When this error occurs, it will sometimes get stuck in a loop spamming the error over and over, locking up the editor completely.
Here are two of the errors I've seen.  I usually see the stream.js:94 one.
stream.js:94
Error: self signed certificate in certificate chain
  at Error (native)
  at TLSSocket.<anonymous> (_tls_wrap.js:914:36)
  at TLSSocket.emit (events.js:104:17)
  at TLSSocket._finishInit (_tls_wrap.js:457:8)

events.js:85
Error: self signed certificate in certificate chain
  at Error (native)
  at TLSSocket.<anonymous> (_tls_wrap.js:914:36)
  at TLSSocket.emit (events.js:104:17)
  at TLSSocket._finishInit (_tls_wrap.js:457:8)

apm config set strict-ssl false

Closing this out, this is a configuration issue where you may need to configure apm/npm when behind a firewall/proxy, see https://github.com/atom/apm#behind-a-firewall for more details.

Disabling SSL is not safe, if you cannot connect it may be due to your corporate firewall, In this case you need to install a trusted certificate. See #8465

@sveilleux This leaves you open to man-in-the-middle attacks. Anyone can pretend to be npmjs.org at this point and then you could end up getting hacked if someone knows that you are using this setting. I do not recommend anyone do this.


Unable to apply update 9.1.2

Seeing pop-up box in interface stating v9.1.2 is available but no way to apply the update.  Not showing anywhere in Home Assistant.  I am currently running v9.1.0.
Is there a manual way to apply the update?  Thanks in advance.

Thank you for the reply...but not sure I follow.   Here is my add-on:

And I am being notified that there is an update withing the UI...how should I go about updating?

???  So why am I seeing the "New version available"?  Sorry if this is an ID10t question, but trying to learn here.

9.1.2 fixes the notification issue. No need to disable the changelog

Well, I didn't mention anything about changelog. 😆

Yeah I know that was just because someone could have suggested that as solution, 9.1.2 made it opt-in so if someone wants can enable that on settings :)


StackParser crashes when using /in and /out parameter

StackParser crashes when using /in and /out parameter because the StreamReader/StreamWriter instances "sr" and "sw" are closed too early.

Was this issue solved by #61?


Ignore not-yet created databases on other coordinators

Scope & Purpose
Ignore not-yet created databases on other coordinators when querying the list of currently running or slow AQL queries.
This prevents a "database not found" error to be potentially returned in a multi-coordinator setup when the list of slow queries is accessed/cleared directly after a new database has been created.
Multi-coordinator support for the current/slow query list access is added in 3.6.10/3.7.5 only, so this issue was not yet in any released version.

[x] :hankey: Bugfix (requires CHANGELOG entry)
[ ] :pizza: New feature (requires CHANGELOG entry, feature documentation and release notes)
[ ] :fire: Performance improvement
[ ] :hammer: Refactoring/simplification
[x] :book: CHANGELOG entry made

Backports:

[x] Backports required for: 3.6 (https://github.com/arangodb/arangodb/pull/13189)

Testing & Verification

[x] This change is a trivial rework / code cleanup without any test coverage.
[x] The behavior in this PR was manually tested

Link to Jenkins PR run:
http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/13134/

Tests blue


Kubernetes Cluster is using the wrong Godo endpoint for deletion

What happened?
When deleting a Kubernetes Cluster, it didn't get deleted.
How can we reproduce it?

Create a Kubernetes Cluster using crossplane
Delete the resource and wait for it to be deleted

It should never be deleted.
What environment did it happen in?
Crossplane version:
Provider version 0.1.0
This is caused by the Kubernetes controller calling godo.Database.Delete

Hitting the same here


[v1] Pull to refresh is triggering on scrollup when the list is inside tabs

This happens when I use a page with multiple tabs and lists inside each tab.
The ptr was expected to refresh only on the top of the list, but container[0].scrollTop is = 0, because the container is the .page not the .tab
https://github.com/framework7io/framework7/blob/v1/dist/js/framework7.js#L9294
This works for my case, it migth be helpful to include in the code:
if($$(container[0]).hasClass('tabs-and-searchbar')){     scrollTop = $$(container[0]).find('.tab.active').scrollTop(); } else{     scrollTop = container[0].scrollTop;   }

Sorry, v1 is not maintained anymore


Better than the real thing

Based on some of my testing I have to say that your implementation is actually producing better results that the original neural-doodle: https://twitter.com/netputing/status/710119813847207937

Thanks!

The differences come down to the two core algorithms: gram-based (as this version) works well for more creative painted styles, and patch-based (as original) works quite well for higher fidelity photos—as indicated by your other experiment: https://twitter.com/netputing/status/713879168866512900
I've just recently added a new --variety flag that allows the patch-based approach to perform better in creative painted styles too, or texture generation. This means for the first time you can blend between fidelity and creativity: https://github.com/alexjc/neural-doodle
Here's an example rendering of your lily-pond with --variety=0.5 and --semantic-weight=1.0:

The version with --variety=0.0 (as from the paper pre-print) is a bit more accurate but also more boring:

It's great to have such a wide variety of projects to be able to compare results! Thanks for doing this too, it drives progress forward very quickly indeed ;-)


Typing Master Clone

Is your feature request related to a problem? Please describe.
Typing Master Clone
Describe the solution you'd like.
A web app using HT,L5, CSS3, JS.
Describe alternatives you've considered.
None
Add any other context or screenshots about the feature request here.
None

/assign


Allow exporting when events are defined

Something something events require registry, maybe a static instead?

Exporting is now possible with no events, but if any actual emitting or listening is to be done then the plugin must be used, else panic.


Correct use of resources children

Hey Guy,
  Could I ask you a question if you have time? Sorry I realise this should have been an issue in it's own right.

I'm using SpringDataRestAdapter to interact with my spring data rest api. From the screen shot you can see that I've just loaded all the questions and I'm attempting to load their answers (one-to-many) relationship. In the debug window the _embeddedItems array is an array of Questions with _links to each questions answers. I'm trying to prompt SpringDataRestAdapter to autoload the answers by passing 'answers' as an argument to the processWithPromise call but to no avail.
The urls look like http://localhost:8080/api/questions http://localhost:8080/api/question/1/answers
The Question.loadAnswers(question) call is commented out... It works in that it loads the question's answers but I felt I was using the framework incorrectly.
Here is the method
Question.loadAnswers = function (question) {

            question.answers = question.answers? question.answers : [];

            angular.forEach(question._links.answers, function (answerLink) {
                var deferred = $http.get(answerLink);
                return SpringDataRestAdapter.processWithPromise(deferred).then(function (data) {
                    question.answers = data._embeddedItems;
                });
            });
        };

Congratulations on an excellent piece of coding Guy! I've also posted this question up on stackoverflow in case the issue is with my understanding of promises as opposed to how to use the framework :)
http://stackoverflow.com/questions/36072090/springdatarestadapter-load-child-resources
Thanks, Mark.

Hi Mark,
sorry from my late response and thanks a lot for the praise :). You need to set the recursive flag on the fetch function such that the following call will fetch the answers properly:
SpringDataRestAdapter.process(deferred, 'answers', true).then(...)

You can see the documentation here https://github.com/guylabs/angular-spring-data-rest#the-fetch-method-parameters and here you can see a running example https://github.com/guylabs/angular-spring-data-rest/blob/master/test/angular-spring-data-rest-provider.fetch.spec.js#L148
I hope this solves your issue.
Thanks and regards,
Guy

Yer a gentleman Guy,
       Thanks for getting back to me, aye I found that in the docs at

some stage. Thanks for the framework, it's made my life a helluva lot
easier!
Thanks,
Mark.
On Tue, Apr 5, 2016 at 8:07 PM, Guy Brand<EMAIL_ADDRESS>wrote:

Hi Mark,
sorry from my late response and thanks a lot for the praise :). You need
to set the recursive flag on the fetch function such that the following
call will fetch the answers properly:
SpringDataRestAdapter.process(deferred, 'answers', true).then(...)
You can see the documentation here
https://github.com/guylabs/angular-spring-data-rest#the-fetch-method-parameters
and here you can see a running example
https://github.com/guylabs/angular-spring-data-rest/blob/master/test/angular-spring-data-rest-provider.fetch.spec.js#L148
I hope this solves your issue.
Thanks and regards,
Guy
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/guylabs/angular-spring-data-rest/issues/22#issuecomment-205950970

Hey Mark,
ok cool that you found out yourself and thanks for using it! :)
Regards,
Guy


Ignore this, wrong base selection.

A thousand of apologies, dear Senipah.  Trying to rebase my forked repository, I forgot to change the bases and the new branch was requested on your original repo.  Apologies.


Private key & file transfers

Hi,
I'm trying out flightplan and couldn't transfer files. My whole private key is being inserted for the -i option rather than the key path.
rsync --files-from /tmp/346da2ce-db08-4e6c-b508-d36eb1f41adc -az --rsh="ssh -p22 -i -----BEGIN RSA PRIVATE KEY-----[PRIVATE KEY CONTENTS]-----END RSA PRIVATE KEY-----
" ./ core@<IP_ADDRESS>:/home/sage/.ssh/authorized_keys
localhost > Warning: Identity file -----BEGIN not accessible: No such file or directory.
localhost > ssh: Could not resolve hostname rsa: Name or service not known
localhost > rsync: connection unexpectedly closed (0 bytes received so far) [sender]
localhost > rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.0]
localhost ● failed (255)
● Command exited abnormally on localhost

It looks like this happens in transport/ssh.js -
config.privateKey =
  fs.readFileSync(config.privateKey, { encoding: 'utf8' });

and then in transport/shell.js -
var sshFlags = (remote.privateKey ? ' -i ' + remote.privateKey : '');

I added  "config.privateKeyName" in ssh.js before reading from the file and referenced that in shell.js and it's working for me now.

Will fix. Thanks for reporting.

0.6.1 has been released and should fix this problem :beers:

It looks like the problem still occurs
localhost > Warning: Identity file -----BEGIN not accessible: No such file or directory.
localhost > ssh: Could not resolve hostname rsa: Name or service not known
localhost > rsync: connection unexpectedly closed (0 bytes received so far) [sender]
localhost > rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.1]
localhost ● failed (12)
● Command exited abnormally on localhost

> fly --version
0.6.1

Make sure that the local version is also 0.6.1. You can verify this easily by running ./node_modules/.bin/fly --version. Are you sure that you're pointing to an exisiting file, try an absolute path if in doubt.

Yes, you are right. Sorry for the noise ;)


Fix and update CI runs

Exception for sanity tests, update molecule and make sure new distros will stay supported/old ones are removed.

The problem with the kubernetes roles is caused by a non available release bigger then 1.28.2. The newest releases of kubernetes >= 1.29.0 are not published in the "old" apt respository anymore.
deb [signed-by=/etc/apt/keyrings/kubernetes-apt-keyring.gpg] https://apt.kubernetes.io/ kubernetes-xenial main

This can easily be verified with: apt-cache policy kubelet
kubelet:
  Installed: (none)
  Candidate: 1.28.2-00
  Version table:
     1.28.2-00 500
        500 https://apt.kubernetes.io kubernetes-xenial/main amd64 Packages
     1.28.1-00 500
        500 https://apt.kubernetes.io kubernetes-xenial/main amd64 Packages
     1.28.0-00 500
        500 https://apt.kubernetes.io kubernetes-xenial/main amd64 Packages
     1.27.6-00 500
        500 https://apt.kubernetes.io kubernetes-xenial/main amd64 Packages

The new repositories can be found at: https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/#install-using-native-package-management
More infos https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/change-package-repository/
Those repositories have the kubernetes version pinned within the repo url. This can be nice, but not for our setup and it can case problems to upgrade from older versions.

Yes, the apt.kubernetes.io mirrors will also be likely going away soon (or are already offline by now).

@MarkusTeufelberger please review those changes.


POC: Sparse protocol support

Quick and dirty way to support sparse protocol and set it by default.
The proper way is to support registry selection and protocol type detection.

Very interesting, thanks for putting this POC together!
Regarding the protocol type detection, is there a good way for us to use crates_index to do that? Or is that something that crates_index will have to build and expose to us?
Also, by using sparse protocol by default, are we likely to expose Windows users to this bug? https://github.com/frewsxcv/rust-crates-index/issues/126

I guess it's one of the internal things that cargo should "cratelize" for reusing. It need to parse through the hierarchy of config.toml to figure out the index URL of the specified registry. Then we can determine if it's sparse or not by checking the sparse+ prefix.
Windows should be fine since reqwest handles it anyway.

Since this PR, the crates_index became unmaintained but then thanks to the author of tame-index, we switched to that crate and gained sparse index support in #506.
The next release of cargo-semver-checks will have sparse index support 🎉 Thanks for the help and for your patience on this!


please add dialog tag (new tag in chrome 25)

please add dialog tag (new tag in chrome 25)

This issue was imported from Google Moderator
Moderator votes: +4
Issue added by Ali.MD on 2013-08-16
To vote this issue up or down, simply include +1 or -1 in your comment.

+1

Already covered: http://caniuse.com/#feat=dialog


WIP: Change edalize branch to surelog_esr

This PR changes edalize version to version after rebasing with newer ESR version.
Signed-off-by: Kamil Rakoczy<EMAIL_ADDRESS>

This PR is obsolete, closing.


Introduce support for Waiting for given cluster conditions

As a test writer of components running on Kubernetes, it would be extremely useful to have the capability to wait for one or more cluster conditions before proceeding in the test.
A framework for Waiting
A new package klient/wait could be the starting point for an API to express conditions for waiting by leveraging the wait package in API machinery "k8s.io/apimachinery/pkg/util/wait"):
package wait

func For(cond func() (bool, error)){...}

So, a test writer may have condition as follows:
func TestSomething(t *testing.T){
    wait.For(t, func() (bool, error) {
        var ns coreV1.Namespace
        cfg.client.List(ns)
        ...
    )}
}

Pre-defined conditions
The framework could have a collection of pre-defined conditions that can be used by test writers:
func TestSomething(t *testing.T) {
   var pod coreV1.Pod
   wait.For(PodReadyCondition(pod))
}

@harshanarayana I missed that ping. Sorry.

No worries @vladimirvivien Let me open a PR with some prototype for a feedback.

@vladimirvivien I have opened a draft PR for the same. Hope the changes in there matches with what you had in mind for this behavior.


[SPARK-9470]Removed redundant public keyword from Function interface …

…for JAVA api

Can one of the admins verify this patch?

Can one of the admins verify this patch?

I agree it's redundant, and I don't write public on my Java interface methods. However, some people do on the grounds that it's clearer (they are in fact public, not package-private). I don't think it's worth changing. Do you mind closing this PR? Also, please have a look at https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark

I understand your concern, closing the PR.


JDBC4 is support or not?

Hi,
I found hikariCP has one property：
_connectionTestQuery
If your driver supports JDBC4 we strongly recommend not setting this property. This is for "legacy" drivers that do not support the JDBC4 Connection.isValid() API. This is the query that will be executed just before a connection is given to you from the pool to validate that the connection to the database is still alive. Again, try running the pool without this property, HikariCP will log an error if your driver is not JDBC4 compliant to let you know. Default: none
I use clickhouse-jdbc with hikariCP, so I want to know does this jdbc support jdbc4?

I use clickhouse-jdbc with hikariCP, so I want to know does this jdbc support jdbc4?

Yes. Did you run into any issue?

I use clickhouse-jdbc with hikariCP, so I want to know does this jdbc support jdbc4?

Yes. Did you run into any issue?

I want to confirm that 'connectionQueryTest' is needed to anything like 'SELECT 1' or not.


useSuspenseQuery: Server functions cannot be called on initial render.

I've swapped out useQuery for useSuspenseQuery and I'm now getting the following error:
ApolloError: Server Functions cannot be called during initial render. This would create a fetch waterfall. Try to use a Server Component to pass data to Client Components instead.
This is happening (assumption noted) because I am calling a server function to retrieve my authorization token when creating my authLink for the client side apollo client:
const authLink = setContext(async (_, { headers }) => {
    const token = await getAuthToken(); <-- Server function

    return {
      headers: {
        ...headers,
        authorization: token ? `Bearer ${token}` : "",
      },
    };
  });

This error does not get shown when using useQuery, only when using useSuspenseQuery. I've attempted other methods of retrieving my token but unfortunately cannot reliably do this.

Created a route handler to retrieve the token. This works for the client side, but fails on the initial server request due to the path not being absolute. I know I can work around this, but would prefer not to if possible.
I'm unable to use 3rd party cookie libraries to read the token on the client side as it is httpOnly (which I'd prefer to keep as is for obvious reasons).
I could pass the token in as a prop from the ApolloWrapper, but unfortunately I have no way to reliably ensure that the token is regularly updated (i.e. read once on mount, it will become stale after a period of time).

I use PreloadQuery (as covered in the docs):
Parent component:
<PreloadQuery
       query={QueryDocumentDocument}
       variables={{
         take: 10,
         skip: 0,
       }}
     >
       <Suspense fallback={<ChildComponentLoading />}>
         <ChildComponent />
       </Suspense>
     </PreloadQuery>

Child component:
const { data } = useSuspenseQuery<Query, QueryVariables>(
    QueryDocument,
    {
      variables: {
        filter: {
          take: pageSize,
          skip: (currentPage - 1) * pageSize,
        },
      },
    },
  );

Any assistance would be greatly appreciated.

Thanks for your response. The path I've decided to take, based on your suggestion, is altering my API so that it can accept either cookie or header based authentication.
The RSC client sends the header based auth, and the 'client' client sends credential based cookies. NextJS not making things easy but at least I have a workaround for the timebeing.
I still seem to be getting an unauthorized response on my very first RSC request, but I'll just have to live with that - I'm no longer getting the error I mentioned above.
Appreciate your help!

is there a approach to solve it ??

i think it's possible, the rest of my app does this but now I am suddenly getting an error for one page, stay posted

you just need to await the prefetchedQuery in the Page, that clears the client error @ikaasraa

you just need to await the prefetchedQuery in the Page, that clears the client error @ikaasraa

Please send some example

In the SRC (Page)
  const bobPromise = queryClient.prefetchQuery({
    queryKey: bobQueryKey,
    queryFn: () => getBob(accessToken),
  } as any);

  const promises = [bobPromise];

  await Promise.all(promises);

In the Client
  const { data: bobData } = useSuspenseQuery({
    queryKey: bobQueryKey,
    queryFn: () => getBob(accessToken as any),
  });

Boom, no error @ikaasraa

@withintheruins14 that looks like TanStack Query code, not Apollo Client code. Are you sure you're in the right place?

@withintheruins14 that looks like TanStack Query code, not Apollo Client code. Are you sure you're in the right place?

you're right! I was just realzing this in the tub - anyhow I was making my rounds answering this question for people who might be stuck...! Deleting my response


Pr val pipeline changes

Build Pipeline changes for imodel02 PR validation.
Original PR: https://github.com/iTwin/itwinjs-core/pull/4662

Please link issue.


Incorrect build/run instructions for Listing2

In the main Readme file, under the heading "Listing2", it says to "Change into the Listing1 directory". I believe that it should be "Change into the Listing2 directory".
Further, it says to do "make ctest -R commit or make commit_tests". I think you first need to do "cmake .", so it should be "cmake . make ctest -R commit or make commit_tests".
It would also be more readable if these commands were on their own lines and formatted as code.
(These are obviously minor issues, but I suspect that you want to make these examples as correct as possible.)

Corrected README instructions and fixed formatting for issue reported by @magnus-ekman with ffbdab998e5a8500eb2ee684ad87f21bce4baf48 commit.


msal-browser sample not working

Please follow the issue template below. Failure to do so will result in a delay in answering your question.

Library

[ ]<EMAIL_ADDRESS>or<EMAIL_ADDRESS>[x ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>
Important: Please fill in your exact version number above, e.g<EMAIL_ADDRESS>Framework
If you are using a framework, please provide the framework and version (e.g. Angular v8, React v16, etc).
React v16
Description
The sample doesn't appear to work with the packages in npm. When are you planning to synchronize these?
The public package contains handleCallbackResponse whereas the sample now contains handleCallbackPromise, as well as a bunch of error handling and interactionrequired stuff.
Can you advise on how to proceed? I am desperately trying to get our app running in the Teams iframe now that the redirect is fixed. The sample code is all over the place though and I am not sure which one to use.
yarn deps:
info Direct dependencies
├─<EMAIL_ADDRESS>└─<EMAIL_ADDRESS>info All dependencies
├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>└─<EMAIL_ADDRESS>Done in 26.23s.
Security
No
Regression
Probably
Configuration
N/A
// Provide configuration values here.
// For Azure B2C issues, please include your policies.

Reproduction steps

yarn add @azure/msal-browser
try to incorporate latest sample VanillaJSTestApp2.0
missing deps

Expected behavior
The sample actually works.
Browsers
No

@taysco the samples in the repository are dev samples, and are meant to work with the local version of the library. We have a sample here which is intended to be current with the npm package.

Thanks. When are you planning the push the new versions? There's a lot of new functionality in the newer releases that really need to be publicly available. I don't really want to set up a npm feed just for this :) This feature should really be prioritized imo.

@taysco Sorry for the delay, we are preparing for a full release and I haven't been able to do a new beta version just yet. I will try to get a new version out shortly.

@taysco I have pushed a new release of msal-browser and msal-common to npm today. I am working on updating the quickstart sample.

Awesome, thank you very much. Great work btw.


Only display failed test

Can there be an option that the output only display failed tests?

Hmm... a new report format might be the best choice for this. In fact, you should try the dotted reporter. In you helper,
Turn.config.format = :dotted

Or on the command line
$ turn -D ...

I think that does what you want.

That does it. Thanks!


Add CPU and disk space killing to performance monitoring

In the same way that we can kill jobs that take too much memory, we need to be able to set thresholds for CPU time used, wall time, and disk space used so that we kill jobs before the pilot or sites do.

Right now we have a memory monitoring (MaxRSS and MaxVSize) that is shipped along the job.
On the agent side, there is a "config.JobStatusLite.stateTimeouts" where we specify for how long jobs can be in the running/pending state (the action I believe to be a condor_rm or close to it).
For disk space, there is nothing monitoring it from the WMAgent side.
If we should implement it, then leave it open. @ticoann @ericvaandering ?

@ericvaandering, Eric can we close this?


feat: install utilities

[x] aptitude
[x] arp
[x] cron
[x] curl
[x] dnsutils
[x] flatpak
[x] htop
[x] iotop
[x] locate
[x] neofetch
[x] net-tools
[x] nmap
[x] resolvconf
[x] snap (with core)
[x] software-properties-common
[x] ssh-server (openssh-server)
[x] traceroute
[x] vim
[x] wget
[x] whois
[x] xclip

:tada: This issue has been resolved in version 1.9.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


fix: correct the sentence error in README.md

The word thanks is plural in this case.
Types

[x] 🐛 Bug Fixes

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

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

Hi, @harlentan
thanks for your contribution, we found that thanks goes to is more popular use on the web, see the results here https://textranch.com/361074/special-thanks-go-to/or/special-thanks-goes-to/.
It is both okay, but for now, we still want to use the word because it's better known.