Make federation a first-class citizen

This PR makes federation a first-class citizen by effectively adding the concept of registry_hostname to all resources. registry_hostname is a rename of what we currently call remote within our codebases.
Motivation:

There's work that I want to do to no longer send the full buf.yaml over the wire to the backend - we're defining the buf.yaml to not make up part of a Module, and once you do this, it becomes somewhat easy to deconstruct what you send over the wire. Even moreso, I'd argue this is desirable - the backend should not have to concern itself with buf.yamls, their layout, or their parsing, as they will not make up part of a Commit's digest.
To do such deconstruction, you need some message that makes up what we call, ModulePin right now - a Commit and its associated Digest. However, both historically and likely soon-to-be in the future, we've allowed for federation, meaning that it's possible that some `Commits' may lie outside of the given BSR instance you are calling via the API.
You therefore need a way to represent the registry of a Commit both in the request, and returned Commit objects.
It was pointed out that a shortcoming of this API is that federation wasn't accounted for, and this is a use case we currently have for legacy reasons, regardless of what we want going forward (which may be federation as well).

The path to this PR:

First, you realize you need to add a registry_hostname to Commit. Easy enough.
Next, you realize that you need to qualify all IDs on the Commit as scoped to the BSR instance as denoted by registry_hostname. For example, module_id is now the ID of the Module on the BSR instance as denoted by registry_hostname.
Inevitably, this means you need registry_hostnames the whole way down - Modules, Users, Organizations specifically.
At this point, for consistency and because we're letting half of our resources account for federation, you realize you likely want registry_hostname on Tag, VCSCommit, Branch as well.

What this PR does:

Adds registry_hostname to all resources.
Clarifies in the comments that IDs are scoped to the given registry_hostname.
Refactors .*Refs: .*FullNames are moved inside Refs as a nested message Name (this is likely a nice cleanup anyways, as we only use FullNames inside of Refs anyways at the API level). Since both id and name must be scoped to a registry_hostname, it is not desirable to repeat registry_hostname on both a theoretical id wrapper, and .*FullName, hence now defining .*FullName as a nested message that requires other data in the encapsulating message.
Adds a CommitRef that will be used in the CommitService on CreateCommits in a future PR.
Updates basically every comment to say that registry_hostnames need to match the BSR instance you are invoking for now. As this changes, we can relax these comments.

To be honest, I don't like it. It feels very messy. But I don't know if there's a better solution here, assuming we need to account for federation.
Let's discuss this on Monday @rodaine @jhump @Alfus @pkwarren @jchadwick-buf @saquibmian @doriable @mfridman and come to a conclusion.

Closing as we've decided not to move forward with representing federation as-is in the new API, and will evaluate how and when we want to handle federation in the future, likely moving concerns client-side.


Change Initiative: popover not truncating long CI names

I think this only happens if the CI name contains no spaces, if it does contain spaces it can word-wrap.

Investigation shows this is only a problem for unbroken names with underscores.  Hyphens line-break correctly, no simple solution found.  Closing.


ludusavi: 0.25.0 -> 0.26.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/mtkennerly/ludusavi/releases.
meta.description for ludusavi is: Backup tool for PC game saves
meta.homepage for ludusavi is: https://github.com/mtkennerly/ludusavi
meta.changelog for ludusavi is: https://github.com/mtkennerly/ludusavi/blob/v0.26.0/CHANGELOG.md
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.26.0 with grep in /nix/store/4ql0highyxarlsgiywc44ing3r319fvy-ludusavi-0.26.0
found 0.26.0 in filename of file in /nix/store/4ql0highyxarlsgiywc44ing3r319fvy-ludusavi-0.26.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

ludusavi

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/4ql0highyxarlsgiywc44ing3r319fvy-ludusavi-0.26.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ludusavi https://github.com/r-ryantm/nixpkgs/archive/aa28a21c38517912fa87ee2cccfa41cc1f605773.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/aa28a21c38517912fa87ee2cccfa41cc1f605773#ludusavi

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/4ql0highyxarlsgiywc44ing3r319fvy-ludusavi-0.26.0
ls -la /nix/store/4ql0highyxarlsgiywc44ing3r319fvy-ludusavi-0.26.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

ludusavi

Maintainer pings
cc @pasqui23 for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

Do not merge, this update breaks with
# ~/src/nixpkgs on  auto-update/ludusavi [$MS]                                                                                at 22:57:21 ❄ ❌101 took 3s xsh
; $RUST_BACKTRACE=1

# ~/src/nixpkgs on  auto-update/ludusavi [$MS]                                                                                at 22:58:19 ❄ xsh
; result/bin/ludusavi
wp_linux_drm_syncobj_manager_v1#40: error 0: surface already exists
Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@40:
thread 'main' panicked at /build/ludusavi-0.26.0-vendor.tar.gz/wgpu-core/src/device/global.rs:1859:21:
internal error: entered unreachable code: Fallback system failed to choose present mode. This is a bug. Mode: AutoVsync, Options: []
stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: wgpu_core::device::global::<impl wgpu_core::global::Global<G>>::surface_configure::validate_surface_configuration
   3: wgpu_core::device::global::<impl wgpu_core::global::Global<G>>::surface_configure
   4: <wgpu::backend::wgpu_core::ContextWgpuCore as wgpu::context::Context>::surface_configure
   5: <T as wgpu::context::DynContext>::surface_configure
   6: wgpu::Surface::configure
   7: iced_winit::program::run_instance::{{closure}}
   8: iced_winit::program::run::Runner<Message,F,C>::process_event
   9: core::ops::function::impls::<impl core::ops::function::FnMut<A> for &mut F>::call_mut
  10: winit::platform_impl::linux::wayland::event_loop::EventLoop<T>::poll_events_with_timeout
  11: iced_winit::program::run
  12: iced::program::Program::run_with
  13: ludusavi::gui::run
  14: ludusavi::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
thread 'tokio-runtime-worker' panicked at /build/ludusavi-0.26.0-vendor.tar.gz/futures-util/src/stream/stream/select_next_some.rs:32:9:
SelectNextSome polled after terminated
stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::panicking::panic
   3: <futures_util::stream::stream::select_next_some::SelectNextSome<St> as core::future::future::Future>::poll
   4: <tokio::future::poll_fn::PollFn<F> as core::future::future::Future>::poll
   5: <futures_util::stream::unfold::Unfold<T,F,Fut> as futures_core::stream::Stream>::poll_next
   6: <futures_util::stream::stream::map::Map<St,F> as futures_core::stream::Stream>::poll_next
   7: <futures_util::stream::stream::map::Map<St,F> as futures_core::stream::Stream>::poll_next
   8: <futures_util::future::select::Select<A,B> as core::future::future::Future>::poll
   9: iced_futures::subscription::tracker::Tracker::update::{{closure}}
  10: tokio::runtime::task::raw::poll
  11: tokio::runtime::scheduler::multi_thread::worker::Context::run_task
  12: tokio::runtime::scheduler::multi_thread::worker::Context::run
  13: tokio::runtime::context::scoped::Scoped<T>::set
  14: tokio::runtime::context::runtime::enter_runtime
  15: tokio::runtime::scheduler::multi_thread::worker::run
  16: <tokio::runtime::blocking::task::BlockingTask<T> as core::future::future::Future>::poll
  17: tokio::runtime::task::core::Core<T,S>::poll
  18: tokio::runtime::task::raw::poll
  19: tokio::runtime::blocking::pool::Inner::run
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.


Nested link and orphan characters

This PR fixes issue #430.
To fix this issue, I do not allow nested markups in regular links. However, in the future we need to deal with markup on the description of the link as per the syntax specification.
Second, I created a list of orphan characters that might appear inside of a markup that does not allow nested markups. Once out of such markup, I skip any orphan character with an end capture.
Let's say we have the following:
zoo =and *boo and= bar* and *goo zar*

Then Treesitter would collect the following: =and *boo and=, *boo and= bar* and *goo zar*. In this case, we should skip *boo and= bar*.
Similarly, if we have:
This is =a *1 b= and *ab cd* foo

Then Treesitter would collect the following =a *1 b=, *1 b= and * and *ab cd*. In this case, we should skip *1 b= and *.
Feel free to test against additional corner cases. All highlights are correct in the file below:
* Circle

Let a circle with radius \( r \), then the perimeter is given by \(2\pi r\) and the area by \( π * r^2 \).

Some examples:
 - Small circle \( 1 \), \( A = \pi \)
 - Big circle \(1000 \), \(A = \pi * 1000^2\)
 - this is /slanted/
 - a \test
 - a \goof{test}

One more thing \(\).

\( a + b \) and foo

\( a \) b

The book is on the table \enlargethispage{2\baselineskip} and \( \mathbb{R} + 1 \) and \foo{bar}

And \foo{ bar } and \foo{bar } and \foo{bar} and \foo{} and \foo{bar and foo}

hello \foo{bar} and (\(1 - 2\)) and \alpha and \boo and \foo. And (\foo)

Foobar \(n\)-th character, -th should not be higlighted.

This should only highlight =\ab= : \ab12

This should not be math: =\( 1 + 1\)= ~\(1 + 1\)~

This should only be verbatim: =*1*=

This should only be latex: \( 1 + =*2*= \) \(a ~2~ \)

This should not get higlighted: \2ab

T : *\( 1 + *2* \)*

This is *important* and ~foo(x) = x + 1~ foo /bar/

Bold and verbatim *=abc=* slanted and verbatim /=foo=/ bold and slanted */foo/* bold, slanted and verbatim */=abc=/*

This is \( *1 + /1/ \) and *ab =a= cd* and *fo /f f f/ =abc=  and =abc *ab*= a* *=ab=*

abc =a *a* b=

This is =a *1  b= and *ab cd* foo

This is =a *1 b= and* b

This is =a *1* b= and *ab cd* foo

This is [[https://foobar/foo]] foo/

@gzagatti on previous PR you wrote this:

Allow for proper nested markup highlight. The syntax specification says text markup except for code and verbatim should accept any elements from the standard set, which sort of contradicts their own specification that says that text markup should only be preceded by blank space or a set of pre-defined characters (perhaps we can open an issue on the syntax specification upstream). This ensures that =foo= and foo =bar= foo have the same highlight. Also, Emacs and Pandoc export =foo= as bolded code.

Can you give me a better example of this? I don't seem to understand what is actually nestable and what is not.
I did some tests in Emacs orgmode, and it seems everything is nesting almost everywhere.
For example, this text:
zoo =and *boo /and= bar/ test* and *goo zar*

*foo =bar= foo*

Renders like this in emacs:

Second and has bold, italic and verbatim applied to self. Shouldn't some of the markup be missing from it because it's also a verbatim?
Also, second line has a bolded verbatim, which means verbatim is nesting inside the bold.
I also tried =foo *bold* bar= and it did a bold inside verbatim.
I don't think we need to do all this tracking of nested entries, we just need to figure out what to clear or not in this loop https://github.com/nvim-orgmode/orgmode/blob/master/lua/orgmode/colors/markup_highlighter.lua#L320-L328 .
When two entries are matched, this loop clears all "opened" markers that are found between them. If we figure out what we can leave here, other changes might not be necessary. Of course, for links we need to do some additional work, currently I'm talking about markup.

I did a more detailed comparison with Emacs, and I noticed few things:

Latex \word{something} is highlighted only up to { in Emacs, while we highlight the whole thing up to }
Line 22, This should only highlight =\ab= : \ab12 also highlights 1 after ab in Emacs, while we don't highlight numbers
Line 32, bolded math, in Emacs it's bolded only up to 2, while we bold the whole thing
Last line, Emacs bolds a inside verbatim, we don't.

Also, on line 28, if you give it some spacing around 2 in the latex, it will apply bold to it, and even combination of bold + italic if you use non-verbatim (In Emacs):

I think we can solve some of the nested highlights (like verbatim inside latex) by setting a proper priority to a extmark. LateX should always have greater priority over verbatim and code, but not greater priority over other markup.

Thanks for the detailed comments.
First let me go back to the syntax specification. It says that a text markup is composed of the following objects:
PRE MARKER BORDER BODY BORDER MARKER POST

None of the elements above are separated by whitespace characters.
The pattern BORDER BODY BORDER can be denoted as CONTENT. The CONTENT depends on the markup type:

If the markup is code or verbatim, all its content should be considered plain text.

Otherwise, all of its content should be considered as a series of objects from the standard set, i.e. it can contain nested org content.

BORDER should be a non-whitespace character.
Now let me try to tackle some examples to illustrate some points --- all of the images are obtained after exporting the org file to html using Emacs:

In =a + 1= , a + 1 should be considered verbatim.

In =(*foo 1 2)= bar*, (*foo 1 2) which could easily be Lisp code should be considered verbatim. Next, bar* should be plain text. However Emacs will parse this text incorrectly, as it will take ( as verbatim, *foo 12) as bold verbatim and bar* as bold.

In zoo =and *boo /and= bar/ test* and *goo zar* the same logic as in the previous bullet point applies, so and *boo /and should be verbatim, goo zar should be bold, no other markup should apply. However, Emacs will again parse this text incorrectly.

In abc =a *a* b= the same logic as in the previous bullet point applies, so a *a* b should be verbatim, no other markup should apply. However, Emacs will again parse this text incorrectly.

Now, let's pick a nestable markup:

In *a =foo= b*, a =foo=b should be bold and =foo= should be bold and verbatim.

In *=foo=*, =foo= should be bold and verbatim. You might say that this is wrong, because =foo= was preceded by * which is not included in the PRE markers. However, in this case we should consider that = was preceded by the beginning of a line and thus the markup is correct.

Moving on to LaTex markup. Here the specification says that a LaTex fragment should follow on the the patterns below:
\NAME BRACKETS
\( CONTENTS \)
\[ CONTENTS \]

None of the elements above are separated by whitespace characters. But note that CONTENTS can begin with whitespaces.
Fragments like \foo and \foo{bar} follow the first pattern above, since BRACKETS is optional.
NAME consists of alphabetic characters, so it excludes numeric characters. Therefore \ab12 should only highlight \ab. Again, in this case the Emacs implementation is incorrect.
The reason why numeric characters are excluded is because in LaTex macros can only be composed of alphabetic characters. The LaTex wiki states:

Name your new command \wbalTwo and not \wbal2 as digits cannot be used to name macros — invalid characters will error out at compile-time.

Next, concerning \foo{bar}. It is a matter of personal taste whether to include the text {bar} in the highlight or not. Since the syntax specification says that this is just plain text, I prefer to highlight to make this clear to the user.
Now, we can consider some additional examples --- all of the images are obtained after exporting the org file to html using Emacs:

In \( a + 1 \), a + 1 should be LaTex.

In \(  1 +  = *2* =  \) \(a ~2~ \), both 1 + 2 = *2* = and a ~2~ should be LaTex. No additional markup should apply because LaTex markup is non-nestable. Again, Emacs will parse this text incorrectly. Note that ~ is a special character in LaTex so it does not show up in the exported image.

Finally, there should be no priority of verbatim inside of LaTex because is non-nestable. So what appears as verbatim in LaTex fragment should be parsed as plain text. The same applies for LaTex in verbatim, and for any markup inside non-nestable markups.
In summary, Emacs parses some in-line markup incorrectly, specifically it fails when there are overlapping markups like:
*foo /ab cd* ef/

The specification says that the content of a nestable markup should contain elements of the standard set of objects, i.e. it can contain nested org content. It is thus ambiguous with regard to the above construction. I would argue that all nested markup should be closed within its parent. So, to obtain the desired result above we should have:
*foo /ab cd/* /ef/

Fortunately, all html exports from Emacs agree to that. The implementation in this PR is much closer to the markup in the exported html files and follow the syntax specification more strictly.
I hope that this clarifies most of the points you raised above. Let me know if anything else is unclear. I will then try to tackle:

I don't think we need to do all this tracking of nested entries, we just need to figure out what to clear or not in this loop https://github.com/nvim-orgmode/orgmode/blob/master/lua/orgmode/colors/markup_highlighter.lua#L320-L328 .

Thank you for the detailed explanation and examples.
One sentence caught my attention:

However Emacs will parse this text incorrectly, as it will take ( as verbatim, foo 12) as bold verbatim and bar as bold

Does this mean that html export is more correct than Emacs itself? I'm trying to figure out what source should we trust the most?

Emacs
Syntax specification
Exports

My thought was that first there was an Emacs implementation, from which syntax specification and exports were created.
Some of the things in the html export does really make sense, like having "raw strings" in the verbatim/code, but Emacs just doesn't behave that way. I'm not familiar with Emacs/Orgmode history to know how things were developed, and in which order.
I did try to export some of these into PDF via org-latex-to-pdf, and results are similar, so it seems that Emacs does really have less correct highlighting than others.

I am also not very familiar with Emacs/Orgmode history. I have been using it for about a year now and have converted all my notes to orgmode after having tried many different markup languages.
According to the authors of the syntax specification:

This document describes and comments on Org syntax as it is currently read by its parser (org-element.el) and, therefore, by the export framework. This is intended as a technical document for developers and those particularly interested in the syntax. Most users will be better served by the Org manual.

My interpretation is that the syntax tries to follow the export rules as close as possible and should be the source of truth for developers. Therefore, I would set my trust in the following order: (1) syntax specification, (2) exports and (3) Emacs.
Also, according to org-element.el the syntax can be represented as a list. So, overlapping markups are not correct.
Therefore, when the specification says that the content of a markup can be a series of objects from the standard set, it means that all elements must be fully contained in the markup.
When writing this, I have thought about these additional corner cases:
This *Ab *ab cd*

This *Ab *ab* cd*

This *Ab *ab* cd**

This *Ab *ab cd**

I think I should be able to tackle them by tweaking this PR.

Ok, lets follow the syntax specification then. It does make more sense.

I think I should be able to tackle them by tweaking this PR.

Would you be willing to do some refactorings, that I also did as part of #432  ?
I have few things on my mind:

Merge latex_result and result since it's the same thing, just don't apply concealing for latex (I did this in my PR)
Track ranges per line, and then merge them at the end into a single result to iterate and apply extmarks.
Do not track nesting, but instead clear things once we come to the end of the line.

I think if we do things per line we could potentially handle nesting and conflicts more easily. Basically in your edge case example:
This *Ab *ab cd*, we could go from first * to last *, and once we hit the end of line, we can figure out that second * is basically not a valid marker. Of course, this is theory, implementation is more complex.
I don't have much experience writing parsers, so I'm open for suggestions.
If you think it's not possible to do it that way, lets just try to avoid string.gmatch and similar regex stuff as much as possible, since this code runs on every redraw, and I would love to have it as performant as possible.

I will try to follow your suggestions and see if I can implement until next week.

I used to solve a similar problem with brackets
(()(()))
  ^
  open_stack = ( (

   ^
   open_stack = (
   we close one bracket so we pop last bracket from stack and wrap whole text between

Latest master changes should address all of these issues. If you find anything else please open up a separate issue. thanks!


Add standard style

@ironwallaby What do you think of this? It's hooked up to tests too.
More info: https://github.com/feross/standard

I think it's opinionated in the wrong direction. ;) (I favor double quotes, semicolons, and no spaces after keywords or function names.)
That said, it's your project, and I'm happy with obeying whatever style guide you prefer: any guide is better than none!

All the changes look good!

That said, it's your project, and I'm happy with obeying [...]

That's not how open source works :) Happy to defer this until we come up with a better alternative. I'm a big fan of semicolons too but also really like that standard doesn't have any configuration and just works.
Let's let this PR sit and stew for a bit. Maybe the style will grow on us :deciduous_tree:

Completely agree that the zero configuration is super nice. I'll start my changes in #13 from your branch and see how it works for me. :)

:+1: Thanks for giving it a shot. (FWIW - this is the first project I'm trying standard with too)

So, after using standard style, my only major problem with is forcing if branches to be squished together. I think it hurts code clarity. However, in each instance that it came up in the code, there were code stink issues anyway, so refactoring removed the problem entirety.
So, I suppose in that case, requiring weird code style patterns helped. :+1:
While I'm not sold on standard, it's by no means terrible, and it might be worth running with (at least in the short term!) on a small library like this.


Enantiomer

Reference Issue

What does this implement/fix?
The following python  code will generate enantiomers of a molecular structure given in xyz coordinates. It would be useful to have enantiomer when the structure is given in xyz coordinate in some of the databases.
The code flips a molecular structure by taking the geometry given as a XYZ file, and changing the sign in front of the Z coordinates.
Save it, call it flip_xyz, make it executable and call it using e.g.
flip_xyz molecule.xyz flipped_molecule.xyz

@iiitmjay, thanks for putting in the effort to submit a PR.
Unfortunately it's not currently in a form suitable for acceptance into the RDKit.
The PR contains two different pieces of functionality, both of which have serious problems:

The part that's new - the piece that generates the enantiomer of the coordinates from an XYZ file - is a command line script that provides functionality working with a very particular type of file. The RDKit is primarily intended to be used as a library/toolkit to build other pieces of software, as such we generally don't include pure command line scripts like this as part of the library. This is the kind of functionality that people often incorporate into their own collections of RDKit tools that they host in separate github repos. If you think that this would be useful to others, it would be better to create your own repo for it.
The other part of the PR is the tautomer reordering function that we previously discussed. Unfortunately, the structural problems we discussed there have not been addressed: the test you created still doesn't work at all (it contains at least one Python syntax error), isn't implemented using Python's standard unittest functionality. and it hasn't been integrated with the test infrastructure so that the tests are run automatically.

Given the problems, I'm going to close the PR. Before reopening it or resubmitting, please get in touch with me via email so that we can discuss the situation.


Update Pages “home”

Automatically generated by Netlify CMS

👷 Deploy Preview for chic-shortbread-66a66b processing.

Name
Link

🔨 Latest commit
4eb28664986c7fe029fa688abe758f900783d32a

🔍 Latest deploy log
https://app.netlify.com/sites/chic-shortbread-66a66b/deploys/654efb340996510009735635


go domain: complete install prerequisites

README.rst
Setup section
Add prerequisites for GO.

Install a git client for your environment (e.g. from https://desktop.github.com/).

Install our godocjson tool (preprocess godoc output to JSON, in a way similar to jsdoc -X).

.. code:: bash
  go get github.com/rtfd/godocjson

Add go domain in your conf.py.

.. code:: python
  extensions = [ 'sphinxcontrib.golangdomain',...

Before running building your doc, make sure the godocjson executable is in your path.

The golang mapper hasn't been touched in a while, and we never had good docs here. These would be great additions to the docs.


Batch determination KeyError for non-Staff user

Describe the bug
Given a user not having the "Staff" role, e.g. "Admin" or "Staff Admin", when submitting a Batch Determination, then a KeyError (shown via an HTTP 500 error) occurs.
To Reproduce
Steps to reproduce the behavior:

Log in as a non-Staff user (or remove the Staff group from your user in Wagtail Admin)
Visit apply/submissions/all/
Select a couple of submissions having the same status
Click "Status" button (at the top of the table)
Select "Dismiss" from the dropdown
Click "Update"
Click "Send"

See the 500 error.
Expected behavior
Either a permission error or a successful update to the submissions' status.
Priority

Low priority (annoying, would be nice to not see)

Affected roles

Non-Staff who do Batch Determination
Developers
Testers

Desktop (please complete the following information):

OS: GNU/Linux, PureOS 10
Browser: Firefox 115
Version: v5.3.1

Additional context
Found and/or refined by Tris, @frankduncan, and me.

Hey, thanks for submitting this! What user role were you exactly? I tried this as Applicant & Partner and couldn't get the submissions page to render, just hung at a white screen (which should also prob result in a 404). It also isn't in the nav bar at that point.

@wes-otf Admin

@wes-otf See the suggested fix in #3796. If there's a better way we are all for it. Have a great weekend!

Closed via #3796.


Java RFC - 021 Projections API Update Operations Implementation

@tambeau commented on Fri Nov 05 2021
Implementation of Update Operations for Java gRPC Projections API
Update

[x] Projection (Name, Query, EmitEnabled)
[ ] Config (Name, Config)

Update config is not available yet.


[Feat]: ENHANCING THE ACCESSORIES PRODUCTS SAME LIKE OTHER PAGES

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description

all the products in men, women and kids section are in one alignment and design
where as this accessories products does not align to this style...
I'd like to enhance them to the better style along with the add to cart button
Use Case
This would have great user experience
Benefits
No response
Priority
High
Agreements

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC contributor
[X] I'm a Hacktoberfest contributor
[X] I want to work on this issue
[X] I'm willing to provide further clarification or assistance if needed.

@harikasayani
@Tejashri-Taral
While committing  changes I'm getting this way
can you help me with this??

hello can you respond??
@Tejashri-Taral
@harikasayani
I've done done all  the changes to the pages but committing changes is raising a error!


Fix testsuite for task storage

Ensure that it is possible to test against live S3
(tox passenv settings + a pytest CLI option to set the bucket)
Rearrange dependencies so that we can test that the library is usable without boto3
Ensure untested lines are run by the testsuite (e.g. StorageException.__str__)
Improve error handling and testing around invalid result_reference data

With a couple of careully considered no-cover pragma comments, this now provides complete test coverage when the --funcx-s3-bucket argument is provided.
For example, I've been running under tox -- --funcx-s3-bucket sirosen-funcx-test

[sc-11645]


GetYTPlayerConfig - error

It stopped working today 😢
[Extraction] pattern (ytplayer\.config\s*=\s*) failed: The operation couldn’t be completed.

Thanks, will look at it later today

fixed with version 0.1.1


Do not grey options that are active but just not selected

We do not want to grey out any options that are available for the user to select, only the suboptions.
Here the "immediately" option appears to be greyed out and not an option, but it is actually available to select.

And when "immediately" is selected, the embargo should not be greyed out like it is below:

To translate for implementers: the "label" of the radio button shouldn't be gray when it's not selected.


Fail to run "azd up" for sample "AspireWithNode"

Describe the issue:
Run the azd up command failed and the error messages are as follows:

Repro Steps:

Clone code.
Run command cd samples/AspireWithNode.
Run command azd init -> choose Confirm and continue initializing my app -> Enter environment name.
Run command azd up.

Environment:

Azd version: azd version 1.8.0-beta.1-daily.3661089 (commit d078aeb7cf1497aa7c8d629d2f6d434554e0cd9a)
Aspire version: 8.0.0-preview.5.24201.12
Sample: AspireWithNode
Branch: preview.5

Expected behavior:
azd up command can be executed successfully.
@rajeshkamal5050, @vhvb1989 for notification.

Duplicate of https://github.com/Azure/azure-dev/issues/3649


Fix '0 IF 0x01 0x81 ENDIF 1 '  ✅

✅ issue #131
✅ follows contribution guide
✅ code change includes tests

Add the is_pushing_opcode function in the flow.cairo file.This function is to verify if the OP_CODE has the function of pushing the next OP_CODE in the stack. (0x01-0x4b)
Add if validation in the execute function of the engine.cairo file.
If the OP_CODE is a pushing op_code. The verification of is_opcode_disabled is omitted because is not required.
If the OP_CODE is not a pushing op_code. Continue with the verification of the is_opcode_disabled.

(After commits of Agu 22, the results continue to be the same as in the image)
Build

Test

Closes #131

I'd recommend reading this to get a better understanding of how OP_DATA_X and OP_PUSHDATAX work https://wiki.bitcoinsv.io/index.php/Pushdata_Opcodes
The current implementation isn't handling how the opcodes are used fully correctly


Vue 3 css variables

Codecov Report

Merging #210 (274dec6) into vue-3 (ad396c4) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##            vue-3     #210   +/-   ##
=======================================
  Coverage   89.74%   89.74%
=======================================
  Files           2        2
  Lines         195      195
  Branches       32       32
=======================================
  Hits          175      175
  Misses         20       20

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 ad396c4...274dec6. Read the comment docs.


How to set a metadata key/value pair?

I would like to implement the following command to rotate vertuically and horizontally a video.
ffmpeg -i <VIDEO_NAME> -metadata:s:v rotate="-180" -codec copy -y <OUTPUT>

I do it in this way because it is much faster than using hflip() and vflip(), since for these options reencoding is necessary.
Thak you very much in advance!

https://github.com/kkroening/ffmpeg-python/issues/112
Something like stream.output(<output>, metadata='s=v') should work.

Hi it's possibile set the title on metadata title dynamically with your library for example in this ways:
stream = ffmpeg.output(stream,base, **{'metadata:title='tmp)
Help me


Unexpected return from SQLLab query -- no column names

I expect SELECT column names, but get the first row of data in SQLab while querying from Clickhouse?
apache-superset        0.38.1
SQLAlchemy             1.3.24
SQLAlchemy-Utils       0.36.8
clickhouse-driver      0.2.0
clickhouse-sqlalchemy  0.1.6

这个问题好像出现了好久，一直没有被解决，我用的superset1.4.1版本也是这个问题

I have the same problem

Just checking in... are you still experiencing this in newer versions of Superset, e.g. 2.0.1 or current master?

Since we're now on 3.1, on the verge of 4.0, we're not supporting 2.x  or prior versions actively. If anyone is experiencing this issue in current versions, please file a new issue with updated context and repro steps. Thank you for understanding :)


Installed , helium running but can't add to Nebra dashboard
It
It's 2 hours ago I started the hotspot with new image
Why I can't add to Nebra dashboard?

Claimed via local ip dashboard


[Feature][CDCSOURCE] Write to Starrocks auto create table

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
use flink sql to synchronize multi tables, when some tables not exists, it can auto create these tables.
Use case
No response
Related issues
No response
Are you willing to submit a PR?

[x] Yes I am willing to submit a PR!

Code of Conduct

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

Can you provide suggestions on configuration information for ddl statements?

i want to add table model option(primary key, unique key, duplicate key, aggregate key）and bucket num option.
base on primary key column for distributed by hash.
for example.
a table in mysql database
create table test.mysql_test(
id int primary key,
name varchar(50),
age int
).
auto create starrocks table for mysql_test in mysql database.
create table test.mysql_test(
id int,
name string,
age
)
{table_model}(id)
distributed by hash(id) buckets {buckets_num}
@aiwenmo can you help me to provide suggestions?


Added a pubsub channel implementation

This is similar to Tokio's Broadcast channel, except that it doesn't allocate.
The publishers and subscribers are dynamic. They use an &dyn channel reference because it's really annoying to have to specify the mutex and const generics every time.
Do we need fully generic types as well?

I don't see the advantage of every subscriber having its own queue. They can still loose messages because of the fixed queue size. So, you'd only use more memory. Can you maybe clarify what the advantage is?
WRT the message id tracking, if every subscriber had its own queue you wouldn't need it. But in this system with a shared queue, every subscriber must know which items it has already read. It could have read none of the items in the queue, some or all. So you need to keep track of that in some way.
The Lagged error is something we would need. For us it would be a major error if a message wasn't read, so we do need that information. How much we lagged is not very important but the info is there anyways and it's good to see how bad the situation is.
What is possible is to create a convenience method on top that ignores the lag and just tries to give you the next message, that's not a bad idea IMO.
About the name bikeshedding, I don't have strong opinions. Implementing the stream traits is a good idea!
Maybe we should keep the names the same as what Tokio does? That's probably not a bad idea... I'll check

The futures::Sink trait is pretty annoying and its interface doesn't really map very nicely on the current API. Maybe let's wait with that one until somebody actually needs that...

I don't see the advantage of every subscriber having its own queue. They can still loose messages because of the fixed queue size. So, you'd only use more memory. Can you maybe clarify what the advantage is?

That's a good point. The only thing I can think of is that it simplifies the bookeeping, but I agree less memory usage is more important.

WRT the message id tracking, if every subscriber had its own queue you wouldn't need it. But in this system with a shared queue, every subscriber must know which items it has already read. It could have read none of the items in the queue, some or all. So you need to keep track of that in some way. The Lagged error is something we would need. For us it would be a major error if a message wasn't read, so we do need that information. How much we lagged is not very important but the info is there anyways and it's good to see how bad the situation is. What is possible is to create a convenience method on top that ignores the lag and just tries to give you the next message, that's not a bad idea IMO.

Yeah, I think maybe the StreamExt implementation could do that for instance. Wrt. loosing messages being a major error, wouldn't it be another option to have the publisher wait until all subscribers have consumed the message before continuing? Maybe this could be another publisher type, but it seems easier to catch/prevent the error this way.

About the name bikeshedding, I don't have strong opinions. Implementing the stream traits is a good idea! Maybe we should keep the names the same as what Tokio does? That's probably not a bad idea... I'll check

To me, wait and even next is not that descriptive, maybe next_message is better. I'm fine either way, just wanted to start a discussion now before the api is settled.

edit: Ok Tokio uses sender/receiver instead of publisher/subscriber so their naming doesn't really match

The futures::Sink trait is pretty annoying and its interface doesn't really map very nicely on the current API. Maybe let's wait with that one until somebody actually needs that...

I was thinking the futures::Stream trait

Yeah, I think maybe the StreamExt implementation could do that for instance. Wrt. loosing messages being a major error, wouldn't it be another option to have the publisher wait until all subscribers have consumed the message before continuing? Maybe this could be another publisher type, but it seems easier to catch/prevent the error this way.

That's already kind of the case. A subscriber can only lag if a publish_immediate method has been called. This is a balance between practicalities. The channel needs capacity for every publisher that might wait, while no capacity is needed for a publisher that only calls publish_immediate.

I was thinking the futures::Stream trait

I know! It just made me wonder about the Sink trait.
I have now implemented Stream in a way where it ignores lag results alongside some lag free methods.
I've named those methods _pure and I'm open to suggestions :P

Some general throughts:

There's A LOT of "unchecked" stuff. Have you tested it has an impact on the generated code? the compiler is very good at optimizing these out. It'd be great if we could get this to "no unsafe", like the current Channel.
The forced use of dyn feels a bit strange. On one hand you're micro-optimizing the code with lots of "unchecked", but on the other hand you use dyn which probably has more (negative) impact than the (positive) impact of the "unchecked"s. Maybe you could do like the Channel, where publisher/subscriber don't use dyn, and the user can optionally opt into dyn if the generics are too annoying?

Ok, I think I have implemented all the feedback now.
All unsafe is gone and you can now choose between dyn channels and generic channels.
For that last bit I played a little with the PubSubBehavior trait. Pub and Sub now have a generic reference through that trait.
To save a little bit more typing, I made newtypes DynPublisher and Publisher that simply hold a Pub and deref it.
It's a bit verbose, but it saves on having double implementations.

Excellent, thank you so much for writing this 🚀 🚀
bors r+


Projects Pager Styling Broken

The pager doesn't look styled correctly. It is really compressed.
http://dotnetfoundation.org/Projects

Deployed @joeaudette's fix


feature:IR - adding the switch statement parse

This commit adds support for the switch statement parse to its
IR.
Signed-off-by: Nathan Martins<EMAIL_ADDRESS>
- What I did
- How to verify it
- Description for the changelog

Update the docs that referente the entry block to reference the previously block.

Already fixed

I think that there is a lot of improvements that we can made on this implementation, but I think that we can leave as this for now, I don't have any better idea that we can use now.

I totally agree, the code is very complex and should be improved, but I also couldn't think of anything for now.

Added a TODO so we can review this again in the future.


LDAP demo based on setup

Using LDAP environment variables instead of fixed "kopano.demo" for ldap-demo docker image

Thanks for the pr!


Update perplexity-api extension

Description

Renamed commands to match Raycast's built-in AI commands for easier discovery.
Added Change Tone to Friendly command.
Improved tooltips for configuration of command prompts.

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Thanks for the update @xilopaint 🔥
@maximilianzuern could you check this?


Use freedesktop.org xdg-open instead of open

open is aliased to openvt on debian systems.

Updated with fallback for Mac and Windows.


Document how to migrate from "trick" to "MQTT" mode

Since Meross has been heavily limiting API access, I decided to pull the plug and move to Meross LAN for my production environment, and it is working very well. In a few months we'll see how it works with TRVs, but, in the meantime (it's summer here), I can use it to see TRV temperatures and control a light bulb.
I didn't configure my devices to use MQTT, thus, as far as I understood, I'm leveraging the "flaw" in Meross protocol, and it is working great.
Now the question: what will happen when Meross will update the firmwares and, eventually, fix this flaw? I will be forced to configure them all for MQTT.
How difficult will the migration be?
Might it be useful if you write some document about it?

Hey @almico,
If Meross would 'fix' this, you could still use the devices in their original 'pairing' with Meross. You'd just need to know the key in order for the http protocol to work correctly (#40) and still use them with meross_lan.
Pairing the devices to your own MQTT environment is a different story. The process is neither easy nor hard: it works but you'll need a good preparation setting up the correct environment and re-pairing all the devices. It works both with HASSIO mqtt addon and with a 'raw' MOSQUITTO server (this one would need to be setup carefully with certificates, ports, authentication so that's a lot of stuff).
Pairing with your MQTT doesn't free you from the key: you just know it since when you re-pair your devices you set the key in configuration and so you can use it in meross_lan too.
I suggest you to slowly plan and try some testing with just one meross device: you first setup your MQTT environment (I guess HASSIO MQTT addon is the best option in order to keep your HA installation the more 'streamlined') and then re-pair the device and then check it really works. It could be a little pain (or not) but you'll see. Maybe it's easier done than said.
Bear in mind that:

putting Meross devices in your MQTT environment will isolate them from the cloud (good or not)
you'll have 'instant' updates of devices state
you'll 'loose' firmware updates (but you can just disable automatic device updates inside the Meross app)
you'll loose the option to control your devices from another platform (so for instance if your HA is not working/reachable you can't use the device from the Meross app anymore)
you can still go back at any time and re-pair the device with the Meross App ;)

Hey @almico, I'll close this down: there's an excellent guide here and looks like the last HA mosquitto addon is working good now


feature/void

Add a new UnaryOperator void

Nice! This looks good, I'm just wondering what happened to this commit for the compiler support https://github.com/googleprojectzero/fuzzilli/commit/bb872e1b2422540e7290db058c9eb2807c1f1170 @vi3tL0u1s? We can also just land this CL as it is and add the compiler support in a follow-up PR. WDYT?

Hi @saelo, I’ve added the compiler support as you suggested. Thank you so much for the reminder!

Ok great, thanks! I think there's a merge conflict though, and also I think there used to be a compiler test as well (https://github.com/googleprojectzero/fuzzilli/commit/bb872e1b2422540e7290db058c9eb2807c1f1170#diff-e3c74f57e01c1d64375830a153bdede28b838e44615cad0ba7085d5754390c2e), can you add that again, too?

Hi @saelo, I’ve added the compiler test. Regarding the conflict, I believe it might be due to this PR not including the logic for the delete feature, which was merged earlier. I’m not entirely sure how to resolve this. Could you provide some guidance?

Ah yes I see, let me try to figure out how to resolve that :)

Ok, that worked. I guess I'll just merge these commits, then locally squash the merge commit, then force push. A bit hacky but oh well :)

Okay done! I had to change the test a little bit because it ends up redefining the output constant from the prefix: https://github.com/googleprojectzero/fuzzilli/blob/d4796eddf8ebfc901dd11db610dc949d0226dbb2/Sources/Fuzzilli/Util/JavaScriptExecutor.swift#L21 but otherwise, this seems to have worked. Thanks! :)

Thank you so much @saelo!


Contemplate removing rm and/or rename it to something longer?

I mean, face it.  It's BY FAR the most malicious thing that people are going to try.
If we don't need to use that very often for real purposes, we could at least get rid of the easy usage of it.

nvm, already implemented.


std.conv: Avoid undefined bytes in toChars() results for radix 10

The buffer is initialized from right-to-left in initialize(), and unused bytes are left alone. Previously, the whole result wasn't preinitialized with T.init, so the unused buffer bytes weren't well-defined. Initialize it now (with zeros), as the whole buffer is still used for equality/identity comparisons etc.

Does this have a bug report?

It now does.


net: listen tcp: errno -9

What version of Go are you using (go version)?
go1.10beta2
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
GOARCH="mipsle"
GOBIN=""
GOCACHE="/root/.cache/go-build"
GOEXE=""
GOHOSTARCH="mipsle"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/root/go"
GORACE=""
GOROOT="/opt/lib/golang"
GOTMPDIR=""
GOTOOLDIR="/opt/lib/golang/pkg/tool/linux_mipsle"
GCCGO="/opt/bin/gccgo"
GOMIPS="softfloat"
CC="/opt/bin/gcc"
CXX="/opt/bin/g++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -mabi=32 -march=mips32 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build074360272=/tmp/go-build -gno-record-gcc-switches"

What did you do?
Ran this code
package main

import (
	"net"
	"fmt"
)

func main() {
	_, err := net.Listen("tcp", ":8080")
	if err != nil {
		fmt.Println(err)
	}
}

What did you expect to see?
No output
What did you see instead?
listen tcp :8080: errno -9
I'm trying to get Go programs to run on a softfloat mips32r2 router. The first issue I encountered was pipe2 syscall not being supported by the kernel, so I wrote a patch to use pipe syscall plus fcntl instead (see mips_no_pipe2.patch). Now I'm facing this issue with net.Listen always failing. Any help or hints on how to debug this are appreciated.
Thanks,
Alex

This error was caused by epollcreate1() returning ENOSYS instead of -ENOSYS. This caused was interpreted as success and the value of ENOSYS was later passed as a file descriptor to epollctl() leading to the (valid) EBADF.

@daenney, I saw your post about net.Listen() on the RT-AC66U and I thought you might be interested to know that it should work fine now that this is fixed (should be in Go 1.11 or try it out now on master).


Support finding same issue originated markdown that has different name

Why

If you do following instructions, you get two markdown files with different name but same content

close issue → markdown file generated
reopen issue
rename issue
reclose issue → markdown file generated in different name

solved


NotImplementedError: igemmlt not available (probably built with NO_CUBLASLT)

System Info
p3.2xlarge, python 3.12
accelerate==0.30.1
bitsandbytes==0.43.1
transformers==4.40.2
peft==0.10.0
Reproduction
import transformers
from peft import LoraConfig, TaskType, get_peft_model, prepare_model_for_kbit_training
from transformers import InstructBlipForConditionalGeneration

model = InstructBlipForConditionalGeneration.from_pretrained(
    "Salesforce/instructblip-flan-t5-xl",
    quantization_config=transformers.BitsAndBytesConfig(
        load_in_8bit=True,
    ),
    low_cpu_mem_usage=True,
)
peft_config = LoraConfig(
    task_type=TaskType.FEATURE_EXTRACTION,
    inference_mode=False,
    r=8,
    lora_alpha=32,
    lora_dropout=0.1,
    target_modules="all-linear",
)
model = get_peft_model(
    prepare_model_for_kbit_training(model), peft_config
)
model.merge_and_unload()

Expected behavior
No error. But I see the following stacktrace:
NotImplementedError                       Traceback (most recent call last)
Cell In[8], line 1
----> 1 model.merge_and_unload()

File ~/.local/share/hatch/env/pip-compile/amzn-product-dna-science-devel/t-spEv9X/antonstv/lib/python3.12/site-packages/peft/tuners/lora/model.py:784, in LoraModel.merge_and_unload(self, progressbar, safe_merge, adapter_names)
    756 def merge_and_unload(
    757     self, progressbar: bool = False, safe_merge: bool = False, adapter_names: Optional[list[str]] = None
    758 ) -> torch.nn.Module:
    759     r"""
    760     This method merges the LoRa layers into the base model. This is needed if someone wants to use the base model
    761     as a standalone model.
   (...)
    782     ```
    783     """
--> 784     return self._unload_and_optionally_merge(
    785         progressbar=progressbar, safe_merge=safe_merge, adapter_names=adapter_names
    786     )

File ~/.local/share/hatch/env/pip-compile/amzn-product-dna-science-devel/t-spEv9X/antonstv/lib/python3.12/site-packages/peft/tuners/lora/model.py:438, in LoraModel._unload_and_optionally_merge(self, merge, progressbar, safe_merge, adapter_names)
    436 if hasattr(target, "base_layer"):
    437     if merge:
--> 438         target.merge(safe_merge=safe_merge, adapter_names=adapter_names)
    439     self._replace_module(parent, target_name, target.get_base_layer(), target)
    440 elif isinstance(target, ModulesToSaveWrapper):
    441     # save any additional trainable modules part of `modules_to_save`

File ~/.local/share/hatch/env/pip-compile/amzn-product-dna-science-devel/t-spEv9X/antonstv/lib/python3.12/site-packages/peft/tuners/lora/bnb.py:95, in Linear8bitLt.merge(self, safe_merge, adapter_names)
     91     state.SCB = weight.SCB
     93 # Dequantize the result of identity matrix and int8 weight because bitsandbytes does not support int8
     94 # dequantization directly
---> 95 output = dequantize_bnb_weight(weight, state=state)
     96 if not self.use_dora[active_adapter]:
     97     w_data = output.to(lora_data.dtype).to(lora_data.device) + lora_data

File ~/.local/share/hatch/env/pip-compile/amzn-product-dna-science-devel/t-spEv9X/antonstv/lib/python3.12/site-packages/peft/utils/integrations.py:68, in dequantize_bnb_weight(weight, state)
     66 if state.CxB is None:
     67     state.CxB, state.SB = bnb.functional.transform(weight.data, to_order=state.formatB)
---> 68 out32, Sout32 = bnb.functional.igemmlt(im, state.CxB, Sim, state.SB)
     69 return bnb.functional.mm_dequant(out32, Sout32, SCim, state.SCB, bias=None).t()

File ~/.local/share/hatch/env/pip-compile/amzn-product-dna-science-devel/t-spEv9X/antonstv/lib/python3.12/site-packages/bitsandbytes/functional.py:2333, in igemmlt(A, B, SA, SB, out, Sout, dtype)
   2330         has_error = lib.cigemmlt_ampere_8(ptr, m, n, k, ptrA, ptrB, ptrC, ptrRowScale, lda, ldb, ldc)
   2332 if has_error == 100:  # `ERR_NOT_IMPLEMENTED` is defined as 100 in `ops.cu`
-> 2333     raise NotImplementedError("igemmlt not available (probably built with NO_CUBLASLT)")
   2335 if has_error:
   2336     print(f"A: {shapeA}, B: {shapeB}, C: {Sout[0]}; (lda, ldb, ldc): {(lda, ldb, ldc)}; (m, n, k): {(m, n, k)}")

NotImplementedError: igemmlt not available (probably built with NO_CUBLASLT)

Hi @stevenmanton,
Thanks for the details. This issue is showing up because the Tesla V100 does not support the int8 tensor cores. There's probably some improvement we can make here on the PEFT and/or BNB side to make this fail more graciously (or fall back to the slower algorithm).
In the meantime, you might have better luck using the 4bit quantization, or switch to an instance with a newer GPU (e.g. g4dn, g5, g6).

Thanks for the feedback! Yes, a more descriptive error code would certainly be useful. In my case, I actually trained a model with the 8-bit quantization so that the memory consumption was less. However, I found that the inference was much faster loading the un-quantized model, since I couldn't merge the weights. I saw some slight numerical differences in the output, but nothing very large for the test samples I looked at.


Unable to Instantiate CW3 Contract on Osmosis Chain

I am using the SigningCosmWasmClient and attempting to instantiate a simple CW3 on Osmosis, but I am running into the following error message:
Uncaught (in promise) Error: Broadcasting transaction failed with code 2 (codespace: sdk). Log: unable to resolve type URL /cosmwasm.wasm.v1beta1.MsgInstantiateContract: tx parse error     at SigningCosmWasmClient.broadcastTx (cosmwasmclient.ts:256:1)     at async SigningCosmWasmClient.instantiate (signingcosmwasmclient.ts:252:1)     at async onSubmit (CreateNewWalletForm.tsx:287:1)
Everything seems to be correct and I am wondering if there is an issue with the signing client not being able to find the type URL.
I am using
"@cosmjs/cosmwasm-stargate": "^0.25.6",
and here is the relavent code
    const client: SigningCosmWasmClient =       await SigningCosmWasmClient.connectWithSigner(         'https://testnet-rpc.osmosis.zone/',         offlineSigner       );
const msg: any = {
  voters: [
    {
      addr: 'osmo1XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX',
      weight: 50
    },
    {
      addr: 'osmo1XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX',
      weight: 50
    }
  ],
  threshold: 51,
  max_voting_period: {
    time: 604800
  }
};

const result = await client.instantiate(
  'osmo1XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX',
  CODE_ID_TESTNET,
  msg,
  'my-fun-cw3'
);

Could this be a bug with the signing client?

This was user error.

@swizzmagik Do you happen to recall what the solution for this was?

@kevinroleke the threshold message was incorrectly formatted and instead of how I had it above it needed to be:
const msg: any = {
  voters: [
    {
      addr: 'osmo1XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX',
      weight: 50
    },
    {
      addr: 'osmo1XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX',
      weight: 50
    }
  ],
  threshold: {
    absolute_count: {
      weight: 51
    }
  },
  max_voting_period: {
    time: 604800
  }
};

@swizzmagik How did you initialize your offline signer? Seem to be running into some issues with setting that up

@ratankaliani This is essentially how we did it. I hope this helps!
`
const getOfflineSigner = async () => {
if (!window.keplr || !window.getOfflineSigner) {
throw new Error('Error connecting to wallet or keplr');
}
await window.keplr!.enable(network.chainInfo.chainId);
return await window.getOfflineSigner(network.chainInfo.chainId);
};
const getSigningClient = async (): Promise<
SigningCosmWasmClient | undefined

=> {
const offlineSigner = await getOfflineSigner();

return await SigningCosmWasmClient.connectWithSigner(
  network.chainInfo.rpc,
  offlineSigner,
  {
    gasPrice: {
      amount: Decimal.fromUserInput(network.fee.gas, 4) as any,
      denom: network.fee.amount[0].denom
    }
  }
);

};`


Experiencing ArgumentNullException on login callback

Hey, I'm pretty sure I have everything setup properly based on the guide in your readme file, but on the callback (after visiting the IDP) I'm getting the following error:
crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100]
      Unhandled exception rendering component: Failed to handle login call back, response URL 'https://localhost:4000/authentication/login_callback#state=HRdqLNnA6Eeap23YwiTqZt-RG41BfeeOTf-5cUKyeNA&session_state=f47d2784-6bc6-4e43-9976-6437dfb30b7c&code=5933f67d-201a-4871-b080-78d71610c34a.f47d2784-6bc6-4e43-9976-6437dfb30b7c.a09a64c7-48f7-4ec6-bc15-2fc79b498bff'.
System.Security.SecurityException: Failed to handle login call back, response URL 'https://localhost:4000/authentication/login_callback#state=HRdqLNnA6Eeap23YwiTqZt-RG41BfeeOTf-5cUKyeNA&session_state=f47d2784-6bc6-4e43-9976-6437dfb30b7c&code=5933f67d-201a-4871-b080-78d71610c34a.f47d2784-6bc6-4e43-9976-6437dfb30b7c.a09a64c7-48f7-4ec6-bc15-2fc79b498bff'.
 ---> System.ArgumentNullException: AuthenticationResponse (Parameter 'State')
   at ITfoxtec.Identity.BlazorWebAssembly.OpenidConnect.OpenidConnectPkce.LoginCallBackAsync(String responseUrl)

I've had a look at your OpenidConnectPkce class but couldn't see what the issue should be. (Was thinking it might be the casing on the "state" param, but changing it to  "State" instead yielded no positive result. :/
I'm pretty new at blazor, so I can't attach the debugger. But let me know if I can provide any information you might need.

Looking at the code the issue seems to be that the fragment isn't parsed correctly. The first parameter in the fragment will contain a '#'.
A quick test with using this to parse the fragment instead of reading it directly from the Uri in the GetResponseQuery method of the :
string fragment = rUri.Fragment;
            if (fragment[0] == '#')
                fragment = fragment.Substring(1);

I've created the pull request here: https://github.com/ITfoxtec/ITfoxtec.Identity.BlazorWebAssembly.OpenidConnect/pull/11 that should fix this.

Thank you for the bug report. The bug is fixed in commit  https://github.com/ITfoxtec/ITfoxtec.Identity.BlazorWebAssembly.OpenidConnect/commit/71abff2556c3662e81786c5181ecbff107d67007

Bug fixet in version 1.5.0 https://github.com/ITfoxtec/ITfoxtec.Identity.BlazorWebAssembly.OpenidConnect/releases/tag/1.5.0

Nice thanks!


Package request: posting

Project description
Posting
The API client that lives in your terminal.
Posting is a beautiful open-source terminal app for developing and testing APIs.
Fly through your API workflow with an approachable yet powerful keyboard-centric interface. Run it locally or over SSH on remote machines and containers. Save your requests in a readable and version-control friendly format.

Metadata

homepage URL: https://posting.sh
source URL: https://github.com/darrenburns/posting
license: Apache 2
platforms: unix, linux, darwin

Add a :+1: reaction to issues you find important.

Duplicate of #327855


add heart beat handler to jetty

Please answer these questions before submitting pull request

Why submit this pull request?

[x] Bug fix

[ ] New feature provided

[ ] Improve performance

Related issues

Bug fix

Bug description.
Normal access heartbeat interface appears 405
How to fix?
add jettyServer.addHandler(new InstanceHeartBeatServletHandler(getManager())); to AgentModuleJettyProvider class's addHandlers method.

New feature or improvement

Describe the details and related test reports.

Coverage increased (+0.003%) to 24.732% when pulling 76d471cfb311f18608dddde5d33fd862999d7e9b on tincopper:master into af03e9260745cf3755ff2682d0509eda686d9512 on apache:master.


Documentation links not working

the documentation links for sample queries are not working.

This applies to the "cached set of queries" - links seem to be fine as long as GE can get them from DevX API. It looks like:
https://github.com/microsoftgraph/microsoft-graph-explorer-v4/blob/01a8e74285a60a049630e89935941da7540f0de5/src/app/views/sidebar/sample-queries/queries.ts
Needs to update their links to match https://github.com/microsoftgraph/microsoft-graph-devx-content/blob/dev/sample-queries/sample-queries.json


missing restrictions / wrong behavior for special characters for SSID and password

right now its possible to create and edit networks and use almost every possible character without any restrictions. Tests showed different effects for using e.g. "&" oder " ' "(apostrophe) as SSID / password.
Expected behavior: following characters should be allowed and supported:
a-z A-Z 0-9 ! " # $ % & '( ) * + , - . / : ; < = > ? @ [ \ ] ^ _ ` { | } ~
Result: buggy characters which to be fixed:
"<>'&
its propably a socketman/openwrt issue, feel free to ask me in slackchat for more input.

"
<
>
'
&

Are you saying that SSID's or password that contain these characters don't work?

yes<

'

Except that one, which is sanitised in the back end, the rest should not cause any issues.

we tried it yesterday with an ubiquiti lite, its not working as expected.
<>& get translated to some code
' destroyes the openwrt config
" interrupts ct cloud saver with error

We used to over validate. Now we added so many international customers, we've dropped off.
Looks like we have to be more strict again.

I've checked this and they're all allowed but get santized.
" becomes:
option ssid        'My SSID "'

&& becomes:
option ssid        'My SSID &&'

Actually, I've just checked the backend and only the " & ' characters are being filtered in this way.
However, the way that they configs are being rendered causes the problem.
The good news though is that the new version of Socketman addresses this. SM will be out later this month so I might close this.

ok maybe my understanding for "santized" is wrong, what should it mean ? if i enter the password "ernie&bert" in the cloud i will have to enter "ernie&bert" as password to connect... also the radioed displayed ssid for "Peter&Paul" is broadcasted as "Peter&Paul".....

At the moment, it looks like the configs are being cleaned / sanitized twice.

I've added a quick fix for now to remove the double sanitize. Changes will be live today

@simonmorley your fix works for < > and &.
The apostrohe ' is still a problem because it has impact in the openwrt wlan config. Maybe dont allow it in the frontend as easiest fix ?

Can you paste your openwrt config file with the ' please

ok i entered e.g. ssid name "test'ssid" and in the openwrt wlan config its saved as line
option ssid        'test\'ssid' which probably leads to a syntax error.
for the password its "secret'key" which is pasted in the configfile as
option key         'secret'key' which also leads to a syntax error.

I'll add a validation to the front and back-end. Don't think the SSID is an issue, it's the passy field that would crash it.

We've added another validation on the backend for the ' in the password and SSID.  This will be available when the current beta build has been merged in.


fix some bugs under linux

fix some pathes errors in cmake file
add log.h
The implement of template method must appear in the header file. http://stackoverflow.com/questions/1111440/undefined-reference-error-for-template-method

Hi @you-n-g, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Xiao Yang (Person Consulting)). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;


update listworkflow query

Summary
Updates ListWorkflows query with updated schema

All looks good to me! But will defer approval to Meg


Installer may black screen

When the installer has installed TCP Gecko and I press A to return to the home menu it sometimes ends up freezing with a black screen before it goes back to the home menu. I just wanted to mention this since it seems like it didn't happen with older versions of the installer.

I always got the same issue when trying to install PyGecko on 4.1.0.

Did it do the exit to grey that IM_Close does? I've never had any issues on 5.5.1, only when userspace and the browser misbehaves, and usually doing a clean reboot and clearing cookies fixes it (which it happens rarely)


MariaDB to PostgreSQL data migration

This issue covers the current progress with the data migration initiative and outlines detailed next steps. Our goal is to eventually migrate all of the data in MariaDB into a PostgreSQL production database, ensuring the entire Macrostrat infrastructure operates off a single server.
Current milestones

We have taken Macrostrat production data from MariaDB, normalized it using pre-scripts and post-scripts, and successfully cloned the data into a PostgreSQL database: macrostrat_two, within the schema: macrostrat_temp.
This migration is performed within the Macrostrat's development environment.
We now have a fully functioning instance of MariaDB data in PostgreSQL, which is a big step towards managing all data in PostgreSQL.

We are currently in the process of updating a v2 API clone (possibly to become v3) by redirecting all endpoints from the MariaDB database to the PostgreSQL macrostrat_two clone. This step is to ensure that we can have a fully functioning API that works smoothly with PostgreSQL data only. We are almost complete with this step, and only have 7 more endpoints to redirect.
Next steps
After all endpoints are repointed, we need to do some in-depth testing to ensure that this API functions identically to production. As of now, we can currently say that the endpoints execute and successfully run when repointed to the PostgreSQL macrostrat_two clone. However, we need to ensure that data is being returned in the same format as production.
Code updates

#61 tracks the evolution of the migration scripts
https://github.com/UW-Macrostrat/macrostrat-api/pull/229 tracks API changes required for Macrostrat's v2 API to operate solely using PostgreSQL

Migration status reports
MariaDB to macrostrat_two (standalone PostgreSQL database)
Below are some stats that show our progress with cloning the MariaDB data into the PostgreSQL macrostrat_two database. These results (from compare_data_counts()) show the table, row count, and column count comparisons between any two databases. Stats are executed from utils.py in MariaDB Migration to PostgreSQL

Data Comparison: The comparison between the MariaDB production database and its clone on the PostgreSQL macrostrat_two database shows that all tables, row counts, and column counts are identical after the migration.

MARIADB (db1) comparison to PG MACROSTRAT_TWO (db2). These should be clones.

Success! All tables exist in both MariaDB and PG Macrostrat_Two. Checking row counts....

Success! All row counts in all tables are the same in both MariaDB and PG Macrostrat_Two!

Success! All column counts in all tables are the same in both MariaDB and PG Macrostrat_Two!

macrostrat_two to existing Macrostrat database, macrostrat schema in PostgreSQL
We conducted a data comparison between the cloned PostgreSQL macrostrat_two database and the existing PostgreSQL macrostrat database in the Macrostrat development environment. The results indicate discrepancies in tables, row counts, and column counts.
Next Steps
We'll need to decide how to resolve these discrepancies. Potential solutions could be merging the macrostrat_two data into the macrostrat database, or vice versa. We could also maintain the data in separate databases as is. Let me know your thoughts on how to proceed.
PG MACROSTRAT_TWO (db1 maria db clone) comparison to PG MACROSTRAT (db2). This will show what data needs to be moved over from Maria to PG prod.

ERROR: PG Macrostrat_Two tables that are not in PG Macrostrat:
 ['canada_lexicon_dump', 'colors', 'col_areas_6april2016', 'col_equiv', 'col_notes', 'interval_boundaries', 'interval_boundaries_scratch',
'lookup_measurements', 'measuremeta_cols', 'minerals', 'offshore_hole_ages', 'offshore_sections', 'offshore_sites', 'pbdb_matches',
rockd_features', 'ronov_sediment', 'stats', 'strat_names_lookup', 'structures', 'structure_atts', 'tectonics', 'temp_areas',
'uniquedatafiles2', 'units_datafiles', 'unit_boundaries_backup', 'unit_boundaries_scratch', 'unit_boundaries_scratch_old', 'unit_contacts',
'unit_equiv', 'unit_measures_pbdb', 'unit_seq_strat', 'unit_tectonics', 'offshore_baggage', 'offshore_fossils', 'unit_dates', 'unit_liths_atts',
'unit_notes']

ERROR: PG Macrostrat tables that are not in PG Macrostrat_Two:
 ['strat_name_footprints', 'grainsize', 'pbdb_collections', 'pbdb_collections_strat_names', 'unit_lith_atts', 'temp_rocks', 'temp_names']

ERROR: Row count differences for 25 tables in both PG Macrostrat_Two and PG Macrostrat databases:
Table Name: (PG Macrostrat_Two Rows, PG Macrostrat Rows)
{'autocomplete': (58361, 58488), 'cols': (5647, 5651), 'col_refs': (5709, 5713), 'intervals': (1510, 1626), 'liths': (200, 207),
'lookup_strat_names': (51211, 51214), 'lookup_units': (49812, 119462), 'lookup_unit_attrs_api': (49811, 119461), 'lookup_unit_intervals':
(49812, 119462), 'measuremeta': (129739, 129744), 'measures': (3418720, 3419018), 'projects': (11, 12), 'refs': (205, 210), 'sections'
(11586, 12713), 'strat_names': (51211, 51214), 'strat_names_meta': (43278, 43281), 'strat_tree': (29452, 29459), 'timescales': (25, 31),
'timescales_intervals': (1830, 1971), 'units_sections': (50386, 119762), 'unit_measures': (105302, 105048), 'unit_strat_names': (28315,
28319), 'units': (50134, 119510), 'unit_environs': (55578, 125140), 'unit_liths': (99062, 173515)}

ERROR: Column count differences for 14 tables in both PG Macrostrat_Two and PG Macrostrat databases:
Table Name: (PG Macrostrat_Two Columns, PG Macrostrat Columns)
{'cols': (13, 15), 'col_groups': (4, 3), 'environs': (6, 5), 'lith_atts': (5, 4), 'lookup_strat_names': (28, 22), 'lookup_unit_intervals': (19, 20),
'measuremeta': (14, 15), 'measures': (13, 12), 'sections': (6, 2), 'strat_names': (9, 5), 'strat_tree': (6, 4), 'unit_strat_names': (4, 3), 'units':
(15, 14), 'unit_environs': (7, 5)}

Some small questions @amyfromandi
There seem to be more rows in macrostrat vs. macrostrat_two in almost all cases. This seems surprising. We should expect to see more rows in macrostrat_two in almost all cases.

Additionally, with few exceptions, macrostrat should have a strict subset of primary keys that are in macrostrat_two. Perhaps we could add a quick check for that for certain tables?
We'll have to focus on what's going on with 'strat_name_footprints', 'grainsize', 'pbdb_collections', 'pbdb_collections_strat_names', and 'unit_lith_atts'. Where do they come from? Are they used? Are they really not present in MariaDB? etc.
'temp_rocks' and 'temp_names' are not important, presumably

Also, one other comment — the v2 API here is meant to stay stable as v2, and not evolve to v3. So ensuring parity of responses from MariaDB to PostgreSQL is critical.

We have to look into the following tables:

strat_name_footprints

grainsize

pbdb_collections

pbdb_collections_strat_names

unit_lith_atts

temp_rocks

temp_names'
are not important

strat_name_footprints is created by a script in the PostgreSQL database, as a sort of look-up table.
Seems bad that we're missing grainsize

The following tables are not found in MariaDB but are important to preserve in PostgreSQL. We should copy their contents out of the macrostrat schema before doing a restore.

macrostrat.grainsize -> macrostrat_defs.grainsize
macrostrat.pbdb_collections -> macrostrat_pbdb.collections
macrostrat.pbdb_collections -> macrostrat_pbdb.collections_strat_names

The tables should be "mirrored" into the macrostrat schema using view definitions so that APIs that refer to them don't break.

Some small questions @amyfromandi
There seem to be more rows in macrostrat vs. macrostrat_two in almost all cases. This seems surprising. We should expect to see more rows in macrostrat_two in almost all cases.

Additionally, with few exceptions, macrostrat should have a strict subset of primary keys that are in macrostrat_two. Perhaps we could add a quick check for that for certain tables?
We'll have to focus on what's going on with 'strat_name_footprints', 'grainsize', 'pbdb_collections', 'pbdb_collections_strat_names', and 'unit_lith_atts'. Where do they come from? Are they used? Are they really not present in MariaDB? etc.
'temp_rocks' and 'temp_names' are not important, presumably

Here are the latest variances after MariaDB was restored into the dev environment.
ERROR: Macrostrat_Two_Maria tables that are not in Macrostrat:
 ['stats', 'strat_names_lookup', 'structures', 'structure_atts', 'tectonics', 'temp_areas', 'uniquedatafiles2',
'units_datafiles', 'unit_boundaries_backup', 'unit_boundaries_scratch', 'unit_boundaries_scratch_old',
'unit_contacts', 'unit_dates', 'unit_equiv', 'unit_notes', 'unit_measures_pbdb', 'unit_seq_strat',
'unit_tectonics', 'unit_liths_atts', 'canada_lexicon_dump', 'colors', 'col_areas_6april2016', 'col_equiv',
'col_notes', 'interval_boundaries', 'interval_boundaries_scratch', 'lookup_measurements', 'offshore_baggage',
'measuremeta_cols', 'minerals', 'offshore_fossils', 'offshore_baggage_units', 'offshore_hole_ages', 'offshore_sections',
'offshore_sites', 'pbdb_intervals', 'pbdb_liths', 'pbdb_matches', 'rockd_features', 'ronov_sediment']

ERROR: Macrostrat tables that are not in Macrostrat_Two_Maria:
 ['strat_name_footprints', 'grainsize', 'pbdb_collections', 'pbdb_collections_strat_names', 'unit_lith_atts',
'temp_rocks', 'temp_names']

ERROR: Row count differences for 26 tables in both Macrostrat_Two_Maria and Macrostrat databases:
Table Name: (Macrostrat_Two_Maria Rows, Macrostrat Rows)
{'sections': (12813, 12713), 'strat_names': (51229, 51210), 'strat_names_places': (50321, 50288),
'strat_tree': (29467, 17519), 'units': (127229, 119508), 'timescales': (37, 31), 'timescales_intervals': (2194, 1970),
 'units_sections': (127481, 119762), 'unit_boundaries': (135708, 53799), 'unit_econs': (3157, 3148),
'unit_measures': (105307, 105048), 'unit_strat_names': (28322, 28316), 'unit_environs': (134617, 125138),
 'unit_liths': (189907, 173513), 'autocomplete': (58599, 58488), 'cols': (5654, 5651), 'col_areas': (5357, 5351),
 'col_groups': (352, 350), 'col_refs': (5716, 5645), 'intervals': (1715, 1626), 'liths': (212, 207),
'lookup_strat_names': (51229, 51214), 'lookup_units': (127229, 119462), 'lookup_unit_attrs_api': (127228, 119461),
lookup_unit_intervals': (127229, 119462), 'refs': (213, 210)}

ERROR: Column count differences for 13 tables in both Macrostrat_Two_Maria and Macrostrat databases:
Table Name: (Macrostrat_Two_Maria Columns, Macrostrat Columns)
{'sections': (6, 2), 'strat_names': (9, 5), 'strat_tree': (6, 4), 'units': (15, 13), 'unit_strat_names': (4, 3),
 'unit_environs': (7, 5), 'cols': (13, 16), 'environs': (6, 5), 'lith_atts': (5, 4), 'lookup_strat_names': (28, 22),
 'lookup_unit_intervals': (19, 20), 'measuremeta': (14, 15), 'measures': (13, 12)}

test comment


Audio not synced with video

Netflix add-on version
1.20.3
Operative systems used
CoreELEC
Kodi version used
Kodi 20 (Nexus)
Description of the bug
My system is installed on a Tanix TX3 mini, in the past it had already given the same problem, which was then resolved on its own, but now it My system is installed on a Tanix TX3 mini, in the past it had already given the same problem, which was then resolved on its own, but now it has persisted for days and the difference between audio and video is much longer.Really annoying.sisted for days and the difference between audio and video is much longer.Really annoying.
Steps to reproduce the behavior
No response
Debug log - mandatory
https://paste.kodi.tv/yuqutobota.kodi
Possible fix
No response
Additional context
No response
Screenshots
No response

unfurnately i have already investigated to this last year, but the problem was on android only and limited to specific hardware
after some months the problem is disappeared without do nothing
so i have not understand exactly where come the problem but its not addon dependent and no real solutions
you can try use "audio offset" on addon "playback" settings as workaround

I had already seen the "audio offset" function, but it is not easily usable, furthermore the defect is also progressive, I don't think it is feasible. I'll do some tests. Thanks anyway and good work.

I managed to solve the audio synchronization problem by lowering the resolution from 1080 to 720 by operating in the settings, I hope it helps you and everyone who has encountered my same problem.


fix: Improve rendering of program output to fit window dimensions.

Currently, the rendering of program output is a bit wonky. For example, notice below how the visualization doesn't expand to fill the available width and is far too tall for the container.

Fortunately, Plot allows us to specify manual widths and heights of plots. We can take advantage of this by passing along the clientWidth and clientHeight properties of the containing DOM node to the invisible iframe where the plot is rendered. This should ensure we get nicely-sized plots for the program output.
In addition to the above, the following improvements should be in scope for this issue:

[ ] Add an event listener to trigger program runs on Shift + Enter, Cmd + S, and Ctrl + S.
[x] Show a program as "stale" by lighting up its Execute button (á la Observable).

Addressed in #19.

[ ] Debug and address any issues around tick marks; we're currently rendering far too many tick marks.

90% of the implementation added in #18.


Adding an experience system

While playing the game, characters in a party will be able to gain experience while facing off the AI and getting through a level. The design for the experience will have to keep in mind that at first, it should be easy to level up but as time passes, it will take longer.
By leveling up a character, players will be given the opportunity to increases the stats of their character by using skill points.

[x] Deciding which algorithm to use to level up characters in a party
[x] Design stats for every character type to represent their job role
[ ] Create a view for skill update

Since the last 2 commits, both the formula to compute the experience points and the manager to distribute them have been implemented. The static interface for leveling up a character has been made and all that remains is to create it in the dynamic prototype

I'll consider the matter for the experience system as completed for now.


[zh]adjust format in tasks/administer-cluster

[zh]adjust format in tasks/administer-cluster
  % ./scripts/lsync.sh content/zh/docs/tasks/administer-cluster/dns-debugging-resolution.md
content/zh/docs/tasks/administer-cluster/dns-debugging-resolution.md is still in sync

 %./scripts/lsync.sh content/zh/docs/tasks/administer-cluster/network-policy-provider/calico-network-policy.md
content/zh/docs/tasks/administer-cluster/network-policy-provider/calico-network-policy.md is still in sync

 % ./scripts/lsync.sh content/zh/docs/tasks/administer-cluster/reserve-compute-resources.md
content/zh/docs/tasks/administer-cluster/reserve-compute-resources.md is still in sync

 % ./scripts/lsync.sh content/zh/docs/setup/best-practices/node-conformance.md
content/zh/docs/setup/best-practices/node-conformance.md is still in sync

/lgtm
/approve


Do not parse volume from revision part

Related #125
Fixing these records:
✅ | NIST IR 4335v1990rNov1990 | NIST IR 4335rNov1990 | ✅ | NIST.IR.4335v1990rNov1990 | NIST.IR.4335rNov1990 | The NIST PDES toolkit: technical fundamentals
✅ | NIST SP 260-126v2013r2013 | NIST SP 260-126 rev 2013 | ✅ | NIST.SP.260-126v2013r2013 | NIST.SP.260-126rev2013 | The NIST Traceable Reference Material Program for Gas Standards

@mico can you help fix the conflict and merge? Thanks.


Use monkeypatch to eliminate side effects in config tests

While testing the IOPIPE_ENABLED issue I noticed that the config tests were setting os.environ values that persisted beyond the scope of their tests. This can have unintended side effects with other tests. Instead, using monkeypatch we can patch the environment only within the scope of the test itself.

@pselle Is this ok to merge?


Unable to create Repo Ruleset if RepositoryName fields are empty

Same as #2809 but for RepositoryName conditions.
Receiving same error 422 Validation Failed [{Resource: Field: Code: Message:Invalid target patterns: ''}] when "exclude" is empty and omitted.
Expected Behavior:
The github.Ruleset struct should include all the necessary fields to create a GitHub Ruleset, ensuring that no required fields are omitted, allow users to create ruleset successfully without encountering any errors.
Steps to Reproduce:
Both conditions.repository_name.include and conditions.repository_name.exclude fields are required even when empty.
Additional Information:
go-github library version: v54.0.0

@ysoldak - would you like to submit a PR yourself, or shall I open this up to our wonderful community of contributors to this repo?

@gmlewis yes, I shall make a PR, no prob. Filed the issue late Friday so I don't forget :D

@gmlewis yes, I shall make a PR, no prob. Filed the issue late Friday so I don't forget :D

Excellent, @ysoldak !  Thank you!
It's yours.

Check out our CONTRIBUTING.md guide for writing a PR - it has some helpful tips like the reminder to run go generate ./... and push the results along with running tests locally with go test ./... to make sure everything is working.  Oh, and of course, running gofmt on your code in case you don't already have that integrated with your editor on-save (which I much prefer - actually I use goimports).

It's yours now, @gmlewis :P

That was fast.  :joy:


Proc improvement

I tried to improve processes widget to be more in line with the original gotop version. This should fix #49 and partially improve #67.
old process widget

new process widget

Thanks, this looks much better!


bug(): virtualscroll does not resize correctly when the platform has resized

Ionic version:  (check one with "x")
[ ] 1.x (For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[x] 3.x
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
Grid breaks after resizing
Manual WINDOW resizing: https://youtu.be/X1eoQjR3s34
Automatic BODY resizing: https://youtu.be/zElUNvA6pDY
Expected behavior:
Grid not to break. realistic scenario is screen rotation, iPad multitasking, windows pinning, etc (anything that changes window width)
Manual video is quite disturbing (many weird things), while automatic is better.
Steps to reproduce:
Open the conference app, go to speakers, then run:
let i = 1688;
function r() {
  if (i-- <= 320) return;
  document.body.style.width = i + "px";
  setTimeout(r, 10);
}
r();

Thanks for opening an issue. So that demo is a little weird because that page also uses virtual scroll and a little custom css to get it to look right. Does this happen with just a normal grid setup?

That is what the question mark is for, I have no idea if this specifically relates to grid, I am guessing grid + vs then..
Just wondered around and saw this strange thing,..
vs is  one of the bigger things needed to be addressed in v3/v4

Current behavior:
I have a list of responsive items, so that on a narrow screen we have a single list, and on a wider, (e.g. landscape) we have 2 or more. I now wish to make this list virtual however I find when I switch from portrait to landscape, the items to not fresh to now show two columns (or sometimes one of two rows will show 2 columns). It is close to working. If you load the app while in landscape, and change to portrait, it will adjust correctly, though sometimes you need to scroll to refresh it to see the items.
If you open the app on portrait, and change to landscape, it normally just shows the single column of items.
Expected behavior:
The list updates it's layout when a phone changes orientation.
Steps to reproduce:
I have attempted to reproduce in a plunk here, but it does not seem to quite work as I see it when running in a proper Ionic project (eg either in the browser using Ionic serve, or built and running on a device). I have a public repo here that shows it better.
I have a post about it here and here

Added some info above that points out some different symptoms that are caused by this same issue.

+1

I also have this as outlined here which is from some time ago. I just tried it out again using 3.7.0, but still seems the same.
Has anyone got this going and working responsive, as in the layout can change from 1 to 2 to 3 elements per row depending on screen width (i.e rotate tablet or phone from portrait to landscape)
I am adjusting the width of the list items using media queries, perhaps there is another way that works?

ion-grid and virtualScroll do not seem to work together.
`

{{attr}}

<ion-list [virtualScroll]="data | async" [virtualTrackBy]="trackBy" no-margin>
<ion-row *virtualItem="let item" row-highlight (click)="itemClicked(item, $event)">
<ion-col *ngFor="let attr of showCols" class="table-col">

<ion-icon *ngIf="item[attr]" name="checkmark">

<ng-template #asString>
{{item[attr]}}

`
The columns in the list part do not behave as expected. For example, if the table has three columns, each column should take a third of the screen width. This happens for my first row, which contains the column header names, but then the actual data columns do not spread across the page width equally. I used pretty much the same setup, but without virtualScroll, and then the grid works fine.
Please make grid and virtualScroll compatible with each other.

Please make ion-gird and virtualScroll compatible.
In the table component I created below, the header row is spaced correctly. For example, if the table has three columns, each column header in the first row receives a third of the <content> width.
However, the other rows (which contain the virtualScroll data), are not spaced equally across the width of the <content>. When I used the same setup, but with *ngFor instead of [virtualScroll], the table layout worked beautifully. Is there no way you can make this work?
<ion-grid>
  <ion-row>
    <ion-col align-self-center>
      {{title}}
    </ion-col>
    <ion-col text-right *ngIf="showAddButton">
      <button no-margin no-padding ion-button clear icon-right (click)="addButtonClicked()">
        <ion-icon name="person-add"></ion-icon>
      </button>
    </ion-col>
  </ion-row>
  <ion-row>
    <ion-col *ngFor="let attr of showCols" class="vp-col" class="table-header">
      {{attr}}
    </ion-col>
  </ion-row>

  <ion-list [virtualScroll]="data | async" [virtualTrackBy]="trackBy" no-margin>
    <ion-row *virtualItem="let item" row-highlight (click)="itemClicked(item, $event)">
      <ion-col *ngFor="let attr of showCols" class="table-col">

          <ion-icon *ngIf="item[attr]" name="checkmark"></ion-icon>

        <ng-template #asString>
           {{item[attr]}}
        </ng-template>
     </ion-col>
   </ion-row>
 </ion-list>
</ion-grid>


Confusing @fs prefix for some files

Describe the bug
I noticed this earlier when I was testing different versions of Vite locally, but now I'm also getting this with regular setups: Some paths sometimes end up as absolute and prefixed with @fs. Most recent example with npm init solid from today:

cc @jaro-sevcik
Reproduction
https://drive.google.com/file/d/1R0rix01pglrxyu-skX0r7W25KVsMU_vx/view
Steps to reproduce
mkdir solid-start
cd solid-start
npm init solid  # selected todomvc, SSR and no TS
npm install
npm run dev

System Info
System:
    OS: Linux 5.19 Debian GNU/Linux rodete 12 (rodete)
    CPU: (128) x64 AMD EPYC 7B12
    Memory: 470.09 GB / 503.87 GB
    Container: Yes
    Shell: 5.9 - /usr/bin/zsh
  Binaries:
    Node: 18.10.0 - ~/.nvm/versions/node/v18.10.0/bin/node
    npm: 8.19.2 - ~/.nvm/versions/node/v18.10.0/bin/npm
  Browsers:
    Chrome: 111.0.5563.64
    Firefox: 102.7.0esr

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

@patak-dev, @bluwy, and @dominikg had some thoughts here regarding potential out-of-root resources. In this case the resource isn't out of root.

As discussed, this is because SolidStart hardcodes the /@fspath to the HTML, so it should be fixed on their end instead to be a root-relative path. Closing this for now.


fix: typescript error regarding null

The value for DayValue should be Date | undefined not null.
If you let it be null you will get the following error as I do.
TypeScript error in /Users/brandonroberts/code/weight/src/App.tsx(39,9):
No overload matches this call.
  Overload 1 of 3, '(props: Optional<DatePickerProps<Day>, "value">): ReactElement<any, string | ((props: any) => ReactElement<any, string | ... | (new (props: any) => Component<any, any, any>)> | null) | (new (props: any) => Component<...>)>', gave the following error.
    Type 'DayValue' is not assignable to type 'Day | undefined'.
      Type 'null' is not assignable to type 'Day | undefined'.  TS2769

    37 |
    38 |       <DatePicker
  > 39 |         value={day}
       |         ^
    40 |         onChange={setDay}
    41 |         inputPlaceholder="Select a day range"
    42 |         shouldHighlightWeekends

For more info about this issue https://github.com/Microsoft/TypeScript/issues/26214
null is a different type and value from boolean and undefined. undefined === null would also result to false. So if you want this to run without an error, you have two options:

Assign undefined, not null, because the type says it accepts either boolean or undefined.
Change the type to include null, e.g. boolean | undefined | null (or prop?: boolean | null).

I think null approach is perfectly fine. I've found an interestingly: value works perfectly fine when used along with the Calendar component. But it doesn't work with the DatePicker component. I think it has to do something with this line in index.d.ts:
export interface DatePickerProps<TValue extends Value> extends CalendarProps<TValue>
@thebrodmann any idea?🤔

Found the fix!: if we replace line 61 of index.d.ts from this:
declare function DatePicker(props: Optional<DatePickerProps<Day>, 'value'>): React.ReactElement;
to this:
declare function DatePicker(props: Optional<DatePickerProps<DayValue>, 'value'>): React.ReactElement;
it would work again! But the thing is I wanna add undefined support to the date picker value as well:D

But the thing is I wanna add undefined support to the date picker value as well

Great! So we should also add it's support it in TypeScript definition too.

@8brandon can you close this PR and submit another one for develop branch(not master
) with changes to include both null and undefined support, please? Then we can work on it

Yea before I do I'm not actually sure if you need null or undefined checks.
It seems to work fine with just
export type DayValue = Day;
&
const [day, setDay] = React.useState();

@8brandon The ideal case is to support both null and undefined 🤔

@8brandon This is now fixed in 3.1.3 🎉


Upgrade to Confluent.Kafka 1.6.0

Dear @TsuyoshiUshio, @fbeltrao and @ryancrawcour,
thanks again for upgrading to Confluent.Kafka 1.5.2 (#185). Nevertheless, we still saw some partitions occasionally stalling on the consumer side, even after applying all of the mitigations outlined at https://github.com/edenhill/librdkafka/issues/3109.
However, after just moving on to v1.6.0-PRE3, things appear to be really smooth now, see also https://github.com/edenhill/librdkafka/issues/3109#issuecomment-728064365.
I just wanted to give you a heads up on this and will notify you as soon as 1.6.0 GA is out.
With kind regards,
Andreas.

Hi @amotl
Thank you, once it is released, I'll update it.

Hi @amotl
Can I ask you a question?

How can we reproduce the issue? EventHubs will cause the issue?
How exactly the log from libkafka we are going to see?
Some of users look hit this issue, however, I can't have a confidence.

Dear Tsuyoshi,
thanks for asking. I want to apologize that I can't really provide any more detailed insights. We have neither a repro nor any logs available and just upgraded to the most recent version of librdkafka in a trial-and-error manner. What I can tell you is about the symptoms we experienced and more details about our environment.
We are using confluent-kafka-python to connect to Azure Event Hubs from a) a self-provisioned Kubernetes cluster on Azure and b) (only recently) from a managed AKS cluster.
We are using the maximum of 32 partitions available on Azure Event Hubs and consume from them by sharding the load to 32 consumer instances, each one running on a different pod.
Occasionally, we saw specific partitions to be stalled from consumption. It looks like it has always been the same, like 5 and 21 - so at least there have been some deterministic aspects around this issue ;].
We determined the issue by a) seeing the specific consumer instances "hanging" (i.e. no more log output) and b) by monitoring the partition offset time metric for each partition.
With kind regards,
Andreas.
P.S.: You will recognize that our environment didn't either use Confluent.Kafka nor was connecting to a vanilla Kafka broker. Instead, we used the Python client (also based on librdkafka) and have been connecting to Azure Event Hubs. However, we are about to use azure-functions-kafka-extension within a rewrite of our infrastructure and thought it would be a good idea to give you a heads up on this in order to prepare everything accordingly that we won't trip into the same issues. Hence, I came here to share our observations with you and suggest to a) bump to the most recent versions of librdkafka and b) unlock the configuration options socket.keepalive.enable and metadata.max.age.ms (https://github.com/Azure/azure-functions-kafka-extension/issues/187) in order to be able to adjust to the recommended settings by Microsoft when connecting to Event Hubs.
P.P.S.: monitoring the partition offset time metric for each partition - that is: Putting event.enqueued_time and partition_context.last_enqueued_event_properties["offset"] from def on_event(self, partition_context: PartitionContext, event: EventData) coming from azure-eventhub into Prometheus and displaying it within Grafana.

Thank you for sharing! It helps!

Done the upgrading. https://github.com/Azure/azure-functions-kafka-extension/releases/tag/3.3.1


docs: add doc about CLI and clean terminal doc for CLI

Overview
This PR adds docs about the CLI to the README, and cleans up the extra unecessary docstring in the run function, since a dynamically generated text is displayed automatically from the function inputs already.
Closes #131

LGTM