Search bar in translations

It will be good to have a search bar in translations.
With a big list finding gets difficult so either a search bar or a tree structure will be helpful.

Are you talking about this UI?

Until there's a better alternative, remember you can use incremental search (type the first few letters in quick succession, i.e. "D", "A", and the selection will jump to items that start with "da-" in the list).

Along these lines, is there a way to search the valid translation languages (list) in advanced scripting?

@m-kovalsky Use this script:
using System.Globalization;

var cultures = CultureInfo.GetCultures(CultureTypes.SpecificCultures).Select(c => c.Name);

cultures.Output();


Add Copy Paste to Docs Site

Makes life easier for people wanting to quickly grab an icon short code

hooray!


Closing braces on the same line

Is it possible to change folding style to something idea-like with closing braces on the same line as opening?
Expected:
function add(x, y) { ... }

Actual:
function add(x, y) { ...
}

UP

@alexdima up

Duplicate of https://github.com/microsoft/vscode/issues/3352


fix(package): support Node v22 to allow deploying on vercel

TL;DR
Downgraded Node.js version from 23.3.0 to 22.12.0 across all project configurations and documentation.
What changed?

Updated Node.js version to 22.12.0 in Dockerfile, .nvmrc, and package.json files
Modified documentation in README files (ES, KOR, PTBR, RU) to reflect new Node.js requirement
Updated GitPod configuration to use Node.js 22.12.0
Commented out branch deployment trigger in GitHub Actions workflow

How to test?

Run nvm install v22.12.0
Run nvm use v22.12.0
Delete node_modules and package-lock.json
Run pnpm install
Verify application builds and runs successfully
Confirm Docker build completes without errors

Why make this change?
Node.js 23.3.0 is a newer release that may have compatibility issues with some dependencies. Downgrading to the more stable 22.12.0 version ensures better compatibility and reliability across the project's ecosystem.

#37  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Merge activity

Dec 29, 7:34 AM EST: A user started a stack merge that includes this pull request via Graphite.


Typo in fblualib/fblualib/thrift/README.md

There is a typo in the README.md file. thrift.from_file should take the file as its parameter.
-- from open io.file object
local f = io.open('/tmp/foo')
local obj = thrift.from_file(obj)

This should be
-- from open io.file object
local f = io.open('/tmp/foo')
local obj = thrift.from_file(f)

thanks, fixed readme via commit: https://github.com/facebook/fblualib/commit/6cc3a55946b81cbe00184195a781baafcce42c28


Smaller TAA fixes

Extracted the easy stuff from #8974 .
Problem

Commands from update_previous_view_projections would crash when matching entities were despawned.
TaaPipelineId and draw_3d_graph module were not public.
When the motion vectors pointed to pixels that are now off screen, a smearing artifact could occur.

Solution

Use try_insert command instead.
Make them public, renaming to TemporalAntiAliasPipelineId.
Check for this case, and ignore history for pixels that are off-screen.

Nitpick, but enlarging of names should be discouraged unless it is an new/bespoke concept or term, where as TAA is an industry standard and can be found with a simple google search if someone doesn't know what it stands for.

If we do end up renaming things, do we also need a migration guide section? Or does this not apply because of experimental?

The only renames are currently internal, so it's not a breaking change :)

I won't have time to test this later this week so I'm testing it now given that it already has an approval and is on the milestone.
This PR does not fix the edge smearing issue:

@DGriffin91 thanks for the test! Should be fixed now. The approach I was using before doesn't work with the way TAA is currently setup, so when I pulled out of the larger changes it wasn't working.

Tested with the example from #10200 and the obvious edge blurring is no longer present. Can't really comment beyond that.


No module named 'TDNN'

Using Python 3.5
I tried to run this project with its basic settings and cannot even run main.py as it claims there's a missing module.
Though init.py in the models folder says it can't find TDNN, I verified that the file is indeed there.
C:\Users\dbishop\Desktop\lstm-char-cnn-tensorflow-master>python main.py --dataset ptb
Traceback (most recent call last):
File "main.py", line 5, in
from models import LSTMTDNN
File "C:\Users\dbishop\Desktop\lstm-char-cnn-tensorflow-master\models_init_.py", line 1, in
from TDNN import TDNN
ImportError: No module named 'TDNN'

Issue seems to come from using python 3. The project claims to be python3 compatible, but I see xrange instead of range all over, and had to use python3-style imports to get around the issue above.
How do I use this project with python 3?

@Lolologist
Same issue occurs for me. Seems to be import issue. Solving this by:
Change:
from TDNN import TDNN
to:
from .TDNN import TDNN
there are also some other import statements you have to change too

@Lologist: I use python3.5, and still got the import error: No module named 'base', after following your suggestions.


Usage 'N4BiasFieldCorrection' utilty

I'm trying to use the ANTs 'N4BiasFieldCorrection' utility on a neonatal T2-weighted MR image of the brain. When I simply run 'N4BiasFieldCorrection' with no options, I see the command usage/options. However, I can't seem to run it on an image using the following command shown below. I do not have a binary mask image.
jimalex>N4BiasFieldCorrection -c [100x100x100x100,0] -b [200] -s 3 -i T2image.nii.gz -o T2image_N4.nii.gz
N4BiasFieldCorrection: No match.

I suspect you are running a c shell, which doesn't like square brackets. Try:
bash
N4BiasFieldCorrection -c [100x100x100x100,0] -b [200] -s 3 -i T2image.nii.gz -o T2image_N4.nii.gz

Indeed. That worked like a charm, Thnx.

Someone on Sourceforge reported the same issue, apparently quoting the string also helps.


Support Slack as the Messenger implemetation

Slack is a group chat system as HipChat or Skype.  This issue is to support slack client as the Messenger implementation in Walter.

Close with #65


Allow log level to be configurable

I was discussing with @st0012 how we might prevent $stderr output appearing when running the tests. He suggested:

. A better way may be introducing logging level to LSP output. And in testing we just increase the logging level to warn. (this cases’s message is likely info or debug)

Once we have that, we can add some detailed messages at debug level, which will make debugging easier

I love this idea. We should be relatively low effort if we just use Ruby's logger library and set that as a singleton somewhere.


[Documentation] Defaulting guidelines

How to categorize this PR?

/area documentation
/kind technical-debt
What this PR does / why we need it:
Add documentation for the followed convention while writing defaulting functions and its unit test.
Which issue(s) this PR fixes:
Part of https://github.com/gardener/gardener/issues/7312
Special notes for your reviewer:
/cc @Kostov6
Release note:

NONE

/retest


Storybook : Product Details Component Images

Description
Images for Storybook : Product Details Component
Fixes # (issue)
How to test?
Please provide a short summary how your changes can be tested?
Checklist

[X] I have performed a self-review of my own code
[X] I have followed the name conventions for CSS Classnames and filenames, Components names and filenames, Style filenames, if you are in doubt check the the project README.MD and here https://github.com/HackYourFuture-CPH/curriculum/blob/master/review/review-checklist.md
[X] I have commented my code, particularly in hard-to-understand areas, if you code was simple enough mark the box anyway
[X] I have made corresponding changes to the documentation, if you code was simple enough mark the box anyway
[X] This PR is ready to be merged and not breaking any other functionality

This PR has nothing to do with Storybook so don't use that label for it.
I don't see a need to add these images when you can use CSS to create them.
Check these examples Heart https://codepen.io/raubaca/pen/xZQZjV Arrows https://codepen.io/MaryG/pen/WbvRrz
Please close the PR and add CSS to your Component (#82)

Okey Daniel I will update codes


Catch GraphQL execution errors.

Closes https://github.com/ashkan18/graphlient/issues/31.
Renamed errors to class names with Error in the end.
See https://github.com/github/graphql-client/pull/132 and https://github.com/exAspArk/graphql-errors/issues/2

👍


Godot is not finding methods in script (3.6.rc1)

Tested versions
3.6.rc1.official.cfc4a0eff
System information
Mac Sonoma 14.4.1 (23E224)
Issue description
I was testing GUT with 3.6.rc1.official.cfc4a0eff.  Upon first launch it complained that it could not find a setter in gut.gd at line 38:
error(38,1):  The setter function isn't defined.

The setter exists.  I commented out everything from setget forward and it complained about the next one.  I commented out all the setget clauses and it ran, but then quickly errored stating different functions could not be found.
I have not tested any of the previous 3.6 versions.  This works fine in 3.5.3 and the repo has not changed in awhile.
Steps to reproduce

Open the following repo in 3.6.rc1.official.cfc4a0eff.
Open addons/gut/gut.gd
Notice that it says the setter is not defined.

https://github.com/bitwes/Gut/tree/godot_3x
or
git clone -b godot_3x https://github.com/bitwes/Gut
Minimal reproduction project (MRP)
See steps to reproduce

I bisected this regression to #61993
Reverting 5bcc3d476cd06c9e9edd00e63a221d77d9ff7c0b fixes the issue.

I would revert it now and make a better fix after 3.6 is released. Indeed we are at RC, the original issue was minor and the fix is prone to regressions. Meanwhile I will try to investigate it ASAP.

Fixed by #94386.


[SUPPORT]Fail to run compaction in Docker Demo

I follow the Docker Demo this , and everything run properly before step 8.
when I did compaction schedule like Docker Demo doc said, It return an attempted not a complete.  and there is no requested compaction, so cannot run compaction .

设置参数hoodie.compact.inline.max.delta.commits=1；
参考docker/demo/compaction.commands ；

@fengjian428 Are you running it off the master branch ? I did not see any problems with it.

@fengjian428 Is the issue resolved for you?

I reproduced this issue by using the 0.9.0 Release source code, and resolved it by running two more commands in the file docker/demo/compaction.commands:
compaction schedule --hoodieConfigs hoodie.compact.inline.max.delta.commits=1
compaction run --parallelism 2 --sparkMemory 1G  --schemaFilePath /var/demo/config/schema.avsc --retry 1


Upgrade Jackson 2.17.1 -> 2.17.2

This PR contains the following updates:

Package
Type
Update
Change

Jackson
import
patch
2.17.1 -> 2.17.2

[ ] If you want to rebase/retry this PR, check this box

Suggested commit message:
Upgrade Jackson 2.17.1 -> 2.17.2

See https://github.com/FasterXML/jackson-bom/compare/jackson-bom-2.17.1...jackson-bom-2.17.2


Call API

Also with Bridge API

I left 1 PR with Bridge and Call API together to avoid merge conflict. All new branched I will create based on v3-preview


Better pub.dev presentation

Better pub dev presentation
Triple has a lot of potential, but with so many state management packages available, it needs some marketing. Having to dig into the docs to see what the package does may discourage users. A minimal introduction to pub.dev could be beneficial to the adoption of the package.
Solution
Add minimal code exemples on readme instead of just redirecting to the doc.
Presenting the concept of TSP shortly could be nice too.
Maybe end with killer features (hydrated, undo/redo ?) presentation and a link to the doc ?
However, we should be carefull to not overhelm the reader !
Regards

It's my fault, I didn't see that there was a description in the "triple" package.
However, I think this still applies to the "flutter_triple" package since users (like me) can land directly on flutter_triple without seeing triple package.

Added: https://pub.dev/packages/flutter_triple/example

@Pierre2tm if u have any other suggest, we are open to hear =)


Can you tag a new version?

To get the corrected module path in go.mod published.

Done, new tag is v1.1.0.


Merge and obsolete one of two vCJD terms

Mondo term (ID and Label)
variant Creutzfeld Jacob disease (MONDO:0005409)
Reason for deprecation
Appears to be a spelling variation for:
variant Creutzfeldt-Jakob disease (MONDO:0007012) which has more xrefs associated with it.

oh, we should definitely merge, can you do this Nicole?
On Mon, Sep 30, 2019 at 2:14 PM gtsueng<EMAIL_ADDRESS>wrote:

Assigned #847 https://github.com/monarch-initiative/mondo/issues/847 to
@cmungall https://github.com/cmungall.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/monarch-initiative/mondo/issues/847?email_source=notifications&email_token=AAAMMONHROXYNRPUJGX33K3QMJTZ5A5CNFSM4I4AY572YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOT5XLZ3Q#event-2674834670,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAMMOIQEDYXVW2ORPV4HVDQMJTZ5ANCNFSM4I4AY57Q
.

@paolaroncaglia FYI - I obsoleted MONDO:0005409 variant Creutzfeld Jacob disease (EFO_0004597) on PR https://github.com/monarch-initiative/mondo/pull/865


Update yakyak 1.4.3: correct app stanza

Installation of YakYak was failing.
Changed yakyak to YakYak to fix it.

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.

Additionally, if adding a new cask:

[ ] Named the cask according to the token reference.
[ ] brew cask install {{cask_file}} worked successfully.
[ ] brew cask uninstall {{cask_file}} worked successfully.
[ ] Checked there are no open pull requests for the same cask.
[ ] Checked the cask was not already refused in closed issues.
[ ] Checked the cask is submitted to the correct repo.

Thanks for the PR!


Code Availability for ConsistI2V Project?

Hi there!
I'm excited about the ConsistI2V project's ability to have consistent image to video as the source. I noticed the code isn't currently available in the repository. While I understand it's still under development, I'm curious if there's any information about a potential release timeframe.
I appreciate any insights you can share about the code's availability. Thanks for your time and the awesome project!

waiting for the code...

We will release it very soon. Stay tuned.

Thank you for your interest. We have released our code in this repo and model at https://huggingface.co/TIGER-Lab/ConsistI2V.


Fixed a NameError on exception, added a unit test.

Fixes #130

@nathanielmanistaatgoogle
Sorry about not adding unit test for the exception clause.

Thanks for the fix; just the one nitpick comment.

@nathanielmanistaatgoogle Thanks for the comment, PTAL

@nathanielmanistaatgoogle PTAL

Thanks!


Users/tolee/workbooks s360 compliance

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[x] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[x] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of “no breaking changes
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[x] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

/azp run

Any tips on getting the model validation to pass?

@kairu-ms Breaking change has been approved. Please merge the PR when you have the chance to review

@kairu-ms Breaking change has been approved. Please merge the PR when you have the chance to review

@kairu-ms Breaking change has been approved. Please merge the PR when you have the chance to review

@tonykslee Please attach S360 issue links.

@kairu-ms Breaking change has been approved. Please merge the PR when you have the chance to review

@tonykslee Please attach S360 issue links.

@kairu-ms Breaking change has been approved. Please merge the PR when you have the chance to review

@tonykslee Please attach S360 issue links.

https://msazure.visualstudio.com/Swagger KPIs/_workitems/edit/8189496
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=1E0163D4-3B2E-4B33-81EC-1AD9C971CBBA
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=761275DB-C7B4-4B3A-AFA7-1D180640F5F9
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=C772BF0D-C279-4ADC-9777-2B30838FDA5A
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=C80E63FA-D08D-45BB-92FB-584DE1F4AB9D
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=01770025-6D8C-4E9D-9F0C-73AABA652FD4
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=C329CBC2-D252-45BB-9338-82527E198D36
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=16EAC02E-B086-4C36-8B46-922E28F7D5BD
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=0142ECCE-D373-4529-B2BB-99812988396E
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=718BE99F-4162-4804-B775-A72D04E5C45A
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=08E01A69-D9F7-4EB9-8BA4-CCA5BF02DECB
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=C195B570-E5D8-40DD-AC20-D2C9CDCDFF89
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=7B93B086-7E1A-41FF-B75C-D89AA6A8708B
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=F6B08779-EDAB-42FC-9CB1-DBE429285A89

@kairu-ms Breaking change has been approved. Please merge the PR when you have the chance to review

@tonykslee Please attach S360 issue links.

https://msazure.visualstudio.com/Swagger KPIs/_workitems/edit/8189496
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=1E0163D4-3B2E-4B33-81EC-1AD9C971CBBA
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=761275DB-C7B4-4B3A-AFA7-1D180640F5F9
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=C772BF0D-C279-4ADC-9777-2B30838FDA5A
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=C80E63FA-D08D-45BB-92FB-584DE1F4AB9D
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=01770025-6D8C-4E9D-9F0C-73AABA652FD4
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=C329CBC2-D252-45BB-9338-82527E198D36
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=16EAC02E-B086-4C36-8B46-922E28F7D5BD
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=0142ECCE-D373-4529-B2BB-99812988396E
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=718BE99F-4162-4804-B775-A72D04E5C45A
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=08E01A69-D9F7-4EB9-8BA4-CCA5BF02DECB
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=C195B570-E5D8-40DD-AC20-D2C9CDCDFF89
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=7B93B086-7E1A-41FF-B75C-D89AA6A8708B
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=F6B08779-EDAB-42FC-9CB1-DBE429285A89


AMR.load and AMR.amr_to_string changes data during read in test/amr_examples

amr_to_string appears to change data as its being read. This means that a test case (AMR.amr_to_string(AMR.load(ASKEModel, model_expr))) == modelrep will always fail. Here are two concrete observations of this issue:

"@" character is omitted on AMR.load
Expected Call the argument of amr_to_string in the test case M. A substring of M.header should read:
"...ASKE Model Representation: SIR<EMAIL_ADDRESS>Observed The substring of M.header omits the "@" character:
"...ASKE Model Representation: SIR Model0.1..."
A match case in amr_to_string erroneously interprets ODERecord as ODEList
Expected The ODERecord is interpreted by the ODERecord match case and return "ODE_Record = ..."
Observed The relevant substring in the output of amr_to_string has "ODE Equations" instead.

@quffaro Can you upload these examples as tests to some branch in this repo?


Vulnerability roundup 111: cassandra-3.11.10: 1 advisory [9.1]

search, files

[x] CVE-2021-44521 CVSSv3=9.1 (nixos-21.11, nixos-unstable)

CVE details
CVE-2021-44521
When running Apache Cassandra with the following configuration: enable_user_defined_functions: true enable_scripted_user_defined_functions: true enable_user_defined_functions_threads: false it is possible for an attacker to execute arbitrary code on the host. The attacker would need to have enough permissions to create user defined functions in the cluster to be able to exploit this. Note that this configuration is documented as unsafe, and will continue to be considered unsafe after this CVE.

Scanned versions: nixos-21.11: 2128d0aa28e; nixos-unstable: 5aaed40d22f.
Cc @roberth

This CVE only affects configurations with a specific option enabled that is not enabled by default.


@hmr:keep not honored if lang="ts"

Describe the bug
If lang="ts" then @hmr:keep is not honored. (@hmr:keep-all still works).
Reproduction

Clone https://github.com/Leftium/kit-bugs/tree/hmr
Open /lang-ts route
Click button to change value of count
Trigger HMR (by changing increment amount)

Expected: value of count is preserved.
Actual: value of count is reset.
Notes:

The /lang-js route does not have this problem.
@hmr:keep-all works for both JS and TS.

Logs
No response
System Info
System:
    OS: Windows 10 10.0.22621
    CPU: (8) x64 Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
    Memory: 6.01 GB / 23.86 GB
  Binaries:
    Node: 18.9.0 - D:\dropbox\a\nodejs\64v18.9.0\node.EXE
    Yarn: 1.22.18 - D:\dropbox\home\.yarn\bin\yarn.CMD
  Browsers:
    Edge: Spartan (44.22621.963.0), Chromium (108.0.1462.76)
    Internet Explorer: 11.0.22621.1
  npmPackages:
    @sveltejs/adapter-auto: ^1.0.0 => 1.0.0
    @sveltejs/kit: ^1.0.0 => 1.0.1
    svelte: ^3.54.0 => 3.55.0
    vite: ^4.0.0 => 4.0.3

Severity
annoyance
Additional Information
Reference: https://github.com/sveltejs/svelte-hmr/tree/master/packages/svelte-hmr#svelte-hmr

That's because vitePreprocess uses esbuild to transpile TS to JS. esbuild unfortunately removes (most) comments by default, so the comment was likely stripped before svelte-hmr sees them.
I'm not really sure how this can be fixed, other than:

Hoping esbuild would support not stripping comments one day. It strips now due to performance reasons.
Use svelte-preprocess and typescript to preprocess lang="ts"

no2 can be used to workaround in the meantime if you rely on this feature. You can turn off script processing in vitePreprocess specifically with vitePreprocess({ script: false }).

closing as wontfix, svelte-hmr is getting replaced by Svelte 5 native hmr support


Upgraded to 1.4.0, but it seems like next()/response.send() isn't called within the passport example

Hey!
I'm not entirely sure why, but it seems like the following method never really triggers the next()/ response.send() functions (even though it's returned as a promise) and the server hangs when I call login using 1.4.0.
Let me know if you have any ideas on where I could look to resolve this.
Cheers!
/**
     * Authenticate user with local info (in Database).
     * @param email
     * @param password
     * @param request
     * @param response
     * @param next
     */
    @Post('/login')
    public login(
        @Required() @BodyParams('email') email: string,
        @Required() @BodyParams('password') password: string,
        @Request() request: Express.Request,
        @Response() response: Express.Response,
        @Next() next: Express.NextFunction
    ) {
        console.log('resquest.cookies', request.cookies);

        return new Promise<IUser>((resolve, reject) => {

            try{
                Passport
                    .authenticate('login', (err, user: IUser) => {

                        if (err) {
                            reject(err);
                        }

                        request.logIn(user, (err) => {

                            if (err) {
                                reject(err);
                            }

                            resolve(user);
                        });

                    })(request, response, next);
            }catch (er){
                console.error(er);
            }
        })
            .catch((err) => {

                if(err && err.message === "Failed to serialize user into session") {
                    throw new NotFound('user not found');
                }

                return Promise.reject(err);
            });

    }

EDIT
Adding something like following after the promise creation seems to resolve this:
...
         .then(x => {
            response.send(x);
            next();
        })
...

Hi @zoubarevm ,
Effectively, it's a  bug about the new middleware management, when you use @Next() and return a promise at the same time.
v1.4.1 fix them :)
Thanks a lot :)

@Romakita awesome! Just tried it and it works :)
Thanks for your help!


Use a dict or yaml file system to pass in arguments in classes instead of kwargs

Some classes, like RayTracing, are receiving arguments through kwargs.
These have to be changed to receive arguments with the dict or yaml file system, used in ArrayModel, for example.

I'd suggest always supporting both, so you can construct the class like:
instance = MyClass(param1=x, param2=y)
instance = MyClass(**config_dict["MyClassParams"])

and ideally have that second way be a constructor like:
instance = MyClass.from_config(config_dict)

That is what we do in ctapipe - all classes be default are constructed with keyword args, but we provide speclialized constructors that do it from a string, config file, etc.

Thanks for the comments.
I changed the system in order to allow for all the options, consistently. We now have by default a system that accepts a dict or a yaml file as arguments and all the classes have a classmethod to built it from kwargs.
I think that makes more sense because we have some classes with long lists of configurable parameters, so users may often want to store them in yaml files for the sake of reusability.


fix wifi signal strength display

Here's a PR to show WiFi signal strength.  The basic code was present, but it was not called and would display in wrong place.

works great! I put mine with a slight offset
        ...
        gfx.setPixel(SCREEN_WIDTH / 2 + 35 + 2 * i, 8 - j);
  ...
  gfx.drawString(SCREEN_WIDTH / 2 + 45, -1, String(quality) + "%");

Nice, I like that!

The basic code was present, but it was not called

@squix78 do you remember why you never activated this? Simply lack of time?
I prefer @gsemet's version with the offset. @mikecarlton if you were to rebase onto current master to resolve the conflicts we could merge this PR and give you proper credit (rather than just commit the code ourselves). Interested?

@marcelstoer -- i'd be happy to rebase and update this pr.  Will take me a day or two to get to it.

Cool, looking forward to it, thanks.

Thanks, looks nice!


IgnoreCondition: support !! sha ignores

Amend Dependabot::Config::IgnoreCondition to support !! requirements for git dependencies.
This is a syntax previously used internally by Dependabot's backing service: if you @dependabot ignore an update from one Git SHA to another, one of these was created.
Since the syntax isn't supported by Gem::Requirement, care is taken to avoid parsing it as such: it's not returned in ignored_versions, but is included in a new helper: Dependabot::Config::IgnoreCondition#ignored?.

@feelepxyz also did this in https://github.com/dependabot/dependabot-core/pull/3564 , let's take that.


Clone params/options with prototype in order to allow FormData instan…

…ces in body

+10000 if it actually works? I am seeing [object object] in the request.
---------------------------------134840230
Content-Disposition: form-data; name="file"

[object Object]
—-------------------------------134840230--


Add TV Package

I need TV Package (PlayStore, AndroidTV Launcher, Android TV Customization, Android TV Widget, TV Voice Input, Remote Control Service, Second Screen Setup, Second Screen Setup Auth) for create mini TV-Box from OrangePI 5 Plus
I think it will be a very good addition to your project because anyone can do it TV-Box which he wants, not a large tablet with unadapted programs for the TV

If this is still in need, please recommend some commonly used TVGapps and i could implement a script in the future


chore(main): release eslint-config-fuf 0.9.0

:robot: I have created a release beep boop
0.9.0 (2024-04-15)
Features

eslint-config-fuf: add storybook ruleset (ba7492c)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/fuf-stack/ts-project-setup/releases/tag/eslint-config-fuf-v0.9.0 :sunflower:


Cannot upload photos after Mac update

After updating to 2.2.6 I can no longer upload photos.

Thank you for your report. Could you specify what login method you have used? Have you tried to logout, remove and login again to see if it works?

I tried it.   I removed the update and now I can upload photos again.
Il Mer 29 Apr 2020, 14:27 Feruz M<EMAIL_ADDRESS>ha scritto:

Thank you for your report. Could you specify what login method you have
used? Have you tried to logout, remove and login again to see if it works?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/esteemapp/esteem-surfer/issues/285#issuecomment-621384226,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APMPLRFWY5IGFHNATXQEGRLRPBWQ3ANCNFSM4MT5LA5A
.

You removed, using 2.2.5? It is always recommended to use latest version. If you could elaborate more on what login method you have used, perhaps we could find the cause of the issue.

Yes 2.2.5.  I'd love to use 2.2.6 if it performed the functions that I
use.  I logged in on the esteem app for mac.
Il Mer 29 Apr 2020, 14:59 Feruz M<EMAIL_ADDRESS>ha scritto:

You removed, using 2.2.5? It is always recommended to use latest version.
If you could elaborate more on what login method you have used, perhaps we
could find the cause of the issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/esteemapp/esteem-surfer/issues/285#issuecomment-621400785,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APMPLRCHEML3H2KJOBTAGRLRPB2HXANCNFSM4MT5LA5A
.


user: Setup Gorm for backend/database CRUD

As a user, I want any information that I submit in applications surveys signups etc to be saved, so that I can be reviewed approved recognized (etc) by the website
Definition of Done

[ ] Gorm is setup in the backend to communicate with DB
[ ] Gorm can perform necessary CRUD applications

Tasks

[x] #103
[ ] #108
[ ] #107
[x] #118
[x] #114
[x] #105
[x] #116
[x] #121

Fixed requested changes in pull request of this feature/user story into main
[t:15]


Code format breaks code

If (-NOT $global:balloon)

is reformatted into
If (-NOT$global:balloon)

which is unrunnable.
I have stumbled over this when I tried to integrate https://github.com/proxb/PowerShell_Scripts/blob/master/Invoke-BalloonTip.ps1 into our project.

This is really critical issue for me too.
This
Start-Job -ScriptBlock { runThis.exe --color=blue --name=jacob }

is reformatted to
Start-Job -ScriptBlock { runThis.exe --color = blue --name = jacob }

Autoformatting applied on git commit makes this a particulary nasty bug.

Closed as a duplicate of #102.


perf(pencil): remove graphiteWidth option

BREAKING CHANGE: The graphiteWidth option has been removed.
The default graphite width of 10mm is always used for performance reasons.

Codecov Report

Merging #20 (7b6348c) into main (0ebbbc1) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #20   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         2
  Lines           18        18
=========================================
  Hits            18        18

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0ebbbc1...7b6348c. Read the comment docs.


Issue #14: NavBar Component

Made a basic navbar with the new logo made by @Ayush-Shukla02  and did some css styling

Use the colours from
: root selector in index.css don't use other colors
and change code to
`

Text
Text

`
nav{   display: flex;   justify-content: space-between;   padding: 10px 30px; } .logo{   display: flex;   align-items: center; } .logo>img{   margin-right: 10px;   width: 50px;   border-radius: 50%; } .nav-options{   display: flex;   align-items: center; } .nav-options>a{   padding: 10px;   margin: 5px; }
change the code to these please or see the code here and make the changes

HTML
nav{
display: flex;
justify-content: space-between;
padding: 10px 30px;
}
.logo{
display: flex;
align-items: center;
}
.logo>img{
margin-right: 10px;
width: 50px;
border-radius: 50%;
}
.nav-options{
display: flex;
align-items: center;
}
.nav-options>a{
padding: 10px;
margin: 5px;
}

and also this merge has conflicts see why they are happening and how can they be resolved

GitHub, generate site

I guess aarush needs to comment it for it to work.

@OmGuptaIND look at the code now , i made the css cleaner but i need .NavMenu and .ProjectName for easy changes in css

Abhi ek kam kar bas, sare changes squash merge kar. package-lock.json mat track kar. npm install karne par vo apne aap aajaega local par, so no need to update it. Waise mai .gitignore file banakar daal deta hu, taki aage apne aae ye changes.

Work done


Add BasicEventContent derive and create AnyBasicEventContent enum

CI is failing, otherwise LGTM.

Didn't actually notice you had updated this after my review. Thanks, looks good now!


Dataset format

I would like to inquire about the specific format of the dataset under train
train
vis  1.jpg   2.jpg ...
nir   1.jpg  2.jpg ....
Is the infrared and visible light data one-to-one correspondence？

Hello,
Yes,  for training, the infrared and visible light data are in one-to-one correspondence. Please rename the folders to TH for infrared and VIS for visible light data


Capacity error when Repdeploying

Upon trying to redeploy after receiving the error mentioned in #26 I am now getting this validation error:
{"code":"InvalidTemplateDeployment","details":[{"code":"InsufficientQuota","message":"The specified capacity '120' of account deployment is bigger than available capacity '0' for UsageName 'Tokens Per Minute (thousands) - GPT-35-Turbo'."}],"message":"The template deployment 'Microsoft.Template-20230630090235' is not valid according to the validation procedure. The tracking id is '072a60c3-87f9-4f1e-95e3-f4a259595e09'. See inner errors for details."}
Any advice?

Is there already a deployment for gpt35 turbo model on that same AOAI instance?.  If so you may have to manually adjust that existing deployment to lower#.  Let me try to replicate the issue on my end.

I just redeployed having not touched the project over the weekend and it worked fine...
Earlier I had an issue with purging soft deletes...I wonder if it was related.

Perfect - Will close the issue for now


Article should clearly document which VM sizes support Ultra Disks

The article states "Not every VM size is available in every supported region with ultra disks", but there are no specific references to any documentation on exactly what VM-sizes in what regions supports Ultra disks.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 46ddbb6b-a5dd-fdea-6276-4a7f9b1aeff2
Version Independent ID: f4a24ccd-7498-bb91-dcf2-dadf071c58fa
Content: Select a disk type for Azure IaaS Linux VMs - managed disks - Azure Linux Virtual Machines
Content Source: articles/virtual-machines/linux/disks-types.md
Service: virtual-machines
Sub-service: disks
GitHub Login: @roygara
Microsoft Alias: rogarana

@olavt
Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate.

@roygara
Can you please check and add your comments on this doc update request as applicable.

@olavt Thanks for reaching out, the article documents which regions ultra is in, as well as which series of VM supports ultra disk, in the ga-scope-and-limitations heading. It does not, and cannot, give an exact list of the region matchups. There is no article that has a list of the regional availability for the VM SKUs to my knowledge.
To get that information, you have to use one of the scripts in the dedicated ultra doc, here: https://docs.microsoft.com/en-us/azure/virtual-machines/linux/disks-enable-ultra-ssd#determine-vm-size-and-region-availability
These scripts will let you know what VM SKU/Disk combo is in which region, plus what zone it is in for your subscription (the zone availability is subscription specific, one sub could only have the combination in zone 2, whereas another sub could be zone 1). Because of this, you must use the scripts to determine which region/disk/zone combination is right for you.
@VikasPullagura-MSFT FYI
#please-close


Button pressed/released events

I've never written an app using Gtk, so let me know if I'm missing something obvious.
I want to have a button that does different things when pressed vs released. I found this Python code on StackOverflow: https://stackoverflow.com/a/19441817
self.button = Gtk.Button("Hi Printer")
self.button.connect("pressed", self.on_button_clicked)
self.button.connect("released", self.on_button_released)

With Gir.Core, I could add an OnClicked event handler for a Gtk.Button:
_hello.OnClicked += (sender, args) => Console.WriteLine("Clicked");

but I don't see pressed and released events. It looks like the file containing the OnClicked event is a generated file (Button.Signals.Generated.cs) so I'm not quite sure what to do.
Thanks!

This is my fault - This was only available in Gtk3, and removed in Gtk4. Apparently I can use a custom widget and GtkGestureClick to handle this. I'll try figure it out, or think of a new UI design that doesn't need this.

This works!
var gesture = GestureClick.New();
gesture.PropagationPhase = PropagationPhase.Capture;
gesture.OnPressed += (_, _) => Console.WriteLine("Pressed");
gesture.OnReleased += (_, _) => Console.WriteLine("Released");
_hello.AddController(gesture);

Hey, great you solved your problem. I could not have helped you very much as I'm not very familar with GTK either: I'm just the guy working on bindings for GObject based libraries😅.
Having some C# docs or sample projects to refer to for common problems would be very nice. So any help is welcome.


Rename Microsoft.AspNetCore.App.PlatformManifest.txt

Fix https://github.com/aspnet/AspNetCore/issues/8836
Description
The SDK is not reading version-conflict resolution data from our targeting pack because the manifest is in the wrong location. As a result, the SDK is copying assemblies into the build/publish output which should have come from the shared framework instead.
Customer Impact
When a project references EF Core 3.0 and ASP.NET Core 3.0,  published output is not optimized and duplicates assemblies which should have come from the shared framework.
Regression?
Yes, this is a regression from the shared framework behavior in 2.2.
Risk
Low.

@Eilon for QB process

Tracking QB approval here: https://devdiv.visualstudio.com/DevDiv/_workitems/edit/843061/

QB approved, waiting for a re-run of Templates Tests before I merge (first run failed with yarn flakiness).

QB approved for Preview 4. Please check in and watch the build stay green.
And please also resolve https://devdiv.visualstudio.com/DevDiv/_workitems/edit/843061 when done.


[test] Update to Cadence 0ff20e15e7e1

Description
Automatically update to:

onflow/cadence 0ff20e15e7e1
onflow/flow-go-sdk v0.44.0-stable-cadence.2
onflow/flow-go 4c4527a42fb0
onflow/flow-emulator 9116c416533f0de723a74ee830b19400d296c87a

No idea why CI was failing before, but updating to at least Go 1.20 fixed the build errors. Cadence, flow-go, etc. all already require 1.20 anyway


CI: Pre-commit error in main codes

Seems like it should be solved by modifying the Github Actions config file, probably need to add caching or something like that


chore: set the status to SIGNED.

Description
Update the status of base-002-fp-upgrade to SIGNED for now and should be set  to EXECUTED after execution.

I will close this PR because this is not necessary and the correct flow to change the status to SIGNED should be only for PSPs runbooks.
From this conversation on discord:
Ah interesting. So SIGNED was intended to be a terminal state for things like presigned pause, where we sign the playbook and don't have any immediate plans to execute. For this kind of playbook (sign + execute around the same time) we typically go straight from READY TO SIGN to EXECUTED. The reason being a "terminal status" matters is because we want to use those to determine which tasks to automatically exceute in CI: https://github.com/ethereum-optimism/superchain-ops/issues/337
Mentioning this issue -> https://github.com/ethereum-optimism/superchain-ops/issues/337

I will close this PR because this is not necessary and the correct flow to change the status to SIGNED should be only for PSPs runbooks.
From this conversation on discord:
Ah interesting. So SIGNED was intended to be a terminal state for things like presigned pause, where we sign the playbook and don't have any immediate plans to execute. For this kind of playbook (sign + execute around the same time) we typically go straight from READY TO SIGN to EXECUTED. The reason being a "terminal status" matters is because we want to use those to determine which tasks to automatically exceute in CI: https://github.com/ethereum-optimism/superchain-ops/issues/337
Mentioning this issue -> https://github.com/ethereum-optimism/superchain-ops/issues/337


Thank you for sharing your very interesting work

Sorry this is not an Issue, but thank you very much for sharing your really interesting work!
I also look forward to you sharing the policy dissection method and training code as well.

I did not realize that you had already shared them with us. Thank you very much!


Image quality from Converter project is of unreadable quality

Describe the bug
When the following command is run against Azure provider the output image quality is so low (due to the amount of columns) that it is unreadable. See attachment for example.
python -m focus_converter.main explain --provider azure --image-path azure_graph.jpeg
Expected behavior
An image quality that is more readable or can support zooming from the viewing application.
Screenshots

Desktop (please complete the following information):

Development Environment is GitHub Codespaces.

Awesome, the quality and usability of the new format is much better. Thank you!


can u update forum release number to 2.17.1

nothing

Changed the notification on the top. Will update the topic when I'm near my computer again.


XSS vulnerability in the page compare feature on the Author Env

Required Information

[X] AEM Version, including Service Packs, Cumulative Fix Packs, etc:  AEM Cloud
[X] ACS AEM Commons Version: 6.6.0___
[X] Reproducible on Latest? yes/no

Vulnerability reported through Security Scan on AEM Cloud Author env:
BLS T001 Medium xxs bug to be remediated:
ADOBE AEM Cloud
Reflected Cross-Site Scripting (XSS)
The /apps/acs-commons/content/page-compare.html endpoint in the AEM author application is vulnerable to Reflected XSS via the a and b GET parameters. User input submitted via these parameters is not validated or sanitized. As a result, arbitrary JavaScript code is executed in the victim's browser. This vulnerability was reported in the previous AEM BAA for 2023, as Finding [T001] and has been assigned CVE-2022-28820. Since that report, the CVE in question was remediated within the AEM ACS Commons project in version 5.2.0. However, according to recent issues on the AEM ACS Commons github project[2], this same vulnerability has been reintroduced into the project, or previous fixes were insufficient. This vulnerability exists due to a lack of adherence to the following SCF IDs: * TDA-06 * TDA-06.5 * TDA-09 * TDA-09.2 * TDA-09.3 * TDA-09.4 * TDA-09.5 * TDA-09.7 * TDA-18 * WEB-09
https://github.com/Adobe-Consulting-Services/acs-aem-commons/releases
ASC Commons latest version 6.6.2

Disable the page-compare.html functionality of the AEM ACS Commons project if possible, otherwise restrict access to the endpoint via AEM dispatcher rules.
Sanitize user-supplied values for dangerous characters.
User-supplied input should always be considered hostile and untrusted. When receiving user-supplied input, the data should be sanitized to encode dangerous characters (such as "&", "<", ">", """, "'", and "/") to make any content that is eventually rendered into a response benign.
Ideally, sanitization should occur when the data is received (input stage) and also when the data is being rendered into a response (output stage).
Whenever possible, use well-established and trusted libraries to perform sanitization and filtering of input as opposed to trying to craft a solution from scratch.

Please describe briefly the expected behavior, i.e. when I do X, Y should happen.
Questions:
Is it possible to fix this issue soon?  If not could you please suggest if we can disable the page compare feature in our author env?

Can you come up with a PR containing a fix?

@kwin  I would have loved to but currently my plate is full!


TypeError: (0, _reactNativeRedash.useValue) is not a function. (In '(0, _reactNativeRedash.useValue)(0)', '(0, _reactNativeRedash.useValue)' is undefined)

TypeError: (0, _reactNativeRedash.useValue) is not a function. (In '(0, _reactNativeRedash.useValue)(0)', '(0, _reactNativeRedash.useValue)' is undefined)**
Please help to solve this

TypeError: (0, _reactNativeRedash.useValue) is not a function. (In '(0, _reactNativeRedash.useValue)(0)', '(0, _reactNativeRedash.useValue)' is undefined)**
Please help to solve this

Im also getting same error

Downgrading to 2.1.1 version works ok.

TypeError: (0, _reactNativeRedash.useValues) is not a function. (In '(0, _reactNativeRedash.useValues)(0)', '(0, _reactNativeRedash.useValues)' is undefined)
using versions
"react-native-reanimated": "~2.8.0",
"react-native-redash": "^18.0.0",
Please help me to overcome this.


Android app crashes on long press of input field

[x] I have read the README
[x] I have already searched for the same problem
[x] I have read and done the setup for Android: IMPORTANT Note for Android and iOS and IMPORTANT Note for Android
[x] I have read and done the setup for iOS: IMPORTANT Note for Android and iOS and IMPORTANT Note for iOS
[x] I have ran the sample app and it does not work there

Environment

Technology
Version

Flutter version

Plugin version

Android version

iOS version

Xcode version

Device information:
Description
Expected behavior:
Current behavior:
Steps to reproduce

This
Than that
Then

Images
Stacktrace/Logcat

In order to fix the issue, I have changed the if condition (value != null) to (!value.equalsIgnoreCase("null")).

In order to fix the issue, I have changed the if condition (value != null) to (!value.equalsIgnoreCase("null")).

This ticket may be relate to: 'https://github.com/pichillilorenzo/flutter_inappwebview/issues/527'

I think it's fixed at: https://github.com/pichillilorenzo/flutter_inappwebview/commit/26e63cedee11a5427012955c63e131b61781ef89


Gas limit override feature

Hello, thanks for the awesome project!
Simple-uniswap-sdk is really useful!
I have a problem with the automatic gas limit detection. It is often set for a too-small value, so I keep getting the  Warning! Error encountered during contract execution [Out of gas] on my trade transactions. Is there any way to manually set the Gas Limit?

Hey the sdk only returns you the tx without any gas limit defined its up you to fill the gaps with it yourself. If you don’t and send it to web3 or ethers it will try to estimate it for you.
We just return:
transaction: {
to: string;
from: string;
data: string;
value: string;
};
hope this helps!

to set you can just set it on that transaction object aka transaction.gas = xxxx etc etc


build errors

Hi Paul, have just cloned & built Soundpipe and tried installing Sporth, but make fails with:
ugens/pluck.c:47:27: error: no member named 'pick' in 'sp_pluck'
            pluck->pluck->pick = sporth_stack_pop_float(stack);
            ~~~~~~~~~~~~  ^
ugens/pluck.c:70:27: error: no member named 'pick' in 'sp_pluck'
            pluck->pluck->pick = sporth_stack_pop_float(stack);
            ~~~~~~~~~~~~  ^

I'm guessing pluck->pluck->pick has become pluck->pluck->pickup, so I changed that, but then there're more errors which I've got no idea how to fix:
ugens/tin.c:8:5: error: unknown type name 'sp_tin'; did you mean 'sp_in'?
    sp_tin *tin;
    ^~~~~~
    sp_in
/usr/local/include/soundpipe.h:744:3: note: 'sp_in' declared here
} sp_in;
  ^
ugens/tin.c:17:13: warning: implicit declaration of function 'sp_tin_create' is invalid in C99 [-Wimplicit-function-declaration]
            sp_tin_create(&tin);
            ^
ugens/tin.c:18:55: error: use of undeclared identifier 'sp_tin'; did you mean 'sp_in'?
            plumber_add_module(pd, SPORTH_TIN, sizeof(sp_tin), tin);
                                                      ^
/usr/local/include/soundpipe.h:744:3: note: 'sp_in' declared here
} sp_in;
  ^
ugens/tin.c:33:13: warning: implicit declaration of function 'sp_tin_init' is invalid in C99 [-Wimplicit-function-declaration]
            sp_tin_init(pd->sp, tin);
            ^
ugens/tin.c:44:13: warning: implicit declaration of function 'sp_tin_compute' is invalid in C99 [-Wimplicit-function-declaration]
            sp_tin_compute(pd->sp, tin, &trig, &out);
            ^
ugens/tin.c:49:13: warning: implicit declaration of function 'sp_tin_destroy' is invalid in C99 [-Wimplicit-function-declaration]
            sp_tin_destroy(&tin);

Am really keen to try this out so any pointers are highly appreciated! :)

Hey Karsten,
You'll need to use the 'dev' branch of Soundpipe. This isn't written anywhere, so I've made a note of it in the README. Let me know if that fixes things. If you have issues with building Soundpipe dev, feel free to use this ticket to report it.

:+1: - Thanks & all working! Now on to reverse engineerring/learning by example... :) V. impressed so far though! Do you plan or think either Soundpipe or Sporth could be used for live coding too?

Thanks!
Soundpipe by itself couldn't/shouldn't be used for live coding, but it can certainly be used as an audio engine for one!
In theory, yes, Sporth could be used for live coding. I have even been working on an experimental live coding environment called Sporthlive, which is in the util folder. I wouldn't try it out yet though, unless you don't mind getting your hands dirty, as nothing is documented yet. I also have plans on getting Sporth inside of ChucK, which I think may be able to do.


Parlsey 1.2.0 fails on HMR simulations with propyne-containing molecules

Progress

[x] Make reproducing case for reported issue
[x] Ensure case reproduces for openff-1.2.0, but not openff-1.0.0 or openff-1.1.0
[x] Make openff-1.2.1 candidate (both constrained and unconstrained), with changes described below
[x] Ensure candidate FF does not reproduce error
[ ] Follow Standard Release Process

Problem Description
On Aug 11, 2020:

Christopher Bayly  11:09
We have just uncovered a really bad symptom with Parsley 1.2 when running MD on a molecule containing a a propyne substituent on a phenyl, as in c1ccccc1C#CC. The symptom is that the MD blows up and returns a NaN, but it only happens when Hydrogen Mass Repartitionlng (HMR) is turned on. We looked into it and the 4 fs timestep with HMR is the cause: the methyl bond with the triple-bond carbon hits a resonant frequency and ultimately explodes causing the NaN. This should not happen and I think I can see why: I think the force constants for the C#C triple bond and the attached methyl C-CH3 do not make sense. For the latter (single bond), bond type b24 has a super-high force constant 1.2977e+03 that you would expect for a triple bond, not a single bond. Conversely the triple bond with bond type b27 has a weak force constant 8.23e+02 that you would expect for a single bond not a triple bond. You can check this against the other "single bond" and "double/triple bond" force constants in the same section of the offxml. The smoking gun is that when we use GAFF2 which has more-or-less expected k's (high for the triple bond, regular low for the single), there is no issue with MD using HMR. (edited)

(gif from Gaetano Calabro)

Proposed resolution
Per decision in FF-release meeting on September 3, 2020

Decisions:
We will modify 1.2.0 by hand to assign b24’s k to 800, b27’s k to 1000 → Rename to b24-MANand b27-MAN → test against propyne containing molecule (jax 15 beta-secretase case from DH) → Release 1.2.1

Do we know if this happens in both OpenMM and gromacs, or just OpenMM? Also, which integrator was used?

OpenMM presumably. Unsure about integrator. @cbayly13 indicated that the error happens reliably and quickly, but is unable to share code since it's internal. I'm working on a reproducing case and will upload that once I have it.

@jchodera Do you have a code snippet using OpenMM+HMR? DIgging through docs now but having an example would save me some time.

Sure!
# Create an openforcefield Molecule object from SMILES
from openforcefield.topology import Molecule
molecule = Molecule.from_smiles('c1ccccc1C#CC')
# Define the keyword arguments to feed to ForceField; use heavy hydrogens and constrained X-H bonds
# (Note that this differs a bit from allowing SMIRNOFF to control masses and cosntraints)
from simtk import openmm, unit
from simtk.openmm import app
forcefield_kwargs = { 'constraints' : app.HBonds, 'rigidWater' : True, 'removeCMMotion' : False, 'hydrogenMass' : 4*unit.amu }
# Initialize a SystemGenerator using GAFF
from openmmforcefields.generators import SystemGenerator
system_generator = SystemGenerator(small_molecule_forcefield='openff-1.2.0', forcefield_kwargs=forcefield_kwargs, molecules=molecule)
# Create an OpenMM System from an Open Force Field toolkit Topology object
system = system_generator.create_system(molecule.to_topology().to_openmm())
# Run a simulation
temperature = 300 * unit.kelvin
collision_rate = 1.0 / unit.picoseconds
timestep = 4.0 * unit.femtoseconds
# Use BAOAB
integrator = openmm.LangevinMiddleIntegrator(temperature, collision_rate, timestep)
context = openmm.Context(system, integrator)
molecule.generate_conformers()
context.setPositions(molecule.conformers[0])
# Integrate
niterations = 1000
nsteps_per_iteration = 250
for iteration in range(niterations):
    integrator.step(nsteps_per_iteration)
    state = context.getState(getEnergy=True)
    print(f'{state.getTime()/unit.picoseconds:12.3f} ps :  potential {state.getPotentialEnergy()/unit.kilocalories_per_mole:16.3f} kcal/mol')

output with openff-1.2.0:
       1.000 ps :  potential           39.453 kcal/mol
       2.000 ps :  potential           43.479 kcal/mol
       3.000 ps :  potential           48.913 kcal/mol
       4.000 ps :  potential           47.405 kcal/mol
       5.000 ps :  potential           43.038 kcal/mol
       6.000 ps :  potential           53.795 kcal/mol
       7.000 ps :  potential              nan kcal/mol
       8.000 ps :  potential              nan kcal/mol
       9.000 ps :  potential              nan kcal/mol
      10.000 ps :  potential              nan kcal/mol
      11.000 ps :  potential              nan kcal/mol

with openff-1.0.0:
       1.000 ps :  potential           73.354 kcal/mol
       2.000 ps :  potential           71.585 kcal/mol
       3.000 ps :  potential           74.965 kcal/mol
       4.000 ps :  potential           74.602 kcal/mol
       5.000 ps :  potential           78.396 kcal/mol
       6.000 ps :  potential           77.423 kcal/mol
       7.000 ps :  potential           79.104 kcal/mol
       8.000 ps :  potential           75.350 kcal/mol
       9.000 ps :  potential           75.802 kcal/mol
      10.000 ps :  potential           77.676 kcal/mol
      11.000 ps :  potential           76.635 kcal/mol
      12.000 ps :  potential           74.958 kcal/mol
      13.000 ps :  potential           74.385 kcal/mol
      14.000 ps :  potential           77.336 kcal/mol
      15.000 ps :  potential           76.727 kcal/mol
      16.000 ps :  potential           75.620 kcal/mol
      17.000 ps :  potential           71.890 kcal/mol
      18.000 ps :  potential           76.717 kcal/mol
      19.000 ps :  potential           78.543 kcal/mol
      20.000 ps :  potential           75.369 kcal/mol
      21.000 ps :  potential           78.076 kcal/mol
      22.000 ps :  potential           76.400 kcal/mol
      23.000 ps :  potential           74.812 kcal/mol
      24.000 ps :  potential           76.822 kcal/mol
      25.000 ps :  potential           77.451 kcal/mol
      26.000 ps :  potential           76.050 kcal/mol
      27.000 ps :  potential           74.618 kcal/mol
      28.000 ps :  potential           74.391 kcal/mol
      29.000 ps :  potential           79.433 kcal/mol
      30.000 ps :  potential           74.723 kcal/mol
      31.000 ps :  potential           83.331 kcal/mol
      32.000 ps :  potential           75.466 kcal/mol
      33.000 ps :  potential           75.762 kcal/mol
      34.000 ps :  potential           74.493 kcal/mol
      35.000 ps :  potential           74.044 kcal/mol
      36.000 ps :  potential           77.265 kcal/mol
...

That said, I'm not certain this isn't an OpenMM specific numerical instability with angles near pi, or torsions when any one angle nears pi. I'm pretty sure we are still not using the numerically stable expressions derived by Bill Swope for these terms, which may be needed.

Thanks @jchodera!
Here's the code to make both normal and unconstrained openff-1.2.1, reproduce the error, and show that it affects the expected force fields.
Making the new FF files
from openforcefield.typing.engines.smirnoff import ForceField
ff = ForceField('openff-1.2.0.offxml')
bh = ff.get_parameter_handler('Bonds')
for param in bh.parameters:
    if param.id == "b24":
        param.k = 800. * unit.kilocalorie_per_mole / (unit.angstrom ** 2)
        print(param)
    if param.id == "b27":
        param.k = 1000. * unit.kilocalorie_per_mole / (unit.angstrom ** 2)
        print(param)
ff.to_file('openff-1.2.1.offxml')

<BondType with smirks: [#6X2:1]-[#6X4:2]  length: 1.465575905254 A  k: 800.0 kcal/(A**2 mol)  id: b24  >
<BondType with smirks: [#6X2:1]#[#6X2:2]  length: 1.218049770442 A  k: 1000.0 kcal/(A**2 mol)  id: b27  >

from openforcefield.typing.engines.smirnoff import ForceField
ff = ForceField('openff_unconstrained-1.2.0.offxml')
bh = ff.get_parameter_handler('Bonds')
for param in bh.parameters:
    if param.id == "b24":
        param.k = 800. * unit.kilocalorie_per_mole / (unit.angstrom ** 2)
        print(param)
    if param.id == "b27":
        param.k = 1000. * unit.kilocalorie_per_mole / (unit.angstrom ** 2)
        print(param)
ff.to_file('openff_unconstrained-1.2.1.offxml')

<BondType with smirks: [#6X2:1]-[#6X4:2]  length: 1.465575905254 A  k: 800.0 kcal/(A**2 mol)  id: b24  >
<BondType with smirks: [#6X2:1]#[#6X2:2]  length: 1.218049770442 A  k: 1000.0 kcal/(A**2 mol)  id: b27  >

Reproducing the error for 1.2.0, and showing it doesn't affect 1.0.0, 1.1.0, and 1.2.1
# Create an openforcefield Molecule object from SMILES
from openforcefield.topology import Molecule
molecule = Molecule.from_smiles('c1ccccc1C#CC')
# Define the keyword arguments to feed to ForceField; use heavy hydrogens and constrained X-H bonds
# (Note that this differs a bit from allowing SMIRNOFF to control masses and cosntraints)
from simtk import openmm, unit
from simtk.openmm import app
forcefield_kwargs = { 'constraints' : app.HBonds, 'rigidWater' : True, 'removeCMMotion' : False, 'hydrogenMass' : 4*unit.amu }
# Initialize a SystemGenerator using GAFF
from openmmforcefields.generators import SystemGenerator
for ff_name in ('openff-1.2.0', 'openff-1.1.0', 'openff-1.0.0', 'openff-1.2.1'):
    print()
    print()
    print(ff_name)
    system_generator = SystemGenerator(small_molecule_forcefield=ff_name, forcefield_kwargs=forcefield_kwargs, molecules=molecule)
    # Create an OpenMM System from an Open Force Field toolkit Topology object
    system = system_generator.create_system(molecule.to_topology().to_openmm())
    # Run a simulation
    temperature = 300 * unit.kelvin
    collision_rate = 1.0 / unit.picoseconds
    timestep = 4.0 * unit.femtoseconds
    # Use BAOAB
    integrator = openmm.LangevinIntegrator(temperature, collision_rate, timestep)
    context = openmm.Context(system, integrator)
    molecule.generate_conformers()
    context.setPositions(molecule.conformers[0])
    # Integrate
    niterations = 10
    nsteps_per_iteration = 250
    for iteration in range(niterations):
        integrator.step(nsteps_per_iteration)
        state = context.getState(getEnergy=True)
        print(f'{state.getTime()/unit.picoseconds:12.3f} ps :  potential {state.getPotentialEnergy()/unit.kilocalories_per_mole:16.3f} kcal/mol')

openff-1.2.0
1.000 ps :  potential           43.568 kcal/mol
2.000 ps :  potential              nan kcal/mol
3.000 ps :  potential              nan kcal/mol
4.000 ps :  potential              nan kcal/mol
5.000 ps :  potential              nan kcal/mol
6.000 ps :  potential              nan kcal/mol
7.000 ps :  potential              nan kcal/mol
8.000 ps :  potential              nan kcal/mol
9.000 ps :  potential              nan kcal/mol
10.000 ps :  potential              nan kcal/mol
openff-1.1.0
1.000 ps :  potential           72.692 kcal/mol
2.000 ps :  potential           74.271 kcal/mol
3.000 ps :  potential           70.596 kcal/mol
4.000 ps :  potential           73.193 kcal/mol
5.000 ps :  potential           78.326 kcal/mol
6.000 ps :  potential           81.247 kcal/mol
7.000 ps :  potential           79.374 kcal/mol
8.000 ps :  potential           77.016 kcal/mol
9.000 ps :  potential           70.389 kcal/mol
10.000 ps :  potential           72.727 kcal/mol
openff-1.0.0
1.000 ps :  potential           75.120 kcal/mol
2.000 ps :  potential           84.182 kcal/mol
3.000 ps :  potential           78.065 kcal/mol
4.000 ps :  potential           76.811 kcal/mol
5.000 ps :  potential           81.001 kcal/mol
6.000 ps :  potential           81.146 kcal/mol
7.000 ps :  potential           77.968 kcal/mol
8.000 ps :  potential           78.745 kcal/mol
9.000 ps :  potential           78.205 kcal/mol
10.000 ps :  potential           76.285 kcal/mol
openff-1.2.1
1.000 ps :  potential           39.100 kcal/mol
2.000 ps :  potential           47.156 kcal/mol
3.000 ps :  potential           42.099 kcal/mol
4.000 ps :  potential           43.874 kcal/mol
5.000 ps :  potential           45.213 kcal/mol
6.000 ps :  potential           40.509 kcal/mol
7.000 ps :  potential           46.466 kcal/mol
8.000 ps :  potential           48.286 kcal/mol
9.000 ps :  potential           51.831 kcal/mol
10.000 ps :  potential           48.733 kcal/mol

We are deviating from the meeting notes above: They say to rename the modified parameters to b24-MAN, but @trevorgokey points out (and I agree) that this is confusing, and even b24-manual is inconvenient, because it makes this force field incomparable (by parameter labeling studies) to others in the Parsley line.
We will leave a manual comment in the OFFXML files explaining the change.

Ah, testing this with the UNCONSTRAINED candidate FF still shows the explosion. Is this acceptable, or should we look at other solutions?

openff_unconstrained-1.2.1
1.000 ps :  potential           42.302 kcal/mol
2.000 ps :  potential           44.210 kcal/mol
3.000 ps :  potential           41.396 kcal/mol
4.000 ps :  potential           41.892 kcal/mol
5.000 ps :  potential           50.392 kcal/mol
6.000 ps :  potential           46.798 kcal/mol
7.000 ps :  potential           50.715 kcal/mol
8.000 ps :  potential           45.248 kcal/mol
9.000 ps :  potential              nan kcal/mol
10.000 ps :  potential              nan kcal/mol

Verified with @davidlmobley -- This is expected, and only the constrained version of the new FF should be used with HMR.
Jeffrey Wagner  15:38
@John Chodera @dmobley @cbayly I've made the proposed changes to create a 1.2.1 release candidate. The normal version of this FF openff-1.2.1 successfully simulates the propyne system. However, openff_unconstrained-1.2.1 still sometimes explodes.
I'm unfamiliar with HMR. Is HMR always run with hbond constraints? If not, the changes in the new unconstrained FF are not adequate to fix the propyne issue.

David Mobley  15:39
That should be what we’re after! The unconstrained FF is not for MD.
15:40
When running MD without constraints on HBonds, one needs a smaller timestep. HMR does nothing to fix this. It simply makes it so that you can get by with an EVEN LARGER timestep than normal when running with HBond constraints.


Update bless_client.py

Allow bless_client.py to accept ~/.aws/credentials
Use LogType=None because the logs generally live in another account

As it stands, the recommendation to contain all BLESS items in a completely isolated account is one that I think is very reasonable. After setting that up and granting the appropriate cross-account perms to invoke the lambda, I ran into this issue. https://forums.aws.amazon.com/thread.jspa?messageID=715494
Because of that, I couldn't get it to work until I disabled the LogType='Tail' arg from the lambda handler invocation. I toyed w/ the idea of adding yet another param to bless_client.py, but I didn't think it warranted that. If there's a better way to get the logline of your request, let me know.

Thanks for the feedback bI'll take a look at this pr's next week when I'm back in the office.
Sent from a mobile device.

On Jun 10, 2016, at 11:43 AM, Adam McElwee<EMAIL_ADDRESS>wrote:
Allow bless_client.py to accept ~/.aws/credentials
Use LogType=None because the logs generally live in another account
As it stands, the recommendation to contain all BLESS items in a completely isolated account is one that I think is very reasonable. After setting that up and granting the appropriate cross-account perms to invoke the lambda, I ran into this issue. https://forums.aws.amazon.com/thread.jspa?messageID=715494
Because of that, I couldn't get it to work until I disabled the LogType='Tail' arg from the lambda handler invocation. I toyed w/ the idea of adding yet another param to bless_client.py, but I didn't think it warranted that. If there's a better way to get the logline of your request, let me know.
You can view, comment on, or merge this pull request online at:
https://github.com/Netflix/bless/pull/8
Commit Summary
Allow bless_client.py to use ~/.aws/credentials. Use LogType=None because the logs generally live in another account
File Changes
M bless_client/bless_client.py (5)
Patch Links:
https://github.com/Netflix/bless/pull/8.patch
https://github.com/Netflix/bless/pull/8.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Closed, and migrated the work to #9 from a new fork + a few more tweaks.


using iptables marks or ipsets

I have multiple ipsets the /24 is having around 50k entries. I was thinking of not dropping or rejecting this traffic. But redirecting it to a page. Sort of what cloudflare is doing.
I thought maybe a good performing if eg iptables could mark traffic and mod_security could use that in their rules. Or maybe even better, have mod_security access ipsets directly?
I have the impression this does not exist yet, is there maybe an alternative I don't know about?

Hi @f1-outsourcing,
I'm afraid mod_security2 (more precisely the Apache) can't access the marked parts of an IP packet - of if it does, you can't access them through any variable. Therefore you can't control them (redirect, etc...).
But if you have the exact list, and use Apache (you added the label [2.x]), then you should do that on Apache side. You don't need to delegate this task to ModSecurity IMHO.


dpg, support consume multiple content types

Fix https://github.com/Azure/autorest.java/issues/1474

1, run checkstyle locally before push
2. push after all commits is ready on your local
both caused unnecessary disturbance to review (i.e. me)
wait a day for review from Srikanta

1, run checkstyle locally before push 2. push after all commits is ready on your local (instead of after each commit) both caused unnecessary disturbance to reviewer (i.e. me)
wait a day for review from Srikanta

sure, will do that next time.

@srnagar Could you please take a look at this pr?


How to add a name to the datepicker input?

I'm sure I'm missing something obvious here, so please excuse what may be a completely idiotic question (be helpful sans flaming and I'll leave sooner :) ).
I'm using datepicker in a form (in Laravel Spark) like so:
app.js:
window.Vuestrap = require('vue-strap/dist/vue-strap.min.js');

var app = new Vue({
    mixins: [require('spark')],

    components: {
        'datepicker': Vuestrap.datepicker
    },

    data: function () {
        return {
            dob: '01/01/1980'
        }
    }
});

HTML:

    Date of Birth

        <datepicker
          :value.sync="dob"
          format="MM/dd/yyyy">
        </datepicker>

But when I hit the submit button and post the form, there is no field/value which correspond to the datepicker field (although any other basic inputs and their values show up fine)... and adding name= doesn't seem to help.
So, how does one add a name so the value gets submitted through the POST?
Side note: the datepicker example in the documentation is quite buggy. Sometimes it doesn't show the chosen date to the right of "Selected date is:", other times leaving disabled days disabled in the calendar even after that choice was deselected from the dropdown, or the date shown is off by one day from the selected date, etc.
(Using vue-strap v1.0.8 and vue v1.0.13)

Just add the attribute yourself in the ready method of your component. So in your case:
window.Vuestrap = require('vue-strap/dist/vue-strap.min.js');

var app = new Vue({
    mixins: [require('spark')],

    components: {
        'datepicker': Vuestrap.datepicker
    },

    ready: function () {
        // add name attribute to datepicker input since
        // vue-strap doesn't provide this prop
        $('.datepicker').find('input').attr('name', 'your-name-attr');
    }

    data: function () {
        return {
            dob: '01/01/1980'
        }
    }
});

It's a lame workaround but it gets the job done.

what if we don't wanna use jQuery?

you can make a little hack extending the datepicker.
Check this fiddle: https://jsfiddle.net/wffranco/1zec7xL3/
the example must works even if you change the name dynamically


Feature Request: Typescript Svelte and NextJS guides

API guides for Svelte and NextJS

I'm not sure that I understand what do you mean. Please file a new issue in the JS SDK repo with more details.
As of now, you can find some examples in https://github.com/pocketbase/js-sdk#ssr-integration.


Add The Always Right Institute

Swift and more.

Just a quick one before I merge this, is this a company blog or an individual one? Looks like maybe it's a company?

This is definitely more of a personal one, even though i’m self employed and borders sometimes cross.

(the ari is non an actual institute but fake, in case that isn’t obvious 😬)

Sounds good! Figured as much but wanted to check.


Script should not use the date anymore

#98 shows that if we want to be able to not build binaries if the git commit is the same as the latest, we need to update the script first to not use the date of the day any more.
@gridbugs, what was your solution to do it? Only using the https://preview.dune.build/latest/ will partially solve the problem, as the script still needs the date to open the tar file.

This is something that could have been solved easily by storing the date of the most recent build in a text file and serving it over http (or just putting it in the git repo and pointing the install script at that file). This is still an option. It would be easy to implement and require a trivial change to the install script to make work. I vote that we do this.
Alternatively, now that we've set up a redirect (such as https://preview.dune.build/latest/x86_64-unknown-linux-musl) we could rely on the name of the tar.gz file it downloads to determine the date. But have you tried using curl or wget to download https://preview.dune.build/latest/x86_64-unknown-linux-musl? The webserver at preview.dune.build is using http3, and the version of curl that I have (and probably most people who will be running the script) doesn't speak http3, so it's not even able to follow the redirect to the latest version. Is it an option to configure the webserver to use http2 instead of http3? Otherwise we won't be able to connect to it from the install script.

There's a bigger issue with the redirect links (e.g. https://preview.dune.build/latest/x86_64-unknown-linux-musl) where the redirect can't be followed by curl unless it has support for http3 built in (which my version does not, and I assume most users won't have it either). We either need to configure the server to use http2 instead of http3 or serve the redirect from a different server. Alternatively we could just store the date of the latest build in a text file in the repo and check it from the install script. It's less elegant but would be trivial to implement, at least to put out the immediate fire (I still can't use the install script in Australia until about midday ;) ) until we can figure out how to get the redirect working properly.

There's a bigger issue with the redirect links (e.g. https://preview.dune.build/latest/x86_64-unknown-linux-musl) where the redirect can't be followed by curl unless it has support for http3 built in (which my version does not, and I assume most users won't have it either).

Odd, my curl negotiates HTTP2 from the server just fine (and has no HTTP3 support):
$ curl -vL https://preview.dune.build/latest/x86_64-unknown-linux-musl -o /dev/null
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* Host preview.dune.build:443 was resolved.
* IPv6: (none)
* IPv4: <IP_ADDRESS>
*   Trying <IP_ADDRESS>:443...
* Connected to preview.dune.build (<IP_ADDRESS>) port 443
* ALPN: curl offers h2,http/1.1
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
*  CAfile: /etc/pki/tls/certs/ca-bundle.crt
*  CApath: none
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Server hello (2):
{ [122 bytes data]
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
{ [15 bytes data]
* TLSv1.3 (IN), TLS handshake, Certificate (11):
{ [2039 bytes data]
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
{ [80 bytes data]
* TLSv1.3 (IN), TLS handshake, Finished (20):
{ [36 bytes data]
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.3 (OUT), TLS handshake, Finished (20):
} [36 bytes data]
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256 / x25519 / id-ecPublicKey
* ALPN: server accepted h2
* Server certificate:
*  subject: CN=preview.dune.build
*  start date: Oct  2 07:12:08 2024 GMT
*  expire date: Dec 31 07:12:07 2024 GMT
*  subjectAltName: host "preview.dune.build" matched cert's "preview.dune.build"
*  issuer: C=US; O=Let's Encrypt; CN=E6
*  SSL certificate verify ok.
*   Certificate level 0: Public key type EC/prime256v1 (256/128 Bits/secBits), signed using ecdsa-with-SHA384
*   Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 2: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [122 bytes data]
* using HTTP/2
* [HTTP/2] [1] OPENED stream for https://preview.dune.build/latest/x86_64-unknown-linux-musl
* [HTTP/2] [1] [:method: GET]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:authority: preview.dune.build]
* [HTTP/2] [1] [:path: /latest/x86_64-unknown-linux-musl]
* [HTTP/2] [1] [user-agent: curl/8.6.0]
* [HTTP/2] [1] [accept: */*]
} [5 bytes data]
> GET /latest/x86_64-unknown-linux-musl HTTP/2
> Host: preview.dune.build
> User-Agent: curl/8.6.0
> Accept: */*
>
{ [5 bytes data]
< HTTP/2 303
< alt-svc: h3=":443"; ma=2592000
< location: https://get.dune.build/2024-10-18/x86_64-unknown-linux-musl/dune-2024-10-18-x86_64-unknown-linux-musl.tar.gz
< server: Caddy
< content-length: 0
< date: Fri, 18 Oct 2024 08:10:18 GMT
<
* Ignoring the response-body
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
* Connection #0 to host preview.dune.build left intact
* Issue another request to this URL: 'https://get.dune.build/2024-10-18/x86_64-unknown-linux-musl/dune-2024-10-18-x86_64-unknown-linux-musl.tar.gz'
* Host get.dune.build:443 was resolved.
* IPv6: (none)
* IPv4: <IP_ADDRESS>
*   Trying <IP_ADDRESS>:443...
* Connected to get.dune.build (<IP_ADDRESS>) port 443
* ALPN: curl offers h2,http/1.1
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* TLSv1.3 (IN), TLS handshake, Server hello (2):
{ [122 bytes data]
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
{ [15 bytes data]
* TLSv1.3 (IN), TLS handshake, Certificate (11):
{ [2029 bytes data]
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
{ [79 bytes data]
* TLSv1.3 (IN), TLS handshake, Finished (20):
{ [36 bytes data]
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.3 (OUT), TLS handshake, Finished (20):
} [36 bytes data]
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256 / x25519 / id-ecPublicKey
* ALPN: server accepted h2
* Server certificate:
*  subject: CN=get.dune.build
*  start date: Oct  2 07:12:08 2024 GMT
*  expire date: Dec 31 07:12:07 2024 GMT
*  subjectAltName: host "get.dune.build" matched cert's "get.dune.build"
*  issuer: C=US; O=Let's Encrypt; CN=E6
*  SSL certificate verify ok.
*   Certificate level 0: Public key type EC/prime256v1 (256/128 Bits/secBits), signed using ecdsa-with-SHA384
*   Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 2: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [122 bytes data]
* using HTTP/2
* [HTTP/2] [1] OPENED stream for https://get.dune.build/2024-10-18/x86_64-unknown-linux-musl/dune-2024-10-18-x86_64-unknown-linux-musl.tar.gz
* [HTTP/2] [1] [:method: GET]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:authority: get.dune.build]
* [HTTP/2] [1] [:path: /2024-10-18/x86_64-unknown-linux-musl/dune-2024-10-18-x86_64-unknown-linux-musl.tar.gz]
* [HTTP/2] [1] [user-agent: curl/8.6.0]
* [HTTP/2] [1] [accept: */*]
} [5 bytes data]
> GET /2024-10-18/x86_64-unknown-linux-musl/dune-2024-10-18-x86_64-unknown-linux-musl.tar.gz HTTP/2
> Host: get.dune.build
> User-Agent: curl/8.6.0
> Accept: */*
>
{ [5 bytes data]
< HTTP/2 200
< accept-ranges: bytes
< alt-svc: h3=":443"; ma=2592000
< content-type: application/gzip
< etag: "d4ykv63kdgqo417qn"
< last-modified: Fri, 18 Oct 2024 02:31:27 GMT
< server: Caddy
< vary: Accept-Encoding
< content-length: 6775151
< date: Fri, 18 Oct 2024 08:10:18 GMT
<
{ [4735 bytes data]
100 6616k  100 6616k    0     0  1119k      0  0:00:05  0:00:05 --:--:-- 1379k
* Connection #1 to host get.dune.build left intact

The tar file name can be picked by -o anyway, so whatever its name is on the server only matters if you don't overwrite it. Generally I think that is nice as when you download it with a browser you don't get dune-latest (1).tar.gz but rather properly named tarballs and can also determine what nightly they were without unpacking.

 It just looks like it can't open the IPv4 socket at all (and we don't support IPv6, but that's a separate issue).
curl 8.6.0 (x86_64-redhat-linux-gnu) libcurl/8.6.0 OpenSSL/3.2.2 zlib/1.3.1.zlib-ng brotli/1.1.0 libidn2/2.3.7 libpsl/0.21.5 libssh/0.10.6/openssl/zlib nghttp2/1.59.0 OpenLDAP/2.6.7
Release-Date: 2024-01-31
Protocols: dict file ftp ftps gopher gophers http https imap imaps ipfs ipns ldap ldaps mqtt pop3 pop3s rtsp scp sftp smb smbs smtp smtps telnet tftp ws wss
Features: alt-svc AsynchDNS brotli GSS-API HSTS HTTP2 HTTPS-proxy IDN IPv6 Kerberos Largefile libz NTLM PSL SPNEGO SSL threadsafe TLS-SRP UnixSockets

#105 should fix the date issue, but but I have no idea about the connectivity issue. I've also tried it with a curl on Alpine:
curl 8.10.1 (x86_64-alpine-linux-musl) libcurl/8.10.1 OpenSSL/3.3.2 zlib/1.3.1 brotli/1.1.0 zstd/1.5.6 c-ares/1.33.1 libidn2/2.3.7 libpsl/0.21.5 nghttp2/1.62.1
Release-Date: 2024-09-18
Protocols: dict file ftp ftps gopher gophers http https imap imaps ipfs ipns mqtt pop3 pop3s rtsp smb smbs smtp smtps telnet tftp ws wss
Features: alt-svc AsynchDNS brotli HSTS HTTP2 HTTPS-proxy IDN IPv6 Largefile libz NTLM PSL SSL threadsafe TLS-SRP UnixSockets zstd

and it works there (well, the shell script goes to the fallback because $SHELL is not set but given it runs in busybox sh that's to be expected).

I can no longer reproduce the error I got last week downloading the file with curl. Not sure what changed, but it now works for me on macos, nixos, and alpine.


Jenkins-based demo option

Should be easy to switch from in-automation-node to Jenkins build

https://www.linux.com/blog/learn/chapter/Intro-to-Kubernetes/2017/5/set-cicd-pipeline-kubernetes-part-1-overview

Should we consider running a Jenkins server in a docker container to show we can integrate with on prem Jenkins.

The blog I linked above walls through running Jenkins and a Docker registry inside Kubernetes.

Could we run it within Minikube?
Goals:

Show we can integrate with people's existing real world build servers
Convenient setup so that it's not hard to prep a machine for a demo, and it's not hard for users to replicate that
Make it easy to see Jenkins logs or UIs during demos, as waiting without any feedback looks back
Access to Jenkins UI to show builds and logs

Add Jenkins integration sample to README. Do we need a plugin?

Issue moved to atomist/sdm-ecosystem#9


Issues about sharing chart

Sharing charts with iframe is awesome. I want to make a static site like this, and we take Kramdown as the format that supports iframe grammar. And with the update of data, the chart is also updated.
I found two ways to share charts in Superset. One is share the chart directly, and the data will be updated automaticlly. But it shows all the charts of the dashboard. The other one is "explore chart" with iframe. But in this case, the chart will no longer update since the url is fixed in static site.
How can I make a automaticlly updated chart with a fixed chart url?

To confirm, the request is - to share individual updated chart in iframe from the dashboard?
bringing in our iframe expert @rusackas

To confirm, the request is - to share individual updated chart in iframe from the dashboard? @guoguoguilai
bringing in our iframe expert @rusackas

Yes, this is what I want

Any update?


Necessary updates for dependency management

@mvp-2003 upload your pipfile also.
pipfile.lock is generated every time when you install pipfile, so that will not help here alone.


Steppers

I'd love to see steppers implemented
https://material.io/archive/guidelines/components/steppers.html

Me too! Would be awesome!

I agree! Would be awesome

Yes please!

@Lucidize @cedwards-telis ,
Thanks for reporting! We are always looking for contributors if you want to open a PR and tackle this. 🙂

Those would be nice. I think there is enough examples of components in MatBlazor for someone to implement. Please contribute!


add more border styles to BorderSide style element

Add dashed", "dotted", "double", "groove", "ridge", "inset", "outset" to BorderSide class

Looks like the pre-submit checks failed. Just some linting stuff. The best option is to set up the pre-commits described here: https://google.github.io/mesop/internal/development/
The precommits should manually run the ruff formatter to fix the formatting.
For a manual run, I think the command is something like:
pre-commit run --files FILES

Thanks for sharing the steps to fix the pre-checks. I think this has now passed the pre-checks.

Hmm looks like there is another type checking issue on the demo page. It's an interesting one. I'm not quite sure how best to resolve that type checking issue.
For simplicity, you may just want to remove the loop. Then for the styles, just hardcode to different styles.

Closing this one. We ended up merging a similar pull request in https://github.com/google/mesop/pull/509


[AutoPR servicefabric/resource-manager] Add version 2018-02-01 Microsoft.ServiceFabric specification

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/2844

Rebuild everything from scratch in https://github.com/Azure/azure-sdk-for-python/pull/1960


Error while adding rule Host: unexpected number of parameters; got 2, expected one of [1]

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you do?
Migrating docker image from v2.10 to v3.0 I've encountered the following error message in the logging when recreating my Traefik service:
traefik-traefik-1  | 2023-09-10T13:53:00.528139005Z 2023-09-10T13:53:00Z ERR error="error while adding rule Host(`example.com`, `www.example.com`): error while adding rule Host: unexpected number of parameters; got 2, expected one of [1]" entryPointName=websecure routerName=app-apache@docker
traefik-traefik-1  | 2023-09-10T13:53:23.047640325Z 2023-09-10T13:53:23Z ERR error="accept tcp [::]:443: use of closed network connection" entryPointName=websecure
traefik-traefik-1  | 2023-09-10T13:53:23.047658159Z 2023-09-10T13:53:23Z ERR error="close tcp [::]:443: use of closed network connection" entryPointName=websecure
traefik-traefik-1  | 2023-09-10T13:53:23.047662477Z 2023-09-10T13:53:23Z ERR error="accept tcp [::]:80: use of closed network connection" entryPointName=web
traefik-traefik-1  | 2023-09-10T13:53:23.047665623Z 2023-09-10T13:53:23Z ERR error="close tcp [::]:80: use of closed network connection" entryPointName=we

The Traefik router label for app-apache is as follows:
      traefik.http.routers.app-apache.rule: Host(`${APP_DOMAIN}`, `www.${APP_DOMAIN}`)

Note
${APP_DOMAIN} is example.com from the logging above.

I've read the migration guide before upgrading to v3.0, which does not denote anything related to changes with the Host rule.
I've read the latest documentation regarding rules, and the examples show that having multiple hosts, Host(example.com, ...), is still a valid rule.

What did you see instead?

What version of Traefik are you using?
v3.0
What is your environment & configuration?
# (paste your configuration here)

Add more configuration information here.
If applicable, please paste the log output in DEBUG level

Hello,
It's in the documentation:

All matchers now take a single value

https://doc.traefik.io/traefik/v3.0/migration/v2-to-v3/#matchers

hey @ldez 👋
Thanks, I thought v3 was no longer experimental (as the image on dockerhub was tagged v3.0). Sorry for that.
Is the equivalent of Host(`example.com`, `www.example.com`) in v3 then Host(`example.com`) || Host(`www.example.com`) ?

Is the equivalent of Host(example.com, www.example.com) in v3 then Host(example.com) || Host(www.example.com) ?

yes
https://doc.traefik.io/traefik/v3.0/routing/routers/#rule


For an admin, his/her role should be "owner" for any environment/project

For an admin, his/her role should be "owner" for any environment/project by default
https://github.com/rancher/rancher/issues/6365

TF is not related: test_docker_ports_from_container

@alena1108 @ibuildthecloud can you review the role fix

LGTM


SLDS ScDU CEDS JSON-LD Workgroup Proposing Human Readable versus Code IRIs

The SLDS Scalable Data Use Workgroup developing CEDS JSON is proposing a change to the Ontology to allow for the JSON-LD to be more human readable. This involves changing the Ontology IRI's from ID's to the CEDS technical names. Examples below of how this would impact the Ontology are provided. Note that the ID's will still be provided as metadata for the Classes, Properties, and Individuals, but will exist as dc:identifiers only.  Everything else remains the same.
Current Ontology Naming:
<!-- Class: OrganizationName -->
**<rdfs:Class rdf:about="http://ceds.ed.gov/terms#C200246">**
	<rdfs:subClassOf rdf:resource="http://ceds.ed.gov/terms#BaseCEDSResource"/>
	<rdfs:label>Organization Name</rdfs:label>
	<skos:notation>OrganizationName</skos:notation>
	<dc:creator>Common Education Data Standards</dc:creator>
	<dc:identifier rdf:datatype="http://www.w3.org/2001/XMLSchema#token">C200246</dc:identifier>
    <rdfs:comment>Information about an organization.</rdfs:comment>
</rdfs:Class>

Proposed Ontology Naming:
<!-- Class: OrganizationName -->
**<rdfs:Class rdf:about="http://ceds.ed.gov/terms#OrganizationName">**
	<rdfs:subClassOf rdf:resource="http://ceds.ed.gov/terms#BaseCEDSResource"/>
	<rdfs:label>Organization Name</rdfs:label>
	<skos:notation>OrganizationName</skos:notation>
	<dc:creator>Common Education Data Standards</dc:creator>
	<dc:identifier rdf:datatype="http://www.w3.org/2001/XMLSchema#token">C200246</dc:identifier>
    <rdfs:comment>Information about an organization.</rdfs:comment>
</rdfs:Class>

Current Ontology Naming:
<!-- Data Property Relationship: OrganizationName -->
**<rdf:Property rdf:about="http://ceds.ed.gov/terms#P000009">**
<rdfs:label>Activity Title</rdfs:label>
	<skos:notation>ActivityTitle</skos:notation>
	**<schema:domainIncludes rdf:resource="http://ceds.ed.gov/terms#C200246"/>**
	<schema:rangeIncludes rdf:resource="http://www.w3.org/2001/XMLSchema#string"/>
	<dc:creator>Common Education Data Standards</dc:creator>
<dc:identifier rdf:datatype="http://www.w3.org/2001/XMLSchema#token">P000009</dc:identifier>
</rdf:Property>

Proposed Ontology Naming:
<!-- Data Property Relationship: OrganizationName -->
**<rdf:Property rdf:about="http://ceds.ed.gov/terms#ActivityTitle">**
<rdfs:label>Activity Title</rdfs:label>
	<skos:notation>ActivityTitle</skos:notation>
	**<schema:domainIncludes rdf:resource="http://ceds.ed.gov/terms#OrganizationName"/>**
	<schema:rangeIncludes rdf:resource="http://www.w3.org/2001/XMLSchema#string"/>
	<dc:creator>Common Education Data Standards</dc:creator>
<dc:identifier rdf:datatype="http://www.w3.org/2001/XMLSchema#token">P000009</dc:identifier>
</rdf:Property>

Note where there are double asterisks in the code above. That is where the original and changes are being highlighted.

Well, that's annoying. I spent I do not how long changing the PESC JSON-LD transcript from using technical names to numbers (it put that work back about month because I don't have much time per week to spend on it).  With this I would have to change them back again.
I do understand the human factors in working with opaque ids. When I suggested using opaque ids, because they are more maintainable (i.e. you can change labels without creating inconsistencies) and more international, I also said that you need some technology to support human users. One would be a lookup service so that when the technical name is entered the numeric id is provided.
Is the CEDS JSON group using JSON LD? If not then they don't need to use the RDF ids at all, but could produce a mapping from JSON to RDF in RML to get RDF when it is needed.  If they are, then they can use technical names as keys in the JSON and give these the RDF @id in the @context.


How to integrate point-feature option in the standard workflow ?

Hi, thank you for this wonderful tool and detailed explanation.
I've noticed that from the below release,

4/21/2020 - v2.1.2 release new features to improve transcriptome assembly:
introduced an option to load point features from a tab-delimited text
this point-feature option is introduced. I'm sorry if I've missed some documentation on this but I couldn't find more information on it except in the manual page. It would be really nice if you could clarify:

Is the location of the point feature supposed to be 1-based (as in gtf files)?
In what step should we give this option? The step to create gtf files from individual samples or the merging step?

I would really appreciate it if you could also briefly explain how stringtie would cooporate point-features in the algorithm. For example,
3. If given point features don't match the gtf files produced by stringtie, how would they be prioritized?
4. What if the mismatch occur between given point features and reference annotation?
5. How does stringtie process alternative promoters? Will incomplete TSS information in point-feature file remove the true transcripts with alternative TSSs? or can we prioritize TSSs in the point-feature files?
Of course if you could share with us about other things that we need to keep in mind when applying this option, that would be really appreciated.
Thank you in advance for your time.

Just adding a plus one to this issue, I have also asked related questions in https://github.com/gpertea/stringtie/issues/330. To my mind this looks to be a very useful feature, so it would be great if these questions could be addressed in replies or the documentation.