cannot create new actions

Alarmo Version
v1.9.4
HA Version
2022.7.7
Bug description
when I try to create a new action/notification or try to edit an existing action, when saving the configuration, it shows an error:
Something went wrong!
Message format incorrect: extra keys not allowed @ data['actions'][0]['service_data']
Response error: 400
Please report the bug.
***this is an example of yaml code:
service: notify.mobile_app_netcom
data:
message: La alarma está configurada en {{arm_mode|lang=es}}
title: Alarma Armada
service_data:
message: La alarma está configurada en {{arm_mode}}
title: ''
Steps to reproduce
when I try to create a new action or try to edit an existing action
Relevant log output
_No response

_

Please restart home assistant. If you installed the update from the HACS integration you will notice a red message to notify you to restart home assistant...

yes, i did it 2 times, but the error is still there..
I'll try again tomorrow, now I'm back to version 1.9.4
Thank you

This is probably a cache issue.
I am guessing you still see v1.9.4 in the top-right corner of the Alarmo panel.
After updating to v1.9.5, please refresh the browser cache.

OK! you're right! it was a cache problem, the strange thing is that I tried it with 3 different browsers, with one of them I never use it to access home assistant, and I got the same result, that's why I had initially ruled out that it was a cache problem...
thanks a lot!!
Sorry for the bad english, I had to use an automatic translator...


service definition

Hello i will try to use the tool but i have difficulty to adapt for my case :
in proto file i have a service definition
// The greeting service definition.
service Greeter {
// Sends a greeting
rpc SayHello (HelloRequest) returns (HelloReply);
}
do you know how to parse ?

as a workaround, I suggest doing the service manually


Help bot: Remove triage_message() (last place in tree?)

@derAnfaenger indicated this function was removed in many places; this seems to be the last place in the tree to remove it.

Automated message from Dropbox CLA bot
@neiljp, it looks like you've already signed the Dropbox CLA. Thanks!

LGTM

Merged, thanks @neiljp!


daplie.com server offline?

found this package via https://www.npmjs.com/package/serve-https
tried
npm install --global<EMAIL_ADDRESS>https://daplie.com/ refuses to connect via both my local isp and my mobile data.
testing with this service reports failures on 31 different servers across multiple continents and regions.
https://www.uptrends.com/tools/uptime
npm WARN deprecated<EMAIL_ADDRESS>this package has been deprecated                                                         npm ERR! Error while executing:                                                                                npm ERR! C:\Program Files\Git\cmd\git.EXE ls-remote -h -t https://git.daplie.com/Daplie/daplie-cli-tunnel.git                                        npm ERR!                                                                                npm ERR! fatal: unable to access 'https://git.daplie.com/Daplie/daplie-cli-tunnel.git/': Could not resolve host: git.daplie.com                      npm ERR!                                                                                npm ERR! exited with error code: 128

Hey @aspiringguru,
I'd like to resurrect serve-https in the future as it serves a certain niche, but for the moment I'd recommend either https://git.rootprojects.org/root/greenlock-express.js (easy server deployment) or https://telebit.cloud (localhost development).
It looks like you're on Windows. Greenlock works great on Windows. I don't expect you'd have any problems.
Telebit will have 1st class Windows support within the next week or two - that's what I'm working on right now (as in, literally, right now), actually.


Link to Tags using sluggedName instead of the name itself.

this allows tag names to contain any character, including spaces etc, thus validation of the name is now removed
slugged name is automatically generated in the same way as for the questions
the change is backwards-compatible as all the names are transferred to suggedName upon migration

Notice: this passes unit tests, however will not build on Travis until https://github.com/caelum/mamute/pull/134 is merged
Closes #120
Closes #119

Since we support the configurations below at mamute instances, the user can use a dash to split tags ):
# Regular expression to split tags inside Java
tags.splitter.regex = \\,
# Char used to split tags inside the JSP forms. It must matchs with the tags.splitter.regex property
tags.splitter.char = ,
# Regex of allowed characters for tag names
tags.sanitizer.regex = [a-zA-Z0-9-]

I think we should use them when generating the slugged tags(maybe the Normalizer should be customizable too)

I noticed that but I didn't see any case where this would matter. Is there
any? Can you provide an example of string that could cause issues?
On Thursday, January 15, 2015, Leonardo Cesar Wolter <
<EMAIL_ADDRESS>wrote:

Since we support the configurations below at mamute instances, the user
can use a dash to split tags ):
Regular expression to split tags inside Java
tags.splitter.regex = \,
Char used to split tags inside the JSP forms. It must matchs with the tags.splitter.regex property
tags.splitter.char = ,
Regex of allowed characters for tag names
tags.sanitizer.regex = [a-zA-Z0-9-]
I think we should use them when generating the slugged tags(maybe the
Normalizer should be customizable too)
—
Reply to this email directly or view it on GitHub
https://github.com/caelum/mamute/pull/135#issuecomment-70033562.

--
Matej Balantič
T +49<PHONE_NUMBER>
W http://about.me/Matej.Balantic

I could use dash to split and allow spaces on my tags: java ee-jpa
The final result would be java-ee and jpa. If I decide to update those tags, it would be shown as java-ee-jpa :)

That shouldn't be true as only the sluggedName would contain the dash, not
the name. So you would still end up with
java ee
jpa
after insert which would work fine when updating. Maybe I just don't
understand, can you write a unit test which would cause the issue you are
talking about?
On Thursday, January 15, 2015, Leonardo Cesar Wolter <
<EMAIL_ADDRESS>wrote:

I could use dash to split and allow spaces on my tags: java ee-jpa
The final result would be java-ee and jpa. If I decide to update those
tags, it would be shown as java-ee-jpa :)
—
Reply to this email directly or view it on GitHub
https://github.com/caelum/mamute/pull/135#issuecomment-70085693.

--
Matej Balantič
T +49<PHONE_NUMBER>
W http://about.me/Matej.Balantic

Oh, we are keeping the name and the sluggedName, got it. Sorry, I thought you wanted to normalize the name of the tags :)

Hi, so I amended the pull requests:

addressed the review comments regarding indentation and brackets, where I noticed it at least,
slugging for tags is now done by normalizing alphabetic characters and then url encoding special characters. Also added tests for C# and c++

I've addressed the review comments, please review when you can

closing here see https://github.com/caelum/mamute/issues/119#issuecomment-192878835 for more details

This fix (disallowing most characters) although simpler does not allow Japanese or Chinese tags, etc. The updated brutalizer and tag slugging would have allowed any Unicode language.


Duplicate canvas when running in vite dev

Expected Behavior
As many ReactP5Wrapper instances as integrated
Actual Behavior
For each ReactP5Wrapper instance is two canvas are shown
Steps to Reproduce the Problem

npm create vite@latest
npm install @p5-wrapper/react
App.js:

import { useState } from 'react'
import reactLogo from './assets/react.svg'
import viteLogo from '/vite.svg'
import './App.scss'
import { ReactP5Wrapper } from '@p5-wrapper/react'

function App() {
  const [count, setCount] = useState(0)

  function sketch(p5) {
    p5.setup = () => p5.createCanvas(600, 400);

    p5.draw = () => {
        if (p5.mouseIsPressed) {
            p5.fill(0);
          } else {
            p5.fill(255);
          }
          p5.ellipse(p5.mouseX, p5.mouseY, 80, 80);
    };
  }

  return (
    <>

Vite + React

        <button onClick={() => setCount((count) => count + 1)}>
                    count is {count}
        </button>

                    Edit src/App.jsx and save to test HMR

                Click on the Vite and React logos to learn more

      <ReactP5Wrapper sketch={sketch} />
    </>
  )
}

export default App

Specifications
Package Version: 4.2.0

Also see #255, #162, etc

Hey @jamesrweb,
thanks a lot for your answer. I am not using Next.js, but do use strict mode in react due to the default configuration of the vite@latest composition. By removing the strict mode tag I also get rid of the duplicate canvas.

This worked! Please add that workaround into the readme file to help others solving this common confusion :)
For me, I moved the ReactP5Wrapper outside of StrictMode wrapper like this:
// main.tsx
// ...

// Remove the `StrictMode` wrapper, leaving the `App` unwrapped.
ReactDOM.createRoot(document.getElementById("root")!).render(<App />);

// App.tsx
// ...

function App() {
  return (
    <>
      {/* The p5wrapper component is free from `StrictMode` */}
      <ReactP5Wrapper sketch={sketch} />
      <React.StrictMode>
        {/* While this area has strict mode enabled */}

Hello, strict mode!

      </React.StrictMode>
    </>
  );
}


issue with privatize fails with Better.Function

Bogus case
	var Foobar	= Better.Class(function(){
		this._steps		= [];
	}, {
	        // arguments: [],
	        privatize: true
	})

	Foobar.prototype.push = Better.Function(function(arg){
	         this._steps.push(arg)
	}, {
	        arguments: ["String"],
	        return: undefined
	})

	// ---------------------------------------------

	var foobar = new Foobar();
	foobar.push("test");

Explaination

when the _steps is accessed, the caller is compared to the list of private function
but the private function is the Better.Function one... so the comparison fails
if the .push is declared as a normal function, not Better.Function, we compare the good function

Solutions

if the function is a BetterFunction, stack the original function, and not the better function


Android app crashes after naming device

Android version 4.2.2
Keybase version 1.0.0-alpha-2
I signed into my Keybase account using my username and my desktop device. Adding the code worked ok. I named the device and clicked continue, then the app crashes.
If I reopen it, I can see that the "Phone" device has been created (it's in the list of devices to use for signing in, along with the desktop and the paper key) but it doesn't seem to be associated with the app.4.2.2.
I revoked the device and tried again, but the same thing happened.

Experiencing the same. Works fine with Android M but not Jellybean.
Maybe Jellybean support can be dropped altogether, and concentrate on KK, M, N, and Android O? (My Jellybean phone is only serving as secondary/backup.)

@techmagus can you push the Gear > "Send Feedback" and send up your logs? We can take a look, thanks!

@maxtaco I can't get as far as seeing a gear icon -- the options are just "create an account" and "log in". As I described above, I tried logging in but the app crashes. Is there another way of sending the logs?
(I'd definitely like to see Jellybean support kept as I'm still using it!)

cc @cjb

Perhaps best for us to just try to repro the bug ourselves in a Jellybean simulator, I'll add an internal bug report to do that.
(Haven't reached an opinion yet on how much effort we should put in to supporting Jellybean.)

Any progress on this? Anything we can do to help?

Same here. Android app crashed immediately after entering text verification code and now won't let me log in even though the device is listed as verified.
Android 4.2.2 on GT-I8200.
What can I do to help debug this?

Submitted report from the Android.

@specious I don't think we can support that version of Android, I think it's too old.  I hope the keybase app didn't cause your screen to crack BTW!

@maxtaco, I absolutely concur that this Android is too old to officially bother supporting. Isn’t it curious though, that it’s possible to have a device that is listed as vefiried and yet it cannot log in? How is that happening?

@maxtaco, I absolutely concur that this Android is too old to officially bother supporting. Isn’t it curious though, that it’s possible to have a device that is listed as verified and yet it cannot log in? How is that happening?

My guess is that the app crashed when trying to store the secret key to the Android keystore, and now the app can't read the private key back out.  So it got most the way through the provisioning process, but died when trying to access the key material.

@maxtaco and @specious It makes sense to not support this version of Android. Especially since it essentially is not supported right now.
But in that case it should be limited on the play-store/f-droid and/or the AndroindManifest.xml.
That would keep people (like me) with an old device from trying to install it, and getting a crash. Which is far more annoying than seeing a "this app is not compatible with your device", which I am kinda used to, having such an old Android.

Good point. cc: @keybase/react-hackers

Not to mention the fact that I am eating up all these great device names, and now that they're revoked I can't re-use them 😆 😢

@jbonhag can you send feedback from the app?

Just sent the logs, hope they help!


sparse.linalg.svds: ensure non-negative singular values for which='SM'

When estimating the smallest magnitude singular values of a singular
matrix, it is common for ARPACK to return tiny negative values.  These
are handled carefully in which='LM', but not for which='SM'.  Simple
examples such as
  A = csr_matrix(([1.,1,1,1,1], ([0,1,1,2,3],[0,0,1,0,1])), shape=(4,3))
  svds(A, which='SM', k=2, return_singular_vectors=False)

produce FloatingPointError: invalid value encountered in sqrt.  This
commit ensures that the estimated eigenvalues are non-negative.

https://github.com/scipy/scipy/pull/10830 supersede this PR

Apologies your PR didn't get reviewed @jedbrown. We're short on reviewers that understand sparse linalg.
After merging gh-10830, your example now gives:
>>> A = csr_matrix(([1.,1,1,1,1], ([0,1,1,2,3],[0,0,1,0,1])), shape=(4,3))
>>> svds(A, which='SM', k=2, return_singular_vectors=False)
/Users/rgommers/Code/scipy/scipy/sparse/linalg/eigen/arpack/arpack.py:1871: RuntimeWarning: invalid value encountered in sqrt
  cutoff = cond * np.max(eigvals)
array([      nan, 1.1755705])

Just checking: I assume that's the expected behavior?

It is not expected/desirable behavior. Expected behavior is to return [1.1755705, 0] without errors. A singular matrix is not malformed input.

Sorry, I do not have a setup to run it myself and debug now. But there is something I do not understand in this error in https://github.com/scipy/scipy/pull/8169#issuecomment-552223536
The corresponding code is line 1864-1871 of https://github.com/scipy/scipy/blob/master/scipy/sparse/linalg/eigen/arpack/arpack.py
    # Gramian matrices have real non-negative eigenvalues.
    eigvals = np.maximum(eigvals.real, 0)

    # Use the sophisticated detection of small eigenvalues from pinvh.
    t = eigvec.dtype.char.lower()
    factor = {'f': 1E3, 'd': 1E6}
    cond = factor[t] * np.finfo(t).eps
    cutoff = cond * np.max(eigvals)

First, notice the 1865 line eigvals = np.maximum(eigvals.real, 0) ,which is suggested in PR, appearing in the merged code. That is why I have proposed closing this PR.
Second, there is no explicit sqrt call in the line 1871:

cutoff = cond * np.max(eigvals)

so I am unsure where the error comes from.
If this error is re-confirmed, the proper course of action may be to close this PR, since the proposed fix is already merged, and instead open a new bug report with this error.

Thanks @jedbrown, and thanks for the detailed feedback @lobpcg.
It looks like I was indeed testing with the wrong version. At least, I can't reproduce it anymore:
In [1]: from scipy.sparse import csr_matrix

In [2]: from scipy.sparse.linalg import svds

In [3]: %paste
  A = csr_matrix(([1.,1,1,1,1], ([0,1,1,2,3],[0,0,1,0,1])), shape=(4,3))
  svds(A, which='SM', k=2, return_singular_vectors=False)

## -- End pasted text --
Out[3]: array([0.       , 1.1755705])

In [4]: import scipy; scipy.__version__
Out[4]: '1.5.0.dev0+9e27e4c'

Sorry about the confusion. Seems fixed, closing.


Specifying hash property to generate method has no effect

Steps to reproduce:

Create a new short instance with a DB connection
Call short.generate and specify a hash
Inspect the created document

Expected behavior:

Hash of saved document should match the hash specified in the document creation
If the hash was a duplicate, an error should be raise

Actual behavior: a random hash is generated
Gist: https://gist.github.com/matmar10/6659ce1d67df8f79eda4
It seems change #26 had no effect.

Could not reproduce. I was confused by the fact that the existing hash is always returned for an identical URL, event when a hash is specified. That seems like undesired behavior, because it's not honoring what was passed in and it's also not complaining or giving any notice. I'll create a separate issue/patch/test for that case. Closing.


[Backport-1.x]Avoid override of routes() in BaseRestHandler to respect the default behavior defined in RestHandler (#889)

Description
[Describe what this change achieves]
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

start gradle check

@dblock @saratvemulapalli Could we have anyone review this backport PR? One of the PR on security plugin needs this PR to be merged. Thanks!

@dblock Should not that PR be split into 2 separate PRs the same way how that was done in main?

I'm ok with these going together, as long as we're ok squashing them (the only way merges happen here).

@dblock I think we're ok squashing them as long as the finally merged comit message will reflect both of the 2 PRs.

@dblock Are we waiting for anything to merge it?

IMO, those commits should not be squashed as they address two different issues.

@vrozov is right, @cliu123 would you please split these into two backport PRs? I thought I could override the merge to be just the commits, but it's disabled by admin on the repo

I am going to change my mind, I think @vrozov is right, @cliu123 would you please split these into two backport PRs? sorry for the annoyance

@dblock Removed the 2nd commit from this PR. Once this PR get merged, I'll PR the other commit using the same branch.

start gradle check

Merged, thx

@dblock Thanks for reviewing and merging! This is the PR for another commit.


Video preprocessor defenses

Similar to the audio data case, it would be great to have a basic set of preprocessor defenses available for video data.
For example, one could adapt the current JpegCompression and SpatialSmoothing preprocessors such that they are able to handle video data on a frame-by-frame basis. Furthermore, we have recently introduced the FFmpeg dependency, which is a powerful tool that can also convert or compress video data. Building on top of FFmpeg, we could thus add a video compression preprocessor that compresses original video input by choosing a lower bit rate.

[x] JpegCompression now supports video data


[related_resources] add yival.ai to the prompt tools section

Thank you for the contribution! Edited slightly for consistency and to match the Yival readme.


Bump cloudsql-proxy image

Description
Bump cloudsql-proxy image from 1.19.1-alpine to 1.23.0-alpine
and it's alpine version from 3.13.5 to 3.14.0

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


Fix/multi cut via

ViaCut defines width and height, is the height and width in "1" redundant?

ViaCut defines width and height, is the height and width in "1" redundant?

I think the ViaArrayGenerator overrides the default via specification.
@soneryaldiz @meghna09  @arvuce22 can confirm.


Camera only exits out with "Q" when no extra paramters

@daniegr amazing package and code. This is truly one of the best packages on pose estimation I found. Everything is super clean and efficient. Truly a masterpiece.
Noticed though that I can only exit out of the camera using "Q" when its just
python track.py when I try using it with other models, the Q exit does not work and I have to terminate it from terminal. I don't know if you encountered that as well

@funeconomist: Thanks man. Highly appreciated! Regarding your issue, didn't the program even quit if you clicked the camera screen before typing 'Q'?


Update Procfile

IBM Cloud toolchain: Delivery Pipeline deployed customers to dev, including commit 55a8f53c515923e13586a399abfe7d522be85d74

IBM Cloud toolchain: Delivery Pipeline deployed customers to prod, including commit 55a8f53c515923e13586a399abfe7d522be85d74


Groups

Currently I'm doing a 'computed' that crawls through fields.
I have a form with input groups and it's list in menu on left (fixed positioned). Form is long.
It would be nice if I could define "valid-group" for inputs and then check if all inputs in group are valid (and if it has dirty fields) to mark it.

Thank you for your comment !!
I want to understand more about your above comment.
I hope that you provide the example codes. :smiley_cat:

Sorry, I wrote it fast and incomprehensibly.
For example, currently v-validate creates vm.validation.[model-name] object. What I mean is create directive v-validate-group (for example: v-validate-group="groupName") which creates vm.validationGroups.[groupName]` with listed all validations.
Example:
<h1
    v-class="has-error: validationGroup.personalData.dirty && validationGroup.personalData.invalid">
Personal data</h1><!-- this could be also a fixed-placed menu on side of the page-->
<input type="text"
    v-model="form.personalData.name"
    v-validate="minLength: 3"
    v-validation-group="personalData"></input>
<input type="text"
    v-model="form.personalData.pesel"
    v-validate="required, pesel"
    v-validation-group="personalData"></input>

(pesel is a type of ID which I have to validate with date of birth, sex and calculate the check digit)
If any of those 2 fields is invalid, header has class has-error.
It would be nice if it would be implemented natively.

Thank you for your details example code.
That's sounds good !!
I'll try to consider this feature at #41.

I implemented in 2.0.0-alpha.1


Release Notes Not Updated

CHANGELOG.md says: "Please refer to the Github ngCordova Releases file for detailed information." but the releases have not had release notes since 0.1.17-alpha.

I knew I keep forgetting something.

This has been fixed; going forward we will include release notes.  Thanks for bringing this up.
https://github.com/driftyco/ng-cordova/releases/tag/v0.1.24-alpha


Moved Postgres9 to the STIG Archive Table

Overall Review of Changes:
Moved Postgres9 to the STIG Archive table
Issue Fixes:
N/A
Enhancements:
Moved Postgres9 to the STIG Archive table
How has this been tested?:
Tested directly on ReadTheDocs

Thank you!


Static type checking for match

Right now our match function is limited in its static type checking. It will not statically tell you whether or not you have a handler for all keys, will not ensure that the _ is used as a catch-all, and probably more. It would be great if the Kybra match function were just as powerful as the Rust match function, but as least as powerful as Azle's.
What we really want from Python's type hinting system is something like TypeScript's keyof operator or index types. Unfortunately the Python type hinting system seems to just not be powerful enough to do this yet. Here are a number of issues that explore these limitations:

https://github.com/python/typing/discussions/1280
https://github.com/python/typing/issues/685
https://github.com/python/mypy/issues/7856
https://github.com/python/mypy/issues/7856#issuecomment-549488040
https://peps.python.org/pep-0544/

We are looking to remove match entirely


cmd/link: 'index out of range' when build with buildmode=plugin

go version

go version devel +d13fa4d Fri Oct 14 03:58:15 2016 +0000 linux/amd64

go env

GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/md/.gvm/pkgsets/master/global"
GORACE=""
GOROOT="/home/md/.gvm/gos/master"
GOTOOLDIR="/home/md/.gvm/gos/master/pkg/tool/linux_amd64"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build545183226=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"

What did you do?
I tried to build following code:

package main
func Test(value string) string {
return "test" + value
}

by calling go build -buildmode=plugin
What did you expect to see?
go build -buildmode=plugin should not return any error
When func Test(value string) string has no string argument:

package main
func Test() string {
return "test"
}

code compiles without any error.
What did you see instead?

panic: runtime error: index out of range
goroutine 1 [running]:
panic(0x5aa860, 0x69d560)
/home/md/.gvm/gos/master/src/runtime/panic.go:527 +0x1a0
cmd/link/internal/ld.(*deadcodepass).flood(0xc42006fce0)
/home/md/.gvm/gos/master/src/cmd/link/internal/ld/deadcode.go:292 +0xdd2
cmd/link/internal/ld.deadcode(0xc4200768f0)
/home/md/.gvm/gos/master/src/cmd/link/internal/ld/deadcode.go:62 +0xdb
cmd/link/internal/ld.Main()
/home/md/.gvm/gos/master/src/cmd/link/internal/ld/main.go:186 +0x81b
main.main()
/home/md/.gvm/gos/master/src/cmd/link/main.go:55 +0x139

I believe this is #17140, which I believe is fixed by https://golang.org/cl/29692, which is waiting for review.


[BUG] Upstream repository for cri-o has moved

New versions of cri-o have moved to a different location. This causes installations using cri-o as CRI to fail.
The installer needs to be updated to use the new repository, in the same way that the Kubernetes repository was moved.

For now the installation issue has been worked around, but we're still not using the new upstream repository, since I could not find any stable release packages there, only pre-releases.

This has been fixed in commit: e9b11085c5781698cff6d02c76b707adf47ae6f7


🧑💻 : Fixing the visibility of Project Names in Dark Mode

:red_circle: Title :Fixing the visibility of Project Names in Dark Mode.
:red_circle: Enhancement Aim : To make Project Names visible clearly in Dark Mode.
:red_circle: Changes : The Text of the Project Names can be turned into black in Light mode and white in Dark Mode.
Screenshots 📷

✅ Details to Include When Taking the Issue:
Name : Lokesh | Contributor
Participant Role (Specify the Open Source Program name, e.g., GSSOC, Hacktoberfest, etc.): gssoc'24-ext, Hacktoberfest.

Happy Contributing! 🚀
Wishing you all the best on your open source journey. Enjoy! 😎

Name : Deven | Contributor
Program Name : Hacktoberfest
Can you please assign this tak to me. I can solve this issue ASAP! I really want to contribute to this issue

@iamrahulmahato can you please guide me about the contribution works?


Add namespace metadata to the templates

Without this field running helm template --namespace <namespace> will not fill it. See https://github.com/helm/helm/issues/10737
It should not affect any examples using helm. I'm not sure about direct kubectl calls. Should I update examples to use --namespace?
Also, what kind of chart version bump should I add if this PR would get to be accepted?

I accept the CLA
Please add label hacktoberfest or hacktoberfest-accepted

Thanks for raising this pull request and spending the time. Sorry for the delay in responding, but if to explicitly specify a namespace within generated resources or not is a hotly debated topic. I wanted to refresh my memory on the discussion prior to responding.
The question of a Helm Best Practice in this area is discussed here in issue 5465.
Although @bacongobbler received some push back on his comments, I think he is the defacto owner and therefore gets to declare Good Practice:
In general, templates should not define a namespace. This is because Helm installs objects into the namespace provided with the --namespace flag. By omitting this information, it also provides templates with some flexibility for post-render operations (like helm template | kubectl create --namespace foo -f -)
In my head one major reason to explicitly declare a namespace would be if the Helm Chart needed to deploy resources across multiple namespaces, in another GitHub issues 3553, he highlights that charts are generally restricted to one namespace:
Compared to kubectl, Helm does not have strict enforcement enabled. We tried to do that for Helm 3 but had to back out as people were deploying apps across multiple namespaces, breaking a long-standing assumption in Helm 2 that charts should be restricted to a namespace. Enforcing it meant breaking user's charts, which we avoided with the Helm 3 update. So we had to remove that constraint in Helm 3.0.0-alpha.2.
Regardless the IBM MQ Helm Chart only deploys into a single namespace, and therefore I don't think that argument holds too much water.
Within the sample script you will see that we set kubectl default namespace to the one we are targeting the deployment for. There are numerous ways to do this which accomplish the same thing, but as the core Helm organization do not appear to support it, explicitly adding a namespace to each resource does not appear to be the best.
Am I missing anything?

I see, I didn't know there was such official recomendation. I'll close the PR then.


Translation for the page 'Installation -> Getting Started'

Please help us translating this page in Italian!
Aiutaci a tradurre questa pagina in Italiano!
You can find all the details about how to help here: https://github.com/reactjs/it.reactjs.org/issues/1
GRAZIE! :smile:

Working on this


Error "Cannot find module 'cypress'"  using Yarn Berry

Hi there!
This action worked with yarn berry workspaces. but, this action can't find the "cypress" module.
Error: Cannot find module 'cypress'

I found the issue of Yarn Berry and tried as follows.

https://github.com/cypress-io/github-action/pull/260

here is the relavant configuration:
jobs:
  check-e2e-test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - name: Use Node.js 14.x
        uses: actions/setup-node@v1
        with:
          node-version: 14.x

      - name: Cypress run
        uses: cypress-io/github-action@v2
        with:
          install-command : yarn install --immutable --immutable-cache
          start: yarn start
          wait-on: 'http://localhost:3000'
          browser: chrome
          headless: true

here is github-action log:
Run cypress-io/github-action@v2
  with:
    install-command: yarn install --immutable --immutable-cache
    build: yarn run build
    start: yarn start
    wait-on: http://localhost:3000
    browser: chrome
    headless: true
    record: false
    config-file: cypress.json
Received 22 of 22 (100.0%), 0.0 MBs/sec
Cache Size: ~0 MB (22 B)
/usr/bin/tar --use-compress-program zstd -d -xf /home/runner/work/_temp/be0c8559-6dda-42c1-822d-2db565488a1c/cache.tzst -P -C /home/runner/work/*****/*****
Cache restored successfully
Received 0 of 353031365 (0.0%), 0.0 MBs/sec
Received 58720256 of 353031365 (16.6%), 28.0 MBs/sec
Received 155189248 of 353031365 (44.0%), 49.3 MBs/sec
Received 251658240 of 353031365 (71.3%), 60.0 MBs/sec
Received 344642757 of 353031365 (97.6%), 65.7 MBs/sec
Received 353031365 of 353031365 (100.0%), 61.3 MBs/sec
Cache Size: ~337 MB (353031365 B)
/usr/bin/tar --use-compress-program zstd -d -xf /home/runner/work/_temp/dd9a16d5-2321-41d4-9f8f-3e8284d07e08/cache.tzst -P -C /home/runner/work/*****/*****
Cache restored successfully
install command command "yarn install --immutable --immutable-cache"
current working directory "/home/runner/work/*****/*****"
/usr/local/bin/yarn install --immutable --immutable-cache
➤ YN0000: ┌ Resolution step
Resolution step
➤ YN0000: └ Completed in 0s 376ms
➤ YN0000: ┌ Fetch step
Fetch step
➤ YN0000: └ Completed in 0s 743ms
➤ YN0000: ┌ Link step
Link step
➤ YN0000: └ Completed in 0s 397ms
➤ YN0000: Done with warnings in 1s 966ms
/opt/hostedtoolcache/node/14.17.6/x64/bin/npx cypress cache list
┌─────────┬───────────────────┐
│ version │ last used         │
├─────────┼───────────────────┤
│ 8.4.1   │ a few seconds ago │
├─────────┼───────────────────┤
│ 8.5.0   │ a few seconds ago │
└─────────┴───────────────────┘
build app command "yarn run build"
current working directory "/home/runner/work/*****/*****"
/usr/local/bin/yarn run build
The following changes are being made to your tsconfig.json file:
  - compilerOptions.paths must not be set (aliased imports are not supported)

Creating an optimized production build...
Compiled successfully.

File sizes after gzip:

  74.98 KB  build/static/js/2.c1fee284.chunk.js
  1.71 KB   build/static/js/3.b8a66e6b.chunk.js
  1.17 KB   build/static/js/runtime-main.2d193d74.js
  1.01 KB   build/static/js/main.a1fef262.chunk.js
  554 B     build/static/css/main.f09a1402.chunk.css

The project was built assuming it is hosted at /.
You can control this with the homepage field in your package.json.

The build folder is ready to be deployed.
You may serve it with a static server:

  yarn global add serve
  serve -s build

Find out more about deployment here:

  cra.link/deployment

start server "yarn start command "yarn start"
current working directory "/home/runner/work/*****/*****"
waiting on "http://localhost:3000" with timeout of 60 seconds
/usr/local/bin/yarn start
The following changes are being made to your tsconfig.json file:
  - compilerOptions.paths must not be set (aliased imports are not supported)

ℹ ｢wds｣: Project is running at http://<IP_ADDRESS>
ℹ ｢wds｣: webpack output is served from
ℹ ｢wds｣: Content not from webpack is served from /home/runner/work/*****/*****/public
ℹ ｢wds｣: 404s will fallback to /
Starting the development server...

Compiled successfully!

You can now view ***** in the browser.

  Local:            http://localhost:3000
  On Your Network:  http://<IP_ADDRESS>:3000

Note that the development build is not optimized.
To create a production build, use yarn build.

Error: Cannot find module 'cypress'
Require stack:
- /home/runner/work/_actions/cypress-io/github-action/v2/dist/index.js

The above error occurred and was solved using with command.
  check-e2e-test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - name: Use Node.js 14.x
        uses: actions/setup-node@v1
        with:
          node-version: 14.x

      - name: Cypress run
        uses: cypress-io/github-action@v2
        with:
          install-command : yarn install --immutable --immutable-cache
          command: yarn test:e2e

here is yarn test:e2e script:
"test:e2e": "start-server-and-test start http://localhost:3000 cypress:run",

Why can't I find the cypress module when I use the command provided by Cypress github-action? Or did I miss something?
I'd appreciate it if you had any other advice. thank you!🙏

I have this same issue. I don't run the install command in the cypress-io/github-action@v2, but in a previous workflow run step:
run: yarn install --immutable --immutable-cache
This was working previously with yarn, but this is now yarn "berry" (3.0.2).
I am using PnP and a Zero-Installs Yarn setup.

Having the same issue when using the following setup:
name: Cypress
on: deployment_status
jobs:
  e2e:
    if: github.event.deployment_status.state == 'success'
    runs-on: ubuntu-latest
    steps:
      - name: Check out Git repository
        uses: actions/checkout@v2
      - name: Run Cypress
        uses: cypress-io/github-action@v2
        env:
          CYPRESS_BASE_URL: ${{ github.event.deployment_status.target_url }}

Restoring Cypress cache error: Cache service responded with 403
Restoring NPM cache error: Cache service responded with 403
/usr/local/bin/yarn --frozen-lockfile
yarn install v1.22.11
[1/4] Resolving packages...
[2/4] Fetching packages...
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info "<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The CPU architecture "x64" is incompatible with this module.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info "<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info "<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning "analytics > @analytics/core ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "next > styled-jsx ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "@storybook/addon-a11y > @storybook/api ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| 16.x || 16.4.0-alpha.0911da3".
warning "@storybook/addon-a11y > @storybook/api ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| 16.x || 16.4.0-alpha.0911da3".
warning "@storybook/addon-a11y > @storybook/api > @reach/router ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^15.0.0 || ^16.0.0".
warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "@storybook/addon-essentials ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "@storybook/addon-essentials ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "@storybook/addon-essentials ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "@storybook/react ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "chromatic ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency "webpack@>=2".
warning "@storybook/addon-postcss ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^5.0.0".
warning "@storybook/addon-postcss ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^5.0.0".
warning "@storybook/addon-postcss ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^5.0.0".
warning "@storybook/addon-essentials > @storybook/addon-docs > @storybook/core ><EMAIL_ADDRESS>has unmet peer dependency "webpack@*".
warning "@storybook/react ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "@storybook/react ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "@storybook/react > @babel/preset-flow ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "@storybook/react > @babel/preset-flow > @babel/plugin-transform-flow-strip-types ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[4/4] Building fresh packages...
Done in 64.94s.
/usr/local/bin/npx cypress cache list
┌─────────┬───────────┐
│ version │ last used │
├─────────┼───────────┤
│ 8.5.0   │ a day ago │
└─────────┴───────────┘
/usr/local/bin/npx cypress verify

[STARTED] Task without title.
[SUCCESS] Task without title.
Saving NPM cache error: Unable to reserve cache with key yarn-linux-x64-2a75aa6bb91a1fe6a02361e54c7b8336bf132bdbde79a48d3146324302a86a93463189683d43d89f6919b3eb95a4f77d80ecf11d37b38522000e7ca93162a038, another job may be creating this cache.
Saving Cypress cache error: Unable to reserve cache with key cypress-linux-x64-2a75aa6bb91a1fe6a02361e54c7b8336bf132bdbde79a48d3146324302a86a93463189683d43d89f6919b3eb95a4f77d80ecf11d37b38522000e7ca93162a038, another job may be creating this cache.
Error: Cannot find module 'cypress'
Require stack:
- /home/runner/work/_actions/cypress-io/github-action/v2/dist/index.js

@forgo Thank you for your advice!
I modified it as you suggested, but it doesn't work.
  check-e2e-test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - name: Use Node.js 14.x
        uses: actions/setup-node@v1
        with:
          node-version: 14.x

      - name: Install dependencies
        run: yarn install --immutable --immutable-cache

      - name: Cypress run
        uses: cypress-io/github-action@v2
        with:
          install: false
          start: yarn start
          wait-on: 'http://localhost:3000'
          browser: chrome
          headless: true

I'm using PnP and a Zero-Installs Yarn 3.0.2 setup.
Anyway, is it impossible to install using yarn berry in Cypress github-action?

@CharlesStover in my demo, the correct way is "command-prefix: yarn">_<

Run cypress-io/github-action@v2
/usr/local/bin/yarn --frozen-lockfile
yarn install v1.22.17
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
warning "react-spring ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "react-spring ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "react-spring ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "react-spring ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "react-spring ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "react-spring ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "react-spring ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[4/4] Building fresh packages...
$ patch-package
patch-package 6.4.7
Applying patches...
<EMAIL_ADDRESS>✔
<EMAIL_ADDRESS>✔
<EMAIL_ADDRESS>✔
Done in 31.35s.
/usr/local/bin/npx cypress cache list
┌─────────┬─────────────┐
│ version │ last used   │
├─────────┼─────────────┤
│ 9.0.0   │ 13 days ago │
└─────────┴─────────────┘
/usr/local/bin/npx cypress verify
[STARTED] Task without title.
[SUCCESS] Task without title.
/usr/bin/tar --posix --use-compress-program zstd -T0 -cf cache.tzst -P -C /home/runner/work/editor/editor --files-from manifest.txt
Cache Size: ~148 MB (155076066 B)
Cache saved successfully
/usr/bin/tar --posix --use-compress-program zstd -T0 -cf cache.tzst -P -C /home/runner/work/editor/editor --files-from manifest.txt
Cache Size: ~187 MB (196090537 B)
Cache saved successfully
start server "yarn vite command "yarn vite"
current working directory "/home/runner/work/editor/editor"
waiting on "http://localhost:3000" with timeout of 60 seconds
/usr/local/bin/yarn vite
yarn run v1.22.17
$ /home/runner/work/editor/editor/node_modules/.bin/vite
Pre-bundling dependencies:
prosemirror-commands
prosemirror-inputrules
prosemirror-model
prosemirror-state
prosemirror-view
(...and 6 more)
(this will be run only when your dependencies or config have changed)
vite v2.6.14 dev server running at:

Local:    http://localhost:3000/
Network:  http://<IP_ADDRESS>:3000/

ready in 768ms.
Cypress test command: npx yarn dlx cypress run --config-file cypress.json
/usr/local/bin/npx yarn dlx cypress run --config-file cypress.json
yarn run v1.22.17
error Command "dlx" not found.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Error: The process '/usr/local/bin/npx' failed with exit code 1

the wrong version
Run cypress-io/github-action@v2
/usr/local/bin/yarn --frozen-lockfile
yarn install v1.22.17
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
warning "react-spring ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "react-spring ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "react-spring ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "react-spring ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "react-spring ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "react-spring ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "react-spring ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[4/4] Building fresh packages...
$ patch-package
patch-package 6.4.7
Applying patches...
<EMAIL_ADDRESS>✔
<EMAIL_ADDRESS>✔
<EMAIL_ADDRESS>✔
Done in 31.35s.
/usr/local/bin/npx cypress cache list
┌─────────┬─────────────┐
│ version │ last used   │
├─────────┼─────────────┤
│ 9.0.0   │ 13 days ago │
└─────────┴─────────────┘
/usr/local/bin/npx cypress verify

[STARTED] Task without title.
[SUCCESS] Task without title.
/usr/bin/tar --posix --use-compress-program zstd -T0 -cf cache.tzst -P -C /home/runner/work/editor/editor --files-from manifest.txt
Cache Size: ~148 MB (155076066 B)
Cache saved successfully
/usr/bin/tar --posix --use-compress-program zstd -T0 -cf cache.tzst -P -C /home/runner/work/editor/editor --files-from manifest.txt
Cache Size: ~187 MB (196090537 B)
Cache saved successfully
start server "yarn vite command "yarn vite"
current working directory "/home/runner/work/editor/editor"
waiting on "http://localhost:3000" with timeout of 60 seconds
/usr/local/bin/yarn vite
yarn run v1.22.17
$ /home/runner/work/editor/editor/node_modules/.bin/vite
Pre-bundling dependencies:
  prosemirror-commands
  prosemirror-inputrules
  prosemirror-model
  prosemirror-state
  prosemirror-view
  (...and 6 more)
(this will be run only when your dependencies or config have changed)

  vite v2.6.14 dev server running at:

  > Local:    http://localhost:3000/
  > Network:  http://<IP_ADDRESS>:3000/

  ready in 768ms.

Cypress test command: npx yarn dlx cypress run --config-file cypress.json
/usr/local/bin/npx yarn dlx cypress run --config-file cypress.json
yarn run v1.22.17
error Command "dlx" not found.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Error: The process '/usr/local/bin/npx' failed with exit code 1

my yml
name: type simulate test
on: [push]
jobs:
  cypress-run:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - name: Cypress-run
        uses: cypress-io/github-action@v2
        with:
          command-prefix: yarn
          start: yarn vite
          wait-on: 'http://localhost:3000'

I was really stuck and that saved me so much time, thanks @CharlesStover ! 🥇

Has anybody got this to work with Cypress 10, Yarn 3, and cypress-io/github-action v4?
I can get it working with Cypress 10, Yarn 3, and cypress-io/github-action v3.1.0. But I would like to instead use cypress-io/github-action v4.

I also cannot get it working with cypress-io/github-action v4.

Cypress v10 + Cypress GitHub Action v4 + Yarn v3
Sorry I'm late to upgrading to v4.
Create the file ./scripts/cypress-pnp.cjs. If you are using Yarn workspaces, create it in the workspace that's running cypress.
// running Cypress from root
const { mkdirSync, writeFileSync } = require('fs');

const SPACES = 2;

const PACKAGE_JSON = {
  name: 'cypress',
  version: '0.0.1',
  main: './index.cjs',
  type: 'commonjs',
  peerDependencies: {
    cypress: '*',
  },
};

mkdirSync('./node_modules/cypress', {
  recursive: true,
});

writeFileSync(
  './node_modules/cypress/package.json',
  JSON.stringify(PACKAGE_JSON, null, SPACES),
);

writeFileSync(
  './node_modules/cypress/index.cjs',
  `require('../../.pnp.cjs').setup();
module.exports = require('cypress');`,
);

// running Cypress from packages/package-name workspace:
const { mkdirSync, writeFileSync } = require('fs');

const SPACES = 2;

const PACKAGE_JSON = {
  name: 'cypress',
  version: '0.0.1',
  main: './index.cjs',
  type: 'commonjs',
  peerDependencies: {
    cypress: '*',
  },
};

mkdirSync('./node_modules/cypress', {
  recursive: true,
});

writeFileSync(
  './node_modules/cypress/package.json',
  JSON.stringify(PACKAGE_JSON, null, SPACES),
);

writeFileSync(
  './node_modules/cypress/index.cjs',
  `require('../../../../.pnp.cjs').setup();
module.exports = require('cypress');`,
);

(The only difference between the two is the ../../ before .pnp.cjs for workspaces.)
For the cypress-io/github-action:

If you are using with.project for a workspace, move it to with.working-directory.
Set with.install to false. Remove with.install-command since we installed in a previous step.
Just to be safe, keep with.command-prefix set to yarn dlx.

If time permits this weekend, I'll package this script up into a Node module to make this easier; but the above copy-paste job should work for now.
Link to proof of concept run where the installation is passing for me.

You're likely to get this error if you're using yarn or pnpm workspaces. To solve it, just install cypress before running this action, like so:
- run: pnpm install cypress -wD # or yarn add cypress -wD
- uses<EMAIL_ADDRESS>

@saseungmin
Please check out Yarn Plug'n'Play and see if it meets your needs. This is new functionality contributed by @PilotConway.


Add Koyeb as a deployment option

Describe this PR
Hi there :wave:
Added a deployment guide for Koyeb.

Changes
Add and reference the Koyeb deployment guide.

What issue does this fix?

Any other relevant information

Note: it seems that the service is in preview and one can not signup instantly ⬇

Could be that it's too early to add to our docs because of that and things could also change and add some maintenance of the docs?

Hi @Jolg42
This should be fine, we’re at the end of the private preview phase.
The platform is actually already used in production and there are not going to be any breaking changes.

Thanks @edouardb and @Jolg42 for your reviews/edits!


Create the data model - Error scaffolding db - Could not load file or assembly Bricelam.EntityFrameworkCore.Pluralizer

I am getting below error while scaffolding db.
System.IO.FileNotFoundException: Could not load file or assembly 'Bricelam.EntityFrameworkCore.Pluralizer, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
File name: 'Bricelam.EntityFrameworkCore.Pluralizer, Culture=neutral, PublicKeyToken=null'
at System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMarkHandle stackMark, IntPtr pPrivHostBinder, Boolean loadTypeFromPartialName, ObjectHandleOnStack type, ObjectHandleOnStack keepalive)
at System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean loadTypeFromPartialName)
Could not load file or assembly 'Bricelam.EntityFrameworkCore.Pluralizer, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
Thanks for your assistance.

netstandard2.0

all
runtime; build; native; contentfiles; analyzers

After removing below lines form csproj file, it worked
  <PrivateAssets>all</PrivateAssets>
  <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets>
</PackageReference>

But, I would like to understand why after to erase that lines the problem was solved.


Jumpto not working

You should provide a demo where we are using jumpto prop I did not understand how it works searched a lot but end up with no result

https://github.com/react-native-community/react-native-tab-view/blob/8e8e3fcf4bf4fd405f0aea11d0bfc4ee92ba8442/example/src/CustomTabBarExample.tsx#L96


How can I jump Today in calendar widget?

Description
Is there a way to jump Today in calender widget?
Please tick the boxes

[X] You've read the docs
[X] You've checked for duplicate issues

Hi, I'm sorry but I don't quite understand what you mean by that?
Are you asking if there's a fast way to come back to the current month after navigating in previous or future months?

Sorry for my badly expression.
I see many calender widgets have a button, which can be clicked to jump Today, as well other buttons to Next month >,Prev month <, etc.
But I don't find how to come back to today easily, if I go to another month.

Sorry for my badly expression. I see many calender widgets have a button, which can be clicked to jump Today, as well other buttons to Next month >,Prev month <, etc. But I don't find how to come back to today easily, if I go to another month.

Just click back on > and find the current month again 😆  , the current date is highlighted, so it's easier to find. If you have trouble remembering the current date, you can add a Clock widget and display the date on it.

Just click back on > and find the current month again 😆

Uh... good idea. Thanks. :smile:


PackedArray casing style

The casing style of the methods in PackedArray are inconsistent. I would propose switching everything to camelCase instead of snake_case. This would probably cause a lot of other code to have to change though.

Will fix. As far as I know they're not used in many places

Fixed. Will be in next update


Hamap under IPS not working

As implemented in the  8b4da2c commit, IPS is breaking if Hamap is set as an application.

Fixed at4 commit 8b4da2c.


Figure out how to pull in dotfile configuration

Bonus points if I can make that configurable such that others can pull in their own environments and easily customize their setup. Maybe that should also be a separate container that is to be copied into the base image.

Fixed in #21


unable to update cli using homebrew

I tried to install the latest CLI from the docs: https://docs.microsoft.com/en-us/cli/azure/install-azure-cli-macos?view=azure-cli-latest. I'm pretty sure I installed using brew so I ran:
brew update && brew install azure-cli
it ran for a while, then this:
Error: An unexpected error occurred during the `brew link` step
The formula built, but is not symlinked into /usr/local
Permission denied @ dir_s_mkdir - /usr/local/Frameworks
Error: Permission denied @ dir_s_mkdir - /usr/local/Frameworks

Tried to do this manually:
~/src/vscode-docker$ brew link --overwrite python3
Linking /usr/local/Cellar/python3/3.6.4_2... Error: Permission denied @ dir_s_mkdir - /usr/local/Frameworks

So I tried running with sudo and get a big error:
~/src/vscode-docker$ sudo brew link --overwrite python3
Password:
Error: Running Homebrew as root is extremely dangerous and no longer supported.
As Homebrew does not drop privileges on installation you would be giving all
build scripts full access to your system.

If i run brew upgrade azure-cli i see:
Error: azure-cli 2.0.26 already installed
if i which az gives me /usr/local/bin/az

Please provide
CLI version (az --version) / OS version / Shell Type (e.g. bash, cmd.exe, Bash on Windows)

sorry.  Im on a Mac (10.13.2) using bash. after trying to run az upgrade a few different ways, now i have this:
~/src$ az -v
No module named 'pkg_resources'
Traceback (most recent call last):
File "/usr/local/Cellar/azure-cli/2.0.26/libexec/lib/python3.6/site-packages/knack/cli.py", line 187, in invoke
self.show_version()
File "/usr/local/Cellar/azure-cli/2.0.26/libexec/lib/python3.6/site-packages/azure/cli/core/init.py", line 79, in show_version
print(get_az_version_string())
File "/usr/local/Cellar/azure-cli/2.0.26/libexec/lib/python3.6/site-packages/azure/cli/core/util.py", line 60, in get_az_version_string
installed_dists = get_installed_cli_distributions()
File "/usr/local/Cellar/azure-cli/2.0.26/libexec/lib/python3.6/site-packages/azure/cli/core/util.py", line 51, in get_installed_cli_distributions
from pkg_resources import working_set
ModuleNotFoundError: No module named 'pkg_resources'

Are you in a Python virtual environment or have 'az' installed elsewhere on the machine?

i am not in a python virtual environment as far as i know and i may have had az installed elsewhere. i can't remember how i originally installed it. i think there was a .dmg or .zip for mac as well, but that doesn't seem to exist anymore.

I have very similar issues. Wondering if it has anything to do with running Python 3.6.3 using the Anaconda distribution?
$ python --version
Python 3.6.3 :: Anaconda, Inc.

Same here, do you have any news?

I solve my case, hope solve yours:
1.- Uninstall Azure CLI (could have an error, it is ok)
brew uninstall azure-cli
2.- Update just brew
brew update
3.- Upgrade brew
brew upgrade
4.- Clean up brew
brew cleanup
5.- Reinstall just the Azure CLI
brew install azure-cli
6.- Check the CLI
az help
Hope it works for you!

@grimaldou 's suggestion worked for me after I made sure that Python 3.6.x was properly installed. I used Anaconda to install and activate it in an environment.

It looks like I had originally installed the az CLI using the install script (https://docs.microsoft.com/en-us/cli/azure/install-azure-cli-linux?view=azure-cli-latest). I cleaned that up using the instructions provided with that page, then installed using homebrew and it works.  Generally.  When I run az --version I get this:
~/src$ az --version
No module named 'pkg_resources'
Traceback (most recent call last):
  File "/usr/local/Cellar/azure-cli/2.0.28/libexec/lib/python3.6/site-packages/knack/cli.py", line 187, in invoke
    self.show_version()
  File "/usr/local/Cellar/azure-cli/2.0.28/libexec/lib/python3.6/site-packages/azure/cli/core/__init__.py", line 79, in show_version
    print(get_az_version_string())
  File "/usr/local/Cellar/azure-cli/2.0.28/libexec/lib/python3.6/site-packages/azure/cli/core/util.py", line 60, in get_az_version_string
    installed_dists = get_installed_cli_distributions()
  File "/usr/local/Cellar/azure-cli/2.0.28/libexec/lib/python3.6/site-packages/azure/cli/core/util.py", line 51, in get_installed_cli_distributions
    from pkg_resources import working_set
ModuleNotFoundError: No module named 'pkg_resources'

Hi Chris,
This happens when your Python environment is not set up correctly. I manage Python versions and environments for different projects with Anaconda. When I run az —verion under my standard environment I get the same error as reported below. However, the command works when I change to me Python 3.6.2 environment under which azure-cli was installed. Here is an example of the output it gives me:
peter@Peters-MacBook-Pro >  source activate py3.6.2
peter@Peters-MacBook-Pro > az --version
azure-cli (2.0.27)
acr (2.0.21)
acs (2.0.26)
advisor (0.1.2)
appservice (0.1.26)
backup (1.0.6)
batch (3.1.10)
batchai (0.1.5)
billing (0.1.7)
cdn (0.0.13)
cloud (2.0.12)
cognitiveservices (0.1.10)
command-modules-nspkg (2.0.1)
configure (2.0.14)
consumption (0.2.1)
container (0.1.18)
core (2.0.27)
cosmosdb (0.1.19)
dla (0.0.18)
dls (0.0.19)
eventgrid (0.1.10)
extension (0.0.9)
feedback (2.1.0)
find (0.2.8)
interactive (0.3.16)
iot (0.1.17)
keyvault (2.0.18)
lab (0.0.17)
monitor (0.1.2)
network (2.0.23)
nspkg (3.0.1)
profile (2.0.19)
rdbms (0.0.12)
redis (0.2.11)
reservations (0.1.1)
resource (2.0.23)
role (2.0.19)
servicefabric (0.0.10)
sql (2.0.21)
storage (2.0.25)
vm (2.0.26)
Python location '/Users/peter/Anaconda2/envs/py3.6.2/bin/python3.6'
Extensions directory '/Users/peter/.azure/cliextensions'
Python (Darwin) 3.6.2 |Anaconda custom (x86_64)| (default, Jul 20 2017, 13:14:59)
[GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.57)]
Legal docs and information: aka.ms/AzureCliLegal
Hope this helps.
Kind regards,
--
Peter Hayward
Data Scientist · Praelexis
Capital Place F · 15 - 21 Neutron Avenue · Technopark · Stellenbosch · 7600
Tel: +27 (0) 72 354 5228
Email<EMAIL_ADDRESS><EMAIL_ADDRESS>
On 02 Mar 2018, at 03:38, Chris Dias<EMAIL_ADDRESS>wrote:
It looks like I had originally installed the az CLI using the install script (https://docs.microsoft.com/en-us/cli/azure/install-azure-cli-linux?view=azure-cli-latest https://docs.microsoft.com/en-us/cli/azure/install-azure-cli-linux?view=azure-cli-latest). I cleaned that up using the instructions provided with that page, then installed using homebrew and it works. Generally. When I run az --version I get this:
~/src$ az --version
No module named 'pkg_resources'
Traceback (most recent call last):
File "/usr/local/Cellar/azure-cli/2.0.28/libexec/lib/python3.6/site-packages/knack/cli.py", line 187, in invoke
self.show_version()
File "/usr/local/Cellar/azure-cli/2.0.28/libexec/lib/python3.6/site-packages/azure/cli/core/init.py", line 79, in show_version
print(get_az_version_string())
File "/usr/local/Cellar/azure-cli/2.0.28/libexec/lib/python3.6/site-packages/azure/cli/core/util.py", line 60, in get_az_version_string
installed_dists = get_installed_cli_distributions()
File "/usr/local/Cellar/azure-cli/2.0.28/libexec/lib/python3.6/site-packages/azure/cli/core/util.py", line 51, in get_installed_cli_distributions
from pkg_resources import working_set
ModuleNotFoundError: No module named 'pkg_resources'
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/Azure/azure-cli/issues/5503#issuecomment-369791588, or mute the thread https://github.com/notifications/unsubscribe-auth/AA69groQZRj3k_bU18B4aaeFGZKE1Ej8ks5taKKqgaJpZM4R7-XP.

Update:
I was was given a tip that my python setuptools might have been deleted (see here). So, I ran:
curl https://bootstrap.pypa.io/ez_setup.py | python
but that failed with permission issues to /Library/Python. I ran again with sudo but that still failed.
After digging around the docs more, I installed wget with brew, which in turn notified my that my python was out of date (a bit weird).  So I ran:
brew upgrade python
And from there, everything started working.

What worked for me was going to this folder /usr/local/Cellar/python/3.6.4_3/Frameworks/Python.framework/Versions/3.6/lib
and creating and empty folder called "pkg_resources" and then run
az --version
After that all good, I started installing the azure-iot-developer-kit which was my main goal. Thanks for the tips on this page!

You could also trybrew doctor and see if that provides any hints.

I ran
brew reinstall python3
to fix this

The fix by @grimaldou worked after I followed the instructions here by chingNotCHing.

brew reinstall python3 fixed it for me, too.

works for me +1

Seeing this issue on macos:
$ az --version
azure-cli                         2.0.72 *
command-modules-nspkg               2.0.3
core                              2.0.72 *
nspkg                              3.0.4
telemetry                          1.0.3
Python location '/usr/local/Cellar/azure-cli/2.0.72_1/libexec/bin/python'
Extensions directory '/Users/****/.azure/cliextensions'
Python (Darwin) 3.7.4 (default, Sep  7 2019, 18:27:02)
[Clang 10.0.1 (clang-1<IP_ADDRESS>)]
Legal docs and information: aka.ms/AzureCliLegal
You have 2 updates available. Consider updating your CLI installation
$ brew update && brew upgrade azure-cli
Already up-to-date.
Error: azure-cli 2.0.72_1 already installed
MacOS Version: Mojave 10.14.6
Shell Type: bash
Not in a virtualenv


Namespace naming assertions

Enhancement description
It would really make sense to have the ability to enforce not only the actual class naming like this:
        return PHPat::rule()
            ->classes(Selector::extends(ApiTestCase::class))
            ->shouldBeNamed('/ApiTest$/', true);

But to apply rules for namespace:
        return PHPat::rule()
            ->classes(Selector::extends(ApiTestCase::class))
            ->shouldBeNamed('/\\\\Tests\\\\Api\\\\.+ApiTest$/', true);

In this example, phpat would check if api tests are placed in Tests\Api directory and named with ApiTest suffix.

To achieve this we would need to add the ability to combine assertions (#242) and a new assertion shouldBeInNamespace, being the first one the most challenging feature.

I wonder why couldn't we allow shouldBeNamed to work with full classname (including namespace) rather than class basename?
Currently shouldBeNamed applied to Foo\Bar class checks only Bar part (rather than Foo\Bar).
From my side, while I was trying to make it work, it has taken me quite a while until I understood that shouldBeNamed works only with the last part of the namespace.
Please, let me know your thoughts on this regard

TBH I have no hard feelings on this, but the classname selector works with FQCN so this could be an opportunity to standarize selector and assertion. There is a PR open but since this is a breaking change, it will need to be released with v0.11 (which I plan to finish by the end of the month)

Released with https://github.com/carlosas/phpat/releases/tag/0.11.0 🚀

Thank you @carlosas , it's a great deal what you are doing!
It's such a pleasure to use a tool like this! It truly allows us to enforce very specific architecture rules at the very deep code level.
Thus, I just want to say thank you for all the effort spent on this project!


patch hcsshim to work with go1.9

In go1.9, fi.IsDir() returns false if the directory is also a symlink.
(see https://github.com/golang/go/commit/1989921aef60c83e6f9127a8448fb5ede10e9acc)
This breaks copyFileWithMetadata as it will not pre-create the
destination dir, causing the SetFileBasicInfo call to fail
This fixes the problem by checking syscall.FILE_ATTRIBUTE_DIRECTORY
directly.

@sunjayBhatia I just merged https://github.com/Microsoft/hcsshim/pull/147 which prevents the errors caused when using the raw isDir from file attributes in the check at https://github.com/Microsoft/hcsshim/blob/37b447b34728eb60903866ab8f9b3131ac911da0/legacy.go#L494
Can you rebase on that change?

@darrenstahlmsft we have a story to do so and will let you know soon about validating those changes! thanks so much for this

FWIW I validated this PR using Docker and Containerd locally (based on master) with the proposed change on both Go1.8 and Go1.9 😄

@sunjayBhatia can you rebase this PR on master please?

ping @sunjayBhatia any news on this one? 😅

@darrenstahlmsft @thaJeztah rebased on master and updated this PR branch

@sunjayBhatia thanks, but can you also add the suggestion from https://github.com/Microsoft/hcsshim/pull/144#discussion_r141944524 back in? The fixes in master should prevent the issues you were seeing in https://github.com/Microsoft/hcsshim/pull/144#discussion_r142542338 from occurring now.

@darrenstahlmsft updated to to the same as isReparsePoint and it now for being a directory with syscall.FILE_ATTRIBUTE_DIRECTORY. copyFileWithMetadata is unchanged

Looks good. Thanks!

Thanks!


RFC: Helpers directory

Issue
I checked the module NimbleTemplate.Template and I think some functions do not belong to this module. We can extract these functions into the helper module and group them in the Helpers directory.

Solution
Introduce the helpers directory and we can place all helper functions there.

Who Benefits?
Developers
What's Next?

[ ] Create refactoring NimbleTemplate.Template PR

👍 Micky


Feat: login M2M with basic auth credentials

What this PR is for?
This PR adds the command to set up M2M basic auth credentials, together with the methods required to authenticate via M2M to the console.
The PR also includes some refactoring of the already existing files, to make the integration more smooth.

TODO: fix cylomatic complexity in CreateMockServer function (testutils.go)


[CAMEL-21362] camel k8s run cannot find pod on openshift

https://issues.apache.org/jira/browse/CAMEL-21362

So it seems it needs 2 labels now.

thanks for the review @squakez

Should this be removed in 4.x as well? It'd be a breaking change.

Should this be removed in 4.x as well? It'd be a breaking change.

yeah fine to remove in 4.8.x as its a brand new release and 4.8.0 is a bit buggy here

LGTM.
A little out of scope but I saw this comment in the code :
https://github.com/apache/camel/blob/f23f02531518c8a2b34a0b5d582a96e81fcd7c42/dsl/camel-jbang/camel-jbang-plugin-kubernetes/src/main/java/org/apache/camel/dsl/jbang/core/commands/kubernetes/KubernetesExport.java#L232-L237
Do you know if there is a lot of diff between jkube, quarkus and generated manifest for labels ?

Should this be removed in 4.x as well? It'd be a breaking change.

It is a valid concern. However, as this is a prototyping tool, I think we should not worry that much as we don't expect production workflows leveraging this directly.

I think the root cause of all of this is that when using OpenShift as a cluster-type we switch from Kubernetes Quarkus extension to the OpenShift Quarkus extension and unfortunately these two seem to behave differently.
The Quarkus Kubernetes extension properly merges the Kubernetes manifest coming from the Camel JBang plugin (in src/main/kubernetes) with its own generated Kubernetes manifest. The Quarkus OpenShift extension presumably is not doing the same merger so things like the INTEGRATION_LABEL may not get properly added to the final Kubernetes manifest.
Switching from INTEGRATION_LABEL to KUBERNETES_NAME_LABEL as in this PR fixes it because KUBERNETES_NAME_LABEL is what the Quarkus extension uses. I am fine with the fix in this PR and I also think that is does not break existing behavior since the users coming from 4.8.0 will not face breaking changes because of this as it is an internal detail in the manifest.
In general we need to analyze and find out why the Kubernetes manifest is not merged properly when using the Quarkus OpenShift extension. In 4.8.0 the focus was to support plain Kubernetes where all of this is working properly.

@christophd can you create a JIRA with your last comment so we wont forget

@davsclaus see https://issues.apache.org/jira/browse/CAMEL-21365

@tdiesler can you update the PR
modified:   dsl/camel-jbang/camel-jbang-plugin-k/src/test/java/org/apache/camel/dsl/jbang/core/commands/k/IntegrationExportTest.java


Add Monsterland Team Name

The team consisting of derShakes, derTendro and Gorg is called "Monsterland". I edited the file data.json accordingly.
I hope this is the right place, where teams are stored
Please tell me, if this change has to be made somewhere else :)

I can add additional team names if you need help

Great, thank you! Feel free to add more team names.


Add expiration tag to text note

Hi @thesimplekid, thanks for the PR! After merging #17, this branch has merge conflicts. I'll merge when this is fixed.

fixed


Support changing the backing field used by auto-accessors

Reopening https://github.com/tc39/proposal-decorators/issues/511 here as suggested by @pzuraq in this comment.
The README of the decorators proposal stats that the getter and setter defined by the auto-accessors "default to getting and setting a value on a private slot.", so why not allow the use of a different backing field?
The suggestion
Allow accessor to take the backing field name as parameter: accessor(fieldName) accessorName.
accessor(#x) x = 1; would be equivalent to accessor x = 1; except that with the former #x would be accessible syntactically in the class.
The following example would be valid:
class C {
  accessor(#x) x = 1;

  method() {
    this.#x = 456;
  }
}

The backing field can also be public for those who want to avoid private class fields:
class C {
  accessor(_x) x = 1;
}

The above would roughly desugar to:
class C {
  _x = 1;
  get x() {
    return this._x;
  }
  set x(val) {
    this._x = val;
  }
}

This would probably also solve #10 as being an alternative to the private getter and setter syntax.
Other alternative
An alternative that would more resemble C# would be (or similar):
class C {
  #x = 1;
  accessor x { get as #x; set as #x; }
}

PS: This is my first time contributing to discussions on TC39 proposals 😅

That seems like a nice addition, altho i don’t see the value in allowing public properties to be set here - if you want a public property then what’s the point of get/set functions?

While it may appear that the sole purpose of get/set functions is to provide public access to private properties, I assure you that this is not the case. Accessors have a broader functionality as they facilitate the abstraction of a class or object's internals, including private-by-convention properties, private language properties, and dynamic properties (such as computed properties).
Accessors have several common use cases, such as:

Read-only properties
Lazy-evaluated properties
Input validation when setting a property
Emitting events when the property value changes

These use cases are applicable to both private class fields and private-by-convention public class fields.
Private class fields are intentionally more restricted than public ones (for instance, they are incompatible with use cases requiring "protected" or "package" visibility). Therefore, in certain scenarios where private class fields cannot be utilized, a private-by-convention approach is more suitable.

Furthermore, allowing non-private names might simplify expanding auto-accessors to work on object literals, as the README states:

Under Consideration: We may consider expanding auto-accessors to work on object literals in the future, however the necessary private name semantics are currently not defined for object literals.

Absolutely, that's why I called it private-by-convention and it's how we used to do private properties be for private class fields.
But as I've mentioned before, some use cases cannot make use of private class fields as they are too restrictive. Until a better alternative exists, private-by-convention are the only option.
Aside: Since one of those restrictions is their incompatibility with proxies (https://github.com/tc39/proposal-class-fields/issues/106), might this be remedied in a future proposal or is it a non-starter?

I think it’s a nonstarter - it’s not just proxies, it’s anything that depends on the identity of a receiver. One simply can’t wrap something one doesn’t own and expect to be able to have identical semantics.

Thank you for the clarification 😄


[microNPU][ETHOSU] Fix CopyComputeReordering pass arguments

No arguments were passed to CopyComputeReordering pass and the same parameters were used for all targets. This fix takes arguments for CopyComputeReordering pass from Vela.
In networks tests, the amount of memory used for U65 has increased because now after CopyComputeReordering pass, the number of DMA commands executed in parallel has increased.
cc @neildhickey, @lhutton1, @ekalda, @leandron

Thanks @Aleksei-grovety!


Warn Dengue prone area

If there is a lot of incidents in a area, warn the people living there and submit the data to government agencies to take action.

Hi sarang-s Can I work on this issue?

Yeah sure.
On 27 Feb 2018 9:28 a.m., "Sahan Monaara"<EMAIL_ADDRESS>wrote:

Hi sarang-s Can I work on this issue?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/scorelab/dengue-stop/issues/67#issuecomment-368739697,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Agzohy1nrjbRIjgBSqrQmAcoqFTNdC06ks5tY31-gaJpZM4RdIDL
.


Dueling vs CPU.

Hi. Each time I start the duel against CPU. The game display a 'DRAW' result and ends the duel. What should I do?

I'm guessing it's because you're trying to start a duel without choosing a deck for you and the CPU ?

Actually, i did create a deck for both. But can I use all cards? Or are they limited?
Sent from Yahoo Mail on Android
On Sat, 5 Aug 2023 at 2:24, @.***> wrote:
I'm guessing it's because you're trying to start a duel without choosing a deck for you and the CPU ?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

That could be the problem. Did you try starting the duel with structure decks only ? (the json files in the StructureDeck folder) ?

That could be the problem. There's some options to enable the use of banned cards or bypass the 3 cards limit in Settings.json. Also did you try starting the duel with structure decks only to see if it works ? (the json files in the StructureDeck folder) ?

Yeah. I will try that. One last question, is it possible to add Online mode for this? Just for smaller communities who want to have specific format and duels.

https://github.com/pixeltris/YgoMaster/blob/master/Docs/PvP.md

Sounds like missing or empty decks. There are no deck limits using the duel starter UI. Starting with no deck selected or a deck with no cards will result in a draw.


Added some files which closes 4 issues

Please merge those
Hi there, I have contributed 4 files which closes 4 issues and deleted
helloworld .c and helloworld.py and printf.c because they may be
reported as spam.
Hope you will like my contribution and please merge pr.
closing #256 #254 #176 #193

Bro please merge 🥺

Please merge this @Astrodevil

I think you will

Put diamond pattern problems in pattern folder inside C++, and don't delete any file, even basic one

ok

sir I am in problem can't retrieve it

At least put your diamond pattern programs in mentioned folder

Yeah I will review and do

Please check

@Astrodevil Can you now merge

thanks bro


Add function to get associatred PRs for a commit

Added a function to query GitHub's GraphQL API for a commit's associated pull requests

Added @yolocs  and @drevell for Go readability (this repo should be setup for that)


Fix #6825 by reducing the changed files to those only related to the issue

#6825 fixed #3275 by @jersiovic, but it was prevented from merging as it changed too many files.
This PR, I branch it from master, only apply the commit 106ff07 and bd531cf from jersiovic in #6825 of which were key commits for fixing #3275 and there are any other changes.
PS: hope this PR does not offense your contributions @jersiovic as it reuse your works. If it does, I will close it.

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

@li0803 no problem,  thank you for submitting the PR

apply jersiovic 2) and 3) review suggestion


Audit Password Managers and Security Tools

We want to make sure everything we recommend is something we should be recommending.
Any Password Managers or Security Tools that aren't reputable should be removed.
I did a once over when I started contributing to the list, and we should do another pass.

@alichtman This is the right. Software security is very important.


Fix dns setup module outputs

Fix dns setup module outputs

Module outputs set as variables.

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


feat: support the Continuous Scanning capability

PR Type:
Enhancement

PR Description:
This PR introduces the Continuous Scanning feature in Kubescape, a tool for Kubernetes security. The main changes include:

Enabling Continuous Scanning in the Kubescape Operator Helm chart.
Providing detailed documentation on how to use the Continuous Scanning feature.
Adding a new ConfigMap for matching rules related to continuous scanning.
Modifying the operator deployment to include the new ConfigMap.
Updating the values.yaml file to include configurations for continuous scanning.

Once kubescape/storage#59 and kubescape/operator#174 are merged, we can use our proper Quay images.

PR Main Files Walkthrough:
 files:
charts/kubescape-operator/README.md: Added extensive documentation on the Continuous Scanning feature, including its installation, accessing results, and how it works.
charts/kubescape-operator/templates/configs/matchingRules-configmap.yaml: Introduced a new ConfigMap for matching rules related to continuous scanning.
charts/kubescape-operator/templates/operator/deployment.yaml: Updated the operator deployment to include the new ConfigMap for continuous scanning.
charts/kubescape-operator/values.yaml: Added new configurations for the continuous scanning feature, including the ConfigMap name and matching rules. Also updated the operator image repository and tag.

User Description:
Overview
This PR adds support for Continuous Scanning. It exposes new values
that control:

whether to enable Continuous Scanning
which resources to monitor.

I left some docs in the README before we merge kubescape/kubescape.io#25. But after we merge it, I will remove the docs from the README and provide the links to the new documentation.

I apologize, I re-requested review for the wrong PR :man_facepalming:


AWS Athena connector

For middling data AWS Athena is an excellent low cost warehouse/lakehouse that works with open table formats like iceberg, hudi and delta lake.
Would definitely get us to try quarry if Athena was supported!

Hi @alfredHerdwatch,
Appreciate the request! We're looking at rolling out connectors over time. AWS Athena isn't at the top of our list at the moment, but if you have the time, we'd love to talk to you about your use case on a call

Ily 🫶 __


Set query based on new parameters

This may be done in the resolve field of the search.type state, or in the onInit function of the component. The query function should take as parameters:

A function to convert query parameters to an $http query.
Map, reduce and/or filter functions to turn the response into something that provides data for ui-grid.

Query working with $http for type3 in v0.0.6


update templates to support e2e for kubernetes 1.28

Updated github action to run kubernetes 1.28 tests and also consider test result to merge the PR (via mergify)
depends-on #4056
closes #4052

/test ci/centos/k8s-e2e-external-storage/1.28

/test ci/centos/mini-e2e-helm/k8s-1.28

/test ci/centos/mini-e2e/k8s-1.28

@nixpanic as per official doc it's not reached eol yet https://kubernetes.io/releases/

@mergifyio queue

As the mergify configuration is changed, merging this one manually


Question about the GaussLegendre basis

Hello,
We're trying to understand the implementation of the GaussLegendre basis, and gradient, used on triangles when using L2_FECollection, in particular, in
void L2_TriangleElement::CalcShape
and
void L2_TriangleElement::CalcDShape
both in fe.cpp. Do you maybe have a reference to literature where this is explained in a bit more detail?
For example, when computing the gradient of a P1 function we're expecting a matrix with 1's and -1's, but instead we're getting other values.
We're also wondering what the difference is between using CalcLegendre(p, x, u); (which is commented) and CalcChebyshev(p, x, u); in static void CalcBasis in fe.hpp.
Thanks,
Sander

Hi Sander,
In 1D, the GaussLegendre basis is just an interpolatory basis in the Gaussian quadrature points. This is an example of an open basis in our terminology, where the endpoints are not included as degrees of freedom (which explains the slopes you are seeing).

An examples of a closed basis is GaussLobatto, which is an interpolatory basis in the Gauss-Lobatto quadrature points, which do include the endpoints of the interval and thus are appropriate for H1-type spaces.

Another example of a closed basis is the Bernstein positive basis, which is interpolatory only at the endpoints (the rest of the degrees of freedom don't correspond to function values).

For quads and hexes, the GaussLegendre and GaussLobatto bases are just Cartesian products of the 1D ones. Things are more involved for triangles and tets, but basically you start with the 1D dofs on the edges and extend in a triangular lattice on the faces and in the interior.
@v-dobrev can probably provide more details for this particular case if you are interested. He or @pgmaginot may also have more information about your last question.
Hope this helps,
Tzanio

Hello Tzanio,
Thanks for the explanation. The reason we were looking at this was because we were getting weird solutions from our code. We started to compare our MFEM matrices to those of another code we have and the matrices were different, so we figured this might be because of the different basis functions that were being used. We eventually found that we had to increase the order of the quadrature used in VectorDomainLFIntegrator and now everything works. Tamas posted this as a new question.
Sander

See #330.


RFC Split the repo based on the projects in the repo

Right now the huggingface_repo includes three projects;

huggingface_hub: which is the core library used by integration libraries and api-inference-community
api-inference-community which handes integration with some of the third party libraries
huggingface_widgets which is located under the js folder and hosts the code for the inference widgets

The three projects require different dev environments, have different development styles, and follow different release cycles.
This request for comment is for us to see if it would make sense to separate the repo into three different repositories.
cc @julien-c @LysandreJik @osanseviero @Narsil

no strong opinion on my side, for context we pushed to experiment with a single repo some time ago to see if it would gain "critical mass" on GitHub, but it's maybe not as important anymore
So I'm open to re-splitting.

After some discussions last week I think it makes sense to split. I think having clearer release cycles for api-inference-community would be beneficial, and not having a mixed bag of everything in a single repo.
@adrinjalali, js has many things: inference snippets, widgets, snippets of code for each library, the definition of the tasks tree, etc. There are two other directories: tasks and docs, which I would move with js. Soon huggingface_hub will have new proper docs, which would be in this repo. docs would be just documentation about product usage. This has the advantage that moon-landing will just directly depend on that repo instead of huggingface_hub and huggingface_widgets.

Sounds good to me @osanseviero . I think on top of the API docs we need some user guides as well, which would go in the docs/ folder, but I agree that the product specific docs can (or should) move and be where js goes.
In terms of how to execute this, I suggest:

[ ] creating two repositories, one for api-inference-community and one for js (not sure what we're gonna call this one)
[ ] mirror the existing content of this repo there
[ ] move issues related to those projects to those repos
[ ] stop accepting PRs which change these two projects in this repo and direct people to those other repos
[ ] move existing PRs to those repos, or merge some of the existing ones here, and keep those two repos in sync with this one while this is happening
[ ] delete those projects from this repo

WDYT?

I am fine either way (single or split) !
We need to not forget moving all github actions related and adapt them in consequence too.

We also need to change moon-landing to access the new repo instead of this one.

I personally have no opinion on this suggestion, as I don't not routinely work with these projects but thought I would share my experience.
In my experince, lots of individual repos scales poorly as an org grows. Having fewer, bigger repos, increases the likelihood that the repo will be well maintained (as it is less liklely to get abandoned without intention, and geenral has more eyes on it), offers an easier path for code sharing (local files/ local symlinks are far easier to maintain and utilise than cross-repository ones), makes enforcing code and quality standards easier and, in particular, makes sharing CI easier.
I don't think there is any inherent problems with multi-language mono-repos, whether custom tooling is used to support that or not.
I also think there are better mechanisms for importing dependencies than relying on the entire repo. Package repositories, both public and private, exist to address that problem.

As everyone involved in the thread seems to react positively to the split, we will now go ahead and split the repository in three parts with @adrinjalali.
We're currently trying the following:

Keep huggingface_hub as the source of truth with all commits and files. At the end of the process, when we have verified everything works correctly as expected, we will remove the files of the two other repositories in a single commit.
Create a new repository huggingface/api-inference-community.

That repository is set at the first commit of the huggingface_hub repository (https://github.com/huggingface/huggingface_hub/commit/1884eff38b8a2a592f58ab521d49253130222650).
We then cherry-pick all commits that touched to the api-inference-community folder, and apply those commits only.
We remove the files that were included in commits that are not related to the api-inference-community.
We move the contents of the folder to the root of the repository.

We do the same with the new repository huggingface/<name_to_be_found_for_the_js_folder>:
We complete the checklist shared by Adrin here: https://github.com/huggingface/huggingface_hub/issues/744#issuecomment-1060693866

@Narsil could you please have a look at https://github.com/huggingface/api-inference-community and check if things are okay? I have a fork of the old version under my account in case we end up needing it.

I think I made sure the .github and api-inference-community are in sync here and in https://github.com/huggingface/api-inference-community
One thing I think is missing is the USER_API_TOKEN secret, which I'm not sure how to generate for the new repo.

The js, tasks and docs folders, alongside all commits that touched to these files, have been moved to the public repository https://github.com/huggingface/hub-docs.
Similarly, there is a secret missing for the js tests which is the NETLIFY_AUTH_TOKEN.

@mishig25 who's "owning" the widgets or @beurkinger might be able to add a new netlify token (ping me if you can't find one)

All action items on this issue seem to be completed.


ROADMAP: Observability included

Grafana Dashboards and configuration as part of the Operator start up

I started some work on the Dashboards here

Do we have more outstanding features for this Roadmap item?

closing the Roadmap GH issue since it's completed


Rahul hybrid dev setup

Coverage remained the same at 94.977% when pulling a98e213336a8ebbe57ab5cfdded13e96987919cd on rahul-hybrid-dev-setup into 6601e50a282f0eaae2ea754ec2092db768b7e259 on main.

Thoughts on the relationship between this and existing developer dockerfiles?
a. Thoughts on using this to replace them?
You should be able to revert package-lock.json -- only need to update it if making changes to one of the package.json files.

I think the Dockerfile.app and Dockerfile.server could be useful in some future docker world, but this hybrid approach was the most painless way of getting up and running for me. I wouldn't be opposed to keeping them around for the future, or deleting them to reduce clutter


Use Go bugfix version in go.mod directives

What does this PR do?

Update all go.mod files to use the bugfix Go version (1.21.7) instead of the minor version (1.21).
Motivation

It is preventing importing dependencies with a bugfix version set (ie. we can't import a dependency using 1.21.0 for example, this is forcing us to add the bugfix)
Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Should we update the docker files and the other places we reference 1.21?

/merge

I think this is failing because https://github.com/DataDog/datadog-lambda-extension/blob/23357637625a986f53bdc218c43c9c52656156d5/scripts/Dockerfile.alpine.build#L10 is still using Go 1.20, which cannot parse go 1.21.7 from the go.mod:
go.mod:3: invalid go version '1.21.7': must match format 1.23

Thanks @brycekahle I believe you are right, I opened a PR in that repo to bump the Go version 👍

/merge


add wallpaper script for GrapheneOS

first public version

first public version
current tested version:
ersion: ImageMagick 6.9.10-23 Q16 x86_64 20190101

in case error:
convert-im6.q16: attempt to perform an operation not allowed by the security policy `HTTPS' @ error/delegate.c/InvokeDelegate/1726.
edit /etc/imagemagick-6/policy.xml
change

to


crc16 kermit mask issue ?

in the kermit crc computation, a 0xFFFF mask is used, but when checking with the C lib at
https://github.com/lammertb/libcrc/blob/master/src/crckrmit.c
in the same funciton, the mask used is 0x00FF
which one is correct ?

The latter seems to be more correct in this case, since we are dealing with a CRC16 hash. 0xFFFF only makes sense when CRC32 hashes are being dealt with.

@alexgorbatchev, you can go ahead and close this issue as there never was an issue to talk about here in the first place.


How to add a new property to vue (object) data?

My data goes below
 data: {
                contacts: {
                    "1": {
                        isSelected: false,
                        UID:"1",
                        cardType: 0
                    },
                    "2": {
                        isSelected: false,
                        UID:"2",
                        cardType: 0
                    },
                    "3": {
                        isSelected: false,
                        UID:"3",
                        cardType: 0
                     },
            }
...

I could use this method to add new contact, but it got a compatibility problem, so I wonder are there some other ways to add new property to object, or I'd better change to use array instead of  object.
this.contacts = Object.assign({}, this.contacts, newObj);
Thanks a lot.

Read the docs: Vue.set

Thanks, using the set method, and It's OK now.
this.$set('contacts[' + newPsgId + ']', newObj)
Vue.set(this.contacts[newPsgId], 'name', this.editPsgName);

The previous solution does not work for me (Vue ^ 3.0.0)
Do it myself. Hope this helps someone.
this.$set(this.contacts, newPsgId, newObj)

this.$set()
is not long a function in vue 3

You don't need it in Vue 3, only in Vue 2.


Java: Fix range analysis bug where int was assumed.

Addition or subtraction of known strictly positive or negative expression accidentally assumed the expression to be of integral type and wrongly concluded x >= 1 from x > 0 and x <= -1 from x < 0.
This fixes https://github.com/Semmle/ql/issues/2335

Could you please submit a release note for this PR and also the other recent changes (#2304, #2305).

This PR just made the 1.23 cut-off, so the change note for all three PRs should be targeted at 1.23.

https://github.com/Semmle/ql/pull/2373


Said hello to myself

hello!

Hi, I assume this was just a "test" pull request? I will close the pull request.
Thanks
Stephanie