Chronial/snapraid-runner Issue #3: Add support for smart command

The formatting output in the email isn't the greatest, but it's enough to discern the result of the SMART command.

@Chronial anything I need to do to close out this MR?

Thanks for working on this! 🎉

@k3vmcd I simplified the implementation a bit. Does this still fulfill your requirements? Please see here how to fix your PATH issue on cron.


Unable install Ledger Nano S ripple wallet

I am getting access is denied for Ipersist file when I'm trying to install the wallet.
attaching the image below

Sachin

This might be caused by bitdefender antivirus, see this similar situation

After the innstall I'm getting this

please help


Add a 3-section hero section that interlaps with the Open Fresno bridge logo

Issue is being put on hold until OpenFresno is able to acquire our domain from Code for America and finish setting up the template through OpenSac.org.


qbo prepend code import settings page changes

Summary by CodeRabbit

New Features

Enhanced import settings functionality with the addition of import_code_fields, allowing for more detailed configurations.
Introduced getImportCodeFieldConfig method to fetch import code field configurations.
Added interactive elements in the UI for selecting import categories and import codes.

Bug Fixes

Improved initialization safety by adding checks in the lifecycle method to prevent potential runtime errors.

Style

Adjusted layout spacing for better UI presentation and user experience.

Documentation

Updated placeholder text for clarity in the import field configuration component.


Embed the version of wit-bindgen in generated files

Following up on @Mossaka's idea in #486, we should add a comment to generated source files indicating the wit-bindgen version, for debugging purposes.

My plan was to add a producers section to the wasm inside the component-type section, so that the version of wit-bindgen carried through to the final artifact. Of course, we can also make a string available in the generated code.


Please invite me to the GitHub Community Organization

Name
Ibrahim Raimi Olayinka
Discord Username (if applicable)
No response
Additional Context
The developers,  the more i realize that it's such a “awesome” community. ...

Check your email or organisation page
Thank you for contribution 🙂
Please contribute in Unique-Github-Profiles

Thanks for having me contribute to your organization.


Make project compatible with Python 3.7+

Closes #35

So far, it's a lot of find-and-replace work. I have replaced the types, but get_origin() needs to be replaced, too. As of now, it's 447 tests failed, 12 tests passed :)

Alright, I have resolved almost everything that needed to be resolved. There is one last problem, though.
The test argparse.test_parser.py::test_invalid_arguments fails when a subparser doesn't have a dest. It happens right on the last step, where the error message gets generated. This was a known bug (see https://github.com/python/cpython/issues/73484) which was fixed in 3.11 (https://github.com/python/cpython/pull/3680) and backported to 3.9 (https://github.com/python/cpython/pull/27304). Since it's a module function, we can't reliably backport/patch it.
@SupImDos any ideas what we can do here? I propose adding a default metavar to the SubParsersAction with the value of, e.g., "COMMAND":
class SubParsersAction(argparse._SubParsersAction):
+    def __init__(self, *args, **kwargs):
+        kwargs.setdefault("metavar", "COMMAND")
+        super().__init__(*args, **kwargs)

Basically, this would be analogue to this:
parser = argparse.ArgumentParser()
subparsers = parser.add_subparsers(metavar="COMMAND", required=True)
test_sub = subparsers.add_parser("test")
test_sub.add_argument("--flag", type=bool, default=False)

$ python3.7 parsing.py --help
usage: parsing.py [-h] COMMAND ...

positional arguments:
  COMMAND

optional arguments:
  -h, --help  show this help message and exit

$ python3.7 parsing.py
usage: parsing.py [-h] COMMAND ...
parsing.py: error: the following arguments are required: COMMAND

The same code under Python 3.7, but without metavar
$ python3.7 parsing.py --help
usage: parsing.py [-h] {test} ...

positional arguments:
  {test}

optional arguments:
  -h, --help  show this help message and exit

$ python3.7 parsing.py
Traceback (most recent call last):
  File "parsing.py", line 9, in <module>
    parser.parse_args()
  File "/Users/nikita/.pyenv/versions/3.7.16/lib/python3.7/argparse.py", line 1755, in parse_args
    args, argv = self.parse_known_args(args, namespace)
  File "/Users/nikita/.pyenv/versions/3.7.16/lib/python3.7/argparse.py", line 1787, in parse_known_args
    namespace, args = self._parse_known_args(args, namespace)
  File "/Users/nikita/.pyenv/versions/3.7.16/lib/python3.7/argparse.py", line 2022, in _parse_known_args
    ', '.join(required_actions))
TypeError: sequence item 0: expected str instance, NoneType found

@kytta
Wow, thanks so much for all your hard work. This looks great!
1. Minor Type Checking Error
Looks like we might need to add a type: ignore[union-attr] to the BooleanOptionalAction backport so the CI/CD passes. The Python standard library typing is always a bit dodgy.
https://github.com/kytta/pydantic-argparse/blob/python-37/pydantic_argparse/argparse/actions.py#L194
-            setattr(namespace, self.dest, not option_string.startswith('--no-'))
+            setattr(namespace, self.dest, not option_string.startswith('--no-'))  # type: ignore[union-attr]

2. Argparse SubParser Backport Bug
Hmm this is an interesting one. Ideally I would like to keep the same behaviour (i.e., show the different command options across the different versions. i.e.,
$ python examples/commands.py
usage: Example Program [-h] [-v] [--verbose] {build,serve} ...
Example Program: error: the following arguments are required: {build,serve}

I can think of a few things we can do:

Default Static Metavar
As you suggest above, we can provide a default/dummy metavar to the SubParsersAction.
pydantic_argparse/argparse/actions.py
class SubParsersAction(argparse._SubParsersAction):
+    def __init__(self, *args, **kwargs):
+        kwargs.setdefault("metavar", "COMMAND")
+        super().__init__(*args, **kwargs)

However, this means the help does not display the actual options we have (i.e., in this case {build,serve} - just the COMMAND string.
$ python examples/commands.py
usage: Example Program [-h] [-v] [--verbose] COMMAND ...
Example Program: error: the following arguments are required: COMMAND

Dynamic Metavar Using Property
Another option we have is to hijack the metavar value using a @property. This way we can dynamically construct the string with self.choices to provide the desired {build,serve} string. It is a bit messy though, and we have to provide a dummy @metavar.setter method. Not sure if I really like this option.
pydantic_argparse/argparse/actions.py
class SubParsersAction(argparse._SubParsersAction):
+   @property
+   def metavar(self) -> Optional[str]:
+       """Docstring...
+
+       Returns:
+           Optional[str]: ...
+       """
+       # Explanation?
+       # Type checking?
+       # What if no `self.choices`?
+       return '{' + ','.join(self.choices) + '}'
+
+   @metavar.setter
+   def metavar(self, value: Any) -> None:
+       """Docstring...
+
+       Args:
+           value (Any): ...
+       """
+       # Dummy method, we can't allow it to be set
+       return None

The desired result is produced below.
$ python examples/commands.py
usage: Example Program [-h] [-v] [--verbose] {build,serve} ...
Example Program: error: the following arguments are required: {build,serve}

Backport and MonkeyPatch _get_action_name
Finally, we could provide our own monkey-patch for the fixed _get_action_name method as below. This would provide the desired functionality and be relatively clean? I think I like this, but I'm not sure if we might introduce some issues by monkey-patching the standard library.
pydantic_argparse/argparse/patches.py
"""Docstring..."""

# Standard
import argparse
import sys

# Typing
from typing import Optional

# Some comments here explaining why we do this
# https://github.com/python/cpython/blob/main/Lib/argparse.py#L739-L751
if sys.version_info < (3, 9):
    def _get_action_name(argument: Optional[argparse.Action]) -> Optional[str]:
        """Docstring."""
        if argument is None:
            return None
        elif argument.option_strings:
            return '/'.join(argument.option_strings)
        elif argument.metavar not in (None, argparse.SUPPRESS):
            return argument.metavar  # type: ignore[return-value]
        elif argument.dest not in (None, argparse.SUPPRESS):
            return argument.dest
        elif argument.choices:
            return '{' + ','.join(argument.choices) + '}'
        else:
            return None

    # Monkey-Patch
    argparse._get_action_name = _get_action_name

The desired result is produced below.
$ python examples/commands.py
usage: Example Program [-h] [-v] [--verbose] {build,serve} ...
Example Program: error: the following arguments are required: {build,serve}

@kytta I think at the moment I prefer (3). What do you think?

Looks like we might need to add a type: ignore[union-attr] to the BooleanOptionalAction backport so the CI/CD passes.

Yup, done!

2. Argparse SubParser Backport Bug
Hmm this is an interesting one. Ideally I would like to keep the same behaviour (i.e., show the different command options across the different versions.
[...]
I can think of a few things we can do:
1. **Default Static Metavar**

This would be my favourite way to do this, but I understand that having every command as a metavar is more helpful than just "COMMAND".

2. **Dynamic Metavar Using Property**

Too messy, such that the code becomes less readable.

3. **Backport and MonkeyPatch `_get_action_name`**

I am usually not a fan of monkey patching module functions, but this is pretty clean, and we can turn it off on newer Python versions with sys.version_info check.

@kytta I think at the moment I prefer (3). What do you think?

Yeah, let's do that.

@SupImDos another thing I wanted to ask: How do you like typing_extensions and importlib_metadata to be imported? They currently use two different approaches, and I want to use the same one for both of them:

Version-checked. We would only install the backports on those Python versions, where they're needed, and check the version at runtime:
# foobar.py
if sys.version < (3, 8):
    import importlib_metadata as metadata
else:
    from importlib import metadata

# pyproject.toml

[tool.poetry.dependencies]
# [...]
importlib_metadata = { version = ">=4", python = "<3.8" }

Always import. We don't care about the Python version and always use the backport:
# foobar.py
import importlib_metadata as metadata

# pyproject.toml

[tool.poetry.dependencies]
importlib_metadata = ">=4"

I like the (1) better, as it allows us to ship less dependencies to the most users (as I don't think that many people use Python 3.7 in production, especially for command-line-apps). It is also very easy to remove later with pyupgrade. But the code is cleaner with the second option 🤔

How do you like typing_extensions and importlib_metadata to be imported?

Version-checked. We would only install the backports on those Python versions, where they're needed, and check the version at runtime...

This feels like the correct way to do it. As you say, it allows us to ship less dependencies to the most users.

Always import. We don't care about the Python version and always use the backport...

Less code branching is a lot cleaner and it is tempting. But I think (1) is still better in a practical sense.
@kytta I agree with you that we should go with (1)  😃
I am interested to see how the code coverage is calculated with branches that only execute in certain Python versions. We will have to see 🤔

I am interested to see how the code coverage is calculated with branches that only execute in certain Python versions. We will have to see 🤔

This is also an interesting moment.
A while ago I have noticed the comment # pragma: <3.8, cover somewhere, and it was supposed to disable coverage on the branches on specific Python repos. I have used it in my project, and it worked.
Now, I have tried to also use it here (see commit c2bcc6ce305cea9629dc281b52a7a34bf2c34c5a), but it didn't work (at least locally). For me, poe test reports missing lines, these version checks to be exact.
I then tried to look this pragma up, but neither coverage nor pytest-cov docs mention anything other than pragma: no cover…
If we can't get this to work, I propose setting pragma: no cover on lines for Python 3.7–3.8 and only run coverage on the newer versions

@kytta
I've done a bit of a look into the # pragma: >x.y cover and I think I might have worked it out. As far as I can tell it looks like it comes from the covdefaults package.
I had a look at your venvy project which uses # pragma: <3.8 cover and # pragma: >=3.8 cover, and it looks like it has covdefaults installed.
I think this works? covdefaults looks pretty useful. Maybe we should do:

poetry add --group dev covdefaults
Modify pyproject.toml[tool.coverage.run]
- branch = true
+ plugins = ["covdefaults"]
-
- [tool.coverage.report]
- show_missing = true
- exclude_lines = [
-   "if __name__ == .__main__.:",
- ]

Does this sound right? What do you think?

@kytta I've done a bit of a look into the # pragma: >x.y cover and I think I might have worked it out. As far as I can tell it looks like it comes from the covdefaults package.
I had a look at your venvy project which uses # pragma: <3.8 cover and # pragma: >=3.8 cover, and it looks like it has covdefaults installed.
I think this works? covdefaults looks pretty useful. Maybe we should do:
1. `poetry add --group dev covdefaults`

2. Modify `pyproject.toml`
   ```diff
   [tool.coverage.run]
   - branch = true
   + plugins = ["covdefaults"]
   -
   - [tool.coverage.report]
   - show_missing = true
   - exclude_lines = [
   -   "if __name__ == .__main__.:",
   - ]
   ```

Does this sound right? What do you think?

Oh right, I completely forgot about this package! Yeah, this looks good, I'll add this to pyproject.toml

Alright, everything is fixed, and the only thing left is the coverage for some of the backports:

Should we even cover those? I mean, it's not even our code... 🤔

@kytta
Thanks so much, this looks great!

Alright, everything is fixed, and the only thing left is the coverage for some of the backports
Should we even cover those? I mean, it's not even our code... :thinking:

You're right, I would be happy with a # pragma: no cover for now, as you say its not our code anyway. I think the CI/CD is only failing because of the <100% coverage (which will be fixed by the pragmas) and a whitespace issue in patches.py.
I'll do my best to review this properly as soon as I can 😃

Alright, should be done now! All checks run fine on my machine 👌🏻


Improved and completed french translation

Use of french verbs indiquer/spécifier
Limit use of conjugation, prefer infintive
Tested in CLI

Signed-off-by: Olivier Le Monnier<EMAIL_ADDRESS>

This pull request didn't trigger Jenkins as its author isn't in the whitelist.
An organization member must perform one of the following:

To have this branch tested by Jenkins, use the "ok to test" command.
To have a one time test done, use the "test this please" command.

Those commands are simple Github comments of the format: "jenkins: COMMAND"


Adjust ConfiguConfigStore for the Approval Queue feature

Suggestion
The ConfiguConfigStore class set method currently doesn't acknowledge that configs might not have been mutated but instead inserted into an approval queue for admin review. To indicate to users of the store, the method should throw an exception in this scenario.
Motivation
Improved UX and clarity to users of ConfiguConfigStore
Tasks

[x] TS SDK implementation
[x] CLI implementation

This issue is no longer relevant due to the Python and Go SDKs being deprecated in favor of @configu/proxy


Calling store.dispatch() from a React component file?

I apologize if this is something that has already been cleared up, but a keyword search in the issues didn't turn up anything that helped.
If I want to call store.dispatch(someAction) from a component file, what is the correct way to access the store instance?
Right now I have the following, which works, but I'm not sure that it's the right approach:
index.jsx:
...
const store = applyMiddleware(
  loggingMiddleware, // log every action
  thunk // making API requests from actions
)(createStore)(reducer);

export {
  store
};
...

Controls.jsx
import {store} from './index.jsx';
import * as actions from './actions';
...
let clickHandler = function(node, data) {
  store.dispatch(actions.nodeClicked(data))
}
export const Controls = React.createClass({
  render: function() {
    // React component gets rendered, and it passes the clickHandler to a
    // function that attaches it to a D3 visualization
  }
});

Is there anything wrong with exporting/importing the store like this? I think I could just create the click handlers as part of the React component and call this.context.store, but in reality there are about a dozen different event handlers that get passed to the D3 visualization, so that's not really practical in this situation.

Check out https://github.com/rackt/react-redux for a helper method to bind dispatch to your components

Specifically, from http://rackt.org/redux/docs/basics/UsageWithReact.html

Any component wrapped with connect() call will receive a dispatch function as a prop, and any state it needs from the global state.

Is there anything wrong with exporting/importing the store like this?

This won't work if you render your app on server because you want to have different store instance per request on server. That's why we never recommend this approach in the docs.
Why not do this instead?
import { Component } from 'react';
import { connect } from 'react-redux';
import * as actions from './actions';

let createHandlers = function(dispatch) {
  let onClick = function(node, data) {
    dispatch(actions.nodeClicked(data))
  };

  return {
    onClick,
    // other handlers
  };
}

class Controls extends Component {
  constructor(props) {
    super(props);
    this.handlers = createHandlers(this.props.dispatch);
  }

  render() {
    // pass this.handlers anywhere you'd like
  }
}

export connect()(Controls);

@gaearon Looks great, thank you!

@gaearon Actually, after trying it out, I'm getting undefined for this.props.dispatch.
The relevant parts of my code:
import React from 'react';
import {Component} from 'react';
import {connect} from 'react-redux';
import * as vizActions from './vizActions';
import viz from './lib/viz';

let createHandlers = function(dispatch) {
  return {
	click: function(DOMNode, data) {
		// Getting undefined here
		dispatch(vizActions.setSelectedNode(data));
	}
  };
}

class Viz extends Component {
  constructor(props) {
    super(props);
    console.log(this.props.dispatch); // <- Getting undefined here
    // Passing the redux dispatch to be used in handlers function
    this.handlers = createHandlers(this.props.dispatch);
  }

  componentDidMount() {
    // Create Viz
  }

  componentDidUpdate() {
    // Update Viz Data, passing in this.handlers
  }

  render() {
    return

;
  }
};

function mapStateToProps(state) {
  return {
    // Pass the network used for the viz as a prop
    network: state.get('visualization').get('network')
  };
}

export const VizContainer = connect(mapStateToProps, vizActions)(Viz);

However, after reading another issue (https://github.com/rackt/redux/issues/239) I realized that I am actually binding my actions to this.props via connect(), so I can just pass the necessary action when I call createHandlers(). Maybe this is not the best approach but it works now:
...
let createHandlers = function(action) {
  return {
	click: function(DOMNode, data) {
                // This works now
		action(data);
	}
  };
}

class Viz extends Component {
  constructor(props) {
    super(props);
    // Passing the redux dispatch to be used in handlers function
    this.handlers = createHandlers(this.props.setSelectedNode); // passing action creator function
  }
...

Actually, after trying it out, I'm getting undefined for this.props.dispatch.

Because you are not running the code I posted. In the code I posted connect did not receive second paramater. You pass vizActions there. That's why you don't get dispatch. If you remove vizActions from connect call you will get it.
Both approaches are equivalent though so go with what reads best to you.

:+1: Ok, that makes sense now. Thanks for the help!

Kinda late to the party, but replying just in case it helps someone later (including myself).
If a custom mapDispatchToProps is needed (the second param passed to connect), explicitly add dispatch as one of the keys.
const mapDispatchToProps = (dispatch) => {
  return {
    dispatch,

    // ... other custom mapped dispatch functions ...
    myFunction: (myParam) => {
      dispatch(State.Actions...)
    },
  }
}

export default connect( mapStateToProps, mapDispatchToProps )(Viz);

Sorry to add to an old thread but I think my question kinda relates to this.
I have an action which toggles the side menu for my app and when I use store.dispatch() inside my SideMenu component everything seems to work fine but when I tried the approach of passing down dispatch from the parent app.js. A re-render is triggered for the whole app every time I toggle the Side Menu.
What would be the difference between the 2 approaches that is causing this?

Hi. I also have this problem.
@gaearon ,  i'm grateful for your guidance. I've used your solutions, but I can not understand and use them.
I do not know how to use this.handlers When the user clicks on a card, I send that card id to the parent's components and run the action.
import React , { Component } from 'react';
import { Col } from "react-bootstrap";
import { connect } from 'react-redux';
import Home from "../components/Home";
import { fetchHome, asideArticle } from "../actions/index";

let createHandlers = function(dispatch) {
    let onClick = function(node, articleId) {
        dispatch(asideArticle(articleId))
    };
    return {
        onClick
    };
}

class HomeContainer extends Component {
    constructor(props) {
        super(props);
        this.handlers = createHandlers(this.props.dispatch);
        console.log('constructor => this.props.dispatch => Result => dispatch is undefined);
    }
    componentDidMount() {
        this.props.fetchHome();
    }

    render() {
        const { homeData, article } = this.props;

       //
        return (
            <Col>
                <Home homeData={homeData} asideArticle={(articleId) => asideArticle(articleId) } />
            </Col>
        );
    }
}

const mapStateToProps = state => ({
    homeData : state.home,
    article: state
});

function loadData(store){
    return store.dispatch(fetchHome());
}

export default {
    loadData,
    component: connect(mapStateToProps, { fetchHome, asideArticle })(HomeContainer)
}

How can I use this.handlers and pass the articleId after passing the click event to pass it ?
And what does the node parameter mean in the function(node, articleId) and what does it do?


Allow pkgr user sudo access without password

Allow the packager user to run commands with sudo without requiring a password

This will help with https://github.com/crohr/pkgr/issues/67


evalv3: strange behaviour with chaining of list comprehensions

What version of CUE are you using (cue version)?

$ cue version
cue version v0.0.0-20240507175810-9efad9041981

go version go1.22.1
      -buildmode exe
       -compiler gc
  DefaultGODEBUG httplaxcontentlength=1,httpmuxgo121=1,tls10server=1,tlsrsakex=1,tlsunsafeekm=1
     CGO_ENABLED 1
          GOARCH arm64
            GOOS linux
             vcs git
    vcs.revision 9efad90419811c9a27682857ffdc9324cdb7e094
        vcs.time 2024-05-07T17:58:10Z
    vcs.modified false
cue.lang.version v0.9.0

Does this issue reproduce with the latest release?
Yes
What did you do?
# old evaluator
env CUE_EXPERIMENT=''
exec cue export x.cue
cmp stdout stdout.golden

# new evaluator
env CUE_EXPERIMENT='evalv3'
exec cue export x.cue
cmp stdout stdout.golden

-- x.cue --
import "math/bits"

x: [...bool]
x: [true, false, true, true]
y: [for _, v in x {[if v {1}, 0][0]}]
z: [for i, v in y {bits.Set(*z[i-1] | 0, len(y)-i-1, v)}][3]

-- stdout.golden --
{
    "x": [
        true,
        false,
        true,
        true
    ],
    "y": [
        1,
        0,
        1,
        1
    ],
    "z": 1
}

What did you expect to see?
Passing test.
What did you see instead?
# old evaluator (0.012s)
# new evaluator (0.011s)
> env CUE_EXPERIMENT='evalv3'
> exec cue export x.cue
[stderr]
z: error in call to math/bits.Set: non-concrete value _:
    ./x.cue:6:20
[exit status 1]
FAIL: /tmp/testscript820382168/repro.txtar/script.txtar:8: unexpected command failure

Note that it is understood that the reference in the declaration of z to *z[i-1] | 0 is "wrong" by virtue of the result of z being a scalar value (contrast https://cuelang.org/play/?id=MSdriK7Ernf#w=function&i=cue&f=eval&o=cue) but reporting this actual error for completeness' sake.

Simplification 1:
import "math/bits"
z: [0, bits.Set(*z[0] | 0, 0, 0)][1] // Same error

Simplification 2:
z: [0, z[0]][1] // results in `_`

BTW,  it is correct for this to be an error. The error message is just confusing.
The old evaluator was incorrect here: z is an integer value in the final result, so z[x] is not a valid expression.
It remains a bit open what a correct error would be, but probably a cycle error is the most appropriate.

The old evaluator was incorrect here: z is an integer value in the final result, so z[x] is not a valid expression.

Yep indeed, hence why I wrote in the original description:

Note that it is understood that the reference in the declaration of z to *z[i-1] | 0 is "wrong" by virtue of the result of z being a scalar value (contrast https://cuelang.org/play/?id=MSdriK7Ernf#w=function&i=cue&f=eval&o=cue) but reporting this actual error for completeness' sake.

Regarding:

It remains a bit open what a correct error would be, but probably a cycle error is the most appropriate.

Seems to make sense. That would give a "hint" that the code refers to self, when it really shouldn't.


Add support for request options with a timeout

See https://github.com/google/generative-ai-js/pull/31, https://github.com/google/generative-ai-android/pull/52
The new design allows passing a requestOptions argument when creating the model. Currently they cannot be passed to generateContent and the other calls like safety settings and generation config, but we can add optional arguments later and it should not be breaking for anyone since the class is final.
The initially supported option is a timeout. cc @brianquinlan - Do you think we should punt on this for now until package:http supports "real" timeouts which cancel requests, or should we implement faked support for now and update to also cancel the outstanding request when we implement timeouts there?
More options may be added later.

I'd add fake support - we don't even have a proposed implementation for timeouts in package:http, do we?

No, we need to solve the upgrade path for client implementations. Once we solve that problem I think the API and implementation questions are manageable.
We could also hold off on adding timeouts in this SDK for now and revisit after http gets the new feature, or at least a concrete API design.


Add capability of setting number of threads to the container

Closes #259.

Codecov Report

Merging #319 into master will decrease coverage by 3.05%.
The diff coverage is 91.66%.

@@            Coverage Diff             @@
##           master     #319      +/-   ##
==========================================
- Coverage   91.22%   88.17%   -3.06%
==========================================
  Files          57       57
  Lines        3147     3171      +24
  Branches      604      609       +5
==========================================
- Hits         2871     2796      -75
- Misses        147      248     +101
+ Partials      129      127       -2

Flag
Coverage Δ

#unittests
88.17% <91.66%> (-3.06%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

hummingbird/ml/operator_converters/constants.py
100.00% <ø> (ø)

...gbird/ml/operator_converters/sklearn/kneighbors.py
79.66% <66.66%> (ø)

hummingbird/ml/convert.py
62.50% <77.77%> (-18.49%)
:arrow_down:

hummingbird/ml/_container.py
89.14% <92.30%> (-1.61%)
:arrow_down:

hummingbird/ml/_topology.py
89.30% <92.75%> (+1.49%)
:arrow_up:

hummingbird/ml/_utils.py
82.97% <100.00%> (-3.23%)
:arrow_down:

hummingbird/ml/supported.py
84.69% <100.00%> (-5.94%)
:arrow_down:

...mmingbird/ml/operator_converters/sparkml/linear.py
42.85% <0.00%> (-57.15%)
:arrow_down:

...bird/ml/operator_converters/sparkml/discretizer.py
52.94% <0.00%> (-35.30%)
:arrow_down:

... and 6 more

Continue to review full report at Codecov.

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


Add extra manual for Vite/Inertija/Vue

I had problems understanding the readme for the setup of Vite/Inertija/Vue. I found a lot of entries & blog post of people having difficulties. I think it makes sense to create a seperate document and slim down the Readme.md in the future.
What do you think?

Thanks for the PR! I appreciate that this is a common issue and I'll revisit the Readme soon to see if I can make it simpler/clearer. For now I'm going to keep everything in one file.

Thank you for considering my PR and for your commitment to revisiting the Readme. I understand the decision to keep everything in one file for now.
I'd like to add a specific suggestion that might help clarify the setup process for others, especially those working with Vue/Inertia/Laravel. The current Inertia documentation references Ziggy for routing, but it's not immediately clear whether Ziggy's features are directly compatible with Inertia & Vue setups. This can be a bit confusing for new users.
For instance, in the installation section, it might be beneficial to explicitly state whether Ziggy works seamlessly with Inertia & Vue or if additional steps are required. Additionally, the section on JavaScript frameworks seems to suggest that we need to import the route() function without using @routes, which can be misleading for users who are not deeply familiar with these technologies.
Clearer distinctions and examples in these areas could significantly ease the learning curve for newcomers and reduce the potential for confusion. I believe these small adjustments in the documentation could make a substantial difference for developers integrating these technologies.
Thanks again for your work on this project, and I look forward to the updated Readme!

For those who look for instructions for Laravel, Vue.js, Inertia.js, I wrote a dedicated article: https://iwasherefirst2.medium.com/how-to-setup-ziggy-on-laravel-inertija-vite-vue-19385f50848e


question

HI
I have a doubt regarding the backend KV store supported by libkv, today it supports etcd, cosul, zookeeper. Can it support any other backend which implement the Store interface ?? Like say suppose I give the options to docker daemon
DOCKER_OPTS="--cluster-store=other://<IP_ADDRESS>:4001/...
Will this be supported, like user can specify anything running remotely which can act  as a remote KV store?
Thanks

Hi @prateekgogia,
Yes, if a store backend supports most of the calls specified in the Store interface, it can be leveraged through libkv. For example we can think about adding a redis driver. I'm currently working on implementing an additional driver for irmin a git-like storage that implements most of this Store interface.
Any store that has Put/Get/List/Watch and CAS can be used with docker by specifying --cluster-store. A driver can still be implemented without full support for the  Store interface but that does brake the abstraction and this means that you will not be able to use it seamlessly alongside consul, etcd or zookeeper (you'll have to handle special cases, etc.).
We cannot point to any store though. Each store backend is supported through its own driver here in libkv (by calling their respective client library to communicate with the remote store).

@abronan Thanks for your reply.
What if I write a Http based store backend, and write a driver for it to be included in libkv. Now we could specify
DOCKER_OPTS="--cluster-store=httpstore://<IP_ADDRESS>:5000/...
and this backend store at <IP_ADDRESS> can be like a generic REST server running, which implements all the Store interface mentioned above.
Now, for each docker daemon I can specify this store and it accepts KV data over http through driver/client in libkv.
Do you think something of this sort will be accepted ?

Hi @abronan any comments on the request above ?

@prateekgogia Sorry for the long delay in the reply. The problem in using a generic approach is that we end with no consistency guarantees (whether weak or strong). Which makes the code way more complex on the application side, now I need to take care of all the edge cases where the data could be stale because I have no idea what's behind.
Of course this can be done but the goal of the abstraction is to make sure we register only the kind of store that make sense at the application level. So if we require strong consistency guarantees, we are going to register consul, etcd and zookeeper together. If I don't need this guarantee I can hypothetically register a redis or a simpleDB driver (if those were implemented), etc.
Writing such a driver is definitely possible, but the problem lies in what's behind the REST API? What are the guarantees provided with the store, the calls supported? etc.

Closing this one, but feel free to jump in or open a new issue if you have any more questions or issues to report. Thanks!


Update README.md

No, this is not perfect or final, but it's important to get something mostly correct up quickly.

LGTM. Thanks!


Release Google.Analytics.Admin.V1Alpha version 2.0.0-alpha15

Changes in this release:
Bug fixes

BREAKING CHANGE Remove values PAID_AND_ORGANIC_CHANNELS_FIRST_CLICK, PAID_AND_ORGANIC_CHANNELS_LINEAR, PAID_AND_ORGANIC_CHANNELS_POSITION_BASED, PAID_AND_ORGANIC_CHANNELS_TIME_DECAY corresponding to the deprecated attribution models from the ReportingAttributionModel enum, as per announcement in https://support.google.com/analytics/answer/9164320issue 040623 (commit c84ffbc)

New features

Add GetSubpropertyEventFilter, ListSubpropertyEventFilters methods to the Admin API v1 alpha (commit c84ffbc)
Add the default_conversion_value field to the ConversionEvent type (commit c84ffbc)

Documentation improvements

Update the documentation for the RunAccessReport method (commit c84ffbc)
Update the documentation for grouping_rule, system_defined fields of the ChannelGroup type (commit c84ffbc)

Created release for Google.Analytics.Admin.V1Alpha-2.0.0-alpha15


System checking script

Lets create a report.sh at par with install.sh in root folder.
It will be executed by 2 means:

on server without easyengine *

bash https://raw.github.com/rtCamp/easyengine/stable/report.sh | sudo bash

on server with easyengine *

ee system report

When running on system without easyenigne, we can show warning that report may be inaccurate.
Output
On execution it will generate report with details like below. Later on we can add CLI options to control depth, amount of details, etc
## Hardware
CPU > Core, Model, Make,
RAM > DDR2/DDR3
HDD > SATA/SSD, Amount, Used/Free
Network > 100mbps, 1gbps
IP-Address > number of Public IPs

Check if running behind proxy.

## OS
Distro > name, version + 32/64-bit
Partition table
Mount points

## Software
Packages : non-OS packages
PHP
MySQL (database)
Nginx
Apache
Postfix
Ruby
Python
nodejs

## Sites
site > names, document root, size, is-wordpress?
webroots

search file names wp-config.php across file-system
wordpress sites list

## databases
list database with sizes

## Mail Server
check is mail server is present
clamav, spamassasin, roundcube, etc

## Filesystem Analysis
top 10 folder (du -hs / | sort -hr)

Closing because no longer relevant with time and also v4 moving to docker.


[Bug]: Transform Tool Erase is not saving to history.

What happened?
Transform Tool Erase is not saving to history when selecting portions of an image and deleting them with the delete button.
Steps to reproduce the problem

With an image loaded, go to (S) Select Image.
Drag over an area of the image and press the Delete key.
Portion of image is deleted, but nothing appears in history.
Click on "Save Workspace", notice that the area you have deleted comes back.
To test how it should work, drag over an area and move it somewhere else.
Notice that in the history, "Transform Tool Erase" and "Transform Tool Apply" shows up.

What should have happened?
The "Transform Tool Erase" should be showing up when deleting as well as when moving selections.
Commit where the problem happens
zero01101/openOutpaint@7de3a26, zero01101/openOutpaint-webUI-extension@522c187
What platforms do you use to access openOutpaint?
Windows
What browsers do you use to access the UI ?
Mozilla Firefox
Browser Extensions/Addons
none
AUTOMATIC1111 webUI Commandline Arguments
--medvram --opt-sdp-attention --api
Additional information
No response

sorry for the delay - so you've definitely come across a bug, but not the one you think lol
so the selection tool isn't exactly like photoshopts, i.e. you don't need to select a region to delete first - to remove pixels, you'd simply right-click over the region you want to erase using the dream (txt2img) or img2img tool directly.  the (DEL) key shortcut is for removing any drawn masks you've put over the image, not any actual image content... however, the fact that (DEL) does remove image content should not be happening, so i'm definitely going to have to figure out what happened there... guessing the wrong canvas is being used for selection operation...


Add peers bootstrap merge local writes integration test

cc @xichen2020 @martin-mao @cw9

Coverage decreased (-0.2%) to 80.022% when pulling b3dd0d848ffc28c7f366c8ca690983ec4cd59d71 on merge-latest-bootstrapped-block into 36694a18940fba02cf09be84be1ef2add92f118a on master.

Coverage decreased (-0.3%) to 79.877% when pulling 5db1e92cad57585af1d10910956b9e223ba3774a on merge-latest-bootstrapped-block into 36694a18940fba02cf09be84be1ef2add92f118a on master.

Coverage decreased (-0.2%) to 80.06% when pulling a684662e519c89b4063a608765d9b1073f2f22c7 on merge-latest-bootstrapped-block into 36694a18940fba02cf09be84be1ef2add92f118a on master.

Coverage decreased (-0.2%) to 80.06% when pulling dde3c9cabbc12181fd41d15b158d2dfcdf05891d on merge-latest-bootstrapped-block into 36694a18940fba02cf09be84be1ef2add92f118a on master.

other than the nit LGTM

Coverage decreased (-0.3%) to 79.931% when pulling a522f51e66a88d2dc5b7c7253c392b2cac289d64 on merge-latest-bootstrapped-block into 36694a18940fba02cf09be84be1ef2add92f118a on master.

Coverage decreased (-0.3%) to 79.931% when pulling a522f51e66a88d2dc5b7c7253c392b2cac289d64 on merge-latest-bootstrapped-block into 36694a18940fba02cf09be84be1ef2add92f118a on master.

Coverage decreased (-0.1%) to 80.067% when pulling 0f245883ce52973240ef5b1d689e369904d53116 on merge-latest-bootstrapped-block into 36694a18940fba02cf09be84be1ef2add92f118a on master.

Coverage decreased (-0.1%) to 80.067% when pulling 0f245883ce52973240ef5b1d689e369904d53116 on merge-latest-bootstrapped-block into 36694a18940fba02cf09be84be1ef2add92f118a on master.


ci: pick up cilium-cli v0.11.9 for master/v1.11 workflows

The --base-version flag is no longer necessary and has been deprecated,
see https://github.com/cilium/cilium-cli/pull/891 for details.
Release notes: https://github.com/cilium/cilium-cli/releases/tag/v0.11.9

Enabled CI 3.0 tests passed (all GKE-based workflows are curently disabled due to #20013, AKS currently blocked on #19379):

AWS CNI: https://github.com/cilium/cilium/runs/6934599941?check_suite_focus=true
EKS: https://github.com/cilium/cilium/runs/6934599465?check_suite_focus=true

Removing DO NOT MERGE commit for now and marking as ready for review. Not sure whether we should wait for above issue/PR to be fixed/merged so we could run other workflows as well.

Another green run of AWS-CNI, EKS and GKE:

https://github.com/cilium/cilium/actions/runs/2527689856
https://github.com/cilium/cilium/actions/runs/2527689839
https://github.com/cilium/cilium/actions/runs/2527689875

Force-pushing again to also test external workloads and multicluster.

Tests are green again:

AWS-CNI: https://github.com/cilium/cilium/actions/runs/2534564618
EKS: https://github.com/cilium/cilium/actions/runs/2534564627
GKE: https://github.com/cilium/cilium/actions/runs/2534564622
Multicluster: https://github.com/cilium/cilium/actions/runs/2534564611
External workloads: https://github.com/cilium/cilium/actions/runs/2534564620

Removing DO NOT MERGE commit and marking as ready to merge.


Add snake game

I want to add a snake game.Snake game is a javascript game.
Snake is a sub-genre of action video games where the player maneuvers the end of a growing line, often themed as a snake. The player must keep the snake from colliding with both other obstacles and itself, which gets harder as the snake lengthens.
It would look like this-

Hi,I have experience with the project's tech stack.Please assign this issue to me.It would be grateful for me to contribute.

@stuti-09 I want to contribute.Please assign me

I want to add a snake game it's just simplest task for me. I can make some valuable improvements. I'll start working on it right away. If you have any specific requirements or suggestions, please let me know. Looking forward for collaborating with you all on this.
Thanks !

Hi ,
Aditya Bagla ( GSSOC'23 contributor )
I would like to contribute on this issue . Can you please assign me ?

Project already present


graph init Ethereum/matic/Decentraland contract (480a0f4e360e8964e68858dd231c2922f1df45ef) fails

Which packages are impacted by your issue?
@graphprotocol/graph-cli
Describe the issue
graph init with answers:

Protocol · ethereum
Product for which to initialize · hosted-service
Subgraph name · maoueh/decentraland
Directory to create the subgraph in · decentraland
Ethereum network · matic
Contract address · 480a0f4e360e8964e68858dd231c2922f1df45ef
✖ Failed to fetch ABI from Etherscan: ABI not found, try loading it from a local file
✖ Failed to fetch Start Block: Failed to fetch contract creation transaction hash

However, this ABI exists there, see curl "https://api.polygonscan.com/api?module=contract&action=getabi&address=0x480a0f4e360E8964e68858Dd231c2922f1df45Ef"
Reproduction
See below
Steps to Reproduce the Bug or Issue
graph init then answer questions above
Expected behavior
Works
Screenshots or Videos
None
Platform

OS: macOS
NodeJS: 18.5.0
@graphprotocol/cli version(s): 0.59

Subgraph Manifest
No response
Subgraph GraphQL Schema
No response
Additional context
No response

The issue is that API wants address to be prefixed with "0x". Otherwise it throws an error.
The wizard should probably just add the prefix if it's not there.


Cannot edit text on android

Hello
I access it with android phone, but I can't edit text

Can't confirm with latest Chrome.
What browser are you using?
https://github.com/user-attachments/assets/9acf51e7-e34d-4020-9e84-d6aac7d26390

https://github.com/user-attachments/assets/ecc62c0b-768c-4e27-8f36-fa5789ddfd55
I am using samsung note 10+

Unfortunately, can't reproduce. Anyway, most likely it is fabric.js issue and I don't think I can fix it.
I've added "edit" button as workaround. Is this suitable for you?
https://github.com/user-attachments/assets/d73636c1-293e-4c29-b047-4e299dd0addf


Re-instate Download CLI e2e tests

disabled e2e tests given https://github.com/rancher/rancher/issues/46068

Per @samjustus, the related backend work has been merged for both 2.9.0 & 2.8.x. Let's verify that we can reinstate this E2E test.

Thanks for update. Though original issue still open and links used in UI still seem dead still (for example https://releases.rancher.com/cli2/v2.9.0-rc4/rancher-darwin-amd64-v2.9.0-rc4.tar.gz).
Noticed 2.8 has merged (https://github.com/rancher/cli/pull/378) but not 2.9 (https://github.com/rancher/cli/pull/379). Following that though the workflows would need to run and bits uploaded

2.9 appears to be merged now though https://github.com/rancher/rancher/pull/46141 is still open and the URL is still not working, even with RC5. @enrichman keep us posted on when the bits are uploaded since this E2E test helps with automated testing as QA scrambles to manually test.

@gaktive that's strange, the binaries are uploaded. Do you have the failing link to check the differences?

The -rc5 links look good to me, but rancher 2.9-head builds still reference the -rc4 links, so we'll need https://github.com/rancher/rancher/pull/46141  merged before our tests pass


weight tracker - xaxis scale problem (daily vaues are plotted by year)

Hi,
with Obsidian 1.1.3, I have a weight tracker with this programing:
searchType: frontmatter
searchTarget: weight
folder: Calendar
dateFormat: YYYYMMDD
startDate: 20221201
endDate: 20221231
line:
    title: Weight Log
    yAxisLabel: Weight
    yAxisUnit: kg
    lineColor: yellow

and all the values in a month a plottet not by day, neither by week, neither by month, but by year (annex).
plottet_wrongly.pdf
How can I get daily values plottet by day, on the X axis?
Thanks a ton!
Manfred

I had a terrible time getting tracker charts to work when my naming scheme was YYYYMMDD instead of YYYY-MM-DD. I ended up renaming all my journals to add the dashes. Another option might be to add a
line:
    xAxisTickInterval: 1d

to see if it can break out the data by day.


Add Text/Fonts in the UI_dashboard

Describe the bug
Just like people can add squares and circles, We want out users to be able to add text content. When the User clicks the font/text icon on that bottom bar, A default text should always be adding on the development environment.
File/Files you will work on
ui_dashboard.html
Possible Lines of Code
You should not add above the possible lines of code. (if given)
Result or Final Looks
We except the users to able to add some text.

Can you assign it to me ?

@NtemKenyor please assign this task to me.


Shouldn't expired suppressions fail the build?

We have had a suppression for the critical CVE-2014-9515 for the longest time, but we let it expire a week ago (<suppress until="2024-01-10Z">).
We were surprised to see our builds NOT fail when running the Maven plugin with -DfailBuildOnCVSS=7.
DC properly logs the suppression
12787 [INFO] Suppression is expired for rule<EMAIL_ADDRESS>regex=true, caseSensitive=false},cve={CVE-2014-9515,}}

Yet, the build does not fail and Dozer is still listed under "Suppressed Vulnerabilities" in the report. I checked the docs for a configuration option that would explain this behavior but found none. Also, the suppression documentation has examples for expired suppressions but don't give any further hints as for the expected behavior.

Sorry, turns out we had a suppression for the same CVE in multiple suppression files; expired in one, not expired in the other.


add indices

We should rise awareness that indices are important

Ok.
I saw Alexander prepared a new example with transfers, which is actually correct. Let's switch to it?

Yes I am closing this one in favor of Alexander's PR.


Update eslint-plugin-react version to 7.4.0

This update allows npm shrinkwrap to run cleanly when using eslint 4 as v7.4.0 supports eslint 4 as a peer dependency.

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

The build failed due to a deprecation warning:
/home/travis/build/uber-web/uber-eslint/packages/eslint-config-uber-jsx/test/fixtures/pass.jsx
29:14  warning  React.PropTypes is deprecated since React 15.5.0, use the npm module prop-types instead  react/no-deprecated

✖ 1 problem (0 errors, 1 warning)

Ideally we'd update pass.jsx to use prop-types instead of React.PropTypes. Is that acceptable?

Coverage remained the same at 100.0% when pulling a4fb14bb1e66fb544eeaec4c6cc1c4198f3d858a on shannonmoeller:update-react-plugin into 1d1100bf4c492cfc038d572b3f5af59ce430ee61 on uber-web:master.

Coverage remained the same at 100.0% when pulling a4fb14bb1e66fb544eeaec4c6cc1c4198f3d858a on shannonmoeller:update-react-plugin into 1d1100bf4c492cfc038d572b3f5af59ce430ee61 on uber-web:master.

Coverage remained the same at 100.0% when pulling 01e7e70dd09300ddf3ee5e083103bdbd7a578962 on shannonmoeller:update-react-plugin into 1d1100bf4c492cfc038d572b3f5af59ce430ee61 on uber-web:master.

Coverage remained the same at 100.0% when pulling d743c1d7e289d7fd455b840f3d47647edbf7f81c on shannonmoeller:update-react-plugin into 1d1100bf4c492cfc038d572b3f5af59ce430ee61 on uber-web:master.


[Snyk] Upgrade @reduxjs/toolkit from 2.2.0 to 2.2.7

Snyk has created this PR to upgrade @reduxjs/toolkit from 2.2.0 to 2.2.7.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 7 versions ahead of your current version.

The recommended version was released on 2 months ago.

Release notes

Package name: @reduxjs/toolkit

2.2.7 - 2024-07-27This bugfix release fixes issues with "TS type portability" errors, improves build artifact tree shaking behavior, and exports some additional TS types.
Changelog
TS Type Portability
We've had a slew of issues reported around "TS type portability" errors, such as:

#1806
#3962
#3983

The error messages are typically along the lines of:

Type error: The inferred type of 'configureStore' cannot be named without a reference to '@ reduxjs/toolkit/node_modules/redux'. This is likely not portable. A type annotation is necessary.

@ aryaemami59 did some deep investigation and concluded these were due to a mixture of using interface instead of type in most places, not pre-bundling our TS typedefs, and not exporting some of the unique symbols we use internally.
Arya put together a highly detailed writeup and set of fixes in  #4467: Fix: TypeScript Type Portability Issues, and that appears to resolve all of those issues we've seen.  Thank you!
Other Changes
Arya also did significant work to improve RTK's treeshaking, tweaking internal definitions to let bundlers better separate out unused code.
We've exported additional types like UpdateDefinitions and RetryOptions, per request.
listenerMiddleware.withTypes() methods now allow passing in an ExtraArgument generic.
What's Changed

Fix: TypeScript Type Portability Issues by @ aryaemami59 in #4467
Export UpdateDefinitions from toolkit/query by @ joekrill in #4519
feat: Adds ExtraArgument to withTypes for listenerMiddleware. by @ antondalgren in #4517
Improve treeshakeability of build artifacts by @ aryaemami59 in #4435
Export RetryOptions by @ markerikson in #4529

Full Changelog: v2.2.6...v2.2.7

2.2.6 - 2024-06-29This bugfix release:

Brings internal useIsomorphicLayoutEffect usage in line with React Redux in React Native environments
Exports FetchBaseQueryArgs type
Fixes an issue in recent createEntityAdapter sorting perf improvements that could (in specific cases) cause Immer to throw an error

What's Changed

Fix useIsomorphicLayoutEffect usage in React Native environments by @ aryaemami59 in #4436
Add export for FetchBaseQueryArgs by @ WilsonCWong in #4465
Fix Immer current usage when calling addManyMutably more than once by @ JacobShafer in #4420
Golf a few pieces of entity adapter code by @ EskiMojo14 in #4485

Full Changelog: v2.2.5...v2.2.6

2.2.5 - 2024-05-16

2.2.4 - 2024-05-09

2.2.3 - 2024-03-31

2.2.2 - 2024-03-21

2.2.1 - 2024-02-14

2.2.0 - 2024-02-12

    from @reduxjs/toolkit GitHub release notes

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:

🧐 View latest project report
📜 Customise PR templates
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 8.27%. Comparing base (ed4b158) to head (e17111b).

Additional details and impacted files
@@          Coverage Diff           @@
##           master    #800   +/-   ##
======================================
  Coverage    8.27%   8.27%
======================================
  Files          68      68
  Lines        3952    3952
  Branches      864     864
======================================
  Hits          327     327
  Misses       3625    3625

Flag
Coverage Δ

8.27% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

/retest

:tada: This PR is included in version 1.45.6 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Expand Max Depth of Model Inheritance

Currently, the Parser limits the maximum depth of inheritance to 10 levels. Would it be possible to expand this limit to 12 or more?

this repo implements the DTDL parser based on the DTDL v3 spec
Can you move this ticket to https://github.com/Azure/opendigitaltwins-dtdl/

@joebeernink see https://github.com/digitaltwinconsortium/DTDLParser/pull/137


Issues with Structural Beams to Revit

Do you have a sample for Revit Structural elements like beams and braces?  I can get model lines to transfer, but not so with beams.

@thazell you should use the Family Instance Component:
Insertion Points = Start and EndPoint
Structural Type = Strucutral Beam Component
And Family & Type

@moethu thanks!  That worked.


[bug] Vanced microG high battery drain on Redmi Note 8 Pro

I am not sure how to prove this other than stating the obvious, that after I removed all Vanced apps battery drain stopped.
Yes microG and YT Vanced were excluded from battery optimisation.
Yes microG was set to autostart.
MIUI version is 12.5.3 and I believe drain started after last update, not sure if update of MIUI or Vanced
Device is a year old. I am not using mobile excessively so battery used to last up to 3 days, problem was noticed after it dropped to less than a day. It was so severe that I thought battery or device has gone bad, hence started seeking for a solution.
It appears that issue is fixed after I removed Vanced apps. Please advise since I dont know how to reproduce or add more helpful info. Logs or whatever is needed.

Same here. :/
This is the screenshot from battery usage since last night (note that it's 7:15am in the morning on the screenshot):

I went to sleep with about 80% battery.

It happened to me too. Last night, I had 75%. In the morning I had 6%. When I go to battery usage it says it's Google Play Services, but microG is specifically designed to work with Google Play Services.
I have Xiaomi Redmi Note 8 running Android 9 amd MIUI 11.

Same here. :/
This is the screenshot from battery usage since last night (note that it's 7:15am in the morning on the screenshot)
I went to sleep with about 80% battery.
EDIT: This was on OnePlus 6, OxygenOS <IP_ADDRESS> (Android 11)

It happened to me too. Last night, I had 75%. In the morning I had 6%. When I go to battery usage it says it's Google Play Services, but microG is specifically designed to work with Google Play Services. I have Xiaomi Redmi Note 8 running Android 9 amd MIUI 11.

Yes very strange, so its not just MIUI. I recommend you guys try to remove all vanced apps and see if issue persists. If not then its obviously vanced issue.

Settings Up Adb
Creating A Logcat

Is this normal

Still an issue on note 8 pro in 2024. Massive drain that stopped after removing microG...


feat: Implement poseidon2_permutation in comptime interpreter

Description
Problem*
Resolves another of the many builtin/foreign functions that still need to be implemented in the interpreter
Summary*
Additional Context
Documentation*
Check one:

[x] No documentation needed.
[ ] Documentation included in this PR.
[ ] [For Experimental Features] Documentation to be submitted in a separate PR.

PR Checklist*

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

@vezenovm I'd like to avoid a test for this since it will be tested as part of the derive function when that is done and this also just delegates to an existing lib function.

I'd like to avoid a test for this since it will be tested as part of the derive function when that is done and this also just delegates to an existing lib function.
I'll wait to merge until your response though if you disagree

Ok that is fine. I mainly just wanted to make sure we got the same result in comptime and in run time. But it will be tested as part of derive anyway.


Cleanup after deploy: remove tmp folder + zip

after the zip task finished => remove the tmp folder
after deployment => remove zip
on create: remove empty npm log file from tmp

the temp files (and npmlog in particular) tend to be very helpful when things blow up. npm log is empty if everything works OK, which is why it seems useless.
By forcing the code to remove everything as it goes along, we'd lose valuable troubleshooting info. Instead, I suggest doing the removals as the last step of create and update. that way, if something blows up meanwhile, the files stay. if everything works OK, they'll get removed.

thats true.

the last commit does not delete the tmp folder on error while zipping
npmlogs will stay there if an error occurs.

I'd rather just leave everything and remove at the end of create/update. in that case the zipdir function doesn't need to change at all, and we know that if there's an error, it will bail before that. I plan to work on supporting lambda uploads through s3 next week, so that will be a nice chance to add the removal of temp files as well to the end of create/update. I'll close this pull request meanwhile without merging, because I'll just integrate that functionality differently.

I've pulled your changes in, and merged manually. This will go out on the next release (1.8.1) - it probably won't show here as merged because I had to manually copy the files to avoid conflicts with some other changes. Thanks for working on this!

Ok cool! Thx
mfg,
Philipp Holly

On Sep 21, 2016, at 1:46 AM, Gojko Adzic<EMAIL_ADDRESS>wrote:
I've pulled your changes in, and merged manually. This will go out on the next release (1.8.1) - it probably won't show here as merged because I had to manually copy the files to avoid conflicts with some other changes. Thanks for working on this!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

1.9.0 is now on NPM with these changes. see https://claudiajs.com/news/2016/09/21/claudia-1.9.0.html for more info


device: Add Kindle Scribe, breadcrumb and dailycal

Add breadcrumb and breadcrumb.dailycal templates for Kindle Scribe.
Renderings:

kscribe.breadcrumb.default.2024.pdf
kscribe.breadcrumb.default.dailycal.2024.pdf

Does anyone know how to fix it?


Int Terminal set to Git on Win launches external window (in addition to integrated).

VSCode Version: 1.21.0
OS Version: Windows 10

Steps to Reproduce:

Within User settings, set "terminal.integrated.shell.windows" to the path of your Git bash executable and save.
Now launch the Integrated Terminal from within an open folder in the editor. It will open it both as an integrated terminal and as an external window.
Sorry, I edited because I just realized smth else: if you then (that is, once you have both opened) try to close the external window of Git bash, it will also close the integrated one.

Let me know if I can provide any help or any further info, etc.

Does this issue occur when all extensions are disabled?: Yes/No
Yes, confirmed.

The git-bash.exe is not a command processor. You need to use bash. You find it in the under C:\Program Files\Git\bin\bash.exe`.


Regression(?) TOS not accepted.

Hello,
I'm not sure if this version of the map accepted the TOS automatically for you as PokemonGo-Map used to do for you but atm the Terms of Service are not accepted automatically when adding clients to the application. This leads to 'fresh accounts' not working at all, you just get a bunch of errors in the developer tools -> console.
Logging into the game on the same accounts, accepting the Terms of Service and then starting up the server does work.

Does anyone use the same device they play on to accept the TOS to activate the worker accounts?  I used to be able to do this through an emulator but this does not work any longer and I am hesitant to use my phone to register workers.  Any advice or suggestions would be greatly appreciated.

I got an old android phone I use to catch the first mon with etc. Sucks to have to physically log in etc to each account but fortunately I catch 3-4 mons on each account and they have not had any problems since.

I also use a secondary device to activate the account after they've successfully banned both the Bluestacks and Nox options. If I recall correctly in the early days it was mentioned that the IMEI gets sent along and thus  they could ban your entire device permanently if they wanted to - I would indeed advice you not to use the device you normally play on.
Either borrow a phone from someone who doesn't play or use an old device you no longer actively use.

Thanks for the advice, I will definitely not use my phone to activate the accounts,  I just tried to using an old phone but I could not download the app due to the phone being too outdated I guess.  I may try looking into purchasing a really cheap phone to try to have someone else activate an account for me as I can't wait to get the radar back up and working.

You can try sideloading the pokemon app. I have an old phone (galaxy s3) that I use for this purpose and this is what I had to do. I think as long as you're on 4.4 the app will work (although it crashes a lot on this phone).
Alternatively you can try using pokealert on the old phone, which will accept the TOS and catch the starter pokemon for you.

Thanks, I will try sideloading before I buy a new phone,  I did borrow a friends phone to activate one worker just to verify the new installation and I am up and running but do need to add some workers now.
thanks all


Image editing screen feels under designed

When editing an image, the screen feels under designed, including tight field tittles, confusing layout and unstyled buttons.

Relates to #4055 and #2339 (my comment about focal point UI)

Here is a layout that should make this screen clearer and more usable on smaller desktop viewports. The idea is we use the 'Replace' link in place of the default 'Choose file' UI element, opening the file choose file dialog.
The styling on the 'File' field is to be consistent with the approach outlined on #4055


No Robots settings for pages created before plugin was installed

Not sure if this is actually a bug or intended:
On pages that were created BEFORE I installed the plugin, the Robots settings are not automatically set to Default, which is why an error message pop ups when trying to update and save those pages. I know this is the default Kirby behavior, but it's quite confusing for my clients. Maybe this can be solved with a hook?
Loving the plugin, by the way!

I'd accept a migration script for Kirby CLI that solves the issue as PR, see https://github.com/tobimori/kirby-seo/issues/30#issuecomment-1672957250

I'll give this a crack when I get a chance.

Note to myself: Maybe there's a way to solve this easily with a page.save:before hook.

After looking at it again, to my understanding this idea is impossible to solve with hooks, because validation always occurs before running the hook which will prevent running the hook if the fields are not set yet and the page is not a draft.


"Description"  should have word wrap limit on main page

Steps to Create -

Add long description
UI shows up all description on main page it should be formatted in some limited word wrap

@naina-verma great catch! Is this the title or the description? The description should not display in the list view. If this is the title, it should only be one line of say 62 characters mx and then truncate, when displaying in the list. There should be a finite distance between the right side of the title and area between the next element to the right of it in the list, so that when the control re-sizes, the text truncates in a proportional way. Does this make sense? Getting this feedback in quick, so lmk if it doesn't and I can get you more info.

@Mgranfie ,
I would suggest limited number of work wrap should be better ,as title displays limited words on main page similarly Descriptions should be displaying 62(max) words and append (... Dots ) at the end of description for continue reading.

@naina-verma I think we are saying the same thing? Let me confirm...

The description should not show in the list view.
The Title should show.
The Title should display enough characters to always show at least "30" characters and then truncate with "...".
The title should display enough characters to leave "60" pixels between the end of the title and the first icon on the right.

These numbers are loose, trying to get the concept across and how resize will work. I have attached a couple of files. LMK if these make sense...

@Mgranfie this issue was raised on the current UI (http://demo.almighty.io/#/work-item-list).
Naina is referring to the description field. We have enabled two fields for quick add - title and description.
It is interesting on how users are entering the PDD on the current UI. The title is a combination of PDD ID, type, and brief description. A detailed description of the PDD item is captured under the description field.
Again this page may get invalidated based on the UX that is defined by your team.
We can keep this issue in mind when defining the description experience

if description is included in the list view how would it behaves
how does the description field behave in the detailed view
etc

@naina-verma please see the designs located here:
https://github.com/almighty/almighty-ux/issues/14
The designs are not too detailed, so please do ask away... I hope the sketches help, to start.

@naina-verma description should not display in the list.


[VL] Add shuffle writer type to ColumnarExchange display string

To distinguish between the hash and sort shuffle writer types more clearly, add "hash" or "sort" to the operator's display string, and remove [id=#$id] as it's the same as [plan_id=#$id] in Exchange

Thanks! Just a little nit.


Performance and documentation updates

Small fix to the SAFE_LOG macro.
Small update per Tom's request to identify the project as a prototype.
Big update to clean up the tinyscheme interpreter.
Big performance boost.

make test in docker failed (while running run-tests): screen logs as follows:
run-tests.sh: run unit tests for python, common, contracts and eservice
run-tests.sh: run unit tests for python package
run-tests.sh: run unit tests for common library
run-tests.sh: run unit tests for eservice
run-tests.sh: run unit tests for contracts
run-tests.sh: start enclave and provisioning services
run-tests.sh: start tests without provisioning or enclave services
run-tests.sh: start request test
run-tests.sh: start request test with tampered block order, this should fail
[02:20:59 ERROR   pdo.eservice.pdo_helper] send_to_contract failed; <class 'ValueError'>, ('',)
[02:20:59 WARNING pdo.contract.request] contract invocation failed;
[02:20:59 ERROR   pdo.test.request] enclave failed to evaluation expression; contract invocation failed
run-tests.sh: start integer-key contract test
run-tests.sh: start mock-contract contract test
run-tests.sh: start key value store test
run-tests.sh: start memory test
run-tests.sh: start tests with provisioning and enclave services
run-tests.sh: start storage service test
run-tests.sh: start request test
run-tests.sh: start integer-key contract test
run-tests.sh: start key value store test
run-tests.sh: start memory test
run-tests.sh: start pdo-create and pdo-update tests
run-tests.sh: create the contract
export CONTRACTID=jbTnMy/ePC2Enotii9GOg7RFcW5UsLb5pvgT4qKyWC0=
run-tests.sh: increment the value with a simple expression 15 times, querying enclaves in round robin
run-tests.sh: contract has the wrong value (10 instead of 11) for enclave 3
run-tests.sh: shutdown services
Makefile:79: recipe for target 'test-with-no-build' failed
make: *** [test-with-no-build] Error 111

make test in docker failed (while running run-tests): screen logs as follows:
..

Interesting, i could run 'make -C docker test' succesfully.  But i've seen the 10 instead of 11 error before, can't remember exactly when, though.

you need to rebuild completely.
the old scheme packages were updated.
On Tue, Apr 16, 2019 at 12:11 PM prakashngit<EMAIL_ADDRESS>wrote:

@prakashngit commented on this pull request.
pdo-shell script with exchange contract fails in this PR. I noticed this
after rebasing with 178, and while testing for db. This used to work before.
All services are up. I run ./scripts/set-up.sh in contracts/exchange.
Following is the logs:
create the asset type for red marbles
created type "LcvB/Vjjl10f3LNVTMlP7afgu7NIrjm512TK2Ujogfs="
create the red marble vetting organization
created the vetting organization
create red marble issuers
ERROR: method evaluation failed; eval: unbound variable: call/cc
create the asset type for green marbles
created type "m5nCR3y8pefOvT+uNYhy9jFF1MEcFYpI3Sy86jLStMg="
create the green marble vetting organization
created the vetting organization
create green marble issuers
ERROR: method evaluation failed; eval: unbound variable: call/cc
issue 10 green marbles to user1
ERROR: method evaluation failed; ledger has not been initialized
issue 20 green marbles to user2
ERROR: method evaluation failed; ledger has not been initialized
issue 30 green marbles to user3
ERROR: method evaluation failed; ledger has not been initialized
issue 40 green marbles to user4
ERROR: method evaluation failed; ledger has not been initialized
issue 50 green marbles to user5
ERROR: method evaluation failed; ledger has not been initialized
issue 60 red marbles to user6
ERROR: method evaluation failed; ledger has not been initialized
issue 70 red marbles to user7
ERROR: method evaluation failed; ledger has not been initialized
issue 80 red marbles to user8
ERROR: method evaluation failed; ledger has not been initialized
issue 90 red marbles to user9
ERROR: method evaluation failed; ledger has not been initialized
issue 100 red marbles to user10
ERROR: method evaluation failed; ledger has not been initialized
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/hyperledger-labs/private-data-objects/pull/177#pullrequestreview-227391473,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAbEULEZbremTGqC17O-bGIdxQh6QB-1ks5vhiBmgaJpZM4ctBYg
.

ah... we do need to remove the continuations from the exception package.
poo.
will update.
On Tue, Apr 16, 2019 at 12:23 PM Mic Bowman<EMAIL_ADDRESS>wrote:

you need to rebuild completely.
the old scheme packages were updated.
On Tue, Apr 16, 2019 at 12:11 PM prakashngit<EMAIL_ADDRESS>wrote:

@prakashngit commented on this pull request.
pdo-shell script with exchange contract fails in this PR. I noticed this
after rebasing with 178, and while testing for db. This used to work before.
All services are up. I run ./scripts/set-up.sh in contracts/exchange.
Following is the logs:
create the asset type for red marbles
created type "LcvB/Vjjl10f3LNVTMlP7afgu7NIrjm512TK2Ujogfs="
create the red marble vetting organization
created the vetting organization
create red marble issuers
ERROR: method evaluation failed; eval: unbound variable: call/cc
create the asset type for green marbles
created type "m5nCR3y8pefOvT+uNYhy9jFF1MEcFYpI3Sy86jLStMg="
create the green marble vetting organization
created the vetting organization
create green marble issuers
ERROR: method evaluation failed; eval: unbound variable: call/cc
issue 10 green marbles to user1
ERROR: method evaluation failed; ledger has not been initialized
issue 20 green marbles to user2
ERROR: method evaluation failed; ledger has not been initialized
issue 30 green marbles to user3
ERROR: method evaluation failed; ledger has not been initialized
issue 40 green marbles to user4
ERROR: method evaluation failed; ledger has not been initialized
issue 50 green marbles to user5
ERROR: method evaluation failed; ledger has not been initialized
issue 60 red marbles to user6
ERROR: method evaluation failed; ledger has not been initialized
issue 70 red marbles to user7
ERROR: method evaluation failed; ledger has not been initialized
issue 80 red marbles to user8
ERROR: method evaluation failed; ledger has not been initialized
issue 90 red marbles to user9
ERROR: method evaluation failed; ledger has not been initialized
issue 100 red marbles to user10
ERROR: method evaluation failed; ledger has not been initialized
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/hyperledger-labs/private-data-objects/pull/177#pullrequestreview-227391473,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAbEULEZbremTGqC17O-bGIdxQh6QB-1ks5vhiBmgaJpZM4ctBYg
.


Python support

An alternative approach to https://github.com/cloudflare/workers-sdk/pull/4896
What this PR solves / how to test:
Compared to #4896, this leans more on Wrangler's setup for --no-bundle JS workers, and treats Python workers as a special case of --no-bundle workers. It:

Ensures that python modules are properly supported throughout the --no-bundle pipeline
Turns on --no-bundle for Python workers, as well as adding a default Python module rule

This has a couple of benefits—notably saving python source files will trigger a workerd restart, and multiple python files which import each other are supported (there appears to be a workerd bug with imported nested python modules, so that isn't supported)
This PR also adds basic support for a requirements.txt file for python workers
Author has addressed the following:

Tests

[x] Included
[ ] Not necessary because:

Changeset (Changeset guidelines)

[x] Included
[ ] Not necessary because:

Associated docs

[ ] Issue(s)/PR(s):
[ ] Not necessary because:

pnpm run --filter wrangler start dev $PWD/index.py --compatibility-flag experimental

@dom96 where are you running this? Is index.py in the root of the Wrangler repo?

@penalosa it's in the root of the workers-sdk repo

@penalosa it's in the root of the workers-sdk repo

Ah, that'll probably be it then. What happens if you try to run the fixture in fixtures/python-worker or add an index.py file to a new folder?

@penalosa ahh, that works. Thanks!


How is client migration managed?

I am working on using QUIC in a cloud environment where migrations occurred frequently.
I have been running some tests using your implementation where the client, given as example in the library, is connected to the public server:
http3-test.litespeedtech.com:4433
The client runs in a Mac OS and it has been modified in order to perform a cycle of a number of the same HTTP GET requests and a sleep phase between each of them. The connection to the server is closed after the last HTTP request.
The migration of the client is performed switching the access point to which the laptop is connected from the normal adsl wifi used inside the house to a wifi provided by a mobile device using hotspot. The laptop, and so the client, changes the public address and the migration is handled by the two endpoints.
I print the frames and the information inside them in every datagram that the client sends/receives in order to check how the two endpoints handle the migration and I find out that the client receives three different path challenge frames in three different datagrams for the same path (same path ID) but with different challenges inside each of them, for each of them it responses with a path response frame.
Another thing that happens is that the client changes the source ID.
I read the draft and find out that the server can send multiple path challenge in order to avoid problems derived from the possibility of packet loss; but with the same path challenge and the client has to reply only to the first one it receives.
There is no section that says something about multiple path challenge frames (and so multiple path validation) for the same path during a migration.
Instead the change of the source ID of the client is conformed with the section 9.5 of the draft for privacy reason.
My question is why the client receives these three frames and not just one. Thanks very much.

the client has to reply only to the first one it receives.

This is incorrect.  The client (or server -- either endpoint) MUST respond to a path challenge.  In Section 8.4:
   On receiving a PATH_CHALLENGE frame, an endpoint MUST respond
   immediately by echoing the data contained in the PATH_CHALLENGE frame
   in a PATH_RESPONSE frame.

When lsquic detects a new path, it sends a path challenge.  Path challenges do not follow a normal packet loss logic.  This is because the path is new and we don't know anything about it.  A path challenge is sent until response is received using exponential backoff: 25ms, 50ms, 100ms, and so on.  The code is here:
https://github.com/litespeedtech/lsquic/blob/v2.19.4/src/liblsquic/lsquic_full_conn_ietf.c#L4172L4173

Thanks a lot for the explanation. I get now what I misunderstood from the draft.

A path challenge is sent until response is received using exponential backoff: 25ms, 50ms, 100ms, and so on.

So if I understand correctly, in my case, the client receives three different path challenge frames because when the server detects a new path it sends the first path challenge frame; then, before the server processes the path response frame in reply to its first path challenge, the timer fires two different times and so each time the server sends a new path challenge frame for the same path.
When the server processes the path response frame in reply to its first path challenge it unsets the timer and so no other path challenge frames are going to be sent.
The client instead immediately replies to each path challenge frame received echoing the data contained.
And I guess this behavior is the one explained in the last paragraph of the Section 9.4

   An endpoint might set a separate timer when a PATH_CHALLENGE is sent,
   which is cancelled if the corresponding PATH_RESPONSE is received.
   If the timer fires before the PATH_RESPONSE is received, the endpoint might send a new
   PATH_CHALLENGE, and restart the timer for a longer period of time.

Yes, this is exactly right.


Refactor syncing, invalid media on mobile

Summary of Changes

Introduces a TokenStateManagerProvider that's modeled similarly to web. It's a global context that keeps track of errored and syncing tokens.
Introduces a TokenFailureBoundary that's modeled similarly to web. It handles:

Automatic polling for Syncing tokens
Default fallbacks: TokenPreviewErrorFallback and TokenPreviewLoadingFallback

All instances of ReportingErrorBoundary have been migrated to TokenFailureBoundary. We should be using the latter moving forward.
getVideoOrImageUrlForNftPreview has been fully deprecated and replaced with getPreviewImageUrls or useSinglePreviewImage. We should use the latter moving forward
ensure syncing tokens appear in notications (important for recently minted tokens)
ensure syncing or errored tokens are pressable to create a post (important for recently minted tokens)
at the raw asset display level, ensure onError is passed and uses markTokenAsFailed from new token state context. this fixes the infinite loading displays and provides the user with a more accurate error.

Not handled in this PR
This PR focuses on ensuring invalid or syncing tokens are wrapped in a proper boundary and does not crash the app. The following tasks are not handled in this PR, and will be addressed in fast-follows
P0

responsive design for various sizes (currently there's a bug where the text overflows for tiny previews)
test end-to-end minting flow on testnet, starting from the Notifications screen

unhandled case
unhandled case

P1

ability to refresh errored / invalid tokens like web
internal documentation of new components, usage for team

P2 and below

shimmer states where tokens are rendered
low-priority views or components that are unlikely to display a loading or errored NFT (e.g. PFPs, trending gallery cards, etc.)

Demo or Before/After Pics
Will improve these in a subsequent PR, but this is what it looks like for now

Picker
Post Preview
Feed

Edge Cases
List any common edge cases that you have considered and tested.
Testing Steps
Provide steps on how the reviewer can test the changes.
Checklist
Please make sure to review and check all of the following:

[ ] I've tested the changes and all tests pass.
[ ] (if web) I've tested the changes on various desktop screen sizes to ensure responsiveness.
[ ] (if mobile) I've tested the changes on both light and dark modes.

one small thing before merging, noticed that the forced square ratio made portrait and landscape assets overflow outside its container so I removed the aspect-square class from the wrapping View around NftDetailAsset in these 3 places:
PostTokenPreview
NftDetailScreenInner
UniversalNftDetailScreenInner
hope the aspect-square isn't super important for a case im not thinking of - I didnt notice any major issues after a quick test. maybe affects virtualization? either way I figured we could improve in a follow up if needed, otherwise the detail page and composer looked a bit broken for non square images so this change seemed worth making before merging this!

PostTokenPreview
NftDetailscreenInner (portrait)
NftDetailscreenInner (landscape)

||||


fix: 🐛 build bug

I wanted to send a PR to the fork repository, but I made a mistake, so I'm closing it. Thank you.


Hi, can you share the training code?

Please refer to https://github.com/Shiaoming/ALIKE/raw/main/assets/ALIKE_code.zip.


TypeError: mime.lookup is not a function

This package erroneously set the semver range of the mime package to >=1.2.6. mime has been completely rewritten from version 2.0 and its api is different. Also, it requires Node 6+.
After failing to contact mikeal about this, I have forked this package and published it to npm with mime pinned properly to ^1.x.x instead.
If anyone needs it, it's here:
https://www.npmjs.com/package/filed-mimefix
https://github.com/andreialecu/filed
I'll be lightly maintaining it, if required.

Thank you!


User inputs dataset name

[x] Validate the dataset name doesn't have any spaces or special characters.
[x] Calls api/v1/dataSetName to pass the name to the server.
[x] Server side validation of name (will be used as the table name in SQL db)

:tada: This issue has been resolved in version 1.7.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


geo_near Sorting

Am I doing something wrong? It seems that I geo_near automatically always sorts by distance. I'd like to be able to sort by other fields:
@appointments = Appointment.desc(:created_at).geo_near(mycity.coords, :max_distance => @distance, :unit => :mi, :spherical => true)
This always sorts by distance, not created_at

You are using the wrong method.
GeoNear will always sort by distance.
River.where(:source.near => {:point => [-73.98, 40.77], :max => 5})
is the filter


Please update test-and-release and add node 20 tests

Please update test-and-release.yml and add tests for node 20.
Unless you know that your adapter does not work with node 20 please extend tests to include node 20 as node 20 has been released as official version now
If you adapter hat problems with node 20, please consider fixing them in the near future

done


How to Take a Screenshot at failed step in Nunit Framework

Can someone help me how to take screenshot at failed step in Nunit Framework test case
Currently I can take screenshot at the given line

Hi @dbhimar,
Not part of this project but I recently needed to do something very similar and looking at the following URLs helped :
https://docs.nunit.org/articles/nunit/writing-tests/TestContext.html
https://docs.nunit.org/articles/nunit/writing-tests/setup-teardown/index.html
Here is a pretty straightforward example:
public class Tests : PageTest
{
    [TearDown]
    public async Task TakeScreenshotOnFailure()
    {
        if (TestContext.CurrentContext.Result.Outcome == ResultState.Error)
        {
            await Page.ScreenshotAsync(new()
            {
                Path = "screenshot.png",
            });
        }
    }

    [Test]
    public async Task RandomlyCaptureScreenshot()
    {
        await Page.GotoAsync("https://playwright.dev");

        if (TestContext.CurrentContext.Random.Next(1, 100) % 3 == 0)
        {
            throw new Exception("This will happen randomly");
        }
    }
}

Thank you @RuaanKruger, we're working on supporting this feature natively and its tracked in this issue: https://github.com/microsoft/playwright-dotnet/issues/2214

@RuaanKruger  Thanks, but I want to take screenshot at failure statement only

@mxschmitt Thank you for the headsup

Folding into https://github.com/microsoft/playwright-dotnet/issues/2214 since it includes screenshot on failure. (I can't make promises, but I hope to be able to ship this feature in 1.27)


Issue/3885 to from int (#3953)

Pull request opened by the merge tool on behalf of #3953

Pull request rejected by merge tool. The tests for this branch did not succeed.

Merged into branches iso5 in a5c49df0c44dab57a9bea0e137702ae0f9d72ee5


Question: Not printing line number on error

Hi I ran the tracing sample but it was not printing the line number. This is my current output.
INFO[0001] opening                   app=myapp env=prod path=Readme.md
 ERROR[0001] opening                   app=myapp duration=22.987µs env=prod error=open Readme.md: no such file or directory path=Readme.md
  INFO[0002] opening                   app=myapp env=prod path=Readme.md
 ERROR[0002] opening                   app=myapp duration=8.866µs env=prod error=open Readme.md: no such file or directory path=Readme.md

My code is  (taken from the tracing examlple)
package main

import (
	"os"
	"time"

	"github.com/apex/log"
	"github.com/apex/log/handlers/text"
)

func work(ctx log.Interface) (err error) {
	path := "Readme.md"
	defer ctx.WithField("path", path).Trace("opening").Stop(&err)
	_, err = os.Open(path)
	return
}

func main() {
	log.SetHandler(text.New(os.Stderr))

	ctx := log.WithFields(log.Fields{
		"app": "myapp",
		"env": "prod",
	})

	for range time.Tick(time.Second) {
		_ = work(ctx)
	}
}

go version go1.8.3 darwin/amd64

I have the same question about printing filename and line number. I tried stack sample to show filename and line number and it does not work.
Here is my sample code:
package main

import (
	"github.com/apex/log"
	"github.com/apex/log/handlers/cli"
	"github.com/pkg/errors"
)

func main() {
	log.SetHandler(cli.Default)

	ctx := log.WithField("filename", "")

	for range time.Tick(time.Millisecond * 200) {
		for range time.Tick(time.Millisecond * 200) {
			log.Info("upload")
			log.Info("upload complete")
			log.Warn("upload retry")
			ctx.WithError(errors.New("unauthorized")).Error("Why no line number?")
		}
	}


[Bug] Enhance Log Formatting Documentation

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
Per documentation from https://docs.getdbt.com/reference/global-configs/logs#log-formatting

If the value of this config is json, dbt will output fully structured logs in JSON format; otherwise, it will output text-formatted logs that are sparser for the CLI and more detailed in logs/dbt.log.

I propose to add all allowed values as well as specifying the default one.
Similar to https://docs.getdbt.com/reference/global-configs/logs#log-level

This is a more flexible alternative to the --debug flag. The available options for the log levels are debug, info, warn, error, or none.

Expected Behavior
Unambiguous and clear documentation
Steps To Reproduce
Not applicable
Relevant log output
Not applicable

Environment
Not applicable

Which database adapter are you using with dbt?
No response
Additional Context
Documentation only

Thanks for reaching out @iamtodor !
https://github.com/dbt-labs/docs.getdbt.com is our repository for our documentation website, so I've transferred this issue accordingly.
We haven't had much other feedback about adding an "Open" button that links to our documentation issue templates, but that would be easy to do without much downside.
It would be just adding a snippet like the following in github/ISSUE_TEMPLATE/config.yml:
  - name: Documentation
    url: https://github.com/dbt-labs/docs.getdbt.com/issues/new/choose
    about: Problems and issues with dbt documentation

I opened https://github.com/dbt-labs/dbt-core/pull/10239 within the dbt-core repo to add this to the issue types.


please update the ARM template to be fully executable

[Enter feedbacplease update the ARM template to be fully executable

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

ID: d7e900ff-163f-b325-827d-4340e8901cd2
Version Independent ID: d21f588f-eff8-0c9b-d44f-1842fa5f3922
Content: Deploy container image from Azure Container Registry using a managed identity - Azure Container Instances
Content Source: articles/container-instances/using-azure-container-registry-mi.md
Service: container-instances
GitHub Login: @tomvcassidy
Microsoft Alias: tomcassidy

@porrascarlos802018
Thanks for your feedback! We will investigate and update as appropriate.

@porrascarlos802018
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

@porrascarlos802018 I couldn't reproduce this issue. It's too vague for me to tell what the problem is, but I could execute the ARM template.
If you're still encountering this issue, please make another issue with more specific information so I can address the problem.
Thank you. #please-close


Config failed: Could not log in to ElectroluxStatus

Hi, since today the Intigrations config failed with an error:
Could not log in to ElectroluxStatus, 429, message='', url=URL('https://api.eu.ocp.electrolux.one/one-account-authorization/api/v1/token')
What is wrong?

429 -> Too Many Requests

Yes you should wait a little and confirm that it is still working through the app

I get Unauthorized for the last couple of days.
_connect(), ClientError: 401, message='Unauthorized', url=URL('https://api.eu.ocp.electrolux.one/one-account-authorization/api/v1/token')

This happens randomly, especially when you restart HA frequently
Does it still work with the Electrolux app ?

This happens randomly, especially when you restart HA frequently
Does it still work with the Electrolux app ?

I can log into the Electrolux app with my user but the machine looks to be offline in the app.

It is strange taht I see Offline in the app and Connectivity staus as disconnected in the integration but I can see otyher sensors and I can use the controls. For example to change the program, even when the connextivity status is disconnected.
I opened a ticket towards Electrolux to check why I see the status as Offline in their app.

It is strange that you could log into the app, maybe the cookie is still valid, but anyway I guess that the server refuses the connection whatever it comes from the app or the integration with your login.
I guess that your account has been locked. I think you can unlock by resetting your password.
Both integration & app use the same API to get info. This is the problem with cloud integrations : your appliance is usually on the same network as your HA or app, but it has to go through their server to work...

It is strange that you could log into the app, maybe the cookie is still valid, but anyway I guess that the server refuses the connection whatever it comes from the app or the integration with your login.
I guess that your account has been locked. I think you can unlock by resetting your password.
Both integration & app use the same API to get info. This is the problem with cloud integrations : your appliance is usually on the same network as your HA or app, but it has to go through their server to work...

I didn't do any action and it is working now. Looks like it was an issue on the server side.

It is strange that you could log into the app, maybe the cookie is still valid, but anyway I guess that the server refuses the connection whatever it comes from the app or the integration with your login.

I guess that your account has been locked. I think you can unlock by resetting your password.

Both integration & app use the same API to get info. This is the problem with cloud integrations : your appliance is usually on the same network as your HA or app, but it has to go through their server to work...

I didn't do any action and it is working now. Looks like it was an issue on the server side.

Hi,
I think there was a server side issue this morning. Our washing machine was offline in HA but also in the AEG app. My instance in HA recovered by itself around 11:43 this morning.

I close the issue as it is not related to the integration


Merge commons master to browse-commons-via-app branch

Description
I have updated my local master from commons master and merged it to a new branch taken out from browse-commons-via-app branch.
It will update the browse-commons-via-app branch with the new code in master in main repository.
I have fixed the conflicts.

Codecov Report

Merging #1632 into browse-commons-via-app will decrease coverage by 0.01%.
The diff coverage is 0%.

@@                    Coverage Diff                    @@
##           browse-commons-via-app   #1632      +/-   ##
=========================================================
- Coverage                    3.75%   3.74%   -0.02%
=========================================================
  Files                         158     159       +1
  Lines                        7965    7992      +27
  Branches                      735     737       +2
=========================================================
  Hits                          299     299
- Misses                       7649    7676      +27
  Partials                       17      17

Impacted Files
Coverage Δ

...w/commons/contributions/ContributionsActivity.java
0% <ø> (ø)
:arrow_up:

...mmons/contributions/ContributionsListFragment.java
0% <ø> (ø)
:arrow_up:

.../java/fr/free/nrw/commons/auth/SessionManager.java
15.38% <0%> (-1.29%)
:arrow_down:

...n/java/fr/free/nrw/commons/auth/LoginActivity.java
0% <0%> (ø)
:arrow_up:

...rw/commons/mwapi/ApacheHttpClientMediaWikiApi.java
4.69% <0%> (-0.03%)
:arrow_down:

.../fr/free/nrw/commons/widget/PicOfDayAppWidget.java
0% <0%> (ø)

...java/fr/free/nrw/commons/upload/UploadService.java
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Visualize detailed coverage information on GitLab

Thanks a lot for this package, it's been very useful to set up a package on GitLab.!
There is one thing I couldn't figure out though. I'm running "code coverage" after testing, and I got the corresponding code on the gitlab-ci.yml config file:
.coverage:
  coverage: /Test coverage (\d+\.\d+%)/
  after_script:
    - |
      julia -e '
        using Pkg
        Pkg.add("Coverage")
        using Coverage
        c, t = get_summary(process_folder())
        using Printf
        @printf "Test coverage %.2f%%\n" 100c / t'

However, this just gives an overall number. Is there a way to visualize this coverage information, that is, file by file, line in codecov GitHub hosted packages? Or is it a limitation of GitLab that one has only access to a final number (overall coverage percentage)?
EDIT: please feel free to close if this is off-topic and coverage visualization is not done via the gitlab-ci.yml config file that PkgTemplates generates.

Is there a code coverage service like Codecov or Coveralls that supports GitLab? Because that's what we're looking for here.

After a very brief search it seems that Codecov does support GitLab, so that's worth looking into.

Ah, you are right! Actually, there is an example julia repo in GitLab here https://gitlab.com/tkpapp/GitlabJuliaDemo.jl that has codecov enabled.

I think the best way forward is to add actual GitLab support to Coverage.jl, since GitLab is officially supported by Codecov. Adding such support looks simple, I just need to test some things before submitting a PR.

My Codecov experiments have so far been mostly failures, Codecov gave me HTTP errors when I tried to use my Coverage.jl fork, so I am probably setting some fields incorrectly. Then I tried to use their agnostic Bash uploader with an LCOV file, which kind of worked but had some missing info. I think with some more effort we can make it work, but I'll try another day. I'm also going to look into Coveralls which claims to support GitLab.


Add QR Code "scan to share" button that redirects to OID4VP flow

This PR adds a button to the wallet home view (if there are any rawCredentials on the screen) which redirects to the OID4vp flow. The button will not appear if there are no credentials added yet.
I also bumped the CompileSDK version to match the newest version of Android Studio.
Note: This is the Android version of this PR: https://github.com/spruceid/mobile-sdk-ios-app/pull/21

Question: what happens currently when the QR-code is scanned?

Question: what happens currently when the QR-code is scanned?

It only redirects to a new component that will handle the OID4VP integration, but the OID4VP flow will be integrated in another PR

Question: what happens currently when the QR-code is scanned?

It only redirects to a new component that will handle the OID4VP integration, but the OID4VP flow will be integrated in another PR

https://github.com/spruceid/mobile-sdk-kt/pull/37 contains a handler to navigate to an OID4VP view.