Auto add builtin provider to Generic based on passed locale

Feature request
An idea is very simple:
generic = Generic('ru', auto_add_builtin=True)
generic.russia_provider.inn()

Instead of this:
from mimesis import Generic
from mimesis.builtins import RussiaSpecProvider

generic = Generic('ru')
generic.add_provider(RussiaSpecProvider)
generic.russia_provider.inn()

Optionally we can make builtin's name customizable:
generic = Generic('ru', auto_add_builtin=True, builtin_custom_name='russia')
generic.russia.inn()

@ceccoemi @sobolevn What do you, guys, think?

I do not see any problems with this three lines of code.
What problem are you trying to solve?

@sobolevn I'm trying to make it easier to add country-specific data to Generic. For example, in common cases when you need to generate Personal info for locale ru, you will exactly need some data from RussiaSpecProvider, such as inn, patronymic and etc.

@lk-geimfari I think that is a good idea.
What do you think about adding the builtin provider by default? The generic provider generates all the data from a locale so I think that is reasonable to add the builtin too:
g = Generic('ru')
g.russia_provider.inn()

It's ok to add the parameter builtin_custom_name if you think that it will not add unnecessary complexity.
I could work on this next week. Let me know!


Clarify which docs people should look at

The README should clearly point people to the docs at angular.io/dart.
Also, we should clarify everywhere people might end up when looking for these docs. E.g., when you go to https://pub.dartlang.org/packages/angular2, you see the following links:

(everything from the README)
Homepage: github.com/dart-lang/angular2
we can change this in angular2's pubspec with the homepage field
Documentation: www.dartdocs.org/documentation/angular2/2.0.0-beta.21/ (which, fortunately, now points to https://angular.io/docs/dart/latest/api/, but that itself could have a more helpful intro)
we can change this in angular2's pubspec by adding a documentation: field

I'm creating an internal CL for the pubspec.yaml changes.

CL submitted. Not sure when it'll be reflected in this repo.


Date field cannot be exited using tab

Issue:
When clicking into a date field the date picker popup is not closed automatically when using the tabulator key. The user has to click into the next field which slows down the input process.
Wanted solution:
The form should be navigable using the keyboard only.

The solution could be quite hard to implement, actually. I did some digging in the AntDV source code and it seems that one cannot simply handle keypress events or similar on the DatePicker component, since the corresponding events are processed internally and won't be emitted for external listeners. At least with the Vue way of life. I could imagine that good old addEventListener on the input DOM node might work though.


Calling anno.getSelected() after anno.cancelSelected() returns a selection

Select an annotation with anno.selectAnnotation()
Cancel it with anno.cancelSelected()
Calling anno.getSelected() returns the previous selection, undefined or null was expected.

Same behaviour in 2.5.2 and 2.5.5.

Yikes - this is actually a combination of a bug and a design feature... Thanks for reporting!
I'll fix the bug with the next release. After the fix, this will work:
// 1. select annotation
anno.selectAnnotation('...');

// 2. Cancel & wait for async operation to complete
await anno.cancelSelected();

// 3. Prints undefined
console.log(anno.getSelected());

Note that cancelSelected is an async operation. Therefore, you need to use await if you want to use getSelected immediately after cancelSelected.


Normalize Audio Volume for Consistent Playback

I find myself readjusting the volume over and over again during the playing session, normalizing the audio levels can prevent that.

Is your feature request related to a problem? Please describe.
During playback sessions, users often need to readjust the volume multiple times due to inconsistent audio levels. This can be distracting and reduces the efficiency of the task.
Describe the solution you'd like
Implement audio normalization to ensure consistent volume levels throughout the playback session. This will eliminate the need for users to constantly adjust the volume, providing a smoother and more efficient experience.
Describe alternatives you've considered
An alternative solution could be to provide a manual volume normalization option that users can enable or disable as needed. Another option could be implementing an automatic gain control (AGC) feature to adjust the volume dynamically during playback.
Additional context
Implementing audio normalization will require updates to the audio processing pipeline or changes in the loading audio part of the app. This enhancement aims to improve the user experience by providing consistent audio levels, reducing the need for manual volume adjustments.


HLSL sm4 ALM reference for round_ni incorrectly refers to round_ne

Link to article:
https://docs.microsoft.com/en-us/windows/win32/direct3dhlsl/round-ni--sm4---asm-
Problem:
In the Remarks section the article states:
"round_ne rounds toward -infinity, commonly known as floor()."
Should refer to round_ni instead of round_ne (the latter rounds towards nearest even).

@GrantMeStrength Can you please take a look at this issue?

Thanks, fixed!


Change config file and log file locations.

Fixes #6
Config location is now AppDirs.config_dir and logs are stored to UserDirs.document_dir. Refer to platform-dirs for exact folders on different OSes.
Should database file be stored in AppDirs.data_dir?
Personally I don't like storing files in the current directory, especially when it's just a single file, but I will leave it up to your judgement.

Also changed some Strings to PathBufs to fit the use cases.
And replaced #[cfg(target_os = "linux")] with #[cfg(unix)] and similarly for Windows.

Except clippy errors and minor mistakes everything looks super!

Should database file be stored in AppDirs.data_dir?
Yeah sure.

For backwards compatibility, on start, we should probably first look if we have a database in the current directory and if we do and data_dir contains no database we should move the database to data_dir and also notify the user about this (log this event).
If there is a database in the current directory and in the data_dir we should log a warning saying that the database in the current location is ignored and show the path to the used database.

Also , I think it would be good to log database path when starting the database_manager.

Also, in the readme, edit the How to Install section's last paragraph and add information about database location.

For backwards compatibility, on start, we should probably first look if we have a database in the current directory and if we do and data_dir contains no database we should move the database to data_dir

I wonder if backwards compatibility is something we should care about at this point. I don't think there are many servers running at this moment :sweat_smile:. So to me it seems not worth it to add code for backwards compatibility. A migration guide in the release notes should be enough.

I wonder if backwards compatibility is something we should care about at this point.

Sounds reasonable, we will add a migration guide instead of backwards compatibility. I will write this down so I won't forget that.

So log directory name and 2 other important things left:

log database path when starting the database_manager.
in the readme, edit the How to Install section's last paragraph and add information about database location (on both Windows and Unix).

Updated the code

Also, you seem to not use the formatter (cargo fmt), shared/src/misc/db_manager.rs is not formatted properly. You should make sure you have it enabled. In the meantime I will try to add to to the CI.

Please merge new commits from the master branch into your branch.

Also, you seem to not use the formatter

I actually have pre-commit and pre-push hooks to check fmt and clippy, but I omitted shared/ directory, oops

Everything seems to be working good. @LoipesMas thanks for you help on this project! ❤

Glad I could help!


Decide on whether we should never modify objects in-place

Should we decide that things like this should never touch the object data but rather return new data?
new_citymodel = citymodel.clean()

Suggestion: Make sure nothing modified in-place and if we later want to optimize, then add something like numpy argument out = object for certain functions.


if link includes # - link is cutting

Steps to reproduce

https://prnt.sc/sd337a
2.https://prnt.sc/sd33g1

Description
When I share link to facebook or twitter, my link is cutting off after number sign(#) symbol, please help anyone!
Environment
"react-native": "0.61.5",
ios 13.2.2
react-native-share
"react-native-share": "^3.3.2",
Link to repo (highly encouraged)
https://github.com/Vitalik7

Hi @Vitalik7, this is happening only on Twitter and Facebook? Also, are you using the Share.open or Share.single?

Hi @MateusAndrade this specific case, when app installed for example twitter and we share link with number sign symbol then is open modal window and link is ok, but if app not installed we redirect to browser and then link is cutting.
I am using Share.single

does it only happens on iOS?

@jgcmarins I don't know what with android, because we supported only ios


Upgrade NullAway 0.11.1 -> 0.11.2

This PR contains the following updates:

Package
Type
Update
Change

NullAway

patch
0.11.1 -> 0.11.2

NullAway
compile
patch
0.11.1 -> 0.11.2

Release Notes

uber/NullAway (NullAway)
v0.11.2
Compare Source

JSpecify: add another bailout check for raw types (#1021)
JSpecify: handle intersection type in one place (#1015)
JSpecify: fix for crash with wildcard types (#1020)
Maintenance:

Update to Error Prone 2.30.0 (#1017)
Add test for #1011 (#1018)

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

Suggested commit message:
Upgrade NullAway 0.11.1 -> 0.11.2

See:
- https://github.com/uber/NullAway/blob/master/CHANGELOG.md
- https://github.com/uber/NullAway/releases/tag/v0.11.2
- https://github.com/uber/NullAway/compare/v0.11.1...v0.11.2


Locale (or other customized field) should be shown in results

We have tests which are executed on different locales and it is required to show such results in test runs. Or show any customized field.

relates to https://github.com/qaprosoft/zafira/issues/328

Closed as duplicate.


Unique Proxy Validation Failures

User story.
As a QA, I'd like there to be a way of grouping similar validation problems together so that I can track discrepencies in a ticketing system.
Is your feature request related to a problem?
I love the visibility that I get from prism, but it's hard to objectively know how many validation errors occur with each API endpoint.  It'd be great for a prism session to be able to group similar validation errors (though I appreciate this is hard) - even if it was just at the particular endpoint level.
Describe the solution you'd like
A way of specifying the dimension(s) of how errors should be tracked; so that they can be ingested and loaded into a ticketing system (such as JIRA).

@andylockran this is an interesting feature request. We don't think this feature belongs in Prism itself, but could be a good feature for our hosted Prism solution in our Stoplight Platform. I'm going to close this ticket, but @ryotrellim will follow up with a link follow for tracking this feature request for Stoplight Platform.

@andylockran I've created a new roadmap item to collect insights like these. Can I ask you to submit this idea and any details or suggestions directly to https://roadmap.stoplight.io/c/168-reporting-analytics-and-metrics ?
Thanks!


reST Primer duplicates the Sphinx version; should link to it instead

Similar to PEP 12, the reST primer in the devguide duplicates the same information in the Sphinx reST primer, along with some bits specific to its particular context.
In fact, unlike PEP 12, they are mostly word for word identical and thus clearly derive from a common source, with the Sphinx version being close to a strict superset of the CPython version, containing some additional and updated sections but also still mentioning many CPython-specific conventions (e.g. section heading format).
This near-duplication is clearly not very DRY, and has several main problems:

Additions, improvements and updates/changes to one are not reflected in the other. Clearly, the more appropriate place for this is the Sphinx docs as it is generally applicable to all Sphinx users, and indeed they seem to have been kept much more up to date there, and it also links the full reST reference for each section for readers looking for more information.
Readers already familiar with reST or just looking for the CPython-specific bits must either dig through each section, or may skip it entirely and miss them

Therefore, I propose for the Devguide reST primer:

Recommending and linking the Sphinx reST primer at the top of the Devguide reST primer section
Linking each top-level devguide reST primer section to the corresponding Sphinx section via Intersphinx
Eliminating all but the CPython-specific guidance/convention/recommendations in each section

There are also some non-specific bits that could be trimmed from the Additional Markup Constructs section, and each role/directive should be linked to its canonical full Sphinx documentation if present, but that can be addressed separately on a case by case basis.
If we agree this is desirable, I'm willing to take this on, unless @ezio-melotti would prefer to do it.
Somewhat related: python/devguide#916

This was brought up again at the December docs community meeting, where this seems to be a reasonable step to move forward with. @Mariatta @encukou or anyone (it will have to be one of the few people with write permission on this repo), could you transfer this issue to the devguide repository, as it is more appropriate there? Thanks!


build: enable skipLibCheck for tsc

🏆 Enhancements
🏠 Internal
From TypeScript handbook:
--skipLibCheck       Skip type checking of all declaration files (*.d.ts).

This cuts build-time for tsc in half. Most TS errors can still be captured by ESLint.
Also limit typeRoots to ./node_modules in the root folder so to reduce chances of type conflicts from packages/* and plugins/*.

Swapping the boolean for the cache cleaning sounds like a good way to speed things up, but are you sure swapping that default doesn't have any potentially negative impacts?

It won't break CI and published packages at least. For local developers, things may break if they cleaned up d.ts files without removing .tsbuildinfo. But they can also run yarn clean manually and start fresh again.


Evaluation Metric

Hello,
I want to ask about something related to the quantitative results in the paper (http://www.ipb.uni-bonn.de/wp-content/papercite-data/pdf/chen2019iros.pdf).
How are the numbers in [TABLE I: Results on KITTI Road dataset] calculated? I can see there is a devkit available at KITTI website (http://www.cvlibs.net/datasets/kitti/eval_odometry.php). However, this devkit generates a file for each kitti sequence containing error values for subsequences of different lengths. So, is the overall error for a sequence just the simple average of these values in the error file?

Hey @MohamedAfifii,
Thanks for following our work.
As far as I know, the final results are the average of all the subsequences, which you could find more detailed information in the official evaluation code: https://s3.eu-central-1.amazonaws.com/avg-kitti/devkit_odometry.zip.
Note that, for kitti road dataset, we use the old lengths which are = {5,10,50,100,150,200,250,300,350,400}, since some of the road sequences are less than 800 frames.
I hope my answer helps!

Hey @MohamedAfifii,
Thanks for following our work.
As far as I know, the final results are the average of all the subsequences, which you could find more detailed information in the official evaluation code: https://s3.eu-central-1.amazonaws.com/avg-kitti/devkit_odometry.zip.
Note that, for kitti road dataset, we use the old lengths which are = {5,10,50,100,150,200,250,300,350,400}, since some of the road sequences are less than 800 frames.
I hope my answer helps!

Thanks for your reply.
So is the overall total error the micro average (average of individual subsequence errors) or the macro average (average of sequence errors)?

Thanks for your reply.
So is the overall total error the micro average (average of individual subsequence errors) or the macro average (average of sequence errors)?

Thanks for your reply.
So is the overall total error the micro average (average of individual subsequence errors) or the macro average (average of sequence errors)?

For the KITTI odometry benchmark, we will in the end get only one evaluation result, which is the average over all sequences and subsequences.
For more information about the KITTI odometry benchmark, we refer to the original website: http://www.cvlibs.net/datasets/kitti/eval_odometry.php
Since the benchmark is not a part of this work, I would like to close this issue.
Please feel free to drop me messages if there is any other question about SuMa++.

Thanks for your reply.
So is the overall total error the micro average (average of individual subsequence errors) or the macro average (average of sequence errors)?

For the KITTI odometry benchmark, we will in the end get only one evaluation result, which is the average over all sequences and subsequences.
For more information about the KITTI odometry benchmark, we refer to the original website: http://www.cvlibs.net/datasets/kitti/eval_odometry.php
Since the benchmark is not a part of this work, I would like to close this issue.
Please feel free to drop me messages if there is any other question about SuMa++.


Investigate and smooth out load spikes on prod worker nodes

Lead: @murali-shris
Describe the bug
There are periodic large load spikes which correspond with scheduled jobs (compaction, scans, ...) which are straining our worker nodes
Expected outcome

Shared documented understanding of which scheduled jobs are driving load
Adjusted jobs schedules to spread load ~evenly over time

@cconstab @cpswan Can you please grant me access to the required monitoring dashboards to help me investigate this issue

Two possible causes of CPU spike

sec check which runs every 15 mins. created inbound connection to secondary and runs scan
hive expiry check which is a scheduled job on server which runs every 10 mins.This scans every key in hive and checks for expiry

merged PR to randomise hive expiry check
https://github.com/atsign-foundation/at_server/pull/497

Moving the task to next sprint (PR-30) to validate the performance once the changes are deployed.

@cconstab @cpswan Is this issue still occurring in prod? any work to be done in the upcoming sprint related to load spikes?

Will take a look or @cpswan

@murali-shris things are a lot better, but I'm still seeing some hourly spikes, so maybe another scheduled job elsewhere in the secondary?

@murali-shris @cpswan should we move priority up to high for PR43 sprint planning?

@murali-shris @cpswan should we move priority up to high for PR43 sprint planning?

yes @ksanty ..we can revisit whether prod spike still exists


What does the "Status" filter mean - Can we do something more useful with it

Expected outcome

What does the "Status" filter mean. What is the differnece between Status and Current step?
Can we make the Status be "Not inidiated", "in Progress" "Hold" and "Issue"?

Lets discuss this rather than doing anything. I am unsure what this means at the moment
Business Value / Developer Experience

Acceptance Criteria

[ ] when selecting
[ ] items which covers
[ ] the expected outcome

this has now been explained to Edward :)


Error when downloading Shapefiles

Got the attached error message when unzipping downloading shapefile:
"Either no instances were identified for export or no resources have exportable geometry nodes                Please confirm that the models of instances you would like to export have geometry nodes and that                those nodes are set as exportable"
This happens for multiple sites (Emily Carr House, Nanaimo Court House, etc.)

[ ] Resolve ability to download shapefiles

@emjohnst - I think you need to show me what you're doing. I just created a shapefile without issue..

@bferguso Hi Brett it's working today now, we just tested it. It was not working for Katie or I yesterday and we tried several different sites. Very weird. I'll close this issue.


fix: replace hard coded server config in import script.

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

Project coverage is 100.00%. Comparing base (020f495) to head (c224f7f).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##              main        #3   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            8         8
  Lines          988       988
  Branches       103       103
=========================================
  Hits           988       988

Flag
Coverage Δ

unittests
100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Update tracking-loss-in-unity.md

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/tracking-loss-in-unity.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Wrong content section in the sidebar

Describe the bug
context
I open https://sphinx-book-theme.readthedocs.io/en/stable/tutorials/get-started.html#add-a-source-repository-button-to-your-theme or press "Add a source repository button to your theme" content button on https://sphinx-book-theme.readthedocs.io/en/stable/tutorials/get-started.html.
expectation
I expected content section on the right panel to change to "Add a source repository button to your theme".
bug
But instead it tells me that the previous section is active.
If I scroll down a little bit, then the section is correct.

Reproduce the bug

Go to https://sphinx-book-theme.readthedocs.io/en/stable/tutorials/get-started.html#add-a-source-repository-button-to-your-theme

List your environment
OS: macOS 12.3
Browser: Safari 15.4

I am noticing this too with v0.3.2. Have you found any way to resolve this @mathbunnyru?

No, I haven’t. But I didn’t actually try to find it, because web is definitely not my area of expertise.

It seems that the active class tag is being added to the wrong <li> entry in the right side menu (the entry above the actually active one).
Was this present in any of the previous versions? I just started using this theme.

Clicking on one of the entries in the menu positions you exactly 12 pixels above the chosen section.

Currently,  data-offset parameter of the Bootstrap Scrollspy is set to "60" in the body tag of each HTML file. By changing this to "73" it works as expected, but there is some jittering. The optimal value seems to be "80".

I just started using this theme.

Me as well, we've only started using it quite recently and the old versions don't work well for us for another reason.
@haklc could you make a PR changing this value of Bootstrap Scrollspy?
@choldgraf may I ask you to take a look here?

This is now fixed upstream, we just need to wait for a release then update here.

Great, thank you!

When is the next release expected? I'd love to use this theme but I cannot manually fix this value after HTML files are generated on Read the Docs.

There's a release candidate for the upstream theme out now (https://github.com/pydata/pydata-sphinx-theme/releases/tag/v0.9.0rc1) and then it's a question of doing the necessary changes to make this theme support it. No promises on timeline though.

The upstream new version has been released 🎉
https://github.com/pydata/pydata-sphinx-theme/releases/tag/v0.9.0

Any news as to when a newer version of pydata-sphinx-theme will be integrated into sphinx-book-theme?

Yep this will be closed by the following PR and we'll get a release candidate out soon after that:

https://github.com/executablebooks/sphinx-book-theme/pull/640

I think this works much better now, but subtopic links are a bit broken.
https://jupyter-docker-stacks--1855.org.readthedocs.build/en/1855/#jupyter-notebook-deprecation-notice
When I visit this page, it doesn't show Jupyter Notebook Deprecation Notice subtopic (and I think it should).

I've used just released rc version: https://github.com/jupyter/docker-stacks/pull/1855

good catch - fixing it in:

#669


failing to commit into a db

Failing to create dx into a DB
both in clojure and in shadow-cljs
Version: https://github.com/ribelo/doxa/commit/956a3244ea15bedf69f18cc74385b7c2bec5635a
Steps:
(def data [{:db/id 1 :name "Petr" :aka ["Devil"]}])
(def db (dx/create-dx data))
; {}

(type db)
;  clojure.lang.PersistentArrayMap

Gives no error.
Project – https://github.com/spacegangster/rf-doxa-etude
Comment
I've set up doxa as a git submodule.
I'm open to consider it's something wrong with my setup.
I'm ready to jump on a call if needed, I think that would be faster for both of us.
If that fits you – pick a time here https://calendly.com/ivan-de-lightpad/30min

My social anxiety is heightened when I have to speak English. I will be happy to write to you, but I can only speak to the wall or to my dog ;)

Recently when fixing a bug I didn't include the tests because the change was small, but the bug ate the parenthesis and it came out as it did

Nice one mate! All fixed 🥳🥳🥳

I can make you a PR with the github script that will run the tests automatically, if you want.

Yes, please.


pip install error

Hello,
I have an error when pip installing the parametric-plasma-source (attached output). I have a fresh install of Linux and have followed the OpenMC workshop instructions for OpenMC/DAGMC, below. I am obviously reluctant to start playing about with modules in-case I break the OpenMC/DAGMC install.
https://github.com/ukaea/openmc_workshop/blob/test_conda_install_script/install_scripts/install_conda_cadquery_openmc_dagmc_trelis_plugin.sh
Could you advice on fixing the Pip install?
Thanks,
Sam

Thanks for reporting, I'm not sure if the output got attached to that last message, but it could be helpful for solving this
While we look into this problem I wonder if this works for you
git clone https://github.com/open-radiation-sources/parametric-plasma-source.git
cd parametric-plasma-source
pip install .

I noticed the main branch was a bit out of date with develop so have made a PR #5

Please see the error below, sorry for not attaching correctly previously:
plasma_source_error.txt

Looks like the pip upload doesn't contain everything
extract from the error file
"/tmp/pip-install-4v9d7vdy/parametric-plasma-source" does not appear to contain CMakeLists.txt.

Cloning the directory as you suggested installs correctly, thanks.

Could be that we need to add cmake as an install dependency. A better solution would be to put cmake into the requirements.txt but use the manylinux build to generate a wheel that doesn't need to be compiled on the user's machine.

Looks like that merging worked @DanShort12
https://github.com/open-radiation-sources/parametric-plasma-source/actions/runs/345529430

Therefore I suggest we merge from development to main and that should update the main pypi package

Yep, sounds good to me. That should hopefully fix this error.

Looks like the merge to main didn't quite update the pypi package :-(
https://pypi.org/project/parametric-plasma-source/#history

The creation of a github release triggered the github action which updated the pypi release and solved this problem. Feel free to reopen if this reoccurs. Closing for now


MvcCoreLoggerExtensions - Information Leakage Security Vulnerability

Describe the bug
Information leakage found in MVCCoreLoggerExtensions.cs facility.
On line 195 of MvcCoreLoggerExtensions.cs
The action method arguments are logged. MVC applications may contain authentication screens where user sensitive credentials can be obtained from these log files.
To Reproduce
Set up logging in an MVC app, develop a login screen, configure logging at INFO-level and watch the logs spit out user credentials.
Expected behavior
User credentials should never be logged. In fact, any unpredictable data (that is user input) should be left to the implementor to decide if it should be logged. I would think the correct approach is to not log the arguments at all and leave that up to the MVC developer to choose carefully and control that logging on their own.

Interesting. As Information isn't the default loglevel you wouldn't get this logged by default, but when you do tweak the logging level yes, this is a potential problem if you haven't secured your logs like best practice would dictate.
So I'm not classifying this as a security patch Tuesday type bug, but rather something that will be fixed in the next scheduled releases for 2.x and above. The change will be that rather than the argument name/value pair being logged you'll only see the argument names. Tracing will instead log the full name/value pair.

@mkArtakMSFT Can you assign this to someone please?

@blowdart  - thanks for the eyes on this. much appreciated.

For future reference, security issues should first go to<EMAIL_ADDRESS>where they can qualify for our bug bounty. Github issues can't qualify.

Thanks @blowdart.
@pranavkm lets get this fixed for 2.1, 2.2 as well as the upcoming releases.

Why is the fix for this to completely remove the logging of the arguments? Wouldn’t it make more sense to just reduce the log level on the arguments as the log level documentation would suggest? On Debug or even Trace, this shouldn’t be a problem at all.
In the past, being able to access the action arguments using a more specialized logging level did help a lot when debugging problems. So I would really miss this in the future, and removing this completely will likely end up with people adding new action filters that log out all the stuff again.
I do not really understand OP’s issue where a “login/authentication screen” would show log output though.

@poke - hope this helps with understanding the applied case...
The crux of the issue is argument logging, which happens on every MVC controller action method in aspnetcore, when logging is configured at Information level or below. This means all payloads end up in your log files. Think about when your app would have this controller / method:
class AccountController {
[Post]
Login(string username, string password){ }
...
}
Every time someone logs in to your app, you now have their plain text UN and PW sitting in your log file (unless your logging is configured at Error level or higher).
At first glance, leaving payload logging on at the Debug level seems appropriate as most people don’t typically deploy logging configuration at debug levels.
But even then, MSFT is still putting themselves at risk of data leakage just so developers can find an easier way to debug argument values sent to a controller action method.
What didn’t seem appropriate was the blind logging of every payload captured by any MVC controller action when the log level is set to information. Information level, according to the doc is supposed to help with general flow of the app. Payloads, specifically credentials, don’t supply long term value, they don’t help with assessment of the user moving through the app; worse, they present a rapidly increasing dumpster fire of corporate security risk the more eyes that see them and the longer the information sits at rest.
In my humble opinion, the decision MSFT is making is based on security posture, not ease of use, and I think that’s right.
Also, as I read it, it sounds like they are leaving argument logging on at “Trace” level...which is congruent with how the doc describes this intention of this level, and encourages readers to heed warning as well.

@aaronlcope
Thanks for the details. Actually, consuming form input like that is rather rare. In practice, you would probably end up using a complex type that represents the passed values from the form. This allows you for example to do proper model validation (without making the action signature explode) and it also allows you to use tag helpers within your Razor view.
This solution is for example covered in this Stack Overflow question from 2017.
I personally do think that we should assume that the average developer is careful enough to configure the logging level correctly and that the the log files (if there are any; because by default there aren’t) are protected enough. Not assuming that means that we are crippling all other developers that are protective enough while appreciating the default logging behavior. And if we accept “they can easily add an action filter” as an argument, then we could as well just get rid most logging altogether, going back to classic ASP.NET where all this was a choice developers had to explicitly make (by adding stuff).
And with ideas like #3700 on the horizon, we simply cannot avoid logging something just because someone accidentally exposed some sensitive information.

Also, as I read it, it sounds like they are leaving argument logging on at “Trace” level...which is congruent with how the doc describes this intention of this level, and encourages readers to heed warning as well.

Unfortunately, the PR #9227 for this completely removes the arguments, and does not move it to a different log level.

2.1: https://github.com/aspnet/AspNetCore/commit/836964a653e355fe4e28241e0ff485dfb5d3ccdf
2.2: https://github.com/aspnet/AspNetCore/commit/836964a653e355fe4e28241e0ff485dfb5d3ccdf
3.0-preview5: https://github.com/aspnet/AspNetCore/commit/dfae19ee7c3ef84f7281031618ed80f6597c380d


Serverless v2 support

Add support for serverless v2
Update serverless provider to use version installed with project rather than one installed with deployer.

Sample jobs from frankenstack:
Serverless v2: https://console.aws.amazon.com/codesuite/codebuild/022393549274/projects/frankenstack-Deploy-Action-travis/build/frankenstack-Deploy-Action-travis%3A21d6c054-7248-4993-83de-f8841ec0d3d2/log?region=us-east-1
Serverless v1: https://console.aws.amazon.com/codesuite/codebuild/022393549274/projects/frankenstack-Deploy-Action-travis/build/frankenstack-Deploy-Action-travis%3Af5ae6e64-d19d-4f51-aecf-10fd4557a88b/?region=us-east-1

LGTM


Updated Assigning Procedure

Updated procedures to assign eDiscovery Managers and eDiscovery Administrators.  The updates are in line with the wording used in the UI.

@nenonix @JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks.


"mros2" branch is not the one corresponding to the Ver.0.4.0

First, I apologize for making a mistake updating the branch below to the original main (Can I revert forcefully?).
https://github.com/mROS-base/embeddedRTPS/tree/mros2_track-ertps-1410a87
The current mROS2 repository refers to a commit ID directly, not a branch, as below.
Agent-less: a node on mROS 2 autonomously discovers communication nodes on the host with the feature of embeddedRTPS. It means no agent/bridge is required for pub/sub communication from the embedded devices.
    mros2 currently uses embeddedRTPS @ 1410a87 as it is.

But, it is inconvenient to make some pull requests if there is no branch to be based.

Sorry again.
I created this issue on the wrong repository. So, I will close this one.
And, I've created the same issue on the correct one as below.
https://github.com/mROS-base/embeddedRTPS/issues/10


Docker Ubuntu Linux with External Ollama Server Not working

Describe the bug
The current repo isn't working with Docker, Ubuntu Linux 22.04, with an External Ollama server.
The following is how to reproduce it:
git clone https://github.com/coleam00/bolt.new-any-llm.git
cd bolt.new-any-llm
cp .env.example .env.local
nano .env.local
(edit the following line)
OLLAMA_API_BASE_URL=http://<IP_ADDRESS>:11434
(when i do a curl from the docker host machine to <IP_ADDRESS>:11434, I get 'ollama running'
docker build . --target bolt-ai-production
docker-compose --profile production up
The site will come up, but when I select Ollama in the drop down it doesn't have any of the models that I have installed populated.
I have also tried everything from switching the docker-compose.yaml line from RUNNING_IN_DOCKER=true to false.
Link to the Bolt URL that caused the error
http://<IP_ADDRESS>:5173/
Steps to reproduce
git clone https://github.com/coleam00/bolt.new-any-llm.git
cd bolt.new-any-llm
cp .env.example .env.local
nano .env.local
(edit the following line)
OLLAMA_API_BASE_URL=http://<IP_ADDRESS>:11434
(when i do a curl from the docker host machine to <IP_ADDRESS>:11434, I get 'ollama running'
docker build . --target bolt-ai-production
docker-compose --profile production up
Expected behavior
Should have a list of Ollama models that are displayed and that can be used
Screen Recording / Screenshot
No response
Platform

OS: [Ubuntu Linux, Docker, Ollama External on Windows]
Browser: [Chrome]

Additional context
No response

Same issue here, never been able to get ollama external server working in any installation method.
OS: [Ubuntu Linux with docker, Ollama on external linux server]
Browser: [Chrome, Brave, Edge]
I'm able to log into the container using docker exec -it bolt-bolt-ai-1 bash
Check the environment variable for ollama
printenv | grep OLLAMA_API_BASE_URL
the output shows it's set correctly
OLLAMA_API_BASE_URL=http://<IP_ADDRESS>:11434
yet, bringing the container up shows it's not set:

me to have the same issue

please try the latest version


add docker compose for testing

Signed-off-by: Peng Huo<EMAIL_ADDRESS>Description
add docker compose for testing.
customized spark image
The customized Spark image include opensearch-spark-30_2.12-3.0.0-SNAPSHOT.jar
docker build --pull --rm -f "spark/Dockerfile" -t maximus/spark:v3.2.1 "spark"
docker compose
docker compose includes

1 OpenSearch 2.3 node.
1 Spark master node.
2 Spark worker node.

How to use

launch spark-shell on master node.

./bin/spark-shell --master spark://spark-master:7077

execute

scala> import org.apache.spark.sql.SQLContext
import org.apache.spark.sql.SQLContext

scala> import org.apache.spark.sql.SQLContext._
import org.apache.spark.sql.SQLContext._

scala> import org.opensearch.spark.sql._
import org.opensearch.spark.sql._

scala> val sql = new SQLContext(sc)

scala> val accounts = sql.read.json("/root/maximus/data/accounts.json")

scala> val options = Map("pushdown" -> "true", "opensearch.nodes" -> "maximus-os")

scala> accounts.saveToOpenSearch("accounts", options)

Check List

[ ] New functionality includes testing.

[ ] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #1311 (b8524bd) into feature/spark-integration (45fc371) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@                     Coverage Diff                      @@
##             feature/spark-integration    #1311   +/-   ##
============================================================
  Coverage                        98.35%   98.35%
  Complexity                        3627     3627
============================================================
  Files                              343      343
  Lines                             8951     8951
  Branches                           578      578
============================================================
  Hits                              8804     8804
  Misses                             142      142
  Partials                             5        5

Flag
Coverage Δ

sql-engine
98.35% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


This fixes the weird angular stuff - we need to do this in every othe…

This might actually solve a TON of performance issue in notebooks as well if we make these changes there.
Specifically: https://github.com/microsoft/azuredatastudio/pull/10857/files#diff-1d9b614e6b182267f591bb2ee0acf3a3R103-R110
I added everyone else as reviewers as an FYI
Essentially without this code, everytime the checkbox that top checkbox of the column was clicked, it reconstructed all the other checkboxes.
So in the import extension, if we had 30 columns, that would be 60 checkbox objects each click - and it also didn't even visually show it right.
Extend this to any other component that has for loops and this completely blows up.

Or just don't use angular 🙃

If this PR solves your problem, resolve the conflicts and merge it in @aasimkhan30


chore(starknet_api): use const fn create for testing block info

This change is

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2561  👈 (View in Graphite)
#2446
#2445
#2444
#2443
main

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

No need for this PR.


Permute input parameters of main models to quantify sensitivity (alá Mirco) for the robustness section

sample random epsilon from a normal distribution that covers an appropriate range and permute input parameters with it. (One permuted input variable pr. test to establish causality). E.g.
dom_t -> dom_t + epsilon  where epsilon is sample from a normal distribution covering +-3ns
Save results in our current format and give to Rasmus

As agreed at today's meeting I'll just tag @mhaminh

@asogaard sorry - yes this is done.


⚠ Bofrost.de has degraded performance

In f33cd1c, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 912 ms

Resolved: Bofrost.de performance has improved in 8d98490 after 13 minutes.


MAISTRA-2437: Push configuration as String

Envoy doesn't handle well passing a Struct as the configuration field.
When an extension retrieves its value, it gets binary data.
Passing string instead is safe. Extensions will get the value as string
and can unmarshal it into a proper JSON struct.
While on it, also fixed a potential index out of range error.

/retest

/retest

Changing the base branch didn't work well. Will create another PR.


Incorrect use of doxygen special commands in documentation

Example:
@returns The @param number added with 2.

Maybe the docs should just be rewritten.


⚠ Fortnite has degraded performance

In 9d25ddc, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1627 ms

Resolved: Fortnite performance has improved in dc1a4e7.


Status check route

Fixes issue #25
@dkvc

@dkvc wow it's almost like I was paying zero attention, embarrassing. Got it straight, also didn't know that about logging, thanks for the feedback!

@dkvc wow it's almost like I was paying zero attention, embarrassing. Got it straight, also didn't know that about logging, thanks for the feedback!

No worries, thanks for pull request! LGTM! :rocket:


QUnit 2.0 IE8 support

Hey, I tried looking but didn't find a good definite answer about this. Does QUnit 2.0 drop IE8 support? We just tried updating to it on videojs and then noticed that the tests were failing.
It turned out the issue was an Object.defineProperty call that doesn't work on IE8.
Thanks.

There's a note about browser compatibility on qunitjs.com:

QUnit currently supports the same browsers as jQuery 3.x.

For legacy browser support, including Internet Explorer versions lower than IE9, please use the 1.x series of QUnit.

Oh, thanks. I was looking for something like that; I guess I totally missed it.


Can't build on Netlify because of React issues

Link to reproduction
No response
Payload Version
v3 beta
Node Version
18
Next.js Version
15 rc.0
Describe the Bug
I'm just trying to deploy the app after npx create-payload-app@beta and getting such error:

Locally build works if I use --force flag.
Reproduction Steps
Just try to deploy v3 demo app to Netlify
Adapters and Plugins
db-mongodb

The minimum Next.js version we support is canary.53 - cannot use rc.0 with the latest payload.
Once you upgrade that, you might still get peer dependency warnings from React 19. That's normal, I'd either pass --force / --legacy-peer-deps, or switch to pnpm which is faster, more stable and works out-of-the-box with payload. Nothing we can do about these warnings right now, will have to wait for React 19 stable, and for the other packages to upgrade their peer dependencies.
These warnings (other than the Next.js rc.0 one) can be safely ignored though

@AlessioGr I haven't installed next by myself. This version (rc.0) is a result of npx create-payload-app@beta which I run today.

@AlessioGr I haven't installed next by myself. This version (rc.0) is a result of npx create-payload-app@beta which I run today.

Thank you, fixed this in https://github.com/payloadcms/payload/pull/7283! New projects now install the correct next version, if you install them with npm install --legacy-peer-deps


Sign up form

[ ] Username
[ ] Email
[ ] Password
[ ] Validate Password
[ ] Sign up button
[ ] Log in button

handling on blurs for password and email and adding mutation call to login button and signup button.

Signup form was created using mui framework library.


Kysely, better error messages for faulty migration?

I have a migration file with a few hundred lines in it, and I am getting this error:
$ pnpm tsx scripts/migrate.ts
failed to execute migration "0006"
failed to migrate
error: syntax error at or near ","
    at <anonymous> (./my_project/node_modules/.pnpm/pg@8.11.3/node_modules/pg/lib/client.js:526:17)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at PostgresConnection.executeQuery (./my_project/node_modules/.pnpm/kysely@0.26.3/node_modules/kysely/dist/cjs/dialect/postgres/postgres-driver.js:72:28)
    at <anonymous> (./my_project/node_modules/.pnpm/kysely@0.26.3/node_modules/kysely/dist/cjs/query-executor/query-executor-base.js:37:28)
    at SingleConnectionProvider.#run (./my_project/node_modules/.pnpm/kysely@0.26.3/node_modules/kysely/dist/cjs/driver/single-connection-provider.js:27:16)
    at PostgresConnection.executeQuery (./my_project/node_modules/.pnpm/kysely@0.26.3/node_modules/kysely/dist/cjs/dialect/postgres/postgres-driver.js:91:69)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at <anonymous> (./my_project/node_modules/.pnpm/kysely@0.26.3/node_modules/kysely/dist/cjs/query-executor/query-executor-base.js:37:28)
    at SingleConnectionProvider.#run (./my_project/node_modules/.pnpm/kysely@0.26.3/node_modules/kysely/dist/cjs/driver/single-connection-provider.js:27:16) {
  length: 90,
  severity: 'ERROR',
  code: '42601',
  detail: undefined,
  hint: undefined,
  position: '55',
  internalPosition: undefined,
  internalQuery: undefined,
  where: undefined,
  schema: undefined,
  table: undefined,
  column: undefined,
  dataType: undefined,
  constraint: undefined,
  file: 'scan.l',
  line: '1188',
  routine: 'scanner_yyerror'
}

How can I better debug what is going on?
position: 55 doesn't seem to have anything to do with my migration file, nor does line: 1188, can I print something out which gives what postgres/kysely is reading internally perhaps somehow? Or how else can I figure out where the error is more easily? I've been resorting to commenting out lines of my migration to find the culprit, but then the partial migration succeeds, and I have to add another migration file with the rest of the first file, and repeat. Would be great to avoid that somehow.
Thanks for the help!
I've boiled the error down to this migration:
import { Kysely } from 'kysely'

export async function down(db: Kysely<any>): Promise<void> {}

export async function up(db: Kysely<any>): Promise<void> {
  await db.schema
    .alterTable('files')
    .renameColumn('kind', 'sort')
    .addColumn('note', 'text')
    .addColumn('hold__code__base', 'uuid', c =>
      c.references('seed_file_hold.code__base').notNull(),
    )
    .addColumn('link__form__name', 'text', c => c.notNull())
    .addColumn('link__code__base', 'uuid', c => c.notNull())
    .execute()
}

But can't seem to idenitfy where that , comma is, but that is kind of beside the point, would be nice to know how to more effectively debug this.
After fixing that finally (I guess can't mix alterTable renames with adds), I get another similar error:
$ pnpm tsx scripts/migrate.ts
failed to execute migration "0006"
failed to migrate
error: column "reference" does not exist
    at <anonymous> (./my_project/node_modules/.pnpm/pg@8.11.3/node_modules/pg/lib/client.js:526:17)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at PostgresConnection.executeQuery (./my_project/node_modules/.pnpm/kysely@0.26.3/node_modules/kysely/dist/cjs/dialect/postgres/postgres-driver.js:72:28)
    at <anonymous> (./my_project/node_modules/.pnpm/kysely@0.26.3/node_modules/kysely/dist/cjs/query-executor/query-executor-base.js:37:28)
    at SingleConnectionProvider.#run (./my_project/node_modules/.pnpm/kysely@0.26.3/node_modules/kysely/dist/cjs/driver/single-connection-provider.js:27:16)
    at PostgresConnection.executeQuery (./my_project/node_modules/.pnpm/kysely@0.26.3/node_modules/kysely/dist/cjs/dialect/postgres/postgres-driver.js:91:69)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at <anonymous> (./my_project/node_modules/.pnpm/kysely@0.26.3/node_modules/kysely/dist/cjs/query-executor/query-executor-base.js:37:28)
    at SingleConnectionProvider.#run (./my_project/node_modules/.pnpm/kysely@0.26.3/node_modules/kysely/dist/cjs/driver/single-connection-provider.js:27:16) {
  length: 100,
  severity: 'ERROR',
  code: '42703',
  detail: undefined,
  hint: undefined,
  position: undefined,
  internalPosition: undefined,
  internalQuery: undefined,
  where: undefined,
  schema: undefined,
  table: undefined,
  column: undefined,
  dataType: undefined,
  constraint: undefined,
  file: 'tablecmds.c',
  line: '3527',
  routine: 'renameatt_internal'
}

So basically it would be nice to be able to better debug :)

Hey 👋
PostgreSQL's alter table allows either a single rename column action or multiple add column actions, not both. See https://www.postgresql.org/docs/current/sql-altertable.html.


Fix encoding when measuring content length, otherwise downloaded card…

… is cut

Fixes #88

I'll refine in later and add tests.


Cow: Watch datatoolbar.com

Cow requests the watch of the watch_keyword datatoolbar\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

datatoolbar\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.


Another attemp to build pyfai

Let's try that, @CJ-Wright.
(also, sorted the dependencies)

Thank you, @CJ-Wright!


safely interrupt streaming requests

Safely interrupt streaming requests
Enables raising a StreamInterruption exception from a callback handler to interrupt streaming requests.
Handles cleanup of the underlying HTTP request.
More details, example usage
Here's an example usage of a callback handler that I've tested as working:
class VerboseStreamingStdOutCallbackHandler(StreamingStdOutCallbackHandler):
    @property
    def always_verbose(self) -> bool:
        """Whether to call verbose callbacks even if verbose is False."""
        return True

def make_interrupt_streaming_callback_handler(backend):
    class InterruptStreamingCallbackHandler(VerboseStreamingStdOutCallbackHandler):
        def on_llm_new_token(self, token: str, **kwargs: Any) -> None:
            if not backend.streaming:
                message = "Request to interrupt streaming"
                backend.log.info(message)
                raise StreamInterruption(message)
    return InterruptStreamingCallbackHandler()

At this moment, I've only implemented the change for the _generate method in the OpenAI Chat LLM. I have not investigated the _agenerate method, or any other LLMs yet -- would like to get some feedback/confirmation on the approach first.
Who can review?
Community members can review the PR once tests pass. Tag maintainers/contributors who might be interested:
@agola11

Thanks for your PR @thehunmonkgroup, I think the approach makes sense at a high level. One nit is that we no longer need to specify the always_verbose property as the verbose flag now only controls the StdOutCallbackHandler
We're in the process of rethinking our approach to streaming to make it easier for users to control what gets streamed/what doesn't. I should have a clearer idea of how to move forward by tomorrow so let me get back to you then.

@agola11 is there any update on this? Would really love to have a clean and sane way to stop streaming requests :)

@agola11 alrighty, I fixed an upstream conflict, this PR is in a good state again.
Can we move this feature forward? I'm happy to work on it to better prepare it for merge.

@agola11 Can you give me some  guidance on this PR? I've been maintaining it for two months with no feedback. Happy to put in the work, but I need your help!


Frames for pre-compiled sources report wrong path/line/column

Neovim pre-compiles a couple of it's modules.
See https://github.com/neovim/neovim/blob/0fe0cf5adaab06b92250eb350306de63c4d4f36f/CONTRIBUTING.md?plain=1#L259-L268
If you try to step into a function that's defined in such a pre-compiled module like vim.validate (https://github.com/neovim/neovim/blob/0fe0cf5adaab06b92250eb350306de63c4d4f36f/runtime/lua/vim/shared.lua#L849-L854), the debug adapter reports frames like:
stackFrames = { {
    column = 0,
    id = 31,
    line = 0,
    name = "validate",
    source = {
      name =<EMAIL_ADDRESS>      path = "/path/to/dev/project/a/vim/shared.lua"
    }
  }, {

/project/a is not the folder containing neovim, but a different project I was debugging. It looks like it resolves this as relative path against the working directory?
These frames currently lead to two errors with nvim-dap:

Vim:E474: Invalid argument
Debug adapter reported a frame at line 0 column 1, but: Cursor position outside buffer. Ensure executable is up2date
and if using a source mapping ensure it is correct

The first is because it tries to place a sign at line 0. The second because it tries to jump to its position. Neither works in an empty document. (Signs are 1 based, and nvim-dap sets linesStartAt1 = true, so 0 is invalid anyways)
The specification says 0 line should be ignored, but under the condition that the source attribute is missing:
https://microsoft.github.io/debug-adapter-protocol/specification#Types_StackFrame
  /**
   * The line within the source of the frame. If the source attribute is missing
   * or doesn't exist, `line` is 0 and should be ignored by the client.
   */
  line: number;

So I'm a bit reluctant to simply ignore line=0 frames.
Is there a way osv could resolve the proper source, or maybe skip them?

Thank you for the issue, I made a small change to resolve the vim runtime directory. It reads into VIMRUNTIME and appends it to the path. This allows to step into vim internal functions as well.
What I was not sure is if all the vim internal scripts resides in VIMRUNTIME . At the moment, I cannot think of a case which would not work. But you probably know more about this.
Feel free to close this issue if you feel like it is solved.

Thanks for looking into this.
The path is now resolved correctly, but column and line are still set to 0. Is it possible to change that as well?

The new behaviour is that such precompiled modules cannot be stepped into.

Thanks, that's a nice improvement over the error messages.


HTTP SD: Allow charset in content type

This PR replaces the Content-Type header check, which only allows application/json, with a regex that allows multiple (valid) combinations and formats of application/json; charset=utf-8.
(credit to @roidelapluie for the regex)
Fixes #8971

I noticed that this regex still allows an infinite number of spaces between application/json and charset=utf-8 (example: application/json;  charset=utf-8). I don't think the standard explicitly disallows it, but should we?

Wait . Did I really forget to push my http_test.go with my tests? 😅

There were test 🙃

Ya know, I do remember finding it weird that there were none

Exceeded deadline again 😠


[BUG] IOS Build Error.

Describe the bug
Using Precompose 1.6.0 is working fine, but when I upgrade to 1.6.1 get this Build Error.
Failed to load native library:libjansi.jnilib. The native library file at .gradle/native/jansi/1.18/osx/libjansi.jnilib is not executable, make sure that the directory is mounted on a partition without the noexec flag, or set the jansi.tmpdir system property to point to a proper location.  osinfo: Mac/arm64

w: Cannot infer a bundle ID from packages of source files and exported dependencies, use the bundle name instead: ComposeApp. Please specify the bundle ID explicitly using the -Xbinary=bundleId=<id> compiler flag.
e: Compilation failed: Exception during generating code for following declaration:
Inside: FILE fqName:<root>
Inside: CLASS OBJECT name:ComposableSingletons$AppKt modality:FINAL visibility:internal superTypes:[]
@Composable
private fun <init>$lambda$8$lambda$7$lambda$6($navigator: Navigator, /* var */ $composer: Composer?, $changed: Int) {
  $init_global()
  var $composer: Composer? = $composer
  when {
    when {
      areEqualByValue(first = $changed.and(other = 11).reinterpret<Int, Int>(), second = 2.reinterpret<Int, Int>()).not() -> true
      true -> $composer.<get-skipping>().not()
    } -> { // BLOCK
      Navigation(navigator = $navigator, $composer = $composer, $changed = #moe_tlaster_precompose_navigation_Navigator$stable)
    }
    true -> $composer.skipToGroupEnd()
  }
  return theUnitInstance()
}

Cannot infer a bundle ID from packages of source files and exported dependencies, use the bundle name instead: ComposeApp. Please specify the bundle ID explicitly using the -Xbinary=bundleId=<id> compiler flag.

 * Source files:
 * Compiler version: 2.0.0
 * Output kind: FRAMEWORK

To Reproduce
Steps to reproduce the behavior:

Run on apple device.

Seems like we're on board with the same issue: https://github.com/JetBrains/compose-multiplatform/issues/4809#issuecomment-2169302897

Sorry, the solution for this error is to apply:
kotlin.native.cacheKind=none property
to gradle.properties file like said
here


update the doc to match the new directory structure

What type of PR is this?
(documentation)
What this PR does / why we need it?
Update the file path to match the operator-sdk structure
Which Jira/Github issue(s) this PR fixes?
Fixes #OSD-12460
Special notes for your reviewer:
Pre-checks (if applicable):

[ ] Tested latest changes against a cluster
[ ] Included documentation changes with PR

/lgtm

Codecov Report

Merging #117 (7de6ad9) into master (b589559) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #117   +/-   ##
=======================================
  Coverage   56.82%   56.82%
=======================================
  Files          11       11
  Lines         711      711
=======================================
  Hits          404      404
  Misses        299      299
  Partials        8        8


(PDF) How to let partition_pdf and partition_via_api detect automatically language(s) of a PDF?

In the file lang.py, I see the use of the library langdetect.
In the same file, there is a function detect_languages() but it looks that partition_pdf and partition_via_api do not use it in the case of a PDF.
If it is true, why partition_pdf and partition_via_api do not use it to detect automatically the languages of the PDF?
Because of that, we have to write manually in the parameter languages the list of languages of the PDF.
Did I miss something?

+1, good question, I also met the problem when to process pdf(two language text inside), it can process english, but not Chinese word.


experimental: make it possible to pick harness generation heuristics

Makes it easier to focus during development and make experiments targeted

/gcbrun skip

/gcbrun skip


Prepare for release 0.5.1.

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


Add support email address to license form

When a user has a license issue that requires account support, show an email address users can contact for support.
<EMAIL_ADDRESS>https://github.com/tokens-studio/figma-plugin/issues/2525

Will be fixed in 2.0


[RFR] Apply recommandations for running Jest on Travis

See Jest documentation

Are you sure this improves test duration?

Improve no, but at least it prevent it from timing out


Fix smoothscroll to work with zz/zt/zb

This commit does two things:

First, existing zt/zb/zz implementation is buggy when 'smoothscroll' are 'wrap' are set. They can lead to inconsistency bugs with regarding to repainting and cursor states.
For zz, if the user uses zz whenever the top line is smooth-scrolled, the resulting draw will be wrong. For zt, if the line above the current line is super long (meaning it is so long that the wrapped line covers more than the entire screen), it will lead to the cursor being in a bad state. For zb, the exact conditions are harder to reproduce, but basically it triggers when the top line is smooth scrolled, and second line is more than one physical line tall.
Most of the reasons why they are broken is because reset_skipcol() or redraw_later() aren't called in the right place, so this change will make sure to call them appropriately.

Second, zb/zz currently will not utilize 'smoothscroll' in a satisfactory fashion. If 'smoothscroll'/'wrap' are set, we should be able to accurate put the current line at the bottom/middle of the screen by smooth-scrolling a long wrapped line at the top of the screen. This change will make those two commands do that.

Also, add tests to regression test these features.

For the first point (inconsistency bugs), see the following asciicast which demos how to trigger them.

Also, I think scrolloff is currently not working perfectly when smoothscroll is set. The logic is not taking smoothscroll into account and it also doesn't handle super long lines (lines that cannot be shown in its entirely on the screen). I decided not to tackle them for now as I don't think they lead to any serious bugs, just that it would scroll a little more than necessary.
Ideally, when we have smoothscroll, scrolloff can be more precise in always just showing that many physical lines for zt and zb (actually, for zb, we don't even need smoothscroll since we can show partial lines depending on the display setting).

This commit does two things:

First, existing zt/zb/zz implementation is buggy when 'smoothscroll' are
'wrap' are set. They can lead to inconsistency bugs with regarding to
repainting and cursor states.
For zz, if the user uses zz whenever the top line is smooth-scrolled,
the resulting draw will be wrong. For zt, if the line above the current
line is super long (meaning it is so long that the wrapped line covers
more than the entire screen), it will lead to the cursor being in a bad
state. For zb, the exact conditions are harder to reproduce, but
basically it triggers when the top line is smooth scrolled, and second
line is more than one physical line tall.
Most of the reasons why they are broken is because reset_skipcol() or
redraw_later() aren't called in the right place, so this change will
make sure to call them appropriately.

Second, zb/zz currently will not utilize 'smoothscroll' in a
satisfactory fashion. If 'smoothscroll'/'wrap' are set, we should be
able to accurate put the current line at the bottom/middle of the screen
by smooth-scrolling a long wrapped line at the top of the screen. This
change will make those two commands do that.

Also, add tests to regression test these features.

Thanks.  The 'smoothscroll' implementation is tricky, there is quite a
bit of interference with other options and features.  We'll just have to
find and fix the problems over time.
--
Violators can be fined, arrested or jailed for making ugly faces at a dog.
[real standing law in Oklahoma, United States of America]
/// Bram Moolenaar -- @.*** -- http://www.Moolenaar.net   \
///                                                                      \
\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///


Patch-AzureEdition

Update doc to reflect the inability to switch between azure edition and non-azure edition

#assign: @robinharwood, @Xelu86
@robinharwood @Xelu86
Can you review the proposed changes?
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


[FLINK-32971][PYTHON] Add pyflink proper development version support

What is the purpose of the change
The following doc describes the python version specification: https://peps.python.org/pep-0440/#developmental-releases
Extract:
Developmental releases are also permitted for pre-releases and post-releases:

X.YaN.devM       # Developmental release of an alpha release
X.YbN.devM       # Developmental release of a beta release
X.YrcN.devM      # Developmental release of a release candidate
X.Y.postN.devM   # Developmental release of a post-release

At the moment pyflink supports only .dev0 development version. In this PR I've added .devM support.
Brief change log
Added .devM support.
Verifying this change
Manually:
# Change version to: __version__ = "1.19.dev1"

cd flink

conda env remove -n venv
conda create -y -n venv python=3.10
conda activate venv
pip3 install -r flink-python/dev/dev-requirements.txt

cd flink-python
python3 setup.py sdist bdist_wheel

cd apache-flink-libraries
python3 setup.py sdist

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

cc @gyfora @mbalassi @morhidi

Any specific reason to be more lenient and not use \d+ instead?

I personally don't think that Flink must re-implement the versioning standard. I know this case it's just changing 2 chars to different 2 but the main direction is not to have python version check.

Any specific reason to be more lenient and not use \d+ instead?

I personally don't think that Flink must re-implement the versioning standard. I know this case it's just changing 2 chars to different 2 but the main direction is not to have python version check.

That is a fair point, thanks!


fix(spec-operations): update badge colors [khcp-5779]

Summary
Addresses:
https://konghq.atlassian.net/browse/KHCP-5779

PR Checklist

[ ] Naming & Structure: the files and package structure use the conventions outlined in the Creating a Package docs.
[ ] Tests pass: check the output of all package unit and/or component tests.

[ ] If this PR is the result of a bug, test coverage was added accordingly.

[ ] Functional: all changes do not break existing APIs, but if so, a BREAKING CHANGE commit is in place to bump the major version.
[ ] Conventional Commits all commits follow the conventional commit standards outlined in the main README.
[ ] Docs: includes a technically accurate README, and the docs have been updated accordingly based on the changes in this PR.

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


ADD more info on foreign addr in netstat

using GeoIP2 City database add useful info about foreign IP:

Maybe just country code (or flag :P ) with possibility to see other results in a different view in order to don't have many columns in main view.


Determining if the JavaScript API is working

I have successfully gone through the basics of Buble and see my results.  But when I attempt to use the JavaScript API, and use the following code for example:
var buble = require( 'buble' );

var input = 'const answer = () => 42;';
var output = buble.transform( input );

console.log( output.code );
console.log( output.map );

and click save, nothing happens. Is something suppose to happen?
Also, when I run from the following node command from the terminal...
node my-file.js
node tells me...
Error: Cannot find module 'buble'
I installed Buble as an npm global dependency, so I don;t understand why node can't find it and also not sure what next steps should be for processing with the API.
Thanks for any guidance in this

Since "Click save" and global NPM installation are not Bublé features you're in the wrong place.

Learning how to use npm and nodejs (which we all had to do once, so don't feel bad about it!) is out of scope here.


Cookbook database doesn't deal with non zero-padded output folder names

I'm looking at Qian's future projections perturbation run in /g/data/ik11/outputs/access-om2-01/01deg_jra55v13_ryf9091_qian_wthmp. The output in this directory goes from output836 (year 2110) to output1035 (year 2160). The folder names are not zero padded. Because of this, it looks like the cookbook database only gives access to the last 10 years (output1000, year 2151 to output1035, year 2160).
Is there a solution to this, other than requiring all folder names to be zero-padded?

Are you sure the problem is due to the folder names? I have no problem with 01deg_jra55v140_iaf_cycle4_jra55v150_extension, which runs from output992 to output1004 - see /g/data/ik11/outputs/access-om2-01/01deg_jra55v140_iaf_cycle4_jra55v150_extension.

@aekiss no I'm not sure. But I can't think of what else it would be. In a jupyter notebook:
PERT_SST = cc.querying.getvar('01deg_jra55v13_ryf9091_qian_wthmp', 'temp', session, frequency='1 monthly')
PERT_SST.time

Gives output:
array.DataArray'time'time: 120
array([cftime.DatetimeNoLeap(2150, 1, 16, 12, 0, 0, 0, has_year_zero=True),
...
       cftime.DatetimeNoLeap(2159, 12, 16, 12, 0, 0, 0, has_year_zero=True)],
      dtype=object)
...

Is it possible that this could be related to the permission problems we had on these files leading to funky indexing? Can we force the database to re-index these files (ping @angus-g)? Or perhaps just make a temporary new database to test?

Yeah I think it's from permissions problems, the earliest indexed date in that experiment is indeed 2150-01-01 (corresponding to output996). I think @micaeljtoliveira would be able to re-run the indexing to pick them up?

Oh ok. I thought the database update happened every night. That must be the explanation.

I think it's meant to, but looks like it's been failing due to running out of walltime lately: https://accessdev.nci.org.au/jenkins/blue/organizations/jenkins/COSIMA%2FCC Database Build/activity/

Unfortunately the nightly indexing has been failing quite often, but not always because of running out of walltime. I need to spend some time looking into this.

Just confirming that this issue was with the indexing. I can now access all the data.

@rmholmes Great! Last week I finally managed to fix several issues with the indexing. Hopefully it will be a smoother process from now
on.

Thanks @micaeljtoliveira!


Examples would be cool

Honestly I still have no idea what this is good for. I come here from the fluentd docker doc (chapter: "Additional Step 2: Concatenate multiple lines log messages").
The example given there with -e:4:in. I have no idea what it is or does. Please explain.

See README.md and test code, please.

I don't see examples in either. I see configuration variations but not what they do. What's the input? What's the result? What's the reason?

documentation provides input examples.
README.md describes configuration parameters.
test code provides example configuration and input and output.

documentation provides input and configuration examples.
This one is not clear. That's why I created this issue.

README.md describes configuration parameters.
test code provides example configuration and input and output.

Why do you repeat that? I already responded to that.

The example given there with -e:4:in. I have no idea what it is or does. Please explain.

This is a mark for an end line to concatenate message with regular expressions.
# start line and the second line contain "-e:2"
2016-04-13 14:45:55 +0900 docker.28cf38e21204: {"container_id":"28cf38e212042225f5f80a56fac08f34c8f0b235e738900c4e0abcf39253a702","container_name":"/romantic_dubinsky","source":"stdout","log":"-e:2:in `/'"}
2016-04-13 14:45:55 +0900 docker.28cf38e21204: {"source":"stdout","log":"-e:2:in `do_division_by_zero'","container_id":"28cf38e212042225f5f80a56fac08f34c8f0b235e738900c4e0abcf39253a702","container_name":"/romantic_dubinsky"}
# Concatinate end line should contain "-e:4"
2016-04-13 14:45:55 +0900 docker.28cf38e21204: {"source":"stdout","log":"-e:4:in `<main>'","container_id":"28cf38e212042225f5f80a56fac08f34c8f0b235e738900c4e0abcf39253a702","container_name":"/romantic_dubinsky"}

will concatinate with this plugin:
2016-04-13 14:45:55 +0900 docker.28cf38e21204: {"container_id":"28cf38e212042225f5f80a56fac08f34c8f0b235e738900c4e0abcf39253a702","container_name":"/romantic_dubinsky","source":"stdout","log":"-e:2:in `/'\n-e:2:in `do_division_by_zero'\n-e:4:in `<main>'"}

I'm wondering why these examples are hard to understand for you.
Do you want to concatenate log such as one by one Fluentd Docker drivers'?
Or just want to try to follow the above article?
If you tell us what you want to do with this plugin, it would be able to solve your question more easily.

Yeah, I'm just going through the article you linked and try to understand what they write there. I never felt a reason to concat log messages. Usually it's convenient that they are each on their own line.
The only usecase I can think off myself that may or may not go into a similar direction is for instance nginx reporting 150x "I got a request from client <IP_ADDRESS> and responded with 200". This could be combined in log aggregation to "I got a request from client <IP_ADDRESS> and responded with 200 (150x)" in a single line.

Our assuming use cases are:

Concatenate Ruby or other LL multiline stacktrace
JVM null pointer or something exception multiline stacktrace
Golang stack trace

They are in Docker container.
If there is any problem or feedback, you can report as an issue in https://github.com/fluent/fluentd-docs.


Windows 7 VMWARE crash

VMWARE with Win 7 64bit.
The app will crash on startup, version prior the hotfix worked fine.

Supermium is being run in a VMware guest, right?
I have been primarily testing in a Windows 7 VM in VMware Workstation 10 and it has worked very well with all changes I have made.
Which version of VMware software and guest additions are being used?

VMware® Workstation 17 Pro
17.5.0 build-22583795
Win 7 Ultimate x64 with latest updates.
The host is AMD Ryzen™ 7 7840HS ; Graphics Model. AMD Radeon™ 780M
Could be that VM drivers dont like dx11 as previously it was going via vulkan
If you need a crash report let me me know.

Have you tried Supermium 119 and earlier? Those would also default to D3D11.
And if not, command line switches can be used to force another renderer, including the Vulkan renderer (--enable-vulkan --use-angle=vulkan), OpenGL (--use-angle=gl) or D3D9 (--use-angle=d3d9).

I am using thorium 119 atm.
Will test with other renderers and see how it goes.

Hmm, odd but fixed the issue, tried vulkan it loaded fine, reverted back to d11 still works so all good.


from 25th to 28th of this month

this is working fine in the site(try it now) but not giving the desired result in java code

Working in the latest code 0.13


Add Jetpack/JetBrains Compose icons (Light & Dark)

This PR adds light and dark icons for Jetpack/JetBrains Compose
Preview

Light
Dark

@tandpfun Does this look alright?


Rely on OpenAPI/jsonschema's Relative References

This could work eventually. It's not worth it since the current script is sufficient: https://github.com/Observation-Management-Service/ewms-workflow-management-service/blob/main/resources/build_openapi_schema.py


Internship Assignment : Batch Effect correction in Deconvolution of Spatial transcriptomics profiles

As per the Assignment, I have modified the following functions in order to implement a batch effect correction in the spatial deconvolution Modules of the RNAStereoscope model :
RNADeconv.init
RNADeconv._get_generative_inputs
RNADeconv.generative
RNADeconv.loss
RNAStereoscope.init
RNAStereoscope.setup_anndata
I have tested the following implementation in the following notebook : https://colab.research.google.com/drive/1guMxkfaDBrAXQavRVManOv5WlTPoFBvL?usp=sharing  where I follow the work done in https://docs.scvi-tools.org/en/stable/tutorials/notebooks/spatial/stereoscope_heart_LV_tutorial.html in order to show the efficiency of the Batch effect correction !

Please remake PR this within your forked repo, not to the upstream repo @Mathixx


Need help with manual OTEL integration for spark jobs

Hi Tsukada,
I am trying to instrument our spark structured streaming jobs and came across issue raised by you https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/9638.
I am still going through the documentation on how to manually instrument the job. If possible, please share the boilerplate implementation.
Thanks !

Hi himanshujeena,
What you need is an example written in Scala?
If I create something like this poc with manual instrumentation in Scala, can it help you?

Yes, I am looking for Scala example.
That would be a great help. Thanks!

Hi himanshujeena,
It's done. Please see 'manual' branch.
https://github.com/tsukada-ascade/spark-structed-streaming-poc/tree/manual
Run it, you will get a result like shown below. The "THIS IS MANUAL" span is manual.
Thanks

Thanks a bunch tsukada :)


Knex always modify record when knex gets timestamp(datetime)

DB
created_at datetime
-----------------------
2017-01-01 11:11:11

But Knex gets
created_at: 2017-01-01T02:11:11.000Z
I know if this column is timestamp but this is datetime.
How to get record(datetime) without changes?
knex config
knex = knex({ // local
    client: 'mysql2',
    connection: {
      host: process.env.DBHOST,
      user: process.env.DBUSER,
      password: process.env.DBPASS,
      database: process.env.DBNAME,
      ssl: {
        ca: process.env.CA,
      },
    },
    pool: {
      afterCreate: function (conn, done) {
        conn.query("SET time_zone = 'Asia/Tokyo';", function (err) {
          done(err, conn);
        });
      }
    },
  });

sry I solved.
Add dateStrings: true to connection: {}


Adding the Jobs API

As of Know there is a static data of jobs So,we can create a new REST ful API which can be created using the Traditional MVC architecture . where we can create a model and controllers and connect it to frontend .
Can you assign me this issue under GSSOC'24

Seems Good ! Go Ahead 🚀 @neelamnagarajgithub

Hey, could you assign me this issue as I am familiar with this and make it a quick and fast optimized API service for the website available too @PatilHarshh .

Solved this issue unde pr #10
Created a total Jobs RESTFUL API
CREATED
Jobs-Model✅
Jobs-Controller✅
Job Route✅
and using middleware connected to /api/v1/Jobs
we can
✅create a new Job by sending post request to /api/v1/Jobs
✅get all job details by sending get request to /api/v1/Jobs
✅we can update and delete the Jobs details by sending the patch and delete request to /api/v1/Jobs/id
✅ we can get a particular job details by sending get by id request to /api/v1/Jobs


STOP HACKING USERS!

Please STOP HACKING PEOPLE

Dont use anything from their profile their files hack your system and gpu!

The code is literally right here for anybody to check and clearly shows we're doing none of that.

Code is different than what is in the file!

No, it's not.


Update pulsar-client, ... to 3.3.0

About this PR
📦 Updates

org.apache.pulsar:pulsar-client
org.apache.pulsar:pulsar-functions-api

from 3.1.3 to 3.3.0
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.apache.pulsar" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.apache.pulsar" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #205.


Add the nodejs and node6js actions for greeting

I don't think we need test nodejs action, because by default, greeting.js is running on nodejs container.
So only nodejs 6 action is needed.

Merged. Close it.

By default it runs on nodejs 6 not nodejs.  Where are these nodejs and nodejs 6 tests coming from?

Can you please take me thru each of the tests in this file?  Where are the equivalent tests in openwhisk?


fix:Modify yu ju for contributor-graph repository

Modify yu ju for contributor-graph repository

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

Note that there are spaces

and also update here


Enhance Stratification Key Handling with Missing Data and Type Flexibility

Description
The current implementation of the stratification process in the code does not robustly handle scenarios where stratify_cols may be None, a DataFrame, or contain missing values. This can lead to issues, especially in feature spaces with incomplete data. The proposed enhancement aims to address these shortcomings by introducing additional checks and processing steps.
Problem

Handling of stratify_cols: The current code assumes that stratify_cols is either a list of column names or a truthy value without considering if it might be None or a DataFrame. This lack of flexibility can cause errors when stratify_cols is a DataFrame or None.

Missing Data in Stratification Keys: The existing implementation does not account for missing values in the stratification key, which can lead to errors or incorrect stratification results when there are missing data points in the features or labels.

Proposed Solution

Type Checking and Flexibility:

Implement explicit checks to verify if stratify_cols is None or a DataFrame.
If stratify_cols is a DataFrame, directly concatenate it with the target variable (y or y_valid_test).
If stratify_cols is not a DataFrame, treat it as a list of column names to be selected from X or X_valid_test.

Handling Missing Data:

After creating the stratification key (stratify_key or strat_key_val_test), check if it is not None.
Make a copy of the stratification key and fill any missing values with an empty string (''). This ensures that the stratification process works even with incomplete data, preventing potential errors.

Code Changes
Introduce the following block after creating the stratification key:
if stratify_key is not None:
    stratify_key = stratify_key.copy()
    stratify_key = stratify_key.fillna('')

Similarly, for the validation/testing dataset:
if strat_key_val_test is not None:
    strat_key_val_test = strat_key_val_test.copy()
    strat_key_val_test = strat_key_val_test.fillna('')

Modify the logic for creating the stratification keys to include checks for None and DataFrame types, as well as handling missing data.
This enhancement will make the code more robust, flexible, and reliable, especially in scenarios where data completeness cannot be guaranteed. By ensuring proper handling of different types and missing data, the code will be better suited for real-world applications where these challenges are common.

This seems to work as a fix but will cause issues with imputation later if we are using our current implementation.
Currently imputation defaults as treating "nan" values as missing but if we replace these values with '' then this will no longer be imputed as empty strings are not treated as nan in Python.
A suggested fix for this:
If we are imputing and stratifying by cols we should change the missing value in the SimpleImputer.
SimpleImputer(missing_values='')

Another fix would be to remove the current way we handle imputation and completely convert to custom pipeline steps so that the user would need to implement this code outside the class.


extension: pg_trgm

support for similarity of text using trigram matching
https://www.postgresql.org/docs/current/pgtrgm.html
Use case for me for pglite:

Offloading work from the DB to instant read replicas living inside serverless functions
pg_trgm is commonly used for string comparisons and provides the GIN and GIST index handling

pg_trgm is supported in the current alpha/@next release, expected to go final in about a week.


Vote for release of v1.2.5

At least 3 approvals are needed from the 4 owners for tagging 9d9e2cb1efbad77745b57601947a3b537313ba7f from the v1 branch as v1.2.5.

[ ]  Sajay Antony (@sajayantony)
[ ]  Shiwei Zhang (@shizhMSFT)
[ ]  Steve Lasker (@SteveLasker)
[x]  Sylvia Lei (@Wwwsylvia)

Aside from the dependency bump-ups, there is one noteworthy change:

types.AuthConfig is moved to registry.AuthConfig  in docker/docker v25.0.0. Although there is no public API change on oras-go side, it may still break users if they are using oras-go v1 along with old versions of docker/docker (see #678).

See the change log for more details.
Please respond LGTM or REJECT (with reasoning).

LGTM. We need to mention the types.AuthConfig change in the release note.

LGTM


Allow to Navigate to Success Submission page

Issue:
When submitting a new Rental Application, the Success page was by-passed and user was navigated to Account Select page.
Description of changes:

Fix to allow users to navigate to Success Submission page

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the namex license (Apache 2.0).

/gcbrun

Temporary Url for review: https://strr-ui-dev--pr-294-hn3iwhpu.web.app


Cannot load YouTube video because YouTube player element ID required

Use<EMAIL_ADDRESS>but i cannot load YouTube video
There is an error below
Uncaught (in promise) Error: YouTube player element ID required.

Mac OS Big Sur version: 11.5.2
Chrome version: 93.0.4577.63

Sorry, I can't reproduce this error. It would be great if you gave more information (browser, os) and ideally - an example with this error

OP didn't mention the stack trace, but for me the console error is:
www-widgetapi.js:897 Uncaught (in promise) Error: YouTube player element ID required.
    at pl.gl (www-widgetapi.js:897:121)
    at new pl (www-widgetapi.js:928:22)
    at Proxy.initPlayer (YouTube.vue?6574:118:21)
    at YouTube.vue?6574:97:34

Unfortunately this error still occurs

MacOS Big Sur 11.4 (20F71)
Chrome Version 100.0.4896.75

Same here. Anyone found a fix yet?

Same here. 😢

same here. The weird is it was working until last Friday.

Same error here


Add P2S VPN support OS - iPad OS

The documentation does not include the iPad OS as an OS that supports P2S VPN connections.
https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-vpn-faq#supportedclientos
My understanding is that the iPad OS is a branch of iOS, and is based on iOS 13.x or later, so the both OS is almost same.
Could you please list the iPad OS as a supported OS in the documentation?

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

ID: 98d7fd30-80a8-f690-6191-d97ae4cac174
Version Independent ID: 3e15f99b-2f2d-7adc-a2d9-0b2184989db7
Content: Azure VPN Gateway FAQ
Content Source: articles/vpn-gateway/vpn-gateway-vpn-faq.md
Service: vpn-gateway
GitHub Login: @yushwang
Microsoft Alias: yushwang

@saiut  Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

Hi @CHEEKATLAPRADEEP-MSFT i would like to work on this issue but i could find the link to the documentation in the github could you provide the path to the document

@v-sreekesh P2S suport device document is "https://github.com/MicrosoftDocs/azure-docs/blob/master/includes/vpn-gateway-faq-p2s-all-include.md"

Hi @v-sreekesh , if you have any updates, please tell me these updates.

Hi @saiut
Currently, we have not validated the P2S connections on iPad OS. I will check with the team to see if we can start the validation and update the document. Unfortunately, we cannot update the docs until the validation is completed.
Thanks!!

#reassign:aybatra

Thank you for you dedication to our documentation.
Unfortunately, we have been unable to review this issue in a timely manner. We sincerely apologize for the delayed response. We are closing this issue. If you feel that the problem persists, please respond to this issue with additional information.
Please continue to provide feedback about the documentation. We appreciate your contributions to our community.
#please-close


Option to select how many images to preload with lazyload

The only feature I am wishing for would be the ability to choose how many images to preload like the numImagesToPreload feature in Royal Slider (referring to royal slider documentation - options - numImagesToPreload).
A page I'm working on will have many carousels, around 10-15, with 5-10 images each. On Demand lazy loading helps, but means a delay every time the user changes the image.
Progressive lazy loading means a decent first load of the initially visible images, but a lot of bandwidth used otherwise for images that may never actually be seen.
(Otherwise I am of course so happy with slick, it's an amazing library, many thanks)

I needed this function too but because SlickSlider doesn't support different sources for 72dpi and retina images I had to use another plugin. I chose lazyLoadXT (https://github.com/ressio/lazy-load-xt).
I implemented it using:
slickSlider.on('afterChange', function() {
    var activeSlide = $('.slick-slide.slick-active');
    activeSlide.next().find('img[data-srcset]').lazyLoadXT({
        show: true
    });
});

There is another value for lazyLoad option in the source code, not documented though: 'anticipated'.
It seems to do what the OP was looking for.

From what I have seen 'ondemand' on an autoplay slideshow always seems to pull in required images about 2 slides ahead of when they will be used, which feels like it handles this in a pretty sensible way

Any news about this? (sorry for duplicate)

@kdesigns In version 1.9.0 there is no function called lazyLoadXT. Is there a new way to lazy load the next image?

@pminf have you tried slickNext ?
$('.your-element').slick('slickNext');

There is another value for lazyLoad option in the source code, not documented though: 'anticipated'.

Why is this not documented? Works like exspected and was introduced in release 1.7.1

if you wanna preload 1 img, you can use this way
let currentS = $(".photo_viewer_slideshow");
currentS.slick({
lazyLoad: "ondemand",
slidesToShow: 1.000000001,
slidesToScroll: 1,
});


return current pageX, pageY with the event

It could be generally useful if the event passed to the handlers could also hold the current X & Y coordinates of the mouse at the time of firing. This could be added as part of the event.data, or more seamlessly (though potentially an unwanted side-effect for some) copied over the pageX/pageY of the returned event itself. This would make it much easier for those who want their handler to, for example, position something relative to the location of the pointer at the time of firing.
Thoughts? If I have time and there's interest, I can put an example implementation in a pull request.

@usmonster - I'm in agreement with the copy-coordinates approach, as the default (and only) behavior. Just make sure to increment the version and note the (possible) backwards incompatibility for folks that were using the pageX/pageY of the original event. If someone complains we can consider adding a configuration option.

While implementing this I realize the possibility that the most common use case may care about the current pointer coordinates only for the over handler and not for out. That said, I'm hesitating--should I still copy the current values onto both events (for consistency), or is it better to copy them only for the over handler?
Copying current coordinates to the event passed to out would still allow access to the originalEvent's coordinates, though this could arguably be a more surprising/less intuitive default behavior..
Anyone have a compelling use case to support either option?

Actually, I've just convinced myself that it's fine to copy both, I'll just document this change.

I keep going back and forth on consistency vs. intuition issue, and it's blocking the release...
Basically, I'd just like some/any feedback as to whether it makes more sense to leave the out handler event as-is (it has the pointer coordinates of the original mouseleave event), or if it's objectively better to give it the coordinates that are "current" at the moment when the handler is called (i.e. after the timeout, if any is given--this would require additional mousemove tracking between the mouseleave and said timeout).
Thoughts? @flesler, @roydukkey, @briancherne?

In my opinion it makes sense to leave it the way it currently is, because out means, well when the mouse moves out. So my vote is to leave e.pageX and e.pageY alone.
It would be easy to add e.delayedPageX and e.delayedPageY. But, I'm not in favour of modifying the behaviour of jQuery.
Wouldn't it be fine to update the out signature to include a parameter for things that are additional to jQuery? Something along these lines:
// out: Function( Event eventObject, Object delayedCoord )

$( "p" ).hoverIntent( function() { }, function( event, delayed ) {
     delayed.pageX;
     delayed.pageY;
});

Thanks for the rapid feedback, @roydukkey! I agree with the semantics of out, though the same reasoning could be applied to the over case. One can imagine valid use cases where someone might want to have access to the actual handler-time coordinates instead of (or in addition to) the event-time coordinates for both mouseenter/"over" and mouseleave/"out" cases. Applying the same kind of modification for both event/handler pairs would also preserve a kind of semantic and behavioral symmetry.
All that said, I may be leaning slightly toward leaving the mouseleave/out case alone, at least for this release, since the necessity of the change is currently less compelling than for the mouseenter/over case. Still, I'll leave the issue open a bit for other feedback until a decision is made.
As for the proposed alternatives, I doubt we'd add a delayedPageX value to the event or change the API of the handler in any case, especially since the latter could arguably be a more disruptive change. thanks for the suggestions, though!

Right. I did overlook the over case, but do you mind elaborating on how you feel the latter could be disruptive? Though the handler would be applied as Function( Event eventObject, Object delayedCoord ) both parameters are still optional and do not present any new requirements in implementing hoverIntent. out: function() { } and out: function( event ) { } would still be acceptable without any issue.

No problem! To elaborate, the disruption I was talking about is more to the users of the plugin, since hoverIntent is meant to be a drop-in replacement for .hover. If hoverIntent passed its own proprietary object to the handler--which can be any user-provided function--we have no guarantee that the function would behave the same. What if someone reuses the out function elsewhere and it already has different behavior based on its arguments? This would break for them. I think most behavior changes like this should be done in a way that doesn't change the API/contract that says "we will only pass an Event to the callback, even if your callback can take more arguments." Hope that makes sense.