text:
Question about fundamental differences between postgrest-starter-kit vs subzero-starter-kit

Hi,
I just started to learn postgrest-starter-kit, subzero-starter-kit and jekirl/postgrest-starter-kit and I found that, even they more-or-less provide solution for the "same" problem, they provide different functionality and services when we look at the details.
If I am right, some basic differences are:

subzero-starter-kit focuses on using postgrest-plus in the background and provide tools for easy subzerocloud migration/support
postgrest-starter-kit is for open-source postgrest not as tightly boundled to subzero
jekirl/postgrest-starter-kit is a restructured and modified subzero-starter-kit
all-of-them basically based on docker
only subzero provides a logout function which deletes the cookie on the client using set-header function

Feature
subzero-*
postgrest-*
jekirl-*

postgrest

X
X

postgrest-plus (1 connection)
X

docker image all-included except pgsql
X

separate docker images for components (db, postgrest, rabbitmq, openresty)

X
X

supports cookies via set-header
X

provides logout function out of box by deleting cookie
X

Anything else, which should be important?
(I will extend this post as I will have more time)

The first major difference is that subzero-* (while the code in repo is MIT) uses the docker images from subzero which are commercial products.
Other notes:

jekirl-* seems to be a fork of the old postgrest starter kit, not seeing any "restructuring/improvements"
cookies-* can be used postgrest-* but the thing that makes them work in this context is the "cookie auto refresh" mechanism which is part of the subzero's commercial offering.
separate containers - there are separate containers for subzero-* also however a single container is a feature, not a weakness (easier to deploy, faster intercontainer communication )
subzero-* (through a combination of code in postgrest-plus and openresty) provides analytical queries (groupby, window functions), function call in select, graphql api and (upcomming) odata api.

that's a bird-eye view

Thank you, that explain what I experienced when I evaluated all the three variants.
From my point of view, docker is not an option, but it was really easy to test them and I can imagine the benefits of using them for those folks, who use docker as basis.
Thanks again!

docker is not the only option (after all it only wraps binaries configs and lua scripts) however it's much more tedious to setup

Sorry, my bad, I was not so careful when I wrote that.
So, I have different existing infrastructures where I plan to use postgrest-starter-kit, but without any docker related magic or subzero-cli. This is because I prefer the existing infrastructure, where I already have some of the stack components.
I really like this kind of stack (pgsql + postgrest + rabbitmq + openresty) and the way you bundled into a template in your commercial container with postgrest-plus and into an open source free psk.

authors: pongraczi ruslantalpa

repo: subzerocloud/postgrest-starter-kit


text:
ion icons now showing any longer

I noticed today that all the icons from the ion icon set are not showing up in my custom made tool bar. Can anyone reproduce the issue with other tool bars?

Seems to be the same as #264, #266, #268, #269, it's caused by an update to the font (in #263). Try prefixing them with md- or ios-. Some icons may also have been removed (not sure about that), anyway you can have a look at the Ionicons website to find the right names for the icons.
Hope that helps :slightly_smiling_face:

@ericcornelissen Thank you so much, it does help. It turns out all icons from ion must now be prefaced by either md- or ios-, and a lot of them have been removed or renamed. It's just a bit confusing because searching for an icon on their website using md- or ios- does not match anything.

source: gharchive/issue

authors: ericcornelissen gilbertohasnofb

repo: suda/tool-bar

license: mit

license_type: permissive

license_source: bigquery


text:
Update schema to latest version.

It not update.

Thanks!!

source: gharchive/pull-request

authors: Manfred sudara

repo: sudara/alonetone

license: MIT

license_source: github-api


text:
Feature Request: Apply to Login Screen as well

As the title says: I would like to hide the clock on the login screen as well as when logged in. Is that possible?

Just saw this, I will attempt to incorporate it within the following weeks!

authors: shade-belisar sudfish

repo: sudfish/Hide-Clock-Extension


text:
vercel build breaking - Error: Detected unsupported "use-node-version" in your ".npmrc".

Error: Detected unsupported "use-node-version" in your ".npmrc". Please use "engines" in your "package.json" instead.
16:21:42.667 | Error: Command "vercel build" exited with 1
16:21:42.709 | Command "vercel build" exited with 1

@devilankur18  is this issue is still open? or someone fixed this

@AmolShelke2 this is closed.

repo: sugarcane-ai/sugarcane-ai


text:
Updated Readme file

Contributes towards #20

We want the activity to work inside Sugar.  Please make sure it does so and include how to do it in the documentation.  You may need to make changes to other repositories to get it to work.

@quozl i am bit confused, can you give me a bit more clear instruction about task.......

We want the activity to work inside Sugar. Please make sure it does so and include how to do it in the documentation. You may need to make changes to other repositories to get it to work.

should i take reference from this https://github.com/sugarlabs/sugar-docs/blob/master/src/web-activity.md

@quozl i will look into these and add this section in this files

It does relate. I can't give clear guidance; if I knew what was to be done I'd probably do it.
https://github.com/sugarlabs/sugar-web is the software component that provides an interface between Sugar and an activity of language JavaScript.
https://github.com/sugarlabs/sugar is the Sugar graphical shell for use on desktop and laptop computers, written in C, Python, and GTK. This can be installed on Linux.
https://github.com/llaske/sugarizer is the JavaScript graphical shell and activities for use on tablets, phones, and other computers, written in JavaScript.
This repository connect-the-dots is a Sugar activity that depends on sugar-web and sugar repositories to be used.
Our GSOC repository may also have some interesting ideas.

I was able to run the activity to work inside Sugar. And have updated the readme file....

@quozl should i make a pr in sugarizer to add this activity??

Great that you got it working inside Sugarizer, but that's not what I'm asking about.  I'm asking about running the activity inside Sugar.
@llaske would be best person to ask about adding to Sugarizer.  He will likely consider if the activity is meaningful in the context of the other activities already in Sugarizer.

sugar-web links JavaScript activities into sugar-toolkit-gtk3 using WebKit.
Continue looking.

repo: sugarlabs/connect-the-dots-activity


text:
Adding hire page #3

closes #3
This page should have a list of reasons why my future recruiter should hire me. This page has further pages:- an experience page, an essay page and a projects page.

#3 issue closed


text:
Set functional defaults for media headers and ghostscript path

Tasks:

[x] test coverage
[ ] gather feedback for my changes
[x] added changelog line

Informations:

Q
A

Tests pass?
yes

Fixed tickets
fixes #983, fixes #982

BC Breaks
yes?

Doc
none

Part of: https://github.com/sulu-io/sulu-standard/pull/437/files

@alexander-schranz we should remove the default values from parameters.yml?

@wachterjohannes done in this PR: https://github.com/sulu-io/sulu-standard/pull/437/files

authors: alexander-schranz wachterjohannes

repo: sulu-io/sulu


text:
Make Face Mask Detector

Spot the mask-wearers and non-mask-wearers in the crowd.
Utilize a pre-trained deep learning model to detect whether a person is wearing a face mask in real-time from webcam input or image files.

Can I take ownership of this issue, @sumanth-0? I’m ready to handle it!


text:
Make Guess The Number Reverse (AI version)

Solves issue #102
This PR implements a number guessing game in Python using a binary search algorithm.
Players think of a number within a specified range, and the program makes intelligent guesses based on user feedback.
Below are the key components and features of the implementation:

The game starts by prompting the user to set an upper limit, ensuring the chosen number is greater than 1.
Players think of a number within that range, and the program utilizes binary search to minimize attempts by asking if the guess is higher, lower, or correct.
The game keeps track of the number of attempts, providing feedback on how quickly the player's number was guessed.

Hi! I’ve updated the file structure as requested. Is it possible now?


text:
🛑 SISTEMA ROYAL-HOLIDAY is down

In c598efa, 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 a278a3f.


text:
3.6.0 Started overriding my code coloring

How are you using the lua-language-server?
Visual Studio Code Extension (sumneko.lua)
Which OS are you using?
Windows
What is the issue affecting?
Other
Expected Behaviour
Not to override all my editor colors
Actual Behaviour
3.6.0 Started overriding my code coloring and there does not seem to be an option to stop it.
Reproduction steps
Update to 3.6.0+
Additional Notes
No response
Log File
No response

Please provide screenshot with command editor.action.inspectTMScopes

When I open the workspace everything looks fine until the extension finishes loading/scanning everything then it changes the styles.

Maybe you are looking for Lua.semantic.enable.
Otherwise, you can custom semantic style by editor.semanticTokenColorCustomizations

Thanks those will do it.

repo: sumneko/lua-language-server


text:
Remove item doens't work properly

This is caused by the use of index as a key int the list of elements

Hello, I wanna join your team.

repo: sun-empire-solutions/todo-app


text:
Would this work for SIP/VoIP on Kamailio/Opensips

Hi there.
Apologies for raising a ticket. Was unsure how to get in touch. I would like to implement this with a SIP proxy (Opensips) to send push notifications to APNS + Firebase. Can your project be used in this scenario?
Thanks.

I have never done this before so I do not know.
We are sorry.

Not a problem. Thx for responding, but it would be possible to send notifications to APNS + Firebase?

but it would be possible to send notifications to APNS + Firebase?

Yes.

repo: sunaoka/push-notifications-php


text:
SFENMove などの名前を USIMove などに変更するべき

SFEN 自体は USI プロトコルで使われる局面情報の表し方であり、指し手などの表記は SFEN には含まれず、USI プロトコルの一部なので、parseSFENMove や newByUSIFromSFENPosition などの名前を parseUSIMove や newByUSIFromUSIPosition または newByUSIFromSFEN (または冗長だがそのまま newByUSIFromSFENPosition) に変更するべきと考えます。

将棋所の作者さんのウェブサイトだと混合したような説明になっていますが、@romstad さんの説明や FEN についての文書を見ると SFEN や FEN 自体は局面情報のみの意味で使われていることが多いと思います。

repo: sunfish-shogi/electron-shogi


text:
Fix used config indices and update Desarrolla cache package to ~2.0

Hi there, another PR to address a couple issues I ran into:

In the Desarrolla cache package v1.8, the MemCache driver always adds localhost as a server. This will result in errors if memcache is run elsewhere. This has been corrected in v2.0, thus the package update.
The DesarrollaCacheFactory used incorrect config indices for some adapters. This has been corrected, and I've added some tests for these functions (skipping those for which the required depedency is not available locally)

Thank you @Feijs !!

authors: Feijs sunspikes

repo: sunspikes/php-ratelimiter


text:
Signup auth metadata UUID incompatibility.

Describe the bug
I have a function that runs when signing up a user that extracts the metadata and then inserts some values into another table but the issue is inserting values from metadata for columns that require UUID is not possible as UUID is not serialisable in JSON. So I have to send the data as text but the issue is Postgresql throws error saying type expected is of UUID but text given.
To Reproduce
      response = supabase.auth.sign_up({
        "email": email,
        "password": password,
        "options": {
            "data": {
            "first_name": first_name,
            "last_name": last_name,
            "role": role,
            "organization_name": organization_name,
            "organization_id": organization_id
            }
        }
        })

organization_id column ideally requires UUID.
Error
column "organization_id" is of type uuid but expression is of type text
function:
handle_new_user
  begin
    insert into public.users (id, first_name, last_name, organization_name, organization_id, role)
    values (new.id, new.raw_user_meta_data->>'first_name', new.raw_user_meta_data->>'last_name', new.raw_user_meta_data->>'organization_name', new.raw_user_meta_data->>'organization_id', new.raw_user_meta_data->>'role');
return new;
end;

I figured it out!
just had to enclose the required column into uuid()
 begin
    insert into public.users (id, first_name, last_name, organization_name, organization_id, role)
    values (new.id, new.raw_user_meta_data->>'first_name', new.raw_user_meta_data->>'last_name', new.raw_user_meta_data->>'organization_name', uuid(new.raw_user_meta_data->>'organization_id'), new.raw_user_meta_data->>'role');
return new;
end;

repo: supabase-community/supabase-py


text:
fix: check for Deno

Build errors as Deno is undefined when not using the global runtime.

cc: @hf jfyi

repo: supabase/gotrue-js


text:
webhooks: order is not guaranteed on rapidly generated requests to same end point.

Improve documentation
I suggest adding a note in the docs that for rapidly generated requests order of the http requests at the endpoint is not guaranteed.
Based on observation testing realtime broadcast endpoint and bulk inserts the requests arrive out of order at the endpoint.    I assume this is because the actual http request generated by pg_net does not wait for a response before sending the next request.  With http there is no guarantee the requests will arrive in order especially with a very short time span between them.
The lack of order was observed both with realtime endpoint and a webhook service endpoint.
The sequence generating the order issue is a bulk insert
insert into cats (count)
select * from generate_series (2300,2350)

The trigger function calls pg_net per row.
Note: It would be useful to have a mode where pg_net would be "sync" on the http side.  It could wait for response before sending next response (especially if url is same).  It will still be async on the SQL caller side so different that the http extension.

I don't think any async HTTP client guarantees order, why is this needed?

Note: It would be useful to have a mode where pg_net would be "sync" on the http side. It could wait for response before sending next response (especially if url is same). It will still be async on the SQL caller side so different that the http extension.

IIUC, you want the HTTP requests to be done in order, I don't think this is possible (or straightforward) with the current epoll implementation (https://github.com/supabase/pg_net/pull/139) as the file descriptors might be readable/writable at different times. But really this is a strange requirement for an async HTTP client. I would like to know if any other client supports something like that.

Just saying it should be mentioned maybe at the webhook level as users issuing webhooks close together from something like inserts may expect them to show up in order at their edge function.  Not sure pg_net is even mentioned at the webhook level.
Maybe I'm naive, but had not thought about it before, and in doing realtime broadcasts with pg_net on bulk inserts, got caught off guard when they would show up out of order.
If you think all your users of webhooks understand this, then feel free to ignore.
Was not asking for a fix from pg_net, it just makes it not usable for doing realtime broadcasts where order might be needed.  Which was the task at hand at the time to avoid using http extension or notify as a way to have higher performance than postgres_changes with RLS.

You Can't Guarantee Webhook Ordering
You obviously CAN guarantee ordering, it's just that you can't guarantee it as the sender, you need cooperation from the receiver.

References:

https://www.svix.com/blog/guaranteeing-webhook-ordering/
https://news.ycombinator.com/item?id=32333661

So it looks like the sender can't guarantee order.

If you think all your users of webhooks understand this

webhooks uses pg_net but is another component in the end, there's no control over it on this repo. Maybe this ordering matter can be documented once webhooks is established as a pg extension (see https://github.com/supabase/postgres/pull/1152). It may be added here or in another repo.


text:
Custom HEAD request for object info

What kind of change does this PR introduce?
feature
What is the current behavior?
Current HEAD implementation would download the file from S3
What is the new behavior?
A custom HEAD route  that will return the file headers and check RLS upon request

Pull Request Test Coverage Report for Build 3234814719

140 of 173 (80.92%)  changed or added relevant lines in 6 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.3%) to 84.32%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/backend/s3.ts
0
4
0.0%

src/backend/file.ts
1
13
7.69%

src/routes/object/getObjectInfo.ts
130
147
88.44%

Totals

Change from base Build 3233928817:
-0.3%

Covered Lines:
3400

Relevant Lines:
3979

💛  - Coveralls

authors: coveralls fenos

repo: supabase/storage-api


text:
WASM FDW url resolution issue

Bug report
I have a few custom FDW's written with the postgres_fdw template provided. I've been working on an interesting error:
Query 1 ERROR at Line 1: : ERROR:  wasmtime error: WebAssembly translation error
There seems to be some incorrect logic in handling http(s) related remote connections.
https://github.com/supabase/wrappers/blob/8a30794da96da18b013beccfa7a957a998689a1d/wrappers/src/fdw/wasm_fdw/wasm_fdw.rs#L46-L122
Describe the bug
Remote supabase postgres (15.6) database issues a: Query 1 ERROR at Line 1: : ERROR:  wasmtime error: WebAssembly translation error after defining a remote server and foreign table pointing at a https file hosted outside of the "release process" on GitHub actions. Local postgres (16.6) crashes.
To Reproduce
first test:

compile fdw: cargo component build --release --target wasm32-unknown-unknown
create foreign wrapper with said output (I know checksum calculations aren't used for file:///)
test and works

second test:

compile fdw:  cargo component build --release --target wasm32-unknown-unknown
serve the file via a simple Python server locally or in my case Deno (2.1.2).
test and works http://localhost:8000/fdw/test_fdw.wasm

third test:

stick compiled fdw anywhere; on a supabase S3 bucket,  apache httpd server, even a public release on GitHub
after compiling locally via gh release
create server, foreign table and see error prop up.

fourth test:

use local postgres
point to remotely hosted wasm
create server and table
postgres crashes

behavior is also present (no database crash) but WASM error on Postgres 15.6 (hosted on Supabase)
This reliably works on all supabase wasm-fdw's built locally with: cargo component build --release --target wasm32-unknown-unknown and served via any of the aforementioned endpoints: paddle, notion, etc.
case@corp paddle_fdw % wasm-tools validate -vv target/wasm32-unknown-unknown/release/paddle_fdw.wasm
[2024-12-05T18:31:28Z INFO ] read module in 733.167µs
[2024-12-05T18:31:28Z INFO ] module structure validated in 3.883958ms
[2024-12-05T18:31:28Z INFO ] functions validated in 1.401333ms

case@corp paddle_fdw % curl -I https://wiw.org/~case/paddle_fdw.wasm
HTTP/1.1 200 OK
Date: Thu, 05 Dec 2024 18:32:10 GMT
Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/5.4.16
Strict-Transport-Security: max-age=63072000; includeSubdomains; preload
Last-Modified: Thu, 05 Dec 2024 18:16:20 GMT
ETag: "28629-62889e5289c1e"
Accept-Ranges: bytes
Content-Length: 165417

< HTTP/2 200
< content-type: application/octet-stream
< content-disposition: attachment; filename=paddle_fdw.wasm
< content-length: 133622
< accept-ranges: bytes
< cache-control: public, max-age=3600
< last-modified: Thu, 05 Dec 2024 02:16:47 GMT
< access-control-allow-origin: *
< vary: Accept-Encoding
< date: Thu, 05 Dec 2024 18:39:14 GMT
< via: http/2 edgeproxy-h

headers off another remote with should be the correct  headers to indicate to reqwest to allow a successful download. I believe the current document deployment process is one where the GitHub action provided (softprops/action-gh-release@v2):
https://github.com/softprops/action-gh-release/blob/92bc83c4214f780e84c7d2a85464a2ca05ebc2f0/src/github.ts#L143-L154
sets the correct mime type and serves it correctly as my test on manually issuing a release via gh release with the compiled output which is confirmed to be correct is also failing.
Here's the current headers off the actual released artifact:
curl -L -I https://github.com/supabase/wrappers/releases/download/wasm_paddle_fdw_v0.1.1/paddle_fdw.wasm

HTTP/2 200
content-type: application/octet-stream
last-modified: Wed, 14 Aug 2024 06:57:09 GMT
etag: "0x8DCBC2E5148BA20"
server: Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0
x-ms-request-id: ddf6a6fa-f01e-0011-3d14-407be1000000
x-ms-version: 2024-08-04
x-ms-creation-time: Wed, 14 Aug 2024 06:57:09 GMT
x-ms-lease-status: unlocked
x-ms-lease-state: available
x-ms-blob-type: BlockBlob
content-disposition: attachment; filename=paddle_fdw.wasm
x-ms-server-encrypted: true
accept-ranges: bytes
date: Thu, 05 Dec 2024 18:56:53 GMT
via: 1.1 varnish
age: 8
x-served-by: cache-iad-kjyo7100088-IAD
x-cache: HIT
x-cache-hits: 1
x-timer: S1733425014.504189,VS0,VE1
content-length: 163743

The testing of local HTTP caching seems to be off as I frequently have to remove the cache rm * ~/Library/Caches/*.wasm to get it to reload even over local HTTP.
Final output:
case@corp paddle_fdw % curl -L https://github.com/supabase/wrappers/releases/download/wasm_paddle_fdw_v0.1.1/paddle_fdw.wasm > wut.wasm
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  159k  100  159k    0     0   490k      0 --:--:-- --:--:-- --:--:--  490k
case@corp paddle_fdw % wasm-tools validate -v wut.wasm
[2024-12-05T18:59:01Z INFO ] read module in 78.625µs
[2024-12-05T18:59:01Z INFO ] module structure validated in 5.570375ms
[2024-12-05T18:59:01Z INFO ] functions validated in 1.703584ms
case@corp paddle_fdw % curl -L https://wiw.org/~case/paddle_fdw.wasm > why.wasm
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  161k  100  161k    0     0   121k      0  0:00:01  0:00:01 --:--:--  121k
case@corp paddle_fdw % wasm-tools validate -v why.wasm
[2024-12-05T18:59:41Z INFO ] read module in 148.5µs
[2024-12-05T18:59:41Z INFO ] module structure validated in 933.417µs
[2024-12-05T18:59:41Z INFO ] functions validated in 703.166µs

Feel free to use the server mentioned in this docs, here's a simple test:
create server paddle_server
  foreign data wrapper wasm_wrapper
  options (
    fdw_package_url 'http://wiw.org/~case/paddle_fdw.wasm',
    fdw_package_name 'supabase:paddle-fdw',
    fdw_package_version '0.1.1',
    fdw_package_checksum '36ac1cf5eebfa57a70a8d068a21d858a32771cac07721633e3c15ee8841510df',
    api_url 'https://sandbox-api.paddle.com', -- Use https://api.paddle.com for live account
    api_key_id 'test'
);

create foreign table test (
  id text,
  name text,
  email text,
  status text,
  custom_data jsonb,
  created_at timestamp,
  updated_at timestamp,
  attrs jsonb
)
  server paddle_server
  options (
    object 'customers',
    rowid_column 'id'
 );

select * from test;

drop server if exists paddle_server cascade;

Expected behavior
All files served via http(s):// if wasm-tools reports that the file is correct and is working locally should just work
System information
# macOS
case@corp paddle_fdw % uname -a
Darwin corp.local 24.1.0 Darwin Kernel Version 24.1.0: Thu Oct 10 21:02:26 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T8122 arm64
# local postgres
case@corp paddle_fdw % psql -c "SELECT version();"
                                                           version
------------------------------------------------------------------------------------------------------------------------------
 PostgreSQL 16.6 (Homebrew) on aarch64-apple-darwin24.1.0, compiled by Apple clang version 16.0.0 (clang-1600.0.26.4), 64-bit
# supabase
case@corp paddle_fdw % psql $POSTGRES_URL -c "SELECT version();"
                                      version
------------------------------------------------------------------------------------
 PostgreSQL 15.6 on aarch64-unknown-linux-gnu, compiled by gcc (GCC) 13.2.0, 64-bit

I’m not at my computer at the moment, but I have a diff or a PR that fixes this issue I can add in a few hours.

Thank you very much for reporting this issue! We've noticed this issue and identified it was caused by different version of Rust wasm compiler. The GitHub release workflow always used the latest version of Rust, but the Wasm runtime used in Supabase was compiled with older version of Rust, so they are not compatible with each other.
This issue has been fixed in #369, which fixed Rust version to 1.81.0 in the workflow. The same issue hasn't been fixed in the template repo, that's why you saw this issue when using it. I've raised another PR to fix it.

Ah, so the issue on the Supabase platform was caused by binary incompatibility, that's interesting. The remote downloading issue is still an issue with 1.83 as the base from remote locations though, so even though the incompatibility issue will no longer persist, we may end up with incorrect semantics, as local postgres would crash without the new changes applied. Please feel free to test or close if you think it's not an issue.

authors: akacase burmecia

repo: supabase/wrappers


text:
chore: restructure providers to separate category-specific stuff out

common-object-related methods are pulled into crm/engagement categories
all other methods are for generic provider implementations
Test Plan
[Describe test plan here]
Deployment instructions
[Add any special deployment instructions here]

hm there are some circular dependencies here. working them out

fixed circular deps

repo: supaglue-labs/supaglue


text:
chore: release 0.15.2

Test Plan
[Describe test plan here]
Deployment instructions
[Add any special deployment instructions here]

What does this release include?

authors: lucasmarshall tomkit


text:
[BUG:] Crash at /ban

Bug: [Crash at /ban]
Informations
BetterBan Version: 1.4.2 (dev96)
Server-OS: Linux
PHP Version: 8.0.16
PocketMine-MP Version: 4.2.3
Error
PocketMine-MP Crash Dump Wed Mar 16 12:09:05 UTC 2022

Error: include(phar:///home/container/plugins/BetterBan_dev-95.phar/src/supercrafter333/BetterBan/Forms/BBDefaultForms.php): Failed to open stream: phar error: Cannot open phar archive "/home/container/plugins/BetterBan_dev-95.phar" for reading
File: pmsrc/vendor/pocketmine/classloader/src/BaseClassLoader
Line: 93
Type: ErrorException

A PLUGIN WAS INVOLVED IN THIS CRASH
BAD PLUGIN: BetterBan

Code:
[84] 		}, true, $prepend);
[85] 	}
[86]
[87] 	/**
[88] 	 * Called when there is a class to load
[89] 	 */
[90] 	public function loadClass(string $name) : bool{
[91] 		$path = $this->findClass($name);
[92] 		if($path !== null){
[93] 			include($path);
[94] 			if(!class_exists($name, false) and !interface_exists($name, false) and !trait_exists($name, false)){
[95] 				return false;
[96] 			}
[97]
[98] 			if(method_exists($name, "onClassLoaded") and (new ReflectionClass($name))->getMethod("onClassLoaded")->isStatic()){
[99] 				$name::onClassLoaded();
[100] 			}
[101]
[102] 			return true;
[103] 		}

Backtrace:
#0 pmsrc/vendor/pocketmine/classloader/src/BaseClassLoader(93): pocketmine\errorhandler\ErrorToExceptionHandler::handle(integer 2, string[237] include(phar:///home/container/plugins/BetterBan_dev-95.phar/src/supercrafter333, string[95] phar:///home/container/PocketMine-MP.phar/vendor/pocketmine/classloader/src/Base, integer 93)
#1 pmsrc/vendor/pocketmine/classloader/src/BaseClassLoader(93): include()
#2 pmsrc/vendor/pocketmine/classloader/src/BaseClassLoader(83): BaseClassLoader->loadClass(string[46] supercrafter333\BetterBan\Forms\BBDefaultForms)
#3 plugins/BetterBan_dev-95.phar/src/supercrafter333/BetterBan/Commands/BanCommand(57): BaseClassLoader->{closure}(string[46] supercrafter333\BetterBan\Forms\BBDefaultForms)
#4 pmsrc/src/command/SimpleCommandMap(220): supercrafter333\BetterBan\Commands\BanCommand->execute(object pocketmine\player\Player#571593, string[3] ban, array[0])
#5 pmsrc/src/Server(1408): pocketmine\command\SimpleCommandMap->dispatch(object pocketmine\player\Player#571593, string[3] ban)
#6 pmsrc/src/player/Player(1383): pocketmine\Server->dispatchCommand(object pocketmine\player\Player#571593, string[3] ban)
#7 pmsrc/src/network/mcpe/handler/InGamePacketHandler(754): pocketmine\player\Player->chat(string[4] /ban)
#8 pmsrc/vendor/pocketmine/bedrock-protocol/src/CommandRequestPacket(51): pocketmine\network\mcpe\handler\InGamePacketHandler->handleCommandRequest(object pocketmine\network\mcpe\protocol\CommandRequestPacket#601695)
#9 pmsrc/src/network/mcpe/NetworkSession(397): pocketmine\network\mcpe\protocol\CommandRequestPacket->handle(object pocketmine\network\mcpe\handler\InGamePacketHandler#593550)
#10 pmsrc/src/network/mcpe/NetworkSession(360): pocketmine\network\mcpe\NetworkSession->handleDataPacket(object pocketmine\network\mcpe\protocol\CommandRequestPacket#601695, string[25] M./ban. O}..$>..x..s.....)
#11 pmsrc/src/network/mcpe/raklib/RakLibInterface(192): pocketmine\network\mcpe\NetworkSession->handleEncoded(string[29] ..e.OJ.cP..}vM.n...7..s..20..)
#12 pmsrc/vendor/pocketmine/raklib-ipc/src/RakLibToUserThreadMessageReceiver(42): pocketmine\network\mcpe\raklib\RakLibInterface->onPacketReceive(integer 0, string[38] .......g.wZ.......w.G...Y.7..g....h.c.)
#13 pmsrc/src/network/mcpe/raklib/RakLibInterface(122): raklib\server\ipc\RakLibToUserThreadMessageReceiver->handle(object pocketmine\network\mcpe\raklib\RakLibInterface#570920)
#14 pmsrc/vendor/pocketmine/snooze/src/SleeperHandler(123): pocketmine\network\mcpe\raklib\RakLibInterface->pocketmine\network\mcpe\raklib\{closure}()
#15 pmsrc/vendor/pocketmine/snooze/src/SleeperHandler(82): pocketmine\snooze\SleeperHandler->processNotifications()
#16 pmsrc/src/Server(1660): pocketmine\snooze\SleeperHandler->sleepUntil(double 1647432545.1572)
#17 pmsrc/src/Server(1046): pocketmine\Server->tickProcessor()
#18 pmsrc/src/PocketMine(304): pocketmine\Server->__construct(object BaseClassLoader#2, object pocketmine\utils\MainLogger#3, string[16] /home/container/, string[24] /home/container/plugins/)
#19 pmsrc/src/PocketMine(327): pocketmine\server()
#20 pmsrc(11): require(string[60] phar:///home/container/PocketMine-MP.phar/src/PocketMine.php)

readjustment instructions
[I've done...]
[1. Write /ban]
[2. Crash]
fix suggestions [optional]
X

My mistake, now it works, I think I forgot to restart when I put the plugin.


text:
cell layout and spatial diffusion generation part of the code

Hello author, about  cell layout and spatial diffusion generation part of the code, directly run it? I disposed point_den, single_point, and gmm_map and I didn't get good results.

I supplied some details. These details will help you reproduce paper results. Thanks.

Thank you very much for your reply。I run the code you provided and got good results。I made a few minor changes to the inside, just to visualize the image。

But there are some parts that are not square，Will it have a bad effect on the future。Still, the number of epochs I trained was not enough, so I set batch-3 epoch-200000。

Is the threshold 0.4 a fixed value? For every type of generation。Looking forward to your reply!


text:
Update styles of the Gatsby blog to match webflow blog

Goal
We want the Gatsby blog to have styling consistent with the webflow blog.
List of all inconsistencies

Proper margin, padding, font size, font weight and font style

Headings
Paragraphs
Images
Lists and list items
Footnote text

Footnote superscript link styling
Indentation for list items
border-bottom for headings

Pushed to prod

authors: rishabhpoddar st-jay

repo: supertokens/blog


text:
⚠ Nano has degraded performance

In d81f774, Nano (https://nano.shuttleapp.rs/up) experienced degraded performance:

HTTP code: 0
Response time: 0 ms

Resolved: Nano performance has improved in e7ac738 after 16 minutes.


text:
Rust crate does not work with MSVC

The Rust crate blst does not compile when using MSVC as the compiler.

I'm not a C developer, but I did a little digging to figure out the root cause, and it appears that __STDC_VERSION__ was not defined. Following suggestions in the similar issue #103, I tried adding CFLAGS=/std:c11, but I got the same error.
I tried preprocessing a C file with these variables using C11 and it output the other condition that can cause the no_asm file to error, which is __STDC_NO_VLA__ being set to 1.
Apparently MSVC does not support Variable Length Arrays, which appears to be an optional extension. I did some research and it seems that they are generally not recommended for a variety of reasons, e.g. security, performance, and portability.
I'm using Windows 11 with Visual Studio 2022.

The Rust crate blst does not compile when using MSVC as the compiler.

This is a bit misleading, as the problem is not as general. It doesn't work specifically with 32-bit MSVC as the compiler.
If you have to build for 32-bit Windows (why?), add clang in the Visual Studio installer and execute cargo at x86 Tools Command Prompt. For reference, the prompt gives you 32-bit clang-cl on your %PATH%. This, 32-bit clang-cl on %PATH%, can be achieved by any other means.

I'm just trying to cargo run some code using BLS locally, not build an executable for 32 bit Windows. I'm on a 64 bit machine (Ryzen 5600X).
I'm using PowerShell inside of VSCode, which is a pretty typical development environment. Not sure why the shell I'm using plays any role in whether or not blst will compile?

Weird, I'm on a 64-bit version of the OS on 64-bit hardware, so I'm really not sure why it decided to default to i686. Setting the target did indeed work.
Thanks for the help.

authors: Rigidity dot-asm

repo: supranational/blst


text:
[BUG] Fatal Error: Unable to get window info from SDL

Describe the bug
When trying to launch TF2 via TF2BD, I get an error complaining about being unable to get window info from SDL
Logs
2024-06-07_18-02-19.log
Screenshots

Desktop (please complete the following information):
Linux Mint 21.3 Virginia
TF2BD v1.6.3.55
Additional context
This did not occur before updating packages
This does not occur when running TF2 directly through steam

"This did not occur before updating packages" interesting, my guess might be that we're loading the OS's version of sdl instead of the supplied sdl binary of tf2, and that's being incompatible with tf2.
For now just work around it by supplying your own rcon params and launching tf2 separately via steam (see #26's launch params), sorry about that.

I believe the issue is that the game is supposed to use the Steam Linux Runtime libraries but is instead using system libraries

yea probably

I changed how tf2 launches under linux and its my best guess on the proper way to fix this issue, can you try the latest build artifacts?
Two of the distros i use don't have this problem so it's kind of a shot in the dark lol

It works although the terminal command length limit is hit a lot quicker when using command line parameters

Nevermind it triggered insecure mode


text:
feat: Fix animations

Changes
Fixed

Sticking when closing at the end

Changed

Split the animation speed into opening and closing speeds. The closing speed has been reduced.
FlexibleBottomSheetRoute has been made public

https://github.com/surfstudio/flutter-bottom-sheet/assets/39735343/638a4643-3652-4ee1-9bd6-388e170b7212
https://github.com/surfstudio/flutter-bottom-sheet/assets/39735343/c624d307-c957-44ff-9142-e8d8b251288b
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
[x] Specified related tasks and/or related PRs.
[x] Specified Changes.
[x] Attached videos/screenshots demonstrating the fix/feature.
[x] All unspecified fields in the PR description deleted.
[x] 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).

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

Comparison is base (b126c39) 100.00% compared to head (2959672) 100.00%.

:exclamation: Current head 2959672 differs from pull request most recent head 5037257. Consider uploading reports for the commit 5037257 to get more accurate results

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #95   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            4         4
  Lines          273       273
=========================================
  Hits           273       273

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

authors: codecov-commenter internetova

repo: surfstudio/flutter-bottom-sheet


text:
feat(SNP-1246): App Links Implementation

Changes:

add deeplink feature
implement app_links
add simple deeplink handling

Demo:
https://github.com/surfstudio/surf-flutter-app-template/assets/125694327/20fc3b2d-170c-4f9e-9070-0fdc65815376

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

Project coverage is 26.39%. Comparing base (339c48c) to head (91d6974).
Report is 17 commits behind head on main.

:exclamation: Current head 91d6974 differs from pull request most recent head be40baf. Consider uploading reports for the commit be40baf to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #118   +/-   ##
=======================================
  Coverage   26.39%   26.39%
=======================================
  Files          55       55
  Lines         917      917
=======================================
  Hits          242      242
  Misses        675      675

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

authors: codecov-commenter danyaao

repo: surfstudio/surf-flutter-app-template


text:
Added homepage, doc cleanup, blog start

Added the requested homepage, did some cleanup on the doc sidebar so that aren't fully expanded on load. (Cleaner look). Started the work on setting up blogging.

It looks great!
A couple of comments:

I don't think we need to explicitly talk about Docusaurus in the front page 😅 There is already a mention in the footer.
I would say to try to be less cheerful. Don't get me wrong on this, I like the mood, but I'll remove some sentences such as the "Hello from ..." or the "We suggest you to please put on your hard hat," 😅
Not sure if we want to enable blog or just keep this as documentation.
Also not sure if we want a front page at all or improve the main doc index page. With this PR it will take an extra click just to go to the main docs, and then another click to read whatever you want to read.

Adding @rdoxenham to the thread :)

Thanks for this @jimmyrmartin - so, front page, absolutely this is what we should have. The purpose here should be a landing page where it takes us to the documentation, the blog, video's, and various other sections. Hence why I didn't want the original landing page to simply be the docs page.

I added these per @rdoxenham's asks in the OG Trello/Jira.
@e-minguez I'm always open to suggestions and viewpoints. The landing page Docusaurus mention is a place holder to make the page not look so dearth of content. It will definitely be replaced with links to the blog, videos, presentations, and so on.

👍🏻

I'm trying to add a little personality in our language outside of the technical documentation itself. Documentation that is useful but also friendly (like our Geeko) and playful in small amounts lead to people being more engaged. We may be 'engineers' but we are still people. There is a lot of research in cognitive psychology and documentation on the effect. The documentation part of it, of course can be all buttoned up and fully professional.
https://www.oreilly.com/content/the-eight-rules-of-good-documentation/
Again, I'm open to varying opinions, so hopefully this small novel of a "code commit comment" is helpful to explain my thinking.

It is, thanks. From my point of view (this is just me, we can disagree of course!) I prefer to keep the landing page and technical documentation just technical. Bear in mind that there are a lot of non US readers and some of the expressions outside of the technical field can be unknown (I personally need to look for "stalwart" 😄 ). On the other hand we can vary the tone in blog posts of course!

Also, I won't lie, I still don't fully agree with the uncollapsed sidebar. For someone that deals with a lot of neurodiversity from many angles in my life, it's a bit more to take in and "distracting". Though, I do also see your view on it.

Honestly it is fine if you want to collapse all sections, but based on the fact that we don't have too much content, it serves as a ToC... (see for example https://rancher.github.io/elemental-toolkit/docs/) however when we have enough content I'll encourage to collapse them.

I'm happy to be working on this with you.

Likewise! 🤗

TBH: 'Stalwart' might have been a 'ten dollar word' (See side note) pulled out of my mental thesaurus. It seemed to fit at the time of writing. We can iterate, of course.
I do understand the uncollapsed sidebar. I'm not insisting on my way. I see your reasoning over TOC. Just mentioned it due to some personal and professional experience many don't see that side of. For instance, my daughter basically needs a "reading mode" type of experience to be able to focus on the content when being confronted with digital media due to the amount navigational elements vs informational.
Shall we have an Edge Engineering chat about the general content management?
Side note:
'ten dollar word' is likely another American English expression that maybe Rhys or Gary doesn't get, though they are native "English" speakers. I believe it's primarily used these days in the Southern United States.
https://www.grammarphobia.com/blog/2012/10/ten-dollar-words.html#:~:text=The phrase “ten-dollar word%2C” for example%2C,to important or pretentious words

Sorry, I forgot about this yesterday 😓 Merged!

authors: e-minguez jimmyrmartin rdoxenham


text:
Line wrapping

Is it possible to add line wrapping for long legend titles?

There are other plugins that provides features like these.
Checkout the awesome d3-jetpack

Oh cool, thanks!
On Sat, Sep 19, 2015 at 11:27 PM, Ming Liu notifications@github.com wrote:

There are other plugins that provides features like these.
Checkout the awesome d3-jetpack
https://github.com/gka/d3-jetpack#d3wordwrap
—
Reply to this email directly or view it on GitHub
https://github.com/susielu/d3-legend/issues/8#issuecomment-141752736.

Is there any update on this @susielu ? I have just started using d3-legends and loving it so far. Thanks for building this. I need to move my legends to new line if there isn't any space, like this and it would be great if the library provided this feature.

@axelson I've added the functionality to allow for text wrapping for the title, example here: http://d3-legend.susielu.com/#color-quant
@aendrew I'll think about adding in functionality for multi-line legends. Will probably start with enabling text-wrapping for labels first.
Thanks!
Susie

authors: akshayKhot axelson ming-codes susielu


text:
raw.githubusercontent.com の rate limit

https://github.community/t/raw-githubusercontent-com-rate-limit/142444

60 回 /per らしい
しかし回答している人は GitHub の中の人じゃないし、アカウント停止されている。
制限ないって言ってる人もいるが、多分あるんじゃないかな？
https://stackoverflow.com/a/66522313
自分で問い合わせるのが早くて確実か

https://docs.github.com/ja/rest/reference/rate-limit

https://support.github.com/request

https://docs.github.com/en/rest/overview/resources-in-the-rest-api#rate-limiting

For unauthenticated requests, the rate limit allows for up to 60 requests per hour.
Unauthenticated requests are associated with the originating IP address, and not the user making requests.

repo: suzuki-shunsuke/issue


text:
class in svelte applied two times

Describe the bug
prod:

dev:

Reproduction
https://github.com/mieaw/class-in-svelte-applied-two-times
Logs
No response
System Info
System:
    OS: Windows 10 10.0.22621
    CPU: (8) x64 Intel(R) Core(TM) i7-CPU @ 1.80GHz
    Memory: 17.88 GB / 31.89 GB
  Binaries:
    Node: 18.16.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 9.5.1 - C:\Program Files\nodejs\npm.CMD
    pnpm: 8.6.7 - C:\Windows\system32\pnpm.CMD
  Browsers:
    Edge: Spartan (44.22621.1702.0), Chromium (113.0.1774.57)
    Internet Explorer: 11.0.22621.1
  npmPackages:
    @sveltejs/adapter-auto: ^2.0.0 => 2.1.0
    @sveltejs/kit: ^1.20.4 => 1.22.3
    svelte: ^4.0.5 => 4.0.5
    vite: ^4.4.2 => 4.4.4

Severity
blocking an upgrade
Additional Information
i can work with this issue :/

Seems to be duplicate of #10379

Closed as duplicate 🙂

authors: Renkas mieaw tcc-sejohnson

repo: sveltejs/kit


text:
Run code on the client regardless of whether layout is reset

Describe the problem
@anudeepreddy already opened a pull request https://github.com/sveltejs/kit/pull/2160 to solve the problems mentioned in #2154 and #1356, and not sure if it'll really solve the other problem mentioned in #2130.
But According to @Rich-Harris comments from #1356, by importing src/routes/__layout.svelte with other _layout.reset.svelte files, we avoid the extra dynamic import for the error page that may fail if imported at demand.
I really like the idea of having an app level layout file, as it open other possibilities including app level imports and gaining access to $app/stores without having to duplicate code in every __layout.reset.svelte.
Unfortunately, the current approach isn't playing well with code splitting, and I'm starting to worry about bloating other minimal pages with unnecessary components and other modules (e.g: login page).
Describe the proposed solution
I recommend that src/routes/__layout.svelte will get splitted into two other files:

The first one would be the app layout, and always imported. It should cover error pages, and other app level imports, and from there, the programmer could gain access to $app/stores and other objects.
The second one is optional and specific to the root path.

In case if anyone objected about the additional nesting level of layout:

the second file could be optional and not mandatory
we still could have a root level layout attached to body
I'm not sure if <svelte:fragment> will play an important role with this, but I'll try to think about it later.

Alternatives considered
I'm listing some possibilities for naming conventions. These are not decisive, and others may come up with better alternatives:

__layout.svelte and __layout.main.svelte
__root.svelte and __layout.svelte

Importance
nice to have
Additional Information
No response

This sounds very similar to https://github.com/sveltejs/kit/issues/1165

This is EXTREMELY IMPORTANT.

Let's say I'm using @urql/svelte and its initClient().
If I use that method both in

src/routes/__layout.svelte and in
src/routes/login/__layout.reset.svelte

it initializes my urql client two times!
Is there a workaround today?
I'm using it like this because in src/routes/__layout.svelte I redirect the user to /login if is not authenticated.

I was facing this double initialization issue in CSS, where my __layout.svelte css was messing up with __layout.reset.svelte in #1356.
I have a workaround to use css by a
<link> tag inside <svelte:head>
But still, it is not technically perfect. I am still facing issues in creating apps with different styling in sub routes.

There does currently seem to be a conflation between different uses of __layout.svelte in the root path location. Here's the ones I can see mentioned here:

Layout which should apply to all paths under the root path (which is essentially all paths, because that's how paths work).
Layout which should apply to ONLY the root path. Currently only possible by putting a layout.reset.svelte on all other paths, which is obviously messy.
Layout which should be applied regardless of other resets later in the path.
"Layout" which just executes setup scripts for the client side.

Option 4 should not be a layout at all, as it's not "laying anything out" on the client side. There are already proposals for this, namely #1538 and #1530. These will run any client side initialization code you specify without having to include it in an otherwise useless layout file.
The other three are more debatable. Currently, options 1 and 2 are the same and option 3 does not exist. My idea would be to make option 1 into __layout.svelte, option 2 into __layout.root.svelte, and option 3 into __layout.global.svelte. This would greatly increase the flexibility of layout files and remove the need for a lot of strange workarounds.

One possible workaround could be the technique I mention in this proposed FAQ entry:
import { initClient } from 'some-library';

const noop = () => {};
let storedClient = null;
export const client = readable(null, (set) => {
  if (!storedClient) {
    storedClient = initClient('whatever params you need');
  }
  set(storedClient);
  return noop;
});

Then in the rest of your code, just import the client store and use it as $client.get('some-query'). You're guaranteed that the initClient function will be called exactly once (or zero times if it's never actually needed). Note that if the user refreshes the page, then initClient will be called again, but that's almost always what you'd want.

@rmunn, and how is store better than a simple variable?
//db.js
import { initClient } from 'some-library';

let db;
export function GetDB() {
    if (!db) {
        db = new initClient("...");
    }
    return db;
}

//api endpoint or else
import { GetDB } from "$lib/db";

export async function get(req) {
    const client = GetDB();

    let result = await client.func();
};

This is now be possible with (rather advanced, don't freak out) usage of named layouts:
/src/routes/
  /__layout-app.svelte             # your app-wide layout
  /__layout@app.svelte             # your default layout, goes inside app-wide layout `/__layout-app.svelte`
  /__layout-reset@app.svelte       # an empty <slot/> layout, goes inside app-wide layout `/__layout-app.svelte`
  /some/regular/page.svelte        # goes inside layout `/__layout@app.svelte`
  /some/random/page@reset.svelte   # goes inside reset layout `/__layout-reset@app.svelte`

You can have app, root, path and reset-specific code in named layouts that you can structure freely.

authors: AlexRMU DhyeyMoliya benmccann frederikhors jchanes04 jsprog mrkishi rmunn


text:
Non repeatability of build

Describe the bug
Apologies for this being rather vague, but I thought I'd post it in case someone else notices the same behavior and can add anything to it.
The build output (only noticed with the Node adapter) doesn't appear to be consistent / repeatable. It seems like things from previous dev / build runs are leftover and then appear in the build output.
The symptom that I noticed is using vite-imagetools to import images and output <picture> elements with srcset size variations. dev works fine but at some point doing a prod build starts repeating references to images that don't exist. So for a 1024w image, there would be 2 entries, but only one image ref would actually exist in the build output.
For example, the build should output:
<picture class="md:shrink-0 h-56 w-full object-cover">
	<source
		srcset="
			/_app/immutable/assets/screenshot-9c104e5b.avif  480w,
			/_app/immutable/assets/screenshot-559be74f.avif  768w,
			/_app/immutable/assets/screenshot-b0784bda.avif 1024w,
			/_app/immutable/assets/screenshot-9fcf0c9d.avif 1280w
		"
		sizes="100vw"
		type="image/avif" />
	<source
		srcset="
			/_app/immutable/assets/screenshot-00c46908.webp  480w,
			/_app/immutable/assets/screenshot-54686df4.webp  768w,
			/_app/immutable/assets/screenshot-58f959ca.webp 1024w,
			/_app/immutable/assets/screenshot-658e2b07.webp 1280w
		"
		sizes="100vw"
		type="image/webp" />
	<source
		srcset="
			/_app/immutable/assets/screenshot-3ffa6799.jpg  480w,
			/_app/immutable/assets/screenshot-03229d52.jpg  768w,
			/_app/immutable/assets/screenshot-a416e08c.jpg 1024w,
			/_app/immutable/assets/screenshot-0ac9a3ed.jpg 1280w
		"
		sizes="100vw"
		type="image/jpeg" />
	</picture>

<picture class="md:shrink-0 h-56 w-full object-cover">
	<source
		srcset="
			/_app/immutable/assets/screenshot-9c104e5b.avif  480w,
			/_app/immutable/assets/screenshot-bd1088e1.avif  480w,
			/_app/immutable/assets/screenshot-559be74f.avif  768w,
			/_app/immutable/assets/screenshot-144f1307.avif  768w,
			/_app/immutable/assets/screenshot-b0784bda.avif 1024w,
			/_app/immutable/assets/screenshot-74e803fe.avif 1024w,
			/_app/immutable/assets/screenshot-9fcf0c9d.avif 1280w,
			/_app/immutable/assets/screenshot-f1b721c2.avif 1280w
		"
		sizes="100vw"
		type="image/avif" />
	<source
		srcset="
			/_app/immutable/assets/screenshot-00c46908.webp  480w,
			/_app/immutable/assets/screenshot-e1e5cb3b.webp  480w,
			/_app/immutable/assets/screenshot-54686df4.webp  768w,
			/_app/immutable/assets/screenshot-654a313c.webp  768w,
			/_app/immutable/assets/screenshot-58f959ca.webp 1024w,
			/_app/immutable/assets/screenshot-a41453fb.webp 1024w,
			/_app/immutable/assets/screenshot-658e2b07.webp 1280w,
			/_app/immutable/assets/screenshot-1c9830c6.webp 1280w
		"
		sizes="100vw"
		type="image/webp" />
	<source
		srcset="
			/_app/immutable/assets/screenshot-3ffa6799.jpg  480w,
			/_app/immutable/assets/screenshot-5106e4a9.jpg  480w,
			/_app/immutable/assets/screenshot-03229d52.jpg  768w,
			/_app/immutable/assets/screenshot-697d964e.jpg  768w,
			/_app/immutable/assets/screenshot-a416e08c.jpg 1024w,
			/_app/immutable/assets/screenshot-1438080e.jpg 1024w,
			/_app/immutable/assets/screenshot-0ac9a3ed.jpg 1280w,
			/_app/immutable/assets/screenshot-68909a9c.jpg 1280w
		"
		sizes="100vw"
		type="image/jpeg" />
	</picture>

Deleting the .svelte-kit folder before the build fixes it.
Reproduction
TODO
Logs
No response
System Info
System:
    OS: macOS 11.7
    CPU: (8) x64 Intel(R) Core(TM) i7-4850HQ CPU @ 2.30GHz
    Memory: 550.15 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 18.10.0 - ~/Library/pnpm/node
    npm: 8.19.2 - ~/Library/pnpm/npm
  Browsers:
    Brave Browser: 102.1.39.122
    Chrome: 106.0.5249.119
    Edge: 106.0.1370.52
    Firefox: 101.0
    Safari: 16.0
  npmPackages:
    @sveltejs/adapter-node: next => 1.0.0-next.99
    @sveltejs/kit: next => 1.0.0-next.524
    svelte: ^3.52.0 => 3.52.0
    vite: ^3.1.8 => 3.1.8

Severity
serious, but I can work around it
Additional Information
I checked if anyone had reported duplicate refs in the vite-imagetools repo, but didn't find anything. That, and the .svelte-kit folder deletion fixing it makes me believe it's todo with SvelteKit Build (possibly specific to the Node adapter).

This seems to have fixed itself


text:
feat(adpater-node): support all esbuild build options

This PR allows changing the options passed to esbuild build which allows to customize the server generation like target node version, sourcemap, inject, and more.
It contains one braking change: out is renamed to outdir to follow the esbuild API. It is possible to avoid a breaking change by making out an alias for outdir. I'm happy to adjust the PR.
Before submitting the PR, please make sure you do the following

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

Tests

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

Changesets

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

I think it would be clearer if these options were nested under single esbuildOptions param field instead of spread amongst the base param obj.

I think it would be more clear if these options were nested under a single esbuildOptions param field instead of spread amongst the base param obj.

I have adjusted the PR to use a esbuildOptions parameter. I changed the default options to use outdir instead of outfile to support code splitting. This still creates a single build/index.js file because the entrypoints filename is index.js. If the outfile option is set outdir will not be used because esbuild expects either outfile or outdir.

Commit message has a typo.

Commit message has a typo.

Sorry, I do not know what you mean.

https://github.com/sveltejs/kit/pull/1692/commits/c6075d7f54a464ff8be743fbce0effb0d38cc432
I assume the title is supposed to be "adapter" and not "adpater"

Same thing in the commit message. (Don't know if you will fix it later or overlooked it)

c6075d7
I assume the title is supposed to be "adapter" and not "adpater"

Same thing in the commit message. (Don't know if you will fix it later or overlooked it)

I can not fix that now. But I believe that PRs are squashed and use the PR title (which is fixed) as commit message.

Just thought I would raise before we adopt esbuild more significantly, but the initial usage of esbuild was a suggested soln

Mostly just playing around for now, but this is intended to solve the perennial problem of dependencies behaving weirdly, by allowing adapters to determine what gets bundled.
-Rich Harris in #1091

Has there been more thought on alternative solutions or is esbuild usage likely to stick around? @Conduitry @benmccann

@jthegedus it's not an area I understand well, so I will defer to Rich and Conduitry

It looks like this PR needs to be rebased

It looks like this PR needs to be rebased

Done.

There's a related PR for adapter-vercel here: #1732

I do not know if using config.kit.vite().esbuild is the best way here. In my specific use-case I want to use a different esbuild config (mainly target and format).
Maybe a hybrid approach:
{
	...config?.kit?.vite()?.esbuild,
	...esbuildOptions,
}

But that would make reasoning about the resulting config difficult.
What is your take on this?

Is there anything I can do to progress this PR?

Since the common js output format is also available in this PR. I'm wondering if we can check if  __dirname and require already exist before shim it, so the configuring is easier. I tried building it to cjs before and it's throwing an error in the runtime because import.meta.url is undefined.
But regarding how to check if __dirname exists, I can only think of some hack like this:
var __dirname;
__dirname = __dirname ?? dirname(fileURLToPath(import.meta.url))

Since the common js output format is also available in this PR. I'm wondering if we can check if  __dirname and require already exist before shim it, so the configuring is easier. I tried building it to cjs before and it's throwing an error in the runtime because import.meta.url is undefined.
But regarding how to check if __dirname exists, I can only think of some hack like this:
var __dirname;
__dirname = __dirname ?? dirname(fileURLToPath(import.meta.url))

(Sorry I spamed the notification. accidently deleted the previous comment)

Since the common js output format is also available in this PR. I'm wondering if we can check if __dirname and require already exist before shim it, so the configuring is easier. I tried building it to cjs before and it's throwing an error in the runtime because import.meta.url is undefined.
But regarding how to check if __dirname exists, I can only think of some hack like this:
var __dirname;
__dirname = __dirname ?? dirname(fileURLToPath(import.meta.url))

(Sorry I spamed the notification. accidently deleted the previous comment)

I use define + inject:
shim-node-cjs.js
import { pathToFileURL } from 'url'

export const shim_import_meta_url = /*#__PURE__*/ pathToFileURL(__filename)

And the in the esbuild config:
    // Or something like path.relative(import.meta.url, './shim-node-cjs.js')
    inject: [require.resolve('./shim-node-cjs.js')],
    define: {
      'import.meta.url': 'shim_import_meta_url',
    },

This works quite well for single file outputs.

I'm also fine with an example in the doc. I just thought making it work out of the box would be a little bit easier for the user.

Why are you wanting to change target and format?

Why are you wanting to change target and format?

We are bundling the server and the assets using pkg into an executable. pkg needs cjs as format and we can use a higher target (v16).

And we're hosting with Windows IIS with iisnode, which doesn't seem to support ESM.
People using other hosting platforms that don't already have an official adapter may want to leverage the node adapter. And since some other adapters also ship common js. I think it would a good idea to allow configuring node adapter to output common js.

@sastan it looks like this PR will need to be rebased

I do not know if using config.kit.vite().esbuild is the best way here

I agree. It's better to keep them separately configurable


text:
Text in homepage link

This is just #9607 with an additional commit that corresponds to https://github.com/sveltejs/site-kit/pull/88 — I can't work out how to open a PR against that branch 😅

This is fixed in site-kit's text PR and #9607

authors: PuruVJ Rich-Harris


text:
[Feature Request] alternative to changesets for better release flow

Usage example, including component, action, motion, or utility API
We need to implement an alternative to changesets because there is no config option to publish sub directories.
Possible implementation - describe how the feature can be implemented
As of right now, I have not thought of a possible implementation.
Do you want to contribute this feature and create a pull request
Yes

Changesets was replaced with a home grown solution

repo: svelteuidev/svelteui


text:
Localization of Digits

Some languages use other digits than Western Arabic (that is: 01234...). Some examples are Eastern Arabic (٠١٢٣٤٥٦٧٨٩: U+06F0..U+06F9) and Perso-Arabic (۰۱۲۳۴۵۶۷۸۹: U+0660..U+0669).
Is it within the scope of this gem to provide tools to localize digits of numbers? Can I provide pull request to extend localize or any new function to provide this facility?

This is a duplicate of #135. Let's keep the discussion there.

authors: arashbm radar


text:
Infer orientation from input data

currently read pair orientation must be specified from the command line

9ed9cdc67a316df613ff2913533de1b50a7a156d

repo: svviz/svviz


text:
@ApiOperation does not support multiple "consumes"/"produces"

If a method is annotated with on of the following:
@Consumes({ MediaType.APPLICATION_XML, MediaType.APPLICATION_JSON })
...
@Produces({ MediaType.APPLICATION_XML, MediaType.APPLICATION_JSON })

Then there is no way to actually translate this into swagger annotations, as the following is not supported:
@ApiOperation(consumes = {MediaType.APPLICATION_XML, MediaType.APPLICATION_JSON},
              ... or ...
              produces = {MediaType.APPLICATION_XML, MediaType.APPLICATION_JSON})

Is there a known way around this?

It takes a comma-separated string, not an array of strings. If you already annotate the method with @Consumes and @Produces you shouldn't need to declare it in the @ApiOperation as well.

@webron,
Thanks for clearing this out! I hadn't noticed! Much appreciated! :)

authors: carlspring webron

repo: swagger-api/swagger-core


text:
@Api(hidden = true) failed

@Api(hidden = true) decorate controller unsuccessful
<dependency> 			<groupId>io.springfox</groupId> 			<artifactId>springfox-swagger2</artifactId> 			<version>2.7.0</version> 		</dependency> 		<dependency> 			<groupId>io.springfox</groupId> 			<artifactId>springfox-swagger-ui</artifactId> 			<version>2.7.0</version> 		</dependency>

That's Springfox, not Swagger Core. Please file an issue with them.


text:
Request some examples of local $ref

What should I pass in swaggerModels, is that an array
It just doesn't work for some reason

The swaggerModels parameter should be populated with the models stored in your swagger definition.  It is an array of the definitions.
This is the part of the swagger definition in allModels or definitions or components.schemas (depending on swagger version).

authors: ZehuaZhang brodyd


text:
Fill feed URL field from params

Read the feed URL from params on request to /feeds/new and let it fill the feed URL field. This enables integration with the RSS Subscription Extension extension for Google Chrome and should allow integration with similar extensions, for Google Chrome or other browsers.

What do you think about a different endpoint? Just so it's clear how this could be used /feeds/oneclick or something?

Looks like a neat extension - does it open the page in Stringer and we have to click 'Add'? Or is the intent that we can subscribe directly from the GET?

When using the extension to subscribe to a feed, it opens the feed reader in a new tab. Feeds and corresponding URLs are configurable, but only GET-requests appear to be supported.
My first thought was to add a new endpoint to add the feed directly, without user interaction. Then I changed my mind and implemented it this way because it's the minimal functional patch and let's us avoid using GET requests to modify application state.

:+1: works for me

authors: Koronen swanson

repo: swanson/stringer


text:
Pages: remove Currency.tsx

думаю можно удалить эту страницу, так как она не используется либо доработать
@noxonsu что думаешь?

я хз что это , скрин?

https://github.com/swaponline/MultiCurrencyWallet/blob/867e76e1be0098174c2a6a64f1c328b5c7ce83dc/src/front/shared/routes/index.tsx#L97
в роутах только используется, но зайти на эту страницу у меня не получилось никак

удалить конечно

authors: VitaliyShulik noxonsu

repo: swaponline/MultiCurrencyWallet


text:
ресерч возможности закрыть вкладку и чтоб своп работал

Problem
после создания оредра юзеру нужно держать вкладку открытую, что очень неудобно
Task
нужно провести ресерч
-можно ли свап.онлайну работать через сервис воркеры
-можно ли попросить юзера установить специальное расширение которое будет держать своп в фоне
-любые другие идеи, например паковать в электрон
Purpose
Area
весь сайт
Estimate time of implementation
низвестно, требуется комментарий спеца
Additional data

я проверил, на андроде если свернуть хром, то приложение работает, и даже свапы выполняет, тоесть фоновые вкладки работают отлично, осталось только сделать их неубиваемыми (через минут 15 уже отключается процесс похоже)

как вариант выносить в service worker

Не. это не вариант.  Я хочу начать своп, закрыть ноут и поехать на велосипеде.
Я готов заплатить чтобы кто-то за меня это сделал. Вот и все.
При этом так как лицензия не подразумевает хранения крипты за пользователя или их приватников, это должно быть trustless.
Брать просто деньги за транзу ибо нам они нужны чтобы довести свопы до конца

приватники нужны во время свапа, либо передавать приватники маркетмейкеру либо никак


text:
убрать левые теги c иконами из header

 убрать тем более в асетах нет картинок этих

authors: nikdementev noxonsu


text:
Новый вид транзакций

Pull request template
Checklist

[x] I have read the CONTRIBUTING guide
[x] branch rebased on develop
[x] styleguide check npm run validate
[x] good naming
[x] keep simple
[ ] video or screenshot attached
[ ] testing instruction attached
[x] check your PR once again

Description

Video or screenshot

What and how to test

Что за новый вид транзакций , где? Что поверять?

authors: noxonsu nthgness


text:
[WIP] Add support for libinput_switch input devices

These are used primarily by laptops to signal
the state of the lid (open/closed) and tablet
mode if supported, based on ACPI events.
AFAICT this should be feature-complete for wlroots itself, I've added what looks correct for rootston but am unsure if this is all I need.
Seems to be working well within sway, but I assume sway will also need some formal support for these new events.
2018-11-15 00:13:53 - [backend/libinput/events.c:94] Added Lid Switch [0:5]
2018-11-15 00:13:53 - [backend/libinput/events.c:173] Switch capability match for device Lid Switch
2018-11-15 00:13:53 - [backend/libinput/switch.c:20] Created switch for device Lid Switch
2018-11-15 00:13:53 - [backend/libinput/events.c:173] Switch capability match for device ThinkPad Extra Buttons
2018-11-15 00:13:53 - [backend/libinput/switch.c:20] Created switch for device ThinkPad Extra Buttons
2018-11-15 00:14:37 - [backend/libinput/switch.c:41] Got switch event type 2 state 1 from ThinkPad Extra Buttons
2018-11-15 00:14:58 - [backend/libinput/switch.c:41] Got switch event type 2 state 0 from ThinkPad Extra Buttons
2018-11-15 00:15:12 - [backend/libinput/switch.c:41] Got switch event type 1 state 1 from Lid Switch
2018-11-15 00:15:16 - [backend/libinput/switch.c:41] Got switch event type 1 state 0 from Lid Switch

Just an RFC currently, this is my first delve into the guts of wlroots.

Updated with correct wlr_event.state and wlr_event.type enums to fix BSD build and removed debug logs.

This looks good for the wlroots side. Now we need to decide how to expose this in rootston config (and later in sway).

Thanks. I'd assume they probably just need to be exposed as hooks, I can't imagine there will be a set of actions which are universally appropriate, rather will depend on user hardware and preference.

What about something like this
[device:Just A Switch]
switch_toggle = exec echo toggle
switch_toggle:on = exec echo on

On further thought, I wonder if it's better to just listen to the switch types, regardless of the device that generates them?
There are only two, LIBINPUT_SWITCH_LID and LIBINPUT_SWITCH_TABLET_MODE, and I doubt any device would have more than one of each, so perhaps it's better to ignore the device name (which will likely vary from laptop to laptop) then just react to the events by specifying a binding command, so:
[switches]
lid:open = exec echo open
lid:close = exec echo close
lid:toggle = exec echo toggle
tablet_mode:true = exec echo tablet
tablet_mode:false = exec echo laptop
tablet_mode;toggle = exec echo toggle

Yeah, maybe that's better. Maybe we could match the part on the left of the colon with either the device name or the type.

16:51 <tokyovigilante> Does rootston process general libinput events? I'm trying to add tablet and laptop switch support but the devices never seem to be initialised in rootston
16:59 <damjan> tokyovigilante: isn't that done in wlroots?
17:00 <tokyovigilante> yeah I've done added support for it in wlroots, but rootston doesn't seem to see those devices to listen to events from
17:01 <tokyovigilante> It only seems to see the keyboard and pointer. I'm testing rootston from inside a sway session, maybe that's the problem

libinput is not used if you run a nested compositor (e.g. if you run rootston inside of sway).

Oh right, makes sense. I did try to run from a TTY but get a crash with exit on startup without obvious debug message. Will try and solve.

This latest set adds some support for Rootston, and logs a debug message when the switches are triggered. I'm not sure whether to add another class for the switch command handling itself, as this would duplicate a lot of the code in keyboard.c, or to factor this code out to a separate shared class.

I'm not sure whether to add another class for the switch command handling itself, as this would duplicate a lot of the code in keyboard.c, or to factor this code out to a separate shared class.

You mean another file?
Probably better to split the command handling stuff in a separate file.

Oh yeah sorry another file. OK I'll refactor it.

OK, I think this is ready for a review, all working on my system with the config:
[switch:lid]
on = exec echo "Lid opened"
off = exec echo "Lid closed"
toggle = exec echo "Lid moved"

[switch:tablet]
on = exec echo "Entered tablet mode"
off = exec echo "Entered laptop mode"
toggle = exec echo "Toggled tablet mode"

[switch:ThinkPad Extra Buttons]
on = exec echo "Matched named device switch on"
off = exec echo "Matched named device switch off"

Only wrinkle is that the lid switch events don't seem to be received by rootston. I wonder if they are intercepted by ACPI as systemd is set to suspend automatically when the lid is shut.

Whoops, rebased.

Please remove "WIP" from the PR title once it's ready for review!

Oh sorry! Have been working on Support (which is definitely still WIP) but think this PR is in reasonable shape.

Thanks, will make the style changes ASAP. Is there a style guide about?
On Mon, Dec 10, 2018, at 3:16 AM, Drew DeVault wrote:

@ddevault requested changes on this pull request.

Overall this looks pretty good, nice work

— You are receiving this because you authored the thread. Reply to
this email directly, view it on GitHub[1], or mute the thread[2].

Links:

https://github.com/swaywm/wlroots/pull/1377#pullrequestreview-182984582
https://github.com/notifications/unsubscribe-auth/AAAyq9Jx4awy6rZjEfLyXS0VBvk4P4djks5u3TdTgaJpZM4Ye2Qy

Yes, see CONTRIBUTING.md.

Style nits attended to, and I've improved the config matching logic somewhat.

Thanks!

No, thank you!

authors: emersion tokyovigilante

repo: swaywm/wlroots


text:
Fix heap-use-after-free in wlr_send_tablet_v2_tablet_pad_leave

See swaywm/sway#4660
This change does fix the crash, but I am not sure if this is the proper way to do it, so I want someone with knowledge about wlroots memory management to review this.
cc @emersion @Ongy

Will need to rebase those commits together before the final merge

Will need to rebase those commits together before the final merge

Do I also need to squash them together, or will that be done automatically? (Sorry, this is my first time sending a PR on github.)

Squash, yes please.
https://git-rebase.io

authors: ddevault kuruczgy


text:
SWC can't strip useless parentheses during minification

Describe the bug
SWC can't strip useless parentheses during minification.
Input code
let f = window.__anything;
const str = (f ? "bEvNbr " : "") + ((f ? "WhAZY " : "") + ((f ? "kLKrsq " : "") + ((f ? "bLIxaN " : "") + ((f ? "bOjOhu " : "") + ((f ? "lksDzB " : "") + ((f ? "edsxqC " : "") + "fygwnR kQBRAp fwqTyU sJymt jdraHW hcJKTR eqrBPF kVZHcH dwawJR iATxZH jQenOz glXlAQ ejfOAg imuUWK jePIQM eCuFxb ieWmMp YseoS "))))));

console.log(str);

Config
{
  "jsc": {
    "parser": {
      "syntax": "ecmascript"
    },
    "target": "es2022",
    "loose": true,
    "minify": {
      "compress": {},
      "mangle": {}
    }
  },
  "module": {
    "type": "es6"
  },
  "minify": true,
  "isModule": true,
  "sourceMaps": true
}

Playground link
https://play.swc.rs/?version=1.2.189&code=H4sIAAAAAAAAA4WSy26CQBSG9zzFH1aaJj5ATdOArUFQEaqlujFchvtFGCjg05fKglpBz2Zmzvzfl7M4Iclh4wWlF1tJOTke9bjOXS92poyZxDQHzbPme2TjFazx%2Fr02MrB4BsuOGTT1hNHl%2FK02pLncYX%2BV%2BZ%2FrssFSymh6E%2B4DOshYLip93QsNgX9g2ZfdYhC%2BJ%2BgkYUDfzvxdySNRJyMWrdLZQ1krZO3aKWMVgcKr3Al2mW7rHahYRzl8K9MFDa4pSlsVJM34zRzB50EwBVilXooqPG5bHQT4ConlM5zwK%2BQUEN%2BWOQdeVOw0CT7ZLJQVyKyYVwY8okWrE%2FaUJB9gB4frH%2Fu2e93pXu1tPGUuS5eEZBImzqhZvab1A1UZqs6iAgAA&config=H4sIAAAAAAAAAzWMSwrDMAxE76K1F8WLLnyHHEK4anCJP0gy1ITcvVGc7maGeW%2BHj0QIOzRkIbYkoyh%2BIQDFjBI5NYXDgSKvpDaLf3gPDrZahSAod3KQU0nvYXysuTGJnPnEMpZ1I8uHtfrqVwMdjS7Z0%2BR%2FerqSLPdvdqmdIy3YZC7HD3Z6E2S2AAAA
Expected behavior
let e=window.__anything;const n=(e?"bEvNbr ":"")+(e?"WhAZY ":"")+(e?"kLKrsq ":"")+(e?"bLIxaN ":"")+(e?"bOjOhu ":"")+(e?"lksDzB ":"")+(e?"edsxqC ":"")+"fygwnR kQBRAp fwqTyU sJymt jdraHW hcJKTR eqrBPF kVZHcH dwawJR iATxZH jQenOz glXlAQ ejfOAg imuUWK jePIQM eCuFxb ieWmMp YseoS ";console.log(n);

Actual behavior
let a=window.__anything;console.log((a?"bEvNbr ":"")+((a?"WhAZY ":"")+((a?"kLKrsq ":"")+((a?"bLIxaN ":"")+((a?"bOjOhu ":"")+((a?"lksDzB ":"")+((a?"edsxqC ":"")+"fygwnR kQBRAp fwqTyU sJymt jdraHW hcJKTR eqrBPF kVZHcH dwawJR iATxZH jQenOz glXlAQ ejfOAg imuUWK jePIQM eCuFxb ieWmMp YseoS ")))))))

Version
1.2.189
Additional context
No response

Could you provide a more concise reproduction?

Simpliefied repro:
console.log(a + ('d' + (b ? 'c' : 'd')))

should be
console.log(a + 'd' + (b ? 'c' : 'd'))

after compress

authors: Austaras SukkaW

repo: swc-project/swc


text:
fix(es/compat): change array spread syntax result on loose mode

Description:

Related issue:

Closes #7354

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.lsdyi seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@Kaciras Sorry to push code without tests. I'm new to this repo🥹, kind of confused where I can complete whole testing process. I noticed we can write input/index.js and inpuit/.swcrc which I think are input example, but I'm confused how I can generate output, which is output/index.js

You can do UPDATE=1 cargo test

Also, can you sign the CLA?

CI is failing. You can update snapshots with UPDATE=1 cargo test

@kdy1 Thank you for the reminder. I'm

Hello @kdy1 , I update the testing file and snapshots. Could you please help me check the code?

Thanks for the CR yesterday @kdy1 , is there anything I can do with this PR?

Please remove the redundant clone. It's removable

Good afternoon ☕ @kdy1  I've removed the redundant clone() method and collected list elements in a specific new for loop. Could you please help me check whether the code meets expectation?

authors: CLAassistant kdy1 lsdyi


text:
Fix SEE considering unprofitable recaptures

Our SEE calculation assumed that opponents would always recapture, even if it were unprofitable for us to do so. This tweaks the math a bit to assume that our opponent will stand pat if a recapture is unprofitable for them materially.

Graphite Merge Job
Current status: ⏳ Queued to merge
This pull request is currently queued to be merged as part of a stack.
This comment was auto-generated by Graphite.

Job Reference: Xyf5xoMTqneX2jTHoCF0


text:
SES time zone

Support decoding time zones in the following format Fri, 26 Jun 2020 03:04:03 -0500 (CDT)
Motivation:
Currently if an email is received with the common header date which includes the timezone in alphabetical form in brackets after the numeric timezone the date does not decode, and SES.Event does not decode.
Modifications:
Code changes include cropping text after any open bracket found in the date string before passing it through the dateFormatter. I don't know of a dataFormat string that will support the above format. If there is one obviously it would be better to use that instead.
Result:
SES.Event decodes even when it holds a date in the above format

orthogonal to these changes but we should add a link to SES event from https://github.com/swift-server/swift-aws-lambda-runtime#integration-with-aws-platform-events

Added the link in

thanks @adam-fowler

authors: adam-fowler tomerd

repo: swift-server/swift-aws-lambda-runtime


text:
Add size for indexstoredb_symbol_role_t

This was previously miscompiling with clang (would be 32 bit instead of
64 bit) and now errors with clang 19. Note that this doesn't seem to
have had any impact within indexstore-db itself - the C++ side is
using a different enum (SymbolRole) which has:
Canonical = uint64_t(1) << 63,

And seems like the only real use of Canonical is
foreachCanonicalSymbolOccurrenceImpl itself (also C++).

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test Windows platform

@swift-ci please test Windows platform

repo: swiftlang/indexstore-db


text:
Simplyfiying the implementation of custom content (Support for Custom HTML)

Feature Name
Support for Custom HTML
Description
I would like to propose a feature enhancement for the Swift DocC compiler to support the inclusion of custom HTML files, specifically header.html and footer.html, with the ability to apply custom elements to DocC documentations. This feature would greatly enhance the customization options for generated documentation.
The DocC compiler should be designed to automatically identify custom HTML files—such as header.html and footer.html—that are stored in a specified directory. By employing a wildcard search, the compiler can efficiently detect these files without requiring users to make manual adjustments to the build process. This approach simplifies management and integration for users who wish to incorporate multiple custom HTML files into their documentation seamlessly.
Furthermore, this enhanced functionality allows users not only to include these customized elements easily but also to style them using CSS. By leveraging CSS, users can ensure a cohesive and visually appealing presentation consistent with their branding across all documentation. This capability plays a vital role in creating a professional and unified look and feel, making the documentation more effective and engaging for its intended audience.
Motivation
Currently, the process of adding custom headers and footers to DocC documentation is not straightforward, which limits the ability to align documentation with project branding. By allowing users to include their own HTML files, we can create a more cohesive and branded documentation experience.
Importance
By streamlining this process, we could significantly enhance the overall usability of DocC documentation. Simplification would not only make it easier for developers to implement these features, but it would also open up greater flexibility and customization options. This would empower teams to align the documentation's visual aesthetics with their project branding more effectively.
A more user-friendly approach would allow developers to devote more time to content creation rather than getting lost in technical hurdles. Ultimately, investing in a streamlined process is vital for ensuring that documentation serves its purpose—providing clear, professional, and consistent guidance that reflects the essence of the project it represents. The potential benefits of such enhancements could lead to more engaging documentation experiences and stronger connections with users.
Alternatives Considered
No response

[Update 23/10/24 19:23]: While reviewing the pull requests, I found #1056, which introduces a custom-scripts.json file for managing custom scripts. This file can also be utilized to include HTML elements, allowing for greater flexibility in documentation customization. For instance, users could easily add their own header and footer HTML files through this configuration, streamlining the process of integrating custom elements into the generated documentation. For example, users can specify their custom HTML files, such as headers and footers, within the configuration like this:
{
   "htmlElements": {
       "header": "path/to/header.html",
       "footer": "path/to/footer.html"
   }
}

This approach can serve as an alternative to the previously mentioned wildcard detection method.
See the full pitch on forums.swift.org ...

As has already been pointed out in the Swift Forums thread that you linked to: DocC already supports including custom header and footer HTML files gated by the --experimental-enable-custom-templates feature flag.

repo: swiftlang/swift-docc


text:
Add simplified implementation of documentation input discovery

Bug/issue #, if applicable: rdar://136208312
Summary
This is the second of many changes to redefine how documentation contexts are created.
This change specifically renames "documentation bundle" to "documentation inputs" and creates a new type that discovers documentation catalogs and creates documentation inputs. This is the same as LocalFileSystemDataProvider and GeneratedDataProvider except that it doesn't conform to DocumentationWorkspaceDataProvider (or any other protocol for that matter).
This new code is't used anywhere (except in the tests that verify that it behaves the same as the previous code). It's going to be a large change to switch over to this implementation, so I've deferred that to a follow up PR because people have been saying that they prefer multiple smaller PRs over one larger PR. For the same reason, this PR doesn't deprecate the old "documentation bundle" name or update existing code that references it.
Dependencies
This builds on top of the changes from #1031.
The specific changes in this PR can be seen in this diff
Testing
Nothing in particular. This is not user-facing change.
Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[x] ~Added~ Update tests
[x] Ran the ./bin/test script and it succeeded
[x] Updated documentation if necessary

I talked to some people about this offline and we agreed that it would be better to split the bundle renaming into a separate PR.

@swift-ci please test


text:
Normalize SE-0451 author and previous proposal fields

The author field of SE-0451 includes a reference to the previous proposal that SE-0451 was based on.
The Author field should only include people. The reference to a previous proposal should be in the Previous Proposal field.
Note also that the author of the previous proposal (SE-0275) is properly credited in that proposal and does not need to be included as part of the current proposal (SE-0451) unless the author of SE-0451 wishes to include them as a co-author.
This PR normalizes the Author and Previous Proposal fields and closes https://github.com/swiftlang/swift-org-website/issues/856.

@allevato, would you like to include Alfredo as a co-author?  You should probably only do so if he's interested in still participating.

authors: dempseyatgithub rjmccall

repo: swiftlang/swift-evolution


text:
Build one test product for both Swift Testing and XCTest (with Swift Testing enabled by default.)

This PR refactors the previously-experimental Swift Testing support logic so that only a single build product is produced when using both XCTest and Swift Testing, and detection of Swift Testing usage is no longer needed at compile time.
On macOS, Xcode 16 is responsible for hosting Swift Testing content, so additional changes may be needed in Xcode to support this refactoring. Such changes are beyond the purview of the Swift open source project.
Resolves rdar://120864035.

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test Windows

Mac CI failures are due to the swift-test command not recognizing its own new --test-bundle-path argument.

@swift-ci please test

@swift-ci please test

@swift-ci please test Windows

@swift-ci please test

@swift-ci please test

@swift-ci please test Windows

@swift-ci please test

@swift-ci please test Windows

Note to self: https://github.com/swiftlang/swift/blob/a3bf1fc4c2ddc46f899b49a88898dee82d63f63e/lib/SIL/IR/SILDeclRef.cpp#L558C1-L559C1

Working around https://github.com/swiftlang/swift/pull/69113 not being present in CI toolchains (?)

@swift-ci please test

@swift-ci please test Windows

@swift-ci please test

@swift-ci please test Windows

@swift-ci please test

@swift-ci please test Windows

@swift-ci please test

@swift-ci please test Windows

@swift-ci please test Windows

@swift-ci please test

@swift-ci please test Windows

I've looked through all the changes and didn't spot any obvious issues though I'm not at all familiar with this code so please take this approval with a grain of salt :)

Thanks Dennis—the more eyes the better given the size of the diff.

Wait what

Okay then.

repo: swiftlang/swift-package-manager


text:
[CMake] Enable package CMO only in newer compiler

Cherry-pick #2764 into release/6.0

@swift-ci Please test

repo: swiftlang/swift-syntax


text:
Feature request: Indented output in the console for tests within a suite

Description
Currently the output to the console is flat:
For example, the below console output...
◇ Test run started.
↳ Testing Library Version: unknown (Swift 5.10 toolchain)
◇ Suite NotificationsDeepLinkUrl started.
◇ Test returnsAppPreferencesNotificationsUrl_wheniOS() started.
✔ Test returnsAppPreferencesNotificationsUrl_wheniOS() passed after 0.003 seconds.
✔ Suite NotificationsDeepLinkUrl passed after 0.003 seconds.
◇ Suite QueueNotificationsForRunChangesReturningBranchNames started.
◇ Test returnsEmptyArray_whenOldRunsHasARun_butNotificationsAreNotAvailable() started.
✔ Test returnsEmptyArray_whenOldRunsHasARun_butNotificationsAreNotAvailable() passed after 0.008 seconds.
◇ Test returnsEmptyArray_whenOldRunsIsEmpty() started.
✔ Test returnsEmptyArray_whenOldRunsIsEmpty() passed after 0.002 seconds.
◇ Test returnsNewRun_whenOldRunsHasANewRun_andNotificationsAreAvailable_andNotificationPreferenceIsEveryone() started.
✔ Test returnsNewRun_whenOldRunsHasANewRun_andNotificationsAreAvailable_andNotificationPreferenceIsEveryone() passed after 0.012 seconds.
✔ Suite QueueNotificationsForRunChangesReturningBranchNames passed after 0.023 seconds.
✔ Test run with 4 tests passed after 0.027 seconds.

This can be difficult to read both at a glance and with some time invested, especially when Suites are nested within other Suites.
Proposal
It would be nice if we could indent the tests/suites to a hierarchy like the below structure:
◇ Test run started.
↳ Testing Library Version: unknown (Swift 5.10 toolchain)
◇ Suite MySuite started.
  ↳ ◇ Suite MyChildSuite started.
      ◇ Test someTest() started.
      ✔ Test someTest() passed after 0.003 seconds.
      ↳ ◇ Suite MyGrandChildSuite started.
          ◇ Test someGrandChildTest() started.
           ✔ Test someGrandChildTest() passed after 0.003 seconds.
◇ Suite MyOtherSuite started.
  ↳ ◇ Suite MyOtherChildSuite started.
      ◇ Test someOtherTest() started.
      ✔ Test someOtherTest() passed after 0.003 seconds.

Benefits
The above output is easier to read at a glance and to see what tests and suites are a part of their parent - simplifying readability and seeing at a glance where a test might live to go and debug and ultimately fix it.
Potential issues
All the indenting
This could of course get a bit crazy if you have many nested Suites where the indentation could be so long that it becomes unreadable so we could either:

Limit this indentation to A sensible level like 5 child indents
Leave this down to the developer who ultimately controls their levels of nested Suits/Tests

Parallelised tests
As pointed out by @stmontgomery here https://github.com/apple/swift-testing/issues/296#issuecomment-2002027577 in my original post https://github.com/apple/swift-testing/issues/296, this could work badly with parallelised tests where the output is non-linear and indentation would cause the tests to be indented under a parent that it's not a part of, eg a parallelised test could appear under a suite it's not a part of because it just happened to run at the same time as the other test in the other suite.
However, this could be remedied simply by the parents being printed on the line above in the console if it hasn't already to make it explicit where the test came from.
Expected behavior
No response
Actual behavior
No response
Steps to reproduce
No response
swift-testing version/commit hash
0.6.0
Swift & OS version (output of swift --version && uname -a)
swift-driver version: 1.90.11.1 Apple Swift version 5.10 (swiftlang-5.10.0.13 clang-1500.3.9.4)
Target: arm64-apple-macosx14.0
Darwin AT-ALK6L5VQ 23.3.0 Darwin Kernel Version 23.3.0: Wed Dec 20 21:30:44 PST 2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T6000 arm64

Apologies for the delay, this sounds great re OS log and the direction for having a more complex/controlled output instead of stderr
Sounds like this one might be on hold for a while until the ground work is done for that above but all sounds good to me 👌🏻

Tracked internally as rdar://103374320.

Couldn't we make a stopgap that adds @Suite names to each @Test name?
Given the following code:
import Testing

@Suite struct GuitarTests {
  @Test func chordTest() {}
}

@Suite struct BassTests {
  @Test func chordTest() {}
}

Current output:
◇ Test run started.
↳ Testing Library Version: 94 (arm64e-apple-macos13.0)
◇ Suite BassTests started.
◇ Suite GuitarTests started.
◇ Test chordTest() started.
◇ Test chordTest() started.
✔ Test chordTest() passed after 0.001 seconds.
✔ Test chordTest() passed after 0.001 seconds.
✔ Suite GuitarTests passed after 0.001 seconds.
✔ Suite BassTests passed after 0.001 seconds.
✔ Test run with 2 tests passed after 0.001 seconds.

After (ad-hoc) improvement:
◇ Test run started.
↳ Testing Library Version: 94 (arm64e-apple-macos13.0)
◇ Suite BassTests started.
◇ Suite GuitarTests started.
◇ Test BassTests.chordTest() started.
◇ Test GuitarTests.chordTest() started.
✔ Test GuitarTests.chordTest() passed after 0.001 seconds.
✔ Test BassTests.chordTest() passed after 0.001 seconds.
✔ Suite GuitarTests passed after 0.001 seconds.
✔ Suite BassTests passed after 0.001 seconds.
✔ Test run with 2 tests passed after 0.001 seconds.

authors: YOCKOW adamcarter93 adammcarter grynspan

repo: swiftlang/swift-testing