text:
Invalid hook call on login page

Describe the bug
I'm getting the following error:
(node:18527) UnhandledPromiseRejectionWarning: Error: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://fb.me/react-invalid-hook-call for tips about how to debug and fix this problem.
    at resolveDispatcher (/Users/david/workspace/dongwon-api/node_modules/react/cjs/react.development.js:1465:13)
    at Object.useState (/Users/david/workspace/dongwon-api/node_modules/react/cjs/react.development.js:1496:20)
    at ae (/Users/david/workspace/dongwon-api/node_modules/styled-components/dist/styled-components.cjs.js:1:13232)
    at processChild (/Users/david/workspace/dongwon-api/node_modules/admin-bro/node_modules/react-dom/cjs/react-dom-server.node.development.js:3043:14)
    at resolve (/Users/david/workspace/dongwon-api/node_modules/admin-bro/node_modules/react-dom/cjs/react-dom-server.node.development.js:2960:5)
    at ReactDOMServerRenderer.render (/Users/david/workspace/dongwon-api/node_modules/admin-bro/node_modules/react-dom/cjs/react-dom-server.node.development.js:3435:22)
    at ReactDOMServerRenderer.read (/Users/david/workspace/dongwon-api/node_modules/admin-bro/node_modules/react-dom/cjs/react-dom-server.node.development.js:3373:29)
    at renderToString (/Users/david/workspace/dongwon-api/node_modules/admin-bro/node_modules/react-dom/cjs/react-dom-server.node.development.js:3988:27)
    at html (/Users/david/workspace/dongwon-api/node_modules/admin-bro/lib/frontend/login-template.js:73:53)
    at processTicksAndRejections (internal/process/task_queues.js:94:5)
    at async /Users/david/workspace/dongwon-api/node_modules/@admin-bro/express/lib/authentication/login.handler.js:19:23

Installed libraries and their versions

admin-bro@3.4.0
@admin-bro/express@3.1.0
@admin-bro/sequelize@1.2.1
react@16.13.1
react-dom@16.13.1

To Reproduce
Steps to reproduce the behavior:

Use buildAuthenticatedRouter to create AdminBro router.
Run the app & visit /admin

Additional context
There's a closed issue about this matter, but I was not able to resolve this problem after removing node_modules or by adding react & react-dom as dependencies.

Just confirming, are you using admin-bro-expressjs or @admin-bro/express?

@dziraf My mistake, I'm using @admin-bro/express^3.1.0, and @admin-bro/design-system version is 1.7.0.

I will try to reproduce this error tomorrow. I DID get this error before, but only when developing admin-bro packages by yarn link-ing them though.
Two extra questions:

Is it an existing project and this is a new error or you've only just setup admin bro?
Could you check what's the package version of React in:
/node_modules/react/package.json
and
/node_modules/@admin-bro/design-system/node_modules/react/package.json
/node_modules/admin-bro/node_modules/react/package.json
It should be at the top.

First off, thanks for looking into this issue.
To answer your questions,

I started using admin-bro recently but just recently set up buildAuthenticatedRouter and encountered this error.
react version in /node_modules/react' is 16.13.1, node_modules/@admin-bro/design-systemis 16.13.1, and finally innode_modules/admin-bro` is also 16.13.1.

To provide a bit more context, I'm using a custom dashboard but I don't think it's related to this as the hook errors show up even when I'm using the vanilla dashboard.

I tried to reproduce on a clean project but I'm not experiencing this problem there.
Are you able to set up a simple repository where this error occurs for you so that I can clone it?
Also, we've released admin-bro@v4.0.1 - I doubt updating will help in this case but is worth trying

I ended up fixing this problem. These are the steps I took:

Removed node_modules completely again
Deleted react & react-dom from dependencies in my package.json
Ran npm install again
On install, npm was complaining about missing peer dependencies for admin-bro like before (react, react-dom, etc).
Used install-peerdeps on admin-bro packages.
Works like a charm

After trying everything that has been mentioned about this error, it continues to persist... I don't know what to do...

This error disappears when I use admin-bro@3.2.5....

Happened to me on buildAuthenticatedRouter:
"@admin-bro/design-system": "^1.7.3",
"@admin-bro/express": "^3.1.0",
"@admin-bro/mongoose": "^1.1.0",
"@admin-bro/passwords": "^1.0.3",
"admin-bro": "^4.0.1",
"express-formidable": "^1.2.0",
"express-session": "^1.17.1",
"react": "^17.0.2",
"react-dom": "^17.0.2"
Using yarn as package manager.

Fixed by using same react/react-dom versions as in admin-bro dependencies:
"react": "=16.13.1",
"react-dom": "=16.13.1"

@yarikpwnzer Well I tried with the exact same version but it doesn't work either. It only works if I use admin-bro@3.2.5.

What is the difference between admin-bro-expressjs an @admin-bro/express ??

I was just playing with the packages (deleting and re-downloading them and changing their versions) and it just started working. Weird...
sorry for all of the comments

@kodesak I opened yarn.lock and checked versions of react/react-dom and what I noticed that there were two entries: one was added by me (17.0.2) and another was dependency of admin-bro (16.13.1). For it worked also without adding it to my dependencies, but since I'm using eslint I got errors in the code.

I am getting the same error. It works totally fine with local server but when I try to run in the Testing or Staging server it throws this error. I have referred all the solutions regarding this from https://reactjs.org/warnings/invalid-hook-call-warning.html. I think I have multiple react as shown in attached image but I am not able to figure out how can I correct the tree or solve it. Thanks in advance!

At this point, I am probably going to abandon this package because of this error that is stopping me every time...

I get this issue when i have React version ^17.0.2 in my dependencies. If i change it to adminjs version 16.13.1 the issue disappears. But then my Next.JS SSR stops working (monorepo). I need it to work with my main React dependency being of version ^17.0.2 somehow.
@dziraf Could you suggest a solution please?

Coming from the error message:
(node:20508) UnhandledPromiseRejectionWarning: Error: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.
    at resolveDispatcher (C:\Users\maxim\WebstormProjects\portfolio\node_modules\react\cjs\react.development.js:1476:13)
    at Object.useState (C:\Users\maxim\WebstormProjects\portfolio\node_modules\react\cjs\react.development.js:1507:20)
    at ae (C:\Users\maxim\WebstormProjects\portfolio\node_modules\styled-components\src\utils\isStaticRules.js:6:54)
    at processChild (C:\Users\maxim\WebstormProjects\portfolio\node_modules\adminjs\node_modules\react-dom\cjs\react-dom-server.node.development.js:3043:14)
    at resolve (C:\Users\maxim\WebstormProjects\portfolio\node_modules\adminjs\node_modules\react-dom\cjs\react-dom-server.node.development.js:2960:5)
    at ReactDOMServerRenderer.render (C:\Users\maxim\WebstormProjects\portfolio\node_modules\adminjs\node_modules\react-dom\cjs\react-dom-server.node.development.js:3435:22)
    at ReactDOMServerRenderer.read (C:\Users\maxim\WebstormProjects\portfolio\node_modules\adminjs\node_modules\react-dom\cjs\react-dom-server.node.development.js:3373:29)
    at renderToString (C:\Users\maxim\WebstormProjects\portfolio\node_modules\adminjs\node_modules\react-dom\cjs\react-dom-server.node.development.js:3988:27)
    at html (C:\Users\maxim\WebstormProjects\portfolio\node_modules\adminjs\lib\frontend\login-template.js:73:53)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at C:\Users\maxim\WebstormProjects\portfolio\node_modules\@adminjs\express\src\authentication\login.handler.ts:27:19
    ```

    I think the first probable reason `1. You might have mismatching versions of React and the renderer (such as React DOM)` might be the case. Because from the stacktrace above, we see that `react-dom` is used from `node_modules\adminjs\node_modules\react-dom` directory (older version), but then `react` is used from `node_modules\react` directory (newer version, which is specified in package.json).
    That being said, it makes sense why lowering the `react` version in package.json fixes the issue. Yet i currently don't know why this behaviour appears and how to make it work like the rest of the app does. (Everything in adminjs works fine except the login page)

Ok so i just wrote "styled-components": "=4.4.1" in my package.json and it started working 😂.
From the third line of stacktrace at ae (C:\Users\maxim\WebstormProjects\portfolio\node_modules\styled-components\src\utils\isStaticRules.js:6:54) i saw that it also uses my newest styled-components package, then it goes to my latest react package. I use Yarn. I assume that it saw that my styled-components version and the one in adminjs are compatible (though not the same, i checked) so it linked it to share for adminjs. That somehowe caused the usage of another React version i described above.
Thats how i understand it, though it's kinda a bit crazy. I would be glad if someone can clear this up more.

To fix this issue, I switched to yarn and added this in my package.json.
"resolutions": {
    "adminjs/react": "17.0.2",
    "adminjs/react-dom": "17.0.2"
  },

I'm stucked in this issue. I'm working on a project on two pc. On the first it always have been worked and on my new pc i have this issue even if i have same package.json file with same versions on both pc, i don't understand why...

Fixed by using same react/react-dom versions as in admin-bro dependencies: "react": "=16.13.1", "react-dom": "=16.13.1"

This worked for me, after a whole day of trying to figure out the issue. Thanks a bunch

i ran into this issue again. was working fine until the latest update. however once i updated latest versions of adminjs @adminjs/express @adminjs/mongoose this error started coming. i resolved it by installing react and react-dom into my backend.

i ran into this issue again. was working fine until the latest update. however once i updated latest versions of adminjs @adminjs/express @adminjs/mongoose this error started coming. i resolved it by installing react and react-dom into my backend.

This worked for me just fine after many tries as it auto-updates all dependencies !

Issue is not fixed. After latest update, react needs to be manually installed so that adminjs can run.

authors: Gr8z ItsYou RolandVrignon RudrikaJnext basit3407 coolprinze dziraf kodesak mkayander petrakoww yarikpwnzer yassir63


text:
refactor: moved the OTel samples from howtos to patterns directory since they are full examples

Changes:

refactor: moved the OTel samples from the /howtos directory to /patterns directory since they are full runnable samples and not how-Tos.

Thanks @TamimiGitHub!

source: gharchive/pull-request

repo: SolaceSamples/solace-samples-go

license_type: permissive

license_source: github-api


text:
Add reference load forecast method

[x] Closes #55 .
[x] I am familiar with the contributing guidelines.
[ ] Tests added.
[ ] Updates entries to docs/source/api.rst for API changes.
[ ] Adds descriptions to appropriate "what's new" file in docs/source/whatsnew for all changes. Includes link to the GitHub Issue with :issue:`num` or this Pull Request with :pull:`num`. Includes contributor name and/or GitHub username (link with :ghuser:`user`).
[x] New code is fully documented. Includes numpydoc compliant docstrings, examples, and comments where necessary.
[ ] Maintainer: Appropriate GitHub Labels and Milestone are assigned to the Pull Request and linked Issue.

This PR adds persistence_hourofday_dayofweek() function, which will serve as a baseline/reference load forecast. The basic idea is similar to a Smart Persistence, but instead of a clear-sky model, the method uses a dynamically updated trend of the load to adjust the (dull) persistence forecast. For load (or net load), adjusting for hour of day (HOD) and day of week (DOW) trends typically provides a noticeable improvement over (dull) persistence, while requiring a minimal number of assumptions about the data.
NOTE: still a WIP. I've already coded up a script that completes all the steps, but the main thing left now is converting the scripts into functions compatible with the solarforecastarbiter work flow.

While I work on integrating the reference (net) load forecast into SFA, here's a sample script showing the main ideas. Note: this code is (obviously) not consistent with SFA conventions and has a range of "oddities" (e.g. I'm abusing the definition of "clear-sky"), but the main concepts are valid: estimate the "typical" load (as a function of hour of day and weekday vs weekend) using a rolling window and then adjust the (dull) persistence forecast using the "typical" load. (Same basic idea as a Smart Persistence using a clear-sky irradiance model.)
Script to generate a (dull) persistence and smart persistence forecast of net load:
import numpy as np
import pandas as pd

def estimate_clearsky(df, var="demand"):
    """Estimate clear-sky dynamically.

    Parameters
    ----------
    df : pandas.DataFrame
        Time-series of the target variable.
    var : str
        The target variable column.

    Returns
    -------
    cs : pandas.DataFrame
        Time-series of the clear-sky model.

    """

    # reshape to (date, hour of day)
    df.insert(df.shape[1], "hod", df.index.hour + df.index.minute / 60.0)
    df = pd.pivot_table(df, index=df.index.normalize(), columns="hod", values=var)

    # estimate clearsky for weekday vs weekend (0=Monday, 6=Sunday)
    frames = []
    for dow in [(0, 1, 2, 3, 4), (5, 6)]:

        group = df[df.index.dayofweek.isin(dow)]

        # update every week
        group = group.resample("1w", closed="right", label="right").median()

        # if missing, use the most recent weekly estimate
        group = group.resample("1D", closed="right", label="right").fillna(method="ffill")

        # remove dates not in the specified DOW
        # (e.g. don't use the weekday trend for weekend)
        group = group[group.index.dayofweek.isin(dow)]

        frames.append(group)

    df = pd.concat(frames, axis=0).sort_index().reset_index()
    df = df.melt(id_vars="timestamp", var_name="hour", value_name=f"{var}_clear")
    df["hour"] = pd.to_numeric(df["hour"])
    df["timestamp"] = df["timestamp"] + df["hour"] * np.timedelta64(1, "h")
    df = df.set_index("timestamp")
    df = df[[f"{var}_clear"]]

    return df

if __name__ == "__main__":

    # timestamp (local) + net load [MWh]
    df = pd.read_csv("load_caiso.csv", parse_dates=True, index_col=0)

    # add clear-sky index (kt) for demand
    cs = estimate_clearsky(df, var="demand")
    df = df.join(cs, how="outer")
    df.insert(df.shape[1], "demand_kt", df["demand"] / df["demand_clear"])

    # forecast horizon (single)
    horizon = "2h"  # RT market
    #horizon = "26h"  # DA market (due by 10am) = noon next day

    # add Persistence forecast
    pers = df.copy()
    pers = pers.shift(periods=1, freq=horizon)
    df = df.join(pers, rsuffix="_pers")

    # add Smart Pers. forecast
    df.insert(df.shape[1], "demand_smart", df["demand_kt_pers"] * df["demand_clear"])

    # add timestamps
    df.index.name = "target_datetime"
    df.insert(df.shape[1], "forecast_datetime", df.index - pd.Timedelta(horizon))

    df = df[["demand", "demand_pers", "demand_smart"]].dropna(how="any")

    # compute error metrics
    var = "demand"
    for model in ["pers", "smart"]:
        error = (df[f"{var}_{model}"] - df[var]).values
        mae = np.mean(np.abs(error))
        mbe = np.mean(error)
        rmse = np.sqrt(np.mean(error ** 2))
        mape = np.mean(np.abs(error / df[var].values))
        print("{:<10}: {:<6}: MAE = {:>6.1f} | MBE = {:>6.1f} | RMSE = {:>6.1f} | MAPE = {:>6.1%} | max = {:>8.1f}".format(var, model, mae, mbe, rmse, mape, df[var].max()))

Sample output using 1 year (2017) of hourly net load data from CAISO:
# `horizon = "2h"`
demand    : pers  : MAE = 1759.6 | MBE =    1.6 | RMSE = 2218.1 | MAPE =   6.6% | max =  49899.0
demand    : smart : MAE =  515.2 | MBE =    7.2 | RMSE =  769.4 | MAPE =   1.9% | max =  49899.0

# `horizon = "26h"`
demand    : pers  : MAE = 2271.3 | MBE =   -0.8 | RMSE = 2897.3 | MAPE =   8.5% | max =  49899.0
demand    : smart : MAE = 1333.9 | MBE =   63.8 | RMSE = 2183.9 | MAPE =   4.8% | max =  49899.0

For net load, MAPE is the most commonly used metric and the Smart Persistence forecast (using the dynamically estimated "typical" load) shows a distinct improvement compared to the Persistence.
NOTES:

obviously "clear-sky" isn't the correct term, but I'm still figuring out the best nomenclature for this
there's not a clear answer to whether computing the "typical" load by a) weekday vs weekend or b) day of week (i.e. one typical load profile for Monday, a different profile for Tuesday, etc.) is "optimal"

I'm still thinking through some details of the implementation (so that this work is compatible with the other reference forecast functions) and will likely have some questions during tomorrow's team call. To help, I'll try to make a slide/diagram to illustrate the proposed reference forecast procedure in order to aide the discussion.

FYI I got delayed on working on this, but I'll be able to make progress before Monday.

FYI I'm working through this now following the discussion the other week re: starting with a week-ahead persistence forecast to capture the day of the week trends in load.

@wholmgren Assuming the tests pass, this PR is ready for review.

@dplarson if I still understand the code I wrote correctly and I understand the intent here, I believe the persistence_dayofweek function might not be needed at this time. Instead, you'd want to focus your efforts on the following function:
https://github.com/SolarArbiter/solarforecastarbiter-core/blob/142e41d2cfeba4e9651e130d51cb4a464144ebb9/solarforecastarbiter/reference_forecasts/main.py#L149-L162
main.run_persistence works with Forecast objects to formalize the calls to the lower level functions in the persistence module. The logic in the function relies on it only supporting intraday or day ahead forecasts. Maybe you'd want to add check functions like utils._is_dayahead and utils._is_weekahead to help the control flow but I'm not certain.
I believe the persistence forecast notebook in https://github.com/SolarArbiter/workshop should still work. At least it works in the mybinder link (see Readme badge) - cells 30-31 are most relevant.
This is all relevant because whatever net load reference forecasts we add to the dashboard are going to be driven by Forecast objects passed through main.run_persistence.

Yes, persistence_dayofweek() is just a wrapper around persistence_interval() and therefore is not 100% essential at this time. But I'm fine with omitting it as a separate function and instead modifying main.run_persistence() to support day of week persistence (using persistence_interval()). I'll work on that.

FYI I'm taking the approach of adding a kwarg to utils._intraday_start_end() and utils._dayahead_start_end() to switch between match the data by day of the week, where the kwarg will be set automatically based on the forecast.variable value.
Example: day-ahead forecast for Monday 4/20:

_dayahead_start_end(dayofweek=False): return data range of Sunday 4/19 (midnight-to-midnight)
_dayahead_start_end(dayofweek=True): return data range of Monday 4/13 (midnight-to-midnight)

@dplarson why a kwarg instead of a new function?

why a kwarg instead of a new function?

@wholmgren That was something I wasn't 100% sure about. Either way is feasible, but I thought it would be "cleaner" to add a kwarg to both _intraday_start_end() and _dayahead_start_end() instead of adding two additional functions for dayofweek (one for dayofweek intra-day and one for dayofweek day-ahead). With a kwarg, get_data_start_end() could then look like this:
# whether to factor in the day of week
if forecast.variable in ["load"]:
    dayofweek = True
else:
    dayofweek = False

if _is_intraday(forecast):
    data_start, data_end = _intraday_start_end(
        observation, forecast, run_time, dayofweek=dayofweek)
else:
    data_start, data_end = _dayahead_start_end(
        run_time, dayofweek=dayofweek)

But I'm open to suggestions.

Oh, but I could also just make a single function for dayofweek data ranges (regardless of whether intra-day or day-ahead horizons).

Hm I don't think we're on the same page... I thought we were talking about taking obs from from Monday April 20 and making it the forecast for Monday April 27. In our framework that's a 7 day ahead horizon with a 24 hour run length (issue frequency). So I don't see where the intraday concept comes in here.

Hm I don't think we're on the same page... I thought we were talking about taking obs from from Monday April 20 and making it the forecast for Monday April 27. In our framework that's a 7 day ahead horizon with a 24 hour run length (issue frequency). So I don't see where the intraday concept comes in here.

I understand what you're suggesting and that is fine with me.
To clarifying my comments: originally I was thinking that for load forecasts of any run length (24 hours, 1 hour, 5 hours, etc.), the dayofweek persistence would use obs from 7 days prior to the forecast_start-forecast_end range. Example:

at 10:00 Monday 4/20, forecast load for 12:00–15:00 Monday 4/20: use obs from 12:00–15:00 Monday 4/13
at 19:00 Sunday 4/19, forecast load for Monday 4/20 (midnight-to-midnight): use obs from Monday 4/13 (midnight-to-midnight)

But if you're fine with keeping it as a 7 day ahead horizon with a 24-hour run length, then I'll implement it as that.

Thanks, that helps a lot. I guess I'm not sure what the right answer is. I like the flexibility you describe.
What would you do in this case:

at 10:00 Monday 4/13, forecast load for Monday 4/20 (midnight-to-midnight)

Also hopefully it's clear from the comments in the code, especially the utils code, that I was not thrilled with the implementation. So improvements are welcome.

at 10:00 Monday 4/13, forecast load for Monday 4/20 (midnight-to-midnight)

This brings up a good point. In my mind, we should (eventually) move towards adding a persistence-type reference method that keeps a running estimate of "typical" load values (as a function of time of day and day of week or weekday/weekend) and then forward-fill using the most recent estimate. So in the example you listed, the Monday 4/20 (midnight-to-midnight) forecast would use the most recent Monday data, which could be either a) a combination of Monday 4/13 before 10:00 and Monday 4/6 (midnight-to-midnight) data, b) only Monday 4/6 (midnight-to-midnight) or c) a rolling window (e.g. all Mondays from the past 4 weeks).
With that said, my main thoughts are as follows:

in this PR, we only add support for the week-ahead persistence based on the persistence_interval() function
after this PR is merged, we move onto a more sophisticated persistence that incorporates day-of-week trends (e.g. a rolling estimate of "typical" values as a function of time of day and day of week, where the persistence uses the most recent estimate whether that is from 1 week ago or multiple weeks ago)

@wholmgren This PR now implements week-ahead persistence, which is run by main.run_persistence() instead of day-ahead persistence when the forecast variable is load.
If that's fine with you, please review. If not, then let's schedule a call early next week (Monday, Tuesday or Wednesday) to discuss.

Let's wait on merging this until beta5 is released on Monday. I'm not certain the changes to ALLOWED_VARIABLES won't propagate into some corner of the API or dashboard where it's not yet fully supported. And we're already struggling with bugs in beta5 testing so I don't want another feature to test at the last minute.

That makes sense to me. In the meantime, I'll address your other comments on the code.

@dplarson looks like a good first step to me. The whatsnew changes should now go to the rc1 file.
@alorenzo175?

I rebased against master and moved the whatsnew changes to the rc1 file.

thanks @dplarson !

authors: dplarson wholmgren

repo: SolarArbiter/solarforecastarbiter-core

license: MIT


text:
⚠ SolarOscp has degraded performance

In 149d68e, SolarOscp ($SOLAROSCP_URL) experienced degraded performance:

HTTP code: 200
Response time: 321 ms

Resolved: SolarOscp performance has improved in cb4abd4 after 9 minutes.

source: gharchive/issue

repo: SolarNetworkFoundation/upptime


text:
Fix & break up the test for Part 01 Step 17

From j1939-84 created by mmschaefer: SolidDesignNet/j1939-84#43
Unit tests for Part 01 Step 17 need to broken down to one error per test and the test need to be update to cover all lines of code.  Verification to the latest version of the spec (issued 6/24/2021) is also included here.

[x] Break up test
[x] Added additional tests
[x] Verified to latest version issued June 24, 2021 Specification


text:
Dynamically loading panes

Responding to the README:

And so we hope we will end up with panes dynamically laoded according to user configuration preferences.

I thought I'd describe what I currently do and what I'm still missing.
A pane needs to be defined and registered using JS, so I have a index.html file that provides a custom pane sitting in my pod. When I navigate to it within solidos, it gets rendered in an IFrame.
Within that file, I call
parent.panes.register(p)

Or so that it becomes the default pane for that session:
parent.panes.list.unshift(p)
parent.panes["myPaneName"]=p

The latter is a workaround because register always adds panes in order of decreasing preference, so a user-defined pane will never be default
I currently have to specifically navigate to index.html within solidos. Pasting the URL straight into the location bar doesn't load solidos, and navigating to the folder loads solidos but not index.html. https://github.com/SolidOS/solidos/issues/196 would change the latter, i.e. the pane registration code would run automatically when navigating to the folder
In some use cases, I don't need the pane to be always available - it would be ok for it to be registered only when navigating to a folder. For other use cases, it would be useful if the pane was automatically loaded from my preferences file (perhaps lazily the first time the relevant class is encountered). Presumably this would be just JS rather than an index.html, though maybe it could be an entire custom component.
I do see there are security issues with executing arbitrary JS that has access to the entire parent solidos environment. I only have html files I have written in my pod at this time.

Despite the limitations above I find it very useful to be able to change a custom pane on the fly rather than having to recompile and without adding it to the mashlib bundle.

@josephguillaume can you give the index.html link or content?

Here's an example:
https://josephguillaume.solidcommunity.net/public/index.html
It creates a pane with a link to open the resource in an external window with Penny.
I have other examples that have hard-coded paths/vocabs and would need work before being able to shared.
I've been using an older mashlib on my own pod. As it turns out, the latest behaviour on solidcommunity.net is a bit different.
Opening the link directly to both the path and folder just return the html (not solidos), and the registration therefore doesn't work in that context. It looks like dokieli is already the default handler for a folder with an index.html too.
The pane does get registered as intended when navigating within solidos to the folder or index.html page.
Here's an entry point into solidos to be able to see the behaviour
https://josephguillaume.solidcommunity.net/public/index.ttl

authors: bourgeoa josephguillaume

repo: SolidOS/pane-registry


text:
wont load model

🔍 Issue Description
export my yft.xml file go to blender import into it loads in 6 ish seconds and nothing is there tried many models and same outcome blender 4.2.3 and newest release of sollumz
🛠 Sollumz Version(s)
2.5.0
🖥 Blender Version(s)
4.2.3
🧩 Area
Fragments
🔄 Reproduction steps
anytime i try to import
🎯 Expected Result
help figuring it out
⚠ Current Result
just wont work
📎 Attachments
nothing shows

do you have import as asset enabled?

repo: Sollumz/Sollumz


text:
[Suggestion] Creative Energy Storage

As the name suggest, it would be nice to have a creative energy storage that makes a network essentially have infinite energy buffer and removes and a network can transfer (sometimes when you have so much energy being drained from the network it will stop transferring all together)

I can add infinite energy feature. Currently, you can shift click a Flux Storage with Admin Configuration to fill it up.
I'm not quite sure under what circumstances the transfer stop you mentioned will occur, but flux networks have no transfer limit.

authors: BloCamLimb iMeltedConsumer

repo: SonarSonic/Flux-Networks


text:
AWS IAM Role to connect to RDS Postgress

Is there a way we can connect Sonarqube to RDS Postgres using AWS IAM Role using helm chart values?

Hi @govindarajvenkatesan ,
if i read and understand you correctly you want to use a AWS IAM role token to connect sonarqube to a RDS database and yes that should be possible if you provide your token [1] as a jdbc password. The jdbc overwrite section should help you here.
Please note that the creation of the token and general surrounding setup like secret rotation etc can not be handled by the chart.

@tobias-trabelsi-sonarsource  Yes we are looking to use IAM role to connect to DB instead of using password
"arn:aws:iam::<account>:role/rds-access-sandbox_sonarqube",

So as per your comment above we can pass above ARN in jdbcPassword?

No you will need to provide a auth token as the jdbcPassword

@tobias-trabelsi-sonarsource  Sure. Let me check on the same.
Also when we tried to pass the override values to helm chart install, the chart seems to be picking up the default value. Can you guide what would be the right override settings to connect to Postgres DB?
gvenkatesan@WLUD21B20:/mnt/c/Users/106466/Scripts$ aws-vault exec 'gvenkatesan' -- helm get values sonarqube -n sonarqube
USER-SUPPLIED VALUES:
jdbcOverwrite:
  enable: false
  sonar.jdbc.password: <>
  sonar.jdbc.url: jdbc:postgresql://postgres-devxyz.us-east-1.rds.amazonaws.com/db_sandbox_sonarqube
  sonar.jdbc.username: admin

 #kubectl exec -it sonarqube-sonarqube-0 -n sonarqube -- env | grep jdbc
SONAR_JDBC_URL=jdbc:postgresql://sonarqube-postgresql:5432/sonarDB
gvenkatesan@WLUD21B20:/mnt/c/Users/106466/Scripts$

see the little jdbcOverwrite.enable flag there? you need to explicitly enable the jdbc overwrite and disable the postgresql that is shipped as a dependency of this chart

@tobias-trabelsi-sonarsource
This is how we are generating the db auth token using IAM role. What would be the best way to use this in helm chart? Please suggest. Thanks.
"export PGPASSWORD=$(aws rds generate-db-auth-token --hostname postgres-dev.xxx.us-east-1.rds.amazonaws.com --port 5432 --region us-east-1 --username db_sandbox_sonarqube")

this is a very philosophical question that i can not really answer.
if you are managing secrets in your cluster already it might be a good idea to continue with that and reference it using jdbcOverwrite.jdbcSecretName. If this is a long living token and you just want to deploy SQ, you can set this token in jdbcOverwrite.jdbcPassword and it will be picked up.
Whenever you are rotating this token you will need to adjust both of them. If there is a secret provider in your cluster already doing this for you it might be better to use this one. if you are doing this all manually, then it does not matter and will be a manual operation anyway.

@tobias-trabelsi-sonarsource  Does it supports an annotation like a snippet below
apiVersion: v1
kind: ServiceAccount
metadata:
  name: apitoken-server
  annotations:
    eks.amazonaws.com/role-arn: "arn:aws:iam::<account>:role/rds-access-sandbox_sonarqube"

We provision Postgres using IAM Roles for Service Accounts (IRSA)  and we wanted to make use of this to connect from sonarqube to Postgres.

okay i thought i already clarified that you need to provide something that can work with the default jdbc driver for postgresql. there is no additional logic provided by this chart or sonarqube that would allow you to rotate or inject something specific to AWS.
you can use token auth as explained before to authenticate against database and you will need to provide the credentials as jdbc username / password. how you do this is up to you

@tobias-trabelsi-sonarsource  Was looking something like this --> https://github.com/SonarSource/helm-chart-sonarqube/blob/master/charts/sonarqube/values.yaml#L459
Is there any examples that SonarQube repo has?

nope

@tobias-trabelsi-sonarsource  I have the below in upstream/values.yaml
  image:
    pullPolicy: "Always"
    tag: 9.2.4-community
  postgresql:
    enabled: false
  sonarProperties:
    sonar.core.serverBaseURL: "https://sonar-sandbox.dev.com"
    sonar.search.javaAdditionalOpts: "-Dlog4j2.formatMsgNoLookups=true"
  jdbcOverwrite:
    enable: true
    jdbcUrl: "jdbc:postgresql://postgres-dev.xyz.us-east-1.rds.amazonaws.com/sandbox_sonarqube?socketTimeout=1500"
    jdbcUsername: xyzr"
    jdbcSecretName: "sonarqube-jdbc"
    jdbcSecretPasswordKey: "jdbc-password"
    ```

    While trying to locally render the template; don't see the  jdbcOverwrite values getting populated in the upstream.yaml. It's still getting all the default values. Thoughts?

    ```
    helm dependency update upstream
    helm template sonarqube upstream > resources/upstream.yaml

it seems like you are not referencing the values you provided. If i take your values and save them as test.yaml for example i can see that they are correctly propagated to the chart with
helm template -s templates/jdbc-config.yaml -f test.yaml sonarqube/sonarqube

=>
---
# Source: sonarqube/templates/jdbc-config.yaml
apiVersion: v1
kind: ConfigMap
metadata:
  name: release-name-sonarqube-jdbc-config
  labels:
    app: sonarqube
    chart: sonarqube-1.2.5_179
    release: release-name
    heritage: Helm
data:
  SONAR_JDBC_USERNAME: "xyzr"
  SONAR_JDBC_URL: "jdbc:postgresql://postgres-dev.xyz.us-east-1.rds.amazonaws.com/sandbox_sonarqube?socketTimeout=1500"

@tobias-trabelsi-sonarsource  So we have values.yaml under the folder upstream>values.yaml
The update-upstream.sh script pulls down the SonarQube helm chart, and templates it out to the resources/upstream.yaml file.
#!/usr/bin/env sh

helm dependency update upstream
helm template sonarqube upstream > resources/upstream.yaml

So how can we get all the templates and populate with overrides in values.yaml without passing those -f values.yaml file?

what about
helm template -f upstream/values.yaml sonarqube upstream > resources/upstream.yaml

if this is not an option, you can try to tinker around with -set as documented here.
on a side-note: ArgoCD can work with helm repositories directly. There is no need for this kind of scripting. a Chart.yaml that references the original helm chart and correctly scoped values are enough:
Chart.yaml
apiVersion: v2
name: sonarqube
description: sonarqube
type: application

version: 0.1.0
appVersion: "9.2.4"

dependencies:
- name: sonarqube
  version: "1.2.5_179"
  repository: https://SonarSource.github.io/helm-chart-sonarqube

values.yaml
sonarqube:
  image:
    pullPolicy: "Always"
    tag: 9.2.4-community
  postgresql:
    enabled: false
  sonarProperties:
    sonar.core.serverBaseURL: "https://sonar-sandbox.dev.com"
    sonar.search.javaAdditionalOpts: "-Dlog4j2.formatMsgNoLookups=true"
  jdbcOverwrite:
    enable: true
    jdbcUrl: "jdbc:postgresql://postgres-dev.xyz.us-east-1.rds.amazonaws.com/sandbox_sonarqube?socketTimeout=1500"
    jdbcUsername: "xyzr"
    jdbcSecretName: "sonarqube-jdbc"
    jdbcSecretPasswordKey: "jdbc-password"

@tobias-trabelsi-sonarsource Tried that as well; but still getting the default templates getting rendered.

Uhm this is not the chart in this repo. what repo do you have configured for upstream. could it be the one from oteemo by any chance?

@tobias-trabelsi-sonarsource Here is the Chart.yaml file values

the version you specify there is not known. can you give me the exact version of the chart you are using? we never released a chart with the chart version 9.2.4
latest sonarqube chart as of now is version 1.2.5+179

@tobias-trabelsi-sonarsource Made this change and see the below

Okay this is looking like the right chart now at least. Still the values that you showed me are not picked up, so i guess there is still a scoping issue. did you already try to set the values in the correct scope (might be sonarqube or sonarqube-upstream... i am a bit confused by this kind of setup)?

@tobias-trabelsi-sonarsource  How do we disable this pod? What values should we be passing to disable this? Thanks
https://github.com/SonarSource/helm-chart-sonarqube/blob/master/charts/sonarqube/templates/tests/sonarqube-test.yaml#L1

@tobias-trabelsi-sonarsource  NM. Found it --> https://github.com/SonarSource/helm-chart-sonarqube/blob/master/charts/sonarqube/values.yaml#L451. THanks

@tobias-trabelsi-sonarsource What would be the stable docker taag that we can for 9.2.4? Will this be right?
tag: 9.2.4

@tobias-trabelsi-sonarsource  Where can we find the release notes for 9.2.4? --> https://github.com/SonarSource/docker-sonarqube/releases/tag/9.2.4

@tobias-trabelsi-sonarsource  Also can you let us know what is this used for - SONAR_WEB_SYSTEMPASSCODE ?
Is this needed and anyway we can securely store this password?
---
# Source: sonarqube-upstream/charts/sonarqube/templates/secret.yaml
---
apiVersion: v1
kind: Secret
metadata:
  name: sonarqube-sonarqube-monitoring-passcode
  labels:
    app: sonarqube
    chart: sonarqube-1.2.5_179
    release: sonarqube
    heritage: Helm
type: Opaque
data:
  SONAR_WEB_SYSTEMPASSCODE: "xxxxx"

@govindarajvenkatesan you can find the release notes in their respected posts here.
The SONAR_WEB_SYSTEMPASSCODE is used for the liveness probe as well as for monitoring purposes. It is mandatory in this helm chart and can not be externalized

@tobias-trabelsi-sonarsource Thanks. Anyway we can securely use SONAR_WEB_SYSTEMPASSCODE similar to jdbcSecretPasswordKey?

Sadly not yet. There were ideas to do that but they did not work out

Thanks @tobias-trabelsi-sonarsource

repo: SonarSource/helm-chart-sonarqube


text:
Horizon v2.31.0 and RPC v21.4.0 changes

Please add support to your SDK for the following API changes.
Horizon Changes
Horizon v2.31.0 made the following changes:

New endpoint: POST /transactions_async allows asynchronous transaction submission (code: stellar/go#5188).
Error schema change: POST /transactions now includes a the hash in its timeout response, which may or may not require code changes depending on how your SDK handles transaction submission errors (code: stellar/go#5328).

Soroban RPC Changes
RPC v21.4.0 added the following endpoints:

getTransactions, which returns pages of transaction details (code: stellar/soroban-rpc#174).
getFeeStats, which returns aggregated fee statistics over a few ledgers (code: stellar/soroban-rpc#172).
getVersionInfo, which returns detailed information about the software versions the RPC server is running (code: stellar/soroban-rpc#132). Please keep in mind that this endpoint accidentally used snake_case for response fields and it will be updated to camelCase (see soroban-rpc#164) as part of Protocol 22's breaking changes when the time comes.

Reference

RPC documentation for getFeeStats.
RPC documentation for getTransactions.
RPC documentation for getVersionInfo.
Horizon documentation for /async_transactions.
JavaScript implementations: stellar-sdk#989 (/transactions_async) and stellar-sdk#1006 (/getFeeStats), both included in v12.2.0.

Hello @Shaptic,
thank you for adding this issue. It has been resolved in release 2.6.4.

authors: Shaptic christian-rogobete

repo: Soneso/stellar-ios-mac-sdk


text:
Agent Training, Music and Sound Effects, Bug Fixes

This branch consists of the logic needed to train the agents with the mlagents-learn Python tool. It includes some trained neural network models for the player and alien agents to use. I added the main menu and first stage music to not make the game have no sound. The aliens can now play a death sound effect. Lastly, I made a lot of bug fixes including where if the player dies and still got rid of all of the aliens, the player can proceed to the next stage.

 Once the training is over, implement to switch models in between stages.

repo: SonicKurt/Galaga-AI


text:
Endwalker OST is out

Opening this as an issue such that Upgrade Music Quality can be updated to reflect this

Yeah, I'm still waiting for my delivery. Will be done once I receive it.

Try this. https://github.com/Soreepeong/XivAlexander/blob/main/StaticData/MusicImportConfig/Endwalker.json

Doesn't work. I tried it out with both ffmpeg from 2022-03-21 and stable 5.0 just in case, but I got the same errors.
Tried importing both decrypted m2ts files (used MakeMKV) and also the MP3 files from the disc, error logs from both are attached below. Source files work in media players just fine.
mp3_import.txt
m2ts_import.txt

authors: Sergster1 Soreepeong TheNikomo

repo: Soreepeong/XivAlexander


text:
Can't see the patch 7.05 raid (savage) boss cast bar and debuff description

I'm using "JapaneseWithEnglish_SayQuest Japanese", and the skill name of the boss is displayed well on the 1st to 3rd floors, but from the 4th floor, I can't see the skill name of the boss, such as 'narrow witch hunt,, witch hunting, witchgleam'. There is nothing written on the casting bar.. The debuff description window only shows - and nothing is written.

7.05신규 레이드 영식레이드에서 1에서3층까진 보스가 뭘캐스팅 하는지 스킬이름이 보이는데 4층 부터는 보스가 무슨 공격을 쓰는지 캐스팅바에 아무것도 안적혀있고 텅 비어있어요 디버프창 설명에도 아무것도 안뜨고 ‘-‘라고만 적혀있어요

I've not been able to figure out any solution for this unfortunately. I've tried changing the backup language and adding other root directories for the game files. In the logs, the move names and "add" names don't appear either. Weird that this is the only fight this isn't working for


text:
fix(ffe-form-react): remove checkbox props

BREAKING CHANGE:
Instead of having an innerRef prop, use the more modern
approach with React.forwardRef. This means that instead
of using the innerRef prop, refs should be passed as
they would to any other React element.
- <Checkbox innerRef={ref} />
+ <Checkbox ref={ref} />

While we're doing breaking changes anyway, removed
support from the two deprecated props label and
valid. Use children and aria-invalid instead.
- <Checkbox invalid={true} label="To arr is pirate" />
+ <Checkbox aria-invalid={true}>To arr is pirate</Checkbox>

Sure, I'll take a look. I thought I ran them locally but it's possible I forgot 🦡

Oh, clearly I didn't run them 😂

Coverage remained the same at 84.797% when pulling 9e6b39b4172b09a5f62ea20727240efaffb6c248 on ivarni:use-forwardref into 21daff832228108aaf2db3922378efda045a89fd on SpareBank1:develop.

authors: coveralls ivarni


text:
🛑 Yiffed Main is down

In 04b276d, Yiffed Main (https://yiffed.net/) was down:

HTTP code: 526
Response time: 207 ms

Resolved: Yiffed Main is back up in 90d315c after 15 minutes.

repo: SparksTheFolf/STF-Uptime-Status


text:
[BUG] Failed to launch the browser process

"Failed to launch the browser process!\n/var/folders/ss/tlgf043d2_d50b22hy4r0tk40000gn/T/chromium: /var/folders/ss/tlgf043d2_d50b22hy4r0tk40000gn/T/chromium: cannot execute binary file\n\n\nTROUBLESHOOTING: https://pptr.dev/troubleshooting\n"
Version
"@sparticuz/chromium": "^109.0.6",
"puppeteer": "^19.7.5",
"puppeteer-core": "^19.7.5",
import chromium from '@sparticuz/chromium';
import log from 'lambda-log';
import puppeteer, { Browser, Page } from 'puppeteer-core';

export class WebSiteParserBase {
  protected pageTimeout: number;

  constructor(pageTimeout: number | null = null) {
    this.pageTimeout = pageTimeout ?? 180000;
  }

  protected async launchBrowser(headless?: boolean): Promise<Browser> {
    try {
      return await puppeteer.launch({
        args: chromium.args,
        defaultViewport: chromium.defaultViewport,
        executablePath: await chromium.executablePath(),
        headless: headless ?? chromium.headless,
        ignoreHTTPSErrors: true,
      });
    } catch (error) {
      error.reason = 'Unable to start browser';
      log.error(error);
    }
  }

  protected async goToPage(sourceUrl: string, browser: Browser): Promise<Page> {
    const page = await browser.newPage();
    await page.goto(sourceUrl, {
      timeout: this.pageTimeout,
      waitUntil: ['load', 'networkidle0', 'networkidle2'],
    });

    return page;
  }
}

Just ran into this as well while trying to get my project running locally with serverless-offline on my M1 Macbook. Are you trying to get it running on an ARM environment by any chance? According to #19 that's not support by this package yet.

Probably related, but I've been trying to get around this via docker https://github.com/Sparticuz/chromium/issues/70 and setting the --platform linux/x86_64
The only alternative that has been successful for me is to use the locally installed chromium path. In this case I am using playwright:
const executablePath = process.env.ENV === 'local'
      ? playwright.chromium.executablePath()
      : await chromium.executablePath();

This issue is a direct copy of https://github.com/Sparticuz/chromium/issues/42  as well so you can likely close this out and comment over there instead with ideas.

Hi  @AgniaStaravoitava I faced similar issues, but it was mostly due to version incompatibility. I have documented my ways to debug. Hope it helps!
https://adapttive.com/blog/serverless-scraping#how-to-debug

So this lib is a no-go for local testing if you have an M1/2 Mac?

@alexcroox You can just use local chrome for testing.
set process.env.IS_LOCAL = something, and try something like this:
await puppeteer.launch({
  args: process.env.IS_LOCAL ? undefined : chromium.args,
  defaultViewport: chromium.defaultViewport,
  executablePath: process.env.IS_LOCAL ? '/path/to/Chromium' : await chromium.executablePath(),
  headless: process.env.IS_LOCAL ? false : chromium.headless,
});

Hey @Sparticuz shouldn't it work locally for mac? I mean your previous package worked and so does puppeteer. I don't want to use my local Chrome as it reduces my confidence in my local env testing.
Is there a chance this is fixable?

Workaround on mac in case anyone is still stuck
brew install chromium --no-quarantine

// index.js
await puppeteer.launch(
  executablePath: process.env.IS_LOCAL ? '/opt/homebrew/bin/chromium' : await chromium.executablePath(),
  // ...
});

IS_LOCAL=true node index.mjs

Here's a workaround I found if using with AWS SAM with M1 Macs:

Set container architecture to "amd64".
Set experimental Rosetta emulation on Apple Silicon in Docker settings. This is needed to avoid a segmentation fault bug when emulating with qemu (https://github.com/docker/for-mac/issues/6204)

@conrad-scherb Thank you! That worked perfectly for me.

Thank you so much @wickedst , you saved my life 🙏

authors: AgniaStaravoitava Myztiq Sparticuz alexcroox ccmetz choijun conrad-scherb hasan-wajahat janvennemann milindsingh wickedst

repo: Sparticuz/chromium


text:
Task - simple new specimen

   after I have completed adding the information for an identifier
      then as soon as the input loses focus
         that identifier is highlighted as duplicate
            if it is in fact duplicate

Consider similar functionality for all identifier creation.

Function exists in comprehensive digitization.

repo: SpeciesFileGroup/taxonworks


text:
How to mount a json file to hoverfly docker container

I want to use "sudo docker run -it -p 8888:8888 -p 8500:8500 -v simulation.json:xxxxx spectolabs/hoverfly:latest" to mount a exist json file ,This file is made by "hoverctl" ,I want to mount this file to hoverfly container when it start .but can not find the mount path in container . Or this is the wrong way to do this issue ? when i want to get response by url ,and  the simulation json contain the matcher ,but  the response was
Hoverfly Error!
There was an error when matching
Got error: Could not find a match for request, create or record a valid matcher first!
It seems my json file do not mount to the container successfully.

This is the full url request
curl  -k --proxy http://localhost:8500 -H "Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE1NDE3NTA3NzIsImlhdCI6MTU0MTc0NzE3MiwiaXNzIjoiSGl0cm9uIiwic2NvcGUiOlsidHIxZDF1bSIsImRldmJpbmQiXSwidXNlcl9pZCI6ImdpdGh1YjozMjY2ODUxNSJ9.vn_XB-ZRo2qyu0iyq_Oidc7PLMnZg55upj_h1FUUKMSEG2fqgXqWH65ZANJZSmviN-4e57k2IGeVMfTIvq_hckOWFgGmbYNdFcSHJ8__-YstEe33VZ4o7MZswc5uuBetS56xxz_JCRwxZJYKR-ItJIEvmdapRDav0ochJ6Ft8uMGd9SS8kDM7fb_obrPWakEk8xFKyNSaXUoD_RZDjkIw-nWJ0ga8C1ESS4wp0jh6oCas8EaWbj8k0EDMGQSsp8jf-GiYcH_rgtU9wP8RSoRxQQqGQOiAAe0x1bx30q63FcCdy4oqJQ6fblRrLQoaISTsGebJ1GoJ2H4iqiyNmldrCjcpePTXf9RTc2H0R0dtjZPl0Cd7YsT9uzh1U5ZDA692EZwgI1AxCwsWtA-wqbiVFc4pY3VVOx64yGOp4dtcHpYQVVVlV0re9xHO2Ww-fI1ocmUyTAvJvgT4HkosY5TDG1hq-aQ5RhNA5tlYeHGzqEDMVMO3JqGe6bKnkYbnWgIydZWl_M-Ll6s_V8U-9ZIV6gJhJ8uL4mjxdYg0vG5MJurtn5iZs9U_XUfsrDXCOeIEjBFCwMYhg_tn9GxiJtMjEGhhcGKqUpEW6QPQKwSuyAaHodaeeWgWc1k-PsAkgAhugUOFaKst5ev9n5mu8UFDLk7vRG7uVq5naeodKPUFgw" -H "apikey: vRlXrdcLcME6yWtZKG6ug5BpC6vYmCCr" http://172.17.0.2:8888/api/v1/jwt/validate
Hoverfly Error!
There was an error when matching

and i can get the test url get from hoverfly
hun@hun16:~/hoverfly$ curl  -k -H "Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE1NDE3NTA3NzIsImlhdCI6MTU0MTc0NzE3MiwiaXNzIjoiSGl0cm9uIiwic2NvcGUiOlsidHIxZDF1bSIsImRldmJpbmQiXSwidXNlcl9pZCI6ImdpdGh1YjozMjY2ODUxNSJ9.vn_XB-ZRo2qyu0iyq_Oidc7PLMnZg55upj_h1FUUKMSEG2fqgXqWH65ZANJZSmviN-4e57k2IGeVMfTIvq_hckOWFgGmbYNdFcSHJ8__-YstEe33VZ4o7MZswc5uuBetS56xxz_JCRwxZJYKR-ItJIEvmdapRDav0ochJ6Ft8uMGd9SS8kDM7fb_obrPWakEk8xFKyNSaXUoD_RZDjkIw-nWJ0ga8C1ESS4wp0jh6oCas8EaWbj8k0EDMGQSsp8jf-GiYcH_rgtU9wP8RSoRxQQqGQOiAAe0x1bx30q63FcCdy4oqJQ6fblRrLQoaISTsGebJ1GoJ2H4iqiyNmldrCjcpePTXf9RTc2H0R0dtjZPl0Cd7YsT9uzh1U5ZDA692EZwgI1AxCwsWtA-wqbiVFc4pY3VVOx64yGOp4dtcHpYQVVVlV0re9xHO2Ww-fI1ocmUyTAvJvgT4HkosY5TDG1hq-aQ5RhNA5tlYeHGzqEDMVMO3JqGe6bKnkYbnWgIydZWl_M-Ll6s_V8U-9ZIV6gJhJ8uL4mjxdYg0vG5MJurtn5iZs9U_XUfsrDXCOeIEjBFCwMYhg_tn9GxiJtMjEGhhcGKqUpEW6QPQKwSuyAaHodaeeWgWc1k-PsAkgAhugUOFaKst5ev9n5mu8UFDLk7vRG7uVq5naeodKPUFgw" -H "apikey: vRlXrdcLcME6yWtZKG6ug5BpC6vYmCCr" http://172.17.0.2:8888/api/v2/simulation
{"data":{"pairs":[],"globalActions":{"delays":[]}},"meta":{"schemaVersion":"v5","hoverflyVersion":"v0.17.7","timeExported":"2018-11-20T03:12:26Z"}}

You just need to add the import argument to import from the mounted file:
" sudo docker run -it -p 8888:8888 -p 8500:8500 -v {full path to the simulation file}:/var/hoverfly/simulation.json  spectolabs/hoverfly:latest -import /var/hoverfly/simulation.json"
In fact you can use all the flags available for hoverfly (see hoverfly --help) when you start the hoverfly container.

thank you ,it resolve my problem .closed.

repo: SpectoLabs/hoverfly

license_source: bigquery


text:
Added ProxyFromEnvironment configuration option

This should allow auto proxy configuration based off of http_proxy/https_proxy and no_proxy environment variables, referenced in issue #373

Hey @Bruno-DaSilva,
The common usage of Hoverfly is set the HTTP_PROXY and HTTPS_PROXY environment variables to the address of Hoverfly.  This is something suggested to users in our documentation as well as being something our functional tests do.
As a result of this, this breaks functional tests by causing a proxying loop when the HTTP_PROXY and HTTPS_PROXY variables are set to Hoverfly.
There are two possible solutions to this.
The first is to implement some kind of check to make sure that those variables are not set to point to Hoverfly before setting the default HTTP client's proxy settings.
The second is to have proxy as a startup flag on the Hoverfly binary core/hoverfly/cmd/main.go which is then passed through GetNewHoverfly() and into GetDefaultHoverflyHTTPClient(). This startup flag could then be added to Hoverctl, providing the same functionality as this change, but more as a configuration.
I think the second option is more work, but it makes sense. If you are running behind a proxy but you wanted to put Hoverfly infront of that, you should be setting HTTP_PROXY and HTTPS_PROXY to Hoverfly and then telling Hoverfly that their is a proxy between itself and its intended destination.
I'm interested to hear your thoughts.
I'm interested to hear your opinion

Hey @benjih, you certainly bring up an excellent point. I've been looking at this from my own perspective only, where we use docker containers to isolate our services (and so there would not be conflicts with environment variables). You are right, though, that this does pose a problem for the larger user base and the solution I've offered thus far would potentially mean more work/confusion for them.
With regards to your first solution, while it could work, I do see a rather large problem with it. How does hoverfly know that the HTTP_PROXY env variable is pointing to itself? Does it send an http request to whatever it is set to in order to verify if it is actually pointing to a hoverfly instance? What happens if you're trying to chain multiple hoverflys together (it's a rather edge case circumstance but it could happen), how would you know that the hoverfly you get a response back is yourself?
The second option, however, is much more explicit and less brittle in my opinion. You will avoid the 'autodetection' issue entirely, and give users full control of having a proxy setting enabled or disabled. There are two ways to do this in my opinion:

have simply a true/false flag as an option which just takes from the env variables
have an explicit setting somewhere (command line/config file; proxy_host: test.host.proxy.com, proxy_port: 443). It would require more implementation but would allow users to be explicit with their proxy settings without having to set or change an environment variable.

Now, I think the second option is without a doubt the best solution of the two. My only question is which way to go (true/false vs explicit config) do you think is the better solution? I can take a crack at whichever you think is best.

I think having it as an explicit option would be best and then have main.go pass it through on construction of a new Hoverfly instance via the config. Putting the proxy address in config seems appropriate to me.

Oh perfect, implementing that in hoverctl would have been my next question. I'll get on that :)

Hey @benjih, I've made the changes and updated the pull request (it's a super small change).
I'm new to golang so I'm sure there's some conventions I'm breaking. I'm open to any feedback as to what is missing/should be changed.

Just had a looking at the pull request and its looking great!
I spoke to a few of the people here and we had a bit of a debate as to whether or not the external-proxy flag was clear enough. Someone mentioned that it might cause some confusion as external could have several meanings depending on the situation.
An idea was suggested to rename it to upstream-proxy as this was a bit cleare. If you configure a second proxy in a chain of proxies, you can only link them by configuring a proxy with an upstream proxy location.
I'm interested to hear your thoughts in the matter.
Other than that, all good. I await your response and any changes required and then I will merge this in.
Thank you very much @Bruno-DaSilva.

@benjih Thanks for taking a look so fast. You're definitely right that it's not clear enough, I was struggling to find a succinct flag to describe what it actually did. upstream-proxy sounds much better, I'll make that change.

authors: Bruno-DaSilva benjih


text:
Urgent Help Aggregating

I am trying to use this aggregator, but i am getting the error
  File "aggregator.py", line 31, in extract
    assert len(set(all_keys)) == 1, "All runs need to have the same scalar keys. There are mismatches in {}".format(all_keys)
AssertionError: All runs need to have the same scalar keys. There are mismatches in []

my dir structure looks like this
ls ../results/
inference.run63++100  inference.run64  run61  run62  run63  run63++025  run63++050  run63++075  run63++100  run64  run64-inference  run64-nospeed  run64+vision  run65  run65-pure  run66  run67  run68  run68++050  run68++050-inference

I am trying to aggregate all my runs (which have many variables) into a single csv so I don't have to download each one manually and then aggregate it manually... picture example attached:

So i managed to get a script that merges the manually downloaded CSVs into a single csv, for anyone who would need something like this:
import pandas as pd
import glob
from run_name_getter import *

import matplotlib.pyplot as plt

files = glob.glob("movingForward/*.csv")

if len(files) == 0: raise BaseException("no files")

step_column = pd.read_csv(files[0], usecols=['Step'])

all_csvs = [pd.read_csv(p, usecols=['Value']) for p in files]

for i in range(len(all_csvs)):
    csv = all_csvs[i]
    run_name = get_run_name(files[i])
    csv.columns = [run_name]

metric_name = get_metric_name(files[0])

all_csvs = [step_column] + all_csvs

df = pd.concat(all_csvs, axis=1)

df.plot(x="Step", alpha=0.5, title=metric_name)
plt.show()

the only downside now is I have to manually download each CSV for each run for each metric.

repo: Spenhouet/tensorboard-aggregator


text:
World locked on first login

hi, the plugin looks great, excellent work!
I have a problem... when I log in with a new account and I receive the message "Your Account was generated." You cannot interact with the world, as if it were protected, this is solved by re-entering the server with the message "We loaded your Data, you can now play."
I don't know if this problem is due to natural behavior of the plugin, some interference with another plugin (although I tried removing all of them), or a user permissions problem.
I tried to follow the code, for example in the JoinListener.java class to see if there was something that would block entities but I did not find the problem
The plugin is configured with MongoDb
I am running it on paper 1.20.1

Hello there,
do which version of MySQL-Sync do you use?
~ leo

The same thing happened at our house.
It's not a problem when the server has just started up, but it seems to happen when (no one) has been logged in for a long time.
Re-logging in or moving the server again will cure the problem.
PaperMC 1.21 #40
Velocity #400
MariaDB V15.1
MySQL-Sync 1.4.14

After a number of attempts, we found that it is likely to be due to MySQL timeouts.
Reproduction methods include
You can check this immediately by setting MySQL's wait_timeout to 10 seconds.
Alternatively, restart MySQL and you can check it immediately in-game.

The same thing happened on our server.
It's not a problem when the server has just started up, but it seems to happen when (no one) has been logged in for a long time.
Re-logging in or moving the server again will cure the problem.
In the player's connection log when the phenomenon occurs.
[11:52:34 INFO]: [MySQL-Sync] §aConnected to the MySQL
This is speculation, but it may be related to reconnection after a DB server timeout or something like that.
After a number of attempts, we found that it is likely to be due to MySQL timeouts.
Reproduction methods include
You can check this immediately by setting MySQL's wait_timeout to 10 seconds.
Alternatively, restart MySQL and you can check it immediately in-game.
PaperMC 1.21 #40
Velocity 3.3.0 #400
MariaDB V15.1
MySQL-Sync 1.4.14

Can confirm that this happens all the time, and does confuse a lot of players.

Hello federkone, RuaWing and Hezkore,
thank you for messaging me about this problem. Now that I have more Informations about it, I will look deeper into the problem.
Will update you three as soon, as I have a update.
~ Leo

authors: Hezkore MoonLightRose RuaWing SphinxHD federkone

repo: SphinxHD/MySQL-Sync


text:
Can Nginx-Modsecurity surport senting logs to Syslog

i know that nginx can suport logging to syslog, and is there some way that can do this that sent to syslog except deploy a syslog-client to sent log.

@meigea as far as I can recall, you can tune your log entries to be written to Nginx error_log and being so, they could be logged to syslog by tuning Nginx to do it.
I don't think the audit_log / debug_logs have native support for sending it syslog. But you could use the HTTPS transport by setting the SecAuditLogType to "HTTPS" which allows sending the logs directly to a remote (or localhost) server without the usage of a log collector such as MLogC (2.x). See #1839.

@victorhora Thank you very much , i think you have helped me.

authors: meigea victorhora

repo: SpiderLabs/ModSecurity-nginx


text:
Compute Engine with Cloud SQL sample

This PR brings a new sample, which shows how to deploy a server to Google Compute Engine. The server uses a database within Google Cloud SQL.
Additionally, LocalClient was renamed to ClientApp. From now, the Gradle task for running the client allows to configure a hostname and port to establish a connection with the gRPC server.

@armiol PTAL.

repo: SpineEventEngine/todo-list


text:
MoveEntityEvent not fired for Projectiles and Items

I am currently running

SpongeForge version: 7.1.7-RC3881

SpongeVanilla version: 7.1.7-RC265

Java version: 1.8.0_162

Operating System: Windows 10

Plugin:

@Listener
public void onMoveEntity(MoveEntityEvent e, @Getter("getTargetEntity") Entity y) {
	TestPlugin.LOGGER.info("move: " + y.getType().getId());
}

Issue Description
MoveEntityEvent is not fired for Projectiles and Items. Probably caused by: https://github.com/SpongePowered/SpongeCommon/blob/b1638839846a2740e2e5a95f5fe8b7c77341ccd8/src/main/java/org/spongepowered/common/event/SpongeCommonEventFactory.java#L911

Removing the two instanceof checks seems to have no harmful side effects.
It was originally introduced by blood in https://github.com/SpongePowered/SpongeCommon/commit/0e3bc55efc07816a5360d0330d104ab532e507d4. @bloodmc Any particular reason for that?

I believe it originally was added because of how much spam would be caused by adding those move events. The events themselves are not costly to construct, but the amount of events being thrown on a large server and plugins processing them would exceed current expectations (picture a high density chest containing 200+ types of items dropping all 200+ item stacks as new entities, and each tick a new move event being thrown for each of them, and GP now processing them).

This is a good point, especially for items. I feel as though tracking an items movement isn't necessarily that important, but projectiles definitely have more use cases while being quite a lot more common.
I'm thinking we could for now at least enable the event for projectiles.
@Yeregorix What is your use case for tracking item entity movement?

I'm developing a custom region manager for a private server which need to detect when an entity enter or exit a region.
I understand the impact on performance but first, I think it's the responsibility of plugin developers to not do heavy things in this event. Secondly, the choice is a lot arbitrary. I can't understand it at all for Projectiles. I can understand it slightly for Items but it no longer make sense if you have another mod which add new entities way worse than Items.
I know it's not every day we need to listen for Items movements. A good compromise could be to make it configurable globally/per world, and disabled by default.

Duplicate of https://github.com/SpongePowered/SpongeCommon/issues/2004

authors: ImMorpheus JBYoshi Yeregorix gabizou parlough

repo: SpongePowered/SpongeCommon


text:
🛑 [A] IP Ending with .167 is down

In 2a0d163, [A] IP Ending with .167 ($IP_GRP_A.167:$MONITORING_PORT) was down:

HTTP code: 0
Response time: 0 ms

Resolved: [A] IP Ending with .167 is back up in 3703363 after 6 minutes.


text:
Implement processor for S1118: "Utility classes should not have public constructors"

We have quite a few violations of S1118 in Sorald, and I want to fix them. It's a trivial processor to implement, and so I think we should implement it even though it's a code smell and not a bug or security risk.

Very good idea. We also have some pending "BUG" violations on Spoon.

Very good idea. We also have some pending "BUG" violations on Spoon.

Yes! Most of them are hard or unsolvable with automatic repair, but I've found a few that we can fix with current as it is today :). Expect a few Sorald PRs in Spoon over the coming days.

authors: monperrus slarse

repo: SpoonLabs/sorald


text:
Added code files to local

Fixes Issue
Hi,
OM|PA-Animating Buttons
I have fixed the issue#1261
Kindly review the code.
I have added files to local and updated data,js.
Changes proposed

Screenshots

Checklist

[x] You've linked this PR to the correct issue.
[x] You have checked that the code is working correctly.
[x] You ⭐ the repository!

Note to reviewers

Please check #1346

Hi,
OM|PA-Animating Buttons,
I tried it yesterday but couldn't succeed to make a successful PR. U may see this in the closed Prs. It's my first attempt here in this open-source ...kindly review it.


text:
docs: add pull request template in markdown format

Closes #780
I have written detailed comments to ensure that anyone can easily understand the meaning.

@Spyware007
I am tagging you because merging this change would greatly facilitate the process for others.
I am not suggesting to merge the PR just for the sake of GSSoC'23; rather, I genuinely believe that implementing a proper PR template and issue form would streamline the overall workflow. It would not only make it easier for contributors but also assist you during the review process.

@Anmol-Baranwal Thank you so much!


text:
Bridge peripheral & Modem block

Implements #15

The bridge doesn't seem to call attach() on peripherals. It seems the issue about adding API for peripheral attachment handling might be important to add for this.

Hmmm, it should be called here. I'll test this now. :confused:

Would it be too crazy to try to isolate all calls to IPeripheral.attach() (including those in vanilla CC), and replace them with a different call to the theoretical PeripheralAttachmentRegistry proposed here? It would delegate to the registered handlers, one of which simply calls IPeripheral.attach()

Well, we've got a core mod, so it is feasible. #17 is next on my to do list, though I'm probably going to have to rewrite the entire API so we are shipping interfaces and not code as much as possible. Something like this

That's a good idea. For now, I'll branch and see how much I can do with the peripheral attachment registry idea.

Thanks, I'm still confused about #16, so if you could also do something with that, it would be great.

I've implemented a turtle upgrade for the wireless bridge using the methods bindToCard and bindFromCard. Currently it also wraps the turtle as a peripheral so you can remotely turn it on and off. I wish that we could wrap turtles as OpenPeripheral's IInventory peripheral instead, but no such luck.

Progress!

I'm not sure about having it as a peripheral now. I might revert support for it from the original bridge as well as otherwise behaviour is inconsistent. The issue lies in the fact that nodes must occupy the middle slot of a multipart and this doesn't. I'll have to think about this.
I'm going to merge anyway, and maybe add this as another issue.

authors: ElvishJerricco SquidDev

repo: SquidDev-CC/CC-Tweaks

license: mit


text:
Back to Top Button Added

Live site link:
https://swadhin2001.github.io/fix-your-nums/

Merged 👍

repo: Srijita-Mandal/fix-your-nums


text:
.half call to fix?

I am sorry that I cannot provide my python Traceback log (already reverted my code, sadly).
I was trying to update my previous code based on SD v1, I faced the error message :
Input type (torch.cuda.HalfTensor) and weight type (torch.cuda.FloatTensor) should be the same conv2d
Since I haven't modified the core part of the model, I thought this error came from the compatibility issue between my custom-made code.
However, I couldn't find where HalfTensor came from. And I found this line from SD v2 code a while after reverting my code :
return checkpoint(self._forward, (x,), self.parameters(), True)   # TODO: check checkpoint usage, is True # TODO: fix the .half call!!!
I am wondering where is the ".half call" to fix; it might solve my 2nd attempt for the patch. 👍

the tensor needs to be .half(). So wherever it's being decoded just add .half() to the end of the final tensor

Last time I got this issue, I fixed by upgrading transformers' lib
pip install --upgrade git+https://github.com/huggingface/diffusers.git transformers accelerate scipy

authors: KyonP nguyenmeteorops richservo

repo: Stability-AI/stablediffusion


text:
Tag new release?

Hi, thank you for making and maintaining this library.
Is there any way you could tag a new release?
I'm particularly concerned about this commit not being in the latest release, but maybe I'm misunderstanding it:
https://github.com/StackExchange/wmi/commit/b12b22c5341f0c26d88c4d66176330500e84db68
I like using semantic versions where possible so I'd really appreciate it.
Thank you!

Hello, any feedback on this request?

This is on our wishlist as well.
@captncraig you seem to be the last active maintainer, do you have time to create a new tag? Preferrably adhering to Go module requirements, ie prefixed with a v, so something like v1.1.0.

Tagged 1.1.0

authors: captncraig carlpett shawnps-sigsci

repo: StackExchange/wmi


text:
[bug]: Files missing on new app creation

Describe the bug
When using the stacked_cli to create a new app, some files are missing and the app can't build.
What operating system do you use?
Linux
Information about the installed tooling
# stacked --version
1.13.1
# flutter --version
Flutter 3.22.2 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 761747bfc5 • 2024-06-05 22:15:13 +0200
Engine • revision edd8546116
Tools • Dart 3.4.3 • DevTools 2.34.3
Steps to reproduce the issue
Commands
stacked create app new_app
cd new_app
flutter run -d <HARDWARE_ID>

Results
llib/main.dart:2:8: Error: Error when reading 'lib/app/app.bottomsheets.dart': No such file or directory
import 'package:new_app/app/app.bottomsheets.dart';
       ^
lib/main.dart:3:8: Error: Error when reading 'lib/app/app.dialogs.dart': No such file or directory
import 'package:new_app/app/app.dialogs.dart';
       ^
lib/main.dart:4:8: Error: Error when reading 'lib/app/app.locator.dart': No such file or directory
import 'package:new_app/app/app.locator.dart';
       ^
lib/main.dart:5:8: Error: Error when reading 'lib/app/app.router.dart': No such file or directory
import 'package:new_app/app/app.router.dart';
       ^
lib/main.dart:10:9: Error: Method not found: 'setupLocator'.
  await setupLocator();
        ^^^^^^^^^^^^
lib/main.dart:11:3: Error: Method not found: 'setupDialogUi'.
  setupDialogUi();
  ^^^^^^^^^^^^^
lib/main.dart:12:3: Error: Method not found: 'setupBottomSheetUi'.
  setupBottomSheetUi();
  ^^^^^^^^^^^^^^^^^^
lib/main.dart:22:21: Error: The getter 'Routes' isn't defined for the class 'MainApp'.
 - 'MainApp' is from 'package:new_app/main.dart' ('lib/main.dart').
Try correcting the name to the name of an existing getter, or defining a getter or field named 'Routes'.
      initialRoute: Routes.startupView,
                    ^^^^^^
lib/main.dart:23:24: Error: The method 'StackedRouter' isn't defined for the class 'MainApp'.
 - 'MainApp' is from 'package:new_app/main.dart' ('lib/main.dart').
Try correcting the name to the name of an existing method, or defining a method named 'StackedRouter'.
      onGenerateRoute: StackedRouter().onGenerateRoute,
                       ^^^^^^^^^^^^^
Target kernel_snapshot failed: Exception

FAILURE: Build failed with an exception.

Expected behavior
No response
Screenshots
No response
Additional Context
No response

I am having the same errors too. Any fix for this?

You need to generate that code.
You can run stacked generate but it should run that automatically after the stacked create command

@maxiggle & @Nialisc did running stacked generate resolve this issue?

@sebastianbuechler yes,
I just tried it

authors: FilledStacks Nialisc maxiggle sebastianbuechler

repo: Stacked-Org/stacked


text:
NPM package broken

I consistently run into errors with the npm package version, however installing from GitHub works.  I suspect the npm package needs updating.

@andrewtlove -
Help me out here. Which errors? How are you running the tool? What are you seeing?
The published npm version right now does not have consistent documentation with the master branch or API. master. Are you using the right documentation?
The npm package doesn't need updating, as a new version hasn't been published.

@andrewtlove -
I've published a new version to npm and added unit tests.
Please let me know if anything doesn't work.

authors: Marak andrewtlove

repo: Stackvana/stack


text:
"Continue the conversation" appears even when there are no suggested questions

The problem is instead that there there are no suggested questions. Suggested questions should always appear.

Not sure what steps to reproduce are so will leave QA for @bryceerobertson

authors: bryceerobertson melissasamworth

repo: StampyAI/stampy-ui


text:
Implement search for the Thingpedia documentation

Using the lunr FTS library, custom code to extract the text of
our markdown files, and custom code to do highlight and
search-as-you-type
Fixes #116

Pull Request Test Coverage Report for Build 358

5 of 31 (16.13%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 53.511%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

routes/thingpedia_developer_console.js
5
31
16.13%

Totals

Change from base Build 356:
-0.1%

Covered Lines:
4300

Relevant Lines:
7446

💛  - Coveralls

authors: coveralls gcampax


text:
watchOS & visionOS Support

Problem
The Spezi module should support watchOS to enable developers to build an Apple Watch-based application and visionOS to support developers who want to develop applications running on Apple Vision Pro.
The current Spezi module only supports and automatically tests iOS builds.
Solution
Add support for the latest watchOS and visionOS versions. We must add them as supported platforms in the Swift package file and update the Swift tools version to 5.9 if required.
Additional context
All changes should be as cross-platform as possible. Increasing the iOS minimum platform target is acceptable.
The StanfordBDHG/SwiftPackageTemplate demonstrates the CI setup for visionOS and watchOS that should also be adopted for this Spezi module.
Code of Conduct

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

visionOS and macOS support achieved via #18

Thank you @philippzagar!

authors: PSchmiedmayer philippzagar vishnuravi

repo: StanfordSpezi/SpeziStorage


text:
/api/show_data automatically aggregates results by db or table

Feature request
Provides an option to count the data size of all databases or tables via the RESTful API /api/show_data.

I want try this task, can you assign it to me?

I want try this task, can you assign it to me?

Of course! If you have any questions, please feel free to discuss with me at any time.

Feature request
Provides an option to count the data size of all databases or tables via the RESTful API /api/show_data.

I have a question about this requirement. Should I provide a table parameter to indicate that I want to count the current table size?
In show data statement we can calculate each table size in table format
StarRocks > show data;
+--------------------------+----------------+---------------------+
| TableName                | Size           | ReplicaCount        |
+--------------------------+----------------+---------------------+
| table_1                       | 587.555 KB     | 36                  |
| table_2                      | 88.386 KB       | 36                  |
| table_3                      | 433.913 KB     | 36                  |
| table_4                      | 0.000 B           | 36                  |
| table_5                      | 71.426 KB       | 36                  |
| table_6                      | 166.251 KB     | 36                  |
| table_7                      | 49.008 KB      | 36                  |
| table_8                      | 6.404 MB       | 36                  |
| table_9                      | 5.617 MB        | 36                  |
| table_10                    | 433.913 KB     | 36                  |
| Total                          | 13.809 MB      | 360                 |
| Quota                        | 8388608.000 TB | 9223372036854775807 |
| Left                            | 8388608.000 TB | 9223372036854775447 |
+--------------------------+----------------+---------------------+

Do we want to remain unified?

Feature request
Provides an option to count the data size of all databases or tables via the RESTful API /api/show_data.

I have a question about this requirement. Should I provide a table parameter to indicate that I want to count the current table size?
In show data statement we can calculate each table size in table format
StarRocks > show data;
+--------------------------+----------------+---------------------+
| TableName                | Size           | ReplicaCount        |
+--------------------------+----------------+---------------------+
| table_1                       | 587.555 KB     | 36                  |
| table_2                      | 88.386 KB       | 36                  |
| table_3                      | 433.913 KB     | 36                  |
| table_4                      | 0.000 B           | 36                  |
| table_5                      | 71.426 KB       | 36                  |
| table_6                      | 166.251 KB     | 36                  |
| table_7                      | 49.008 KB      | 36                  |
| table_8                      | 6.404 MB       | 36                  |
| table_9                      | 5.617 MB        | 36                  |
| table_10                    | 433.913 KB     | 36                  |
| Total                          | 13.809 MB      | 360                 |
| Quota                        | 8388608.000 TB | 9223372036854775807 |
| Left                            | 8388608.000 TB | 9223372036854775447 |
+--------------------------+----------------+---------------------+

Do we want to remain unified?

I think it's ok.

@Jin-H are you still working on this issue?

authors: Jin-H kevincai sduzh

repo: StarRocks/starrocks