v1.0.0 release candidate

This Draft pull request is for tracking and documenting the first non-beta release.
Transitioning out of beta will involve an interface freeze and stability guarantee based on the integrated component tests.
Future enhancements and features will be added by pull-request and increment the minor version number. Future bug fixes will commit to master and increment the patch number.
(!) Backwards-incompatible interface changes
These changes are not compatible with pre-release beta versions of the library.

[x] Update buffer initialisation interface to be generic subroutine

New features and enhancements
These changes do not affect existing interfaces from the pre-release version.

[x] Add fclCommandQPool object for handling multiple command queues
[x] Automatically make sure global dims are multiples of local dims at kernel launch
[x] Get ifort build working
[x] Add interfaces for creating sub-buffers
[x] Add fclInit() quick context setup function
[x] Allow device filtering based on supported features
[ ] Add support for OpenCL user events
[ ] Add deallocation routines for fcl objects

Integrated component tests

[x] Test queue pool objects
[x] Test events
[x] Test profiling

General software engineering tasks

[x] Populate all OpenCL 1.2 error codes
[x] Add copyright and license headers to library source files
[x] Add continuous integration to run tests
[ ] Update README with more info (dependencies, quick build&run, third-party sources etc.)
[ ] Update inline documentation (FORD)
[ ] Update main documentation site for new features and interfaces
[ ] Create quick reference card (cheatsheet)
[ ] Add CONTRIBUTING guidelines and CHANGES document to repository

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@8c2af70). Click here to learn what that means.
The diff coverage is 71.4%.

@@            Coverage Diff            @@
##             master       #6   +/-   ##
=========================================
  Coverage          ?   43.77%
=========================================
  Files             ?       23
  Lines             ?     3317
  Branches          ?        0
=========================================
  Hits              ?     1452
  Misses            ?     1865
  Partials          ?        0

Impacted Files
Coverage Δ

src/Focal_Utils.f90
52.77% <ø> (ø)

src/Focal.f90
0% <ø> (ø)

src/Focal_Error.f90
8% <0%> (ø)

src/Focal_NoDebug.f90
0% <0%> (ø)

test/testPinnedMemory.f90
98% <100%> (ø)

test/testQueuePool.f90
100% <100%> (ø)

test/testKernelSetup.f90
100% <100%> (ø)

test/testLocalMem.f90
100% <100%> (ø)

test/testProfiling.f90
100% <100%> (ø)

test/testMemoryTransfer.f90
98.18% <100%> (ø)

... and 11 more

Continue to review full report at Codecov.

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

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@8c2af70). Click here to learn what that means.
The diff coverage is 77.02%.

@@            Coverage Diff            @@
##             master       #6   +/-   ##
=========================================
  Coverage          ?   72.82%
=========================================
  Files             ?       10
  Lines             ?     1402
  Branches          ?        0
=========================================
  Hits              ?     1021
  Misses            ?      381
  Partials          ?        0

Impacted Files
Coverage Δ

src/Focal_Utils.f90
52.77% <ø> (ø)

src/Focal_Error.f90
8% <0%> (ø)

src/Focal_NoDebug.f90
0% <0%> (ø)

src/Focal_HostMemory.f90
96.96% <100%> (ø)

src/Focal_Query.f90
87.25% <100%> (ø)

test/Focal_Test_Utils.f90
67.56% <100%> (ø)

src/Focal_Debug.f90
44.03% <38.09%> (ø)

src/Focal_Setup.f90
79.07% <85.84%> (ø)

src/Focal_Memory.f90
82.87% <87.87%> (ø)

src/Focal_Profile.f90
85.27% <88.23%> (ø)

Continue to review full report at Codecov.

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

All changes are now implemented, documented and tested.
Some new features still in need of documentation.
Outstanding items not prerequisite for release, so now ready to merge.


How to enable LSR as described in Attentional Encoder Network for Targeted Sentiment Classification?

In the paper Attentional Encoder Network for Targeted Sentiment Classification, you show that AEN with LSR yields a significant improvement over AEN without LSR. However, when looking in the code, the respective class https://github.com/songyouwei/ABSA-PyTorch/blob/bf55517ed5cb8dda5960b15575e87dd06101586d/models/aen.py#L16 is actually never being used. How to use it? Why did you disable it?

LSR is not used by default because other implemented models do not use this trick.
https://github.com/songyouwei/ABSA-PyTorch/blob/bf55517ed5cb8dda5960b15575e87dd06101586d/train.py#L23
You can enable it by replacing nn.CrossEntropyLoss() with CrossEntropyLoss_LSR()
https://github.com/songyouwei/ABSA-PyTorch/blob/bf55517ed5cb8dda5960b15575e87dd06101586d/train.py#L160

Alright, that's awesome. Thank you very much =)

Do you happen to know how to weight the loss of different classes differently? E.g., our dataset is pretty imbalanced and we'd like to weight classes accordingly. In the regular CrossEntropyLoss provided by pytorch, there is a weight parameter that allows to do that. My current implementation changes your _toOneHot_smooth as follows:
    def _toOneHot_smooth(self, label, batchsize, classes):
        base_prob = self.para_LSR * 1.0 / classes
        one_hot_label = torch.zeros(batchsize, classes) + base_prob

        if self.weight is not None:
            one_hot_label = one_hot_label * self.weight

        for i in range(batchsize):
            index = label[i]
            one_hot_label[i, index] += (1.0 - self.para_LSR)

        return one_hot_label

whereby self.weight is a tensor consisting of C numbers (where C is the number of classes). Does this seem correct to you? I'd very much appreciate your feedback!


update Rac3-Truck Readme

Dear @laurensvalk and @dlech,
Here are my changes for Rac3 Truck.
Thank you very much!
Antoni

Dear @laurensvalk and @dlech,
I updated my Rac3-Truck README further and checked with my dad @TheVinhLuong102.
It is now ready for your review!
I found my video of with the Pybricks code.
Thank you very much!
Antoni

Hi @laurensvalk and @dlech,
@AntoniLuongPham and I have followed the BOOST Auto Builder README and updated those for Rac3 Truck, RoboDoz3r and Wack3m to a similar format.
Re: the videos, we have @AntoniLuongPham's YouTube videos for Rac3 Truck and RoboDoz3r that show PyBricks code (instead of EV3Dev2). The presentational eloquence is, understandably, borderline passable but not great :) Please do consider if these are good enough for your website. If they are not, we can use the LEGO RobotMak3r Studio videos instead for now, and try to re-film and re-submit Antoni's presentations later the next time he and his sister build these models.
Thank you.
Vinh

Thank you all for all the hard work!
It may take us a while to process everything and settle on a good format for images, video, and descriptions. I apologize for changing things around a lot :)
For now I've merged all submissions as-is, so we can all get a proper preview of how it looks on the website. With this in place, you may find it easier to go through existing content pages, and make changes and fixes as needed. Hope this helps. Please stay tuned :)

@laurensvalk,
Thank you so much!
We love the changes you've been making to publish the projects to the website, and totally understand that everyone is discovering new technical requirements while doing this.
I realized the significance of these changes so instructed @AntoniLuongPham and @ArianaLuongPham to pause on writing new programs and focus instead on refactoring the existing ones. It's been a great experience for them -- learning that documenting and presenting is just as much hard work as building the robots and coding the programs. :)
Vinh

@dlech and @laurensvalk, the PyBricks website looks absolutely fabulous -- the embedded images & videos are very engaging to young robot makers!
Now that we see the content rendered on the site, we'll refine the code & docs further. :)
Btw @dlech I see that you're limiting the code block width to 70 chars. Is this parameter pretty much fixed going forward? If yes, we'll refactor the code to limit the line length from 79 to 70 -- so that the viewers will need no horizontal scrolling.
Vinh

Yes, if you can run flake8 on the code and fix any errors/warnings, that will help us keep a somewhat consistent code style among projects.

@dlech we'll happily do! @ArianaLuongPham shall champion this and perform some good deeds. ;)

@dlech another thing we should think about is how to display the code for robots with multiple variants / games. For example, EV3 Tracker and the Inventor Core robots have 5-10 different tasks, each of which is interesting on its own. However, displaying all the programs at the same time on the same page is overwhelming to the viewer.
Maybe we should consider a collapse/expand mechanism?

For those, we might want to just show the first task as an example and just mention that there are more if you download the entire project.
Another thing while you are cleaning things up is that we should be using # comments instead of """. MicroPython has a limitation that doc comment strings actually allocate memory even though they are not used for anything.

For EV3 (and only EV3), we will need to make a button to download the entire project folder anyway, so if you just want to show snippets of interesting code instead of the entire file on those pages, that is fine too.

Another thing while you are cleaning things up is that we should be using # comments instead of """. MicroPython has a limitation that doc comment strings actually allocate memory even though they are not used for anything.

Although since we don't run .py files on the device other that EV3 which has plenty of memory, it probably isn't really a problem.

@dlech no problem, since @AntoniLuongPham and @ArianaLuongPham will be scrubbing the programs & docs another round to optimize the look & feel on the website, we'll take all of the ^ suggestions into account for each refactoring exercise. :)

@dlech, @laurensvalk, for the community/fan creations, shall we explicitly credit the robot designers (e.g. @laurensvalk, Martyn Boogaarts, etc.) on the website too?
Right now it appears as if the Pybricks code project submitter is also the creator of the design.
Vinh


Fixed user being unable to delete root Node if is an inherited Scene

User wasn't able to delete the root Node because it was being treated as
a foreign Node since it was an inherited Scene
Fixes #23007

Thanks!


Updated components names.

According to https://bugzilla.mozilla.org/show_bug.cgi?id=1594717.

Coverage remained the same at 25.455% when pulling 342b29654d4744b684e5710ad09dc34475b120aa on jensstutte:dom_workers_storage_names into 2d41e48218234efedfbe3ef460bdb6be9c3c1361 on mozilla:master.

Thanks


Installing WSL2 on Dell Inspiron 7415 bricks machine

Windows Version
Windows 11 Pro
WSL Version
2
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version
No response
Distro Version
Ubuntu 22.04
Other Software
No response
Repro Steps

Install WSL2.
Attempt to install Ubuntu 22.04
Reboot machine
Screen is pixelated until you get into recovery mode
Reset Windows
Retry from 1.

Installing the kernel extension may be necessary to repro.
Expected Behavior
Not that. I think it's corrupting the graphics driver, but it turns the screen to snow.
Actual Behavior
See above, turns screen to illegible snow. The problem started within the last week. I thought I'd physically damaged the laptop based off the corruption of the graphics driver, but I'm filing the bug from the same machine and as long as I don't install WSL on it it works fine.
I think specifically it has to do with the on board Radeon graphics card
Diagnostic Logs
I cannot interact with the wsl executable without running the risk of bricking the machine back into recovery mode. Even wsl --update seems to break it now.

@aylusltd, please fill out the version fields in the bug from wsl --version in the bug filed above.

@pmartincic the issue only happens after installing the kernel extension and running wsl --update but then it looks like that. There is no issue with the version I can see after I reinstall the operating system.

This is what I see now for reference:

I reinstalled through the app store to see if this bricks again. Details:
PS C:\Users\ceoja> wsl --version
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>-1
WSLg version: 1.0.59
MSRDC version: 1.2.4677
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.2428

Dead again

Have to do this every time:

Any updates on this? Happy to try a reinstall if there's been a new release.


Add School of Scholars domain

@bhandarypujandev I am closing the request as a duplicate to #17514.


Better field path creation

Field paths now respect using integers and bracket notation for array indices, and likewise, treat dot notation as a property location, even when parseable to an integer.

Fixes #169

Looks good

I for-see a few issues getting logged because someone is bound to be using friends.0.firstName lol


Feature/fetch all contacts

Adds support for the get all contacts operation, including pagination marker & custom property selection.
Also adds generalized support for array params in url generation code.

Closed due to inactivity


Wrong link to Azure SDK client libraries

wrong link to Azure SDK client libraries

Learn Build status updates of commit 0ee5447:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/cognitive-services/what-are-cognitive-services.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@PatrickFarley
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


To Do until next version

add support for solar radiation data
add support for pressure data
add support for temperature data
enable flexible timeframes (less or more than one year)
implement extension of spatial boundaries to next available data point
enable import of manually downloaded raw data for processing
add calculation of windspeed af user-given heigth

No longer relevant, closing


fix: pom.xml to reduce vulnerabilities

The following vulnerabilities are fixed with an upgrade:

https://snyk.io/vuln/SNYK-JAVA-COMGOOGLECODEGSON-1730327
https://snyk.io/vuln/SNYK-JAVA-COMGOOGLEGUAVA-1015415
https://snyk.io/vuln/SNYK-JAVA-COMGOOGLEGUAVA-32236
https://snyk.io/vuln/SNYK-JAVA-COMGOOGLEPROTOBUF-173761
https://snyk.io/vuln/SNYK-JAVA-COMJCRAFT-30302
https://snyk.io/vuln/SNYK-JAVA-COMMONSCODEC-561518
https://snyk.io/vuln/SNYK-JAVA-COMMONSIO-1277109
https://snyk.io/vuln/SNYK-JAVA-IONETTY-30430
https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEHTTPCOMPONENTS-1048058
https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEHTTPCOMPONENTS-31517
https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEPDFBOX-30025
https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEPDFBOX-30693
https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEPDFBOX-30694
https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEPDFBOX-32417
https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEPDFBOX-72426
https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEPOI-30026
https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEPOI-30027
https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEPOI-30698
https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEPOI-30699
https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEPOI-30701
https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEPOI-31387
https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEPOI-31438
https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEPOI-32049
https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEPOI-466324
https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEPOI-548686
https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEXMLBEANS-1060048
https://snyk.io/vuln/SNYK-JAVA-ORGBOUNCYCASTLE-1035561
https://snyk.io/vuln/SNYK-JAVA-ORGBOUNCYCASTLE-1296075
https://snyk.io/vuln/SNYK-JAVA-ORGBOUNCYCASTLE-173771
https://snyk.io/vuln/SNYK-JAVA-ORGBOUNCYCASTLE-2841508
https://snyk.io/vuln/SNYK-JAVA-ORGBOUNCYCASTLE-31048
https://snyk.io/vuln/SNYK-JAVA-ORGBOUNCYCASTLE-32340
https://snyk.io/vuln/SNYK-JAVA-ORGBOUNCYCASTLE-32361
https://snyk.io/vuln/SNYK-JAVA-ORGBOUNCYCASTLE-32363
https://snyk.io/vuln/SNYK-JAVA-ORGBOUNCYCASTLE-32364
https://snyk.io/vuln/SNYK-JAVA-ORGBOUNCYCASTLE-32365
https://snyk.io/vuln/SNYK-JAVA-ORGBOUNCYCASTLE-32366
https://snyk.io/vuln/SNYK-JAVA-ORGBOUNCYCASTLE-32367
https://snyk.io/vuln/SNYK-JAVA-ORGBOUNCYCASTLE-32368
https://snyk.io/vuln/SNYK-JAVA-ORGECLIPSEJETTY-1090340
https://snyk.io/vuln/SNYK-JAVA-ORGECLIPSEJETTY-32151
https://snyk.io/vuln/SNYK-JAVA-ORGYAML-3113851
https://snyk.io/vuln/SNYK-JAVA-XALAN-31385
https://snyk.io/vuln/SNYK-JAVA-XERCES-2359991
https://snyk.io/vuln/SNYK-JAVA-XERCES-30183
https://snyk.io/vuln/SNYK-JAVA-XERCES-31585
https://snyk.io/vuln/SNYK-JAVA-XERCES-608891

Abanoned


DOC: <Issue related to /v0.2/docs/integrations/text_embedding/baidu_qianfan_endpoint/>

URL
https://python.langchain.com/v0.2/docs/integrations/text_embedding/baidu_qianfan_endpoint/
Checklist

[X] I added a very descriptive title to this issue.
[X] I included a link to the documentation page I am referring to (if applicable).

Issue with current documentation:
无法调用接口

Idea or request for content:
直接使用千帆的api可以成功，但是用langchain的接口会报错

请更新您的LangChain版本。


we'll then make a PR for TreeMesh to see if removing interfaces from cache_parabolic simplifies the implementation.

Opened unintentionally


fix(SSG): Correct extension of the file output

fixed https://github.com/honojs/hono/issues/2028
Author should do the followings, if applicable

[x] Add tests
[x] Run tests
[x] yarn denoify to generate files for Deno

@watany-dev
Great! Merge now.


Missing expected output file /test/outdir/discover/denovo_sequences.fa

I fear I may be missing something.
This is the set of commands that I used:
# downloading some TB reads (works fine)
wget ftp://ftp.sra.ebi.ac.uk/vol1/fastq/SRR230/005/SRR23086705/SRR23086705_1.fastq.gz

# getting the index (works fine)
drprg index --download mtb

# running predict (fails)
drprg predict -x mtb -i SRR23086705_1.fastq.gz --illumina -o outdir/

This is the error from drprg predict
11.12 [2023-11-14T23:44:10Z INFO ] Outdir doesn't exist...creating...
11.12 [2023-11-14T23:44:10Z INFO ] Discovering variants...
36.82 Error: Failed to update discover PRG
36.82
36.82 Caused by:
36.82     Missing expected output file /test/outdir/discover/denovo_sequences.fa

Is there something I can do to get drprg predict to run to completion? I fear I have missed something in the documentation somewhere.

Hi @erinyoung
I can't seem to reproduce this issue.
I ran your exact commands and the run completed successfully.
Which version are you using and how did you install drprg?

I installed Dr. PRG from source (or so I thought). I installed rasusa, seqfu, pandore, mafft, bcftools, and make_prg from source as well. Do you have an idea as to which dependency wasn't installed correctly? (All of their help messages work.)

My apologies, I need to amend my comment.
I downloaded the binaries for pandora, make_prg, drprg, seqfu, and rasusa. I built bcftools from source and downloaded the deb file for mafft and installed it that way.

It will be Pandora giving the error and it will depend on which version of Pandora you used. drprg relies on a very specific version. There's a just recipe that will download the right one if you run just pandora, or you can see the URL here https://github.com/mbhall88/drprg/blob/ef65d4a46e2a31cc268d4e5a106fbce72fb95e0e/justfile#L17
FYI when i tried to recreate your issue I used the conda recipe for drprg. You could also try the container if that's an option for you.

My apologies! I realized I never told you that I resolved my issues by reinstalling pandora!


[BUG] tspcontrol restart: analyze plugin not restarted, but tsp is

Bug description:
When tspcontrol is used to restart the analyze plugin with the below command, it seems that the tsp is restarted and not the analyze plygin
How to reproduce:
run the following command:
tsp -v --control-port 3001 -I ip <IP_ADDRESS>:5500 -l <IP_ADDRESS> -P analyze -i 2 -c --json-line  -O drop
get the plugin id
tspcontrol -t localhost:3001 list
 0: -I ip
 1: -P analyze
 2: -O drop

from the tsp output i get
* tsp: user interrupt, terminating...
* ip: leaving multicast group <IP_ADDRESS> from local address <IP_ADDRESS>

Expected behavior:
something similar when the "tables" plugin is restarted. on tsp output you can see that the plugin is restarted.
control commands: received from <IP_ADDRESS>:64334: restart -s 1
* tables: restarting due to remote tspcontrol

Environment:

OS: Windows
OS version: 10
TSDuck full version: 3.36-3360
Installation type: official binary

Hi @enricovittorini
I do not see the same thing. With the same command, I get this:
* analyze: { "pids": ... }
* control commands: received from <IP_ADDRESS>:37867: list
* analyze: { "pids": ... }

And this:
* analyze: { "pids": ... }
* control commands: received from <IP_ADDRESS>:46307: restart -s 1
* analyze: restarting due to remote tspcontrol
* analyze: { "pids": ...


Incompatible with creolib/Great big world

Mod Name
creolib/Great big world
Mod Homepage
https://www.curseforge.com/minecraft/mc-mods/great-big-world
Describe the bug
crash on startup
Steps to reproduce
1.Add mod great big world which ships with CreoLib
2.add connector and ffapi connector extras (newest version until I report this issue
3.crash
...
Logs
[main/ERROR] [dev.su5ed.sinytra.connector.service.FabricMixinBootstrap/]: Non-unique Mixin config name mixinextras.init.mixins.json used by the mods com_github_llamalad7_mixinextras and mixinextras
Additional context
No response

Please include your full log from a paste site, not just the parts you think are relevant, as they might not be important at all. The line you listed is a non-fatal error and doesn't crash the game

OK
latest.log

OK, here is full log: https://pastebin.com/2aCPwRS8


fix: move integration port to unregistered range

:bug: default integraiton port conflict with Mac OS Monteray's new AirPlay listener
Moves the integration testing port into the unregistered range (above
49151) to minimize potential future conflicts.
/kind bug
Fixes #700

/lgtm


How can I change the fonts?

Hi,
Is it possible to customize the fonts? I tried with customized CSS param but I couldn't get any result?
Thanks

Hi @hadisinaee, please see the documentation on using custom CSS files. Basically, you need to create your own CSS file, put that in the /static folder of your site and add the filename to the parameter.


Doesn't work with 0.8

I believe L.TileLayer.Canvas has been removed, similar issue to https://github.com/aparshin/leaflet-boundary-canvas/issues/5?

Hmm. That's bad. Unfortunately, I don't have the time to fix it but would gladly review/accept pull requests.

I'd also need support for maskcanvas in 0.8. I'm neither a Leaflet, nor a Javascript guru, but I could give it a try if no one else finds time.

I won't have time to implement it but can review and merge.

Cannot assign this ticket to me - however I'll work on it.

@shaula I just added you as collaborator.

To keep you up-to-date: I got a version working with leaflet 0.8-dev from January. Unfortunately they changed the implementation of the GridLayer afterwards, which caused troubles again. Will soon continue to find out why it does not work.

I added L.GridLayer.MaskCanvas. It works with the current master of leaflet (version 1.0-dev).


[Feature Request]: Login and Signup Module using MongoDB

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
I'd like to request the addition of a Login and Signup module that utilizes MongoDB for user authentication and management. This feature would include:
User Registration: Collect and store user data such as username, email, and password (hashed for security) in MongoDB.
User Login: Authenticate users by validating credentials against stored data.
Session Management: Use JWT (JSON Web Tokens) to maintain user sessions securely.
Password Encryption: Implement bcrypt or another secure hashing algorithm to protect passwords.
Use Case
This feature will enable the project to manage user authentication securely and efficiently. Users will be able to:
Register new accounts.
Log in using their credentials.
Stay logged in with session management, improving overall user experience.
Benefits
Improved Security: Storing user data in a structured and secure way using MongoDB, with password hashing, will protect sensitive information.
Scalability: MongoDB's flexible schema allows easy updates and future enhancements to user profiles.
User Experience: A streamlined login/signup flow with session management enhances the usability of the platform, making it more user-friendly.
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

I would like to add login and signup for authentication i would like to contribute

hi @Anjalis14 any updates ?

Hey @manikumarreddyu if nobody is working on this issue I can work on this.

Hi @harish08102004 you go ahead...

can you please let me know how much time do you need to complete this issue @harish08102004

By today this will be done.

@manikumarreddyu will it be possible to assign me this issue if nobody had responded so far. I could also continue my work with community forum based on this.

Hey @J-B-Mugundh I'm already on it.

Hey @J-B-Mugundh I'm already on it.

Okay! Carry on.. Please try to make it a bit quick as u mentioned it would be over by yesterday.

hi @harish08102004 i m very sorry to infrom you that..today evening is your deadline to complete this issue..whatever may be the reasons for not completing...it should be completed...because many other issues are in pending because of this one...please understand the situation and work according to it..it been a week already..


manifest does not behave as it should since this release 1.0.2

From version 1.0.2 when you pass extra parameters it does not put them in object as before and as the documentation, as it always worked that way.

now you enter the variables directly instead of entering the structure as an object

@UlisesGascon @MatteoDiPaolo @inigomarquinez

Fixed in v2.0.0: https://www.npmjs.com/package/make-manifest


Discrepancy in twiss output between MAD-X and xtrack for solenoid

Dear all,
I obtain significant differences in the propagation of the twiss parameters through a solenoid between MAD-X (and TRACE3D) and xtrack. The single particle trajectories, also obtained with the respective twiss commands, only feature minor differences.
I reviewed the source code for the solenoid and experimented with different options (solenoid slicing, multipole kicks, reference particle etc.) but was not able to identify any obvious issues.
I’ve attached a small example. Could you let me know if this behaviour is expected or if I'm doing anything wrong?
Thanks a lot for your help,
Elisabeth
from cpymad.madx import Madx
import xtrack as xt
import matplotlib.pyplot as plt

# MADX
mad = Madx()
mad.input(
    '''
    BEAM;
    mso : solenoid, l =  0.3, ks=5.;
    end: marker;

    testsol: sequence, l = 1.5;
    mso, at = 1.15;
    end, at = 1.5;
    endsequence;
    '''
)
mad.use(sequence="testsol")

tw_madx = mad.twiss(
    x=0.005, y=0.005,
    px=0.001, py=-0.001,
    alfx=-0.4, alfy=-0.4,
    betx=0.4, bety=0.5
)

# Conversion
line = xt.Line.from_madx_sequence(
    sequence=mad.sequence.testsol,
    allow_thick=True,
    enable_align_errors=True,
    deferred_expressions=True
)

print(line.element_dict['mso'])
# prints:
#
# Solenoid(length=0.3, ks=5, ksi=0, radiation_flag=np.int64(0),
# num_multipole_kicks=np.int64(0), _order=np.int64(5),
# inv_factorial_order=0.00833, knl=array([0., 0., 0., 0., 0., 0.]),
# ksl=array([0., 0., 0., 0., 0., 0.]), mult_rot_y_rad=0, mult_shift_x=0,
# _sin_rot_s=-999, _cos_rot_s=-999, _shift_x=0, _shift_y=0,
# _shift_s=0, _internal_record_id=RecordIdentifier(buffer_id=np.int64(0), offset=np.int64(0))

line.particle_ref = xt.Particles(mass0=xt.PROTON_MASS_EV,
                            p0c=3.86e6)

tw = line.twiss(x=0.005, y=0.005, px=0.001, py=-0.001,
        alfx=-0.4, alfy=-0.4, betx=0.4, bety=0.5)

# plot Twiss parameters
plt.figure(figsize=(4, 3))
plt.plot(tw_madx.s, tw_madx.betx, color='black', label=r'$\beta_x$ (MAD-X)')
plt.plot(tw.s, tw.betx, linestyle='--', color='black', label=r'$\beta_x$ (xtrack)')
plt.plot(tw_madx.s, tw_madx.bety, color='red', label=r'$\beta_y$ (MAD-X)')
plt.plot(tw.s, tw.bety, linestyle='--', color='red', label=r'$\beta_y$ (xtrack)')
plt.axvspan(1,1.3, color='gray', alpha=0.3)
plt.xlabel('s / m')
plt.ylabel(r'$\beta$ / m')
plt.legend()
plt.tight_layout()
plt.savefig('beta.png')
plt.close()  # Close the figure after saving to avoid overlapping plots

# plot trajectory differences
plt.figure(figsize=(4,3))
plt.plot(tw_madx.s, (tw_madx.x-tw.x[1:]), color='black', label='x')
plt.plot(tw_madx.s, (tw_madx.y-tw.y[1:]), color='red', label='y')
plt.axvspan(1,1.3, color='gray', alpha=0.3)
plt.xlabel('s / m')
plt.ylabel(r'$u_{madx} - u_{xtrack}$ / m')
plt.tight_layout()
plt.legend()
plt.savefig('traj.png')

I suspect it comes from coupling and the different definitions of the betx,bety using the edwarg-teng (default MAD-X) and (Mais-Ripken default xsuite). Could you check if it is the case by using the ripken option in madx?

Hi Riccardo,
Indeed, that explains it. My bad, I had missed that.
Thanks for the fast response!
Cheers, Elisabeth

Thank you for the check. Don't hesitate to reopen in case you still see issues.


feat: add cosmosdb

This adds an Azure CosmosDB Producer.

the output producer by the template must be json
the  json must contain the field declared as partition_key in the configuration


Enable PWM for stm32f100

Crate stm32f1 handles CCRx registers differently for stm32f103
and for all the other supported MCU families. As a result,
naming conventions to access CCRx fields  are not the same.
Enable support for PWM on stm32f100 using 'feature' switch to
distinguish between stm32f103 and other MCUs at compile time
and use the correct CCRx field names.
Signed-off-by: Sergey Matyukevich<EMAIL_ADDRESS>

Thanks for your contribution. I've one question and one request to make:

Crate stm32f1 handles CCRx registers differently for stm32f103 and for all the other supported MCU families.

Does this mean stm32f103 is different to all other chips (which essentially matches your implementation), or is stm32f100 different to all other chips (in which case it would be better to match for the stm32f100 feature)?
Could you also please add an entry to CHANGELOG.md?

Hi @therealprof

In fact, I don't think there is a difference. According to datasheets, general-purpose TIM registers are the same. It looks like it is all about TIM register naming conventions. For instance, for stm32f103 it is tim2::ccr::CCR and for stm32f100 (and all the other chip families in f1 crate) it is tim2::ccrX::CCRX. So far I couldn't figure out why it is different by looking at SVD files.

Let me know if it makes sense to fix on stm32f1 level rather then in stm32f1xx-hal.

Changelog: will do and resubmit tomorrow. Unless you suggest to follow stm32f1 fixing path...

Regards,
Sergey

@geomatsi Yes, it should eventually be fixed in stm32-rs, working around it should be fine for now, please add a comment to your change about this.

https://github.com/stm32-rs/stm32-rs/pull/169
https://github.com/stm32-rs/stm32-rs/pull/167

Hi @therealprof and all,
Updated Changelog.md file and force-pushed PR.
Regards,
Sergey


mgmt, remove dockerfile

fix https://github.com/Azure/azure-sdk-for-java/issues/28632
Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check for com.azure.resourcemanager:azure-resourcemanager-samples
API review is created for com.azure.resourcemanager:azure-resourcemanager-samples. You can review APIs here.


Fix wrong results after pow and sqrt

Fixes #222.
Description of the changes:

Pow is calculated for Numerator and Denominator separately to avoid rounding difference
gcdrat fixed to not accept result if optimization caused change in numeric value

How changes were validated:

new automated tests added

Replaced by #297


Dynomite server crashes in Memcached mode

When I start dynomite (I'm using code from v0.6 branch) it often fails (50% of the time) with:
[2017-11-20 12:57:52.619] conf_push_scalar:541 push 'memcached-4:8101:memcached-rack2:dc2:4294967294' [2017-11-20 12:57:52.620] conf_handler:1291 conf handler on dyn_seeds: memcached-4:8101:memcached-rack2:dc2:4294967294 [2017-11-20 12:57:52.622] _dn_alloc:259 malloc(24) at 0x1c53e30 @ ../dyn_array.c:64 [2017-11-20 12:57:52.623] conf_server_init:134 init conf server 0x1c538c0 [2017-11-20 12:57:52.660] dn_resolve_inet:520 address resolution of node 'memcached-4' service '8101' failed: Name or service not known [2017-11-20 12:57:52.660] _dn_free:305 free(0x1c53ed0) @ dyn_string.c:59 [2017-11-20 12:57:52.660] conf_handler:1302 conf: directive "dyn_seeds" has an invalid value [2017-11-20 12:57:52.660] conf_pop_scalar:564 pop 'memcached-4:8101:memcached-rack2:dc2:4294967294' [2017-11-20 12:57:52.660] _dn_free:305 free(0x1c53e50) @ dyn_string.c:59 dynomite: configuration file '/etc/dynomite/conf/memcached-3.yml' syntax is invalid [2017-11-20 12:57:52.660] conf_pop_scalar:564 pop 'dyn_seeds' [2017-11-20 12:57:52.660] _dn_free:305 free(0x1c53810) @ dyn_string.c:59 [2017-11-20 12:57:52.660] conf_pop_scalar:564 pop 'dyn_o_mite' [2017-11-20 12:57:52.660] _dn_free:305 free(0x1c53790) @ dyn_string.c:59 [2017-11-20 12:57:52.660] _dn_free:305 free(0x1c41b70) @ ../dyn_array.c:82 [2017-11-20 12:57:52.660] _dn_free:305 free(0x1c53710) @ dyn_string.c:59 [2017-11-20 12:57:52.660] dn_stacktrace:326 [0] /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390) [0x7fa2eaa2c390] ??:0 [2017-11-20 12:57:52.664] dn_stacktrace:326 [1] dynomite(string_deinit+0x3) [0x429953] /dynomite/src/dyn_string.c:58 [2017-11-20 12:57:52.669] dn_stacktrace:326 [2] dynomite(conf_destroy+0x55) [0x410385] /dynomite/src/dyn_conf.c:146 [2017-11-20 12:57:52.674] dn_stacktrace:326 [3] dynomite(conf_create+0x170) [0x410680] /dynomite/src/dyn_conf.c:2233 [2017-11-20 12:57:52.681] dn_stacktrace:326 [4] dynomite(core_start+0x80) [0x415350] /dynomite/src/dyn_core.c:281 [2017-11-20 12:57:52.685] dn_stacktrace:326 [5] dynomite(main+0x64f) [0x40cdff] /dynomite/src/dynomite.c:574 [2017-11-20 12:57:52.690] dn_stacktrace:326 [6] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7fa2ea368830] ??:0 [2017-11-20 12:57:52.693] dn_stacktrace:326 [7] dynomite(_start+0x29) [0x40d2a9] ??:? [2017-11-20 12:57:52.698] signal_handler:132 signal 11 (SIGSEGV) received, core dumping
meaning it can't discover another dynomite node.
Also, if one node goes down, and other node tries to replicate - it also goes down.
I'm running several dynomite nodes in docker, so there is definitely some race condition between nodes, but guess dynomite should some how gracefully handle such cases (try to reconnect several times after some timeout?).
What would you suggest to do to avoid this problem?
Here is my config (for reference):
`dyn_o_mite:
datacenter: dc2
dyn_listen: <IP_ADDRESS>:8101
dyn_port: 8101
dyn_seed_provider: simple_provider
dyn_seeds:
memcached-4:8101:memcached-rack2:dc2:4294967294
listen: <IP_ADDRESS>:8102
rack: memcached-rack2
servers:
<IP_ADDRESS>:11211:1
timeout: 150000
tokens:<PHONE_NUMBER>
data_store: 1
dyn_o_mite:
datacenter: dc2
dyn_listen: <IP_ADDRESS>:8101
dyn_port: 8101
dyn_seed_provider: simple_provider
dyn_seeds:
memcached-3:8101:memcached-rack2:dc2:2147483647
listen: <IP_ADDRESS>:8102
rack: memcached-rack2
servers:
<IP_ADDRESS>:11211:1
timeout: 150000
tokens:<PHONE_NUMBER>
data_store: 1`
2)When I'm trying to use Spy Memcached client and save data - it works fine.
But when I'm trying to read I receive:
[2017-11-20 12:44:49.561] server_rsp_forward:834 <CONN_CLIENT 0x528b660 11 from '<IP_ADDRESS>:54290'> <REQ 0x556fc00 4124:0::1 REQ_MC_GET, len:14> RECEIVED <RSP 0x5b1ce00 4126:0 RSP_MC_END len:5> [2017-11-20 12:44:49.561] stats_server_to_metric:1800 metric 'read_responses' for server [2017-11-20 12:44:49.561] _stats_server_incr:1816 incr field 'read_responses' to 1 [2017-11-20 12:44:49.561] stats_server_to_metric:1800 metric 'read_response_bytes' for server [2017-11-20 12:44:49.561] _stats_server_incr_by:1846 incr by field 'read_response_bytes' to 5 [2017-11-20 12:44:49.561] msg_local_one_rsp_handler:1005 <REQ 0x556fc00 4124:0::1 REQ_MC_GET, len:14> SELECTED <RSP 0x5b1ce00 4126:0 RSP_MC_END len:5> [2017-11-20 12:44:49.564] dn_stacktrace:326 [0] /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390) [0x7f07351b4390] ??:0 [2017-11-20 12:44:49.578] dn_stacktrace:326 [1] dynomite(memcache_post_coalesce+0x114) [0x4331a4] /dynomite/src/proto/dyn_memcache.c:1556 [2017-11-20 12:44:49.596] dn_stacktrace:326 [2] dynomite(req_done+0x174) [0x420994] /dynomite/src/dyn_request.c:148 [2017-11-20 12:44:49.612] dn_stacktrace:326 [3] dynomite() [0x40db52] /dynomite/src/dyn_client.c:282 [2017-11-20 12:44:49.622] dn_stacktrace:326 [4] dynomite(msg_recv+0x575) [0x420385] /dynomite/src/dyn_message.c:890 [2017-11-20 12:44:49.632] dn_stacktrace:326 [5] dynomite(core_core+0xff) [0x414aff] /dynomite/src/dyn_core.c:386 [2017-11-20 12:44:49.641] dn_stacktrace:326 [6] dynomite(event_wait+0xeb) [0x43a90b] /dynomite/src/event/dyn_epoll.c:259 (discriminator 2) [2017-11-20 12:44:49.713] dn_stacktrace:326 [7] dynomite(core_loop+0x166) [0x415996] /dynomite/src/dyn_core.c:650 (discriminator 4) [2017-11-20 12:44:49.732] dn_stacktrace:326 [8] dynomite(main+0x671) [0x40ce21] /dynomite/src/dynomite.c:585 [2017-11-20 12:44:49.743] dn_stacktrace:326 [9] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f0734af0830] ??:0 [2017-11-20 12:44:49.755] dn_stacktrace:326 [10] dynomite(_start+0x29) [0x40d2a9] ??:? [2017-11-20 12:44:49.774] signal_handler:132 signal 11 (SIGSEGV) received, core dumping /dynomite/startup.sh: line 6: 9 Segmentation fault (core dumped) dynomite --conf-file=/etc/dynomite/conf/${DYN_CONFIG_FILE} --verbosity=11
is this some known problem?

Try to create different issues for different crashes.
For the first one, it complains that the syntax for the file is invalid, can you post your conf file for that node?
For the second case, this could be a bug since that is part of the code that I changed recently and we do not use memcache actively internally so may be few things slipped through the crack. Can you please try if v0.5.9 works for you?

For the first issue - I've mentioned my config above:
dyn_o_mite:
datacenter: dc2
dyn_listen: <IP_ADDRESS>:8101
dyn_port: 8101
dyn_seed_provider: simple_provider
dyn_seeds:
memcached-4:8101:memcached-rack2:dc2:4294967294
listen: <IP_ADDRESS>:8102
rack: memcached-rack2
servers:
<IP_ADDRESS>:11211:1
timeout: 150000
tokens:<PHONE_NUMBER>
data_store: 1
dyn_o_mite:
datacenter: dc2
dyn_listen: <IP_ADDRESS>:8101
dyn_port: 8101
dyn_seed_provider: simple_provider
dyn_seeds:
memcached-3:8101:memcached-rack2:dc2:2147483647
listen: <IP_ADDRESS>:8102
rack: memcached-rack2
servers:
<IP_ADDRESS>:11211:1
timeout: 150000
tokens:<PHONE_NUMBER>
data_store: 1
let me try 0.5.9
thanks for feedback

let me know once you tried 0.5.9

Same problem with 0.5.9

I can reproduce this as well using dynomite inside Docker (built with the official Dockerfile). My config:
dynomite:
  dyn_listen: <IP_ADDRESS>:8101
  listen: <IP_ADDRESS>:8102
  stats_listen: <IP_ADDRESS>:22222
  data_store: 1
  tokens:<PHONE_NUMBER>
  servers:
    - memcached-1:11211:10

I saved that as dynomite.yml,  started a memcached container, and ran the following to start the Dynomite container:
docker run -v $PWD/dynomite.yml:/etc/dynomite.yml -p 8102:8102 --rm --entrypoint '/dynomite/src/dynomite' --net testbed_default dynomite -c /etc/dynomite.yml -v11
Then, I ran the following to trigger the crash: echo -n "get foo\r\n" | nc localhost 8102
The full log file from Dynomite is at output.txt

To add to my previous comment: it looks like it was an issue of the services in Docker repeatedly failing because they couldn't find each other and eventually they happened to be up at the same time.
I don't think that should be reported as "invalid syntax" since the syntax is obviously correct.

Invalid syntax is reported for dynomite.yml, not in case of miscommunication. I am not following the issue you are facing and how it is related to Docker container communication.

I'm saying the logs from Dynomite are telling me the syntax is invalid even though it's apparently not invalid.

Can you send us your Dynomite logs?

Sigh. I just spun up the services again and am now not getting this error. I have not changed the config file at all, so the syntax is the same as before when it was throwing the invalid syntax error.


Kernel interrupt test hangs when running with IRQ lock intolerant timer

Describe the bug
The tests/kernel/interrupt test (in particular, test_prevent_interruption) hangs when running on a platform that uses a system timer that requires the timer interrupt to be serviced in order for z_timer_cycle_get_32 to return the correct value (i.e. "IRQ lock intolerant timer").
These platforms include (but are not limited to):

qemu_nios2 (altera_avalon_timer_hal)
qemu_cortex_r5 (xlnx_psttc_timer)

To Reproduce
Build and run tests/kernel/interrupt for any of the aforementioned platforms.
Expected behavior
test_prevent_interruption successfully completes.
Screenshots or console output
*** Booting Zephyr OS build zephyr-v2.2.0-381-g1c6487474842  ***
Running test suite interrupt_feature
===================================================================
starting test - test_isr_dynamic
PASS - test_isr_dynamic
===================================================================
starting test - test_nested_isr
SKIP - test_nested_isr
===================================================================
starting test - test_prevent_interruption
locking interrupts

Environment (please complete the following information):

OS: Ubuntu 18.04
Toolchain: Zephyr SDK 0.11.2
Commit SHA: 1c6487474842a694c1bcb0cea5055b846b81aab6

Analysis
This happens because test_prevent_interruption calls k_busy_wait, which uses z_timer_cycle_get_32 for time reference, after locking (disabling) interrupts.
Since the z_timer_cycle_get_32 implementation for the aforementioned platforms returns the value of an internal counter that is updated by the timer ISR, the k_busy_wait function, which relies on that function, hangs when interrupt is locked.
Proposed solution
~Use a wait mechanism that does not rely on the z_timer_cycle_get_32 function in the test.~
Since it is indeed expected of z_timer_cycle_get_32 (and therefore k_busy_wait) to work when IRQ is locked, we must fix the system timer drivers for the aforementioned platforms instead.

cc @andrewboie

Related to #22956

@stephanosio the problem here is that when IRQs are locked, k_busy_wait() hangs forever. This is the bug, the issue is not the test, the test happens to expose it.
I would NACK any patch that changes the test to sweep this issue under the rug. If anything, a specific dedicated test that shows that k_busy_wait() works with IRQs locked needs to be added

Jumping in with a quick triage on those two drivers, just for postericty: yeah, what both of these do is return a static in-memory count from z_timer_cycle_get_32() which is updated only from the timer ISR.  So anything that blocks the timer ISR from arriving will prevent this clock from advancing.
The intent of this API is that it should be a synchronous read from some sort of hardware counter, so this scheme (implementing the cycle counter in terms of the timer driver) really can't be correct.  Though apparently we can get away with it for a lot of tests (most k_busy_wait() happens in drivers, which are platform-specific anyway).
I don't know the Altera and Xilinx hardware in question.  Surely they have a register where we can read the current count, no?

This (unused) register in the Xilinx driver looks promising:
#define XTTCPS_COUNT_VALUE_OFFSET  0x00000018U  /**< Current Counter Value */

The Altera driver is on top of a HAL with thicker headers, so I gave up looking.  I'm sure it has one too though.

@andyross Altera requires another timer source AFAIK. There is a comment that explains this. This is a virtual FPGA CPU so it's possible to configure this when defining the CPU itself. Nobody's had time or inclinationt to add support yet.
	/* Per the Altera Embedded IP Peripherals guide, you cannot
	 * use a timer instance for both the system clock and timestamps
	 * at the same time.
	 *
	 * Having this function return accumulated_cycle_count + get_snapshot()
	 * does not work reliably. It's possible for the current countdown
	 * to reset to the next interval before the timer interrupt is
	 * delivered (and accumulated cycle count gets updated). The result
	 * is an unlucky call to this function will appear to jump backward
	 * in time.
	 *
	 * To properly obtain timestamps, the CPU must be configured with
	 * a second timer peripheral instance that is configured to
	 * count down from some large initial 64-bit value. This
	 * is currently unimplemented.
	 */

If anything, a specific dedicated test that shows that k_busy_wait() works with IRQs locked needs to be added

@andrewboie That would be helpful. There seem to be quite a few (at least 3 IIRC) timer drivers that do not conform to this.

@andyross For Xilinx (and possibly Altera), we would need to do one of the following:

Switch the timer mode of operation from "Interval" to "Capture" (i.e. convert it to a "running timer") and return its register value.
Use another timer as an always-running timer and return its register value.

It seems like I might already have a fix here (I was going to implement tickless support for TTC, but decided to drop it because QEMU didn't like it; #19869):
https://github.com/stephanosio/zephyr/commit/9da8fdef6db8d29e658cbafb3e69f9fca6dd6961
I will create a PR for this today (without tickless support).

As far as I can see, the litex_timer should have the same problem.
@mateusz-holenko @kgugala @pgielda Could you confirm?

@stephanosio It seems so after reading the code, but we'll verify this on HW.

One note relative to the issues being discussed here: devices without access to a proper cycle counter can solve this alternatively with CONFIG_ARCH_HAS_CUSTOM_BUSY_WAIT and an appropriate amount of magic (e.g. a hand-tuned assembly loop).  The use of z_timer_get_cycle_32() is just the default implementation.

@stephanosio I confirm that the test fails on the HW:
(venv) grey@grey:~/localantmicro/zephyr/sanity-out/litex_vexriscv/arch.interrupt$ sudo flterm --port /dev/ttyUSB1 --kernel zephyr/zephyr.bin --speed 115200
[sudo] password for grey:
[FLTERM] v2.4-31-g8898c78 Starting...
        __   _ __      _  __
       / /  (_) /____ | |/_/
      / /__/ / __/ -_)>  <
     /____/_/\__/\__/_/|_|
 (c) Copyright 2012-2019 Enjoy-Digital
 BIOS built on Mar 16 2020 09:58:40
 BIOS CRC passed (74875417)
 Migen git sha1: d11565a
 LiteX git sha1: 02bfda5e
--=============== SoC ==================--
CPU:       VexRiscv @ 100MHz
ROM:       32KB
SRAM:      32KB
L2:        8KB
MAIN-RAM:  262144KB
--========== Initialization ============--
Initializing SDRAM...
SDRAM now under software control
Read leveling:
m0, b0: |11111111110000000000000000000000| delays: 05+-05
m0, b1: |00000000000000111111111111000000| delays: 20+-06
m0, b2: |00000000000000000000000000000001| delays: 31+-00
m0, b3: |00000000000000000000000000000000| delays: -
m0, b4: |00000000000000000000000000000000| delays: -
m0, b5: |00000000000000000000000000000000| delays: -
m0, b6: |00000000000000000000000000000000| delays: -
m0, b7: |00000000000000000000000000000000| delays: -
best: m0, b1 delays: 20+-06
m1, b0: |11111111110000000000000000000000| delays: 05+-05
m1, b1: |00000000000000111111111111000000| delays: 20+-06
m1, b2: |00000000000000000000000000000001| delays: 31+-00
m1, b3: |00000000000000000000000000000000| delays: -
m1, b4: |00000000000000000000000000000000| delays: -
m1, b5: |00000000000000000000000000000000| delays: -
m1, b6: |00000000000000000000000000000000| delays: -
m1, b7: |00000000000000000000000000000000| delays: -
best: m1, b1 delays: 20+-06
SDRAM now under hardware control
Memtest OK
--============== Boot ==================--
Booting from serial...
Press Q or ESC to abort boot completely.
sL5DdSMmkekro
[FLTERM] Received firmware download request from the device.
[FLTERM] Uploading kernel (26828 bytes)...
[FLTERM] Upload complete (7.7KB/s).
[FLTERM] Booting the device.
[FLTERM] Done.
Executing booted program at 0x40000000
--============= Liftoff! ===============--
*** Booting Zephyr OS build zephyr-v2.2.0-313-g4fd38265224d  ***
Running test suite interrupt_feature
===================================================================
starting test - test_isr_dynamic
PASS - test_isr_dynamic
===================================================================
starting test - test_nested_isr
Triggering irq : 90
PASS - test_nested_isr
===================================================================
starting test - test_prevent_interruption
locking interrupts

We'll look into this.

@stephanosio I confirm that the test fails on the HW:

@mateusz-holenko Thanks for checking. I have created an issue to track this: #23622.


fix typo

Pull Request Test Coverage Report for Build 4259

0 of 0   changed or added relevant lines in 0 files are covered.
21 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.04%) to 36.379%

Files with Coverage Reduction
New Missed Lines
%

azkaban-exec-server/src/main/java/azkaban/execapp/event/JobCallbackRequestMaker.java
21
56.25%

Totals

Change from base Build 4256:
-0.04%

Covered Lines:
10678

Relevant Lines:
29352

💛  - Coveralls


replace suppressing rules for static analysis with ignore_for_file: type=lint

Hello,
I'm using the bloc pattern with the recommended very_good_analysis. This results in many linting warnings with isars generated files such as "Document all public members.", "Cascade consecutive method invocations on the same reference.", and so on. This gets especially frustrating when you keep making changes to your models.
A simple solution would be to replace the generated rules with "// ignore_for_file: type=lint" which would remove linting from the generated files all together.

Isar version: 3.0.5

Im really glad that we got a new update for Isar and that the project seems to be alright.
Since this easy fix was not included in the this update I'd like to bring some attention to it again.
Can we hope to see it in the next version?


Fix requirements and tests for test data repo

opencdms-test-data requirements currently depends on a dev branch (52-pygeoapi-provider-plugin-for-surface-cdms) of the old opencdms-dev version of pyopencdms:
https://github.com/opencdms/opencdms-test-data/blob/main/requirements_dev.txt#L9

Addressed by http://github.com/opencdms/pyopencdms/issues/2


[Bug] Downloading Issue

Is there an existing issue for this?

[X] Yes, I have searched the existing issues

Product Variant
Cloud (http://rxresu.me)
Current Behavior
After downloading the resume in PDF format,  it only shows half part of the resume.
Here is an example,
RxResume_PDFExport_2020a3t005_shahida-jahangir_1694611686.pdf
Expected Behavior
No response
Steps To Reproduce
No response
What browsers are you seeing the problem on?
No response
Anything else?
No response

Hi and ?


[kmac] Report entropy error on app interface

Hi KMAC experts,
I would like to confirm a current design behavior:
1). EDN related error occurs (for example: entropy timeout, entropy configured wrong mode etc)
2). The error is reflected to err_code register and interrupt kmac_err_o will fire
3). However, if the kmac operations is in APP interface, the behavior is different:
a). If it is keymgr interface, the error bit is set to 1.
b). If it is rom_ctrl or lc_ctrl interface, the error bit is NOT set.  -> Is this okay? Shall we still fire an error?
We would like to check if the application interface behavior is expected.
Thanks,
Cindy

ah it kind of feels like the behavior should probably be consistent.


Add flag for docker container to disable PEAnalyzer

Is your feature request related to a problem? Please describe.
We are currently seeing errors where analyzing Google.Protobuff.dll is failing. I am basing this off the following log file, but to be honest where the logs are showing results from many threads it could be a different file.
2023-07-25 14:50:35,103 org.owasp.dependencycheck.AnalysisTask:90
WARN  - An error occurred while analyzing '/src/src/<REDACTED>/bin/Debug/net7.0/Google.Protobuf.dll' (PE Analyzer).
2023-07-25 14:50:35,107 org.owasp.dependencycheck.AnalysisTask:91
DEBUG -
org.owasp.dependencycheck.analyzer.exception.AnalysisException: java.io.EOFException: Expected to read bytes from the stream
	at org.owasp.dependencycheck.analyzer.PEAnalyzer.analyzeDependency(PEAnalyzer.java:273)
	at org.owasp.dependencycheck.analyzer.AbstractAnalyzer.analyze(AbstractAnalyzer.java:131)
	at org.owasp.dependencycheck.AnalysisTask.call(AnalysisTask.java:88)
	at org.owasp.dependencycheck.AnalysisTask.call(AnalysisTask.java:37)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: java.io.EOFException: Expected to read bytes from the stream
	at org.boris.pecoff4j.io.DataReader.safeRead(DataReader.java:157)
	at org.boris.pecoff4j.io.DataReader.skipBytes(DataReader.java:85)
	at org.boris.pecoff4j.io.ResourceParser.alignDataReader(ResourceParser.java:299)
	at org.boris.pecoff4j.io.ResourceParser.readStringPair(ResourceParser.java:217)
	at org.boris.pecoff4j.io.ResourceParser.readStringTable(ResourceParser.java:204)
	at org.boris.pecoff4j.io.ResourceParser.readStringFileInfo(ResourceParser.java:246)
	at org.boris.pecoff4j.io.ResourceParser.readVersionInfo(ResourceParser.java:151)
	at org.boris.pecoff4j.io.ResourceParser.readVersionInfo(ResourceParser.java:122)
	at org.owasp.dependencycheck.analyzer.PEAnalyzer.analyzeDependency(PEAnalyzer.java:165)
	... 7 common frames omitted

Describe the solution you'd like
We wish to leave the other --experimental analyzers enabled. Other analyzers appear to have the ability to pass a CLI flag to dependency-check.sh that will disable various analyzers.
Something like --disablePEAnalyzer that would disable the analyzer.
Describe alternatives you've considered
We could disable all analyzers but there doesn't appear to be an enable option other than --experimental.
Additional context
We are running the docker container as part of a github action.

As well I would also love to see something like the ossIndexRemoteErrorWarnOnly flag that would allow us to treat the errors as warnings rather than being fatal.

@trdyer for the latter I presume you'd like a similar switch as failOnError for the maven plugin? That is: a flag that is by default true, causing it to exit with RC 13 on fatal errors and RC 14 on non-fatal errors (e.g. errors of individual analyzers so that the results of the tool are to be considered incomplete), changing the behavior for non-fatal errors to return RC 0 as if all went well (still breaking on fatal errors)


Unhandled Runtime Error  ChunkLoadError: Loading chunk vendor failed. i have installed everything latest in alpine container and getting this error which is related to excalidraw i guess so any fixes for it?


Incompatable with Ansible 2.9+

The filter 'version_compare' has been deprecated for some time. I see a ticket was opened on this, but the issue was closed without being addressed.
Previous ticket (154)
Error message:
TASK [mindpointgroup.stig_rhel6 : Check OS version and family] *****************
task path: /home/nick/.ansible/roles/mindpointgroup.stig_rhel6/tasks/main.yml:1
fatal: [ec1-1-1-1.compute-1.amazonaws.com]: FAILED! => {
    "msg": "The conditional check 'ansible_os_family == 'RedHat' and ansible_distribution_major_version | version_compare('6', '==')' failed. The error was: template error while templating string: no filter named 'version_compare'. String: {% if ansible_os_family == 'RedHat' and ansible_distribution_major_version | version_compare('6', '==') %} True {% else %} False {% endif %}"
}

That playbook has two tasks in main that call that filter:
- name: Check OS version and family
  assert:
      that: ansible_os_family == 'RedHat' and ansible_distribution_major_version | version_compare('6', '==')
      msg: "This role can only be run against RHEL/CENTOS 6. {{ ansible_distribution }} {{ ansible_distribution_major_version }} is not supported."
  tags:
      - always

- name: Check ansible version
  assert:
      that: ansible_version.full | version_compare(rhel6stig_min_ansible_version, '>=')
      msg: You must use Ansible {{ rhel6stig_min_ansible_version }} or greater
  tags:
      - always

This is fixed. You seem to have an old checkout.

It's still in the latest release? I just manually downloaded it.
tasks/main.yml
Lines 3 and 10

https://github.com/MindPointGroup/RHEL6-STIG/blob/cb79aee7f213a4505daf024fe3c63bf883d5d92f/tasks/main.yml#L1-L13
The failure you are seeing is the "tests as filters" deprecation from ansible-2.5.  The version_compare test is still good and has not been deprecated.
Your error has:
    that: ansible_os_family == 'RedHat' and ansible_distribution_major_version | version_compare('6', '==')
versus what's in the repo:
    that: ansible_os_family == 'RedHat' and ansible_distribution_major_version is version_compare('6', '==')

It's possible that a release to ansible galaxy has not been done in some time, but I'm not involved with that process.

It's also in the primary branch of this repo, so not sure where I'm missing a fix for it.

Was fixed here: https://github.com/MindPointGroup/RHEL6-STIG/pull/155 so it's not in the latest release.  I'll push to get an updated release cut.


Not letting me use recaptcha in two places on one page

Hi,
Thanks for the package it is fantastic!
I am having a slight problem. I have two forms on one page but its only letting me use reCaptcha once. Any solutions?

do you have two recaptchas there?

+1
Same issue here, I have two forms on one page, but I can't create twi configs on server neither on client

@meichenblatt the quick fix for this issue I'm using:

reCaptcha is hidden by default on both forms
after user click on submit - show reCaptcha
user needs to check reCaptcha
user needs to send form again by clicking on submit button

a bit not user-friendly, but works

@dr-dimitru https://github.com/appshore/Meteor-reCAPTCHA updated to allow multiple captchas.
@manybothans I will be happy to merge whatever part of the fork that you found useful since I'm no longer working full time with Meteor for the time being.


vs like codefix

how can i add a visual studio like popup(codefix) in avalonedit?

See https://github.com/icsharpcode/SharpDevelop/tree/master/src/AddIns/DisplayBindings/AvalonEdit.AddIn/Src/ContextActions for a possible implementation.


Undefined quiet method

Everytime that i try to use quiet method it show to me that the quiet method is undefined
Example ->
Hashie::Mash.quiet.new({'random': 'teste'})
Returns ->

This method was added in PR #488
Is this a bug or i'm doing something wrong?

What version of Hashie are you using?

I'm using 3.6.0

That method was introduced in v4.0.0

Ahh thx man, helped a lot


Show docker stats totals

It would be really useful if docker stats included a totals flag like -t so that it can add up the stats at the bottom like so:
CONTAINER           CPU %               MEM USAGE / LIMIT    MEM %               NET I/O               BLOCK I/O
dn1                 0.25%               243.5 MB / 6.24 GB   3.90%               576.4 kB / 1.313 MB   11.5 MB / 589.8 kB
dn2                 0.27%               246.3 MB / 6.24 GB   3.95%               565.7 kB / 1.327 MB   10.24 MB / 585.7 kB
...
=======================================================================================================================
1175.5kB            1%                  ....

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

I'm +1 on this.
This is helpful to me because I need the number of totals for performance test.
I'll take this if no one else if working on it.
#dibs

Closing as it was decided that it breaks some contract. Feel free to open new issue.


Test failure in fct_dbt__model_executions

The Unique test on this model is failing when I run on dbt Cloud:
Failure in test unique_fct_dbt__model_executions_model_execution_id (models/schemas.yml)

I suspect this is a result of two things, but it might still need more digging.

If I run all the commands (seed, run, test, etc.) and upload artifacts after each one following the instructions on this package's home page, I end up with two manifests with the same dbt_cloud_run_id (one from seed and one from run) which in turn creates two records per node in dim_dbt__models.
Using the dbt_cloud_run_id environment variable for this join in fct_dbt__model_executions:

model_executions_with_materialization as (

    select
        model_executions_incremental.*,
        models.model_materialization,
        models.model_schema,
        models.name
    from model_executions_incremental
    left join models on
        (
            model_executions_incremental.command_invocation_id = models.command_invocation_id
            or model_executions_incremental.dbt_cloud_run_id = models.dbt_cloud_run_id
        )
        and model_executions_incremental.node_id = models.node_id

),

This doesn't immediately get caught if you use dbt Cloud for ci because the first dbt run doesn't have the artifacts from itself, so only the manifest from dbt seed exists the first time dbt_artifacts runs. Any subsequent run fails.
A simple workaround is not to upload manifest after dbt run (or seed, but I figure it's good to upload it at the earliest possible step), but I'm not sure if that breaks anything later on in this package? If not, it might be a simple documentation fix to take manifest out of that step. I tested this and it resolves the failing test, I just don't know if this loses any detail I should have.
Another possible solution would be to coalesce(dbt_cloud_run_id, command_invocation_id) into a single field so when the cloud_run_id is present it gets used, otherwise it falls back on the command_invocation_id. This might be a bigger task throughout the package, but I think would have the side effect of solving this issue.

I've also just run into this problem. The simple workaround mentioned by djbelknapaw is helpful but doesn't resolve it for historical records that have already been uploaded.
I'm currently weighing up archiving historical data and truncating the dbt_artifacts_table in conjunction with the workaround to get tests passing again.

We've been busy reimplementing the package, opening it up to be compatible with more adapters. This shouldn't be a problem any more, we'd be grateful for any feedback on the first beta release: https://github.com/brooklyn-data/dbt_artifacts/releases/tag/1.0.0b1


question

Hi, by any chance the ding talk group disappeared. Did you unlock the room?

DingTalk group id: 645010455

Why can't I see the group??
I have a question
What should I do when inserting content in json format in coro_http? json is in key:value format.

dont search at groups, you should search it in the first tab.

dont search at groups, you should search it in the first tab.

Or: public group

The group is not visible in the public group as well.

In Postman, json is entered in the form {"name" : "asdf"}. How should I enter it in client.post?

Reference in new

how you join it before?

The group is not visible in the public group as well.

how you join it before?

{"name" : "asdf"}

just set this string as the parameter of the client.post

I did the same thing, but it doesn't work now, so I posted a question.

where is your history record?

I did the same thing, but it doesn't work now, so I posted a question.
Is there an issue with dingtalk right now??

I can search it and there is no problem.

I suddenly logged out of Dingtalk, and after logging back in, the group disappeared... I think it's an issue with my PC.

I was curious because an issue occurred when I put it in general json format.
Also, from the perspective of the server that received the request, I want to see both the key and value.

https://qr.dingtalk.com/action/joingroup?code=v1,k1,y2Lc5Ni9wUDVBa592sWFBz5y75fLAD3Fth2/7XoDlYc=&_dt_no_comment=1&origin=11

https://github.com/alibaba/yalantinglibs/discussions

https://github.com/alibaba/yalantinglibs/discussions

Please create you discussions here.

Oh, I logged out again and logged back in and was able to find the group, so I sent another group request..! Sorry!


Server disconnected without sending a response.

When I execute "python gradio_app.py --share" to build Gradio App, it works normally. But when I select seg to enter PROMPT（bear） and click RUN, "Server disconnected without sending a response" will appear.

Hello! Sry for the late response, we will try to figure out this problem later, you can also try to use the online demo~


Fix type mismatch for signTransaction in sol-ext

📦 Pull Request
[Provide a general summary of the pull request here.]
ref #695
✅ Fixed Issues

[List any fixed issues here like: Fixes #XXXX]

🚨 Test instructions
[Describe any additional context required to test the PR/feature/bug fix.]
⚠ Don't forget to add a semver label!
Please only add one label:

patch: Bug Fix?
minor: New Feature?
major: Breaking Change?
skip-release: It's unnecessary to publish this change.

📦 Published PR as canary version: Canary Versions

:sparkles: Test out this PR locally via:
npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>

:rocket: PR was released in<EMAIL_ADDRESS>:rocket:


working through crafting interpreters in Rust

leaving this here to leave some random comments behind - was surprised by the naive benchmark numbers
the program should be relatively simple and elegant, but rust has all this other random overhead (bringing in libgcc, mprotect, etc.). I thought fs::read would be super simple.
I also found that the unbuffered zig std.debug.print actually meant it would literally split up buffers by the line and was making double the syscalls to write() the output.
after making corrections, the clean zig implementation finally reports 2.28x speedup

after inlining the identifier logic, Rust got an insane perf boost...

benchmark 1 w/ PHF, it's completely overkill with such a small number of short strings. rarely will ever see a benefit in any compiler

safe utf8 checking vs. unchecked

inlined from_keywords (has a decent impact on performance when I used an example w/ no keywords)

using from_raw_parts for zero-copy string parsing

where i'm at w/ zig vs. rust impl

how did iterator give a free ~30% speedup?

Overview of all notable attempts at optimization in chronological order

one more experiment - match over byte slices is actually slower than the match over unchecked &str... this was surprising tbh, I thought for sure that unchecked str was adding significant overhead but I guess not.


Using an absolute spec path outside of karma basePath

I'm trying to write a script that dynamically builds the webpack entry file to get the best of both worlds (Usage/Alternate Usage in the readme.) from command line arguments. I'm putting this file in a temporary directory so the entry in the files array is an absolute path. However it looks like the require paths are somehow tied to the karma basePath. Is what I'm trying to do a terrible idea? Am I missing a crucial detail? Do I need to slightly tweak the karma-webpack implementation?

@maxkostow - Need to know if this is still an issue. For the sake of efficiency, we are starting with current versions and the team can work back from there.
If this is still an issue on a recent version of the loader & it's peerDeps, please respond here so we can get this properly triaged.

Yeah this is still an issue.

Thanks, well get it on the list and get into it.


Using init(attempt:) always produces Result with AnyError type

I'm using Result in one of my projects but the thing that I would really appreciate is the ability to initialize a Result with a throwing closure but with an arbitrary Error type. Eg.:
let result = Result<String, WrapperError>(attempt: { throw SomeOtherError() })

where WrapperError can wrap other Errors just like AnyError
I've submitted a pull request here: https://github.com/antitypical/Result/pull/254

Why are you using WrapperError instead of AnyError?
I'm curious why you'd do this and what benefit you're getting from it.

So, WrapperError is just an example of a concrete struct or enum that conforms to Error and can be initialized with an arbitrary Error (just like AnyError).
Let's say I have an error like this:
enum StringMangleError : Swift.Error, ErrorInitializing {
    case emptyString
    case stringTooLong
    case other(Error)

    init(_ error: Swift.Error) {
        if let stringMangleError = error as?  The only way I can think of writing that function now would be:
func asyncMangle(_ string: String, completion: (Result<String, StringMangleError>) -> Void) {
    do {
        completion(.success(try mangle(string)))
    } catch {
        completion(.failure(StringMangleError(error)))
    }
}

But with the proposed changes, it would be as easy as:
func asyncMangle(_ string: String, completion: (Result<String, StringMangleError>) -> Void) {
    completion(Result(attempt: { return try mangle(string) }))
}

I think the way you'd normally do this with Result would be:
func asyncMangle(_ string: String, completion: (Result<String, StringMangleError>) -> Void) {
    let result = Result<String, AnyError>(attempt: { return try mangle(string) })
        .mapError { StringMangleError($0.error) }
    completion(result)
}

It's not as concise as your example, but I'm not sure the indirection is worth the brevity in this case.

Right. I guess that's a slightly more brief and functional way of writing that.
However, I wasn't aiming so much for brevity but rather better inference, especially when it comes to errors.
It might seem inconsequential from the provided example but in my current project I'm connecting many classes where each class has its own Error enum. A less cumbersome way to map between results where two Results have the same associated Value type but different Error types would be much appreciated. Better inference for attempt: initializers (without the need to go through AnyError) would also greatly reduce clutter in my codebase.
Currently, Result(attempt: {"foo"}) always produces Result<String, AnyError>, with no possibility to infer other Error wrappers.
The following will currently not build:
let result: Result<String, CustomError> = Result(attempt: {"foo"} )
To achieve this, one needs to manually map AnyError to WrapperError (as you suggested):
let result: Result<String, WrapperError> = Result(attempt: {"foo"} ).mapError{ WrapperError($0.error) }
Additionally, Result({ "foo"}) also currently produces Result<String, AnyError>, although a non-throwing closure should in my opinion actually produce a Result<String, NoError>.
There is also currently no default inference for Result(value: "foo") although the inferred type could easily be Result<String, NoError>
In my updated pull request, the following is true
(assuming BasicError is just a simple struct that conforms to Error):

Result({"foo"}) is equivalent to Result<String, NoError>.success("foo")
Result(attempt: {"foo"}) is equivalent to Result<String, AnyError>.success("foo")
Result(attempt: { throw BasicError() } is equivalent to Result<String, AnyError>.failure(AnyError(BasicError()))
let result: Result<String, WrapperError> = Result(attempt: {"foo"}) is equivalent to Result<String, WrapperError>.success("foo") and will build if WrapperError conforms to ErrorInitializing
let result: Result<String, WrapperError> = Result(attempt: { throw BasicError()} ) will build and is equivalent to Result<String, WrapperError>.failure(WrapperError(BasicError())) if WrapperError conforms to ErrorInitializing
Result(attempt: { throw WrapperError(BasicError())} ) is equivalent to Result<String, AnyError>.failure(AnyError(BasicError())) if WrapperError conforms to ErrorConvertible (AnyError will actually wrap WrapperError's underlying Error)
let basicResult = Result<String, BasicError>(value: "foo") can be error-mapped with basicResult.mapError(to: WrapperError.self) or simply let wrappedResult: Result<String, WrapperError> = basicResult.mapError() if WrapperError conforms to ErrorInitializing

Here's what I'd suggest:

Result(attempt:) should only be used when calling code you don't control. Anything you do control should return a Result. You should wrap external code with an interface that returns a Result.

The custom errors that your code returns can be mapped into a different cases of an outer enum if you need to handle them in a single spot.

In general, relying on inference isn't a great idea because Swift's type inference is limited. So I'm always hesitant to add an API that relies solely on inference.

Closing this due to inactivity.


Testing a game that transfer lamports: "sum of account balances before and after instruction do not match"

instructions::play is defined like this:
use crate::state::game::*;
use anchor_lang::prelude::*;

pub fn play(ctx: Context<Play>, data: FlipArgs) -> Result<()> {
    let game = &mut ctx.accounts.game;
    game.flip(&ctx.accounts.player, data)
}

#[derive(Accounts)]
pub struct Play<'info> {
    #[account(mut)]
    pub game: Account<'info, Game>,
    #[account(init, payer = payer, space = Game::MAXIMUM_SIZE + 8)]
    /// CHECK: insecure
    pub player: AccountInfo<'info>,
    #[account(mut)]
    pub payer: Signer<'info>,
    pub system_program: Program<'info, System>,
}

game.flip will then attempt to charge the player a fee:
pub fn flip(&mut self, player: &AccountInfo, data: FlipArgs) -> Result<()> {
        match self.charge_fee(player) {
            Err(e) => return Err(e),
            _ => match data.heads_or_tails {
                true => self.play_heads(player),
                false => self.play_tails(player),
            },
        }
    }

    fn charge_fee(&self, player: &AccountInfo) -> Result<()> {
        if **player.try_borrow_lamports()? < self.static_amount {
            return Err(CoinflipError::InsufficientFunds.into());
        }

        let fee = self.calculate_fee();

        **player.try_borrow_mut_lamports()? -= fee as u64;

        Ok(())
    }

Typescript chai tests try to setup the game, airdrop balance to the player and then flip:
it("play: heads", async () => {
    const gameKeypair = anchor.web3.Keypair.generate();
    await setupGame(gameKeypair);

    const playerKeypair = anchor.web3.Keypair.generate();
    const signature = await programProvider.connection.requestAirdrop(
      playerKeypair.publicKey,
      anchor.web3.LAMPORTS_PER_SOL,
    );
    await programProvider.connection.confirmTransaction(signature);
    const balance = await programProvider.connection.getBalance(playerKeypair.publicKey);

    console.log(balance);

    await program.methods
      .flip({ headsOrTails: true })
      .accounts({
        game: gameKeypair.publicKey,
        player: playerKeypair.publicKey,
      })
      .signers([playerKeypair])
      .rpc();

    // ...
  });

But fails with:
2) solana-anchor-coinflip
       play: heads:
     Error: failed to send transaction: Transaction simulation failed: Error processing Instruction 0: sum of account balances before and after instruction do not match
      at Connection.sendEncodedTransaction (node_modules/@solana/web3.js/src/connection.ts:4068:13)
      at processTicksAndRejections (internal/process/task_queues.js:93:5)
      at Connection.sendRawTransaction (node_modules/@solana/web3.js/src/connection.ts:4030:20)
      at sendAndConfirmRawTransaction (node_modules/@project-serum/anchor/src/provider.ts:284:21)
      at AnchorProvider.sendAndConfirm (node_modules/@project-serum/anchor/src/provider.ts:144:14)
      at MethodsBuilder.rpc [as _rpcFn] (node_modules/@project-serum/anchor/src/program/namespace/rpc.ts:29:16)

I think the problem lies in the pub struct Play definition:
#[derive(Accounts)]
pub struct Play<'info> {
    #[account(mut)]
    pub game: Account<'info, Game>,
    #[account(init, payer = payer, space = Game::MAXIMUM_SIZE + 8)]
    /// CHECK: insecure
    pub player: AccountInfo<'info>,
    #[account(mut)]
    pub payer: Signer<'info>,
    pub system_program: Program<'info, System>,
}

@SvenDowideit @joemccann @tomlinton @fanatid would appreciate your help here as the TicTacToe example does not include payments or lamport transfers.
cc @susguzman @ktoxcon

pls go to discord for support questions like this


spring-security-oauth2: DefaultRedirectResolver does not check port in redirection endpoint

Not sure if this is intentional or not, but there are no doc (at least not in code) that indicates that the port part of the URI is ignored:
https://github.com/spring-projects/spring-security-oauth/blob/master/spring-security-oauth2/src/main/java/org/springframework/security/oauth2/provider/endpoint/DefaultRedirectResolver.java#L117
This means that http://somesite.com:8080/rdr may be the only registered endpoint, but http://somesite.com:1234/rdr will still work.
Probably not an issue in real-world deployments but..

It's been that way for a long time as far as I can tell. We match the protocol and the host and path, but not the port. I added a sentence to java docs.


Add focus state styles for the cookie banner

What
Further to https://github.com/alphagov/govuk-frontend/issues/2098, we should add a focus style for the cookie banner. This could be similar to the notification banner focus state.
We could add this in https://github.com/alphagov/govuk-frontend/pull/2126 or separately if we don't want to block merging that PR.
Why
The cookie banner needs to have a focus state as it should be focused after the user accepts or rejects cookies.
Who needs to know about this
Designer, developer
Done when

[ ] We've decided what the focus state should be
[ ] We've added the styles
[ ] The styles have been reviewed by a designer

Two ideas for team review:
Offset outline

Background and underline to text

We have decided to publish the component without a visible focus state to start with.
From @hannalaakso: The focused cookie banner is the first element on the page and the last thing the user
interacted with prior to it gaining focus. We therefore assume that moving focus to it is not going to surprise users, and that giving it a visible focus indicator could be more confusing than helpful, especially as the element is not normally keyboard operable.
We have flagged this in the research section of the guidance as something to monitor.
A related discussion: w3c/wcag#1001
It's also worth noting that this is different to what we do with the notification banner which does have a visible focus indicator. However, the notification banner is further down the page and the user might not have interacted with it prior to it gaining focus so it is helpful to indicate to users that the focus has moved to it (even though the element, like the cookie banner, isn’t normally keyboard operable).


Mac app crashes

The last version 0.2.1 crashes after login with Google:
Crashed Thread:        11  Chrome_IOThread
Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000010
Exception Note:        EXC_CORPSE_NOTIFY

Getting the same on a fully up to date Mac. Can dump a full log but seems like it's pretty reproducible on login with a google acct.

I had this same problem. Re-installed Chrome in Applications and it fixed it.


[INFRA] Update archive mailing list address

Why are the changes needed?

Replace the obsolete address with a new one.
How was this patch tested?

Review
Was this patch authored or co-authored using generative AI tooling?

No

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

Project coverage is 0.00%. Comparing base (eb1b599) to head (858e6cc).

Additional details and impacted files
@@          Coverage Diff           @@
##           master   #6838   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files         687     687
  Lines       42441   42441
  Branches     5793    5793
======================================
  Misses      42441   42441

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

Thanks, merged to all release branches, namely master/1.10/1.9


VM's lookupResolvedPackageUris returns mismatched results when a filename contains a comma

Found in https://github.com/Dart-Code/Dart-Code/issues/4572. If a filename contains a comma, the results of lookupResolvedPackageUris appear to treat the URI as if it is two (split on the comma) and returns two nulls in the results. This means all of the subsequent results are shifted off-by-one (for each comma), and the length of the results do not match the length of the input.

@bkonyi FYI. I don't know how this could happen if the JSON is deserialized as JSON, but maybe you have some ideas what might be happening here?

Possibly the issue is in ParseJsonArray here, which just assumes commas are separators and doesn't take into account quoted strings?
https://github.com/dart-lang/sdk/blob/463c7cb5a2fdedf1022e3e71db9b79aa5bc8849e/runtime/vm/service.cc#L3605-L3618

/cc @bkonyi @derekxu16 @rmacnak-google

So there's a couple of issues here. As @DanTup pointed out, ParseJSONArray isn't equipped to handle , or ] characters if they're part of a string in the list. This isn't difficult to fix assuming the VM service is sending JSON arrays of strings with actual string formatted elements (e.g., ["foo", "bar"]).
Unfortunately, the VM service uses toString() to convert each element of JSON maps, and List<String>.toString() doesn't actually wrap the individual elements with quotes. This means that, <String>['foo,dart', 'bar.dart'].toString() gives '[foo,dart, bar.dart]', which would be passed directly to the service's C++ code.

I think this issue is the cause of https://github.com/flutter/flutter/issues/137163 which is the top Flutter crash on stable/3.16.4.
I'm going to improve the error (we shouldn't try to complete a completer twice) and see if I can work around it, but with a workaround it's likely going to leave something not working correctly, because we won't have the mapping for some files.

CC: @DanTup
flutter doctor
[✓] Flutter (Channel stable, 3.19.6, on macOS 14.4.1 23E224 darwin-arm64, locale en-RW)
    • Flutter version 3.19.6 on channel stable at /Users/knowbee/fvm/versions/3.19.6
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 54e66469a9 (14 hours ago), 2024-04-17 13:08:03 -0700
    • Engine revision c4cd48e186
    • Dart version 3.3.4
    • DevTools version 2.31.1

@knowbee do any your filenames happen to contain a comma? If so, then removing the comma will resolve the issue until this issue is resolved.

@DanTup There are no commas in any of my files. What's intriguing is that the app runs OK using the Flutter CLI but fails to run when using the Vscode debugger tool thus throwing the above error.

@knowbee

What's intriguing is that the app runs OK using the Flutter CLI but fails to run when using the Vscode debugger tool thus throwing the above error.

That makes sense, because the CLI doesn't use this API. It's used by VS Code to map package: URIs back to file paths on your disk, so when the debugger stops in package:foo/foo.dart we can tell VS Code which file to open on disk.

There are no commas in any of my files.

In that case, would you mind capturing a log so we can review the API calls?

Temporarily add the setting "dart.maxLogLineLength": 99999999, to your VS Code user/workspace settings (to reduce the chance of lines being truncated)
Run the Dart: Capture Debugging Logs command from the VS Code command palette
Run your app
Trigger the exception
Click cancel on the logging notification to stop logging and open the log

Extract any lines that contain lookupresolved or urilist (case insensitively) and share them here. Please review there's nothing sensitive in them before sharing (they should only contain file and package names/paths). If you need to edit anything out, please try to avoid modifying too much (replacing words is fine, but try not to modify anything that might be triggering this bug, such as non-alphanumerics that maybe are also affecting the json parsing).
Thanks!

@DanTup Here's the file; I only extracted lines containing lookupresolved or urilist and saved them to a separate txt file.
Dart-Code-Log-2024-03-06 12-24-28.txt

@DanTup Here's the file; I only extracted lines containing lookupresolved or urilist and saved them to a separate txt file.
Dart-Code-Log-2024-03-06 12-24-28.txt

@knowbee looks like you have a comma in this file here:

widgets/common/modals/bk_welcome_disclaimer_,modal.dart

So if you rename that file, it should avoid the bug :-)

@DanTup Thank you so much, It's now Fixed 😄

Thank you so much for this fix. For anyone else who is not that technical and is facing the same issue, all you need to do is:

Click on any of the folders or files in V.S. Code(for me all the folders appear on the right).
Then press F3.
Just search for a ",".
Change the file name and also do not forget to change the name in all the other files you might have called it in.
Have fun building!

me funciono lo de la coma muchas gracias, pero ahora no me da imagen corre pero se queda en blanco ;c


pad Initial packets from the server

We were previously only padding Initial packets from the client, but
it's useful (albeit not required) to also pad server Initial packets to
make sure the path supports packets of at least 1200 bytes as soon as
possible.

tests::limit_handshake_data is failing

Yeah, that test is a bit weird, need to figure out what's going on with it.

As far as I know PMUTD is done on the send path independently by both endpoints, so this is a simpler version of that.
But anyway the original idea was that not receiving an Initial packet in the first place is probably better than receiving one and then having to wait for the Handshake packets that might not arrive because they are too large. This way the client would be able to timeout sooner if the path doesn't allow the connection.
But thinking about this some more, this is probably more hassle than it's worth, so I'll just close it. We can think about this more later on.


add youtube shorts blocking on mobile

Closes #29

Thanks for pull request. I need to make some changes to something else and then I'll build it on publish


Add API for smooth scrolling

Set smoothScrollX or smoothScrollY to true on DataEditor to have smooth scrolling on the respective axis(es).
Under the hood this has the following effects:

Setting smoothScrollX or smoothScrollY to true on GridScroller, which causes
onVisibleRegionChanged to fire with more granularity, passing
tx and/or ty arguments as appropriate.

Those are passed into translateX and translateY props on the data grid
to specify a pixel translation on top of the cellXOffset/cellYOffset

If you don't do the above, it should work exactly as before, with the minor difference that scrollLeft is now clamped to be >= 0 in ScrollRegion update callback.

@jassmith I think this puppy is ready for a look.

Bottom line still goes AWOL when scrolling down, make sure you test on a non-retina device.

@jassmith  Good catch! Tested on Windows and fixed that and another issue as well.


Removed STAFF constant, added footer to paginated embed

Removed the STAFF constant within the cog in favor of the STAFF_ROLES constant present in bot.constants.
Added a footer to the paginated embed that points to the Rules page of the site, as the default embed does.
Very slight refactoring: moved the set_footer line to the default embed instead of having it set before-hand every time.

The STAFF_ROLE constant update is already in Hemlock's PR: https://github.com/python-discord/bot/pull/314

After some discussion, we decided to change this from a url in the footer to a link in the header. Changes were committed straight to the fork.


Fix setup-envtest.sh for vendoring repos

How to categorize this PR?

/area dev-productivity
/kind bug
/priority normal
What this PR does / why we need it:
Repos that vendor gardener and use the vendored hack scripts for test execution (e.g. our extensions) will fetch the kubebuilder tools to $REPO_ROOT/vendor/github.com/gardener/gardener/bin on make test.
As this dir is most likely not ignored, this PR changes setup-envtest.sh to use $REPO_ROOT/bin (works for g/g and vendoring repos).
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

NONE

cc @dkistner

Cherry-picked to release-v1.11


Allow users to click on predefined time periods to switch report in dashboard

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1686
Originally created by @bencodezen on 2020-02-08 13:12:14

Related to https://gitlab.com/meltano/meltano/issues/1631
In order for a user to change the time period, they need to open the Analyze tool to change the column. We want them to be able to do this directly from the dashboard section (particularly default reports).
MVP: Rather than make the dropdown a dynamic query, we create multiple reports in advance and the dropdown is simply a toggle for which report is being viewed.

View 5 previous comments from the original issue on GitLab


CHM Parser Improvement

This pull request to improve Tika CHM Parser.

hey @thaichat04 did we ever merge this?

Yes, I did merge to master before release 1.7

Thanks @thaichat04


There is an error info bar when opening one OAuth attached file share which already has the correct rbac role

Storage Explorer Version: 1.34.0-dev (98)
Build Number: 20240315.2
Branch: main
Platform/OS: Windows 10/Linux Ubuntu 22.04/MacOS Sonoma 14.4(Apple M1 Pro)
Architecture: x64/x64/x64
How Found: From running test cases
Regression From: Not a regression
Steps to Reproduce

Open Settings -> Check 'Enable Files OAuth Support'.
Select one storage account whose region is 'eastus2euap' -> Assign RBAC role 'Storage File Data Privileged Contributor' to one azure account against the storage account.
Expand the storage account -> File Shares.
Select one file share -> Copy the URL.
Open connect dialog -> Select 'File share' -> Select 'Sign in using OAuth'.
Select the azure account -> Next -> Paste the URL -> Connect the file share.
Check whether there is no error info bar.

Expected Experience
There is no error info bar.
Actual Experience
There is an error info bar.

 RequestId:b473a782-b01a-0020-06a6-76bda7000000 Time:2024-03-15T07:02:01.4627136Z

@v-xianya can you try to repro this, but make sure at least 5min have passed after being assinged the role 'Storage File Data Privileged Contributor'?

@v-xianya can you share with me the subscription and name of the storage account you reproduce this in, and the name of the share in that account as well.

Hi @MRayermannMSFT I shared the information on teams.

@v-xianya I understand the issue now. The problem is that we are unable to list the file share's snapshots. We are trying to do this so we can populate the snapshots drownpdown. For now, we're going to won't fix this issue. We'll wait to see if any users run into this in real life, once file share OAuth support ships.


Handling crashes in PSO

I am trying to implement a PSO for a model. Sometimes, depending on the combination of input parameters, the model crashes and returns None. How should I handle this case with pymoo? Maybe postprocessing the _evaluate function to give a default value to those cases that crashed?

Yes, I would sorround the third-party code with a try-catch and then set the objective to a large value (or introduce a inequality constraint to be 1 if failed and 0 if it succeeded. both will work)


[WIP] feat: add whitespace character class

Summary
This PR implements whitespace character class.
Test plan
Passings tests

I was thinking how this api should look like, and although this looks good I think it's not the best DX experience.
If someone has zero knowledge about Regex having one for example enum with Characters would be better. As user could leverage autocomplete Character.whitespace or Character.digit WDYT?

@okwasniewski I think that common namespace enum for character classes is not enough, as user will struggle with all other component imports (oneOrMore, buildRegex, range, etc). One way to solve it would be recommend prefixed imports:
import * as re from "ts-regex-builder";

const regex = re.buildRegex(
  re.oneOrMore(
    re.whitespace)
  )
)

So far this is the most autocompletion friendly thing I have figured out. @okwasniewski, @jaworek maybe you have some alternative ideas how could we improve autocompletion, API discovery, import management.

I've rebased on main and did some type tweaks. Pls do reverse review @jaworek

I've rebased on main and did some type tweaks. Pls do reverse review @jaworek

Thanks! LGTM 🚀