Nuxt Bridge app.baseURL doesn't work with i18n module

Environment

Operating System: Darwin
Node Version:     v14.18.1
Nuxt Version:     latest
Package Manager<EMAIL_ADDRESS>Bundler:          Webpack
User Config:      -
Runtime Modules:  -
Build Modules:    -

Reproduction
nuxt.config.js
import { defineNuxtConfig } from '@nuxt/bridge'

export default defineNuxtConfig({
router: {
    base: '/d/'
  },
})

Describe the bug
The base path in nuxt bridge seems to be broken. If I set it to the above /d/ every preload link in the frontend is set to /d/d/ and all files are also reachable only with this path.

It seems the only url which is not affected by this is the one to the header js file in production

What makes the thing worse - because the file lies under /d/d/ and the whole site is broken
Additional context
No response
Logs
No response

I have the exact same issue with a nuxt/bridge even without using any third-party modules. When I define router.base with some value - let's assume /test/ for example - it gets doubled in the script routes, embedded to the header. Any solution for this yet?

I was able to hard code __nuxt folder path using buildAssetsDir (it's not even documented!) - but I guess that's a pretty weak solution. Hope this issue will get addressed soon.

Same issue here.

yes - also had the problem that my fonts in /assets were not found - because the prefix was missing - the key was to specify the buildAssetsDir string as specified by @sweetpalma even though it should be the default anyway...(i also added baseURL and router.base but buildAssetsDir really made all the difference)
app: {
  buildAssetsDir: '/_nuxt/'
}

I also had the same issue. I followed the work around by @sweetpalma and @saraha33. That fixed the issue. Thanks!
At least buildAssetsDir is now in the docs.


Already registered to bower.io!

Already registered to bower.io, but i dont found on README.md, please update,  so many people wiould like that!

Which iscroll package is this? Searching for "iscroll" returns about 20 results.

:+1:


Terminal couldn't be opened if profile's commandline couldn't be opened (re-open)

Environment
Windows build number: Microsoft Windows [Version 10.0.18963.1000]
Windows Terminal version (if applicable): commit id 734fc1d

Steps to reproduce
still, like #1404
at the defualt profile, "commandline" can't be opened, terminal starts and right after it shuts down.
Make profile a mistake, like the image under.

After that, starting a windows terminal, terminal automatically closes without any message.

Expected behavior
Terminal shows up an error message like #2422

Actual behavior
Terminal doesn't show up any error message, just shuts down.

Doesn't #2422 solve this?

@wolf99 It didn't.

This is still #982.


Filtering Suggestion List then Using Arrow Keys and Enter not returning expected result

Describe the bug
If you type a letter or two in the SearchField to filter the suggestions, then use the arrow keys to select one of the filtered items and press Enter, the item of the unfiltered suggestion list at the index of the selected item of the filtered list is returned instead.
To Reproduce
Using the example code on pub.dev, click in the Basic SearchField and type "d", then arrow down with "DEF" highlighted and press enter.  The resulting text in the SearchField is "ABC" instead of "DEF".

Hello @murvkins, Thanks for filing the issue. I was able to reproduce the issue.

fixed in v0.9.9
Thank you for your contribution!


support hyprpm

https://wiki.hyprland.org/Plugins/Using-Plugins/#installing--using-plugins

to my surprise, it's already supported and just works? I'll update the README install instructions once i have time :slightly_smiling_face:


[TAIK-2326] - Add boring avatars on avatar component

@krzwc you can play with boring component here:
https://deploy-preview-58--taikai-rocket-kit.netlify.app/?path=/story/design-system-atoms-avatar-image--boring-avatar


define path for each total annihilation modded installation directory

Is your feature request related to a problem? Please describe.
i only seem to be able to select 1 directory in the settings
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
multiple installations of TAF does not seem to be the solution
Wanna have the bug fixed quickly?
Visit Issue hunt...

nevermind i figured it out

replicating these options cleanly in the settings menu would be nice though i assume as i write this that the list in the settings menu will in fact population once i have specified the directories through this UI element

there should be more options.
3.1 and 3.9 should be presented as options, maybe include OTA also.
the list in the settings menu should automatically be populated with all known mods rather than just tacc when initially launched.

with v0.12.1 the settings/totalannihilation table is pre-populated with all known mods from the server

Awesome, thanks!
On Sun, 11 Apr 2021 at 01:38, Axle1975 @.***> wrote:

Closed #1 https://github.com/ta-forever/downlords-taf-client/issues/1.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ta-forever/downlords-taf-client/issues/1#event-4577488729,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADKVZKEOPIJ4BAGIG5ASN7TTIBIENANCNFSM42LJHLWQ
.

--
The Universal Declaration of Human Rights
The Universal Declaration of Human Rights (UDHR) is a milestone document in
the history of human rights. Drafted by representatives with different
legal and cultural backgrounds from all regions of the world, the
Declaration was proclaimed by the United Nations General Assembly in Paris
on 10 December 1948 (General Assembly resolution 217 A
http://www.un.org/en/ga/search/view_doc.asp?symbol=A/RES/217(III)) as a
common standard of achievements for all peoples and all nations. It sets
out, for the first time, fundamental human rights to be universally
protected and it has been translated into over 500 languages.
http://www.ohchr.org/EN/UDHR/Pages/SearchByLang.aspx
Download PDF
http://www.ohchr.org/EN/UDHR/Documents/UDHR_Translations/eng.pdf


BitStream ctor does not memset the data array to all 0, which could cause incorrect write of another bitstream

At lines between 220 and 227 in void BitStream::Write(BitStream *bitStream, BitSize_t bits2Write):
} else
{
// Existing byte
if( bitStream->data[bitStream->mReadPosBits >> 3] &
( 0x80 >> ( bitStream->mReadPosBits & 7 ) ) )
data[mWritePosBits >> 3] |= 0x80 >> ( numberOfBitsMod8 );
// Set the bit to 1else 0, do nothing
}

this function supposes that the memory adress after write position is default initilized with value of 0. However, it may not be so

Anothing surprised me is that why this function does not reuse the WriteBits() instead of rewriting a new inplementations for write of bitstream

Anothing is this function could be very slow because it writes one bit each time in worset case. Use WriteBits() when write-position mods 7 equals 0.

Does this actually cause an issue? My understanding is that there can always be some 'junk' bits (byte padding) at the end of a BitStream once sent since it must send full bytes and does not send the number of bits used. The receiving bit stream does not know where the meat of the payload ends (in terms of bits). As such you need to always consider that and never read past what you know has been written (am I making any sense?)..
I could be totally wrong here, but my analysis suggests this.

Unsure if changed since I last programmed on RakNet a decade ago, but the not setting it to 0 should not affect anything and was purposefully not done to help performance.

It is very DANGEROUS to reply on compiler's default initialization for setting up all zeros.
this method is very slow as it copies bit one after another. A easy and faster impl is reusing writebits() method to have a chance of memcpy().


Token length extension

Hi dear Team,
First of all thanks for this amazing resource! This is super cool and helpful in many ways!
I am working with a protein complex that only is marginally longer than 2048AA -> 2400AA and have access to H100/A100 80GB GPUS so I think I would be able to run it. I already read #77 -> Cubic scaling, I know.
So I skimmed the code a little. There is only a checking function I saw so far, if I disable that will the model run or did you guys hardcode anything more that would make this unfeasible? If not I would just fork the repo and run my version with longer context :)
Love your work and again thanks so much!

Thanks for kind words,

if I disable that will the model run or did you guys hardcode anything more that would make this unfeasible?

There is no our hard-coded constraint, but AFAICT models won't work for size that is different from what was exported, and largest exported was 2048 (previously I tried and it didn't work).

Okay thank you I will give it a shot and report back!

Hey gave it a shot. Guess the diffusion size is fixed. At least it did not work for me and makes sense that it would not work.


Add opt-in metrics collection

The goal of this issue is to track the ideas and concerns with metrics collection of this GitHub Action. The major goal of this is to ensure that we collect and document the decision process for metrics we want to collect and use.
To start, I am considering the use of the JSON Schema Specification as a way for us to provide a publicly auditable contract with our users. Furthermore, this ensures that we have the capability to build tooling for the metrics we collect by providing a known interface.
Here is the rough outline of things I am interested in collecting:

Repository name
Repository owner
Workflow name
GitHub event trigger (ie PR, workflow trigger)
Cloud provider selected
Instance type
Total run time

Would there be any interest in collecting maximum CPU, GPU, and RAM usage? As discussed elsewhere, we would be interested in getting that data for our own debugging purposes. If the overheads are small, it might be good to get that data on a broader scope to see "how well is an instance type getting used"?

I can't currently think of any expectations of privacy with my use of these runners. I'm in favor of my usage being tracked wherever data might potentially be useful
At the level of individual runs, I can only think of resource usage for similar reasons @IAlibay described, and presumably this would also be useful for people to review at an organization level every few months. I, for example, have no idea how much VRAM I'm using or need

I appreciate the feedback! Getting actually system usage may require some more research to ensure that we can get that data via an API and will likely require some role permission changes on the AWS side. If this is the case, I think this data will be considered "optional telemetry" (especially if we can't ensure a similar API on other cloud providers).
tl; dr: I do think system usage is worth looking into and will update on what I find.

I was able to find a resource from AWS on adding a CloudWatch script to add GPU monitoring. This would require adding an additional script to these machines (which we should be able to add since we do something similar to install GitHub's runner software).
The question is what additional permissions would be needed on the AWS side to query those CloudWatch metrics.

I have a start of a JSON schema (see below) that currently does not handle system metrics. This is the most we can currently handle without needing to modify permissions we recommended in our docs around AWS.
{
	"$schema": "https://json-schema.org/draft/2020-12/schema",
	"$id": "https://github.com/omsf-eco-infra/gha-runner/blob/main/metrics.schema.json",
	"title": "gha-runner metrics",
	"description": "The metrics schema to be collected when using this action",
	"type": "object",
	"properties": {
		"version": {
			"description": "The version of the schema.",
			"type": "string"
		},
		"repository": {
			"description": "The repository using the action.",
			"type": "string",
			"pattern": ".*\/.*"
		},
		"workflowName": {
			"description": "The name of the workflow that is run",
			"type": "string"
		},
		"trigger": {
			"description": "The GitHub event that triggered the run",
			"type": "string"
		},
		"cloudProvider": {
			"description": "The cloud provider used",
			"type": "string"
		},
		"instanceType": {
			"description": "The cloud instance type",
			"type": "string"
		},
		"runtime": 	{
			"description": "The total runtime of the action",
			"type": "string",
			"format": "duration"
		}
	},
	"required": ["repository", "workflowName", "trigger", "cloudProvider", "instanceType", "runtime"]
}


Update/install readme

Here is a quick update to link the user to the main page (with the releases tarballs) and adding a note about cmake. This will close #401

And feel free to tweak as you see fit! (edits from maintainers should be on)

Coverage decreased (-0.1%) to 93.825% when pulling b0b1df92d90c93dc062b7d5cb33f0c38cf739bbb on researchapps:update/install-readme into d098c0ff86a1a704ab4b42eef8efbee8dec5cf9d on akheron:master.

That's strange - this is a bit old (from February!) and it says it's from an unknown repository. Are you able to edit directly to adjust the changes, or should I open a new pull request?

I suspect you've deleted the fork of jansson - this is preventing me from directly editing.  I think if you fork again and recreate the 'update/install-readme' branch it should update this PR.  If not then you could open a new PR.


cdesktopenv: init at 2019-11-30

Motivation for this change
The Common Desktop Environment was created by a collaboration of Sun, HP, IBM, DEC, SCO, Fujitsu and Hitachi. Used on a selection of commercial UNIXs, it is now available as open-source software for the first time.

Things done

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

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

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

Notify maintainers
cc @joachifm

@GrahamcOfBorg build cdesktopenv

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/cde-common-desktop-environment-is-available-for-nixos/5049/1

@markuskowa Thank you!


thread main panicked when app name is empty

This is a silly one, but should be handled gracefully. The following roc code:
app ""
    packages { pf: "https://github.com/roc-lang/basic-cli/releases/download/0.3.2/tE4xS_zLdmmxmHwHih9kHWQ7fsXtJr7W7h3425-eZFk.tar.br" }
    imports [pf.Stdout]
    provides [main] to pf

main = Stdout.line "Hello, I have an empty name!"

Causes this crash when we do roc run:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 2, kind: NotFound, message: "No such file or directory" }', crates/compiler/build/src/program.rs:820:79
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Output of roc --version
roc nightly pre-release, built from commit 0c50ee0 on Mi 31 Mai 2023 10:03:48 UTC
Output of roc check
0 errors and 0 warnings found in 21 ms.

Naming the app . causes the following slightly different output:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 21, kind: IsADirectory, message: "Is a directory" }', crates/compiler/build/src/program.rs:820:79
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

⚠ Naming the app ../parent causes a file named parent to be created on a parent folder, which could in theory lead to attacks on REPL servers

⚠ Naming the app /absolute/path will create the file on the absolute path. Depending on which permissions the roc script is being run with, we could potentially overwrite critical components on a server

No longer reproduces


⚠ ClamAV has degraded performance

In 754b778, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 237 ms

Resolved: ClamAV performance has improved in d89d989 after 10 minutes.


Minor incremental coverage bug

Incremental coverage can say that a continue statement is uncovered when it actually is.
Minimal case
cirq/t.py
def func(*args):
    for a in args:
        if a:
            return 2
        else:
            continue  # Incremental coverage thinks this is untouched
    return 1

cirq/t_test.py
from cirq import t

def test_func():
    assert t.func(False) == 1
    assert t.func(True) == 2

This was not fixed because Python's optimizer replaces a jump to a continue with a jump to the top of the loop. See https://bugs.python.org/issue2506. There are two ways of fixing this:
1.Tell Coverage.py to ignore continue
def func(*args):
    for a in args:
        if a:
            return 2
        else:
            continue  # pragma: no cover
    return 1

Add useless code to bypass CPython's peephole optimizer so that coverage records correctly

def func(*args):
    for a in args:
        if a:
            return 2
        else:
            1+1
            continue
    return 1

@Strilanc Thoughts?

For now we'll stick with # coverage: ignore annotations. That's far better than a mystery expression to trick the optimizer.

continue is used multiple times.  cirq/circuits/qasm_output.py: line 168 for example. How was this coverage issue fixed?

The mystery continues..

If it's not happening anymore, it may have been fixed upstream from us.

Victory reports not happening anymore.


stage_external_sources Comparing source_name of the node instead of the name of the node

Describe the bug
When calling the  stage_external_sources macro and passing the source name as a list of values, when the name does not contain a '.' it is comparing the node.source_name instead of the node.name for the selected source.
Steps to reproduce
In my pre-hook I am can call the macro with the select parameter with the schema.source_name and it works. If I just call it with the source_name it does not.
Expected results
Calling the macro with the schema or without the schema should still find the source by name.
Actual results
Ignores the source if only the name is used in the select parameter.
Which database are you using dbt with?

[ ] redshift
[ ] snowflake
[x] other (specify: BigQuery)

The output of dbt --version:
Core:
  - installed: 1.8.4
  - latest:    1.8.4 - Up to date!

Plugins:
  - bigquery: 1.8.2 - Up to date!

The operating system you're using:
macOS 14.5

The output of python --version:
Python 3.11.9

Additional context
I believe that Line 20 in the macro stage_external_sources is the culprit. I think that the following would fix the issue. Unless I am misinterpreting the intention of that line of code.
existing code
                        {% if src == node.source_name %}

proposed change
                        {% if src == node.name %}

Hi,
I've encountered an issue with the stage_external_sources macro in the latest release. The problem arises from this change. Because of this change, I'm unable to run the command dbt run-operation stage_external_sources --args '{"select": "source_name"}'. With this command line, I was previously able to drop and create all the tables from my source (using ext_full_refresh = true).
Could you advise on how I can run all tables using the current setup?
Locally, I added an argument to the macro to use tags that I had assigned to my sources, and it works perfectly. Could you please look into this issue and consider incorporating a similar solution?
I'm new to GitHub, so any guidance or help would be greatly appreciated!
Thanks!

Hi,
I observed the same issue as laurianneol.
This change broke the selection of all tables within a source like described in the syntax section of the readme: https://github.com/dbt-labs/dbt-external-tables?tab=readme-ov-file#syntax
# stage all Snowplow and Logs external sources:
$ dbt run-operation stage_external_sources --args "select: snowplow logs"

If I find time, I'll open a bug.
Best regards


Refactor windows_service unit tests

Description
Refactoring the windows_service provider tests.
Issues Resolved
N/A
Check List

[x] New functionality includes tests
[ ] All tests pass
[ ] RELEASE_NOTES.md has been updated if required (not required for bugfixes, required for API changes)
[x] All commits have been signed-off for the Developer Certificate of Origin. See https://github.com/chef/chef/blob/master/CONTRIBUTING.md#developer-certification-of-origin-dco

@stuartpreston @tas50 can either of you review this?


Bug: Standard CefSharp Menu Context is not Working

The CefSharp standard menu contexts that can be activated using right mouse click on the home page are not working.
For example: Print, View Source and so on.
It can be simply deactivated in future.

This bug is fixed in e7b92d8f6597435d4f619f63bd912d564c7e68d7


[BACKEND] Fix enable_debug implementation.

Print before every pass and after failures if MLIR_ENABLE_DUMP is set.

Depends on https://github.com/openai/triton/pull/1948 to be merged first


Introductory information about ASP.NET Core Version

Hi all. I've written an introductory post with information about .NET Core version and Sergen.
http://serenity.is/blog/2017/01/18/welcome-to-aspnet-core
Hope it will help you test .NET Core version, though it is still in beta, just like .NET Core itself.
Please try it and let me know how it goes.

Only Sql Server supported and you need Sql Authentication / Remote Server for OSX / Linux

Once again, thank you very much for your time and your effort @volkanceylan !

Thank  you very much @volkanceylan !

You are really a genius man.

https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.1-preview2.1-download.md
This is the version used in the project

Congratulation! A great step into the right direction imho.

Some things have changed after VS2017, see latest blog post.


[Draft] [OData] Expose Content-Id of failing changeset response

This approach...

does not consume the lazily evaluated HttpResponse from the batch response. All lazy behavior properties of ODataRequestResultMultipartGeneric are kept maintained.
no longer throws away the batch meta information but instead combines it with the original payload to new class Entry(String meta, String payload) whereas the meta information like Content-ID can be extracted easily.
All changes are not public API breaking. The affected classes are package-private.

Merged in https://github.com/SAP/cloud-sdk-java/pull/347


Allow requesting presences via member chunking

See: https://github.com/discordapp/discord-api-docs/pull/1116

This is... somewhat less-useful, given how gateway intents will affect things. I'll re-open this if it turns out people want / need this.


Small visual issue with country selector on iPhone 6s

[ ] Small visual issue with country selector on iPhone 6s

@teolemon You mean, the drop-down button?

Yup

yeah flutter dropdown menus are prone to this bug, I can take a look, I'm working on something similar on the side

https://openfoodfacts.slack.com/archives/C027W09UMM1/p1641572449000500

#950


In zerocopy-derive UI tests, detect whether we're building with RUSTFLAGS='-Wwarnings'

This is how we run zerocopy-derive's UI tests in CI, and so if a developer locally runs UI tests treating warnings as errors, they will generate the wrong .stderr files, and CI will fail.
If RUSTFLAGS='-Wwarnings' is absent the test harness should eagerly fail with a single descriptive error, rather than proceed to run UI tests (which will produce lots of errors).
For those interested in tackling this, the file to look in is: https://github.com/google/zerocopy/blob/main/zerocopy-derive/tests/trybuild.rs

What are your thoughts on explicitly appending -Wwarnings to RUSTFLAGS when running zerocopy-derive's UI tests? It seems like last value wins when multiple, conflicting flags are passed into RUSTFLAGS.
Example: RUSTFLAGS='-Dwarnings -Wwarnings', -Wwarnings takes precedence.

For CI, we already do that:
https://github.com/google/zerocopy/blob/ca7f28bcfb1825edf320f13d87b8fe68c0e880f0/.github/workflows/ci.yml#L225-L241
Ideally, we'd also enforce that in our trybuild.rs test itself. Due to limitations of the trybuild crate, we cannot pass in -Wwarnings there. We can, however, audit the value of the ambient RUSTFLAGS environment variable and error-out accordingly. Alternatively, we can switch to the ui-test crate which allows fine-control over RUSTFLAGS.

Do we also want to fail if RUSTFLAGS is not present?

Good question; I'm not sure. I'm also wondering on how this interacts with folks who have a .cargo/config file that sets RUSTFLAGS — and whether we should go so far as to provide one in the repo.

Oh right, I forgot about .cargo/config. Is there a way to read that file other than parsing it directly?

I believe this is superseded by #1414. Feel free to re-open if you think that's wrong.


Add the newer insights

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

@rboucher - Would you close this public repo PR and work in the private repo instead? Thanks.

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


Add locale support to WebChat

Fixes #3296
Description
Update createDirectLine to accept and pass locale option.

zh-CN test case failed due to the locale feature is not enabled in DLJS.

LGTM!


keeper-cli error when running in redis:alpine

The latest version of ksm (1.1.1) throws an exception when running in the redis:alpine container (and possibly others). We're using ksm in our docker-compose file to start redis via a shell script, using the "exec" command to replace an environment variable with the secret. We run the keeper/keeper-secrets-manager-cli:latest image first and the redis container executes /cli/musl/ksm and we see the following exception:
Traceback (most recent call last):
  File "ksm.py", line 1, in <module>
  File "PyInstaller/loader/pyimod03_importers.py", line 540, in exec_module
  File "keeper_secrets_manager_cli/__init__.py", line 13, in <module>
  File "PyInstaller/loader/pyimod03_importers.py", line 540, in exec_module
  File "keeper_secrets_manager_core/__init__.py", line 1, in <module>
  File "PyInstaller/loader/pyimod03_importers.py", line 540, in exec_module
  File "keeper_secrets_manager_core/core.py", line 24, in <module>
  File "PyInstaller/loader/pyimod03_importers.py", line 540, in exec_module
  File "keeper_secrets_manager_core/utils.py", line 31, in <module>
  File "PyInstaller/loader/pyimod03_importers.py", line 540, in exec_module
  File "keeper_secrets_manager_core/keeper_globals.py", line 12, in <module>
  File "PyInstaller/loader/pyimod03_importers.py", line 540, in exec_module
  File "importlib_metadata/__init__.py", line 6, in <module>
  File "PyInstaller/loader/pyimod03_importers.py", line 540, in exec_module
  File "zipp/__init__.py", line 9, in <module>
ModuleNotFoundError: No module named 'zipp.py310compat'

This error does not occur in the 1.1.0 version.

keeper/keeper-secrets-manager-cli:<IP_ADDRESS> or latest now have a fixed MUSL/Alpine CLI binary.


Feature proposal: pandas vectorize decorator

numpy has a very useful vectorize decorator: http://docs.scipy.org/doc/numpy/reference/generated/numpy.vectorize.html that allows writing a function for scalars and then pass in arrays transparently. Under the hood, the function is called multiple times on subsets of the data.
I'm currently writing code that operates on a Series object. Some of those functions can also be passed in DataFrames and still work the same while some would require special logic. I think a pandas vectorize decorator could be very useful for these cases. In my specific case, I can just write that myself easily but I thought I'd bring it up. Perhaps this already exists and I just don't know about it.

Here is a quick and dirty fast-pass:
from collections import OrderedDict
import pandas as pd

def vectorize(func):
    def wrapper(df, *args, **kwargs):
        if df.ndim == 1:
            return func(df, *args, **kwargs)
        elif df.ndim == 2:
            # Call function on each column
            out = OrderedDict()
            multidim_output = False
            for col in df:
                out[col] = func(df[col], *args, **kwargs)
                if isinstance(out[col], pd.Series):
                    multidim_output = True
            if multidim_output:
                return pd.DataFrame(out)
            else:
                return pd.Series(out)

    return wrapper

this is essentially apply

@jreback can that be used as a decorator?

pls show why you would want to actually do this

This is an example function that works on a Series but not a DataFrame:
def calc_alpha_beta(df_rets, benchmark_rets):
    ret_index = df_rets.index
    beta, alpha = sp.stats.linregress(benchmark_rets.loc[ret_index].values,
                                      df_rets.values)[:2]

    return alpha * 252, beta

With my decorator I just pass in a DataFrame too and it would magically work.

You're saying I could do:
# if series
calc_alpha_beta(rets_as_series, bmark)
# if dataframe
df_rets.apply(calc_alpha_beta, args=(bmark,))
# with decorator method
calc_alpha_beta(df_rets, bmark)

pass axis=1 and u have to pass the args in the function itself

@jreback pass axis=1 to linregress you mean? Note that the columns in the dataframe could have different lengths and I'd call .dropna() on them. Then there really is no way around a loop, so I think it's a legitimate case.

So the calc_alpha_beta function is one of many in my library. Another one would be rolling sharpe ratio:
def rolling_sharpe(df_rets, rolling_sharpe_window):
    return pd.rolling_mean(df_rets, rolling_sharpe_window) \
        / pd.rolling_std(df_rets, rolling_sharpe_window) * np.sqrt(252)

That one works on DataFrames natively. So from an API standpoint it would be odd to have some functions that work on Series and DataFrames, and others that require you to use .apply().

adding syntax that papers over non performant functions is just not a good idea
magically making things work on series which are often vectorized and data frames which may or may not is another trap
you can use .pipe to do this in any event

Fair enough, just thought I'd bring it up as an idea, as I said I can just do that manually with my own decorator. numpy.vectorize certainly came in handy in many cases. It's slow but sometimes speed does not matter.
I don't see how pipe could be used here?

Updated code:
def vectorize(func):
    def wrapper(df, *args, **kwargs):
        if df.ndim == 1:
            return func(df, *args, **kwargs)
        elif df.ndim == 2:
            return df.apply(func, *args, **kwargs)

    return wrapper

df.pipe(rolling_sharpe)


Does this support torch.nn.parallel.DistributedDataParallel?

Currently not.
The implementation is designed for multi-GPU BatchNorm, which is commonly used for Computer Vision tasks. Thus, it uses NCCL for multi-GPU broadcasting and reduction.
Distributed version needs other types of synchronization primitive operations (e.g., via shared memory or cross-machine synchronization).
Contributions will be highly appreciated!

Just let you know that PyTorch Compatible Synchronized Batch Norm is provided here http://hangzh.com/PyTorch-Encoding/index.html

@zhanghang1989 Does this support torch.nn.parallel.DistributedDataParallel?

@acgtyrant yes, see the mnist example https://github.com/zhanghang1989/PyTorch-SyncBatchNorm#mnist-example

@zhanghang1989 Excuse me, I only see that you use the DataParallel, not the DistributedDataParallel. If you are sure, I use the DistributedDataParallel by myself later.

BTW, the python notebook is 404.

This no reason that it won't work with DistributedDataParallel .  https://github.com/zhanghang1989/PyTorch-SyncBatchNorm/blob/master/mnist.py
I will add  python notebook later

Thanks @vacancy for the introduction! Nice work. I have plan of supporting distributed training, due to a recent paper use it in object detection.
@acgtyrant The only thing need to be considered for distribute is making sure the number of gpus is set correctly https://github.com/zhanghang1989/PyTorch-Encoding/blob/master/encoding/nn/syncbn.py#L196

@zhanghang1989 I am not an expert at this. But it seems to me that the DistributedDataParallel uses different implementation as DataParallel for broadcasting and reduction. While in a single process, multi-thread setting (DataParallel), one can use simple NCCL's broadcast and reduce, for tensors shared across multiple processes or even multiple machines, we need special implementation, which is defined in the package torch.distributed.

@vacancy Thanks for the information.

I read the source code of DistributedDataParallel, I find that it does not broadcast the parameters like DataParallel, it only all_reduce the gradient so that all model_replicates use the same gradient to optimize the same model at all, and all model_replicates use the same buffer which is broadcasted from the model in the device 0 of the rank 0 node.
@zhanghang1989 I think your syncbn use only comm.broadcast_coalesced and comm.reduce_add_coalesced which only support cross-gpu, it does not support cross-node which is distributed.

I wrote a distributed bn, but it does not work, any idea?
import torch
from torch.autograd import Function
import torch.cuda
import torch.nn.functional as F
from torch.nn.modules.batchnorm import _BatchNorm

class AllReduce(Function):
    @staticmethod
    def forward(ctx, input_):
        torch.distributed.deprecated.all_reduce(input_)
        return input_

    @staticmethod
    def backward(ctx, grad_output):
        torch.distributed.deprecated.all_reduce(grad_output)
        return grad_output

class SynchronizedBatchNorm2d(_BatchNorm):
    def __init__(
            self, num_features, eps=1e-5, momentum=0.1, affine=True,
            track_running_stats=True):
        super(SynchronizedBatchNorm2d, self).__init__(
                num_features, eps, momentum, affine,
                track_running_stats)
        self.world_size = torch.distributed.deprecated.get_world_size()

    def forward(self, input_):
        if input_.dim() != 4:
            raise ValueError('expected 4D input (got {}D input)'
                             .format(input_.dim()))

        if not self.training:
            return F.batch_norm(
                input_, self.running_mean, self.running_var,
                self.weight, self.bias,
                self.training, self.momentum, self.eps)

        batchsize, channels, height, width = input_.size()
        numel = batchsize * height * width
        input_ = input_.permute(1, 0, 2, 3).contiguous().view(channels, numel)
        sum_ = input_.sum(1)
        sum_of_square = input_.pow(2).sum(1)
        sum_ = AllReduce.apply(sum_)
        sum_of_square = AllReduce.apply(sum_of_square)
        mean = sum_ / (numel * self.world_size)
        sumvar = sum_of_square - sum_ * mean
        unbias_var = sumvar / (numel * self.world_size - 1)
        bias_var = sumvar / (numel * self.world_size)
        std = bias_var.clamp(self.eps) ** 0.5

        self.running_mean = (
                (1 - self.momentum) * self.running_mean
                + self.momentum * mean.detach())
        self.running_var = (
                (1 - self.momentum) * self.running_var
                + self.momentum * unbias_var.detach())

        if self.affine:
            output = (
                    (input_ - mean.unsqueeze(1)) / std.unsqueeze(1) *
                    self.weight.unsqueeze(1) + self.bias.unsqueeze(1))
        else:
            output = (input_ - mean.unsqueeze(1)) / std.unsqueeze(1)

        return output.permute(1, 0).contiguous().view(
                batchsize, channels, height, width)

Thank you.

Hi @acgtyrant
What do you exactly mean by "SynchronizedBatchNorm2d is not numerical stable only"?

My tests show that my implemented SynchronizedBatchNorm2d is not numerical stable, there is not any other error.

@acgtyrant Is DistributedDataParallel working for you? Are you planning to send a Pull Request?
Thank you all for this beautiful work!

It works, but because the secrecy laws from my boss, I delete the post which contains the source of the distributed synced bn, sorry.
However, it is easy to be implemented, the torch.distributed.all_reduce is synced automatically, so just warp it as an autograd function and use it to all_reduce sum and sum_of_square, then use this function in your implemented synced bn module.

How about  using torch.nn.parallel.DistributedDataParallel but only running on one node with 8 gpus? Does this repo work?

How about using torch.nn.parallel.DistributedDataParallel but only running on one node with 8 gpus? Does this repo work?

For torch.nn.parallel.DistributedDataParallel please use torch.nn.SyncBatchNorm


Add range by ID extension to coderef

Add an extension to <coderef> processing to allow selecting ranges by ID. For example, with source fact.hs
-- START-FACT
fact :: Int -> Int
fact 0 = 1
fact n = n * fact (n-1)
-- END-FACT
main = print $ fact 7

and it's used with
<codeblock><coderef href="fact.hs#line-id(START-FACT,END-FACT)"/></codeblock>

The result will equivalent to
<codeblock>fact :: Int -> Int
fact 0 = 1
fact n = n * fact (n-1)</codeblock>

Some markup language processor has this same support, but haven't found it again. The basic idea was the same, you have markers in the source file and those are used to define the range. I can't remember if that was language agnostic, so that it would recognize that comments in e.g. Java are marked with // and in Ruby with #. In the end, I think it may be safer to not try to add language specific processing, but rather just use the ID and check if that exists in the line. It's up to the authors to use IDs that do not appear in other context in the same file.

Looking for feedback on the syntax too. The current one is
uri ("#id-range(" start ("," end)? ")" )?

And I don't feel strongly about the id-range scheme name. I don't want to go for syntax like fact.hs#START-FACT,END-FACT because IMO it's too terse.

I don't like its syntax, but maybe it would be more DITA like to use the syntax of @conref and @conrefend, even if the technical implementation is different, because the concept (what the author wants to do) is the same. As an author, I don't care how (and by whom (e.g. TC or DITA-OT dev)) a functionality is implemented. But if I want to conref a range of a file, I expect to use @conref and @conrefend
So this:
<codeblock>
  <coderef href="fact.hs#line-id(START-FACT,END-FACT)"/>
</codeblock>

Could be:
<codeblock>
  <coderef conref="fact.hs#topic-id/START-FACT" conrefend="fact.hs#topic-id/END-FACT"/>
</codeblock>

The point is, the fact.sh is not an XML DITA file. Thus, we can't use conref with it. We already have supported line-range extension for a while now, thus would basically be just an alternative range selector.

Why not overriding the mechanism, e.g. with an additional @format?
<codeblock>
  <coderef conref="fact.hs#topic-id/START-FACT" conrefend="fact.hs#topic-id/END-FACT" format="plain-text"/>
</codeblock>

That would be very heavy overloading of base DITA functionality. There's a reason why <coderef> exists, instead of DITA TC trying to make conref work with plain text. Using the line extension is already defined in an existing specification RFC 5147; this uses a similar approach.

Also, using something like conref="fact.hs#topic-id/START-FACT" requires that that Haskell file has two IDs topic-id and START-FACT. There is no syntax or concept for IDs in Haskell, thus we would have to invent that syntax. Same goes for every other possible target file type.

Why not use two query parameters: fact.hs?startline=x&endline=y

@drmacro if the target URI is an absolute URI to an external resource, those parameters will be sent to the server and the results may not be the same as without them. The URI fragment is never sent to the server.

Good point. Then I think your function syntax is probably as good as anything. It's reasonably consistent with XPointer's precedent.

Since the use most closely parallels RFC5147, I'd parallel that syntax. So, instead of:
<coderef href="Parser.scala#line=4,10"/>
you'd specify
<coderef href="Parser.scala#token=START-FACT,END-FACT"/>
Since the toolkit isn't aware of the syntax of the code it's including, we don't know that the IDs are in fact IDs as defined in the code. All we know is that a matching token was found somewhere in a line. I think using token instead of id helps to communicate that.

I like @shaneataylor's token idea. That's clean and simple. The value space for IDs is pretty much all characters except comman and whitespace.

FWIW, I also like @shaneataylor 's idea - clean and simple. (And I think @jelovirt had a pretty clear / appropriate reasoning for why we can't overload @conref here).

Update syntax to token=start,end for consistency with RFC 5147.

:+1: LGTM, I'm OK to merge as-is now, pending any other comments.


How do you change the texture of a lua sprite

Describe your problem here.
How do you change the texture of a lua sprite
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
no

makeLuaSprite('tag', 'newImage', x, y);

Make sure that the tag is the exact same as the sprite that's already made with the image you want replaced


Blur map with tile size of 256px

Hi,
I installed the plugin and configured it as the readme file, but the map image is a little blurry.

This is my code:
Map::make('location')
                        ->label('Location')
                        ->columnSpanFull()
                        ->default([
                            'lat' => 37.1013615,
                            'lng' => -7.8312011,
                        ])
                        ->afterStateUpdated(function (Set $set, ?array $state): void {
                            $set('latitude', $state['lat']);
                            $set('longitude', $state['lng']);
                        })
                        ->afterStateHydrated(function ($state, $record, Set $set): void {
                            $set('location', ['lat' => $record->latitude, 'lng' => $record->longitude]);
                        })
                        ->extraStyles([
                            'min-height: 40vh',
                            'border-radius: 0px',
                        ])
                        ->liveLocation()
                        ->showMarker()
                        ->markerColor('#22c55eff')
                        ->showFullscreenControl()
                        ->showZoomControl()
                        ->draggable()

                        ->tilesUrl('https://tile.openstreetmap.org/{z}/{x}/{y}.png')
                        ->zoom(10)
                        ->detectRetina()
                        ->showMyLocationButton()
                        ->extraControl([
                            'zoomDelta' => 1,
                            'zoomSnap' => 2,
                        ]),

After digging a bit I found out an option to change the map tile size to 256px (by default is 512px)
->extraTileControl([ 'tileSize' => 256])

in this case de map appears good but the coordinates are completely wrong

My setup:
Plugin version 1.2.5 (also happens on 1.3.0)
PHP: 8.2
Laravel 11.23
Filament 3.2
Is this some missing configuration or a bug?

i have same problem

I found the fix.
Just set the zoomOffset to zero
->extraTileControl([
    'tileSize' => 256,
    'zoomOffset' => 0,
])

But the plugin by default uses the tileSize = 512 and zoomOffset = -1
The zoomOffset option is primarily used to correct the zoom level when tiles of a different size are used (e.g., 512).
For tileSize: 256 (default in leafletjs), the zoomOffset should be zero.


Update Discretization::PointSearch to use points directly

With #510 there is no need to create boxes to search for points.

This is actually what we are doing right now


Limit filesystem reports to discoblocks

Currently, node exporter exposes all the drives. It would be nice to limit drives with ignored-mount-points options

We have different design which solved this by design


Cursor goes crazy after clicking Add Function Breakpoint twice

Issue Type: Bug
Click plus icon for Add Function Breakpoint in Breakpoints tab of Run side panel
Click plus icon again
Cursor begins to flicker and alternate between the two text boxes for the  new function breakpoints with high frequency

CPU use jumps to over 50% from 12%

Switching focus to different application window interrupts the cursor activity CPU goes back down to 12%
Switching back to vscode makes the cursor go crazy again
Deleting all breakpoints stops the cursor activity and brings CPU down
VS Code version: Code 1.53.2 (622cb03f7e070a9670c94bae1a45d78d7181fbd4, 2021-02-11T11:48:04.245Z)
OS version: Windows_NT x64 10.0.19042

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5 CPU         660  @ 3.33GHz (4 x 3325)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: unavailable_offopengl: enabled_onprotected_video_decode: unavailable_offrasterization: unavailable_offskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.93GB (5.88GB free)

Process Argv
--crash-reporter-id e86d712e-1df7-440f-91ae-1043a236a317

Screen Reader
no

VM
0%

Extensions: none

Thanks for reporting this. I have pushed a fix, you can try it out in latest vscode insiders from tomorrow to let us know if the issue is now good for you. Thanks


How to disable Report Portal in WebdriverIO during local execution

What is the correct way to disable sending test results to report portal during local test execution.

Hi @adityagautam !
You can just not provide the RP reporter in wdio config based on some parameter (e.g. some ENV identifier).
Hope this helps!

Hi @adityagautam !
I mean smth like this
// wdio.conf.js

exports.config = {
// ...
reporters: isLocal ? [] : [[Reporter, rpConfig]],
// ...

Let me know if this helps!

Hi @adityagautam !
Were you able to check out my suggestion?
Is this issue still relevant to you?

I guess it won't work and will result in error.
reporters: isLocal ? [] : [[Reporter, rpConfig]],
try following
reporters: isLocal ? 'spec' : [[Reporter, rpConfig]],

@umarkhanTR
Empty array is also acceptable, referring wdio docs.

I will close this ticket, feel free to open a new one if you have any questions.


_method in form request is case sensative

Version 1.1
It appears that the ParseFormData() in the Request which reads the _method value from submitted form data is case sensitive. Lower case methods cause a 405 error to be thrown in our application.
The following call throws a 405
Example:
POST http://localhost:8080/route
Body:
_method=post
The following is handled by the route
Example:
POST http://localhost:8080/route
Body:
_method=POST

Actually, according to RFC7231 Section 4, the HTTP method token should be case sensitive. So technically it's correct.

This isn't the http method, this is to do with the _method body attribute, which is not covered by RFC7231. Handling lowercase _method values would allow for improved compatibility with other frameworks which do not follow http convention (see rails for a good example).

@zonal-andrewp We :heart: pull requests :wink:


feat: add rounded prop to overlay component

Current dependencies on/for this PR:

next

PR #235

PR #236

PR #237

PR #238

PR #239   (this PR)

This comment was auto-generated by Graphite.


Better file navigation

With a switch to LT I observe that I spend a lot more time finding a right buffer to work with. That's because I have to options to do it:
A. Find a tab I'm looking for.
B. Use navigate feature.
Option A is quite time consuming if you have many buffers open (which tends to be my case). What makes it even worth is that code base I deal with has lot of files with a same name like core.js, looking at the tab it's hard to know which on I need to jump to, there's no place I can take a look at file path either so I end up looking at source to detect whether it's core.js or not.
Option B is also not ideal since I need to type file names over and over & the matching file names again don't help here either.
Before switching to light table I used peep open that had plugins to all of the major editors. I would not dive into details
how it works as you can take a look at their page and this post:
https://peepcode.com/blog/2010/file-navigation-in-text-editors
But the main difference from current LT's navigate feature is that next time you open it it does not shows same results as before, instead it shows stack of most frequent files you navigated with more contextual info. As a matter of fact I never even looked at tabs when using it since it was faster and with more info.
So this is a suggestion to borrow some of the ideas to make navigation feature in LT better ;)

If anyone is still interested in this, add it to the feature wishlist. Also, provide some details – doing so as a comment on this issue is fine – as PeepCode seems to have been acquired and neither of the links in the original comment work now.

Doesn't narrowing to the desired workspace (cntrol-o, open recent workspace), and then cntrol-o with the completion (type file name, work well for this already?
Improvements here could be arrow-key nav in the workspace pane, but one typically doesn't switch workspaces constantly.


when I try to use str.encode(), bytes(str, encoding='utf-8') or import binascii, there would be error.

I tried with py3.7 and flexx 0.7, these function or module would not work, the error would be: str.encode is not a function or, bytes is not defined , or binascii is not a built-in function in JS. These are all pure python method or module. How would I solve that?

I would like to do some conversion between string and byte, byte and hex, hex and int.

Ok, thanks.


Bad user experience with the icons

Description
I have originally posted this as a comment here but I received no response from the maintainers. So I'm reposting this as an issue for visibility.
For context, there are currently two icon systems in nuxt/ui. One is based on tailwind css and the other is based on nuxt-icon. The user may switch between the two using a dynamic attribute.
This is a very bad design decision. Quoting @benjamincanac here for the original reasoning behind this design decision:

It's a tiny bit more work as you have to install the iconify packages for the collections you want to use but this makes icons instantly load as they are bundled in your css instead of fetching them from the Iconify API when rendering the page the first time.

So the problem we're trying to solve here is that "nuxt-icon causes icons to not instantly load", right?
And I would agree that it's a pretty bad problem. The iconify API is not the most reliable, and occasionally icons don't render on the Nuxt UI official website.
This is caused by a known issue in nuxt-icon, nuxt-modules/icon#34 or nuxt-modules/icon#99
Basically, nuxt-icon doesn't load the icon on the server side, and instead opt to call the iconify API from the client at all times.
So the reasonable solution to the problem of "nuxt-icon icons doesn't instantly load" would be "fix nuxt-icon so that icons can be injected and bundled at build time".
Instead of doing that, here we introduced another dependency so that icons can be injected by tailwind as a CSS icon.
What's the problem with that?

Dynamic icons, which was partially addressed in feat(Icon): switch to nuxt-icon with dynamic prop or app config #862. feat(Icon): switch to nuxt-icon with dynamic prop or app config #862 basically falls back to the nuxt-icon component when dynamic = true. But then with that, you once again lose the ability to allow icons to load instantly, which was why egoist/tailwindcss-icons was introduced in the first place.
Behavior consistency. nuxt-icon allows you to define custom Icon API sources using addIconProvider. egoist/tailwindcss-icons expect you to provide them in nuxt.config.ts. I can use bundle:name as the name property in "static" icons but not dynamic icons. That means for any custom icons I have to package them twice, once for static icons as an npm package and once for dynamic icons on my custom iconify server.
Implementation discrepancy. nuxt-icon embeds the SVG into the DOM. egoist/tailwindcss-icons uses CSS icons. monotone icons are image-mask. Image icons are background-image. That means if I want to style a subset of the paths in the SVG, I can do that with nuxt-icon, but not egoist/tailwindcss-icons.

What I'm trying to say here is that by introducing egoist/tailwindcss-icons you're significantly complicating an otherwise simple problem. Just go into nuxt-icon, help out @Atinux, and fix nuxt-icon so that it can preload icons. Call useAsyncData to fetch the icons on the server side so they're available as soon as the page loads. That way you have one unified method of loading icons, instead of introducing a whole lot of mental overload for a problem as trivial as showing icons.

Damn I do not like your tone dear @Neo-Zhixing, small reminder that all the tools you are using to make your website are completely free AND open source, so a thank you to start is more than welcome.

What I'm trying to say here is that by introducing egoist/tailwindcss-icons you're significantly complicating an otherwise simple problem.

nuxt-icon was introduced afterward to solve another issue of dynamic icon but I do agree that this is still not the best UX.

Call useAsyncData to fetch the icons on the server side so they're available as soon as the page loads

Did you look at the code before pretending that it is an easy fix to do?
nuxt-icon already preload the icons during SSR: https://github.com/nuxt-modules/icon/blob/0aa6fd707a455ea8c416f73e1b4ef7295e12647e/src/runtime/Icon.vue#L93
If you take a look at the playground: https://stackblitz.com/edit/nuxt-icon-playground?file=app.vue
You will notice that no call to Iconify API is done and everything is inlined during SSR.
The main issue of nuxt-icon is during client-side navigation where it needs to fetch the API. This is why we decided to go with tailwindcss-icons for Nuxt UI to start because it solves this UX issue and fallback to nuxt-icon for dynamic one (an icon that take a bit of time to load is better than no icon at all).
I do plan to add a way to preload the icons in the future for nuxt-icon, but it is not an easy task as it needs to rely on a build plugin (Vite / Webpack), in the meantime, I still believe that we do have a good Icon system that is still a no brainer to use.

Umm I do want to point out that, the reason I'm complaining about the problems with the icon solution in nuxt/ui is that a lot of components in nuxt/ui-pro directly reference the icon component defined here. The comments above are directed towards the maintainers of nuxt/ui-pro who seem to be the same group of people as nuxt/ui maintainers.
And nuxt/ui-pro is by no means "free AND open source", because it's in fact neither.
As a paying customer, I'm not expecting 7x24 support but I do think that I should be able to complain about product usability. Customer stories like this one can help make the product better by allowing the developers to better understand user needs. They also serve as a guidance for future customers so they can form a more informed purchase decision.

nuxt-icon was introduced afterward
That contradicts what I'm hearing from @benjamincanac 's statement regarding how this design decision was made.

Did you look at the code before pretending that it is an easy fix to do?
nuxt-icon already preload the icons during SSR

I recognize that the icons are preloaded during SSR. However, what I was suggesting is that "the icons should be available as soon as the page loads."
The problem we have now is that during client-side navigation the icons may not load immediately, and that produces disturbing results like this:

What useAsyncData does really well is blocking the page navigation before the data is available. I think that should be entirely possible, and it should be easy to do.

This is why we decided to go with tailwindcss-icons for Nuxt UI to start because it solves this UX issue
All we need is icon loads blocking page navigation. That solves 99% of the problem by avoiding sudden layout changes, and it should be both easier and less intrusive to the developer experience. Design decisions like "introducing another dependency that does the same thing as the current solution but differently" should not be made lightly and they should be well justified.

Icon preloading is a nice to have because when you know all the values an icon may take on, all variants can be loaded at page load so that when the icon name attribute changes the icons will be able to load immediately. However, that does not take away from the immediate bugfix we can have which is using something like useAsyncData to block page loads before the icon data becomes available.

@Neo-Zhixing What problem do you have with the default solution exactly? What is your use-case for using the dynamic mode?

@benjamincanac I had enabled the dynamic mode globally because

I wanted to use fontawesome pro and other custom icons. I have already setup a private icon server and I want to use that. With  nuxt-icon this is easy:

import { addAPIProvider } from '@iconify/vue'

addAPIProvider('dust', {
  resources: ['https://icon.dust.rs'],
})

However, the CSS icon solution introduced a whole different codepath, meaning that I have to repackage all the icons and feed them to egoist/tailwindcss-icons separately.

Styling.  egoist/tailwindcss-icons doesn't inject the SVG into the DOM and instead renders the icon as css attributes. That makes it impossible to correctly style duotone icons.

because some of my icons are dynamic.

useAsyncData won't solve the issue of displaying the text, but it is actually <Suspense> doing such.
As we do have an await here: https://github.com/nuxt-modules/icon/blob/0aa6fd707a455ea8c416f73e1b4ef7295e12647e/src/runtime/Icon.vue#L100 it should wait
If the text is displayed, this mean that something wrong happened. Do you mind creating a small reproduction so we can help figure out the root cause?

Should we transfer this to nuxt-icon as it's not related to @nuxt/ui?

@benjamincanac
Please leave this issue as is. This issue is specifically about why it's a bad decision to introduce egoist/tailwindcss-icons. The nuxt-icon prerender issue is tangent to that. I'll open a separate issue in nuxt-icon.
Once nuxt-icon can prerender icons and block page navigations when icons haven't been loaded, we should be able to get rid of egoist/tailwindcss-icons here because the reasons to justify adding egoist/tailwindcss-icons no longer holds true.

@Atinux I did some digging this weekend and it's hard to reproduce this reliably. My website was deployed on Vercel, and about 50% of the deploys never have icons prerendered while the other 50% always do.
I suspect that because the loadIcon method from iconify has a 750ms timeout, if many requests to iconify were made in parallel from the same server during prerender, some of those requests may timeout leaving behind the raw text.
I've definitively seen icons rendered as text on some nuxt official websites before, so this is a widespread but hard to reproduce problem. You'll only see it flash into text once. Subsequent requests will not have the icon prerendered but you won't notice a flash as the icon was cached. And only the timed out icons will have this flash.
In my case this phenomenon is particularly bad, because my custom icon server may require 1-2s to spin up.
There are two ways to fix this:

Increase timeout to 100s
Batch icon requests during prerender

I'll open a separate issue in nuxt-icon later once I'm able to better validate this.

@Neo-Zhixing We didn't introduce @egoist/tailwindcss-icons, this module was created with it. We introduced the dynamic prop recently which fallbacks to nuxt-icon for edge cases. We are not gonna drop the parsing through Tailwind CSS in any case.


Increment version to 0.1.2

Fix issue #30: enhance the precision of the calculation of ellipse parameters from a matrix when rotations are close to +/-0.25 or +/-1.25.

@JuliaRegistrator register branch=main

Comments on pull requests will not trigger Registrator, as it is disabled. Please try commenting on a commit or issue.


Correct ZSH completion definitions

Supplying fix from https://github.com/cekit/cekit/pull/562.
This makes it auto-loadable (and adds some error handling)  - see http://zsh.sourceforge.net/Doc/Release/Completion-System.html

Could you add a changelog entry under 8.X, thanks for the PR.

Done! :-)
( Not sure why the AppVeyor CI is failing - it looks like CI setup issues? )

I ended up force pushing to fix some merge issues.  You'll need to reset your fork to continue.
git remote add upstream https://github.com/pallets/click
git fetch upstream
git checkout master
git reset --hard upstream/master
git push -f

Cherry picked to 7.1 in #1479

Is the #compdef prog_name what makes this auto loadable? Where is that in the docs? What does auto loading look like?
I'm assuming (( ! $+commands[%(script_names)s] )) && return 1 is the error handling, but what exactly does it do?
The changes still work, which is why I merged them assuming you're more familiar with it, but I don't really know much about ZSH or completion. Would really appreciate an explanation so I can maintain this better.


luci-mod-status: display log_file in status if defined

Commit includes wrapper syslog in /usr/libexec. If a log file is configured, the output of this file is displayed. Otherwise the output of logread is displayed.

Is it certain that the wrapper script passes the same exit codes as logread?
In general this is a good idea, although I think other devs would want to see the wrapper go in to a different repo. I don't think there's any real merit in doing so, since the GUI is the only place it gets leveraged here.

Is it certain that the wrapper script passes the same exit codes as logread?
In general this is a good idea, although I think other devs would want to see the wrapper go in to a different repo. I don't think there's any real merit in doing so, since the GUI is the only place it gets leveraged here.

This is a good point. I added a variable error_code to exit the script with the return  code from logread.
If there is the need to move the wrapper somewhere else, I will not obstruct that.

I made the necessary changes, @systemcrash
The exit codes are identical to logread.
I am looking forward to your review.
Thank you!

Merged. Thanks @Chris1189

@stokito we determined that -F is a write only parameter, not read. Ie destination file.
is there a good way to reconcile these disparities?

Perhaps it’s time for an option to read from a specific file.
So the only problem is log filtering…? The -e option only ever filters for
line start. So unless the log pages get some filter option, what’s the win?
(Js can filter by itself without relying on underlying binaries).

I agree with @stokito here, don't implement parallel infrastructure in the gui, don't attempt to read log files directly when cli level commands exist for that purpose.

Is that what you assess has happened here? The script still leverages logread. But until logread itself gains a parameter to read from other log files, the wrapper script uses cat.

Is that what you assess has happened here?

What happens here is that LuCI starts implementing log related infrastructure code, this belongs into base first.

As @systemcrash mentioned logread only puts log messages to a specific file with -F.
In /etc/config/system the option log_file redirects log messages to the set file. We wanted to display contents of that file because this way we can see log messages from before boot.
From the messages you wrote to the discussion I gathered that you wish to add the filter option -e from logread to the syslog-wrapper?
My intent was not to implement parallel infrastructure but to add a feature. I want to read the file if it is set.


[DO NOT MERGE] Auto PR to update dependencies of istio

This PR will be merged automatically once checks are successful.
none

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-test.sh
225b5e26fdf28d9bca5bf902a33a254060e63445
link
/test istio-unit-test

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-test.sh
225b5e26fdf28d9bca5bf902a33a254060e63445
link
/test istio-unit-test

prow/istio-unit-tests.sh
225b5e26fdf28d9bca5bf902a33a254060e63445
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Add Secrets Reference for Integration Tests

Context
For the past week, our integration tests have been unable to access the GitHub Client ID and Secret, causing test failures and preventing successful test execution.
Solution
This update adds CLIENTID and CLIENTSECRET as environment variables in the build and test workflow. With these additions, the builder pipeline now successfully recognizes the required variables, ensuring integration tests can run as expected.

༼ つ ◕_◕ ༽つ Nice job


Summon, not toggle visibility, window on command line dispatch

Summon, not toggle visibility, window on command line dispatch
PR Checklist

[x] Closes #10292
[x] I work here
[x] Manual test

Detailed Description of the Pull Request / Additional comments

This is the same as #10389, just a different route. I didn't realize it at the time.

Validation Steps Performed

Opened a window. Dispatched the wt -w 0 - p <profile> and watched it join/summon instead of minimize the active WT.

@msftbot merge this in 1 minute


Route filter on planner is hidden

Route filter (type) buttons are hidden.

The webpage must be zoomed out in the browser to show the buttons

@pyrog I have been trying to reproduce this problem in browerstack.com without success, do you still see the problem today?


document is not defined related to CustomEvents

I'm experiencing an odd issue... after a while of running my bankai server (generated by create-choo-app version ^9.0.0-1), I stopped it, and now I can't start it back up.
First, I got an error about window not being defined in the context of window.EventSource('sse').

Recognising this as part of choo-reload, I disabled that plugin. Now I'm getting an error about document not being defined in the context of document.createEvent.

I've tried removing a bunch of my code, and reinstalling all dependencies, and I'm still getting the issue. Any idea why?

Off the top of my head it looks like something that shouldn't be running on the server is running on the serve hence the document & window issues.
Are you trying to do server side rendering? Does bankai even support that?

No, I'm not, just a basic create choo app

Bankai does server rendering out of the box now; hence this code failing. Should check with typeof window !== 'undefined' before calling that function

The featured choo example fails with bankai 9 because of this.  If we expect people to check for window, we should add that to the example me thinks.  That or we handle this inside of choo.mount.

Yeah I wasn't calling that function; I just did create-choo-app. I think it's being thrown by one of the deps?
Regarding SSR being enabled by default, is that relevant to people using bankai as a dev server, or is it an optimisation? I've personally not had to use SSR yet. I wouldn't mind getting it as a free bonus, but it also means I don't consider the implications of window being absent when I'm just throwing a basic UI together. So I wonder how we'd make that more clear, perhaps in the errors, or maybe make it so that if SSR fails the client code still runs rather than the whole app dying?

So it looks like the CustomEvent was tied to dragula's use of the crossevent library. Disabling dragula made it work, though that means I can't use dragula with bankai.
The first screenshot, though, dealt with choo-reload. I'll try to reproduce it again.

I spent the last couple of hours trying to debug an issue which I think is related to this ticket, but I'm not using create-choo-app, or bankai@next.
I did a fresh npm install --save choo bankai. This installs choo 6.0.0 and bankai 8.1.1. I tried running the following block of code:
var choo = require('choo')
var html = require('choo/html')

var app = choo()

app.route('/', hello)
document.body.appendChild(app.start()

function hello (state, emit) {
  return html`<div>Hello world</div>`
}

bankai crashes and returns ReferenceError: document is not defined. Following the suggestion in this thread, I then ran the following block of code:
var choo = require('choo')
var html = require('choo/html')

var app = choo()

app.route('/', hello)

if (typeof window !== 'undefined') {
  document.body.appendChild(app.start())
}

function hello (state, emit) {
  return html`<div>Hello world</div>`
}

Note: the same issue with the same fix will occur if you're using app.mount() too.
This code now works, but I'm still very confused as to why there has to be a window check even when using bankai 8.1.1 which doesn't seem to do anything SSR related.
Is there a dependency that both bankai 8.1.1 and bankai@next are both using that has caused bankai 8.1.1 to break without a window check?
This has me concerned because if you don't do a window check (which isn't mentioned in either the choo README or the bankai README), your app breaks, and there's no obvious explanation as to why. If you were a new user trying the choo/bankai stack for the first time, I feel it would be somewhat confusing.


Make multi-line "edit cell dialog" larger if it contains more text and if user's screen resolution can handle it

When editing individual cells with quite a bit of text, I end up dragging the little 'enlargement corner' in the "edit cell" dialog all the time, which is not fun. I think, today, many user's screen resolution can totally deal with a slightly larger dialog window. Perhaps even one that flexibly adapts a bit to the length of text in it.

versus

@trnstlntk Looks like you made it about 30% larger, are you suggesting to have the edit cell dialog to autosize up to 30% larger when necessary to fit text?  What would be a good maximim autosize for horizontal as well as vertical, in your opinion, considering some use laptops with 14in - 15in (381mm) screens?  Perhaps we can come to some agreement on allowing autosizing % percentage against the screen size available and leave maximally 30% bordering all around the browser screen?  That way it will be somewhat consistent across all screen resolutions?

After a little research and asking friends, it seems we might best go with a simple tried and true Jquery plugin to quickly accomodate your needs.  Try it out:  http://www.jacklmoore.com/autosize/

I use a 15 inch laptop, and my previous one was 14 inch. In both cases the screen would very easily accommodate a (much) larger input box. When the user clicks 'edit' it means they are indeed interested in ... editing, and I think it's OK if a popup then takes up quite a bit of screen real estate; as long as the buttons at the bottom remain accessible.
Re actual sizing, percentages, maximums ... this would typically be an area where I'd appreciate professional input from a trained UX designer, who is aware and experienced in typical user behavior, user needs, and common UX patterns in today's web applications.

I added the accessibility label, mainly because I have a hunch this also affects that aspect of our UI.


Update criterion-compare-action

This should hopefully make it work for forks as well.
Closes #208

Ah, it looks like it doesn't handle throughput anymore.

I decided to just disable the throughput for now. I'll trade it for functioning benchmark reports.

Right, there's still throughput on master. But it should work. I'll take my chances.
bors r+


Unable to rake compile numruby

Bug Report
I am unable to rake compile the given gem file
To Reproduce
Just the normal installation of dependencies, and cloning of files with git clone
Expected Behavior
rake compile should run fine
Actual Behavior
ashvith@ideapad:~/Git/numruby$ rake compile
mkdir -p tmp/x86_64-linux/numruby/3.0.0
cd tmp/x86_64-linux/numruby/3.0.0
/usr/share/rvm/rubies/ruby-3.0.0/bin/ruby -I. ../../../../ext/extconf.rb
checking for apparent GNU g++ binary with C++0x/C++11 support... *** ../../../../ext/extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers.  Check the mkmf.log file for more details.  You may
need configuration options.

Provided configuration options:
	--with-opt-dir
	--without-opt-dir
	--with-opt-include
	--without-opt-include=${opt-dir}/include
	--with-opt-lib
	--without-opt-lib=${opt-dir}/lib
	--with-make-prog
	--without-make-prog
	--srcdir=../../../../ext
	--curdir
	--ruby=/usr/share/rvm/rubies/ruby-3.0.0/bin/$(RUBY_BASE_NAME)
/home/ashvith/Git/numruby/ext/mkmf.rb:74:in `<top (required)>': You need a version of g++ which supports -std=c++0x or -std=c++11. If you're on a Mac and using Homebrew, we recommend using mac-brew-gcc.sh to install a more recent g++. (RuntimeError)
	from ../../../../ext/extconf.rb:1:in `require_relative'
	from ../../../../ext/extconf.rb:1:in `<main>'
rake aborted!
Command failed with status (1): [/usr/share/rvm/rubies/ruby-3.0.0/bin/ruby ...]
/usr/share/rvm/gems/ruby-3.0.0/gems/rake-compiler-0.9.9/lib/rake/extensiontask.rb:193:in `block (2 levels) in define_compile_tasks'
/usr/share/rvm/gems/ruby-3.0.0/gems/rake-compiler-0.9.9/lib/rake/extensiontask.rb:190:in `block in define_compile_tasks'
Tasks: TOP => compile => compile:x86_64-linux => compile:numruby:x86_64-linux => copy:numruby:x86_64-linux:3.0.0 => tmp/x86_64-linux/numruby/3.0.0/numruby.so => tmp/x86_64-linux/numruby/3.0.0/Makefile
(See full trace by running task with --trace)

Your Environment

Ruby version used: ruby 3.0.0p0 (2020-12-25 revision 95aff21468) [x86_64-linux]
Operating system and version: Ubuntu 20.10
gcc and g++ version: 10.2.0

Changing the version to g++-8 does the trick.
First install version 8:
sudo apt-get install g++-8

To switch the version to 8, do:
sudo update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-8 10

"10" can be replaced with any version that you have currently as your default.
To quickly switch the version next time:
sudo update-alternatives --config g++


Enable runit installation in OEL systems

The imeyer/runit packagecloud repo does not have the ability to
resolve packages for OEL systems.
This commit enables runit cookbook to be able to install in OEL
systems by forcing the os platform to be rhel since that is the base
and packages should work the same way.
Pointing to packagecloud repo (master) in github since there is where
the new code for forcing exist. (Need to release it to Supermarket)

What are you thoughts on this? :smile: cc/ @cwjohnston @chrisroberts

Hi @afiune, thanks for the PR.
Looks like this needs rebase at the moment. After checking it out locally, kitchen-vagrant is not able to automatically pull in a base box for oel-67.  Is there additional configuration you can add for the base box image?

@cwjohnston rebasing.. I honestly built the box manually through https://github.com/rafacas/vagrant-boxes ... I wonder if I can upload it somewhere public...

@cwjohnston what about now? :smile:

This is the whole output of the kitchen converge:
➜  runit git:(afiune/make-it-work-in-oel) kitchen converge default-oel-66
-----> Starting Kitchen (v1.4.2)
-----> Converging <default-oel-66>...
       Preparing files for transfer
       Preparing dna.json
       Resolving cookbook dependencies with Librarian-Chef 0.0.4...
       Removing non-cookbook files before transfer
       Preparing validation.pem
       Preparing client.rb
-----> Installing Chef Omnibus (install only if missing)
       Downloading https://www.chef.io/chef/install.sh to file /tmp/install.sh
       Trying wget...
       Download complete.
       Downloading Chef  for el...
       downloading https://www.chef.io/chef/metadata?v=&prerelease=false&nightlies=false&p=el&pv=6&m=x86_64
         to file /tmp/install.sh.2356/metadata.txt
       trying wget...
       url	https://opscode-omnibus-packages.s3.amazonaws.com/el/6/x86_64/chef-12.5.1-1.el6.x86_64.rpm
       md5	ef7dab3bc7a3b9aca6899de6892497d3
       sha256	76dda2a604738ba8f7790261180d75fc1949a441a4bd791cb9a0857b6e11c72d
       downloaded metadata file looks valid...
       downloading https://opscode-omnibus-packages.s3.amazonaws.com/el/6/x86_64/chef-12.5.1-1.el6.x86_64.rpm
         to file /tmp/install.sh.2356/chef-12.5.1-1.el6.x86_64.rpm
       trying wget...
       trying curl...
       Comparing checksum with sha256sum...

         If you are installing
       on production servers via an automated process this is DANGEROUS and you will
       be upgraded without warning on new releases, even to new major releases.
       Letting the version float is only appropriate in desktop, test, development or
       CI/CD environments.

       WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING

       Installing Chef
       installing with rpm...
       warning: /tmp/install.sh.2356/chef-12.5.1-1.el6.x86_64.rpm: Header V4 DSA/SHA1 Signature, key ID 83ef826a: NOKEY
       Preparing...                ########################################### [100%]
          1:chef                   ########################################### [100%]
       Thank you for installing Chef!
       Transferring files to <default-oel-66>
       Starting Chef Client, version 12.5.1
       Creating a new client identity for default-oel-66 using the validator key.
       resolving cookbooks for run list: ["runit_test"]
       Synchronizing Cookbooks:
         - runit_test (1.0.1)
         - runit (1.7.5)
         - runit_other_test (1.0.0)
         - packagecloud (0.1.1)
       Compiling Cookbooks...
       Converging 5 resources
       Recipe: runit::default
         * service[runit] action nothing (skipped due to action :nothing)
         * execute[start-runsvdir] action nothing (skipped due to action :nothing)
         * execute[runit-hup-init] action nothing (skipped due to action :nothing)

        (up to date)
           * log[pygpgme_warning] action write (skipped due to not_if)
        (skipped due to not_if)

             - update content in file /etc/pki/rpm-gpg/RPM-GPG-KEY-packagecloud_io from none to e42d7e
             --- /etc/pki/rpm-gpg/RPM-GPG-KEY-packagecloud_io	2015-11-30 23:16:35.867654776 +0100
             +++ /tmp/chef-rest20151130-2464-1kic9qp	2015-11-30 23:16:35.863652698 +0100
             @@ -1 +1,65 @@
             +-----BEGIN PGP PUBLIC KEY BLOCK-----
             +Version: GnuPG v1.4.11 (GNU/Linux)
             +
             +mQINBFLUbogBEADceEoxBDoE6QM5xV/13qiELbFIkQgy/eEi3UesXmJblFdU7wcD
             +LOW3NuOIx/dgbZljeMEerj6N1cR7r7X5sVoFVEZiK4RLkC3Cpdns0d90ud2f3VyK
             +K7PXRBstdLm3JlW9OWZoe4VSADSMGWm1mIhT601qLKKAuWJoBIhnKY/RhA/RBXt7
             +z22g4ta9bT67PlliTo1a8y6DhUA7gd+5TsVHaxDRrzc3mKObdyS5LOT/gf8Ti2tY
             +BY5MBbQ8NUGExls4dXKlieePhKutFbde7sq3n5sdp1Ndoran1u0LsWnaSDx11R3x
             +iYfXJ6xGukAc6pYlUD1yYjU4oRGhD2fPyuewqhHNUVwqupTBQtEGULrtdwK04kgI
             +H93ssGRsLqUKe88uZeeBczVuupv8ZLd1YcQ29AfJHe6nsevsgjF+eajYlzsvC8BN
             +q3nOvvedcuI6BW4WWFjraH06GNTyMAZi0HibTg65guZXpLcpPW9hTzXMoUrZz8Mv
             +J9yUBcFPKuFOLDpRP6uaIbxJsYqiituoltl0vgS/vJcpIVVRwSaqPHa6S63dmKm2
             +6gq18v4l05mVcInPn+ciHtcSlZgQkCsRTSvfUrK+7nzyWtNQMGKstAZ7AHCoA8Pb
             +c3i7wyOtnTgfPFHVpHg3JHsPXKk9/71YogtoNFoETMFeKL1K+O+GMQddYQARAQAB
             +tDdwYWNrYWdlY2xvdWQgb3BzIChwcm9kdWN0aW9uIGtleSkgPG9wc0BwYWNrYWdl
             +Y2xvdWQuaW8+iQI+BBMBAgAoBQJS1G6IAhsvBQkJZgGABgsJCAcDAgYVCAIJCgsE
             +FgIDAQIeAQIXgAAKCRDC5zQk1ZCXq13KD/wNzAi6rEzRyx6NH61Hc19s2QAgcU1p
             +1mX1Tw0fU7CThx1nr8JrG63465c9dzUpVzNTYvMsUSBJwbb1phahCMNGbJpZRQ5b
             +vW/i3azmk/EHKL7wgMV8wu1atu6crrxGoDEfWUa4aIwbxZGkoxDZKZeKaLxz2ZCh
             +uKzjvkGUk4PUoOxxPn9XeFmJQ68ys4Z0CgIGfx2i64apqfsjVEdWEEBLoxHFIPy7
             +FgFafRL0bgsquwPkb5q/dihIzJEZ2EMOGwXuUaKI/UAhgRIUGizuW7ECEjX4FG92
             +8RsizHBjYL5Gl7DMt1KcPFe/YU/AdWEirs9pLQUr9eyGZN7HYJ03Aiy8R5aMBoeY
             +sfxjifkbWCpbN+SEATaB8YY6Zy2LK/5TiUYNUYb/VHP//ZEv0+uPgkoro6gWVkvG
             +DdXqH2d9svwfrQKfGSEQYXlLytZKvQSDLAqclSANs/y5HDjUxgtWKdsL3xNPCmff
             +jpyiqS4pvoTiUwS4FwBsIR2sBDToIEHDvTNk1imeSmxCUgDxFzWkmB70FBmwz7zs
             +9FzuoegrAxXonVit0+f3CxquN7tS0mHaWrZfhHxEIt65edkIz1wETOch3LIg6RaF
             +wsXgrZCNTB/zjKGAFEzxOSBkjhyJCY2g74QNObKgTSeGNFqG0ZBHe2/JQ33UxrDt
             +peKvCYTbjuWlyrkCDQRS1G6IARAArtNBXq+CNU9DR2YCi759fLR9F62Ec/QLWY3c
             +/D26OqjTgjxAzGKbu1aLzphP8tq1GDCbWQ2BMMZI+L0Ed502u6kC0fzvbppRRXrV
             +axBrwxY9XhnzvkXXzwNwnBalkrJ5Yk0lN8ocwCuUJohms7V14nEDyHgAB8yqCEWz
             +Qm/SIZw35N/insTXshcdiUGeyufo85SFhCUqZ1x1TkSC/FyDG+BCwArfj8Qwdab3
             +UlUEkF6czTjwWIO+5vYuR8bsCGYKCSrGRh5nxw0tuGXWXWFlBMSZP6mFcCDRQDGc
             +KOuGTjiWzLJcgsEcBoIX4WpHJYgl6ovex7HkfQsWPYL5V1FIHMlw34ALx4aQDH0d
             +PJpC+FxynrfTfsIzPnmm2huXPGGYul/TmOp00CsJEcKOjqcrYOgraYkCGVXbd4ri
             +6Pf7wJNiJ8V1iKTzQIrNpqGDk306Fww1VsYBLOnrSxNPYOOu1s8c8c9N5qbEbOCt
             +QdFf5pfuqsr5nJ0G4mhjQ/eLtDA4E7GPrdtUoceOkYKcQFt/yqnL1Sj9Ojeht3EN
             +PyVSgE8NiWxNIEM0YxPyJEPQawejT66JUnTjzLfGaDUxHfseRcyMMTbTrZ0fLJSR
             +aIH1AubPxhiYy+IcWOVMyLiUwjBBpKMStej2XILEpIJXP6Pn96KjMcB1grd0J2vM
             +w2Kg3E8AEQEAAYkERAQYAQIADwUCUtRuiAIbLgUJCWYBgAIpCRDC5zQk1ZCXq8Fd
             +IAQZAQIABgUCUtRuiAAKCRA3u+4/etlbPwI5D/4idr7VHQpou6c/YLnK1lmz3hEi
             +kdxUxjC4ymOyeODsGRlaxXfjvjOCdocMzuCY3C+ZfNFKOTtVY4fV5Pd82MuY1H8l
             +nuzqLxT6UwpIwo+yEv6xSK0mqm2FhT0JSQ7E7MnoHqsU0aikHegyEucGIFzew6BJ
             +UD2xBu/qmVP/YEPUzhW4g8uD+oRMxdAHXqvtThvFySY/rakLQRMRVwYdTFHrvu3z
             +HP+6hpZt25llJb3DiO+dTsv+ptLmlUr5JXLSSw2DfLxQa0kD5PGWpFPVJcxraS2p
             +NDK9KTi2nr1ZqDxeKjDBT6zZOs9+4JQ9fepn1S26AmHWHhyzvpjKxVm4sOilKysi
             +84CYluNrlEnidNf9wQa3NlLmtvxXQfm1py5tlwL5rE+ek1fwleaKXRcNNmm+T+vD
             +dIw+JcHy8a53nK1JEfBqEuY6IqEPKDke0wDIsDLSwI1OgtQoe7Cm1PBujfJu4rYQ
             +E+wwgWILTAgIy8WZXAloTcwVMtgfSsgHia++LqKfLDZ3JuwpaUAHAtguPy0QddvF
             +I4R7eFDVwHT0sS3AsG0HAOCY/1FRe8cAw/+9Vp0oDtOvBWAXycnCbdQeHvwh2+Uj
             +2u2f7K3CDMoevcBl4L5fkFkYTkmixCDy5nst1VM5nINueUIkUAJJbOGpd6yFdif7
             +mQR0JWcPLudb+fwusJ4UEACYWhPa8Gxa7eYopRsydlcdEzwpmo6E+V8GIdLFRFFp
             +KHQEzbSW5coxzU6oOiPbTurCZorIMHTA9cpAZoMUGKaSt19UKIMvSqtcDayhgf4c
             +Z2ay1z0fdJ2PuLeNnWeiGyfq78q6wqSaJq/h6JdAiwXplFd3gqJZTrFZz7A6Q6Pd
       wHUv7Fg357kRSdzKv9D
             +bgmhqRHlgVeKn9pwN4cpVBN+idzwPefQksSKH4lBDvVr/9j+V9mmrOx7QmQ5LCc/
             +1on+L0dqo6suoajADhKy+lDQbzs2mVb4CLpPKncDup/9iJbjiR17DDFMwgyCoy5O
             +HJICQ5lckNNgkHTS6Xiogkt28YfK4P3S0GaZgIrhKQ7AmO3O+hB12Zr+olpeyhGB
             +OpBD80URntdEcenvfnXBY/BsuAVbTGXiBzrlBEyQxg656jUeqAdXg+nzCvP0yJlB
             +UOjEcwyhK/U2nw9nGyaR3u0a9r24LgijGpdGabIeJm6O9vuuqFHHGI72pWUEs355
             +lt8q1pAoJUv8NehQmlaR0h5wcwhEtwM6fiSIUTnuJnyHT053GjsUD7ef5fY1KEFm
             +aZeW04kRtFDOPinz0faE8hvsxzsVgkKye1c2vkXKdOXvA3x+pZzlTHtcgMOhjKQA
             +sA==
             +=H60S
             +-----END PGP PUBLIC KEY BLOCK-----

           * template[/etc/yum.repos.d/imeyer_runit.repo] action create

             - update content in file /etc/yum.repos.d/imeyer_runit.repo from none to 437004
             --- /etc/yum.repos.d/imeyer_runit.repo	2015-11-30 23:16:36.055749040 +0100
             +++ /etc/yum.repos.d/.imeyer_runit.repo20151130-2464-e9nh3m	2015-11-30 23:16:36.055749040 +0100
             @@ -1 +1,10 @@
             +[imeyer_runit]
             +name=imeyer_runit
             +baseurl=https://packagecloud.io/imeyer/runit/el/6/$basearch
             +repo_gpgcheck=1
             +gpgcheck=0
             +enabled=1
             +gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-packagecloud_io
             +sslverify=1

             - execute the ruby block yum-cache-reload-imeyer_runit
           * execute[yum-makecache-imeyer_runit] action nothing (skipped due to action :nothing)
           * ruby_block[yum-cache-reload-imeyer_runit] action nothing (skipped due to action :nothing)

           - install version 2.1.2-1.el6 of package runit

       Running handlers:
       Running handlers complete
       Chef Client finished, 6/14 resources updated in 02 minutes 43 seconds
       Finished converging <default-oel-66> (6m5.95s).
-----> Kitchen is finished. (6m8.37s)
zlib(finalizer): the stream was freed prematurely.
➜  runit git:(afiune/make-it-work-in-oel)

And finally here the output of the kitchen verify:
➜  runit git:(afiune/make-it-work-in-oel) kitchen verify default-oel-66
-----> Starting Kitchen (v1.4.2)
-----> Setting up <default-oel-66>...
       Finished setting up <default-oel-66> (0m0.00s).
-----> Verifying <default-oel-66>...
       Preparing files for transfer
-----> Installing Busser (busser)
Fetching: thor-0.19.0.gem (100%)
       Successfully installed thor-0.19.0
Fetching: busser-0.7.1.gem (100%)
       Successfully installed busser-0.7.1
       2 gems installed
-----> Setting up Busser
       Creating BUSSER_ROOT in /tmp/verifier
       Creating busser binstub
       Installing Busser plugins: busser-serverspec
       Plugin serverspec installed (version 0.5.7)
-----> Running postinstall for serverspec plugin
       Suite path directory /tmp/verifier/suites does not exist, skipping.
       Transferring files to <default-oel-66>
-----> Running serverspec test suite
-----> Installing Serverspec..
Fetching: sfl-2.2.gem (100%)
Fetching: net-telnet-0.1.1.gem (100%)
Fetching: net-ssh-2.9.2.gem (100%)
Fetching: net-scp-1.2.1.gem (100%)
Fetching: specinfra-2.44.3.gem (100%)
Fetching: multi_json-1.11.2.gem (100%)
Fetching: diff-lcs-1.2.5.gem (100%)
Fetching: rspec-support-3.4.1.gem (100%)
Fetching: rspec-expectations-3.4.0.gem (100%)
Fetching: rspec-core-3.4.1.gem (100%)
Fetching: rspec-its-1.2.0.gem (100%)
Fetching: rspec-mocks-3.4.0.gem (100%)
Fetching: rspec-3.4.0.gem (100%)
Fetching: serverspec-2.24.3.gem (100%)
-----> serverspec installed (version 2.24.3)
       /opt/chef/embedded/bin/ruby -I/tmp/verifier/suites/serverspec -I/tmp/verifier/gems/gems/rspec-support-3.4.1/lib:/tmp/verifier/gems/gems/rspec-core-3.4.1/lib /opt/chef/embedded/bin/rspec --pattern /tmp/verifier/suites/serverspec/\*\*/\*_spec.rb --color --format documentation --default-path /tmp/verifier/suites/serverspec
       os: {:family=>"redhat", :release=>"6.6", :arch=>"x86_64"}
       os: {:family=>"redhat", :release=>"6.6", :arch=>"x86_64"}

       Package "runit"
         should be installed

       Command "ps -ef | grep -v grep | grep "runsvdir""
         exit_status
           should eq 0
         stdout
           should match /runsvdir/

       File "/etc/service"
         should be directory
         should be mode 755
         should be owned by "root"
         should be grouped into "root"

       Finished in 0.22637 seconds (files took 0.37914 seconds to load)
       7 examples, 0 failures

       Finished verifying <default-oel-66> (0m28.95s).
-----> Kitchen is finished. (0m31.23s)
zlib(finalizer): the stream was freed prematurely.
➜  runit git:(afiune/make-it-work-in-oel)

@cwjohnston ping :smile:

while true do
  system 'ping  @cwjohnston @chrisroberts'
  sleep 86400
end

cc/ @cwjohnston @chrisroberts :smiling_imp:

@afiune Thanks for the updates. I'm running all the rhel tests now to confirm there's no regression. If all looks good, this should be green lit for the next release.

@afiune I ran the default suite successfully, but encountered a pretty solid failure with the service suite. Can you confirm that you are able to run that test?
Here's the output (sparing you a few thousand lines of kernel info that it spat out):
       STDERR:
       ---- End output of /usr/bin/python /opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.5.1/lib/chef/provider/package/yum-dump.py --options --all-provides --yum-lock-timeout 30 ----
       Ran /usr/bin/python /opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.5.1/lib/chef/provider/package/yum-dump.py --options --all-provides --yum-lock-timeout 30 returned
       [2015-12-02T18:21:03+01:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
>>>>>> Converge failed on instance <service-oel-66>.
>>>>>> Please see .kitchen/logs/service-oel-66.log for more details
>>>>>> ------Exception-------
>>>>>> Class: Kitchen::ActionFailed
>>>>>> Message: SSH exited (1) for command: [sh -c '

sudo -E /opt/chef/bin/chef-client --local-mode --config /tmp/kitchen/client.rb --log_level auto --force-formatter --no-color --json-attributes /tmp/kitchen/dna.json --chef-zero-port 8889
']
>>>>>> ----------------------

@luckymike interesting. Let me look at that one.. :smile:

@afiune If you can rebase this I'll get it merged in and released

@tas50

thanks and I enjoyed the gif


ENH: Add image.astype(pixel_type) for casting

Similar to the numpy.ndarray.astype, supporting itk PixelType's and
numpy dtype's.
More convenient than itk.cast_image_filter, similar to
numpy.ndarray.astype. itk.Image PixelType's are supported along with
scalar numpy dtype's. itkType.itkCType.GetCTypeForDType is added to
support conversion.

Failing test unrelated.


[fix] Fix For Error Code Collision Due To 8-bit Component Code

The component names were 8-bit fields and the associated code for the components were more than 8-bits. Due to this, the components names greater than 256 were overflowing, rendering the error codes incorrect.

Problems merging with main. Will raise another PR for this.


Lack of clarity about sim function vs feature map for paper/code

Hi, I read your paper and found the following confusing. When you're describing your ablations which culminate in ReBased it starts with

x^2 – substituting the original kernel function with a simple element-wise squaring operation, ϕ(x) = x^2.

but, this doesn't seem to be what happens in your code. See these lines
https://github.com/corl-team/rebased/blob/7a085b40e0a2c615f35ee43afd19f856df37819e/flash_linear_attention/fla/ops/triton/rebased_fast/parallel.py#L68-L69
My understanding of Linear Attention is the following. We need two functions: a similarity function (called sim or s) which takes two vectors and returns a scalar and a feature map (called phi typically) which takes a single vector and returns another vector (possibly of different dimension). Ignoring normalization by 1/sqrt(d) for simplicity, Linear Attention requires that
s(q, k) = dot(phi(q), phi(k))
Those lines of code I linked to correspond to defining
s(q, k) = dot(q, k)**2
The feature map phi which corresponds to this similarity function is not elementwise squaring. I.e.,  phi(x) = x**2 is not the corresponding feature map for that similarity function. The correct corresponding feature map is phi(x) = flatten(outer(x, x))
One could say similar things about the other variants in the ablations, including ReBased.
Am I missing something?

Hi, thank you for your interest. Sorry for the confusion, by phi=x^2 we use simplified notation. From my perspective in case of sim(q, k) = (q^Tk)^2 we have phi(q) != q^2.  However, we still can factorise our similarity into kernels.
Check out tests with the reference implementation:
https://github.com/corl-team/rebased/blob/fc11fa14b28b1a0948a03d69675ac0163b6d75d2/flash_linear_attention/fla/layers/rebased_fast.py#L66-L70
https://github.com/corl-team/rebased/blob/fc11fa14b28b1a0948a03d69675ac0163b6d75d2/flash_linear_attention/fla/layers/rebased_fast.py#L161

Still confused.
These lines you link to
https://github.com/corl-team/rebased/blob/fc11fa14b28b1a0948a03d69675ac0163b6d75d2/flash_linear_attention/fla/layers/rebased_fast.py#L66-L70
correspond to computing an outer product and flattening.
To clarify, it seems like you agree that the similarity function is sim(q, k) = dot(q, k)**2 but do you agree with

The feature map phi which corresponds to this similarity function is not elementwise squaring. I.e., phi(x) = x**2 is not the corresponding feature map for that similarity function. The correct corresponding feature map is phi(x) = flatten(outer(x, x))

Agree?

Yes. I agree. The verification code can be even simpler
import numpy as np

q = np.random.normal(0, 1, 64)
k = np.random.normal(0, 1, 64)

self_outer_flatten = lambda x: np.outer(x, x).flatten()

assert np.allclose(np.dot(q, k)**2, np.dot(self_outer_flatten(q), self_outer_flatten(k)))

Good. We're on the same page there.
Returning to my original post, and the title of this issue: your paper seems to be inconsistent/confused with your code.

x^2 – substituting the original kernel function with a simple element-wise squaring operation, ϕ(x) = x^2.

Your paper seems to me to be conflating a similarity function (also called a kernel function) with a feature map (phi). There is no element-wise squaring anywhere. Your paper doesn't use the term "feature map" or "feature function" or "feature representation" anywhere.

Noting that we provided a one-dimensional scenario in the paper for simplicity, we agree that the notations of the kernel function and feature mapping therein can be confusing. We will update it to make it more accurate. Thank you for pointing that out!


Types\AmountType cast as double

Hi there,
I think it's wrong to use double here. I know ebay ask for double but the problem is with prices without decimals.
Example:
$request = new Types\ReviseItemRequestType();
$item = new Types\ItemType();
$item->BuyItNowPrice = new Types\AmountType(['value' => 100]);

Request looks like this:
Array
(
    [Item] => Array
        (
            [BuyItNowPrice] => Array
                (
                    [value] => 120
                )

            [Description] => Microwave-safe.
Dishwasher-safe.
            [ItemID] =><PHONE_NUMBER>34
            [StartPrice] => Array
                (
                    [value] => 100.99
                )

            [Title] => Simple mug
        )

)

eBay error returned:

Error: Invalid start price/Buy It Now price.
You have entered invalid start price or Buy It Now price.

I know that I'm supposed to send 120.00 but since prices are stored in DB and I get the values using sql query I'm getting a 'string' type for the price stored in DB.
And I don't think it's possible to cast that value to a double with two zero decimals.

I'm sorry, the problem was elsewhere.

No problem :)


Topbar becomes too huge

          Our topbar becomes too huge...

Originally posted by @sanyavertolet in https://github.com/saveourtool/save-cloud/pull/2226#discussion_r1236643193
We need to come up with an idea of decreasing topbar size

We can introduce Hamburger button to our topbar to reduce this size and add additional info

Need to fix "logout" menu when we are not authorised:

Yes, Log in might be nice. Moreover, log in might be even better if it redirects to the page on which the log in button was pressed

I guess this issue is completed @akuleshov7 ?


Revert "Integrate commissioner and device clusters with operational credentials"

Reverts project-chip/connectedhomeip#6705
This PR has broken PASE connection for chip-tool/python chip device controller in real device and virtual CIRQUE mobile device test, and make TE3 branch cutoff(Today) in danger, this change is also blocking song's another TE3 critical fix(https://github.com/project-chip/connectedhomeip/pull/6761)
Issues:
https://github.com/project-chip/connectedhomeip/issues/6797
With this change, cirque mobile test is broken
https://github.com/project-chip/connectedhomeip/runs/2582236209?check_suite_focus=true
Without this change, cirque mobile test pass
https://github.com/yunhanw-google/connectedhomeip/runs/2582288143?check_suite_focus=true

@woody-apple  please decide if we can revert it, considering TE3 cutoff date is today, not sure if TE3 needs to test this feature. thanks

The conflict here is that the controller needs access to the clusters to perform commissioning, including operational certificate exchange. chip-device-ctrl swaps out the IM delegate wholesale and assumes that nothing else will be touching anything to do with the clusters. I've run into the same problem for IP commissioning. Right now, I'm working on a PR that will allow this to be controlled by a build flag, which is obviously not ideal in the long term. If we revert this, it will affect TE3 - we won't be able to test operational certificates or IP commissioning.

@pan-apple ?

@pan-apple ?

I agree with what @cecille said above. The flow is breaking because how chip-device-ctrl is handling the IM messages. Reverting #6705 is not the right fix. I think Song is working on a PR to fix the actual issue.
Also, for reference, the commissioning flow is working fine with iOS CHIPTool app.

@pan-apple ?

I agree with what @cecille said above. The flow is breaking because how chip-device-ctrl is handling the IM messages. Reverting #6705 is not the right fix. I think Song is working on a PR to fix the actual issue.
Also, for reference, the commissioning flow is working fine with iOS CHIPTool app.

Per latest TOT test result from @cjandhyala
chip-tool is also breaking because of this issue.
ios app is also breaking in tot
Song's PR fails to fix the above issue, that is why we try to revert.
After revert, chip-tool and chip-device-ctrl can work

close this one, since TE3 is pushed to next Friday, we would focus on right solution forward