text:
Issue 1500: Use the built-in formatting in logging methods

Pull Request Description
This pull request closes #1500
Acceptance Test

[X] Building the code with mvn clean install -Dintegration.tests still works.
[X] Running mvn spring-boot:run in the strongbox-web-core still starts up the application correctly.
[X] Building the code and running the strongbox-distribution from a zip or tar.gz still works.
[X] The tests in the strongbox-web-integration-tests still run properly.

Questions

Does this pull request break backward compatibility?

[ ] Yes
[X] No

Does this pull request require other pull requests to be merged first?

[ ] Yes, please see #...
[X] No

Does this require an update of the documentation?

[ ] Yes, please see strongbox/strongbox-docs#{PR_NUMBER}
[X] No

Hi @raksit31667 !
Thank you for your contribution!
Would you mind signing the ICLA, as described in the Contributing page?
Also, please, feel free to join our chat channel, if you'd like to learn more about the project and/or like to find out what else you could help with.
Kind regards,
Martin

@raksit31667 ,
Thanks for signing the ICLA!
@ptirador ,
Would you like to review this? :)

repo: strongbox/strongbox


text:
Command Groups

Hey, I've tested your Help command and I had one problem, when I added a command group, the bot just put the typing status and after that nothing happens, after I removed the command group all was working again. I checked the Cog, if there was any mistake in it, but no. So let me know, if it is my fault or the one from the help command.

Oh, i found the error was a mistake from my site.

source: gharchive/issue

repo: stroupbslayen/discord-pretty-help

license: MIT

license_type: permissive

license_source: github-api


text:
Migrate global datepicker_options into Datepicker component, limit jQuery UI imports

Who is this PR for?
developers
What problem does this PR fix?
It's a step towards https://github.com/studentinsights/studentinsights/issues/1758.  This came up as I was looking to see what it would take to upgrade to jQuery 3.x, since Firefox raises CSP violations on load for jQuery 1.12.x.
What does this PR do?
Removes two global bits that <Datepicker /> relied on - window.datepicker_options and an asset path sent down in application.html.erb.  Also scopes down the sprockets imports for jQuery UI.

selfie

source: gharchive/pull-request

repo: studentinsights/studentinsights

license: mit

license_source: bigquery


text:
Profile: Allow showing MCAS in summary if no STAR, remove SGP graphs if no data

Who is this PR for?
Bedford educators
What problem does this PR fix?
In Bedford, they don't use STAR assessments, but the profile still assumes these are meaningful.
Separately, there's no SGP data for students in younger grades (or other students taking MCAS for the first time).  Yet these charts still appear.
What does this PR do?
Adds a PerDistrict.js function that enables showing MCAS in place of STAR for the summary tabs on the student profile.
Updates the details sections to hide the SGP charts if there is no data.
Screenshot (if adding a client-side feature)

Checklists
Which features or pages does this PR touch?

[x] Student Profile

Does this PR use tests to help verify we can deploy these changes quickly and confidently?

[x] Included specs for changes
[x] Manual testing made more sense here

selfie


text:
Remove eager includes from schools_controller

These aren't needed on the precomputed path, so are probably pulling in more data than is needed.

Tests pass locally and kevin says 🚢

authors: alexsoble kevinrobinson


text:
20200205 Go: Image Rendering in 2D Video Games with Ebiten

标题：Go: Image Rendering in 2D Video Games with Ebiten
原文链接：https://medium.com/a-journey-with-go/go-image-rendering-in-2d-video-games-with-ebiten-912cc2360c4f
译者自己根据原文翻译，译文保存为 markdown 格式，并附上尾部的签名。
---
via: https://medium.com/a-journey-with-go/go-image-rendering-in-2d-video-games-with-ebiten-912cc2360c4f

作者：[Vincent Blanchon](https://medium.com/@blanchon.vincent)
译者：[译者ID](https://github.com/译者ID)
校对：[校对者ID](https://github.com/校对者ID)

本文由 [GCTT](https://github.com/studygolang/GCTT) 原创编译，[Go 中文网](https://studygolang.com/) 荣誉推出

翻译 by alandtsang

repo: studygolang/GCTT


text:
Nuget包上面的目前是.Net Core和Framework，能不能改成.Net Standard？

Nuget包上面的目前是.Net Core和Framework，能不能改成.Net Standard？

.net standard 请使用以前的版本，.net core 3.0+ 元包机制的更改，无法继续使用 .net standard

authors: stulzq xxdqr

repo: stulzq/IPTools


text:
manifest.json

This gem definitely, solved my problem in precompiling my assets with same fingerprinting to be deployed to multiple instances of app server code. I am however seeing a side effect when trying to redeploy by seeing the following exception:
`parse': (<unknown>): mapping values are not allowed in this context at line 1 column 13 (Psych::SyntaxError)
	from /Users/hootan/.rvm/rubies/ruby-2.0.0-p451/lib/ruby/2.0.0/psych.rb:205:in `parse_stream'
	from /Users/hootan/.rvm/rubies/ruby-2.0.0-p451/lib/ruby/2.0.0/psych.rb:153:in `parse'
	from /Users/hootan/.rvm/rubies/ruby-2.0.0-p451/lib/ruby/2.0.0/psych.rb:129:in `load'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/recipes/deploy/assets.rb:26:in `parse_manifest'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/namespaces.rb:191:in `method_missing'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/namespaces.rb:191:in `method_missing'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/recipes/deploy/assets.rb:93:in `block (3 levels) in load'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/execution.rb:138:in `instance_eval'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/execution.rb:138:in `invoke_task_directly'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/callbacks.rb:25:in `invoke_task_directly_with_callbacks'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/execution.rb:89:in `execute_task'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/execution.rb:101:in `find_and_execute_task'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/callback.rb:38:in `call'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/callbacks.rb:141:in `block in trigger'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/callbacks.rb:141:in `each'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/callbacks.rb:141:in `trigger'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/callbacks.rb:23:in `invoke_task_directly_with_callbacks'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/execution.rb:89:in `execute_task'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/execution.rb:101:in `find_and_execute_task'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/callback.rb:38:in `call'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/callbacks.rb:141:in `block in trigger'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/callbacks.rb:141:in `each'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/callbacks.rb:141:in `trigger'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/callbacks.rb:27:in `invoke_task_directly_with_callbacks'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/execution.rb:89:in `execute_task'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/namespaces.rb:191:in `method_missing'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/namespaces.rb:110:in `block in define_task'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/recipes/deploy.rb:234:in `block (3 levels) in load'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/execution.rb:56:in `transaction'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/namespaces.rb:191:in `method_missing'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/recipes/deploy.rb:233:in `block (2 levels) in load'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/execution.rb:138:in `instance_eval'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/execution.rb:138:in `invoke_task_directly'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/callbacks.rb:25:in `invoke_task_directly_with_callbacks'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/execution.rb:89:in `execute_task'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/namespaces.rb:191:in `method_missing'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/namespaces.rb:110:in `block in define_task'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/recipes/deploy.rb:201:in `block (2 levels) in load'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/execution.rb:138:in `instance_eval'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/execution.rb:138:in `invoke_task_directly'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/callbacks.rb:25:in `invoke_task_directly_with_callbacks'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/execution.rb:89:in `execute_task'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/configuration/execution.rb:101:in `find_and_execute_task'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/cli/execute.rb:46:in `block in execute_requested_actions'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/cli/execute.rb:45:in `each'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/cli/execute.rb:45:in `execute_requested_actions'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/cli/help.rb:19:in `execute_requested_actions_with_help'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/cli/execute.rb:34:in `execute!'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/lib/capistrano/cli/execute.rb:14:in `execute'
	from /Users/hootan/.rvm/gems/ruby-2.0.0-p451@global/gems/capistrano-2.15.5/bin/cap:4:in `<top (required)>'
	from /Users/hootan/.rvm/rubies/ruby-2.0.0-p451/bin/cap:23:in `load'
	from /Users/hootan/.rvm/rubies/ruby-2.0.0-p451/bin/cap:23:in `<main>'

I removed manifest-.json from app/shared/assets folder and the redeploy works fine, but this is not practical to login to every single instance and remove. Is this a known problem ? please help.

This error occurs in :update_asset_mtimes if there is more than 1 manifest*.json in the shared_path/shared_assets_prefix.  The above fix should remove the manifest from this location instead.
I think we should change to:
    desc "remove manifest file from remote server"
    task :remove_manifest, roles: :web do
      run "rm -f #{shared_path}/#{shared_assets_prefix}/manifest*.json"
    end

Thanks @steakchaser, would you mind submitting a pull request?

+1
@stve Have you had a chance to take a look at the PR from @steakchaser ?

Nevermind. It looks like @steakchaser did submit that PR after all. The gem just hasn't been updated on rubygems.

authors: hootan-nikbakht nozpheratu steakchaser stve

repo: stve/capistrano-local-precompile


text:
🛑 Panel is down

In 80e5d17, Panel (https://portal.xoro-hosting.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Status is back up in 9b1b003 after 43 minutes.

repo: stxrlite/xoro-updates


text:
[EXCLUSIVE CLIP] Five Girls Five Rocket Viral Video

In the fast-paced world of social media, it doesn’t take long for a unique or intriguing clip to capture the imagination of millions. The latest phenomenon? The “Five Girls Five Rocket Viral Video”, a dazzling piece of content that has become an instant sensation across platforms. This video, which showcases a group of five girls performing a synchronized and visually stunning stunt involving five rockets, has sparked a frenzy of shares, discussions, and imitations worldwide.
🔴 ➤► WATCH THE VIDEO HERE✅👉 https://shorturl.at/H0aYQ (VideoLink)
🔴 ➤► WATCH THE VIDEO HERE✅👉 https://shorturl.at/H0aYQ (VideoLink)
What is the “Rocket Viral Video”?
The Rocket Viral Video features five young women showcasing a perfectly choreographed sequence involving rockets. While the exact origins of the video remain unclear, its captivating visuals and flawless execution have made it impossible for viewers to look away. Each girl holds a rocket, launching them in precise coordination, creating a jaw-dropping spectacle that combines science, artistry, and entertainment.
The synergy of the performers, their confidence, and the dramatic backdrop have made the 5 girls 5 rocket breakout video an unforgettable watch. From Instagram reels to TikTok duets, the video has become a cultural touchstone for creativity and teamwork.
The Rise of the “5 Rocket 5 Girl Viral Video Breakout”
The viral journey of the 5 rocket 5 girl video breakout is a textbook case of how powerful social media can be. The video initially surfaced on platforms like YouTube and TikTok, where its unique concept and mesmerizing execution drew significant attention. Within hours, it began trending under hashtags like #RocketGirls, #5Rockets5Girls, and #ViralVideoBreakout.
As more users began sharing the video, it transcended language and geographical barriers. Memes, reaction videos, and recreations quickly followed, further amplifying its reach. Celebrities and influencers also jumped on the bandwagon, sharing their admiration and even attempting to replicate the stunt.
Why Did the “5 Girl 5 Rocket Video Breakout” Go Viral?
Several factors contributed to the five girls five rocket viral video becoming such a sensation:
Unconventional Concept: Combining five rockets and five performers in a synchronized act was something fresh and unexpected.
Visual Appeal: The video’s stunning visuals, paired with an engaging soundtrack, made it ideal for social sharing.
Relatability and Aspiration: The performers’ teamwork and determination resonated with audiences, inspiring them to recreate the stunt.
Global Accessibility: Short, impactful, and easy to share, the video was perfectly suited for platforms like TikTok, Instagram, and Twitter.
The Impact of the “Five Girls Five Rocket Viral Video”
Beyond its entertainment value, the video has sparked broader discussions about the power of collaboration and innovation in social media content. Schools, dance troupes, and content creators have used it as a template to inspire their own creations.
🔴 ➤► WATCH THE VIDEO HERE✅👉 https://shorturl.at/H0aYQ (VideoLink)
🔴 ➤► WATCH THE VIDEO HERE✅👉 https://shorturl.at/H0aYQ (VideoLink)
Moreover, the clip has demonstrated the potential for short-form content to captivate global audiences in an era of dwindling attention spans. The 5 girl 5 rocket video breakout serves as a reminder that creativity and originality remain key drivers of online virality.
Conclusion
The five girls five rocket viral video is more than just a trending clip; it’s a celebration of creativity, teamwork, and the boundless potential of digital platforms. As it continues to dominate timelines and inspire countless recreations, it cements its place as one of the most talked-about viral phenomena of the year.
If you haven’t seen it yet, prepare to be amazed by this unique and unforgettable display of talent and ingenuity!
🔴 ➤► WATCH THE VIDEO HERE✅👉 https://shorturl.at/H0aYQ (VideoLink)
🔴 ➤► WATCH THE VIDEO HERE✅👉 https://shorturl.at/H0aYQ (VideoLink)

NEW NEW

.
.
.
.
.
.
.

.
.
.
.
.
.
.
NEW NEW

.
.
.
.
.
.
.

.
.
.
.
.
.
.
NEW NEW

.
.
.
.
.
.
.

.
.
.
.
.
.
.
NEW NEW

.
.
.
.
.
.
.

.
.
.
.
.
.
.
cvcvc

repo: styled-components/styled-components


text:
Perf with responsive styling and pure components

I'm a big fan of styled-system so first, thanks!
I was curious about the use of the array literal in responsive styling: <RoundedBox borderRadius={[1,2]} /> I created a little sandbox to show this: a responsive-styled pure component will re-render even though incoming props from the parent component do not change: https://codesandbox.io/s/m7p59mv3xx
The example is kind of contrived - I want the RoundedBox component to be pure so it's pretty obvious this will fail when you pass a prop with an array literal.
Perf should be measured before optimizing - however - given that object/array literals in renders is an infamous way of accidentally re-rendering in React, do you think there should be a note in the docs to mention that using responsive styling through array literals will break pure components? A simple suggestion is, if you're using a pure component, break out the array literal into a const...

Sorry for the delay, I haven't looking into the performance implications at this level, but I'd guess that it's negligible for most use-cases. Feel free to experiment on a branch with the benchmarks and let me know if you find anything interesting. I think a potential future solution for some of this might be in using babel plugins, but going to close this issue out for now

For what it's worth, we found a pretty significant performance impact with inline array literals, in that it effectively ruins pure. With a relatively large app, it becomes important to use pure to keep performance reasonable, and any prop literal is inherently a reference mismatch -- having a note in there might be valuable to others with larger-scale projects.
Also interested in which Babel plugins you're referring to, as we'd love to utilize them to improve our performance.

@AaronBuxbaum How did you identify this performance issue? Am trying to figure out a sporadic bug at the moment that I think might be related to performance but don't know how to identify.. any leads much appreciated

@AaronBuxbaum How did you identify this performance issue? Am trying to figure out a sporadic bug at the moment that I think might be related to performance but don't know how to identify.. any leads much appreciated

If you're seeing a lot of renders in your react dev tools, something is updating too much, and this is one possibility. I think your first step should be to figure out if your renders are expensive, or if you're re-rendering too much. Once you're there, you can dig into the problem -- multiple renders implies problems with things like this (which means that you can resolve a lot by hoisting object/function literals and using pure), but expensive few renders implies very different problems.

authors: AaronBuxbaum adiun georgefeast jxnblk

repo: styled-system/styled-system


text:
🛑 Cubari (Dynasty Scans) is down

In ce2a1ea, Cubari (Dynasty Scans) (https://cubari.moe/read/dynasty/the_engagement_of_the_disgraced_witch_and_the_cross_dressing_princess/?cache_buster=$GITHUB_RUN_NUMBER) was down:

HTTP code: 500
Response time: 430 ms

Resolved: Cubari (Dynasty Scans) is back up in 312dc9b after 12 minutes.

repo: subject-f/cubari-status-page


text:
🛑 Cubari (MangaSee) is down

In 92eb439, Cubari (MangaSee) (https://cubari.moe/read/mangasee/One-Piece/?cache_buster=$GITHUB_RUN_NUMBER) was down:

HTTP code: 500
Response time: 306 ms

Resolved: Cubari (MangaSee) is back up in 5e879b2 after 1 minute.


text:
🛑 Cubari (Gist) is down

In 34f5103, Cubari (Gist) (https://cubari.moe/read/gist/OPM/?cache_buster=$GITHUB_RUN_NUMBER) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Cubari (Gist) is back up in 258f0ad after 23 minutes.


text:
⚠ Guya.moe Proxied has degraded performance

In 10e7b04, Guya.moe Proxied (https://ice.guya.moe/) experienced degraded performance:

HTTP code: 200
Response time: 12904 ms

Resolved: Guya.moe Proxied performance has improved in 173a2e9 after 2 hours, 27 minutes.

repo: subject-f/guya-status-page


text:
No color decorators for syntax from SublimeText/Tailwind CSS

When I set the syntax of my stylesheet files in Sublime Text to one of the default ones (CSS, CSS3) the color decorators work just fine. For working with Tailwind CSS I use https://github.com/SublimeText/TailwindCSS/ because directives like @apply and nesting are not supported by the other two. However, color decorators don't work with that syntax.
I tried to change my LSP-tailwindcss settings to include the source.css.tailwindcss scope but it still doesn't work:
{
  "selector": "source.jsx | source.js.react | source.js | source.tsx | source.ts | source.css.tailwind | source.css | source.scss | source.less | text.html.vue | text.html.svelte | text.html.basic | text.html.twig | text.blade | embedding.php | text.html.rails | text.html.erb | text.haml | text.jinja | text.html.elixir",
  "languages": [
    {
      "languageId": "css",
      "scopes": ["source.css", "source.css.tailwind"],
      "syntaxes": [
        "Packages/CSS/CSS.sublime-syntax",
        "Packages/CSS3/CSS3.sublime-syntax",
        "Packages/Tailwind CSS/Tailwind CSS.sublime-syntax"
      ]
    }
  ]
}

Do I have the wrong setup? How do I get the "Tailwind CSS" syntax to show color decorators as well?
Ouptut from "Troubleshooting: LSP-tailwindcss"
Troubleshooting: LSP-tailwindcss
Version

LSP: 1.20.0
Sublime Text: 4141

Server Test Run

exit code: 0
output

Server Configuration

command

[
  "/usr/bin/node",
  "/home/jnns/.cache/sublime-text/Package Storage/LSP-tailwindcss/18.7.0/language-server/node_modules/@tailwindcss/language-server/bin/tailwindcss-language-server",
  "--stdio"
]

shell command

/usr/bin/node "/home/jnns/.cache/sublime-text/Package Storage/LSP-tailwindcss/18.7.0/language-server/node_modules/@tailwindcss/language-server/bin/tailwindcss-language-server" --stdio

selector

source.jsx | source.js.react | source.js | source.tsx | source.ts | source.css | source.scss | source.less | text.html.vue | text.html.svelte | text.html.basic | text.html.twig | text.blade | embedding.php | text.html.rails | text.html.erb | text.haml | text.jinja | text.html.elixir

priority_selector

(source.css)|(source.css.tailwind)

init_options

{}

settings

{
  "tailwindCSS": {
    "classAttributes": [
      "class",
      "className",
      "ngClass"
    ],
    "colorDecorators": true,
    "emmetCompletions": false,
    "experimental": {
      "classRegex": []
    },
    "files": {
      "exclude": [
        "**/.git/**",
        "**/node_modules/**",
        "**/.hg/**"
      ]
    },
    "includeLanguages": {},
    "lint": {
      "cssConflict": "warning",
      "invalidApply": "error",
      "invalidConfigPath": "error",
      "invalidScreen": "error",
      "invalidTailwindDirective": "error",
      "invalidVariant": "error",
      "recommendedVariantOrder": "warning"
    },
    "rootFontSize": 16,
    "showPixelEquivalents": true,
    "validate": true
  }
}

env

{
  "PATH": "/usr/bin:/usr/bin:"
}

Active view

File name

/home/jnns/<...>/forms.css

Settings

{
  "auto_complete_selector": "meta.tag, source - comment - string.quoted.double.block - string.quoted.single.block - string.unquoted.heredoc",
  "lsp_active": true,
  "syntax": "Packages/Tailwind CSS/Tailwind CSS.sublime-syntax"
}

base scope

source.css.tailwind

## Project / Workspace
 - folders
```json
[
  "/home/jnns/<...>"
]

is project: True
project data:

{}

LSP configuration
{
  "clients": {
    "LSP-pyright": {
      "enabled": false
    }
  }
}

System PATH

/home/jnns/.local/bin
/usr/local/bin
/usr/local/sbin
/usr/bin
/usr/sbin

Add this to LSP-tailwindcss settings.
    "initializationOptions": {
        "userLanguages": {
            "tailwind": "css",
        }
    },

Note that this is something that should be fixed in this package still.

authors: jnns rchl

repo: sublimelsp/LSP-tailwindcss


text:
Fix image tagging

Images should be cross-tagged without v prefix, make sure it's so.
Signed-off-by: Mike Kolesnik mkolesni@redhat.com

Backported as #409

repo: submariner-io/releases


text:
Document everything OVN

The OVN support will bring some changes that need to be documented from the architecture point of view.
See:  https://github.com/submariner-io/enhancements/pull/11
Related-Issue: https://github.com/submariner-io/submariner/issues/778

I was discussing this with @sridhargaddam, and wanted to summarize our thinking here:

At least from a user perspective, OVN should "just work". We do need to:

Add OVN to the list of CNI support matrix: https://submariner.io/getting_started/#support-matrix
Mention that for OVN-based clusters there is no need to open 4800 UDP ports (which normally being used for vxlan-submariner)
Document known issues/limitations (for e.g, OVN is not supported with Globalnet): https://submariner.io/operations/known_issues/

We also need to update some of the architecture pages (and diagrams?), in particular the Route Agent: https://submariner.io/getting_started/architecture/route-agent/

Document known issues/limitations (for e.g, OVN is not supported with Globalnet): https://submariner.io/operations/known_issues/

PR raised:
https://github.com/submariner-io/submariner-website/pull/402

* Add OVN to the CNI support matrix: https://submariner.io/getting_started/#support-matrix

PR: https://github.com/submariner-io/submariner-website/pull/403

authors: mangelajo nyechiel sridhargaddam

repo: submariner-io/submariner-website


text:
Decode extrinsic error at ingestion

Hi guys,
For the moment an extrinsic module error is coming in the form
{
  "__kind": "Module",
  "value": {
    "error": "0x06000000",
    "index": 9
  }
}

Unfortunately, this is not very helpful when we try to show it in the UI of an explorer. It would be nice to have it in the decoded form like what @polkadotjs/api api.registry.findMetaError returns:
{
  args: [],
  docs: [ 'Contract trapped during execution.' ],
  fields: Type(0) [ registry: TypeRegistry {}, initialU8aLength: 1 ],
  index: 11,
  method: 'ContractTrapped',
  name: 'ContractTrapped',
  section: 'contracts'
}

Is this something you guys plan on supporting?

Hey! It's likely not feasible to support on the archive explorer side as it simply presents the raw data saved by the ingester. I recommend setting up a separate squid for these purposes and then decode the error using
(ctx._chain as any).scaleCodec.decodeBinary(...)

Take a look at this squid to get an idea of how to handle events and extrinsic at the squid side
https://github.com/subsquid/talisman-squidtest/tree/firesquid-migration

Hey, thanks for the explanation!
There's no problem subscribing directly to succeeded and failed extrinsics in the squid but the error returned is still not decoded. Is it possible to expose a method like ctx._chain.decodeError() similar to ctx._chain.decodeCall() that could be used in the squid processor to get the decoded error? If I understood well from this article: https://wiki.polkadot.network/docs/maintain-errors#polkascan-and-subscan, the index 9 in my example above indicates the index of the pallet as described in the chain metadata and the error 0x06000000 indicates the index of the error in the error field of the pallet description. Since the squid archive explorer already has the chain metadata, it should be relatively easy to resolve the error?

We'll look into supporting this on our end so I'll close the issue.

authors: XY-Wang dzhelezov

repo: subsquid/squid-sdk


text:
Update Travis CI tests to use newer Node.js versions

As the ^1.4.1 syntax used for currently including the escodegen module was first introduced in npm 1.3, the npm 1.2 verison included with node 0.8.x fails at installing the dependency.
The escodegen module itself also in version 1.3.3 changed from requiring node >=0.4.0 to requiring node >=0.10.0, so it explicitly doesn't support 0.8.x anymore either.
The pull request to update the required acorn dependency ran into this issue and since that very same PR preferably should use the caret operator for the dependency it would be better to stop testing in node 0.8.x and start testing in newer node versions instead.
Related PR: https://github.com/substack/node-detective/pull/41

Thanks! Fixed by https://github.com/substack/node-detective/pull/46

authors: voxpelli zertosh

repo: substack/node-detective


text:
Find and Replace: Select All in one of the inputs should not select all in the document.

At the moment, keyboard events bubble up to the editor which handles certain combos, such as CtrlOrCommand-a, having the effect that Select All is applied to the area where the internal selection is.

We should either prevent all events from bubbling up, or consume certain combos.

Yeah I saw that too. I wonder if it would make sense to use Substance TextInput instead of the native input fields. Maybe then we have things better under control? (also enabling commands cmd+g etc.)

Command-G is more relevant as a short-cut for next, when the cursor is inside the doc.
Have you noticed, that you can travers with ENTER? Shift-Enter is not handled yet, though.

Don't think that Substance TextInput is solving this problem for us.

In this case it is really important to bind a keydown handler for CtrlOrCommand+a on the input. The SelectAllCommand is working only for Surfaces.

Maybe I didn't understand your suggestion... It would make sense to have a native input component, which is having all the common handlers. That's true.
If Substance TextInput is doing this already, I'd suggest to move it into the kit.

But don't use it for a model! :)

Surfaces are bound to models. So the inputs in the FaRD(ialog) ;) are not candidates for Surfaces.

The would need a detached (temporary model) of course. Anyways.. as said it was just a thought, since now this is the only place where we have <input> elements. :)

That is an overkill. We are perfectly able to create a native input with enough handlers attached to be compliant with the rest of the Substance actors.

Still it makes sense to have such a thing, so we do not need to reinvent it each time.

now this is the only place where we have  elements.

The key difference is that FaRD is app chrome, not content.

Fair enough. Let's stick with what we have then.

Yeah. Still I am in favor of creating a Component around Input which behaves nicely. :)

Fixed via https://github.com/substance/texture/commit/64860304b46f5df232771efb81ddc059f934d298

authors: michael oliver----

repo: substance/texture


text:
add rubocop to travis

Seems like a shame to have defined rubocop config (and implemented rubocop changes) and not enforce it.
I've pinned the version of rubocop to the latest version to prevent arbitrary correctness changes.

Thank you so much for contributing.
We run Rubocop via Code Climate, though, (see https://codeclimate.com/github/substancelab/route_downcaser/pull/47 for an example). I wonder if it is worth running it on Travis as well?

Ah ok, I didn't see that. But it would be helpful to make it a development dependency pinned to the version being used. (just to make it easier to develop on). Shall I adjust the PR to remove travis and keep the dev dependency? Or if you're not convinced, you can just close it :)

Have made this change in case helpful

I am toying with the idea of switching to https://github.com/testdouble/standard instead of raw Rubocop. It would require us to not rely on Code Climate, but that's not a dealbreaker for me.
What do you think of this instead?

I don't see a problem with testdouble/standard  -- the standards seem more sensible than rubocop defaults.
And in terms of moving the rubocop from codeclimate to travis -- I would generally prefer this as I feel like a codeclimate fail is advisory (and needs informed judgement) whereas rubocop fail (like test suite fail) tend to be more absolute.

We've switched to standard by now.

authors: koppen timdiggins


text:
Use programmaitc SS API instead of REST API from Hub Manager module

Currently there are some classes in hub manager module that address SS API via REST. However we have programmatic code API that could be used. REST API is for external clients

Done

repo: subutai-io/base


text:
[UI] [Monitoring] Too many values impacts usability.

For replay this improvement you need:
Test case

Go to SS and login under any account.
Go to Monitoring page.

Improvement: On the Monitoring graphs (i.e. disk) usability is impacted by excessive values. The popup displayed is out of control. Let's condense some of the values into rows where it makes sense. For example here:

On this popup let's condense the "avialable", "used" and "total" metrics in a nice way onto a single row instead of have each one of these on its own row.

Tested.

authors: NikolaiB akarasulu


text:
Add DellyBoard theme

DellyBoard
https://github.com/Dellyare/DellyThemes
Theme for keyboard in Apple style
Checklist
Failure to complete this checklist or deleting boxes from the checklist will result in the closing of your pull request unless this is a theme update. Please write any comments regarding this checklist at the bottom of your pull request.
Check every box.

[x] I am the original author of this theme or have permission from the original author to make this pull request.
[x] All copyright of this theme's contents belong to the listed author or is cited in the repository linked above.
[x] This theme's target has been marked appropriately and only styles said target.
[x] This theme works properly on the latest versions of SteamOS for Steam Deck, decky-loader and SDH-CssLoader.
[x] This theme only uses * or !important if absolutely necessary.
[x] This theme is under 4MB in size and uses the least disk space possible.
[x] This theme's preview image does not include text unless it is necessary to describe changes that can be made.
[x] This theme is safe for work and does not contain any sexual, drug-related, or profane content.
[x] This theme prefixes any CSS variables with a unique identifier.

Check one box.

[x] I am not bundling a part of another theme with this theme to encourage mixing and matching themes.
[ ] Themes included with this theme are toggleable using a patch.

Check one box.

[x] This is a keyboard theme applied to the default keyboard.
[ ] This is a system-wide theme applied to the default keyboard. The keyboard is toggleable using a patch.
[ ] This theme does not target the keyboard.

Hi, would you mind joining this discord? We are planning to migrate all themes to a custom built site soon, and want to discuss how that should happen.
For the PR, I'll review it tomorrow

authors: Dellyare suchmememanyskill

repo: suchmememanyskill/CssLoader-ThemeDb


text:
"Community Guidelines" footer link clicked on mobile loads that forum page scrolled down rather than at its top

Same issue that once existed for the main forum link, turbo-links whitelist or something?

Closed by https://github.com/sudara/alonetone/commit/b2a0979f7075e6b56652e80eb7606e5bdf0b1999

authors: ofsound sudara

repo: sudara/alonetone


text:
chromadb问题

大神 好， 因为docker镜像太大 ，所以我目前采用的是 "Use with Nuxt 3 Development Server"  安装方式 。 我目前只想把本地RAG跑通 ，因此用了 qwen:0.5b + nomic-embed-text 的组合 ，我用了两台虚拟机 ，一个安装：ollama  , 一个安装了：chat-ollama + chromadb + redis .  我的.env大概如下：

问题 ： 是因为这个域名导致我不能保存向量数据吗 ，  我被卡住了，麻烦大神指导下 ，谢谢。

repo: sugarforever/chat-ollama


text:
WOS client should log non-200 responses

It currently does not check the response code or log anything. As a result, the user has no way of knowing if there was an error.

repo: sul-dlss/rialto-etl


text:
🛑 SISTEMA ROYAL-HOLIDAY is down

In 155cbf9, SISTEMA ROYAL-HOLIDAY (https://www.royalholiday.com.ar/reservas/admin/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SISTEMA ROYAL-HOLIDAY is back up in a0c6d0f.


text:
🛑 SISTEMA ROYAL-HOLIDAY is down

In ece920f, SISTEMA ROYAL-HOLIDAY (https://www.royalholiday.com.ar/reservas/admin/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SISTEMA ROYAL-HOLIDAY is back up in 4064cbb.


text:
一些3.4.0新增功能的语法检查异常

单独写lua没能复现
另外有没有强制修改类型的配置方式，比如
`---@class A
local a = {}
---@class B:A
---@type string|number
local c = 1
---comment
---@return A
---@return string|number
local function func1()
return a, c
end
---comment
---@return B
---@return number
local function func2()
local ta, tb = func1()
return  ta, tb
end`
在这种情况下我怎么去配置使ta、ta符合返回值类型？

感觉上可以加个配置还忽略可控类型验证，不然现有代码出现太多错误了

可以使用 ---@cast var type 和 --[[@as type]] 转换类型，我晚点写个文档。

  所有分支都return了

你再看看？

呃，最后一个不是else，我的错

---@type UnityEngine.Vector3
local x = Vector3.zero
x = x + x  已显式定义变量的类型为 `UnityEngine.Vector3` ，不能再将其类型转换为 `number`

算术运算都变成number了
另外number和integer不兼容，这个检查太头疼了

另外number和integer不兼容，这个检查太头疼了

设置里有让 number 和 integer 兼容的选项

算术运算都变成number了

3.5.0 会支持重载运算符，可以解决这个问题

单独写lua没能复现

你在原来的代码上删除业务代码，只保留一个结构看看

我家里没能复现，周一上班公司的提示也没了

诊断速度变慢，写代码时十几秒才能诊断完

诊断速度变慢，写代码时十几秒才能诊断完

请开一个新的issue并提供日志与可复现此问题的演示工程

500个应该是没问题的，我的工作项目有1500+个文件也无压力，应该是有什么隐藏的bug导致的，这个只有用示例调试才好查

500个应该是没问题的，我的工作项目有1500+个文件也无压力，应该是有什么隐藏的bug导致的，这个只有用示例调试才好查
这个版本我们项目有 800多个诊断问题 会不会和这个有关系，我们有1500多个类型注解

有没有方法实现可选返回值？

有没有方法实现可选返回值？

---@return number?

有没有方法实现可选返回值？

---@return number?

这种怎么处理，手动写个 return nil?
---@return BattleRecordOne?
function BattleEnemy:GetBattleRecord()
    if self.battleRecord then
        return self.battleRecord.record
    end--这里提示要返回值
end

---@return BattleRecordOne?
function BattleEnemy:GetBattleRecord()
    if self.battleRecord then
        return self.battleRecord.record
    end--这里提示要返回值
end

#1257

local tm = os.date("*t", os.time())
local t = os.time(tm) -- 不能将 `string|osdate` 赋给参数 `osdate?`。

local tm = os.date("*t", os.time())
local t = os.time(tm) -- 不能将 `string|osdate` 赋给参数 `osdate?`。

开个单独的issue，以后版本改为分析参数来决定返回值

Is there any other issue?

authors: Whimsyduke septbr sniper00 sumneko

repo: sumneko/lua-language-server


text:
"Lua.workspace.ignoreDir" doesn't ignore my file

I use custom format to store my settings, similar to json but in lua notation. I called it "luat" and when I added "*.luat" pattern to "Lua.workspace.ignoreDir" it is still highlighted red:

The language service currently has a setting. If a lua file is ignored, but you actively open the file, the language service will temporarily assume that the file has not been ignored (in order to provide functions such as automatic completion and floating prompts). But this does cause inconvenience in some cases, and I will consider how to improve it.

authors: sumneko winterwolf


text:
Which is PHPUnit coverage type, C0 or C1 or C2?

Coverage type:

Type
Name
Description

C0
Statement coverage
Tỉ lệ bao phủ câu lệnh

C1
Branch coverage
Tỉ lệ bao phủ nhánh - Mỗi nhánh của if phải được test ít nhất 1 lần

C2
Condition Coverage
Tỉ lệ bao phủ điều kiện - Mỗi điều kiện trong lên if đều được test 2 case: 1 là true 2 là false

[ ] 1. Dựa vào kết quả coverage của Issue #1, kết luận PHPUnit coverage thuộc loại nào?
[ ] 2. Câu lệnh ở đây là lệnh trong function hay tính cả class property?
[ ] 3. Test case tests/C0/DumpExampleTest.php đã cover 100% C0 coverage, nhưng đã đủ test case cho class DumpExample chưa?

Theo kết quả test thì hiện tại coverage đang thuộc C0 do khi test class DumpExample

Test đã chạy qua hết các lệnh của function examine.
Chưa đạt được C1 do funtion examine không có nhánh else.
Chưa đạt C2 do chưa test đk false cho funtion  examine

Câu lệnh chỉ tính lệnh trong function, không tính đến các class property.

PHP Unit coverage thuộc loại C0, Vì:

Test đã chạy qua hết các câu lệnh của function examine
Chưa đạt được C1 do chưa test case else của function examine
Chưa đạt được C2 do điều kiện if mới chỉ được test case true, chưa được test case false

Câu lệnh ở đây là lệnh trong function, không tính đến class property

@taipt-0504

Chưa đạt được C1 do funtion examine không có nhánh else

Em thấy chưa chuẩn lắm anh nhể, vì if thì luôn ngầm định có nhánh else.
if ($condition) {
    // ...
}

=> 2 test cases: chạy vào trong block if và không chạy vào trong block if
if ($condition) {
    // ...
} else {
    // ...
}

=> 2 test cases: chạy vào trong block if và chạy vào trong block else

@taipt-0504 @huongvnq-1722
A/e update thêm câu 3 nhé

C0 do đã phủ toàn bộ xử lý nhưng chưa chú ý đến điều kiện.
Em không hiểu lắm class property là gì :p. Đang hiểu nó là kiểu getAttribute, ... có đúng không ạ?
Đủ test case theo điều kiện C0 nhưng C1, C2 chưa đủ

@nganltb-1258

PHPUnit nó tính coverage là C0 (Statement coverage) ấy, chưa support tính C1, C2 coverage
Ý anh là class property hay class field, VD như public $fillable = []
Trường hợp này 100% code coverage nhưng vẫn bị lack case đúng không, gây ra bug nếu ko test đủ


text:
棋譜形式一括変換機能

せっかく CSA や KIF, SFEN, USI に対応したので、棋譜一括変換機能を作っても良いと思う。
ただ、 Electron 将棋に搭載すべき機能なのか微妙なのと、自分が頻繁に使うわけではないのでモチベーションもそこまで高くはない。

https://github.com/yaneurao/YaneuraOu/wiki/定跡の作成
やねうら王は拡張子 .sfen で SFEN (というか USI) を行ごとに記載しているらしい。

repo: sunfish-shogi/electron-shogi


text:
About me and Contact sections are not clearly delineated on Home page

On home navigation, about me and contacts do not have distinctive sections.

Created headers to separate these items and display them with very clear sections.


text:
Hard to find docs

Do docs exist for this project? If so some sort of link on the github page (maybe in the Readme) would be helpful, as I can't obviously find one.

In case you haven't found them already they are here: https://docs.sunpy.org/projects/radiospectra/en/latest/ :rofl:

authors: Cadair dstansby

repo: sunpy/radiospectra


text:
Update to official latest mergeable

Our mergeable is full of bugs. We should update our config and move to the official hosted version.

Well, I thought mergeable had implemented my feature, but it's actually still sitting in the issue queue. Fuck.
https://github.com/mergeability/mergeable/issues/145
https://github.com/mergeability/mergeable/issues/62
Tagging as upstream. I tried clobbering something up for the proposed "unless" operator, but it's a bit non-trivial.

See #434 .
Blocked on https://github.com/mergeability/mergeable/pull/227

repo: sunriseos/SunriseOS


text:
v2.50 release

What features and issues are more urgent for version 2.5.0?  And what is your plan for 2.5.0?

@dota17 @jjenkov @ChristianWilkie

I like you guys feedback on this. In my mind it is

get jenkins up and running with code coverage
its been a while since last release, so get a release out soon

maybe we should upgrade to java 8 ,just like @jjenkov says java 6 or java 7 is too old   #169

I would say, that the highest priority should be to just get a release out. As far as I can see, v. 2.4.0 is 3 years old. I would go for a minimum of functionality in 2.5.0, just to bring SuperCSV "back to life" .

If upgraded to J8, would SuperCSV work correctly under J9+? My application uses SCSV, and a problem that I run into is its incompatibility with J9+ just generally. It would be a big upgrade for me if that issue was resolved. (as always, thank you for maintaining this!)

@DraqueT  Is the approach to make a J9 specific release? or will the https://github.com/super-csv/super-csv/pull/152 suffice?

Hi, @kbilsted
I don`t think super-csv version 2.5.0 make a J9 specific release. I think it is enough that ensuring super-csv 2.5.0 can be imported and used in java9 module application(#138 ).
Because java9 modules is important and influential. When we upgrade Java 9, we need to design reasonable modules for super-csv,
And

Hi, @kbilsted
Are you plan to upgrade to java8 in 2.5?
If so, we can incorporate super CSV java8 into super CSV and address #152. that will ensuring super-csv can be imported and used in java9 module application.

Adding support for escaping quotes using \" instead of leaving this as unhandled seems reasonable, very hard to recover from errors based on this otherwise.

@dota17  I'd vote for caution. Can you make things work in a side branch for JDK 9 for now and get experince with it with some users?
isn't java8-specifc jar a part of the existing mvn build?

I can probably help out on getting this to compile on Java 8. This is used on one of the Apache projects I'm working on and there are some bug fixes I could really stand to have. Glad to see active development again.

The master branch does build just fine on Java 8 though. Not sure if what some of the other issues actually were.

@shawnweeks thanks. I'll install jdk8 and retry

@shawnweeks thanks. I'll install jdk8 and retry

I just ran "mvn clean install" using adoptopenjdk on macos. All the test cases ran and everything. Jars appear to be there in the build not sure what else needs to be tested but it should at least build until we move the compile versions forward.

Hi, @kbilsted
I am sorry. Can you change the name of the branch from java9 to java8 ：）.

sorry yes. I have been away for some days. Had some business I had to do.

Any chance for a 2.5.0 release soon?
What issues/things are still open to do so?

Any chance for a 2.5.0 release soon?
What issues/things are still open to do so?

Same question here, do you have a 2.5.0 release soon or is anything open here ?

authors: DraqueT apatrida dota17 edu-de jjenkov kbilsted patric-r shawnweeks

repo: super-csv/super-csv


text:
Delete File

Just want to know whether we can delete a file using supercsv.

First created the ICsvBeanWriter
Write the data using ICsvBeanWriter
Close the ICsvBeanWriter

even if the data is not available in the step 2 we are creating the file and their is not way to delete the file.
any idea how can we achieve this?
Thanks,
Nagaraju

HI i'm not fully sure i understand the problem. Try submitting some Java code for how you think you could use the framework. Why not simply delete the file yourself? why start wrtiting to a file before you check if you have data to write?

ICsvBeanWriter is just an abstraction for writing any bean as CSV row. CsvBeanWriter class pushes CSV String to Writer object which is given in constructor. You probably uses FileWriter class which creates file at the beginning.
You have two solutions:

You can use StringWriter which writes data to memory. At the end, after writing, you can check the length of the String and save it to file if needed. Consumes time and memory but doesn't create file if it is not needed.
You can close the stream and remove file if it is empty.

Summary: does not look like an issue in super-csv library. I vote to close this.

+1 @ZioberMichal

authors: ZioberMichal kbilsted nagraj321


text:
Add java.time parsers and formatters

Fixes #53 . I have tried to match the structure of the java.time package, which diverges from joda.time. I also tried to design locale-independent tests that also use the current locale.

Hi. It looks really good! I've noticed that you are using different imports order than it is in project.
Project's order:

static
java.*
org.*

In your commit:

org.*
java.*
static

I think that we should use the same order.

I’ll see what I can do about the imports. Importing the eclipse configuration does not seem to solve all format issues :-)

This is a reason why I've crated this issue #61 :smirk:

authors: ZioberMichal ludovicofischer


text:
🛑 Cabinet Place Online is down

In 7c6f6cd, Cabinet Place Online (https://www.cabinetplaceonline.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Cabinet Place Online is back up in 3721f57 after 6 minutes.

repo: superwebpros/uptime


text:
远程唤醒

基于RT-Thread+RA6M4的远程开机助手概要
https://club.rt-thread.org/ask/article/e086a4b93cd3b143.html

WOL 远程唤醒，需要网卡带电支持。

进去BIOS打开这个功能

参考
https://mp.weixin.qq.com/s/9p_LTT-7w14MqGiDDNRVmA
设置一下电源按钮，然后记录一下mac地址
然后关闭计算机
然后进入小程序
输入计算机的mac地址即可
#小程序://网络唤醒WakeOnLan/mPDLCY0OakAkNif

https://blog.csdn.net/m0_37624610/article/details/108196206


text:
blackjackgame

this will help to learn the javascript concept by making this game

Thanks for PR. Merged.

repo: surajondev/JavaScript


text:
Only health at container level

Right now pod spec allows you to do both livenessProbe and readinessProbe and since both the fields represent the same data strcuture behind the scene which is called probes.
So a container will look like the following:
containers:
- image: wordpress:4
  health:
    httpGet:
      path: /
      port: 80
    initialDelaySeconds: 120
    timeoutSeconds: 5

the pod that is generated out of this will look like this:
containers:
- image: wordpress:4
  livenessProbe:
    httpGet:
      path: /
      port: 80
    initialDelaySeconds: 120
    timeoutSeconds: 5
  readinessProbe:
    httpGet:
      path: /
      port: 80
    initialDelaySeconds: 120
    timeoutSeconds: 5

So essentially you just specify health field which is probe type and then it is populated into readinessProbe and livenessProbe in the output. But if user provides the fields readinessProbe or livenessProbe explicitly then health field is ignored! Those fields are used directly.

agreed, with one exception. lets fail if there is health field  with readinessProbe or livenessProbe defined

authors: kadel surajssd

repo: surajssd/opencomposition


text:
feat: Added a service for displaying snacks

Checklist
A service has been written that will help you use flutter_easy_dialogs to display snacks "out of the box".
https://github.com/surfstudio/surf-flutter-app-template/assets/39735343/142d53c3-d05f-4d2c-b4de-421ab6411766

[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Is there an existing issue for this PR?

link issue here (use keywords like fix, close, resolve etc. if necessary)

[x] Have the files been linted and formatted?
[ ] Have the docs been updated to match the changes in the PR?
[ ] Have the tests been updated to match the changes in the PR?
[x] Attached videos/screenshots demonstrating the fix/feature.
[ ] Have you run the tests locally to confirm they pass?

New Features
What new capabilities does this PR add?
What docs changes are needed to explain this?

Codecov Report
Attention: Patch coverage is 0.77519% with 128 lines in your changes are missing coverage. Please review.

Project coverage is 23.25%. Comparing base (339c48c) to head (59786b9).
Report is 17 commits behind head on main.

Files
Patch %
Lines

...tures/snack_queue/presentation/snack_queue_wm.dart
0.00%
61 Missing :warning:

...k_queue/presentation/default_snack_controller.dart
4.16%
23 Missing :warning:

...tures/debug/presentation/ui_kit/ui_kit_screen.dart
0.00%
18 Missing :warning:

.../features/debug/presentation/ui_kit/ui_kit_wm.dart
0.00%
8 Missing :warning:

...s/snack_queue/presentation/snack_queue_widget.dart
0.00%
5 Missing :warning:

...snack_queue/presentation/snack_queue_provider.dart
0.00%
4 Missing :warning:

...atures/snack_queue/presentation/top_snack_bar.dart
0.00%
4 Missing :warning:

lib/l10n/app_localizations_en.g.dart
0.00%
2 Missing :warning:

lib/l10n/app_localizations_ru.g.dart
0.00%
2 Missing :warning:

...es/snack_queue/presentation/snack_queue_model.dart
0.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #114      +/-   ##
==========================================
- Coverage   26.39%   23.25%   -3.14%
==========================================
  Files          55       61       +6
  Lines         917     1045     +128
==========================================
+ Hits          242      243       +1
- Misses        675      802     +127

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

authors: codecov-commenter internetova

repo: surfstudio/surf-flutter-app-template


text:
feat: Changed readme file

Changes

updated readme file

Checklist for self-check

[x] Commits and PRs have been filed according to the rules on the project.
[x] The author is marked as an assigne and assigned mandatory reviewers.
[x] Required labels marked
[ ] Specified related tasks and/or related PRs.
[x] Specified Changes.
[ ] Attached videos/screenshots demonstrating the fix/feature.
[x] All unspecified fields in the PR description deleted.
[ ] New code covered by tests.

Checklist for reviewers

[ ] CI passed successfully (with a green check mark).
[ ] PR is atomic, by volume no more than 400 (+-) corrected lines (not including codogen).

Design:

[ ] System design corresponds to the agreements on structure and architecture on the project.
[ ] The code is decomposed into necessary and sufficient components.

Functionality:

[ ] The code solves the problem.
[ ] Any changes to the user interface are reasonable and look good.

Complexity:

[ ] The code is clear, easy to read, functions are small, no more than 50 lines.
[ ] The logic is not overcomplicated, there is no overengineering (no code sections that may be needed in the future, but no one knows about it).

Tests:

[ ] Updated or added tests for mandatory components.
[ ] The tests are correct, helpful, and well designed/developed.

Naming:

[ ] The naming of variables, methods, classes and other components is understandable.

Comments:

[ ] The comments are understandable and helpful.

Documentation:

[ ] All labels are correct
[ ] Technical documentation updated (after approval, updates last reviewer).

@Evgenia-bit I do not have permission for creating a PR or commiting to a branch. Please, contact SA and lease me with access.

authors: Evgenia-bit samir-a-ts

repo: surfstudio/surf-flutter-faded-text


text:
widget request "lokesh pretty checkbox"

https://lokesh-coder.github.io/pretty-checkbox/#basic-checkbox
from the https://github.com/surveyjs/editor/issues/232

I've added pretty-checkbox custom widget basic implementation. It works for checkboxes and radiobuttons with limited set of options. The widget inner markup highly depends on the certain pretty-checkbox options. This makes common implementation of this widget too complex IMO.

@tsv2013, I can't make your version of the widget to work for my case. I am not sure what I miss.
I attached a simplified version of my code, "suyveyjs-form.html" and "surveyjs-form.js" here: https://github.com/surveyjs/editor/issues/232, to show how it works for my case.
Please advise.

@tjtaojiang Sorry for delay. I've added example how to integrate pretty-checkbox custom widget. It resides on our site - https://surveyjs.io/Examples/Library/?id=custom-widget-pretty-checkbox&platform=Angular2
As for your implementation of the custom widget - I cann't find binding between question value and the widget control.
I suggest you try to integrate our custom widgets pack into your application.
We'll provide you with the necessary support. Please feel free to contact us in case of any difficulties.

@tsv2013, binding by: row.value and row.text.  In my simplified code, you can run it and see the result.

@tsv2013, I noticed one thing, your  alter the look and feel for the pretty checkbox.  Check https://lokesh-coder.github.io/pretty-checkbox/, and look for "Svg" and "Recurring" checkbox, it supposed to be curved.

@tsv2013, I copy your sample code from your link above and click "Edit in Plunker", for some reason, I still can't make your code to work.
I attached a simplified version from my implementation here for you to see how it work for me:
surveyjs_widget_for_pretty_checkbox.zip.
To answer your previous concern, check row.value and row.text in the js, which I used for data binding.
I think my way has full control in term of custom widget. I just do not know if it will break some surveyjs process , like required filed property, etc.  I will keep testing.
Any advise is much appreciated.

@tsv2013, I noticed a very big bug in your recent changes.
All other types are blocked from addCustomWidget, except "radiogroup" and "checkbox". In other words, in "isFit:", you can only see "radiogroup" and "checkbox" type, other types like "text" will be blocked.
I think you need to fix this issue.

@tjtaojiang On this page (https://surveyjs.io/Examples/Library/?id=custom-widget-pretty-checkbox&platform=Angular2) you can find the "Edit in Plunker" button. In this case our site creates a new "ready to run" plunk containing the current sample code.
E.g. after I clicked this button I've got the following plunk with the pretty-checkbox example for angular platform:
https://plnkr.co/edit/chHf8x?p=preview
It works for me ok.
Does this plunk work for you?

@tjtaojiang In the sampe plunk - https://plnkr.co/edit/chHf8x?p=preview
the following lines from the index.html files are responsible for adding the "pretty-checkbox" custom widget functionality:
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/pretty-checkbox@3.0/dist/pretty-checkbox.min.css"/>
<script src="https://unpkg.com/surveyjs-widgets"></script>

because of the code of our "pretty-checkbox" custom widget implementation is resides in the "https://unpkg.com/surveyjs-widgets" script.

@tjtaojiang I've also created a plunk with the code you sent me in the "surveyjs_widget_for_pretty_checkbox.zip" archive.
This is the link to the plunk with your code - https://plnkr.co/edit/e3uqCK?p=preview
We can use this plunk as a starting point for the further discussion.
Note that I've commented reference to our custom widgets package (in the index.html file) because you are using your own implementation of the "pretty-checkbox" custom widget:
    <!--<script src="https://unpkg.com/surveyjs-widgets@0.98.4/surveyjs-widgets.js" type="text/javascript"></script>-->

Could you check this plunk also?

My thoughts about the pretty-checkbox cutom widget implementation
"pretty-checkbox" is the CSS library and requires different markup for different features.
This makes us to drop our default-generated markup of the "checkbox", "radiogroup" (and that much more worse the "matrix") questions and replace it with the markup required to make "pretty-checkbox" work properly.
If we remove our default markup, we become responsible for

the two-way binding of the custom widget: subscribe on the question value changes and reflect them in the UI, and subscribe the UI control input and pass entered values to the question;
the whole SurveyJS question functionality as read-only behaviour, "other item", "column count" and other options

Our basic implementation of the "pretty-checkbox" custom widget at this moment contains basic options and binding functionality and supports "checkbox" and "radiogroup" quesions only.
The full functionality can be added to the certain custom widget implementation by the united efforts of the SurveyJS team and the community. I hope on your understanding and support.

@tsv2013, for some reason, this Plunker version does not work when I copy them into my local: https://plnkr.co/edit/?p=preview. I still see the old radio and checkbox.

@tsv2013, for some reason, this Plunker version does not work when I copy them into my local: https://plnkr.co/edit/chHf8x?p=preview. I still see the old radio and checkbox.

@tjtaojiang Could you tell me whether the plunker https://plnkr.co/edit/chHf8x?p=preview works for you or not?

@tjtaojiang hello! Could you please describe your use case? Does the example in our site looks good? Do your problem with integrate widget in your project or with widget functionality?

@dmitrykurmanov, as I mentioned above, I copy three files in https://plnkr.co/edit/chHf8x?p=preview into my local, because some websites are blocked by my company, I need to use https://go.weblife.io to download all blocked css and js into my local.  I attach zip file contain all three I modified and used in my local.  You can see duplicated due to the websites are block and I have downloaded.  After I put all three in one directory and click html, I still only see the default (old fashion) radio and checkbox.

@dmitrykurmanov, as I mentioned above, I copy three files in https://plnkr.co/edit/chHf8x?p=preview into my local, because some websites are blocked by my company, I need to use https://go.weblife.io to download all blocked css and js into my local. I attach zip file contain all three I modified and used in my local. You can see duplicated due to the websites are block and I have downloaded. After I put all three in one directory and click html, I still only see the default (old fashion) radio and checkbox.
test-surveyjs-form.zip

Hi, @dmitrykurmanov, @tsv2013,
After getting the sample code from https://plnkr.co/edit/chHf8x?p=preview, I do see the default checkbox and radiogroup are changed to pretty checkbox.
But at least I noticed those issues:
(1). You have modified the default checkbox to a square shaped pretty checkbox. If I need other shapes like "Svg" -> "Recurring", a curve shape checkbox, on https://lokesh-coder.github.io/pretty-checkbox/, or if I need to use the old square checkbox, I still need to create a custom widget, which is actually what users will need: how to create custom widget to cope their requests.
(2). Your new implementation deactivate colCount. Check your sample case.
(3). https://unpkg.com/surveyjs-widgets, or actually https://unpkg.com/surveyjs-widgets@0.98.4/surveyjs-widgets.js, has disabled any custom widget implementation. Uncomment addCustomWidgetForDatePicker() in test-surveyjs-forms.js in my attachment:
test surveyjs widget.zip
, you will see isFit: never gets called.
(4). For lengthy label radio or checkbox, the current pretty checkbox cuts the total description. Check my attachment above.

@tjtaojiang Answering your questions:
(1) - I've implemented "addOn" feature for the "pretty-checkbox" custom widget. It allows to insert any additional markup before the "label" tag
For "SVG" mode you will need to add the following code:
  var prettyCheckbox = Survey.CustomWidgetCollection.Instance.getCustomWidgetByName(
    "pretty-checkbox"
  );
  var checkboxSettings = prettyCheckbox.widgetJson.settings.checkbox;
  checkboxSettings.rootClass = "pretty p-svg p-curve";
  checkboxSettings.addOn =
    "<!-- svg path -->" +
    '<svg class="svg svg-icon" viewBox="0 0 20 20">' +
    '<path d="M7.629,14.566c0.125,0.125,0.291,0.188,0.456,0.188c0.164,0,0.329-0.062,0.456-0.188l8.219-8.221c0.252-0.252,0.252-0.659,0-0.911c-0.252-0.252-0.659-0.252-0.911,0l-7.764,7.763L4.152,9.267c-0.252-0.251-0.66-0.251-0.911,0c-0.252,0.252-0.252,0.66,0,0.911L7.629,14.566z" style="stroke: white;fill:white;">' +
    "</path>" +
    "</svg>";

(2) I've implemented the "colCount" feature
(3) I've checked different custom widgets (including the "pretty-checkbox") on the same page of a survey - they all works fine for me.
I've checked the last code you sent us and found that you commented your custom widget initialization function:
function onAngularComponentInit() {
    // addCustomWidgetForDatePicker();
    Survey.SurveyNG.render("surveyElement", {model: survey});
}

After I've uncommented this call, everything works ok for me.
(4) I've checked your attachment, and see that long item descriptions are not trimmed. At this point I'd like to clarify - what behaviour for the long item descriptions is suitable for you? Could you share a screenshot or drawing with desired view.

@tjtaojiang The changes mentioned above will be available since 0.98.6. For more details you can check the 0d7f9b9195ee6a07cc578981e4ec54cb48b26341 commit.

Hi @tsv2013,
(1). Due to the (2) - (3), I can't test this: "If I need other shapes like "Svg" -> "Recurring", a curve shape checkbox, on https://lokesh-coder.github.io/pretty-checkbox/, or if I need to use the old square checkbox..."
(2). colCount is still not working. I attach my code here for reference
test surveyjs widget.zip. You can check the attached image file, test-surveyjs-form.jpg .
(3).  Check my attachment above, https://unpkg.com/surveyjs-widgets, or actually now: https://unpkg.com/surveyjs-widgets@0.98.5/surveyjs-widgets.js, still disable radiogroup and checkbox. Much worse, in my real code (not attached), it disables any custom widget implementation.
(4). Check the attached image file, lengthy label still stretch out and trimmed.

@tjtaojiang
As I wrote in this comment (https://github.com/surveyjs/widgets/issues/12#issuecomment-353289703) - "The changes mentioned above will be available since 0.98.6". After 0.98.6 will be released, you will be able to try "addOn" feature and "colCount" option. I'll also add corresponding demo on our site.
As for (3) - I'm not able to reproduce this issue on my side. Can you prepare an example in plunker or any other sandbox or project or github repo? So I will be able to reproduce the issue and fix it.
(4) - I do understand that things are not so good as they can be. But could you give your opinion - how it should be fixed?

@tjtaojiang I've checked your code and screenshot you sent. And I can say that datePickerWidget is applied on your page. You see an empty space instead of date picker control because you disable default rendering via setting the isDefaultRender: false option and nothing created in the afterRender: function (question, el) {         } function as I can see from your custom datePickerWidget code from your file:
function addCustomWidgetForDatePicker() {
    var datePickerWidget = {
        isFit: function (question) {
            alert("question = |" + question + "|\n"
                + "question.getType() = |" + question.getType() + "|\n"
                + "question.inputType = |" + question.inputType + "|\n"
                + "question.class = |" + question.class + "|\n"
                + "question.name = |" + question.name + "|\n"
                + "question.title = |" + question.title + "|\n"
            );
            return (question.getType() === 'text') && (question.inputType === 'date');
        },
        isDefaultRender: false,
        afterRender: function (question, el) {
        }
    };

    Survey.CustomWidgetCollection.Instance.addCustomWidget(datePickerWidget);
}

@tjtaojiang In order to use custom widgets, their code sould be loaded after the core SurveyJS library:
    <script src="https://surveyjs.azureedge.net/0.98.5/survey.angular.js" type="text/javascript"></script>
    <script src="https://unpkg.com/surveyjs-widgets@0.98.5/surveyjs-widgets.js" type="text/javascript"></script>

@tsv2013,
Refer to your: "As for (3) - I'm not able to reproduce this issue on my side. Can you prepare an example in plunker or any other sandbox or project or github repo? So I will be able to reproduce the issue and fix it."
Please use my previous zip file, test surveyjs widget.zip, the 4th post above this one, click test-surveyjs-form.html after you unzip.  You can see radio and checkbox element never got passed into isFit: in addCustomWidgetForDatePicker() .
I will post another post to illustrate how do I cope my issues (10 - (4) next.

Hi @tsv2013 and @dmitrykurmanov,
Here is how I solve my issues from (1) - (4).  I need to comment out , otherwise it will disable all custom widget I created, as I mentioned before.
Here is the attachement for it:
test surveyjs widget-3.zip
click test-surveyjs-form.html after you unzip it.
I am not sure my way will introduce any other issues, which may break some calculation and dependency, like required property etc.
Please offer advise.

Hi @tsv2013 and @dmitrykurmanov,
Here is how I solve my issues from (1) - (4). You need to comment out https://unpkg.com/surveyjs-widgets@0.98.5/surveyjs-widgets.js as in test-surveyjs-form.html, otherwise it will disable all custom widget I created, as I mentioned before.
Here is the attachement for it:
test surveyjs widget-3.zip
, click test-surveyjs-form.html after you unzip it.
I am not sure if my code will introduce any other issues, which may break some surveyjs calculation and dependency, like required property etc.
Please offer advise.

@tjtaojiang  The "radio and checkbox element never got passed into isFit in addCustomWidgetForDatePicker()" because they are already fit for another custom widget. It is hard to apply two custom widgets on the same question. This can lead to unexpected side effects.
But until now our pretty-checkbox custom widget was activated always by question type if pretty-checkbox css styles were loaded on the page. I've changed this behaviour to activation by property: renderAs that should be set to "prettycheckbox" value.
As for your implementation of the pretty-checkbox custom widgets. Your certain implementation can better be suitable for solving your certain tasks. I don't see any problems in your implementation for now except of absence of two-way bindings: UI will not updated in case of model has been changed and choosen in UI values are not passed in the model. The last problem is crucial because if you choose some items and press Complete button you will see validation complains "Please answer the question." because the values you have choosen haven't been stored in the question.

@tsv2013, I will look into the two-way bindings issue you mentioned.
As far as "radio and checkbox" are already fit for another custom widget, then user will not be able to create a widget for their requirement?  This may not be a good idea. Can we remove the limit?

@tsv2013, I will look into the two-way bindings issue you mentioned. Do you have any recommendation how should I modify my implementation to cope with the issue?
As far as "radio and checkbox" are already fit for another custom widget, then user will not be able to create a widget for their requirement? This may not be a good idea. Can we remove the limit?

Hi @tsv2013 and @dmitrykurmanov,
Here is my current version which will fix two-way bindings issue. It also contains a custom widget for a date picker (pikaday object):
test surveyjs widget-4.zip. If you wish, I can move the date picker (pikaday object) custom widget to a separate thread.
But there is a minor issue which I have not figured out.  For some reason, the checkbox does not show the white check sign inside the checkbox. Do you know why?
I will be on vacation. I won't reply to you until I come back.  Thanks.

Hi @tsv2013 and @dmitrykurmanov,
Here is my current version which will fix two-way bindings issue. It also contains a custom widget for a date picker (pikaday object):
test surveyjs widget-4.zip
. If you prefer, I can move the date picker (pikaday object) custom widget to a separate thread.
But there is a minor issue which I have not figured out. For some reason, the checkbox does not show the white check sign inside the checkbox. Do you know why?
I will be on vacation. I won't be able to reply to you until I come back. Thanks.

authors: dmitrykurmanov tjtaojiang tsv2013

repo: surveyjs/widgets


text:
Shadab M S

I have added my code here please accept the pull request.

Hey @shadabms ,
Could you please change the font size?

authors: Inframind shadabms

repo: sushant-j/my-first-pull-request


text:
New version

New version should be released in order to start using SPM. I would suggest doing a minor bump to 2.3.0.

Yes indeed, that also occurred to me while I was drinking my beer this evening 😀 Will do tomorrow!

Thanks a lot and enjoy that beer 💪

Done! Since nothing else changed, I labeled the version 2.2.2. Thanks again!

authors: LucianoPolit svdo

repo: svdo/ReRxSwift


text:
Wallet Standard support, bug fixes and upgrades

Wallet Standard support
Dependencies upgraded to recent versions
Accessibility warnings fixed

If you can't wait for the merge of this PR, consider using aztemi/svelte-on-solana-wallet-adapter repo instead. It is a fork and already has these commits with additional features integrated.

Thanks!
Will try this out now

That'll great @cogoo. Thanks.

@cogoo
have you also tried
https://github.com/portalpayments/svelte-on-solana-wallet-adapter
do u know if these support solana mobile adapters?
which one do you recommend?

repo: svelte-on-solana/wallet-adapter


text:
feat: simple testing library

Alternative to #32
This takes more of a lightweight approach where we provide a bare minimum api for testing rather than controlling the whole testing pipeline. This should allow for better flexibility as we're no longer tied to any particular testing framework.
Notes:

Had to rename the directory of the vitest addon as it was somehow interfering with vitest or tinypool during runtime, causing shit to randomly break
Storybook has been pinned to v8.3.x as v8.4.x flat out doesn't work. I haven't had a moment to fully investigate the issue yet.

TODO:

Snapshots?
look into using vitest workspaces
Should we continue to use degit to clone the vite templates? If so, should we pin it to a specific commit hash (see here)? Or should this be something we manage fully (perhaps as part of create)?

Ohhh and there is another thing I just noticed: How are the directory names inside .test-output/_tests generated? Here are my directories inside drizzle
-1930824653_0
-1930824653_1
-1930824653_2
-1930824653_3
-1930824653_4
-1930824653_5
-1930824653_6
-1930824653_7

They are semi-useful at least. In #32 I generated them based on the options passed for each test, so that if a test failed you could identify it by directory name and run it by hand.

How are the directory names inside .test-output/_tests generated? Here are my directories inside drizzle

they're based on the task id provided by vitest. Each test gets their own meta.json (similar to how we had it in svelte-add) that documents the options that were passed in.

They are semi-useful at least. In #32 I generated them based on the options passed for each test, so that if a test failed you could identify it by directory name and run it by hand.

not sure if that's a scalable solution. imagine having multiple test cases that share the same addon options but they evaluate different things

repo: sveltejs/cli


text:
Support for subdomains in SvelteKit

Describe the problem
I do want to start this off with the acknowledgment that subdomains with SvelteKit is possible. However, there is no clear documentation nor have I found any clear and concise examples on how to do so. The only reason I even assume it is possible  is because of kit.svelte.dev.
If I am wrong, and there is a clear and documented way of adding support for subdomains to SvelteKit websites then please do let me know and I will close this issue.
Describe the proposed solution
The proposed solution is that of the title.
Alternatives considered
Subdirectories are fine, just not ideal.
Importance
nice to have
Additional Information
No response

I don't know what this is asking for. You have access to the hostname via the event that's sent to endpoints and the $page store that's available to pages.
kit.svelte.dev is its own app/site that is completely separate from the app/site at svelte.dev.
Is the request to be able to have one app serve multiple hostnames, and have the hostname be part of what distinguishes routes, instead of just the path?

I understand I have access to the site's hostname. Even then there is still no clear documentation.
I am using cloudflare pages and see no clear way of using multiple subdomains with one or even multiple SvelteKit projects.

subdomains are something that you configure with DNS (not with your frontend framework), so there's nothing that SvelteKit would do here
If you'd like help or are confused about something, please ask on Discord

Hi!
I think that the question being asked is if someone wants to use dynamic subdomain routing can they do that in Svelte Kit as part of their routing scheme:
I.e.
http://mysubdomain.example.com => '/subdomain/mysubdomain/'
http://myexcellentsubdom.example.com/homepage => '/subdomain/myexcellentsubdom/homepage'
http://first.second.example.com => '/subdomain/first/second/'
http://first.second.example.com/another/page => '/subdomain/first/second/another/page'

In express this is possible using express-subdomain-handler
In other words: Just like you can use src/routes/about/+page.svelte and src/routes/blog/[slug]/+page.svelte to make /blog/foo and about pages on mysite.com, so too you should be able to create a route for a subdomain such as /src/routes/[subdomains]/login/+page.svelte or /routes/search.site/+page.svelte to make a login.mysite.com or search.mysite.com subdomain.
This seems like a reasonable and understandable request, so I think that this issue should maybe be reopened.

authors: Conduitry benmccann cowboycodr rocketinventor

repo: sveltejs/kit


text:
1.0.0-next.455 causing broken Netlify response header behavior

Describe the bug
With a simple upgrade to @sveltejs/kit from 1.0.0-next.454 to 1.0.0-next.455 with no code changes except the ones needed for the upgrade, the response headers of the pages as served from Netlify are different. I suspect that something changed with the build to where now the netlify.toml is not being read (even though it seems to be detected when looking at the Netlify build logs for the branch).
The response headers (truncated) for an initial html page are changed as follows:
- cache-control: public, max-age=0, must-revalidate
- content-type: text/html; charset=UTF-8
- cross-origin-embedder-policy: require-corp
- cross-origin-opener-policy: same-origin
- strict-transport-security: max-age=31536000; includeSubDomains; preload

+ cache-control: no-cache
+ content-type: text/html
+ link: <./_app/immutable/assets/_layout-7e2cdc5f.css>; rel="preload";as="style"; nopush, <./_app/immutable/assets/modalProvider-2c7dffb9.css>; rel="preload";as="style"; nopush, <./_app/immutable/assets/outputLoadingMessage-6ab61537.css>; rel="preload";as="style"; nopush, <./_app/immutable/assets/tooltip-0a1c217e.css>; rel="preload";as="style"; nopush, <./_app/immutable/start-9e2d9bc6.js>; rel="modulepreload"; nopush, <./_app/immutable/chunks/index-f9b80742.js>; rel="modulepreload"; nopush, ...

The only custom ones set in the netlify.toml are the cross-origin headers you see there (COOP and COEP).
Reproduction
Upgrade from 1.0.0-next.454 to 1.0.0-next.455 and follow the simple changes described here
Logs
No response
System Info
The build image used is the default one in Netlify Ubuntu Focal 20.04.
Severity
blocking an upgrade
Additional Information
No response

Please provide a repro as described in the issue template

https://github.com/papiro/svelte-kit-netlify-issue
netlify: https://master--aquamarine-palmier-db1503.netlify.app/

I haven't been able to get the old behaviour working, despite countless permutations of kit and adapter-netlify versions, and the provided repro won't build on Netlify at all, so unfortunately I have no idea what changed. The https://master--aquamarine-palmier-db1503.netlify.app/ deployment doesn't appear to be active.
I can't spend any more time on this, so if it's not possible to create a reliable repro then I'm afraid we'll have to close this. For all we can tell, it could be a change to Netlify itself. It seems quite unlikely that a change to Kit would result in this behaviour — far more likely to be a change to adapter-netlify.

Hmmmm, i left a clean git commit history so you could see what changes i made. Barely any. I apologize i took the site down. Got overzealous cleaning stuff up. I can redeploy it, but it sounds like you're confident this isn't a Svelte-Kit issue anyways. Also, I moved past the issue by creating a +page.ts so it's not an issue which is bothering me any longer so we can close it if you'd like. I'd be okay with that.

authors: Rich-Harris papiro


text:
Adapter Vercel Image Optimizations

Describe the problem
Would be really awesome if adapter-vercel package accepted images option for using Vercel's native image optimization. It only requires simple addition of images object to build config file .vercel/output/config.json.  I would submit a pull request but I am sure the options, naming conventions, etc would not be as the team would desire. Given it is such a straightforward task it probably wouldn't prove helpful.
Describe the proposed solution
Here are the options
type ImageFormat = 'image/avif' | 'image/webp';

type RemotePattern = {
  protocol?: 'http' | 'https';
  hostname: string;
  port?: string;
  pathname?: string;
};

type ImagesConfig = {
  sizes: number[];
  domains: string[];
  remotePatterns?: RemotePattern[];
  minimumCacheTTL?: number; // seconds
  formats?: ImageFormat[];
  dangerouslyAllowSVG?: boolean;
  contentSecurityPolicy?: string;
};

https://vercel.com/docs/concepts/image-optimization
https://vercel.com/docs/build-output-api/v3#build-output-configuration/supported-properties/images
Alternatives considered
No response
Importance
nice to have
Additional Information
No response

I'm not sure just adding the options is enough, there's also work involved to create a specific image component I guess? Related to #241

I'm not sure just adding the options is enough, there's also work involved to create a specific image component I guess? Related to #241

you can leave that to the community, because thats more subjective and that would be separate from an adapter package anyway,  but without the ability to put these options in the build config then you can't use it, so this shouldn't be the breakpoint of using features

Also all the solutions I have seen are for local images, not remote images.

I'm not sure just adding the options is enough, there's also work involved to create a specific image component I guess? Related to #241

Next and Nuxt have supported image components, but from my understanding once enabled you could also just update your image srcs manually from eg /public/images/logo.png to /_vercel/image?url=/public/image/logo.png?w=320&q=80. A fancy image component could come later if the community wants it, but just enabling this would be a great enhancement IMO

Next and Nuxt have supported image components, but from my understanding once enabled you could also just update your image srcs manually from eg /public/images/logo.png to /_vercel/image?url=/public/image/logo.png?w=320&q=80. A fancy image component could come later if the community wants it, but just enabling this would be a great enhancement IMO

Exactly

@lettucebowler has made a PR for this #8667.

Someone shared an example on Discord (https://discord.com/channels/457912077277855764/1068354495240741005/1070047413898850424)
// Image.svelte

<script lang="ts">
  import { dev } from '$app/environment';

  let className = ""
  export { className as class };
  export let image:WpImage
  export let showTitle = false
  export let lazy = true
  export let height  = 1280
  export let quality = 70
  export let width = 720
  export let unoptimized = false

  const sizeArr = [640, 768, 1024, 1280, 1536, 2048]

  const vercelImg = (sourceUrl:string,size:number) =>
  (`/_vercel/image?url=${encodeURIComponent(sourceUrl)}&w=${size}&q=${quality} ${size}w`)

  $:({ srcSet, sourceUrl, title, altText} = image)
  $: vercelSrcSet = sizeArr.map(size=>vercelImg(image?.sourceUrl,size)).join(',')

  // dyanmic srcset only for optimized (w/vercel)
  $: imageSrcSet = (unoptimized || dev) ? srcSet : vercelSrcSet

  let element
</script>

<img
  {width}
  {height}
  title={showTitle ? title : undefined}
  srcset={imageSrcSet}
  src={sourceUrl}
  alt={altText ?? title}
  class={className ?? undefined}
  loading={lazy ? 'lazy' : 'eager'}
  {...$$restProps}
  bind:this={element}
/>

// scripts/vercel-images.js
import fs from 'node:fs';
import dotenv from 'dotenv'
dotenv.config()
// sizes should be shared variable with Image component
import {sizes} from './theme.cjs'

const file = '.vercel/output/config.json';

const config = {
  ...JSON.parse(fs.readFileSync(file, 'utf-8')),
        images: {
                "sizes": sizes,
                "domains": [],
                "minimumCacheTTL": 60,
                "formats": ["image/avif", "image/webp"],
                "remotePatterns": [
                        {
                            "hostname": "yourcdn\\.cloudfront\\.net$"
                        },
                ]
            }
};

fs.writeFileSync(file, JSON.stringify(config, null, 2));

// package.json

"build": "vite build && node scripts/vercel-images",

@benmccann do you have working example hoisted anywhere (e.g. GitHub, Code sandbox etc. ). I wanted to see the configuration details. Thanks.

There's a draft PR for this: https://github.com/sveltejs/kit/pull/10323

Hi @hartwm, thanks so much for providing these examples! I do have one question I wonder if anyone knows the answer to.
Vite lets you import images like this:
<script>
	import logo from '$images/example.png';
</script>

That means that a hash gets put in their name so that they can be cached forever. Is it possible to use such an image with the Vercel image solution?
When I go to https://vercel-images-sveltekit.vercel.app/ I notice that the local image can't be cached as strongly as the Vite processed images we have today. If you hit the page a second time, it returns a 304 response as opposed to avoiding the request entirely. I wonder if it's possible to use an imported image so that Vite processes the request before Vercel takes over possibly allowing us to skip the request entirely still. If it's possible, it'd be a great example to add to https://github.com/hartwm/vercel-images-sveltekit

@benmccann You can set Cache-Control headers with Vercel...
https://github.com/leoj3n/svelte-vercel-optimized-images?tab=readme-ov-file#avoiding-304-network-requests
It looks like you merged https://github.com/sveltejs/kit/pull/8667#pullrequestreview-1730990777 which relates to the OP... Considering the ability to set Cache-Control with Vercel, your remaining question may be answered, and so you might now be able to close this open issue.

@benmccann Regarding "Vite processes the request before Vercel takes over"...
It kind of defeats the purpose of using Vercel to send the correct image type (avif/webp) based on headers sent from the browser, as well as the (pre-defined) dynamic image sizes. If you circumvent Vercel you would have to generate all those permutations ahead of time yourself which could be prohibitive for user uploaded images, as mentioned.
I do believe Next.js implements their own code that emulates what the Vercel image optimization endpoint does, so it may be possible to add such functionality to SvelteKit itself, but you probably will have a very similar approach.

authors: aakash14goplani benmccann dummdidumm hartwm izznatsir leoj3n lettucebowler


text:
Fetching works on initial page load, not on page reload

Describe the bug
I'm fetching data from an API in my route's load function, but I can't find a way to make it work on subsequential loads.
Logs
using ctx.fetch: TypeError: Failed to execute 'fetch' on 'Window': Illegal invocation at load
using fetch: ReferenceError: fetch is not defined at load
To Reproduce
install sveltekit
create a component that loads data in the <script> tag, as follows:
export async function load(ctx) {     // Call our fetch     let postsData;     postsData = await fetch( 	    'https://jsonplaceholder.typicode.com/posts' 	    ).then((x) => x.json());     console.log(postsData); }
Expected behavior
I expect the response to be logged to the console on each pageload.
Using fetch, it works on initial load, not reloads.
Using ctx.fetch, it works on reloads, but not inital load.
Stacktraces
Unfamiliar with stacktraces. This is my first time publishing an issue to a repo, so any information about this/how I can better format my issues would be much appreciated. I have more bugs/issues I've found that I'm too scared to post. Really hate bugging you guys when you're working so hard, but I'm lost on a few things.
Information about your SvelteKit Installation:

Diagnostics

The output of npx envinfo --system --npmPackages svelte,@sveltejs/kit,vite --binaries --browsers
System:
OS: Windows 10 10.0.19042
CPU: (8) x64 Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
Memory: 8.92 GB / 15.89 GB
Binaries:
Node: 15.11.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.10 - ~\AppData\Roaming\npm\yarn.CMD
npm: 7.7.5 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: Spartan (44.19041.423.0), Chromium (89.0.774.68)
Internet Explorer: 11.0.19041.1
npmPackages:
@sveltejs/kit: next => 1.0.0-next.69
svelte: ^3.29.0 => 3.37.0
vite: ^2.1.0 => 2.1.5

Your browser

(Using NPM & Brave Web Browser)

Your adapter (e.g. Node, static, Vercel, Begin, etc...)
Node adapter

Severity
How severe an issue is this bug to you? Is this annoying, blocking some users, blocking an upgrade or blocking your usage of SvelteKit entirely?
I guess I could store content statically, but this is a big problem for me as I'm trying to use Sveltekit to refactor some of my projects that use APIs everywhere. Axios might work as a workaround, but I'm trying to use as many Svelte/Sveltekit features as possible because I'm a big believer in what you guys are doing. If I could figure this out & some other problems I'm having, I'm ready to start refactoring some of my projects to use Svelte/Sveltekit instead of react & related helped frameworks
Additional context
I love what you guys are doing & would love to help if I can. Svelte is a breath of fresh air after getting annoyed & leaving the development community years ago. Thank you so much for everything youre doing, even if you can't help me out

One thing to remember with the load function is that it can run on both the server OR the client.
So when you say you see it in the console, do you mean the terminal window where you are running npm run dev or the browser console?
With SSR enabled (the default) the load function is called on the server and the response embedded into the page so that it doesn't need to re-run on the client (but in dev, it does re-run). One the app has been loaded then navigating between routes will call the appropriate load functions for them but only on the client at that point. So, be sure to check both.
Minor tip: as you already have the function marked as async it's easier to use await than ye-olde promise chaining, so you could write:
export async function load(ctx) {
  const resp = await fetch( 'https://jsonplaceholder.typicode.com/posts' )
  const post = await resp.json()
  return {
    props: post
  }
}

(assuming the route component has a property named post)

@evan-thurston You're forgetting to use the fetch parameter passed to your load function. Because load can run on the server or the client, but the built-in window.fetch function is only available on the client, Svelte-Kit includes a fetch function that will work in either environment, and passes it to your load function as a parameter. You're supposed to use that function rather than the built-in fetch. So change your load function to use ctx.fetch instead of fetch and it should work. Or rewrite it the way the documentation recommends (and the way CaptainCodeman showed in his example) using destructuring to get the fetch parameter, i.e. export async function load({ fetch }) and then you can just write await fetch('...') and you'll be using Svelte-Kit's supplied function.

authors: CaptainCodeman evan-thurston rmunn


text:
Component styles flicker/blink with SSR mode on

Describe the bug
When applying stylings to components or pages, on SSR mode, first server stylings get rendered, and then client ones.
In some cases, when components / pages use more 'dynamic' data like slots, $$restProps with class names, lists, etc., what oddly happens is that there is a 'flicker', where server stylings do not seem to match client ones.
Below is a video with two examples of when this happens:
https://github.com/sveltejs/kit/assets/61620873/e5688342-1c23-4994-a4ba-807fc1247e1b
Reproduction
About twenty lines: https://www.sveltelab.dev/vg1t4x2cb8n84f4
Logs
No response
System Info
I've spoken to a number of people so I don't think that it is a device-specific thing. But anyway:

  System:
    OS: macOS 13.3.1
    CPU: (8) arm64 Apple M1
    Memory: 83.23 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 19.6.0 - /opt/homebrew/bin/node
    Yarn: 1.22.11 - /opt/homebrew/bin/yarn
    npm: 9.4.0 - /opt/homebrew/bin/npm
  Browsers:
    Brave Browser: 113.1.51.114
    Safari: 16.4
  npmPackages:
    @sveltejs/adapter-auto: ^1.0.0-next.91 => 1.0.0-next.91
    @sveltejs/kit: next => 1.0.0-next.589
    svelte: ^3.55.1 => 3.55.1
    vite: ^4.0.0 => 4.1.1

Severity
annoyance
Additional Information
No response

The same issue happens even when setting export const csr = false. Interestingly, the only workaround seems to be wrapping for loops in a flexbox.

   {#each item as item}

               Page

   {/each}

But I would suggest this approach be avoided. When setting e.g. 5 divs (without the for loop), there are no spaces. Only through the above do they have spaces on the server-rendered HTML, and then revert to no spaces / gaps as expected (see repro). So this seems to be more of a workaround than expected behavior.

This issue is not caused by when styles are applied, but differences in the whitespace present in the SSR markup and the client-side rendered elements.
The SSR markup inserts a text node with "\n     " between each child div:

But when client-side rendered, those nodes are removed:

There are multiple whitespace issues open in the Svelte repo, so not sure if this is a duplicate or not (or what workarounds would be). Transferring over there for now.

authors: Destaq geoffrich


text:
Inspector - open parent component

Describe the problem
If I have a button and i open it with inspector, it opens the button component, but usually I dont care about the button component, but about component where the button is used.
Describe the proposed solution
If i click on component with inspector, i could get list of parents for this component and i could click on one of them to open them instead. It would open parent component on line, where selected component is used.
Inspector could have current behavior on left click and this more advanced one could be on right click.
Alternatives considered

Importance
would make my life easier

you can use the up arrow key to select the parent component

@ToP29  does arrow selection help with your usecase?

Yes, it is ok. Thank you

repo: sveltejs/vite-plugin-svelte


text:
Svelte 5 - css nesting broke

Describe the bug
Not sure if this is the right spot to report, but since the error window mentions this plugin specifically, figured I'd start here.
Anyways, not sure if I'm doing something wrong but in the current stable version of Svelte, the following component compiles and functions as expected

Welcome to SvelteKit

Visit kit.svelte.dev to read the documentation

However in the current Svelte 5 beta,  an error is triggered saying Expected a valid CSS identifier. This is tested from a fresh install of SvelteKit running

npm create svelte@latest

afterwards running

npm install svelte@next

to install Svelte 5
Not sure how support was implemented in Svelte 4 but it'd be great to have this working in the final release without having to download another package.
Reproduction URL
https://github.com/sortofsleepy/svelte5-vite-css-error
Reproduction

Svelte 5 should already be setup in package.json so error should pop up immediately
Rerun npm i svelte@latest to compare and contrast.

Logs
[plugin:vite-plugin-svelte] C:/Users/Joseph/Documents/projects/tests/svelte-test/src/routes/+page.svelte:9:1 Expected a valid CSS identifier

C:/Users/Joseph/Documents/projects/tests/svelte-test/src/routes/+page.svelte:9:1

7  |  			color:red;
8  |  		}
9  |  	}
   |   ^
10 |  </style>

CompileError: Expected a valid CSS identifier
    at error (file:///C:/Users/Joseph/Documents/projects/tests/svelte-test/node_modules/svelte/src/compiler/errors.js:568:8)
    at read_identifier (file:///C:/Users/Joseph/Documents/projects/tests/svelte-test/node_modules/svelte/src/compiler/phases/1-parse/read/style.js:491:3)
    at read_selector (file:///C:/Users/Joseph/Documents/projects/tests/svelte-test/node_modules/svelte/src/compiler/phases/1-parse/read/style.js:289:11)
    at read_selector_list (file:///C:/Users/Joseph/Documents/projects/tests/svelte-test/node_modules/svelte/src/compiler/phases/1-parse/read/style.js:157:17)
    at read_rule (file:///C:/Users/Joseph/Documents/projects/tests/svelte-test/node_modules/svelte/src/compiler/phases/1-parse/read/style.js:139:12)
    at read_body (file:///C:/Users/Joseph/Documents/projects/tests/svelte-test/node_modules/svelte/src/compiler/phases/1-parse/read/style.js:64:18)
    at read_style (file:///C:/Users/Joseph/Documents/projects/tests/svelte-test/node_modules/svelte/src/compiler/phases/1-parse/read/style.js:25:19)
    at tag (file:///C:/Users/Joseph/Documents/projects/tests/svelte-test/node_modules/svelte/src/compiler/phases/1-parse/state/element.js:264:20)
    at new Parser (file:///C:/Users/Joseph/Documents/projects/tests/svelte-test/node_modules/svelte/src/compiler/phases/1-parse/index.js:65:12)
    at parse (file:///C:/Users/Joseph/Documents/projects/tests/svelte-test/node_modules/svelte/src/compiler/ph

System Info
System:
    OS: Windows 10 10.0.19045
    CPU: (24) x64 AMD Ryzen 9 5900X 12-Core Processor
    Memory: 16.00 GB / 31.90 GB
  Binaries:
    Node: 20.8.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.1.0 - C:\Program Files\nodejs\npm.CMD
    pnpm: 6.32.3 - ~\AppData\Roaming\npm\pnpm.CMD
  Browsers:
    Edge: Spartan (44.19041.3570.0), Chromium (119.0.2151.58)
    Internet Explorer: 11.0.19041.3570

native css nesting isn't supported in svelte4 by itself, some parts of it work but thats because svelte4 uses css-tree. svelte5 does not and hasn't implemented native css nesting yet.
To work around this, use a preprocessor that converts nested syntax to unnested. This can be done with postcss or lightningcss (experimental option on vite)

see https://github.com/sveltejs/svelte/issues/8587 and https://github.com/sveltejs/svelte/pull/9343
closing here as it is not caused by vite-plugin-svelte. Please follow the issues on svelte repo for updates.

authors: dominikg sortofsleepy