text:
No --dry-run output by default - update README?

I've ran cargo release --dry-run as per the README, only to get a very terse output:
$ cargo release --dry-run
[2020-10-20T17:48:42Z INFO ] Update mycrate to version 0.2.6
[2020-10-20T17:48:42Z INFO ] Starting mycrate's next development iteration 0.2.7-alpha.0
[2020-10-20T17:48:42Z INFO ] Pushing HEAD to origin
[2020-10-20T17:48:42Z INFO ] Pushing v0.2.6 to origin

I recognized that this is formatted just like env_logger, which I use in my crate, so the next thing I tried was RUST_LOG=trace cargo release --dry-run, only to get the same output.
So, I looked up issues in this repo related to --dry-run, and finally found https://github.com/sunng87/cargo-release/issues/161 - where I discovered that I need to use cargo release --dry-run -vv which does output the commands as the README suggests.
This is kind of hard to discover though, especially as not even https://github.com/sunng87/cargo-release/blob/master/docs/reference.md notes that cargo release supports the -v flag. I am not too experienced with Rust so this might be a common pattern, but I would like to suggest - would it be possible to mention this in the README for newbies like me? :)
Thanks!

Thank you! That's an issue when when changed default log output level. I think a better solute is to set log level to debug by default when --dry-run is enabled.

fixed in https://github.com/sunng87/cargo-release/commit/99a1364b387bd40a6c1885532c4fc96c71530db8


text:
Children voice

Hi,
Did you know if it is possible to customize your model to generate children speeches ?
Thanks

I need this too to my project! haha

Interesting, not sure. I don't have a specific history prompt, but it's possible

closing for inactivity, probably better as a discussion or in discord

we don't support adding custom voices, but there are a few options:

use the provided ones
check out the discord channel (#audio-prompts)
check out community projects https://github.com/rsxdalv/bark-speaker-directory
play with bark, and if you find a voice a voice you like you can save it as an npz and re-use in the future

source: gharchive/issue

authors: felipelalli gkucsko vogloblinsky

repo: suno-ai/bark

license: MIT

license_type: permissive

license_source: github-api


text:
FS: StorageCachedBlockDevice should live in storage-device

StorageCachedBlockDevice is truthfully a fancy StorageBlockDevice<CachedBlockDevice>. The only difference between the two is that it has a special read method that is totally broken handles misaligned blocks in a somewhat efficient way. There's no reason why this function couldn't be implemented on StorageBlockDevice.
@Orycterope since you're going to be fixing the broken read method anyways, I think you should move it to storage_device at the same time.

yep, that was my plan all along

authors: Orycterope roblabla

repo: sunriseos/SunriseOS


text:
RemovedInDjango40Warning with Django 3 and djoser 2.0.3

There are several RemovedInDjango40Warning: django.utils.translation.ugettext_lazy() is deprecated in favor of django.utils.translation.gettext_lazy() warnings when running tests on Django 3 and djoser 2.0.3.

I am also getting these warnings, along with force_text() is deprecated in favor of force_str()

@dekoza just FYI, Django REST Framework 3.11.0 already released and supports django 3.0.
Thank you for your work on djoser, it's awesome :).

Any update on Django3 support now that DRF supports it?

authors: Uninen akittas mattcamp yevgenybulochnik

repo: sunscrapers/djoser

license: mit

license_source: bigquery


text:
Parse error: syntax error, unexpected '?' in (...)/vendor/suomato/luna/src/helpers.php on line 8

I get this error in php 5.6 envioronment:
Parse error: syntax error, unexpected '?' in (...)/vendor/suomato/luna/src/helpers.php on line 8
In PHP 7.0 and 7.1 works fine

Hi @jvmonjo. According to theme requirements you should use at least PHP 7.0.

I was just wondering, from my ignorance, if that was the only issue in PHP 5.6 and if it was easy to fix, you could support php 5.6 so you can get to more people.
But I guess there will be more problems if you chosen not to support php 5.6 so feel free to clese the issue.

I think that it is only issue in PHP 5.6 and I can fix that. I still strongly recommend using PHP 7.0 or PHP 7.1

authors: jvmonjo suomato

repo: suomato/base-camp


text:
cannot get user after Google Auth sign in

Bug report

[x] I confirm this is a bug with Supabase, not with my own application.
[x] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
I'm using Supabase Auth helpers. I configured and tested that signing up a user with email/password is good.
However, when trying to set up Google auth, I cannot login my user. This is somewhat related to this unresolved discussion: https://github.com/orgs/supabase/discussions/16743
Tutorial I Followed
https://supabase.com/docs/guides/auth/social-login/auth-google#using-the-oauth-flow-for-web
Troubleshooting

User DOES get added to the Authentication Dashboard, with a Provider = Google, which suggests they were successfully authorized
Sign in with google redirects to localhost:3000 with a code_challenge parameter, which suggests that Google is authenticating the login
Configured all redirects on Supabase + Google Console as per the documentation

To Reproduce
I can get the URL from my google auth
      const googleRes = await supabase.auth.signInWithOAuth({
        provider: "google",
        options: {
          redirectTo: "http://localhost:3000",
        },
      });

which returns  a URL with the code_challenge
{\"data\":{\"provider\":\"google\",\"url\":\"https://qctnbkfmquxoifgzwmml.supabase.co/auth/v1/authorize?provider=google&code_challenge=<CODE_CHALLENGE>&code_challenge_method=s256\"}

now back in my main page, if I execute getUser, it returns null.
supabase.auth.getUser()

Expected behavior

User would be signed in after signing in with Google.
Actual:  supabase.auth.getUser() returns null

Screenshots
If applicable, add screenshots to help explain your problem.
System information
"@supabase/auth-helpers-nextjs": "^0.8.7",
"@supabase/supabase-js": "^2.39.2",
"next": "14.0.4",

Full Code

See my full code snippet
const supabase = createClientComponentClient(
  NEXT_PUBLIC_SUPABASE_URL,
  NEXT_PUBLIC_SUPABASE_ANON_KEY
);
const handleGoogleSignIn = async () => {

  try {
    const googleRes = await supabase.auth.signInWithOAuth({
      provider: "google",
      options: {
        redirectTo: "http://localhost:3000",
      },
    });

    const tokenRes = await passGoogleTokenToSupabase(googleRes);

    // router.refresh();
  } catch (err) {
    console.error(err);
  }
};

async function passGoogleTokenToSupabase(request) {
  try {
    const requestUrl = new URL(request.data.url);
    const code = requestUrl.searchParams.get("code_challenge");
    if (code) {
      console.log("got the code");
      localStorage.setItem("codePassedToExchangeCodeForSesssion", code);
      const { data, error } = await supabase.auth.exchangeCodeForSession(
        code
      );

      return data;
    } else {

      return null;
    }
  } catch (err) {
    console.error(err);
  }
}

similiar error here, with latest supabase(self hosted) when trying keycloak oauth:
`
⨯ AuthApiError: invalid flow state, no valid flow state found
at handleError (webpack-internal:///(rsc)/./node_modules/.pnpm/@supabase+auth-js@2.63.0/node_modules/@supabase/auth-js/dist/module/lib/fetch.js:74:11)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async _handleRequest (webpack-internal:///(rsc)/./node_modules/.pnpm/@supabase+auth-js@2.63.0/node_modules/@supabase/auth-js/dist/module/lib/fetch.js:120:9)
at async _request (webpack-internal:///(rsc)/./node_modules/.pnpm/@supabase+auth-js@2.63.0/node_modules/@supabase/auth-js/dist/module/lib/fetch.js:99:18)
at async SupabaseAuthClient._exchangeCodeForSession (webpack-internal:///(rsc)/./node_modules/.pnpm/@supabase+auth-js@2.63.0/node_modules/@supabase/auth-js/dist/module/GoTrueClient.js:417:33)
at async eval (webpack-internal:///(rsc)/./node_modules/.pnpm/@supabase+auth-js@2.63.0/node_modules/@supabase/auth-js/dist/module/GoTrueClient.js:744:28) {
__isAuthError: true,
status: 404,
code: 'flow_state_not_found'
}
GET /auth/callback?state=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE3MTMyNzQ5MDYsInNpdGVfdXJsIjoiaHR0cDovL3VuaS1leHBsb3JhdGlvbi1zdHVkaW8ubWxvcHMuZHAudGVjaCIsImlkIjoiMDAwMDAwMDAtMDAwMC0wMDAwLTAwMDAtMDAwMDAwMDAwMDAwIiwiZnVuY3Rpb25faG9va3MiOm51bGwsInByb3ZpZGVyIjoia2V5Y2xvYWsiLCJyZWZlcnJlciI6Imh0dHA6Ly91bmktZXhwbG9yYXRpb24tc3R1ZGlvLm1sb3BzLmRwLnRlY2giLCJmbG93X3N0YXRlX2lkIjoiZDA1MTlhZGUtNzdiZi00MGU0LWFhMWQtMWFlMTMzMmM0YmY4In0.3QbimsFr4xBq0MLeHnEc6FruNpFleA83amX1LxMeFeE&session_state=f99c94f8-08f1-4656-b743-e8c8a85633d6&code=2fbff133-22fb-44b8-b5a4-e621afab3f0d.f99c94f8-08f1-4656-b743-e8c8a85633d6.d650aec2-a988-49ac-a63f-670ba6959540 500 in 426070ms`

similiar error here, with latest supabase(self hosted) when trying keycloak oauth: `
⨯ AuthApiError: invalid flow state, no valid flow state found at handleError (webpack-internal:///(rsc)/./node_modules/.pnpm/@supabase+auth-js@2.63.0/node_modules/@supabase/auth-js/dist/module/lib/fetch.js:74:11) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async _handleRequest (webpack-internal:///(rsc)/./node_modules/.pnpm/@supabase+auth-js@2.63.0/node_modules/@supabase/auth-js/dist/module/lib/fetch.js:120:9) at async _request (webpack-internal:///(rsc)/./node_modules/.pnpm/@supabase+auth-js@2.63.0/node_modules/@supabase/auth-js/dist/module/lib/fetch.js:99:18) at async SupabaseAuthClient._exchangeCodeForSession (webpack-internal:///(rsc)/./node_modules/.pnpm/@supabase+auth-js@2.63.0/node_modules/@supabase/auth-js/dist/module/GoTrueClient.js:417:33) at async eval (webpack-internal:///(rsc)/./node_modules/.pnpm/@supabase+auth-js@2.63.0/node_modules/@supabase/auth-js/dist/module/GoTrueClient.js:744:28) { __isAuthError: true, status: 404, code: 'flow_state_not_found' } GET /auth/callback?state=xxx&session_state=xxx&code=xxx 500 in 426070ms`

Found something weird: My nextjs app works fine with supabase instance deploy on supabase.com, but when I switch to use a self-hosted instance, it gives me this error.
I debugged step by step and found the only different is the code parameter called with /auth/callback, code Self-hosted version is something like '3ccfedb0-142a-4f95-a50c-d496f02b577c.704c8b6e-0761-4a26-a365-26689fb80fcb.d650aec2-a988-49ac-a63f-670ba6959540', which is not 'uuid.NewV4()'.

After setting this env to auth container, get things working well now.
  GOTRUE_EXTERNAL_KEYCLOAK_REDIRECT_URI: https://MY-SUPABASE-HOSTNAME/auth/v1/callback

can you elaborate more please ? I'm using a self hosted supabase instance on coolify and integrated azure auth. I'm using nextjs for my app. On the server, this is my code:
`'use server'
import { createClient } from "@/utils/supabase/server";
import { redirect } from "next/navigation";
export async function azureAuth(): Promise {
const supabase = createClient();
const { data, error } = await supabase.auth.signInWithOAuth({
provider: 'azure',
options: {
scopes: 'email',
redirectTo: process.env.AZURE_AUTH_CALLBACK_URL,
},
})
if (data.url) {
redirect(data.url) // use the redirect API for your server framework
}
}
`
the flow is working fine and I get to login into my microsoft account, but when the callback url is called with a valid code and state, I get a 500.
I have this redirect uri for the gotrue auth container:
- 'GOTRUE_EXTERNAL_AZURE_REDIRECT_URI=https://myappurl.com/api/auth/azure/callback'
which leads to a nextjs api route with this:
`
import { cookies } from 'next/headers'
import { NextResponse } from 'next/server'
import { type CookieOptions, createServerClient } from '@supabase/ssr'
export async function GET(request: Request) {
const { searchParams, origin } = new URL(request.url)
const code = searchParams.get('code')
// if "next" is in param, use it as the redirect URL
const next = searchParams.get('next') ?? '/'
if (code) {
const cookieStore = cookies()
const supabase = createServerClient(
process.env.NEXT_PUBLIC_SUPABASE_URL!,
process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY!,
{
cookies: {
get(name: string) {
return cookieStore.get(name)?.value
},
set(name: string, value: string, options: CookieOptions) {
cookieStore.set({ name, value, ...options })
},
remove(name: string, options: CookieOptions) {
cookieStore.delete({ name, ...options })
},
},
}
)
const { error } = await supabase.auth.exchangeCodeForSession(code)
if (!error) {
return NextResponse.redirect(${origin}${next})
}
}
// return the user to an error page with instructions
// TODO: implement page
return NextResponse.redirect(${origin}/auth/auth-code-error)
}
I don't understand the problem here.
`

authors: FingerLiu shawnesquivel yaberkane05

repo: supabase/auth-helpers


text:
feat: add link to the Dart doc

What kind of change does this PR introduce?
Adds a link to the Dart doc for storage.
Closes https://github.com/supabase/storage-dart/issues/1
What is the current behavior?
There are no doc or link to any docs in the repo.
What is the new behavior?
Users can navigate themselves to the official doc.

What's the point of pointing your own fork of it? Is there any docs there?

@bdlukaa Oh, wow. Thanks for catching that! I really have no idea how that got inserted. It was not supposed to be there.

source: gharchive/pull-request

authors: bdlukaa dshukertjr

repo: supabase/storage-dart


text:
Multiple pools per tenant?

We have multiple microservices using tenant databases. We don't want one service (e.g. Storage @inian) checking out all database connections during (potentially) long transactions.
You could just put some simple metadata in the tenant external_id. So the external_id would be a hash of the tenant (for Supabase it's the project id) and some other key.
Example: mfrkmguhoejspftfvgdz_storage and then when the Storage service connects it the connection string would be psql postgresql://postgres.mfrkmguhoejspftfvgdz_storage:postgres@localhost:7654/postgres
Or should we have some more official pool_key on the tenant record where the username in the connection string would be external_id <> _ <> pool_key?

Yeah just put in the external_id

Turns out we need this. Reopening...

repo: supabase/supavisor


text:
Shellcheck Configuration File Ignored

Describe the bug
Without -x shellcheck won't open any files that may be referenced but not explicitly passed to it on the command line. This is problematic, because super-linter invokes shellcheck once per file.
Expected behavior
I expected shellcheck not to complain simply because I sourced one script from another.
Steps to Reproduce

Create a bash script that sources another bash script.
Run super linter.

Logs
SC1091: Not following: <filename>: openBinaryFile: does not exist (No such file or directory)

For more information:
  https://www.shellcheck.net/wiki/SC1091 -- Not following: <filename>: open...

@Kurt-von-Laven
This is a good catch. i think many users would prefer the behavior of -x when shellcheck is used as most have some sort of referenced files.
Should be an easy fix

@Kurt-von-Laven  Interesting as it seems we already have this in place...
https://github.com/github/super-linter/blob/shellcheck/lib/linter.sh#L795
My guess is that since were not passing scriptdir its not able to properly parse the files location?
Would you be able to troubleshoot this?

That link 404'd for me, but I do see https://github.com/github/super-linter/blob/master/lib/linter.sh#L795. Here is the snippet, which is actually automatically generated by husky. There is a .gitignore file in the same directory as the script that contains only _ and a husky.sh script in the _ directory.
#!/bin/sh

. "$(dirname "$0")/_/husky.sh"

https://github.com/koalaman/shellcheck/wiki/SC1091 suggests:
In case you have access to the file, e.g. if it is included in your source code repository:

# shellcheck source=somefile
source somefile

Did you try that?

Yes, sorry I forgot to mention that I already tried that. It had no effect on the bug, and I believe in retrospect the reason that it didn't work is that it does exactly the same thing as --external-sources, but locally for that one line rather than globally for all files.

I think this is not super-linter's fault, but rather https://github.com/koalaman/shellcheck/issues/1250

Good find; thank you! I don't really think of it as one project or another's fault in a case like this, but rather in terms of the most pragmatic place to make which type of change. I confirmed locally that this issue is resolved by passing --source-path=SCRIPTDIR. I believe it would be helpful to most projects to offer a template .shellcheckrc containing source-path=SCRIPTDIR, which I am happy to contribute if that appeals. Ideally one could pass $GITHUB_WORKSPACE as well, but it seems shellcheck does not substitute environment variables in its config file.

you could play a bit with envsubst when running super-linter, but maybe that would make things a bit obscure.

Thanks for the tip. Definitely not worth the added complexity for us right now since SCRIPTDIR is sufficient for our needs, but hopefully some day :). The plot thickens though... while source-path=SCRIPTDIR fixed the issue locally on shellcheck v0.7.2, we still get the same error on Super-Linter, which is running... shellcheck v0.7.2. I suspect the issue may be that there is presently no template .shellcheckrc, so our .shellcheckrc is not used even though it is in LINTER_RULES_PATH?

@ferrarimarco, I suspect a notification may have been buried since I replied within 10 minutes of your message.

Hi @Kurt-von-Laven .
Having (or not) a .shellcheckrc in our templates doesn't matter. If you set LINTER_RULES_PATH, super-linter should pick yours up.
To confirm, have a look at the output produced by super-linter. Even without enabling debug logging, it should emit that information, IIRC.

I am certainly willing to believe that my theory as to why this is happening is completely wrong. However, I can confirm that .shellcheckrc is picked up when I run shellcheck v0.7.2 locally, but not when I run Super-Linter slim-v4.2.2 with LINTER_RULES_PATH set to /. You are correct that the detected config files are emitted even without debug logging enabled.

Happy to contribute a .shellcheckrc template consisting of source-path=SCRIPTDIR to see if that resolves this issue if that would be accepted.

@admiralAwkbar would it be possible to reopen this ticket? It appears that ShellCheck is also ignoring the template .shellcheckrc. Wild speculation here, but I wonder if something is causing it to run in --norc mode? See https://www.mankier.com/1/shellcheck#RC_Files.

@admiralAwkbar, do you happen to know if the repository root is mounted in Super-Linter's Docker container?

@Kurt-von-Laven  I believe it is

I've just noticed this problem, any update on this?

This is actually a feature request, more than a bug. #1900 (which introduced the .shellcheckrc template file) is not enough for that file to be picked up and passed to shellcheck when super-linter runs it.

@ferrarimarco is there any functional way to decorate the shell_language linter policies? I've also tried the .hadonlint, but it doesn't accept many of the shellcode entries (should I open a different issue for that?)

@ferrarimarco is there any functional way to decorate the shell_language linter policies? I've also tried the .hadonlint, but it doesn't accept many of the shellcode entries (should I open a different issue for that?)

I don't get the question :)
Probably worth opening a separate issue, along with examples.

Chiming in as I'm experiencing the same behavior. Currently, ShellCheck's configuration file is not being picked up.

According to shellcheck docs:

Unless --norc is used, ShellCheck will look for a file .shellcheckrc or shellcheckrc in the script's directory and each parent directory. If found, it will read key=value pairs from it and treat them as file-wide directives.
[...]
If no .shellcheckrc is found in any of the parent directories, ShellCheck will look in ~/.shellcheckrc followed by the XDG config directory (usually ~/.config/shellcheckrc) on Unix, or %APPDATA%/shellcheckrc on Windows. Only the first file found will be used.
[...]

I think we can try moving our .shellcheckrc where shellcheck expects when building the image.
As a workaround, in the meantime, adding a .shellcheckrc in your code base might suffice.

@ferrarimarco you are correct. Putting a .shellcheckrc into the repository root seems to work...

just removed this workflow plugin due to the lack of the much needed -x option.
Thanks for the fish and so long.

just removed this workflow plugin due to the lack of the much needed -x option.
Thanks for the fish and so long.

While I agree that this plugin needs some work, you can set external-sources=true in the .shellcheckrc file (which is the equivalent to -x).

The -x (short form for --external-sources) is set: https://github.com/github/super-linter/blob/aad87c569b8a3de467bf6504c06127822e2845aa/lib/linter.sh#L893
The issue is that Shellcheck doesn't (yet?) support setting an arbitrary location for .shellcheckrc. There's a feature request for this: https://github.com/koalaman/shellcheck/issues/2199
Until that is implemented, there's very little we can do, unfortunately. The workaround described in https://github.com/github/super-linter/issues/1633#issuecomment-997220963 should at least mitigate this issue.

Until that is implemented, there's very little we can do, unfortunately. The workaround described in https://github.com/github/super-linter/issues/1633#issuecomment-997220963 should at least mitigate this issue.

After org name changed, correct link is this https://github.com/super-linter/super-linter/issues/1633#issuecomment-997220963
TLDR: Add .shellcheckrc file to your repo https://github.com/super-linter/super-linter/blob/main/TEMPLATES/.shellcheckrc

Ah.  I'll try adding a .shellcheckrc file to my codebase.
Thanks!
P.S. - Sorry for the rehash.  I couldn't find the workaround as the link was broken, as you discovered.

authors: Kurt-von-Laven TheCaptain989 admiralAwkbar caioaamaral egberts ferrarimarco georglauterbach nantiferov

repo: super-linter/super-linter


text:
correction de l'episode 29 qui etait en fait l'episode 30

L'episode 29 est en fait l'episode special Fast and Furious.
Invalider les films de l'episode 29 n'a pas suffit. J'ai dû faire search/replace dans tous les fichiers scb_movies.json  et aussi supprimer l'episode 29 dans les fichiers scb_episodes.json

En relançant l'import ça m'a remis l'épisode 29 mais sans casser les films du 30, comme ça a l'air de tenir je le remets.

license: ISC


text:
TODO: trasition over to CircleCI

CI Checks have stopped working on travis. I personally know / understand Circle more so I figured it would be worth the investment to just switch over to CircleCI.
.... i'll get around to this when I get a chance 🙂
But in the mean time, if you are submitting a contribution be sure to run typecheck + lint + test npm scripts!

Done 🚀

e6b284f39431c50373dc1dddf90e35b8fd194049
56578820330a366cf0a58421628f10c3dc9af5bc

repo: supermacro/neverthrow


text:
🛑 other is down

In 75678d6, other ($OTHER_SITE) was down:

HTTP code: 0
Response time: 0 ms

Resolved: other is back up in 4152616 after 43 minutes.


text:
Switch to eslint 1.2.0 (closes #29)

\cc @AlexanderMoskovkin @AndreyBelym

lgtm

lgtm
вт, 25 авг. 2015 г. в 18:08, AlexanderMoskovkin notifications@github.com:

lgtm
—
Reply to this email directly or view it on GitHub
https://github.com/superroma/testcafe-phoenix/pull/43#issuecomment-134617004
.

authors: AlexanderMoskovkin AndreyBelym inikulin

repo: superroma/testcafe-phoenix


text:
🛑 Node - de-25dd7d7e.yalaso.top is down

In f6c08e3, Node - de-25dd7d7e.yalaso.top (http://de-25dd7d7e.yalaso.top/api/v1/ping) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Node - de-25dd7d7e.yalaso.top is back up in 8126f83 after 30 minutes.

repo: superrr-vpn/status


text:
🛑 Node - jp-05fd29e8.yalaso.top is down

In 19cd65c, Node - jp-05fd29e8.yalaso.top (http://jp-05fd29e8.yalaso.top/api/v1/ping) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Node - jp-05fd29e8.yalaso.top is back up in 2bc370c after 47 minutes.


text:
typo

correction d'une faute d'orthographe

Merci

authors: Nikodr supertanuki

repo: supertanuki/numeriqueEcoResponsable


text:
More precise annotations for literals

Currently, most (all?) literals eat all the space to the right which makes annotations slightly inaccurate. The downside of fixing this is that parser code is likely to become (much) less clear.

This is specifically a problem for parsers we lift from the parsers package such as integerOrDouble and stringLiteral. We would rather avoid rewriting them, but they eat trailing spaces.

Further research shows that the difference between CharParsing and TokenParsing isn't just cosmetic: parsers built on the latter can be better manipulated/tuned using e.g. parser-transformers like Unspaced.

repo: supki/t


text:
Problem running a yarncommand

Hi and thanks for this awesome tool.
It would be super nice if we could use yarn in Command section because whenever I do so, I get a execvp(3) failed.: No such file or directory
Maybe it's because I misconfigured the environment path variable.
What I use today is /Users/martin/.nvm/versions/node/v7.5.0
Hope you can help and thanks again

Thanks @martinratinaud
You may need to add yarn path to the env path like: /Users/martin/.nvm/versions/node/v7.5.0:/usr/local/bin. It assumes the yarn command is under /usr/local/bin/yarn.
Run which yarn to find your yarn path.

Thanks a lot, in fact, I add to put
/Users/martin/.nvm/versions/node/v7.5.0/bin/
and everything's alright now, maybe it would be nice to add it to src/features/home/SettingsPage.js in help message
Instead of "The environment path to find the command. You may need to set this when using nvm."
could be
"The environment path to find the command. You may need to set this when using nvm. i.e. /path/to/.nvm/versions/node//bin"
Thanks anyway, I close this one

Ok, no problem. I will refine the tooltip.

authors: martinratinaud supnate

repo: supnate/command-pad


text:
Portable builds fail in shared library build

CFLAGS=-D__BLST_PORTABLE__ ./build.sh -shared
+ cc -D__BLST_PORTABLE__ -D__ADX__ -mno-avx -c ./src/server.c
+ cc -D__BLST_PORTABLE__ -D__ADX__ -mno-avx -c ./build/assembly.S
+ ar rc libblst.a assembly.o server.o
+ cc -shared -o libblst.so -Wl,--whole-archive,libblst.a,--no-whole-archive -D__BLST_PORTABLE__ -D__ADX__ -mno-avx -Wl,-Bsymbolic,--version-script=/tmp/ld.blst.279657
/usr/bin/ld: error: libblst.a(server.o): requires dynamic R_X86_64_32 reloc against 'BLS12_381_r' which may overflow at runtime; recompile with -fPIC

4967efe5c49b5abd09895ffa31d54e308835ab15

Ah, misunderstood the build system - CFLAGS="-D__BLST_PORTABLE__ -fPIC" ./build.sh -shared works as expected

CFLAGS environment variable has an absolute priority. Formally speaking one can make a case that -fPIC should be passed nevertheless. Meanwhile passing compiler flags directly to build.sh is better suited for all-round purposes, as ./build.sh -shared -D__BLST_PORTABLE__.

authors: arnetheduck dot-asm

repo: supranational/blst


text:
[HELP] Import vue-quill-editor/dist/ssr in ssr Single File Components

Vue.js version and component version
"vue": "^2.5.15",
"vue-quill-editor": "^3.0.5"
Reproduction
Context :

Vue in SSR (vue-hackernew)
I try to import vue-quill-editor directly in a Single File Components

<template>

    {{ label }}
    {{ helperText }}

      {{ getErrorName }}

</template>

Steps to reproduce
Import vue-quill-editor/dist/ssr in a component with a directive
What is Expected?
Quill is working
What is actually happening?
Error 500 with this error message :
ReferenceError: document is not defined
    at Object.DIFF_DELETE (node_modules/quill/dist/quill.js:7588:0)
    at __webpack_require__ (node_modules/quill/dist/quill.js:36:0)
    at Object.defineProperty.value (node_modules/quill/dist/quill.js:980:0)
    at __webpack_require__ (node_modules/quill/dist/quill.js:36:0)
    at Object.defineProperty.value (node_modules/quill/dist/quill.js:5582:0)
    at __webpack_require__ (node_modules/quill/dist/quill.js:36:0)
    at Object.defineProperty.value (node_modules/quill/dist/quill.js:9972:0)
    at __webpack_require__ (node_modules/quill/dist/quill.js:36:0)
    at Object.<anonymous> (node_modules/quill/dist/quill.js:11484:0)
    at __webpack_require__ (node_modules/quill/dist/quill.js:36:0)

Hi,
I get a 500 when I try to import vue-quill-editor directly in a Single File Components and use the directive only in this component.
It's working when I import vue-quill-editor/dist/ssr from app.js with Vue.use(), it's not working when I import it in the component.
I clearly dont understand something, maybe my syntax is not correct ?
I dont want to use vue-quill-editor from app.js/vue.use() because I want Webpack to bundle it only for one route, not in vendor.js (Quill is big)
Thanks for the good work,
and have a good day
Hugo

import { quillEditor } from 'vue-quill-editor/dist/ssr'

quillEditor is a directive object, is not a component object.
export default {
    name: 'form-editor',
    directives: {
        quill: quillEditor
    }
}

Ouf! I forgot the "quill: " Sorry for that.
Thanks again for the good work and the help

Hi,
finally, I thought it worked, but it's only because I had the vue-quill declaration in my entry-server.
Is it working correctly in SSR mode ?
This is not working :
`

{{ label }}
{{ helperText }}

{{ getErrorName }}

This is not going to work. Quill ssr is not really ssr it's just directive which is inserted during ssr where it's require document and fail.
That's why is in Nuxt example ssr: false: https://github.com/surmon-china/vue-quill-editor/blob/master/examples/nuxt-ssr-example/nuxt.config.js#L4

authors: serdydev surmon-china zajca

repo: surmon-china/vue-quill-editor


text:
Table isn't working well

@vinzvinci Where is that table?

You can check index.md for the table
You can check the information that we provided on _includes folder

Table shows on github-pages

I can suggest you to create:

function (ex. JavaScript) to fill in an HTML table
GH Action that triggers ⬆ that function on change within _includes directory

Just give me a few minutes @vinzvinci , I would make the pull request!

Just give me a few minutes @vinzvinci , I would make the pull request!

I would have added this symbol  | but this means the end of table in the markdown symbols that was why I used a comma, !
| Vincent Villafuerte | vinzvinci | Founder of Surpath | Microsoft Learn Student Ambassador | BS Information System Student | Open Source DevRel | Software Engineer |

created PR do check it @vinzvinci

Thank you @SashoStoichkov for your suggestion, but I want to make it simple for now and maybe soon I will try that features.
-
Hey @chryzcodez, I reviewed your PR and I don't want to use ,  to separate my titles. I prefer the most escaped pipes \| to show this output | so it won't bother the table rows. Still thank you for the PR, you still get green square for the commit that you've made ^_^ .
-
Hey @Nitesh-thapliyal. I preferred your PR, it's simple and maybe I will ignore _includes directory for now. Can you fix the spelling on my name, so you can get more green square.

Again thanks folks, all ideas are welcome.

Ok sure

authors: Nitesh-thapliyal SashoStoichkov chryzcodez vinzvinci


text:
Scrollbars missing

Describe the bug
There are no (vertical) scrollbars in the query pane or the results pane (in combined and individual modes).
To Reproduce
Do a query with enough results...
Expected behavior
scroll bar!
Environment:
Platform: Desktop
OS: Linux
Architecture: x86_64
WebView: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.0 Safari/605.1.15
Version: 2.0.4
Flags: featureFlags: false, models_view: true, apidocs_view: true, themes: false, newsfeed: true

Closing as it cannot be reproduced internally and there has not been further activity on this issue

authors: gregzuro macjuul

repo: surrealdb/surrealist


text:
Typo in README example

class SampleFileRotationDelegate: FileRotationLoggerDeletate {

should be updated to:
class SampleFileRotationDelegate: FileRotationLoggerDelegate {

@neilhamilton
Thanks! I fixed typo in README.
https://github.com/sushichop/Puppy/commit/4d01fb2579ddf7a4df4191c893871517a6590ed7

I'll now close this issue.
Thanks.

authors: neilhamilton sushichop

repo: sushichop/Puppy


text:
Can we add text below the icon in the non-selected tabs

How to add text below the non-selected tabs. I really need this feature and I believe it is useful for others as well.

For this we might have to change many things in the library (like making sure the text is not obstructed by the curve). So this feature will not be implemented for now, sorry.

For this we might have to change many things in the library (like making sure the text is not obstructed by the curve). So this feature will not be implemented for now, sorry.

Can i add floating action button with speed dial

Sorry @NadeemRawther I didn't get your question. Can you please explain it.

Sorry @NadeemRawther I didn't get your question. Can you please explain it.

I mean can i add a button button like

i want to add this kind of button on bottom navigation

This is not currently supported but if you want you can fork and implement it.

I think this is really important to add text below the non-selected tabs. it is a beautiful bottom navigation and could be very useful

I have thought about this and other people have requested this feature as well. But there are some technical challenges that need to be tackled. Handling text in this case is quite tricky. I will do some research and see if this can be done.

authors: Masoudmjm NadeemRawther susonthapa vinay-zorang

repo: susonthapa/curved-bottom-navigation


text:
arm: support arm build

Generated the vmlinux.h from an ARM server via
bpftool btf dump file /sys/kernel/btf/vmlinux format c > vmlinux.h

Tested on Ampere setup:
[root@perf-arm-12 kepler]# uname -r
5.14.0-362.21.1.el9_3.aarch64
[root@perf-arm-12 kepler]# curl localhost:8888/metrics 2>&1 |grep kepler_exporter_build_info
# HELP kepler_exporter_build_info A metric with a constant '1' value labeled by version, revision, branch, goversion from which kepler_exporter was built, and the goos and goarch for the build.
# TYPE kepler_exporter_build_info gauge
kepler_exporter_build_info{branch="",goarch="arm64",goos="linux",goversion="go1.20.14",revision="unknown",tags="include_gcs,include_oss,containers_image_openpgp,gssapi,providerless,netgo,osusergo,libbpf,linux,gpu",version=""} 1
[root@perf-arm-12 kepler]# curl localhost:8888/metrics |grep kepler_process_ |grep joules |sort -k 2 -g |tail
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  132k    0  132k    0     0  32.4M      0 --:--:-- --:--:-- --:--:-- 32.4M
kepler_process_core_joules_total{command="node",container_id="system_processes",mode="dynamic",pid="86862",source="intel_rapl",vm_id=""} 0.195
kepler_process_package_joules_total{command="node",container_id="system_processes",mode="dynamic",pid="86862",source="intel_rapl",vm_id=""} 0.195
kepler_process_core_joules_total{command="sh",container_id="system_processes",mode="dynamic",pid="86735",source="intel_rapl",vm_id=""} 0.549
kepler_process_package_joules_total{command="sh",container_id="system_processes",mode="dynamic",pid="86735",source="intel_rapl",vm_id=""} 0.549
kepler_process_core_joules_total{command="irqbalance",container_id="system_processes",mode="dynamic",pid="2403",source="intel_rapl",vm_id=""} 0.681
kepler_process_package_joules_total{command="irqbalance",container_id="system_processes",mode="dynamic",pid="2403",source="intel_rapl",vm_id=""} 0.681
kepler_process_core_joules_total{command="node",container_id="system_processes",mode="dynamic",pid="87516",source="intel_rapl",vm_id=""} 1.581
kepler_process_package_joules_total{command="node",container_id="system_processes",mode="dynamic",pid="87516",source="intel_rapl",vm_id=""} 1.581
kepler_process_core_joules_total{command="kworker/73:0",container_id="kernel_processes",mode="dynamic",pid="383",source="intel_rapl",vm_id=""} 229.143
kepler_process_package_joules_total{command="kworker/73:0",container_id="kernel_processes",mode="dynamic",pid="383",source="intel_rapl",vm_id=""} 229.143

@vimalk78 @SamYuan1990 how did you build the arm64 kepler_builder image? I can find one for s390 but not arm64

checking

@vimalk78 @SamYuan1990 how did you build the arm64 kepler_builder image? I can find one for s390 but not arm64

I built it on internal RH systems, not in upstram CI.

let see what will happen in #1261

Tested it on ARM
# curl localhost:8888/metrics |grep joules |sort -k 2 -g |grep kepler_process_core |tail -5
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  131k    0  131k    0     0  21.3M      0 --:--:-- --:--:-- --:--:-- 21.3M
kepler_process_core_joules_total{command="node",container_id="system_processes",mode="dynamic",pid="268421",source="intel_rapl",vm_id=""} 0.033
kepler_process_core_joules_total{command="node",container_id="system_processes",mode="dynamic",pid="256051",source="intel_rapl",vm_id=""} 0.06
kepler_process_core_joules_total{command="node",container_id="system_processes",mode="dynamic",pid="256093",source="intel_rapl",vm_id=""} 0.075
kepler_process_core_joules_total{command="irqbalance",container_id="system_processes",mode="dynamic",pid="2403",source="intel_rapl",vm_id=""} 0.3
kepler_process_core_joules_total{command="migration/71",container_id="kernel_processes",mode="dynamic",pid="371",source="intel_rapl",vm_id=""} 104.277
# rpm -qa |grep kepler
kepler-v0.7.7.2.gf4b2922d.dirty-20240226.aarch64
# uname -r
5.14.0-362.21.1.el9_3.aarch64

kepler amd64 and arm64 images are now available

Awesome! Works as expected 👍

@beneiltis this sounds great! would you please write a PR and share your story? https://github.com/sustainable-computing-io/kepler-doc

Sure I am happy to help. But can you elaborate on what I should create a PR for? 😇
I only checked that the image works on arm64 clusters.

Sure I am happy to help. But can you elaborate on what I should create a PR for? 😇 I only checked that the image works on arm64 clusters.

@beneiltis The installation process on ARM is not there yet. It would be great if you can walk through your steps and share how to get started. https://github.com/sustainable-computing-io/kepler-doc/blob/main/docs/installation/kepler.md

I had a clarification regarding this implementation. The implementation has "source=intel_rapl". Is that a display artifact and how does it work with ARM64 when you are using the intel_rapl? Thanks!

repo: sustainable-computing-io/kepler


text:
when trivy output is too long test-modules and plan jobs fail

tfaction version
v1.4.0
Overview
I have noticed when the trivy output is too long reviewdog (I think) fails, crashing the pipeline. as a workaround I have added
trivy.yaml which helps sometimes but not a good solution.
severity:
  - MEDIUM
  - HIGH
  - CRITICAL

Also trivy scans modules/examples in .terraform folder. this is specially annoying when using open source modules like gcp modules where there could be multiple modules we don't use in the current config and trivy scans and reports issues in them producing a huge list of useful and useless information.
How to reproduce
main.tf
####################################################
#             VPC                                  #
####################################################

module "vpc" {
    source  = "terraform-google-modules/network/google"
    version = "~> 9.1"
}

####################################################
#                NAT                               #
####################################################

module "subnet-cloud-nat" {
  source  = "terraform-google-modules/cloud-nat/google"
  version = "5.0.0"
}

####################################################
#             Private service connect              #
####################################################

resource "google_compute_global_address" "database_service_range" {
  provider      = google-beta
  project       = var.project_id
}

resource "google_compute_global_address" "redis_service_range" {
  provider      = google-beta
}

# Creates the peering with the producer network.
resource "google_service_networking_connection" "private_service_access" {
  provider                = google-beta
}

#################################################
#           Private Google APIs                 #
#################################################

module "private-google-apis" {
  source  = "terraform-google-modules/cloud-dns/google"
  version = "5.2.0"
}

#################################################
#           Private GCR                         #
#################################################

module "private-gcr-io" {
  source  = "terraform-google-modules/cloud-dns/google"
  version = "5.2.0"
}

GitHub Actions' log
Raw Output:
message:"Firewall rule allows ingress traffic from multiple addresses on the public internet." location:{path:".terraform/modules/vpc/modules/fabric-net-firewall/main.tf" range:{start:{line:105} end:{line:105}}} severity:ERROR source:{name:"trivy" url:"https://github.com/aquasecurity/trivy"} code:{value:"AVD-GCP-0027" url:"https://avd.aquasec.com/misconfig/avd-gcp-0027"}
Error: [trivy] reported by reviewdog 🐶
Firewall rule allows ingress traffic from multiple addresses on the public internet.

Raw Output:
message:"Firewall rule allows ingress traffic from multiple addresses on the public internet." location:{path:".terraform/modules/vpc/modules/fabric-net-firewall/main.tf" range:{start:{line:75} end:{line:75}}} severity:ERROR source:{name:"trivy" url:"https://github.com/aquasecurity/trivy"} code:{value:"AVD-GCP-0027" url:"https://avd.aquasec.com/misconfig/avd-gcp-0027"}
Warning: [trivy] reported by reviewdog 🐶
Service account access is granted to a user at project level.

Raw Output:
message:"Service account access is granted to a user at project level." location:{path:".terraform/modules/vpc/test/setup/iam.tf" range:{start:{line:41} end:{line:41}}} severity:WARNING source:{name:"trivy" url:"https://github.com/aquasecurity/trivy"} code:{value:"AVD-GCP-0011" url:"https://avd.aquasec.com/misconfig/avd-gcp-0011"}
reviewdog: found at least one result in diff
Error: The process '/home/runner/.local/share/aquaproj-aqua/bin/reviewdog' failed with exit code 1

Expected behaviour
pipeline should pass
Actual behaviour
pipeline failure
Important Factoids
No response
Note
Most of the findings here are not necessary because I'm not using them in my config.
:x: Trivy error
Build link | trivy
Working Directory: modules/network

rule
severity
filepath
range
message

AVD-GCP-0013
WARNING
.terraform/modules/private-gcr-io/main.tf
104 ... 140
Managed zone does not have DNSSEC enabled.

AVD-GCP-0013
WARNING
.terraform/modules/private-google-apis/main.tf
104 ... 140
Managed zone does not have DNSSEC enabled.

AVD-GCP-0007
ERROR
.terraform/modules/project_services/modules/core_project_factory/main.tf
158 ... 158
Service account is granted a privileged role.

AVD-GCP-0007
ERROR
.terraform/modules/project_services/test/fixtures/vpc_sc_project/main.tf
57 ... 57
Service account is granted a privileged role.

AVD-GCP-0011
WARNING
.terraform/modules/project_services/test/setup/iam.tf
57 ... 57
Service account access is granted to a user at project level.

AVD-GCP-0027
ERROR
.terraform/modules/subnet-cloud-nat/examples/nat_with_compute_engine/main.tf
72 ... 72
Firewall rule allows ingress traffic from multiple addresses on the public internet.

AVD-GCP-0030
WARNING
.terraform/modules/subnet-cloud-nat/examples/nat_with_compute_engine/main.tf
36 ... 50
Instance allows use of project-level SSH keys.

AVD-GCP-0041
WARNING
.terraform/modules/subnet-cloud-nat/examples/nat_with_compute_engine/main.tf
36 ... 50
Instance does not have VTPM for shielded VMs enabled.

AVD-GCP-0045
WARNING
.terraform/modules/subnet-cloud-nat/examples/nat_with_compute_engine/main.tf
36 ... 50
Instance does not have shielded VM integrity monitoring enabled.

AVD-GCP-0067
WARNING
.terraform/modules/subnet-cloud-nat/examples/nat_with_compute_engine/main.tf
36 ... 50
Instance does not have shielded VM secure boot enabled.

AVD-GCP-0027
ERROR
.terraform/modules/subnet-cloud-nat/examples/nat_with_gke/main.tf
64 ... 64
Firewall rule allows ingress traffic from multiple addresses on the public internet.

AVD-GCP-0048
ERROR
.terraform/modules/subnet-cloud-nat/examples/nat_with_gke/main.tf
36 ... 52
Cluster has legacy metadata endpoints enabled.

AVD-GCP-0050
WARNING
.terraform/modules/subnet-cloud-nat/examples/nat_with_gke/main.tf
36 ... 52
Cluster does not override the default service account.

AVD-GCP-0056
WARNING
.terraform/modules/subnet-cloud-nat/examples/nat_with_gke/main.tf
36 ... 52
Cluster does not have a network policy enabled.

AVD-GCP-0011
WARNING
.terraform/modules/subnet-cloud-nat/test/setup/iam.tf
36 ... 36
Service account access is granted to a user at project level.

AVD-GCP-0027
ERROR
.terraform/modules/vpc/codelabs/simple/main.tf
104 ... 104
Firewall rule allows ingress traffic from multiple addresses on the public internet.

AVD-GCP-0030
WARNING
.terraform/modules/vpc/codelabs/simple/main.tf
68 ... 91
Instance allows use of project-level SSH keys.

AVD-GCP-0031
ERROR
.terraform/modules/vpc/codelabs/simple/main.tf
84 ... 86
Instance has a public IP allocated.

AVD-GCP-0041
WARNING
.terraform/modules/vpc/codelabs/simple/main.tf
68 ... 91
Instance does not have VTPM for shielded VMs enabled.

AVD-GCP-0045
WARNING
.terraform/modules/vpc/codelabs/simple/main.tf
68 ... 91
Instance does not have shielded VM integrity monitoring enabled.

AVD-GCP-0067
WARNING
.terraform/modules/vpc/codelabs/simple/main.tf
68 ... 91
Instance does not have shielded VM secure boot enabled.

AVD-GCP-0027
ERROR
.terraform/modules/vpc/examples/basic_firewall_rule/main.tf
18 ... 29
Firewall rule allows ingress traffic from multiple addresses on the public internet.

AVD-GCP-0030
WARNING
.terraform/modules/vpc/examples/basic_shared_vpc/main.tf
75 ... 88
Instance allows use of project-level SSH keys.

AVD-GCP-0030
WARNING
.terraform/modules/vpc/examples/basic_shared_vpc/main.tf
57 ... 71
Instance allows use of project-level SSH keys.

AVD-GCP-0041
WARNING
.terraform/modules/vpc/examples/basic_shared_vpc/main.tf
75 ... 88
Instance does not have VTPM for shielded VMs enabled.

AVD-GCP-0041
WARNING
.terraform/modules/vpc/examples/basic_shared_vpc/main.tf
57 ... 71
Instance does not have VTPM for shielded VMs enabled.

AVD-GCP-0045
WARNING
.terraform/modules/vpc/examples/basic_shared_vpc/main.tf
75 ... 88
Instance does not have shielded VM integrity monitoring enabled.

AVD-GCP-0045
WARNING
.terraform/modules/vpc/examples/basic_shared_vpc/main.tf
57 ... 71
Instance does not have shielded VM integrity monitoring enabled.

AVD-GCP-0067
WARNING
.terraform/modules/vpc/examples/basic_shared_vpc/main.tf
75 ... 88
Instance does not have shielded VM secure boot enabled.

AVD-GCP-0067
WARNING
.terraform/modules/vpc/examples/basic_shared_vpc/main.tf
57 ... 71
Instance does not have shielded VM secure boot enabled.

AVD-GCP-0027
ERROR
.terraform/modules/vpc/examples/firewall_logging/main.tf
18 ... 33
Firewall rule allows ingress traffic from multiple addresses on the public internet.

AVD-GCP-0030
WARNING
.terraform/modules/vpc/examples/network_service_tiers/main.tf
34 ... 50
Instance allows use of project-level SSH keys.

AVD-GCP-0031
ERROR
.terraform/modules/vpc/examples/network_service_tiers/main.tf
46 ... 48
Instance has a public IP allocated.

AVD-GCP-0041
WARNING
.terraform/modules/vpc/examples/network_service_tiers/main.tf
34 ... 50
Instance does not have VTPM for shielded VMs enabled.

AVD-GCP-0045
WARNING
.terraform/modules/vpc/examples/network_service_tiers/main.tf
34 ... 50
Instance does not have shielded VM integrity monitoring enabled.

AVD-GCP-0067
WARNING
.terraform/modules/vpc/examples/network_service_tiers/main.tf
34 ... 50
Instance does not have shielded VM secure boot enabled.

AVD-GCP-0030
WARNING
.terraform/modules/vpc/examples/packet_mirroring/main.tf
17 ... 33
Instance allows use of project-level SSH keys.

AVD-GCP-0041
WARNING
.terraform/modules/vpc/examples/packet_mirroring/main.tf
17 ... 33
Instance does not have VTPM for shielded VMs enabled.

AVD-GCP-0045
WARNING
.terraform/modules/vpc/examples/packet_mirroring/main.tf
17 ... 33
Instance does not have shielded VM integrity monitoring enabled.

AVD-GCP-0067
WARNING
.terraform/modules/vpc/examples/packet_mirroring/main.tf
17 ... 33
Instance does not have shielded VM secure boot enabled.

AVD-GCP-0027
ERROR
.terraform/modules/vpc/modules/fabric-net-firewall/main.tf
90 ... 90
Firewall rule allows ingress traffic from multiple addresses on the public internet.

AVD-GCP-0027
ERROR
.terraform/modules/vpc/modules/fabric-net-firewall/main.tf
105 ... 105
Firewall rule allows ingress traffic from multiple addresses on the public internet.

AVD-GCP-0027
ERROR
.terraform/modules/vpc/modules/fabric-net-firewall/main.tf
75 ... 75
Firewall rule allows ingress traffic from multiple addresses on the public internet.

AVD-GCP-0011
WARNING
.terraform/modules/vpc/test/setup/iam.tf
41 ... 41
Service account access is granted to a user at project level.

If you want to ignore .terraform, I think you can use .trivyignore.
Hmm. The crash of reviewdog is an issue of reviewdog.
But it's good for tfaction to handle the issue.

If you want to ignore .terraform, I think you can use .trivyignore.

it would be nice to actually get issues related to the modules we depend on, I guess until trivy comes up with a solution I'll have to ignore .terraform dir.

Hmm. The crash of reviewdog is an issue of reviewdog.
But it's good for tfaction to handle the issue.

yeah, it can be confusing whether its an issue with trivy or reviewdog otherwise.
thank you for the feedback.

authors: rochana-atapattu suzuki-shunsuke

repo: suzuki-shunsuke/tfaction


text:
Rewrite guide Compiling section

Rewrite the Compiling section to reflect new tooling:

Overview should highlight the two steps: configure, compile
Reduce detail and refer to Wiki

Phew, I've done a few passes over this and I'm ready to merge. It's difficult to write short and clear documentation which still captures the necessary detail :)
What I'm trying to achieve is:

Provide a clear outline of the build process: configuration followed by compilation.
Provide a reasonably detailed summary of both steps, referencing the Wiki and other external sources for details.

The previous text didn't provide a clear overview, and genconfig.py was not mentioned at all (now the text refers to configure.py and introduces it as the main configuration preparation tool).
I'll merge in a bit - any comments welcome (and can be applied in separate pulls too).

Skimming the diff a bit, it looks like the original content predates genconfig, which I assume is why it wasn't mentioned. :)

Yeah, the original content was pretty old and predated the external duk_config.h header. But it wasn't very clearly organized even for that state of affairs.

authors: fatcerberus svaarala

repo: svaarala/duktape


text:
第一课作业

pragma solidity ^0.4.14;
contract Payroll{
uint salary = 1 ether;
address Lisa；
address Employee;
uint constant payDuration = 8 seconds;
uint lastPayday = now;
function set(uint new salary) {
  salary = newsalary * 200 wei;
}

function set(address Employee) {
   Lisa = Employee;
}

function addFund() payable returns (uint) {
    return this.balance;
}

function calculateRunaway() returns(uint) {
    return this.balance / salary;
}

function hasEnoughFund() returns(bool) {
    return calculateRunaway() > 0;
}

function getPaid()  {
    if (msg.sender != frank) {
        revert();
    }
    uint nextPayDay = lastPayday + payDuration;
    if (nextPayDay > now) {
        revert();
    }
        lastPayday = nextPayDay;
        frank.transfer(salary);
}

}

@web-flow
https://github.com/Iris666/course.git

repo: svblockdong/course


text:
bash based app runs two times when dropping text snippets (vers 5.1)

If dropping a file onto an app everything works fine.
But if dropping a textsnippet onto an app, the app is executed two times within one run.
Like a loop. But only two times.
On its 1st run stdin will show empty input.
On its 2nd run  it will overwrite the textwindows content and show the dropped text from stdin.
Here is a test script to to see the issue. When running also watch the date/time output in the textwindow.
But please test it multiple times. At the very very 1st run of the app, right after creating, it seems to work for only one time.

!/bin/bash
text=$(cat)
date
echo 'Hello, World'
echo 1 $0
echo 2 $1
echo 3 $text
sleep 5

Running on OS X 10.10.5

Please include the Platypus settings you used.

Platypus apps run the script once when the application is launched, and again whenever you drop text on the app. So you can check whether there's something in stdin, and if not, you know that the script is not being launched as a response to a drag event.

authors: felixdreinulldrei sveinbjornt tewe

repo: sveinbjornt/Platypus


text:
Cannot use import statement outside a module

This is a followup on #2161. This issue had been fixed, but it was reintroduced in the latest sveltekit.
As asked, here is a reproduction: https://github.com/lovasoa/SvelteKit-2161
The stacktrace is
Cannot use import statement outside a module

/tmp/SvelteKit-2161/node_modules/@popperjs/core/dist/esm/popper.js:1
import { popperGenerator, detectOverflow } from "./createPopper.js";
^^^^^^

SyntaxError: Cannot use import statement outside a module
    at Object.compileFunction (node:vm:352:18)
    at wrapSafe (node:internal/modules/cjs/loader:1032:15)
    at Module._compile (node:internal/modules/cjs/loader:1067:27)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1155:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:168:29)
    at ModuleJob.run (node:internal/modules/esm/module_job:195:25)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:337:24)

@lovasoa can you file a new issue with a reproduction? I don't have a way to reproduce and investigate at the moment

Originally posted by @benmccann in https://github.com/sveltejs/kit/issues/2161#issuecomment-1085851247

+1. Breaking my build too.  Very annoying and may have to rip out Sveltestrap, which depends on it, which would make me have to look for a different framework.  This has to get fixed somehow.

I'm not sure why this changed, but the sveltestrap package has been broken for a long time and it'd be nice to get https://github.com/bestguy/sveltestrap/pull/356 merged to fix it

The PR above you mention seems to break sveltestrap with sapper. Until the recent changes in sveltekit, the package worked in both sveltekit and sapper. It really sounds like something should be changed on sveltekit's side...

This is a bug in @popperjs/core — Node is behaving as it should. Popper should either

use an .mjs extension for all the modules in dist/esm/**/*.js, or
create a dist/esm/package.json with {"type":"module"}, or
(ideally) put {"type":"module"} in the root package.json

It should also declare its exports using the "exports" field in package.json.
As far as I can tell, the package has been superseded by floating-ui, which appears to do things differently, so maybe this is fixed already.
Either way, it can be worked around by populating Vite's ssr.noExternal config:
/** @type {import('@sveltejs/kit').Config} */
const config = {
  kit: {
    vite: {
      ssr: {
        noExternal: ['@popperjs/core']
      }
    }
  }
};

export default config;

It seems like the same happens with dayjs. noExternal: ['@popperjs/core', 'dayjs'] helps.

You can try dayjs 2.0 alpha as well since it will support ESM

@Rich-Harris Your above solution is no longer working with the latest sveltekit. Any ideas?
Adding "type": "module" to node_modules/@popperjs/core/package.json does work though as mentioned in https://github.com/bestguy/sveltestrap/issues/463#issuecomment-1073273816

I am also running into this with @sveltejs/kit@1.0.0-next.490 and @carbon/charts...
Cannot use import statement outside a module
/Users/nates/dev/shy-svelte/node_modules/@carbon/charts/interfaces/enums.js:1
import * as EventEnums from './events';
^^^^^^

vite.config.js...
/** @type {import('vite').UserConfig} */
const config = {
	build: {
		sourcemap: true
	},
	optimizeDeps: {
		include: ['@carbon/charts'],
		exclude: ['@carbon/telemetry']
	},
	plugins: [sveltekit()],
	server: {
		port: 3000,
		fs: {
			allow: ['..', '/api/file/']
		}
	},
	serviceWorker: {
		files: (filepath) => !/\.DS_Store/.test(filepath)
	},
	ssr: {
		noExternal: ['@carbon/charts', '@popperjs/core']
	}
}

export default config

@nstuyvesant Could you try removing @carbon/charts from optimizeDeps.include?
See a minimal SvelteKit example set-up.

I modified my vite.config.js it to...
/** @type {import('vite').UserConfig} */
const config = {
	build: {
		sourcemap: true
	},
	optimizeDeps: {
		// include: ['@carbon/charts'],
		exclude: ['@carbon/telemetry']
	},
	plugins: [sveltekit()],
	server: {
		port: 3000,
		fs: {
			allow: ['..', '/api/file/']
		}
	},
	serviceWorker: {
		files: (filepath) => !/\.DS_Store/.test(filepath)
	},
	ssr: {
		// noExternal: [production && '@carbon/charts'].filter(Boolean)
		noExternal: ['@carbon/charts', 'carbon-components', '@popperjs/core'] // doesn't help at all
	}
}

export default config

After that, I got a series of warnings related to failing to load source map for various parts of @carbon/charts then errors  like...
Not found: /node_modules/@carbon/src/interfaces/enums.js.map
Error: Not found: /node_modules/@carbon/src/interfaces/enums.js.map
    at resolve (file:///Users/nates/dev/shy-svelte/node_modules/@sveltejs/kit/src/runtime/server/index.js:267:13)
    at Object.handle (/Users/nates/dev/shy-svelte/src/hooks.server.ts:23:24)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async respond (file:///Users/nates/dev/shy-svelte/node_modules/@sveltejs/kit/src/runtime/server/index.js:295:20)
    at async file:///Users/nates/dev/shy-svelte/node_modules/@sveltejs/kit/src/exports/vite/dev/index.js:406:22
Not found: /node_modules/@carbon/src/interfaces/events.js.map
Error: Not found: /node_modules/@carbon/src/interfaces/events.js.map
    at resolve (file:///Users/nates/dev/shy-svelte/node_modules/@sveltejs/kit/src/runtime/server/index.js:267:13)
    at Object.handle (/Users/nates/dev/shy-svelte/src/hooks.server.ts:23:24)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async respond (file:///Users/nates/dev/shy-svelte/node_modules/@sveltejs/kit/src/runtime/server/index.js:295:20)
    at async file:///Users/nates/dev/shy-svelte/node_modules/@sveltejs/kit/src/exports/vite/dev/index.js:406:22
Not found: /node_modules/@carbon/src/interfaces/index.js.map
Error: Not found: /node_modules/@carbon/src/interfaces/index.js.map
    at resolve (file:///Users/nates/dev/shy-svelte/node_modules/@sveltejs/kit/src/runtime/server/index.js:267:13)
    at Object.handle (/Users/nates/dev/shy-svelte/src/hooks.server.ts:23:24)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async respond (file:///Users/nates/dev/shy-svelte/node_modules/@sveltejs/kit/src/runtime/server/index.js:295:20)
    at async file:///Users/nates/dev/shy-svelte/node_modules/@sveltejs/kit/src/exports/vite/dev/index.js:406:22
Not found: /node_modules/@carbon/src/interfaces/a11y.js.map
Error: Not found: /node_modules/@carbon/src/interfaces/a11y.js.map
    at resolve (file:///Users/nates/dev/shy-svelte/node_modules/@sveltejs/kit/src/runtime/server/index.js:267:13)
    at Object.handle (/Users/nates/dev/shy-svelte/src/hooks.server.ts:23:24)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async respond (file:///Users/nates/dev/shy-svelte/node_modules/@sveltejs/kit/src/runtime/server/index.js:295:20)
    at async file:///Users/nates/dev/shy-svelte/node_modules/@sveltejs/kit/src/exports/vite/dev/index.js:406:22
Not found: /node_modules/@carbon/src/configuration-non-customizable.js.map
Error: Not found: /node_modules/@carbon/src/configuration-non-customizable.js.map
    at resolve (file:///Users/nates/dev/shy-svelte/node_modules/@sveltejs/kit/src/runtime/server/index.js:267:13)
    at Object.handle (/Users/nates/dev/shy-svelte/src/hooks.server.ts:23:24)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async respond (file:///Users/nates/dev/shy-svelte/node_modules/@sveltejs/kit/src/runtime/server/index.js:295:20)
    at async file:///Users/nates/dev/shy-svelte/node_modules/@sveltejs/kit/src/exports/vite/dev/index.js:406:22
Not found: /node_modules/@carbon/src/configuration.js.map
Error: Not found: /node_modules/@carbon/src/configuration.js.map
    at resolve (file:///Users/nates/dev/shy-svelte/node_modules/@sveltejs/kit/src/runtime/server/index.js:267:13)
    at Object.handle (/Users/nates/dev/shy-svelte/src/hooks.server.ts:23:24)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async respond (file:///Users/nates/dev/shy-svelte/node_modules/@sveltejs/kit/src/runtime/server/index.js:295:20)
    at async file:///Users/nates/dev/shy-svelte/node_modules/@sveltejs/kit/src/exports/vite/dev/index.js:406:22
Not found: /node_modules/@carbon/src/tools.js.map
Error: Not found: /node_modules/@carbon/src/tools.js.map
    at resolve (file:///Users/nates/dev/shy-svelte/node_modules/@sveltejs/kit/src/runtime/server/index.js:267:13)
    at Object.handle (/Users/nates/dev/shy-svelte/src/hooks.server.ts:23:24)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async respond (file:///Users/nates/dev/shy-svelte/node_modules/@sveltejs/kit/src/runtime/server/index.js:295:20)
    at async file:///Users/nates/dev/shy-svelte/node_modules/@sveltejs/kit/src/exports/vite/dev/index.js:406:22

I think my problem is that my component attempts to use Carbon Chart's enums...
	import type { LineChartOptions, DonutChartOptions } from '@carbon/charts/interfaces'
	import { Alignments, ScaleTypes } from '@carbon/charts/interfaces/enums'

I'll try copying them into a file inside of my project.

Dropping the import of the two enums solved the problem but I had to redefine them locally.

@Rich-Harris Your above solution is no longer working with the latest sveltekit, even when moving it to vite.config.js.

It works after cutting kite >  vite nesting. Fixed @mobily/ts-belt incompatibility for me:
vite.config.ts
export default defineConfig({
  ...
  ssr: {
    noExternal: ['@mobily/ts-belt'] // !!!
  }
})

Dropping the import of the two enums solved the problem but I had to redefine them locally.

Since my earlier comment on this issue, I've made extensive changes to @carbon/charts and @carbon/charts-svelte that resolved my earlier issues.

authors: Rich-Harris benallfree benmccann ivan-kleshnin king612 kjeske lovasoa metonym nstuyvesant

repo: sveltejs/kit


text:
Conditional configuration in vite.config.js breaks prod build

Describe the bug
If your vite.config.js uses conditional configuration, Svelte stops trying to compile components files to JS during SSR, and the resulting build fails because Rollup/Acorn is trying to parse Svelte files as JS.
Reproduction
https://stackblitz.com/edit/sveltejs-kit-template-default-4wrfgp
Logs
❯ npm run build
$ vite build
vite v2.9.13 building for production...
✓ 34 modules transformed.
.svelte-kit/output/client/_app/immutable/assets/svelte-logo-87df40b8.svg                           1.85 KiB
.svelte-kit/output/client/_app/immutable/assets/fira-mono-cyrillic-ext-400-normal-3df7909e.woff2   15.40 KiB
.svelte-kit/output/client/_app/immutable/assets/fira-mono-cyrillic-400-normal-c7d433fd.woff2       8.89 KiB
.svelte-kit/output/client/_app/immutable/assets/fira-mono-greek-ext-400-normal-9e2fe623.woff2      7.33 KiB
.svelte-kit/output/client/_app/immutable/assets/fira-mono-greek-400-normal-a8be01ce.woff2          10.27 KiB
.svelte-kit/output/client/_app/immutable/assets/fira-mono-latin-ext-400-normal-6bfabd30.woff2      11.10 KiB
.svelte-kit/output/client/_app/immutable/assets/fira-mono-latin-400-normal-e43b3538.woff2          15.90 KiB
.svelte-kit/output/client/_app/immutable/assets/fira-mono-all-400-normal-1e3b098c.woff             75.55 KiB
.svelte-kit/output/client/_app/immutable/manifest.json                                             2.67 KiB
.svelte-kit/output/client/_app/immutable/start-ab798b44.js                                         23.25 KiB / gzip: 8.72 KiB
.svelte-kit/output/client/_app/immutable/pages/__layout.svelte-f0707ee1.js                         4.77 KiB / gzip: 1.86 KiB
.svelte-kit/output/client/_app/immutable/error.svelte-c8df2b3e.js                                  1.56 KiB / gzip: 0.75 KiB
.svelte-kit/output/client/_app/immutable/pages/about.svelte-692f0ea0.js                            2.51 KiB / gzip: 1.15 KiB
.svelte-kit/output/client/_app/immutable/pages/index.svelte-471ba9cf.js                            5.47 KiB / gzip: 2.42 KiB
.svelte-kit/output/client/_app/immutable/pages/todos/index.svelte-dda24c9b.js                      6.86 KiB / gzip: 2.89 KiB
.svelte-kit/output/client/_app/immutable/chunks/index-9fe72fd8.js                                  11.81 KiB / gzip: 5.02 KiB
.svelte-kit/output/client/_app/immutable/chunks/index-92d65ea7.js                                  0.43 KiB / gzip: 0.30 KiB
.svelte-kit/output/client/_app/immutable/chunks/singletons-d1fb5791.js                             0.05 KiB / gzip: 0.07 KiB
.svelte-kit/output/client/_app/immutable/assets/pages/__layout.svelte-da7c5ce3.css                 5.08 KiB / gzip: 1.56 KiB
.svelte-kit/output/client/_app/immutable/assets/pages/about.svelte-bf4528fa.css                    0.11 KiB / gzip: 0.10 KiB
.svelte-kit/output/client/_app/immutable/assets/pages/index.svelte-e12bfb09.css                    1.45 KiB / gzip: 0.52 KiB
.svelte-kit/output/client/_app/immutable/assets/pages/todos/index.svelte-a910a02d.css              3.70 KiB / gzip: 1.03 KiB
vite v2.9.13 building SSR bundle for production...
✓ 0 modules transformed.
transforming (1) .svelte-kit/build/index.js[rollup-plugin-dynamic-import-variables] Unexpected token (1:0)
file: /home/projects/sveltejs-kit-template-default-4wrfgp/src/routes/__layout.svelte:1:0
[vite-plugin-svelte-kit] Unexpected token (1:0)
file: /home/projects/sveltejs-kit-template-default-4wrfgp/src/routes/__layout.svelte:1:0

System Info
  System:
    OS: Linux 5.0 undefined
    CPU: (4) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 16.14.2 - /usr/local/bin/node
    Yarn: 1.22.10 - /bin/yarn
    npm: 7.17.0 - /bin/npm
  npmPackages:
    @sveltejs/adapter-auto: next => 1.0.0-next.53
    @sveltejs/kit: next => 1.0.0-next.359
    svelte: ^3.46.0 => 3.48.0
    vite: ^2.9.13 => 2.9.13

Severity
blocking an upgrade
Additional Information
No response

The second argument configEnv to the config method in the Vite plugin object needs to find its way into the different places the get_vite_config is called from, and we need to use the configEnv if vite.config.js exports a function.

Actually, @benmccann is there a reason that build_server.js and build_service_worker.js try to manually load the Vite config at all? Couldn't they just be passed the config argument that's already passed to the config method in the Vite plugin? It looks like this already takes care of the config resolution for us, including calling the function with the ConfigEnv value if the config exports a function.

Actually, @benmccann is there a reason that build_server.js and build_service_worker.js try to manually load the Vite config at all? Couldn't they just be passed the config argument that's already passed to the config method in the Vite plugin?

Sadly not. An older version did that, which led to issues. See https://github.com/sveltejs/kit/issues/5308

Bummer. All right, I've opened a PR that keeps the get_vite_config function but now passes it a vite_config_env object.

authors: Conduitry benmccann


text:
As of @sveltejs/kit@1.0.13, getting build errors loading JSON from environmental variables

Describe the bug
After bumping @sveltejs/kit from 1.0.12 to 1.0.13 (with no other code changes), running rpm run build started throwing errors toward the end of outputting chunks (see logs below). Reverting to 1.0.12 causes the build to work again.
Reproduction
The error referenced is the third line here:
import { e as env } from "./env-private.js";
const { GOOGLE_RECAPTCHA_SECRET } = env;
const BRAINTREE_DESCRIPTOR = JSON.parse(env.BRAINTREE_DESCRIPTOR || "");

This is what that environmental variable looks like:
BRAINTREE_DESCRIPTOR={"name": "SH YYYY*Class Workshop", "phone": "212-555-1212", "url": "example.com"}

The first line of the code above in the original source is:
import { env } from '$env/dynamic/private'

Logs
> shy-svelte@3.0.4 build
> vite build

vite v4.0.4 building for production...

✓ 1784 modules transformed.
7:31:48 AM [vite-plugin-svelte] dom compile done.
package   	files	 time	   avg
shy-svelte	   94	1.50s	16.0ms

vite v4.0.4 building SSR bundle for production...
✓ 435 modules transformed.
7:16:32 AM [vite-plugin-svelte] ssr compile done.
package   	files	 time	  avg
shy-svelte	   94	0.29s	3.1ms
.svelte-kit/output/server/vite-manifest.json                                             25.42 kB
.svelte-kit/output/server/chunks/prod-ssr.js                                              0.12 kB │ map:     0.23 kB
.svelte-kit/output/server/entries/pages/auth/reset/_token_/_page.ts.js                    0.14 kB │ map:     0.38 kB
.svelte-kit/output/server/entries/pages/_layout.server.ts.js                              0.15 kB │ map:     0.48 kB
.svelte-kit/output/server/entries/pages/classes/_locationId_/_page.ts.js                  0.15 kB │ map:     0.41 kB
.svelte-kit/output/server/chunks/env-private.js                                           0.16 kB │ map:     0.38 kB
.svelte-kit/output/server/internal.js                                                     0.18 kB │ map:     0.09 kB
.svelte-kit/output/server/entries/endpoints/api/announcement/active.json/_server.ts.js    0.20 kB │ map:     0.47 kB
.svelte-kit/output/server/entries/pages/register/_page.server.ts.js                       0.21 kB │ map:     0.50 kB
.svelte-kit/output/server/entries/endpoints/api/class/_server.ts.js                       0.22 kB │ map:     0.49 kB
.svelte-kit/output/server/entries/endpoints/api/product/_server.ts.js                     0.22 kB │ map:     0.50 kB
.svelte-kit/output/server/entries/endpoints/api/user/_id_/_server.ts.js                   0.22 kB │ map:     0.49 kB
.svelte-kit/output/server/entries/endpoints/api/location/_server.ts.js                    0.23 kB │ map:     0.51 kB
.svelte-kit/output/server/entries/endpoints/api/workshop/_server.ts.js                    0.23 kB │ map:     0.51 kB
.svelte-kit/output/server/entries/endpoints/api/class/_id_/_server.ts.js                  0.23 kB │ map:     0.50 kB
.svelte-kit/output/server/entries/endpoints/api/product/_id_/_server.ts.js                0.23 kB │ map:     0.50 kB
.svelte-kit/output/server/entries/endpoints/api/location/_id_/_server.ts.js               0.23 kB │ map:     0.51 kB
.svelte-kit/output/server/entries/endpoints/api/workshop/_id_/_server.ts.js               0.23 kB │ map:     0.51 kB
.svelte-kit/output/server/entries/endpoints/api/announcement/_server.ts.js                0.23 kB │ map:     0.52 kB
.svelte-kit/output/server/entries/pages/checkout/_page.ts.js                              0.23 kB │ map:     0.53 kB
.svelte-kit/output/server/entries/endpoints/api/payment/order/_server.ts.js               0.24 kB │ map:     0.55 kB
.svelte-kit/output/server/entries/endpoints/api/schedule/_server.ts.js                    0.24 kB │ map:     0.53 kB
.svelte-kit/output/server/entries/endpoints/api/history/_server.ts.js                     0.24 kB │ map:     0.53 kB
.svelte-kit/output/server/entries/endpoints/api/announcement/_id_/_server.ts.js           0.24 kB │ map:     0.53 kB
.svelte-kit/output/server/entries/endpoints/api/product/_id_.json/_server.ts.js           0.24 kB │ map:     0.53 kB
.svelte-kit/output/server/entries/endpoints/api/location/_id_.json/_server.ts.js          0.24 kB │ map:     0.53 kB
.svelte-kit/output/server/entries/endpoints/api/user/_id_.json/_server.ts.js              0.24 kB │ map:     0.53 kB
.svelte-kit/output/server/entries/endpoints/api/workshop/_id_.json/_server.ts.js          0.24 kB │ map:     0.53 kB
.svelte-kit/output/server/entries/endpoints/api/schedule/_id_/_server.ts.js               0.24 kB │ map:     0.52 kB
.svelte-kit/output/server/entries/endpoints/api/class/_id_.json/_server.ts.js             0.25 kB │ map:     0.53 kB
.svelte-kit/output/server/entries/endpoints/api/schedule/_id_.json/_server.ts.js          0.25 kB │ map:     0.54 kB
.svelte-kit/output/server/entries/endpoints/api/announcement/_id_.json/_server.ts.js      0.25 kB │ map:     0.56 kB
.svelte-kit/output/server/entries/pages/reserve/_page.server.ts.js                        0.26 kB │ map:     0.53 kB
.svelte-kit/output/server/entries/endpoints/api/payment/_id_.json/_server.ts.js           0.28 kB │ map:     0.56 kB
.svelte-kit/output/server/entries/pages/_page.ts.js                                       0.33 kB │ map:     0.69 kB
.svelte-kit/output/server/chunks/db.js                                                    0.34 kB │ map:     0.90 kB
.svelte-kit/output/server/entries/pages/profile/_page.server.ts.js                        0.38 kB │ map:     0.78 kB
.svelte-kit/output/server/entries/pages/_layout.ts.js                                     0.39 kB │ map:     0.88 kB
.svelte-kit/output/server/entries/pages/classes/_page.svelte.js                           0.39 kB │ map:     0.10 kB
.svelte-kit/output/server/entries/pages/shynet/_page.ts.js                                0.42 kB │ map:     0.80 kB
.svelte-kit/output/server/entries/pages/admin/_page.ts.js                                 0.44 kB │ map:     0.84 kB
.svelte-kit/output/server/chunks/history.js                                               0.44 kB │ map:     0.72 kB
.svelte-kit/output/server/entries/endpoints/api/teacher/current.json/_server.ts.js        0.47 kB │ map:     0.85 kB
.svelte-kit/output/server/entries/endpoints/api/unsubscribe/_email_/_server.ts.js         0.49 kB │ map:     0.86 kB
.svelte-kit/output/server/entries/endpoints/api/master/admin.json/_server.ts.js           0.50 kB │ map:     0.90 kB
.svelte-kit/output/server/chunks/stores.js                                                0.50 kB │ map:     1.80 kB
.svelte-kit/output/server/entries/pages/_error.svelte.js                                  0.52 kB │ map:     0.33 kB
.svelte-kit/output/server/entries/endpoints/api/user/merge/_server.ts.js                  0.53 kB │ map:     1.01 kB
.svelte-kit/output/server/entries/endpoints/api/master/active.json/_server.ts.js          0.54 kB │ map:     0.89 kB
.svelte-kit/output/server/entries/endpoints/api/subscribe/_server.ts.js                   0.54 kB │ map:     0.92 kB
.svelte-kit/output/server/entries/endpoints/api/payment/search.json/_server.ts.js         0.56 kB │ map:     1.05 kB
.svelte-kit/output/server/entries/endpoints/api/class/search.json/_server.ts.js           0.56 kB │ map:     1.05 kB
.svelte-kit/output/server/entries/endpoints/api/product/search.json/_server.ts.js         0.56 kB │ map:     1.05 kB
.svelte-kit/output/server/entries/endpoints/api/location/search.json/_server.ts.js        0.56 kB │ map:     1.06 kB
.svelte-kit/output/server/entries/endpoints/api/workshop/search.json/_server.ts.js        0.56 kB │ map:     1.06 kB
.svelte-kit/output/server/entries/endpoints/api/announcement/search.json/_server.ts.js    0.56 kB │ map:     1.07 kB
.svelte-kit/output/server/entries/pages/classes/_locationId_/_page.svelte.js              0.56 kB │ map:     0.42 kB
.svelte-kit/output/server/entries/endpoints/api/schedule/search.json/_server.ts.js        0.56 kB │ map:     1.07 kB
.svelte-kit/output/server/entries/endpoints/api/history/_what_-_id_.json/_server.ts.js    0.57 kB │ map:     1.05 kB
.svelte-kit/output/server/entries/endpoints/api/history/_what_-_id_/_server.ts.js         0.57 kB │ map:     1.05 kB
.svelte-kit/output/server/entries/endpoints/api/user/search.json/_server.ts.js            0.58 kB │ map:     1.08 kB
.svelte-kit/output/server/chunks/config.js                                                0.58 kB │ map:     0.61 kB
.svelte-kit/output/server/chunks/hooks.server.js                                          0.61 kB │ map:     1.45 kB
.svelte-kit/output/server/entries/endpoints/api/file/_server.ts.js                        0.62 kB │ map:     1.14 kB
.svelte-kit/output/server/entries/endpoints/api/file/_filenum_/_server.ts.js              0.66 kB │ map:     1.21 kB
.svelte-kit/output/server/chunks/user.js                                                  0.67 kB │ map:     1.22 kB
.svelte-kit/output/server/entries/endpoints/api/history/me.json/_server.ts.js             0.68 kB │ map:     1.26 kB
.svelte-kit/output/server/entries/endpoints/api/history/search.json/_server.ts.js         0.73 kB │ map:     1.34 kB
.svelte-kit/output/server/entries/endpoints/api/message/_server.ts.js                     0.77 kB │ map:     1.39 kB
.svelte-kit/output/server/entries/endpoints/auth/reset/_server.ts.js                      0.82 kB │ map:     1.50 kB
.svelte-kit/output/server/entries/endpoints/auth/forgot/_server.ts.js                     1.11 kB │ map:     2.05 kB
.svelte-kit/output/server/entries/endpoints/api/attendance/search.json/_server.ts.js      1.18 kB │ map:     2.08 kB
.svelte-kit/output/server/chunks/enums.js                                                 1.28 kB │ map:     1.32 kB
.svelte-kit/output/server/chunks/stores2.js                                               1.30 kB │ map:     3.09 kB
.svelte-kit/output/server/chunks/index2.js                                                1.35 kB │ map:     4.32 kB
.svelte-kit/output/server/entries/pages/teachers/_page.svelte.js                          1.39 kB │ map:     1.31 kB
.svelte-kit/output/server/chunks/sendgrid.js                                              1.41 kB │ map:     2.52 kB
.svelte-kit/output/server/chunks/AddToCart.js                                             1.57 kB │ map:     1.56 kB
.svelte-kit/output/server/entries/endpoints/api/user/_server.ts.js                        1.61 kB │ map:     2.90 kB
.svelte-kit/output/server/entries/pages/forgot/_page.svelte.js                            1.64 kB │ map:     2.75 kB
.svelte-kit/output/server/entries/pages/merge/_page.svelte.js                             1.96 kB │ map:     3.01 kB
.svelte-kit/output/server/entries/endpoints/auth/google/_server.ts.js                     1.97 kB │ map:     3.64 kB
.svelte-kit/output/server/entries/endpoints/auth/_operation_/_server.ts.js                1.99 kB │ map:     3.74 kB
.svelte-kit/output/server/chunks/datetime.extensions.js                                   2.05 kB │ map:     4.48 kB
.svelte-kit/output/server/chunks/index.js                                                 2.19 kB │ map:     5.67 kB
.svelte-kit/output/server/entries/pages/auth/reset/_token_/_page.svelte.js                2.34 kB │ map:     3.83 kB
.svelte-kit/output/server/chunks/crud.js                                                  2.45 kB │ map:     4.64 kB
.svelte-kit/output/server/chunks/Paginator.js                                             2.56 kB │ map:     3.15 kB
.svelte-kit/output/server/entries/endpoints/api/history/reservation/_server.ts.js         2.65 kB │ map:     4.72 kB
.svelte-kit/output/server/entries/pages/teachertraining/_page.svelte.js                   2.77 kB │ map:     2.61 kB
.svelte-kit/output/server/entries/pages/history/_page.svelte.js                           2.92 kB │ map:     3.95 kB
.svelte-kit/output/server/entries/pages/login/_page.svelte.js                             3.13 kB │ map:     5.25 kB
.svelte-kit/output/server/chunks/CartEditor.js                                            3.18 kB │ map:    11.40 kB
.svelte-kit/output/server/entries/pages/reserve/_page.svelte.js                           3.19 kB │ map:     5.43 kB
.svelte-kit/output/server/entries/pages/register/_page.svelte.js                          3.58 kB │ map:     6.41 kB
.svelte-kit/output/server/entries/pages/confirmation/_page.svelte.js                      3.61 kB │ map:     4.43 kB
.svelte-kit/output/server/entries/pages/leta/_page.svelte.js                              3.61 kB │ map:     0.13 kB
.svelte-kit/output/server/entries/pages/privacy/_page.svelte.js                           3.69 kB │ map:     0.16 kB
.svelte-kit/output/server/entries/pages/profile/_page.svelte.js                           4.22 kB │ map:     6.35 kB
.svelte-kit/output/server/chunks/AddToCalendar.js                                         5.33 kB │ map:     5.83 kB
.svelte-kit/output/server/entries/pages/shynet/_page.svelte.js                            5.93 kB │ map:     8.52 kB
.svelte-kit/output/server/entries/pages/workshops/_page.svelte.js                         7.28 kB │ map:    10.41 kB
.svelte-kit/output/server/chunks/index3.js                                                8.07 kB │ map:    86.24 kB
.svelte-kit/output/server/entries/pages/terms/_page.svelte.js                             8.98 kB │ map:     0.24 kB
.svelte-kit/output/server/entries/pages/_page.svelte.js                                   9.12 kB │ map:     6.87 kB
.svelte-kit/output/server/entries/pages/checkout/_page.svelte.js                          9.31 kB │ map:    26.50 kB
.svelte-kit/output/server/chunks/payment.js                                              11.37 kB │ map:    18.59 kB
.svelte-kit/output/server/chunks/server-internal.js                                      18.81 kB │ map:    27.44 kB
.svelte-kit/output/server/entries/pages/_layout.svelte.js                                23.21 kB │ map:    28.32 kB
.svelte-kit/output/server/chunks/Users.js                                                29.91 kB │ map:    45.56 kB
.svelte-kit/output/server/chunks/Classes.js                                              37.04 kB │ map:    55.54 kB
.svelte-kit/output/server/index.js                                                       76.12 kB │ map:   174.92 kB
.svelte-kit/output/server/entries/pages/admin/_page.svelte.js                           811.10 kB │ map: 1,628.12 kB
undefined:1

SyntaxError: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
    at file:///Users/nates/dev/shy-svelte/.svelte-kit/output/server/chunks/payment.js:7:35
    at ModuleJob.run (node:internal/modules/esm/module_job:194:25)

Node.js v18.13.0
[vite-plugin-sveltekit-compile] Prerendering failed with code 1
error during build:
Error: Prerendering failed with code 1
    at ChildProcess.<anonymous> (file:///Users/nates/dev/shy-svelte/node_modules/@sveltejs/kit/src/exports/vite/index.js:629:15)
    at ChildProcess.emit (node:events:513:28)
    at ChildProcess._handle.onexit (node:internal/child_process:291:12)

### System Info

```Shell
System:
    OS: macOS 13.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 386.08 MB / 32.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.13.0 - /opt/homebrew/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 9.3.1 - /opt/homebrew/bin/npm
  Browsers:
    Chrome: 109.0.5414.87
    Firefox: 108.0.2
    Safari: 16.2
  npmPackages:
    @sveltejs/adapter-node: ^1.1.4 => 1.1.4
    @sveltejs/kit: 1.2.2 => 1.2.2
    svelte: ^3.55.1 => 3.55.1
    vite: ^4.0.4 => 4.0.4

Severity
blocking an upgrade
Additional Information
No response

Please provide a complete reproduction.
Also, does this also happen with the latest version of SvelteKit?

Here's a complete repro using the SvelteKit skeleton...
https://github.com/nstuyvesant/issue-8646
It happens with the latest SvelteKit (1.2.2 as of this writing) and any version from 1.0.13 on.

I should also mention that npm run dev - no problems.

authors: Conduitry nstuyvesant


text:
introduce devPlatform kit configuration

Hello :wave:
The changes here introduce a devPlatform option for the kit config so that developers can provide their own platform mocking implementation for local development.
Given the conversation in #4292, @rich-harris' pushback), #3535, #8397, and so on... I am aware that the changes here might just get rejected but I wanted to propose them anyways as I think that this could be a valid short/medium term solution that many developers could take advantage of right now (instead of making them indefinitely wait for a better solution that might or might not come at some point in the future).
From an outsider's perspective and the issues I mentioned above (which seem pretty stale) I don't know what the Svelte team's current plan is regarding this issue, if you have a different/better solution in the works that can be applied soon-ish that'd be awesome, but if you don't please give this PR's a second thought since this clearly seems to be an issue that various developers struggle with. Moreover please note that the changes here are pretty minimal so they should be very simple to deprecate/remove in the future if a better alternative does get implemented.
As an example of the use of this devPlatform config, I've implemented this simple demo which shows how this could be used to locally develop an application using a Cloudflare KV binding, you can see here how the devPlatform is being set and here how it is being used.
Currently the only alternative workaround that can allow developers to use bindings with the Vite dev server is by leveraging server hooks, I included an example of that here. As you can see this is much much more cumbersome than the proposed API and also effects the production build, so it's definitely not a great alternative in my opinion.
Additionally I'd like to point out that there's a precedence of such an API, QwikCity is actually doing the exact same thing in their Vite plugin (see their docs), showing that even if not perfect this seems to be an acceptable solution for this problem.

resolves #4292
(also #4908, and maybe more)

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[ ] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[ ] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[ ] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

This would be great

Yeah, I agree, this doesn't feel like the right API. Until we figure out how we want to have adapters affect dev mode, I think the best option is to have a handle hook that does some assignments in an if (dev) { ... }, as mentioned in the PR description. This gets treeshaken out of production builds. It seems like an entirely acceptable workaround to me.

This feels like the wrong API to me. I think it'd be better if the adapter could be used to provide the platform in dev mode as well

@benmccann are saying that you'd be ok with this approach if I moved the devPlatform to be part of an adaptor config instead? or are you saying that this feels like the wrong approach/API full stop?

Yeah, I agree, this doesn't feel like the right API. Until we figure out how we want to have adapters affect dev mode, I think the best option is to have a handle hook that does some assignments in an if (dev) { ... }, as mentioned in the PR description. This gets treeshaken out of production builds. It seems like an entirely acceptable workaround to me.

As I also mentioned in the PR description, I do agree with you saying that there might be a better solution on how adapters should effect dev mode as a whole, what I am questioning here is: when is that solution going to be implemented? any time soon? if not, wouldn't it be nice to provide a valid stopgap easily-removable/deprecatable solution that can help solving the issue right now?
Regarding the handle solution again I kind of do agree with you that it is a kind of acceptable but it does still required developers to implement this hands-on hack which does have (even if minimal) implications in the production build (since the dev code can be tree shaken away but the handle itself cannot).
Basically what I'm trying to ask here is, are the benefits of implementing such a change outweighed by the cons?

Thinking about what the implementation will look like for some of that stuff, it's probably quite finicky and involves a lot of knowledge of the internals, so if you're cool with it @dario-piotrowicz then maybe it's more logical for us to pick it up from here? Appreciate all the work that you've put into it so far!

I've made a start in https://github.com/sveltejs/kit/pull/11730, though there are a few TODOs and open questions still outstanding

@Rich-Harris Thanks so much for looking into this 🙂
We on the Cloudflare team are really keen and hopeful to get this sort of dev bindings support ready as soon as we can. We're also working with other framework authors to apply the same across the whole js ecosystem.
Whatever you think it's best, both for your framework and for hopefully expedite this feature's implementation works for us, and we're always happy to keep working on this and/or support in any other way we can.
So yeah please feel free to take it over if you want, but I am always here to pick it back up and/or help in any manner I can.

Thank you @dario-piotrowicz! If you have any pointers on how to populate caches and context, and how to test it locally (see notes on the other PR), we'd be very grateful. Also, is it okay that we're not calling bindings.dispose but are just killing the process?

Probably a useless comment here that you are all already aware of, but wrangler-proxy is a great example of how to use wrangler in development for SK - but I thought it might help 🤷♂

authors: Conduitry Rich-Harris dario-piotrowicz saturnonearth


text:
Add generic type for session

Previously, in Sapper, we could use generics to ensure our session type was used correctly:
E.g. if I had a session type that was { foo: string; }
import { stores } from "@sapper/app";

const { session } = stores<MySessionType>();

$session.foo; // correct usage
$session.bar; // invalid, compiler shows error

This PR adds the same generic support in getStores as well as a 3rd param in the generic for LoadInput
SvelteKit:
import { getStores } from "$app/stores";

const { session } = getStores<MySessionType>();

Before submitting the PR, please make sure you do the following

[ ] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[x] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[x] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpx changeset and following the prompts

@dummdidumm GrygrFlzr pointed out on Discord that this PR doesn't help with this:
import { session } from '$app/stores';

I wonder if there's anything we could do here?
I had a quick search and found this https://stackoverflow.com/questions/42986950/how-to-define-import-variable-type
i.e. update your own ambient type per project, something like this:
declare module "$app/stores" {
    const session : MySessionType;
    export = session;
}

If that's the only solution, perhaps it should be documented?

That seems like a useful addition, but I wouldn't add it to the site docs, only to the jsdoc in the ambient-modules.d.ts file

Odd. I just tested this in the example project.
In a component:
<script lang="ts">
  import { session } from "$app/stores";
</script>

<div>{$session.fo}</div>

This doesn't work, VSCode thinks session in the component is Writable<any>
/// <reference types="@sveltejs/kit" />

declare module "$app/stores" {
  import type { Writable } from "svelte/store";

  export const session: Writable<{ foo: string; bar: string }>;
}

However, if I remove the reference it all works and VSCode picks up the error.
Does this line actually need to be included?
/// <reference types="@sveltejs/kit" />

Yes it needs to be included, else other imports from $.. and .svelte imports in TS components are no longer recognized by TypeScript (giving false positives). My guess is that the broader type wins here, since both definitions are loaded, so this approach won't work. If people really want session to be a certain writable, I guess they have to do something like export const myTypedSession: Writable<SomeInterface> = session. But I wouldn't add this to the docs then.

I'm prob missing something. Why doesn't SvelteKit propagate the return type of getSession from src/hooks.ts?
I have
// src/hooks.ts

export function getSession(): Record<string, string> {
  // ...
  return session
}

yet when I import
import { session } from '$app/stores'

it has type
(alias) const session: Writable<any>

authors: dummdidumm janosh seanlail


text:
Allow service workers to import assets

#9256. I don't know if this is a good idea or not but thought I'd try. Basically, build.lib always results in a single JavaScript file with everything inlined, whereas build.rollupOptions gives us more flexibility. But I'm not sure if it creates other problems. For example, a dynamic import(...) will be inlined at the moment; with this PR it will keep the dynamic import (which won't work in a non-module service worker, and we can't use module service workers yet) and will inject Vite's module preloading logic, which won't work because it references document.
There might be a combination of configuration options that gives us the bits we need without the bits we don't — for now I'm just going to leave this here
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[ ] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[ ] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[ ] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[ ] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

and will inject Vite's module preloading logic, which won't work because it references document.

Vite has an option to disable that I believe. I also thought I'd mention that the PWA plugin just calls Rollup directly to build their service worker and doesn't use Vite to do it, so that's potentially another option - although it means options from the vite.config.js won't get used in that build, so I'm not necessarily sure it's better

Options from vite.config.js (apart from define) already don't get used, because in general they don't make sense in this context. But using Rollup would mean we needed to add support for define and TypeScript and probably other things, so I'm not sure it's worth it unless absolutely necessary

Vite has an option to disable that I believe

Any idea what it's called? I can't find it

Oh, interesting, I thought that only related to <link rel="modulepreload">. Somewhat surprised that they're controlled by the same option. Tried it, it works

This should get a test but that'll be easier after merging #9250, so it can use the same mechanism

Added a test, I think this is ready to go

For example, a dynamic import(...) will be inlined at the moment; with this PR it will keep the dynamic import

Can we set a rollup option to inline the dynamic import? I imagine that's what lib is doing under the covers

that was done in a34f855d481634e263faa75bf3d44728de57f5b1

authors: Rich-Harris benmccann


text:
Warnings caused by missing newlines in exhale output

I'm getting lots of warnings like the following when I build my docs:
/path/to/source/exhale/file_src_helpers.hh.rst:10: WARNING: Explicit markup ends without a blank line; unexpected unindent.
The file generated by exhale looks like this:
.. _file_src_helpers.hh:

File helpers.hh
===============

|exhale_lsh| :ref:`Parent directory <dir_src>` (``src``)

.. |exhale_lsh| unicode:: U+021B0 .. UPWARDS ARROW WITH TIP LEFTWARDS
Definition (``src/helpers.hh``)
-------------------------------

I think Sphinx just wants an empty line before that subheading "Definition". Looking at the exhale source, there are only 3 places where a line with the U+021B0 character is generated; one has that extra newline, and two don't. As a quick fix, I added another newline to the ones that didn't have it, but there could easily be something more subtle going on here.
I know it's just a warning, and the docs end up just fine either way. On the other hand, having a bunch of warnings that don't "mean" anything makes it much more difficult to pick out the ones I should actually fix.
Please let me know if I can help with debugging this.

Thanks for reporting @emprice, this is definitely a bug!  The tests don't really catch this scenario, but what you describe above should not be what is generated.  Can you check that #172 fixes these warnings for you please?  Assuming things are good I'll do a quick release :slightly_smiling_face:

I just regenerated my docs, and #172 does appear to fix all those spurious warnings for me. Thanks so much for the quick fix, @svenevs!

Awesome, thanks for confirming!  v0.3.5 is on pypi now :slightly_smiling_face:

authors: emprice svenevs

repo: svenevs/exhale