Easy stacks parameter tiers

Description of your changes
This PR is a placeholder for discussions around what configuration sets we want to have as easy stacks and not intended to be merged. Folder structure and namings are subject to change per one-pager coming for #1095 .
The folder easystacks_temp consists of configuration sets for 3 cloud providers. I imagine we'll likely have small, medium and large options for each of them, in total 9 different configuration set. Right now, all tiers are copies of each other. Via reviews on this PR, we can arrive on the best suited parameters for each. We start with the minimal configuration set for each provider.
Initial configuration values are taken from Wordpress example, a few things are updated like Azure k8s version from 1.12.8 to 1.14.8.
Likely, we'll have a generic controller as base per #1095 and each set will fork from that, change the values/files and publish as stack. It could be the case that stack CRD to expose a spec field like tier and user can use which tier they'd like to use without needing to install a different stack for different tiers. So, there would be 3 stacks, one for each provider but one stack might include more than 1 configuration set. All those implementation details to be discussed on #1095
The files look like this right now: (for easy browsing)
├── aws
│   ├── environment
│   └── resources
├── azure
│   ├── environment
│   └── resources
└── gcp
    ├── environment
    └── resources

[skip ci]

How has this code been tested?

Checklist

I have:

[ ] Run make reviewable to ensure this PR is ready for review.
[ ] Ensured this PR contains a neat, self documenting set of commits.
[ ] Updated any relevant documentation and examples.
[ ] Reported all new error conditions into the log or as an event, as
appropriate.

For more about what we believe makes a pull request complete, see our
definition of done.

Great! :squid:
Only two thoughts so far:

Did we intentionally use resources as the folder name in the AWS packs, but services in the other ones? It seems like they're fulfilling the same purpose, so I'm not sure why we have two different names instead of a single one.
I would lean more toward creating a single "tier" for now, especially if we only know what one of the tiers would look like. We can add more in the future. I also suspect that tiers will be roughly aligned with use-cases. For example, the first tier that we provide will probably be intended to provide sensible defaults so that someone can play around with examples easily, so I'm not sure yet whether a name like "small", "medium", or "large" even makes sense for that example tier.

I imagine we'll likely have small, medium and large options for each of them, in total 9 different configuration set.

Is size the only variant we expect to need? I'm wondering whether we might also want, for example, resource classes with different access strategies. I can't imagine everyone will want to create a whole new VPC just to deploy a database, for example. Do we need an alternative that allows them to deploy into an existing VPC, or allow traffic from a particular IP range rather than a private VPC?
Perhaps it would help to identify some common user stories for folks who would be installing an Easy Stack? Are we targeting folks coming to Crossplane with a fresh new cloud provider account and no opinions about how infrastructure works?

I would lean more toward creating a single "tier" for now, especially if we only know what one of the tiers would look like. We can add more in the future.

Yeah, I guess you're right. I'll scope down this PR into 1 configuration set for each provider.

Did we intentionally use resources as the folder name in the AWS packs, but services in the other ones? It seems like they're fulfilling the same purpose, so I'm not sure why we have two different names instead of a single one.

Not intentionally, resources is the one for now. Though both the folder structure and naming of the resources are subject to change. I wanted this PR only to discuss what the actual parameters should be. I believe it's better to discuss the folder structure in #1095 since it'll be somehow tied to how the controller will work.

Are we targeting folks coming to Crossplane with a fresh new cloud provider account and no opinions about how infrastructure works?

I think this is the initial intent. I am updating this PR to create a minimal version of each resource class. I will try to make sure publishing a new configuration set is as easy as dumping your YAML files and build the stack.

Nice. This is a bit of a nitpick, but I believe it still makes sense to have the resource pack name in the folder path, so that it's easier to add more of them later. Maybe something like changing cluster/easystacks_temp/aws to cluster/easystacks_temp/quickstart-aws would work well. I'm not sure whether quickstart-aws or aws-quickstart would be better; guess it depends on how people are searching for them, and whether they want multiple providers or not.

Maybe something like changing cluster/easystacks_temp/aws to cluster/easystacks_temp/quickstart-aws would work well.

This PR is not intended to be merged though. It's just to show what configurations will go into each easy stack. So, the folder name in cluster/easystacks_temp/<foldername> doesn't really matter.

All easy stacks implementations are completed and this PR is updated with the validated configurations.
Here is the repositories:
https://github.com/muvaf/minimal-gcp
https://github.com/muvaf/minimal-aws
https://github.com/muvaf/minimal-azure
This is the generic reconciler used by all of them:
https://github.com/muvaf/crossplane-resourcepacks
When template stacks are ready, easy stacks will be ported to template stacks and their repositories will live under crossplaneio org.
@prasek @jbw976 actually I think we can move them right away since eventually they will be moved, template stacks porting work could be a PR instead of a new repo. What do you think?

@prasek @jbw976 actually I think we can move them right away since eventually they will be moved, template stacks porting work could be a PR instead of a new repo. What do you think?

I would love to move them sooner than later, I am actually a fan of always using the crossplaneio org even for prototyping work.
What exactly needs to be moved right now to the crossplaneio org? The repos listed below? Can you open an issue with all the information so that we can follow up on that soon? Thanks @muvaf!

https://github.com/muvaf/minimal-gcp
https://github.com/muvaf/minimal-aws
https://github.com/muvaf/minimal-azure
https://github.com/muvaf/crossplane-resourcepacks

I am actually a fan of always using the crossplaneio org even for prototyping work.

@jbw976 Honestly, I didn't know how to do it properly with the specific licensing stuff, upbound build and all and you were away, so I just didn't want to be blocked.
Here is the issue https://github.com/crossplaneio/crossplane/issues/1136


Website should be responsive , not working properly in Mobile Browser

@chocos10 wanna to do it :P


really need a serious xml builder

{"Name"=>"Color", "Value"=>["Black", "Pink", "Yellow", "Blue"]} went in
and
<Name>Color</Name><Value>BlackPinkYellowBlue</Value> went out
which should be
<Name>Color</Name><Value>Black</Value><Value>Pink</Value><Value>Yellow</Value><Value>Blue</Value>
why not try ActiveSupport or something?

well, i see
you prefer another way to handle that array params, to input
{"Name"=>"Color", [{"Value"=>"Black"}, {"Value"=>"Pink"}, {"Value"=>"Yellow"}, {"Value"=>"Blue"}]}
ummm, but this is not so common...
i would like to have my own fork :-(

looking through the forks i found this commit https://github.com/meismann/ebayr/commit/d7c46e2c3e56c6dd40350fcaac5e35bec4a05505

Look's ready to go except that the hash's use the ruby 1.9 syntax "{asdf: 1}." We target 1.8.3+

I disagree with the title of the issue, @CicholGricenchos - "need" is too strong a word. Of course I started with XML builder libraries (nobody with any experience writes XML processors without good reason); if you dig through the history, you might find some old versions that used various libraries (including ActiveSupport, Nokogiri::XML::Builder, and even REXML). I systematically abandoned them one by one, for various reasons (poor Ruby version compatibility, inappropriate APIs, or way too many gem dependencies). Eventually I determined that the more reasonable course of action for the very predictable XML output requirements of eBayR was a (thoroughly tested), bare-bones custom job.
So I need to be convinced. Please feel free to fork the project, and if a pull request comes in which replaced eBayR's built-in XML processors, provably works on all Ruby version from 1.8.7 onwards, includes benchmarks indicating a significant speedup, and has the support of the other developers, I'll of course be quite happy to merge it into master and release a new version.

Sorry for that phrasing, since I don't daily use English..
I knew more about the situation now, thank you and your post!

You're welcome, @CicholGricenchos, and it's a credit to your English that I didn't notice you weren't a native speaker. :gb:


Operation cannot be fulfilled on certificates.certmanager.k8s.io "my-domain-test": StorageError: invalid object, Code: 4

/kind bug
What happened:
This is more of a request for help than necessarily a bug. Apologies if its just interpretation of the docs.
After installing cert-manager with helm, creating a ingress, issuer and cert i get the following error on cert creation:
kubectl describe certificate my-test-cert watch
Events:
  Type     Reason                 Age   From                     Message
  ----     ------                 ----  ----                     -------
  Warning  ErrorCheckCertificate  9s    cert-manager-controller  Error checking existing TLS certificate: secret "my-domain-test not found
  Normal   PrepareCertificate     9s    cert-manager-controller  Preparing certificate with issuer
  Normal   PresentChallenge       9s    cert-manager-controller  Presenting http-01 challenge for domain my-example.co
  Normal   SelfCheck              9s    cert-manager-controller  Performing self-check for domain my-example.co
Error from server (NotFound): certificates.certmanager.k8s.io "watch" not found

I've replaced the real domain with my-example.co here.

Installed

How to reproduce it (as minimally and precisely as possible):
My domain has a static ip and the domain resolves successfully. Content is served through the following ingress. I'm able to reach the site through http.
---
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: kibana
  annotations:
    kubernetes.io/ingress.global-static-ip-name: my-static-ip
  labels:
    app: kibana
spec:
  tls:
  - hosts:
    - my-example.co
    secretName: my-domain-test
  backend:
    serviceName: nginx-service
    servicePort: 80
  rules:
  - host: my-example.co
---

My issuer:
apiVersion: certmanager.k8s.io/v1alpha1
kind: Issuer
metadata:
  name: letsencrypt-issuer
  namespace: default
spec:
  acme:
    # The ACME server URL
    server: https://acme-staging.api.letsencrypt.org/directory
    # Email address used for ACME registration
    email<EMAIL_ADDRESS>    # Name of a secret used to store the ACME account private key
    privateKeySecretRef:
      name: letsencrypt-key
    # Enable the HTTP-01 challenge provider
    http01: {}

Finally, my cert:
---
apiVersion: certmanager.k8s.io/v1alpha1
kind: Certificate
metadata:
  name: my-example.co
  namespace: default
spec:
  secretName: my-domain-test
  issuerRef:
    name: letsencrypt-issuer
  commonName: my-example.co
  acme:
    config:
    - http01:
        ingress: kibana
      domains:
      - my-example.co

Note: I've referenced my ingress through
    - http01:
        ingress: kibana

I interpreted the docs to indicate the ingress will be modified to intercept the http challenge.
Environment:

Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.0", GitCommit:"fc32d2f3698e36b93322a3465f63a14e9f0eaead", GitTreeState:"clean", BuildDate:"2018-03-26T16:55:54Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"9+", GitVersion:"v1.9.6-gke.1", GitCommit:"cb151369f60073317da686a6ce7de36abe2bda8d", GitTreeState:"clean", BuildDate:"2018-04-07T22:06:59Z", GoVersion:"go1.9.3b4", Compiler:"gc", Platform:"linux/amd64"}

Cloud provider or hardware configuration**: GCP
Install tools: helm via helm install --name cert-manager --namespace kube-system stable/cert-manager

Possible duplicate - https://github.com/jetstack/cert-manager/issues/347

Could you try again with v0.3.0 and report back? There have been considerable changes since v0.2.3 😄

I have the same issue 0.3.1


Configure maxAttempts

What version of Shaka Player are you using?:
2.4.1
What did you do?
Attempt to access maxAttempts from retryParameters.
What did you expect to happen?
Get the value of maxAttempts
What actually happened?
"Assertion failed: only methods on Player"
I am trying to add some custom error handling; a 'diagnostic mode'. Essentially, pass in a predefined parameter and the player enters a debug mode, where error stacks, stats and such-like are printed to the display. That works fine; however, I seem to have hit a stumbling block with getting at the maxAttempts defined in shakaPlayer.player_.configure().
For simplicities sake, I'm looking to do something along the lines of:-
     if (!shakaPlayer.player_.networkingEngine_.manifest.retryParameters.maxAttempts) {
console.log('do something');
}

But evidently, I am getting the "only methods on Player" error.  I can see I can get the default parameters from shaka.net.Backoff but how can I access those set in configure()? Went round and round in circles with this today and didn't gain any headway!
Thanks.

If you want access to the values in the current configuration, try Player.prototype.getConfiguration():
player = new shaka.Player(videoElement);
// ...
const maxAttempts = player.getConfiguration().manifest.retryParameters.maxAttempts;

You may also be interested in the config tutorial, which introduces the basic config concepts and API.
Does this answer your question?

Thanks @joeyparrish. That did the job; cheers.


Improve SoraStream provider

Summary
Implement more extractors
Please confirm the following

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.

I didn't have time to add all the extractors, so for now there is only one

Nothing is working and can we please have subtitles

Nothing is working

Make an issue about this!

can we please have subtitles

I don't know if it's possible but I'll look into it

Add 2-3 new video servers in TMDb provider on Release 1.6.8

Add 2-3 new video servers in TMDb provider on Release 1.6.8

You're a legend. Well done!

First thank you for your great effort
Latest provider update of TMDB doesn't support Arabic subtitles it's even not support subtitles at all , so it's temporary useless

Add 2-3 new video servers in TMDb provider on Release 1.6.8

They all doesn't support subtitles !!

They all doesn't support subtitles !!

Duplicate of #132


New version: ByteDance.Doubao version 1.22.6

Created by 🥟 Dumplings in workflow run #8027.

Log
Updated: 1.21.3 → 1.22.6
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

@wingetbot run

This package installs and launches normally in a Windows 10 VM.


🐛 Bug Report: Bitbucket Cloud integration maxes out at 900 repositories

📜 Description
We have been struggling with a fluctuating amount of components for a while now, with some components being suddenly unavailable, and we have narrowed it down to an issue with the Bitbucket Cloud integration.
As far as I can tell, this happens because Bitbucket Cloud's API (specifically this one) doesn't go past 1000 repositories.
In page 9, the property next is missing. It's possible to go to page 10 by calling the endpoint manually, but as soon as you try to go page 11 it returns "Cannot fetch results past result number 1000".
Same goes for pages with a higher pagelen: for some reason the maximum pagelen is 373, so if we use a pagelen of 373, it works until we try to go to page 3, since it exceeds 1000 results.
I'm not sure how to resolve this since it sounds like a limitation in Bitbucket Cloud's API, so I would love to discuss possible solutions in this issue. As soon as we come to a conclusion, I'd be more than happy to submit a fix.
👍 Expected behavior
It should retrieve all repositories
👎 Actual Behavior with Screenshots
It actually maxes out at 900 repositories
👟 Reproduction steps

Use Bitbucket Cloud Locations
Have more than 900 repositories in Bitbucket

📃 Provide the context for the Bug.
{"class":"BitbucketCloudEntityProvider","level":"info","message":"Committed 900 Locations for catalog files in Bitbucket Cloud repositories","plugin":"catalog","service":"backstage","target":"bitbucketCloud-provider:default","taskId":"bitbucketCloud-provider:default:refresh","taskInstanceId":"41b49bcf-799c-4697-9980-d843c2419471"}
🖥 Your Environment
OS:   Darwin 24.0.0 - darwin/arm64
node: v20.15.1
yarn: 4.5.0
cli:  0.27.1 (installed)
backstage:  1.31.1

Dependencies:
  @backstage/app-defaults                                          1.5.11
  @backstage/backend-app-api                                       0.7.9, 0.9.3, 1.0.0
  @backstage/backend-common                                        0.17.0, 0.21.7, 0.23.3, 0.24.1, 0.25.0
  @backstage/backend-defaults                                      0.4.4, 0.5.0
  @backstage/backend-dev-utils                                     0.1.5
  @backstage/backend-openapi-utils                                 0.1.18
  @backstage/backend-plugin-api                                    0.6.21, 0.7.0, 0.8.1, 1.0.0
  @backstage/backend-tasks                                         0.5.27, 0.6.1
  @backstage/backend-test-utils                                    1.0.0
  @backstage/catalog-client                                        1.7.0
  @backstage/catalog-model                                         1.7.0
  @backstage/cli-common                                            0.1.14
  @backstage/cli-node                                              0.2.8
  @backstage/cli                                                   0.27.1
  @backstage/config-loader                                         1.9.1
  @backstage/config                                                1.2.0
  @backstage/core-app-api                                          1.15.0
  @backstage/core-compat-api                                       0.2.8, 0.3.0
  @backstage/core-components                                       0.12.5, 0.13.10, 0.14.10, 0.15.0
  @backstage/core-plugin-api                                       1.9.4
  @backstage/dev-utils                                             1.1.0
  @backstage/errors                                                1.2.4
  @backstage/eslint-plugin                                         0.1.9
  @backstage/frontend-plugin-api                                   0.6.7, 0.7.0, 0.8.0
  @backstage/integration-aws-node                                  0.1.12
  @backstage/integration-react                                     1.1.31
  @backstage/integration                                           1.15.0
  @backstage/plugin-api-docs                                       0.11.9
  @backstage/plugin-app-backend                                    0.3.74
  @backstage/plugin-app-node                                       0.1.25
  @backstage/plugin-auth-backend-module-atlassian-provider         0.3.0
  @backstage/plugin-auth-backend-module-auth0-provider             0.1.0
  @backstage/plugin-auth-backend-module-aws-alb-provider           0.2.0
  @backstage/plugin-auth-backend-module-azure-easyauth-provider    0.2.0
  @backstage/plugin-auth-backend-module-bitbucket-provider         0.2.0
  @backstage/plugin-auth-backend-module-bitbucket-server-provider  0.1.0
  @backstage/plugin-auth-backend-module-cloudflare-access-provider 0.3.0
  @backstage/plugin-auth-backend-module-gcp-iap-provider           0.3.0
  @backstage/plugin-auth-backend-module-github-provider            0.2.0
  @backstage/plugin-auth-backend-module-gitlab-provider            0.2.0
  @backstage/plugin-auth-backend-module-google-provider            0.2.0
  @backstage/plugin-auth-backend-module-guest-provider             0.2.0
  @backstage/plugin-auth-backend-module-microsoft-provider         0.2.0
  @backstage/plugin-auth-backend-module-oauth2-provider            0.3.0
  @backstage/plugin-auth-backend-module-oauth2-proxy-provider      0.2.0
  @backstage/plugin-auth-backend-module-oidc-provider              0.3.0
  @backstage/plugin-auth-backend-module-okta-provider              0.1.0
  @backstage/plugin-auth-backend-module-onelogin-provider          0.2.0
  @backstage/plugin-auth-backend                                   0.23.0
  @backstage/plugin-auth-node                                      0.4.17, 0.5.2
  @backstage/plugin-auth-react                                     0.1.6
  @backstage/plugin-bitbucket-cloud-common                         0.0.0-use.local
  @backstage/plugin-catalog-backend-module-aws                     0.4.2
  @backstage/plugin-catalog-backend-module-bitbucket-cloud         0.3.2
  @backstage/plugin-catalog-backend-module-github                  0.7.3
  @backstage/plugin-catalog-backend-module-scaffolder-entity-model 0.2.0
  @backstage/plugin-catalog-backend-module-unprocessed             0.5.0
  @backstage/plugin-catalog-backend                                1.26.0
  @backstage/plugin-catalog-common                                 1.1.0
  @backstage/plugin-catalog-graph                                  0.4.9
  @backstage/plugin-catalog-import                                 0.12.3
  @backstage/plugin-catalog-node                                   1.13.0
  @backstage/plugin-catalog-react                                  1.13.0
  @backstage/plugin-catalog-unprocessed-entities-common            0.0.4
  @backstage/plugin-catalog-unprocessed-entities                   0.2.8
  @backstage/plugin-catalog                                        1.23.0
  @backstage/plugin-devtools-backend                               0.4.0
  @backstage/plugin-devtools-common                                0.1.12
  @backstage/plugin-devtools                                       0.1.18
  @backstage/plugin-events-node                                    0.3.10, 0.4.0
  @backstage/plugin-home-react                                     0.1.17
  @backstage/plugin-home                                           0.7.10
  @backstage/plugin-kubernetes-common                              0.8.3
  @backstage/plugin-org                                            0.6.29
  @backstage/plugin-permission-backend                             0.5.49
  @backstage/plugin-permission-common                              0.7.14, 0.8.1
  @backstage/plugin-permission-node                                0.7.32, 0.8.3
  @backstage/plugin-permission-react                               0.4.26
  @backstage/plugin-proxy-backend                                  0.5.6
  @backstage/plugin-scaffolder-backend-module-azure                0.2.0
  @backstage/plugin-scaffolder-backend-module-bitbucket-cloud      0.2.0
  @backstage/plugin-scaffolder-backend-module-bitbucket-server     0.2.0
  @backstage/plugin-scaffolder-backend-module-bitbucket            0.3.0
  @backstage/plugin-scaffolder-backend-module-cookiecutter         0.3.0
  @backstage/plugin-scaffolder-backend-module-gerrit               0.2.0
  @backstage/plugin-scaffolder-backend-module-gitea                0.2.0
  @backstage/plugin-scaffolder-backend-module-github               0.5.0
  @backstage/plugin-scaffolder-backend-module-gitlab               0.5.0
  @backstage/plugin-scaffolder-backend                             1.25.0
  @backstage/plugin-scaffolder-common                              1.5.6
  @backstage/plugin-scaffolder-node                                0.4.11
  @backstage/plugin-scaffolder-react                               1.12.0
  @backstage/plugin-scaffolder                                     1.25.0
  @backstage/plugin-search-backend-module-catalog                  0.2.2
  @backstage/plugin-search-backend-module-elasticsearch            1.5.6
  @backstage/plugin-search-backend-module-explore                  0.2.2
  @backstage/plugin-search-backend-module-techdocs                 0.2.2
  @backstage/plugin-search-backend-node                            1.3.2
  @backstage/plugin-search-backend                                 1.5.17
  @backstage/plugin-search-common                                  1.2.14
  @backstage/plugin-search-react                                   1.8.0
  @backstage/plugin-search                                         1.4.16
  @backstage/plugin-signals-react                                  0.0.5
  @backstage/plugin-techdocs-backend                               1.10.13
  @backstage/plugin-techdocs-common                                0.1.0
  @backstage/plugin-techdocs-module-addons-contrib                 1.1.14
  @backstage/plugin-techdocs-node                                  1.12.11
  @backstage/plugin-techdocs-react                                 1.2.8
  @backstage/plugin-techdocs                                       1.10.9
  @backstage/plugin-user-settings-common                           0.0.1
  @backstage/plugin-user-settings                                  0.8.12
  @backstage/release-manifests                                     0.0.11
  @backstage/test-utils                                            1.6.0
  @backstage/theme                                                 0.2.19, 0.5.7
  @backstage/types                                                 1.1.1
  @backstage/version-bridge                                        1.0.9

👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
Yes I am willing to submit a PR!

In the meantime, I have found a solution that works for us by first retrieving all projects and then calling the endpoint for each project. This moves the limit from 900 repositories per workspace to 900 repositories per project.
I'm thinking of wrapping up a PR that allows you to choose some sort of mode to allow this.

Oh wow, well that's not great is it? Seems a little strange that you can only get half the results back with BitBucket API's, there must be a better way to query the API to get a list of all them for sure. See what you can come up with and let's take a look in a review :pray:

@benjdlambert if I'm understanding the code correctly, we're specifically searching for repositories that contain a catalog-info.yaml file, which also helps with creating the location of this file, so I'm not sure if there is a good alternative.
My PR should be ready today and then I'm off for 2 weeks, just a heads-up in case I don't respond 😅

Unfortunately, there is an issue with the Bitbucket Cloud API and its pagination that I tried to address with Atlassian. So far, they were not very helpful on that one.
The issue is that the result set has no stable order and the pagination is page-based. Hence, going through all pages does not mean you will get all the results. You might have received some results more than once and others not at all.
I was already thinking about a solution for that one...

This specific issue has been fixed in #26873, so I guess it can be closed? @pjungermann @benjdlambert

Gonna close as fixed by #26873, let's handle other potential bugs in new issues


doc: add runtime/README.md and libextism/README.md

C: https://github.com/extism/extism/blob/new-readmes/libextism/README.md
Rust: https://github.com/extism/extism/blob/new-readmes/runtime/README.md
Also includes some small usability improvements I stumbled across when working on the docs

Merging this to get it out of the way to the namespace changes, we can make more doc updates in future PRs if needed.


Support HDF5 datasets

Can we add h5py as a dependency to the viewer workers ? It's a pretty common dependency for vision datasets since it allows to read hdf5 files which is common in this field (used by 180k+ repos on github)
related to https://huggingface.co/datasets/sayakpaul/nyu_depth_v2/discussions/5#638a1d4dc7f3cc0d220ea643
cc @severo

It's already installed:
https://github.com/huggingface/datasets-server/blob/main/workers/datasets_based/poetry.lock#L673

❤


[UI][Bug Hunt] Enabled clickaway feature on the context-switcher | CU-232yuch

Signed-off-by: asubedy<EMAIL_ADDRESS>Description
Enabled clickaway feature.
This PR fixes #
Notes for Reviewers
*Signed commits
https://user-images.githubusercontent.com/51183483/157248555-94aad0d2-f6da-4123-907f-27ae60424ec6.mov

[ ] Yes, I signed my commits.

Task linked: CU-232yuch Add a ClickAwayListener to the context switcher

Codecov Report

Merging #5181 (b8fd4c9) into master (705dbad) will decrease coverage by 8.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #5181      +/-   ##
==========================================
- Coverage   31.81%   23.81%   -8.01%
==========================================
  Files          62       62
  Lines        5287     5287
==========================================
- Hits         1682     1259     -423
- Misses       3186     3754     +568
+ Partials      419      274     -145

Flag
Coverage Δ

gointegrationtests
?

unittests
23.81% <ø> (ø)

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

Impacted Files
Coverage Δ

mesheryctl/internal/cli/root/system/update.go
1.05% <0.00%> (-58.95%)
:arrow_down:

mesheryctl/internal/cli/root/system/status.go
1.14% <0.00%> (-55.18%)
:arrow_down:

mesheryctl/internal/cli/root/system/start.go
1.91% <0.00%> (-54.55%)
:arrow_down:

mesheryctl/internal/cli/root/system/restart.go
1.92% <0.00%> (-48.08%)
:arrow_down:

mesheryctl/internal/cli/root/system/stop.go
2.15% <0.00%> (-44.61%)
:arrow_down:

mesheryctl/internal/cli/root/system/logs.go
3.26% <0.00%> (-36.96%)
:arrow_down:

mesheryctl/internal/cli/root/system/check.go
1.03% <0.00%> (-23.03%)
:arrow_down:

mesheryctl/internal/cli/root/system/dashboard.go
1.49% <0.00%> (-16.42%)
:arrow_down:

mesheryctl/pkg/utils/healthcheck.go
8.82% <0.00%> (-4.42%)
:arrow_down:

Continue to review full report at Codecov.

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


Help to understand particles behavior when interacting with rigidbody

Hello,
For my application, I am trying to instantiate fluid particles in a mesh model of a jug. I am creating a fluid block on top of the jug and trying to run the simulation to have the particles collect inside the jug. However, the particles seem to be hitting an imaginary wall(?) outside the jug itself.
I am attaching the snapshots along with the .OBJ file of the jug and configuration+code of the environment used.
Any help rectifying this issue is highly appreciated. Thank you!

"Configuration":
	{
		"pause":true,
               "particleRadius": 0.003,
		"timeStepSize": 0.0001,
                 "cameraPosition":[0,0.5,1],
		"density0": 1000,
		"simulationMethod": 4,
		"gravitation": [0,-9.81,0],
		"cflMethod": 0,
		"cflFactor": 0.5
	}

scene.fluidBlocks.append(
        Scenes.FluidBlock(
            id='Fluid',
            box=Scenes.Box([-0.025, 0.22, -0.025], [.025, .32, .025]),
            mode=0,
            initialVelocity=[0.0, 0.0, 0.0],
            ))
scene.boundaryModels.append(Scenes.BoundaryData(
        meshFile="../models/elongated_new.obj",
        translation=[0, 0, 0], scale=[1,1,1], color=[0.5, 0.5, 0.5, 1.0], isAnimated=True,
        rotation=r,
        isWall=False, mapInvert=False, mapResolution=[25, 25, 25]))

objfile.zip

That is strange. Can you please try to delete the cache files or start with the --no-cache option?
If this does not help, try to set the value "boundaryHandlingMethod" to 0.
Hope that helps.

Hello, I deleted the cache files and tried to run it, but the results remain the same.
It seems I am unable to change the boundary method. I am using the python interface and within the json file for the scene, I set "boundaryHandlingMethod": 0. However, in gui window, under the 'Simulation' tab, I still see 'Bender et al. 2019' instead of ''Akinci et al. 2012' for the boundary handling method. Are there additional things to be configured/coded in order to change the boundary method?

Hello, looks like it had to do with the thickness of my 3d object. Once I increased the thickness, the issue seems to be resolved.
Thank you for your support!


Fix  strip common prefix

Consider this a reopened version of #665.
I've applied @jkni's (excellent) changes and made some changes, mostly for Python 3 compatibility (map returns a list in py2, but a generator in py3, so we have to flatten it to a list. I pulled out a method to do just that.).
@jkni can you please review and smoke test on Windows when you get a chance? and @ptnapoleon can you review for readability? I think Joel's changes make this much more readable but I already know the test, so.

Sufficiently readable. I wouldn't complain about comments on those variables explaining what they are, but the names are pretty descriptive. I'll leave functional review to Joel.

Both abortedcompaction_test and compaction_test pass on my Windows environment now. +1.

\o/ Thanks, all. Merging.


Feature request:  ability to change 'audit_utc_timestamp' field name in audit logging

When enabling Search Guard audit logging using Elasticsearch as the data type, is there a way to change the name of the 'audit_utc_timestamp' field name to '@timestamp' or perhaps even copy the field so both are populated?  The reason I ask due to Kibana, we create index patterns in Kibana of aliases that then contain many other indexes.  If the created Search Guard audit index is added to an alias with other security audit related logs then in Kibana only a single field is supported as the timefield.

We will include this in the next release (v24) expected next week. Thx for this feature request.


Mixed content failure after deploying Hetzner Loadbalancer

In #894, we stopped using a check for accessing data over http and https. This issue has popped up again when I tried to deploy a secured Hetzner cloud loadbalancer. Right now, I'm using a custom docker image but we need to have some kind of settings in the
flexmeasures config to decided the usage of the content over http and https.

Have you confirmed that using this setting would fix the issue in your environment?
And can you explain why it would be needed?

Now if you try to access testing subdomain, you will not see the data because the container is using our official docker image.

We are attempting to access data over https connection, but the backend currently provides the data via http connection. In order to ensure the security of our data and enable the display of charts over a secure connection https, we have to implement a Content Security Policy (CSP) with the upgrade-insecure-requests directive. This directive instructs the browser to automatically upgrade any insecure http requests to secure https requests, thereby enhancing the overall security of the web page

Okay, I see how the secure load balancer would lead to the necessity of such a policy being optional.
How should we call this new config setting?
FLEXMEASURES_ENFOREC_SECURE_CONTENT_POLICY ?
And the default value should be False
Please also document this setting in the config documentation part.


Reporting changes to binary registry keys (CHEF-5323)

@opscode/client-eng,
I'm working on CHEF-5323, and wondering what thoughts are on how to handle reporting changes in binary registry keys. Two ideas from @sersut and @adamedx are 1) don't send/track any information for binary registry keys or 2) send/track an md5/checksum so that changes to the key can be detected/indicated.

Has this fixed made it into master (Sorry I'm a Github newb)? Chef client 12.2.1 still exhibits the same behavior reported in this bug with the core registry_key resource when setting a dword value with binary data. Tested this on Windows Server 2012 R2.

@jdmundrawala, @btm, @ksubrama, here's a fun one that got buried, possibly since I don't know how to properly mention @lamont-granquist (see earlier comments).
@keyrage, it's not in master yet I'm sure since we lost track of this one. Have you found a workaround?

Maybe it regresssed somehow or there is some edge case that wasn't fixed in the first place? https://github.com/chef/chef/issues/1470 was supposed to be the fix for this, which was merged in https://github.com/chef/chef/commit/74452e993f527d76f46b5fba33993cc477691146 and GitHub says every tag from 11.14.0 up to current contains that commit.

@danielsdeleo, possibly one or the other. I cloned the source and had a look and you're right that it should be in all versions from 11.14. I deployed 12.3 and hit the same problems.
@adamedx, Whats best? Should I open a new issue? I'll create a test cookbook and data to use for testing.

Sorry, sorry.
I built a simple test cookbook and couldn't initially recreate the error. Much head scratching and head bashing against walls occurred.
Turns out the issue isn't with the registry_key resource but actually is in the attributes.rb file where the binary data for the registry_key resource declaration, is set inside double quotes rather than single quotes.

@keyrage let's keep this issue. @btm, @jdmundrawala, @ksubrama can you give a yay / nay on picking this up? @btm, if you don't have bandwidth, let's you and I talk to find someone to help.

@keyrage can you share your cookbook

Link to the test cookbook I created with the attribute set with double quotes which should generate a JSON encoding error.
https://onedrive.live.com/redir?resid=71C0037690790A7!29680&authkey=!AO7poUEgQBcvfNM&ithint=file%2Czip

I think the best thing to do here would be to base64 encode your attribute.
Thoughts?

I seem to be able to get around the issue solely by enclosing the binary data in single quotes. Is that an acceptable approach or is there possible danger in that approach? Whats the benefit of encoding in Base64? My concern is that adds additional complexity and difficulty in debugging?

when you do single quotes, it's not actually binary data:
2.1.2 (main):0 > '\x61'.length
=> 4
2.1.2 (main):0 > "\x61".length
=> 1
2.1.2 (main):0 > "\x61"
=> "a"

The benefit of Base64 encoding is that your string becomes jsonifyable, and Chef likes to turn your data into json when it communicates outside of the process.

I'm working on patches to ffi-yajl and chef-client to make sure that the node.save and reporting POST don't ever fail due to non-UTF8 characters.  chef/ffi-yajl#57 is the ffi-yajl patch.

@keyrage We're unable to reproduce the JSON encoding error with your cookbook now. I'm guessing @lamont-granquist's work on ffy-yajl prevents the error. I'm closing this, but if anyone can still replication the JSON encoding error please post reproduction steps.


XComponent React child does not load inside parent

Hello!
I am having an issue to get my React content rendered inside an xcomponent. It looks like my child component, built in ReactJS, is rendered when run in webpack-dev-server or inside an iframe.
When called using xcomponent parent it doesn't seem to render. The component does render, the iframe is created and even the CSS is displayed, however the React itself does not render inside the child (strangely if I try an alert inside the component, it does get displayed, however the component never gets mounted).
I have included xcomponent in the parent and child as the documentation says.
What am I missing here?
Thanks

I was able to find out that if directly passing window.xprops to my App component, the child component was rendered in xcomponent.
However, as I was using a react-router here, I am not really sure how to pass down window.xprops, so it would be injected into all my routes. I've tried passing down xprops to Routes component, but it seemed to cause the described issue.
Would you be able to provide an example on ReactJS with React-Router?
Thanks

Hi, I had the same question -- here is what I got working:
import React from 'react';
import { Route, Switch, BrowserRouter } from 'react-router-dom';
import zoid from 'zoid';
import MyComponent from './MyComponent';

const MyZoidComponent = zoid.create({
  tag: 'my-tag',
  url: 'my-url'
});

function App(props) {
  return (
    <BrowserRouter>
      <Switch>
        <Route
          path="/mypath"
          render={router => (
            <MyComponent {...props} {...window.xprops} {...router} />
          )}
        />
... other routes
      </Switch>
    </BrowserRouter>
  );
}

export default App;

I did not need to reference zoid in MyComponent.js ... it has no idea it is being framed by zoid or in an iframe on another site.
This is also a better example in modern React.js of how to integrate zoid ... took me a while to translate the example code.


After updating to 1.18-0.6.3.jar, previously working game instance crashes on startup

Describe the Bug
I made myself a modded Minecraft instance and have been playing in it for over a week now. Flywheel and Create are in it, and there have been no issues with them at any point up until now.
This morning, when launching the game via the Curseforge app, I noticed that there were updates available for Create and Flywheel, and so I installed them. Afterwards, Minecraft started crashing on startup. It crashes so early that no crash report is generated, but latest.log contains a severe error referencing Flywheel right at the end.
Afterwards, I manually downloaded the April releases of Flywheel and Create that I was using before this update, and put them back into my mods folder, deleting the newer versions. Now, Minecraft starts up again just fine.
Reproduction Steps
Since this may be a cross-mod incompatibility issue with something else in my modlist, I can't offer detailed reproduction steps. For me, it went simply "1.) install latest version, 2.) attempt to start game, 3.) watch it explode".
Expected Result
I expected the game to launch.
Screenshots and Videos
No response
Crash Report or Log
https://pastebin.com/vkdfYmUe
Operating System
Windows 10
What is your GPU?
Nvidia Geforce GTX 1060 6GB
Mod Version
0.6.3
Minecraft Version
1.18.2
Loader Version
Forge 40.1.52
Other Mods
They are listed in the attached logfile.
Additional Context
No response

Not an issue with flywheel. Looks like Create: Steam Powered hasn't updated to Create 0.5 yet


better secrets management

travis warning is about vignettes not being in inst/doc; pretty small for a support/research package


Compatibility with DSA/TDE Lifepoints

Hello im Playing Das Schwarze Auge/The Dark Eye (5th Edition) - Version 3.2.0 and try to configure the Lifepoints to mark an Actor as defeated. But every value i try to set, isnt working.
If i search for the values with _token.actor.data i find them under data.status.wounds.
I tried data.data.satus.wounds.value and data.status.wounds.value, but nothing works.
I have to say, that in the System, an actor counts as "defeated" if the Lifepoints go unter 0, but they can be below it.
Can you help me somehow to get this working?

i don't know all systems, but does inputing that data path in the console give you a number? also do you get any errors? Your best bet would be to ask in your system channel in the main foundry discord


Window Maximize/Restore/Resize

Is there any way to disable maximize, restore, and resize?

@xMikan09 , I added this feature recently. Check this https://podgorskiy.github.io/bimpy/bimpy.html#bimpy.Context.init
When you init context, you need to pass resizable=False to the init method.


"Include" settings on export panel are gone

The export settings panel for "Include" is empty
Screenshots

Version

OS: linux
Blender Version  2.82
Addon version 1.2.74 (installed manually)

Can you please confirm if this is happening for you as well?

Yeah, I noticed too: https://github.com/KhronosGroup/glTF-Blender-IO/issues/1040#issuecomment-623584276. For now you can fix it by updating to Blender 2.90.
Note that you'll still need at least 2.83.9 for addon version 1.2.74 though:

Well, I probably fail a merge somewhere. I will fix the 2.83 branch

OK, I just committed the fix.
This should be available in next build, probably tomorrow.
Thanks !

Great, it was fast.
Thanks so much :)

@julienduroure blender-v2.83-release is still using 2.90's CI script though.
I think it would probably be easier to use git cherry-pick instead of merging branches. So if a PR is against master and you want the change in 2.83, instead of switching the PR's base branch to 2.83, merge the PR into master normally, then cherrypick the commits you want into the 2.83 branch.

@scurest In Blender repo, the process is to merge, not using cherry-pick. This is why I'm trying to have the same process here to detect merge issue (Well, seems I failed for this one...).
https://github.com/KhronosGroup/glTF-Blender-IO/blob/f72e57ffdde87995e4f31501e783b45a56e1c560/.circleci/config.yml#L9
Is that the only line to change to get 2.83 tests back on blender-v2.83 branch?

@julienduroure Oh, okay.

Is that the only line to change to get 2.83 tests back on blender-v2.83 branch?

Yeah.


IMAGING-304 - Use Comparator combinator

Coverage remained the same at 76.667% when pulling 645f3515ed5d3bce27bfe67c583f3316cb5cd9de on arturobernalg:feature/IMAGING-304 into 9d850d22a546963b86d13322db5d28350bd4ce81 on apache:master.

Merged, thanks!


Vendor mtrmac/image:change-sigstore-layout

This demonstrates https://github.com/containers/image/pull/247 .  There is a TestCopyDockerSigstore which tests that the write staging / read HTTP paths for a sigstore are interoperable, but it does not prescribe a specific layout, so it does not need updating.

@runcom Re-vendored from master, no other changes in this repo. PTAL.

:+1:


I met an issue when I tried to init dapr with Win 10

After I installed Docker Desktop with WSL2, I ran the command "dapr init", and I got the following error messages:
PS D:\Tools\dapr> dapr init
Making the jump to hyperspace...
Container images will be pulled from Docker Hub
Installing runtime version 1.12.0
Downloading binaries and setting up components...
unable to confirm whether dapr_redis is running or exists. error
exec: "docker": executable file not found in %!P(MISSING)ATH%!(NOVERB)
I don't know how to solve it.
Thanks!

Install Docker and make sure Docker is running. If Docker is installed and running, make sure the Docker socket file exists in the default location.
https://docs.docker.com/engine/reference/commandline/dockerd/#daemon-socket-option
If you don't want to use docker initialize Dapr in slim mode dapr init --slim.

@mukundansundar please move this issue to CLI. Thanks!

Install Docker and make sure Docker is running. If Docker is installed and running, make sure the Docker socket file exists in the default location. https://docs.docker.com/engine/reference/commandline/dockerd/#daemon-socket-option
If you don't want to use docker initialize Dapr in slim mode dapr init --slim.

I'll try it, thanks!


chat mode not trigger onReady event

when I set chat as true, can not trigger onReady event

This works for me:
<div
  data-tf-widget="<form-id>"
  data-tf-on-ready="onTypeformReady"
  data-tf-chat></div>
<script src="//embed.typeform.com/next/embed.js"></script>

<script>
  function onTypeformReady(data) {
    alert('onReady')
    console.log('form ready', data)
  }
</script>

https://glitch.com/edit/#!/organic-oasis-output
Can you share more details, eg. your code please?


Nav Bar

Improved navigation bar css (detail changes). If it looks good I think this issue can be closed


Remove gennaro-tedesco/boilit

This repo has not been updated since 2021-04-17 13:31:27 UTC.
Can @gennaro-tedesco confirm whether this repo is still intended for use?

Yes, the project is still being used. However if you deem it irrelevant (or only want to keep constantly updated ones) feel free to remove :)


8Muses ripper not downloading images as jpeg

Ripme version: 1.7.59
Java version: 1.8.0_171
Operating system: Win10 Version 1803
Exact URL you were trying to rip when the problem occurred:
https://www.8muses.com/comics/album/Fred-Perry-Comics/Not-Warnerd

Expected Behavior
Expected images to be downloaded as jpeg
Actual Behavior
All downloaded images were not jpegs when the rip completed. over half the files that were downloaded were plain files without a type and were not viewable in my photo gallery

I can't reproduce this using the link you posted, but I've run into this before. It seems to be caused by 8muses not setting the content type header on all the images it returns. The most obvious way to fix this would be to check the files magic number if the content type header is null

Awesome, thanks for the quick reply


Add stdlib compat <0.0.1

This enables Pkg operations inside the test suite for DI, as explained here: https://discourse.julialang.org/t/why-random-jl-is-fixed-to-version-0-0-0/105957/2
Fix #96

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 75.11%. Comparing base (f1bf915) to head (b564a1e).

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #97      +/-   ##
==========================================
- Coverage   79.62%   75.11%   -4.52%
==========================================
  Files          17       17
  Lines         702      651      -51
==========================================
- Hits          559      489      -70
- Misses        143      162      +19

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Interesting, thanks!


Add builtin validation for SPV_NV_shader_sm_builtins

Also add a Builtin test generator variant that takes
capabilities and extensions.
Tests

verify that the SMCountNV, SMIDNV, WarpsPerSMNV, and WarpIDNV Builtins are
accepted as Inputs in Vertex, Fragment, TessControl, TessEval, Geometry,
and Compute.
verify that the SMCountNV, SMIDNV, WarpsPerSMNV, and WarpIDNV Builtins are
accepted as Inputs in MeshNV and TaskNV shaders.
verify that the SMCountNV, SMIDNV, WarpsPerSMNV, and WarpIDNV Builtins are
accepted as Inputs in the 6 ray tracing stages
verify that the SMCountNV, SMIDNV, WarpsPerSMNV, and WarpIDNV Builtins are
NOT accepted as Outputs.
verify that the SMCountNV, SMIDNV, WarpsPerSMNV, and WarpIDNV Builtins are
NOT accepted as non-scalar integers (f32, uvec3)
verify that the SMCountNV, SMIDNV, WarpsPerSMNV, and WarpIDNV Builtins are
NOT accepted as non-32-bit integers (u64)

@alan-baker @s-perron @dneto0 - it seems the appveyor build timed out with the new tests that I added.
[00:42:12] 15/18 Test #15: spirv-tools-test_val_abcde ............***Timeout 300.02 sec
...
[00:44:48] Total Test time (real) = 707.34 sec
[00:44:48] The following tests FAILED:
[00:44:48] 	 15 - spirv-tools-test_val_abcde (Timeout)
Can we get the timeout increased?
It seemed to trigger at 300 seconds, and it was about 12 tests from the end, according to the log.
I added 456 new tests (the power of templatized tests!) to the existing 17131 tests.  On my local machine they add about 1 - 1.5 seconds of execution time to the val_abcde tests, and that subtest runs in about 18 seconds for me. The whole suite runs in 47 seconds for me. (this is on a 6 year old laptop!)
It's pretty crazy that on the CI machine it takes over 300s for the val_abcde test and 700s for the full suite.
I also have more builtin tests that I'm planning to add (for ray tracing), so we're definitely going to need a higher timeout.

You can change the timeout in the .appveyor.yml file in the root of the repo. I would prefer incrementing as needed and as minimally as needed. If you include that change in this PR we can make sure the timeout is long enough.

Previously we split the suite. Can we change abcde to an abc and de suite?
Dan
On Wed., Jun. 5, 2019, 13:46 alan-baker<EMAIL_ADDRESS>wrote:

You can change the timeout in the .appveyor.yml file in the root of the
repo. I would prefer incrementing as needed and as minimally as needed. If
you include that change in this PR we can make sure the timeout is long
enough.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/KhronosGroup/SPIRV-Tools/pull/2656?email_source=notifications&email_token=AAACLC3F6IXP2AXFZYQ65MTPY73X3A5CNFSM4HTZXV5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXAPTOI#issuecomment-499186105,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAACLCYHHLVAOGZ75MON64DPY73X3ANCNFSM4HTZXV5A
.

Pushed a change to bump the timeout to 310 seconds.
@dj2 I'd prefer to leave splitting the test suite up to someone more familiar with the project.

Can I get this reviewed/merged? Thanks!

Thanks!


wasmparser static TypeId assert can trigger with -Zrandomize-layout

The following wasmparser code can fail if compiling with nightly and -Zrandomize-layout due to a static assert triggering on the size of TypeId when the field order gets reshuffled.
/// Represents a unique identifier for a type known to a [`crate::Validator`].
#[derive(Debug, Copy, Clone, PartialEq, Eq, Hash)]
pub struct TypeId {
    /// The index into the global list of types.
    pub(crate) index: usize,
    /// The effective type size for the type.
    ///
    /// This is stored as part of the ID to avoid having to recurse through
    /// the global type list when calculating type sizes.
    pub(crate) type_size: u32,
    /// A unique integer assigned to this type.
    ///
    /// The purpose of this field is to ensure that two different `TypeId`
    /// representations can be handed out for two different aliased types within
    /// a component that actually point to the same underlying type (as pointed
    /// to by the `index` field).
    unique_id: u32,
}

// The size of `TypeId` was seen to have a large-ish impact in #844, so this
// assert ensures that it stays relatively small.
const _: () = {
    assert!(std::mem::size_of::<TypeId>() <= 16);
};

should we increase the limit her, remove the assert, or use repr(C) on TypeId to enforce the field order of this type?
We ran into this when building our application with nightly and -Zrandomize-layout which builds all dependent crates including wasmtime and wasmparser with it as well and this failed to build. Another option could be to move the assert to a unit test so it only gets triggered in the development of wasmparser and not in usages of the crate?

Oh dear sorry for the breakage! I think it's probably best to use #[repr(C)] here which I think should fix the issue for you. If you'd like to send a PR that'd be appreciated!


Cydia is not 64bit

hi cydia was not 64bit version at my iphone 6s plus... it was 32 bit.
and after installing 2-3 tweaks.. when it respring: cydia, settings, phone, sms, and so much more apps and home dock was deleted (not icons vanished it was like completely deleted)
for example phone app was gone and when someone called me there was nothing on phone...
and when will stable build will come out?

I do not mot think this has anything to do with yalu but with cydia. Saurik is working on updating cydia. Ur better off asking this question in r/jailbreak #162
On 31 jan. 2017 15:29 +0100, LastPust<EMAIL_ADDRESS>wrote:

hi cydia was not 64bit version at my iphone 6s plus... it was 32 bit.
and after installing 2-3 tweaks.. when it respring: cydia, settings, phone, sms, and so much more apps and home dock was deleted (not icons vanished it was like completely deleted)
for example phone app was gone and when someone called me there was nothing on phone...
and when will stable build will come out?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub (https://github.com/kpwn/yalu102/issues/336), or mute the thread (https://github.com/notifications/unsubscribe-auth/ARGTBtWxeiK7fVSYyn1PK0hC0r1iPftoks5rX0U6gaJpZM4LytEq).

but cydia is updated daily  http://apt.saurik.com/beta/cydia-arm64/
yalu app is the one installs cydia for the first time? so yalu app is need to be updated right? idk

https://github.com/kpwn/yalu102/issues/64

U update cydia from within cydia.
On 31 jan. 2017 15:35 +0100, LastPust<EMAIL_ADDRESS>wrote:

but cydia is updated daily http://apt.saurik.com/beta/cydia-arm64/
yalu app is the one installs cydia for the first time? so yalu app is need to be updated right? idk
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub (https://github.com/kpwn/yalu102/issues/336#issuecomment-276379204), or mute the thread (https://github.com/notifications/unsubscribe-auth/ARGTBgXwBxZdQkmmhI73DSCSLUZcIADNks5rX0a6gaJpZM4LytEq).

@LastPust: Cydia 64-bit is still in beta. When 64 bit is stable and ready it will be release for cydia. And the correct debian packages can be added to yalu. until then 32-bit is the default stable.

Can u close this issue please @LastPust


Adds new script sample 'lists-teams-decluttering'

@tmaestrini thanks for opening the PR. We will review it ASAP.
Is this PR connected to some issue?

@milanholemans does my changes fit? Or do you want me to fix anything else?

Looks good at first sight @tmaestrini 👍

Do you want me to do sth else, @Adam-it ?

Do you want me to do sth else, @Adam-it ?

Hi, rather not 😉.
Sorry for the hold up. Please be a bit more patient before we process your PR 🙏👍

@Adam-it Thanks for the feedback! 🙏
I've fixed all the details according to your orders – please see current version…

@Adam-it Thanks for the feedback! 🙏
I've fixed all the details according to your orders – please see current version…
The sample script in https://pnp.github.io/cli-microsoft365/contribute/script-sample/new-script-sample should be updated to fit the specification.

Thanks for the quick turn around. I will give it a check ASAP.
What do you see lacking in the script sample? Maybe we could add this to this PR along the way 🙂

Dear @Adam-it, thank you – really appreciated!
The lacking in the template script is a minor thing; it concerns the indentation starting from line 104 to 106 and 110 to 112.

Dear @Adam-it, thank you – really appreciated!
The lacking in the template script is a minor thing; it concerns the indentation starting from line 104 to 106 and 110 to 112.

I see.
I say if you still have time we could add this small change to this PR as well 👍

@tmaestrini if I understood you correctly you are ready for another round right? I marked this PR as 'ready to review' and planning to do so in the upcoming weekend 👍

Dear @Adam-it, thank you – really appreciated!
The lacking in the template script is a minor thing; it concerns the indentation starting from line 104 to 106 and 110 to 112.

I see. I say if you still have time we could add this small change to this PR as well 👍. If not I will do it when merging

Hey @Adam-it! No need anymord, @milanholemans fixed it in his commit: https://github.com/pnp/cli-microsoft365/commit/d781816e65aada455b901d16e32692034e564559

Hey @Adam-it! No need anymore, @milanholemans fixed it in his commit: d781816

Looks like someone was monitoring our conversation 😅. Cool, we have it sorted out. I will try to process this PR during the weekend 👍

I was aware of this issue since I my last PR to update the syntax was merged. However I wasn't able to update it until a few days ago ☺

Ready to merge 🚀

Thank you, @Adam-it! 🙌 the merge will be done by your team, right? So my work is done "for now"?

Thank you, @Adam-it! 🙌 the merge will be done by your team, right? So my work is done "for now"?

yep. I am doing it now together with other PRs. Should be live in 10-20 min

merged manually. Thank you for your awesome work👏
You Rock 🤩


Add german translation and set default language to english

Also fixes #24

@cornips can you give me some feedback on this pr?

@ricardoboss It is a good PR! Thank you so much for your translation. I merged it in the develop branch, to be published in the upcoming release.

Translations are now maintained through Transifex: https://www.transifex.com/cornips/flobro/


Replace Glide with Coil #29

I have replaced Glide with Coil library for image loading.
This is my first PR. Let me know if you have any feedback! :)

Thank you for the contribution. I really appreciate it. I'll try to review sometime today.

Sure! Let me know if you have any suggestions or if something needs to be changed.


Missing 1.1.15 release.

Because of an issue with Maven Central, 1.1.15 was pushed without the release being tagged.  We have a problem here because if we tag the 1.1.15 commit on here, it won't have an associated build.gradle commit updating the version number.  Therefore, we need to retract the release from Maven Central, if possible, for consistency.

I am not sure if it's possible to "retract" an artifact on maven central, as a rule. I can try to contact the sonotype folks to override it. Do you want me to do so?

No, that's fine.  We'll just ignore this.


Introduce stop_strings and stop_token_ids sampling params

Summary of changes:

added new parameters to GenerationConfig: stop_strings, include_stop_str_in_output and stop_token_ids
by default include_stop_str_in_output is false, stop_strings and stop_token_ids are empty
on add_request pipeline adds eos_token_id to stop_token_ids and stop_token_ids is considered in processing ignore_eos and EOS penalty
implemented support for these parameters for ContinuousBatchingPipeline - when one of stop_strings / stop_token_ids gets generated, generation is finished
included gtest tests for stop_token_ids and python tests for stop_strings for greedy (HF also has this parameter, so we can compare with HF output). Included also python tests for beam search, but they are skipped since HF does not seem to handle it as expected and outputs are different.

Port to master is included in #854

Closing in favor of #854


feat: add prefer-repository-shorthand rule

PR Checklist

[x] Addresses an existing open issue: fixes #71
[x] That issue was marked as status: accepting prs
[x] Steps in CONTRIBUTING.md were taken

Overview
Added new rule for shortened GitHub repo urls declaration.

👋 @azat-io just checking in, did you mean to re-request my review on this?

@JoshuaKGoldberg Hi, I've been a little busy lately. I'll be able to come back tomorrow and finalize the remaining comments on the pull request.

Done ✅

Awesome, will re-review!
A couple notes:

I'd prefer if you didn't force push. It makes it a little more cumbersome to check out the branch and see a history of changes locally.
If you ever need me to re-review, it's fastest to use the re-request review button (step 5 in https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review). I missed this till now 😓

@all-contributors please add @azat-io for code.

🤖 Beep boop! This comment was added automatically by all-contributors-auto-action.
Not all contributions can be detected from Git & GitHub alone. Please comment any missing contribution types this bot missed.
...and of course, thank you for contributing! 💙


graft_neuron functionality

Returns a neuron with a single neurite starting at the given section.
Note that this is not a deep copy: the data points in the grafted neurite
are the same as in the original neuron
This PR will allow Lida (and others!) to use already existing neuromorpho features but on specific neuron parts (such as starting from the apical point for example)

Codecov Report

Merging #650 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master   #650   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          41     41
  Lines        2041   2048    +7
=====================================
+ Hits         2041   2048    +7


ADC4 Temperature

I am trying to get temperature based on this article https://www.electroniclinic.com/read-raspberry-pi-pico-onboard-temperature-sensor/
In short:
Now, you might be thinking to which pin this onboard temperature sensor is connected? This onboard temperature sensor is connected to one of the ADCs or Analog-to-Digital Converters. The temperature sensor does not have a physical pin in the board but is accessed as ADC4. This onboard temperature sensor works by delivering a voltage to the ADC4 pin that is proportional to the temperature.
I am not sure how to access this based on available documentation. Any help is appreciated.

@susnick Hi, Kaluma does not support onboard temperature sensor now. I'll implement this feature in the next release. I think I can release test version soon.

@susnick Could you please try it with the attached test FW?
Here's the example code.
If you confirm it works well and close this issue, I'll merge this change into the main branch.
kaluma-rp2-pico-1.1.0-beta.1_temp_adc_test_0218.uf2.zip
const { ADC } = require('adc');
const rp2 = require('rp2');

var a = new ADC(rp2.TEMPERATURE_ADC);
var value = a.read(); // Read the ADC value at the RP2 intenal temperature ADC.
var adc_voltage = value * 3.3;
var temperature = 27-(adc_voltage-0.706)/0.001721;
console.log(temperature);

Looks good thanks.

@susnick Thank you. I'll merge it to master branch and release it next release.


Backspace fails when using Open3

Shout out to Deivid: Long time, no talk :).  Here is an interesting bug...
require 'open3'

include Open3

Open3.popen2e('echo Hello') do |input, stdOutErr, waitThread|
   byebug
end

Try entering a series of characters, and then pressing backspace.  You are unable to press backspace on the command prompt and have it register on the interface (buffer flushing problem?).  Pressing enter does register the inputs.
For example, I type in byebug at the breakpoint "stdErrf", then I try to erase the 'f' with backspace, the interface does not update.  However, if I press enter, the value of stdErr is returned as the underlying workings registered the keyboard input, just not the interface.
Additional Info:
Ruby Version: ruby 2.0.0p247 (2013-06-27) [i386-mingw32]
OS: Windows 7, Intel Processor
Byebug Version: 2.7.0

This could be fixed by bb98cd6.

Could somebody experiencing this try latest master? :)

@deivid-rodriguez wish I could, but I have moved onto another project that does not have an ENV enabled for this :(

Thanks anyways @kevjames3

Sorry for the long wait. I still have problems on byebug (9.0.5), will try to use your master branch for a while to see if this happens again.

@Startouf Note that you have to manually reapply https://github.com/deivid-rodriguez/byebug/commit/bb98cd60cfeceee8ce626a222346ef432e7d2a0e, which is not currently in master.


[stable/jenkins] Provide default job value

What this PR does / why we need it:
This fixes the helm template warning when providing a job map.
warning: destination for jobs is a table. Ignoring non-table value <nil>

Special notes for your reviewer:
This should probably applied to all other values as well, because you'd get similar warnings when setting a value to a nil value.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/assign @torstenwalter

/ok-to-test

/lgtm

@hpurmann Thank you for your contribution.


[FEATURE] linux installer uninstaller option

Feature Description
It would be great to have a way to uninstall properly.
Similar Features or References
For now I'm doing nexa remove on models downloaded.
Cleaning up /etc/environment then systemctl disable nexa.service
and finally manually deleting :
/usr/local/bin/nexa /opt/nexa-linux-cuda/ /etc/systemd/system/nexa.service
but maybe I forgot something or maybe there is a better way.

Do you mean uninstall the installed linux executable?
Unlike on MacOS or on Windows, to uninstall nexa-sdk executable on linux, you need to run the following commands:

sudo rm -rf /opt/nexa-linux-cuda (or sudo rm -rf /opt/nexa-linux-cpu if you are not using cuda)
sudo rm -rf /usr/local/bin/nexa and sudo rm -rf /usr/local/bin/nexa-exe


Allow timestamp without trailing Z

Fixes Github Issue #270
Signed-off-by: Sam Curren<EMAIL_ADDRESS>

Codecov Report

Merging #275 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           master    #275   +/-   ##
======================================
  Coverage    78.9%   78.9%
======================================
  Files         230     230
  Lines       10487   10487
======================================
  Hits         8275    8275
  Misses       2212    2212

Thanks!


Item Model Fix

Mod name
Item Model Fix
Curseforge link
https://www.curseforge.com/minecraft/mc-mods/item-model-fix
Modrinth link
N/A
Other link
https://github.com/PepperCode1/Item-Model-Fix
What it does
Fixes the gaps in generated item models.
Why should it be in the modpack
It fixes those annoying transparent lines in handheld items, see the CurseForge page.
Why shouldn't it be in the modpack
N/A
Categories

[ ] Performance optimization
[x] Graphics optimization
[ ] New feature
[ ] Optifine parity
[x] Fixes a bug/dependency
[ ] Replaces an existing mod

Think I thought of this at some point but please Mojang, fix it upstream 😄

Added


to fixed number line

can i set parameter to let budoux output fixed line

Hi! Could you clarify what the fixed line means with some examples? What's the ideal output expected?

never mind ,I  managed to that.for example as following.
default as this
echo $'本日は晴天です。\n明日は曇りでしょう。' | budoux
本日は
晴天です。
---
明日は
曇りでしょう。

what I  want is fixed line let say 2 because I want to limit words/characters in each line ,then I  cal and join the first and last 3 line into new line
@tushuhei

Hmm, sorry I think I need some more clarification.
What is the ideal output for the command echo $'本日は晴天です。\n明日は曇りでしょう。' | budoux with the parameter you want to have?

since i really dont know japanese ,perhaps this text example isnt that proper, my case is i want to cut long paragpraph into small ones without cutting from middle of sentence, i found your lib is kinda of can do this job.
my idea came into first get raw output of budouX,then line by line count the total words ,

Yes, BudouX can be used to separate a long paragraph into a series of phrases.
If you're interested in counting the phrases (or words) in total, I believe you can get the desired results using sed and wc like this:
echo $'本日は晴天です。\n明日は曇りでしょう。' | budoux -d='' | sed  '/^$/d' | wc -l

Closing this bug for now, but fee free to reopen if anything.

I'm looking for the same . : takes a string as input and breaks it into lines based on the maximum number of characters per line specified by the user, ensuring that no word is split in the middle. Words longer than the specified maximum characters should be placed on their own line.


Support for network policy calico

Is there an existing issue for this?

[X] I have searched the existing issues

Description
We would like to implement network policy as calico in our AKS deployment via terraform.
New or Affected Resource(s)/Data Source(s)
azurerm_aks
Potential Terraform Configuration
No response
References
No response

Hello @sandesh1994199
as far as I understand you can already do this with the variable network_policy.
https://github.com/Azure/terraform-azurerm-aks/blob/f3b0be8421a36040b98371896ccf3df807756070/variables.tf#L624-L628
https://github.com/Azure/terraform-azurerm-aks/blob/f3b0be8421a36040b98371896ccf3df807756070/main.tf#L272
Could you please clarify if there is anything else that is not supported ?
Thanks

Hi @sandesh1994199, can @zioproto's answer solve your issue? If you have any further question, please let us know, thanks!

I'm closing this issue as no user response received. Please feel free to reopen it if you still have questions on this issue @sandesh1994199 .


[CERT-TEST-FAILURE] [TC-MEDIAPLAYBACK-6.8] - Test-failed

Feature Area
Other
Test Case
TC-MEDIAPLAYBACK-6.8
Reproduction steps
Step 1 : executed the below mentioned command to put DUT into a commissionable state
./chip-tv-app
Step 2 : Once DUT reach the commissionable state sent below mentioned command on TH.
./chip-tool pairing onnetwork 1 20202021
Step 3 : TH reads the ActiveTextTrack attribute attribute from the DUT by sending mentioned command
./chip-tool mediaplayback read active-text-track 1 3
Expected value :

[1705561901.609219][4148:4150] CHIP:TOO: Endpoint: 3 Cluster: 0x0000_0506 Attribute 0x0000_0009 DataVersion:<PHONE_NUMBER>
[1705561901.609389][4148:4150] CHIP:TOO:   ActiveTextTrack: {
[1705561901.609426][4148:4150] CHIP:TOO:     Id:
[1705561901.609459][4148:4150] CHIP:TOO:     TrackAttributes: null
[1705561901.609490][4148:4150] CHIP:TOO:    }

Actual value :

[1705561628.435827][4129:4131] CHIP:DMG: 	InteractionModelRevision = 11
[1705561628.435882][4129:4131] CHIP:DMG: }
[1705561628.436296][4129:4131] CHIP:TOO: Endpoint: 3 Cluster: 0x0000_0506 Attribute 0x0000_0009 DataVersion:<PHONE_NUMBER>
[1705561628.436859][4129:4131] CHIP:TOO:   ActiveTextTrack: {
[1705561628.436923][4129:4131] CHIP:TOO:     Id: activeTextTrackId_0
[1705561628.436979][4129:4131] CHIP:TOO:     TrackAttributes: {
[1705561628.437032][4129:4131] CHIP:TOO:       LanguageCode: languageCode1
[1705561628.437131][4129:4131] CHIP:TOO:       DisplayName: displayName1
[1705561628.437187][4129:4131] CHIP:TOO:      }
[1705561628.437237][4129:4131] CHIP:TOO:    }
[1705561628.437705][4129:4131] CHIP:EM: <<< [E:54602i S:60341 M:230830833 (Ack:35510143)] (S) Msg TX to

Bug prevalence
whenever I do
GitHub hash of the SDK that was being used
b044b5e486a625fb68dd684317221c65b3fa61c7
Platform
raspi
Anything else?
As per the test plan, step 1 expects that when TH reads the ActiveTextTrack attribute, the DUT should respond with a null value. However, in the current SDK, we are receiving a list.
Additionally, after successfully sending the DeactivateTextTrack command, when TH attempts to activate by sending the ActiveTextTrack command, it doesn't actually activate, although a success response is received
PFA log below:
TC-MEDIAPLAYBACK-6.8.txt
Test-Plan Reference :
https://github.com/CHIP-Specifications/chip-test-plans/blob/master/src/cluster/media.adoc#tc-mediaplayback-6-8-text-track-verification

should be fixed now

resolved in latest TOT.


Cordova arch error

If build cordova targets get error:
Uncaught TypeError: Class constructor SvelteComponentDev cannot be invoked without 'new'
https://github.com/meteor/meteor/blob/c7534dbcddd3c677efb6297e67132b05bd63dc87/packages/babel-compiler/babel-compiler.js#L90
This line makes modernBrowsers only for web.browser arch, but svelte need it if we compile web.cordova

There is a work around how to make babel proprly transpile svelte's internals: https://forums.meteor.com/t/transpile-certain-node-modules-with-babel-at-meteor-build/48546
You just need to link the svelte package from node-modules inside any of meteor-watchable directories, e.g. /imports

I don't have a cordova project to test with, but if anyone wants to, feel free to submit a PR documenting how to fix this.

I am not sure that it is really a melte problem as it seems to be related to the way meteor-babel handles node_modules imports... However, it is possible to reproduce it without cordova, using some legacy browser (ie 11 would do). I'll try to have a look at it - perhaps will find something

Thanks @r00t3g. I tried the legacy client, and melte itself also caused syntax errors. I published<EMAIL_ADDRESS>to fix that, and also document how to have Meteor recompile svelte.


Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

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

4 packages failed to build:

cargo-depgraph
cargo-modules
cargo-mutants
insulator2

18 packages built:

cargo-component
cargo-deny
cargo-dist
cargo-hack
cargo-llvm-cov
cargo-semver-checks
cargo-tally
cargo-tauri
cargo-udeps
cargo-workspaces
cargo-zigbuild
cinny-desktop
kiwitalk
modrinth-app
modrinth-app-unwrapped
pot
surrealist
treedome

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

1 package failed to build:

insulator2

18 packages built:

cargo-component
cargo-deny
cargo-dist
cargo-hack
cargo-llvm-cov
cargo-semver-checks
cargo-tally
cargo-tauri
cargo-udeps
cargo-workspaces
cargo-zigbuild
cinny-desktop
kiwitalk
modrinth-app
modrinth-app-unwrapped
pot
surrealist
treedome

Removed the broken updates.
Ready for merging from my side.


AL2022 became AL2023 for GA

A simple rename.
Fixes: https://github.com/toolbx-images/images/issues/93
Fixes: https://github.com/amazonlinux/amazon-linux-2023/issues/420
I've only tested this a little bit by building the container.

Thanks, you'll have to update https://github.com/toolbx-images/images/blob/main/.github/workflows/amazonlinux.yaml & https://github.com/toolbx-images/images/blob/main/.github/workflows/amazonlinux-pr.yaml as well.

Ahh yep, thanks for that pointer. Teaches me for not grepping :)
Let's see if that fixes the checks

Thanks!


Export number_of_native_contexts() and number_of_detached_contexts()

Hello @dainis,
in pr #38  I've implemented export number_of_native_contexts() and number_of_detached_contexts(), which are also part of HeapStatistics class since Node10.
Can you please merge it ?

thx


Fixed missing ./ in local require path

This should fix the Error: Cannot find module 'src/index.js' errors, which was probably introduced via the changes in this commit: https://github.com/ericelliott/autodux/commit/08851126f700cfa49c71a64dd6c3261d4e92186a

Published<EMAIL_ADDRESS>

Sweet, thanks!


Proposal: Standard Library

I think it would be a good time to begin to work on an official standard library for alloy, and include it in this repo (under lib/ folder?).
At first, I think most of it should simply be wrappers around the C stdlib. Everything that deals with files and system access needs to be C stdlib wrappers until some kind of conditional compilation depending on operating systems and architectures is implemented. For other stuff (eg. maths/string functions), it can be completely implemented in alloy already.
I'm interested in working on this.

(oh, and I have no idea how issue labels work, maybe I don't have permission to add them)

Yeah you just don't have the permissions :(
As for a standard library, I think it would be a nice idea to do it some point soon -- but I don't think it will be possible just yet, still a few things we need to implement.
A lot of the stuff we can just write bindings for C stuff, as for math, we may have to use C's math library for some of the more complicated stuff so it's more accurate, portable, ...? As for strings, yeah sounds good, we'll probably do Pascal style, which means we may have to do a c++ style c_str() function for backwards compatibility with C.
If you want to start working on this now while I do the other stuff for the compiler that'd be cool :)

Yeah, I think it makes sense to make the Alloy string library nicer than the painful C one.
I think I'll just see what I can do with stdio at the moment.

Oh also, file inclusion needs some thought. For instance, we have our lib folder -- but when we include a file it needs to be compiled with it because it generates the header files when its compiled, but they are deleted afterwards?
For instance, if we had a library, i.e "string.aly", you would have to compile that with your other files, and also specify an absolute path to the lib folder, so we need to do it C-style where it checks the lib folder either when you specify a different operator, i.e. C uses the greater than and less than for library stuff. Or, we do it another way... which I'm not too sure about?

I made a proposal not long ago about modules, that might be of help.
There could be a compiler option that specifies directory(s) to look for to find the files in !use tags. The compiler could also search the directory the main file is in.

Another thing that needs to be considered:
For malloc(), should a void type be implemented or generics?

This is something that I've considered, whether we support generics or if we just go for a void type. I'm not too sure, it deserves its own issue.

Ok, right now I'm just using void because the compiler lets any type through.

Yeah, sounds good.

Approved


CSA Deployment Pop Quiz

Working API's coming from a deployed server.   Individuals will be required to know the following...

Show JWT signup and/or login process
Explain a POJO and changes to a POJO
Explain security configuration rules that are required for access
Describe docker and process for update docker application
Describe route 53 and process for domain setup
Show API access code and error handling, specifically redirect on 403
Describe managing CORS policies through Nginx and Java
Describe reverse proxy of server_name to proxy_pass

https://github.com/rohinsood/csa/issues/3

Raymond's Scores

Akshat Popquiz answers

Varaprasad Pop Quiz Answers

Ishi Pop Quiz Answers

who up poppin they quiz

Rachit's Pop Quiz Answers

Soham's Pop Quiz Answers

Aditya Nawandhar
Final Score - 3.7/4

Parav's Quiz

Tanisha Quiz

Shreyas

https://github.com/EdwinKuttappi/CSABlog/issues/9

Orlando Carcamo
Period 3
3.59/4
Issue

Kaiden Do
Period 1
Score: 3.6/4.0
Link to Issue: https://github.com/kaiden-dough/kaidencsablog/issues/4

Toby Leeder
Period 3
Score: 3.6/4.0
Issue

David Vasilev
Period 1
Score: 3.7/4
Link to Issue: https://github.com/DavidVasilev1/CSAsite/issues/7#issue-2108310495

Tay's Answers and Scores

Shaurya Goel
Period 3
Score: 3.55/4.0
Issue

Isabelle Gunawan
Period 1
Score: 3.5/4
Issue

Emaad Mir
Period 1
Score: 3.6/4
Emaad Mir’s Deployment Pop Quiz

Aaron Rubin
Period 3
Score: 3.15/4
Issue

Vivian Ni
Period 1
Score: 3.65/4
Issue

Derrick Huang
Period 1
Score 3.6/4
Derrick Huang's Deployment Pop Quiz Issue

Grace Wang
Period 1
Score 3.6/4
Issue

Drew Reed
Period 1
Score 3.65/4.0
Link to issue

Kevin Du
Period 1
Score: 3.05/4
Link To Issue

Vardaan Sinha
Period 1
Score: 3.60/4
Link to Issue

Ethan Tran
Period 1
Score: 3.5/4
Issue Link

Ethan Tran
Period 1
Score: 3.5/4
Issue Link

Alexander Lu
Period 1
Score: 3.6/4
Issue Link

Ethan Tran
Period 1
Score: 3.5/4
Issue Link

Tirth Thakkar
Period 1
Score: 3.6/4.0
Issue

Mirza Beg
Period 1
Score: 3.65/4
Issue Link

Emma Shen
Period 1
Score: 3.6/4
Issue Link

Aliya Tang
Period 3
Score: 3.6/4
Issue Link

Theo Huntalas
Period 1
Score: 3.65/4
Issue

Vinay Rajagopalan
Period 3
Score: 2.1375/4
Issue

Ethan Zhao
Period 1
Score: 3.55/4.0
https://github.com/dolphinalt/APCSA-Pages/issues/10

Finn Carpenter
P1
3.65/4
https://github.com/F1nnC/stud/issues/6

Aniket Chakradeo
Period 3
3.6/4
Link to Issue

Yuri Subramaniam
Period 3
scores

Raunak Mondal
Period 1
Score: 3.6/4
Issue

Nikhil Chakravarthula
Period 1
3.6/4
Link to Issue

Sreeja Gangapuram
Period: 1
Score: 3.6/4
Issue

Vishnu Aravind
Period 1
3.6/4
Issue

James Lee
P3
3.25/4
issue

Shivansh Goel
Period 3
3.4/.4
Issue

Ekamjot Kaire
Period 1
Score: 3.55/4.0
issue

Anthony Bazhenov
Period 1
Score: 3.4/4
Issue

Ryan McWeeny
Period 1
total score: 3.35/4

AJ Ruiz
Period 1
3.6/4
The Issue

Krishiv Mahendru
Period 3
3.64/4
Link To Issue

Luna Iwazaki
Period 3
Issue

Quinn Bireley
Period 3
Issue

Haoxuan Tong
Period 3
Score: needs to review
issue

Tanay Patel
Per 3
3.05/4
Issue


Fix some links that were broken when repo was moved to another org

Fixes #86

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@58a83c0). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #87   +/-   ##
=========================================
  Coverage          ?   81.49%
=========================================
  Files             ?       11
  Lines             ?      881
  Branches          ?       22
=========================================
  Hits              ?      718
  Misses            ?      141
  Partials          ?       22

Continue to review full report at Codecov.

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

👍

👍


Is training code available?

As far as I know, prompt-to-prompt uses plain pretrained SD models, so no training needed. Hope this helps!


Refactor seedu address → taskbook

Codecov Report

Merging #106 (5b9efb1) into master (9dddd1a) will increase coverage by 0.02%.
The diff coverage is 78.94%.

@@             Coverage Diff              @@
##             master     #106      +/-   ##
============================================
+ Coverage     66.03%   66.06%   +0.02%
  Complexity      422      422
============================================
  Files            86       86
  Lines          1428     1429       +1
  Branches        158      158
============================================
+ Hits            943      944       +1
  Misses          443      443
  Partials         42       42

Impacted Files
Coverage Δ

src/main/java/taskbook/AppParameters.java
75.00% <ø> (ø)

src/main/java/taskbook/Main.java
0.00% <ø> (ø)

src/main/java/taskbook/MainApp.java
0.00% <ø> (ø)

src/main/java/taskbook/commons/core/Config.java
68.18% <ø> (ø)

...c/main/java/taskbook/commons/core/GuiSettings.java
69.23% <ø> (ø)

...rc/main/java/taskbook/commons/core/LogsCenter.java
78.37% <ø> (ø)

src/main/java/taskbook/commons/core/Messages.java
0.00% <ø> (ø)

src/main/java/taskbook/commons/core/Version.java
82.50% <ø> (ø)

...c/main/java/taskbook/commons/core/index/Index.java
100.00% <ø> (ø)

...ok/commons/exceptions/DataConversionException.java
100.00% <ø> (ø)

... and 76 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Fix of errors reported by the sample aggregator. Invalid sample.json

Existing Sample Changes
Description
After adding some samples, the sample aggregator started reporting errors in the validation of sample.json files. In three samples, due to a missing comma, json files turned out to be invali
Fixes Issue#
https://jira.devtools.intel.com/browse/ONSAM-1601
https://jira.devtools.intel.com/browse/ONSAM-1600
https://jira.devtools.intel.com/browse/ONSAM-1599
External Dependencies
List any external dependencies created as a result of this change.
Type of change
Please delete options that are not relevant. Add a 'X' to the one that is applicable.

[X] Implement fixes for ONSAM Jiras

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[X] oneapi-cli

@ShwethaSelma @ManjulaChalla @jimmytwei
Hello. Can you please review it?


Remove obsolete su parameter in documentation

The su parameter was removed from the classes and templates in favor of su_owner and su_group.

Thanks for the PR @stefanandres!


DatePicker: fix time-spinner click bug

Test environment
Google Chrome: <= 50.0.2661.102
It's hard to select time-spinner__item by click，usually have to click several times。
Please make sure these boxes are checked before submitting your PR, thank you!

[ ] Make sure you follow Element's contributing guide (中文 | English | Español).
[ ] Make sure you are merging your commits to dev branch.
[ ] Add some descriptions and refer relative issues for you PR.

We may not fix bugs if they only exist in older browsers. Plus, we should use $nextTick only when we have to.


Feature: add support for Cilium

Good idea behind your tool. Consider looking at Cilium as well as Cilium Network Policies are becoming very commonly used.
https://docs.cilium.io/en/stable/security/policy/

Example endpointSelector netpol for Cilium:
apiVersion: "cilium.io/v2"
kind: CiliumNetworkPolicy
metadata:
  name: "l3-rule"
spec:
  endpointSelector:
    matchLabels:
      role: backend
  ingress:
  - fromEndpoints:
    - matchLabels:
        role: frontend

Example cluster wide policy that wont have any connection to namespaces.
apiVersion: "cilium.io/v2"
kind: CiliumClusterwideNetworkPolicy
metadata:
  name: "clusterwide-policy-example"
spec:
  description: "Policy for selective ingress allow to a pod from only a pod with given label"
  endpointSelector:
    matchLabels:
      name: leia
  ingress:
  - fromEndpoints:
    - matchLabels:
        name: luke

As far as I am concerned, these are the two scenarios we need to support. A node selector policy will also use the endpointSelector and can only be used with clusterwide policies.

Hello @nvibert,
I have started implementing support for Cilium. I think I have covered the most basic usage of Cilium for both namespaced and cluster wide policies, however, it would be nice if somoene with more experience with Cilium could assist.
Are you able to test the Cilium scans if I merge it in a couple of days ~?

Yeah, happy to test it @deggja !

Thank you @nvibert
#95 has been merged for the first iteration of cilium support and is included in the latest release (3.0.6).
You can try the scan using the CLI (not implemented for dashboard/UI yet). Homebrew is updated, so you can download it using brew or just a binary directly from releases.
The main command for cilium is netfetch scan --cilium
This command initiates a scan for the kind: CiliumClusterwideNetworkPolicy and matches the endpointSelector in those policies towards namespaces and pods in the cluster. It also checks for a default-deny-all policy for the entire cluster. It will report its findings in the CLI.
If no cluster wide default-deny-all is in place, a namespace scoped scan will initiate when the cluster wide scan has finished. This will look for kind: CiliumNetworkPolicy in the different namespaces.
I have tested this with some CNPs and CCNPs and it seems to be able to locate all these different policies and match them to the pods they target.
Can you test and see if you are able to do the same? If there are policies that the scan do not pick up, it would be nice to know how these look in YAML. I'm sure there are policies/scenarios and corner cases it is not covering as of now.
Also, I have not implemented any support to look for policies that handle traffic between different k8s clusters. That is out of scope for now.
Looking forward to hear how it goes 🚀

Hello Daniel. First, as mentioned above, I really like the idea behind the tool!
Netfetch did not seem to notice the policies I deployed. I followed the Star Wars demo and netfetch didn't realize it had deployed some network policies to protect my Deathstar deployment.
nicovibert:~$ netfetch scan default --cilium
Running Cilium network policies scan for namespaces: default
Mode: CLI
Using default kubeconfig path: /Users/nicovibert/.kube/config
Policy type: Cilium

Unprotected pods found in namespace default:
default deathstar-7848d6c4d5-286mj <IP_ADDRESS>
default deathstar-7848d6c4d5-r25k5 <IP_ADDRESS>
default tiefighter <IP_ADDRESS>
default xwing <IP_ADDRESS>

Even though I have deployed the Cilium Network Policies. Maybe the tool should leverage the cilium endpoint list output instead to verify if enforcement has been configured.
nicovibert:~$ kubectl -n kube-system exec -it cilium-h9zm7 cilium endpoint list
kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl exec [POD] -- [COMMAND] instead.
Defaulted container "cilium-agent" out of: cilium-agent, config (init), mount-cgroup (init), apply-sysctl-overwrites (init), mount-bpf-fs (init), clean-cilium-state (init), install-cni-binaries (init)
ENDPOINT   POLICY (ingress)   POLICY (egress)   IDENTITY   LABELS (source:key[=value])                                              IPv6   IPv4           STATUS
           ENFORCEMENT        ENFORCEMENT
302        Disabled           Disabled          4          reserved:health                                                                 <IP_ADDRESS>   ready
1182       Disabled           Disabled          1          reserved:host                                                                                ready
3486       Enabled            Disabled          33327      k8s:app.kubernetes.io/name=deathstar                                            <IP_ADDRESS>   ready
                                                           k8s:class=deathstar
                                                           k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=default
                                                           k8s:io.cilium.k8s.policy.cluster=kind-kind
                                                           k8s:io.cilium.k8s.policy.serviceaccount=default
                                                           k8s:io.kubernetes.pod.namespace=default
                                                           k8s:org=empire

Typically, that's how we would look at whether an endpoint is protected by a network policy - by logging onto the Cilium agent node and running the command above.
Would you be able to go through the Star Wars demo and let me know if you have any more luck?

Hello Daniel. First, as mentioned above, I really like the idea behind the tool!
Netfetch did not seem to notice the policies I deployed. I followed the Star Wars demo and netfetch didn't realize it had deployed some network policies to protect my Deathstar deployment.

nicovibert:~$ netfetch scan default --cilium

Running Cilium network policies scan for namespaces: default

Mode: CLI

Using default kubeconfig path: /Users/nicovibert/.kube/config

Policy type: Cilium

Unprotected pods found in namespace default:

default deathstar-7848d6c4d5-286mj <IP_ADDRESS>

default deathstar-7848d6c4d5-r25k5 <IP_ADDRESS>

default tiefighter <IP_ADDRESS>

default xwing <IP_ADDRESS>

Even though I have deployed the Cilium Network Policies. Maybe the tool should leverage the cilium endpoint list output instead to verify if enforcement has been configured.

nicovibert:~$ kubectl -n kube-system exec -it cilium-h9zm7 cilium endpoint list

kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl exec [POD] -- [COMMAND] instead.

Defaulted container "cilium-agent" out of: cilium-agent, config (init), mount-cgroup (init), apply-sysctl-overwrites (init), mount-bpf-fs (init), clean-cilium-state (init), install-cni-binaries (init)

ENDPOINT   POLICY (ingress)   POLICY (egress)   IDENTITY   LABELS (source:key[=value])                                              IPv6   IPv4           STATUS

           ENFORCEMENT        ENFORCEMENT

302        Disabled           Disabled          4          reserved:health                                                                 <IP_ADDRESS>   ready

1182       Disabled           Disabled          1          reserved:host                                                                                ready

3486       Enabled            Disabled          33327      k8s:app.kubernetes.io/name=deathstar                                            <IP_ADDRESS>   ready

                                                           k8s:class=deathstar

                                                           k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=default

                                                           k8s:io.cilium.k8s.policy.cluster=kind-kind

                                                           k8s:io.cilium.k8s.policy.serviceaccount=default

                                                           k8s:io.kubernetes.pod.namespace=default

                                                           k8s:org=empire

Typically, that's how we would look at whether an endpoint is protected by a network policy - by logging onto the Cilium agent node and running the command above.
Would you be able to go through the Star Wars demo and let me know if you have any more luck?

Thank you for testing!
I will go through the same demo and let you know how it goes. This is extremely valuable feedback, and I will make sure the application can handle it. My own testing was with quite basic policies. Thank you again for testing, this will make the app a lot better.

@nvibert Seems like the namespaced scan was depending on the cluster wide scan for marking pods as protected, obviously that wont work when you scan a specific namespace. Thats a blunder on my part of things.
I have merged some changes to main now, and I have gone through the same demo. I have also added verbose outputs to the CLI - so that it is a bit easier to see if a pod is being targeted by a netpol or not.
Do you want to test again and verify that it works? Feel free to test with additional policies as well. There is a --dryrun flag that you can use if you want to ensure that no changes are made during scans.
e.g. netfetch scan default --cilium --dryrun

After further testing of the Cilium scans, this now seems to work. The application is picking up the Cilium policies in clusters. Some tweaking is neccessary, however, that is outside the scope of this issue.
The follow up and improvement of the scanning logic will be done in #106.
Closing this issue. Thank you @nvibert for the help.

Nice one! I will play around with it when I get the chance!