Any Configuration or function to obtain url endpoint? Question

Hi, i write the following question in stack overflow. (https://stackoverflow.com/questions/63905280/nswag-swagger-how-to-get-url-service-from-component)
Are any configuration to obtain url param from component?

something like this: locationService.GetUrlEndpoint() o locationService.Url()
consider, i cannot exposer another method to return string url (i'm trying to save at localstorage urls when device is offline)

You cpuld extend the template and generate another method saveLocationUrl() per operation

See https://github.com/RicoSuter/NSwag/wiki/Templates

Any updates for this? It says only extension templates should be overridden.


Database query ordering rule

Hello,
Not a bug/issue, I just want to get an answer.
What is the ordering rule when I use queries like this:
this.allNews = this.af.database.list('news', {
            query: {
                orderByChild: 'labels/all',
                equalTo: true
            }
        });

I'm trying to get the latest news from the database.. based on it's label but right now, after I set the priority with this:
this.news.$ref.ref.child(newObjectKey).setWithPriority(newsSend,0-Date.now());
It seems like it is just not available at all..... As I see the database now seems good, the new items are on the top... but when I use a query it always return with the oldest elements first and then the new ones..
Please help.. I'm trying to figure out how it's working and how can I get the elements as I mentioned.
reference link:
http://stackoverflow.com/questions/43286119/firebase-query-on-multiple-child

I'm sorry, a few minutes I've found the answer:
https://www.firebase.com/docs/web/guide/retrieving-data.html#section-complex-queries
Which means the items will be shorted lexicographically.


Fix reporting exit code when command line export fails

Fixes #83042.

See https://github.com/godotengine/godot/pull/89229#issuecomment-1981987490 for the reasoning that led me there... turns out it was a simple issue of wrong use of if / else branches...

Cherry-picked for 4.2.2.
Cherry-picked for 4.1.4.


Added a Diff Utility

Description
This is a Diff Utility that takes in two file names as command-line arguments and compares them. It then shows the difference between the two files indicating what has changed where.
Fixes #(issue_no)

[ ] Issue_no: <insert your issue no here>
[x] Not applicable

Type of change
Choosing one or more options from the following as per the nature of your Pull request.

[x] New project insert
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation Update

Project

Your Project Name: Diff Utility

Short Description: This is a Diff Utility that takes in two file names as command-line arguments and compares them. It then shows the difference between the two files indicating what has changed where.

Demo Screenshot:

Checklist:
Please tick all the boxes that are fulfilled by your Pull Request.

[x] I have named my files and folder, according to this project's guidelines.
[x] My code follows the style guidelines of this project.
[x] I have commented on my code, particularly in hard-to-understand areas.
[x] I have created a helpful and easy to understand README.md, according to the given README_TEMPLATE.
[x] My changes do not produce any warnings.

Hello @ndleah, please review and merge my PR. If some changes are required, then please do let me know.
Also it'd be great if you could add a hacktoberfest-accepted tag to this PR.


ImportExcel can't autosize, even though mono-libgdiplus is installed

I get the following message when using import-excel with Powershell on OSX:
WARNING: ImportExcel Module Cannot Autosize. Please run the following command to install dependencies:
brew install mono-libgdiplus

However, mono-libgdiplus is installed and I even reinstalled. All software is up-to-date:
Mac OSX Big Sur 11.6.8 (20G730)
Homebrew 3.5.10
mono-libgdiplus 6.1_1
Powershell 7.2.6
Powershell Module ImportExcel 7.8.0

What's wrong, what can I do?

Could be the check for that needs to be updated. Can you still use -AutoSize? Does it work? Or no go?

Sorry, I've no idea as I'm not using this software regulary. I followend and article (https://adamtheautomator.com/powershell-excel/) using ImportExcel and advising to install mono-libgdiplus on the mac, so I did it. I worte the program some time ago and I never noticed this warning I'm reporting, so I guess it's probably new due to some updates. However, the mere import of the Excel files seems to function. In my program I'm using '-Autoresize' only when $IsMacOS - thus on Windows, and I don't recall what it does.

@dfinke Encountering the same with PS 7 Core.
libgdiplus is already the newest version (6.0.4+dfsg-2).
libc6-dev is already the newest version (2.35-0ubuntu3.1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Importing required Module: 'ImportExcel' ...
WARNING: ImportExcel Module Cannot Autosize. Please run the following command to install dependencies:
apt-get -y update && apt-get install -y --no-install-recommends libgdiplus libc6-dev

@ili101 wondering if you know more about this?

It looked like .Net 6 drooped support for it on non-windows System.Drawing.Common only supported on Windows.
So it looks like it's not going to work on PS 6.2 and up?
EPPlus 6.0.3 stopped using it as a dependency https://github.com/EPPlusSoftware/EPPlus/issues/572
I don't see how we can make it work on new PS versions 🫤

Thanks @ili101 wanted to get your confirmation.


Fix #5318: define version of discord_simple as requirement

Short Description:
Change the version number of the discord_simple requirement to use the latest version available.
Fixes/Resolves/Closes (please use correct syntax):

#5318

Already an PR for this one


chore(master): Release 0.31.0

:robot: I have created a release beep boop
aztec-package: 0.31.0
0.31.0 (2024-03-26)
Features

Add batched signerless contract calls (#5313) (be60eb3)
Dynamic proving (#5346) (6a7ccca)
Less earthly runners + e2e GA runners, bb bench (#5356) (2136a66)

barretenberg.js: 0.31.0
0.31.0 (2024-03-26)
Features

Earthly bb tests + arm + satellites (#5268) (eca12b3)
Less earthly runners + e2e GA runners, bb bench (#5356) (2136a66)
Simplified bb Honk interface (#5319) (a2d138f)

aztec-cli: 0.31.0
0.31.0 (2024-03-26)
Features

Capture broadcasted functions in node (#5353) (bc05db2)

Bug Fixes

cli: Support initializers not named constructor in cli (#5397) (85f14c5)

aztec-packages: 0.31.0
0.31.0 (2024-03-26)
⚠ BREAKING CHANGES

avm: per function avm run (#5421)
rename storage inclusion proof to historical storage read (#5379)
plug-in new outbox and update examples to use api to fetch inclusion proofs #4769 (#5292)
Mark transactions as reverted on L1 (#5226)

Features

Add batched signerless contract calls (#5313) (be60eb3)
Add specific error for attempting string[x] = ".." (https://github.com/noir-lang/noir/pull/4611) (13a12d5)
AuthWit: Chain_id and version in hash (#5331) (5235c95)
Authwit: Lookup the validity of authwits (#5316) (7c24870)
Avm lookup and/or/xor (#5338) (489bc2c)
avm: Add AvmContextInputs (#5396) (12e2844)
avm: Per function avm run (#5421) (f024751)
avm: Track gas usage in AVM simulator (#5438) (4884d83)
Capture broadcasted functions in node (#5353) (bc05db2)
Dynamic proving (#5346) (6a7ccca)
Earthly bb tests + arm + satellites (#5268) (eca12b3)
Fix awkward snippet indention in docs (#5367) (c55d3da)
Fold proving key polys instead of prover polys (#5436) (239ebfb)
Implement serdes for u64 #4990 (#5411) (5a6bcef)
Introduce max_block_number (#5251) (6573173)
Less earthly runners + e2e GA runners, bb bench (#5356) (2136a66)
Mark transactions as reverted on L1 (#5226) (40ecc02)
Plug-in new outbox and update examples to use api to fetch inclusion proofs #4769 (#5292) (fec1008)
Read_calldata (#5409) (034fbf0)
Remove NUM_FIELDS_PER_SHA256 (#5392) (86a181b)
Rename storage inclusion proof to historical storage read (#5379) (b6e7216)
Returning non-nullified messages only (#5390) (4c671be)
Simplified bb Honk interface (#5319) (a2d138f)
Simplify offsets and sizing using new block structure (#5404) (efa0842)
Throw by default when awaiting a tx that reverted (#5431) (c9113ec)
Truncate SHA hashes inside circuits (#5160) (9dc0d2a)
Unified CircuitChecker interface (#5343) (13cef1f)
ZeroMorph working with IPA and integration with ECCVM (#5246) (c4dce94)

Bug Fixes

Addressing flakiness of uniswap_trade_on_l1_from_l2.test.ts (#5443) (2db9cad)
avm-simulator: Hashing opcodes indirection (#5376) (a4b1ebc)
Broadcasting unconstrained function with empty sibling (#5429) (933145e)
ci: Disable uniswap test in earthly build (#5344) (0d69162)
cli: Support initializers not named constructor in cli (#5397) (85f14c5)
Copy and deploy complete contents of l1-contracts (#5447) (501c5e9)
Don't cancel protocol-circuits-gate-diff in master (#5441) (6894a78)
E2e_static_calls.test.ts bad merge (#5405) (4c56536)
Generate noir interface for constructors (#5352) (8434d2f)
Limit earthly to few users (#5375) (71e8ab4)
Login to dockerhub before 'docker compose' (#5440) (4f7696b)
Revert cbind breakage (#5348) (c237193)
ssa: Use accurate type during SSA AsSlice simplficiation (https://github.com/noir-lang/noir/pull/4610) (13a12d5)
Track class registered count in tx stats (#5417) (ff8eafc)
Watch command should not spawn more than one tsc watch (#5391) (25caf4d)

Miscellaneous

Always use serialize function to get hash preimage in noir circuits or when comparing structs etc #3595 (#5439) (22e0f0d)
aztec-nr: Unify contexts behind interfaces (#5294) (36e0f59)
bb: Removed powers of eta in lookup and auxiliary relations (#4695) (f4e62ae)
CamelCase in noir-projects -> snake_case (#5381) (eea711f)
ci: Create a dedicated job for the AVM unit tests (#5369) (59ca2ac), closes #5366
Clean out prover instance and remove instance from oink (#5314) (a83368c)
Cleaning up messaging types (#5442) (dfffe5d), closes #5420
Compute registerer address on the fly (#5394) (5d669b9)
Delete slither output from version control (#5393) (41107e3)
Fix migration notes (#5452) (8c4e576)
github: Improve PR template "document later" checkbox description (https://github.com/noir-lang/noir/pull/4625) (13a12d5)
Make get_notes fail if returning no notes #4988 (#5320) (be86ed3)
Meld flavor and and circuit builder modules (#5406) (f0d9d1b)
Messaging naming fixes (#5383) (0226102)
Moving public inputs back to instance (#5315) (9cbe368)
Name change: gen perm sort to delta range constraint (#5378) (841855f)
Nuking l1 to l2 messages from block body (#5272) (ee176d2), closes #5072
Reduce size of revert code from Field to u8 (#5309) (1868e25)
Remove mocking function in EccOpQueue again (#5413) (6fb4a75)
Remove snapshots from protocol-contracts (#5342) (31ca344)
Remove unused FunctionLeafPreimage struct (#5354) (dc51c2b)
Rename reverted to revertCode (#5301) (950a96d)
Replace relative paths to noir-protocol-circuits (262ae02)
Replace relative paths to noir-protocol-circuits (91a60db)
Replace relative paths to noir-protocol-circuits (9fc9fbd)
Replace relative paths to noir-protocol-circuits (9939e99)
Replace relative paths to noir-protocol-circuits (0b24aae)
Replace relative paths to noir-protocol-circuits (c4d89d5)
Reverting accidental changes (#5371) (c1484ce)
Skip foundry install if possible (#5398) (060fa1e)
Skip slither in docker (#5384) (8a76068)
Update docs with function names to match version 0.25.0 specifications (https://github.com/noir-lang/noir/pull/4466) (13a12d5)
Update integers.md to note support for Fields using from_integer (https://github.com/noir-lang/noir/pull/4536) (13a12d5)
Update min compiler version of contracts (#5305) (dcf6bb3)
Use random tmp directory and cleanup afterwards (#5368) (5c0e15d)

Documentation

Update versions-updating.md (#5358) (0f09b63)

barretenberg: 0.31.0
0.31.0 (2024-03-26)
Features

Avm lookup and/or/xor (#5338) (489bc2c)
Earthly bb tests + arm + satellites (#5268) (eca12b3)
Fold proving key polys instead of prover polys (#5436) (239ebfb)
Less earthly runners + e2e GA runners, bb bench (#5356) (2136a66)
Read_calldata (#5409) (034fbf0)
Simplified bb Honk interface (#5319) (a2d138f)
Simplify offsets and sizing using new block structure (#5404) (efa0842)
Unified CircuitChecker interface (#5343) (13cef1f)
ZeroMorph working with IPA and integration with ECCVM (#5246) (c4dce94)

Bug Fixes

Revert cbind breakage (#5348) (c237193)

Miscellaneous

bb: Removed powers of eta in lookup and auxiliary relations (#4695) (f4e62ae)
ci: Create a dedicated job for the AVM unit tests (#5369) (59ca2ac), closes #5366
Clean out prover instance and remove instance from oink (#5314) (a83368c)
Meld flavor and and circuit builder modules (#5406) (f0d9d1b)
Moving public inputs back to instance (#5315) (9cbe368)
Name change: gen perm sort to delta range constraint (#5378) (841855f)
Remove mocking function in EccOpQueue again (#5413) (6fb4a75)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/AztecProtocol/aztec-packages/releases/tag/aztec-packages-v0.31.0 :sunflower:

:robot: Release is at https://github.com/AztecProtocol/aztec-packages/releases/tag/aztec-cli-v0.31.0 :sunflower:

:robot: Release is at https://github.com/AztecProtocol/aztec-packages/releases/tag/aztec-package-v0.31.0 :sunflower:

:robot: Release is at https://github.com/AztecProtocol/aztec-packages/releases/tag/barretenberg-v0.31.0 :sunflower:


Change  the vengeance indicators to use varbits

This pr

Makes the indicators way more reliable, especially veng other
Make veng and veng other use the same indicator since it's the same cooldown
Make it so the indicator is removed if the config is switched off

To clarify why the previous implementation wasn't very consistent.
Getting venge other'ed didn't trigger the venge active indicator as normal veng and veng other uses different graphics, but even then, the graphic would often be overwritten.
Using veng other also often doesn't trigger the veng cooldown timer as you aren't neccesarily interacting with the other player if you are moving while using the psell.


Suitable server for production enviroment  (apache/nginx) ?

I have written my APIs using crow, and for testing purpose i run the server using ./a.out. But server gets closed whenever any exceptions occurs. Since my code is all set to go into production, I would like to keep running my server irrespective of exception. Please suggest me a way, how to combine it with server like apache, nginx e.t.c

There is no official module to support the production environment. I am currently experimenting to reverse proxy Apache with Crow. Not sure about the performance advantage though.
https://www.digitalocean.com/community/tutorials/how-to-use-apache-as-a-reverse-proxy-with-mod_proxy-on-ubuntu-16-04
This article might be of help to you.

I tested performance of Crow with simple php script served by Apache2.
The performance was 4X downgraded when using Crow.

It's working except a few timeouts recorded while testing with wrk.

I was able to do it with nginx and it's working pretty well. How can I start the application server (crow server not nginx) as soon as it goes offline due to some reason.

Can you consider catch all exceptions on entry point?

I think catching all exceptions at entry point is great. In addition to that consider using docker to restart and run multiple instances of you app.

@All : I have started catching exception at entry point only. And I am running my application server with runit.


dein#util#_load_merged_plugins() raise E474

Problems summary
https://github.com/Shougo/dein.vim/blob/3f9b6412bb35c1e807e5c72563bd10e54a0fc53c/autoload/dein/util.vim#L433-L438
json_decode({string}) raise E474: Invalid argument when an item in a list is quoted by single quotes instead of double quotes (invalid json, like vimson).
Expected
json_decode should not be used while user might use neovim and vim and json and vimson is completely different.
Or
Do not use string({object}) to create a vimson and create a valid json (quote with double quotes) even in neovim or old vim.
Or
Simply use writefile() and readfile() instead of making json while merged just contain plugin names (but it solved _load_merged_plugins() function only)
Environment Information

OS:
Vim version: NVIM-0.1.3 vs Vim 7.4.1685

Provide a minimal .vimrc with less than 50 lines (Required!)
" In neovim, eval is used instead of js_decode
eval("['A']")
" => ['A']

" In Vim, js_decode is used instead of eval
js_decode("['A']")
" => E474: Invalid argument

" Opposite is OK
eval('["A"]')
" => ['A']
js_decode('["A"]')
" => ['A']

Reproduce

Remove ~/.vim/bundle/merged
Start neovim to create ~/.vim/bundle/merged
Start vim to load ~/.vim/bundle/merged

Screen shot (if possible)
The E474 raise cause something like the below

Upload the log messages by :redir and :message

OK.  Fixed.

Thanks :+1:


Can't run /createtown - Bad request: 400 : Invalid Form Body

Tried three times - errors as follows:

Queue Request [Guild:<PHONE_NUMBER>275889264]
Exception: BadRequestException
Message:   Bad request: 400 : Invalid Form Body
Stack trace:
   at Bot.DSharp.ExceptionWrap.WrapExceptionsAsync[T](Func`1 f) in /home/runner/work/bot-on-the-clocktower/bot-on-the-clocktower/Bot.DSharp/ExceptionWrap.cs:line 40    at Bot.Core.Interaction.BaseInteractionQueue`1.QueueInteractionAsync(String initialMessage, IBotInteractionContext context, Func`1 queuedTask) in /home/runner/work/bot-on-the-clocktower/bot-on-the-clocktower/Bot.Core/Interaction/BaseInteractionQueue.cs:line 60

Queue Request [Guild:<PHONE_NUMBER>275889264]
Exception: BadRequestException
Message:   Bad request: 400 : Invalid Form Body
Stack trace:
    at Bot.DSharp.ExceptionWrap.WrapExceptionsAsync[T](Func`1 f) in /home/runner/work/bot-on-the-clocktower/bot-on-the-clocktower/Bot.DSharp/ExceptionWrap.cs:line 40    at Bot.Core.Interaction.BaseInteractionQueue`1.QueueInteractionAsync(String initialMessage, IBotInteractionContext context, Func`1 queuedTask) in /home/runner/work/bot-on-the-clocktower/bot-on-the-clocktower/Bot.Core/Interaction/BaseInteractionQueue.cs:line 60

Queue Request [Guild:<PHONE_NUMBER>275889264]
Exception: BadRequestException
Message:   Bad request: 400 : Invalid Form Body
Stack trace:
    at Bot.DSharp.ExceptionWrap.WrapExceptionsAsync[T](Func`1 f) in /home/runner/work/bot-on-the-clocktower/bot-on-the-clocktower/Bot.DSharp/ExceptionWrap.cs:line 40    at Bot.Core.Interaction.BaseInteractionQueue`1.QueueInteractionAsync(String initialMessage, IBotInteractionContext context, Func`1 queuedTask) in /home/runner/work/bot-on-the-clocktower/bot-on-the-clocktower/Bot.Core/Interaction/BaseInteractionQueue.cs:line 60

Either I don't understand the 'setup' for this bot, or it simply isn't working

Sounds like something is busted, not that you're doing anything wrong. I'll try to find some time to take a look.

I'm able to reproduce this locally but I haven't had time to dig any further. Probably something changed about Discord's API, I'm guessing.

This is happening for me when I run /game as well.

Hmm the error message here is
{   "allowed_mentions": {     "_errors": [       {         "code": "MODEL_TYPE_CONVERT",         "message": "Expected an object/dictionary."       }     ]   } }

I've deployed a new version that seems to fix this issue! Still have no idea why it suddenly started happening.


build(application): Set the "Main-Class" attribute

This is not actually done by Gradle's application plugin, so set it manually to allow the JAR to be run via java -jar ....

Not really needed as dependent JARs would not be on the classpath anyway.


fix(schema): added description on esModule

This PR contains a:

[ ] bugfix
[ ] new feature
[x] code refactor
[ ] test update
[ ] typo fix
[ ] metadata update

Motivation / Use-Case
Added 'description' field on esModule option.

Breaking Changes

Additional Info

CI is not passing
run npm run test locally
I guess is there some security alert, you need to do auditing of the dep

Yes, Its passing everything in locally.

npm audit ?

There was a security issue on serialize-javascript, fixed this. thanks @anikethsaha

cool 👍


GC optimization & reuse in core forwarding flow

Mosn reclaims and reuses the temporary memory in each module the handling mechanism is relatively fragmented and unsystemized. It is necessary to perform an integrated memory reuse scheme based on the main stream forwarding flow, which provides simple memory usage pattern and better gc performance due to smaller memory footprint.

Fixed by #169


SP 5490: Backport of PDI-18569

:x: Build failed in 45m 22s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine

:ok_hand: All tests passed!
Tests run: 3634, Failures: 0, Skipped: 7    Test Results

Errors:
Filtered log (click to expand)

script returned exit code 1

:information_source:  This is an automatic message

:white_check_mark: Build finished in 33m 53s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine

:ok_hand: All tests passed!
Tests run: 3634, Failures: 0, Skipped: 7    Test Results

:information_source:  This is an automatic message


Feature/improve doc

Improve doc for MTS

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

Ready to merge.


Add a list store example

Still working on this?

Now we have 4th list store example

What can I say.. lists are important ;-)

Still working on this?

Will address comments later today.

This is ready to go.

Looks good to me apart from

https://github.com/gtk-rs/examples/pull/221/files#r255327253
https://github.com/gtk-rs/examples/pull/221/files#r250937432
https://github.com/gtk-rs/examples/pull/221#discussion_r255316835

Thanks :)

Ready to merge.

Thanks a lot!


Add New Component Axial Linking Approach

What is the change?
Closes #769. A request was made to improve the axial linking logic to take advantage of the block grids system in ARMI. This PR aims to accomplish that. While previous behavior is maintained, there are several changes:

AssemblyAxialLinkage::_getLinkedComponents now allows for multiple component axial linkage. Any components with multiple linkages are resolved in AxialExpansionChanger::retrieveLinkedComponent.
AxialExpansionChanger::retrieveLinkedComponent accounts for 3 cases to try and resolve the multiple axial linkage. See test_axialExpansionChanger.py::TestRetriveAxialLinkage for details.
Tests have been added and modified to account for new grid block behavior.
i. A block grid was added to armi/tests/detailedAxialExpansion/refSmallCoreGrid.yaml
ii. Additional complexity was added to the simple assembly defined in test_blockBlueprints.py.

Why is the change being made?
To support a user request for downstream analyses.

Checklist

[x] This PR has only one purpose or idea.
[x] Tests have been added/updated to verify that the new/changed code works.

[x] The code style follows good practices.
[x] The commit message(s) follow good practices. Keckler let me know that commit history isn't important, so the world gets the working branch!

[ ] The release notes (location doc/release/0.X.rst) are up-to-date with any important changes.
The documentation is still up-to-date in the doc folder. Another item for #935....
[x] The dependencies are still up-to-date in setup.py.

I pushed some changes to this branch so that the axial expansion changer can properly handle blocks that don't have any solid components. This was leading to issues with assemblies accidentally changing overall height, which is not supposed to happen (the DUMMY block is supposed to compress to allow for the overall assembly height to remain unchanged).
I also added a test on this fix.

I have absolutely no clue why some of the bookkeeping related tests are failing. I am not seeing any failures when I run locally on 3.9, and I don't think that I made any changes that are related to the operation of the database code.

I do not know why this branch is now seeing some test failures in the bookkeeping module. I do not see any errors when I run those tests locally with 3.9, and I did not make any changes related to the bookkeeping module.

Okay, after some offline discussion with @albeanth , the changes that I mentioned in the comment above have been rolled back. Instead of trying to handle them, we are explicitly going to block users from having blocks in their assemblies that don't have any solid components in them. In such scenarios, it is unclear how the axial expansion should be performed and so we just disallow it. The exceptions to this are:

The dummy block
An assembly with no solid components at all is allowed.

I added the appropriate logic and an associated test.

@keckler a subtle hint hint you want this sooner than later, eh? 😄

I can't run my model without this branch, so at the very least I needed to get the merge conflicts resolved. But yes, sooner is better!

I will carve some out time this week to restart this effort. I know John would like to see this PR gone too!

I'll just close this for now. This PR is tracked elsewhere so it's not going to get lost. When this work gets prioritized I'll reopen it.

@keckler @john-science We need to push this through.

Hey @keckler & @albeanth,
Will you ask Dana and Casey if they can decrypt this: https://youtu.be/F_PmQFr5CTY?si=QsVNSxIgP8cNzO0S
They have no idea what's coming.

@keckler @john-science We need to push this through.

this will come through ~6 months.


WIP: Overhaul Playground.jl

I did some heavy refactoring of the Playground.jl package for the purpose of improving maintainability and reliability. Code should be in a working state.
One outstanding issue is that I think that this package should be renamed to "Playgrounds.jl" as I think that I would like to rename the type PlaygroundConfig to just Playground.

Looks like a new version of Lint.jl got released which is causing me issues here.

FWIW, the Lint.jl issue is a result of the new release, which is why I added the following commit to master the other day. I'll update dev with a real fix soon.

So, so my general comments so far.

I'd like to see the coverage back up to ~88% before I merge.
I'm not sure I like the "CORE" change. I'm not suggesting I like the current setup more, but I don't think "CORE" is very descriptive. Maybe "SHARED" or "USER"?
With regard to renaming I'm not inclined to do that at the moment cause of complications with METADATA. I don't think we should just rename it on people, but I also don't want to clutter up the METADATA registry.

Honestly, I dislike julia's pkg naming conventions for exactly this reason (it is more likely to create name conflicts between modules and regular types) and would rather the pkg be called "playground".

Is your issue with "CORE" strictly just the name? Using Git as an example the naming convention there is: system, global, and local. I think maybe "ROOT" could be a good name. I don't like "USER". Maybe "SHARED_ROOT"? What do you think?

It is very much a naming issue, but since a lot of the merge request is improving readability we should pick names that make sense. I don't like "ROOT" either cause it doesn't really describe what it is. I think probably our 3 best options in order of my preference are "SHARED", "COMMON" or "GLOBAL" as they are best at describing why we have this shared or common user level directory.


TypeError: Cannot read property 'ack' of null

Describe the bug
When I tried to change any state of the light it never worked neither using the iobroker interface or any other iobroker interface.
To Reproduce
Steps to reproduce the behavior:

Go to 'iobroker Objects'
Click on 'hue.0' (and other subfolders)
Try to change any state of a light bulb
It turnes red and the following error log appears:

Stacktrace
hue.0 | 2020-02-20 09:46:33.143 | error | at process._tickCallback (internal/process/next_tick.js:68:7)
-- | -- | -- | --
hue.0 | 2020-02-20 09:46:33.143 | error | at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
hue.0 | 2020-02-20 09:46:33.143 | error | at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
hue.0 | 2020-02-20 09:46:33.143 | error | at client.mget (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:619:13)
hue.0 | 2020-02-20 09:46:33.143 | error | at states.getStates (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5922:17)
hue.0 | 2020-02-20 09:46:33.143 | error | at adapter.getStates (/opt/iobroker/node_modules/iobroker.hue/main.js:207:17)
hue.0 | 2020-02-20 09:46:33.143 | error | at handleParam (/opt/iobroker/node_modules/iobroker.hue/main.js:132:55)
hue.0 | 2020-02-20 09:46:33.143 | error | (12215) TypeError: Cannot read property 'ack' of null
hue.0 | 2020-02-20 09:46:33.143 | error | (12215) uncaught exception: Cannot read property 'ack' of null

Expected behavior
The light bulb should turned on and the stat in ioBroker should not be red.
Screenshots & Logfiles
See Stacktrace above.
There seems to a null-case in line 132 of main.js.
Versions:

Adapter version: 3.2.2
JS-Controller version: iobroker.admin 4.0.3
Node version: 10.18.1
Operating system: Raspbian 10.2
Bridge model:

Additional context
I already prepared a PR which catches the null and made it working again for me.

In this case the state had no value. It can happen directly if you "Kill" your state DB (or it gets corrupt) or such ... so because of a reason the state value was killed ...


bydbatt

sorry, stable after latest, else testing is alewys red

sorry, stable after latest, else testing is alewys red


Fail fast on invalid rename, i.e do not show the input box asking for new symbol name

Environment data

VS Code version: 1.43
Extension version (available under the Extensions sidebar): 2020.2.64397
Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info #3977): tested with both. Doesn't seem to effect this

Steps to reproduce:

In a python file, place cursor on None and try to rename it using F2
See input box
Enter a new name and press enter

Bug
See notification that says No result!
Here's what our builtin js/ts extension shows for this case (we show this before the input appears):

This is implemented using prepareRename: https://github.com/microsoft/vscode/blob/c0c9e0043ce6133042268f22847021ad9a1ce410/extensions/typescript-language-features/src/features/rename.ts#L34

Another case: no refactoring library is installed

Hi @mjbvz
Apologies for the late response. Unfortunately, I am not able to repro this behavior. For me, I get the error notification
Refactor failed. Rename refactoring should be performed on resolvable python identifiers. [<FrameSummary file refactor.py, line 382 in watch>, <FrameSummary file refactor.py, line 352 in _process_request>, <FrameSummary file refactor.py, line 260 in _rename>, <FrameSummary file refactor.py, line 129 in refactor>, <FrameSummary file refactor.py, line 156 in onRefactor>, <FrameSummary file c:\Users\karraj\Desktop\isort\.venv\lib\site-packages\rope\refactor\rename.py, line 28 in __init__>]

When trying to use F2 (Rename symbol command) on None.
Do you have the library rope is installed? Please send the python output channel and logs mentioned in the template.

Just to confirm: the bug is that it should fail as soon as you press f2; I should never see the input box in these cases because we know the rename operation will fail

I see, yes that's something we could improve.

ctags/rope is being removed  in the 2021.10 release (#17225) so this issue is now stale. Please try using Jedi or Pylance language servers for renaming.

Another case: no refactoring library is installed

ctags/rope is being removed  in the 2021.10 release (#17225) so this issue is now stale.

This is still a issue with all language servers.


[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative-sandbox/channel-wg-leads
/assign knative-sandbox/channel-wg-leads
Produced by: knative-sandbox/knobots/actions/update-deps
Details:
bumping knative.dev/eventing 23198cd...40fa622:
  > 40fa622 Fix cloudevent adapter panic (# 5424)
  > 18a70de Convert channel event transformation e2e to rekt (# 5423)
  > d74ca9d Update community files (# 5420)
  > 869220a Disable chaosduck on the webhook (# 5419)
  > 5af518d [QE] Extension point for transport used to send events in upgrade tests (# 4815)
  > cf5b0eb upgrade to latest dependencies (# 5417)
bumping knative.dev/reconciler-test 8d70771...ffe49e0:
  > ffe49e0 Update community files (# 201)
bumping knative.dev/pkg 67897f4...e749d6a:
  > e749d6a Update community files (# 2129)

/retest


FileUpload doesn't fully support non-seekable streams

FluentFtp version: 33.0.3
LOC: https://github.com/novak-as/FluentFTP/blob/master/FluentFTP/Client/FtpClient_FileUpload.cs#L724
"FluentFTP.FtpException: Error while uploading the file to the server. See InnerException for more info.
 ---> System.NotSupportedException: Specified method is not supported.
   at System.Net.Http.HttpBaseStream.get_Length()
   at FluentFTP.FtpClient.UploadFileInternalAsync(Stream fileData, String localPath, String remotePath, Boolean createRemoteDir, FtpRemoteExists existsMode, Boolean fileExists, Boolean fileExistsKnown, IProgress`1 progress, CancellationToken token, FtpProgress metaProgress)
   --- End of inner exception stack trace ---
   at FluentFTP.FtpClient.UploadFileInternalAsync(Stream fileData, String localPath, String remotePath, Boolean createRemoteDir, FtpRemoteExists existsMode, Boolean fileExists, Boolean fileExistsKnown, IProgress`1 progress, CancellationToken token, FtpProgress metaProgress)
   at FluentFTP.FtpClient.UploadAsync(Stream fileStream, String remotePath, FtpRemoteExists existsMode, Boolean createRemoteDir, IProgress`1 progress, CancellationToken token)
  ...

Stream type:
{Name = "ContentLengthReadStream" FullName = "System.Net.Http.HttpConnection+ContentLengthReadStream"}
    Assembly: {System.Net.Http, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a}
    AssemblyQualifiedName: "System.Net.Http.HttpConnection+ContentLengthReadStream, System.Net.Http, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" ...

There is a check for not-seekable streams, but Length also throws NotSupportedException if steam isn't seekable (https://docs.microsoft.com/en-us/dotnet/api/system.io.stream.length?view=netcore-3.1)

This is correct. Some users have worked around by first buffering their stream into a MemoryStream or similar and then giving it to FluentFTP. Due to technicalities, we NEED to know the length of the file otherwise we cannot transfer it.
If you think it is a bug and that its possible to support non-seekable streams, you are welcome to submit a PR.

If you think it is a bug and that its possible to support non-seekable streams, you are welcome to submit a PR.

I blame the design of System.IO.Stream. I understand the .NET BCL team agrees it's poorly designed - hence the love for the new System.IO.Pipelines.
I'm not really able to submit a PR, but I would propose not using Stream directly, but instead requiring all input to be using a simple wrapper struct which means more cases can be handled:
struct StreamWithLength
{
    public static implicit operator Stream(StreamWithLength self) => self.Stream;

    // Implicit conversion for known-good Stream subclasses:
    public static implicit operator StreamWithLength(FileStream fs) => new StreamWithLength( fs );
    public static implicit operator StreamWithLength(MemoryStream ms) => new StreamWithLength( ms );

    public StreamWithLength( Stream stream, Int64 length )
    {
        this.Stream = stream ?? throw new ArgumentNullException(nameof(stream));
        this.Length = length; // TODO: Validate length?
    }

    // Specialized constructors:

    public StreamWithLength( FileStream fileStream )
        : this( stream: fileStream, length: fileStream.Length )
    {
    }

    public StreamWithLength( MemoryStream ms )
        : this( stream: ms, length: ms.Length )
    {
    }

    public Int64 Length { get; }
    public Stream Stream { get; }
}

As it has implicit conversion to/from Stream it should be a drop-in replacement.

Here is a good implementation of non-seekable streams. Rather then calculate progress for user you can return total sent bytes and user can do his own progress implementation.
https://github.com/sshnet/SSH.NET/blob/develop/src/Renci.SshNet/SftpClient.cs#L2274


[8.x] test helper runs to make new files, but first test run uses old files

The test helper will properly run the script to rebuild the webpack bundles, but the server seems have loaded the older bundles, so so the server or client in integration tests needs to be told to refresh.
How do we know?
Make a change to do some logging in the JS code and the log in phantom js shows the old print statements, not the new ones that just changed.
If you change the script to build the test files, the tests will totally fail as the old file has been deleted. This is certainly related to the webpacker lite helpers using the old version of the manifest. Maybe there is some caching of the manifest in the test env?
"build:test": "rm -rf ../public/webpack/test && NODE_ENV=test yarn run build:client && NODE_ENV=test yarn run build:server",

Fixed by using 2.0.4 of https://github.com/shakacode/webpacker_lite.


Java Manipulators ( OOPs section)

Add in example for Java manipulators and explain the concept of manipulators.

I would like to try to work on this.

@dinitrogen-tetroxide, please update whenever you are done, and please have some time constraints for the task.

I will. I should be done with it in 4 days.

hey, I would like to contribute..

Not sure how that works. This is the first time I've worked on a PR.

I've finished the file. I mentioned this issue in my pull request.


Refactor Settings Screen. Introduce ViewModel

Fixes #97

Please give feedback on this redesign:
https://github.com/user-attachments/assets/c3103a15-4f8e-4860-a164-fa9172114833


Record multi clamp series resistance

It looks like we missed adding series resistance to the .NET version of the multi clamp data structure.
https://github.com/Symphony-DAS/symphony-core/blob/1ea41a6837e02cc019635a95e836af8964dc2356/src/symphony-core/Symphony.ExternalDevices/MulticlampInterop.cs#L436
We should add it and make sure it is recorded in the data file.

https://github.com/Symphony-DAS/symphony-core/commit/94c691b3ad4f01246fa32f55d24476b856393368


Instrument property in proteomics domain is not precise

What are you missing?
For users the property "instrument" when registering measurements is not clear, since it can be the LC system, the mass spec device, or both.
What we actually expect, is the ms device.
Why do you need a solution?
It is unclear for the users what is expected.
Ideas
Maybe just call it MS device, and be precise.
Code of Conduct

[X] I agree to follow this project's Code of Conduct

No need to change instrument for NGS (@oquendoM)


Clean up function instances after deleting the broker cluster when using the Kubernetes runtime

Is your enhancement request related to a problem? Please describe.
In a Kubernetes environment, if the functions are not deleted before the broker cluster is deleted, the function objects (StatefulSets and Services) are left undeleted. It seems the best practice to clean up these objects is to add customized labels to the Kubernetes runtime configuration and then find objects to delete with these labels, is it?
Describe the solution you'd like
Pulsar may accept an owner reference as a new Kubernetes runtime configuration and add the owner reference to function objects automatically. The owner reference might point to an object representing the broker cluster. And when the broker object is deleted, the function objects should be deleted by the garbage collector automatically.
Describe alternatives you've considered
Additional context

The issue had no activity for 30 days, mark with Stale label.

Closed as stale and no one worked on it. If anyone wants to continue it, feel free to reopen and submit a patch.


Remove "panel" theme property from ButtonGroup

A leftover from the time it was its own node.

Thanks!


Add support for health endpoint

This change adds an optional health endpoint path which will return a 200 status code.
This is useful for environments where you might be deploying this as a Docker service behind
a service discovery mechanism or load balancer which has a health check.
You can set either the -H flag or specify the HEALTH_PATH environment variable as in this example:
HEALTH_PATH=/health aws-es-kibana

When specified, you’ll see this additional console output:
Health endpoint enabled at http://<IP_ADDRESS>:9200/health

Thanks to @williamhaley for the assist!
I also had to update the AWS-SDK to add support for ECS task IAM roles.

Anything I can do to move this PR along?

I double for having it. It looks relatively simple as long as conflicts are resolved

Up to date now.  I also bumped the sdk version because ECS IAM credentials aren't supported in the version you were using.


contentChanges in onDidChangeTextDocument may be manipulated by other extensions

I don't know if this is really a bug, but it exposed a bug in the Dart extension and I thought I should highlight it.
VS Code usually sorts the edits passed to onDidChangeTextDocument in reverse-order, so that if they are applied sequentially (without dealing with the fact that offsets are all based on the original document) they still work. Based on @alexdima's comment at https://github.com/microsoft/vscode/issues/11487#issuecomment-244977115 I don't think this is guaranteed, but it is the current behaviour (even if I send edits in offset-ascending order, they come through in offset-descending order).
Dart was accidentally taking advantage of this - and edits are applied by the language server sequentially. Some users reported weird behaviour, which turned out to be a different extension they had installed called reverse() on contentChanges, which resulted in the edits being reversed when they got to Dart, and thus we sent nonsense edits to the language server (the result was weird phantom errors).
The "bad" extension code is here:
https://github.com/austenc/vscode-blade-spacer/blob/ae88ae1e82719c7b9fc088b93903285ac61b283a/src/extension.ts#L35
It's not really bad - in that, Dart should not have assumed the order of edits would always be reverse-offset (it's not specified to be that way), however it's an easy trap to accidentally fall into (especially as the docs do not call this out at all). It also seems strange for another extension to be able to upset things in this way.
I think the docs should at least call out in the onDidChangeTextDocument description (and the contentChanges field) that edits should not be assumed to be in an order that can be applied sequentially, or they should always be provided this way (and not allowed to be manipulated by other extensions).
(Note: I'm fixing Dart to sort them when sending to the language server - this was definitely my bug - but it'd be good to reduce the chances of others having it in future - especially when it's not so easy to track down when caused by another extension doing something like this).

Oops, I hit submit too quickly before reading the dupe suggestions. This was raised a few days ago and fixed a few hours ago in:
https://github.com/microsoft/vscode/issues/88310
That said - I think the docs should still be clearer here. If the intention is to guarantee the order, I think it should be documented so we know if we can rely on it.
cc @jrieken
@dbaeumer I think the LSP spec should be clearer about this too. I suspect I have a similar bug in our server there if this extension would also cause the LSP client to send the changes in the wrong order.

@jrieken can you clarify the guarantees here? The issue was fixed as if VS Code is going to guarantee the order, but the docs do not mention this (one way or the other). It would be better if the spec was explicit to avoid this coming up again (and it not being clear if it's a bug).


fix: do not reward beneficiary if with_reward_beneficiary is false

Currently, the coinbase address appears in the write_set before self.apply_rewards(...) is called. This is causing all txs to depend to each other.

Merged the fix into dev and reth2.


docker-compose: 2.20.3 -> 2.21.0

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 252476 run on x86_64-linux 1

22 packages built:

apptainer
apptainer-overriden-nixos
apx
charliecloud
docker (docker_20_10)
docker-client
docker-client.man
docker-compose
docker-gc
docker.man (docker_20_10.man)
docker_24
fn-cli
nvidia-docker
pipework
python310Packages.jupyter-repo2docker
python310Packages.jupyter-repo2docker.dist
python311Packages.jupyter-repo2docker
python311Packages.jupyter-repo2docker.dist
singularity
singularity-overriden-nixos
udocker
udocker.dist


Provide testing support for Python 3.12 – drop support for {3.8, 3.9}

This PR:

adds testing for Python 3.12 (+ update 1 test that failed in Python 3.12)
drops testing for Python {3.8, 3.9}
provides clear "oldest" and "no-optional" CI environments
updates workflows accordingly
updates docs accordingly
couple other minor odds and ends

@martinfleis, I am not sure why dev is failing here for installing shapely. Seems like we are doing the same thing in momepy with no problem. I am probably missing something fairly obvious...


Gridview

anyone care to review ?  please also see screenshot

@nomwerp wow!! Nice feature. The only thing I see, is the overlapping of text in some of the rows. Maybe increasing the height of elements will help?

thanks,  yeah the overlaps get worse with real  (longer) data. it seems something is messed up with gridview,  all bits are set to wrap content for height but for some reason some of the rows that have text wrapping seem to get the wrong height...

An issue that I noticed throughout the project is that layout files referring to "dimen" resources that do not exist. Am I the only one that has this issue?

@Pho3niX90 i'd guess android sdk version issues?   for example: @dimen/abc_text_size_large_material seems to be defined in
build/intermediates/exploded-aar/com.android.support/appcompat-v7/22.1.1/res/values/values.xml
maybe build.gradle needs updating?
    compile 'com.android.support:appcompat-v7:22.1.1'```

I made some changes to the files to prevent the overlap of text. I hope I did it correctly in github for you to see

@Pho3niX90  yeah i see your (now closed?) pull request #116 , is the main trick to add an empty text view below each result_view item?
        android:layout_width="fill_parent" android:text=""></TextView> ```

the layout_span doesn't seem to help for me but if you give it a background colour it nicely highlights the issue:

@nomwerp you can active the "view layout bounds" on your device's Developer Tools, for debugging how the rows are rendering exactly.

Sorry I redid it. There are 2 file changes.

Only diff is I have the altitude in the gps as well.

thanks! will have a closer look at it later

@nomwerp is this to be merged or closed?

please merge if you're happy with it, as you see from the screenshot there are still some minor issues but we can work on them later

@Pho3niX90 thanks for your suggestions, adding extra space does definitely help but doesn't seem to solve the issue with the gridview itself, I'll try to sort it later.

Any updates on this?

hey,  just close it.  too far behind to merge it now
would still be nice to have a gridview...
On Thursday, 12 May 2016 04:51:53 CEST Paulo Pires wrote:
Any updates on this?
—You are receiving this because you were mentioned.Reply to this email directly or view it on
GitHub[1][2]

[1] https://github.com/pires/android-obd-reader/pull/115#issuecomment-218734978
[2] https://github.com/notifications/beacon/AJpBTnXpek5jrmR6awFUE3cZ_y6gusb-ks5qAxRZgaJpZM4FbiXU.gif


Fix completion details auto-imports crashes

Fixes #52661
The ExportInfoMap is a multimap that contains information about every way that every export is re-exported from different places. Usually, a single symbol that gets re-exported multiple times has a single key pointing to an array of each place it’s exported from. When auto-imports are displayed in completions, we show one completion per key, and we simply pick the “best” re-exporting location out of that array. This lets us prefer short import paths over deep imports. (When and whether this is actually a good heuristic is beside the point.)
The exception is when a single symbol is exported by an ambient module. Ambient modules are considered a stronger signal that the name of the module is significant. For example, when "node:fs" re-exports everything from "fs", we don’t want to be forced to pick which module is the “better” place to import readFile from—we’d rather show a completion for both, even though the exported symbol is the same in both. So each of these get their own keys in the multimap.
When completionEntryDetails is called and we have to re-find the export we showed in the previous completionInfo request, we never used to check the module symbol when searching the ExportInfoMap—instead, we asserted on it later, issuing the message seen in the telemetry bug. The fix is simply to check that the module symbol matches as part of our search instead of returning the first export info where just the export symbol itself matches.
The fix sounds obvious, so why was this not more broken before? Well, when completionEntryDetails is called for an import from an ambient module, we were able to take shortcut that skips this search through the ExportInfoMap containing the faulty code. So the only way for the bug to manifest is when we request details for a symbol that a non-ambient module re-exports from an ambient module, and the iteration order mattered—it could have been correct by coincidence sometimes.

@typescript-bot user test tsserver

we were able to take shortcut that skips this search through the ExportInfoMap containing the faulty code

Actually, that shortcut is the other stack trace that shows up in the user tests. I suspect they’re different root causes, but maybe I’ll try to tackle that one too in this PR.

@typescript-bot user test tsserver
@typescript-bot perf test this

@typescript-bot user test tsserver

Hm, my last commit fixed the npm repro I was able to get locally. Not sure what’s going on there now.

I can’t repro those last two crashes locally, so I’m giving up on them for now. This fixes the large majority of the ones reported at #52660.


added airspeed to ekf2 replay

@CarlOlsson Is this complete and good to go? Can you attach plots of the replay?

Yes it should work. Will update with plots in a sec

Airspeed innovation

The log file

Jenkins test this please.

Jenkins test this please.

Jenkins test this please.

Rebased and applied.


Python: readded mocked HF unit test

Motivation and Context

We moved all Hugging Face tests to integration, because they connect to HF to download models, now readded tests with mocking, not yet for streaming.
Description

Contribution Checklist

[x] The code builds clean without any errors or warnings
[x] The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
[x] All unit tests pass, and I have added new tests where possible
[x] I didn't break anyone :smile:

Python 3.10 Test Coverage Report • FileStmtsMissCoverMissingsemantic_kernel/connectors/ai/hugging_face/services   hf_text_completion.py42420%3–149TOTAL567089284%
Python 3.10 Unit Test Overview

Tests
Skipped
Failures
Errors
Time

1287
1 :zzz:
0 :x:
0 :fire:
14.757s :stopwatch:


Introducing Local/Remote release deployments

In this PR we introduce the possibility to deploy local or remote release to the docker registry

Nice.  Just read the docs on ADD vs. COPY for a dockerfile.  Looks like this was easier than you thought it would be eh?  :)

yes it was :)


Footer Section

There isn't a proper footer in this website, So i work on this issue and want to give a proper footer to this website, Please assign this issue to me under SWOC(Social Winter of Code)

@saismrutiranjan18 Wait until 1st January,2025

@saismrutiranjan18 Wait until 1st January,2025

Okay

@saismrutiranjan18 Issue Assigned to you


Numbers only crashing plugin

If you type in any repeating string consisting of the same numbers repeated over and over, it causes a memory overflow.

Yes, that's a problem. I tracked it down to the leet speak detection in Password Score. Simple solution: turn of leet speark support. Will also work on a better solution.


[ Adaptation Prompt] Fix llama rotary embedding issue with transformers main

Currently the adaptation prompt slow tests are failing on transformers main due to a recent refactor to add compatibility with static cache. https://github.com/huggingface/transformers/pull/27931
That PR broke the adaptation prompt forward pass, as module.rotary_emb forward pass now have position_ids as a required argument, thus breaking the current impmelementation of llama roatary embedding as we don't pass position_ids in PEFT.
In addition, cos / sin are now directly indexed through that method, therefore we don't need to call our method that also indexes cos / sin with positon_ids. As computing the query states given cos / sin is a one-liner, I slighlty modified the logic in llama_compute_query_states to make sure the forward pass works fine with transformers main
cc @pacman100 @BenjaminBossan

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


[BUG] Points with image pointStyle render when pointRadius: 0

Expected Behavior
Points should not render if pointRadius: 0, no matter if the pointStyle is an image or one of the other styles. Similarly, a point should render on hover if pointHoverRadius > 0, no matter the pointStyle.
Current Behavior
The points render despite pointRadius being set to 0.
Possible Solution
Seems like a simple enough thing to fix if you know where to look in the code (wouldn't mind submitting a PR but don't know my way around).
Steps to Reproduce (for bugs)
https://codepen.io/anon/pen/qMLgoB
Environment

Chart.js version: 2.7.2
Browser name and version: Chrome (latest)

This is solved in v3.0.0-beta.7 https://codepen.io/etimberg/pen/yLaPePO


[Distribution] Do not call abortReleaseUpload API when uploading file failed

Context: We are deprecating PATCH /v0.1/apps/{owner_name}/{app_name}/release_uploads/{upload_id} API (openapi.appcenter.ms swagger link). When calling App Center CLI with incorrect build number AND incorrect build version (see command below) at the same time, the CLI will call the deprecated PATCH API with aborted on file upload failure.
appcenter distribute release --file <localFilePath> --app <appName> --group <groupName> --build-version <build-version> --build-number <build-number>
We investigated the distribute backend and discovered the aborted release upload status is never used in any meaningful way. We should stop using aborted status.
Solution: On the client-side, CLI will no longer call any aborted API on upload failure. The server side will be fixed in a different PR.

FYI @atkhalsa

@dhei could you please share the PR which actually fixes the backend behavior

Solution: On the client-side, CLI will no longer call any aborted API on upload failure. The server side will be fixed in a different PR.

I think server-side should go first in such case and only if it has no issues we can complete this PR.


Question::What is the default path used by tldr for cache management ...

Under Linux/Ubuntu system, What is the default path used by tldr for cache management.
For eg, options '--update' & '--clear-cache' updates and clear the tldr cache ...
Is there any config option to move cache to custom location ?

Under Linux, the XDG cache directory (by default ~/.cache/tealdeer) is used. It can be overridden using the TEALDEER_CACHE_DIR variable.
This should probably be documented in the docs, and there should be a command to list all directories...

Nice, cfg option "TEALDEER_CACHE_DIR" is working fine.
Thanks

I'll re-open the issue to keep it as a reminder to update the docs :slightly_smiling_face:


Log errors in ALTS handshaker initial op completion cb

It's possible for errors to be posted to the on_handshaker_service_resp_recv cb because the initial batch of ALTS stream ops doesn't have a recv_trailing_metadata op (errors would only show up in its status if it did).
The problem is that we're currently calling back the inner recv message op callback with true unconditionally, and swallowing such errors. As a result, errors in the initial batch of ALTS handshake stream ops result in the following log message, which is tricky to make sense of:
recv_buffer is nullptr in alts_tsi_handshaker_handle_response()

There's an internal stress test that sees a lot of these log messages. This patch changes things so that the stress test logs will now have enough context to reveal the ALTS handshake error causes.

node macos: https://github.com/grpc/grpc/issues/20095
RBE tsan C/C++: https://github.com/grpc/grpc/issues/19726
interop cloud-to-prod is failure to build  java docker image due to flake downloading dependency


Bug: (perfectionist/sort-switch-case) default and 'default' cases are separated

Describe the bug
default and 'default' get sorted and produce invalid code
Code example
switch (variant) {
  default:
  case 'default':
    return 1;

  case 'userList':
    return 2;
}

gets fixed to:
  switch (variant) {
    case 'default':
      return 1;
    case 'userList':
      return 2;

    default:
  }

which produces broken code
ESLint version
v9.14.0
ESLint Plugin Perfectionist version
v3.9.1
Additional comments
No response
Validations

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

Hello! Thank you for your issue!
Sounds strange. It seems we have already fixed this issue in #229.
I'll try to reproduce the problem.

I understand your problem. This is a different problem. At the moment we expect the default case to be at the end.
To be honest, this is the first time I see this style of writing switch-case. This is a bug, we will fix it. Thank you!

This issue is fixed in next: the sorting result is
switch (variant) {
    case 'userList':
        return 2;
    case 'default':

    default:
        return 1;
}

@hugop95 Awesome. I unfortunately could not find a corresponding test case in test/sort-switch-case.test.ts. Perhaps if it is not there, it should be added.

The issue example can be simplified to
 switch (variant) {
    default:
    case 'default':
        return 1;
}

which gets sorted to
switch (variant) {
    case 'default':
        return 1;
    default:
}

@azat-io Good idea!

Fixed in 960e21c49f56155a13f1bccc47ab35d649bc67e4.
Released in v4.0.0.
If you'd like, you can support the release with a retweet:


[rest] add response backcompat mixin

fixes #20600
running autorest test suite with these new responses https://github.com/Azure/autorest.python/pull/1047

/azp run python - cosmos - ci

@xiangyan99 I'm going to split out the removal of _return_pipeline_response from this PR. It will be in a separate PR that will probably merge next release (have talked about it with @lmazuel )

/azp run python - storage - ci

/check-enforcer override


Need cart functionality

In cart needed functionalities like remove a product from cart.
Buttons like proceed to payment or checkout.

I like to add a cart functionality


Large laggies due to dynamic light from the first person

Large laggies due to dynamic light from the first person
If you turn off the light from the first person, there are no lags
Maybe it's because of someone else's fashion
Frametime when I hold a glowing object in my hands

Default frametime

Steps:

Join in the world
I pick up any luminous object
Big laggs

Mods

OS Windows 10
Minecraft version 1.21
Fabric Loader version 0.16.0
Mods: in screenshots
Version 0.2.9

Honestly, I tried to figure out what the problem was, turned off the mods, turned them on and nothing helped. The problem is fixed if I run the game with a maximum of 20 mods
there may be an incompatible mod, but I still haven't been able to figure out which one
if anything, dynamic resources are disabled in the mod Modern Fix, so it shouldn't affect

For my modpack:
Lag spikes with moving dynamic lights are a triple combo.
Spent 20 hours on it.
3 reasons (if even one of these issues isn’t fixed, the problem will persist):

A conflict between ModernFix (mixin.perf.deduplicate_location=true) and CopyCats mod.
CopyCats creates new ResourceLocation  very many times per tick at com.copycatsplus.copycats.compat.Mods.rl(), which shouldn't happen.
Since deduplicate_location tries to fix duplicated ResourceLocations it caused lag spikes.
https://github.com/copycats-plus/copycats/issues/176

The modpack had the Embeddium option "chunk_builder_threads": 1  enabled.
By default, it’s set to 0, meaning the number of threads is determined automatically (at least 2-4 for modern CPUs).
A single thread caused various issues, including with this option.

I was trying to figure out why the BetterMC modpack didn’t have this problem at all, while it was very noticeable in mine.
Using binary search, I discovered that BetterMC had the option always_defer_chunk_updates": true enabled in its Embeddium config.

Result:
All issues identified and resolved. No more lag from dynamic lights at all.


Limit number of attempts that can be made to auth using OTP

The limit is necessary otherwise the OTP (4 digits) can easily be brute forced.

Good catch! Thanks. I can't believe I missed this.


Fix for #32342

When expanding abbreviations, do so from bottom to top.  This way a change higher up will not interfere with text below.

Thanks @jmdowns2!


captcha invalidates "Use view to create"

This time, since captcha is not in a form, it doesn't repeat and you simply can't finalize your view.
So captcha works, but sometimes not where it is needed :smile:

I think this is now fixed if on https://github.com/saltcorn/saltcorn/pull/1508 and version 0.1.4 of this plug in. I might try to implement hcaptcha to see if the way I've enhanced the Saltcorn plugin API can deal with this.

Breadcrumbs are cool indeed!
Also even when not finalizing the edit, it kept the settings.


Price not shown when autosize or custom size

When I use autosize or custom size the half width of the price right bar is not visible.

Actually the same issue happens in normal view, without custom or autosize.

I'm afraid that's an issue with TradingView itself then. This component is only a very simple wrapper.

You're right, closing this. Thanks for the prompt reply!


beta5 problems

Describe the bug
running cargo update on my project
then cargo leptos watch
failed to compile with
error: queries overflow the depth limit!
i increased recursion limit with
#![recursion_limit = "256"]
then it is compiled but at run time when i hit code that uses
expect_context function it gives me error
thread 'tokio-runtime-worker' panicked at /home/eltahawy/.cargo/registry/src/index.crates.io-6f17d22bba15001f/reactive_graph-0.1.0-beta5/src/owner/context.rs:261:9:
Location { file: "src/app/review_model.rs", line: 11, col: 19 } expected context of type "nagah::app::BackendContext" to be present
Note
the code worked fine at previous version
i provide the context from the axum integration
    let context = BackendContext {/*code*/};

    let app = Router::new()
        .leptos_routes_with_context(
            &leptos_options,
            routes,
            move || provide_context(context.clone()),
            {
                let leptos_options = leptos_options.clone();
                move || shell(leptos_options.clone())
            },
        )
        .fallback(leptos_axum::file_and_error_handler(shell))
        .with_state(leptos_options);

Leptos Dependencies
axum = { version = "0.7", optional = true }
console_error_panic_hook = "0.1"
leptos = { version = "0.7.0-beta" }
leptos_axum = { version = "0.7.0-beta", optional = true }
leptos_meta = { version = "0.7.0-beta" }
leptos_router = { version = "0.7.0-beta" }
tokio = { version = "1", features = ["rt-multi-thread"], optional = true }
tower = { version = "0.4", optional = true }
tower-http = { version = "0.5", features = ["fs"], optional = true }
wasm-bindgen = "=0.2.93"
thiserror = "1"
tracing = { version = "0.1", optional = true }
sqlx = { version = "0.8", features = [ "runtime-tokio", "tls-rustls","postgres","uuid","chrono" ] ,optional = true}
http = "1"
chrono = { version = "0.4.38", features = ["serde"] }
serde = { version = "1.0.210", features = ["derive"] }
http-auth-basic = "0.3.5"

The recursion and overflow issues should have been fixed or improved by #3015. If not, please open a new issue with a reproduction.
Likewise, for the other issue, feel free to open a separate issue with a reproduction but as it stands there's not enough here to reproduce it.

@gbj I have a similar error in leptos v0.7.2 for an example which I can't really make a "minimal" reproduction for.
I've narrowed it down to where commenting out a single atomic node with no attributes and single-character static text content. Copying out a smaller section of this view! macro around the node in question to a smaller example does not reproduce the error. This view involves a lot of mathml if that is relevant.
Is there another workaround? I tried the suggested #![recursion_limit = "256"] (even #![recursion_limit = "4096"]) which does not seem to have an effect.

@lnay I would believe it. If I recall correctly the "inert HTML" optimizations that are in place to prevent this in the general case are disabled for both SVG and MathML. If your large amount of MathML is static, I would recommend inlining it as a string using inner_html (so, say
 rather than
<math><math><math><math>
, if you see what I mean)
If it is dynamic, there's more of a conversation to be had I suppose. Including breaking parts of it out into separate pieces of the view and using .into_any() to erase the types, as I assume the issue here is the breadth/depth of the view types if it's a large piece of complex markup.

Thanks for the suggestions, I will see how it goes. Parts of the markup is static, others dynamic, and the original also had embedded html <button>s (those sections where commented out in all the cases mentioned above).
That last one is possibly not standard compliant, but works in all tested browsers.


docs: Update CONTRIBUTING.md

Description
Updated the CONTRIBUTING.md with what we discussed today in the all-hands meeting.
Heavily inspired by https://github.com/firebase/flutterfire/blob/master/CONTRIBUTING.md#the-release-process :heart:
Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

We won't use a GitHub action for publishing?
(meaning you have to do all the work)

Someone should still need to review that the release is correct. This is the process they use on flutter fire. I wouldn't fully automate it just in case (yet, at least)

I did a small change on the PR template (removed the part about updating the changelog) will merge anyways. Thanks for checking!


Crash

Steps to reproduce
Fatal Python error: handle_doc did not receive a result
Python runtime state: initialized

Current thread 0x00007f245fdbba80 (most recent call first):
  File "<string>", line 135 in get_completions
  File "<string>", line 16 in vimpy3complete
  File "<string>", line 1 in <module>
Vim: Caught deadly signal ABRT

Error detected while processing function python3complete#Complete[35]..VimLeave Autocommands for "*"..function <SNR>90_NetrwBookHistSave:Vim: Finished.

line    9:
E565: Not allowed to change text or change window:   1split
Error detected while processing function python3complete#Complete[35]..VimLeave Autocommands for "*"..function <SNR>90_NetrwBookHistSave[12]..<SNR>90_NetrwEnew:
line   35:
E565: Not allowed to change text or change window: keepj keepalt enew!
Error detected while processing function python3complete#Complete[35]..VimLeave Autocommands for "*"..function <SNR>90_NetrwBookHistSave:
line   29:
E578: Not allowed to change text here
line   30:
E578: Not allowed to change text here
line   38:
E578: Not allowed to change text here
line   52:
E578: Not allowed to change text here
line   77:
E565: Not allowed to change text or change window
line   78:
E565: Not allowed to change text or change window: keepalt 4bwipe!

Expected behaviour
no crash
Operating system
Ubuntu
Version of Vim
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Sep 28 2021 11:18:09)
Logs and stack traces
No response

Steps to reproduce

Here you should have described what you did when the crash occurred :(
Looks like this is caused by the python3 complete plugin. Are you using different python3 than your vim was compiled with?
Can you please test with an uptodate Vim? (self-build and debugging symbols enabled, so we can get a backtrace, see https://github.com/vim/vim/wiki/Debugging-Vim-Bugs#creating-a-gdb-stack-trace)

@chrisbra Yes, sorry, but I wasn't sure what to include exactly.  I was editing a file.  This is consistently happening now.

Are you using different python3 than your vim was compiled with?

Yes, my virtual environment is on Python 3.10.

Can you please test with an uptodate Vim? (self-build and debugging symbols enabled, so we can get a backtrace,

Doing that now.  Thank you.

You want me to do steps 1, 2, 3?

I can't seem to reproduce with the master vim.

=================================================================
==492491==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 83707 byte(s) in 81 object(s) allocated from:
    #0 0x7f0b782aabc8 in malloc (/lib/x86_64-linux-gnu/libasan.so.5+0x10dbc8)
    #1 0x560e6b5ce034 in PyMem_RawMalloc Objects/obmalloc.c:572
    #2 0x560e6b5ce034 in _PyObject_Malloc Objects/obmalloc.c:1956
    #3 0x560e6b5ce034 in _PyObject_Malloc Objects/obmalloc.c:1949

Indirect leak of 4779 byte(s) in 5 object(s) allocated from:
    #0 0x7f0b782aabc8 in malloc (/lib/x86_64-linux-gnu/libasan.so.5+0x10dbc8)
    #1 0x560e6b5ce034 in PyMem_RawMalloc Objects/obmalloc.c:572
    #2 0x560e6b5ce034 in _PyObject_Malloc Objects/obmalloc.c:1956
    #3 0x560e6b5ce034 in _PyObject_Malloc Objects/obmalloc.c:1949

SUMMARY: AddressSanitizer: 88486 byte(s) leaked in 86 allocation(s).

Anyway, long story short seems to be that running vim in a virtual environment that has Python 3.10 activated seems to cause crashes in vim.  My solution for now is to run vim from outside the virtual environment.

@NeilGirdhar wrote:

==492491==ERROR: LeakSanitizer: detected memory leaks

It's only a leak. It does not explain a crash.
And it's probably not a real leak in the sense that some memory is not freed when exiting (at least if you don't build with -DEXITFREE)

VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Sep 28 2021 11:18:09)

This is not the full version (we don't see the included patches).
Ideally attach the output of vim --version.
If you can reproduce the crash with a asan (address sanitizer) build and with a recent vim from git, please attach the full output of asan.  I suggest you run vim with vim 2> asan.log to capture it.

@dpelle Here's the version as requested.  If I have time, I'll try to get you a full log.
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Sep 28 2021 11:18:09)
Included patches: 1-3458
Modified by<EMAIL_ADDRESS>Compiled by<EMAIL_ADDRESS>Huge version with GTK3 GUI.
Try building with python statically linked.

@brammool Yeah, I think I tried you're suggestion, and you're right that it works.
The issue is that I'm in a virtual environment with Python 3.10.  Is there some way to get to vim built with 3.8 to work?  Or is there a package I can point Ubuntu at that's built with 3.10?

Have you tried https://launchpad.net/~jonathonf/+archive/ubuntu/vim-daily

@chrisbra Sorry for the late reply.  Yes, I'm already using those builds, but thank you for the suggestion.

It looks like there is no way we can prevent this by changing Vim, therefore closing.

@brammool I don't understand.  Is it normal for Vim to crash because it's compiled with a different Python than the system Python?
Probably a suitable workaround would be to look for the Python it was compiled with using python3.8 from the path.

@brammool I don't understand.  Is it normal for Vim to crash because
it's compiled with a different Python than the system Python?
Probably a suitable workaround would be to look for the Python it was
compiled with using python3.8 from the path.

It would be best if Vim can check that the library loaded dynamically is
the right one.  If it would have an API version number we could make
sure that we load the right one.  I'm not aware of something like this
existing.  MS-Windows has always had this problem with library version
numbering, perhaps a solution was implemented somehow?
--
hundred-and-one symptoms of being an internet addict:
86. E-mail Deficiency Depression (EDD) forces you to e-mail yourself.
/// Bram Moolenaar -- @.*** -- http://www.Moolenaar.net   \
///                                                                      \
\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///


Hello, please could you describe how to upload FW with Arduino IDE in this case?

I really don´t know where to put those downloaded libraries. thank you very much.

https://community.home-assistant.io/t/sonoff-homeassistant-alternative-firmware-for-sonoff-switches-for-use-with-mqtt-ha/2332/57
Have a look at this discussion. It may help


fix: revert downgrade packages to avoid docker build issue

Reverts ExpediaGroup/comparadise#126

:tada: This PR is included in version 1.0.8 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Nice project

Hello @stijnvanhulle, it's a really nice project and I really like the way you structured it. What do you think about helping me on orval or merging our project somehow? I don't have a lot of time to maintain and improve it so would be great to combine forces. Let me know what you think about this.

@anymaniax Thank you very much 💯 . At this moment, I'm not yet sure about the future. It started as a tryout to make a plugin system around creating generated code. That changed a little bit, now it's a tool to generate React-Query hooks, Axios controller and Zod schemas out of a Swagger file.
For now, it's more like a hobby project so maybe later in the future, we can combine/integrate Orval.

What do you think about having a discussion on discord or something else one day? We can even see each other around a beer if you want since we are both from Belgium 😅


tutorial for dataloader

Motivation and Context
Why is this change required? What problem does it solve?:
If it fixes an open issue, please link to the issue here:
Description
Describe your changes in detail:
Screenshots (if appropriate):
Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

[x] Documentation update
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Is this PR ready for review, or a work in progress?

[x] Ready for review
[ ] Work in progress

How Has This Been Tested?
Put an x in the boxes that apply:

[x] Current tests cover modifications made
[ ] New tests have been added to the test suite
[ ] Modifications were made to existing tests to support these changes
[ ] Tests may be needed, but they are not included when the PR was proposed
[ ] I don't know. Help!

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have signed (or will sign when prompted) the tensorwork CLA.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

hey @hhsecond just a heads up this needs to be rebased after the changes in #113

Also the Travis OSX Py3.7 build should now work with the hotfix included in #113

Github is acting weird since the rebase and not letting me update the PR. Closing this and recreating another one


Porting the MathJax display from previous DSpace versions

Description of the feature request
Previous versions of DSpace contained the possibility of enabling the rendering of scientific formulas and symbols on different item pages.
This should also be ported to DSpace 7 for preservation of default functionality.
An example of how this is currently displayed in DSpace:
The 2 formulas that are present in the abstract are:

$\text{H}_2$/$\text{O}_2$
$\text{H}_2 + \text{O}_2(1\Delta) = \text{H} + \text{HO}_2$

When actually displaying the values, it's rendered as an actual formula, and not simply as the text that is present in the DB

Describe the solution you'd like
The current configuration possibility should be ported to the DSpace 7 codebase.
Most, if not all, of this work would be present in the angular side of things.
Rest should only be relevant for the enabling/disabling of the config.

This is part of a larger issue:  in earlier releases, textarea fields could be formatted.  In 7.3, line breaks entered in the item editor are removed, and entering even plain HTML markup causes it to be displayed as-is.
We have abstracts with multiple paragraphs and even tables.  Line breaks are quite common.  Markup is rare but we have some.
The 7.x documentation still has a page on "Simple HTML Fragment Markup" which is no longer true and probably does not represent well the eventual resolution of this issue.

Added a zero hour estimate as this will be include in fix for #1762


Test failures on mips64 with OpenBLAS 0.3.1

Hi,
The Debian package for OpenBLAS 0.3.1 fails some of the "u"-tests on mips64, see:
https://buildd.debian.org/status/fetch.php?pkg=openblas&arch=mips64el&ver=0.3.1%2Bds-1&stamp=1530702292&raw=0
Note that the tests were passing with 0.2.20, so this is a regression.
Best,
Sébastien

Note that the Debian mips64el port uses the N64 ABI with hardware floating point and the MIPS64R2 ISA.
The OpenBLAS package is currently built with TARGET=SICORTEX (note 100% sure whether this is the right target for the generic package though).

Thanks for the report. I suspect the 0.2.20 utests passing was mostly (or entirely) due to there being fewer of them - most were reactivated in 0.3.0. (Which makes this ticket basically a continuation of #1469, unfortunately the Fedora folks do not build-test mips and I have not acquired a mips64 system yet.) Hopefully my fixes for mips32 will apply, in which case there should be a PR for you to test later today...

DSDOT is the only one I managed to fix, the others I plan to replace with their mips C counterparts that are already used in the I6400, I6500 and P6600 targets.


Add and Fix Error Page in the APP

Figma Link

@ankit2001 can you please remove the plugins and have this be just a new page - also can you make the buttons look more like the design without the shadows?


use VOCABULARY instead of ruleNames in lexer test

Probably should use VOCABULARY instead of ruleNames in lexer test because it may not work in some cases (wrong name order). I tried it with another language grammar in my project and only VOCABULARY worked correctly.

Right, thanks for fixing this one!


Better blacklist check

This is a problem in volto core. https://github.com/plone/volto/blob/master/src/components/manage/UniversalLink/UniversalLink.jsx#L69-L72
But added a customization for it here as the ticket priority is Urgent
We have config.settings.externalRoutes defined in the project. A route external to main volto site will get past that blacklist check.
Left comments explaining the issue

@andreiggr To be fixed directly in Volto Core


feat(AppLayout): Allow set the height of header for custom header

Issue #, if available:
Closes #39
Description of changes:
Add a new prop for AppLayout so that users can set the height of header if a custom header is used.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Assertion ECMA_STRING_IS_REF_EQUALS_TO_ONE (string_p) in ecma_free_string_list

JerryScript revision
cefd391772529c8a9531d7b3c244d78d38be47c6
Build platform
Ubuntu 22.04.3
Build steps
python ./tools/build.py --builddir=xxx --debug --clean --compile-flag=-fsanitize=address --compile-flag=-g --strip=off --lto=off --logging=on --line-info=on --error-message=on --stack-limit=20

Test case
//poc1.js
class s { constructor ( ) { } [ { [idx1] : { [{ [idx1] : { [idx2] : {}}} = [5.7]] : {}}} = [5.7] ] = class { } }
new s ( ) ;

//poc2.js
const obj = { a : (o) = 1 };
var a = { a : (o) = 1 } = obj;

(class C2 { ["foo"] = 5; ["foo"] = {} + {} })((new (class o { ["foo"] = 5; [{ a : (o) = 1 } = obj] = {} + {} })).foo === 5);
print(o === 1);

Execution steps
./xxx/bin/jerry poc.js

Output
//poc1.js
Unhandled exception: ReferenceError: idx1 is not defined

ICE: Assertion 'ECMA_STRING_IS_REF_EQUALS_TO_ONE (string_p)' failed at /home/qbtly/Desktop/target/jerryscript/jerry-core/ecma/base/ecma-literal-storage.c(ecma_free_string_list):75.
Error: JERRY_FATAL_FAILED_ASSERTION

//poc2.js
Unhandled exception: ReferenceError: Variables declared by let/const must be initial

ICE: Assertion 'ECMA_STRING_IS_REF_EQUALS_TO_ONE (string_p)' failed at /home/qbtly/Desktop/target/jerryscript/jerry-core/ecma/base/ecma-literal-storage.c(ecma_free_string_list):75.
Error: JERRY_FATAL_FAILED_ASSERTION

does https://github.com/jerryscript-project/jerryscript/issues/4525 related to this?

So far, the preliminary conclusion in the comments section is that this is a memory leak? I think the last issue with a similar error is January 2021. Does the community have a corresponding plan to fix this problem? Or what are the current conclusions about this issue, such as the impact is relatively small?

@happy-boy-maker you a bot?

@akosthekiss I don't know what makes you think I'm a robot.

You have summarised the above mentioned, potentially related issue for no apparent reason.
Then ask for plans and conclusions, without giving context on why it is of importance to you.
All this without any history of involvement with the project.

So, please, shed light on context.

@akosthekiss Our project uses Jerry as the JS engine. The issue released on the official platform can help us check whether some problems are introduced by ourselves. Memory leakage is a serious problem. So, I'd like to know how jerry's official attitude to this issue is. The triggering conditions provided by developers seem to be triggered by incorrect JS cases. Whether this problem does not affect the normal use of Jerry can be avoided by verifying the code.

does #4525 related to this?

Sorry for the late response. Yes, probably #4525 is the minimized testcase for this fuzzer testcase.


"Evaluated the place holder for a PostTcType" error possible while collecting type info

Run on the store repo version https://github.com/fpco/store/commit/deaa1c3c2e28f6bbbb566b605cc87a3963478d3b,
with stack ghci --with-ghc intero --no-load --no-build --ghci-options "-odir=/tmp/intero15779w9j" --ghci-options "-hidir=/tmp/intero15779w9j" --stack-yaml stack-7.8.yaml --test
Prelude> :load test/Spec.hs
[ 1 of 14] Compiling System.IO.ByteBuffer ( /home/mgsloan/fpco/store/src/System/IO/ByteBuffer.hs, interpreted )
[ 2 of 14] Compiling System.IO.ByteBufferSpec ( /home/mgsloan/fpco/store/test/System/IO/ByteBufferSpec.hs, interpreted )
[ 3 of 14] Compiling Data.Store.Impl  ( /home/mgsloan/fpco/store/src/Data/Store/Impl.hs, interpreted )
[ 4 of 14] Compiling Data.StoreSpec.TH ( /home/mgsloan/fpco/store/test/Data/StoreSpec/TH.hs, interpreted )
[ 5 of 14] Compiling Data.Store.TH.Internal ( /home/mgsloan/fpco/store/src/Data/Store/TH/Internal.hs, interpreted )
[ 6 of 14] Compiling Data.Store.TH    ( /home/mgsloan/fpco/store/src/Data/Store/TH.hs, interpreted )
[ 7 of 14] Compiling Data.Store.Internal ( /home/mgsloan/fpco/store/src/Data/Store/Internal.hs, interpreted )
ma[ 8 of 14] Compiling Data.Store       ( /home/mgsloan/fpco/store/src/Data/Store.hs, interpreted )
[ 9 of 14] Compiling Data.Store.TypeHash.Internal ( /home/mgsloan/fpco/store/src/Data/Store/TypeHash/Internal.hs, interpreted )
[10 of 14] Compiling Data.Store.TypeHash ( /home/mgsloan/fpco/store/src/Data/Store/TypeHash.hs, interpreted )
[11 of 14] Compiling Data.Store.Streaming ( /home/mgsloan/fpco/store/src/Data/Store/Streaming.hs, interpreted )
i[12 of 14] Compiling Data.Store.StreamingSpec ( /home/mgsloan/fpco/store/test/Data/Store/StreamingSpec.hs, interpreted )
[13 of 14] Compiling Data.StoreSpec   ( /home/mgsloan/fpco/store/test/Data/StoreSpec.hs, interpreted )
n
[14 of 14] Compiling Main             ( test/Spec.hs, interpreted )
Ok, modules loaded: Data.StoreSpec, Data.Store, Data.Store.Internal, Data.Store.TH, Data.Store.TH.Internal, Data.Store.TypeHash, Data.StoreSpec.TH, Data.Store.TypeHash.Internal, Data.Store.Impl, Main, Data.Store.StreamingSpec, System.IO.ByteBufferSpec, System.IO.ByteBuffer, Data.Store.Streaming.
Collecting type info for 14 module(s) ...
Error while getting type info from Data.Store.Internal: intero: panic! (the 'impossible' happened)
  (GHC version 7.8.4 for x86_64-unknown-linux):
    Evaluated the place holder for a PostTcKind

Please report this as a GHC bug:  http://www.haskell.org/ghc/reportabug

Error while getting type info from Data.Store.TH: intero: panic! (the 'impossible' happened)
  (GHC version 7.8.4 for x86_64-unknown-linux):
    Evaluated the place holder for a PostTcType

Please report this as a GHC bug:  http://www.haskell.org/ghc/reportabug

Error while getting type info from Data.Store.TH.Internal: intero: panic! (the 'impossible' happened)
  (GHC version 7.8.4 for x86_64-unknown-linux):
    Evaluated the place holder for a PostTcKind

Please report this as a GHC bug:  http://www.haskell.org/ghc/reportabug

Error while getting type info from Data.Store.TypeHash.Internal: intero: panic! (the 'impossible' happened)
  (GHC version 7.8.4 for x86_64-unknown-linux):
    Evaluated the place holder for a PostTcKind

Please report this as a GHC bug:  http://www.haskell.org/ghc/reportabug

I've seen this on  number of projects in the past, possibly only those involving TH, but I'm not sure. The message comes from Intero which catches the exception for specific modules rather than failing hard and getting no info for all modules. However, it should only be appearing on GHC 7.8.4 as the land-mines in the AST were fixed to avoid this kind of buggerance in 7.10 IIRC.

Ahh, that makes sense!  Yes, this is with 7.8

Closing as GHC 7.8 is a couple versions back.


feat: Onboard New York Trees dataset

Description
Pipelines included:

new_york_trees.tree_census_2005
new_york_trees.tree_census_2015

Note: It's recommended to open an issue first for context and discussion.
Checklist
Note: Delete items below that aren't applicable to your pull request.

[x] Please merge this PR for me once it is approved.
[x] If this PR adds or edits a dataset or pipeline, it was reviewed and approved by the Google Cloud Public Datasets team beforehand.
[x] If this PR adds or edits a dataset or pipeline, I put all my code inside  datasets/new_york_trees and nothing outside of that directory.
[x] This PR is appropriately labeled.

@adlersantos - I have reviewed - please move to prod.  Thanks!


Add comments describing methods/functions

Problem
When new features are delivered it is sometimes not intuitive how the new function/method is supposed to work. Comments describing the function/method would make it easier to understand the behavior.
Solution
Add comments to describe the functions/methods in the source code.
Alternatives
No response

@SimiHunjan might this issue date be flexible? Perhaps, a good use case for a tech debt label? For example, this issue should be kept in mind when devs are working within the files; rather, something to chip away at than spend time going through every file 😬
Thoughts?

For context, if the method relates to set/get in the protobuf – that should be copied from the protobuf documentation.


Improve step one of the notebook

Fixed

Explaining texts
File downloads
Added additional cells when needed.

Test it for bugs and make sure that the explaining text is correct

When we make the release, we will need to remove the sys.path.append("..") line and the autoreloads. We will also need to update the paths as output_directory = '../example/results' I spect the behaviour to be that the user will be able to just download the example notebook, install onstove with conda and run the notebook directly being in the same directory. So the ../example won't be really required.

I want to "hide" the data download steps into a function that gets called with the country as input only. We can put this function on a utils.py file in the example and import it. I think this will make the notebook cleaner and will avoid confusion among the participants about those download steps.

Thing done:

Reviewed and comlemented text
Fixed one link to documentation that was wrong
Added links to the sections in the description of the notebook
Added links at the end of each section to be able to go back to the top of the notebook
Rearrange order of the mask_all and aling_all methods
Moved the description of each dataset to the section where it is read rather than at the begining of the data processing section
Moved the DataProcessor creation to the data processing step, and left the definition of the output_directory to the begining of the notebook


Cydia Crashing but tweaks working

My yalu102 app is working but cydia continues to crash

https://github.com/kpwn/yalu102/issues/64

yes its a 64 bit

its an iphone 6S

#64: "Stop asking for support here"

why
this is a server problem

@EdoEdii because if the tweaks are working then jailbreak was successful.
If cydia is crashing that's a problem Saurik or yourself should fix.
How about you close this issue and contact me via email at<EMAIL_ADDRESS>can help you there

ok

done


Translation - Words_de.yml

The translation for Rabbit dont work for me, i change the word in the Words_de.yml but only this word dont work.
'101':
MCName: Rabbit
Name: Hase

Try update to the latest version.


arrow_path function doesn't load query params if no path params are passed

https://github.com/jmnuf/crimson-ranger-norishre/blob/6586d6f95638bd81d7c8f37bc013db76d50d048b/src/dark-elves.ts#L181
The check for query params is inside the path params if block so if path is not defined the query params are never checked it they exist.

Fixed within commit: https://github.com/jmnuf/crimson-ranger-norishre/commit/fb70d60357db57b907a61b9826158ccdb15f9d91


Elastic transformations

Support of elastic transforms for keypoints, masks and images is needed

This looks usable https://www.kaggle.com/bguberfain/elastic-transform-for-data-augmentation

yes and no. The does not extend easily to the keypoints. Some work needs to be done...

I am reopening this issue for release 0.3, as release 0.2 has already quite many important fixes and new features.


Update app-service-web-create-app-service-plan-no-h.md

Updated the Sku in this example as 'FREE' doesn't appear to be valid, but 'F1' is

@thepaulmacca : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@thepaulmacca I don't reproduce your issue. The command works as is. #please-close


add some new badges to the readme

This commit adds the following badges

the project License
go report card score
number of Projects go-gitlab is used by (sourced fom sourcegraph)
number of open Github issues

It also rearranges them slightly.

LGTM! Thanks @gjnoonan


Building new WSL2 Linux Kernel 6.6 disables /dev/dri (and VA-API)

Windows Version
Microsoft Windows [Version 10.0.20348.2582] (Windows Server 2022)
WSL Version
<IP_ADDRESS>
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>-microsoft-standard-WSL2
Distro Version
Ubuntu 24.04
Other Software
No response
Repro Steps

Build the new WSL2 Linux <IP_ADDRESS> kernel release
Spin up a Ubuntu 24.04 (or even Ubuntu 22.04) WSL2 instance
Observe that /dev/dri is not there

Expected Behavior
/dev/dri should be present just like before using the older kernel
Actual Behavior
/dev/dri is missing and this makes VA-API impossible.
Workaround
I think the issue seems to be around the way the kernel config  is set up.  After much debugging, I found that /dev/dri is mapped using VGEM as described in this commit.  I then noticed that in the config for the kernel, CONFIG_DRM_VGEM=m instead of CONFIG_DRM_VGEM=y like in the older WSL2 kernels.  After changing the m to y for CONFIG_DRM_VGEM and rebuilding the WSL2 kernel, /dev/dri seems to show up again.
This should probably be fixed directly in the config.
Diagnostic Logs
No response

/feature
I'm tagging this as a feature request since I have provided the solution in the workaround.  No logs are really needed as this one involves building the kernel and following the steps to reproduce the issue.

From https://github.com/microsoft/WSL2-Linux-Kernel/releases
We are very excited kernel module support is now available in WSL2! With this latest kernel update, a large set of loadable modules has been introduced, accompanied by an overall config file update. However, please be aware that when using a custom kernel, the default module support is disabled for now. If you’re using a custom kernel, we recommend you edit your kernel config file to build-in all of the modules that you need.

Thanks @zcobol, I did read that as part of the release notes, but since this is to be the new LTS kernel and the default one at some point soon when you update WSL, I'd imagine that feature (CONFIG_DRM_VGEM) should be enabled by default.  Perhaps it is planned to be done, but I just wanted to open an issue regarding that in case it was not.

The kernel module is included, can you simply load the module (sudo modprobe vgem)?

@benhillis, I haven't tried loading it explicitly, but I raised this issue hoping that in the WSL2 kernel code, perhaps it's a good idea to have it enabled by default so that manual commands don't need to be run each time WSL2 is started to load the VGEM module.  It should in theory work out-of-the-box as it does in the older 5.15 kernel.

Just updated WSL to 2.3.13 and also noticed that /dev/dri was missing. This is required for Emby Media Server to run. Using the sudo modprobe vgem worked, but if this is something that has to be done every time the server restarts, then it really should be enabled by default.


增加关键字 "破局"

补齐 break continue 关键字
并且增加关键字 "破局" 代表 "break"

how about "小步快跑" quq
referenced from: https://github.com/justjavac/ali-words


导入证书之后，双击appxbundle根本无法安装啊

Microsoft store里的根本无法下载
这个appxbundle根本无法安装
提示
““”
This app package’s publisher certificate could not be verified. Contact your system administrator or the app developer to obtain a new app package with verified certificates. The root certificate and all immediate certificates of the signature in the app package must be verified (0x800B010A)
“””

看了一下， 你们提供的证书都是过期的，。，


chore: rearrange bins & set default

This PR shuffles around some of our src/bin
folder to match the layout from
https://doc.rust-lang.org/cargo/guide/project-layout.html.
It also sets a default-run to
mayastor-client as most users will want that as
a default I suspect.
There should not be any behavior changes other than
possibly some logs having
a new filename.

@bors r+

@bors r+

bors merge

bors merge

I think that's an unrelated failure?
@bors retry

I think that's an unrelated failure?
@bors retry

@bors merge

@bors merge

bors merge

bors merge

bors merge

bors merge