text:
Bring list of annotations upward in the document schema

Hallo substance team,
I have the following issue with annotations
while attempting to write an Elixir Renderer (HtmlExporter) for substance document.
Let's say I have the following document produced by a substance editor:
{
  "schema": [
    "myDocumentSchema",
    "0.1.0"
  ],
  "nodes": {
    "body": {
      "type": "container",
      "id": "body",
      "nodes": [
       "id_1",
       "id_2",
       "id_3"
      ]
    },
    "id_1": {...},
    "id_2": {...},
    "id_3": {...},

    "annotation_id_1": {...},
    "annotation_id_2": {...}
  },
}

At present, when I want to apply annotations to the nodes listed in the manifest at /nodes/body/nodes,
I have to scan all nodes at /nodes and for each (id, nodeObject), if nodeObject is an annotation,
then apply it to the target node specified by the nodeObject.path property.
Now, when having a lot of nodes this approach might become unpractical.
Is there a way to have my document schema
explicitely listing annotation ids
in a way that I can pick exactly those nodes upfront and let them act on the others, e.g. as per
{
  "schema": [
    "myDocumentSchema",
    "0.1.0"
  ],
  "nodes": {
    "body": { ... },

    "annotations": {
      "type": "annotation_list",
      "id": "annotations",
      "nodes": [
        "annotation_id_1",
        "annotation_id_2"
      ]
    },
    "id_1": {...},
    "id_2": {...},
    "id_3": {...},

    "annotation_id_1": {...},
    "annotation_id_2": {...}
  },

}

Is there a way to tell substance to include such list in the schema?
I might well have overseen some detail, maybe in the documentation?
Would it be worth considering it a feature?
Cheers,
Andrea

We're discussing persisting an XML-file format like in http://substance.io/lens/data/example-doc.xml for articles.

@zampino we're using the internal representation of substance documents at the moment. In javascript you'd have such helper functions available.

Let's discuss this stuff in person on next meeting.

authors: michael mk zampino

repo: substance/substance


text:
The given range isn't in document

Steps to reproduce:

Open contrib panel
Add one symbol to first contrib name
Remove first contrib

Fixed

whoops wrong issue

This happens if we try to recover the selection on an just deleted surface.

Two issues with different priorities are involved here:

Surface disposal is broken (critical)
Selection is not invalidated if the containing context has been deleted

Fixed the first issue via https://github.com/substance/substance/pull/1071/commits/f51ad882585b12d6e38c4da5f653ced3dc8df22a

source: gharchive/issue

authors: Integral michael oliver----

repo: substance/texture

license: mit

license_type: permissive

license_source: bigquery


text:
Error in script

When I was creating peer on hyper-v I got this error:

Done.

repo: subutai-io/vagrant

license_source: github-api


text:
Convert account to business account

Is there a way to convert a personal account to business account with Instagrapi?

No

With API, you can do. But instagrapi doesn't have that option

authors: brunobely kingbotss sunmasters

repo: subzeroid/instagrapi

license: MIT


text:
About us page

I made an About Us page explaining what the site is about and giving a short tutorial on how beginners can make a pull request on this repo

Everything is great except do these changes :

No javascript in html files
No css in html files
All css files in style folder and named according to their page as page.css
Rebase your code please, I tried to merge but there are too many differences.

Also please do not make so many different changes in one PR.

source: gharchive/pull-request


text:
Publishing on JSR

The Deno Team have made a new registry i wanted to ask if xior could be published on JSR as well.
It would made it easier for Deno users. They have autogen Docs.

Xior's plugins rely on modifying global types, and deno not support, check here:
https://github.com/suhaotian/xior/pull/2
And I tried to publish to JSR, but it's so disgusting when doing that, and failed.

ok, might get better in the future. Jsr is really new.

do u know a good doc gen tool? my primarly i would love to use one for my dependecies.

Try typedoc

I use typedoc generate the docs of xior, check here: https://suhaotian.github.io/xior/

repo: suhaotian/xior


text:
Add Stephon Clark data links

I hope we can add the Stephon Clark data links to the Timeline Page to show what we hope to acheive long-term.
Additionally, I created a generic slide listing "samples" of upcoming topics.
If you all think the Search page is too busy, we can add it to the About Page.
Both sildes are on the 1 attached file.
I added the slides to Phase 3 Folder but Google looks uglier so I attached the PPT slide.
Stephon Clark Data Interconnections SLide.pptx

Added relevant info from above powerpoint to this document. Lines crossed out in this document have been added to linkurious.

authors: gbasel peetucket

repo: sul-dlss-labs/ksr


text:
Do we need to allow DepositFile.json as one of the DepositResource schemas?

It seems like we can get by with just creating the file using handlers/deposit_file.go, which will attach a File resource to the provided Fileset.

Yes, we do.

This is part of not have any resource type's data shape specified / buried in the go code but specified in a consistent MAPs doc.

My concern here is that we've made it possible for clients to create File objects and they can't get any file in storage attached to them.  Is that right?

repo: sul-dlss-labs/taco


text:
Navigation/Breadcrumb Page from type internal link has uuid from linked site

/cc @quehnie

@alexander-schranz can you describe further?

Example Navigation

Point 1 (Internal Link to Point 1.1) (false marked as current page)
Point 1.1(active site) (marked as current page)
Point 1.2
Point 2
Point 2.1 (Internal Link to Point 1.1) (false marked as current page)

To check which site is active in the navigation loop we check uuid == navigationItem.uuid
as Point 2.1 and Point 1 link to the current site they are also marked as current site.
Don't know whats correct uuid we should return. In this case you need the real uuid and not the linked, but in other cases you maybe need the linked site.

So the real issue you want to have solved is probably https://github.com/sulu-io/sulu/issues/492 (although I think the behavior should be like you described).

yeah #492 would fix this problem and the uuid would not be needed.
we should also keep in mind to flag the current page as active and the parent pages maybe as activeParent or hasActiveChild. The difference is sometimes needed e.g. to show the submenu as open when a child page is active.

As #492 is the real issue I close this issue. The current work around is using the path instead of the uuid for active navigation:
{% if path ~ '/' starts with item.path ~ '/' -%}
    class="active"
{%- endif %}

authors: alexander-schranz danrot

repo: sulu-io/sulu


text:
Update to v0.6.9 of summernote?

Would it be possible to update to the latest version (v0.6.9) of summernote any time soon?
Thanks.

@san v0.6.9.0 is released now. This is first time by myself on this repository. If there is problem, Let me know. Thanks.

Hi, I am unable to find the version 0.6.9 in rubygems.org, please help!

@hackerwins It does look like released, but as previous commenter said, when I update from github, I still the previous release. I am not sure how to do it, but may be one step is missing that registers the release with rubygems.org.

@hackerwins You may need to do something like this? http://guides.rubygems.org/publishing/#publishing-to-rubygemsorg
Not sure though.

@hackerwins You may need to do this? http://guides.rubygems.org/publishing/#publishing-to-rubygemsorg
Not sure though.

@rasool-sb Feel free to use my branch until this is resolved:
gem 'summernote-rails', github: 'san/summernote-rails'

Hi @san Thank you so much, :)

@san thanks I'll try

@rasool-sb @san sorry for lazy update
updated rubygems :)

Hurray... Thank you so much @seapy @san Love you and Love this Awesome Gem.. :)

authors: hackerwins rasool-sb san seapy

repo: summernote/summernote-rails


text:
添加属性/方法的方法

能够标注一个方法为“为对象添加属性/方法”的方法吗？比如说
local function A(obj)
obj.name = "233"
end
可以对A进行标注，表示调用A之后obj会多出name属性吗？

调用函数的语义太不明确了，如果未来要支持也是加个新的 LuaDoc 注解。

想了一下还是得用继承来实现，这是为了保证类型定义的严谨，定义的地方多写一点，用的地方就可以少些一点。

authors: Weiged sumneko

repo: sumneko/lua-language-server


text:
Trying to run with half precision gives error "RuntimeError: "LayerNormKernelImpl" not implemented for 'Half'"

I am trying to follow the instructions for bark from the HuggingFace Bark Docs and I saw the part where it said that I can reduce memory footprint by running in half precision by doing the following:
model = BarkModel.from_pretrained("suno/bark-small", torch_dtype=torch.float16).to('cpu')
However when I do this, it crashes with the following error:
File ~/anaconda3/lib/python3.11/site-packages/transformers/models/bark/modeling_bark.py:195, in BarkLayerNorm.forward(self, input)
    194 def forward(self, input):
--> 195     return F.layer_norm(input, self.weight.shape, self.weight, self.bias, eps=1e-5)

File ~/anaconda3/lib/python3.11/site-packages/torch/nn/functional.py:2546, in layer_norm(input, normalized_shape, weight, bias, eps)
   2542 if has_torch_function_variadic(input, weight, bias):
   2543     return handle_torch_function(
   2544         layer_norm, (input, weight, bias), input, normalized_shape, weight=weight, bias=bias, eps=eps
   2545     )
-> 2546 return torch.layer_norm(input, normalized_shape, weight, bias, eps, torch.backends.cudnn.enabled)

RuntimeError: "LayerNormKernelImpl" not implemented for 'Half'

What is causing this? Is there something else I need to add to my code?

In model = BarkModel.from_pretrained("suno/bark-small", torch_dtype=torch.float16).to('cpu'), you are setting the dtata type to a half float try loading it in full float model = BarkModel.from_pretrained("suno/bark-small", torch_dtype=torch.float32).to('cpu').

repo: suno-ai/bark


text:
Add JSON Web Token authentication support

It would great to support the following project that implements JWT auth backend: https://github.com/GetBlimp/django-rest-framework-jwt

+1 Any ideas how we could support DRF token, our custom multi device token and JWT? Probably we should implement some generic layer between our views and authentication backends.

I'm already using djoser with DRF-JWT and it seems to be working just fine. Is it a weird unexpected feature?

Sounds awesome! It would be cool to have it documented and tested. @avimeir, we will appreciate any pull requests in that matter!

Try to turn on token-based authentication on DRF (http://www.django-rest-framework.org/api-guide/authentication/#tokenauthentication) and then follow the usual install of DRF-JWT, then added djoser and it works right of the box with no modifications to the code.

@avimeir,

If so still djoser will be creating token in the database? how did you overcame it?
Will be there any change in the flow of /login/,?

@NabeelValapra

I assume that djoser will use the authentication class configured by DRF, which happens to be DRF-JWT (rest_framework_jwt.authentication.JSONWebTokenAuthentication). I must admit that I haven't looked into it, so the fact that it's working is pure magic at this point :)
Well, you need to follow the DRF-JWT flow for issuing a JWT, by default the endpoint is: ^api-token-auth/

+1 to support JWT. make authentication backend configurable instead of binding with Token auth.

I have read the @haxoza POC in this matter and I think is the way to do it, by the way:
@NabeelValapra

You use rest_framework_jwt.authentication.JSONWebTokenAuthentication, and delete 'rest_framework.authtoken' from your installed apps. At this point, /auth/login/ endpoint is broken (maybe some others) as the token table is not created
I override djoser login url with drf-jwt

url(r'^auth/login/', 'rest_framework_jwt.views.obtain_jwt_token'),

+1

What is the status here? Did anyone get it to work, reproducibly? Would be much appreciated...

Hi @uniqueg, you can always try something like this:

import rest_framework_jwt.views
import djoser.views

urlpatterns = [
    url(r'^auth/login', rest_framework_jwt.views.obtain_jwt_token),
    url(r'^auth/register', djoser.views.RegistrationView.as_view()),
    url(r'^auth/password/reset', djoser.views.PasswordRestView.as_view()),
    url(r'^auth/password/confirm', djoser.views.PasswordResetConfirmView.as_view()),
    ...
]

To be honest, I think that we don't have to implement anything in djoser to support JWT right now.
@haxoza maybe we should close this issue?

@konradhalas
Please document your answer somewhere before closing?
But I agree. It just works.

Thanks a lot @konradhalas and @lwm, it sounds straightforward enough, and clean too! I was a bit confused by the previous discussion and wasn't sure it would work.

FYI: https://github.com/sunscrapers/djoser#json-web-token-authentication

authors: NabeelValapra avances123 avimeir cerdman haxoza konradhalas liaoliaopro lwm uniqueg

repo: sunscrapers/djoser


text:
Can't get session and user after success call supabase.auth.signInWithOAuth(Provider.******)

Can't get session and user after success call supabase.auth.signInWithOAuth(Provider.******)
After signing into the app with supabase.auth.signInWithOAuth(Provider.******);
it is clear that everything worked correctly, the user's photo appears in the window.
But I can't get session and user: Supabase.instance.client.auth.currentSession == null
and Supabase.instance.client.auth.currentUser == null.
In the supabase console, the new user is not added to the user list.
Prompt the decision of reception of session and the user after OAUTH authorization.

@r-serega
Have you setup deep links to bring the user back to the app after completing the OAuth sign in?
You can follow here to configure deep links.

are you talking about this page?

so they are listed

+1

authors: Subrataporwal dshukertjr r-serega

repo: supabase-community/flutter-auth-ui


text:
4.x patches

Restored error type.

Reason:

it is useful
it is used in demos & examples (it will be simpler to convert them to Godot 4)

func _on_auth_error(error : SupabaseAuthError):
	get_tree().call_group("loading_scene", "set_loading")
	match error.type :
		"invalid_grant":
			sign_up(mail ,pwd)

Fixed responses without body

Reason:

assigning null to dictionary type causing error
logout is totally not working (no body in response)

Added missing awaits

Reason:

sign in is just not working for GDScript style, I'm using todo demo (adjusted for 4.x) like below:

# log_screen.gd
func sign_in(email : String, password : String):
	Supabase.auth.sign_in(email, password)
	error_lbl.hide()

# main.gd
func _ready():
	Supabase.auth.connect("signed_in", _on_signed)

And that _on_signed is not executed.
These awaits makes that sign in is working properly and _on_signed is executed.
It fix only GDScript style, JS style don't need that fix.
Looks like example from readme.md not working also without that awaits.
func _ready():
	Supabase.auth.signed_in.connect(_on_signed_in)
	Supabase.auth.sign_in(
		"user@supabase.email",
		"userpwd"
	)

func _on_signed_in(user: SupabaseUser) -> void:
	print(user)

Sorry, that 'sign in' problem should be fixed better. I'm looking for better way.

Hi @stmn
thanks for all your contributions!
The issue with the tasks routines not working with the gdscript style is that since latest betas of Godot 4.0 RefCounted classes are handled differently.
Eventually any reference to the BaseTask is lost and the task is not processed anymore, so the signal will httprequest.completed signal will never be executed.
In my opinion there's no necessity to change the codebase for now, returning a Signal (which will never be directly used), or adding the await in the inner functions (since this will force asynchronous calls to be synchronous anyway).
Instead manually referencing and unreferencing should work.
# base_task.gd

func push_request(httprequest : HTTPRequest) -> void:
+	reference()
	httprequest.request_completed.connect(_on_task_completed.bind(httprequest))
	httprequest.request(_endpoint, _headers, true, _method, _payload)

func _on_task_completed(result : int, response_code : int, headers : PackedStringArray, body : PackedByteArray, handler: HTTPRequest) -> void:
	pass

func _complete(_data = null, _error : BaseError = null) -> void:
	data = _data
	error = _error
	completed.emit(self)
+	unreference()

would you mind making a quick check?

@fenix-hub It works, commited.

authors: fenix-hub stmn


text:
Allow auto detection of --no-verify-jwt

Feature request
When you update your functions, you have to do folder by folder and most of the time the only function who need --no-verify-jwt you forgot to do it.
This will never change, it can be cool to have a way to set for once.
I have made a script who looks into the function folder and deploy all of them
To handle my --no-verify-jwt issue, I added an empty file .no-verify-jwt into the folder stripe_event who is the one i need to have this.
When my script sees this, it runs the command with the option.
Then it's never forgotten.
Describe the solution you'd like
It could be cool to integrate this directly in the CLI
Describe alternatives you've considered
continuing to use my script

Thanks for the suggestion! This is likely going to be a config eventually, e.g.:
[functions.my_function]
no_verify_jwt = true

For now what i'm doing to handle this is a script:
import { existsSync, readdirSync } from 'fs'
import { promisify } from 'util'
import { exec as execCb } from 'child_process'
import { exit } from 'process'
import { outputFile } from 'fs-extra'
import { supa_url } from './utils.mjs'

const exec = promisify(execCb)
const folders = readdirSync('./supabase/functions')
  .filter(file => !file.startsWith('_'))

const projectRef = supa_url.split('.')[0].replace('https://', '')

try {
  console.log('projectRef', projectRef)
  await outputFile('./supabase/.temp/project-ref', projectRef)
  // for in folders
  for (const folder of folders) {
    const fileNoJWT = `./supabase/functions/${folder}/.no_verify_jwt`
    const fileNoDeploy = `./supabase/functions/${folder}/.no_deploy`
    let command = `supabase functions deploy ${folder}`
    let no_verify_jwt = false
    if (existsSync(fileNoJWT)) {
      command += ' --no-verify-jwt'
      no_verify_jwt = true
    }
    if (!existsSync(fileNoDeploy)) {
      console.log(`Upload ${folder}${no_verify_jwt ? ' no_verify_jwt' : ''}`)
      await exec(command).then((r) => {
        if (r.stderr) {
          console.error(folder, r.stderr)
          exit(1)
        }
        return r
      })
      console.log('Done ✅')
    }
    else {
      console.log('Ignored ⏭')
    }
  }
}
catch (e) {
  console.error(e) // should contain code (exit code) and signal (that caused the termination).
  exit(1)
}

i have also add the option to have no_deploy that allow me to store a demo function in GitHub without pushing it

@soedirgo thanks a lot! Where can I found the documentation of the feature?

We'll put up the docs on the CLI reference later. You can use it like so:
# ...

[functions.func_a]
verify_jwt = false

[functions.func_b]
verify_jwt = true

It works !

I ended up here because I missed this in the docs somehow)
I started to implement a custom directive like use strict that could be parsed during the deploy.
'no-verify-jwt`;

import {server} from '...';

The one advantage here is that it's explicit in the code that the default security is disabled for the endpoint...

authors: ChuckJonas riderx soedirgo

repo: supabase/cli


text:
feature: Rename listUsers to findUsers and support filter search and sort params

Feature request
While the PR https://github.com/supabase/gotrue-js/pull/195 adds listUsers, perhaps it should be renamed findUsers since the GoTrue implementation supports a find filter using FindUsersInAudience that finds users with the matching audience with a filter option and a sort:
if filter != "" {
	lf := "%" + filter + "%"
	// we must specify the collation in order to get case insensitive search for the JSON column
	q = q.Where("(email LIKE ? OR raw_user_meta_data->>'full_name' ILIKE ?)", lf, lf)
}

if sortParams != nil && len(sortParams.Fields) > 0 {
	for _, field := range sortParams.Fields {
		q = q.Order(field.Name + " " + string(field.Dir))
	}
}

But, the only filter currently is email.
Describe the solution you'd like

Rename listUsers to findUsers
Support option filter with explicit types like byEmail or email
Consider supporting sort params
Document

Additional context
See: https://github.com/supabase/gotrue-js/issues/187

This is a great suggestion. A couple of notes:

Filtering by arbitrary fields is problematic for scaling issues as larger projects with more than 1000 users will be draining the CPU / disk of the database.
Wildcard prefix/suffix queries can't use indexes so the same (or worse) scaling issues will occur.
Sorting and other facilities on arbitrary fields can incur very heavy resource usage, especially due to paging on sorted fields.

For this reason, we're unlikely to support arbitrary filtering and will be redoing much of the existing anyway to ensure a scalable and performant implementation.
Things we are likely to support when filtering:

Prefix search on email, phone number, other identity provider attributes (Twitter user ID).
Filtering by some categories: blocked / unverified / verified / identity provider...
Token-based pagination instead of page-offset pagination.

Since this spans both gotrue and this library, I'm adding this to the team's backlog. No clear timeline on it yet. I'll close this issue but should people have more to contribute, do comment.

authors: dthyresson hf

repo: supabase/gotrue-js


text:
feat: add fly oauth provider

What kind of change does this PR introduce?

Adds the ability to sign-in with fly (useful for provisioning a fly extension)
Mainly for internal use

@J0 i don't think we'll be exposing this to the public on the hosted platform for now because the fly extensions program is private

repo: supabase/gotrue


text:
fix: Add Web Workers as a way to run health check

What kind of change does this PR introduce?
Adds Web Workers as a way to run heart beat on Realtime to avoid suspending the tab.

Perhaps the non-worker part of the lib should send a message to alert the worker to stop (and possibly to start again on reconnect). Also curious if the server part is able to cleanup resources effectively if it still receives heartbeat.

address: https://github.com/supabase/realtime-js/issues/121

authors: filipecabaco netgfx w3b6x9

repo: supabase/realtime-js


text:
feat: Resumable uploads

What kind of change does this PR introduce?

Resumable uploads feature.

@juancarlospaco has this been tested in a real project to know if it works?

Will this be merged anytime soon? Experiencing some problems with regular uploads from some instances and this has been suggested as a possible fix in a ticket.

I've finally gotten around to reviewing this and there are a few things I think we should change here.

The API seems too verbose and requires too many steps to start uploading when compared to https://github.com/tus/tus-py-client or even https://github.com/tus/tus-js-client.
I have tested this with local Supabase (and this will probably be the same with self-hosted) and the TUS implementation in these environments don't return an upload-expires header and this is not implemented in any of the other TUS clients I've looked at so we should probably not have this either
In the tests you are checking if a url is https, not sure if this is a requirement for uploads as local Supabase doesn't have TLS enabled by default

After having a chat with @grdsdev, I think this PR should be put on hold for now. It diverges from the other Supabase client libraries and we should probably wait for an API design to be agreed upon before including resumable uploads into the Python library itself. In the time being we can add example code to the docs https://supabase.com/docs/guides/storage/uploads/resumable-uploads?queryGroups=language&language=js where Resumable uploads is mentioned using one of the third party libraries available for TUS with Python.

repo: supabase/storage-py


text:
setAuth() is not returning { user, error } when called server side

Bug report
Describe the bug
It seems like the documentation for setAuth() is wrong. The express example shows { user, error } as the returned object. However, it seems like this is not implemented: https://github.com/supabase/gotrue-js/blob/edcd2ffde6dfe81d02700a52a79e635a5ab8839d/src/GoTrueClient.ts#L389
As far as I understand it, this is what is used for server side calls, correct?
Expected behavior
Return { user, error } as documented, also server side.
System information

OS: macOS
Version of supabase-js: v16.1.0^1.31.1
Version of Node.js: v16.1.0

Yes, you're correct. Not sure when the docs will reflect this - or if there are plans to include error in the returned object, but you can contribute to the docs if you'd like - https://github.com/supabase/supabase/blob/master/DEVELOPERS.md
On the server-side, it returns an object with access_token: with a value of whatever you provided it, token_type: bearer, and user: null.
Only on the client-side does it return this info, plus info for the user associated with the token and the current session.

repo: supabase/supabase-js


text:
Chore: improve styling of Auth social error messages

I'm closing this - it's not really important

I'm closing this - it's not really important

repo: supabase/ui


text:
Can you tell me the CVE num about this UAF bug?

Can you tell me the CVE num about this UAF bug?
thanks!

Not committed yet. Not so much useful after a few investigations.

authors: pppdddxxx superguo

repo: superguo/poc-ion-uaf


text:
Create wp-cli.yml

Fixes #10
I included the file at the root of the project to be able to run wpcli command not only inside the wordpress folder

@kuuak this file was dropped to do everything in docker and to avoid adding wp cli as a project dependency, because:

it means one has to install PHP locally (+ wp-cli)
there can be PHP (and wp-cli) version mismatch

What are your thoughts?

An alternative could be to add an alias in package.json maybe? To be able to npm run wp user list

@hsmio It's just because I use quite a lot wp-cli in my daily dev. This doesn't mean that the project is dependent of wp-cli (no script has the wp-cli as dep), but just that it can be used easely if the person has wp-cli installed.
I could add a note to the README that the wp-cli is an optional solution to query WP

authors: hsmio kuuak

repo: superhuit-agency/superstack


text:
[SuperTextfield] Special characers (ñ è ä ü ö) not working when triggered from US keyboard

Certain special characters can't be entered anymore from US keyboard layouts, for example
ñ
ä
è
If they are a combination of two key inputs (for example Option+n and n to create ñ)

@miguelcmedeiros fyi

For reference #828 may be connected.

@matthew-carroll, we don't see this issue with SuperEditor, only with SuperTextField.
The demo app shows the same issue.

@miguelcmedeiros are we talking about hardware keyboard, software keyboard, or both?
@angelosilvestre can you take a look at this?

@matthew-carroll, in my case I was running the demo app on macOS using a hardware keyboard.

@miguelcmedeiros @MarcelKaeding, this is also happening on Super Editor when using keyboard input source.
At first look, this seems to be a flutter issue. For example, in a Brazilian keyboard, to type the character ã we type a ~ followed by an a. This produces the character ã. I would expect the flutter only reports the ã  character. Instead, it reports a ~  character followed by an ã character. There are some similar issues that are already closed in the flutter repo.
I filed https://github.com/flutter/flutter/issues/117294
I will open a PR enabling IME for super textfield on desktop.

authors: MarcelKaeding angelosilvestre matthew-carroll miguelcmedeiros transcendr


text:
🛑 Node - de-053d2451.yalaso.top is down

In 49a0b85, Node - de-053d2451.yalaso.top (http://de-053d2451.yalaso.top/api/v1/ping) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Node - de-053d2451.yalaso.top is back up in 059b701.

repo: superrr-vpn/status


text:
🛑 Node - ca-6790b1e9.yalaso.top is down

In 24b3682, Node - ca-6790b1e9.yalaso.top (http://ca-6790b1e9.yalaso.top/api/v1/ping) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Node - ca-6790b1e9.yalaso.top is back up in 11bf062.


text:
refactor: go through all build

This change is

The default max_width is already set to 100 - what do you think about either going with that (by removing this override) or using a cozier width like 80?

Then let's go with 100.

repo: suraft/suraft


text:
About us page added

Thanks for your opportunity !!

Not really what was shown in #40 at all... quite visually some bugs, if you are able to fix those, besides that fix your image paths.

authors: PumpkinManiac xMrAfonso

repo: surajondev/UI-UX-Design


text:
fix(template): add quantumultx require fields

These fields are mandatory options for the configuration file, even if they have no content.

感谢贡献代码！

authors: PaiJi geekdada

repo: surgioproject/create-surgio-store


text:
Installation instructions plus other README updates

Are there any plans to update the README? Some things that I think should be added include:

Installation instructions
A simple demo for how to use the driver
A link to further documentation
Maybe a contributing/code of conduct section?
Maybe an image/surrealdb logo or something cool at the top (not necessary but kind of cool)

I would be happy to add any or all of the above to the README myself should the owners/maintainer like that.

Okay. Thanks @tsunyoku. I will get started with the image.

Image could be cool, we can likely copy it from the main repo

Are you referring to this image?


text:
Service extraction-dspace requires info object to be filterable by category

See https://github.com/sustainability-zhaw/extraction-dspace/issues/16

This works so no changes required.
{
   queryInfoObjectType(filter: { name: { eq:"publications" } }) {
    objects(order: { desc: dateUpdate }, first: 1) {
      dateUpdate
    }
  }
}

repo: sustainability-zhaw/dgraph-schema


text:
Pin version of requests package

A bit of testing is required.
It looks like gql[requests] pulls a version of requests that is not compatible with urllib 2.x.
Result is the following error:
cannot import name 'appengine' from 'requests.packages.urllib3.contrib'
Possible solutions:

Pin the version of requests to something compatible with gql 3.4.0 and urllib 2.x
Pin the version of urllib to 1.x

Does the PR fix this issue?

It does solve the problem but I have not looked if it is a known issue. Only found information that the error is related to urllib3 and requests compatibility.
Looking at gql and requests requirements my guess is pip is not resolving the deps correctly and the following happens.

gql pulls requests < 3
requests pulls urllib3 < 3 (In our case urllib3 2.x ignoring gql requirements for urllib3 < 2)?

gql
https://github.com/graphql-python/gql/blob/d140b830cd47fea5513b6bc30b1289c6416d25df/setup.py#LL44C1-L48C2
install_requests_requires = [
    "requests>=2.26,<3",
    "requests_toolbelt>=0.9.1,<1",
    "urllib3>=1.26,<2",
]

requests
https://github.com/psf/requests/blob/6e5b15d542a4e85945fd72066bb6cecbc3a82191/setup.py#LL61C1-L66C2
requires = [
    "charset_normalizer>=2,<4",
    "idna>=2.5,<4",
    "urllib3>=1.21.1,<3",
    "certifi>=2017.4.17",
]

Problem was fixed in gql 3.4.1. Upgrading it is the better fix.
https://github.com/graphql-python/gql/issues/412

repo: sustainability-zhaw/sdg-indexer


text:
Resolve containers

Hi
I'm trying to install Kepler on an openshift cluster and an error occurs.
The log of the kepler-exporter pod is as follows:
I0323 15:55:54.326436       1 resolve_container.go:144] failed to get response: failed to get response from "https://XXXXXXXX:10250/pods": Get "https://XXXXXXXX:10250/pods": dial tcp: lookup XXXXXXXX on Y.Y.Y.Y:53: no such host

podLister.ListPods()  returns this error...
How do I resolve it?

XXXXXXXX refers to node name.
The host cannot resolve the IP of the node name.
I wonder why can't we just use the localhost to connect to kubelet.
Do we expect remote kubelet? In that case, I think we might rename the environment name.
btw, we can also get hostname from os.Hostname().
https://github.com/sustainable-computing-io/kepler/blob/7942754e9324f675ca99572e45a0db8dcb1a5ff0/pkg/kubelet/kubelet_pod_lister.go#L56-L67

I wonder why can't we just use the localhost to connect to kubelet.

localhost will be the pod that running kepler ,correct? pod and node has different tcpip stack so I am wondering localhost will not be the right endpoint

May try removing the environment NODE_NAME from the deployment manifest.

not sure whether we need support https://virtual-kubelet.io/ (I guess not) but this might need further discussion

In my environment, using localhost instead of node name does not work...
I'm not sure it's a configuration of openshift or just our environment.
but I replaced reference path for the NODE_NAME to status.hostIP in the yaml instead of  spec.nodeName and it worked.

as I mentioned, the pod running kepler is not able to use localhost to get node info, so that's what you already see
and there must be some issue in your pod DNS setting or it didn't include the hostname of the node into DNS record list
so you can't access through DNS hostname and ip works because it can access.. so it's not kepler unique issue
thus, maybe we can consider provide a config item like IP/HOSTNAME?

@rinana thanks for the solution, can you post a PR?

@rootfs I posted PR #604

may I have two questions here?

if we specific for hostname/ip address, and combine with a port number there... Hence why not just have an env just as hostname:port ?
should we adjust helm and operator for any environment value changes/updates?

closed by #604

thank you @rinana

authors: SamYuan1990 jichenjc rinana rootfs sunya-ch

repo: sustainable-computing-io/kepler


text:
Add ogham/exa

https://github.com/ogham/exa
https://the.exa.website/
A modern replacement for ‘ls’

linux

exa-linux-armv7-v0.10.1.zip
exa-linux-x86_64-musl-v0.10.1.zip
exa-linux-x86_64-v0.10.1.zip

darwin

exa-macos-x86_64-v0.10.1.zip

exa-accoutrements-v0.10.1.zip

repo: suzuki-shunsuke/aqua-registry


text:
Check if Duktape could be added to kangax/compat-table

https://github.com/kangax/compat-table

This seems to be doable, though the results need to be updated manually (I'm not sure if that's the right way). I'll open a few pulls to the compat-table repo.

https://github.com/kangax/compat-table/pull/1069

I find it rather amusing that Duktape passes the "proper tailcall" tests when almost no other major engine/browser does. :)
Tailcalls seem to be a major sticking point for ES6 support in most engines, for whatever reason.

authors: fatcerberus svaarala

repo: svaarala/duktape


text:
Duktape on Wii

Just wanted to let you know that Duktape works well on the Wii. I installed the DevkitPPC toolchain and configured Duktape with --architecture=powerpc32.
Compiling the resulting duktape.c with the DevkitPPC's default options, -g -O2 -Wall -DGEKKO -mrvl -mcpu=750 -meabi -mhard-float and running the provided examples just works.
Well done! 👏

Cool :)

authors: svaarala turbolent


text:
fix: move storybook from styling category to tools category

Storybook feels out-of-place in the styling category to me since it's not a CSS framework like the others and does so much more than just help you with styling.
From their homepage:
Storybook is a frontend workshop for building UI components and pages in isolation. Thousands of teams use it for UI development, testing, and documentation.

Good catch, don't know how it even ended there in the first place.

repo: svelte-add/svelte-add


text:
Missing "./package.json" export in "d3-scale" package (and others)

Describe the bug
After upgrading my LayerChart visualization component library to SvelteKit 1.0.0-next.202 which includes Vite 2.7, I now receive a bunch of the following errors on startup for many d3 packages (d3-scale, d3-shape, d3-array, d3-time)...
12:29:01 PM [vite] Internal server error: Missing "./package.json" export in "d3-scale" package
  Plugin: vite:import-analysis
  File: /home/projects/sveltekit-gw2gco/node_modules/layercake/src/settings/defaultScales.js
      at bail (/home/projects/sveltekit-gw2gco/node_modules/vite/dist/node/chunks/dep-7817f5b4.js:29925:8)
      at resolve (/home/projects/sveltekit-gw2gco/node_modules/vite/dist/node/chunks/dep-7817f5b4.js:29978:7)
      at resolveExports (/home/projects/sveltekit-gw2gco/node_modules/vite/dist/node/chunks/dep-7817f5b4.js:30625:12)
      at resolveDeepImport (/home/projects/sveltekit-gw2gco/node_modules/vite/dist/node/chunks/dep-7817f5b4.js:30641:26)
      at tryNodeResolve (/home/projects/sveltekit-gw2gco/node_modules/vite/dist/node/chunks/dep-7817f5b4.js:30424:20)
      at viteResolve (/home/projects/sveltekit-gw2gco/node_modules/vite/dist/node/chunks/dep-7817f5b4.js:67443:26)
      at Function.eval [as _resolveFilename] (/home/projects/sveltekit-gw2gco/node_modules/vite/dist/node/chunks/dep-7817f5b4.js:67459:20)
      at Function.requireRelative.resolve (/home/projects/sveltekit-gw2gco/node_modules/require-relative/index.js:30:17)
      at resolveViaPackageJsonSvelte (file:///home/projects/sveltekit-gw2gco/node_modules/@sveltejs/vite-plugin-svelte/dist/index.js:1160:55)
      at Context.resolveId (file:///home/projects/sveltekit-gw2gco/node_modules/@sveltejs/vite-plugin-svelte/dist/index.js:1491:26)

What's very perplexing is I didn't have this issue last night and even deployed multiple times via Vercel without any issues.
Based on the error, it seems like the proper fix would be to update all d3 packages (ex. d3-scale) and add ./package.json to exports, although I'm not sure I'm up for PR'ing 50+ packages and how long it would take to get reviewed / merged / released.  I also want to make sure its truly required as well :).
I'm also having trouble limiting the example below LayerChart (installing / importing either LayerCake (which LayerChart is built upon) or d3-scale does not throw the error.  LayerChart also uses my svelte-ux component library which has some d3 references so I don't know if it's a transitive issue.

While writing this I just realized svelte-ux has the same issue, and is similar that it worked last night and deployed to Vercel multiple times.
Reproduction
Here are 2 StackBlitz reproductions for each project:

svelte-ux
LayerChart

Logs
No response
System Info
System:
    OS: macOS 12.0.1
    CPU: (10) arm64 Apple M1 Max
    Memory: 263.47 MB / 32.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.13.0 - /usr/local/bin/node
    npm: 8.1.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 96.0.4664.110
    Edge: 96.0.1054.57
    Firefox: 94.0.2
    Safari: 15.1
  npmPackages:
    @sveltejs/adapter-static: ^1.0.0-next.22 => 1.0.0-next.22
    @sveltejs/kit: ^1.0.0-next.202 => 1.0.0-next.202
    svelte: ^3.44.3 => 3.44.3

Severity
blocking an upgrade
Additional Information
Related?

https://github.com/d3/d3-scale/issues/248#issuecomment-870732005
https://github.com/react-native-community/cli/issues/1168

Some related discussions with mhkeller in LayerCake (see referenced issues/PRs as well)

Interestingly... adding d3-array, d3-format, and d3-time to optimizeDeps to the svelte-ux example fixes it...
vite: {
  optimizeDeps: {
    include: [
      'd3-array',
      'd3-format',
      'd3-time',
    ],
  },
},

and adding d3-scale, d3-shape, d3-time, d3-array, and d3-format to the LayerChart example fixes it...
vite: {
  optimizeDeps: {
    include: [
      'd3-scale',
      'd3-shape',
      'd3-time',
      'd3-array',
      'd3-format'
    ],
  },
},

Each SvelteKit / Vite release I seem to always play the game of what to put in vite.optimizeDeps.include and/or vite.ssr.noExternal and what to take out.  When I was working on the update last night, I know I was getting TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".svelte" for ... that went away when I removed all the optimizeDeps, but maybe I should only not include the Svelte libraries (ex. LayerChart) and leave all the others there (especially d3).
Along with fixing the d3 issue, I know adding these always saves Vite from rediscovering dependencies, which sometimes takes a few passes on initial startup from a clean cache, or as you access a route with new dependencies.

d3-scale and friends should already be added to optimizeDeps.include by default, it's weird that that fixes it, but good to know. There have been similar reports recently about the Missing "./package.json" export in "d3-scale" package error happening and it seems to be an issue from Vite 2.7.

Some initial investigation. I'm able to reproduce them in the stackblitz repros, but when I clone locally and run it, it worked without errors (macos m1). I can find the offending code through the stack trace, but it should technically still be fine. Gonna deep dive this tomorrow.
Otherwise, the workaround vite-plugin-svelte can do is to use createRequire instead of require-relative, but I'm trying to see if it's a bug in Vite first.

In my project this appears to be fixed by upgrading to the just-released Vite 2.7.10. I'm guessing it was https://github.com/vitejs/vite/pull/6306.

I had the same problem with npm run dev – it started to work normally when I run build first..🙆♂

Ah that's really great news! This has been in my backlog for too long now. Closing this.

authors: bluwy dimfeld jarda-svoboda techniq

repo: sveltejs/kit


text:
Conditional loading of a script in svelte:head

Describe the bug
Hello,
Im trying to render a piece of html (in this case script tag) conditionally in head, depending on the resolution of if condition.
Thats how im doing it:
[slug].svelte
<svelte:head>
  {#if post.content.indexOf('lite-youtube') > -1}
    <script type="module" src="https://cdn.jsdelivr.net/npm/@justinribeiro/lite-youtube@1.3.1/lite-youtube.js"></script>
  {/if}
</svelte:head>

In my page content i've got:
content.md
<lite-youtube videoid="xyz"></lite-youtube>

Condition works fine, because if i test it with <title> tag it works perfectly good.
But when i go to the page, it loads the script always, no matter if the if is resolved to true or not.
Am i doing something wrong here?
Reproduction
[slug].svelte
<svelte:head>
  {#if post.content.indexOf('lite-youtube') > -1}
    <script type="module" src="https://cdn.jsdelivr.net/npm/@justinribeiro/lite-youtube@1.3.1/lite-youtube.js"></script>
  {/if}
</svelte:head>

content.md
<lite-youtube videoid="xyz"></lite-youtube>

Logs
No response
System Info
System:
    OS: macOS 12.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 74.70 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 14.18.1 - ~/.nvm/versions/node/v14.18.1/bin/node
    Yarn: 1.22.17 - ~/.nvm/versions/node/v14.18.1/bin/yarn
    npm: 8.1.4 - ~/.nvm/versions/node/v14.18.1/bin/npm
  npmPackages:
    @sveltejs/adapter-static: next => 1.0.0-next.26
    @sveltejs/kit: next => 1.0.0-next.229
    svelte: ^3.46.2 => 3.46.2
    vite: ^2.7.12 => 2.7.12

Severity
serious, but I can work around it
Additional Information
No response

It is a non issue. While preparing minimal reproductible repo i discovered it works as intended.


text:
[adapter-begin] request to collaborate w OpenJS Architect

Writing to see how the team feels about OpenJS Architect taking over the work of being an adapter. Currently Svelte has adapter-begin which I think does the trick but we'd love to help own this and make it completely seamless and not require any additional configuration. Right now we have a bit of an uncanny valley between static asset land and backend land and ideally this wouldn't be so trippy.
I have no idea what the process would be or look like just wanted to propose it here and gauge sentiment.

Oops, sorry yes, arc.codes (which is what Begin.com deploys)
More details: we recently exposed a plugins API which enables fully customizing the local dev env as well as generating the deployment cloudformation. My ideal here is the Svelte adapter is fast, seamless and adheres to cloud best practices. The current implementation works but I'm thinking we can extend it into more than just SSR and would love to help make that happen.

Thanks @brianleroux. We definitely want the Begin.com experience to be seamless for SvelteKit users, and if handing over the adapter is the best way to achieve that then we're all in favour.
The one wrinkle right now is that the adapter API isn't set in stone — for example a few of the things we're considering:

adapters take responsibility for bundling (or not bundling) Vite's output as ESM or CJS depending on the platform's requirements
the utils object passed to adapter.adapt (currently called builder for not-very-good historical reasons) adds a method for creating multiple functions, so that e.g. a single function is responsible for a specific route rather than the entire app
adapters gain the responsibility for using whatever API a platform provides for invalidating caches, so that non-changing pages can be cached for a long time but the cache can be invalidated once there's a new version
integration with things like platform-specific local dev envs (right now we have svelte-kit start for previewing prod builds locally, but it bypasses the adapter output)

So while we definitely want to encourage a healthy ecosystem of third party adapters, it does come with some caveats right now, and I don't want to make any assumptions about your appetite for dealing with them!

Is it a possible way forward that we just collaborate on it here (since all those required from begin already have access I believe), and then if we feel a burning need later on, we can extract it for a hand-over or similar?
I just foresee the potential for a void between the kit API and the Begin adapter widening if it detaches from the monorepo.
I think this is along the lines of what I had in mind for it anyway - I got it to 90% working but then I had some queries around serving static assets, and those couldn't be answered as other issues in kit at the time were getting in the way.
I think it should be in a place now that we can simply welcome PRs here to make it seamless.

Ok cool! I def do not care where the code lives, the goal here is to have a seamless and best in class experience. I know there was some grumbling about the difficulty in the interfaces we provides so I want to eliminate that friction while also hopefully helping the project create better outcomes for users (spoiler: any /* all GET routes won't be it).
Sounds like the kit is still baking so I'll keep an eye out for stability or whenever someone feels it is baked enough to build on please ping this thread so we can properly take it for a spin.

I feel like SvelteKit's getting to be fairly stable. We're about 80% of the way to 1.0. @brianleroux if you'd like to take a stab at fixing up the Begin adapter this is probably a reasonable time to start taking a look at it

had a quick go and found a number of issues;

the latest version published fails; but pinning to "@sveltejs/adapter-begin": "1.0.0-next.6", seems to work ok
the begin-adapter code is written as an export default module so the importing fails… fix by adding .default here:

const begin = require('@sveltejs/adapter-begin');

/** @type {import('@sveltejs/kit').Config} */
module.exports = {
	kit: {
		// hydrate the <div id="svelte"> element in src/app.html
		target: '#svelte',
		adapter: begin.default()
	}
};

this now builds/previews but compiling fails if the app.arc isn't precisely what's in the readme
if the build does succeed it creates a generated file in src/http/get-index and a generated file in src/shared … maybe we should make this work by just generating to .svelte folder and then generating the app.arc file with the correct pathing (?)

the latest version published fails; but pinning to "@sveltejs/adapter-begin": "1.0.0-next.6", seems to work ok

Yes, for all packages you have to use next and not latest. Unfortunately this one's a known pain point (https://github.com/sveltejs/kit/issues/686 and https://kit.svelte.dev/faq#adapters), but I guess it will fix itself when we release 1.0

the begin-adapter code is written as an export default module so the importing fails… fix by adding .default here:

That's different than how the other adapters work. It's probably better if we can make this be just begin() instead of begin.default() for consistency

if the build does succeed it creates a generated file in src/http/get-index and a generated file in src/shared … maybe we should make this work by just generating to .svelte folder and then generating the app.arc file with the correct pathing (?)

Sounds reasonable

const begin = require('@sveltejs/adapter-begin');

We're now creating an ES6 svelte.config.js by default instead of the CommongJS svelte.config.cjs, so in new projects we'll be using import to include the adapter (or at least we will be when the next version is released later today or later this week)

if the build does succeed it creates a generated file in src/http/get-index and a generated file in src/shared … maybe we should make this work by just generating to .svelte folder and then generating the app.arc file with the correct pathing (?)

Yeah - this is just me following the structure of a regular begin project, it sounds like it would be much better if it output to the regular output directory.
Another thing which I found to be a stumbling block when developing the adapter - begin seems to insist on the project being an independent github repository which begin controls the full lifecycle of. Is there a way for us to perhaps allow a svelte-kit project to run locally in the sandbox? it would need to be passed to the adapter, and then the resulting code run up in the sandbox I guess (including the render function).
Right now the adapter dev cycle includes copying the adapter locally into the test project directory (and unwiring pnpm's workspace directives), committing to the begin controlled github repository and then waiting for CI to deploy it. It's fairly time consuming.

Yeah we work locally; no need to involve Begin even…this stuff would all work with vanilla Architect and deploy straight to AWS. I don't really understand why the workflow would require being deployed ?

Hello friends,
I deeply appreciate the ongoing efforts to reach v1.0. 🙌  Any guesstimation about getting the begin adapter working? I'm having the same issue the folks below reported:
https://github.com/sveltejs/kit/issues/998
https://github.com/sveltejs/kit/issues/1532
I :+1: both issues. However I am posting here to resurface/revisist the initial request for OpenJS Architect to take over the adapter development. I would love to tame AWS with Begin and Sveltekit! @brianleroux 💪

Hey @brianleroux - regarding our previous discussion. I was personally championing the begin adapter but due to time constraints, it's not going to be possible for me to work on it at least for the next few months.
The adapter is relatively simple and just needs bringing up to date with the es6 work as far as I know. It had worked previously, but I couldn't get the static assets to work via architect config, so I was just serving them up via Lambda.
Therefore I think to get this working for the, seemingly growing crowd of people who want to use it, it's best if you take over maintenance, either by forking this or just creating your own adapter from scratch, and then just ping me if you need any help!

Super disappointed on how this turned out.

authors: Fghurayri Rich-Harris antony benmccann brianleroux


text:
allow symlinked assets

This might fix #4709
my monorepo setup uses symlinked static assets, and it worked great until https://github.com/sveltejs/kit/pull/5047 !
I believe that check for the casing was too restrictive, so I went ahead and made this PR addressing the issue. There's a test included in the basics app. The issue really only applies to dev, since the build copies symlink contents transparently.
Thanks in advance for the review 🙏
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[x] 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 pnpm changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

@anarchodin @mrkishi @Rich-Harris please have a look 🪟 🔗 ⬆

thank you! the correct fix looks a bit different — we can't just check the end of the path, because that won't work if the symlink source and target have different names. instead we're just checking that file exists in fs.readdirSync(path.dirname(file)), which is only true if the case is correct (and then doing that recursively)

authors: Rich-Harris gaarf


text:
pin @types/node to 16.18

this is intended to stop renovate from attempting to bump @types/node, since we want to use the lowest node version we currently support (which isn't quite possible — we support 16.14, but there's no corresponding @types/node for that).
i'm not sure if renovate works like that? but either way pinning probably makes sense

merged #9962, closing


text:
Follow field ordering of config when writing files

The field ordering when writing the files is completely different from the ordering set in config.yml. It would be friendlier to developers if files were written following the ordering set in configuration.
I know probably this means changing the internal data structure (from sets to arrays), but perhaps you may apply that ordering only when writing, to speed up the process...

It’s on my todo list. Netlify/Decap CMS has the same issue (particularly with JSON):

https://github.com/decaporg/decap-cms/issues/6759
https://github.com/decaporg/decap-cms/issues/6901

Just shipped v0.28.0 with the fix!

authors: josineto kyoshino

repo: sveltia/sveltia-cms


text:
Enable "Always Display in Console" If user is in Restricted Group

Is there an existing feature request for this?

[X] I have searched the existing issues

Is your feature related to a problem? Please describe.
When a users signs in to keycloak I would like to have them see all the applications they have access to without having to login to the site first and create a session.
Describe the solution you'd like
Hello,
I would like to know if it is possible to enable "Always Display in Console" option in the client settings if the user is a member of the restricted group?  If I am not able to do it with the keycloak-restrict-client-auth, can you recommend another approach, whether  programmatically or otherwise.
Much appreciated.
Describe alternatives you've considered
I thought about enabling "Always Display in Console" for all apps, customizing the accounts page using something like Javascript and hide the icon if the user is not in the restricted group.
Anything else?
No response

Hello @elmidwill ,
thanks for suggesting this enhancement. Unfortunately, it is currently not possible to with this extension and I do not see a way to implement this in a general way. To my knowledge, Keycloak does not provide an SPI or extension point to support this. Also it would not be trivial to detect whether a user is allowed to use a client or not, because that heavily depends on the authentication flow configuration.
Maybe in you special case it could be possible to build a custom solution by providing a REST APi endpoint. You may want to check the Developer Guide on how to do this.
You may want to implement some logic to lookup the authenticator config in your authentiction flow. The RestrictClientAuthConfig holds a property getAccessProviderId() the returns the id of the AccessProvider used by the authenticator. You may then lookup the AccessProvider:
AccessProvider accessProvider = keycloakSession.getProvider(AccessProvider.class, accessProviderId);
// Check if access to client is restricted
accessProvider.isRestricted(clientModel);

// Check if access for a user is permitted
accessProvider.isPermitted(clientModel, userModel);

Maybe you can work out something from there.
Regards
Sven-Torben

Sorry for the late reply, can you elaborate a little?

I am suggesting that you build a custom extension. You will have to customize the account console to filter out some of your clients. You may provide a REST API as part of your extensions which tries to determine to which clients a user has access. Provide that list of accessible clients to the account console (frontend) and show the clients to your users. You will have to decide which clients are accessible to the user and which are not. For this you can use the SPI as mentioned in my previous comment (https://github.com/sventorben/keycloak-restrict-client-auth/issues/101#issuecomment-1211240020)

authors: elmidwill sventorben


text:
DeprecationWarnings: phantomjs-prebuilt and request

phantomjs-prebuilt@2.1.16: this package is now deprecated
phantomjs-prebuilt > request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142`

Closing in favor of #254

authors: XhmikosR freakkiller

repo: svg-sprite/svg-sprite


text:
Package.exports types file specification missing

Describe the bug
Package.json .exports field is not correctly specified.
https://www.typescriptlang.org/docs/handbook/release-notes/typescript-4-7.html#packagejson-exports-imports-and-self-referencing notes that typescript will look relative to the import/require file for a .d.ts and ignore the types field when exports is used (I don't think these docs explicitly say this, but, the below error does).
SVGO does not specify the type file in its package.exports field:
"main": "./lib/svgo-node.js",
  "bin": "./bin/svgo.js",
  "types": "./lib/svgo.d.ts",
  "exports": {
    "require": "./dist/svgo-node.cjs",
    "default": "./lib/svgo-node.js"
  },

I think this means TS is looking at either ./dist/svgo-node.d.ts or ./lib/svgo-node.d.ts, and the following error seems to hint that TS can find the types but it really wants the package.json specified properly:
  λ  npx tsc --noEmit
src/filename.ts:5:26 - error TS7016: Could not find a declaration file for module 'svgo'. '/Users/.../node_modules/svgo/lib/svgo-node.js' implicitly has an 'any' type.
  There are types at '/Users/..../node_modules/svgo/lib/svgo.d.ts', but this result could not be resolved when respecting package.json "exports". The 'svgo' library may need to update its package.json or typings.

5 import { optimize } from 'svgo'
                           ~~~~~~

Found 1 error in src/filename.ts:5

I expect this is related to my own module specification and other typescript config:
{
  "$schema": "https://json.schemastore.org/tsconfig",
  "display": "Client",
  "compilerOptions": {
    "esModuleInterop": true,
    "skipLibCheck": true,
    "target": "es2022",
    "allowJs": true,
    "resolveJsonModule": true,
    "moduleDetection": "force",
    "isolatedModules": true,
    "verbatimModuleSyntax": false,

    "strict": true,
    "noUncheckedIndexedAccess": false,
    "noImplicitOverride": true,

    "composite": false,
    "declaration": true,
    "declarationMap": true,
    "sourceMap": true,

    "module": "preserve",
    "noEmit": true,

    "lib": ["es2022", "dom", "dom.iterable"],
    "jsx": "react-jsx"
  },
  "exclude": ["node_modules"]
}

Note that this the same config Matt Pocock uses and is documented here.
I'm sure many configurations of TS maybe will mask this bug, but, this setup seems pretty barebones and the linked definition for what exports should look like is fairly well defined.

TS version: 5.4.5.
Node version 20.12.2.
SVGO version: 3.3.0..

To Reproduce
Run tsc across a file that imports from 'svgo'.
Its quite possible that different specifications for TS mask or otherwise do not exhibit the error.
Expected behavior
TS should be able to find the types.
It does mention that using 1 type file across ESM/CJS could potentially lead to problems.
Desktop (please complete the following information):

TS version: 5.4.5.
Node version 20.12.2.
SVGO version: 3.3.0..

https://github.com/svg/svgo/pull/1984/files#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519
#1984 will fix this issue.

Sorry for the headache! Indeed, we've merged that PR and made a release now, so it should be resolved in v3.3.1.
Thanks for reporting the issue and providing insight meanwhile.

authors: SethFalco mattstyles

repo: svg/svgo


text:
Text toPath

It seems that text elements cannot be converted to path yet. Do you plan to add this feature ?

sample is not defined????

@wm2zfei could you explain your question a bit more? And maybe open a new issue since this one is more than tree years old...

For converting text to Path you can use https://github.com/shrhdk/text-to-svg

or fontkit or opentype...

Yes, text-to-svg is based on opentype :)

authors: Fuzzyma hassenc kuzvac wm2zfei wout


text:
Making a simple get request and setting the response to payload

Hello,
I'm hitting a bunch of road blocks trying to set a response from a axios.get request to action payload. The main issue is that since the response is a promise it takes the entire promise as the payload and there is no way to set the response within the promise as the payload.  Any advice on how to use this middleware to rectify the issue I am having?
I greatly appreciate any direction given and I thank you in advance.
Peter

I don't understand your issue.  Can you provide an example of your action creator and the actions it dispatches?

Closing as we have not heard back from the OP.

authors: nmaves ptums

repo: svrcekmichal/redux-axios-middleware


text:
nxppy.SelectError: No Card detected: 4084

Hi there,
I'm having trouble getting a simple test python app to run
on a Raspberry Pi 2 Model B running Raspbian jessie:
import nxppy

mifare = nxppy.Mifare()
uid = mifare.select()
print(uid)

I keep getting an Error at:
uid = mifare.select()
which says:
nxppy.SelectError: No Card detected: 4084
whether or not a tag is placed on the nxp-module.
After failing quite a few times I tried reading the tag with the explore-nfc basic tool and that worked...

Can you try it in a loop just so you can be sure the card is within the field?
import nxppy
import time

mifare = nxppy.Mifare()

while True:
    try:
        uid = mifare.select()
        print(uid)
    except:
        print("No card found")
        time.sleep(1)

Also, what version of nxppy do you have installed?  In older versions, you could not use the explore-nfc basic tool and nxppy at the same time.  Make sure that the explore-nfc daemon is not running before trying to run the python version.

Thank you very much for your answer!
Unfortunately I already tried it both ways (with and without the loop).
I installed nxppy via
sudo pip install nxppy
and it is version 1.4.3
Also, I did try to run it with and without the explore-nfc deamon being installed.

I forgot to ask, is this on Raspbian?  What version?  I'll see if I can
reproduce the issue.
On Wed, Jul 27, 2016 at 1:50 AM RasPinator notifications@github.com wrote:

Thank you very much for your answer!
Unfortunately I already tried it both ways (with and without the loop).
I installed nxppy via
sudo pip install nxppy
and it is version 1.4.3
Also, I did try to run it with and without the explore-nfc deamon being
installed.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/svvitale/nxppy/issues/42#issuecomment-235512371, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAIXyjMrRAktuhALHTf-Gu3z3iqFjKvDks5qZw3agaJpZM4JVGvL
.

It's Raspbian Jessie Version May 2016

I've seen some rumblings about that release having SPI issues.  Do you have
an older version handy to try?  I'll try to look at this myself, but my
travel schedule is currently a little out of hand.
On Wed, Jul 27, 2016 at 8:59 AM RasPinator notifications@github.com wrote:

It's Raspbian Jessie Version May 2016
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/svvitale/nxppy/issues/42#issuecomment-235612853, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAIXykQMLiuNZikw5EZnWDF0RiA-JNCQks5qZ3JZgaJpZM4JVGvL
.

Thank you very much!!!
It works with an older Version (Linux raspberrypi 4.1.13-v7+ #826 SMP PREEMPT Fri Nov 13 20:19:03 GMT 2015 armv7l GNU/Linux)

Glad to hear!  I'll leave this ticket open until there's a new release to test against.  It's possible something was purposely changed and inadvertently broke nxppy, but I'm willing to wait 1 release to verify.

I reinstalled the latest Raspian today and successfully tested nxppy on both Python 2.7 and 3.4.  The only change needed was to enable SPI.  Not sure what the original problem was, but glad to hear things are working, @RasPinator.  Closing this ticket.

authors: RasPinator svvitale

repo: svvitale/nxppy


text:
Unable to add example value for body

Version:  swagger core 2.0.8, (openapi 3)
I am following the Swagger 2.0 Annotation docs , but I am unable to view example value for body in swagger UI.
public Response updateUserInfo(@RequestBody(description = "", required = true, content = @Content(mediaType = "application/json")}) final String userInfo)
Is there any equivalent of @ApiImplicitParams or @ExampleProperty (from swagger 1.x) for body in swagger 2.x.
Though the above doc states an example for @ApiResponse :
examples = { @ExampleObject(name = "boo", value = "example",summary = "example of boo", externalValue = "example of external value") }
but this is not working for body.
I have also tried this but the example does not show up in swagge UI:
public Response updateUserInfo(@Parameter(examples = {@ExampleObject(name = "userInfo", value = "some example")})) final String userInfo)

This works for me in swagger core 2.0.6:
 public MyResponse myMethod(@RequestBody(description = "test body",
                content = { @Content(mediaType = "application/json",
                     examples = @ExampleObject(
                         name = "test",
                         summary = "test example",
                         value = "{ \"key\" : \"value\"}"),
                schema = @Schema(example = "{ \"key\" : \"value\"}")) }) MyRequest request)

generates the following output in openapi.json:
requestBody": {
    "description": "test body",
    "content": {
        "application/json": {
            "schema": {
                "type": "string",
                "example": {
                    "key": "value"
                }
            },
           "examples": {
               "test": {
                   "summary": "test example",
                   "description": "test",
                   "value": {
                         "key": "value"
                    }
               }
           }
       }
   }
}

repo: swagger-api/swagger-core


text:
docs: Updated jokes.json

Added ten new jokes to jokes.json
They are really funny

issue no #904

repo: swapagarwal/JARVIS-on-Messenger


text:
Add xkcd module to display most recent xkcd comic

XKCD comics are quite popular among programmers so I added a small module which displays the latest XKCD to the user. The api is found here and is provided by the creator of the comic himself.
Example queries:
Show me the latest xkcd
current xkcd
show me an XKCD
Obviously I was unable to test it properly because there is no xkcd intent in the AI. However the module is small enough that I believe it should be working. I think I have followed all the Contributing guidelines but please let me know if I missed something.

@swapagarwal Could you please add some training in wit.ai for this?

@conormag94 Awesome idea for a module! 😄

Thanks @conormag94! 👍


text:
Add a Quiz Game

Different categories of quizzes will be there. Each quiz will have 10 questions and if you win there will be a great animation to congratulate you.

Hello @swapnilsparsh. I would like to work on this issue under GSSOC'22. Can you assign this to me?


text:
Appname camelCase with numbers

I'm building a plugin and brand called "bed66" but wpack.io fails to start because plugin is not considered in camelcase.
Any advice or guidance?

✖ could not start server.
please review the following errors
❯  appName must be in camelCase in project config.
❯  Currently bed66, try bed66

Hi,
This is a restriction in naming things. Simply try bedSixSix or bedSixtySix

Yes, that is what I did to get around the restriction.  Thank you.

authors: hardeepkhehra swashata

repo: swashata/wp-webpack-script


text:
Only one CSS-wide keywords can exist in the property value

Describe the bug
Invalid value
Should throw an error, but it doesn't now.
.Invalid {
	animation-name: default, two;
	animation-name: one, initial;
	animation-name: one, inherit;
	animation-name: one, unset;
	animation-name: revert, three;
	animation-name: revert-layer, four;
	animation-name: "foo", unset;
	animation-name: unset, "foo";
}

Valid value
.Valid {
	animation-name: none, none;
	animation-name: one, none;
	animation-name: "foo", none;
	animation-name: none, "foo";
}

Theoretically, any property that supports multiple values, except for the animation-name property, needs to be handled this way. For details, see: https://github.com/web-platform-tests/wpt/commit/4f82d323fdb6dd39c1370bd61c7252667994d6bc
Input code
No response
Config
No response
Playground link
No response
Expected behavior
swc should throw an error.
Actual behavior
No response
Version
0.125.5
Additional context
No response

This task is more complex, currently we use genetic algorithm to parse (i.e. we are parsing most of properties using Ident in this case, only at-rules and selectors use specific algorithm), regarding to CSS lexer/parser it is valid, but in the context of the property, it is invalid, but yes, it is panned, but I am afraid it will be not soon (week/two weeks), there are more priorities tasks

Yes, this is not a high priority, and normally, no one would write CSS this way.

authors: alexander-akait yisibl

repo: swc-project/swc


text:
Fix macos 10.13 compatible problem

Close https://github.com/swc-project/swc/issues/1039

Thanks!


text:
fix(es/compat): use return statements for method and setter decorator

Description:
This aligns with other implementations such as TypeScript's and correctly implements the currently proposed behavior.
Related issue (if exists):
https://github.com/swc-project/swc/issues/8015

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

authors: CLAassistant jrandolf


text:
[6.0.2] Fix compiling test runners for Android by using the full overlay

Explanation: Compiling test runners with import Bionic worked till July, then the compiler started requiring the larger import Android overlay.
Scope: Only affects Android
Issue: None
Original PR: #8018
Risk: None
Testing: I built and ran the SwiftPM tests natively on Android with this patch.
Reviewer: @bnbarham
Since this issue broke cross-compiling all packages' tests for Android and presents no risk for other platforms, I'd like to get it in quickly for the next patch release.

@swift-ci please test

Passed CI, ready for merge.

Passed CI, ready for merge.

Thanks for staying on top of them :)

Thanks for the quick review. 😄

authors: bnbarham finagolfin

repo: swiftlang/swift-package-manager


text:
Strip \?\ prefix from path generated by resolveSymlink

This aligns the implementation of resolveSymlinks with that of Foundation.String._resolvingSymlinksInPath, which received this canonicalization fix in https://github.com/swiftlang/swift-foundation/pull/639.

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test Windows

@swift-ci Please test Windows

macOS CI failure is unrelated. This change only affects Windows. macOS CI is failing because this is the only repo that build SourceKit-LSP using a 5.9 host compiler, but SourceKit-LSP requires 5.10 to build successfully. We didn’t hit this before because this repo hasn’t seen any changes in the last 2 months, which is when SourceKit-LSP started requiring Swift 5.10.

repo: swiftlang/swift-tools-support-core


text:
In C++ Interop mode, containers with move-only types cannot be imported

Description
Consider the following C++ code:
class Cat {
public:
    Cat() {}
    Cat(const Cat & other) = delete;
    Cat(Cat && other) = default;
    ~Cat() {}
    Cat& operator=(const Cat & other) = delete;
    Cat& operator=(Cat && other) noexcept = default;
};

class House {
public:
    House() {}
    House(const House & other) = delete;
    House(House && other) = default;
    ~House() {}
    House& operator=(const House & other) = delete;
    House& operator=(House && other) noexcept = default;

    std::list<Cat> cats;
};

And then, it is imported into Swift like this:
struct Demo: ~Copyable {
    var house: House?
}

However, the following compilation error occurs:
/Users/omochi/github/omochi/swift-bug-cxx-moveonly-container/Sources/CxxCats/include/CxxCat.hpp:3:2: note: in module 'std_list' imported from /Users/omochi/github/omochi/swift-bug-cxx-moveonly-container/Sources/CxxCats/include/CxxCat.hpp:3:
#include <list>
 ^
/Applications/Xcode16.2-beta.3.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX15.2.sdk/usr/include/c++/v1/list:217:2: note: in module 'std_private_memory_allocator' imported from /Applications/Xcode16.2-beta.3.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX15.2.sdk/usr/include/c++/v1/list:217:
#include <__memory/allocator.h>
 ^
/Applications/Xcode16.2-beta.3.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX15.2.sdk/usr/include/c++/v1/__memory/allocator.h:173:24: error: call to deleted constructor of 'Cat'
    ::new ((void*)__p) _Up(std::forward<_Args>(__args)...);
                       ^
/Applications/Xcode16.2-beta.3.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX15.2.sdk/usr/include/c++/v1/__memory/allocator.h:172:58: note: in instantiation of function template specialization 'std::allocator<std::__list_node<Cat, void *>>::construct<Cat, const Cat &>' requested here
  _LIBCPP_DEPRECATED_IN_CXX17 _LIBCPP_HIDE_FROM_ABI void construct(_Up* __p, _Args&&... __args) {
                                                         ^
/Users/omochi/github/omochi/swift-bug-cxx-moveonly-container/Sources/CxxCats/include/CxxCat.hpp:8:5: note: 'Cat' has been explicitly marked deleted here
    Cat(const Cat & other) = delete;
    ^

Reproduction
I have created a reproducible project.
URL: https://github.com/omochi/swift-bug-cxx-moveonly-container
You can verify it using the following commands:
git clone https://github.com/omochi/swift-bug-cxx-moveonly-container
cd swift-bug-cxx-moveonly-container
swift build

Expected behavior
The build succeeds.
Environment
Tested with Swift in Xcode 16.2 beta 3 and the December 3rd version of the Swift 6.1 snapshot.
swift-driver version: 1.115.1 Apple Swift version 6.0.3 (swiftlang-6.0.3.1.8 clang-1600.0.30.1)
Target: arm64-apple-macosx15.0

Apple Swift version 6.1-dev (LLVM 3a45ba43180a40a, Swift 380c92b03a1cfb2)
Target: arm64-apple-macosx15.0

To the best of my knowledge, the issue has been occurring since the November 14th main snapshot.
Additional information
No response

This issue might be related.
https://github.com/swiftlang/swift/issues/73037

repo: swiftlang/swift


text:
[Frontend/AST] Add -swift-compiler-version option to frontend/modules

This option is going to be used to indicate what compiler was used
to build swift interface/module which is required for SE-0438.

@swift-ci please test

@swift-ci please test Linux platform

@swift-ci please test Windows platform

@swift-ci please test

@swift-ci please test


text:
Add action to the command palette to re-index a project

https://github.com/swiftlang/sourcekit-lsp/pull/1507 added a workspace/triggerReindex request to SourceKit-LSP, which re-indexes a project in SourceKit-LSP if background indexing is enabled.
The request is not intended to be something that users invoke regularly but it is useful as a workaround should SourceKit-LSP’s index up-to-date tracker get out of sync with the project state (which we know can happen in some situations like https://github.com/apple/sourcekit-lsp/issues/1264). The workflow should thus be as follow:

The command palette has a SourceKit-LSP: Re-index project item
When it is selected, the workspace/triggerReindex is sent to the SourceKit-LSP server.
If a methodNotFound error (error code -32601) is returned, a custom error message should be displayed in VS Code that says that says: The installed version of SourceKit-LSP does not support background indexing. If any other error is returned, that error should be displayed as a popup.
If the request succeeds, a popup should be displayed saying something like: Re-indexing a project should never be necessary and indicates a bug in SourceKit-LSP. Please file an issue at https://github.com/swiftlang/sourcekit-lsp/issues/new describing which symbol was out-of-date and how you got into the state. If the user chooses to file an issue, we should enter the workflow to create a diagnose bundle.

Implemented by https://github.com/swiftlang/vscode-swift/pull/964

repo: swiftlang/vscode-swift


text:
Fix for hotmail's RFC5322 bounces when reasonably complicated sender nam...

...es are used.

Thanks for the PR. As announced some time ago, Swiftmailer is not maintained anymore.
Symfony Mailer is the next evolution of Swiftmailer.
It provides the same features with support for modern PHP code and support for third-party providers.

authors: bjdelange fabpot

repo: swiftmailer/swiftmailer


text:
Lack of use of setuid'd fusermount means programs/clients must run as root

Currently, the mount() syscall is made directly from the process invoking fission.NewVolume().
As such, this means the caller to fission.NewVolume() must themselves have root privileges.
Not only that, but the mounted volume would then also only be accessible by a root user.
Bazil FUSE, go-fuse, jacobsa/fuse, and libfuse.a itself all utilize a setuid'd program fusermount to perform the mount... invoked via fork()'ing the calling process and exec()'ing fusermount... passing the file descriptors between processes.
As the goal of package fission is definitely not to enable non-root users to make a file system, this issue is not strictly required. The goal of package fission is, rather, to enable writing a file system in user mode (as opposed to in the Linux Kernel). That said, such a capability would be handy... and, certainly, the clients of the mounted file system should not themselves have to be root.

Resolved (by means of leveraging fusermount of course) as of Release 1.1.1

repo: swiftstack/fission


text:
Design breaking changes

Should we re-evaluate the thing we consider as breaking changes?
I had some feedback concerning the new design of the disabled input and input validation.

New disabled styles were not technically breaking, but visually. Should this have been a breaking change?
The information was there, but projects are not happy with the change
Versioning rules are just about code, not about design. Create the possibility to add a major version even if the code is not breaking
Projects are not happy with the current disabled styles (strikethrough)
We changed disabled styles for accessibility reasons so it's not possible to revert to a non-accessible state, maybe people are also using it wrong
Disabled elements are not accessible either way
Disabled buttons were implemented a little wrong, so the design change broke their page. A minor change resulted in a lot of work. With a major change, expectation would have been different
We could not predict that this would break with incorrect usage
Depends on how often we do design breaking changes (should not be too often)
Inform Design Team about pending major changes so design changes can be implemented as well

Actions

Take major design changes into consideration when deciding for major release versions

authors: alizedebray gfellerph

repo: swisspost/design-system


text:
Listener 事件管理如同鸡肋 只是通知过程  却获取不到事件对应的名称和结果

Q
A

Bug report?
yes

Feature request?
no

Swoft version
1.0.5

Swoole version
2.2.0

PHP version
7.2.1

Runtime environment
Mac

Details

监听器  返回结果获取不到，任务名称获取不到，任务参数的参数获取不到，这个事情监听器可以做什么？

<?php
/**
 * This file is part of Swoft.
 *
 * @link https://swoft.org
 * @document https://doc.swoft.org
 * @contact group@swoft.org
 * @license https://github.com/swoft-cloud/swoft/blob/master/LICENSE
 */

namespace App\Listener;

use Swoft\Bean\Annotation\Listener;
use Swoft\Event\EventHandlerInterface;
use Swoft\Event\EventInterface;
use Swoft\Task\Event\TaskEvent;
/**
 * 任务处理之后 监听处理器
 *
 * @Listener(TaskEvent::AFTER_TASK)
 */
class AfterTask implements EventHandlerInterface
{
    /**
     * @param \Swoft\Event\EventInterface $event
     */
    public function handle(EventInterface $event)
    {
        var_dump($event->getName());
        var_dump($event->getParams());
        var_dump($event->getTarget());
        var_dump($event);
        //任务返回结果获取不到，任务名称获取不到，任务参数的参数获取不到，这个事情监听器可以做什么？
//        var_dump('任务处理之后', $event->getTarget());
    }
}

建议增加 onFinish 回调的 Event 对象增加 $worker_id 和 $task_id。
Swoole 本身的回调 function onTask(swoole_server $serv, int $task_id, int $src_worker_id, mixed $data); 是有的，这里没有让人感觉很奇怪。
另外就是，啥时候能支持在 Swoole\Server->task() 里增加 finish 回调？这样就不需要去 TaskEvent::FINISH_TASK 回调里对各种任务做分流处理了。

authors: CodeMonkeyLuffy louvxiao

repo: swoft-cloud/swoft


text:
add MidweekMeeting pdf file

add MidweekMeeting pdf file

Summary by CodeRabbit

New Features

Introduced a new MidweekMeeting component for generating PDF documents of midweek meeting agendas, complete with detailed sections for various meeting parts.
Added a MidweekMeeting component to the PDF preview replacing the previous WeekendMeeting.

Enhancements

Expanded PDF rendering capabilities with new components for headers, meeting items, titles, songs, tasks, and times, all styled for clarity and visual appeal.

Bug Fixes

Downgraded the firebase package to improve compatibility and stability.

Task linked: CU-86bx53yjk Midweek meeting – Normal

@IlkaA1: there was requested changes to the layout of the midweek meeting template lately. Please work with @ux-git to know the latest update. Other than that, great job! 🫡


text:
Students should be happy they completed the introductory exercise and fill out a questionaire

Scenario
Given an eager student
When they have completed the Ruby on Rails exercise
Then they should celebrate!
Thanks for taking part in the exercise! We would appreciate your feedback to continue to improve in the future.
Please fill out this survey to help the teaching team improve this exercise
Error

Got Students: 'Done!'

43 exercise tests have passed. There are 44 in total. You will solve multiple at once towards the end.

Sorry, it's not working for me yet:
Scenario
Given an eager student
When they have completed the Ruby on Rails exercise
Then they should celebrate!
Thanks for taking part in the exercise! We would appreciate your feedback to continue to improve in the future.
Please fill out this survey to help the teaching team improve this exercise
Error

Got Students: 'Done!'

If you have problems solving this task, please don't hesitate to contact the teaching team!


text:
🛑 BestQA_GO is down

In 77ee687, BestQA_GO (https://www.bestqa.net/go/bestqa_dev/up) was down:

HTTP code: 0
Response time: 0 ms

Resolved: BestQA_GO is back up in e8c43b8.

repo: swuecho/upptime


text:
Cannot find package 'mdsvex'

Just trying things out, but I failed, you might help me?
I cloned the repo and tried to deploy on netlify.
First error: "vite": "^5.0.3" can't run on node 16. (I guess that this bump introduced it: https://github.com/swyxio/swyxkit/pull/212)
So I changed https://github.com/swyxio/swyxkit/blob/main/netlify.toml#L15 to 18
Now the build is succeeding on netlify, but when I go to the site, I have:
This function has crashed
An unhandled error in the function code triggered the following message:

Error - Cannot find package 'mdsvex' imported from /var/task/.netlify/functions-internal/sveltekit-render.mjs

Stack trace
Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'mdsvex' imported from /var/task/.netlify/functions-internal/sveltekit-render.mjs
    at new NodeError (node:internal/errors:387:5)
    at packageResolve (node:internal/modules/esm/resolve:852:9)
    at moduleResolve (node:internal/modules/esm/resolve:901:20)
    at defaultResolve (node:internal/modules/esm/resolve:1115:11)
    at nextResolve (node:internal/modules/esm/loader:163:28)
    at ESMLoader.resolve (node:internal/modules/esm/loader:841:30)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:76:40)
    at link (node:internal/modules/esm/module_job:75:36)

I tried to go back to the previous versions & node 16, but it's still the same.
I'm doing something wrong somewhere, but where?
Thx for your help

hey @jycouet  - no idea whats wrong here unfortunately. this main branch deploys straight to netlify and you can see it works fine there. maybe by browsing the logs u can find a difference? https://app.netlify.com/sites/swyxkit/deploys/656c2f4502018f0008307e27

authors: jycouet swyxio

repo: swyxio/swyxkit


text:
Can I use the Agora AgoraRtcEngine_iOS Pod directly

Hi. Can I put this in my Podfile instead of installing the pod through node_modules?
I've tried it but I get some errors. Namely
Use of undeclared identifier 'AgoraConnectionChanged....
Any ideas? Thanks.

Yes you can, but i think it is bad practice, because you need to confirm which version is the react-native-agora new released dependency. Probably you could provide more details here that I would help you to fix it.

Cool, thanks @Matrixbirds , looks like I was able to get it on second try :)

authors: Jonovono Matrixbirds

repo: syanbo/react-native-agora


text:
🛑 AZ Brick Frames is down

In 1936104, AZ Brick Frames (https://azbrickframes.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: AZ Brick Frames is back up in 0255d02 after 14 minutes.

repo: symapex/upsite


text:
🛑 Superior Surface is down

In 9b1f871, Superior Surface (https://superior-surface.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Superior Surface is back up in 474483b after 47 minutes.


text:
🛑 Prism Carpet Cleaning is down

In 87554e2, Prism Carpet Cleaning (https://prismcarpetcleaningtx.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Prism Carpet Cleaning is back up in 913d2a3 after 11 minutes.


text:
🛑 Absolute Landscape Solutions is down

In 92f352d, Absolute Landscape Solutions (https://absolutelandscapesolutions.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Absolute Landscape Solutions is back up in 185d3c1 after 19 minutes.


text:
🛑 Global Translation is down

In 36eb5d6, Global Translation (https://globaltranslationsrvs.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Global Translation is back up in db14f94 after 47 minutes.


text:
🛑 Dragues Well Repair is down

In d4240a3, Dragues Well Repair (https://dragueswellrepair.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Dragues Well Repair is back up in 0b7d01a after 1 hour, 29 minutes.


text:
🛑 Hammond Floors is down

In 0ceb614, Hammond Floors (https://hammondfloors.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Hammond Floors is back up in 30954a3 after 20 minutes.


text:
🛑 Fresh Auto is down

In 3bca304, Fresh Auto (https://fresh-auto.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Fresh Auto is back up in 5817869 after 1 hour, 28 minutes.


text:
🛑 Clean Wise is down

In 08e2675, Clean Wise (https://cleanwisenv.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Clean Wise is back up in 6d5aefb after 48 minutes.


text:
🛑 Cedar Built Floors is down

In 93d86f1, Cedar Built Floors (https://cedarbuiltfloors.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Cedar Built Floors is back up in 20dbd2c after 30 minutes.


text:
🛑 Dragues Well Repair is down

In 3881a78, Dragues Well Repair (https://dragueswellrepair.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Dragues Well Repair is back up in 9f57af7 after 56 minutes.


text:
🛑 Scrubit Clean is down

In d581b32, Scrubit Clean (https://scrubit-clean.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Scrubit Clean is back up in bec0de7.


text:
🛑 Mr Drywall TX is down

In 945d77d, Mr Drywall TX (https://mrdrywalltx.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Mr Drywall TX is back up in 0376213.


text:
🛑 Decor and Scape is down

In 7338342, Decor and Scape (https://decorandscape.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Decor and Scape is back up in 671b91a.


text:
🛑 Pestero Bug Fortworth is down

In 6dea368, Pestero Bug Fortworth (https://pesterobugfortworth.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Pestero Bug Fortworth is back up in b5055d0 after 26 minutes.


text:
🛑 Cleanaholic is down

In 1750401, Cleanaholic (https://cleanaholictn.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Cleanaholic is back up in ad16148 after 25 minutes.


text:
🛑 Arborcare Ohio is down

In e057ea9, Arborcare Ohio (https://arborcareohio.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Arborcare Ohio is back up in d968a70 after 20 minutes.


text:
🛑 Scrub Clean Seattle is down

In cdf2aa0, Scrub Clean Seattle (https://scrubcleanseattle.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Scrub Clean Seattle is back up in 9ee9185 after 10 minutes.


text:
🛑 Cleanaholic is down

In 772152a, Cleanaholic (https://cleanaholictn.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Cleanaholic is back up in 436ef5e.


text:
🛑 Well Repairman is down

In 8139e71, Well Repairman (https://wellrepairman.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Well Repairman is back up in fe191de after 1 hour, 8 minutes.


text:
🛑 Get Fence Lab is down

In e311a14, Get Fence Lab (https://getfencelab.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Get Fence Lab is back up in 5bdc1f8 after 54 minutes.


text:
🛑 Boosted Audio is down

In fe87074, Boosted Audio (https://boostedaudioor.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Boosted Audio is back up in 0955893.


text:
🛑 Hard Stack Pro is down

In d795f45, Hard Stack Pro (https://hardstackpro.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Hard Stack Pro is back up in f2818a0 after 48 minutes.


text:
Delete duplicate sensio_framework_extra config

It exists already as https://github.com/symfony/demo/blob/bbe5180a8c3b6886ea59227df83de59a4573e586/config/packages/sensio_framework_extra.yaml

Tobias, thanks a lot for this and all the other fixes you sent for the Symfony Demo app.

authors: Tobion javiereguiluz

repo: symfony/demo


text:
Unexpected "javascripts" tag

Hi all, I don't know why the AsseticBundle have been removed and I think that my problem is due to this action
After the last updates I have this error:
request.CRITICAL: Uncaught PHP Exception Twig_Error_Syntax: "Unexpected "javascripts" tag
(expecting closing tag for the "block" tag defined near line 8) in "::template_parent.html.twig"
at line 8." at /var/www/myfolder/vendor/twig/twig/lib/Twig/Parser.php
line 167 {"exception":"[object] (Twig_Error_Syntax(code: 0):
Unexpected \"javascripts\" tag (expecting closing tag for the \"block\" tag defined near line 8)
in \"::template_parent.html.twig\" at line 8.
at /var/www/myfolder/vendor/twig/twig/lib/Twig/Parser.php:167)"} []

And the file "template_parent.html.twig" contain:
 {% block javascripts %}
    {% javascripts
           'bundles/securinetsfrontoffice/js/jquery-1.9.1.js'
           'bundles/securinetsfrontoffice/js/jquery-ui-1.10.3.custom.js'
    %}
    <script type="text/javascript" src="{{ asset_url }}"></script>
    <script language="javascript">
        //some code
     </script>
    {% endjavascripts %}
 {% endblock %}

So I removed the {% javascripts %} {% endjavascripts %} like this
 {% block javascripts %}
    <script type="text/javascript" src="../bundles/securinetsfrontoffice/js/jquery-1.9.1.js"></script>
    <script type="text/javascript" src="../bundles/securinetsfrontoffice/js/jquery-ui-1.10.3.custom.js"></script>
    <script language="javascript">
        //some code
     </script>
 {% endblock %}

And the code worked
So what if my files are not in the /web folder ? (Example: /app/Ressources/public/)
I haven't the right to leave the /web folder

You can add the AsseticBundle manually by running composer require symfony/assetic-bundle or adding it back to the require section in your composer.json file.
For the second part, you may look at the asset function documentation in the twig extension docs, or how to create and manage assets in the templating docs.

Thanks Pierstoval,
I hope there will be no problem by adding the AsseticBundle or a security flaw related to AsseticBunde

There will not, Assetic and its bundle are still supported, they're just not bundled by default to allow users to use different tools to manage assets and frontend tools (like gulp, grunt, etc.)

I see
Thank you again

authors: Pierstoval mohamedaymenkarmous

repo: symfony/symfony-standard


text:
[Site] Using raw data attributes

raw data attributes is a preferred way. The stimulus_* functions will then have to be replaced on https://ux.symfony.com/.
Reference: https://github.com/symfony/ux/pull/1336
What do you think ?

I'll do it if you want. But not this week please :)
I'm gonna make some changes on those files and i'd like to avoid handling conflicts on switch/rebase 😅

Yes @smnandre , no problem :)

authors: seb-jean smnandre

repo: symfony/ux


text:
[Live Components]Docs for Data Binding are insufficient

Attempts to reproduce the behavior demonstrated at Data Binding fail. The docs appear to be insufficient. For example,

    <input
        type="number"
        value="{{ max }}"
        data-model="max"
    >

    Generating a number between 9 and {{ max }}
    {{ this.randomNumber }}

lacks <form>...</form> and <button>...</button>. But even when added the value of max always reverts to the value in .../Components/RandomNumberComponent. Surely something else is missing.

Hey @truckee, are you manually refreshing the page? Does your $max property have #[LiveProp(writable: true)]? The  value should be changing as you type into the input.

Hiya.
... are you manually refreshing the page? If you mean after updating the source code, yes.
Does your $max property have #[LiveProp(writable: true)]? Yes.
Puzzle pieces:
#[AsLiveComponent('random_number')]
class RandomNumberComponent
{
    use DefaultActionTrait;

    #[LiveProp(writable: true)]
    public int $max = 1000;

    public function getRandomNumber(): int
    {
        return rand(0, $this->max);
    }
}

and

    <form>
        <input
            type="number"
            value="{{ max }}"
            data-model="max"
            >
        <button data-action="live#$render">Generate a new number!</button>
    </form>
    {{ this.randomNumber }}

and
{{ component('random_number') }}

I'm not terribly proficient with the frontend part of live components. @weaverryan, any ideas?

I misunderstood the intended behavior. I thought that changing the value of max at input would cause the value of max to change for the next Generate a new number. That is not what I observed. Only today did I note what must be the intended behavior: when the input value of max is changed a new random number within the revised bounds immediately appears. This behavior is substantially more useful.
Apologies for my misunderstanding.

No worries, glad you got it figured out! Be sure to let us know if you have any suggestion on how the docs could be more clear.

authors: kbond truckee