example of stream_audio_v3

Hi, and thanks for this good library!
I managed to get the audio on the speakers, so I know it works, but I would like to use generationOptions.
I cannot find a good example, I'm trying something like :
generation_options = GenerationOptions(
latencyOptimizationLevel=1,   # Adjusts latency optimization
stability=0.5,                # Example stability value
similarity_boost=0.8,         # Example similarity boost
style="informative",           # Example style
use_speaker_boost=True,       # Enables speaker boost
model='eleven_multilingual_v2', # Specifies the model
output_format='mp3_highest',  # Sets the output format
seed=42,                      # Random seed for generation
language_code='fr-FR',        # Language code for the audio
pronunciation_dictionaries=None # Optional pronunciation dictionaries
)
voice.stream_audio_v3(message, None, generation_options)
but I get

  File "\venv\lib\site-packages\elevenlabslib\helpers.py", line 295, in __post_init__
if var is not None and (var < 0 or var > 1):

TypeError: '<' not supported between instances of 'str' and 'int'
What am I doing wrong?
Thanks in advance

You can check the documentation for the GenerationOptions class for a more in-depth explanation of all the parameters.
Style is actually a float value, between 0 and 1 - you can look at elevenlabs' own docs for more information.


Crash on Nil Status

Describe the Bug
Error while running event LtnManager::on_tick (ID 0)
LtnManager/scripts/ltn-data.lua:221: attempt to index field 'status' (a nil value)
stack traceback:
LtnManager/scripts/ltn-data.lua:221: in function 'callback'
flib/table.lua:196: in function <flib/table.lua:169>
(...tail calls...)
LtnManager/scripts/ltn-data.lua:544: in function 'iterate'
LtnManager/control.lua:157: in function <LtnManager/control.lua:153>
To Reproduce
Steps to reproduce the behavior:

Stop Trains from exiting Depot
Wait.  Once all trains have returned it may take a few minutes to occur.
Was Pasting new Depot setup in case that helps.

Be certain to reproduce the issue on the same save file that you upload.
Save file & Username
Upload the save file where the bug occured. If the file is too large for GitHub, use an alternative file service.
Please also provide your in-game username so I can reproduce the conditions exactly.

The mod LTN Manager [ALPHA] (0.3.4) caused a non-recoverable error.
Please report this error to the mod author.
Error while running event LtnManager::on_tick (ID 0)
LtnManager/scripts/ltn-data.lua:455: attempt to concatenate field 'to' (a nil value)
stack traceback:
LtnManager/scripts/ltn-data.lua:455: in function '?'
LtnManager/scripts/ltn-data.lua:544: in function 'iterate'
LtnManager/control.lua:157: in function <LtnManager/control.lua:153>

I apologize for the huge amount of bugs recently! But that's why there's a giant [ALPHA] sticker on the title. :D
Anyway, fixed for the next release. This bug was gnarly and took me almost two hours to solve!


Discussion on license of our package

Here is the issue for discussion of everything related to the license used for our package, as mandated by milestone 4's requirement.

agreed on the changes

Here is my suggestion and justification:
MIT License: This license is easy to understand and widely used for open-source projects. It lets people do a lot with your project, like using it for business, changing it, sharing it with others, and even allowing them to give permission to others to use it. They don't have to use the same license if they change your project and share it. Also, there are only a few rules about how to show copyright information.

I  would also agree with the MIT License in this case (although, we might still change it in the future if we find one that suits our project better). However, because of the level of our package, I don't think there will be any problem by using a license for open-source projects.

@atabak-alishiri @Marcony1 I think both of you raised really good points for keep using the MIT License.
Personally, I would prefer GNU GPL v2/3, but compared to MIT, in this case I think it is adding unnecessary complication and limitation such as requiring the derived works to be only published under the same license.
As this package is meant to be a learning example, a short and simple license only requiring preservation of our copyright and license notices (i.e. MIT License) would suffice.

So, I believe we all agree on using the MIT license for our software. Since the package doesn't include creative content, we won't need a creative license, right?

I think so. Of course we can use CC licenses for our non-code components (i.e. documentations, but that's arguable as they are generated from source codes as well), but it seems like CC do not recommend licensing software using their licenses.
Also, from https://choosealicense.com/non-software/:

... Any open source software license or open license for media (see above) also applies to software documentation...

So, unless we have substantial contents in this project that is not related to the package itself, I would say there is no need a second license.

Closing this issue as all members unequivocally agreed to keep using the MIT License.


kubectl port-forward for Service should fail if no Pods are Ready

What happened: kubectl port-forward to a Service when no Pods in the Service were Ready. kubectl appears to port-forward to the first Pod selected by the Service when they are sorted alphabetically.
What you expected to happen: The port-forward should fail. When a Pod is not ready, a Service will not load balance to it: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/

When a Pod is not ready, it is removed from Service load balancers.

Failing the port-forward to a Service in which no Pods are ready would be in line with the Service behavior, and would be less unexpected.
In my case, I just uncovered a bug in which we are using a port-forward to bootstrap a Deployment via its Service. Because kubectl port-forward was succeeding, we were assuming we had reached a Pod that was ready to receive requests, but actually, we had a race condition where we were reaching a Pod that was sometimes not yet Ready, which failed our bootstrapping script.
How to reproduce it (as minimally and precisely as possible):

apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    app: nginx
  name: nginx
spec:
  replicas: 3
  selector:
    matchLabels:
      app: nginx
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: nginx
        ports:
        - containerPort: 80
        readinessProbe:
          exec:
            command:
            - /bin/false
          initialDelaySeconds: 5
          periodSeconds: 5
---
apiVersion: v1
kind: Service
metadata:
  labels:
    app: nginx
  name: nginx
spec:
  selector:
    app: nginx
  ports:
    - protocol: TCP
      port: 80
      targetPort: 80

$ kubectl get pod -l app=nginx
NAME                     READY   STATUS    RESTARTS   AGE
nginx-57b76f6dd8-868dq   0/1     Running   0          12s
nginx-57b76f6dd8-bjqbg   0/1     Running   0          12s
nginx-57b76f6dd8-kkmns   0/1     Running   0          12s

$ kubectl get service nginx
NAME    TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)   AGE
nginx   ClusterIP   <IP_ADDRESS>   <none>        80/TCP    3m49s

$ kubectl get endpoints -l app=nginx
NAME    ENDPOINTS   AGE
nginx               4m33s

$ kubectl port-forward service/nginx 8080:80
Forwarding from <IP_ADDRESS>:8080 -> 80
Forwarding from [::1]:8080 -> 80

$ curl localhost:8080
<!DOCTYPE html>

<title>Welcome to nginx!</title>

Welcome to nginx!

If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.

For online documentation and support please refer to
nginx.org.

Commercial support is available at
nginx.com.

Thank you for using nginx.

# Logs of the first Pod, alphabetically:
$ kubectl logs nginx-57b76f6dd8-868dq
<startup logs...>
<IP_ADDRESS> - - [19/Apr/2023:19:02:01 +0000] "GET / HTTP/1.1" 200 615 "-" "curl/7.68.0" "-"

# Behavior from within the cluster differs (this is a shell in an alpine Pod in the same namespace):
/ # dig +short +search nginx
<IP_ADDRESS>
/ # curl nginx
curl: (7) Failed to connect to nginx port 80 after 1029 ms: Couldn't connect to server

Anything else we need to know?:
Environment:

Kubernetes client and server versions (use kubectl version):Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.15", GitCommit:"b84cb8ab29366daa1bba65bc67f54de2f6c34848", GitTreeState:"clean", BuildDate:"2022-12-08T10:49:13Z", GoVersion:"go1.17.13", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"23+", GitVersion:"v1.23.17-eks-ec5523e", GitCommit:"d9e9b09276855a532739ef8cb728194aa145430b", GitTreeState:"clean", BuildDate:"2023-03-20T18:46:36Z", GoVersion:"go1.19.6", Compiler:"gc", Platform:"linux/amd64"}

Cloud provider or hardware configuration: EKS
OS (e.g: cat /etc/os-release): Ubuntu 20.04.6 LTS (Focal Fossa)

/triage accepted
/priority backlog
/assign


"wheel" scrolling doesn't work when over pinned columns

When your mouse is over unpinned columns scrolling with the mouse wheel works as expected, if you move the mouse over a pinned column it stops working. You can see this by testing a mouse wheel with the pinning example in the documentation.

thanks for raising. this is a dupe :)
https://github.com/ceolter/angular-grid/issues/14

I just noticed this today. As the issue #14 and this one have been closed, does that mean there won't be any scrolling on the pinned columns?
BTW, thank you for creating such an awesome grid!

#14 is open!!


CSI Camera not working, deciding to use USB camera

Hi everyone!
I am currently working with the jetson orin nano and intended on using a csi camera for inferencing and using jetson-containers. However my camera (Raspberry Pi V2-attached) for some reason is not being detected by my orin. I am running with jetpack 6 right now and have heard that camera issues like this occur. I am wondering if I could use a usb camera and should I downgrade to jetpack 5 to get the csi camera working instead? Ideally, I don't want to have to downgrade, but will more than likely have to if the usb camera doesn't work. Thanks everyone!

Hi @Syncron19, how are you trying to use your MIPI CSI camera from code?  If you started your container with jetson-containers run, it will automatically mount the Argus daemon's socket, so CSI camera can be used inside container through GStreamer (nvarguscamerasrc) or libargus:
https://github.com/dusty-nv/jetson-containers/blob/e77e05ebcbbb15e315bbf8b5bcd160946995a12c/run.sh#L76
Can you check that it works outside of container, using nvgstcapture-1.0 program?

Hey Dusty, so I downgraded down to jetpack 5 today and it works. For some reason, I couldn't get the camera to work at all on the Orin while it was using Jetpack 6. I don't know why that is the case, but for now it will be okay.  To answer your question, nvgstcapture-1.0 did not produce anything despite running "ls /dev/video*" giving me /dev/video0.
I was using a code that was given to me by a friend who is also using the Jetson Orin
docker run -it --runtime=nvidia --device=/dev/video0:/dev/video0
-v /usr/lib/aarch64-linux-gnu/libargus_camera.so:/usr/lib/aarch64-linux-gnu/libargus_camera.so
main_dock


Uploading a file should (optionally) auto-create required directories

Using the command line client or the REST API, there should be an option or it should be standard behaviour that a file upload will create the missing directory structure. Alternatively, a new endpoint should be added to the API to allow creating a directory.
Example: using a fresh container
ubuntu@server:~$ lxc file push somefile test-container/tmp/nonexistingdirectory/somefile
error: open: No such file or directory
errno: 2

If this is not supported, offline file management is basically impossible as creating directories is a basic  required operation.

I would suggest closing this issue in favor of a new issue that describes an addition to the existing API, allowing the creation of directories with custom modes and ownerships.

That's what @tych0 working on, we'll close this and the related issues all at once that's done.
The solution will be support for creating directories, support for listing directories and a flag to create any missing paths along the way in the API. The client side will be done through the -p flag for recursive creation and the -r flag to push and pull to copy a full tree.


update hekatomb to install with pip

hekatomb is now available on pypi to simplify its installation

I moved Hekatomb into a page dedicated to DPAPI
Thank you for the Pull Request 👍

Nice, that's perfect ;) thanks


Make it clear that the user must have the app installed for the bot to be able to create a conversation with the user

Type of issue
Missing information
Feedback

aadObjectId only works if the user has the app installed. This must be clarified.
Page URL
https://learn.microsoft.com/en-us/microsoftteams/platform/bots/how-to/conversations/send-proactive-messages?tabs=dotnet#create-the-conversation
Content source URL
https://github.com/MicrosoftDocs/msteams-docs/blob/main/msteams-platform/bots/how-to/conversations/send-proactive-messages.md
Author
@surbhigupta
Document Id
8097fcbd-adcc-ce49-a378-426c65af9296

Hi @aosolis - Thanks for raising the query.
We will look into it and let you know the updates.

Hi @aosolis!
Thanks for raising the query.
In the document, just before the sub-heading Create the conversation, we have added a detailed note on 'aadObjectId'.
Do you think repeating this information in 'Create the conversation' section will add more clarity?
Kindly clarify.
Thanks in advance.

Hi @aosolis! Thanks for raising the query.
In the document, just before the sub-heading Create the conversation, we have added a detailed note on 'aadObjectId'.

Do you think repeating this information in 'Create the conversation' section will add more clarity? Kindly clarify. Thanks in advance.

Hi @aosolis,
Gentle reminder! We are waiting for your response on this.

Hi @aosolis! Thanks for raising the query.
In the document, just before the sub-heading Create the conversation, we have added a detailed note on 'aadObjectId'.

Do you think repeating this information in 'Create the conversation' section will add more clarity? Kindly clarify. Thanks in advance.

Hi @aosolis,
As discussed with the team. It is already mentioned in the document. Could please confirm whether it should repeat again in the document?

Hi @aosolis! Thanks for raising the query.
In the document, just before the sub-heading Create the conversation, we have added a detailed note on 'aadObjectId'.

Do you think repeating this information in 'Create the conversation' section will add more clarity? Kindly clarify. Thanks in advance.

@v-ramyas5 - This is already documented, so let's close this issue.

We are closing this issue for now, please feel free to reopen it, if required.


Title: Custom Cursor

Is your feature request related to a problem? Please describe.
I'm bored with the normal cursors, I mean like this is an AI era , everything is getting updated ,then why are we still using normal default cursors when you can use custom cursors with effects .
Describe the solution you'd like.
I want to add a custom Intractive cursor for the website, this not only makes the website look cool but also makes it UI more professional.
Describe alternatives you've considered.
Default is boaring
Add any other context or screenshots about the feature request here.
No response

Kindly review the PR.


SPython and SAW support

Azure CLI should use SPython in order to be able to run on SAW (Secure Admin Workstation).

SAW support


fix setPage call to long

It's too long when call setPage method if is running other animation.

Summary
It's too long when call setPage method if is running other animation. I thought its waiting for other animation frame. So, I tried changerequestAnimationFrame to setTimeout.
It looks smoother.

Test Plan

What's required for testing (prerequisites)?
What are the steps to reproduce (after prerequisites)?
Compatibility

OS
Implemented

iOS
✅

Android
✅

Checklist

[x] I have tested this on a device and a simulator
[x] I added the documentation in README.md
[x] I updated the typed files (TS and Flow)

@alpha0010 WDYT ?

setImmediate() might be more appropriate, but yes, seems fine.

setImmediate() might be more appropriate, but yes, seems fine.

Yes,I tried it.setImmediate() is more appropriate.


Does refresh token expire for OneDrive API?

Does the refresh token ever expire for OneDrive API or is it permanent?
Is this statement valid: As long as I have the refresh token I can use it to get fresh access tokens and connect to OneDrive API (unless app permission is manually removed by account holder from https://account.live.com/consent)?

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

ID: 210daf87-f00d-db74-cdb0-279d033d29de
Version Independent ID: 03050364-41d2-e475-69b1-08b554ade330
Content: Authorization for OneDrive API via Microsoft Graph - OneDrive dev center
Content Source: docs/rest-api/getting-started/graph-oauth.md
Product: onedrive
GitHub Login: @JeremyKelley
Microsoft Alias: JeremyKe

Here is the documentation link from AAD that talks about refresh tokens and expiration: https://docs.microsoft.com/en-us/azure/active-directory/develop/refresh-tokens


Dart CLI command Change

Tracking Dart, in the first 'Hello, World!' application, unit testing with 'pub run test' isn't working.
Instead of 'pub' I used 'dart run test' to start unit test for this excercise.

`PS C:\Users\grim\Exercism\dart\hello-world> dart run test
Resolving dependencies...

_fe_analyzer_shared 19.0.0
analyzer 1.3.0
args 2.0.0
async 2.5.0
boolean_selector 2.1.0
charcode 1.2.0
cli_util 0.3.0
collection 1.15.0
convert 3.0.0
coverage 1.0.2
crypto 3.0.0
file 6.1.0
glob 2.0.1
http_multi_server 3.0.0
http_parser 4.0.0
io 1.0.0
js 0.6.3
logging 1.0.1
matcher 0.12.10
meta 1.3.0
mime 1.0.0
node_preamble 2.0.0
package_config 2.0.0
path 1.8.0
pedantic 1.11.0
pool 1.5.0
pub_semver 2.0.0
shelf 1.1.0
shelf_packages_handler 3.0.0
shelf_static 1.0.0
shelf_web_socket 1.0.1
source_map_stack_trace 2.1.0
source_maps 0.10.10
source_span 1.8.1
stack_trace 1.10.0
stream_channel 2.1.0
string_scanner 1.1.0
term_glyph 1.2.0
test 1.16.8
test_api 0.3.0
test_core 0.3.19
typed_data 1.3.0
vm_service 6.1.0+1
watcher 1.0.0
web_socket_channel 2.0.0
webkit_inspection_protocol 1.0.0
yaml 3.1.0
Downloading test 1.16.8...
Downloading web_socket_channel 2.0.0...
Downloading test_core 0.3.19...
Downloading test_api 0.3.0...
Downloading shelf_packages_handler 3.0.0...
Downloading pool 1.5.0...
Downloading package_config 2.0.0...
Downloading node_preamble 2.0.0...
Downloading js 0.6.3...
Downloading io 1.0.0...
Downloading boolean_selector 2.1.0...
Downloading crypto 3.0.0...
Downloading source_maps 0.10.10...
Downloading source_map_stack_trace 2.1.0...
Downloading matcher 0.12.10...
Downloading yaml 3.1.0...
Downloading shelf_web_socket 1.0.1...
Downloading coverage 1.0.2...
Downloading glob 2.0.1...
Downloading file 6.1.0...
Downloading analyzer 1.3.0...
Downloading watcher 1.0.0...
Downloading pub_semver 2.0.0...
Downloading cli_util 0.3.0...
Downloading _fe_analyzer_shared 19.0.0...
Changed 47 dependencies!
Precompiling executable...
Precompiled test:test.
00:01 +1: All tests passed!`

edit: type-o

@bzelban Dart 2.12 did not deprecate pub run. It seems your Windows machine does not have the full path to the Dart executables.
I don't have a Windows machine, but the latest version of dart 2.12.2 still has both dart and pub commands. I recommend you double check your version of dart and the folder where dart is located. Can you find pub?

@bzelban Dart 2.12 did not deprecate pub run. It seems your Windows machine does not have the full path to the Dart executables.
I don't have a Windows machine, but the latest version of dart 2.12.2 still has both dart and pub commands. I recommend you double check your version of dart and the folder where dart is located. Can you find pub?

I'm using Dart SDK version: 2.15.0-6.0.dev (dev)  macos_x64 on an M1 Mac, and came across the same issue which brought me here.
I suppose newbies can somehow find their way here or have the foresight to add pub to their path, but I think the majority of learners would get stuck trying to test and leaving out "dart test" in the HELP.md is defeating the purpose of that file.

@MSoup I agree the docs need to be updated.

Fixed in #348


chore: update formatter conf and apply formatter

Apply the changes proposed as part of formatter config updates in #117
Proposed Changes

Run the formatter on the global codebase

@rajitha1998 @mbcse this should fix the spacing issues, PTAL


Fails to pull image if it already exists with different schema version

Description
While running sonobuoy conformance tests I noticed image pull failures:
Failed to pull image "k8s.gcr.io/pause:3.1": rpc error: code = Unknown desc = Error committing the finished image: image with ID "da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e" already exists, but uses a different top layer: that ID is already in use

Most likely this happens because my setup has the same pause image with a different name.
Steps to reproduce the issue:

setup kubernetes with a custom pause image (that is exactly the same as "k8s.gcr.io/pause:3.1")
run sonobuoy
pods with "k8s.gcr.io/pause:3.1" fail

Describe the results you received:
cri-o fails to pull image.
Describe the results you expected:
image pull succeeds.
Output of crio --version:
crio version 1.11.1
commit: ""

Additional environment details (AWS, VirtualBox, physical, etc.):

Kubernetes 1.11.1 (Kontena Pharos v1.3.0-beta.1 , https://github.com/kontena/pharos-cluster/releases/tag/v1.3.0-beta.1)
CentOS 7.5
DigitalOcean

@nalind could you take a look at this? looks like something that shouldn't happen :confused:

@mtrmac PTAL also

The failure is from c/image/storage/storageImageDestination.Commit, because an image with the same image ID (config digest) exists, but the top layer is different on disk and in the pulled image.
That, indeed, should not generally happen (the same config implies the same list of layers). https://github.com/containers/image/pull/472 would be a possible explanation for v2s1 images, but this is v2s2.
It would be interesting to compare the image’s config.json and the list of layer IDs, and layer DiffIDs, in CRI-O storage. And, of course, the two differing “top layer” IDs.

Most likely this happens because my setup has the same pause image with a different name.

AFAICS naming should not matter, and neither should if the image has been re-compressed when copying to a different registry.
(But, of course, something has gone wrong.)

My best guess: Does the ‘custom pause image (that is exactly the same as "k8s.gcr.io/pause:3.1")’ happen to actually be stored using the “schema 1” format (e.g. in a schema1-only registry)? That does sound fairly unlikely, but it is the only explanation I can think of right now, assuming that the code works as intended. (It’s far more likely that the code is buggy, but then actual debugging instead of guessing would be involved :) )

My best guess: Does the ‘custom pause image (that is exactly the same as "k8s.gcr.io/pause:3.1")’ happen to actually be stored using the “schema 1” format (e.g. in a schema1-only registry)? That does sound fairly unlikely, but it is the only explanation I can think of right now, assuming that the code works as intended.

Indeed it sounds fairly unlikely but somehow it actually is stored using the "schema 1" format.. not sure how that happened (image is stored in quay.io).

Probably because quay.io does not support image manifest v2 schema 2.

Ah, OK. Would it be easy for you to test CRI-O with a rebased GitHub.com/containers/image, then? Note that you need to both update CRI-O and delete the relevant images from local storage (or, maybe easier, delete all of the storage and start afresh) for the presumed fix to work.

@mtrmac We could create a PR with a rebase of containers/image and see if it helps @jakolehm.

A PR would make testing easier for sure.

https://github.com/kubernetes-incubator/cri-o/pull/1731

Since the PR was merged, closing the issue.

It seems that this issue still applies if image is first pulled from an older registry (like quay):
# crictl pull quay.io/kontena/pause-amd64:3.1
Image is up to date for quay.io/kontena/pause-amd64@sha256:cb4bcb1b386a7b68086564c32f2b13d2429a167d271e7312b1d2ae196b4e0b1a

# crictl pull k8s.gcr.io/pause-amd64:3.1
FATA[0000] pulling image failed: rpc error: code = Unknown desc = Error committing the finished image: image with ID "da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e" already exists, but uses a different top layer: that ID is already in use

Tested with cri-o 1.11.6 on CentOS 7.5.

@nalind @mtrmac could you take a look at the above please?

This was supposed to be fixed in the linked https://github.com/kubernetes-sigs/cri-o/issues/1725 .
Has anyone checked so far:

whether that fix is included in the 1.11.6
whether this is reproducible when starting with empty local containers/storage? (Note that once images are pulled with the old buggy version, the error message will continue to show up; they need to be at least untagged, a fresh storage is easier/more certain to reason about.)

@mtrmac tested with fresh cluster.

whether that fix is included in the 1.11.6

looks like https://github.com/kubernetes-sigs/cri-o/pull/1731/commits/4e7f71b714932dafc6a70e9b6dc09112da478be1 isn't in 1.11 branch and it's been tagged only for 1.12.0 onwards. @jakolehm any chance you'll be able to test with 1.12? We'll try to understand if a backport is feasible meanwhile

@runcom I'll test with 1.12.0 once our CI has cooked a new package.

@runcom I'll test with 1.12.0 once our CI has cooked a new package.

could you also test with 1.11.8? that's the latest in 1.11 release and could have that fixed already, not sure if a package is available for centos yet (@lsm5 ptal)

1.11.7 or later should be enough.

1.11.8 works, so most likely also 1.12.0 works.

Confirmed, 1.12.0 works.

thanks for checking, all good here then!


Add new expect test to check diff between metacp and metac.

The goal is to make metac-metacp.diff empty. Currently, it seems the two
disagree on several fronts.
Towards #1378. The first step in syncronizing metacp and metac is to know where they differ.

I have a pending change that improves this test quite a bit. Will push soon!


update on-by-default for csi migration providers

Updates for the following enhancements that are turning on by default but remaining in beta.
https://github.com/kubernetes/enhancements/issues/1490
https://github.com/kubernetes/enhancements/issues/1885
https://github.com/kubernetes/enhancements/issues/1487
https://github.com/kubernetes/enhancements/issues/1488

/hold
until after code freeze to make sure all the enhancements made it

/cc @jlbutler

/assign

/sig storage

@msau42  KEP 1885 should be removed from this PR, correct? I think that's now targeting 1.24.

@msau42 KEP 1885 should be removed from this PR, correct? I think that's now targeting 1.24.

https://github.com/kubernetes/kubernetes/pull/105070 is the k/k PR for KEP 1885 Azure file in-tree to CSI Migration
https://github.com/kubernetes/kubernetes/pull/105070 has a wip label and states it's targeting 1.24

@msau42 Reminder that tomorrow Nov 23rd is the deadline for 1.23 Docs Ready for Review. I think this one will be quick to get resolved once you have fixed up the 1885 component and removed the work-in-progress label.
We have a tight turnaround to getting docs reviewed and approved for the release, and we’re hoping to have all docs in for review by EOB tomorrow. Thank you!

updated to only include azuredisk, aws, and gce
/assign @Jiawei0227
/hold cancel

/assign @xing-yang

/lgtm
Thanks @msau42! Will look for a final tech lgtm and we'll be good to go.

/lgtm

/lgtm

/approve


Flynn CLI not running

I installed flynn cli on my laptop, but when I try to run it, I get this error
Segmentation fault

From our conversation in IRC, we realised this was due to a failed download of the CLI, and re-running the installation fixed it. I have opened #1550 to track fixing this.


Category Management API creation

Task No. #20923-As a developer I need to create an API to perform Category Edit
#20923-As a developer I need to create an API to perform Category Add
File Changed : Startup.cs
File Added:
ICategoryRepository.cs
CategoryRepository,cs
CategoryController.cs

SonarQube analysis reported 5 issues

 5 major

Watch the comments in this conversation to review them.


add Page Views

When we add this service, it will count every hit of this repo. And this will guide us more about the visitors each day and will indicate the total views. For me, this is very helpful both for us and for those will view this repo seeing this page views. If there is the website built from this repo, it can be simply added there too.

I appreciate the intention, but I have mixed feelings about privacy concerns etc.

It's a secured service. It only counts the page hit, no more no less.

We don't need to track page views. It's only a vanity metric, and needless sending of data to a third party.

We don't need to track page views. It's only a vanity metric, and needless sending of data to a third party.


react-native-document-scanner not build for android

Does anyone have an idea ?
run :
react-native run-android
result :
BUILD FAILED in 6s
error Failed to install the app. Make sure you have the Android development environment set up: https://facebook.github.io/react-native/docs/getting-started.html#android-development-environment. Run CLI with --verbose flag for more details.
Error: Command failed: ./gradlew app:installDebug -PreactNativeDevServerPort=8081
/Users/workpc/Projects//android/app/src/main/java/com/isegeldim/MainApplication.java:10: error: cannot find symbol
import org.opencv.DocumentScannerPackage;
^
symbol:   class DocumentScannerPackage
location: package org.opencv
/Users/workpc/Projects//android/app/src/main/java/com/isegeldim/MainApplication.java:16: error: package com.reactlibrary does not exist
import com.reactlibrary.RNPdfScannerPackage;
^
/Users/workpc/Projects//android/app/build/generated/rncli/src/main/java/com/facebook/react/PackageList.java:27: error: cannot find symbol
import org.opencv.DocumentScannerPackage;
^
symbol:   class DocumentScannerPackage
location: package org.opencv
/Users/workpc/Projects//android/app/build/generated/rncli/src/main/java/com/facebook/react/PackageList.java:86: error: cannot find symbol
new DocumentScannerPackage(),
^
symbol:   class DocumentScannerPackage
location: class PackageList
4 errors
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:compileDebugJavaWithJavac'.

Compilation failed; see the compiler error output for details.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 6s
at checkExecSyncError (child_process.js:591:13)
at execFileSync (child_process.js:611:13)
at runOnAllDevices (/Users/workpc/Projects/***/node_modules/@react-native-community/cli-platform-android/build/commands/runAndroid/runOnAllDevices.js:74:39)
at buildAndRun (/Users/workpc/Projects/***/node_modules/@react-native-community/cli-platform-android/build/commands/runAndroid/index.js:158:41)
at then.result (/Users/workpc/Projects/***/node_modules/@react-native-community/cli-platform-android/build/commands/runAndroid/index.js:125:12)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:188:7)

Duplicated https://github.com/Michaelvilleneuve/react-native-document-scanner/issues/52
Basically, change import org.opencv.DocumentScannerPackage; to import com.documentscanner.DocumentScannerPackage in MainApplication.java

@jorgemarrero  I'm having the same problem. I made the change as you said, but the problem was not solved?

Have you follow https://github.com/Michaelvilleneuve/react-native-document-scanner#android-only ?

@jorgemarrero Yes, I did it all step by step. But it didn't. :(

Task :app:compileDebugJavaWithJavac FAILED

Deprecated Gradle features were used in this build, making it incompatible with Gradle 6.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/5.4.1/userguide/command_line_interface.html#sec:command_line_warnings
185 actionable tasks: 31 executed, 154 up-to-date
/Users/workpc/Projects/isegeldim/android/app/build/generated/rncli/src/main/java/com/facebook/react/PackageList.java:27: error: cannot find symbol
import org.opencv.DocumentScannerPackage;
^
symbol:   class DocumentScannerPackage
location: package org.opencv
/Users/workpc/Projects/isegeldim/android/app/build/generated/rncli/src/main/java/com/facebook/react/PackageList.java:86: error: cannot find symbol
new DocumentScannerPackage(),
^
symbol:   class DocumentScannerPackage
location: class PackageList
2 errors
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:compileDebugJavaWithJavac'.

Compilation failed; see the compiler error output for details.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 8s
error Failed to install the app. Make sure you have the Android development environment set up: https://facebook.github.io/react-native/docs/getting-started.html#android-development-environment. Run CLI with --verbose flag for more details.
Error: Command failed: ./gradlew app:installDebug -PreactNativeDevServerPort=8081
/Users/workpc/Projects/isegeldim/android/app/build/generated/rncli/src/main/java/com/facebook/react/PackageList.java:27: error: cannot find symbol
import org.opencv.DocumentScannerPackage;
^
symbol:   class DocumentScannerPackage
location: package org.opencv
/Users/workpc/Projects/isegeldim/android/app/build/generated/rncli/src/main/java/com/facebook/react/PackageList.java:86: error: cannot find symbol
new DocumentScannerPackage(),
^
symbol:   class DocumentScannerPackage
location: class PackageList
2 errors
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:compileDebugJavaWithJavac'.

Compilation failed; see the compiler error output for details.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 8s
at checkExecSyncError (child_process.js:591:13)
at execFileSync (child_process.js:611:13)
at runOnAllDevices (/Users/workpc/Projects/isegeldim/node_modules/@react-native-community/cli-platform-android/build/commands/runAndroid/runOnAllDevices.js:74:39)
at buildAndRun (/Users/workpc/Projects/isegeldim/node_modules/@react-native-community/cli-platform-android/build/commands/runAndroid/index.js:158:41)
at then.result (/Users/workpc/Projects/isegeldim/node_modules/@react-native-community/cli-platform-android/build/commands/runAndroid/index.js:125:12)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:188:7)

This could be related to this issue #56 🤔
I am actually using my own fork of this package https://github.com/Woonivers/react-native-document-scanner

You can try it: yarn add @woonivers/react-native-document-scanner but you will need to change all from react-native-document-scanner to @woonivers/react-native-document-scanner in your project.

This package has done a great job, but I feel it is not maintained.

@jorgemarrero your react-native version ?

@jorgemarrero your react-native version ?

0.59.9

I am using version 0.60. Would you mind if I went to the repo you called? @jorgemarrero

Ahá, probably that's the problem.
0.60 changes a lot in Android, I haven't update for that reason :(

@jorgemarrero What can you do to make it run at 0.60.xx ? do you have an idea ?

@jorgemarrero What can you do to make it run at 0.60.xx ? do you have an idea ?

No idea, I'm sorry 😟
I will face that problem in the next few weeks/months.
The android part is very inspired by this repository https://github.com/ctodobom/OpenNoteScanner, maybe you can find some solution based on that.

Hi @umutcetinkaya ,
I have updated my fork to work with react-native 0.60+

hello @jorgemarrero.
Trying to get it to compile, but getting
PackageList.java:17: error: cannot find symbol import org.opencv.DocumentScannerPackage;
I'm using 0.61.1. Any idea?

hello @jorgemarrero.
Trying to get it to compile, but getting
PackageList.java:17: error: cannot find symbol import org.opencv.DocumentScannerPackage;
I'm using 0.61.1. Any idea?

What's version are you using?

@jorgemarrero  I have cloned your master (2.0.0 I suppose) and trying to run it from example folder

@jorgemarrero I have cloned your master (2.0.0 I suppose) and trying to run it from example folder

Sorry, the example folder was pointing to the previous version. I am working on make that dynamically, but I am having issues with auto-linking.
I have updated master with that change.

@jorgemarrero Did you know that you are running over 0.60 where you are currently forking?

hello @jorgemarrero.
Trying to get it to compile, but getting
PackageList.java:17: error: cannot find symbol import org.opencv.DocumentScannerPackage;
I'm using 0.61.1. Any idea?

You should disable auto link in RN 0.60+
Edit / Create react-native.config.js
module.exports = {
  dependencies: {
    'react-native-document-scanner': {
      platforms: {
        android: null
      }
    }
  }
};

This could be related to this issue #56 🤔
I am actually using my own fork of this package https://github.com/Woonivers/react-native-document-scanner

You can try it: yarn add @woonivers/react-native-document-scanner but you will need to change all from react-native-document-scanner to @woonivers/react-native-document-scanner in your project.

This package has done a great job, but I feel it is not maintained.

Chamo, a ti te ha funcionado este repo con RN 0.60 ?

@Gricardov
Is  @woonivers/react-native-document-scanner working for both Android and iOS?

same issue for me as well. Anyone found the fix???

This repo @woonivers/react-native-document-scanner is great. Work on react-native > 0.6.0.
However, important things like detectedRectangle doesn't work on Android, only on IOS. In my case it is very important to me.

After 2 long days of work, I finally succeeded to make it work. Here is what I've done, inspired by the previous comments and this issue on react-native-splash-screen
Install
$ yarn add https://github.com/Michaelvilleneuve/react-native-document-scanner
Link manually for android
First, we will disable autolink on android , so Edit / Create react-native.config.js at the root of your project
module.exports = {
  dependencies: {
    'react-native-document-scanner': {
      platforms: {
        android: null
      }
    }
  }
};

Now link manually react-native-document-scanner and openCV in your settings.gradle file
include ':react-native-document-scanner'
project(':react-native-document-scanner').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-document-scanner/android')

include ':openCVLibrary310'
project(':openCVLibrary310').projectDir = new File(rootProject.projectDir,'../node_modules/react-native-document-scanner/android/openCVLibrary310')

In android/app/src/main/java/com/your/project/MainActivity.java add
import com.documentscanner.DocumentScannerPackage;
In android/app/src/main/java/com/your/project/MainApplication.java add
import com.documentscanner.DocumentScannerPackage;
In android/app/build.gradle add
dependencies {
    [...]
    compile project(':react-native-document-scanner')
}

The process already described in the readme for iOS works correctly for me.

After 2 long days of work, I finally succeeded to make it work. Here is what I've done, inspired by the previous comments and this issue on react-native-splash-screen
Install
$ yarn add https://github.com/Michaelvilleneuve/react-native-document-scanner
Link manually for android
First, we will disable autolink on android , so Edit / Create react-native.config.js at the root of your project
module.exports = {
  dependencies: {
    'react-native-document-scanner': {
      platforms: {
        android: null
      }
    }
  }
};

Now link manually react-native-document-scanner and openCV in your settings.gradle file
include ':react-native-document-scanner'
project(':react-native-document-scanner').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-document-scanner/android')

include ':openCVLibrary310'
project(':openCVLibrary310').projectDir = new File(rootProject.projectDir,'../node_modules/react-native-document-scanner/android/openCVLibrary310')

In android/app/src/main/java/com/your/project/MainActivity.java add
import com.documentscanner.DocumentScannerPackage;
In android/app/src/main/java/com/your/project/MainApplication.java add
import com.documentscanner.DocumentScannerPackage;
In android/app/build.gradle add
dependencies {
    [...]
    compile project(':react-native-document-scanner')
}

The process already described in the readme for iOS works correctly for me.

@obertil Followed your steps (thanks for the same!) for Android and the it's building without issue, though while running, I am getting the error "RNPdfScanner was not found in the UIManager".  Repeated the steps, but still encountering this issue on Android.  On iOS, facing no issues...
May be you forgot to mention some step here?

@obertil Thanks for your solution
It works for me, with react-native v0.63.3
I've also upgrade the gradle version for the library as below
For ./node_modules/react-native-document-scanner/android/build.gradle
buildscript {
    repositories {
        google()
        jcenter()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:4.0.1'
    }
}

android {
    compileSdkVersion safeExtGet('compileSdkVersion', 29)
    buildToolsVersion safeExtGet('buildToolsVersion', '29.0.2')
    defaultConfig {
        minSdkVersion safeExtGet('minSdkVersion', 16)
        targetSdkVersion safeExtGet('targetSdkVersion', 29)
    }
}

For ./node_modules/react-native-document-scanner/android/openCVLibrary310/build.gradle
android {
    compileSdkVersion 29
    ...
}

And for ./node_modules/react-native-document-scanner/android/gradle/wrapper/gradle-wrapper.properties
...
distributionUrl=https\://services.gradle.org/distributions/gradle-6.2-all.zip

in react-native.config.js
dependencies: {
		'react-native-document-scanner': {
			platforms: {
				"android": {
					"packageImportPath": "import com.documentscanner.DocumentScannerPackage;",
					"packageInstance": "new DocumentScannerPackage()"
				}
			}
		},
		"react-native-perspective-image-cropper": {
			platforms: {
				"android": {
					"packageImportPath": "import fr.michaelvilleneuve.customcrop.RNCustomCropPackage;",
					"packageInstance": "new RNCustomCropPackage()"
				}
			}
		}
	}

Hope it will be in repo one day 😞

@skv-headless  You saved my day thanks a lot.

Too late for me, I already migrated to Flutter due to this. But thanks chamo! <3

You dont need to disable link you only need to add the line below to setting.grade
include ':openCVLibrary310'
project(':openCVLibrary310').projectDir = new File(rootProject.projectDir,'../node_modules/@woonivers/react-native-document-scanner/android/openCVLibrary310')

auto link should know that openCVLibrary310 has already been linked and will only add the code to .java

,
"react-native-perspective-image-cropper": {
platforms: {
"android": {
"packageImportPath": "import fr.michaelvilleneuve.customcrop.RNCustomCropPackage;",
"packageInstance": "new RNCustomCropPackage()"
}
}
}

Hi, thanks for the answer.
Where should I be putting this? In my project or in the library?
The format you have specified caused an error while running react-native run-android,  so I did this:
module.exports = {
    dependency: {
        platforms: {
            // iOS specific properties go here
            ios: {},
            // Android specific properties go here
            android: {
                'react-native-document-scanner': {
                    "packageImportPath": "import com.documentscanner.DocumentScannerPackage;",
                    "packageInstance": "new DocumentScannerPackage()"
                },
                "react-native-perspective-image-cropper": {
                    "packageImportPath": "import fr.michaelvilleneuve.customcrop.RNCustomCropPackage;",
                    "packageInstance": "new RNCustomCropPackage()"
                }
            },
        },
    },
};

Yet I still get the same error. I would really appreciate your help.


ios display issue

Love the plugin!  Only buggy thing is on ios, when drawn in a listview, tapping on the card view treats the card as transparent on ios, even though a background color is explicitly set.  Android does not exhibit this behavior.  See example image:

Without looking I suspect it's the listview selection behavior of iOS
uitableview. You'll want to disable the selection behavior. I can provide
the snippet later. Not near computer now.
On Tue, Dec 5, 2017, 6:02 PM glen-stephens<EMAIL_ADDRESS>wrote:

Love the plugin! Only buggy thing is on ios, when drawn in a listview,
tapping on the card view treats the card as transparent on ios, even though
a background color is explicitly set. Android does not exhibit this
behavior. See example image:
[image: cardview]
https://user-images.githubusercontent.com/32279761/33637406-06a3b072-d9de-11e7-8049-62a6cf987d7b.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bradmartin/nativescript-cardview/issues/74, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFulhLstjstXu7DRCokC8eApeYI9kWG-ks5s9dmNgaJpZM4Q3KDx
.

Thanks!! Here is what I get if I give my labels a background color, however it would be better to get the card's background color to work.

having the same issue outside of listview too. also in earlier versions. never got to fix this. only on iOS

I have my CardViews wrapped in a WrapLayout with an explicit background color and still had the text-shadow issue on iOS.
<ScrollView>     <WrapLayout orientation="horizontal" background="#f5f5ed">         <CardView class="cardStyle" margin="10" elevation="40" radius="25">             <GridLayout rows="10, auto, 10, auto, 10, auto, 10" columns="10, * ,10">                 <Label text="Quick Links" class="h2 text-center" col="1" row="1" textWrap="true"></Label>                 <Button text="View" class="purchase-button" (tap)="goBrowse()" col="1" row="3"></Button>                 <Button text="Visit" class="purchase-button" (tap)="purchaseSubscription()" col="1" row="5"></Button>             </GridLayout>         </CardView>
Is that what @sittingbool is describing? Any suggestions (maybe a different layout or something)?
I'm using Angular with NativeScript and everything looks as expected on Android.

Here's a workaround if you are running into this trying to have CardView inside a ListView. Assuming Angular, use an element ref to access the ListView inside your component, and then disable allowsSelection. eg:
export class MyComponent {
  @ViewChild('list') list;

  ngAfterViewInit() {
    if (this.list && this.list.nativeElement.ios) {
      this.list.nativeElement.ios.allowsSelection = false;
    }
  }
}

The underlying UITableView on iOS trying to allow selection of the card is what is causing the background to become transparent.


Joe Mercado - Sprint Challenge Version 2

@camilamdaniels Missed a change and corrected it.

Assessing Your User Interface and Git Learning
Task 1: Set Up The Project With Git

[ ] Fork the project into your GitHub user account
[ ] Clone the forked project into a directory on your machine
[ ] Create a branch called develop on your local build
[ ] Set your HEAD to your newly created develop branch
[ ] You are now ready to build this project with your preferred IDE

Task 2: Comprehension Questions
Answer the following questions to the best of your ability. You can exercise your Googling skills and use training kit. Open up the Answers.md file and record your responses there.

[ ] If you had to describe semantic HTML to the next cohort of students, what would you say?

[ ] Describe some differences between display: block; and display: inline;.

[ ] What are the 4 areas of the box model?

[ ] While using flexbox, what axis are you using when you use the property: align-items: center?

Task 3: Home Page
Review the provided design file for the home page. Notice the navigation and header images are missing.

[ ] Build the HTML and CSS to create the missing navigation and header.
[ ] Link up the About navigation item to the about.html page

You will also notice there are 10 boxes on the home page that need background colors. Use this list below to correctly style each box:

[ ] box1: teal
[ ] box2: gold
[ ] box3: cadetblue
[ ] box4: coral
[ ] box5: crimson
[ ] box6: forestgreen
[ ] box7: darkorchid
[ ] box8: hotpink
[ ] box9: indigo
[ ] box10: dodgerblue

Task 4: About page
Review the provided design file for the about page. You have been provided the HTML wrapper, footer, and page content for the about page. Create the rest of the missing HTML and CSS to match the design file.

[ ] Copy and paste your home page navigation and header into the about page
[ ] Update the header image with the about page image
[ ] Link the Home navigation item back to the index.html page.
[ ] Build the rest of the about page layout to match the design

Task 5: Merge & Pull Request

[ ] Once you have completed tasks 1-4, push all your commits up to your develop branch.
[ ] Switch your HEAD to master
[ ] Merge the develop branch into master
[ ] Push all your updates up to master
[ ] Create a pull request back to the original fork

Congratulations, you completed the sprint challenge!
Stretch Goals
Stretch goals are only available if you complete every task listed above. Do not work on them until your pull request is in.

[ ] Build a page of your choosing from the navigation items. Come up with content and images that fit the theme.
[ ] Introduce CSS animations to your site.
[ ] Build the contact page and create a form with several inputs of your choosing
[ ] Add responsive breakpoints to your code by using media queries

Great job! The about page looks fantastic!


Update referenced package versions

In #259 we have seen that we are using quite a bunch of old versions for the packages that we reference, and that this can cause problems.
See here for the current versions:
https://github.com/svelte-add/svelte-add/blob/062154a5f6e723987a4d8b69b3894965b7869436/projects/svelte-add/package-versions.js#L2-L23
I have begun working out some new versions, but currently focused only on the ones with patch version changes.

Everything with minor version changes and upwards should probably be analyzed and tested more deeply.

Relates #263

Updated in the latest release


Added image_url of the first listing image to the output table

Hello, as discussed I added retrieving the primary property image. This is my first Github pull request so apologies if I got something wrong, happy to amend.

Apologies for the delay!
This seems like a good idea but I think first I'd like to understand if it slows down the requests by a significant time? If so it would be better to make it optional (as with the get_floorplans parameter).
Also, I think I'd lean towards scraping all the image urls as a list if possible as it seems like that would have a lot more use cases. Not sure how much more effort that would be...


rke2/k3s chart values do not update when switching versions

Setup

Rancher version: v2.6.3-rc4
Browser type & version: Firefox 94.0.2

Describe the bug

Chart values do not update when changing kubernetes version for rke2 and k3s.
To Reproduce

Point to my custom KDM, which has different values for the calico charts for rke2 in v1.22 and v1.21: https://raw.githubusercontent.com/rancher-max/kontainer-driver-metadata/rke2-chart-versions/data/data.json
Navigate to the create cluster page for rke2
Change Kubernetes Version to use v1.21.7+rke2r2
Go to "Edit as YAML"

Result
Notice spec.rkeConfig.chartValues are not updated. I would expect spec.rkeConfig.chartValues.rke2-calico to be using v1.17.6 for tigeraOperator. Basically what is happening is that none of the values are being updated according to the KDM values.
Even if I do not point to any custom KDM and just change the Kubernetes Version in the form to use a k3s version, I still have these rke2-calico config params. I shouldn't have these at all because k3s does not use calico.
Expected Result

Changing kubernetes version in the form on the UI should also update any chart values to be use those associated with that version.
Screenshots

Initial Values:

After Changing:

Additional context

Detailed Description

Context

seeing this issue on v2.6.3-rc4 HA. Not able to upgrade any chart as a standard user.
When we try to upgrade, no requests are sent to the backend  and the screen won't load:

The same issue exists when changing CNI provider instead of Kubernetes version: The addon-config content should be updated to match the CNI provider but it isn't.

This issue is also preventing provisioning of RKE2 cluster with k8s version v1.21.7+rke2r2 (which is the min version available in 2.6.3-rc4 drop down when creating the cluster)

tested on rancher v2.6-head (e62e1ae):

rke2 1.22.4+rke2r2 single node deployment -> working fine
Reopening for the following issue:
rke2 1.21.7+rke2r2 single node deployment -> still broken (workaround: before clicking the button to create the cluster, edit as yaml and remove the entire chartValues section [down until the etcd block] which will deploy successfully).

I think there's multiple issues in this thread. The core issue of chartValues not updating has been fixed (updates on changes to Kubernetes Version, Container Network or Cloud Provider). I don't think those are related to rke2 1.21 failing to provision, that probably needs another issue in rancher/rancher (containing a copy of the chartValues section and also any helpful logs)

There's a fair amount of cluster provisioning cases that should be tested for this issue - see https://github.com/rancher/dashboard/pull/4772#issuecomment-994795874

I successfully reproduced the problem
Reproduction Environment:

Rancher version: v2.6.3-rc4
Rancher cluster type: single-node docker install
Docker version: 20.10
Downstream cluster type: RKE2
Downstream K8s version: (vDefault and switch in dropdown)
Reproduction steps:

Point to Max' custom KDM, which has different values for the calico charts for rke2 in v1.22 and v1.21: https://raw.githubusercontent.com/rancher-max/kontainer-driver-metadata/rke2-chart-versions/data/data.json
Navigate to the create cluster page for rke2
Change Kubernetes Version to use v1.21.7+rke2r2
Go to "Edit as YAML"

Result
Notice spec.rkeConfig.chartValues are not updated.

Note, I also changed CNI and the result was the same.

v2.6-head bbde38e 12/15/2021
Something isn't quite right. Either that or I'm misunderstanding the change. I still expected to see chartValues in the cluster YAML. I have reproduced this one two separate setups each with latest v2.6-head:

@richard-cox I'm going to re-open -- could you follow up and move back to QA Working if this is a non-issue (and explain) or investigate?

What's stored/sent is the diff from the chart's original values, which is nothing if you haven't customized it.  Before we always saved the whole thing, which wasn't necessary (because Helm starts from that anyway) and made it hard to tell what the user intended to customize on edit/future upgrade.

It doesn't look like this change is in the latest RC (v2.6.3-rc6 which uses dashboard tag v2.6.3-rc5). In 2.6-head, as per Vince's comment and the PR comment (I'm kicking myself for not including it in the Notes to QA section), we now don't populate chartValues with default content. You'll be able to see the change in default config though by the Add-on Config tab though.

My checks PASSED
As described here, I tested each area as mentioned and also ran our validation tests on each downstream cluster. I also smoke tested on my own accord checking that cluster provisioning v2 works as expected.
HOWEVER, I did NOT specifically test vSphere and Harvester as @anupama2501 and @slickwarren will check these areas each, respectively.
Reproduction Steps:

Already covered in my prior comment here.

Validation Environment:

Rancher version: v2.6-head 39cecf0 12/16/2021 pulled ~9:00AM Arizona time
Rancher cluster type: single-node docker install
Docker version: 20.10
Downstream cluster type: RKE2 and K3S
Downstream K8s version: Various
Validation steps:

Create an RKE2 and K3S cluster each with k8s 1.22. Create additional ones each with 1.21. Notice, due to the changes chartValues are no longer shown in the cluster YAML. This is expected.

For each of these clusters, during creation switch in the UI from either 1.21 and 1.22 in the dropdown until pick the version will actually deploy with. This is to ensure the UI is working correctly whether or not we switch kubernetes versions prior to submitting the cluster creation form. All my clusters both RKE2 and K3S and versions 1.21 and 1.22 provision without any issues when single-node clusters and multi-node clusters only worked for RKE2 - for those I used a 3-pool configuration like etcd - 3, controlplane - 2, worker - 3. (Default options otherwise used during cluster provisioning). All validation tests run on RKE2 multi-node clusters only.
On each cluster, checked chart versions - they appear to be what they should be set to when compared to KDM. Executed validation tests on each of these downstream multi-node RKE2 clusters. Ensured that validation tests contained no unexpected failures.
Smoke tested on my own accord. I created additional single-node and multi-node clusters for RKE2 and manually tested addons in the UI (this is an additional change in this issue) to ensure these work as expected. I didn't identify any problems with cluster provisioning or with addons during my testing with RKE2. However, my testing was not 100% extensive.

Additional Info:
Note, during my runs of validation tests on RKE2 clusters I did encounter some failures but manually tested where necessary and saw things work correctly.
Note, to validate that addon settings actually worked, I navigated to calico settings (where I applied my addons) and ensured the config looked correct. I saw my settings (overrides) in FelixConfiguration.metadata.annotations.projectcalico.org/metadata

Note, I had some issues with my multi-node k3s clusters. As these are still experimental I didn't run validation tests against them as I couldn't get a multi-node k3s cluster to come up correctly. I still did some basic checks with single node k3s clusters. The focus was primarily on RKE2 downstream clusters.
Lists of setups I checked during my testing:

Create an RKE2 DO Kube version 1.21 instance with no custom addon config
Create an RKE2 DO Kube version 1.21 instance with custom config

Use felixConfiguration.genericXDPEnabled: true

Create an RKE2 DO Kube version 1.22 instance with no custom addon config
Create an RKE2 DO Kube version 1.22 instance with custom config

Use felixConfiguration.wireguardEnabled: true

Create an RKE2 AWS Cluster, any kube version, with custom addon config
(Except I tested primarily with aws ec2 node driver, and one smoke test with DO node driver)

finished validation on v2.6-head 39cecf0 for harvester:
k8s 1.21.7

Create an RKE2 DO Kube version 1.21 instance with no custom addon config
Create an RKE2 DO Kube version 1.21 instance with custom config

Use felixConfiguration.genericXDPEnabled: true

after deployment, check that the additional config has applied (apps & marketplace -> calico -> view values.yaml) -- pass
run automation checks -- pass

finished validation on v2.6-head 39cecf0 for vsphere:
k8s 1.21.7+rke2
Create an RKE2 vsphere Kube version 1.21 instance with no custom addon config
Create an RKE2 vsphere Kube version 1.21 instance with custom config
Use felixConfiguration.genericXDPEnabled: true
after deployment, check that the additional config has applied (apps & marketplace -> calico -> view values.yaml) -- pass
run automation checks -- pass
Upgraded both the clusters to 1.22.4+rke2, validation tests - PASS


Update OMS Agent to latest 1.6 version

OMS agent is outdated. Current version(1.4.4-210) is 2  releases behind.

@asubmani : Thanks for your contribution! The author, @danielsollondon, has been notified to review your proposed change.

#please-close @asubmani Daniel has rewritten this article and it now includes similar information. Please take a look: https://docs.microsoft.com/en-us/azure/virtual-machines/extensions/oms-linux


Not launching while device locked

As you can see here, i am trying to launch device control while in a lockscreen, but it doesn't able to work properly. This issue just happened suddenly, before this it was working perfectly. Don't know what caused this issue.

#143


Support camera arrays [🌟]

I currently don't have a phone with multiple cameras, but came across this component https://github.com/mrousavy/react-native-vision-camera and they claim to have figured out how to seamlessly zoom in/out using multiple cameras, just like the native camera app. Does RNIP, currently do this?

I wonder if supporting camera at all is out of scope of this library @Johan-dutoit ? And we should rip the code out related to camera and just suggest alternative libraries like: https://github.com/mrousavy/react-native-vision-camera ?


how to Integrate Deeplink  info QR

Hi there,
Deeplink relates to the content of the QR code rather than the actual QR code generation.  Once you have a deep link URL that works with your app, you can use this library to generate a QR code containing the link.
Here are some web pages that discuss deep linking (using both universal links and url schemes)
• https://developer.apple.com/ios/universal-links/
• https://developer.apple.com/documentation/xcode/defining-a-custom-url-scheme-for-your-app
• https://developer.apple.com/documentation/xcode/allowing-apps-and-websites-to-link-to-your-content
• https://medium.com/wolox/ios-deep-linking-url-scheme-vs-universal-links-50abd3802f97
• https://www.branch.io/resources/blog/how-to-setup-universal-links-to-deep-link-on-apple-ios/
• https://www.donnywals.com/handling-deeplinks-in-your-app/
Have a misunderstood your issue?

Closing due to lack of feedback


Add an inlet coordinate to data files

As per the suggestion in Issue #86, added an "inlet" coordinate to the data files.

Need to remove inlet_height variable

Closing since superseded by #96


FPT_JTA_EXT.1 Missing Test

We need a test for determining that tenant software cannot access the ports.

Test: authenticate as admin, try, succeed; logout or whatever, try, fail.
Probably need to define physical presence (make sure physical presence is defined in the tech terms.

Added tests, and also added Physical Presence to the tech terms.


invalid encoding: UTF-8 (ArgumentError) on FreeBSD

Hi,
thanks for your effort creating this clean and lean language.
Here's the problem code:
"12345".encode "UTF-8"

here's the exception:
invalid encoding: UTF-8 (ArgumentError)
[4351927] *CallStack::unwind:Array(Pointer(Void)) +87
[4351818] *CallStack#initialize:Array(Pointer(Void)) +10
[4351770] *CallStack::new:CallStack +42
[4335000] *raise<ArgumentError>:NoReturn +24
[4369181] *Iconv#initialize<String, String, Nil>:Nil +349
[4368810] *Iconv::new<String, String, Nil>:Iconv +58
[4364498] *String::encode<Slice(UInt8), String, String, MemoryIO, Nil>:Nil +114
[4364277] *String#encode<String>:Slice(UInt8) +85
[4333210] _start +1658
[4345673] main +41
[4331919] _start +367
[34366562304] ???

UTF-8 is in 'iconv -l' output on my box.
I'm using Crystal 0.18.7 (2016-07-25) from this repo on FreeBSD 10.3-RELEASE-p7 x86_64.
Is it me or some package problems?

Seems like package problems, see https://carc.in/#/r/18sy

It's certainly related to the FreeBSD port. The iconv integration may require some FreeBSD specific fixes. I believe encoding specs didn't pass, but I didn't verify much further, believing it failed because of the unsupported legacy multibytes encodings used in specs.
If a FreeBSD user can take a better look?

@ysbaddaden Yes, sure, what should I do?

Try to further down where the error is actually raised and if it fails with other encodings too. It seems to be an ArgumentError so maybe listing available encodings isn't working correctly?

It fails with other encodings too:
"12345".encode "CP1251"

invalid encoding: CP1251 (ArgumentError)
[4351927] *CallStack::unwind:Array(Pointer(Void)) +87
[4351818] *CallStack#initialize:Array(Pointer(Void)) +10
[4351770] *CallStack::new:CallStack +42
[4335000] *raise<ArgumentError>:NoReturn +24
[4369181] *Iconv#initialize<String, String, Nil>:Nil +349
[4368810] *Iconv::new<String, String, Nil>:Iconv +58
[4364498] *String::encode<Slice(UInt8), String, String, MemoryIO, Nil>:Nil +114
[4364277] *String#encode<String>:Slice(UInt8) +85
[4333210] _start +1658
[4345673] main +41
[4331919] _start +367
[34366562304] ???

As I can see, it fails in iconv.cr here:
    Errno.value = 0
    @iconv = LibC.iconv_open(to, from)
    if Errno.value != 0
      if original_from == "UTF-8"
        raise ArgumentError.new("invalid encoding: #{original_to}")

So it looks like some problems with libiconv bindings.
Is there any way to run specs myself on my box to gather more info?

Thank you!
There should be enough resources from the docs or our CONTRIBUTE.md to compile Crystal from sources, then running crystal spec spec/std/...

Had a little time tinkering with that problem, here's my findings.
In fact, iconv_open libc call is working fine, it returns conversion descriptor as it should according to man iconv. The problem is with error handling code, looks like on FreeBSD errno is never set to zero after successful call.

man errno excerpt:
...
When a system call detects an error, it returns an integer value indicating failure (usually -1) and sets the variable errno accordingly. (This allows interpretation of the failure on receiving a -1 and to take action accordingly.) Successful calls never set errno; once set, it remains until another error occurs. It should only be examined after an error.
...

I commented out exception raising code after iconv_open in src/iconv.cr for test and it worked as a charm - string was converted!
So, I think error handling code has to be corrected to check for a LibC.iconv_open return value first.

man iconv_open excerpt:
...
Upon successful completion of iconv_open(), it returns a conversion descriptor. Otherwise, iconv_open() returns (iconv_t)-1 and sets errno to indicate the error.
...

Here's the output of specs run:
10993 examples, 6 failures, 41 errors, 11 pending

Failed examples:

crystal spec ./spec/std/string_spec.cr:1900 # String encode raises if illegal byte sequence
crystal spec ./spec/std/string_spec.cr:1910 # String encode raises if incomplete byte sequence
crystal spec ./spec/std/io/io_spec.cr:522 # IO encoding decode raises on incomplete byte sequence
crystal spec ./spec/std/io/io_spec.cr:530 # IO encoding decode says invalid byte sequence
crystal spec ./spec/std/io/io_spec.cr:658 # IO encoding encode raises on invalid byte sequence
crystal spec ./spec/std/io/io_spec.cr:673 # IO encoding encode raises on incomplete byte sequence
crystal spec ./spec/std/file_spec.cr:696 # File encoding writes with encoding
crystal spec ./spec/std/file_spec.cr:703 # File encoding reads with encoding
crystal spec ./spec/std/file_spec.cr:710 # File encoding opens with encoding
crystal spec ./spec/std/file_spec.cr:719 # File encoding does each line with encoding
crystal spec ./spec/std/file_spec.cr:728 # File encoding reads lines with encoding
crystal spec ./spec/std/string_spec.cr:1883 # String encode encodes
crystal spec ./spec/std/string_spec.cr:1906 # String encode doesn't raise on invalid byte sequence
crystal spec ./spec/std/string_spec.cr:1916 # String encode doesn't raise if incomplete byte sequence
crystal spec ./spec/std/string_spec.cr:1920 # String encode decodes
crystal spec ./spec/std/string_spec.cr:1925 # String encode decodes with skip
crystal spec ./spec/std/io/buffered_spec.cr:285 # IO::Buffered encoding decode gets_to_end
crystal spec ./spec/std/io/buffered_spec.cr:293 # IO::Buffered encoding decode gets
crystal spec ./spec/std/io/buffered_spec.cr:303 # IO::Buffered encoding decode gets big string
crystal spec ./spec/std/io/buffered_spec.cr:314 # IO::Buffered encoding decode gets big GB2312 string
crystal spec ./spec/std/io/buffered_spec.cr:324 # IO::Buffered encoding decode reads char
crystal spec ./spec/std/io/io_spec.cr:423 # IO encoding decode gets_to_end
crystal spec ./spec/std/io/io_spec.cr:430 # IO encoding decode gets
crystal spec ./spec/std/io/io_spec.cr:440 # IO encoding decode gets big string
crystal spec ./spec/std/io/io_spec.cr:450 # IO encoding decode gets big GB2312 string
crystal spec ./spec/std/io/io_spec.cr:461 # IO encoding decode gets with limit
crystal spec ./spec/std/io/io_spec.cr:468 # IO encoding decode gets with limit (small, no newline)
crystal spec ./spec/std/io/io_spec.cr:475 # IO encoding decode gets with limit (big)
crystal spec ./spec/std/io/io_spec.cr:482 # IO encoding decode gets with string delimiter
crystal spec ./spec/std/io/io_spec.cr:492 # IO encoding decode reads char
crystal spec ./spec/std/io/io_spec.cr:502 # IO encoding decode reads utf8 byte
crystal spec ./spec/std/io/io_spec.cr:512 # IO encoding decode reads utf8
crystal spec ./spec/std/io/io_spec.cr:538 # IO encoding decode skips invalid byte sequences
crystal spec ./spec/std/io/io_spec.cr:566 # IO encoding decode does skips when converting to UTF-8
crystal spec ./spec/std/io/io_spec.cr:572 # IO encoding decode decodes incomplete multibyte sequence with skip (#3285)
crystal spec ./spec/std/io/io_spec.cr:581 # IO encoding encode prints a string
crystal spec ./spec/std/io/io_spec.cr:590 # IO encoding encode prints numbers
crystal spec ./spec/std/io/io_spec.cr:608 # IO encoding encode prints bool
crystal spec ./spec/std/io/io_spec.cr:617 # IO encoding encode prints char
crystal spec ./spec/std/io/io_spec.cr:625 # IO encoding encode prints symbol
crystal spec ./spec/std/io/io_spec.cr:633 # IO encoding encode prints big int
crystal spec ./spec/std/io/io_spec.cr:641 # IO encoding encode puts
crystal spec ./spec/std/io/io_spec.cr:650 # IO encoding encode printf
crystal spec ./spec/std/io/io_spec.cr:666 # IO encoding encode skips on invalid byte sequence
crystal spec ./spec/std/io/memory_io_spec.cr:287 # MemoryIO encoding decode gets_to_end
crystal spec ./spec/std/io/memory_io_spec.cr:294 # MemoryIO encoding decode gets
crystal spec ./spec/std/io/memory_io_spec.cr:303 # MemoryIO encoding decode reads char

Specs failed with the same exception raised (ArgumentError in Iconv#initialize).

We (almost) always check the return value, but it appears we don't for for iconv. Thanks for reducing the issue, I'm fixing the errno handling for iconv_open, iconv_close and iconv.

@ysbaddaden Just tried 0.19.3 on FreeBSD 10 and bug is not gone :(
Here's code from 0.19.3 FreeBSD package stdlib iconv.cr (with old buggy-ish error handling):
    Errno.value = 0
    @iconv = LibC.iconv_open(to, from)
    if Errno.value != 0
      if original_from == "UTF-8"
        raise ArgumentError.new("invalid encoding: #{original_to}")
      elsif original_to == "UTF-8"
        raise ArgumentError.new("invalid encoding: #{original_from}")
      else
        raise ArgumentError.new("invalid encoding: #{original_from} -> #{original_to}")
      end
    end

Do you build FreeBSD package manually or have this automated via your CI?
Thanks for great job, anyway.

Oh. Something wrong, indeed. I'll rebuild the tarball!

@zarianu I rebuilt and reuploaded the tarballs for 0.19.2 and 0.19.3 that were wrong. Tell me if it works for you (eventually). I still have failing specs related to specs, but they seem related to the non supported GB2312 encoding.

@ysbaddaden Everything works for initial code I attached to this issue, thanks, but I'm getting same exception when I'm trying to use HTTP::Client:
invalid encoding: utf-8 (ArgumentError)
[4551911] *CallStack::unwind:Array(Pointer(Void)) +87
[4551802] *CallStack#initialize:Array(Pointer(Void)) +10
[4551754] *CallStack::new:CallStack +42
[4507144] *raise<ArgumentError>:NoReturn +24
[4592827] *Iconv#initialize<String, String, (Symbol | Nil)>:Nil +571
[4592236] *Iconv::new<String, String, (Symbol | Nil)>:Iconv +92
[4785775] *IO::Decoder#initialize<IO::EncodingOptions>:Bool +95
[4785650] *IO::Decoder::new<IO::EncodingOptions>:IO::Decoder +210
[4777988] *Zlib::Inflate +164
[4781757] *Zlib::Inflate +93
[4914291] *HTTP::Client::Response#consume_body_io:Nil +787
[4912076] *HTTP::Client::Response::from_io<(OpenSSL::SSL::Socket+ | TCPSocket+), Bool, Bool>:HTTP::Client::Response +1788
[4828142] *HTTP::Client#exec_internal<HTTP::Request>:HTTP::Client::Response +174
[4827702] *HTTP::Client#exec<HTTP::Request>:HTTP::Client::Response +38
[4826982] *HTTP::Client#exec<String, String, Nil, Nil>:HTTP::Client::Response +22
[4826951] *HTTP::Client#get<String>:HTTP::Client::Response +39
[4465804] _start +2332
[4521961] main +41
[4463839] _start +367
[34367119360] ???

I will try to dig down on this one now ;)
BTW, FreeBSD's iconv supports GB2312 encoding, so maybe failed specs are associated with some other issues (invalid byte count or something):
[kost@chef]% iconv -l | grep 2312
EUC-CN CN-GB CSGB3212 EUCCN GB2312
HZ HZ-GB-2312 HZ-GB2312 HZ8

Looks like FreeBSD libc doesn't support GNU extensions to iconv interface (//IGNORE & //TRANSLIT), so there need to be some workaround (see __iconv() in FreeBSD man).
FreeBSD iconv man
Linux iconv man
Too bad my days of low level/C programming has gone - I should have found this out much earlier.

Since https://github.com/crystal-lang/crystal/pull/3379 is merged, can we close this?


[Feature Request]

**Is your feature request related to a problem? Tests for duplicates for example work great, but you don't know where or what business key the duplicate is on. Rather than just testing the existence it would be great to show end users what records are considered to be duplicate to help aid remediation at source.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Show duplicate count, with business key.
Describe alternatives you've considered
Changing the compiled SQL, but it is a bit onerous
Additional context
N/A

Hi @welsh-wonder - I'm a little unclear what this feature request is actually requesting. Could you please add a little more specifics re: what you would expect the output to show etc?
Also, we're just using the underlying dbt testing framework for these macros, so any output is ultimately controlled by what dbt supports.


Instead of xp drops, we should see the number of what our hit will be. for example a 53 xp drop would be 10.

I can't add much to it, but would be amazing

Duplicate of #4055


:boom: IE styles

:rocket: deployed to http://connecting-to-services-pr-258.dev.c2s.nhschoices.net and using the latest release of nearby-services-api (0.2.0-beta)

Coverage remained the same at 98.897% when pulling 0ead30255b4c49cfc506263af3766ca2d985cc20 on feature/fe-ie-fixes into 50fe14ba93e43923b62b50a5f1f3a9efb5787477 on master.

 Fix CSS in IE (and other browsers)

@ajthomascouk - might be easiest if you talked me through the changes using browser stack for me to review this.

@ajthomascouk walked me through the changes. LGTM.


Avalon does not work with the master branch of Graphene

Description of the issue
Avalon is not working with the latest master of Graphene due to an issue with importing the crypto libraries required by Avalon. While starting the python worker, it is crashing while importing the pyCryptodome library.
Steps to reproduce
Follow the steps to build the python worker here and then start it by running:
docker-compose -f docker-compose.yaml -f compose/graphene-sgx.yaml up

Expected Results
All the libraries should be imported and the code should run properly.
Actual Results
The python worker crashes with the following error while importing the Cryptodome library:
File "/usr/local/bin/wo-processor", line 7, in <module>
   from avalon_worker.work_order_processor import main
File "/usr/local/lib/python3.6/dist-packages/avalon_worker/work_order_processor.py", line 24, in <module>
  import avalon_worker.crypto.worker_encryption as worker_encryption
File "/usr/local/lib/python3.6/dist-packages/avalon_worker/crypto/worker_encryption.py", line 19, in <module>
  from Cryptodome.PublicKey import RSA
File "/usr/local/lib/python3.6/dist-packages/Cryptodome/PublicKey/RSA.py", line 42, in <module>
  from Cryptodome.Math.Numbers import Integer
File "/usr/local/lib/python3.6/dist-packages/Cryptodome/Math/Numbers.py", line 34, in <module>
  from Cryptodome.Math._IntegerGMP import IntegerGMP as Integer
File "/usr/local/lib/python3.6/dist-packages/Cryptodome/Math/_IntegerGMP.py", line 98, in <module>
  lib = load_lib("gmp", gmp_defs)
File "/usr/local/lib/python3.6/dist-packages/Cryptodome/Util/_raw_api.py", line 176, in load_lib
  full_name = find_library(name)
File "/usr/lib/python3.6/ctypes/util.py", line 313, in find_library
  return _findSoname_ldconfig(name) or \
File "/usr/lib/python3.6/ctypes/util.py", line 283, in _findSoname_ldconfig
  res = re.search(regex, p.stdout.read())
File "/usr/lib/python3.6/re.py", line 182, in search
    return _compile(pattern, flags).search(string)
TypeError: expected string or bytes-like object

Description of the issue
Avalon is not working with the latest master of Graphene due to an issue with importing the crypto libraries required by Avalon. While starting the python worker, it is crashing while importing the pyCryptodome library.
Steps to reproduce
Follow the steps to build the python worker here and then start it by running:
docker-compose -f docker-compose.yaml -f compose/graphene-sgx.yaml up

Expected Results
All the libraries should be imported and the code should run properly.
Actual Results
The python worker crashes with the following error while importing the Cryptodome library:
File "/usr/local/bin/wo-processor", line 7, in <module>
   from avalon_worker.work_order_processor import main
File "/usr/local/lib/python3.6/dist-packages/avalon_worker/work_order_processor.py", line 24, in <module>
  import avalon_worker.crypto.worker_encryption as worker_encryption
File "/usr/local/lib/python3.6/dist-packages/avalon_worker/crypto/worker_encryption.py", line 19, in <module>
  from Cryptodome.PublicKey import RSA
File "/usr/local/lib/python3.6/dist-packages/Cryptodome/PublicKey/RSA.py", line 42, in <module>
  from Cryptodome.Math.Numbers import Integer
File "/usr/local/lib/python3.6/dist-packages/Cryptodome/Math/Numbers.py", line 34, in <module>
  from Cryptodome.Math._IntegerGMP import IntegerGMP as Integer
File "/usr/local/lib/python3.6/dist-packages/Cryptodome/Math/_IntegerGMP.py", line 98, in <module>
  lib = load_lib("gmp", gmp_defs)
File "/usr/local/lib/python3.6/dist-packages/Cryptodome/Util/_raw_api.py", line 176, in load_lib
  full_name = find_library(name)
File "/usr/lib/python3.6/ctypes/util.py", line 313, in find_library
  return _findSoname_ldconfig(name) or \
File "/usr/lib/python3.6/ctypes/util.py", line 283, in _findSoname_ldconfig
  res = re.search(regex, p.stdout.read())
File "/usr/lib/python3.6/re.py", line 182, in search
    return _compile(pattern, flags).search(string)
TypeError: expected string or bytes-like object

By looking at the command, you seem to be getting this issue while running fibonacci workload (without Avalon).
We haven't tested graphene workloads against graphene master. While we test it, could you please share python manifest file changes in python worker?

Hi @manju956 ,
I have not made any changes to the python manifest file. I have just added the SPID. My python.manifest is as follows:
sgx.allow_file_creation = 1
# Set the virtual memory size of the SGX enclave. For SGX v1, the enclave
# size must be specified upfront. If Python worker needs more
# virtual memory than the enclave size, Graphene will not be able to
# allocate it.
sgx.enclave_size = "256M"
sgx.thread_num = 8
sgx.file_check_policy = "allow_all_but_log"

# Request remote attestation functionality from Graphene
sgx.remote_attestation = 1

# Specify your SPID and linkable/unlinkable attestation policy
sgx.ra_client_spid = "4559436813665C99DF8EE1BA9FDA3868"
sgx.ra_client_linkable = 1

However, I had to make some changes to the build_gsc_python_worker.sh to make it compatible with the latest version of graphene.
Here in the latest gsc.py file, it expects only one manifest file.
So in the build_gsc_python_worker.sh file, I made the following changes from lines numbers 40-63:
# Manifest files
MANIFEST_FILE="${TCF_HOME}/tc/graphene/python_worker/graphene_sgx/manifest/python.manifest"

# Build image
echo "Build unsigned GSC image"
./gsc build --insecure-args $IMAGE_NAME $MANIFEST_FILE


Insert in Verification API with TAG_MANAGER throws 503

Attempting to verify a site using the TAG_MANAGER always results in an Exception being thrown due to a 503 response being returned with "(503) An unexpected error occurred. Please try your request again.".
I'm using a google service account for the authentication and the account does have edit access to the tag manager account.
The request looks something like the following

POST https://www.googleapis.com/siteVerification/v1/webResource?verificationMethod=TAG_MANAGER
content-type: application/json; charset=UTF-8
authorization: Bearer scrubbedtheauthorizationinfo
accept-encoding: gzip
content-length: 129
BODY: {"owners":["256230575860@developer.gserviceaccount.com"],"site":{"identifier":"http://49lawstreetcaversham.com","type":"SITE"}}

The response comes back like

HTTP 503
content-type: application/json; charset=UTF-8
content-encoding: gzip
date: Thu, 11 Sep 2014 07:23:10 GMT
expires: Thu, 11 Sep 2014 07:23:10 GMT
cache-control: private, max-age=0
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
server: GSE
alternate-protocol: 443:quic,p=0.002
transfer-encoding: chunked
BODY: {"error":{"errors":[{"domain":"global","reason":"backendError","message":"An unexpected error occurred. Please try your request again."}],"code":503,"message":"An unexpected error occurred. Please try your request again."}}

If there's something that I'm doing wrong here, it would be great if the response method could indicate what was going on.

Just noting this down in case someone else stumbles in to the same problem.  This was eventually resolved this morning; the service account user that is using the API needs to have manage and view access to the Google Tag Manager account, not just the container that is present on the site being verified.
The level of access required is surprisingly high and the HTTP 503 response is very misleading as to the underlying problem.


Fix/cluttered leading blog page 871

Pull Request Checklist

[x] I have added screenshots and videos to show before and after the working of my code.
[x] I have ensured that the screen size is set to 100% while making the video.
[x] I have synced the latest fork with my local repository and resolved any conflicts.
[x] I have mentioned the issue number which I created before making this PR .(format to mention issue number is : fixes #(issue number) )
[x] I understand that if any the above conditions are not met , my PR will not be MERGED .

Kindly refork and resync

PR being closed due to not following even 1 POINT of the PR checklist , open a new pr with EACH POINT FOLLOWED


Remove reqwest dependency

Converting to a draft for the time being for further consideration

@KendallWeihe The failure is that we expect Web5Error::Network("failed to lookup address information") but instead we're getting Web5Error::Network("No such host is known"). All that differs is the text of the error message returned to us by TcpStream::Connect in http.rs.
I suspect that Windows rust implementation of TcpStream::connect returns one error message and Mac and Linux return another. In both cases, the error message conveys the same thing, i.e. This host isn't valid.
I'd be comfortable just updating the test to accept either error message. I added a commit doing this.

On second thought, I want to spend more time further contemplating the implications here. Moving back to a draft for the time being.

A leading alternative idea I have here: use reqwest inside the web5 crate, but compile it out during binding, and over the FFI expose the ability to inject an http client lib into web5 from the target languages native runtime. So in other words, for cross language bindings, we enable bring-your-own http client lib. This may be the best of both worlds; more overhead, but we compile away openssl/ring/etc so we reduce the byte code file size in the same way, and we're less likely to run into openssl bugs.

A leading alternative idea I have here: use reqwest inside the web5 crate, but compile it out during binding, and over the FFI expose the ability to inject an http client lib into web5 from the target languages native runtime. So in other words, for cross language bindings, we enable bring-your-own http client lib. This may be the best of both worlds; more overhead, but we compile away openssl/ring/etc so we reduce the byte code file size in the same way, and we're less likely to run into openssl bugs.

FWIW, that's similar to the approach that ktor uses to support different platforms. See here, for more details.


Upgrade to Buf CLI version 1.35.1

This currently disables two tests in BreakingWithProtobufGradleTest:

normally breaking schema with an ignore
schema with multi-directory workspace

I'm still trying to see if I can reasonably get them to pass.

@andrewparmet I was able to get almost everything to pass with fairly minimal changes:

Specify Buf version 1.31.0 for two tests that use buf.yaml alongside bufwork.yaml:

BreakingWithWorkspaceTest/normally_breaking_schema_with_an_ignore
GenerateWithWorkspaceTest/buf_generate_with_default_template_file_path_explicitly_specifying

When generating a virtual workspace for the Protofbuf plugin, generate a v2 buf.yaml file instead of buf.work.yaml
Temporarily ignore the test BreakingWithProtobufGradleTest/normally_breaking_schema_with_an_ignore. This test case runs into the json-vs-json buf breaking issue.

This should allow things to move forward. Next steps are to get the ignored test to pass and do add additional test coverage for cases that combine v2 buf.yaml files with usage of the Protofbuf plugin.

I think there are still some test behaviors that need to be nailed down, but I think this is a reasonable milestone with all existing tests passing and minimal behavior changes.

For some reason a few tests were failing depending on how the Jackson object mapper was initialized. I will look into it further, but for now tests are all passing in CI.


World hopper shows up as world switcher in side bar

Can we either rename the plugin to world switcher or rename the side bar icon to world hopper for consistency.

The plugin do not provides only the world switcher functionality, but also keyboard shortcuts for hopping. I dont see why the names should be consistent

Maybe the main option doesn't need to be consistent with the sidebar hover text, but the option to enable the sidebar specifically ("Show world hopper sidebar") should be.


[SPI] Latches

Hey, I have found 5 latches in the SPI core generated for the earlgray design. I was following the getting-started instructions for FPGA. Are those latches intentional?

The design was generated from: d4d5d2f3bb87af5ca2f2787af5bc19bee04ffc6a
Here is the vivado log file:
vivado.log

Thanks @rw1nkler for reporting. @eunchan can look into it soon.

Thanks! I missed the default value part in the always_comb block. Thanks for the report I will revise and update the design. Curious why this isn't catched by lint tool...

The lint miss is actually a much bigger concern to me.  Who would normally try to figure this out?

The lint miss is actually a much bigger concern to me. Who would normally try to figure this out?

Should be me. I will check the lint result again.

Hum.. checked lint report again but cannot find latch error.. @msfschaffner you have better knowledge than me about the lint, do you know how to enable to catch latches?

Thanks for catching this @rw1nkler!
Let me check why this has not been flagged by lint.
That is something we should amend in our policy.

So after a few experiments with that particular part of the FSM, I can say that this issue is likely a YAVSI (yet another Vivado synthesis issue ;)). I.e., the code enumerates all possible states in that always_comb block. Our linter has rules to check for this and will complain if 1) the always_comb semantics are violated, and 2) if latches are inferred. If you remove one branch from the affected if / else statement, our linter correctly flags this.
For now, #2004 should fix this, but I am going to report this to Xilinx as well.

Thanks @msfschaffner . So the lint tool is smart enough to check whether the if..else if meets full condition or not but Vivado doesn't. Anyway I will keep it in my mind to use else explicitly.

Yep, thank you @msfschaffner for checking this out!


Unexpected end of JSON input

After upgrading to latest, i am now getting this error:
today at 6:00:02 PM SyntaxError: Unexpected end of JSON input
today at 6:00:02 PM    at JSON.parse ()
today at 6:00:02 PM    at JSONFileSync.read (file:///usr/src/app/node_modules/lowdb/lib/adapters/JSONFileSync.js:25:25)
today at 6:00:02 PM    at LowSync.read (file:///usr/src/app/node_modules/lowdb/lib/LowSync.js:24:34)
today at 6:00:02 PM    at file:///usr/src/app/dist/db.js:15:4
today at 6:00:02 PM    at ModuleJob.run (internal/modules/esm/module_job.js:183:25)
today at 6:00:02 PM    at async Loader.import (internal/modules/esm/loader.js:178:24)
today at 6:00:02 PM    at async Object.loadESM (internal/process/esm_loader.js:68:5)
today at 6:19:02 PM file:///usr/src/app/node_modules/lowdb/lib/adapters/JSONFileSync.js:25
today at 6:19:02 PM            return JSON.parse(data);

Looks like your cache file may have gotten corrupted. Take a look at it and fix the problem, or just delete it, and that should fix your problem.

Looks like your cache file may have gotten corrupted. Take a look at it and fix the problem, or just delete it, and that should fix your problem.

Looks like my cache.json file got corrupted, and is now 0 bytes..  This happens everytime i restart cross-seed

Looks like my cache.json file got corrupted, and is now 0 bytes..  This happens everytime i restart cross-seed

Sorry, you can close.. My cache file is 72MB, and if cross-seed gets stopped during a run, it will corrupt it

Sorry, you can close.. My cache file is 72MB, and if cross-seed gets stopped during a run, it will corrupt it

Thanks for writing in, that's actually very helpful information.

Thanks for writing in, that's actually very helpful information.


Map does not load when on the same page as Autocomplete field

Hello,
I am trying to use the autocomplete and google map on the same page and can't get it to work. I'm probably doing something wrong, but what?
The autocomplete field works good but the map does not display. If I manually call load_ivory_google_map from chrome javascript console, then the map loads well and works as expected.
When I look at the generated code, it seems that "load_ivory_google_map" is never called, because when loading the google api in "load_ivory_google_map_api", the callback is defined as "load_ivory_google_place" which never call in turn load_ivory_google_map ...
In my twig page:
            {{ google_map_css(map) }}
            {{ google_map_container(map) }}
            {{ google_map_js(map) }}

           {{ form_widget(eventform.country) }}

in my formtype:
   $builder->add('country', 'places_autocomplete', array(
                    'mapped' => false,
                    // Javascript prefix variable
                    'prefix' => 'googleplace_country',
                    // Autocomplete types
                    'types'  => array(
                        AutocompleteType::CITIES,
                        // ...
                    ),

                    // TRUE if the autocomplete is loaded asynchonously else FALSE
                    'async' => true,

                    // Autocomplete language
                    'language' => 'en',
                ))

The way I build my map:
        $map = $this->get('ivory_google_map.map');
        $map->setLanguage($this->get('request')->getLocale());

my config file:
ivory_google_map:
    api:
        libraries: [ "places" ]
    map:
        # You own map class
        #class: "My\Fucking\Map"

        # Your own map helper class
        #helper_class: "My\Fucking\MapHelper"

        # Prefix used for the generation of the map javascript variable
        prefix_javascript_variable: "map_"

        # HTML container ID used for the map container
        #html_container: "map_canvas"

        # If this flag is enabled, the map will load asynchronous
        async: true

        # If this flag is enabled, the map will autozoom on the overlays added
        auto_zoom: false

        # Center coordinate of the map
        # If the autozoom flag is enabled, the center is not used
        center:
            longitude: 0
            latitude: 0
            no_wrap: false

        # Zoom of the map
        # If the autozoom flag is enabled, the zoom is not used
        zoom: 3

        # Bound of the map
        # If the auto zoom flag is not enabled, the bound is not used
        # If the bound extends overlays, coordinates of the overlays extended are used instead of these coordinates
        # By default, there is no bound
#        bound:
#            south_west:
#                latitude: -2.1
#                longitude: -3.9
#                no_wrap: true
#            north_east:
#                latitude: 2.6
#                longitude: 1.4
#                no_wrap: true

        # Default map type
        # Available map type : hybrid, roadmap, satellite, terrain
        type: "roadmap"

        # Map width
        width: "200px"

        # Map height
        height: "200px"

        # Custom map options
        # By default, there is no map options
        map_options:
            disableDefaultUI: false
            disableDoubleClickZoom: false

        # Custom stylesheet options
        # By default, there is no stylesheet options except width & height
        stylesheet_options:
            border: "1px solid #000"
            background-color: "#fff"

        # google map Api language, default en
        language: en

Your issue has been fixes in #159 but will only be part of the 3.x version of the bundle.


chore: Send all search synchronisation events to a single queue

Instead of using multiple queues/streams all the events are now sent to a single stream search.sync. They are only intended to synchronize data between data-services and search-service.
This requires a change to the Event.queue field. It was used for two things: the redis qeue/stream name and the message type. Now these two are different now and so the event must carry both separately. Events are first stored to the postgres database as single value (its avro payload) and the qeue name is stored alongside. When re-creating the event object from the database, we don't have the (header, payload) tuple, but only a dict[str, Any] (the raw message). This is different to when creating the event from a message-type and structured avro object. Since we never need to read the structured avro object of an event, the Event class is now simplified to only carry the raw message. This makes the generic type param obsolete and removes the early return in the serialize method which checked the payloads runtime type (as when read from the db).
The serialize method is still there to keep the interface, allowing perhaps later to add more structure to the class.
Additional to the canonical constructor of the event, there is a second one, create, for creating an event from a structured avro object and message type.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>7
Details

26 of 26 (100.0%)  changed or added relevant lines in 3 files are covered.
4 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.03%) to 90.505%

Files with Coverage Reduction
New Missed Lines
%

components/renku_data_services/storage/blueprints.py
2
95.26%

components/renku_data_services/storage/models.py
2
85.37%

Totals

Change from base Build<PHONE_NUMBER>4:
0.03%

Covered Lines:
9274

Relevant Lines:
10247

💛  - Coveralls


asyncSplitAt with optimization

Okay, now I'm really out of ideas with this one.
I not sure if asyncSplitAt needs optimization. The main use case of splitAt (sync version) is destructuring, async version exist mainly to fill the gap.
Anyway, I give up on this. @conartist6 @sithmel If you guys know how to fix the issue without complicating the code, you're free to try. Otherwise, I think async version that uses asyncFork/asyncTee

OK I fixed it. It was indeed a bit tricky. Let me write some better tests and I'll put up a PR


Editing Strike from Scale GUI fails on validate.

When editing a Scale Strike from the GUI. when one clicks validate it gives an "Invalid strike configuration error. {.....} is not of type string."  We have to create a whole new strike in order for our edits to work.

I also ran into the same issue. Here are my notes:
The Strike UI page is submitting an invalid JSON to the create strike API. It appears that it is sending a workspace JSON object instead of just the workspace name string for the "new_workspace" field.


Release 11/10 - v3.0

Description of changes

Issue #, if available

Description of how you validated changes
Checklist

[ ] PR description included
[ ] yarn test passes
[ ] Tests are [changed or added]
[ ] Relevant documentation is changed or added (and PR referenced)

Integ tests that are failing are due to cypress timeout issues. I tested manually verified the tests work with @elorzafe and will work on a separate change to update the integ test timeout