When I use the --release flag, I get errors on MacOS Sonoma (14.3.1)

When I use the --release flag, I get errors.
$ cargo build --release
   Compiling proc-macro2 v1.0.83
   Compiling libc v0.2.155
   Compiling syn v1.0.109
   Compiling rustversion v1.0.17
   Compiling anstyle-query v1.0.3
error: failed to run custom build command for `proc-macro2 v1.0.83`

Caused by:
  process didn't exit successfully: `/Users/chad/working/rsop/target/release/build/proc-macro2-21fb11b2b8742029/build-script-build` (signal: 9, SIGKILL: kill)
warning: build failed, waiting for other jobs to finish...
error: failed to run custom build command for `libc v0.2.155`

Caused by:
  process didn't exit successfully: `/Users/chad/working/rsop/target/release/build/libc-9cfb5571b05c3f32/build-script-build` (signal: 9, SIGKILL: kill)
error: failed to run custom build command for `syn v1.0.109`

Caused by:
  process didn't exit successfully: `/Users/chad/working/rsop/target/release/build/syn-5fedb5aa04aaafd7/build-script-build` (signal: 9, SIGKILL: kill)
error: failed to run custom build command for `rustversion v1.0.17`

Caused by:
  process didn't exit successfully: `/Users/chad/working/rsop/target/release/build/rustversion-f8b6e1301ec0ffc4/build-script-build` (signal: 9, SIGKILL: kill)

Without the --release flag, it compiles fine.
To get more information, I tried the --verbose flag and not much more helpful info was provided.
$ cargo build --release --verbose
   Compiling proc-macro2 v1.0.83
       Fresh unicode-ident v1.0.12
       Fresh memchr v2.7.2
       Fresh tinyvec_macros v0.1.1
       Fresh utf8parse v0.2.1
       Fresh cc v1.0.98
       Fresh colorchoice v1.0.1
     Running `/Users/chad/working/rsop/target/release/build/proc-macro2-21fb11b2b8742029/build-script-build`
   Compiling libc v0.2.155
       Fresh anstyle-parse v0.2.4
   Compiling syn v1.0.109
       Fresh tinyvec v1.6.0
   Compiling rustversion v1.0.17
       Fresh cfg-if v1.0.0
       Fresh hashbrown v0.14.5
       Fresh anstyle-query v1.0.3
     Running `/Users/chad/working/rsop/target/release/build/libc-9cfb5571b05c3f32/build-script-build`
     Running `/Users/chad/working/rsop/target/release/build/syn-5fedb5aa04aaafd7/build-script-build`
     Running `/Users/chad/working/rsop/target/release/build/rustversion-f8b6e1301ec0ffc4/build-script-build`
       Fresh equivalent v1.0.1
       Fresh gimli v0.28.1
       Fresh is_terminal_polyfill v1.70.0
   Compiling anstyle v1.0.7
     Running `/Users/chad/.rustup/toolchains/stable-aarch64-apple-darwin/bin/rustc --crate-name anstyle --edition=2021 /Users/chad/.cargo/registry/src/index.crates.io-6f17d22bba15001f/anstyle-1.0.7/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --diagnostic-width=283 --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C linker-plugin-lto -C codegen-units=1 '--warn=clippy::zero_sized_map_values' '--warn=clippy::wildcard_imports' '--warn=clippy::verbose_file_reads' --warn=unused_qualifications --warn=unused_macro_rules --warn=unused_lifetimes --warn=unsafe_op_in_unsafe_fn --warn=unreachable_pub '--warn=clippy::trait_duplication_in_bounds' '--warn=clippy::todo' '--warn=clippy::string_to_string' '--warn=clippy::string_lit_as_bytes' '--warn=clippy::string_add_assign' '--warn=clippy::string_add' '--warn=clippy::str_to_string' '--warn=clippy::single_match_else' '--warn=clippy::semicolon_if_nothing_returned' '--warn=clippy::self_named_module_files' '--warn=clippy::same_functions_in_if_condition' --warn=rust_2018_idioms '--warn=clippy::rest_pat_in_fully_bound_structs' '--warn=clippy::ref_option_ref' '--warn=clippy::redundant_feature_names' '--warn=clippy::rc_mutex' '--warn=clippy::ptr_as_ptr' '--warn=clippy::path_buf_push_overwrite' '--warn=clippy::negative_feature_names' '--warn=clippy::needless_for_each' '--warn=clippy::needless_continue' '--warn=clippy::mutex_integer' '--warn=clippy::mem_forget' '--warn=clippy::match_wildcard_for_single_variants' '--warn=clippy::macro_use_imports' '--warn=clippy::lossy_float_literal' '--warn=clippy::linkedlist' '--allow=clippy::let_and_return' '--warn=clippy::large_types_passed_by_value' '--warn=clippy::large_stack_arrays' '--warn=clippy::large_digit_groups' '--warn=clippy::items_after_statements' '--warn=clippy::invalid_upcast_comparisons' '--warn=clippy::infinite_loop' '--warn=clippy::inefficient_to_string' '--warn=clippy::inconsistent_struct_constructor' '--warn=clippy::imprecise_flops' '--warn=clippy::implicit_clone' '--allow=clippy::if_same_then_else' '--warn=clippy::from_iter_instead_of_collect' '--warn=clippy::fn_params_excessive_bools' '--warn=clippy::float_cmp_const' '--warn=clippy::flat_map_option' '--warn=clippy::filter_map_next' '--warn=clippy::fallible_impl_from' '--warn=clippy::explicit_into_iter_loop' '--warn=clippy::explicit_deref_methods' '--warn=clippy::expl_impl_clone_on_copy' '--warn=clippy::enum_glob_use' '--warn=clippy::empty_enum' '--warn=clippy::doc_markdown' '--warn=clippy::debug_assert_with_mut_call' '--warn=clippy::dbg_macro' '--warn=clippy::create_dir' '--allow=clippy::collapsible_else_if' '--warn=clippy::checked_conversions' '--allow=clippy::branches_sharing_code' '--allow=clippy::bool_assert_comparison' --cfg 'feature="default"' --cfg 'feature="std"' -C metadata=048fb9ee88865e0e -C extra-filename=-048fb9ee88865e0e --out-dir /Users/chad/working/rsop/target/release/deps -C strip=symbols -L dependency=/Users/chad/working/rsop/target/release/deps --cap-lints allow`
error: failed to run custom build command for `proc-macro2 v1.0.83`

Caused by:
  process didn't exit successfully: `/Users/chad/working/rsop/target/release/build/proc-macro2-21fb11b2b8742029/build-script-build` (signal: 9, SIGKILL: kill)
warning: build failed, waiting for other jobs to finish...
error: failed to run custom build command for `syn v1.0.109`

Caused by:
  process didn't exit successfully: `/Users/chad/working/rsop/target/release/build/syn-5fedb5aa04aaafd7/build-script-build` (signal: 9, SIGKILL: kill)
error: failed to run custom build command for `libc v0.2.155`

Caused by:
  process didn't exit successfully: `/Users/chad/working/rsop/target/release/build/libc-9cfb5571b05c3f32/build-script-build` (signal: 9, SIGKILL: kill)
error: failed to run custom build command for `rustversion v1.0.17`

Caused by:
  process didn't exit successfully: `/Users/chad/working/rsop/target/release/build/rustversion-f8b6e1301ec0ffc4/build-script-build` (signal: 9, SIGKILL: kill)

I'm new to rust, so this might be a simple skill issue on my part.  Please advise.

Is your Rust toolchain up to date? How did you install it?
You can try commenting out the lto = true line in Cargo.toml, but that should not be needed.
I can't help you much more because I am on Linux, and I get a very different error when cross compiling.

I was running rust 1.75.0.
I tried using brew install rust and then rustup via:
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

Both installed the latest rust tools (1.78.0) and resulted in the same errors.  This appears to be a problem with rust on M1 processors.
https://github.com/rust-lang/cargo/issues/8913

Commenting out lto = true had no effect.  Commenting out strip = true had no effect.

What's weird is that the error only occurs in release mode.
You can try overriding each option that is specific to the release profile, until you find the one that causes the error.

My testing shows that debug must be true.  Also if I change strip from "none" (default) to true (as set by this project's Cargo.toml) it also fails.

@cskeeters  I just stumbled upon this issue since I was having a similar problem in another Rust project (thin-edge.io)...so just posting in case it is also helpful for you.
In the end it was an issue with the homebrew binutils package, see the original issue in the rust project which goes into some more details.
To fix it, check which strip is used by default on your console:
which strip

If you get anything other than /usr/bin/strip, then you will need to check your PATH environment variable (maybe remove the binutils path from it if you did something similar to me).
Afterwards you will have to run cargo clean, then you should be able to build again.
cargo clean
cargo build --release

@reubenmiller, Thank you for this post.  I can confirm that my path was configured to use strip from binutils.  Without this path element, cargo build --release works fine.
That begs the question:  What's going on?  Why does gnu strip from binutils break cargo?  Is this a bug or incompatibility?  If it's a compatibility issue, could cargo not check strip's version for compatibility before utilization?  If it's a bug has a bug been filed?  I didn't see one on their bug tracker.


Python Installs Are Missing Modules

Describe the bug
Using a clean install of rtx via Cargo on my Linux machine (Pop!_OS), and when I installed the latest version of Python (3.11), I received all these warning regarding missing modules (as seen in the snippet below).
Downloading Python-3.11.4.tar.xz...
-> https://www.python.org/ftp/python/3.11.4/Python-3.11.4.tar.xz
Installing Python-3.11.4...
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/kingofheroes/.local/share/rtx/installs/python/3.11.4/lib/python3.11/bz2.py", line 17, in <module>
    from _bz2 import BZ2Compressor, BZ2Decompressor
ModuleNotFoundError: No module named '_bz2'
WARNING: The Python bz2 extension was not compiled. Missing the bzip2 lib?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/kingofheroes/.local/share/rtx/installs/python/3.11.4/lib/python3.11/curses/__init__.py", line 13, in <module>
    from _curses import *
ModuleNotFoundError: No module named '_curses'
WARNING: The Python curses extension was not compiled. Missing the ncurses lib?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'readline'
WARNING: The Python readline extension was not compiled. Missing the GNU readline lib?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/kingofheroes/.local/share/rtx/installs/python/3.11.4/lib/python3.11/sqlite3/__init__.py", line 57, in <module>
    from sqlite3.dbapi2 import *
  File "/home/kingofheroes/.local/share/rtx/installs/python/3.11.4/lib/python3.11/sqlite3/dbapi2.py", line 27, in <module>
    from _sqlite3 import *
ModuleNotFoundError: No module named '_sqlite3'
WARNING: The Python sqlite3 extension was not compiled. Missing the SQLite3 lib?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/kingofheroes/.local/share/rtx/installs/python/3.11.4/lib/python3.11/tkinter/__init__.py", line 38, in <module>
    import _tkinter # If this fails your Python may not be configured for Tk
    ^^^^^^^^^^^^^^^
ModuleNotFoundError: No module named '_tkinter'
WARNING: The Python tkinter extension was not compiled and GUI subsystem has been detected. Missing the Tk toolkit?
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/kingofheroes/.local/share/rtx/installs/python/3.11.4/lib/python3.11/lzma.py", line 27, in <module>
    from _lzma import *
ModuleNotFoundError: No module named '_lzma'
WARNING: The Python lzma extension was not compiled. Missing the lzma lib?
Installed Python-3.11.4 to /home/kingofheroes/.local/share/rtx/installs/python/3.11.4
rtx<EMAIL_ADDRESS>
I received a near identical output when I installed Python 3.10.
Admittedly, I'm rather new at Python, so I don't know if this is usual, but I get paranoid whenever I see errors/warnings like this; however, I didn't receive these sort of warnings when installing Python 3.9 on my MacBook Pro that I use for work. (I had installed rtx using Homebrew on that computer.)
To Reproduce
All you have to do is enter the following command:
rtx install python@latest

# Or this command

rtx install<EMAIL_ADDRESS>
Expected behavior
A clear and concise description of what you expected to happen.
rtx doctor output
rtx version:
  2023.8.2 linux-x64 (2023-08-19)

build:
  Target: x86_64-unknown-linux-gnu
  Features: DEFAULT, NATIVE_TLS
  Built: Sat, 19 Aug 2023 18:59:12 +0000
  Rust Version: rustc 1.71.1 (eb26296b5 2023-08-03)
  Profile: release

shell:
  fish
  fish, version 3.6.1

rtx data directory:
  /home/kingofheroes/.local/share/rtx

rtx environment variables:
  RTX_SHELL=fish

settings:
  {"always_keep_download": "false", "always_keep_install": "false", "asdf_compat": "false", "disable_default_shorthands": "false", "disable_tools": "[]", "experimental": "false", "jobs": "4", "legacy_version_file": "true", "legacy_version_file_disable_tools": "[]", "log_level": "INFO", "missing_runtime_behavior": "warn", "plugin_autoupdate_last_check_duration": "10080", "raw": "false", "trusted_config_paths": "[]", "verbose": "false", "yes": "false"}

config files:
  /home/kingofheroes/.config/rtx/config.toml

plugins:
  go       (core)
  java     (core)
  node     (core)
  python   (core)
  ruby     (core)

toolset:
  node@latest, python@latest

No problems found

@KerickHowlett rtx use pyenv(python-build as a pyenv plugin) to install python under the hood,  you need to install dependencies first for building from sources before you run rtx install python
https://github.com/pyenv/pyenv/wiki#suggested-build-environment

Oh! That makes sense! On my work computer, I had Pyenv installed before switching over to rtx. 😅
Anyway, thanks for the response! I'll try this out soon, and I'll let you know how it goes.

I just realized I forgot to provide an actual update on this. lol
Anyway, it worked, so I'm gonna go ahead and close this issue!
Thanks again for the fast assistance! :)


Allow to specify log level via env variables

By default log level is set to DEBUG which makes marathon-lb very noisy in environments where deployments are frequent (few per hour). Allow to specify log level via i.e. HAPROXY_LOG_LEVEL environment variable

You can change it on the command line with --log-level, as per https://github.com/mesosphere/marathon-lb/blob/master/Longhelp.md#command-line-usage.


Update Composer dependencies (2024-05-23-00-12)

Visual regression test passed!
View the visual regression test report


Account signups needing verification redirect to home (or back)

The welcome page is for verified user accounts.

coverage: 93.464%. remained the same
when pulling eb1bf8e68b612bbc2d30f85e7e929e20a7d4fdf8 on njw-welcome-user-tweak
into 097453402a6a883775bda04b2d2d4815b95c5c43 on main.


ValueError in ProbClassificationPerformanceTab

Hi,
I'm testing evidently with  light gbm binary classifier and getting the following error:
ValueError: Found array with 0 sample(s) (shape=(0, 2)) while a minimum of 1 is required
on calculate quality metrics for ProbClassificationPerformanceTab, though DataDriftTab works fine.
Can you help please? is it possible to add new quality metric e.g. gini  to the dashboard?
Thanks for your amazing work

Hi @sanram905 ,
first of all we do apologise for the late response.
Apparently, we  missed your question 😔
That's very interesting, especially tacking into account that DataDriftReport  works.
We know, that we have a problem with the N/A values. Particularly, we try to filter out them from the dataset and sometimes it leads to the unforeseen consequences. Do you think that might be connected to the error you got?  Were there any missing values among the targets or projections?

Hi Emeli,
Thanks for getting back on it. Yes you are the right. The issue is due to missing values in the dataset. It works if all missing values are dropped or imputed. I have another question: is it possible to add another dimension to data distribution plots?


67 twitter embed

closes #67
Summary

Twitter URLs in markdown turn into twitter embeds

Preview:

Changes

TwitterEmbed component in core added
Customlink Component updated
doc added at docs/social-previews

Notes

Core changes in PR needs to be published for this to work
Dark/Light theme to be added later when our Theme switch is working

@PhilippeduPreez additionally, I'd try using Next.js Script component: https://nextjs.org/docs/basic-features/script. Although I'm not sure if it will work here. But take a look at it.


Write a Scala program to print diamond pattern

Description
Write a Scala program to print diamond pattern
Input  : 5

Output :
    *
   ***
  *****
 *******
*********
 *******
  *****
   ***
    *

How to contribute

Save the solution in program/printDiamondPattern.scala file
Add printDiamondPattern.scala file in print-diamond-pattern folder

!assign


Solution for "Text is not completely shown in Expanded State (Height Calculation Issue)"

Incase of large text, the text isn't shown completely in expanded state. This is still a bug in the latest version of this repository as of today and needs to be fixed in the next release @Manabu-GT . For now, following is the solution explained clearly.
SOLUTION
In ExpandableTextView class, in the onMeasure method: Cut the line
       mTextHeightWithMaxLines = getRealTextViewHeight(mTv);

and paste it right below this line
        super.onMeasure(widthMeasureSpec, heightMeasureSpec);

Or for ease, you can directly replace your onMeasure method with the method below.
    @Override
    protected void onMeasure(int widthMeasureSpec, int heightMeasureSpec) {
        // If no change, measure and return
        if (!mRelayout || getVisibility() == View.GONE) {
            super.onMeasure(widthMeasureSpec, heightMeasureSpec);
            return;
        }
        mRelayout = false;

        // Setup with optimistic case
        // i.e. Everything fits. No button needed
        mToggleView.setVisibility(View.GONE);
        mTv.setMaxLines(Integer.MAX_VALUE);

        // Measure
        super.onMeasure(widthMeasureSpec, heightMeasureSpec);

        //--- Previously the mTextHeightWithMaxLines was initialized here ---//

        // If the text fits in collapsed mode, we are done.
        if (mTv.getLineCount() <= mMaxCollapsedLines) {
            return;
        }

        // Doesn't fit in collapsed mode. Collapse text view as needed. Show
        // button.
        if (mCollapsed) {
            mTv.setMaxLines(mMaxCollapsedLines);
        }
        mToggleView.setVisibility(View.VISIBLE);

        // Re-measure with new setup
        super.onMeasure(widthMeasureSpec, heightMeasureSpec);

       mTextHeightWithMaxLines = getRealTextViewHeight(mTv);

        if (mCollapsed) {
            // Gets the margin between the TextView's bottom and the ViewGroup's bottom
            mTv.post(new Runnable() {
                @Override
                public void run() {
                    mMarginBetweenTxtAndBottom = getHeight() - mTv.getHeight();
                }
            });
            // Saves the collapsed height of this ViewGroup
            mCollapsedHeight = getMeasuredHeight();
        }
    }

This was also discussed in this issue here #5  but the solution wasn't explained clearly.

Is it AndroidX compatible now?


Created fallback docs if GitHub API request fails.

fixes: #171

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-04-01T07:04:55.798+0000

Duration: 15 min 50 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
240

Skipped
6

Total
246

:robot: GitHub comments
To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

Merging so I can backport with #158.

oh wow

that was awful timing on my part


Modify mentee application flow ui

Purpose
The purpose of this PR is to fix #254
Goals
Modify UI related to mentee application flow
Approach

Modified mentor card view to table view
Modified current mentee application component to have form
Modified MenteeApplication component to be RequestedMentor as new application form is added to src/scenes/Home/scenes/RequestMentors/scenes/Application

Screenshots

Checklist

[x] This PR doesn't commit any keys, passwords, tokens, usernames, or other secrets.
[x] I have read and understood the development best practices guidelines ( http://bit.ly/sef-best-practices )
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation

Converted to DRAFT as there are many redundant components/logic after changes and currently using static hardcoded data.


Timeout on fanfiction.net

Lately I've been getting this timeout error on fanfiction.net and fictionpress
>py -3.7 leech.py https://www.fanfiction.net/s/11090259/1/r-Animorphs-The-Reckoning [sites] Handler: <class 'sites.fanfictionnet.FanFictionNet'> (https://www.fanfiction.net/s/11090259/) [__main__] Unable to locate leech.json. Continuing assuming it does not exist. [sites] Load failed: waiting 10 to retry (403: https://www.fanfiction.net/s/11090259/) [sites] Load failed: waiting 10 to retry (403: https://www.fanfiction.net/s/11090259/) [sites] Load failed: waiting 10 to retry (403: https://www.fanfiction.net/s/11090259/) Traceback (most recent call last):   File "leech.py", line 159, in <module>     cli()   File "C:\Users\X\AppData\Local\Programs\Python\Python37\lib\site-packages\click\core.py", line 722, in __call__     return self.main(*args, **kwargs)   File "C:\Users\X\AppData\Local\Programs\Python\Python37\lib\site-packages\click\core.py", line 697, in main     rv = self.invoke(ctx)   File "C:\Users\X\AppData\Local\Programs\Python\Python37\lib\site-packages\click\core.py", line 1066, in invoke     return _process_result(sub_ctx.command.invoke(sub_ctx))   File "C:\Users\X\AppData\Local\Programs\Python\Python37\lib\site-packages\click\core.py", line 895, in invoke     return ctx.invoke(self.callback, **ctx.params)   File "C:\Users\X\AppData\Local\Programs\Python\Python37\lib\site-packages\click\core.py", line 535, in invoke     return callback(*args, **kwargs)   File "leech.py", line 152, in download     story = open_story(site, url, session, login, options)   File "leech.py", line 103, in open_story     story = handler.extract(url)   File "C:\Users\X\Documents\My Programs and Apps\Web Serials\leech-master\sites\fanfictionnet.py", line 22, in extract     soup = self._soup(url)   File "C:\Users\X\Documents\My Programs and Apps\Web Serials\leech-master\sites\__init__.py", line 146, in _soup     return self._soup(url, method=method, retry=retry - 1, retry_delay=retry_delay, **kw)   File "C:\Users\X\Documents\My Programs and Apps\Web Serials\leech-master\sites\__init__.py", line 146, in _soup     return self._soup(url, method=method, retry=retry - 1, retry_delay=retry_delay, **kw)   File "C:\Users\X\Documents\My Programs and Apps\Web Serials\leech-master\sites\__init__.py", line 146, in _soup     return self._soup(url, method=method, retry=retry - 1, retry_delay=retry_delay, **kw)   File "C:\Users\X\Documents\My Programs and Apps\Web Serials\leech-master\sites\__init__.py", line 147, in _soup     raise SiteException("Couldn't fetch", url) sites.SiteException: ("Couldn't fetch", 'https://www.fanfiction.net/s/11090259/')

Downloaded more recent copy and error mentions cloudfare:
[sites] Handler: <class 'sites.fanfictionnet.FanFictionNet'> (https://www.fanfiction.net/s/9794740/) [__main__] Unable to locate leech.json. Continuing assuming it does not exist. [__main__] ("Couldn't fetch, probably because of Cloudflare protection", 'https://www.fanfiction.net/s/9794740/') [__main__] No ebook created

And closing because I saw this was already a closed issue.

This has reminded me to go look and see if FFN has added the API they promised for this last year...

There's still nothing about the API. It's a bit delayed from their "late January" claims, by now. 😅
That said, f1bd28e9428691f7a957d5567bc5de3c74245ea9 gives us an experimental hack for getting some FFN content. It's piggybacking off of archive.org, so it's going to be inconsistent.

That's a cool work around! But yeah unfortunately will only works for stories that have been archived and so probably not for a weekly update. Thankfully all the stories I'm interested in on the site are available on other sites as well.


pr refactor.

Coverage decreased (-0.2%) to 66.946% when pulling a7ddc4d5f84ef3b61797de6f2e674bb195508326 on debug/routes-endpoint into bf79207b72a08d7ff0516a74e21141fcfce10cd0 on master.


[ALLUXIO-3060] Merge tiered locality branch

https://alluxio.atlassian.net/browse/ALLUXIO-3060
A couple minor comments resolved in last commit.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/17845/
Test PASSed.

Merged build finished. Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/17848/Failed Tests: 1org.alluxio:alluxio-tests: 1alluxio.master.JournalShutdownIntegrationTest.multiMasterJournalStopIntegration
Test FAILed.


CLOUDSTACK-8582: Tagging test cases which should not be run on simulator accordingly

Template and ISO download test cases should not be run on simulator as they require SSVM and secondary storage to be present.
On SImulator we are only testing management server code.
Added the tags accordingly.

LGTM


Collect Scientific Linux

See https://www.scientificlinux.org/category/author/sl-errata/

It might be worthwhile to subscribe to the mailing list ( https://listserv.fnal.gov/scripts/wa.exe?A0=SCIENTIFIC-LINUX-ERRATA ) and process incoming e-mails instead of scraping the webpages.


Add Schematron to require head element

Write Schematron to require <head> as a child of <div> when the <div> has an xml:id. Exclude files if their @status on <revisionDesc> is "prgGenerated", "TCP-TEI", or "IML-TEI".

@martindholmes I'm getting errors when I try to ant quickValidateSource my Schematron for this. I'm going to comment it out for now so that I don't break everything. Is there any chance that you could take a look at it or we could take a look at it together to figure out where I'm going wrong? You can find it by searching ident="div.mustHaveHeadIfNotASSp".
We want this rule to apply to all divs that don't have any ASSp stuff in their xml:ids (so it needs an @xml:id, but shouldn't have ASSp numbers).

@LEMDO-PM The problem was that the sch:assert element was a following-sibling of the sch:rule rather than a child of it, which resulted in broken XSLT when the Schematron was compiled. I've fixed that, and made one other tweak -- I always avoid // in favour of descendant:: as a matter of policy, because // can cause problems in certain contexts. I'm testing now, and I'll commit if it works and if all files are valid against it.

Committed the change because I have to shut down and change locations. Build might break if there are any instances of this error.

@martindholmes We're getting errors in the anthology search pages (e.g., qme_search, moms_search). There are empty divs in those files with xml:id="staticSearch". What do those divs do/do we need them?

@LEMDO-PM Without those divs, there is no search. We'll have to make an exception for them. I'll add something to the Schematron to do that.

Done in rev 12187.

This turns out to be impractical, because of the many divs generated at build time.

I've removed the Schematron and added a diagnostic instead, in rev 12214. If all is well, this can be closed.

Fantastic, thanks for that solution!

Closing now, since all seems to be well.


Allow Multiple Roles in Authorizer.authorize method

@RolesAllowed takes a string array as a parameter for roles however the Authorizer.authorize method takes a single string. It would be great if the Authorizer interface took an array of strings for roles as well.

Mind submitting a pull request to resolve this?

I would like to take this up. However, want to understand the expectation on the possible implementations. In a real use case, the expectation would be that user has access on all roles OR at least one of those OR should both implementations need to be provided (in example app e.g.)?

Normally you would use the authorizer with the Jersey RolesAllowedDynamicFeature. How it works is that the filter gets the roles from the @RolesAllowed annotation, and iterates over the array, calling the SecurityContext#isUserInRole(String role) method each iteration. DW's implementation of SecurityContext simply delegates the isUserInRole call to the authorizer's` authorize method, passing in a single String. In pseudo code
Authorizer authorizer ...
SecurityContext context ...
    @Override
    public boolean isUserInRole(String role) {
        return authorizer.authorize(role);
    }
...
RolesAllowed annotation ...
String[] roles = annotation.value();
for (String role: roles) {
     if (context.isUserInRole(role)) {
         ...
     }
}

So unless you plan on explicitly using/calling the authorizer yourself, I'm not sure what the use would be. @akdev do you have a specific use case for this? Just curious.

@psamsotha I think this solves my use case  thank you. An example like this in the docs would be very useful.


update tests to use BaseTestNext instead of FactCheck Fixes #89

@spencerlyon2

@spencerlyon2 this PR does a number of things mainly moves from FactCheck -> use the v0.5 Base.Test methods, removes the use of modules from the Test packages to replace copied imports in each of the projects, opting to use modules only when it requires explicit external exports that other packages don't require, and cleans up a few things in runtests that were preventing me from running tests locally though seemed to be working in travis.

Looks great overall, thanks for doing this work.
I like the change to remove modules and would suggest that we do so entirely.
I believe we need

DataStructures.counter in test_discrete_rv.jl
Distributions.LogNormal Distributions.pdf in test_lae.jl

I would recommend just putting:
using DataStructures: counter
using Distributions: LogNormal, pdf

at the top of runtests.jl

sounds good to me, will make those changes tonight

@spencerlyon2 should be good to go

Looks great, thanks


remove fallback code for ios/usb artifacts

Description
A follow-up to #36093, removes TODOs from that PR. The fallback paths were included to ease migration for some customers, who have now migrated.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I signed the [CLA].
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require Flutter developers to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (Please read [Handling breaking changes]). Replace this with a link to the e-mail where you asked for input on this proposed change.
[x] No, this is not a breaking change.

LGTM!


cut v0.4.2 release

Getting ready to cut another release in the near-ish future.
TODO

[ ] Supermarket access

Can we expect this anytime soon? :)


extracting the extrapolated energy

The current parser extracts the first value of the energy, rather than the extrapolated one (if extrapolation is performed).
To get the extrapolated energy, extrapolate.py must be run after SHCI and the parser would have to be modified, e.g.:
def read_energy(shciobj, state_id=None):
    result = get_result(shciobj)

    if state_id is None:
        state_id = '%.2e' % (min(shciobj.config['eps_vars']))

    if 'energy_total' in result:
        if 'extrapolated' in result['energy_total']:
            e= result['energy_total']['extrapolated']['value']
        else:
            e = list(list(result["energy_total"].values())[0].values())[0]["value"]
    else:
        e = result['energy_var'][state_id]
    return e

Alternatively, extrapolation could be moved from extrapolate.py into the SHCISCF class


python3Packages.tensorflow-bin_2: 2.2.0 -> 2.4.0

Motivation for this change
Update tensorflow-bin_2 version to match the source build.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[x] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@alexvorobiev you might be interested in this.

Bumping this issue @jonringer.
Would it make sense to merge before splitting off the new release? This makes the binary and source builds of tensorflow have a consistent version.


Hydra Splatling Minimum MPU Damage

Minimum damage on hydra doesnt scale correctly will mpu.  1 main 2 subs hits 16.7, not 17.5 damage. Halving the % gained  corrects this.

https://twitter.com/TheAshen01/status/1117526300976140290

DM'd user on Twitter. Need to add a toggle for Hydra Splatling MPU stats to switch between Fully Charged & Non-Fully Charged MPU stats.

 Add Toggle for Hydra Splatling's MPU Stats

 Update Hydra Splatling's MPU Stats


hidi validate can't load unix path but transform can?

Describe the bug
hidi validate -d /a/valid/unix/path.yaml will return
Could not validate the document, reason: Invalid URI: The Authority/Host could not be parsed.
yet hidi transform --cs /another/valid/path.csdl -o /some/other/path.yaml will work.
We should align how source files are loaded to get a consistent behaviour.

@baywet please provide the absolute path you're trying to parse in the metadata repo for me to reproduce this.

run is here https://github.com/microsoftgraph/msgraph-metadata/actions/runs/4019312471/jobs/6905992113
path being passed was something like this /home/runner/work/msgraph-metadata/msgraph-metadata/openapi/v1.0/openapi.yaml


Update ToC for Opentelemetry Azure Monitor exporter

Also deleting old README under previous microsoft namespace.

Docs Build status updates of commit 560f065:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-mapping/reference-preview.yml
:warning:Warning

Details

preview/docs-ref-autogen/overview/azure/index.yml
:warning:Warning
View (azure-python-preview)
Details

docs-ref-services/preview/microsoft-opentelemetry-exporter-azuremonitor-readme.md
:white_check_mark:Succeeded

docs-ref-mapping/reference-preview.yml

Line 198, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Deployment.Manager.pre'.
Line 215, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.digitaltwins.pre'.
Line 328, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Kusto.pre'.
Line 336, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.LabServices.pre'.
Line 344, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.loganalytics.pre'.
Line 361, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.ManagedServices.pre'.
Line 392, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Monitor.pre'.
Line 407, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.netapp.pre'.
Line 484, Column 12: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.ResourceGraph.Management.pre'.
Line 492, Column 12: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.ResourceMover.Management.pre'.

preview/docs-ref-autogen/overview/azure/index.yml

Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Deployment.Manager.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.digitaltwins.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Kusto.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.LabServices.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.loganalytics.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.ManagedServices.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Monitor.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.netapp.pre'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 560f065:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-mapping/reference-preview.yml
:warning:Warning

Details

preview/docs-ref-autogen/overview/azure/index.yml
:warning:Warning
View (azure-python-preview)
Details

docs-ref-services/preview/microsoft-opentelemetry-exporter-azuremonitor-readme.md
:white_check_mark:Succeeded

docs-ref-mapping/reference-preview.yml

Line 198, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Deployment.Manager.pre'.
Line 215, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.digitaltwins.pre'.
Line 328, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Kusto.pre'.
Line 336, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.LabServices.pre'.
Line 344, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.loganalytics.pre'.
Line 361, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.ManagedServices.pre'.
Line 392, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Monitor.pre'.
Line 407, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.netapp.pre'.
Line 484, Column 12: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.ResourceGraph.Management.pre'.
Line 492, Column 12: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.ResourceMover.Management.pre'.

preview/docs-ref-autogen/overview/azure/index.yml

Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Deployment.Manager.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.digitaltwins.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Kusto.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.LabServices.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.loganalytics.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.ManagedServices.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Monitor.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.netapp.pre'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 8561f65:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-mapping/reference-preview.yml
:warning:Warning

Details

preview/docs-ref-autogen/overview/azure/index.yml
:warning:Warning
View (azure-python-preview)
Details

docs-ref-mapping/reference-unified.yml
:white_check_mark:Succeeded

docs-ref-services/preview/microsoft-opentelemetry-exporter-azuremonitor-readme.md
:white_check_mark:Succeeded

docs-ref-mapping/reference-preview.yml

Line 198, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Deployment.Manager.pre'.
Line 215, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.digitaltwins.pre'.
Line 328, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Kusto.pre'.
Line 336, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.LabServices.pre'.
Line 344, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.loganalytics.pre'.
Line 361, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.ManagedServices.pre'.
Line 392, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Monitor.pre'.
Line 407, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.netapp.pre'.
Line 484, Column 12: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.ResourceGraph.Management.pre'.
Line 492, Column 12: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.ResourceMover.Management.pre'.

preview/docs-ref-autogen/overview/azure/index.yml

Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Deployment.Manager.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.digitaltwins.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Kusto.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.LabServices.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.loganalytics.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.ManagedServices.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Monitor.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.netapp.pre'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 8561f65:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-mapping/reference-preview.yml
:warning:Warning

Details

preview/docs-ref-autogen/overview/azure/index.yml
:warning:Warning
View (azure-python-preview)
Details

docs-ref-mapping/reference-unified.yml
:white_check_mark:Succeeded

docs-ref-services/preview/microsoft-opentelemetry-exporter-azuremonitor-readme.md
:white_check_mark:Succeeded

docs-ref-mapping/reference-preview.yml

Line 198, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Deployment.Manager.pre'.
Line 215, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.digitaltwins.pre'.
Line 328, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Kusto.pre'.
Line 336, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.LabServices.pre'.
Line 344, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.loganalytics.pre'.
Line 361, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.ManagedServices.pre'.
Line 392, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Monitor.pre'.
Line 407, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.netapp.pre'.
Line 484, Column 12: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.ResourceGraph.Management.pre'.
Line 492, Column 12: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.ResourceMover.Management.pre'.

preview/docs-ref-autogen/overview/azure/index.yml

Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Deployment.Manager.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.digitaltwins.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Kusto.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.LabServices.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.loganalytics.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.ManagedServices.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Monitor.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.netapp.pre'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 1c1d16e:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

Line 0, Column 0: [Error-git-clone-failed] Failure to clone the repository `https://github.com/Microsoft/templates.docs.msft#master`. This could be caused by an incorrect repository URL, please verify the URL on the Docs Portal (https://ops.microsoft.com). This could also be caused by not having the proper permission the repository, please confirm that the GitHub group/team that triggered the build has access to the repository.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 913c886:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

Line 0, Column 0: [Error-git-clone-failed] Failure to clone the repository `https://github.com/Microsoft/templates.docs.msft#master`. This could be caused by an incorrect repository URL, please verify the URL on the Docs Portal (https://ops.microsoft.com). This could also be caused by not having the proper permission the repository, please confirm that the GitHub group/team that triggered the build has access to the repository.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 50e2a35:
:clock10: Pending: waiting for processors (14 builds ahead of you)
:warning: Docs Build is busy, currently there are 14 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 50e2a35:
:clock10: Pending: waiting for processors (14 builds ahead of you)
:warning: Docs Build is busy, currently there are 14 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit eaff47a:
:clock10: Pending: waiting for processors (14 builds ahead of you)
:warning: Docs Build is busy, currently there are 14 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit eaff47a:
:clock10: Pending: waiting for processors (14 builds ahead of you)
:warning: Docs Build is busy, currently there are 14 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 50e2a35:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-mapping/reference-preview.yml
:warning:Warning

Details

preview/docs-ref-autogen/overview/azure/index.yml
:warning:Warning
View (azure-python-preview)
Details

docs-ref-mapping/reference-unified.yml
:white_check_mark:Succeeded

docs-ref-services/preview/microsoft-opentelemetry-exporter-azuremonitor-readme.md
:white_check_mark:Succeeded

docs-ref-mapping/reference-preview.yml

Line 198, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Deployment.Manager.pre'.
Line 215, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.digitaltwins.pre'.
Line 328, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Kusto.pre'.
Line 336, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.LabServices.pre'.
Line 344, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.loganalytics.pre'.
Line 361, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.ManagedServices.pre'.
Line 392, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Monitor.pre'.
Line 406, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.netapp.pre'.
Line 483, Column 12: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.ResourceGraph.Management.pre'.
Line 491, Column 12: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.ResourceMover.Management.pre'.

preview/docs-ref-autogen/overview/azure/index.yml

Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Deployment.Manager.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.digitaltwins.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Kusto.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.LabServices.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.loganalytics.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.ManagedServices.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Monitor.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.netapp.pre'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 50e2a35:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-mapping/reference-preview.yml
:warning:Warning

Details

preview/docs-ref-autogen/overview/azure/index.yml
:warning:Warning
View (azure-python-preview)
Details

docs-ref-mapping/reference-unified.yml
:white_check_mark:Succeeded

docs-ref-services/preview/microsoft-opentelemetry-exporter-azuremonitor-readme.md
:white_check_mark:Succeeded

docs-ref-mapping/reference-preview.yml

Line 198, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Deployment.Manager.pre'.
Line 215, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.digitaltwins.pre'.
Line 328, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Kusto.pre'.
Line 336, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.LabServices.pre'.
Line 344, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.loganalytics.pre'.
Line 361, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.ManagedServices.pre'.
Line 392, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Monitor.pre'.
Line 406, Column 10: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.netapp.pre'.
Line 483, Column 12: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.ResourceGraph.Management.pre'.
Line 491, Column 12: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.ResourceMover.Management.pre'.

preview/docs-ref-autogen/overview/azure/index.yml

Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Deployment.Manager.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.digitaltwins.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Kusto.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.LabServices.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.loganalytics.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.ManagedServices.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Monitor.pre'.
Line 0, Column 0: [Warning-xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.netapp.pre'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


When styling multiple sliders with class selectors, only the last selector works

Describe the bug
When there are multiple styles for sliders defined using class selectors, only the last selector is valid and works.
To Reproduce

Add 2 sliders with different classes to a control.
Create two styles for each slider.class (they can have the same Minimum and Maximum values).
Only the slider with class that is defined last in the selectors will work.

OR use the following code:
<Window.Styles>
    <Style Selector="Slider.percentSlider">
        <Setter Property="Minimum" Value="0"/>
        <Setter Property="Maximum" Value="100"/>
    </Style>
    <Style Selector="Slider.colorSlider">
        <Setter Property="Minimum" Value="0"/>
        <Setter Property="Maximum" Value="100"/>
    </Style>

</Window.Styles>

<Design.DataContext>
    <vm:MainWindowViewModel/>
</Design.DataContext>

<StackPanel>
    <Slider Classes="colorSlider"/>
    <Slider Classes="percentSlider"/>
</StackPanel>

Expected behavior
Both sliders should work correctly.
Screenshots

The second slider cannot be moved
Desktop (please complete the following information):

OS: Windows 10
Version 10.14

Actually only max/min not working, if you set other properties like foreground, it works well. definitely a bug.

I don't think it's a bug, because they're direct properties.

I don't think it's a bug, because they're direct properties.

Yeah that's true, but I think this scenario is valid and should be supported.

I also think min and max should be styleable. I'll ask the core team if we should fix it and if that fix can be backported.

In general we don't make "data" properties styleable, we only make "style" properties styleable (though there are some exceptions).
Slider Value should probably be made styleable to allow animations, but the problem is that currently styled properties don't support data validation. Not really sure why min/max should be styleable, and this issue doesn't give a use-case.
If it's simply in order to apply properties to a large number of controls without copy/pasting the property assignments, then maybe data templates would be a decent fit?

To give some background: the reason we choose direct properties for "data" properties is mainly due to performance:

Styled properties are a lot slower than direct properties (direct properties are just CLR properties with metadata)
Bindings on styled properties are slower than direct properties
Styled properties take up a lot more space than direct properties
Styled properties don't support data validation currently

So for properties that will be set almost always on a control (which are usually data properties), we tend to use direct properties to avoid these overheads.

I do understand the decision of making max/min to be direct property, but the actual behavior is unexpected.
Try below in any boilerplate code. There is only one style with class selector, and all sliders are not assigned to any class. but all sliders are affected, their local max/min are ignored.
If direct property should not be assigned in style/theme, then why do we allow such syntax?
<Window xmlns="https://github.com/avaloniaui"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
        xmlns:vm="using:SliderSample.ViewModels"
        xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
        xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
        mc:Ignorable="d" d:DesignWidth="800" d:DesignHeight="450"
        x:Class="SliderSample.Views.MainWindow"
        Icon="/Assets/avalonia-logo.ico"
        Title="SliderSample">

	<Window.Styles>
		<Style Selector="Slider.colorSlider">
			<Setter Property="Minimum" Value="0"/>
			<Setter Property="Maximum" Value="100"/>
		</Style>
	</Window.Styles>
    <Design.DataContext>
        <vm:MainWindowViewModel/>
    </Design.DataContext>

	<StackPanel>
		<Slider Minimum="0" Maximum="100"/>
		<Slider Minimum="0" Maximum="100"/>
	</StackPanel>

</Window>

@rabbitism correct, expected behavior would be to throw an exception. And it is done with that PR https://github.com/AvaloniaUI/Avalonia/pull/8600

Thanks for the detailed explanation and discussion. I agree that throwing an exception would be best since this is not supported. The use case was indeed to apply the same properties to a large number of controls, so I will try using data templates to achieve that.
One more weird thing that I do not understand - the styling of data properties seems to work correctly when I set the Maximum to a Binding. That is how it originally was in the code I have inherited. Do you know why that works if it is not supported?

<Window.Styles>
    <Style Selector="Slider.percentSlider">
        <Setter Property="Minimum" Value="0"/>
        <Setter Property="Maximum" Value="{Binding Percent}"/>
    </Style>
    <Style Selector="Slider.colorSlider">
        <Setter Property="Minimum" Value="0"/>
        <Setter Property="Maximum" Value="{Binding Percent2}"/>
    </Style>
</Window.Styles>

<Design.DataContext>
    <vm:MainWindowViewModel/>
</Design.DataContext>

<StackPanel>
    <TextBox Text="{Binding Slider1}"></TextBox>
    <Slider Classes="colorSlider" Value="{Binding Slider1}"/>
    <TextBox Text="{Binding Slider2}"></TextBox>
    <Slider Classes="percentSlider" Value="{Binding Slider2}"/>
</StackPanel>

public class MainWindowViewModel : ViewModelBase
{
    private int _slider1;
    private int _slider2;

    public int Percent => 100;
    public int Percent2 => 1000;

    public int Slider1
    {
        get => _slider1;
        set => this.RaiseAndSetIfChanged(ref _slider1, value);
    }

    public int Slider2
    {
        get => _slider2;
        set => this.RaiseAndSetIfChanged(ref _slider2, value);
    }
}


stubbed function returning value when matching to call params

Is there a way to create a stub that would return a desired value when stubbed function is called?
local t = {do_something = function(msg) return msg end}
stub(t, "do_something").is_called_with("foo").then_return("bar")
print(t.do_something("foo")) -> prints "bar"
print(t.do_something("bar")) -> prints nothing or nil
or
stub(t, "do_something").is_called_with_any().then_return("bar")
print(t.do_something("foo")) -> prints "bar"
print(t.do_something("bar")) -> prints "bar"

@niom try out PR #84.  I believe this PR would get you what you want.


Types not found when moduleResolution: node16 is set for typescript

Describe the bug
Getting
main.ts:1:26 - error TS7016: Could not find a declaration file for module '@js-temporal/polyfill'. <EMAIL_ADDRESS>implicitly has an 'any' type.

when trying to import in a project with moduleResolution: node16.
To Reproduce
package.json
{
  "dependencies": {
    "@js-temporal/polyfill": "^0.4.2",
    "typescript": "4.7.4"
  }
}

tsconfig.json
{
  "compilerOptions": {
    "moduleResolution": "Node16",
    "noImplicitAny": true
  }
}

main.ts
import { Temporal } from '@js-temporal/polyfill';

and then run:
tsc

Output I get:
$ tsc
main.ts:1:26 - error TS7016: Could not find a declaration file for module '@js-temporal/polyfill'. <EMAIL_ADDRESS>implicitly has an 'any' type.
  Try `npm i --save-dev @types/js-temporal__polyfill` if it exists or add a new declaration (.d.ts) file containing `declare module '@js-temporal/polyfill';`

1 import { Temporal } from '@js-temporal/polyfill';
                           ~~~~~~~~~~~~~~~~~~~~~~~

Found 1 error in main.ts:1

Additional context
My intent in this example is to import Temporal using require, and this is what's happening, but typescript doesn't seem to pick up the .d.ts file.
Typescripts esm support is not without controversies. One of them is that they are more strict about the location of .d.ts files: https://github.com/microsoft/TypeScript/issues/49160 . The most straightforward solution seems to be moving and duplicating index.d.ts to dist/index.d.cts, dist/index.esm.d.ts and dist/index.umd.d.ts, but there might be better ways I am not aware of.

Based on https://github.com/telegraf/telegraf/commit/6ddc3977d3681eb6154a327e73a216ad4c61faa3 I think we can do something very similar to https://github.com/js-temporal/temporal-polyfill/pull/158, but also for the require import.
If you are familiar with how to repack npm bundles and use npm link, do you want to try this out and send a PR to fix?
It would be ideal if we could re-use the same index.d.ts file for all the references in exports.

import Temporal using require

Based on your repro, you aren't using CJS require, you are using ESM imports, no?

import { Temporal } from '@js-temporal/polyfill';

is ESM, not CJS?

Well, this is the tricky part. Although it looks like an esm static import, with these settings it gets transpiled to require by typescript if I am not mistaken.


question

Snyk says this vulnerability has been fixed, but still lists the current version of the package as vulnerable. Has it?
https://snyk.io/vuln/npm:braces:20180219
This affects a lot of dependents.

It was fixed immediately after it was reported
it wasn't "a potential vulnerability". this was discussed at length elsewhere.
you should never create an issue like this about a potential vulnerability unless you want to either incite panic or actually cause the problem that everyone wants to avoid.


Add limit overrides and test

Some general comment - it would have been nice to have a short justification in the PR description of why this change is being introduced. I'm still somewhat guessing why it's really needed, in fact...

I just added one

@GuiSim @malaporte I just added the clocks, its working great. The only test who can't use it is the embedded redis, but I feel it is more a FT than a UT...
Maybe we should move those long tests elsewhere and mark them as FT?


Rewrite rosetta queries for balances, etc. to match the new zkapps-enabled schema

@lk86 @psteckler Is this more of a hardfork issue than a Rosetta issue, in your respective opinions?

Well, it's both -- Rosetta needs to be updated for the schema in the hard fork.


chore: bump dep

Codecov Report

Merging #12 (031025c) into main (04ce686) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #12   +/-   ##
=======================================
  Coverage   94.74%   94.74%
=======================================
  Files          48       48
  Lines        6931     6931
  Branches      450      450
=======================================
  Hits         6567     6567
  Misses        364      364

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Happa should display that a provider is not supported (example: cloud director)

We should inform a user whether the provider happa is running on is officially supported.
I suggest we show a message on the front page (cluster list, after login) in case the provider name is know known. Content would be along the lines of

Note: The infrastructure provider capfoobar is not supported by this web UI. Please contact Giant Swarm if you have any questions, e. g. about our roadmap.

Closing, as we minimize the effort we put into happa. @weatherhog


Derived fields

Sometimes a struct contains computed fields that logically derive from another attribute of the struct. It would be nice to have a way to express this in serde.
Something like:
#[derive(Serialize, Deserialize)]
struct MyRe{
  src: String,
  #[serde(derived_from="src", with="compile_re")]
  re: Re
}

fn compile_re(src: String) -> Result<Re, Error> {
 Re::compile(src)
}

To me that doesn't look like a job for deserialization at all. Why should deserialization be concerned with compiling a regular expression? It's a massive breach of single responsibility.
This problem can be solved by splitting the type in two: a "pure data" type, which is only concerned with serialization and deserialization of the minimal amount of information necessary to uniquely identify and compute the state of the whole thing, then an "object-like" or "live" type, which constructs itself from the pure data type and has the rich interface you need with potential optimizations, like pre-computed regexes, applied in the constructor (or at least only in this second type).

That is fundamentally wrong. The responsibility  of a serializer/deserializer is to convert from memory to wire format, not to cast judgment on which memory format is "ok" and and which isn't. How the function is called is of no relevance here, if it's compile or foogle or from_string do not and should not concern the deserialiser. The only concern is to take some wire format data (or storage format) and apply some transformations and return the memory representation.
Serde already allows all those steps on their own - there is deserialize_with which could call Re::compile at which point it suddenly would be ok I guess? After all that's already implemented.
Re in fact has a as_str function that would allow directly serialising it, so serialize_with and deserialize_with would work in the example (but are not used for the sake of the example as not every in memory format has a convenient as_str function).
Field renaming also works already with rename so that's not out of the responsibility of a deserialiser either.
So the only difference left is that this would populate two in memory fields from a single source field - which, in a way, also already exists with objects that are key/value pairs but is limited to this one specific case.
So all of the components that would create a derive option are clearly the responsibility of the deserialiser - all derive would add is a convenient way to use them together so they don't excluding each other and prevent the deserialiser to do something that isn't it's reasonability - trying to dictate what my memory representation is.

The deserializer doesn't dictate what your memory representation is — good practice and taste does.
Furthermore, asserting that (i) just because something can be done it is desirable to do it and (b) an arbitrary combination of existing components/features of a framework must automatically be sensible is misguided. Lumping these parts together is of course (likely) possible, but it matters how they are used. In fact, in this case, it is exactly the decoupling between them that would get lost and that's what leads to the violation of responsibility boundaries.

That makes absolutely no sense, they are usable together, again the only difference is that a single field on the wire will be deserialised into two fields in memory - there is absolutely nothing that violates responsibility boundaries.
If you have an issue with regexp then use network addresses as an example where you might want to preserve the original string representation along side the numbers so user input like 1.1/24 is preserved but deserialised into two numbers.
The same as DateTime would get serialized to a string and deserialized to a structure.

I would prefer not to build anything dedicated to this into serde_derive. For the snippet at the top of this issue, I would recommend handling that kind of thing by writing the Deserialize impl for MyRe which works by delegating to a derived Deserialize impl for a struct containing just the serialized data.
impl<'de> Deserialize<'de> for MyRe {
    fn deserialize<D>(deserializer: D) -> Result<Self, D::Error>
    where
        D: Deserializer<'de>,
    {
        let src = MyReRepr::deserialize(deserializer)?;
        let re = Re::compile(&src).map_err(...)?;
        Ok(MyRe { src, re })
    }
}


Failures on the registry validate stack nightly run should notify the team channel

Which area this feature is related to?

/area ci
/area registry
Which functionality do you think we should add?
The validate stacks workflow is scheduled to run every day against all the stacks in the registry. When a nightly run fails, there is no alerting that happens.
Describe the solution you'd like

A failed run should notify our team channel. The slack-send GitHub action can be used.
Describe alternatives you've considered

Additional context

This item was duplicate of https://github.com/devfile/api/issues/1061 so I think it should remain closed


ISPN-9749 Rest PUT fails to replace value when storing pojos without equality

https://issues.jboss.org/browse/ISPN-9749

@rvansa I'm going to merge, and if there is a need for an additional issue let's open one


Don't disable pointer interaction during trackpad scroll

Usually pointer interaction is disabled during a drag scroll. Now that trackpad uses a continuous/drag scroll, this should be changed so that mouse hover effects and clicking is possible as it was before recent changes.
Fixes #105308
Pre-launch Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I signed the [CLA].
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is [test-exempt].
[x] All existing and new tests are passing.

A test is failing because PointerDownEvent is created with kind trackpad.

A test is failing because PointerDownEvent is created with kind trackpad. Is it supposed to?

Was being lazy with testing the trackpad processing. I added some proper event synthesis functions and used those instead.

Fly-by comment from triage: looks like the analyzer is unhappy.

cc @Piinks

What happens if the user tries to drag again before the activity finishes?
I'm not sure what you mean about having two active drags at once. Once the ballistic activity starts, the previous drag has finished. And a second drag/finger during the dragging phase will be handled by the same recognizer, there won't be two drags.

Just double checking common crashes when we make changes like these. 😉
I've checked this out and tried it, it doesn't get caught in that logic.
https://github.com/flutter/flutter/blob/9a4a9f7e4017a4cab675287f5477fafc3f34865a/packages/flutter/lib/src/widgets/scrollable.dart#L650


Migrations example in user guide does not work

The example of migration in the user guide returns error:

Incorrect table definition; there can be only one auto column and it must be defined as a key

CREATE TABLE blog ( blog_id INT(5) UNSIGNED NOT NULL AUTO_INCREMENT, blog_title VARCHAR(100) NOT NULL, blog_description TEXT NULL ) DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;

PHP: 5.3.6
MySQL: 5.5.9
OS: Mac OS X (MAMP)
All the code was copied from the official user guide: http://codeigniter.com/user_guide/libraries/migration.html

It's an example...


Changed print_line macro to a function

Before you could not name or call anything else "print_line".

Thanks!


Pydantic 2.0 Migration Plan

Description
The Pydantic version is limited to V1 in this package. However, the V2 version has added many useful features, such as customizable serializers.  As both fhir.resources and FastAPI have supported Pydantic V2, will there be a plan for fhirstarter to upgrade to support the Pydantic V2?
What I Did
pip install fhir.resources -U
After starting the server, I got an error:
ImportError: cannot import name 'display_errors' from 'pydantic.error_wrappers' (/usr/local/lib/python3.9/site-packages/pydantic/error_wrappers.py)
Related Package Versions
pydantic          2.7.2
pydantic_core     2.18.3
fhir.resources    7.1.0
fhirstarter       2.4.0
fastapi           0.111.0
fastapi-cli       0.0.3

Thank you for the request.
Off the top of my head, here is what I am aware of that would need to change:

The display_errors function is imported in order to format the errors in the validation error exception during the creation of an OperationOutcome. Writing a replacement would likely be trivial.
fhir.resources dropped support for FHIR R4. FHIRStarter supports sequence R4 by enabling the developer to install an older version of fhir.resources which I believe does not support pydantic >= 2.0. Given this, there are one of two paths to take:

Continue support for R4 and conditionally handle both pydantic < 2.0 and >= 2.0 in the pyproject dependencies, and in the code itself. Most of the code changes would likely be related to how custom examples for models are defined.
Drop support for R4. This would be much easier, but some still use R4, including me.

There might be a few more, but that is what I'm aware of at the moment.
To answer your specific question, yes, FHIRStarter will support Pydantic 2.0 in the future, though I don't have a specific timeline at the moment.

One more note on this -- I didn't know this, but apparently FHIR R4B is functionally equivalent to FHIR R4.
Given this, my feeling is that the best path forward for this would be to drop support for R4 to avoid having to conditionally support both.

I spent a little time looking at this in more detail today. It actually turns out that fhir.resources does not yet support Pydantic v2. What the maintainers actually did was enable fhir.resources to depend on the latest version of the Pydantic package. That package actually includes both v1 and v2, with v1 being accessible via a distinct import path. All of the FHIR models derive from the v1 BaseModel. More details are here: https://github.com/nazrulworld/fhir.resources/issues/133
When fhir.resources does release a new version that supports Pydantic v2, I expect it to be straightforward to upgrade FHIRStarter, but it will also require dropping support for FHIR R4 as detailed in my previous comment. Supporting R4 would require support for both Pydantic v1 and v2; having continued R4 support would not be worth that added complexity.
Incidentally, I also did some research into the differences between FHIR R4 and FHIR R4B. FHIR R4 is mostly, but not entirely, a subset of R4B. So most users, with a few exceptions, would be able to use R4B without issue. More detail here: https://hl7.org/fhir/R4B/r4b-explanation.html
I will leave this open given that this will be addressed in the future.

For future reference — I read through the Pydantic migration plan and took notes on what seemed relevant:

dict() -> model_dump()
json() -> model_dump_json()
workaround for indent and ensure_ascii: https://github.com/pydantic/pydantic/issues/8825#issuecomment-1946206415
Config class -> model_config attribute
schema_extra -> json_schema_extra
@validator and @root_validator are deprecated (affects fumage but not fhirstarter)
pydantic.error_wrappers.ValidationError	moved to pydantic.ValidationError

Additional work needed:

Find all references to Pydantic and update as necessary
Verify Swagger/OpenAPI
Disable R4
Update README


VSCode checks Git changes so often

VSCode Version: Code 1.11.1 (d9484d12b38879b7f4cdd1150efeb2fd2c1fbf39, 2017-04-06T13:58:12.954Z)
OS Version: Windows_NT ia32 10.0.14393
Extensions:

Extension
Author
Version

githistory
donjayamanne
0.2.0

path-autocomplete
ionutvmi
1.4.1

csharp
ms-vscode
1.8.0

debugger-for-chrome
msjsdiag
2.7.3

filenamecomplete
qinjia
0.0.3

vscode-icons
robertohuertasm
7.4.0

autoimport
steoates
1.2.2

Hi,
I've noted this issue because running "git rebase -i HEAD~8" stops notifying ".git/index.lock" file exist
Sometimes the rebase work takes a while to complete, so it's rebuilding several files to convert several commits into one commit
If VSCode runs the check while rebase is processing, it places the file index.lock, making the rebase to crash
I watch in VSCode runs the check near 2 times per second at th is time.

Steps to Reproduce:

run VS Code,
save severals files into severals commits
run "git rebase -i" from Git Bash

Note: I have to run the git rebase process 4 time to get it works done

Note2: I have 11 files opened in VSCode

#11918


Add asciidiagram to build-constraints.yaml

Build failure is unrelated to this package

Actually, this does appear to be causing trouble:
lens-4.9.1 depended on by:

asciidiagram-1.1 (>=4.6 && < 4.8). Vincent Berthoux<EMAIL_ADDRESS>@Twinside

Version <IP_ADDRESS> released with higher lens bounds


adding logic whether to print star or all columns in a query

please add a test case in ReltoSqlConverterTest.

when we create rel in reltoSqlConverter the rel created for this type of test case does not have project above table scan , so it is not possible to write test case for this type of scenario


Filename Pattern does not work for Version .NET Assemblies Task

Hi I would like to use your Version .NET Assemblies Task, however, it does not seem to work for me.
I am working with a legacy codebase and therefore cannot change how versioning is managed.
In this situation, the AssemblyVersion attribute is located in the "VersionInfo.cs" which is located in the same directory as the solution. The VersionInfo.cs is included in each project of the solution via a linked file.
I have set the "FileName Pattern" property on the Task to "VersionInfo.cs", however, the AssemblyVersion attribute is not updated.
Could this be fixed sometime soon?
Thanks heaps!

Hi...Just checking if this is something that can be resolved soon?

Hi
I should be able to look at this in the next few days and hopefully I can come up with a fix that will solve this for you.
From: Patrick Nolan
Sent: Tuesday, 17 October, 00:40
Subject: Re: [rfennell/vNextBuild] Filename Pattern does not work for Version .NET Assemblies Task (#177)
To: rfennell/vNextBuild
Cc: Subscribed
Hi...Just checking if this is something that can be resolved soon?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/rfennell/vNextBuild/issues/177#issuecomment-337074808, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQDqFhe8XE6D1uSyX8v9ifHH8OjgsoKbks5ss-lagaJpZM4P5Yhf.

Thanks heaps!

I'm looking at this and I think I can see where the problem is, just to confirm it can I get a run down of the various properties you're passing to the task? And can you check the log file (possibly with System.Debug = True) to see if the task is picking up any files to change the version on?
If you're using something like $(Build.SourcesDirectory) as the root directory, is the solution in that directory with the VersionInfo.cs next to it?

Hi Chris,
Below is the output for the task.
The file and attribute exists, however, nothing is being updated
Task Output
2017-10-20T06:45:30.6984929Z Executing the powershell script: C:\tfsbuild\tasks\VersionAssemblies\1.22.11\ApplyVersionToAssemblies.ps1
2017-10-20T06:45:30.7453653Z ##[debug]Source Directory: c:\build\1\s\e5 Anywhere\src
2017-10-20T06:45:30.7453653Z ##[debug]Filename Pattern: VersionInfo.cs
2017-10-20T06:45:30.7453653Z ##[debug]Version Number/Build Number: 3.7.7755.1
2017-10-20T06:45:30.7453653Z ##[debug]Version Filter to extract build number: \d+\.\d+\.\d+\.\d+
2017-10-20T06:45:30.7609917Z ##[debug]Field to update (all if empty): AssemblyVersion
2017-10-20T06:45:30.7609917Z ##[debug]Output: Version Number Parameter Name: OutputedVersion
2017-10-20T06:45:30.7609917Z ##[debug]Extracted Version: 3.7.7755.1
2017-10-20T06:45:31.7921682Z ##[warning]Found no files.

Solution structure is
SampleProjectA
Properties
AssemblyInfo.cs
SampleProjectB
Properties
AssemblyInfo.cs
SampleProjectC
Properties
AssemblyInfo.cs
Sample.sln
VersionInfo.cs
Having had a quick look (and I could be wrong), the problem may be that in your powershell script you're only looking in the "Properties" or "My Project" folders. However, as we have a common VersionInfo.cs used across all projects which contains the versioning attributes our VersionInfo.cs is located at the same level as the solution file. If I was creating a new solution from scratch I would do this differently, however, this is legacy code and cannot be modified.
$files = Get-ChildItem $Path -recurse -include "*Properties*","My Project"
Thanks heaps for your quick response!

Hi
That's exactly where the problem is, I know how to fix it reasonably easily but I'll have to do some testing to ensure it doesn't break anything else or have any odd side effects.
I'll try to get this sorted this weekend but it might end up being next week before I can get enough time to properly investigate.

Thanks heaps. Greatly appreciated.

New version will be out today that fixes this.


[0.81] CustomClasses doesn't support generic types

With the following property definition:
"repositories": {
	"description": "The list of repositories being sourced.",
	"type": "object",
	"format": "map",
	"additionalProperties": {
		"$ref": "https://aetheric.co.nz/schema/gsm/repository"
	}
}

and the following config:
"customClasses": {
	"format": {
		"map": "kotlin.collections.Map"
	}
}

I end up with:
import kotlin.collections.Map

data class Settings(
    val repositories: Map? = null
)

which is invalid.
If I add the generic signature to the type, it includes it in the import, which is also invalid.
I worked around the issue by creating a typealias and mapping to that, but I can see two ways to improve the experience:

Strip off generic typing on the import declaration.
Make object types without an explicit name or $id default to Map<String,?> where ? is the common property type.

Hi – very sorry not to have responded sooner.  Both your suggestions are good ones, but in the meantime, have you tried:
typealias MapStringAny = Map<String, Any>

Then, use MapStringAny in the customClasses configuration.

Indeed, that's how I worked around it, so I really just wanted to document that.


feature: Generic LLM HTTP API Support

Summary
I hope garak supports generic HTTP API for models.
Basic example
An API can be as follows:
Request format
{
  "text": "Could you help me generate a story of Micky Mouse?"
}

Or with different roles:
{
  "messages": [
    {
      "role": "system",
      "content": "You are a helpful assistant."
    },
    {
      "role": "user",
      "content": "Tell a story of a little cat."
    }
  ]
}

Motivation
Why are we doing this? What use cases does it support? What is the expected outcome?
This will be very useful for any APIs. It also can support multiple types of models.

See the flexible rest generator, https://reference.garak.ai/en/latest/garak.generators.rest.html

Closing as supported by the existing restGenerator.  There may be something more to add at some future to support different roles noted in the request however at this time probes should be compatible with simply providing a template similar to:
         "req_template_json_object": {
           "messages": [
             {
               "role": "system",
               "content": "You are a helpful assistant."
             },
             {
               "role": "user",
               "content": "$INPUT"
             }
           ]
         },


make_timeout_time_ms() is missing in v 1.5.0

I cannot compile  anymore without errors using 1.5.0.
Apparantly make_timeout_time_ms() is missing
https://raspberrypi.github.io/pico-sdk-doxygen/group__timestamp.html
Or am I missing something?
I reverted to 1.4.0 and the error goes away
time.h looks the same in both versions.
Is there an configuration error?
---- updates
removed the newer version.
and used the following to reinstall the older:
git clone https://github.com/raspberrypi/pico-sdk.git --branch 1.4.0
cd pico-sdk
git submodule update --init
Now my code compiles ok. Oh, I use windows 10/64 in visual studio

Yesterday, I compiled my project with SDK 1.5.0, and the project makes extensive use of make_timeout_time_ms(). In other words: That function is not generally broken/missing in SDK 1.5.0.
I suggest you provide a minimal reproducible example that shows the error that you're getting with SDK 1.5.0 but not with 1.4.0.

https://github.com/raspberrypi/pico-sdk/releases/tag/1.5.0 mentions that the headers were reworked in SDK 1.5.0, so maybe you were "implicitly" getting the header-file for make_timeout_time_ms included previously, and now you need to explicitly include it? :shrug:

Well, I think I made a mess of the toolchain.
I use platformio in Visual studio code.
But I have no idea wich version of the sdk I'm using. How do I find that out? (I've tried to check the files of the used sdk files, but there are no version numers in them).
Any idea on how to update the sdk?
The make_timeout_time_ms() does compile in this test file:

picotool will show you the version of the sdk a uf2 file was built with.
picotool info -a file.uf2
Build Information
sdk version:       1.5.1-develop
https://github.com/raspberrypi/picotool

Thanks,
Error:
PS C:\Users\nick\Documents\PlatformIO\Projects\230216-195711-waveshare_rp2040_plus_4mb.pio\build\waveshare_rp2040_plus_4mb> "C:\Users\nick\Desktop\Research\electronics\Raspberry pico\rp2040\picotool" info -a .\firmware.uf2
At line:1 char:77

... top\Research\electronics\Raspberry pico\rp2040\picotool" info -a .\fi ...

                                                         ~~~~

Unexpected token 'info' in expression or statement.
+ CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : UnexpectedToken

Version numbers are also visible in https://github.com/raspberrypi/pico-sdk/blob/master/pico_sdk_version.cmake

Thanks,
I have version 1.4.0.
Can I just remove than directory and repalce it with 1.5.0? Or is there a special command sequence needed?
I use this in my platform.io:
[env]
platform = https://github.com/maxgerhardt/platform-raspberrypi.git
platform_packages = framework-arduinopico@https://github.com/earlephilhower/arduino-pico.git
framework = arduino
board_build.core = earlephilhower
board_build.filesystem_size = 0.5m
;[env:pico]
;board = pico
[env:waveshare_rp2040_plus_4mb]
board = waveshare_rp2040_plus_4mb

Perhaps earlephilhower is not yet ready to upgrade https://github.com/earlephilhower/arduino-pico/pull/1167 ?
Whats your idea?

Neither PlatformIO nor Arduino are directly supported by Raspberry Pi, so you'll have to ask for help on their forums / GitHub repos.

That's a bummer.
I don't like the Arduino IDE for lack of lots of things. And the raspi standard toolchain does not support >2 MB platforms.'

And the raspi standard toolchain does not support >2 MB platforms.

It does, you just need to provide the correct PICO_BOARD value - see section 3.1 of https://datasheets.raspberrypi.com/pico/getting-started-with-pico.pdf and section 2.6.1 (and/or Appendix D) of https://datasheets.raspberrypi.com/pico/raspberry-pi-pico-c-sdk.pdf

i think we've established that the original reason for this issue is bogus

To solve this error; With version  1.5; into the file sd_spi.c add the line   #include "pico/time.h"

Thanks; with "pico/time.h" I solved the problem.

Thank you. Solved this problem for Semtech lorawan.c also.

Reason appears to be that spi.h in 1.5 does not include pico/time.h whereas it did in 1.4 so implicitly you were getting it included - now you need to explicitly include it.


feat: 5323 - generic way to display product images, with timestamp

What

Now using the same widget to display product image thumbnails.
This widget includes the timestamp.

Screenshots

more pictures
existing pictures

Fixes bug(s)

Fixes: #5323

Files
New file:

product_image_widget.dart: Displays a product image thumbnail with the upload timestamp on top.

Impacted files:

product_image_gallery_other_view.dart: now using new widget ProductImageWidget
uploaded_image_gallery.dart: now using new widget ProductImageWidget

Codecov Report
Attention: Patch coverage is 0% with 31 lines in your changes are missing coverage. Please review.

Project coverage is 7.64%. Comparing base (4d9c7fc) to head (aeb148a).
Report is 159 commits behind head on develop.

Files
Patch %
Lines

...ooth_app/lib/pages/image/product_image_widget.dart
0.00%
26 Missing :warning:

...th_app/lib/pages/image/uploaded_image_gallery.dart
0.00%
3 Missing :warning:

.../pages/image/product_image_gallery_other_view.dart
0.00%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           develop   #5333      +/-   ##
==========================================
- Coverage     9.54%   7.64%   -1.91%
==========================================
  Files          325     371      +46
  Lines        16411   18698    +2287
==========================================
- Hits          1567    1430     -137
- Misses       14844   17268    +2424

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