text:
Add soramitsu/scale-codec-js-library

Proposal description
There is a list of SCALE codec implementations. I propose to append soramitsu/scale-codec-js-library into it. This project has a core library and a compiler for it. The whole stack is used in Iroha 2 JavaScript SDK. It is well-tested, but it needs more real-life usage experience to become better. I hope adding it to the implementations list might help with it.
Probably it is the most performant and the most type-safe JS implementation.
See its online documentation.

This page will be depricated in the main-md transition (happening soon!)
All libraries like this will be referenced and maintained at https://github.com/substrate-developer-hub/awesome-substrate - please check there for this lib and update if needed!

repo: substrate-developer-hub/substrate-docs


text:
[Windows] Tray keeps crashing

It crashes periodically without any activity. However it is worst when generating an SSH key.

done in dev

source: gharchive/issue

repo: subutai-io/tray

license_type: permissive

license_source: github-api


text:
🐛 BUG: Google ad console error on soft navigation

What operating system are you using?
Mac
Describe the Bug
On the live site, navigating from any page to another seems to log an error to the web console stating that an ad is trying to be inserted into an element which already contains an ad in it.
https://github.com/sugar-cat7/vspo-portal/assets/155891765/d3d074ed-1a1e-4a52-b229-2feb6a1feee3
I expect no error to be logged, however I am unsure as to what behavior should be expected.
This error seems to be caused by the following lines in GoogleAd.tsx (specifically the push() call):
const pathname = usePathname();
useEffect(() => {
  try {
    // eslint-disable-next-line
    ((window as any).adsbygoogle = (window as any).adsbygoogle || []).push(
      {},
    );
  } catch (error) {
    console.error(error);
  }
}, [pathname]);

Because the push fails (see log), the current behavior is that the ad never changes: the ad stays the same until the user performs a hard navigation (refresh or re-open the site elsewhere).
However, the pathname dependency in useEffect suggests that the original intent may have been to switch the ad on every path change.
Which behavior is preferable as a fix for this issue? @sugar-cat7
Please provide any relevant error logs
_app-5cd6971b279c8bd5.js?__WB_REVISION__=5cd6971b279c8bd5:116 TagError: adsbygoogle.push() error: All 'ins' elements in the DOM with class=adsbygoogle already have ads in them.
    at Qp (adsbygoogle.js?client=ca-pub-7433484160229921:221:210)
    at Fp (adsbygoogle.js?client=ca-pub-7433484160229921:217:450)
    at Bp.e.client (adsbygoogle.js?client=ca-pub-7433484160229921:211:43)
    at Ae.ea (adsbygoogle.js?client=ca-pub-7433484160229921:53:239)
    at bj (adsbygoogle.js?client=ca-pub-7433484160229921:87:19)
    at Bp (adsbygoogle.js?client=ca-pub-7433484160229921:211:31)
    at Object.push (adsbygoogle.js?client=ca-pub-7433484160229921:228:150)
    at _app-5cd6971b279c8bd5.js?__WB_REVISION__=5cd6971b279c8bd5:116:3328
    at uU (framework-fda0a023b274c574.js?__WB_REVISION__=fda0a023b274c574:9:84105)
    at oV (framework-fda0a023b274c574.js?__WB_REVISION__=fda0a023b274c574:9:113151)

Thank you.
As you mentioned, we were trying to change the advertisements for each path, but currently, the ads are not being purged appropriately, and it seems that reinsertion is not possible.
If possible, I would like to be able to change the advertisements for each page.(However, if this causes the advertisement scripts to reload and significantly increases the page transition time, I would like to avoid it.)

license: MIT


text:
Code review of org transform

Please do an initial code review focusing on:

lib/rialto/etl/configs/stanford_organizations_to_sparql_statements.rb
lib/rialto/etl/writers/sparql_statement_writer.rb
spec/configs/stanford_organizations_to_sparql_statements_spec.rb

Looking for feedback on anything, but especially transform pattern and Ruby coding.
DO NOT MERGE! Will prepare a complete PR once Researcher profile transform is completed.

I see there are some conflicts here, can you rebase?

source: gharchive/pull-request

authors: jcoyne justinlittman

repo: sul-dlss-labs/rialto-etl


text:
Files are not valid deposit resources

Instead they are deposited via a POST to /v1/file
Per discussion after standup 4/6/18

Let’s be extra clear here given recent confusion and a misleading title:
Files should not be deposited via a POST to the ‘/resource’ route. They should be deposited via a POST to ‘/file’ route. This is from sprint 0 discussions.
Updates to files (currently metadata only) are like any resource a PATCH to ‘/resource/{Id}’ route. We started work on update file (binary) but that was held back given team misunderstanding of current work.
On the ‘/file’ POST, a File is a valid deposit resource. But it builds and validated File metadata differently. Currently that build is invalid in master (it does not follow the MAP spec).
This is a change for the ‘/resource’ POST route and how it handles validations, which doesn’t include Files.

@cmh2166 yes, that is correct.

	Cool. Wasn’t asking, but clarifying for you and others - again, given confusion and unclear PR title.

	Get Outlook for iOS

On Mon, Apr 9, 2018 at 7:47 AM -0700, "Justin Coyne" notifications@github.com wrote:
@cmh2166 yes, that is correct.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

repo: sul-dlss-labs/taco


text:
Install AWS CLI

https://github.com/sul-dlss/operations-tasks/issues/1794
Tracking https://github.com/sul-dlss/operations-tasks/issues/1794

Installed on rialto-etl-prod

authors: aaron-collier jcoyne

repo: sul-dlss/rialto-etl


text:
update plugin to work with rollup 1.x

move rollup to peerDependencies
update all dependencies to latest
fix lint errors with newer eslint

Hi! Thanks for the MR. Looks definitely good to me. But I'll need to set this up locally first. I cannot verify package_lock.json from the web interface. I hope I can get to it soon. Hope it's OK for you that I'm a bit slow.

No rush! I wonder if you recently read the same blog post that I did?
https://snyk.io/blog/why-npm-lockfiles-can-be-a-security-blindspot-for-injecting-malicious-modules/

repo: suluke/express-middleware-rollup

license: mit

license_source: bigquery


text:
Make Virtual Business Card Creator

Networking, but make it digital.
Generate a simple, sharable digital business card with contact information and a QR code.

Assign this issue to me please @sumanth-0 .


text:
Update workflow to deploy to AKS

Update workflow to deploy to AKS

Automated Deployment Warning
Ensure your manifest at ./kubernetes/deployment.yaml uses the image name "skdemoacr.azurecr.io/samples/contoso-website:latest" for the application you wish to deploy.
For example, the image line in your deployment would look something like
image: skdemoacr.azurecr.io/skdemoacr.azurecr.io/samples/contoso-website:latest


text:
Deploying controller to support multiple github organizations

Is there any guidance around deploying this controller in a single EKS cluster to support multiple different GitHub organizations? We have a couple GitHub.com hosted organizations, as well as an on-prem Github Enterprise instance. I was looking to support all of those with actions runners running in the same EKS cluster.

You probably want to explore deploying multiple controllers using the watchNamespace feature, it's not really documented unfortunately. See https://github.com/summerwind/actions-runner-controller/issues/377 for more details.
@mumoshu can provide more details if you get stuck

Yeah, if you also need to isolate each organization('s runners) into a dedicated namespace, --watch-namespace should be handy.
In the Helm chart it is configurable via:
https://github.com/summerwind/actions-runner-controller/blob/b42b8406a2b6d606ef9b531867720039e1de1b42/charts/actions-runner-controller/values.yaml#L103-L104
Also, if you're okay with sharing the GitHub token/app and the namespace across GitHub orgs, I believe just creating RunnerDeployments with various organization field values work.

Please let me move this to Discussions as the question is already answered, the feature that supports the use case already exists, and the documentation enhancement is tracked in another issue #455.

authors: callum-tait-pbx mumoshu tzejohn

repo: summerwind/actions-runner-controller


text:
いいところ診断の結果に優しさを加えたい

以下の結果を追加したい
'{userName}のいいところは優しさです。あなたの優しい雰囲気や立ち振舞に多くの人が癒やされています。'

これから対応しまーす。

6d6f293 にて対応

repo: sumomori/assessment


text:
chore(configs): Temporarily disable security audit in CI

Purpose
The security audit currently produces an error (https://github.com/IBM/audit-ci/issues/103), causing CI to wrongly fail.
Approach and changes

Temporarily disable security audit in CI

Definition of done

[x] Development completed
[x] Reviewers assigned
[x] Unit and integration tests
[x] Meets minimum browser support
[x] Meets accessibility requirements

:tada: This PR is included in version 1.1.0-canary.1 :tada:
The release is available on:

npm package (@canary dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: connor-baer ilyanoskov

repo: sumup/circuit-ui


text:
[BUG] v1.50.73版本无法使用必应对话

Describe the bug / 描述问题
chatall v1.50.73 设置必应链接正常,但用不了必应对话, 选后无法点亮右下角必应图标
To Reproduce / 复现步骤
点击设置,登入bing链接正常,选择bing的三个模型,均无法正常使用,开发者工具显示报错Failed to load resource: the server responded with a status of 404 ()
Expected behavior / 期望行为
希望能正常使用
Screenshots / 截图

Devtools Info / 开发者工具信息

OS and version / 操作系统版本
Windows 11
ChatALL version / ChatALL 版本
v1.50.73
Network / 网络
美国/新加坡 代理VPN
Additional context / 其它相关信息
无

我在v1.50.73版本里面可以正常使用bing, （OS 版本 Windows 10，代理（美国））

有没有试过重启ChatAll?

谢谢回复,有重启过的,今天还是不行.开发者工具页面显示报错Failed to load resource: the server responded with a status of 404 (),是什么原因呢?

谢谢回复,有重启过的,今天还是不行.开发者工具页面显示报错Failed to load resource: the server responded with a status of 404 (),是什么原因呢? 需要我提供更多信息吗?

你浏览器试下下面两个地址，可以看书数据吗
https://www.bing.com/turing/conversation/chats
https://cn.bing.com/turing/conversation/chats

有返回数据,看着都是正常的

我发现其他的模型也有类似问题,这里选择一些模型,但好多都没点亮

我发现其他的模型也有类似问题,这里选择一些模型,但好多都没点亮

我这边是win11的电脑尝试复现该问题，测试了下这边一直是ok的

bingchat 登录时，有点击右上角这个登录吗？

抱歉,应该是登陆的问题.登陆后bing已经都点亮了,感谢
请问1.  GPT-3.5报错 Error: Conversation not found  是什么原因呢?
2. 为什么最近LMSYS模型一直没有返回结果,是什么原因呢?

authors: showkawa tinaFei yangqie

repo: sunner/ChatALL


text:
Template for ap-south-1 region

Feature request
Is your feature request related to a problem? Please describe.
Create template to use for ap-south-1 (Mumbai) Region
Describe the solution you'd like
Add ap-south-1 (Mumbai) as one of Region to launch stack

@yogeshbeniwal
Now, the template for ap-south-1 is available!
Please check it.

repo: supabase-community/supabase-on-aws


text:
feat: standardise logs

What kind of change does this PR introduce?
Improvement
What is the current behavior?
Currently, logs are a bit all over the place with different shapes.
What is the new behavior?
This PR tries to standardize logs across the service and include more useful information such as:

owner
reqId
headers:

'content-type',
'if-none-match',
'if-modified-since',
'upload-metadata',
'upload-length',
'tus-resumable',

Lifecycle events are now also logged and you can find the lifecycle of a specific asset by filtering with:
m.objectPath:"{ref}/{bucket}/{object}

additionally, you can filter by the following properties:
m.type:"event" m.event:~"ObjectCreated" m.project:""

All events will also include a reqId field which can be correlated to the request that was issued from.
m.type:"request" m.reqId:"reqId"

Pull Request Test Coverage Report for Build 6351879663

110 of 176 (62.5%)  changed or added relevant lines in 18 files are covered.
5 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.4%) to 84.337%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/http/routes/tus/index.ts
3
4
75.0%

src/queue/events/multipart-upload-completed.ts
1
2
50.0%

src/queue/events/object-admin-delete.ts
12
13
92.31%

src/storage/uploader.ts
4
5
80.0%

src/storage/object.ts
16
18
88.89%

src/storage/errors.ts
6
9
66.67%

src/http/routes/tus/handlers.ts
0
4
0.0%

src/queue/events/webhook.ts
2
15
13.33%

src/http/plugins/db.ts
1
41
2.44%

Files with Coverage Reduction
New Missed Lines
%

src/storage/errors.ts
1
80.0%

src/http/plugins/db.ts
4
64.96%

Totals

Change from base Build 6337917527:
-0.4%

Covered Lines:
7390

Relevant Lines:
8692

💛  - Coveralls

authors: coveralls fenos

repo: supabase/storage-api


text:
Fetching Failed and Give Invalid API Key

Bug report
Describe the bug
I have rewrite my nextjs project to using latest version and install latest supabase-js. When i fetch all in my tables called "posts", it is work perfectly. but when i fetch one entry in posts that equal to "slug" a, sometimes is not working and response data message: invalid apikey please double check your anon or role blablabla... and error response is null. Then i tried another entries with different slug and thats work perfectly. Why that happen?
To Reproduce
This is my code

Expected behavior
I want it work with my code
Screenshots
Response screenshot

System information

OS: endeavouros - arch - linux
Browser edge
Version of supabase-js: 2.10.0
Version of Node.js: 19.7.0

Additional Context
Sorry for my bad english, i try so hard to explain the problem clearly. But result is not so good, i hope you understand that.

That's not bug, just cached on nextjs so problem solved when i delete .next directory

repo: supabase/supabase-js


text:
Supavisor.Manager will lose its ets state upon process restart

The  Supavisor.Manager has an ets table that will erase when the Manager process crashes.  Is this acceptable?
There's a pattern to avoid data loss (I've used it at work):  http://steve.vinoski.net/blog/2011/03/23/dont-lose-your-ets-tables/
I can submit a PR if state persistence is considered useful in this context.

Thanks!
Clients are handling manager crashes here: https://github.com/supabase/supavisor/blob/4770b987e06950c5be313f8ca6b08d1fe50d1117/lib/supavisor/client_handler.ex#L182
So they should disconnect if they're :busy (to kill it so the end client will reconnect) or resubscribe to the new manager if they're not :busy.
We think this is a bit more straight forward, at least for now.

authors: Dowwie chasers

repo: supabase/supavisor


text:
Add kube-linter

Is your feature request related to a problem? Please describe.
Please add kube-linter for the following reasons:

kube-linter is actively maintained whereas kubeval was last worked on 15 months ago
kube-linter provides robust checks enable/disable

Describe the solution you'd like
Add kube-linter as another linter option for kubernetes manifests
Describe alternatives you've considered
kubeval

This should stay open

Useful pointers:

Container image: https://docs.kubelinter.io/#/?id=using-docker
CLI Usage: https://docs.kubelinter.io/#/?id=usage

authors: ferrarimarco tiagovrtr tis-rpage

repo: super-linter/super-linter


text:
Find go.mod based on Go files

Proposed changes
Close #5292
Readiness checklist
In order to have this pull request merged, complete the following tasks.
Pull request author tasks

[ ] I included all the needed documentation for this change.
[ ] I provided the necessary tests.
[x] I squashed all the commits into a single commit.
[x] I followed the Conventional Commit v1.0.0 spec.
[ ] I wrote the necessary upgrade instructions in the upgrade guide.
[x] If this pull request is about and existing issue,
I added the Fix #ISSUE_NUMBER label to the description of the pull request.

Super-linter maintainer tasks

[x] Label as breaking if this change breaks compatibility with the previous released version.
[x] Label as either: automation, bug, documentation, enhancement, infrastructure.

Thanks for this PR! A few small things to check.

Thanks! A small thing to fix:
            if [ ! grep -Fxq \\"${go_mod_filename}\\" \\"${FILE_ARRAYS_DIRECTORY_PATH}/file-array-GO_MODULES\\" ]; then
            ^-- SC1009 (info): The mentioned syntax error was in this if expression.
               ^-- SC1073 (error): Couldn't parse this test expression. Fix to allow more checks.
                                                  ^-- SC1072 (error): Expected test to end here (don't wrap commands in []/[[]]). Fix any mentioned problems and try again.

Thanks! A small thing to fix:
            if [ ! grep -Fxq \\"${go_mod_filename}\\" \\"${FILE_ARRAYS_DIRECTORY_PATH}/file-array-GO_MODULES\\" ]; then
            ^-- SC1009 (info): The mentioned syntax error was in this if expression.
               ^-- SC1073 (error): Couldn't parse this test expression. Fix to allow more checks.
                                                  ^-- SC1072 (error): Expected test to end here (don't wrap commands in []/[[]]). Fix any mentioned problems and try again.

I have fixed the test

There's an issue, I think:
  2024-03-13 21:41:06 [FATAL]   Error when setting INDEX for GO_MODULES: 0

https://github.com/super-linter/super-linter/actions/runs/8271680556/job/22632678543?pr=5345
Can you kindly take a look? Thanks!

There's an issue, I think:
  2024-03-13 21:41:06 [FATAL]   Error when setting INDEX for GO_MODULES: 0

https://github.com/super-linter/super-linter/actions/runs/8271680556/job/22632678543?pr=5345
Can you kindly take a look? Thanks!

More logs after rebasing:
  2024-04-22 09:49:46 [DEBUG]   PARALLEL_COMMAND_OUTPUT for GO_MODULES (exit code: 255): cd /tmp/lint/test/linters/go_modules/go_modules_good || exit 255; golangci-lint run --allow-parallel-runners -c /tmp/lint/.github/linters/.golangci.yml && echo \"Linted: /tmp/lint/test/linters/go_modules/go_modules_good\"
  parallel: Error: Cannot change into non-executable dir /tmp/lint/test/linters/go_modules/go_modules_good/go.mod: File exists

This is due to how we configure the command to run for GO_MODULES: https://github.com/super-linter/super-linter/blob/56e675bd333f8af069b2d7ba67ade1f39fcd01c4/lib/functions/worker.sh#L123-L139
So the command becomes:
parallel ... --workdir {} ...

({} means: the input item as it is, which is /tmp/lint/test/linters/go_modules/go_modules_good/go.mod because you set it to echo "${go_mod_filename}" >>"${FILE_ARRAYS_DIRECTORY_PATH}/file-array-GO_MODULES").
I'll send another comment with the necessary changes.
Thanks for all your work on this!

@ferrarimarco Thanks for pointing out the issue! It's now updated

Thanks!
We are on the right track!
I think we might still need some refactoring because in the current implementation users will not be able to disable lining of Go modules by using the VALIDATE_GO_MODULES variable. Also, we might report false positives because Go files might be linted one by one (VALIDATE_GO default mode), and also as a module.
Let me think a bit about this.

@ferrarimarco Thank you so much! There're two parts that I have doubts. If you agree, I'll make the edits and squash two commits.

Thanks for the review @harryzcy ! Your proposal SGTM :)

I just squashed two commits to become https://github.com/super-linter/super-linter/pull/5345/commits/4637a4ec70525882b1fdee2ccb977e2569d66180

authors: ferrarimarco harryzcy


text:
Support nested properties when specifying location of apiKey in body

Expected Behavior
I am able to specify token location in nested structure
Current Behavior
Property with specified name is set in root of the data object.
Possible Solution
Allow to use JSON Pointer to specify location.

I like the use of JSON Pointer which nicely covers edge cases with special characters in property names.
One point to consider is how much safe / transparent is for SDK to manipulate the payload after being prepared by map. For example, given the following payload in body:
{
  "data": {
    "properties": ["foo", "bar"]
  }
}

And given the following pointer for apiKey inside body: /data/properties/token
I am trying to add property to an array, which is clearly a mistake which will result into an error during perform (or perhaps even by linter if we can do type checking on body of http call).
Other case is when the properties do not exist in the payload, e.g. I am sending either an empty body or just {"data": {}}. Should SDK automatically create the missing properties in the path for me? I'd say yes.
I think both of these cases are okay assuming they will be explicitly documented and provide friendly error message.

authors: freaz jnv

repo: superfaceai/one-sdk-js


text:
[Android] (DocumentImeSerializer._imeToDocumentPosition) Couldn't map an IME position to a document position - Editor Freezes

We started to get feedback from our first major rollout of SE to android (we've been in production ios/mac os for upwards of a year now with no issues, something we are extremely grateful for, really incredible work).  This error is associated with the crash event, and it is the same base error reported in #1081.
There is common behavior reported throughout every user we have been able to individually contact tagged on this event: the editor stops taking input and it must be closed and then reopened in order to continue editing the document (in our case referred to as an "entry").
This is the average report:

After a short period, text will fail to appear as I'm typing. Fixed by coming out of the editor and going back in. But the problem will repeat resulting in having to go in and out several times to complete the entry.

So far, there doesn't seem to be any one specific action / repro that triggers the crash, but rather a myriad of various common editing actions:
- adding a bulleted list
The user adds a bullet list item and can no longer advance to the next line:
https://github.com/superlistapp/super_editor/assets/37011672/f6415536-b2b0-40c6-9baf-da56b45750f5
- in some cases, adding a new line
The user types "Happy", applies rich-text formatting (header), and then moves to the next line:
https://github.com/superlistapp/super_editor/assets/37011672/35526d0c-718f-401b-8f74-0023444e47fa
- special characters associated with non-English languages

Today I noticed a pattern. The editor freezed after writing "ão" (common in Portuguese words) It happened 2 times and in each of them I had to checkmark, close and open again to continue writing.

- after autocorrection of a typo
The user misspells "waves" (~1:17) and the word is auto-corrected, then the editor freezes.
https://github.com/superlistapp/super_editor/assets/37011672/db03b42c-df0e-41bc-ba1a-a021a4334d70
- manually accepting keyboard text suggestions
The user accepts text suggestion of the word "anonymous"
https://github.com/superlistapp/super_editor/assets/37011672/f7a572aa-8000-4d34-a61b-05fff5bde8ee
The user accepts text suggestion of the word "issues" (~:25)
https://github.com/superlistapp/super_editor/assets/37011672/c13e7a4a-c159-4b28-9ac4-e340772ab565
Below are logs of six separate variants of the same error in order of most to least common:
Variant 1
Fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError
Exception: Couldn't map an IME position to a document position. TextEditingValue: '[redacted]' IME position: TextPosition(offset: 251, affinity: TextAffinity.downstream). Error thrown Instance of 'ErrorDescription'.
DocumentImeSerializer._imeToDocumentPosition (document_serialization.dart:271)
DocumentImeSerializer.imeToDocumentSelection (document_serialization.dart:164)
TextDeltasDocumentEditor._applyInsertion (document_delta_editing.dart:133)
TextDeltasDocumentEditor.applyDeltas (document_delta_editing.dart:69)
DocumentImeInputClient.updateEditingValueWithDeltas (document_ime_communication.dart:215)
DeltaTextInputClientDecorator.updateEditingValueWithDeltas (ime_decoration.dart:119)
TextInput._handleTextInputInvocation (text_input.dart:1867)
TextInput._loudlyHandleTextInputInvocation (text_input.dart:1753)
MethodChannel._handleAsMethodCall (platform_channel.dart:555)
MethodChannel.setMethodCallHandler.<fn> (platform_channel.dart:548)
_DefaultBinaryMessenger.setMessageHandler.<fn> (binding.dart:393)

Variant 2
Fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError
Exception: Couldn't map an IME position to a document position. TextEditingValue: '[redacted]' IME position: TextPosition(offset: 129, affinity: TextAffinity.downstream). Error thrown Instance of 'ErrorDescription'.
DocumentImeSerializer._imeToDocumentPosition (document_serialization.dart:271)
DocumentImeSerializer.imeToDocumentSelection (document_serialization.dart:164)
TextDeltasDocumentEditor._applyInsertion (document_delta_editing.dart:133)
TextDeltasDocumentEditor.applyDeltas (document_delta_editing.dart:69)
DocumentImeInputClient.updateEditingValueWithDeltas (document_ime_communication.dart:215)
DeltaTextInputClientDecorator.updateEditingValueWithDeltas (ime_decoration.dart:119)
TextInput._handleTextInputInvocation (text_input.dart:1867)
TextInput._loudlyHandleTextInputInvocation (text_input.dart:1753)
MethodChannel._handleAsMethodCall (platform_channel.dart:555)
MethodChannel.setMethodCallHandler.<fn> (platform_channel.dart:548)
_DefaultBinaryMessenger.setMessageHandler.<fn> (binding.dart:393)

Variant 3
Fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError: Exception: Couldn't map an IME position to a document position.
TextEditingValue: '[redacted] '
IME position: TextPosition(offset: 132, affinity: TextAffinity.downstream). Error thrown Instance of 'ErrorDescription'.
       at DocumentImeSerializer._imeToDocumentPosition(document_serialization.dart:271)
       at DocumentImeSerializer.imeToDocumentSelection(document_serialization.dart:164)
       at TextDeltasDocumentEditor._applyNonTextChange(document_delta_editing.dart:211)
       at TextDeltasDocumentEditor.applyDeltas(document_delta_editing.dart:75)
       at DocumentImeInputClient.updateEditingValueWithDeltas(document_ime_communication.dart:215)
       at DeltaTextInputClientDecorator.updateEditingValueWithDeltas(ime_decoration.dart:119)
       at TextInput._handleTextInputInvocation(text_input.dart:1867)
       at TextInput._loudlyHandleTextInputInvocation(text_input.dart:1753)
       at MethodChannel._handleAsMethodCall(platform_channel.dart:555)
       at MethodChannel.setMethodCallHandler.<fn>(platform_channel.dart:548)
       at _DefaultBinaryMessenger.setMessageHandler.<fn>(binding.dart:393)

Variant 4
Fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError: Exception: Couldn't map an IME position to a document position.
TextEditingValue: '[redacted] '
IME position: TextPosition(offset: 128, affinity: TextAffinity.downstream). Error thrown Instance of 'ErrorDescription'.
       at DocumentImeSerializer._imeToDocumentPosition(document_serialization.dart:271)
       at DocumentImeSerializer.imeToDocumentSelection(document_serialization.dart:164)
       at TextDeltasDocumentEditor.delete(document_delta_editing.dart:311)
       at TextDeltasDocumentEditor._applyDeletion(document_delta_editing.dart:198)
       at TextDeltasDocumentEditor.applyDeltas(document_delta_editing.dart:73)
       at DocumentImeInputClient.updateEditingValueWithDeltas(document_ime_communication.dart:215)
       at DeltaTextInputClientDecorator.updateEditingValueWithDeltas(ime_decoration.dart:119)
       at TextInput._handleTextInputInvocation(text_input.dart:1867)
       at TextInput._loudlyHandleTextInputInvocation(text_input.dart:1753)
       at MethodChannel._handleAsMethodCall(platform_channel.dart:555)
       at MethodChannel.setMethodCallHandler.<fn>(platform_channel.dart:548)
       at _DefaultBinaryMessenger.setMessageHandler.<fn>(binding.dart:393)

Variant 5
Fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError: Exception: Couldn't map an IME position to a document position.
TextEditingValue: '[redacted]'
IME position: TextPosition(offset: 4, affinity: TextAffinity.downstream). Error thrown Instance of 'ErrorDescription'.
       at DocumentImeSerializer._imeToDocumentPosition(document_serialization.dart:271)
       at DocumentImeSerializer.imeToDocumentRange(document_serialization.dart:220)
       at TextDeltasDocumentEditor.applyDeltas(document_delta_editing.dart:89)
       at DocumentImeInputClient.updateEditingValueWithDeltas(document_ime_communication.dart:215)
       at DeltaTextInputClientDecorator.updateEditingValueWithDeltas(ime_decoration.dart:119)
       at TextInput._handleTextInputInvocation(text_input.dart:1867)
       at TextInput._loudlyHandleTextInputInvocation(text_input.dart:1753)
       at MethodChannel._handleAsMethodCall(platform_channel.dart:555)
       at MethodChannel.setMethodCallHandler.<fn>(platform_channel.dart:548)
       at _DefaultBinaryMessenger.setMessageHandler.<fn>(binding.dart:393)

Variant 6
Fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError: Exception: Couldn't map an IME position to a document position.
TextEditingValue: '[redacted]'
IME position: TextPosition(offset: 316, affinity: TextAffinity.downstream). Error thrown Instance of 'ErrorDescription'.
       at DocumentImeSerializer._imeToDocumentPosition(document_serialization.dart:271)
       at DocumentImeSerializer.imeToDocumentSelection(document_serialization.dart:164)
       at TextDeltasDocumentEditor.replace(document_delta_editing.dart:283)
       at TextDeltasDocumentEditor._applyReplacement(document_delta_editing.dart:184)
       at TextDeltasDocumentEditor.applyDeltas(document_delta_editing.dart:71)
       at DocumentImeInputClient.updateEditingValueWithDeltas(document_ime_communication.dart:215)
       at DeltaTextInputClientDecorator.updateEditingValueWithDeltas(ime_decoration.dart:119)
       at TextInput._handleTextInputInvocation(text_input.dart:1867)
       at TextInput._loudlyHandleTextInputInvocation(text_input.dart:1753)
       at MethodChannel._handleAsMethodCall(platform_channel.dart:555)
       at MethodChannel.setMethodCallHandler.<fn>(platform_channel.dart:548)
       at _DefaultBinaryMessenger.setMessageHandler.<fn>(binding.dart:393)

Thanks for all of the examples. Maybe we need to try to add integration tests so that we run at least some of our tests against a real IME.
@angelosilvestre as a start for this ticket, can you try adding a single integration test that runs on Android, which displays a full-screen editor, types something, and then verifies what was typed?

@matthew-carroll Even using an integration test, wouldn't we be using the same test methods that just send the same platform messages as the IME would do?
We will send messages to the real IME, but I don't think we can type using the virtual keyboard...

Can you poke around the docs and options for that? Can we leverage some Android tooling to send input through the keyboard? Or at least through the IME?


text:
How to play my private video? (Private vimeo video link)

Hello, I have private vimeo video link. Can i use it with that pod? Link example in bellow i can play it in browser but when i use link with pod file it turns "Error = Failed to parse Vimeo response"
https://vimeo.com/230611000/xxxxxxx

@cemalsayin I know it's a late reply but maybe it will help someone else. I had the same issue and fixed it by using fetchVideoURLFrom id instead of fetchVideoURLFrom url... and in that case just pass the 230611000 as id

@budidino I am still facing the same issue tried both fetchVideoURLFrom id & fetchVideoURLFrom URL. But the issue is not fixed. Have you done any other changes?

@nithintwobase the library has been updated, please try again using fetchVideoURLFrom:id

@nithintwobase the library has been updated, please try again using fetchVideoURLFrom:id

hi is that work? It's still a problem.

authors: budidino cemalsayin naariman nithintwobase superm0


text:
Close PDF window when esc key pressed

Currently, to close PDF window, you have to use the mouse (horrid) or press alt+f4 (not likely to seem obvious to many people and also makes me nervous of closing SM by accident instead).
Esc closing it would be ideal and likely what people would expect from how other windows in SM work.

Moved to the appropriate repository.
I don't think I'll implement that. You can just alt-tab if you want to go to SM, or press alt-f4. It would be very annoying if the window closed at the press of a single key. SuperMemo's design isn't ideal in that specific aspect.

authors: alexis- rajlego


text:
🛑 I am feeling anxious is down

In b979bc2, I am feeling anxious (https://iamfeelinganxious.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: I am feeling anxious is back up in 9ba100c.


text:
Replace logging framework

Replace logrus due to rather inactive maintenance. Some options are:

https://pkg.go.dev/golang.org/x/exp/slog
https://github.com/uber-go/zap

As mentioned in https://github.com/suse-edge/nm-configurator/pull/5, the tool will use Rust for its implementation instead replacing the Go PoC.

repo: suse-edge/nm-configurator


text:
Adding a Tips and Tricks section to Edge Book and adding the first page for EIB

Adding a Tips and Tricks section to Edge Book and adding the first page for EIB

@e-minguez new PR here

reworked the document and added a link from EIB component page to it.


text:
Changing the first pull request

This is a test for creating a new pull request here.

The Bot is visible. Thanks


text:
how the upstream build process different to local build?

Describe the bug
A clear and concise description of what the bug is.
using my local build image through make
# kubectl logs kepler-exporter-nhc7c -n kepler
I1101 07:30:48.662096       1 exporter.go:74] Kepler running on version: v0.3-71-g1b92289

using upstream latest
# kubectl logs kepler-exporter-zmf99 -n kepler
I1101 07:51:14.034145       1 exporter.go:74] Kepler running on version:

@SamYuan1990 what's the latest image build ? something about the process might be helpful here
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

The image update is made in workflows/image.yml. A new image will be created every time that the main is updated.
The _build_local and  _build_containerized are using different parameters. This might be the problem...

I am wondering https://github.com/sustainable-computing-io/kepler/blob/main/.github/workflows/image.yml#L20
is the root cause ..

ok, saw your comment, actually with make we can see
Step 13/21 : RUN make clean $MAKE_TARGET SOURCE_GIT_TAG=$SOURCE_GIT_TAG BIN_TIMESTAMP=$BIN_TIMESTAMP
 ---> Running in 8693e36449b7
rm -f -r '_output/bin'

the target is cross-build-linux-amd64 and this build will call _build_local anyway.. so I think it's still same process for build the kepler execute file

@jichenjc. Just make actually run: make _build_containerized ARCH=amd64
_build_containerized has the following arguments:
OS := $(shell go env GOOS)
ARCH := $(shell go env GOARCH)
SOURCE_GIT_TAG=$(SOURCE_GIT_TAG)
BIN_TIMESTAMP=$(BIN_TIMESTAMP)
ARCH=$(ARCH)
MAKE_TARGET="cross-build-linux-$(ARCH)"

_build_local has the following arguments:
GOOS=$(GOOS)
GOARCH=$(GOARCH)
${GO_BUILD_TAGS}
$(LDFLAGS)

The variable that is adding the version is the LDFLAGS, but the _build_containerized does not have this variable. You probably need to add it.
The Makefile has the variable GO_LD_FLAGS := $(GC_FLAGS) -ldflags "-X $(LD_FLAGS)" $(CFLAGS) that is not being used anywhere.
Probably both the _build_containerized and _build_local should use the GO_LD_FLAGS.
By the way, _build_containerized should also have GO_BUILD_TAGS.

thanks for the detailed info, however, curious why my local test build make can create container with LDFLAGS...
something need dig into :)
will submit a PR to this

Humm, you are right @jichenjc ...
I'm using and the _build_containerized and it has the version: v0.3-82-ge5113f5-dirty in the logs.
So, the GO_LD_FLAGS is being computed and used when building the image within the container....
The problem might be something else...

authors: jichenjc marceloamaral

repo: sustainable-computing-io/kepler


text:
Handle KeyboardInterrupt for inputscope-listener

Resolves https://github.com/suurjaak/InputScope/issues/16

A good change, thank you, but I will have to decline this pull request, as the development happens in a private dev-branch. I will incorporate it there.
However, this would not resolve #16, as the problem with Ctrl-C is in main.py.

Over more than a decade of releasing open-source software, I think I've only ever received pull requests from like.. 2 people, so it has never really been a thing :)
But since pull requests cannot be disabled in GitHub anyway, users can always create one. In comparison to issues, they have the added benefit of code on the side, no matter whether and how the changes finally get incorporated.

authors: suurjaak ulcuber

repo: suurjaak/InputScope


text:
Redundant info in error print for duktape/C generated errors

When you throw an error in JS the resulting error printout only contains the call stack (with the top line containing the thrown error + message):
TypeError: Test
    at global (main.js:10)
    at [anon] (eval:1)

However, when you throw an error using duk_error() things look different. Now the resulting printout has 2 sections: Message and Stack where the stack repeats (part of) the message. Here's an example:
  Message:
    Error: Error while creating folder '': No such file or directory in tests/self-tests/fs-specs.js (line 16)
  Stack:
    Error: Error while creating folder '': No such file or directory
        at emptyDirSync () native
        at [anon] (tests/self-tests/fs-specs.js:16)
        at call () native
        at attemptSync (node_modules/jasmine-core/lib/jasmine-core/jasmine.js:3898)
        at [anon] (node_modules/jasmine-core/lib/jasmine-core/jasmine.js:3887)
        at [anon] (node_modules/jasmine-core/lib/jasmine-core/jasmine.js:3872)
        at [anon] (node_modules/jasmine-core/lib/jasmine-core/jasmine.js:816)
        at [anon] (node_modules/jasmine-core/lib/jasmine-core/jasmine.js:478)
        at [anon] (node_modules/jasmine-core/lib/jasmine-core/jasmine.js:4975)
        at call () native
        [...]

(the call stack shown here is already cleaned-up, i.e. no C/C++ stuff).  I would like to get rid of the duplicate message. In such a situation I could remove the top entry of the stack, but that removes an important part for JS errors (as there is no dedicated message printout for them). What else could I do?

Jasmine is on the stack.  Are you sure it’s not catching the error and rethrowing it?  I haven’t seen an error message that looks like that before.

Seems you hit an important point. I didn't expect Jasmine to play a role here, since the difference I saw first was between a top level throw in a .js file vs duk_error(). However when I throw that error in any of the test functions from Jasmine the message shows up with the duplicate error string. So it looks as if Jasmine is doing the "wrong" thing here. Thanks for getting my head to think in the right direction.

An important thing to keep in mind is that in Duktape, like with Lua, once you call into Duktape to execute a script, your C and JS code are fully integrated - Duktape/C functions essentially act as plugins and still run in the same context as any other ecmascript function.  They can throw errors, exceptions will propagate through them while unwinding, etc.  that’s why the “safe call” (error catching) APIs exist, because otherwise you’d throw the error right out of your reach.
This is a bit hard to wrap your head around at first (at least it was for me), but once you understand the implications it becomes very powerful.

Something is catching, modifying, and rethrowing errors - that Message/Stack output definitely doesn't come from Duktape. Some frameworks do catch and rethrow, and may even augment the stack trace before rethrowing. For example, frameworks which translate code may try to modify or add original source file/line information into errors for convenience.
Unfortunately .stack is a non-standard property and as such there's no "standard behavior". Duktape's .stack is quite close (but not identical) to V8's equivalent so usually things work out fine. In particular, you can (1) assign to .stack (replacing the automatic getter-based value), and (2) Object.defineProperty() .stack. Usually this is enough for catch/rethrow framework code.

authors: fatcerberus mike-lischke svaarala

repo: svaarala/duktape


text:
platypus file not reading new script changes

If the platypus file is running test.py, which looks like this:
print(1)
it works. If I then go into test.py and edit it in any way whatsoever, for instance changing it to
print(1)
print(2)
then when I run the platypus file it will still run the first version of test.py. It's almost like the platypus file compiles the first script and stores it, running only that stored version in the future. I have tried several scripts with several changes on several platypus files and it only ever runs the version of the script that existed when the playtpus file was first created. Is this default behavior? I don't see it in the readme. How do I get it to read updated scripts?
I'm on high sierra 10.13.6.
This is my first issue sorry if I have done anything wrong.

Each time you create a Platypus app, your script is copied into the resulting application bundle. If you change the script, you need to recreate the app. If you want to continue editing the original script file and have the changes automatically apply to the app, try the "Create symlink to script and bundled" option when creating the app. This creates a symbolic link inside the application bundle to your script instead of copying it over.

authors: josh-flori sveinbjornt

repo: sveinbjornt/Platypus


text:
方程式という表現を変える

On the other side of the equation, in MapMarker.svelte, we can now get a reference to the Mapbox instance:

上記原文の equation の意図としては、プログラミング的解釈であるため、「代入演算子を用いた式」を指していると思います。
ただ、前の文にある getContext では equation といった表現が無く、ここで新しく出る概念でもないため、この流れのまま「一方、」としたほうが読みやすいのではないかと思いました。
https://sveltejp.dev/tutorial/context-api
https://svelte.dev/tutorial/context-api

CDNの該当のキャッシュをパージしました！
ブラウザーのローカルキャッシュを削除するか、キャッシュの期限(最大1日)が切れると確認できると思います！

authors: ampcpmgp tomoam

repo: svelte-jp/svelte-site-jp


text:
On page preload global css overrides currently loaded page styles

Describe the bug
When we have an <a> anchor tag that links to a separate page different from than the currently loaded page, and both these pages share a global class name, hovering over the anchor tag preloads the next page (or clicking -> navigating to page-2 -> and navigating back to page-1) and overrides the global styles of the currently loaded page.
Reproduction
Repro: https://stackblitz.com/edit/sveltejs-kit-template-default-xsrzyd?file=src%2Froutes%2Fpage2%2F%2Bpage.svelte
NOTE: The only limitation in the above repro is that hover is not preloading assets in stackblitz, but if you click on the anchor tag, navigate to page2 and navigate back to page1, the styles from page2 persist on page1
System Info
System:
  OS: macOS 13.4.1
  CPU: (10) arm64 Apple M1 Pro
  Memory: 256.02 MB / 16.00 GB
  Shell: 3.5.1 - /opt/homebrew/bin/fish
Binaries:
  Node: 18.16.1 - /opt/homebrew/opt/nvm/versions/node/v18.16.1/bin/node
  Yarn: 1.22.19 - /opt/homebrew/bin/yarn
  npm: 9.6.6 - /opt/homebrew/bin/npm
  pnpm: 8.6.6 - /opt/homebrew/bin/pnpm
Browsers:
  Brave Browser: 116.1.57.47
  Chrome: 115.0.5790.170
  Safari: 16.5.2
npmPackages:
  @sveltejs/adapter-node: ^1.3.1 => 1.3.1
  @sveltejs/kit: ^1.22.3 => 1.22.3
  svelte: ^4.0.0 => 4.0.1
  vite: ^4.3.6 => 4.3.9

Severity
serious, but I can work around it
Additional Information
Not sure how serious this issue should be considered, cause leaking global CSS was a mistake on my end as well.
Though, both these global CSS existed inside two different pages, they shouldn't have affected each other.

Essentially a duplicate of #7918/#7751. What happens with conflicting global styles isn't a behavior we want to define. If possible, you should make each page/component's styles be scoped to that page/component.

authors: Conduitry phoenisx

repo: sveltejs/kit


text:
svelte-kit demo app not working correctly with typescript option

Describe the bug
I ran the commands for making a new app on https://kit.svelte.dev/. I chose typescript for the option and when I go to the 'todos' page of the app after running it, any action I do requires a refresh of the page to show the change. I ran the same commands but chose javascript with the type docs and it works fine for that option. Is this an issue with how the demo-app is auto built when typescript is chosen as the option, or is there a deeper typescript compatibility issue to where I should avoid using it for now? I'm new to svelte and svelte-kit by the way..
Reproduction
The reproduction is following the instructions to build a demo app with svelte-kit on this page: https://kit.svelte.dev/. Then, choose typescript and say yes to all of the options.
Logs
No response
System Info
System:
    OS: Windows 10 10.0.19044
    CPU: (4) x64 Intel(R) Core(TM) i5-7300U CPU @ 2.60GHz
    Memory: 1.48 GB / 15.89 GB
  Binaries:
    Node: 16.17.0 - C:\Program Files\nodejs\node.EXE
    npm: 8.1.3 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 104.0.5112.102
    Edge: Spartan (44.19041.1266.0), Chromium (104.0.1293.63)
    Internet Explorer: 11.0.19041.1566

Severity
serious, but I can work around it
Additional Information
By 'work around it' I mean I have to use the javascript option instead.

I'm afraid I can't reproduce this in a freshly created TypeScript app with npm create svelte@latest

After rebuilding for a 3rd time, it works now for some reason. I do get an issue occasionally where it throws an error for me deleting an item, but I'm not sure how to reproduce it, since it seems random. Closing for now I suppose.

authors: Rich-Harris kuehlc


text:
Add stop sign to prevent inheriting from parent layouts

Describe the problem
I have the following routes structure in my Sveltekit project:
src/routes/
└ +layout.svelte
├ Activities/
├ Transfers/
├ Products/
├ About/
├ Terms
├ Welcome/
  └ +layout.svelte

The /Welcome page needs to have its own layout, all the others inherit the layout from root.
Currently I have to put all other pages into a group like (app) so the Welcome page does not inherit from the root layout anymore.
The same applies if I want to have a totally different layout for home page /, I have to put it under a (root) group, and all the other pages under (app) group.
But in both use cases there is still the +error.svelte page, which now has no root layout anymore to inherit from.
Describe the proposed solution
It would make life and routes structure much easier if we could append a stop sign to the layout file, like+layout-.svelte +layout|.svelte or any other suitable char indicating that this layout does not inherit from parent layouts (similar to the @ sign to break out of their parent layout hierarchy).
Importance
would make my life easier
Additional Information
If the +error.svelte page should inherit from root layout, which now is under (app) group, I have to replicate the layout for the root error page. With the proposed solution this would not be necessary.

If I understand the problem correctly I believe you could put parens around (welcome) and it will not inherit the parent layout…it was just added recently to kit.
https://kit.svelte.dev/docs/advanced-routing#advanced-layouts

If I understand the problem correctly I believe you could put parens around (welcome) and it will not inherit the parent layout…it was just added recently to kit.
https://kit.svelte.dev/docs/advanced-routing#advanced-layouts

Layouts (normal and the ones in group) always inherit from the root layout, and this is exactly the problem. There is currently no way to say that a specific layout or page should NOT inherit from root. The only solution is to create 2 groups, but it seems a bit of a overhead for me.

What kind of issues does it create for with +error.svelte for you?
What we won't do is to provide a way to break out of the root layout. Making the guarantee that the root layout is always present makes it possible to put app-wide logic or UI in there. I understand that it may be cumbersome to create a group for this, but this is the tradeoff we are making. The alternative would be to create a #if statement in your root layout to hide the surrounding UI if you are on the welcome page.

Currently I have to include the layout into the +error.svelte page directly, which that does not feel well.
For our use case and I think for others as well, we need to escape from the root layout as well as from the app-wide logic for some pages like Welcome, Home etc. and other distinct pages which break out from the standard layout.
Currently it is already possible to escape from parent layouts in a nested page (by using @), so I am wondering what makes it different from the root one?

It was like this before and it lead to all kinds of subtle inconsistencies:

We can't guarantee that the root layout is the one that is rendered in case of an error. But we would like to lead it and the root error page eagerly to have it available in case of a catastrophic error + no network at this point
If you are on page X and an error occurs which would be rendered in a different root layout, is that what you want?
No clear place to put app-wide logic: Imagine you have two root layouts, someone else would come along and say "but I don't want to duplicate my app-wide logic in these two places"

It's also harder to grasp what layout runs, right now you know the root layout is always there, and you can only go upwards when inheriting or skipping layouts.
As you can see, we need to make a tradeoff (there's no solution that makes everyone happy since use cases are so differently) and we chose "root layout is always present". Yes it means you may need to import your layout UI into your error page, yes it means you either need to create a group or use if statements in your layout UI and load function, but that's an acceptable solution which everyone coming into the code base can easily understand.
Closing this since it's working as designed.

@dummdidumm I understand that there were tradeoffs to make. Can you let me know if I have understood the problem/solution correctly? 🥹
Problem
I have two groups: (maintenance) and (app).
I have a /maintenance page that I don't want to have the "normal" app/root layout. So I put maintenance.svelte in its own group. However, it is still affected by the route layout - it is impossible to break out of the root layout.
I can move the root layout into the (app) group, but then the error page has no more layout.
I can't move the error page into the (app) group because then root-level errors (e.g. 404) won't use the error page.
Solution
Keep root layout and have if statements that remove part of the markup for the /maintenance route.

Yes that's one possible solution. The other one would be to reuse the layout UI inside the root error page.

authors: dummdidumm maximedupre rchrdnsh tonprince


text:
Add unsafe-inline to CSP script-src when using nonces/hashes

Describe the problem
One of the recommendations by https://csp-evaluator.withgoogle.com regarding script-src is the following:

Consider adding 'unsafe-inline' (ignored by browsers supporting nonces/hashes) to be backward compatible with older browsers.

Describe the proposed solution
Add unsafe-inline after none-* to the script-src option by default, or provide a way for users to do it.
Alternatives considered
I tried adding it myself with this configuration:
const config = {
  kit: {
    csp: {
      directives: {
        'script-src': ['unsafe-inline']
      },
    }
  }
};

But this replaces the whole thing, and removes the nonce-*, so the resulting CSP would just be:
script-src 'unsafe-inline'

Importance
nice to have
Additional Information
No response

Do we know what "older browsers" is specifically? If it's IE11 which we don't support anyway we might as well skip this.
Also not sure if this should be given the enhancement or bug label depending on how we see that, so I gave it both.

Do we know what "older browsers" is specifically? If it's IE11 which we don't support anyway we might as well skip this.

@dummdidumm I think we do, nonces and hashes were added in CSP Level 2, so any browser that doesn't support CSP 2 or onwards would be what "older browsers" refers to here — see caniuse.com/contentsecuritypolicy2
As you can see in the caniuse chart, it's not just IE11, it's also Safari < 3.1, Chrome < 39, Edge < 14, and Firefox < 30, most notably.

I'm doubting we want to support several-year-old versions of browsers that update themselves by default, either.

authors: Conduitry aradalvand dummdidumm


text:
cookies.getAll()

Describe the problem
The supabase auth helpers store the session inside cookies to be able to authenticate on the server.
This session can get pretty big and therefore exceeds the cookies size limit.
To overcome this problem we are going to implement cookie chunking.
If you want to store data inside a cookie that exceeds the cookie size limit you have to either implement session id´s or cookie chunking (next auth does this).
Describe the proposed solution
add cookies.getAll()
the return type could be an iterator so something like this is possible:
for (const { name, value } of cookies.getAll()) {
  if (name.startsWith(cookieName)) {
     ...
   }
}

Alternatives considered
Use a "workaround" like this:
export function getChunkedCookie(cookies: Cookies, name: string, opts?: CookieParseOptions) {
	const value = cookies.get(name);
	if (value) {
		return value;
	}

	const chunks: string[] = [];

	for (let i = 0; ; i++) {
		const cookieName = `${name}.${i}`;
		const chunk = cookies.get(cookieName, opts);

		if (chunk) {
			chunks.push(chunk);
		} else {
			break;
		}
	}
	return chunks.length ? chunks.join('') : undefined;
}

Importance
nice to have
Additional Information
No response

yeah, this seems like a reasonable addition. PRs welcome :)

authors: Rich-Harris david-plugge


text:
docs: update adapter-node.md

Fix the npm ci command line for actual version
Extend ORIGIN samples for local development
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.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

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

Changesets

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

A note to other reviewers as to the difference here: if a package is listed in both dependencies and devDependencies the updated command will install it whereas the prior command will not. I suppose this seems like a reasonable change

the updated command will install it whereas the prior command will not

wait npm ci --prod will omit things that are in dependencies and devDependencies but npm ci --omit-dev won't? that seems... surprising

wait npm ci --prod will omit things that are in dependencies and devDependencies but npm ci --omit-dev won't? that seems... surprising

According to ChatGPT, which is what I asked when I was confused by the motivation for this PR. Not sure how much you trust it. It's told me things I know to be blatantly wrong before, so probably wouldn't hurt to verify :grin:

The docs don't mention a --prod flag at all, no idea where that came from
https://docs.npmjs.com/cli/v9/commands/npm-ci

Ah. npm install has a --production flag. Probably this used to be npm install and no one realized that npm was stupid enough to use completely different syntax when changing to npm ci

thanks!

authors: BCsabaEngine Rich-Harris benmccann


text:
fix: 9475 adapter node log request error

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. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

Fixes #9475
This change will additionally log an error if the getRequest function in the SSR handler fails.
I don't think we should test for an error log 😉
Will log an error similar to:

I haven't had time to dig into this, just wanted to point out that you should add a test to assert that the warning is being logged. Here's how:
https://github.com/sveltejs/kit/blob/b48d58e77a8f807075f875f1f1aea420ccec3760/packages/kit/test/apps/basics/test/test.js#L830-L844

My question with this is whether it would get annoying and fill the logs. I'm not that familiar with how logging is configured in JavaScript. This category of issue doesn't indicate any issue with the application and so I'm not sure that error is the appropriate console level to use here.

I've had a lot of trouble debugging an app running with the node adapter. There's literally nothing logged, ever. I think we need to go even further than this PR, but this is at least a good start to handle one kind of error condition. I've been googling for quite a while to better understand how to troubleshoot adapter-node apps and have come up empty-handed, and also tried asking on the Discord.
When you have a production application deployed with adapter-node, at some point you're going to want some logging for later troubleshooting. If you want to keep the noise down, we could use a log level or env var. I'm not quite sure what the typical JS idioms are here either, but I don't think complete silence is reasonable.

authors: benmccann dreitzner symbolicsorcerer tcc-sejohnson


text:
i18n link transform

Describe the problem
I'm currently working on i18n for SvelteKit.
One of the last hurdles would be to enable a language prefix for internal links.
Issue: https://github.com/sveltejs/kit/issues/553
Draft PR: https://github.com/sveltejs/kit/pull/1810
Describe the proposed solution
Add an option for i18n where the language of the current context can be passed to.
This in turn will prefix internal urls (from the html part) with the defined language prefix (eg. 'en', 'de', 'fr',...)
The language prefix is already accessible in most of SvelteKit use cases inside of it
Alternatives considered
I'll not sure if there are any intelligent ones...
Importance
would make my life easier

Hi, thank you for reaching out and looking into i18n
There is no compiler option for a language prefix and vite-plugin-svelte has no knowledge/concept of any routing nor manipulates components on it's own. (besides some small dev-only things to improve dx)
Please elaborate a bit why this is something that should be handled by vite-plugin-svelte and what exactly you want it to do.
An alternative could be to use a markup preprocessor to find links and update them accordingly. This can be added through svelte.config.js without having to change vite-plugin-svelte itself.
note:
i18n for sveltekit is still in draft, see also this issue: https://github.com/sveltejs/kit/issues/1274  (warning, also very long and some overlap with 553), so if there is something that vite-plugin-svelte can do to showcase your draft, it would end up in the recently added "experimental" section of the options until there is a finalized RFC for i18n that describes it in more detail.

@dominikg thank you for your quick answer :)
The problem:

any click me will not change when i18n changes
if we would do that through the router, we run into the problem of users trying to open links in new tabs
svelte kit does not really compile the code itself, so doing a transform after the fact gets way to complicated in my opinion

My though process:

sveltekit knows the current selected language
we also know about internal links
it should be "easy" to transform those at build time
as we hand the build of to vite => vite svelte plugin => svelte it sounds very conveniant to go down that route (pun intended)

Example
`
// IN
// file:

I believe this can and should be handled within sveltekit itself.
Static compile-time replacement like the one you outlined above could be done with a markup preprocessor. But how would that work with clientside routing when the user selects a different language?
Maybe some form of active href building ala   could work better?
I'm going to close this enhancement request as out-of-scope for vite-plugin-svelte, but it's great to see you getting the ball rolling for i18n in sveltekit and would be happy to discuss this further on discord.

@dominikg  thank you!
I am a fan of i18nRoute

authors: dominikg dreitzner

repo: sveltejs/vite-plugin-svelte


text:
Update to 2.x @sveltejs/vite-plugin-svelte result in [ERROR] [plugin externalize-deps]

Describe the bug
After updating to 2.x version, it started giving error about Failed to resolve entry for package
More or less, cannot find solution on my own, giving there error log, config files and repo for reproduction.
https://ptero.co/utydumyqis.coffee
https://ptero.co/irexovomaz.json
Reproduction URL
https://gitlab.com/ZekyTheWolf/laravel10
Reproduction

git clone git@gitlab.com:ZekyTheWolf/laravel10.git
composer install
cp .env.example .env
php artisan key:generate
npm install
npm run dev

Logs
✘ [ERROR] [plugin externalize-deps] Failed to resolve entry for package "@sveltejs/vite-plugin-svelte". The package may have incorrect main/module/exports specified in its package.json: No known conditions for "." specifier in "@sveltejs/vite-plugin-svelte" package

    node_modules/esbuild/lib/main.js:1365:27:
      1365 │         let result = await callback({
           ╵                            ^

    at packageEntryFailure (file:///E:/laragon/www/laravel10/node_modules/vite/dist/node/chunks/dep-3007b26d.js:22004:11)
    at resolvePackageEntry (file:///E:/laragon/www/laravel10/node_modules/vite/dist/node/chunks/dep-3007b26d.js:21999:9)
    at tryNodeResolve (file:///E:/laragon/www/laravel10/node_modules/vite/dist/node/chunks/dep-3007b26d.js:21736:20)
    at file:///E:/laragon/www/laravel10/node_modules/vite/dist/node/chunks/dep-3007b26d.js:62257:40
    at requestCallbacks.on-resolve (E:\laragon\www\laravel10\node_modules\esbuild\lib\main.js:1365:28)
    at handleRequest (E:\laragon\www\laravel10\node_modules\esbuild\lib\main.js:727:19)
    at handleIncomingPacket (E:\laragon\www\laravel10\node_modules\esbuild\lib\main.js:749:7)
    at Socket.readFromStdout (E:\laragon\www\laravel10\node_modules\esbuild\lib\main.js:677:7)
    at Socket.emit (node:events:512:28)
    at addChunk (node:internal/streams/readable:324:12)

  This error came from the "onResolve" callback registered here:

    node_modules/esbuild/lib/main.js:1287:20:
      1287 │       let promise = setup({
           ╵                     ^

    at setup (file:///E:/laragon/www/laravel10/node_modules/vite/dist/node/chunks/dep-3007b26d.js:62246:27)
    at handlePlugins (E:\laragon\www\laravel10\node_modules\esbuild\lib\main.js:1287:21)
    at buildOrServeImpl (E:\laragon\www\laravel10\node_modules\esbuild\lib\main.js:974:5)
    at Object.buildOrServe (E:\laragon\www\laravel10\node_modules\esbuild\lib\main.js:780:5)
    at E:\laragon\www\laravel10\node_modules\esbuild\lib\main.js:2132:17
    at new Promise (<anonymous>)
    at Object.build (E:\laragon\www\laravel10\node_modules\esbuild\lib\main.js:2131:14)
    at build (E:\laragon\www\laravel10\node_modules\esbuild\lib\main.js:1978:51)
    at bundleConfigFile (file:///E:/laragon/www/laravel10/node_modules/vite/dist/node/chunks/dep-3007b26d.js:62210:26)

  The plugin "externalize-deps" was triggered by this import

    vite.config.ts:4:39:
      4 │ import { svelte, vitePreprocess } from '@sveltejs/vite-plugin-svelte';
        ╵                                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

failed to load config from E:\laragon\www\laravel10\vite.config.ts
error when starting dev server:
Error: Build failed with 1 error:
node_modules/esbuild/lib/main.js:1365:27: ERROR: [plugin: externalize-deps] Failed to resolve entry for package "@sveltejs/vite-plugin-svelte". The package may have incorrect main/module/exports specified in its package.json: No known conditions for "." specifier in "@sveltejs/vite-plugin-svelte" package
    at failureErrorWithLog (E:\laragon\www\laravel10\node_modules\esbuild\lib\main.js:1604:15)

System Info
System:
    OS: Windows 10 10.0.22621
    CPU: (16) x64 AMD Ryzen 7 5800H with Radeon Graphics
    Memory: 7.88 GB / 15.86 GB
  Binaries:
    Node: 19.5.0 - C:\Program Files\nodejs\node.EXE
    npm: 9.4.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.22621.1265.0), Chromium (110.0.1587.46)
    Internet Explorer: 11.0.22621.1
  npmPackages:
    @sveltejs/vite-plugin-svelte: ^2.0.0 => 2.0.2
    vite: ^4.0.0 => 4.1.1

having the same issue

Please check https://github.com/sveltejs/vite-plugin-svelte/issues?q=is%3Aissue+label%3Acommonjs+is%3Aclosed for similar issues. vite-plugin-svelte 2.0 doesn't ship CJS anymore so your setup needs to be adjusted as well.

Please check https://github.com/sveltejs/vite-plugin-svelte/issues?q=is%3Aissue+label%3Acommonjs+is%3Aclosed for similar issues. vite-plugin-svelte 2.0 doesn't ship CJS anymore so your setup needs to be adjusted as well.

@bluwy Not helpfull at all... I tried what was said, add to package.json "type": "module", just resulted in problem with laravel plugin...
And after adding config that was provided in FAQ, still got same error...
So, i decided that it would be best to stick with version 1.4.x until there will be better provided support.

For those who come here using the laravel-vite-plugin, this is what helps, awaiting for the Laravel team to come up with ES module instead of CommonJS.

@meduzen thanks, this helped.
Also, its not required to add "type": "module"...
This working well enaugh :D
import { defineConfig } from 'vite';
import laravel from 'laravel-vite-plugin';

import { svelte } from '@sveltejs/vite-plugin-svelte';
const vitePreprocess = import('@sveltejs/vite-plugin-svelte').then(m => m.vitePreprocess())
import path from 'path';

export default defineConfig(({ mode }) => {
	return {
		plugins: [
            laravel({
                input: [
					'resources/scripts/main.ts'
				],
                refresh: true,
            }),
            svelte({
				preprocess: {
					//@ts-ignore
				    script:async (options) => (await vitePreprocess).script(options),
					//@ts-ignore
				    style:async (options) => (await vitePreprocess).style(options),
				}
			}),
		],

		server: {
			cors: mode === "development",
		},

		resolve: {
			alias: {
				'@Layouts':  path.resolve(__dirname, './resources/layouts/'),
				'@Components':  path.resolve(__dirname, './resources/components/'),
			}
		},

		optimizeDeps: {
			exclude: [
				'vite-plugin-svelte'
			]
		}
	}
})

authors: ZekyTheWolf bartektelec bluwy meduzen


text:
Is it possible to pass the event?

Is it possible to pass the event to the c# side and call a preventDefault() on it from c#?

Currently I didn't find any way to do this. The interaction in Blazor between JS events and C# will change in the future, the API currently is not complete. In the future they will extend the Blazor API to be able to call preventDefault() from C# - please see here.


text:
removal of spaces introduced on version 1.3.0 creates corrupted SVG?

Hi, since the new change in 1.3.0
SVGO now removes unnecessary spaces after arcto path command flags.
I am seeing a pattern where striping the spaces makes SVGO output corrupted.
I am using SVGO to optimize for react-native svgs along with svgr
You can play and see it in action with SVGR playground with SVGO enbaled
E.g I have the following source file
<svg xmlns="http://www.w3.org/2000/svg" width="17" height="17" viewBox="0 0 17 17">     <g fill="none" fill-rule="evenodd">         <path d="M-2-6h24v24H-2z"/>         <path fill="#FFF" d="M.45 5.34L15.945.175a.695.695 0 0 1 .88.88L11.66 16.55a.695.695 0 0 1-1.287.082L7.122 9.878.368 6.627A.695.695 0 0 1 .45 5.34z"/>     </g> </svg>
running it with  version 1.2.0
will produce
 <Svg width={17} height={17} {...props}><G fill="none" fillRule="evenodd"><Path d="M-2-6h24v24H-2z" /><Path fill="#FFF" d="M.45 5.34L15.945.175a.695.695 0 0 1 .88.88L11.66 16.55a.695.695 0 0 1-1.287.082L7.122 9.878.368 6.627A.695.695 0 0 1 .45 5.34z" /></G></Svg
while on version 1.3.0
<Svg width={17} height={17} {...props}><G fill="none" fillRule="evenodd"><Path d="M-2-6h24v24H-2z" /><Path fill="#FFF" d="M.45 5.34L15.945.175a.695.695 0 01.88.88L11.66 16.55a.695.695 0 01-1.287.082L7.122 9.878.368 6.627A.695.695 0 01.45 5.34z" /></G></Svg>
checking the diffs it indeed removed spaces
(left is 1.20, right 1.3.0)

But the issue is that react-native-svg isn't able to parse the outputted svg, on android it will crash, and on IOS it will show the following warning

I am not sure if the issue is with svgo or actually a problem of react-native-svg, but would love to get your feedback on which direction the issue originates from.

https://github.com/svg/svgo/issues/1137#issuecomment-518351171

Having the exact same issue here. Version 1.3.0 is removing some nececary spaces which is breaking the svg causing problems with animating the svg:
Before (version 1.2.x):
"M984.04 515.32A7543.73 7543.73 **0 0 0 949** 481l36.67-35.25v-8.88L885 507c4.94 10.53 19.88 34.65 52.42 36.04 21.32.35 39.83-9.24 48-20.98l-1.38-6.74z"
After (version 1.3.0):
"M984.04 515.32A7543.73 7543.73 0 **00949** 481l36.67-35.25v-8.88L885 507c4.94 10.53 19.88 34.65 52.42 36.04 21.32.35 39.83-9.24 48-20.98l-1.38-6.74z"

Why don't SVGO developers deactivate basic noSpaceAfterFlags and finally release an update that fixes this tedious problem that plagues everyone?

authors: barakd f-liva grig0ry wigglepixel

repo: svg/svgo


text:
🛑 Ingroup is down

In c114ed1, Ingroup (https://ingroup.biz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ingroup is back up in 24082c4 after 19 minutes.

repo: svilaa/websites-status


text:
Why the problem of KBAT data leakage is not reflected in your code

I want to know whether the result reported in your paper about KBAT is the result after fix. I only saw the content of the evaluation protocol modified in the code, and did not see the modification of the valid_triples_dict you mentioned, thanks.

Yes, the results are reported after modifying both the evaluation script and the test leakage problem. Thanks for pointing that out. We might have missed that in the version which we made publicly available.

Thank you for your reply. Based on the "they shouldn't use valid_triples_dict (all triples in train, dev, and test) in this line, but should only use training data" you mentioned in other issues, can I understand that it is enough to change the "self.valid_triples_dict = {j: i for i, j in enumerate(self.train_triples + self.validation_triples + self.test_triples)}" in the code to "self.valid_triples_dict = {j: i for i, j in enumerate(self.train_triples )}"?
There is another problem. I noticed that you have commented out two lines of code in  "main.py". In our experiment, this operation will cause loss to fail to converge. Is it possible that you sort out the omissions of the code or should you really comment it out? If it should be commented out, can you tell me why? Thank you.
#main.py
line198	# loss.backward()
line199	# optimizer.step()

Thanks for pointing that out. I have updated the code, please have a look.


text:
Many tests

This library didn't had any automatic tests. As of today it made a good start with all the tests.
And resolved the following issues:

Fixed #45
Fixed #46
Fixed (partially) #47

:tada: This PR is included in version 2.0.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

repo: svrooij/node-sonos-ts


text:
Run in Thread not working

Please answer these questions as part of your new issue.
Which version of Python are you using?
Python 2.7 and Python 3.5
Which OS and version are you running?
Raspbian GNU/Linux 9 (stretch)
Is SPI enabled?
Yes
Are you trying to read/write a Mifare Classic card?  (This is currently unsupported)
No
When I try to run the example in a Thread the python program gets terminated and nothing happens. I don't get any output at all. The process just stops.
Example code
class NfcTagMonitor(Thread):
    '''The tag monitor class definition.
    '''

    def __init__(self, nfc_tag_hold=True):
        """
        Constructor.
        """
        Thread.__init__(self)
        self._stop_event = Event()

        self.lastTag = None
        self.mifare = nxppy.Mifare()

    def run(self):
        """
        The method to run in an additional thread.
        """
        logger.info("NfcTagMonitor: Run the cycle ...")
        while True:
            # reading the card id
            try:
                uid = self.mifare.select()
                if uid != self.lastTag:
                    logger.debug("Selected the following id: %s", uid)
                    self.lastTag = uid
                    # do something ...
            except nxppy.SelectError as se:
                # SelectError is raised if no card is in the field.
                logger.debug(
                    "Had an issue selecting the id. Probably the NFC tag has been removed: %s"
                    , se)
            time.sleep(0.5)

# outer class
self.nfc_monitor = NfcTagMonitor()
self.nfcTagMonitor.daemon = True
self.nfcTagMonitor.start()

Figured it out myself.

repo: svvitale/nxppy


text:
Incorrect link to community package up to 10

Might be a copy paste error: https://github.com/sw-yx/codingcareer.com/blob/master/src/components/FAQ.svelte#L156
Should be -10 instead of -5

eeps thanks

authors: Ang-YC sw-yx


text:
loosing $ref field data when using isResolveFully option

Good day!
I'm using OpenAPIV3Parser
I'm trying to parse my openapi: "3.0.2" yaml file
When I have
parseOptions.isResolveFully = false
I get
Services
type: array
items:
  $ref: '#/components/schemas/Service'

when i set
parseOptions.isResolveFully = true
I get data without any mentioning of the head of the reference (Service):
Services
type: array
items:
  required:
  - artifactId
  - description
  - groupId
  - id
  - name
  - version
  properties:
    id:
      type: integer
      format: int64
      readOnly: true
    name:
      type: string
    description:
      type: string
    groupId:
      type: string
    artifactId:
      type: string
    version:
      pattern: (0|(?:[1-9]\d*))(?:\.(0|(?:[1-9]\d*))(?:\.(0|(?:[1-9]\d*)))?(?:\-([\w][\w\.\-_]*))?)?
      type: string

reference field becomes null. Is there any way to preserve the information about what specificaly referenced type has been Resolved Fully when option is true.

In io/swagger/v3/parser/OpenAPIV3Parser.java, the line 68. it has an if condition to check
                        if (options.isResolveFully()) {
                            result.setOpenAPI(resolver.resolve());
                            new ResolverFully(options.isResolveCombinators()).resolveFully(result.getOpenAPI());

since you set isResolveFully = false, this wont excute and resolveFully is catually the function uncondense the reference object.

Parser uses options as a way to personalize the behavior while parsing:
ResolveFully:
After references are resolved (brought back from the remote location and added to the internal components location), then maybe it is needed that the resolved objects are no longer referenced, but put at the same place they were referenced initially, meaning that in the spec there will not be anymore referenced objects, all will be put inline in the place they are being called, replacing the reference it self. This will make the spec longer.

authors: gracekarina lDummyl zhang435

repo: swagger-api/swagger-parser


text:
Issues with parameter annotation (1.5.0)

When we have a method with more than one parameter of the same type the same @ApiParam fields are applied to both in the swagger json.
I think the reason for this is the following code from PlayReader.java, line 537-548 in the current release):
private List<Annotation> getParamAnnotations(Class<?> cls, Method method, String simpleTypeName) {
    Type[] genericParameterTypes = method.getGenericParameterTypes();
    Annotation[][] paramAnnotations = method.getParameterAnnotations();
    for (int i = 0; i < genericParameterTypes.length; i++) {
        final Type type = TypeFactory.defaultInstance().constructType(genericParameterTypes[i], cls);
        String paramClassName = ((JavaType)type).getRawClass().getSimpleName();
        if (simpleTypeName.equalsIgnoreCase(paramClassName)) {
            return Arrays.asList(paramAnnotations[i]);
        }
    }
    return null;
}

In this code the first annotation that matches the parameter TYPE is returned, making our specification not work in the following example:
public Result accept(
  @ApiParam(value = "Id of the settlement to fetch a file from") @PathParam("id") String id,
  @ApiParam(value = "File id of the file to fetch") @PathParam("fid") String fid) {
return play.mvc.Results.TODO;

}
Since it will return this JSON:
"parameters" : [ {
      "name" : "id",
      "in" : "path",
      "description" : "Id of the settlement to fetch a file from",
      "required" : true,
      "type" : "string",
      "default" : ""
    }, {
      "name" : "fid",
      "in" : "path",
      "description" : "Id of the settlement to fetch a file from", <-- This is wrong
      "required" : true,
      "type" : "string",
      "default" : ""
    },

Wouldn't it be better to match with field position in method declaration with fallback to parameter name and finally fallback to type? Another way would be to use the @PathParam or @QueryParam annotations to bind correct parameter to correct @ApiParam.
Or is this "working as intended"? In other words, we should type them as different types (not a good solution).

Opened a Pull request for fixing this one https://github.com/swagger-api/swagger-play/pull/48

Will close this one.

repo: swagger-api/swagger-play


text:
Please add support for shopspring/decimal

I have an error when I run swag init.
product.go
type(

        Product struct {
		ID        int      `json:"id"`
		Offers    []*Offer `json:"offers"`
	}

	Offer struct {
		ID           int             `json:"id"`
		SKU          string          `json:"sku"`
		Price        decimal.Decimal `json:"price"`
		PriceWithVAT decimal.Decimal `json:"price_with_vat"`
		Currency     string          `json:"currency"`
		Stock        int             `json:"stock"`
		Merchant     *Merchant       `json:"merchant"`
	}

)

domain.go
// API List products godoc
// @Tags products
// @Summary List products
// @Produce  json
// @Success 201 {object} products.Product ""
// @Failure 400 {object} errors.ErrorResponse
// @Failure 500 {object} errors.ErrorResponse
// @Router /products/ [get]

Error:
Decimal is not supported. but it will be set with string temporary.
Please report any problems.Decimal is not supported.
but it will be set with string temporary.
Please report any problems.2018/05/08 11:31:42 Generating products.Merchant
panic: not supported&{773 0xc4204fd830}

As you notice, I am having problems with type Decimal, but also with pointer (to Merchant) inside Offer struct. Can you also add support for pointers?

OK. I check.
And I add plugin for special types.

I support ptr slice and Decimal.
I don't understand problem in products.Merchant.
How do you have struct. Please more info.

Probably all was solved.
Please wait for the merge.

@jmcalves275  Fix via #113. please update swag to  the latest version and reopen this issue if have any problems.
And we will create plugin function asap to support for any specific type that is not basic types. 🎉 🎉

repo: swaggo/swag


text:
testimonial display

Is your feature request related to a problem? Please describe.
Addition of testimonial box feature
Describe the solution you'd like.
Just like various games and features, I am willing to add a box for testimonial.
Describe alternatives you've considered.
NA
Add any other context or screenshots about the feature request here.
No response

@Anamika-Ratna Than you for providing your insight but it is not required as of now.

authors: Anamika-Ratna swapnilsparsh


text:
EOS registration on swap.online

Nik ✨, [11.10.18 12:37]
@diademnetwork
на swap.online после нажатия на кнопку buy account и когда нет денег,
показывается аккаунт и сохраняется в localstorage приватник и аккаунт
но explorer его не видит)

ошибка не исправлена на текущем тестнете, даже если деньги есть пишет что ак активирован, но екслорер его не видит.

https://github.com/swaponline/swap.react/pull/1204

authors: nikdementev noxonsu


text:
bugfix/8-fix-stdio-test

Somehow not passing--this should be fixed.

Forgot to close...

repo: swarm-robotics/rcsw


text:
Improve DMA-BUF lifetime docs

wlr_buffer_get_dmabuf's behaviour avoids exporting the buffer as a DMA-BUF over and over each time we want to import it (e.g. to KMS or EGL).
cc @any1

Thanks!

authors: ddevault emersion

repo: swaywm/wlroots


text:
Profile update request view: fix couple of issues

Move fields not being saved to DB to the bottom of the form
Separate these fields with long horizontal row saying
"These aren't saved"
Change "N/A" to "Not available"
Add some '|default:"—"' to the fields that didn't have this filter

This fixes #538 but in a different way (see attachment).

This PR will cause conflict once #528 is merged.

@maneesha @gvwilson I changed your concept of 3 columns a little bit. Since only 3 fields were not overlapping, I moved them to sort-of a new table down below. See the attachment above and tell me if you like this or not.
@gvwilson the "—" corresponds to empty value being stored, while "Not available" means "that model doesn't have this field so we can't compare". For example, with Person model we don't store ORCID ID.

Will the order of field display be the same for all persons, all the time, with this change? Having fields move up or down the page based on availability of information will be really hard to track.

@gvwilson the order will stay the same on all profile update request details pages (ie. the ones with table from screen shot), unless someone changes that table in template.

@gvwilson rebased the branch.

@gvwilson could you review?

authors: gvwilson pbanaszkiewicz

repo: swcarpentry/amy


text:
Don't include swift-latest symbolic link in available toolchains

When you install a swift snapshot toolchain on macOS it setups up a swift-latest.xctoolchain symbolic link to point to it. We shouldn't include this symbolic link in the list of toolchains available when displaying the Select toolchain... menu

Is there a reason you want to remove it? I feel like it's useful for people who always want to point their VSCode at the latest public Swift toolchain that they've downloaded.

If we are going to keep it we should change the menu item to be Latest Installed Toolchain, or something similar, and verify the toolchain it is pointing to exists

authors: adam-fowler matthewbastien

repo: swift-server/vscode-swift


text:
Provide build settings for version-specific package manifests

Fixes #1670
rdar://136014520

@swift-ci Please test

repo: swiftlang/sourcekit-lsp


text:
[DebugInfo] Fix tests to downstream "specification" attribute

The "specification_of" attribute in LLVM IR was renamed to "specification". Adapt the  tests to the new name.

https://github.com/swiftlang/llvm-project/pull/9600
@swift-ci smoke test

repo: swiftlang/swift


text:
[DebugInfo] Fix debug info round tripping of types inside functions

Types with @_originallyDefinedIn cannot be round tripped,
Types declared inside functions have their mangling affected by the function signature. If the generic signature mentions an @_originallyDefinedIn type, the type inside the function cannot be round tripped either.
This commit disables round tripping for this scenario.

@swift-ci test

@augusto2112 It seems like I still locally get a crash with this PR. I will double-check.
Failed to reconstruct type for $s11SwiftFormat24DocumentationCommentTextV13extractedFromACSg08CompilerA6Syntax6TriviaV_tcfc4LineL_VD
Original type:
(struct_type decl="SwiftFormat.(file).DocumentationCommentText.init(extractedFrom:).Line@S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Core\\DocumentationCommentText.swift:56:12")
Please submit a bug report (https://swift.org/contributing/#reporting-bugs) and include the crash backtrace.
Pass '-Xfrontend -disable-round-trip-debug-types' to disable this assertion.
Please submit a bug report (https://swift.org/contributing/#reporting-bugs) and include the crash backtrace.
Stack dump:
0.      Program arguments: C:\\Users\\hiroshi\\source\\b\\5\\bin\\swiftc.exe -frontend -c S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\API\\Configuration+Default.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\API\\Configuration.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\API\\DebugOptions.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\API\\Finding.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\API\\FindingCategorizing.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\API\\Indent.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\API\\Selection.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\API\\SwiftFormatError.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\API\\SwiftFormatter.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\API\\SwiftLinter.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Core\\Context.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Core\\DocumentationComment.swift -primary-file S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Core\\DocumentationCommentText.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Core\\Finding+Convenience.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Core\\FindingEmitter.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Core\\FormatPipeline.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Core\\FunctionDeclSyntax+Convenience.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Core\\ImportsXCTestVisitor.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Core\\LazySplitSequence.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Core\\LintPipeline.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Core\\ModifierListSyntax+Convenience.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Core\\Parsing.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Core\\Pipelines+Generated.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Core\\RememberingIterator.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Core\\Rule.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Core\\RuleBasedFindingCategory.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Core\\RuleMask.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Core\\RuleNameCache+Generated.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Core\\RuleRegistry+Generated.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Core\\RuleState.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Core\\SyntaxFormatRule.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Core\\SyntaxLintRule.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Core\\SyntaxProtocol+Convenience.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Core\\Trivia+Convenience.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Core\\WithAttributesSyntax+Convenience.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Core\\WithSemicolonSyntax.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\PrettyPrint\\Comment.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\PrettyPrint\\Indent+Length.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\PrettyPrint\\PrettyPrint.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\PrettyPrint\\PrettyPrintBuffer.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\PrettyPrint\\PrettyPrintFindingCategory.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\PrettyPrint\\Token.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\PrettyPrint\\TokenStreamCreator.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\PrettyPrint\\Verbatim.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\PrettyPrint\\WhitespaceFindingCategory.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\PrettyPrint\\WhitespaceLinter.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\AllPublicDeclarationsHaveDocumentation.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\AlwaysUseLiteralForEmptyCollectionInit.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\AlwaysUseLowerCamelCase.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\AmbiguousTrailingClosureOverload.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\AvoidRetroactiveConformances.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\BeginDocumentationCommentWithOneLineSummary.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\DoNotUseSemicolons.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\DontRepeatTypeInStaticProperties.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\FileScopedDeclarationPrivacy.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\FullyIndirectEnum.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\GroupNumericLiterals.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\IdentifiersMustBeASCII.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\NeverForceUnwrap.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\NeverUseForceTry.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\NeverUseImplicitlyUnwrappedOptionals.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\NoAccessLevelOnExtensionDeclaration.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\NoAssignmentInExpressions.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\NoBlockComments.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\NoCasesWithOnlyFallthrough.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\NoEmptyLineOpeningClosingBraces.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\NoEmptyTrailingClosureParentheses.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\NoLabelsInCasePatterns.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\NoLeadingUnderscores.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\NoParensAroundConditions.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\NoPlaygroundLiterals.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\NoVoidReturnOnFunctionSignature.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\OmitExplicitReturns.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\OneCasePerLine.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\OneVariableDeclarationPerLine.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\OnlyOneTrailingClosureArgument.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\OrderedImports.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\ReplaceForEachWithForLoop.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\ReturnVoidInsteadOfEmptyTuple.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\TypeNamesShouldBeCapitalized.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\UseEarlyExits.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\UseExplicitNilCheckInConditions.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\UseLetInEveryBoundCaseVariable.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\UseShorthandTypeNames.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\UseSingleLinePropertyGetter.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\UseSynthesizedInitializer.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\UseTripleSlashForDocumentationComments.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\UseWhereClausesInForLoops.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Rules\\ValidateDocumentationComments.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Utilities\\FileIterator.swift S:\\SourceCache\\swift-format\\Sources\\SwiftFormat\\Utilities\\URL+isRoot.swift -emit-module-path Sources\\SwiftFormat\\CMakeFiles\\SwiftFormat.dir\\Core\\DocumentationCommentText.swift.swiftmodule -emit-module-doc-path Sources\\SwiftFormat\\CMakeFiles\\SwiftFormat.dir\\Core\\DocumentationCommentText.swift.swiftdoc -emit-module-source-info-path Sources\\SwiftFormat\\CMakeFiles\\SwiftFormat.dir\\Core\\DocumentationCommentText.swift.swiftsourceinfo -emit-dependencies-path Sources\\SwiftFormat\\CMakeFiles\\SwiftFormat.dir\\Core\\DocumentationCommentText.swift.obj.d -target x86_64-unknown-windows-msvc -disable-objc-interop -sdk "S:/Program Files/Swift/Platforms/Windows.platform/Developer/SDKs/Windows.sdk" -I S:\\b\\23\\swift -I S:\\SourceCache\\swift-markdown\\Sources\\CAtomic\\include -I S:\\b\\5\\.\\lib\\swift\\host -I "S:\\Program Files\\Swift\\Toolchains\\0.0.0+Asserts\\usr\\include\\cmark_gfm" -I "S:\\Program Files\\Swift\\Toolchains\\0.0.0+Asserts\\usr\\include\\cmark_gfm_extensions" -g -module-link-name SwiftFormat -O -D SwiftFormat_EXPORTS -in-process-plugin-server-path C:\\Users\\hiroshi\\source\\b\\5\\bin\\SwiftInProcPluginServer.dll -plugin-path C:\\Users\\hiroshi\\source\\b\\5\\bin -autolink-library oldnames -autolink-library msvcrt -Xcc -D_MT -Xcc -D_DLL -parse-as-library -module-name SwiftFormat -num-threads 32 -o Sources\\SwiftFormat\\CMakeFiles\\SwiftFormat.dir\\Core\\DocumentationCommentText.swift.obj
1.      Swift version 6.2-dev (LLVM aed73c6d65289c8, Swift ae88aaca8f76c02)
2.      Compiling with effective version 5.10
3.      While evaluating request IRGenRequest(IR Generation for file "S:\SourceCache\swift-format\Sources\SwiftFormat\Core\DocumentationCommentText.swift")
4.      While emitting IR SIL function "@$s11SwiftFormat24DocumentationCommentTextV13extractedFromACSg08CompilerA6Syntax6TriviaV_tcfC".
 for 'init(extractedFrom:)' (at S:\SourceCache\swift-format\Sources\SwiftFormat\Core\DocumentationCommentText.swift:54:10)

@swift-ci test

@swift-ci test

@hjyamauchi thanks for testing, could you try again with the latest commit?

@swift-ci smoke test

@hjyamauchi thanks for testing, could you try again with the latest commit?

@augusto2112 Will do. I also added a reduced test here: https://github.com/swiftlang/swift/issues/78326#issue-2753360747

@hjyamauchi thanks for testing, could you try again with the latest commit?

@augusto2112 Will do. I also added a reduced test here: #78326 (comment)

@augusto2112 The updated PR doesn't seem to fix the issue for me.

That's surprising, let me check again if I'm missing some other case...

@augusto2112 It might be useful to use the reduced test from here: https://github.com/swiftlang/swift/issues/78326#issue-2753360747

@hjyamauchi thanks, I was able to use your reproducer. It actually was not related to @_originallyDefinedIn as I thought, but something else entirely. I'm running the test suite locally and hopefully this will be the last iteration of the fix.

@swift-ci test

@hjyamauchi if you're around this should work with your test case now :)

@swift-ci smoke test

@hjyamauchi if you're around this should work with your test case now :)

Testing

It looks good!