[SPARK-8848] [SQL] [WIP] Refactors Parquet write path to follow Parquet format spec

This PR refactors Parquet write path to follow parquet-format spec.
Major changes include:

Replaces RowWriteSupport and MutableRowWriteSupport with ParquetWriteSupport

Uses ArrayData, MapData, and SpecificMutableRow internally to minimize boxing costs
Eliminates per value data type dispatching costs via prebuilt composed writer functions
Supports legacy mode which is compatible with Parquet format used by Spark 1.4 and prior versions

Migrates large decimal precision write support introduced in #7455

Removes more old Parquet support code

Renames Catalyst* classes under parquet package to Parquet*
Although the original names conform to Parquet data model conventions, they are not intuitive to Spark SQL developers. Considering this piece of code will be read by more SQL devs rather than Parquet devs, we decided to rename them.

Renames spark.sql.parquet.followParquetFormatSpec to spark.sql.parquet.writeLegacyParquetFormat, and turns it off by default.
As pointed out by @rdblue, the original option name looks confusing since there's no intuitive reasons to not follow the spec.

Addresses some PR comments in #6617 made by @rdblue

TODO

[ ] More tests for standard mode and turn on standard mode on by default

[ ] Fixes Parquet log redirection
The old Parquet log redirection code path was buggy and only tries to suppress Parquet logs (written using `java.util.Log`). This PR simply removes it together with old Parquet code. Better solution should be using SLF4J to redirect Parquet internal logs. This might be done in a follow-up PR though.

Merged build triggered.

Merged build started.

Test build #38479 has started for   PR 7679 at commit 9f35aac.

Test build #38479 has finished for   PR 7679 at commit 9f35aac.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #38504 has started for   PR 7679 at commit 5285243.

Test build #38504 has finished for   PR 7679 at commit 5285243.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Build triggered.

Build started.

Test build #38538 has started for   PR 7679 at commit 70af37c.

Test build #38538 has finished for   PR 7679 at commit 70af37c.

This patch fails Spark unit tests.
This patch does not merge cleanly.
This patch adds no public classes.

Build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #38540 has started for   PR 7679 at commit fc35aa4.

Test build #38540 has finished for   PR 7679 at commit fc35aa4.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Merged build triggered.

Merged build started.

Test build #38543 has started for   PR 7679 at commit 1e11412.

Merged build finished. Test FAILed.

Test build #38543 has finished for   PR 7679 at commit 1e11412.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build triggered.

Merged build started.

Merged build finished. Test FAILed.

Test build #38544 has started for   PR 7679 at commit 925ce84.

Test build #38544 has finished for   PR 7679 at commit 925ce84.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #38547 has started for   PR 7679 at commit bb34aa4.

Test build #38547 has finished for   PR 7679 at commit bb34aa4.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #38706 has started for   PR 7679 at commit a6c1502.

@rtreffer It would be great if you can help reviewing decimal related parts of this PR. I further refactored the original decimal writing code, which is now moved to CatalystWriteSupport. Another important fact to notice is that we've recently removed unlimited decimal type and restricted max decimal precision to 38.

Merged build triggered.

Merged build started.

Test build #38713 has started for   PR 7679 at commit 149ac5e.

Test build #38706 has finished for   PR 7679 at commit a6c1502.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test build #38713 has finished for   PR 7679 at commit 149ac5e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

@rdblue This should be my last major piece of refactoring related to parquet-format spec.
@viirya @saucam There are relatively few people in the community who are familiar with all of Spark SQL, Parquet, and Scala. So please feel free to comment :)
Thank you all in advance!

Merged build triggered.

Merged build started.

Test build #38733 has started for   PR 7679 at commit b40848a.

Test build #38733 has finished for   PR 7679 at commit b40848a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Merged build triggered.

Merged build started.

Test build #38835 has started for   PR 7679 at commit 136c9c2.

Test build #38835 has finished for   PR 7679 at commit 136c9c2.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

@liancheng I can transfer tables from mysql -> parquet, including unsigned bigint -> DECIMAL(20) (YEAH!).
I couldn't find any problems by reading the code (yet).

@rtreffer Cool, thanks for the review! I know that there still lacks sufficient compatibility tests for decimals. Will try to add more comprehensive Parquet compatibility tests during Spark 1.5 QA phase (starting next week).

Merged build triggered.

Merged build started.

Test build #39208 has started for   PR 7679 at commit d84fe92.

Test build #39208 has finished for   PR 7679 at commit d84fe92.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #39212 has started for   PR 7679 at commit bb64487.

Test build #39212 has finished for   PR 7679 at commit bb64487.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #39218 has started for   PR 7679 at commit f5006bf.

Test build #39218 has finished for   PR 7679 at commit f5006bf.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Merged build triggered.

Merged build started.

Test build #39362 has started for   PR 7679 at commit 5127b8d.

Test build #39362 has finished for   PR 7679 at commit 5127b8d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Merged build triggered.

Merged build started.

Test build #39422 has started for   PR 7679 at commit 66419b7.

Merged build triggered.

Merged build started.

Test build #39423 has started for   PR 7679 at commit 6bda94b.

Test build #39422 has finished for   PR 7679 at commit 66419b7.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test build #39423 has finished for   PR 7679 at commit 6bda94b.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Merged build triggered.

Merged build started.

Test build #39546 has started for   PR 7679 at commit 679888a.

Test build #39546 has finished for   PR 7679 at commit 679888a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

1.5 code freeze deadline already passed, and this issue wasn't targeted to 1.5 anyway, so I'm not going to get this merged to branch-1.5. The other thing is that, I squeezed too many changes into this single PR. Will split it into multiple ones to ease review. But I'm leaving it open for now to make sure all changes merge cleanly and pass tests.

I'm closing this. Will break it into several smaller PRs.


Deprecate schema keys with Upper case letter

Enhancement summary
Find any keys with uppercase  in eos_cli_config_gen and eos_designs schemas and deprecate in favor of lower case.
Ex. vxlan_interface.Vxlan1 -> vxlan_interface.vxlan1
Which component of AVD is impacted
eos_designs, eos_cli_config_gen
Use case example
Ex. vxlan_interface.Vxlan1 -> vxlan_interface.vxlan1
Describe the solution you would like
deprecate the keys in favor of lower case.
Describe alternatives you have considered
No response
Additional context
No response
Contributing Guide

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

There is only Vxlan1 which need to be deprecate all others are already deprecated.


Can't load standard library from sysroot when toolchain is overridden

As the title suggests, when I override the toolchain used via rustup override set 1.46.0, rust-analyzer can no longer load the workspace, with the error can't load standard library from sysroot.
I've run rustup component add rust-src as well as rustup component add rust-src --toolchain 1.46.0-x86_64-unknown-linux-gnu.
I have verified that the source code exists in both $HOME/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust and $HOME/.rustup/toolchains/1.46.0-x86_64-unknown-linux-gnu/lib/rustlib/src/rust.
The toolchain was added with rustup toolchain add 1.46.0
rust-analyzer version: rust-analyzer 8e9ccbf97 2022-01-03 stable
rustc version: (eg. output of rustc -V)
rustc 1.57.0 (f1edd0429 2021-11-29) (default, works)
rustc 1.46.0 (04488afe3 2020-08-24) (override, does not work)

Rust changed the organization of the source directory a while ago. Rust-analyzer only supports the new organization. Rustc 1.46 still uses the previous organization.

Thanks for the quick reply. It could use a better error message if it's possible to detect this issue, but feel free to close this issue if it doesn't seem worth doing.

I think we can close this. The message is technically correct, but we can't tell why we can't find the libraries unless we special-case the pre-1.46 directory structure. Since nominally only the latest stable is supported, that's probably not worth it.


./jq doesnt work on windows

Try to use ./jq module of ur plugin and it said that "jq tool is not available on your system". But i now that it is. But what more interesting - it works early in 2014. Try to analyse your sources and find that this code
s = subprocess.Popen(["jq", "--version"],
                         stderr=subprocess.PIPE,
                         stdout=subprocess.PIPE)

calls an error "WinError6"
And find this python issue report
And it solves a problem in my case:
s = subprocess.Popen(["jq", "--version"],
                         stdin=subprocess.PIPE,
                         stderr=subprocess.PIPE,
                         stdout=subprocess.PIPE)

I am new to Sublime, and I want to set this up as well. It is not working for me either, with the same error.
Where can I find the fix you mentioned? I am using Sublime Build 3065.

@DrStrangepork,  to apply my fix you need to install SublimePrettyJson plugin from sources and edit PrettyJson.py file in line 32. Paste my snippet instead.

Works, thanks!

added stdin into plugin


Update mockito-core to 3.7.7

Updates org.mockito:mockito-core from 3.6.28 to 3.7.7.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.mockito", artifactId = "mockito-core" } ]

labels: test-library-update, semver-minor

Superseded by #165.


Way to describe dependency/definition content from kubectl

Currently we can just get objects that were created using 3rd party resource. For better UX we should be able to describe them too.
This issue is not strictly bound to AppController itself, but it really improves UX of it.
It requires improvements in kubectl for 3rd party resources.

Is there a reason why you chose to use ThirdPartyResource rather than annotations?

@bgrant0607 Initially we wanted to use annotations but then we discovered that 3rd party resources are better for us.  The reason is simple, to separate deps from k8s object definitions. It allows to modify deps without touching k8s object definition. It adds some complexity obviously. The more complex scenario the more natural that separation is. It also makes unified UX for existing and new objects.

@bgrant0607 the problem with annotations is that it requires an object to annotate. If we created a pod, it would be too late to annotate it with it's dependencies, because it would already be created and running.

https://github.com/kubernetes/community/pull/122


neomutt module

Add a new module for neomutt.
I'm still in the process of testing if all my use cases are handled by this module, but in the meantime if you could have a look over if there is something obvious.
I tried incorporating rycees guidance on the previous pull requests as well.

This might actually be sort of overlapping with #225 but is a bit more self-contained.

I have converted all of my mutt configurations to use this module. Seems to work at least for me.

Wow, impressive! I made a few comments but will need some more time to have a thorough look.
Ping for mail guru @teto as well 🙂

I quickly edited the docs and file locations, give me some time to test these changes tomorrow and I'll also squash the commits back.

And as for the #225 I think this might work well as an underlying primitive for the all-encompassing mail configuration.

Still works :+1:

@MasseR @rycee How do you want to proceed about this ? The goal of the mail PR is exaclty not to have to define MXA-specific (MUA/MRA/MTA) specifics. If we merge this now than we might have to break the API later.
Maybe I can strip down my PR of what is controversial if @MasseR is ok to rework the neomutt configuration to adopt the generic framework ? As the API might change with additionnal feedback/MUA/MRA/MTAs maybe we can do this in a "mail" branch and once it's a bit more tested merge it back to master.

At least I find it extremely valuable to have the ability to do MUA/MRA/MTA specifics. Even if I didn't want to tailor my getmail/fetchmail specifically, I still want to configure neomutt to my liking.
I see value in having best of both worlds. General stuff for the well general stuff, but also program specific stuff for the nitty gritty details.
For the record, this is pretty much how I generalize my configuration between machines right now:

I have a non-committed credentials.nix that contains the specifics for a given environment
I have a committed mail.nix that uses the credentials.nix for server specific stuff, but sets up mutt and mbsync with the shared config as well as nitty gritty details.

# credentials.nix
{
  name = "John Doe";
  smtp_user = "john.doe";
  smtp_password = "`gpg --decrypt foo.gpg`"
  smtp_url = "smtp.gmail.com";
  imap_user = "john.doe";
  imap_password = "`gpg --decrypt bar.gpg`";
  imap_url = "imap.gmail.com";
  mailboxes = [ "INBOX" "nix" "haskell" ];
}

# mail.nix
{config,pkgs,...}:
let credentials = import ./credentials.nix;

in

{
  programs.mutt = {
    enable = true;
    imap = {
      enable = true;
      url = credentials.imap_url;
      user = credentials.imap_user;
      ...
    };
    smtp = {
      ...
    };
    sidebar = {
      ...
    };
    binds = [ ... ];
    macros = [ ... ];
    theme = ./theme;
    mailboxes = credentials.mailboxes;
  };
  programs.mbsync = {
    # pending for conversion to the newish home-manager module, but would use the imap username, password, url and mailboxes
  };
  programs.getmail = {
    # On one of my other machines I don't want to use mbsync, I use getmail instead
    retriever = {
     user = credentials.imap_user;
     ...
    };
  };
}

I see value in having best of both worlds. General stuff for the well general stuff, but also program specific stuff for the nitty gritty details.

That's the idea. The main goal is to factorize the account invariants such as login/password/gpg key/signatures details so that can switch between different programs without grind.
I can't bear having to repeat server details across neomutt/vdirsyncer/offlineimap/mbsync/astroid/alot. So in your example this would only concern this part that could be moved to an accounts attrset
    imap = {
      url = credentials.imap_url;
      user = credentials.imap_user;
      ...
    };
    smtp = {
      ...
    };

Yeah. IMO either leave the responsibility of using the accounts attrset to the caller, or have an overrideable value in the neomutt configuration.
Few things to consider

I prefer not having passwords in the nix store -> use a password command if only supported
Some applications have a different style for using commands

mutt: quoted backticks
mbsync: a field with a plus prefix and quotes PassCmd +"gpg --decrypt foo.gpg"
getmail: a tuple of cmd and arguments password_command = ("gpg", "--decrypt", "foo.gpg")

With the exception of passwords, using the values from your accounts attrsets in these program/service primitives would be easy to add, even later on.
So in short, my recommendation is to have these few programs as primitives that use your account attrset once it's eventually merged. This change would be done either by you or me.

Howdy. Was thinking about this over the weekend and put together #295 as a sort of proof of concept. It's not very fleshed out but I'm hoping the general idea is flexible enough to allow general mail account configuration while still allowing detailed per-program configuration without making the mail module itself too cluttered.

@MasseR @teto I have merged an initial email infrastructure setup to master now.
I included two modules, notmuch and mbsync, as example usage. I've also reworked the neomutt module of this PR to use the new email module: #300

cool ! Thanks for the work on the account module. I've started looking into it and adapted the msmtp module. I am now looking at upgrading the alot plugin and how to deal with multiple accounts. My previous PR did current . When looking at the new notmuch/neomutt package, I notice that every account seems recorded in the same file ?  I liked having one configuration per account ( also because some software won't support several accounts per config file). For neomutt can you switch between accounts defined in the same config ?
Also the pattern to enable per-application is to add booleans like myMailAccount.application.enable = true;. I wonder if it wouldn't be better from a discovery standpoint to have mail applications accept instead an "accounts" option (that defaults to all accounts). This way it gets picked up by the documentation generator (unlike now).

Seems like it is in fact already discoverable, my bad:
+    accounts.email.accounts = mkOption {
+      options = [
+        {
+          neomutt = {
+            enable = mkOption {

Now I wonder about to generate the commands called by the mua for the mra/mta.
should we add neomutt.mta = mkOption {   type = types.enum [ "msmtp" ]; } ?

@teto Thanks for the feedback. Yeah, I considered having something like, e.g., programs.notmuch.accounts but eventually opted against it since I found it more natural to have everything center around the account and the account configuration rather than the programs. I believe it also allows the programs to more easily make use of the "flavor" option.
About the single vs. multiple configurations I had a look at different ways to do it and checked the documentation of mbsync, notmuch, and neomutt. It seems to me that the idiomatic way to set up multiple accounts in these programs is to have a single configuration. My hypothesis here is that one should easily be able to work with multiple accounts from the same program session whenever possible. For example, to search across all accounts in a single notmuch query or to switch between accounts in neomutt without having to restart it. Note, the PR I set up for neomutt has basic support for multiple accounts.
From what I can tell msmtp also supports multiple accounts in one configuration and will choose based on the From field. But yeah, I guess plenty of programs still only support one account at a time and then I think having multiple configs is perfectly fine.
About neomutt and configuration of mta I can think of two reasonable designs,

Automatically using msmtp if accounts.email.accounts.<name>.msmtp.enable = true, otherwise use the builtin SMTP support, or

Have an option accounts.email.accounts.<name>.neomutt.mta of type enum [ "builtin" "msmtp" ], defaulting to "builtin".

@teto My understanding of Notmuch is that everything is done with tags 🙂 So in your case I think something like
{
programs.notmuch.new.tags = [ "new" ];
programs.notmuch.hooks.postNew = ''
  notmuch tag +personal -- tag:new and \<EMAIL_ADDRESS>or<EMAIL_ADDRESS>\)
  notmuch tag +professional -- tag:new and \<EMAIL_ADDRESS>or<EMAIL_ADDRESS>\)
  notmuch tag +inbox +unread -new -- tag:new
'';
}

would be the idiomatic way to distinguish between private and professional email. If you prefer wrapper scripts then they could inject the tag into the search query, something like
#! /usr/bin/env bash
cmd="$1"
shift
notmuch $cmd tag:personal and \("$@"\)

perhaps.

I thought about that and even though I might end up using a single db, here are some points:

my  impression is that the notmuch config can contain only one identity (realName) but I don't want to use my real name for personal mail
my mua alot is not capable of switching between different files
Keeping pro/perso in separate databases is a good way to  prevent mistakes upon contact completion, uninteresting results in research etc. Enforcing the separation would force me to add labels for every mail/search...
I think keeping separate databases should be possible, maybe via an option.

Yeah, notmuch is a bit limited in that it only handles one name. On the other hand, I had a look at the notmuch source code and the name doesn't seem to be used very much. The only serious use I saw was in the notmuch reply functionality, which uses it to construct the From field. I don't know how frequently used the reply command is, do you use it?
About "my mua alot is not capable of switching between different files" I'm not certain what you mean. FWIW I had a look at the alot manual and it does seem to have support for accounts, at least and per-account address books.
In any case, I have no issue against notmuch being configurable to optionally support separate configuration files per account. But I guess the design has to be quite careful. I don't want the modules to gain much in complexity. For example, if alot is added, how should it be set up to cope with the two cases? Same if notmuch support is added to the neomutt module or a future Emacs notmuch configuration…

closing in favor of https://github.com/rycee/home-manager/pull/300 (to reduce confusion).


Wording seems off

This sentence reads:
"Usually, the script with start with one or more sources followed by many transformations and ending with one or more sinks."
I think it should read:
"Usually, the script will start with one or more sources followed by many transformations and ending with one or more sinks."

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

ID: 1a1e4332-203f-14fb-f023-458c9f086a1f
Version Independent ID: e9ec2d22-a220-d1e8-57af-a4e9d975b132
Content: Mapping data flow script - Azure Data Factory
Content Source: articles/data-factory/data-flow-script.md
Service: data-factory
Sub-service: data-flows
GitHub Login: @kromerm
Microsoft Alias: nimoolen

The PR for the fix has been created and it will be merged soon. Thanks again for pointing this out, I am closing the issue based on this update, please let us know if there is something else that we can help you with.


-a option is used for "--auth" and for "--all"

I'm not sure which option is best, instead of -a -all.

I didn't see there is a PR about this: https://github.com/dogsheep/pocket-to-sqlite/pull/7

Great catch, thanks.
I'm going to use it to mean --auth - since other tools in the Dogsheep family have the same convention.
--all will be the only way to specify all.

Just saw that's what you implemented here!

#7


Remove ast.unparse and removeprefix usage for better compatibility with older python versions

Description
We have identified that those two methods (str.removeprefix and ast.unparse) stop us from supporting python versions < 3.9. As version 3.7 is still officially supported for at least another 17 months (according to https://endoflife.date/python) we want to support that version too.
Pull Request Type

[x] Xpipes Core (Jupyterlab Related changes)
[ ] Xpipes Canvas (Custom RD Related changes)
[ ] Xpipes Component Library
[ ] Documentation
[ ] Others (Please Specify)

Type of Change

[x] Refactoring
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Tests

Manual test for same output as before

Start jupyter lab
get output at
http://localhost:8888/xpipes/components/
Check it is still the same as previously

Tested on?

[x] Windows
[ ] Linux Ubuntu
[ ] Centos
[ ] Mac
[ ] Others  (State here -> xxx )

Testing with py38:
it appears to follow the same error with
AttributeError: 'Index' object has no attribute 'lineno'

After more investigation, it appears that the change has only been introduced in py39 as per this issue in another repo.
Bright side is if this can be updated, py37 should be compatible as well (To which I guess I'll have to update my print statements...).

As https://github.com/XpressAI/xircuits/pull/161 has enabled the older python compatibility, I'm going to close this PR. Thanks for helping out!


When UI fails redirect to services status

in case UI fails to load redirect the page to the graphana services status page

Duplicate kube-HPC/hkube#1727

Duplicate https://github.com/kube-HPC/hkube/issues/1727


Recipe2plan better supports maped handles across imports

This PR addresses a limitation with recipe imports in recipe2plan. Before this PR, one could map a handle in a recipe (in B.arcs) to another recipe (in A.arcs) via an import (A.arcs imports B.arcs). Now that we have ingress restricting, the reverse direction (B.arcs imports A.arcs) is needed at compile time (during resolution in recipe2plan). This is because createded handles that are written to need to know if they are ever being read from -- if they are not, they resolve to a smaller type. See this draft PR (#6019) for examples of tests that are fixed by this change.
CC: @mmandlis @piotrswigon @jblebrun

TODO(alxr): Write recipe2plan tests for this change.

I don't think I fully understand the problem or your solution. You might want to find another reviewer for this PR.

Sure thing.

After discussion with the team, this change no longer seems necessary. Closing for now.


Updates to support TypeDoc 0.25.x

I went to recommend this to someone, and noticed it didn't show up in TypeDoc's themes page as having support for 0.25.x. This is because TypeDoc's site filters out plugins/themes which make unreasonable claims about supporting versions to try to avoid recommending broken packages.
This also removes the context cache from the theme. Now that the context includes the current page, it isn't safe to reuse the same context for each page (unless you overwrite the page member on that object) since pieces of TypeDoc assume that the page exists. Currently, this didn't really matter since the only part of TypeDoc that uses it is the piece that builds the "On this page" navigation section, but if you decide to implement #27, this becomes an important change.

Thanks!


Margin between items

How to add Top Margin between two card items

You can use padding on each item


Templates: Re-sort templates so that new ones are at the top

Context
Part of making new templates more visible to users
Summary

Adds creationDate to all templates
Adds a smoll unit test to make sure there's a valid creationDate on all the templates
Updates the template creation README to include creationDate
Sorts templates by creationDate , newest appearing first.

Relevant Technical Choices
NA

To-do

[x] go through and see if we want any more specific ordering of templates beyond "new ones at the top"

User-facing changes
Templates should now appear in a new order where the original templates are at the bottom.

Testing Instructions

Open up Explore Templates
Scroll to the bottom and see that the original templates are at at the bottom of the template gallery with newer ones on top

QA

Open up Explore Templates
Scroll to the bottom and see that the original templates are at at the bottom of the template gallery with newer ones on top

[ ] This is a non-user-facing change and requires no QA

This PR can be tested by following these steps:

UAT

[x] UAT should use the same steps as above.

This PR can be tested by following these steps:

Reviews
Does this PR have a security-related impact?

Does this PR change what data or activity we track or use?

Does this PR have a legal-related impact?

Checklist

[x] This PR addresses an existing issue and I have linked this PR to it in ZenHub
[x] I have tested this code to the best of my abilities
[x] I have verified accessibility to the best of my abilities (docs)
[x] I have verified i18n and l10n (translation, right-to-left layout) to the best of my abilities
[x] This PR contains automated tests (unit, integration, and/or e2e) to verify the code works as intended (docs)
[x] I have added documentation where necessary
[x] I have added a matching Type: XYZ label to the PR

Fixes #8465

Closing this because I had to update the approach for adding creation dates to templates so we could pull in the creation dates without pulling in all the templates.
new PR for this ticket:
https://github.com/google/web-stories-wp/pull/8728


Fix packr.Box when used as http.Filesystem

The Handler created by http.FileSystem checks for those errors and returns http.StatusNotFound instead of http.StatusInternalServerError.
You can find the corresponding code here.

This should solve #23

Love it! Thank you.


Add support for uploading arbitrary file attachments.

We introduce a new class, LazyAttachmentReference, which represents the upload parameters for a file on disk or in-memory Blob/Buffer and can be constructed synchronously. The caller can place LazyAttachmentReference objects anywhere in the event to be logged.
const myFile: Uint8Array = ...;
currentSpan().log({
  input: {
    question: "What is this?",
    context: {
      attachment: new LazyAttachmentUpload(myFile, "bridge.jpg", "image/jpeg"),
    },
  },
});

At span upload time, the SDK replaces lazy attachments with a reference to the object store. The above call is equivalent to:
currentSpan().log({
  input: {
    question: "What is this?",
    context: {
      attachment: {
        filename: "bridge.jpg",
        content_type: "image/jpeg",
        path: "attachments/19/1935ec5b-51fd-4267-a2af-db38ee37f46e",
      },
    },
  },
});

(Users who desire more control may handle the upload on their own and pass the resulting reference.)
At the same time, the upload is also queued. This implementation ensures that log insertion can happen in parallel with attachment uploads.

      attachment: {
        filename: "bridge.jpg",
        content_type: "image/jpeg",
        path: "attachments/19/1935ec5b-51fd-4267-a2af-db38ee37f46e",
      },

We might want to put something in here, like type: "braintrust_attachment" (or something clean/clear) so we can check this in our UI in an unambiguous way.


Changed template for ParseException: used StringBuilder instead of String

Changed template for ParseException: used StringBuilder and chained calls of append() instead of string reassignment and string concatenation. Under the hood every string concatenation is translated to temporary StringBuilder object. That's performance related.

Thanks. We keep it under the hood. We will see to integrate it when we have a test suite on which we have assessed the coverage.

@MarcMazas Do you need help with this test suite?


Fixing conflicts in branch-0.3

Fixes some issues that could not be auto merged into 0.3.
Unit tests pass locally.

build

NOTE: This must be merged with a merge-commit, not a squash commit!

The breaking change was a conflict where GpuShuffleEnv.getDeviceStorage was removed by @revans2 in a refactor. I had added an accessor next to it (for the shuffle timeout feature). So I just cleared that conflict, leaving the timeout accessor there.

build


Performance degredation using RBAC in combination with belongsto filters in user groups

Hi,
we have a good sized ManageIQ environment and are using tenants, groups for our RBAC. We noticed significant performance differences in using ManageIQ as an Admin user or as a regular user. This leads us to take a closer look if the rbac implementation can be the cause of the slowdown.
We had a call with @agrare @Fryguy @kbrock @gubbe505 and myself to discus if we can find the root cause for this and to do some tests in our environment to get some numbers on the actual time spend in rbac and to deliver SQL logs.
To get some test data I created a little test tool to measure the impact of rbac on listing VMs.
You can find the tool here: https://github.com/evertmulder/miq_rbac_log/blob/main/test_rbac.rb
The resulting log (including sql logs) can also be found in this repo:
https://github.com/evertmulder/miq_rbac_log/blob/main/log_ivanchuk4_admin.txt --> Run tool as admin
https://github.com/evertmulder/miq_rbac_log/blob/main/log_ivanchuk4_user1.txt --> Run tool as user
Note the test user has entitlements (belongsto_filters) as shown here: https://github.com/evertmulder/miq_rbac_log/blob/main/user_entitlement.txt
As can be seen in the logs the rbac does an additional 300+ sql calls.
For this test I am using ivanchuck-4.
We are more than happy to provide more logs or try out things to improve on this.

cool!
cc @NickLaMuro @kbrock cause of performance.

not based on anything but reading the code, I still think this is the ultimate problem because it walks the tree in a super-inefficient way (rewalks of the tree, in an inefficient way, multiple times in a loop).
https://github.com/ManageIQ/manageiq/blob/4abf8c6ddd9f1985c1264ca407837423695b1dfd/app/models/miq_filter.rb#L56-L67
I'm not exactly sure how to correct this though, since the belongsto is based on name and not id, and we don't store the name in the relationships table.

FYI - IIRC, the join table relating a Tag to a polymorphic object is Tagging.

also the hierarchical relationship is specified as a string that is parsed then searched for instead of actual SQL relationships.  It has always been my intent to fix that - but not sure if that is causing the slow queries or the tag lookups or both

there aren't really any literal Tag instances here as far as I can tell...they are just named "tag" in the code (in previous iterations I think they actually were tags).

also the hierarchical relationship is specified as a string that is parsed then searched for instead of actual SQL relationships.

Correct.  Some other example belongsto strings:  https://github.com/evertmulder/miq_rbac_log/blob/29b9f4f89b18bf9856abfe06ef060fc959307754/user_entitlement.txt#L11-L35
The code I referenced (and the outer loop outside this code) roughly does the following psuedo-code:
belongsto.each do |str|
  parts = parse(str)

  # find the root obj from the first part
  obj = find_in_db(parts.shift)

  # walk the tree with the rest of the parts
  parts.each do |part|
    obj = obj.children.detect(part)
  end
end

So for a belongsto string, it parses it, finds the root object, then walks the tree step by step.  Tree walking in this way is incredibly expensive because it has to go from the object, to the relationships table, down to the child relationships records, then load the objects from the actual table, then check the objects by name.  That roughly ~6 queries per level in the string hierarchy.  Then do it again for the next belongsto string.
So some things I think we can do are:

Preload the entire relationship tree in a single query, then walk that in-memory (might incur a lot of memory though with a huge hierarchy)

Load the children relationship records only (i.e. use .child_recs instead of .children, but don't resolve to the actual object, then filter that list before resolving the actual objects.

Only pull back the names of the records and not the entire actual object

Find a way to "mix" belongs to filters that are similar so they can be processed in one pass.  For example:
"/belongsto/ExtManagementSystem|VMWare_VC7",
"/belongsto/ExtManagementSystem|VMWare_VC7/EmsFolder|Datacenters/EmsFolder|CLUSTER5/EmsFolder|vm/EmsFolder|Tenants/EmsFolder|VNX",
"/belongsto/ExtManagementSystem|VMWare_VC7/EmsFolder|Datacenters/EmsFolder|CLUSTER5/EmsFolder|vm/EmsFolder|Templates"]},

all references the came VC, and even a huge part of the same folder structure.  If we could walk the tree and apply the filters simultaneously, you remove lot of redundant tree walking.

Medium-term, change how belongsto filters as persisted by not being by name but instead by id.  Having it by id would mean we wouldn't have to resolve the relationship record to an actual object at all, and all filtering could be done in the relationship records themselves.  I'm not sure this would have problems in the future though if record ids change

Alternatively, we could store the object name in the relationships table, but I really don't like this idea because you'd pay a penalty on refresh of every record.

I think that these belongsto strings should be converted to polymorphic relationships in a SQL table.  I have never understood why we store them by name via a hacky string parsing mechanism to later parse them and look them up via SQL queries.  Maybe @gtanzillo remembers why they were implemented that way in the first place, but my recollection is that tags were implemented first via the string mechanism and then the hierarchy stuff was added as a feature leveraging the same technique for expediency.

Yeah I don't understand why we need the full tree path stored as opposed to just a reference to the leaf node.  This is where my personal understanding of this feature starts to break down.
If we only have the leaf node, we can always reconstruct the path to the root in a much more efficient way (see object2belongsto method) if that full path is needed.

I think I figured out a quick PR that might just provide a lot of benefit...putting it together now.

@Fryguy sorry, I tested your PR, but isn't working. We have EmsFolder with the same name on multiple VMware providers and by using the find_object_by_name will return a random EmsFolder with that name, but belonging to a different provider.
A few examples.
{"@timestamp":"2021-05-28T19:43:53.888081 ","hostname":"manageiq-1","pid":92993,"tid":"892600","level":"warning","message":"MIQ(MiqFilter.belongsto2object_list) lookup failed for tag=\"/belongsto/ExtManagementSystem|NSX-T VC Rotterdam/EmsFolder|Datacenters/EmsFolder|CPXVC-SDN101/EmsFolder|vm/EmsFolder|Tenants/EmsFolder|VNX\" parts=[\"ExtManagementSystem|NSX-T VC Rotterdam\", \"EmsFolder|Datacenters\", \"EmsFolder|CPXVC-SDN101\", \"EmsFolder|vm\", \"EmsFolder|Tenants\", \"EmsFolder|VNX\"] result_parts=[\"ExtManagementSystem|VMWare_Arnhem\", \"EmsFolder|Datacenters\", \"EmsFolder|CPXVC-VN602A\", \"EmsFolder|vm\", \"EmsFolder|Tenants\", \"EmsFolder|VNX\"]"}
{"@timestamp":"2021-05-28T19:43:53.912502 ","hostname":"manageiq-1","pid":92993,"tid":"892600","level":"warning","message":"MIQ(MiqFilter.belongsto2object_list) lookup failed for tag=\"/belongsto/ExtManagementSystem|NSX-T VC Rotterdam/EmsFolder|Datacenters/EmsFolder|CPXVC-SDN101/EmsFolder|vm/EmsFolder|Templates\" parts=[\"ExtManagementSystem|NSX-T VC Rotterdam\", \"EmsFolder|Datacenters\", \"EmsFolder|CPXVC-SDN101\", \"EmsFolder|vm\", \"EmsFolder|Templates\"] result_parts=[\"ExtManagementSystem|VMWare_Arnhem\", \"EmsFolder|Datacenters\", \"EmsFolder|CPXVC-VN602A\", \"EmsFolder|vm\", \"EmsFolder|Templates\"]"}
{"@timestamp":"2021-05-28T19:43:54.476128 ","hostname":"manageiq-1","pid":92993,"tid":"892600","level":"warning","message":"MIQ(MiqFilter.belongsto2object_list) lookup failed for tag=\"/belongsto/ExtManagementSystem|Oracle/EmsFolder|Datacenters/EmsFolder|CPXVC-VN105a/EmsFolder|vm/EmsFolder|Tenants/EmsFolder|VNX\" parts=[\"ExtManagementSystem|Oracle\", \"EmsFolder|Datacenters\", \"EmsFolder|CPXVC-VN105a\", \"EmsFolder|vm\", \"EmsFolder|Tenants\", \"EmsFolder|VNX\"] result_parts=[\"ExtManagementSystem|VMWare_Arnhem\", \"EmsFolder|Datacenters\", \"EmsFolder|CPXVC-VN602A\", \"EmsFolder|vm\", \"EmsFolder|Tenants\", \"EmsFolder|VNX\"]"}
{"@timestamp":"2021-05-28T19:43:54.507692 ","hostname":"manageiq-1","pid":92993,"tid":"892600","level":"warning","message":"MIQ(MiqFilter.belongsto2object_list) lookup failed for tag=\"/belongsto/ExtManagementSystem|Oracle/EmsFolder|Datacenters/EmsFolder|CPXVC-VN105a/EmsFolder|vm/EmsFolder|Templates\" parts=[\"ExtManagementSystem|Oracle\", \"EmsFolder|Datacenters\", \"EmsFolder|CPXVC-VN105a\", \"EmsFolder|vm\", \"EmsFolder|Templates\"] result_parts=[\"ExtManagementSystem|VMWare_Arnhem\", \"EmsFolder|Datacenters\", \"EmsFolder|CPXVC-VN602A\", \"EmsFolder|vm\", \"EmsFolder|Templates\"]"}

Next to that, it the difference isn't a great as expected:
User apivnx.
options done in 3.43 sec.
rbac done in 7.09 sec. (vs 7.39 sec)

Thanks @gubbe505 .  Yeah, I was concerned about duplicate names which is why it's still wip... I'm working on that next

what does "options done in" and "rbac done in" refer to?  What lines did you bookend to count that?

@Fryguy See the first post, there has a script (rbac_test.rb) and 2 log files. The options done is the time of the query Vm.all, and the rbac done in the RBAC filtering of the result of the Vm.all.

oh i see now - it's in the tool itself (I was looking in the code): https://github.com/evertmulder/miq_rbac_log/blob/main/test_rbac.rb#L8-L16

The options done is the time of the query Vm.all, and the rbac done is the time of RBAC filtering of the result of the Vm.all.

That's not actually accurate.  Vm.all there is a no-op because it just returns a relation (Rails lazy queries) and isn't actually resolved until later inside of the rbac timing section.  I think the time penalty you are paying in options is actually loading the Vm constant itself (because it lazy loads the code), and I think you are paying a further penalty in the rbac section because it lazy loads all of the descendant classes.
Compare these two things:
> VmOrTemplate.descendants  # Preload the VmOrTemplate class and its descendant classes into memory
> Benchmark.realtime { Vm.all; nil }  # The ; nil prevents irb from executing the query itself
=> 0.06779100000858307
> Benchmark.realtime { Vm.all.to_a; nil } # The to_a is forcing the execution
=> 1.2748610000126064

Can we change your tool slightly?  Try this instead:
+ # Warm up the class names
+ Relationship.pluck(:resource_type).uniq.each { |c| c.constantize.descendants }
+
options = {}
time_options = Benchmark.realtime {
options = {
    :targets => Vm.all,
    :user => user,
    :skip_counts => true,
    :offset => 0,
    :limit => 1000
  }
}

I have a feeling after that the numbers will shift around.

New baseline tests (3x)
options done in 3.31/3.30/3.25 sec (3.3 average)
rbac done in 3.07/4.23/3.46 sec. (3.5 average)
New PR tests (3x)
options done in 3.10/3.51/3.11 sec. (3.3 average)
rbac done in 2.36/2.18/.254 sec. (2.4 average)
Still the same warnings because of the find_object_by_name, but an improvement of about 30%.
Sound like a good start!

I updated the PR with I hope handling for duplicate names as well as being under the correct EMS.

@Fryguy, @kbrock, @chessbyte, @evertmulder New tests after update of PR. This time around I included tests on different datacenters to see the impact of database latency.
Baseline/Pod and DB in same datacenter
Number of VMs 26
options done in 3.25/3.00/3.01 sec. (3.1 average)
rbac done in 2.34/2.43/2.49 sec. (2.4 average)
Lines in SQL logfile: 641
PR changes/Pod and DB in same datacenter
Number of VMs 26
options done in 3.33/3.14/3.13 sec. (3.2 average)
rbac done in 2.16/2.20/2.30 sec. (2.2.average)
Lines in SQL logfile: 329
Baseline/Pod and DB in different datacenter
Number of VMs 26
options done in 3.26/3.14/3.13 sec. (3.2 average)
rbac done in 3.67/3.31/3.55 sec. (3.5 average)
PR changes/Pod and DB in different datacenter
Number of VMs 26
options done in 3.19/3.04/3.01 sec. (3.2 average)
rbac done in 2.41/2.89/3.01 sec. (2.8 average)
The performance gain of the changes are less (10% same datacenter/20% different datacenter) that the first attempt, but now this working correctly. Also the impact of the database latency can be seen and is less a factor on a higher latency,

Test is on a larger Tenant
Baseline/Pod and DB in different datacenter
Number of VMs
options done in 3.26/3.18/3.11 sec. (3.2 average)
rbac done in 3.55/3.42/3.58 sec. (3.5 average)
PR changes/Pod and DB in different datacenter
Number of VMs 475
options done in 3.06/3.29/3.26 sec. (3.2 average)
rbac done in 2.88/2.78/2.88 sec. (2.8 average)
Conclusion
No bigger difference when filtering a larger number of VM's using the same number of belong to filters.

@gubbe505 When you have a chance can you give #21258 a try - this is a really simple refactoring that might have a huge impact, but maybe not on the pages you are looking at, so click all around.


JSF converters

It seems that AngularFaces is incompatible with JSF  converters.
It works with #{..}, but not with {{..}}. Actually the converter is ivoked, but the value is still the same as beans field.
`

<h:outputLabel for="meanRadiusOfBellows"
value="Mean Radius of bellows" />
<p:inputText id="meanRadiusOfBellows"
value="#{calculateBellows.meanRadiusOfBellows}"
converter="lt.mjok.btt.converters.MmToMeterConverter" />
mm

<h:outputLabel for="radiusOfConvolutionRoot"
value="Radius of convolution root" />
<p:inputText id="radiusOfConvolutionRoot" converter="lt.mjok.btt.converters.MmToMeterConverter"
value="{{calculateBellows.radiusOfConvolutionRoot}}"
/>
mm`

AngularFaces was an interesting project, but it turned out to be impossible to migrate it to Angular 2, and since the, the Java community has abandoned UI programming altogether. So I'm closing all remaining tickets and archive the project.


Please invite me to the community

Name
Christopher Martindale
Additional Context
improved tools for project management, including issue tracking, milestones, and project boards, to help teams manage their work more effectively and ensure that project goals are achieved on time

Invitation sent to join the GitHub Organization. Welcome to Infraform 🎉Please check your mail to accept the invitation sent by GitHub! 🤖About usInfraform is an open source solution for serverless platforms, it is designed for developing solutions and enhancing creators to create their infrastructure 💻 Great to have you in our community ✨ Looking forward to your valuable contributions! 🤓 You can also check our community ✨ Github ✨ LinkedIn 💜 You can also share our community with other folks who want to learn about development, DevOps, tech, and contribute together and with us 👉💜👈


docs(custom): 补充pr

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.


cannot download yalu onto my device (Stuck on "verifying applicantion" for 4 hours and nothing happend)

This is not a support forum or generic mailing list.
This form is exclusively for reporting issues caused directly by the inner workings of yalu.
Direct your jailbreaking questions to one of these fine communities:

https://reddit.com/r/jailbreak
http://www.jailbreakqa.com/

Issues, which are not related to yalu's code, may be closed without comment. Do NOT post about: Cydia, tweak, respring/bootloop or app issues UNLESS you have evidence that they are caused by an error in the jailbreaking software itself.
(Delete this bit after reading, and replace it by "I read the issue posting guidelines.")

#162 #64


Documentation and portal does not mention that change to Diagnostic Setting trigger a webapp Restart !

Beware, the documentation does not mention that change to Diagnostic Settings will create Env Variable into the webapp and trigger a restart. Leading to outage !
Document Details
Exemple configure this setting will add a new env vars: AZMON_LOG_CATEGORY_APPSERVICEAPPLOGS_ENABLED and trigger a restart.

..."category": "AppServiceAppLogs", "operationName": "[Microsoft.Web/sites/log](http://microsoft.web/sites/log)", "level": "Information", "resultDescription": "Application is shutting down...
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: bfc316af-0d30-b449-a04f-3019b7a16bc1
Version Independent ID: 01c4c435-fda9-374a-70b3-f1d7f13c7651
Content: Enable diagnostics logging - Azure App Service
Content Source: articles/app-service/troubleshoot-diagnostic-logs.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: msangapu

@Cedric-Bravo Thanks for the feedback! We are currently investigating and will update you shortly.

Cedric-Bravo, We have been discussing on this internally, your feedback has been shared with the content owner for further review, and update the doc as appropriate. Thanks again for your feedback.


Update feature_request.md

Setting untriaged for the default.
Signed-off-by: Lane Holloway<EMAIL_ADDRESS>Description
Sets untriaged on all feature requests to ensure we look at it.
Issues Resolved
N/A
Check List

[ X] New functionality includes testing.

[ X] All tests pass

[ X] New functionality has been documented.

[X ] New functionality has javadoc added

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

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

This is such a mess to make a simple change, having dlv@ make the change since his IntelliJ is already up.


Show task.product on dataset modal

I believe task detail is available on dataset modal, and if so, I should show task.product if it exists. Some app stores application execution status on product.json and loaded to the task
wmc:afq
{ quality_check: 'ERROR: Some tracts have less than 20 streamlines. Check quality of data!' }

I believe this is done (and working..)


Added config for deprecated 'HorizontalPodAutoscaler' apiversion

deprecated "HorizontalPodAutoscaler" apiversion.
The API Version is changed due to deprecated apiversion.
https://kubernetes.io/docs/reference/using-api/deprecation-guide/
Fixes #67

@hydeenoble It looks like you didn't rebase with main. It seems you have pulled in pervious changes into this PR.

Yeah, that's what I did. What command should I run instead?

@hydeenoble You need to rebase your branch with the latest main branch.

@hydeenoble You need to rebase your branch with the latest main branch.

Done! @hickeyma

.DS_Store should not be part of the commit.

Removed!. That was an oversight.


[core] Optimize Theme Mode Selector in Header

Summary
When we have the ability in the theme to select mode (system, dark, and light), a toggle button is created in the header. However, this element occupies precious space in the header that could be used for other types of configurations. The proposal is to follow the MUI documentation style, where there is a gear button that contains configuration options, including the mode selector, along with other settings.
For example: language preferences, display preferences, among others.
Examples

Motivation
No response
Search keywords: theme

Assuming there are going to be many different ways of how users would want this to be executed, perhaps step 1 should be to create the minimum API necessary to customize this in user land.
It's already possible to build your own theme toggle with the useColorScheme hook. The one thing missing then is a way to hide the theme toggle in the header.
cc @apedroferreira Perhaps a quick win here could be to add a slot for the theme toggle

Assuming there are going to be many different ways of how users would want this to be executed (*), perhaps step 1 should be to create the minimum API necessary to customize this in user land. It's already possible to build your own theme toggle with the useColorScheme hook. The one thing missing then is a way to hide the theme toggle in the header.
cc @apedroferreira Perhaps a quick win here could be to add a slot for the theme toggle?
(*) I'm imagining

a toggle button
a drawer as per this issue
a button with popover
on a separate settings page
no toggle at all, just follow the system preference
...

Sounds good, we have 2 slots in the header right now (account + additional actions), but the theme is outside of them.
I guess we should have the minimum amount of slots in the header than can be completely overriden.

Hi, I would like to restore the user theme's choice when user logins back. Is it possible to provide a Slotprops for Theme's user action?
Thanks

@ebengtso Can you elaborate a bit more on what you're trying to do?
Are you storing the dark/light mode choice in the user record on the backend? You should be able to already achieve that functionality with mode and setMode returned by the useColorScheme hook.

@ebengtso Can you elaborate a bit more on what you're trying to do?
Are you storing the dark/light mode choice in the user record on the backend? You should be able to already achieve that functionality with mode and setMode returned by the useColorScheme hook.

Thanks. Two distinct issues:

I had a wrapping ThemeProvider. I removed it and it worked. It was disturbing the following AppProvider.

In the below I was expecting debug to print, but it's not printing when I switch the theme.

const {mode, setMode} = useColorScheme();
useEffect(() => {
console.debug(mode)
}, [mode]);

Regarding 2. The following works for me https://codesandbox.io/embed/gcnmgl?module=/src/Demo.tsx

@ebengtso Here's a stackblitz that demonstrates useColorScheme. Make sure to call it in a component that's rendered under the DashboardLayout.

In this case, where the hook is exported, the dashboard could have the option of a slot for the theme. This way, we could set it to null and customize it through the action or account slot.


 System Darwin 15.6.0
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/me/dev/trading-dev/simple-websockets-setup/node_modules/utf-8-validate
gyp ERR! node -v v11.0.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! no

You may want to report such an issue to the corresponding ws project (which is not this one).

Sure. Sorry. Funny how they just implemented this.
https://twitter.com/github/status/1057678791764467712?s=21


Publish on crates.io

I think this crate could be useful to other people. Publishing it on crates.io would improve its discoverability.

It looks like this happened.


⚠ Bofrost.de has degraded performance

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

HTTP code: 200
Response time: 942 ms

Resolved: Bofrost.de performance has improved in 2d18c32.


API keys

It'd be great for people to have the ability to host this for others. For that to work well, there could be a system to set up API keys and track usage of them.
It could work just like OpenAI API keys.

Fixed in #877


Error leonardjke/omnipay-qiwi[0.1, ..., 0.2] require omnipay/common v3.0-alpha.2 -> found omnipay/common[v3.0-alpha.2] but it does not match your minimum-stability

Why is everything broken?
./composer.json has been updated
Running composer update league/omnipay leonardjke/omnipay-qiwi
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - leonardjke/omnipay-qiwi[0.1, ..., 0.2] require omnipay/common v3.0-alpha.2 -> found omnipay/common[v3.0-alpha.2] but it does not match your minimum-stability.
    - leonardjke/omnipay-qiwi[0.3, ..., 0.4] require omnipay/common v3.0.5 -> found omnipay/common[v3.0.5] but the package is fixed to v3.2.1 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - leonardjke/omnipay-qiwi[0.5, ..., 0.6] require omnipay/common v3.1.2 -> found omnipay/common[v3.1.2] but the package is fixed to v3.2.1 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - Root composer.json requires leonardjke/omnipay-qiwi * -> satisfiable by leonardjke/omnipay-qiwi[0.1, ..., 0.6].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require league/omnipay:*" to figure out if any version is installable, or "composer require league/omnipay:^2.1" if you know which you need.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

Hi, can you give me some additional information about your current php version. I see that it is necessary to update omnipay/common. Maybe you have already installed a omnipay/common and your version is lower that in this project

Not enough details. I created a pull request for updating the version of omnipay/common library and set requirement php 7.2 and 8.*. Close

It works


WIP: Viewshed Performance Increases

The following PR improves the performance of datashader's performance by changing the structures and not the algorithm (taken from GRASS).
In testing, the performance increase was about 75x:

This isn't ready to merge yet...fixing some tests...

Looks like past commit got pulled in here...going to recreate...


Sebastian_project

My name is Sebastian I'm n MSc student at UofT

adding additional comment for TA check before merge


Collectives not appearing on host page

Describe the bug
This host says it has 6 Collectives, but none are appearing on the page.

This is already being taken care of in https://github.com/opencollective/opencollective/issues/1990. Duplicate.


BUG: Cascade deletes no longer bypasses delete permissions.

Fix for https://github.com/silverstripe/silverstripe-framework/issues/10069

Thanks for clarification @dhensby , in that case I think it's ok to keep the behaviour as is and simply improve the docs ;-).

Confirmed that behaviour it intentional so it's a feature not a bug. Also, docs clearly state this fact so no follow up is needed.


Gemini has returned a different issue

"Gemini has returned a different number of lines than the original , trying again"
I'm getting this error, is there a solution for it?

What version are you using? This should be fixed in v1.1.4

Hi, seems to be a problem with how Gemini sometimes handles some dialogs (it decides to arbitrarily split some dialogs in two). I got a fix coming up in the next version with a workaround for this. Hopefully it will solve the problem for good.

I have the same problem and after updating gemini-srt-translator-1.2.0 a new error appeared.
Traceback (most recent call last):
  File "~/gemini-trans/main.py", line 1, in <module>
    import gemini_srt_translator as gst
  File "~/gemini-trans/.venv/lib/python3.11/site-packages/gemini_srt_translator/__init__.py", line 32, in <module>
    from .main import GeminiSRTTranslator
  File "~/gemini-trans/.venv/lib/python3.11/site-packages/gemini_srt_translator/main.py", line 159
    translated_subtitle[int(line["index"])].content = f"\u202B{line["content"]}\u202C"
                                                                     ^^^^^^^
SyntaxError: f-string: unmatched '['

@ongnxco this should be fixed now in version v1.2.1, sorry about that. ;)


[DevTestLab] Enable Shared/Public/Private IP configuration setting on lab vm

[x] Enable Shared/Public/Private IP configuration setting on lab vm
[x] Update documentation as per https://github.com/vishrutshah/azure-cli/pull/8
[x] Update discovery of owner object id through https://github.com/Azure/azure-cli/pull/2648 logic

Codecov Report

Merging #2653 into master will decrease coverage by 0.07%.
The diff coverage is 17.94%.

@@            Coverage Diff             @@
##           master    #2653      +/-   ##
==========================================
- Coverage   61.61%   61.53%   -0.08%
==========================================
  Files         515      515
  Lines       25988    26036      +48
  Branches     3890     3900      +10
==========================================
+ Hits        16012    16021       +9
- Misses       9035     9070      +35
- Partials      941      945       +4

Impacted Files
Coverage Δ

...zure-cli-lab/azure/cli/command_modules/lab/help.py
100% <ø> (ø)
:arrow_up:

...re-cli-lab/azure/cli/command_modules/lab/custom.py
37.5% <ø> (ø)
:arrow_up:

...re-cli-lab/azure/cli/command_modules/lab/params.py
100% <100%> (ø)
:arrow_up:

...li-lab/azure/cli/command_modules/lab/validators.py
13.38% <12.32%> (-0.01%)
:arrow_down:

...-cli-role/azure/cli/command_modules/role/custom.py
17.89% <0%> (ø)
:arrow_up:

...dback/azure/cli/command_modules/feedback/custom.py
34.69% <0%> (ø)
:arrow_up:

src/azure-cli-core/azure/cli/core/_util.py
66.66% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

@derekbekoe @tjprescott I've pushed one more commit onto this PR to be able to work with "default group configuration". I've verified that it is leveraging the default configuration. Feel free to take a quick re-look at the PR. Thanks!

LGTM

Do you need @ericame to sign off?

I've informed her about the review but she seems busy with some other custom issue in Dev Test Lab team. Let's wait until 4:30 pm. If she gets chance to look into that's great or we can continue.

As per offline conversation with @ericame I'll open an issue to check for existence of the "inbountNatRule" for defaulting logic.


Update grafana-tools/sdk dependency to support datasources as a map

As of Grafana 8.3.0, the dashboard schema permits a datasource to be a map, defining the uid, and type of the datasource.
The upstream grafana-tools/sdk, (which is used in the analyse dashboard command) still expects the previous behavior, and will fail to unmarshal a dashboard which uses this new schema.
This PR replaces the dependency with a branch which fixes the problem, but is not yet accepted into the upstream grafana-tools/sdk main branch.
See grafana-tools/sdk#190 for details.
This PR could languish until that PR is merged, however this fix is needed for some downstream projects which depend upon cortextool, so I'm mocking up the interim workaround for anyone else who finds themselves in the same situation.

Closing in favor of #248


Invalid return value specified for OpenDatabase

In the description it says the method returns a Database object but in Return value it says it returns nothing.
Seems like multiple methods of the Installer object have the same issue. Missing return value.

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

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


Fix missing directory on plotting

Hey there!
First, thank you for your amazing work! I have started writing something on my own for algorithmic trading, but it seems like your package can do almost everything I wanted to do in mine (some of them like trailing stop loss are still in development as I see).
This PR today is to fix just a tiny little thing that bothered me: when I ran your Backtest_Strategy.py example, this happened:
Traceback (most recent call last):
  File "Backtest_Strategy.py", line 134, in <module>
    Main()
  File "Backtest_Strategy.py", line 130, in Main
    ], show_plot=True)
  File "/home/gabriel-milan/GIT_REPOS/pyjuque/pyjuque/Plotting/__init__.py", line 316, in PlotData
    plot(fig, filename=os.path.join(file_path, plot_title+'.html'), auto_open=show_plot)
  File "/home/gabriel-milan/.local/lib/python3.7/site-packages/plotly/offline/offline.py", line 597, in plot
    auto_open=auto_open,
  File "/home/gabriel-milan/.local/lib/python3.7/site-packages/plotly/io/_html.py", line 527, in write_html
    with open(file, "w") as f:
FileNotFoundError: [Errno 2] No such file or directory: '/home/gabriel-milan/GIT_REPOS/pyjuque/examples/graphs/Unnamed.html'

This was due to the missing directory when plotting. It's a very simple fix and that is what I wanted to bring on this PR. I'm still on my first steps with pyjuque, and it would be awesome to be able to contribute more in the future.
Best regards,
Gabriel Milan

Awesome man! Thank you for contributing!


[AITT] Remove AITT connection

Remove AITT connection since AITT has been deprecated.
Self evaluation:

Build test: [ ]Passed [ ]Failed [*]Skipped
Run test: [ ]Passed [ ]Failed [*]Skipped

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #224. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.

INFO: You can read if there are misspelled characters at our misspelling check report. Please read http://ci.nnstreamer.ai/nnstreamer-edge/ci/repo-workers/pr-checker/224-202409091343220.536465883255-43b90b3a8c8f474965031965ffd118f0454c3157/report/misspelling_result.txt.


Setup dev cluster with common CSRF secret

This PR is a part of https://github.com/apache/couchdb-couch/pull/80

+1


Mina book - Kimchi section regarding permutation is empty.

Links to add: https://minaprotocol.com/blog/a-more-efficient-approach-to-zero-knowledge-for-plonk.
In the code:
zk_rows is the number of blinders, and is set to 3 at the moment. It is because we evaluate at \z and \omega * z , and for the zero-knowledge property, we need N + 1 blinders where N is the number of evaluations points.
Also https://mirprotocol.org/blog/Adding-zero-knowledge-to-Plonk-Halo and https://www.plonk.cafe/t/noob-questions-plonk-paper/73.

The section is no longer empty. Closing.


Rate limit task processing requests guarded by feature flag

What changed?
Task processing requests will be rate limited if enabled by domain level feature flag

Why?
Introducing wf-id based rate limits for task processing

How did you test it?
Unit tests

Potential risks
None for now since the rate limiting of task processing is guarded by feature flag.

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 018e6119-160f-4fb7-802a-0793f362d36f
Details

28 of 36 (77.78%)  changed or added relevant lines in 5 files are covered.
203 unchanged lines in 10 files lost coverage.
Overall coverage decreased (-0.04%) to 65.125%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

service/history/task/transfer_active_task_executor.go
18
26
69.23%

Files with Coverage Reduction
New Missed Lines
%

service/history/task/transfer_standby_task_executor.go
2
87.84%

service/history/task/timer_task_executor_base.go
2
78.38%

common/task/fifo_task_scheduler.go
2
84.54%

common/util.go
2
91.78%

common/persistence/historyManager.go
2
66.67%

common/persistence/statsComputer.go
3
94.64%

common/persistence/nosql/nosqlplugin/cassandra/workflow_parsing_utils.go
11
88.22%

service/history/task/task_util.go
20
70.57%

common/persistence/serializer.go
62
79.09%

common/persistence/nosql/nosqlplugin/cassandra/workflow.go
97
72.83%

Totals

Change from base Build 018e60fc-6927-4769-9b7b-440334354bdc:
-0.04%

Covered Lines:
95216

Relevant Lines:
146205

💛  - Coveralls


Using TRAP to obtain motif files

I'm a new msCentipede, and I am planning to do TF foot printing analysis using on ATACseq paired-end data.
My main concern is that I want to see if there is TF binding on my data, but first I want to look for all TFs, i.e all PWMs on JASPAR, so I am planning to use TRAP because is fast to doing this. DO you thinks is appropiate to do it?

I haven't used TRAP myself. However, if the output of TRAP is a list of motif sites that a TF likely would bind to, then these sites would be an appropriate input to msCentipede.
I've observed msCentipede to be fairly robust to the set of motif sites used for learning, as long as the set includes many potential binding sites (typically, sites with high PWM scores). So, any software (TRAP, FIMO, others ...) should suffice.

OK, many thanks Anil!


Invalid convexhull polygon for Multipoint objext

Expected behavior and actual behavior.
I am trying to generate convex hull for a MultiPoint object but the returned polygon is an invalid polygon object.
Steps to reproduce the problem.
from shapely.wkt import loads
mps = loads('MULTIPOINT (0.09176166386719853 -0.4594509958047714, 0.0964919595889223 -0.4613185215258491, -0.07720854327505063 -0.3893774144175335, -0.514132735196233 0.4844243124571844, -0.5157563919220147 0.4883439730483261, -0.4438154792984115 0.6620323790359064, -0.44378845454982 0.6620355239884737, -0.4430558191117821 0.6617320714344408, -0.4425193476523399 0.6629710114442775, -0.2750532183528819 0.5968552076395059, -0.2676620363052705 0.5937936520564248, 0.4616312579331061 -0.1299616117871567, 0.4652079369036946 -0.1371183617095489, 0.4668376557292508 -0.141042820548618, 0.4665494319079306 -0.1427098330519487, 0.4665629024181607 -0.1427344571104113, 0.3918467226125127 -0.315278746283741, 0.3861846650602798 -0.3209365927118177, 0.09649195958892229 -0.4613185215258491, 0.09176166386719853 -0.4594509958047714)')
mps.convex_hull.is_valid

Operating system
Ubuntu 16.0
Shapely version and provenance
shapely 1.6b4 installed from PyPI using pip

I can't reproduce this problem. It's possible this is a bug in an older version of GEOS. What do you have installed?
Python 3.6.3 (64-bit), Windows 10, Shapely master, GEOS 3.6.2

Closing for lack of response.


lsb_release -cs in linuxmint is sylvia - should point to base distribution instead

Upstream distribution information resides in /etc/upstream-release/lsb-release
The first line of the installation script could be modified to:
AZ_REPO=$(lsb_release -cs)
if [ -f /etc/upstream-release/lsb-release ]
then
. /etc/upstream-release/lsb-release
AZ_REPO=$DISTRIB_CODENAME
fi

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

ID: fe1526a9-7f22-504e-484c-0f3edc11b178
Version Independent ID: c5dec108-efcd-aa77-04b5-803b6b894dba
Content
Content Source
Service: multiple

Unfortunately we cannot include information for every Linux distribution in the install instructions for apt, due to the wide number of available Debian-based distributions (see https://en.wikipedia.org/wiki/List_of_Linux_distributions#Debian-based). Adding special-casing instructions like this causes a problem because other distributions may deviate from the requirements of Debian/Ubuntu as to where LSB information is required to be stored and how it is treated by lsb_release (see https://wiki.ubuntu.com/DerivativeDistroHowto#File_.2Fetc.2Flsb-release).
The officially tested and supported distributions are also included at the top of the install page. If we later decide to add Mint as a supported and tested platform, the instructions will be updated.


RuntimeError: CUDA error: out of memory with llama-2-13b-chat-hf model on A100 with vllm 0.2.1.post1 version

Hi team, I tried below code on vm with A100 which fastchat and DeepSpeed can both server  the same model
from vllm import LLM, SamplingParams
import os
os.environ['CUDA_LAUNCH_BLOCKING'] = "1"
prompts = [
    "What's the advantage of DeepSpeed",
]
sampling_params = SamplingParams(temperature=0.8, top_p=0.95)
llm = LLM(model="llama-2-13b-chat-hf")
outputs = llm.generate(prompts, sampling_params)

I met the error below,
Traceback (most recent call last):
  File "/home/yalqin/deepspeed_mii/test-vllm.py", line 11, in <module>
    llm = LLM(model="llama-2-13b-chat-hf")
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/anaconda3/lib/python3.11/site-packages/vllm/entrypoints/llm.py", line 93, in __init__
    self.llm_engine = LLMEngine.from_engine_args(engine_args)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/anaconda3/lib/python3.11/site-packages/vllm/engine/llm_engine.py", line 231, in from_engine_args
    engine = cls(*engine_configs,
             ^^^^^^^^^^^^^^^^^^^^
  File "/root/anaconda3/lib/python3.11/site-packages/vllm/engine/llm_engine.py", line 110, in __init__
    self._init_workers(distributed_init_method)
  File "/root/anaconda3/lib/python3.11/site-packages/vllm/engine/llm_engine.py", line 142, in _init_workers
    self._run_workers(
  File "/root/anaconda3/lib/python3.11/site-packages/vllm/engine/llm_engine.py", line 700, in _run_workers
    output = executor(*args, **kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/anaconda3/lib/python3.11/site-packages/vllm/worker/worker.py", line 65, in init_model
    _init_distributed_environment(self.parallel_config, self.rank,
  File "/root/anaconda3/lib/python3.11/site-packages/vllm/worker/worker.py", line 359, in _init_distributed_environment
    torch.distributed.all_reduce(torch.zeros(1).cuda())
                                 ^^^^^^^^^^^^^^^^^^^^^
RuntimeError: CUDA error: out of memory
CUDA kernel errors might be asynchronously reported at some other API call, so the stacktrace below might be incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1.
Compile with `TORCH_USE_CUDA_DSA` to enable device-side assertions.

Can anyone help?

Hi @yaliqin, do you mean you are trying to set up both vLLM and DeepSpeed servers on a single GPU? If so, you should configure gpu_memory_utilization (by default 0.9) to a lower value like 0.5. This means the vLLM instance will occupy 50% of the GPU memory. However, if the model size itself exceeds the 50% of the GPU memory, you will see errors.

Hello,
I am having a similar problem regarding CUDA out of Memory with lama2-13b-hf in GCP. Can anybody help me with it ?

Closing this issue as stale as there has been no discussion in the past 3 months.
If you are still experiencing the issue you describe, feel free to re-open this issue.


Change default format of dataset titles.

To be done after https://github.com/owid/etl/issues/1544
With the new metadata, we have the following options for dataset titles:

Title (producer, year). This is our current default format, but it involves additional manual work (e.g. changing 2023 -> 2023a -> 2023b), and it's redundant (since we already have version in the datasets table.
Title. This is the cleanest option in terms of metadata handling, although currently this would not let us search for a dataset by the producer's name (since producers is not in the datasets table) in the admin, which may be inconvenient in some cases.
Title (producer). Therefore, this seems to be a good tradeoff.

Do we all agree?

[ ] @lucasrodes
[ ] @danyx23
[x] @Marigold

Once decided, I'll change the metadata guidelines.

An alternative would be go with option 2 in ETL, but then in the Grapher step, under the hood, combine title with producer to generate option 3 in Grapher database.

After several discussions, I think we all agree that the best option is to use a dataset title that does not include a reference to any other metadata field (like producer or year). We'll need to improve our admin, search engines (and other tools, like the etl-wizard charts) to make it easy to search by title and other metadata fields.


fix invalid host reference

host is found inside url object which is inside currentServer object

Coverage remained the same at 95.256% when pulling cae6a9b8680ac6125906efe51bbcec838c8410d5 on pkoretic:patch-1 into 592efdf9881676a8cce9dee551b81cfd3acfddb7 on nats-io:master.

LGTM. The parsed server is an Url.

Thanks for the catch!


Palword File Extract not working PLZ HELP

Game name:

Game package name:

Same issue here, worked once and then never again, has issues finding the game.

mine doesnt have issue finding the game its just not pulling the right save file so i cant access my world on steam

It looks to find the right save (level 47) but when i launch the game on the save i am level 31 with older camps. So it must find only older saves and not the most recent one


Bug Fix: wrong invokation to call ./scripts/install_all.bat which let dependency check always pass on Windows platform

Bug fix: issue #9853 to make dependency check valid on Windows platform

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[x] I adhere to the Command Guidelines.

FYI.
As you can see, in our previous dependency_check job Verify src/azure-cli/requirements.*.Windows.txt,
build 20190702.02 exited and return code 0 even though script detectes error. Which is not reasonable.
build 20191031.26 exited and return code 0 even though script interupted.
So, whatever situation, dependency check of CI will always green even though it detects error on Windows platform.
My changes of my first commit can reproduce those build's situation.

talked with @haroldrandom offline. LGTM.


As a fast typer, I can also enter expenses/bills using inbuilt command line to quickly add in transactions

Subtask of #1

using inbuilt command line refers to implementation details. Closing this.


Error Installing

Describe the bug
When Installing Ghost using the command it gives an error
To Reproduce
Try to Install Ghost
Expected behavior
Install Ghost
Screenshots

Desktop (please complete the following information):

OS: [Windows 10]

@klespy Ghost Framework won't work on Windows (only POSIX systems supported).


🚸 Indenting and relevance

Source: https://docs.lamin.ai/scrna2
The indenting is off here:

Also: evidently the block does not proceed with what's recommended. Is the hint relevant?

I don't think that for the purpose of this tutorial the gene hint is helpful. It's more distracting although it can be relevant in some cases. Maybe it wasn't there with an older ensembl version? Anyways, could we remove those genes from the dataset?

Or say "consider adding these genes" instead of "please add those genes" which seems like one should do it (even though the tutorial doesn't do it)

What's missing in this tutorial is simply a curator.validate() call in this block:


Feat: setup http request callback

Code below works fine. it loads video 10/10 times
httpRequestSetup: async (
      url: string,
      segmentByteRange: ByteRange | undefined,
      requestByteRange: { start: number; end?: number } | undefined,
    ) => {
      await new Promise((resolve) => {
        setTimeout(resolve, 1500);
      });

      const headers = new Headers(
        requestByteRange
          ? {
              Range: `bytes=${requestByteRange.start}-${
                requestByteRange.end ?? ""
              }`,
            }
          : undefined,
      );

      return new Request(url, {
        headers,
      });
    },

The implementation of func below works weird. It works only if time in settimeout is less than 1000.
It might be due to  httpNotReceivingBytesTimeoutMs: 1000, because when i change it to 2000, code works fine even with settimeout with 1500 ms.
httpRequestSetup: async (
      url: string,
      segmentByteRange: ByteRange | undefined,
      requestByteRange: { start: number; end?: number } | undefined,
    ) => {
      await new Promise((resolve) => {
        setTimeout(resolve, 1000);
      });

      return null;
    },


docs(logo): update react magma logo

re #718

Codecov Report

Merging #722 (9ca1dd2) into dev (9ca1827) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##              dev     #722   +/-   ##
=======================================
  Coverage   87.15%   87.15%
=======================================
  Files         174      174
  Lines        4374     4375    +1
  Branches     1467     1468    +1
=======================================
+ Hits         3812     3813    +1
  Misses        284      284
  Partials      278      278

Impacted Files
Coverage Δ

...es/react-magma-dom/src/components/Select/shared.ts
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


My plugin is collecting data from someone else's plugin

My name on bStats is andy_ and my plugin is called Challenges. The plugin has only included bStats since 3.0 which was released on the 11th, but the plugin version chart has a segment for 1.0 and the "Players on servers using" graph shows 200 players even before it was released.

are you sure its actually your plugin?
there can be multiple plugins with the same name now iirc. whats your plugin id?

So sorry, didn't realise the bStats id had to be the same as the spigot one. I copy and pasted the class from what was on github and there was no pluginId parameter or variable when I did, not sure if I just got an old version somehow. Thanks.

The id is 6095. I'm pretty sure it's mine, the majority of the plugin version chart is 3.0 and since it was released the server count has gone up.

You'll have to wait for the web site end to support multiple plugins with the same name. That's still not possible.

Just to clarify for OP, Bobcat is referring to #70

There might be some old plugin that had the same name and still sends data.

It looks like that might be the case, although I can't find any other plugin online with the same name. Thanks for the clarification.


RuntimeError: Could not load an opus lib. Tried libopus-0.x86.dll, libopus-0.x64.dll, libopus-0.dll, libopus.so.0, libopus.0.dylib

I've seen this happen to other people but they were fixed by installing opus. Well I have opus installed and still get the same problem.

Fixed by doing
cd <your music bot folder>
cp /usr/lib/*/libopus.so.0 .

i had the same problem but when i do what you told him it said this
cp: /usr/lib/*/libopus.so.0: No such file or directory

my command a dot at the end of it.
are you sure you wrote it with the dot?

i copy and pasted it

-MacBook-Pro:MusicBot-master
$ cp /usr/lib//libopus.so.0 .
cp: /usr/lib//libopus.so.0: No such file or directory

try this
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install libopus0
then
cd <your music bot folder>
cp /usr/lib/*/libopus.so.0 .

then try all the commands but without sudo

hello and i looked up the sudo command and it is for ubuntu and i am on a mac

use the mac command then

do you know what it is?

i think it's yum -code here-


Bug with JSON DOCTYPE and saving Department values

What version of Node.js are you using?
Latest
What version of npm are you using?
Latest
What operating system are you using?
Windows Server 2019
What version of SnailyCAD are you currently using?
https://github.com/SnailyCAD/snaily-cadv4/commit/aa5f726
Describe the Bug

Values are not saving. This is the error I have in console.
Expected Behavior
To be able to save values like Officer Ranks.
Also Department updates/edits.
To Reproduce
No response

that error is not related to this bug report. Are you able to clarify not being able to update values?

I added a new officer rank
the new rank is not showing in default rank drop down for department

trying to edit HSO-GSO-PPS default rank and it wont remove it or even find the new one in the list that i want to change it do

does it show up after a page refresh? I'm unable to reproduce this error

It does not :(
Even logged out and back in.
I give up.
I even updated Snaily just now and it still wont work
I make the new rank... it says the rank is there on the Officer Rank page.
I go to Department
I go to edit Default Rank
Option is not there in the drop down.
I also cannot remove the Default rank to set it as None.
The only thing that works is changing the default rank to an existing rank in the drop down but that doesn't help lol.

Check your Discord DM's please :)


Update scalafmt-core to 2.6.4

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

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

labels: library-update, semver-patch

Codecov Report

Merging #8 into main will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #8   +/-   ##
=======================================
  Coverage   80.00%   80.00%
=======================================
  Files           2        2
  Lines          15       15
=======================================
  Hits           12       12
  Misses          3        3

Continue to review full report at Codecov.

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


Use DREAM NeXus files and add events to enable further testing and workflow development

We have existing DREAM NeXus files, but (as far as I know) there is no event data.
Add event data to make these files usable for running an actual workflow.
~We could use data from the Geant4 files, or simple add noise.~ -> Do this later in a second step.
Extend the capabilities of the "grow nexus" script in scipp/essreduce#13 to add events even if there are none? This would make this usable in a more general context, outside DREAM.

Can use files with fake events that are now being produced by ECDC.


Angular RC5 Support

There is already a fixed merge for for RC5 support. Can you publish a new version to NPM?
br

Published.

thx

Following RC5's introduction of NgModule, are there plans to add a module for ng2-idle and update the README to reflect the changes?


[move-prover] Copy Propagation and Transformation Pipeline.

This PR refactors the copy propagation algorithm in reaching_defs_analysis.rs and applies it to all bytecode. Previously references where skipped for copy propagation because of some issues which are now fixed.
The PR also removes the use of the $tmp variable in the generated bytecode, which is obsolete since the new memory model.
Overall goal was to make code more readable in preparation for understanding and changing the pack/unpack semantics. As a side effect, code may have become some 20% smaller, as well speed seem to have increased by 10-15%.Unfortunately, the butterfly effect required to turn verification off for staple_lbr.
Changes in the algorithm: In the new version, elimination of dead assignments is left to the livevar_analysis.rs, which did already some of this work. The new version also uses the reaching definitions at each program point instead of the exit points; the later would be only correct if we had single-assignment semantics.
Changes in pipepline tools: For debugging, a few changes where made: (a) there is now a flag --dump-bytecode which causes the prover to dump the intermediate bytecode for each step in the pipeline (b) the format of the bytecode output has been (attempted) to improve (c) some assertions have been added to borrow analysis for debugging. Moreover, the pipeline.run() algorithm has been refined that it actually again works breadth first, so processors of functions can access the result of the most recent step in the pipeline for other functions (not used because we do not yet do inter-function analysis and transformation, but might be handy later).

Motivation
Towards refining pack/unpack semantics (sum of coins etc.)
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Existing and new tests.
Related PRs
NA

@shazqadeer FYI, I did remove the propagation of the aliases for the destination of assign as discussed offline, and all tests pass unmodified as before. So it was truly redundant.

I discovered some other redundant code last night in writeback analysis.  I will remove that separately.

/land


Fixed typo in custom js guide header

@jgrevich I think you're targeting the wrong branch - did you mean 1-0-stable?

my fault, I fixed the pull request.


Multiple failure queues

Much like the Ruby implementation, it would be good if we could implement multiple failure queues as an option.
If switched on, failed jobs would no longer go to the failed queue, but, would instead go to #{queue_name}_failed
I have an implementation that I have written at https://github.com/talis/php-resque/pull/1
Would it be worth me sending a pull request?

Send it along; we'll see what happens.  You've already noted the feature drift between the Ruby and PHP versions...  There's a lot of ground to cover to catch up.


GPy.models.SparseGPRegression gives less predictive variance than GPRegression with full data

Hi,
Can anyone provide pointers to how the inducing inputs are chosen/tuned in the GPy implementation of Sparse Gaussian Process (GPy.models.SparseGPRegression).
Also, it is interesting to see that when I train my model using all the data points (using GPy.models.GPRegression), I have higher predictive variance but when I train my model using the Sparse regression module, the predictive variance is low. Anybody has any insight into why this is the case (it's 2d data)? I would assume, more the data, model learning should be better and hence the predictive variance should be lower.
Thanks,
Abhilash

Stale. Please re-open if you're still interested. Sorry for the tremendous delay.


buffers_suffix max size

There should be a way to ask for a prefix of the buffers_suffix, like this:
https://github.com/boostorg/asio/blob/a6008b6427ddfc3222f83c53030c34c802c53b59/include/boost/asio/detail/consuming_buffers.hpp#L96

Can you elaborate?

Since this is a feature and there is no motivating use-case we should close the issue


Use zkAddr format for configuring ZooKeeper addresses in configs

Fixes #299
The serverset name, zk leader namer, and zk storage plugin now all accept ZooKeeper addresses in a consistent way:
zkAddrs:
- host: foo
  port: 123
- host: bar
  port: 456

:star: nice!

:star: 🎆


DEPLOY-632: Update documentation where ingressvalues.yaml file is cre…

…ated

updated README.md

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

I updated also the Optional part, and made it collapsable like it is here: https://github.com/Alfresco/alfresco-infrastructure-deployment#nginx-ingress-custom-configuration.
If is not ok, i will revert those changes.

The steps for deploying this chart are saying to deploy infrastructure in order to have the ingress controller, as it is default with all the dependencies (activemq and identity-service).
Should we offer a command to deploy the infrastructure only with nginx-ingress?


Automated cherry pick of #9410 on release-6.2

Automated cherry pick of #9410 on release-6.2
Cherry pick of #9410 on release-6.2.
/cc  @weblate
NONE

This says "Files changed: 0".

Mmh yeah, all changes are already in the branch. I'm looking at the original PR to see where the missing strings went ... thanks for looking Amy :)


💥 [DevOps] Setup Our Stage3 Server

💥 DevOps ticket

Setup stage3.gradido.net server to test our upcomming new design steps.
@BerndHueckstaedt set green light for it.

May test higher MariaDB version 10.7 o even 10.8? Suggested @clauspeterhuebner .

Done


Bump snapshot version

Build triggered. sha1 is merged.

Build started sha1 is merged.

Build finished.

Codecov Report

:exclamation: No coverage uploaded for pull request base (dev@7ec5351). Click here to learn what that means.
The diff coverage is n/a.

@@          Coverage Diff          @@
##             dev    #126   +/-   ##
=====================================
  Coverage       ?   88.9%
=====================================
  Files          ?      36
  Lines          ?     820
  Branches       ?      88
=====================================
  Hits           ?     729
  Misses         ?      59
  Partials       ?      32

Continue to review full report at Codecov.

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


getCode does not work

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (6130af7 2022-04-07T00:03:16.450116078+00:00)
What command(s) is the bug in?
forge test
Operating System
Linux
Describe the bug
I'm trying to replicate the getCode.t.sol test in a blank project initialized with forge init but it always throws the same "Reason: No such file or directory" error when running the test.
The path is fine and the file is exactly the same as the foundry repo.

// SPDX-License-Identifier: Unlicense
pragma solidity >=0.8.0;

import "ds-test/test.sol";
import "../Cheats.sol";

contract GetCodeTest is DSTest {
    Cheats constant cheats = Cheats(HEVM_ADDRESS);

    function testGetCode() public {
        bytes memory fullPath = cheats.getCode("../WorkingContract.json");
        //bytes memory fileOnly = cheats.getCode("WorkingContract.sol");
        //bytes memory fileAndContractName = cheats.getCode("WorkingContract.sol:WorkingContract");

        string memory expected = string(bytes(hex"6080604052348015600f57600080fd5b50607c8061001e6000396000f3fe6080604052348015600f57600080fd5b506004361060285760003560e01c8063d1efd30d14602d575b600080fd5b6034602a81565b60405190815260200160405180910390f3fea26469706673582212206740fcc626175d58a151da7fbfca1775ea4d3ababf7f3168347dab89488f6a4264736f6c634300080a0033"));
        assertEq(
            string(fullPath),
            expected,
            "code for full path was incorrect"
        );
    }

    function testFailGetUnlinked() public {
        cheats.getCode("UnlinkedContract.sol");
    }
}

I'm fairly confident that the path is supposed to be relative to the root of your project, so the path should be ./src/WorkingContract.json

Indeed, thank u @onbjerg


Textual definition update: remove EC xefs from GO:0004448 def

GO term ID and label for which you request a definition update
GO:0004448 isocitrate dehydrogenase activity

Can you remove the specific EC numbers as attributions for the definition for this term?  They are already corrected assigned as xrefs on the child terms (isocitrate dehydrogenase (NAD+) activity & isocitrate dehydrogenase (NADP+) activity)
id: GO:0004448
name: isocitrate dehydrogenase activity
namespace: molecular_function
def: "Catalysis of the reaction: isocitrate + acceptor = 2-oxoglutarate + CO2 + reduced acceptor." [EC:<IP_ADDRESS>, EC:<IP_ADDRESS>]

@hdrabkin
GO:0004448 isocitrate dehydrogenase activity is the parent for NAD and NADP versions; in this case it seems the enzymes are specific for either cofactors.
Do you agree GO:0004448 isocitrate dehydrogenase activity should be obsoleted?
Thanks, Pascale

I need to check textbooks to confirm this, but my recollection is that, at least in mice and humans and human tumors with somatic mutations, the IDH enzyme that uses NAD+ (IDH2) is different from the one that uses NADP+ (IDH1)and participates in different processes. IDH2 catalyzes a step in the TCA cycle and IDH1 may not have a well-studied process role, but it certainly can't be lumped with IDH1 for function and process annotations. @hdrabkin - any recollections?

@hdrabkin What should we do here? Keep the "GO:0004448 isocitrate dehydrogenase activity" parent term and remove reference to the EC numbers in the def, or just obsolete the term?

Thanks @sjm41
@hdrabkin and I reviewed the guidelines together and this is what we did:

[ ] removed EC from the grouping term GO:0004448
[ ] Made GO:0004448 'do not annotate' - there are 4 EXP that need to be moved to a child

Thanks, Pascale

Yes we did change that, thanks for pointing that out!
Catalysis of the reaction: isocitrate + NAD(P)+ = 2-oxoglutarate + CO2 + reduced NAD(P)H


New feature ##RELATED TO ISSUE RAISED

see I have added the the book mark feature that you asked for , please accept this pr

Great Work, Kudos 👍