Add NuGet/Feedz.io publish support

if not tagged build publish to feedz.io (needs registration by you first), otherwise push to nuget
repository needs secrets FEEDZ_NUGET_API_KEY and PUBLIC_NUGET_API_KEY
only run master worfklow on ubuntu-latest so no multiple publish attempts, could be split if different runner tests needed
generate running preview number for regular builds, prefix comes from VersionPrefix in shared Directory.Build.props (manually incremented)
if tag version is present, overrides whole version string
upgraded Test262Harness, made 1.0.0 release (no semantic versioning promised though)

The end of happy direct pushing to master, huh? :D
Looks awesome BTW! Just a few questions:

Will this publish both the Acornima and Acornima.Extras packages? (I decided to extract the non-essential parts into a separate package to make the core package lighter.)
While we're at it, could you maybe enable source link and determistic build as well before we start to release packages? (The latter can be tricky though. In principle, you need to set the ContinuousIntegrationBuild MSBuild property and that's it. However, as far as I can remember, it does matter at what stage it is passed to MSBuild. For example, if there's a dotnet build, then later a dotnet pack, it won't work if you pass it to dotnet pack because that won't trigger a rebuild. In another project, I ended up with something like this).

Oh, and one more:

if not tagged build publish to feedz.io (needs registration by you first)

I can see here that you created some workspace for acornima at feedz.io. I registered with my GH account. But how can I manage the secrets of this workspace?

I think it will be easier to refer to the current build log here, I'm also sanity checking my answers...
https://github.com/adams85/acornima/actions/runs/7940588505/job/21682044595?pr=4

Will this publish both the Acornima and Acornima.Extras packages? (I decided to extract the non-essential parts into a separate package to keep the core package as light as possible.)

Seems both Extras and SourceGenerators are packed, so they will be also published. Maybe source generators should have <IsPackable>false</IsPackable>? This can be fine tuned later too as not publishing to NuGet yet.
> Pack
  08:54:02 [INF] > /usr/bin/dotnet pack /home/runner/work/acornima/acornima/Acornima.sln --configuration Release --no-build --output /home/runner/work/acornima/acornima/artifacts/packages --version-suffix preview-20240217-0852
  08:54:03 [DBG] MSBuild version 17.8.3+195e7f5a3 for .NET
  08:54:04 [DBG]   The package Acornima.SourceGenerators.0.1.0-preview-20240217-0852 is missing a readme. Go to https://aka.ms/nuget/authoring-best-practices/readme to learn why package readmes are important.
  08:54:04 [DBG]   Successfully created package '/home/runner/work/acornima/acornima/artifacts/packages/Acornima.SourceGenerators.0.1.0-preview-20240217-0852.nupkg'.
  08:54:04 [DBG]   The package Acornima.Extras.0.1.0-preview-20240217-0852 is missing a readme. Go to https://aka.ms/nuget/authoring-best-practices/readme to learn why package readmes are important.
  08:54:04 [DBG]   Successfully created package '/home/runner/work/acornima/acornima/artifacts/packages/Acornima.Extras.0.1.0-preview-20240217-0852.nupkg'.
  08:54:04 [DBG]   The package Acornima.0.1.0-preview-20240217-0852 is missing a readme. Go to https://aka.ms/nuget/authoring-best-practices/readme to learn why package readmes are important.
  08:54:04 [DBG]   Successfully created package '/home/runner/work/acornima/acornima/artifacts/packages/Acornima.0.1.0-preview-20240217-0852.nupkg'.

While we're at it, could you maybe enable source link and determistic build as well before we start to release packages? (The latter can be tricky though. In principle, you need to set the ContinuousIntegrationBuild MSBuild property and that's it. However, as far as I can remember, it does matter at what stage it is passed to MSBuild. For example, if there's a dotnet build, then later a dotnet pack, it won't work if you pass it to dotnet pack because that won't trigger a rebuild. In another project, I ended up with something like this).

Well this is the cool thing about NUKE, it has all these smarts built in when we use ICompile interfaces defaults interface methods...
https://github.com/nuke-build/nuke/blob/59bdf80fcbe9b11f9e443a701d455b5aaa58c532/source/Nuke.Components/ICompile.cs#L45-L51
As we can see in build log:
> Compile
  08:52:17 [INF] > /usr/bin/dotnet build /home/runner/work/acornima/acornima/Acornima.sln --configuration Release --no-restore --version-suffix preview-20240217-0852 /property:ContinuousIntegrationBuild=True

I can see here that you created some workspace for acornima at feedz.io. I registered with my GH account. But how can I manage the secrets of this workspace?

I haven't setup nothing yet, I'm hoping that you will register (and can also update the final feed URL into this PR if not what I suspected).
This is is what I have registered for Quartz.NET

And I have this kind of configuration on GitHub side (note that I have slightly different setup and different feedz API key):

The build for this repo expects to have these configured in this repo's secrets: FEEDZ_NUGET_API_KEY and PUBLIC_NUGET_API_KEY . Why feedz? MyGet seems to be quite badly handled and was down for many days without company giving any statement, some lost their packages too AFAIK. Doesn't matter too much as preview but.. anyway.

I'll push a tweak to ensure source packages are part of packaging too..

Pushed some tweaks to improve package metadata, excluding source generator project from packaging and now also snupkg should be generated, adding Microsoft.SourceLink.GitHub package reference to get Git repo and commit info as part of package.
The time to get some shuteye at this point, happy to answer more questions as they rise.

Well this is the cool thing about NUKE, it has all these smarts built in when we use ICompile interfaces defaults interface methods...

Wow, I like NUKE more and more! Will need to spend some time though to get familiar with it. I'd have hardly figured it out that it uses DIMs to provide defaults... :D

I haven't setup nothing yet, I'm hoping that you will register (and can also update the final feed URL into this PR if not what I suspected).

Interestingly, https://f.feedz.io/acornima/acornima/nuget/index.json returned 200 OK with some valid-looking content. Got confused because of that.
Anyway, I created an org named "acornima" and a repo named the same, so the URL you set in the PR should be actually valid now. Also added the FEEDZ_NUGET_API_KEY secret on GH.

MyGet seems to be quite badly handled and was down for many days without company giving any statement, some lost their packages too AFAIK. Doesn't matter too much as preview but.. anyway.

Yeah, I haven't had a very good experience with MyGet either. For now, I'm totally happy with feedz, then we'll see how it pans out.

I'll push a tweak to ensure source packages are part of packaging too..

Pushed some tweaks to improve package metadata, excluding source generator project from packaging and now also snupkg should be generated, adding Microsoft.SourceLink.GitHub package reference to get Git repo and commit info as part of package.

Big thanks! 🙏  I'll take a closer look tomorrow, but I think we're all set now.

The first preview releases started to appear on feedz.io! 🚀
I checked, both source link and deterministic build work just fine. Many thanks again! 🥇


Serialize isomorphic graphs to identical Turtle

I have a project where I export diagrams to RDF. How can I influence the order of statements when I serialize a sophia graph to turtle?

@GordianDziwis thanks for your interest in Sophia.
Short answer is: you can not guarantee that the Turtle you produce is 100% identical to the source turtle.
Longer answer
What you can do to preserve order

the result of parsers are triple sources, which are ordered ;
you need to store the triples it in a structure that preserves that order, which is not the case of all Graph implementations (because inherently RDF graphs are sets, hence not order);
an example of Graph implementation preserving order is Vec<T> where T: Triple;
serializers have a serialize_triples method which expects a triple source, and is more likely (see below) to preserve that order in the serialization.

Limitations
The contract of [Serializer::triple_source] does not guarantee, in general, that the order of the triples in the source will be preserved, in the serialization.

the n-triples serializer will preserve order, because that's the simplest thing to do ;
the turtle serializer will not preserve order when the pretty option is on, because it prioritizes conciseness and, well, prettyness;
the turtle serializer without the pretty option will, currently, preserve order, but I can't guarantee that future implementation will do (see rationale below).

More generally, there are many issues, beyond triple order, that make it practically impossible to preserve the Turtle representation between parsing and serializing. Take, in particular, prefix declaration:

currently, Sophia does not provide a mean to retrieve the prefix declarations of a given Turtle source (although this is planned for the near future (see #45);
even when it does, it will not account for prefix overriding, as in the following example:

@prefix : <https://example.org/1/>.
:s :p :o.
@prefix : <https://example.org/2/>.
:s :p :o.

and the Sophia turtle serializer will never generate something like that.
Another issue would be heterogenity with "prettiness". Consider the following:
@prefix: <https://example.org/>
:s :p1 [ :a :b ].
:s :p2 _:b.
_:b :c :d.

This turtle is a mix of pretty and non-pretty. There is no way to serialize it back as is with Sophia.

Thank you for your detailed answer!
I do not care so much about the order of the triples or that TurtleIn == TurtleOut for TurtleIn => Graph => TurtleOut, but that the same graph always results in the same Turtle document.
The first use case is version control, I build a graph programmatically and have the serialized graph in git.
And as you said a graph is a set, but the triple source for a serializer is ordered and the order can influence the serialization.
For me, it would be enough if the Turtle serializer with pretty would produce the same Turtle for the same ordered triples from a triple source (is this already the case?). For any order would be even nicer.

Thank you for your detailed answer!
The first use case is version control, I build a graph programmatically and have the serialized graph in git.

got it

And as you said a graph is a set, but the triple source for a serializer is ordered and the order can influence the serialization.

indeed

For me, it would be enough if the Turtle serializer with pretty would produce the same Turtle for the same ordered triples from a triple source (is this already the case?).

I don't know, off the top of my head, if that's already the case, but even if it is currently, I would not rely on it, because I would not consider it to be a design goal of the Turtle serializer.
What you want is a canonical representation of the RDF graph. The good news is that there is a brand new standard for that (https://www.w3.org/TR/rdf-canon/) and that it is implemented in Sophia (https://docs.rs/sophia_c14n/latest/sophia_c14n/rdfc10/index.html). The no-so-good news is that this canonical representation is based on N-Quads (N-Triples if you have a single graph), so it is much more verbose than "pretty" Turtle. But note that N-Triples is a subset of Turtle, so you can still feed it your your Turtle parser and it will work.

Yeah this is what I want, thanks!


Add Netlify

Hej, I would like to add Netlify to the list.
See https://www.netlify.com/open-source/#mooseheads for details about the Open Source activities.
In my experience they don’t want any type of approval and are super flexible. I contacted them because we wanted to move http://yeoman.io/ from GitHub pages to Netlify but we need the »team feature« which isn’t for free by default for Open Source projects. I explained why we need it, and they enabled it for free 💖
Cheers, Michael

Thank you for taking the time to work on a PR for Awesome-Open-Source-Supporters!
To ensure your PR is dealt with swiftly please check the following:

[x] Your submissions are formatted according to the guidelines: [Company Name](link) `tag` - description
[x] Your additions are ordered alphabetically.
[x] Your additions are commercial software that offer their services for free to Open Source projects.
[x] Your additions contain any relevant tags: requires-approval
[x] You have searched the repository for any relevant issues or PRs.
[x] Any category you are creating has the minimum requirement of 2 items.

Hey @mischah, thanks for the contribution! I know they don't technically require an approval, but would you go ahead and add a requires-approval tag to Netlify anyway? It looks like you still have to contact them for any additional (non-freemium) benefits, as opposed to other products that simply offer additional "open source" benefits to any public GitHub repository.

Hej @zachflower, I’ve just added the requires-approval tag.
Let my know if you want me to squash the commits.

No, this is great, thanks @mischah!


Remove checks for legacy .yaml and .json config files.

Signed-off-by: Marc Handalian<EMAIL_ADDRESS>Description
Removes checks for opensearch.yaml/json config files that don't exist.  This was updated from their legacy names to opensearch but does not make sense with opensearch 1.x
Issues Resolved
#358
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[x] 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


Give Xray a nifty icon (and set it for linux)

Includes SVG and PNG icons.
The icon is set during the electron window creation.

As was stated in https://github.com/atom/xray/issues/122#issuecomment-418284651, unfortunately GitHub can't accept community proposals for the icon for legal reasons.

Thanks for your interest @coler706!


Shorter enum names everywhere

Closes #458
Takes the common prefix logic from #881 and applies it library-wide.
This pull request depends on #945

Rebased and ready to go.

In a future PR we should look to move the new members to the top of the declaration, this will result in .ToString and similar reflection-using functions to likely pick up the new names.


should run location sync with specific vagrant sub commands only to i…

connect #531

I updated the PR.


Return all result series when querying multiple selects

[x] Rebased/mergable
[x] Tests pass
[x] Sign CLA (if not already signed)

It is possible to pass this query to InfluxDB::Client#query:
SELECT * FROM foo; SELECT * FROM bar

InfluxDB actually delivers multiple result series, but the Rubygem discards all but the first series. This commit fixes this behaviour and returns/yields all result series.
Additionally fixes some links in the Readme and instructs Travis to test against Ruby 2.3.

N.B. This also fixed spec/influxdb/worker_spec.rb:13 which was broken for me, but not on Travis...

If that helps: I have signed the CLA found in the InfluxDB repository.

Thanks @dmke!


Request for a test case to check litmus manifests

Request to add a new test case to check the litmus manifests and add it in circleci
k8s-env: Minikube or KIND
Repo- https://github.com/litmuschaos/pages

This is a duplicate of https://github.com/litmuschaos/litmus/issues/213


Multiple output formatting

Currently batten output format is human readable text with some nice green and red coloring.
We would like to add an option for machine readable formats, like JSON, which can be used for integrations with server spec or other continuous integration systems.
The output format type should be specified in the batten check command line parameters.
If missing, the default human readable output format should be used.

@jerbia I am happy to help with this - I made a start on a JSON machine readable experiment here (https://github.com/petersellars/batten) as part of #dockerhackday. I am new to Go, so learning as I go to some extent so would appreciate any code review/feedback.
My initial thought was to create a JSON representation and add a '--machine-readable' flag to generate this either as a file or instead of the output currently generated.
Happy to discuss - will work on the JSON representation and let you know how I go.

This would be awesome @petersellars!
Maybe instead of --machine-readable, you could do a flag like:
 --output-format=[text|json|...]

This way you could supply different report formats (like html or yaml or whatever) in the future.

Hi @petersellars! Welcome on board!
I'll be happy to review your code and provide feedback. You can submit a pull request when you are done and we can go over your changes.
As for the parameter name - I agree with @jandre, using "--output-format" will allow
additional formats in the future.
Thanks for contributing!
Amir

Thanks @jandre  and @jerbia - that flag makes sense to me. Had considered yaml as well as json when starting to look at this. I shall continue with the initial json implementation and then submit for review - expect plenty of feedback as new to Go - still learning the Go idioms.


completion/hover: don't override handler globally

buf_request can take a callback, so let's use that :D
(Let me know if I'm missing something)

I think I missed out a lot of things happening in the nightly neovim:( After reading through the docs this should be the way to go. Thanks for the fix!

I think I missed out a lot of things happening in the nightly neovim:( After reading through the docs this should be the way to go. Thanks for the fix!


Is there an more complete demo of babel-plugin-dual-import?

I can not find it

All there is, is at the bottom of the article. You need to be using extract CSS chunks webpack plugin. That's probably the missing piece you're not privy to. Check that repo. It's also linked from the bottom of the article.

l get it . It seems necessary to correspond to the latest version of the extract CSS chunks webpack plugin and other packages.


OpenSSL.SSL.Error

Summary (include Python version)
I am using Anaconda 2019.07 with python3.7 on windows 10 with intelliJ.
When I try to fetch data, I got error like below.
OpenSSL.SSL.Error: [('SSL routines', 'tls_process_server_certificate', 'certificate verify failed')]
If you can adding verify=False option on request, it would be great.
response = self.session.get(url=url, params=params, verify=False)
https://github.com/addisonlynch/iexfinance/blob/6edfde16f70e6a0ae9691dc2279ed5327c02971e/iexfinance/base.py#L159
Date/time of issue
2019-09-11
Expected behavior
Fetch the data
Actual behavior
Occurred Error.

It seems like your client was not able to verify the server's certificate. I would make sure that your SSL CA is up to date, which should resolve the issue.


Added hub pr fish completions and wrapped git completions

Redefined __fish_hub_using_command to support multiple commands (such as hub pr list)
Added hub pr list and hub pr checkout along with their options

Thank you; this looks great! ✨


chore(*): Bump Spin dependency to v2.4.0

This commit bumps the Spin dependency to v2.4.0, and addresses the changes in
the trigger trait.
Signed-off-by: Radu Matei<EMAIL_ADDRESS>

Only kept the version bumps in this PR. Thanks!


Appstudio update mvp-test-component

Pipelines as Code configuration proposal

Pipelines as Code CI/mvp-test-component-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
19 seconds
clone-repository

✅ Succeeded
1 minute
build-container

✅ Succeeded
55 seconds
clamav-scan

✅ Succeeded
12 seconds
sanity-inspect-image

✅ Succeeded
10 seconds
deprecated-base-image-check

✅ Succeeded
19 seconds
clair-scan

✅ Succeeded
13 seconds
sbom-json-check

✅ Succeeded
5 seconds
sanity-label-check

✅ Succeeded
5 seconds
sanity-optional-label-check

✅ Succeeded
6 seconds
show-summary


Support increment PATCH version (e.g. 'Z' in x.y.Z) of semantic version

I've got a project that works with semantic versions like so:

The build number is set to DEVELOPMENT because I'm setting it to the count of git commits, as described here: http://stackoverflow.com/a/24750392/590767. So we can expect CFBundleVersion to look like 2532 or something when you actually do an Xcode build.
When I do a release with fastlane, more often than not, I intend only to increment the PATCH number (e.g. 0.7.0 -> 0.7.1). It'd be great if fastlane could automate that!

Why should fastlane change your app version? Not sure I understand the use case. Maybe you just want the build number to be updated? https://github.com/KrauseFx/fastlane/blob/master/Actions.md#increment_build_number

Hi @KrauseFx
I was looking for something like this issue.
Usually, I work with gulp project and I really like how I can update the version number of my project with gulp (i.e. gulp-release-task )
It would be nice to have an equivalent in fastlane.

+1 e.g. would be nice for a "bump" lane for bumping version numbers in a similar way to what is achievable in js projects via a gulp file

Thanks, this is now implemented :rocket:


[Docs] Add Cloudcraft to Showcase

Cloudcraft is a web service for creating AWS diagrams, used by tens of thousands of developers around the world. The interface is 100% Material-UI (see screenshot below).
I believe it is the largest MUI app I've seen to date, would be cool if you'd consider adding it to the Showcase page. Thanks!

Wow, very cool! Thanks much @tjunnone!

@newoga Thank you for the fantastic work on Material-UI

Wow, awesome :sunglasses: Thanks a lot. :+1: :+1:
@oliviertassinari Take a look and merge :grin:

Nice! Reminds me though we need to remove the "IBM" example (or change the logo) before releasing 0.14.3.

@tjunnone Thanks!

Nice! Reminds me though we need to remove the "IBM" example (or change the logo) before releasing 0.14.3.

I would say, let's remove it :grin:.


Unable to compile on Overleaf.

Description

It just does not compile with any option on Overleaf.
Minimal Working Example

Even just the example template in the source.
Expected behavior:

To compile, possibly with no error.
Actual behavior:

Does not compile, at all.
Additional Information

I suspect the problem is that lately Overleaf has reduced the compiling time for the free accounts. I have experience the very same problem with other templates that before was possible to use in Overleaf.

Indeed, unfortunately the problem seems to be compilation time. If you can, I would suggest using another editor such as TeXworks, TeXstudio, VScode, neovim, or emacs---they all have good support for LaTeX, and you could use GitHub as a "cloud" for collaborating with other people. I am planning to eventually rewrite kaobook from scratch making use of KOMA-script features that I didn't understand back then, so this should de-bloat the package and speed up the compilation.
Another option is to self-host an Overleaf instance; there are some tutorials online, but it's not for everybody. I will also look into hosting myself (on my raspberry pi or VPS) and see if I can offer the service for kaobook users (hopefully this doesn't violate any licences, but I am not sure).


JWT token security concerns

From what i see here, the JWT token is stored in the localStorage.
According to this article it should be stored in the sessionStorage instead to reduce the risk of an XSS attack by avoiding to store the token on the client persistently. As described on the Persisting sessions section of the article, it would break the functionality of persisting a session when relaunching the browser.
There is also a mention about a fingerprint added to the token to mitigate the risk of token side-jacking. Is it implemented in hasura-auth or is there any plan to support it ?
The sample project from hasura that implement thoses recommendations can be found here. You can find the code generating the fingerprint cookie for the user here and the fingerprint check for the refreshToken here

The risk of XSS is very small in modern js frameworks like React, Vue, Svelte, etc. Also, if you have XSS vulnerabilities in your app I don't see how sessionStorage would save you?
If you're concerned about where to persistently store you can always overload our setters and getters and store the refresh token as you prefer:
https://github.com/nhost/nhost/blob/main/packages/nhost-js/src/core/nhost-client.ts#L37-L40
Maybe @plmercereau could provide an example of how to do that?

Hello Sébastien,
First of all, a clarification: the Nhost SDK does not store the JWT but the refresh token in localStorage. We don't store JWTs anywhere else than in memory.
When a user loads a page, it looks for a refresh token in localStorage. This refresh token is sent to the backend (hasura-auth), that updates its expiration date, generates an access token (JWT) and returns it to the client.
You cannot use this refresh token to authenticate any request sent to Hasura. If it has somehow been exposed, it can be invalidated in the backend so it won't be possible to generate any access token (JWT) from it.
We could implement a refresh token fingerprint mechanism, but that being said, we've made the choice to allow users to be able to re-open their session after closing the browser, and there is no other means to achieve that than persisting data in localStorage or in a cookie.
Anyhow, you can store the refresh token in sessionStorage:
const nhost = new NhostClient({
  backendUrl: 'myapp.nhost.app',
  clientStorageType: 'custom',
  clientStorage: {
    getItem: key => sessionStorage.getItem(key) ?? null,
    setItem: sessionStorage.setItem,
    removeItem: sessionStorage.removeItem,
  },
})

"The Nhost SDK does not store the JWT but the refresh token in localStorage. We don't store JWTs anywhere else than in memory."
Isn't the benefit of JWT that it is a fast method of verification because you can store the JWT locally? If the user has to constantly get a new JWT on each page load by sending the refresh token to the server and waiting to get a JWT back from the server, won't this greatly effect the performance of the app?
Plus, if you are not storing the JWT in the cookie, how you are supposed to do verification on a server side endpoint? For example, NextJs has the pages/api folder. We send requests there. Generally, the JWT is sent as cookie to the api endpoint, and we can verify it in the backend, and then send a request to Hasura backend using the JWT. But, if no JWT is stored in the cookie, how are you supposed to do verification of API routes in NextJs?
Thanks.

We used cookies a long time ago with Hasura Backend Plus and we had so many issues with it. Mainly because browsers are starting to block third-party cookies.
In general, if your app is vulnerable to XSS you should fix that first. Luckily, modern frameworks like React and Vue are protected against XSS by default.

Isn't the benefit of JWT that it is a fast method of verification because you can store the JWT locally? If the user has to constantly get a new JWT on each page load by sending the refresh token to the server and waiting to get a JWT back from the server, won't this greatly effect the performance of the app?

The user don't have to generate a new JWT per page load. A JWT token is stored, in memory, for 15 minutes before being refreshed automatically in the background by our JavaScript SDK.

Plus, if you are not storing the JWT in the cookie, how you are supposed to do verification on a server side endpoint?

Our JavaScript SDK makes sure to send the JWT token as an Authorization header.
If you're using our Serverless Functions you can also use the JWT token to verify the user making the request, check our guide: Get the authenticated user in a Serverless Function.

@elitan Thanks for the detailed response. I still have quite a few questions as I'm still a bit confused by the implementation here. We are using NextJs, so the questions below are based on that. Sorry for so many questions, but I didn't want to open an issue for each one, so hopefully we can address all of them here.

"A JWT token is stored, in memory, for 15 minutes before being refreshed automatically in the background." Does this automatic refresh only happen if the entire app is wrapped with the NhostNextProvider? Otherwise, how does this actually occur?

"The user doesn't have to generate a new JWT per page load." Please see issue 622 (https://github.com/nhost/nhost/issues/622). We are using nhost cloud and nextjs and still have this same issue. We are running the latest versions of everything, but sometimes out of nowhere the refresh token requests start firing like crazy, exactly as documented in that issue.  I can't quite figure out what triggers this, so I wouldn't know how to reliably recreate the issue to debug it, but it happens alot.

Assuming we don't use the nhost client, is there a function to generate a new access token from the refresh token without using the nhost client? I am asking b/c I am leaning towards using NextAuth in our app, as the implementation is a bit easier to understand, but in that case, we would need create a callback to generate a new access token after 15 minutes. I couldn't find anything in your docs for a function that will get a new access token with a refresh token.

Isn't there a security risk of exposing the backend nhost URL in every request when using the nhost client? Why should we be letting users know what our backend URL is to access our hasura instance? To get around this issue on our current hasura implementations (using hasura cloud), we simple "proxy" the request to hasura via a server, so the client only sees the API endpoint we proxy thru and not the actual hasura endpoint. Isn't this a more secure way to do it? But, the nhost client doesn't work this way, obviously, and it just calls the hasura endpoint directly. Which brings to the next question...

Serverless functions: As we are using NextJs we don't have a need for using Nhost serverless functions since NextJS can run serverless via the pages/api folder. In that case, would the guide still work. For example, would we just call our NextJS backend with await nhost.functions.call('/api/some-function', { name: 'my name'}); and the client will send in the token as an authorization header? It's not clear if the functions.call is only usable by nhost serverless functions or by any serverless function platform. My other idea was just to get the access token ourselves and pass it via a header using fetch. what's the benefit anyway of using nhost.functions.call instead of a just fetch to call a serverless function?

Serverless: In general, what I don't understand is how to use nhost in a Node environment anyway. It seems as if all guides are just use the nhost client, which is a client side library. Let's say we need to interact with nhost on the server side. We don't want to use hasura admin secret to interact with database, so how do we execute a call? Is the general idea to just get the JWT from the req auth header, and then attach it again in another request to the hasura backend as bearer token? Also, couldn't we create our own JWT to interact with the backend as the JWT secret is provided by Nhost?

Third party Cookies:  I'm not really sure I understand why there is a need to 3rd party cookies here. See how nextauth works.  The auth code basically runs on the server where the app is, so there is no 3rd party cookies; the cookie is set by the same server where the app is running. I presume you didn't go this route b/c you wanted something that could run even without a server and only in the client. But, now you offer serverless as part of nhost anyway, so I would think implementation with cookies would be much, much easier. I would think storing the access token in memory vs cookies (set by the app itself, and not a third party) would be prone to more issues than cookies and makes everything a bit more complicated.

interesting, moving this issue to a discussion


Add golang/x/net/context.Context to storage driver method calls

We'd like to track logs across calls into the storage driver, among other things. Let's add the context to storage driver method calls. The main benefit will be traceable metrics from http requests to storage driver calls. Follow on benefits include using context to provide a richer driver experience.
This may require #193 to be merged before carrying out this change.
See #263 as example of where we'd like to be able to pass the context.

closed by #410


Searchengine: Mojeek

Mojeek is an independent (with its own crawlers, as opposed to DDG, Qwant, ... that rely on Bing and others)search engine from the UK which does not track at all and is therefore privacy respecting.

What license does Mojeek have?

As far as I can tell, Mojeek ist unfortunately proprietary, similarly to most parts of other search engines (e.g. DDG or Qwant). I understand if that's a blocker.
What they do offer over other search engines like, say Qwant, is that they do not use Bing or Yahoo search results, but strictly their own crawler.
Their privacy policy is here.


Submitting SmokeParticleSystem example

👋
Just wanted to submit a port of the Smoke Particles example from Processing. I couldn't find any mention of it in the issues so I assume no one else has done it?
Pull request to follow!

great, go for it! instructions here: https://github.com/processing/p5.js-website/wiki/Adding-examples

closed with https://github.com/processing/p5.js-website/pull/251


added /sleep link, fixes #3

Please pull the team repo changes into your personal repo before pushing. Also update change log.


Add missing base color tokens for calendar theme aware tokens

Pull Request
🤨 Rationale
Added the missing base color tokens required to create calendar theme-aware tokens according to the mockup.
Figma Mockup: https://dev.azure.com/ni/DevCentral/_wiki/wikis/AppCentral.wiki/118969/Schedule-Test-Plans
Azdo Discussion for reference: https://dev.azure.com/ni/DevCentral/_git/Skyline/pullRequest/750620#1720658507

👩💻 Implementation

Added the necessary base colors for the calendar theme-aware tokens

Note: Calendar theme-aware tokens will be added in the follow-up PR

🧪 Testing
NA

✅ Checklist

[x] I have updated the project documentation to reflect my changes or determined no changes are needed.

Changes are now pretty trivial, don't think this needs review from @rajsite or @fredvisser but feel free to comment afterwards or on the follow up PR. I marked this for auto-merge.


Regardless of cloud provider, AWS instance types are suggested

When deployed from the NR App Catalog, the default cloud used for instance right size suggestions is not configurable. It is currently (2.1.0) set to "amazon"  in the code.
Description
If the cloud provider is, say Azure, the suggested instance types are not Azure types, instead AWS types are provided:

Deploying manually allows the value to be set in the code: nerdlets/cloud-optimize-core/context/data.js, by changing the optimizationDefaults.defaultCloud string from 'amazon' to your cloud provider, e.g. 'azure'.
Steps to Reproduce
Deploy the nr1-cloud-optimize NR One application through the app catalog for an account where the hosts are in the Azure cloud.
Expected Behaviour
Azure right-size suggestions provided, when the original instances are also Azure instances.
Your Environment
NR1 CLI v1.22.2
Chrome v83
MacOS Catalina v10.15.5
Cloud Optimize release 2.1.0
Additional Context
The suggested types could be based on:

a single config option, through the UI
the most common cloud instance type
the existing instance cloud type: AWS instance > AWS instance, Azure instance > Azure instance

@crshanks good catch, some of this code was ported from nimbus where you would set your desired cloud to migrate too at the beginning of the process.
This was an oversight, I'll put priority on this to rework this behaviour.

Fixed in #b7eaf78.
Will send a PR to update the app catalog version.


Report errors generated by packagecloud, exit on failure

I ran mitmproxy so I could notice that packagecloud package create was failing with an interesting error.    Prior to this change it fails silently in the script.
This change reports the failure and exits.

Awesome :metal:


Introduce a jitter into root cert rotator

Please provide a description for what this PR is for.
Introduce a jitter into root cert rotator, that sets up a backoff time when starting rotator. This is to prevent race condition when multiple Citadels are deployed and none of the Citadels is in read-only mode.
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[x] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
#17059

@JimmyCYJ: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio
dd99480ee54c8df91d17d905e620e19f051ecb4e
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@JimmyCYJ: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio
91e12adbee49c63bc1ccb6534955ee9f13cc6d48
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


[Windows] Added support for right-click paste on windows

resolves issue #2318
Pastes the clipboard contents to the terminal on right click.

Is this what all windows users expect when enabling quickEdit? Code looks 👍 now at least, but I can't say more than that. I don't use this function and I don't use windows :)

Yes, at least most of them, that's why it's default :)


View as Router's constructor option

Hello, I want to propose use this declaration
new Backbone.Router({
    view: new Backbone.View()
});

which similar to
new Backbone.View({
    collection: new Backbone.Collection()
});

or
new Backbone.View({
    model: new Backbone.Model()
});

Now Router should have initialize() method which will assign view instance to property. It would be nice if view attribute for Router resolves as collection/model attribute for View.

What would be the primary use case for this?  What would view be used for?

A use case would be nice -- but Routers are definitely not single-view-specific. A normal router will handle URLs for tens or hundreds of internal views ... so I don't think we should adopt this change.


Issue parsing .msg file from Outlook

Getting an ArgumentError Exception: invalid byte sequence in UTF-8 error when trying to parse any .msg file saved to my computer from Outlook.
Steps to reproduce

Drag any email from your inbox onto somewhere on your local disc (eg Desktop) to save it.
Try the following code:

test = File.read(File.expand_path("path_to_file.msg"))
Mail.new(test)

and you wil get *** ArgumentError Exception: invalid byte sequence in UTF-8
also trying Mail.new(test.b) just returns what looks like encoded text
Any help would be much appreciated.
Environment
Windows 10
Outlook Version 2004 Monthly Channel

this gem doesn't support msg format, you have to convert it to eml first
there's a tool that will allow you to do that https://github.com/aquasync/ruby-msg

Thanks for the heads up. Going to try and work with the gem you suggested and see how I go although getting a few warnings when using it.
Could I suggest mentioning something about this or more broadly the file extension types supported maybe in the README?

@nocoli if you would like, please create a PR explaining the other gems you can use to parse or read eml files.


fix regex that determines if a tag is deployable

This bug prevented v0.10.0 images from being pushed to quay.

I am pushing the v0.0.10 images manually now. Since this PR is required for all our v0.0.X patch releases going forward, I am merging it now


Support new CDN v2

Description
This updates and supersedes #15 and should close #16.
Issues Resolved

#16

Check List

[x] All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD
[x] New functionality includes testing.
[x] New functionality has been documented in the README if applicable
[x] All commits have been signed for the Developer Certificate of Origin. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/CONTRIBUTING.MD

It actually seems like the mirrors are also now pointing to the CDN. Thats what Im seeing https://mirrors.iuscommunity.org/mirrorlist/?repo=ius-el6&arch=x86_64&protocol=http

@gsdevme yes, but we should still update this to match what upstream has configured for their repos.


Can't install 16.04

Updated to 14936.
Did a clean install:

lxrun /uninstall /full
Turn off WSL from features
Check that %localappdata%\lxss doesn't exists
lxrun /install

But lsb_release -a still shows 14.04
So, how can I get a fresh 16.04 (not a release upgrade from 14.04)?

I think the official download will change in the next build.  If you want to just do it quick and clean, grab @Rolisoft 's WSL distro switcher.

Thanks @fpqc


Invalid Range values return 0 byte responses for Word Documents

When making a request for bytes of a word document that are unsatisfiable we're incorrectly returning a 0-byte response:
Request
GET /encodedstuff/file.docx
Range: bytes=8001-
Response
200 OK
Content-Length: 0
Content-Range: 8001-8000/8001
Note: this is not true for ALL ranges - those that are WAY off correctly return a 416

Confirmed!


No such module 'Dance'

I tried the approach of dragging and dropping Dance.swift into my project and saw the error that No such module 'Dance'.
I then tried the Cocoapods approach and see that Dance is installed but still get the same error.
The sample project included with Dance works but I seem to be unable to use this in another project. I tried cleaning and cleaning the build folder to no avail.
Any suggestions or can you include a demo video?
pod update
Update all pods
Updating local specs repositories
Analyzing dependencies
Downloading dependencies
Using Dance (1.0.6)
Generating Pods project
Integrating client project
Sending stats
Pod installation complete! There is 1 dependency from the Podfile and 1 total pod installed.

PS. In the DanceExample, I dont see an import Dance but only the import UIKit

So the reason you don't see import Dance in the example project is because Dance.swift is part of the module that the project is in. Only when a module is in another scope than the main app's module do you need to import that external module.
As for your issue:
When you're working with cocoapods, make sure you're using .xcworkspace and not your .xcodeproj.
If you're trying to drag and drop Dance.swift into your project, make sure you drop it in your project folder and select 'Copy if needed'. So like drop it right below ViewController.swift.

Thank you for explaining. I copied it earlier as part of the project but was still trying to import it in the class and seeing the error. Without the import Dance it works as expected.


Added additional fields to DepartmentUser (migration), updated python-social-auth version to fix DeprecationWarning

This change is

Reviewed 4 of 4 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from the review on Reviewable.io


Make scripts/rolling_update create before deleting

Summary
When executing ./scripts/rolling_update vpc-link-myapp-us-central1-a with num_instances=1, the running instance is deleted at the same time it's replacement is being created.  This creates a window in time where packets are dropped as there are no operational vpc-link instances or associated route resources.
Affected version: 0.4.3-4-g4ccf4f9

Closed because this only affects development.  Production has more instances and should use a max_unavailable policy appropriate to maintain the SLO.


add time_range support to scan and fix a problem with start row

add three function to Scan to support TimeRange Scan

func (s *Scan) SetTimeRange(from time.Time, to time.Time)
func (s *Scan) SetTimeRangeFrom(from time.Time)
func (s *Scan) SetTimeRangeTo(to time.Time)

In my use case, I only want to calculate the data which was written into hbase in the pass hour. So if I don't set a time range, the client has to read all data from hbase. If the data in hbase is too large, it would cost lots of time. Example:
scan.SetTimeRange(
        time.Unix(1450195200, 0),
        time.Unix(1450454400, 0),
)

fix set start row only bug

// in scan.go:143
} else if s.StartRow != nil && s.StopRow != nil {

In scan.go:143, it pack StartRow/StopRow only if we set them both.
// in scan.go:224~226
if startRow == nil {
    startRow = s.StartRow
}

But in next() method, StartRow will be used. So if I only set a StartRow, it would be nextStart to next region server. But as I didn't set StopRow, the StartRow wouldn't send to the first server. So the first server may return the data I don't want.
On the other hand, I think it is reasonable to set just a StartRow or EndRow. HBase's rowkey has a dictionary order, so its rowkey is meaningful and has a strict order. Sometimes, if there was a panic when I iterated the hbase. When I solved the problem, I can continue to iterate hbase from where it panic last time.

This all seems very fair, the only thing I'd suggest is instead of taking seconds and converting them to milliseconds for HBase. Take UnixNano and floor it to Milliseconds. Gives a little bit more granularity in timeranges.

@Lazyshot It make sense. Have changed to UnixNano.


Example 2 arrow keys don't move camera position

Using arrow keys to move the camera around with example2/ doesn't actually move the camera position.

Hello and thank you for trying out love.scene.
I can confirm that example2 does not work.
Upon further investigation, I found that the example was broken after a recent change to the interface.
Please note that this issue is not a bug with the library, it is just that the example was out of date.
I have just pushed a fixed to the repository.
Thank you for the feedback!


Check the render method of App.

hi
I dont know why I got this error message:

Invariant Violation: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

Check the render method of `App`.

This error is located at:
    in RCTView (at View.js:71)
    in View (at App.js:53)
    in App (created by AwakeInDevApp)
    in RCTView (at View.js:71)
    in View (created by AwakeInDevApp)
    in AwakeInDevApp (at registerRootComponent.js:35)
    in RootErrorBoundary (at registerRootComponent.js:34)
    in ExpoRootComponent (at renderApplication.js:35)
    in RCTView (at View.js:71)
    in View (at AppContainer.js:102)
    in RCTView (at View.js:71)
    in View (at AppContainer.js:122)
    in AppContainer (at renderApplication.js:34)
- node_modules/react-native/Libraries/Renderer/ReactNativeRenderer-dev.js:5103:6 in createFiberFromElement
- node_modules/react-native/Libraries/Renderer/ReactNativeRenderer-dev.js:6638:14 in createChild
- ... 28 more stack frames from framework internals

App.js:
import React, { Component } from 'react'
import { Text, View, StyleSheet, Image } from 'react-native'
import {
  BottomNavigation,
  IconTab,
  Badge
} from 'react-native-material-bottom-navigation'

export default class App extends Component {
  state = {
    activeTab: 'games'
  }
  tabs = [
      {
        key: 'games',
        icon: 'gamepad-variant',
        label: 'Games',
        barColor: '#388E3C',
        pressColor: 'rgba(255, 255, 255, 0.16)'
      },
      {
        key: 'movies-tv',
        icon: 'movie',
        label: 'Movies & TV',
        barColor: '#B71C1C',
        pressColor: 'rgba(255, 255, 255, 0.16)'
      },
      {
        key: 'music',
        icon: 'music-note',
        label: 'Music',
        barColor: '#E64A19',
        pressColor: 'rgba(255, 255, 255, 0.16)'
      }
    ]

    renderIcon = icon => ({ isActive }) => (
      <Icon size={24} color="white" name={icon} />
    )

    renderTab = ({ tab, isActive }) => (
      <FullTab
        isActive={isActive}
        key={tab.key}
        label={tab.label}
        renderIcon={this.renderIcon(tab.icon)}
      />
    )

  render() {

    return (
      <View style={{ flex: 1 }}>
            <View style={{ flex: 1 }}>
              <Text>masoud</Text>
            </View>
            <BottomNavigation
              onTabPress={newTab => this.setState({ activeTab: newTab.key })}
              renderTab={this.renderTab}
              tabs={this.tabs}
            />
     </View>
    )
  }
}

BottomNavigation is the default export. You need to write:
import BottomNavigation, {
  IconTab,
  Badge
} from 'react-native-material-bottom-navigation'

I changed my code but I got the same error:
Invariant Violation: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

Check the render method of `BackgroundDecorator`.

This error is located at:
    in BackgroundDecorator (at BottomNavigation.js:130)
    in RCTView (at View.js:71)
    in View (at BottomNavigation.js:129)
    in BottomNavigation (at App.js:57)
    in RCTView (at View.js:71)
    in View (at App.js:53)
    in App (created by AwakeInDevApp)
    in RCTView (at View.js:71)
    in View (created by AwakeInDevApp)
    in AwakeInDevApp (at registerRootComponent.js:35)
    in RootErrorBoundary (at registerRootComponent.js:34)
    in ExpoRootComponent (at renderApplication.js:35)
    in RCTView (at View.js:71)
    in View (at AppContainer.js:102)
    in RCTView (at View.js:71)
    in View (at AppContainer.js:122)
    in AppContainer (at renderApplication.js:34)
- node_modules/react-native/Libraries/Renderer/ReactNativeRenderer-dev.js:5103:6 in createFiberFromElement
- node_modules/react-native/Libraries/Renderer/ReactNativeRenderer-dev.js:7379:8 in reconcileSingleElement
- ... 28 more stack frames from framework internals

There are more issues with your Code example:

You're using <Icon />, but you don't import a Component named Icon
You're using <FullTab />, but you're importing IconTab

If you fix those issues in your imports, everything works fine: https://snack.expo.io/rJCFIYLzm
import React, { Component } from 'react'
import { Text, View, StyleSheet, Image } from 'react-native'
import BottomNavigation, {
  FullTab,
  Badge
} from 'react-native-material-bottom-navigation'
import Icon from '@expo/vector-icons/MaterialCommunityIcons'

I copy/paste your code but I got the same error:
import React, { Component } from 'react'
import { Text, View, StyleSheet, Image } from 'react-native'
import BottomNavigation, {
  FullTab,
  Badge
} from 'react-native-material-bottom-navigation'
import Icon from '@expo/vector-icons/MaterialCommunityIcons'

export default class App extends Component {
  state = {
    activeTab: 'games'
  }
  tabs = [
      {
        key: 'games',
        icon: 'gamepad-variant',
        label: 'Games',
        barColor: '#388E3C',
        pressColor: 'rgba(255, 255, 255, 0.16)'
      },
      {
        key: 'movies-tv',
        icon: 'movie',
        label: 'Movies & TV',
        barColor: '#B71C1C',
        pressColor: 'rgba(255, 255, 255, 0.16)'
      },
      {
        key: 'music',
        icon: 'music-note',
        label: 'Music',
        barColor: '#E64A19',
        pressColor: 'rgba(255, 255, 255, 0.16)'
      }
    ]

    renderIcon = icon => ({ isActive }) => (
      <Icon size={24} color="white" name={icon} />
    )

    renderTab = ({ tab, isActive }) => (
      <FullTab
        isActive={isActive}
        key={tab.key}
        label={tab.label}
        renderIcon={this.renderIcon(tab.icon)}
      />
    )
  render() {

    return (
      <View style={{ flex: 1 }}>
            <View style={{ flex: 1 }}>
              <Text>masoud</Text>
            </View>
            <BottomNavigation
              onTabPress={newTab => this.setState({ activeTab: newTab.key })}
              renderTab={this.renderTab}
              tabs={this.tabs}
            />
     </View>
    )
  }
}

Is it really the exact same error output? Because the two errors you posted above were different. Could you please post the current error once again, just to be sure?
I can run the code you posted without any errors. You should be able to do the same using the expo snack I posted (together with the Expo app).

I'm using create-react-native-app. I just installed it after that I installed this library.

Since the code works as expected and without any errors in expo snack, it seems to be caused by your local environment (react-native version, expo version, yarn/npm versions, ). You could also simply try deleting the build cache.

check the render method of 'MaterialTopTabView', i dont know what was the error it is in react native android

@anandh-pga MaterialTopTabView is not a part of this library. It's part of react-navigation.

Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.
Check the render method of App.
Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.
import React, { Component } from 'react'
import {useState} from "react";
import Card from './components/card/Card';
import Navbar from './components/navbar/Navbar'
import './App.css'
const App = () => {
const [username, setUsername] = useState("");
const [user, setUser] = useState("");
console.log(user)
return (

{user ? (
<>

</>
) : (

Chat App
<input
type="text"
placeholder="username"
onChange={(e) => setUsername(e.target.value)}
/>
<button onClick={() => setUser(username)}>Login

)}

)
}
export default App
import React from 'react'
const Navbar = () => {
return (
Navbar
)
}
export default Navbar
why I am getting error


ci: don't run release build on PR + run on mac

Closes #53
Nix by default builds rust packages with the release profile.
We don't need this for running tests on PR.
This PR introduces the following changes:

Build with the release profile on push to master.
Run checks (including checks) with the debug profile on PR.
Add builds on darwin.
Add libgit2 to the buildInputs (required on darwin).

omg the darwin build was such a headache!


What was it like to learn Coq?

We’ve recently started a project to find the best way to design our tracks, in order to optimize the learning experience of students.
As a first step, we’ll be examining the ways in which languages are unique and the ways in which they are similar. For this, we’d really like to use the knowledge of everyone involved in the Exercism community (students, mentors, maintainers) to answer the following questions:

How was your experience learning Coq? What was helpful while learning Coq? What did you struggle with? How did you tackle problems?
In what ways did Coq differ from other languages you knew at the time? What was hard to learn? What did you have to unlearn? What syntax did you have to remap? What concepts carried over nicely?

Could you spare 5 minutes to help us by answering these questions? It would greatly help us improve the experience students have learning Coq :)
Note: this issue is not meant as a discussion, just as a place for people to post their own, personal experiences.
Want to keep your thoughts private but still help? Feel free to email me at<EMAIL_ADDRESS>Thank you!

We're closing this issue as it was part of our research for the v3 version of Exercism which has just been released.
Thanks everyone for chipping in! It has been greatly appreciated.


[Snyk] Security upgrade org.apache.jena:jena-arq from 4.9.0-SNAPSHOT to 5.2.0

Snyk has created this PR to fix 1 vulnerabilities in the maven dependencies of this project.
Snyk changed the following file(s):

jena-geosparql/pom.xml

Vulnerabilities that will be fixed with an upgrade:

Issue
Score
Upgrade

Stack-based Buffer Overflow SNYK-JAVA-COMGOOGLEPROTOBUF-8055227
  124
org.apache.jena:jena-arq:  4.9.0-SNAPSHOT -> 5.2.0  No Known Exploit

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Checkmarx One – Scan Summary & Details – 198b84ad-b549-4e17-bcba-5416c612b0c3
New Issues

Severity
Issue
Source File / Package
Checkmarx Insight

Use_of_Cryptographically_Weak_PRNG
/jena-arq/src/main/java/org/apache/jena/sparql/expr/E_Random.java: 34
Attack Vector

Fixed Issues

Severity
Issue
Source File / Package

Host Namespace is Shared
/docker-compose.yaml: 20

Improper_Restriction_of_Stored_XXE_Ref
/jena-iri/src/main/java/org/apache/jena/iri/impl/BuildViolationCodes.java: 35

Improper_Restriction_of_Stored_XXE_Ref
/jena-iri/src/main/java/org/apache/jena/iri/impl/BuildViolationCodes.java: 39

Improper_Restriction_of_Stored_XXE_Ref
/jena-iri/src/main/java/org/apache/jena/iri/impl/BuildViolationCodes.java: 38

Networks Not Set
/docker-compose.yaml: 20


Update bower.json

remove unexpected token

:+1:

Thanks

Nop! Thanks for so usefull tool and great work!


Reverse a Linked List

Related Issue

#351

Proposed Changes

Added the program

Additional Info

Any additional information or context

Checklist

[x ] ✅ My code follows the code style of this project.
[ ] 📝 My change requires a change to the README.
[x] 🎀 I have updated the README accordingly.
[x] 👀 I have read the CONTRIBUTING document.
[x ] ✨ I have added tests to cover my changes.
[ x] 🚩 All new and existing tests passed.
[x] 🌟 ed the repo

Added the program to reverse the linked list

https://github.com/Lakhankumawat/LearnCPP/issues/351

[ ] Bug fix (non-breaking change which fixes an issue)
[ x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Output Screenshots
| ----------- | ----------- |

Code is copy pasted from Leetcode and it is incomplete and issue is already assigned here #272

///--------------------Pull Requests--------------------///

Short Description or CheckLists

Make sure your Pull Request is descriptive and complete the checklist .
I would recommend you to go through this tutorial video of the project here ,thanks.
///------------------Description -----------------------///
For contribution and more guidelines i would recommend you to go through this
tutorial video of the project here, thanks.
///------------------Description -----------------------///
Let me show you how to check the check list , there should be no space inside brackets like [x]
[x]

[x] Checklist
[ ] Or you can just check them from outside without doing any of these
[x] ✨ I have added tests to cover my changes.
[x] 🚩 All new and existing tests passed.
[ ] 🌟 ed the repo

Starr the repo if you haven't !
Have you watched this video ?

///----------------------PR README --------------------///
You need to follow particular guidelines for your README , please follow
these guidelines click here
also you can see how your README should look like see here
for more please go through these here


Add some badges

:tada: This PR is included in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Contact Page issue to solve (gssoc'23)

GSSOC'23
Aim:
I wanted to solve the issue of the contact page by simply removing the unneccesary part. And thereby also adding some code for betterment to solve the bug.

Issue:

@tanujbordikar i think 2,3 contributors also working on this so do it fast i will merge the first pull request


vanishing comments

After a recent upgrade, looks like old comments are no longer visible and new comments can't be added. Using comments_page 0.1.54 and etherpad version 1.8.11 (Git sha: ad84c8a)

From what version of ep_comments?

The comments are still in the db, they are exported as expected via /export/html but aren't displayed on the pad...


Header is case sensitive

While debugging some code running in a lambda environment I figured that basic-auth is not working since Authorization is used with a capital 'A'.
Instead of retrieving the value with headers.authorization something like this should work:
headers [Object.keys(headers).find(key => key.toLowerCase() === 'authorization')]

This would comply with the spec, headers should not be case sensitive: https://stackoverflow.com/questions/5258977/are-http-headers-case-sensitive

I am facing this issue too. In the event.headers, some our custom headers are converted to lowercase. Such as on the FE we are sending X-Header-A, but on the event object, we received x-header-a as the header key