[BUG] With new version the path to config.yaml is wrong

Just updated to the last version, but due to the changes of the paths "/config" instead of "/app" ist no more working. I get the error
====================================================
To support this project, please consider sponsoring.
https://github.com/sponsors/mandarons
https://www.buymeacoffee.com/mandarons

User UID:    911
User GID:    911
====================================================

Loading config from /app/config.yaml ...
Loading config from /app/config.yaml ...
2024-06-25 08:16:28,370 :: ERROR :: icloudpy.base :: base.py :: 186 :: Missing apple_id field
Loading config from /app/config.yaml ...
Loading config from /app/config.yaml ...
2024-06-25 08:16:37,033 :: ERROR :: icloudpy.base :: base.py :: 186 :: Missing apple_id field

** Press ANY KEY to close this window **

Using Docker on Unraid. When logging in to the console I can see there is still a default config.yaml located in /app which is used. I changed my docker config regarding the documentation from /app/config.yaml to /config/config.yaml. Seems that the app itself needs some additional parameters that the new location is working?!

Did you set the environment variable to correct config path ENV_CONFIG_PATH=/config/config.yaml?

@mandarons no, because this is not in the documentation ;)
anyway: just tried it with no effect. the error is still the same.

@mandarons here is the log output, changed a little bit:

====================================================
To support this project, please consider sponsoring.
https://github.com/sponsors/mandarons
https://www.buymeacoffee.com/mandarons

User UID:    911
User GID:    911
====================================================

Traceback (most recent call last):
  File "/lsiopy/lib/python3.11/site-packages/icloudpy/base.py", line 362, in _authenticate_with_token
    req = self.session.post(
          ^^^^^^^^^^^^^^^^^^
  File "/lsiopy/lib/python3.11/site-packages/requests/sessions.py", line 635, in post
2024-06-27 07:21:54,195 :: ERROR :: icloudpy.base :: base.py :: 186 :: Missing apple_id field
    return self.request("POST", url, data=data, json=json, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/lsiopy/lib/python3.11/site-packages/icloudpy/base.py", line 158, in request
    self._raise_error(code, reason)
  File "/lsiopy/lib/python3.11/site-packages/icloudpy/base.py", line 187, in _raise_error
    raise api_error
icloudpy.exceptions.ICloudPyAPIResponseException: Missing apple_id field

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/app/./src/main.py", line 7, in <module>
    sync.sync()
  File "/app/src/sync.py", line 77, in sync
    api = get_api_instance(
          ^^^^^^^^^^^^^^^^^
  File "/app/src/sync.py", line 42, in get_api_instance
    else ICloudPyService(
         ^^^^^^^^^^^^^^^^
  File "/lsiopy/lib/python3.11/site-packages/icloudpy/base.py", line 277, in __init__
    self.authenticate()
  File "/lsiopy/lib/python3.11/site-packages/icloudpy/base.py", line 346, in authenticate
    self._authenticate_with_token()
  File "/lsiopy/lib/python3.11/site-packages/icloudpy/base.py", line 368, in _authenticate_with_token
    raise ICloudPyFailedLoginException(msg, error) from error
icloudpy.exceptions.ICloudPyFailedLoginException: ('Invalid authentication token.', ICloudPyAPIResponseException('Missing apple_id field'))
Traceback (most recent call last):
  File "/lsiopy/lib/python3.11/site-packages/icloudpy/base.py", line 362, in _authenticate_with_token
    req = self.session.post(
          ^^^^^^^^^^^^^^^^^^
  File "/lsiopy/lib/python3.11/site-packages/requests/sessions.py", line 635, in post
2024-06-27 07:21:57,891 :: ERROR :: icloudpy.base :: base.py :: 186 :: Missing apple_id field
    return self.request("POST", url, data=data, json=json, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/lsiopy/lib/python3.11/site-packages/icloudpy/base.py", line 158, in request
    self._raise_error(code, reason)
  File "/lsiopy/lib/python3.11/site-packages/icloudpy/base.py", line 187, in _raise_error
    raise api_error
icloudpy.exceptions.ICloudPyAPIResponseException: Missing apple_id field

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/app/./src/main.py", line 7, in <module>
    sync.sync()
  File "/app/src/sync.py", line 77, in sync
    api = get_api_instance(
          ^^^^^^^^^^^^^^^^^
  File "/app/src/sync.py", line 42, in get_api_instance
    else ICloudPyService(
         ^^^^^^^^^^^^^^^^
  File "/lsiopy/lib/python3.11/site-packages/icloudpy/base.py", line 277, in __init__
    self.authenticate()
  File "/lsiopy/lib/python3.11/site-packages/icloudpy/base.py", line 346, in authenticate
    self._authenticate_with_token()
  File "/lsiopy/lib/python3.11/site-packages/icloudpy/base.py", line 368, in _authenticate_with_token
    raise ICloudPyFailedLoginException(msg, error) from error
icloudpy.exceptions.ICloudPyFailedLoginException: ('Invalid authentication token.', ICloudPyAPIResponseException('Missing apple_id field'))
Traceback (most recent call last):
  File "/lsiopy/lib/python3.11/site-packages/icloudpy/base.py", line 362, in _authenticate_with_token
    req = self.session.post(
          ^^^^^^^^^^^^^^^^^^
  File "/lsiopy/lib/python3.11/site-packages/requests/sessions.py", line 635, in post
2024-06-27 07:22:01,197 :: ERROR :: icloudpy.base :: base.py :: 186 :: Missing apple_id field
    return self.request("POST", url, data=data, json=json, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/lsiopy/lib/python3.11/site-packages/icloudpy/base.py", line 158, in request
    self._raise_error(code, reason)
  File "/lsiopy/lib/python3.11/site-packages/icloudpy/base.py", line 187, in _raise_error
    raise api_error
icloudpy.exceptions.ICloudPyAPIResponseException: Missing apple_id field

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/app/./src/main.py", line 7, in <module>
    sync.sync()
  File "/app/src/sync.py", line 77, in sync
    api = get_api_instance(
          ^^^^^^^^^^^^^^^^^
  File "/app/src/sync.py", line 42, in get_api_instance
    else ICloudPyService(
         ^^^^^^^^^^^^^^^^
  File "/lsiopy/lib/python3.11/site-packages/icloudpy/base.py", line 277, in __init__
    self.authenticate()
  File "/lsiopy/lib/python3.11/site-packages/icloudpy/base.py", line 346, in authenticate
    self._authenticate_with_token()
  File "/lsiopy/lib/python3.11/site-packages/icloudpy/base.py", line 368, in _authenticate_with_token
    raise ICloudPyFailedLoginException(msg, error) from error
icloudpy.exceptions.ICloudPyFailedLoginException: ('Invalid authentication token.', ICloudPyAPIResponseException('Missing apple_id field'))
Traceback (most recent call last):
  File "/lsiopy/lib/python3.11/site-packages/icloudpy/base.py", line 362, in _authenticate_with_token
    req = self.session.post(
          ^^^^^^^^^^^^^^^^^^
  File "/lsiopy/lib/python3.11/site-packages/requests/sessions.py", line 635, in post
2024-06-27 07:22:04,815 :: ERROR :: icloudpy.base :: base.py :: 186 :: Missing apple_id field
    return self.request("POST", url, data=data, json=json, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/lsiopy/lib/python3.11/site-packages/icloudpy/base.py", line 158, in request
    self._raise_error(code, reason)
  File "/lsiopy/lib/python3.11/site-packages/icloudpy/base.py", line 187, in _raise_error
    raise api_error
icloudpy.exceptions.ICloudPyAPIResponseException: Missing apple_id field

That's weird. Can you please post your config.yaml and Unraid app values? It is working fine in my Unraid.

@mandarons just found the problem: its not "ENV_CONFIG_PATH" but "ENV_CONFIG_FILE_PATH". There is a bug in the documentation.
It's correct in the documentation section "Installation using Docker Hub", but it's wrong in the section "Installation using docker-compose". :)

Ugh... sorry about that. I will fix it soon. Thanks for pointing it out.

@mandarons your welcome. keep up your great work, I love iCloud-drive-docker! 👍


[Developing/Frameworks] add LWC tab

This PR adds "LWC" tab to Frameworks. LWC is the framework of Carbon build and maintained by Carbon for Salesforce team. We had to develop this new framework of Carbon in order to support the need of products built on Salesforce platforms.
Changelog
New

lwc.mdx

Changed

frontmatter of all pages under Frameworks so LWC is added as a tab

Hey @carbon-design-system/design pinging to see if this can get an approval for merge. Or let me know if you have feedback! Thanks!


ColorNamed should be Copy/Clone

It's currently not possible to share the ColorNamed across multiple places consistently because the trait impls are missing. I think it should just be the case of adding the derive.

It might be also useful to derive Copy and Clone for other structures implementing Color trait: Rgb and Rgba.


Fix misspellings

connects to #253

:tada: This PR is included in version 4.0.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


IDVA6-1924: Updated parent pom

Short description outlining key changes/additions
Updated parent pom
JIRA Ticket Number
IDVA6-1924
Type of change

[ ] Bug fix
[x] New feature
[x] Breaking change
[x] Infrastructure change

Pull request checklist

[x] I have added unit tests for new code that I have added
[x] I have added/updated functional tests where appropriate
[x] The code follows our coding standards

An exhaustive list of peer review checks can be read here

CI: Security warnings found!


Recursive warning when a dependency is missing a dependabot configuration

Is there an existing issue for this?

[X] I have searched the existing issues

Feature description
One thing that could considerably helps with dependabot usage and spread would be to have a warning when a dependency is not using dependabot.
This could also help when evaluating whether or not to include a dependency in a software project. If I can quickly see the dependabot status of this project, then it is easy to asses if software updates are merged quickly into it.

Good suggestion.
If we fixed the badges again, then libs could more easily advertise their status:

https://github.com/dependabot/dependabot-core/issues/1912


Drop Laravel 5.x support

Going forward in 3.x we intend to drop support for Laravel versions older than 6.x (LTS).
This means dropping the currently supported versions 5.0-5.8 and we only support Laravel 6+ where 6.0 was released on September 3, 2019.
Usage is low enough that we think this can be done at this time: https://packagist.org/packages/laravel/laravel/stats#major/all.
Of course users of those Laravel versions can keep using 2.14.x and below like they are now.
For a bit of background when those versions lost support: https://laravelversions.com/en.
This is a draft for discussion and because of the big cleanup it needs another once over to make sure we removed all version checks and "hacks" to support these older versions.

@stayallive We should also update the README https://github.com/getsentry/sentry-laravel#laravel-version-compatibility


JSON output is enclosed in double array

When using daedalus with --json argument, the older version would produce something like this:
--- Found 1 results:
[ { "bb": 182
  , "i8_1": 33
  , "ul_1": 29320907
 }, { ... }
]

But the new version produces:
[ [ { "bb": 182
  , "i8_1": 33
  , "ul_1": 29320907
 }, { ... }
] ]

(older version for me is the build I did back at the beginning of March, I don't have the exact has of the version)
I'm happy that the first line (--- Found 1 results:) is now gone, but why the double array?

So technically this is a feature not a bug, although I can see it being annoying :)    In general, deadalus can deal with ambiguous grammars, so if a grammar is ambiguous you would get a list of possible results (e.g., try writing def Main = Match 'a' | Match 'a').  If it is not, which is usually the case, you get just a singleton list.   Since your grammar probably produces a list, and is not ambiguous you are getting the double list, which is kind of the equivalent of saying "found 1 result".
Dealing with ambiguous grammars is pretty complicated, so it would be nicer for both the code generator an the daedalus user if we could spot that a grammar is ambiguous statically, without having to run the parser.  Unfortunately, this is non-trivial for the very rich set of grammars supported by daedalus at the moment.  We are, however, working on an analysis that would, hopefully, work well for most common grammars, and once that's functional, we should be able to say ahead of time if the grammar is unambigous, or "possibly ambiguous".
In the shorter term, we could also do something like: only show the first result, and maybe print a warning if there was more than one result, if that would be more helpful?

Iavor: I understand. No need to change anything. I just needed to understand why there were nested arrays. For me it's just a matter of dealing with it (when using the output, if I detect two top-level elements I can warn of ambiguous grammar, otherwise take the first and only result).
Thanks for explaining. This is good.
Fab


Calling nix-env -qa results in failure on not-yet-built project

@olcai wrote on Feb 22, 2019 8:18am UTC:

While Mix to Nix is working well for building projects, I get an error while trying to use nix-env when a project has not been built yet.
We use nix-env to list all available derivations in our internal nix-overlay, so that we can make our CI server build each derivation in turn.
Now, if I create a dummy Elixir project using mix new, setup a default.nix according to the docs, and then call nix-env -f default.nix -qa --show-trace in that directory (without calling nix-build first), I get this:
error: while evaluating 'importElixir' at /nix/store/gz1a1xq552xg69r2iqsnk3hl4skdvslb-source/default.nix:240:18, called
 from /nix/store/gz1a1xq552xg69r2iqsnk3hl4skdvslb-source/default.nix:259:19:
while evaluating 'importJSON' at /nix/store/nh38qpbmmrli8w3zqv00jv120chf1biz-nixos-18.09.1819.76aafbf4bf4/nixos/lib/trivial.nix:237:16, called from /nix/store/gz1a1xq552xg69r2iqsnk3hl4skdvslb-source/default.nix:240:24:
cannot read '/nix/store/yhhb0ih007drznbwd76h8khywbp8pyk1-elixir-term.json', since path '/nix/store/4jv30jsybmwlw9pjay3cm2a15dxkj1ki-elixir-term.json.drv' is not valid, at /nix/store/nh38qpbmmrli8w3zqv00jv120chf1biz-nixos-18.09.1819.76aafbf4bf4/nixos/lib/trivial.nix:238:24

It looks like some kind of bootstrapping problem to me, since the drv-path doesn't exist yet when we try to import it. I'm not fully understanding what to do about it, however. Any pointers? Thank you!

@yegortimoshenko wrote on Feb 22, 2019 3:24pm UTC:

I would recommend something like:
nix-instantiate --json --eval --expr 'builtins.attrNames (import ./.)'

@olcai wrote on Feb 22, 2019 9:05pm UTC:

Ah, yes. Running nix-instantiate before will of course do the trick. Thank you for helping me out and answering questions at the nix-beginner-level.

@yegortimoshenko wrote on Feb 23, 2019 2:12am UTC:

Running nix-instantiate before will of course do the trick.

nix-instantiate,  by itself, won't build these paths. Mix to Nix depends on build during eval. So the way to resolve it depends on what you want to achieve.
If you want to use something in conjunction with nix-env specifically, you might have better luck with nix-build -A name 2> /dev/null || true before nix-env.
That said, unless you want to list dependencies, name/version, or other derivation metadata, you can just list attribute names and have CI using go through them using the command in previous comment, which is what I think Hydra does.
This should be probably fixed upstream in nix-env, reopening as a reminder.


global: change invenio-cli workflow (commands)

Text by @fenekku
After some thoughts:
It actually might be that we have been thinking about this incorrectly: there shouldn't be 2 parallel contexts for which each command is implemented. Maybe it's more a sequence of commands and --prod is really just the last one or two. Something like this:
+------------------+     +---------------------+   +-------------------+      +--------------------+         +--------------------------+       +---------------------------------+
|                  |     |                     |   |                   |      |                    |         |                          |       |                                 |
| invenio-cli init +---> | invenio-cli service +-> | invenio-cli setup +----> | invenio-cli server +-------> | invenio-cli containerize +-----> | invenio-cli server --containers |
|                  |     |                     |   |                   |      |                    |         |                          |       |                                 |
+------------------+     +---------------------+   +-------------------+      +--------------------+         +--------------------------+       +---------------------------------+

Then being clear about the workflow will help users understand the 2 main use cases:
1- I want to just see what InvenioRDM gives me out of the box: I go through invenio-cli init, invenio-cli containerize and invenio-cli server --containers so I can finally see the instance running with no configuration on my side.
2- I am ready to start configuring and iterating: I do the first commands only and in particular the first invenio-cli server (precise names are not important in my explanation). This way my development flow is faster and I can see my changes but at the cost of more installation locally (might need to have header files and so on...).
This would make the usage of the cli more clear, remove the need for us to implement weird / necessarily slow commands and provide a better experience overall. What do you think @ppanero ? (Not saying we should switch now either if we decide to go this way)

@fenekku Currently the CLI rellies on where the python modules are installed (i.e. if it is a --local or a --containers installation). The main issue being the setup and demo commands. There is a need to know to where to "forward" each one (i.e. use click_runner or launch a docker exec ...).
This is one more point to plead for a "heavier" but "full" dependencies installation. That way we could have setup and demo independent of where are the libraries (since the services are always on containers).
We could have two steps: install and build/containerize (names to be agreed), being both optional and compatible. The first one would install it locally (i.e. dev purposes), while the second one would "build" whatever is in the local code (note that if nothing has changed, meaning no install, the code would be the default one so it would still work).
PS: Not sure if we would need full "live reload" (watcher) inside the containers for templates/css if we go this way...


UI styles should be specifiable in a global style sheet

@dbrewster is this still relevant? It is a bit old, but we hadn't seen in grooming until today.


Enabling support to _json to no batched requests;

fix #98

Hey! Thanks for the PR. Unfortunately I don't really understand what you're trying to accomplish here. You reference #98 but that's also a PR. Why the _json key be used?

hi @benwilson512.
with a small adjustment (which I'll do PR later) in the lib https://github.com/jaydenseric/apollo-upload-client it is possible to make submissions of data without problems.
the changes in this PR is to make the behavior of not batched queries also support the _json. So the data are sent in the correct form, for send parameters (especially with depth properties) causes several problems and has many limitations.
example of data to be sent that does not work correctly:
{
  works: ["value1", "value2"],
  withTricksWork: {
    data: "value",
    array: ["..."]
  },

  arrayWithObjectWithMultipleKeysNotWork: [{ k1: "v1", k2: "v2"}, { k2: "v2", k1: "v1"}, ...]
}

My question is, why are not batched queries using _json param. at all and not the standard query and variables param?

why my application is not yet using batched query.
Because for the upload it is necessary to send through the multi-part the that has limitations to parsing and serialization.
If batched queries support _json why not batched queries also does not support, thus maintaining the standard.

The issue is there is already a standard for non batching multipart. You use query for the query and variables for variables, that way it's basically the same as regular POST or GET.
_json isn't really a standard, and in fact the PR you linked to provides "operations" because other than phoenix, it isn't really a normal thing to use.
I suppose my main question is, if you aren't batching, why can't you do 2 + n parts:
-- PART1--
query=mutation ($upload: Upload!) { upload(file: $file) }
variables={"upload":"foo"}
foo=#<file contents>

because de struct is some complex:
Dump of one my forms:
------WebKitFormBoundaryaTjxcVRmzSxSmQBy
Content-Disposition: form-data; name="_json"

{"query":"mutation CreateDocument($input: CreateDocumentInput!) {\n  createDocument(input: $input) {\n    clientMutationId\n    document {\n      id\n      insertedAt\n      __typename\n    }\n    __typename\n  }\n}\n","variables":{"input":{"clientMutationId":"createDocument:rg-e-cpf","content":"{\"rgFront\":{\"Número\":\"9839843748723\",\"Data de expedição\":\"2017-08-30\"},\"rgBack\":{\"Orgão emissor\":\"SSP\",\"Estado de emissão\":\"SP\"},\"cpf\":\"123.123.123-55\"}","attachments":[{"attachment":"input.attachments.0.attachment","fragment":"rgFront","contentType":"image/png"},{"attachment":"input.attachments.1.attachment","fragment":"rgBack","contentType":"image/png"},{"attachment":"input.attachments.2.attachment","fragment":"cpf","contentType":"image/png"}],"employeeId":"RW1wbG95ZWU6YTMzNmViMmQtMDg1OS00ZGVhLWJjNTgtNDg4MGFkN2I1YWE5","companyId":"Q29tcGFueTo3MmM2OTgwZi0zYzYyLTRkYjQtYTg0MS1mYzE4M2VmMDgyMDg=","key":"rg-e-cpf","completed":100,"status":"VALIDATION"}},"operationName":"CreateDocument"}
------WebKitFormBoundaryaTjxcVRmzSxSmQBy
Content-Disposition: form-data; name="input.attachments.0.attachment"; filename="RG.png"
Content-Type: image/png

------WebKitFormBoundaryaTjxcVRmzSxSmQBy
Content-Disposition: form-data; name="input.attachments.1.attachment"; filename="RG.png"
Content-Type: image/png

------WebKitFormBoundaryaTjxcVRmzSxSmQBy
Content-Disposition: form-data; name="input.attachments.2.attachment"; filename="RG.png"
Content-Type: image/png

------WebKitFormBoundaryaTjxcVRmzSxSmQBy--

Sure, but why can't you do something like this:
------WebKitFormBoundaryaTjxcVRmzSxSmQBy
Content-Disposition: form-data; name="query"
mutation CreateDocument($input: CreateDocumentInput!) {
  createDocument(input: $input) {
    clientMutationId
    document {
      id
      insertedAt
      __typename
    }
    __typename
  }
}

------WebKitFormBoundaryaTjxcVRmzSxSmQBy
Content-Disposition: form-data; name="query"
Content-Type: application/json
{"input":{"clientMutationId":"createDocument:rg-e-cpf","content":"{\"rgFront\":{\"Número\":\"9839843748723\",\"Data de expedição\":\"2017-08-30\"},\"rgBack\":{\"Orgão emissor\":\"SSP\",\"Estado de emissão\":\"SP\"},\"cpf\":\"123.123.123-55\"}","attachments":[{"attachment":"input.attachments.0.attachment","fragment":"rgFront","contentType":"image/png"},{"attachment":"input.attachments.1.attachment","fragment":"rgBack","contentType":"image/png"},{"attachment":"input.attachments.2.attachment","fragment":"cpf","contentType":"image/png"}],"employeeId":"RW1wbG95ZWU6YTMzNmViMmQtMDg1OS00ZGVhLWJjNTgtNDg4MGFkN2I1YWE5","companyId":"Q29tcGFueTo3MmM2OTgwZi0zYzYyLTRkYjQtYTg0MS1mYzE4M2VmMDgyMDg=","key":"rg-e-cpf","completed":100,"status":"VALIDATION"}}

------WebKitFormBoundaryaTjxcVRmzSxSmQBy
Content-Disposition: form-data; name="input.attachments.0.attachment"; filename="RG.png"
Content-Type: image/png

------WebKitFormBoundaryaTjxcVRmzSxSmQBy
Content-Disposition: form-data; name="input.attachments.1.attachment"; filename="RG.png"
Content-Type: image/png

------WebKitFormBoundaryaTjxcVRmzSxSmQBy
Content-Disposition: form-data; name="input.attachments.2.attachment"; filename="RG.png"
Content-Type: image/png

------WebKitFormBoundaryaTjxcVRmzSxSmQBy--

_json isn't a standard, I would like to move away from it completely. query and variables is.


Added new command for activity launcher directory

Initially, runAndroid.js pick a default path (i.e package + '.' + .MainActivity), which has a problem because existing android app have different project structure and most of the developer, maintain clean architecture in different directory
Example If suppose if '.MainActivity' is placed in 'activity' directory then react-native still don't have an option where explicitly provide activity launcher directory, So that I have to add another command where we can provide activity launcher directory by using the following command (i.e = react-native run-android --activityLauncherDir=.activity.xxx.yyy, it indicates your launcher activity present in - package.activity.xxx.yyy.MainActvity)

Motivation
Self-learning is a great motivation
Test Plan
(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work. Bonus points for screenshots and videos!)
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/react-native-website, and link to your PR here.)
Release Notes

Duplicate of #17816


Implemented react-router-redux + new Styles

Coverage increased (+0.08%) to 82.118% when pulling bbdb8b71ecc56e1790aa58dc84c2406be0c3feef on dev into 1b680ff912ea80b5cc2177e7a1712737a96b5376 on master.

Coverage increased (+0.08%) to 82.118% when pulling da0427e9bbd461f3ae18eb43f352820a8fcfca87 on dev into 1b680ff912ea80b5cc2177e7a1712737a96b5376 on master.

Coverage increased (+0.08%) to 82.118% when pulling aef6c6e2e8f4d0d115d31acbadc2f984f0b02c57 on dev into 1b680ff912ea80b5cc2177e7a1712737a96b5376 on master.


Link to AspectOS Forum Thread Goes to Old Thread

As above. Found at the bottom of the about page.

Fixed!


update nodejs images in the supported component catalog

User Story
As a developer I would like to use nodejs 12 images with all the features odo provides which includes experimental features like odo debug.
Acceptance Criteria

[ ] Basic features of odo should work correctly with new nodejs images (centos/nodejs-12-centos7, rhscl/nodejs-12-rhel7andnodeshift/centos7-s2i-nodejs`)
[ ] experimental features like odo debug should work correctly with new nodejs images
[ ] tests should all run against these new images and pass
[ ] It should show new nodejs images which are centos/nodejs-12-centos7, rhscl/nodejs-12-rhel7 and nodeshift/centos7-s2i-nodejs as supported images when ran odo catalog list components, But this should happen only when 3 ACs above are fulfilled.

Links

Feature Request: NA
Related issue: https://github.com/openshift/openshift-docs/pull/19597

/kind user-story

/area s2i

I would need to verify that all of these images work in a sample nodejs application and using debug mode as well.
After that I would open a PR on odo-init-image to add the images in the supported list then a similar PR on this Repo.

▶ oc get is nodejs -n openshift
NAME     IMAGE REPOSITORY                                                    TAGS                         UPDATED
nodejs   image-registry.openshift-image-registry.svc:5000/openshift/nodejs   10,10-SCL,8,8-RHOAR,latest   About an hour ago

▶ oc get is nodejs -n openshift
NAME     IMAGE REPOSITORY                                                    TAGS           UPDATED
nodejs   image-registry.openshift-image-registry.svc:5000/openshift/nodejs   10,12,latest   55 minutes ago

▶ oc version
Client Version: 4.4.0-0.ci-2020-02-18-230529
Server Version: 4.4.0-0.ci-2020-02-18-230529
Kubernetes Version: v1.17.1

The nodeshift images mentioned above are no longer supported since we've migrated to using the images from rhscl
For our community examples, we've also moved from centos to ubi

The nodeshift images mentioned above are no longer supported since we've migrated to using the images from rhscl
For our community examples, we've also moved from centos to ubi

How about existing 3.11 clusters? Are those somehow updated to deprecate those images?

The older images are not removed/deprecated. I check it but also verified by this comment https://github.com/openshift/openshift-docs/pull/19597#issuecomment-586220599

Also see this comment: https://github.com/openshift/openshift-docs/pull/19597#issuecomment-586220599

nodejs-8-rhel7 as well as both versions of rhoar-nodejs are no longer supported. While OpenShift does not update imagestreams in stable branches, that does not mean we should encourage further use of unsupported versions.

we need to resolve these issues https://github.com/openshift/odo/issues?q=is%3Aissue+is%3Aopen+label%3Anext-oc-version before we could add nodejs:12 as supported image

we need to resolve these issues https://github.com/openshift/odo/issues?q=is%3Aissue+is%3Aopen+label%3Anext-oc-version before we could add nodejs:12 as supported image

no, we need to resolve this first! Some of the issues will go away when nodejs images are marked as resolved.
We need to add nodejs images into supported images and test what issues will be fixed!


MonitorManager should accept perennial firing on transitions

Monitor Manager should accept perennial firing on transitions.
Given fired transition t0 is enabled.
When thread th0 fires transition t0 using perennial firing.
Then petri monitor shall not try to sleep th0.
And petri monitor should try to wake a thread from transition t0's queue.

TODO: define if all transition should tolerate perennial firing or if this is another label and it becomes a transition's property.
In case perennial firing is a transition's propery, firing interface should not change but return value should always be true for perennial transitions

Should perennial firing a timed transition send the thread to sleep on its own?


wishlist: ziti_stream upstream module for Nginx

The Nginx "stream" module is an example of what I'm dreaming of, e.g., "ziti_stream".  The "stream" upstream module is similar in function to the "http" upstream module, except that it's more generic and doesn't require the traffic to be HTTP.
This new upstream module for Nginx would proxy incoming traffic from normal network ingresses to upstream destinations on the Ziti overlay.

relevant forum topic

The proposed module proxies incoming streams to Ziti overlay services. Because ngx_ziti_upstream_module is an upstream module, its configuration is referenced from within an Nginx proxy server configuration. It's up to that server configuration to decide which streams are passed to the Ziti upstream module. This module introduces an upstream configuration directive like ziti_stream_service (example follows).
Public IPs and common ports, e.g., 80, 443, are scarce. There's tremendous pressure to host public services on common, low ports to pass-through restrictive egress filters, and to multi-plex incoming connections via public IPs. This example illustrates two domain names resolving to a set of shared load balancers that employ Nginx ssl_preread module in a stream server context to map the traffic to an upstream by SNI. This allows the Ziti services to terminate TLS, not the load balancer at the cluster edge. The same general approach would work with an http server context if the upstream Ziti service happens to be an HTTP server.

Hypothetical Nginx configuration expressing the above example.
stream {
    upstream ziti_alpha {
        ziti_stream_service     my-alpha-tcp-service;
    }

    upstream ziti_beta {
        ziti_stream_service     my-beta-tcp-service;
    }

    map $ssl_preread_server_name $upstream_name {
        alpha.example.com       ziti_alpha;
        beta.example.com        ziti_beta;
    }

    server {
        listen                  443;
        proxy_pass              $upstream_name;
        ssl_preread             on;
    }
}

Closing due to no response


delete project

In order to ensure users don't accidentally delete all of their files, the deletion carried out in the project manager will delete the data from the data directory but NOT from the labelstudio database. Instructions in the docs detail how to permanently delete a project from labelstudio.

closes #50


Wrong compare type in _check_signals_ranges_scaling()

Hi, I got an error while running cantool version 37.0.0
Error: '<' not supported between instances of 'NamedSignalValue' and 'int'
This seems to be bug where the signals with type NamedSignalValue are not skipped before being compare with an actual number (in this case, an int). Bug seems to be introduced in version 36.4.0

hm, this probably means that your DBC specifies a minimum value for the signal plus some named values and the value which you try to encode is one of the named ones. I agree that this is a legit use case and that this is a bug. I'll have a look...

@andlaus could you also add a test to ensure we don't regress?
I have my merge happy gloves on this week, wink and we should be able to release a fix ^^.
@triqtruong Thank you for reporting.

@triqtruong: can you please verify that your issue is gone in the latest master version?

@andlaus The issue is gone now. Thank you!
Would it be possible if you could put this as a hotfix version (something like 37.0.1), so it'll be a bit easier to update via pip? Thanks a lot!

Will release when I get home today :).

great, let's close this issue then...


What's the problem?

I am running this code on the docker,and my device is a tesla T4 and a 1080ti. I succeed in the first two batch then I met:
frame #0: c10::Error::Error(c10::SourceLocation, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) + 0x6a (0x7fbde81b093a in /opt/conda/lib/python3.6/site-packages/torch/lib/libc10.so)
frame #1: <unknown function> + 0xcafc (0x7fbde7e27afc in /opt/conda/lib/python3.6/site-packages/torch/lib/libc10_cuda.so)
frame #2: <unknown function> + 0x10291 (0x7fbde7e2b291 in /opt/conda/lib/python3.6/site-packages/torch/lib/libc10_cuda.so)
frame #3: c10::TensorImpl::release_resources() + 0x61 (0x7fbde81a33c1 in /opt/conda/lib/python3.6/site-packages/torch/lib/libc10.so)
frame #4: torch::autograd::Variable::Impl::release_resources() + 0x5e (0x7fbd808d01ee in /opt/conda/lib/python3.6/site-packages/torch/lib/libtorch.so.1)
frame #5: <unknown function> + 0x136d7b (0x7fbde84fbd7b in /opt/conda/lib/python3.6/site-packages/torch/lib/libtorch_python.so)
frame #6: <unknown function> + 0x3540b4 (0x7fbde87190b4 in /opt/conda/lib/python3.6/site-packages/torch/lib/libtorch_python.so)
frame #7: <unknown function> + 0x354111 (0x7fbde8719111 in /opt/conda/lib/python3.6/site-packages/torch/lib/libtorch_python.so)
frame #8: <unknown function> + 0x1993cf (0x5606339343cf in /opt/conda/bin/python)
frame #9: <unknown function> + 0xf1532 (0x56063388c532 in /opt/conda/bin/python)
frame #10: <unknown function> + 0xf12b7 (0x56063388c2b7 in /opt/conda/bin/python)
frame #11: <unknown function> + 0xf1147 (0x56063388c147 in /opt/conda/bin/python)
frame #12: <unknown function> + 0xf115d (0x56063388c15d in /opt/conda/bin/python)
frame #13: <unknown function> + 0xf115d (0x56063388c15d in /opt/conda/bin/python)
frame #14: <unknown function> + 0xe3ba7 (0x56063387eba7 in /opt/conda/bin/python)
frame #15: <unknown function> + 0xe3c13 (0x56063387ec13 in /opt/conda/bin/python)
frame #16: <unknown function> + 0xe3b96 (0x56063387eb96 in /opt/conda/bin/python)
frame #17: <unknown function> + 0x1c4a53 (0x56063395fa53 in /opt/conda/bin/python)
frame #18: _PyEval_EvalFrameDefault + 0x43f8 (0x56063395c478 in /opt/conda/bin/python)
frame #19: <unknown function> + 0x19253b (0x56063392d53b in /opt/conda/bin/python)
frame #20: <unknown function> + 0x198505 (0x560633933505 in /opt/conda/bin/python)
frame #21: _PyEval_EvalFrameDefault + 0x30a (0x56063395838a in /opt/conda/bin/python)
frame #22: <unknown function> + 0x19253b (0x56063392d53b in /opt/conda/bin/python)
frame #23: <unknown function> + 0x198505 (0x560633933505 in /opt/conda/bin/python)
frame #24: _PyEval_EvalFrameDefault + 0x30a (0x56063395838a in /opt/conda/bin/python)
frame #25: <unknown function> + 0x1918e4 (0x56063392c8e4 in /opt/conda/bin/python)
frame #26: <unknown function> + 0x192771 (0x56063392d771 in /opt/conda/bin/python)
frame #27: <unknown function> + 0x198505 (0x560633933505 in /opt/conda/bin/python)
frame #28: _PyEval_EvalFrameDefault + 0x10c7 (0x560633959147 in /opt/conda/bin/python)
frame #29: PyEval_EvalCodeEx + 0x329 (0x56063392e289 in /opt/conda/bin/python)
frame #30: PyEval_EvalCode + 0x1c (0x56063392f01c in /opt/conda/bin/python)
frame #31: <unknown function> + 0x2163c4 (0x5606339b13c4 in /opt/conda/bin/python)
frame #32: PyRun_StringFlags + 0x7d (0x5606339b145d in /opt/conda/bin/python)
frame #33: PyRun_SimpleStringFlags + 0x3f (0x5606339b14bf in /opt/conda/bin/python)
frame #34: Py_Main + 0x423 (0x5606339b52c3 in /opt/conda/bin/python)
frame #35: main + 0xee (0x56063387e02e in /opt/conda/bin/python)
frame #36: __libc_start_main + 0xf0 (0x7fbdec311830 in /lib/x86_64-linux-gnu/libc.so.6)

And then it turns out:
Unable to determine the device handle for GPU 0000:02:00.0: GPU is lost.  Reboot the system to recover this GPU

your gpu might be getting over heated. make sure you have active cooling . just a hunch.


chore(project): replace fetch with whatwg-fetch for testing

drop the github fetch for the npm version of it to avoid github key issues while running travis

not helping enough. systemjs is on github as well


Sketch Library Updates

Summary

update Sketch asset downloads from Get Started and What's New
update version numbers

Updates from

#2625
#2626
#2627

Links to files (when complete)

Will comment with GitLab links when files are ready

Files were updated with the website release for v0.13.5.


Included Link to Graph Course

Please note that for legal reasons we require you to sign the
Contributor Agreement
before we can accept your pull requests.

@janavolkova9 What was the reason for this addition?
We already had the link to the graph course in the parent chapter:

Putting it again in the subchapter, especially General Graph, does not make much sense to me. The course doesn't really named graphs / Gharial, or does it?


Desktop App is not supported on macOS Monterey version 12.6.3

Warning message on downloading the desktop app on macOS Monterey version 12.6.3
“Bruno” cannot be opened because the developer cannot be verified.
macOS cannot verify that this app is free from malware.

Working on getting a signed build out that should solve this issue. Should be done in another 2 days.
Meanwhile please, go to Applications in Finder.
And then right click on Bruno and click open. It will show you a warning, but will allow you to open.
Let me know if you still unable to open, I can send a gif of how I currently open it in Mac.

Thank you, that worked.


Handle Window Close Attempt

We have a little bit of "unnecessary" auto-update code that lead to small errors on Windows. This fixes that issue.

Current coverage is 86.89%

Merging #98 into master will decrease coverage by -0.68% as of 48773c0

@@            master     #98   diff @@
======================================
  Files           32      32
  Stmts          676     656    -20
  Branches         0       0
  Methods          0       0
======================================
- Hit            592     570    -22
  Partial          0       0
- Missed          84      86     +2

Review entire Coverage Diff as of 48773c0

Powered by Codecov. Updated on successful CI builds.


Quiet install log

We set the env var CAPSULE_LOG: none in the main nf-core CI workflows to prevent the massive actions log output from the installation.

Nice, thanks! 🎉


Contributing FIXENV

Utility to help remount, move, or copy the zot installation.

it's possible this won't be needed at that point.

@lbdyck , with the new zopen-config, are you still having to use FIXENV or is zopen-config sufficient now?

if you are referring to .../etc/zopen-config then that does not satisfy - what I need, for use with ZIGI, is either a quick process, which this isn't, or an environment file similar to this:
ZOPEN_ROOTFS=/u/lbdyck/zopen
ZOPEN_LOG_PATH=/u/lbdyck/zopen/var/log
LIBICONV_HOME=/u/lbdyck/zopen/usr/local/zopen/libiconv/libiconv-1.17.20230831_134536.zos
LESS_HOME=/u/lbdyck/zopen/usr/local/zopen/less/less-643.20230909_075924.zos
LIBPATH=/u/lbdyck/zopen/usr/lib:/usr/local/ro202302/envs/cbt/lib:/usr/local/ro202302/envs/cbt/lib/perl5/5.32....
PERL5_HOME=/u/lbdyck/zopen/usr/local/zopen/perl/perl5-blead.20230605_161457.zos
MAN_TEST_DISABLE_SYSTEM_CONFIG=1
GROFF_TYPESETTER=utf8
GIT_TEMPLATE_DIR=/u/lbdyck/zopen/usr/local/zopen/git/git-<IP_ADDRESS>30923_021248.zos/share/git-core/templates
ASCII_TERMINFO=/u/lbdyck/zopen/usr/local/zopen/ncurses/ncurses-6.3.20230914_231534.zos/share/terminfo/

in other words - something quick that doesn't require processing.


Request too old is true when the parameter cannot be parsed

I've just noticed that if the timestamp sent from the client is invalid (i.e. it cannot be parsed), the request will be denied without any information / log entry. In my opinion, it should at least be logged that the format was invalid. Otherwise, it is quite hard to determine why the request has been denied. What do you think? I'll create a PR if you agree.
def request_too_old?(headers)
  # 900 seconds is 15 minutes
  begin
    Time.httpdate(headers.timestamp).utc < (Time.now.utc - 900)
  rescue ArgumentError
    true
  end
end

I agree that it is extremely difficult to know WHY a particular request was not authentic.
I'd love for ApiAuth to provide a way to know exactly what caused a request to fail the check.
I personally would prefer that ApiAuth provide some sort of methods to determine the failure reason as opposed to logging directly. Then it would up to the consumer of the ApiAuth gem to decide exactly what they want to do with the info, weather it be log, or provide a more detailed error response back to the consumer of their API, or whatever else they might want to do with it.


SPIKE: Address support for PR

From the smarty street API  PR has an urbanization field. Determine what if anything we need to do to support PR addresses in simple report https://smartystreets.com/docs/cloud/us-street-api#input-fields
urbanization: "The neighborhood (only Puerto Rican addresses)"

wont do


Capability to determine IOPS support in volumes

A capability to determine which cloud supports IOPS measurement in volumes would be really helpful.

Added in 2015.09


Responsive example doesn't work correctly

Responsive example doesn't work correctly. Height is not restored.
http://prntscr.com/4tubob
http://prntscr.com/4tubqv
http://prntscr.com/4tubtu

@LeusMaximus Is this still an issue?

@LeusMaximus Closing old issues. If you'd like to reopen this, let us know. Thanks!


JSX Not validating when index signature is present

TypeScript Version:  2.0
Code
interface IProps {
  primaryText: string,
  [propName: string]: any
}

function VerticalNavMenuItem(props: IProps) {
  return
props.primaryText

}

function VerticalNav() {
  return (

      <SOME_JSX />
      <VerticalNavMenuItem primaryText={2} />

  )
}

Expected behavior:
In VerticalNav I have the child component: <VerticalNavMenuItem primaryText={2} />
This should throw a type error because primary text must be a string.
However, if I remove   [propName: string]: any from IProps then the type error will be thrown.
Actual behavior:
No error is thrown.

The interpreted intent of the index signature is to allow arbitrary extra properties.

@RyanCavanaugh thanks for the quick response. I guess I'm confused - shouldn't the index signature allow any additional properties with any type, but nevertheless check that the primaryText property has the type string?
Maybe I am misunderstanding the docs but for the following example:
interface SquareConfig {
    color?: string;
    width?: number;
    [propName: string]: any;
}

the docs say that: SquareConfig can have any number of properties, and as long as they aren’t color or width, their types don’t matter.
Does that not mean that the types for color and width do matter?
Also, when I tested this in the TS playground using normal functions the primaryText was checked to be a string.

Sorry, I totally misread your original post. Rereading/investigating

Yeah this is totally supposed to be an error. Thanks for following up!


DSL and space sensitivity

Hi,
looks like there is huge mess with space removal ATM.
For example:
{ 'Flame Shock', {
'target.debuff(Flame Shock)',
'target.debuff(Flame Shock).duration <= 2',
} },
last condition passes space removal:
before: target.debuff(Flame Shock).duration <= 2
after: target.debuff.duration<=2(Flame Shock)
and comparizion does not work properly anymore...

it should look like: target.debuff.duration<=2(Flame Shock)
the arguments dont need to be in a specific place, pString will remove it again and process it no matter where it is in the string as long as it is inside the parentheses.
Ive sent some tweaks for comparison, could you re-test and give me feedback?

Ok, should be fixed in: https://github.com/MrTheSoulz/NerdPack/commit/e67170ce8c8a389455c4cee3ffccb147b6a5c9fb
I found a better way to approch this once i revisoted the problem, thanks for reporting!

Re-open this issues if needed.

Hi,
there is something wrong still because code example above do not work anymore, it fails at this point:
'target.debuff(Flame Shock).duration <= 2',
and stays to spam Flame Shock even if debuff duration is >2.
There is another example:
RegisterConditon("log", function(args)
print( 'Log : '..' - '..(args or 'nil') )
return true
end)
Called { 'Spell', 'log(1)' },
'old' version printed: Log: - 1
'new' version does: Log: - nil
After improvements it prints: Log : nil - 1
RegisterConditon("log", function(args, args2)
print( 'Log : '..' - '..(args or 'nil')..' - '..(args2 or 'nil') )
return true
end)
For conclusion: there is some messup with parameters and conditions after latest changes!

Ok, i think ive fixed now...
If i did, close this isse :)

Hi,
In syntax wise I'd like your previous code more ;-)
At first it did not fix additional parameter issue give as exmaple about log(1). It looks like minor issue but I expect that it will break many "home made" condidions that are not realated with spell nor target.
2nd: now it  is a bit better but another realted issue found. For example this code will fail on case if there is 0 charges. Most probably comparision "=" will not work properly at all as there is executed 0=0 and that is not comparision.
{ 'Stormkeeper', {
'player.buff(Storm Totem)',
'player.spell(Lava Burst).charges = 0',
} },
Current workaround is here:
{ 'Stormkeeper', {
'player.buff(Storm Totem)',
'player.spell(Lava Burst).charges == 0',
} },
Stack trace:
Message: Interface\AddOns\NerdPack\system\dsl.lua:37: attempt to call a nil value
Time: 09/13/16 12:43:36
Count: 1
Stack: Interface\AddOns\NerdPack\system\dsl.lua:37: in function <Interface\AddOns\NerdPack\system\dsl.lua:27>
Interface\AddOns\NerdPack\system\dsl.lua:50: in function <Interface\AddOns\NerdPack\system\dsl.lua:42>
(tail call): ?
(tail call): ?
Interface\AddOns\NerdPack\system\dsl.lua:70: in function <Interface\AddOns\NerdPack\system\dsl.lua:64>
(tail call): ?
Interface\AddOns\NerdPack\system\engine.lua:362: in function `Parse'
Interface\AddOns\NerdPack\system\engine.lua:342: in function `Parse'
Interface\AddOns\NerdPack\system\engine.lua:342: in function `Parse'
Interface\AddOns\NerdPack\system\engine.lua:342: in function `Parse'
Interface\AddOns\NerdPack\system\engine.lua:385: in function `callback'
Interface\AddOns\NerdPack\system\timer.lua:12: in function <Interface\AddOns\NerdPack\system\timer.lua:8>
Interface\SharedXML\C_TimerAugment.lua:16: in function <Interface\SharedXML\C_TimerAugment.lua:14>

Locals: mString = "player.spell(Lava Burst).charges = 0"
spell = "Stormkeeper"
(for index) = 8
(for limit) = 8
(for step) = 1
i = 8
Comperator = "="
tempT = <table> {
 1 = 0
 2 = 0
}
(*temporary) = nil
(*temporary) = "attempt to call a nil value"
tableComparator = <table> {
 1 = ">="
 2 = "<="
 3 = "!="
 4 = "~="
 5 = "=="
 6 = ">"
 7 = "<"
 8 = "="
}
pString = <function> defined @Interface\AddOns\NerdPack\system\dsl.lua:7

Sorry, closed by mistake

Right, seems lile i need a sanity check for nils.
About #=#,  it wont work with the way i build the comparatores. Crs are gonna need to change to ==, same for !=, it becomes ~=.

Ok, think ive fixed the nil issues and managed to support "!=" & "=" again.
Currently testing the log(1) issue

Log(1) seems to work as intended.
Note: arg is target and arg2 is stuff inside parenthesis.
This applys too all conditions unlike the old dsl.
So: player.log(1) = arg is player, arg2 is 1


[tooling] fix clippy command

What does this fix?

Looks like VS Code requires it: https://stackoverflow.com/a/71345794


Another bug with filtering and group monitors

⚠ Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

Description

👟 Reproduction steps

Add Group monitor A
Add monitor B, placed in group A
Click on monitor B to open its details page
Select a filter that applies to monitor B, e.g. "Running"
Observe that monitor B is shown twice

👀 Expected behavior
Group should stay collapsed if filtering is active, and the child is already shown in the root list
😓 Actual Behavior
Group is expanded and monitor is shown twice
🐻 Uptime-Kuma Version
master
💻 Operating System and Arch
Windows 11 x64
🌐 Browser
Mozilla Firefox
🐋 Docker Version
No response
🟩 NodeJS Version
No response
📝 Relevant log output
No response

Also, when filtered the monitors in the list include the full hierarchy - in the image above it shows "Test Group / Test Radius" under "Test Group". When you have lots of monitors this becomes messy as they all begin with "Test Group /" and you can't see which is which.
When filtered, it should not show the hierarchy on the monitor line, only the monitor name itself.

But there are also people who have monitors with the same name, but under a different hierarchy:

sever 1

redis

server 2

redis

The pathname feature was designed for this use case.

But there are also people who have monitors with the same name, but under a different hierarchy:

sever 1

redis

server 2

redis

The pathname feature was designed for this use case.

Then those should be grouped under the groups - e.g.
server 1
redis
server 2
redis
The same way as it works for unfiltered monitors.

Here's an example to illustrate:
Unfiltered:

Filtered:

As you can see in the filtered example, you can no longer see which monitor is what.


Still Getting Errors in Google Dev tools console

I am using the complete version offered at http://foundation.zurb.com/sites/download.html/ in my WordPress theme WP-Forge and I am still getting JS errors in Google dev tools console.
Uncaught TypeError: __WEBPACK_IMPORTED_MODULE_1__home_deployer_sites_node_foundation_customizer_node_foundation_customizer_foundation_sites_js_foundation_core__.a.addToJQuery is not a function     at Object.<anonymous> (foundation.js?ver=6.4:11621)     at __webpack_require__ (foundation.js?ver=6.4:20)     at module.exports (foundation.js?ver=6.4:66)     at foundation.js?ver=6.4:69
Also in theme-functions.js I have the following:
`jQuery(document).foundation();'
and Google dev tools is throwing the following error:
Uncaught TypeError: jQuery(...).foundation is not a function     at theme-functions.js?ver=6.4:2
Even if I change it to this:
$(document).foundation();
I still get the following error:
Uncaught TypeError: $ is not a function     at theme-functions.js?ver=6.4:2
This used to work before I added the new files from 6.4. - WordPress ships with its own version of jQuery and it is in no-conflict mode:

WordPress comes pre-packaged with a copy of jQuery, which you should use with your code. When WordPress’ jQuery is loaded, it uses compatibility mode, which is a mechanism for avoiding conflicts with other language libraries.
What this boils down to is that you can’t use the dollar sign directly as you would in other projects. When writing jQuery for WordPress you need to use jQuery instead.

Any thoughts or ideas?

@tsquez I believe the external declarations as they are today may assume access to $... we can almost certainly resolve this, but to check can you try running window.$ = window.jQuery in a script just before you include the foundation js?

Actually, looking once again at our config I wouldn't expect that to be a problem. Hmm... To track this down, previously you were testing against the build from the dist folder in the package... can you see if that JS works for you? I'm wondering if there's something going on with the way the customizer is generating the js...

@kball - OK I used the js from the rc4 dist folder I had and everything works now and there are no errors in GDT.

Interesting... ok, so it sounds like the customizer JS isn't working in your case... digging into it

sounds good, but actually let me do this. I am going to download the github files and see if that js file works. I normally don't download the complete.zip - I usually use the distro from the repo. let me do that real quick and see what happens.

Found it! Fixing

YOU DAH MAN!!!

Yeah I downloaded the latest version from here and used the files from the distro folder and everything works great. Glad you able to narrow it down. I am going to close this.

Customizer fixed. Thanks again for the report and helping track this down quickly @tsquez!

Anytime amigo


Document useData(), and misc improvements

@AurelienLourot WDYT? On a tangent: as you can see, I've started using the term "component hook" instead of "hook" for usePageContext() and useData(). (I've thought a bit more about it and I came to the conclusion that calling these functions "hook" isn't that much of a misnomer. E.g. useState() is a function to "hook state onto a component". Same for useEffect(): it's a function to "hook an effect into a component".)


Make messages start at bottom of window when conversation length is small

How can I make messages start at the bottom of the chat window/message list when the conversation is short? For example, in the readme example and the chat friends example, the first message sent is displayed at the top of the chat window.
Is it possible to instead achieve the behavior of most chat apps (telegram, messenger, etc.) where the messages always start at the bottom of the chat window, just above the input box?

I also want to achieve that

We're currently trying to achieve the same with some CSS hacks, having a supported option for this would be awesome

Hi, any updates on this?


Do not invoke envinfo on windows

Summary:
CI is broken. Let's not bother attempting to fixing it as it's attempting to call envinfo on Windows
which no one really looks into.
Also the maintainer is unresponsive: https://github.com/tabrindle/envinfo/issues/238
Changelog:
[Internal] [Changed] - Do not invoke envinfo on windows
Differential Revision: D53698194

https://github.com/facebook/react-native/commit/0575033f768447e69f085a3c7f20b00daedd2530


serde(flatten) breaks metadata propagation in errors

When using Figment with nested structs, some of which have #[serde(flatten)] attached, any error that occurs while loading the config for the nested flattened keys wont have any context info attached.
In the following examples the test.toml config is invalid -- a string is specified where a u32 is expected. In the first example flatten isn't used. In the second, the intermediate enum is flattened on the root struct.
use figment::{Figment, providers::{Toml, Format}};
use serde::Deserialize;

fn main() {
    // example without flatten
    let err = figment::Jail::try_with(|jail| {
        #[derive(Clone, Deserialize, Debug)]
        struct TcpConfig {
            timeout: u32,
        }

        #[derive(Clone, Deserialize, Debug)]
        #[serde(rename_all = "lowercase")]
        enum PortConfig {
            Tcp(TcpConfig)
        }

        #[derive(Clone, Deserialize, Debug)]
        struct Config {
            port: PortConfig,
        }

        jail.create_file("test.toml", r#"
            port.tcp.timeout = "not a valid u32"
        "#)?;

        Figment::from(Toml::file("test.toml"))
            .extract::<Config>().map(|c| ())
    }).err().expect("should fail");

    println!("{err}");

    // example with flatten
    let err = figment::Jail::try_with(|jail| {
        #[derive(Clone, Deserialize, Debug)]
        struct TcpConfig {
            timeout: u32,
        }

        #[derive(Clone, Deserialize, Debug)]
        #[serde(rename_all = "lowercase")]
        enum PortConfig {
            Tcp(TcpConfig)
        }

        #[derive(Clone, Deserialize, Debug)]
        struct Config {
            #[serde(flatten)]
            port: PortConfig,
        }

        jail.create_file("test.toml", r#"
            tcp.timeout = "not a valid u32"
        "#)?;

        Figment::from(Toml::file("test.toml"))
            .extract::<Config>().map(|c| ())
    }).err().expect("should fail");

    println!("{err}");
}

When run the output is:
invalid type: found string "not a valid u32", expected u32 for key "default.port.tcp.timeout" in /tmp/.tmpzvTfAI/test.toml TOML file
invalid type: found string "not a valid u32", expected u32

The first error message is far more useful as it explains which key is invalid and which source file.

The way that flatten works in serde is rather troubling and results in lots of issues. In short, when #[flatten] is applied to any field of a struct T, serde does the following in T's derived deserialization:

It collects every field that doesn't match a non-flattened field of the struct into what is effectively a hash map of effectively untyped values. Thus, deserialization for all internal values always succeeds.
It passes that map into a new deserializer, which is then passed to the deserialize implementations for each flattened field type, which performs the true deserialization on that map.
Because the internal keys and values have already "successfully deserialized", any errors from the true deserialization are propagated as if they occurred on the top-level value, i.e, the base value.

This means that figment sees that an error occurred for the entire structure, not any individual key/value pair, and so it has no idea what to assign the error to.
To concretize this, let's take a simplified version of your example:
#[derive(Clone, Deserialize, Debug)]
struct TcpConfig {
    timeout: u32,
}

#[derive(Clone, Deserialize, Debug)]
struct Config {
    #[serde(flatten)]
    port: TcpConfig,
}

For the TOML file timeout = "hi", we have a key of timeout assigned to a string value of "hi". Normally, because timeout is a u32, the deserializer would fail while deserializing the string "hi", giving us the error we want.
In the case of flattened structs, however, the internal "flattening" deserializer accepts everything. Thus the string "hi" deserializes just fine, and no error occurs on that value. Instead, deserialization fails later, after all values have deserialized properly and the only thing remaining is the overall structure, i.e, the complete figment. Here the Config deserializer raises the original error, but the figment deserializer has no idea what to apply it to.
This might be a bit confusing - I apologize. The details are rather gnarly. The short of it is: flattening breaks what it means to deserialize a structure by buffering values and lying that deserialization succeeded, depriving the true deserializer of the information about when errors occur. This means we can't emit a proper error during flattening.
Perhaps there's some work-around, but I'll have to think about it more.

See also https://github.com/serde-rs/serde/issues/2186#issue-1163413259.

Thank you for such a detailed reply! I didn't think to look into the details of how flatten works on the serde side of things.  Your explanation of whats happening under the hood and why that becomes problematic for figment to provide details makes perfect sense.
I was only using flatten try and "clean up" my config file by removing seemingly redundant keys (ie, have tcp or serial on the root rather than port.tcp or port.serial) and to abstract a few common attributes (such as timeout) across various port types (tcp, serial, etc) into a common struct.  For the sake of anyone using my program I'll choose to forgo flatten in favor of better error messages!
Perhaps the figment docs could have a mention of this "gotcha" under the "tips" section?

Perhaps the figment docs could have a mention of this "gotcha" under the "tips" section?

Good idea!


[Bug]: All gas prices show $0.00

The problem
Hi,
Thanks for developing this integration!
It worked fine until this morning. Out of nowhere it shows $0.00. I checked on the GasBuddy website and there was price there. I also removed everything including the gas station and added again, but that did not made any difference.
Not sure if new version broke it or what.
What version of Home Assistant?
core-2024.10.1
What version of GasBuddy?
1.0.14
Diagnostics information

Anything in the logs that might be useful for us?
No response
Additional information
No response

What's the station ID?

The API's reporting 0 as the price:
{
    "data": {
        "station": {
            "brands": [
                {
                    "imageUrl": "https://images.gasbuddy.io/b/56.png"
                },
                {
                    "imageUrl": "https://images.gasbuddy.io/b/56.png"
                }
            ],
            "prices": [
                {
                    "cash": null,
                    "credit": {
                        "nickname": null,
                        "postedTime": null,
                        "price": 0
                    },
                    "fuelProduct": "regular_gas",
                    "longName": "Regular"
                },
                {
                    "cash": null,
                    "credit": {
                        "nickname": null,
                        "postedTime": null,
                        "price": 0
                    },
                    "fuelProduct": "midgrade_gas",
                    "longName": "Midgrade"
                },
                {
                    "cash": null,
                    "credit": {
                        "nickname": null,
                        "postedTime": null,
                        "price": 0
                    },
                    "fuelProduct": "premium_gas",
                    "longName": "Premium"
                },
                {
                    "cash": null,
                    "credit": {
                        "nickname": null,
                        "postedTime": null,
                        "price": 0
                    },
                    "fuelProduct": "diesel",
                    "longName": "Diesel"
                }
            ],
            "priceUnit": "dollars_per_gallon",
            "currency": "USD",
            "id": "156618",
            "latitude": 47.364016302532,
            "longitude": -122.020983695983
        }
    }
}

Maybe they requested their prices be wiped?

Maybe they requested their prices be wiped?

Possible, but I doubt it as other not related stations in radius do not have prices listed.
Really odd. I wonder if something is going on with their system.

Closing this as it appears to be an issue with GasBuddy and not this integration.

@JohnyBeGood
@firstof9 thanks for the integration! I'm trying to keep track of the trends of the gas prices, but the "free" gas is quite annoying... Seems like the API is reporting 0$ when it's "not available". To better reflect that, could it be possible to make the entity "offline" when price is 0$?
Thanks!

could it be possible to make the entity "offline" when price is 0$?

Can you open a feature request for this for me please for tracking?

@JohnyBeGood @firstof9 thanks for the integration! I'm trying to keep track of the trends of the gas prices, but the "free" gas is quite annoying... Seems like the API is reporting 0$ when it's "not available". To better reflect that, could it be possible to make the entity "offline" when price is 0$? Thanks!

Great idea!
I also setup an automation to get notified on price change and it seems like at some point if the price is not updated for certain amount of days it goes to "$0.00" and I get notified.

@brunob45 @JohnyBeGood please see #103 there's a beta with the changes to test if you wouldn't mind.

@brunob45 @JohnyBeGood please see #103 there's a beta with the changes to test if you wouldn't mind.

I re-downloaded beta version. Does price of $0.00 needs to change to offline or something else?

Nevermind. I didn't see that after the re-install it needed a restart.
Now it shows "Unknown"


UI - Skip does not work for the failed tests when scan is run for the first time on the cluster

What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):

Run Scans for an rke cluster for the first time.
For the tests that have failed, click on Skip

Expected Result:
The tests should be skipped.
Actual Result:
Click on skip does not work.
Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): master-head latest - commit id: ``df31802ac
Installation option (single install/HA): single

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): custom
Kubernetes version (use kubectl version):

1.16

Verified on master-head - commit id: 5f917419b

Run Scans for an rke cluster for the first time.
For the tests that have failed, click on Skip
Config map is generated in the security-scan namespace.
Subsequent Run Scans action, skips the apt tests marked.


Fields uneditable on Mac - Yosemite

I'm on 10.10.3 Yosemite - when I run the GUI version of the app, it opens fine but none of the input fields can be edited. They appear to be grayed out.

You have to open a project first. Right now, a "project" is defined as a folder with an index.html file in it. All of the fields will become editable after a folder is chosen.

Thanks for the quick reply! It works fine.

Cool :) Let me know if there are any other issues you have!


feat(actor): add compat feature

Feature or Problem

Introduce compat feature to wasmcloud_actor, when enabled along component, all WIT interfaces provided by wasmCloud host are implemented in terms of the wasmcloud:bus/host
Related Issues

Release Information

Consumer Impact

Testing

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
[ ] x86_64-windows

Tested on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
[ ] x86_64-windows

Unit Test(s)

Added a http-log-rng-compat test identical to existing http-log-rng-component
Acceptance or Integration

Manual Verification

cargo test

Re: http-log-rng-compat, how about builtins-compat?

Yes! The plan is to rename indeed. Need to see more on how it develops, but I think we should be able to just have compat, module and component crates (they would do more than just call builtins)


The interval between getting SMS CAPTchas should be 1 minute; now it's 5 minutes

获取短信验证码间隔应是1分钟，现在是5分钟

短信发送时间间隔1分钟，验证码有效期5分钟

https://github.com/masastack/MASA.Stack.Components/issues/472


Missing Ionicons ion-ios-gear-outline

Looks like the mapping is missing icon 62524, which is called ion-ios-gear-outline
Maybe mapping needs to be regenerated? Spent a little time trying to figure out how you generate these so I could do it myself, but couldn't figure it out. Happy to put up a PR if you show me how.

Also missing 'ion-ios-circle-outline'

Looks like this project depends on https://www.npmjs.com/package/ionicons, but maybe it's worth updating to https://www.npmjs.com/package/ionicons-npm which supposedly better-reflects the ionicons repository?
And austen, I'm guessing you can regenerate things with the npm scripts in https://github.com/oblador/react-native-vector-icons/blob/master/package.json  (though would need to be updated to ionicons-npm or whatever has the newest icons)

Also missing Edit: https://github.com/oblador/react-native-vector-icons/issues/496
Would be super great if these were up-to-date especially since it's the library default!

I think you're all looking at version 2.0.1 of Ionicons, please refer to the linked cheatsheet at http://ionicframework.com/docs/ionicons/
I know it's very confusing that they haven't updated ionicons.com, but I don't have any power over that and there's open issues about it.

@oblador , thanks for the clarification. So am I correct in understanding that ionicons 3.0 is the latest version, and it actually removed a bunch of icons that previously existed in ionicons 2.0 (ie, the ones people above are asking about)?
Is it worth offering ionicons 2.0 as a separate build/dependency in react-native-vector-icons, for folks who want access to all those icons? Or is a fork the right answer here?

@mikelambert Yes, 3.0 was a big breaking change. You should be able to build a custom version yourself with the tools provided by this package.
node generate-icon node_modules/ionicons/css/ionicons.css --prefix=.ion- --componentName=Ionicons --fontFamily=Ionicons > Ionicons.js && cp node_modules/ionicons/fonts/ionicons.ttf Fonts/Ionicons.ttf
"build-ionicons": "node generate-icon node_modules/ionicons/dist/css/ionicons.css --prefix=.ion- --componentName=Ionicons --fontFamily=Ionicons --template=templates/separated-icon-set.tpl --glyphmap=glyphmaps/Ionicons.json > Ionicons.js && cp node_modules/ionicons/dist/fonts/ionicons.ttf Fonts/Ionicons.ttf",

Thank you, I actually linked to that rebuild command in my above comment, though I referenced the wrong NPM.
I was actually asking if it's worth adding an IonIcons20 alongside IonIcons to react-native-vector-icons, as part of RNVI trying to be the master source/method for getting access to all icons. (Otherwise we all need to make our own personal forks, or collab together to make a RNVI+IonIcons2.0 fork and keep it up to date.)

@mikelambert I mean that you can have a local custom component that you generate from the 2.0.1 version and keep in your repository. This is what other people are doing for their own custom sets.

Ahh I see, thank you for the clarification


AAD connect health agent version with removed dependency on Azure Service Bus

Hello
What is the specific version of the AAD CH agent that no longer requires Azure Service Bus port 5671? "Latest version" is too generic.

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

ID: 41c38d39-e36b-dd70-9c8c-1fc28a1dba5e
Version Independent ID: 4a9c6f6b-7627-2d61-402a-a2c405812a61
Content: Hybrid Identity required ports and protocols - Azure
Content Source: articles/active-directory/hybrid/reference-connect-ports.md
Service: active-directory
Sub-service: hybrid
GitHub Login: @billmath
Microsoft Alias: billmath

@Larryngolog, thank you for reaching out. We are looking into this and would get back to you soon on this thread.

@Larryngolog  As per the Azure AD Connect Version History the last changes made in regards to Service Bus was on ver <IP_ADDRESS>
We do not have a fixed version documented where dependency to Azure Service Bus port 5671 was discontinued. We would check on getting more information on the same.

@Larryngolog As of now, the Document on the Azure AD Connect Version history is what we have. We will update the document with details but we do not have an ETA for the same now.
We will be closing this thread. Let us know if you need further help.


[BUG] Net Spec Keys is overwritten in MADDPG

Describe the bug
In the MADDPG system, regardless of the net spec keys given to the network_factory (i.e create_default_networks), the system overwrites these values. This causes issues when trying to give different networks to different agents. This issue occurs on line 318 and 449.
To Reproduce
Steps to reproduce the behavior:

Input any non-standard net_spec_keys to the create default network method
Witness that the inputted value is not carried over

Expected behavior
The given net_spec_keys should be used otherwise the default values should be constructed.
Context (Environment)

Latest Mava
Ubuntu Linux

Additional context
Haven't inspected other classes, might only be present in MADDPG.
Possible Solution
Somehow check for given value - not sure if this is possible. Maybe make net_spe_keys a parameter to the system instead of the network factory.

Closing all TF issues as we are depreciating our TF systems.


Get migration tool ready for use by Flutter

This epic tracks all of the work we believe we need to do to make the migration tool useful for the Flutter team.

As of 1c7fe7196dd7a542f7f91cd6ea2ac81e1a13146c, the null safety migration tool has been removed from active development and retired. No further work on the tool is planned.
If you still need help, or you believe this issue has been closed in error, please feel free to reopen.


Docs section: BCDR - SLAs

Page section: Design Consideration - Host Pool Compute Strategy

For the VM resiliency points AV Sets & AZs are mentioned but not the single instance SLAs for Standard HDD/SSD & Premium SSD. This is called out in the design recommendations near the bottom of the article

Fix:

Add details on SLA for single instance VM depending on which disk storage option is chosen
Perhaps make reference to the design recommendations in the earlier section.

Migrated to ADO


CASSANDRA-16385

See CASSANDRA-16385

Efficiency wise I'm not sure all the extra argument passing is better than a null check. I'll see what I can do to improve it. Thanks for the feedback.

Efficiency wise I'm not sure all the extra argument passing is better than a null check. I'll see what I can do to improve it. Thanks for the feedback.

Efficiency wise I'm not sure all the extra argument passing is better than a null check. I'll see what I can do to improve it. Thanks for the feedback.

They are not about solving the same problem.
The extra argument and the testing-only method is to separate out the testing code in Message.java.
The null check is needed as long as response serializer is fetched. The response serializer can be null if the message has expired.

Efficiency wise I'm not sure all the extra argument passing is better than a null check. I'll see what I can do to improve it. Thanks for the feedback.

They are not about solving the same problem.
The extra argument and the testing-only method is to separate out the testing code in Message.java.
The null check is needed as long as response serializer is fetched. The response serializer can be null if the message has expired.

How does this sound to you? https://github.com/yifan-c/cassandra/commit/9f9498abb96fc0d05417ca6f8c74b180a90ebb1f

How does this sound to you? https://github.com/yifan-c/cassandra/commit/9f9498abb96fc0d05417ca6f8c74b180a90ebb1f

Thanks for the feedback and fixup @yifan-c

Merged alternate version as  838bd8cae6d125cfb055dbf6bfc5a2d4e13cdfcb instead.


BT not working

Hi .. could anyone help me with this?

radar2.0
2020-04-28 11:02:58.936
info
(928) radar2 set to scan every 20 seconds and printers every 720 minutes.

radar2.0
2020-04-28 11:02:58.935
info
(928) arp-scan will use the following interfaces: [ 'ens18' ]

radar2.0
2020-04-28 11:02:58.935
info
(928) Remove name end for host names: .fritz.box

radar2.0
2020-04-28 11:02:58.934
info
(928) use known IP list: []

radar2.0
2020-04-28 11:02:58.934
info
(928) use known BT list: []

radar2.0
2020-04-28 11:02:58.934
info
(928) radar2 set to flag items away if they are not seen for 2 minutes

radar2.0
2020-04-28 11:02:58.933
warn
(928) node-bluetooth not found!

radar2.0
2020-04-28 11:02:58.932
warn
(928)  Noble not available, Error: Error: The module<EMAIL_ADDRESS>compiled against a different Node.js version usingNODE_MO

radar2.0
2020-04-28 11:02:58.852
info
(928) Adapter disconnected and stopped with dostop(false) and callback(true)

radar2.0
2020-04-28 11:02:58.851
error
(928) Error: bind EACCES <IP_ADDRESS>:67     at dgram.js:339:20     at processTicksAndRejections (internal/process/task_queues.js:85:21)

radar2.0
2020-04-28 11:02:58.851
error
(928) uncaught exception: bind EACCES <IP_ADDRESS>:67

radar2.0
2020-04-28 11:02:58.778
info
(928) net-ping not available! Will try to use normal ping!

radar2.0
2020-04-28 11:02:58.773
info
(928) radar2 initialization started...

radar2.0
2020-04-28 11:02:58.764
warn
(928)  adapter.objects.getObjectList is deprecated, and will be removed in the  future. Please use adapter.getObjectList/Async. Report this to  Developer!

radar2.0
2020-04-28 11:02:58.713
info
(928) starting. Version 1.0.9 in /opt/iobroker/node_modules/iobroker.radar2, node: v12.16.2, js-controller: 3.0.19

radar2.0
2020-04-28 09:02:27.327
info
(32526) radar2 set to scan every 20 seconds and printers every 720 minutes.

radar2.0
2020-04-28 09:02:27.327
info
(32526) arp-scan will use the following interfaces: [ 'ens18' ]

radar2.0
2020-04-28 09:02:27.326
info
(32526) Remove name end for host names: .fritz.box

radar2.0
2020-04-28 09:02:27.326
info
(32526) use known IP list: []

radar2.0
2020-04-28 09:02:27.325
info
(32526) use known BT list: []

radar2.0
2020-04-28 09:02:27.325
info
(32526) radar2 set to flag items away if they are not seen for 2 minutes

radar2.0
2020-04-28 09:02:27.325
warn
(32526) node-bluetooth not found!

radar2.0
2020-04-28 09:02:27.323
warn
(32526) Noble not available, Error: Error: The module<EMAIL_ADDRESS>compiled against a different Node.js version usingNODE

radar2.0
2020-04-28 09:02:27.170
info
(32526) Adapter disconnected and stopped with dostop(false) and callback(true)

radar2.0
2020-04-28 09:02:27.169
error
at processTicksAndRejections (internal/process/task_queues.js:85:21)

radar2.0
2020-04-28 09:02:27.169
error
at dgram.js:339:20

radar2.0
2020-04-28 09:02:27.169
error
(32526) Error: bind EACCES <IP_ADDRESS>:67

radar2.0
2020-04-28 09:02:27.168
error
(32526) uncaught exception: bind EACCES <IP_ADDRESS>:67

radar2.0
2020-04-28 09:02:27.093
info
(32526) net-ping not available! Will try to use normal ping!

radar2.0
2020-04-28 09:02:27.084
info
(32526) radar2 initialization started...

radar2.0
2020-04-28 09:02:27.074
warn
(32526) adapter.objects.getObjectList is deprecated, and will be  removed in the future. Please use adapter.getObjectList/Async. Report  this to Developer!

radar2.0
2020-04-28 09:02:27.020
info
(32526) starting. Version 1.0.9 in /opt/iobroker/node_modules/iobroker.radar2, node: v12.16.2, js-controller: 3.0.19

You may miss access rights.  are you running on linux and did you run scripts from readme after install?
You need to re-run scripts also after update of nodejs again!

just ran through them .. no change

Interesting .. I found this screenshot in the forum. Are the settings "hcitool lescan anstelle von Noble verwenden" .. completely gone or hidden?

green now:
daniel@iobroker:/opt/iobroker$ node -v
v10.20.1
daniel@iobroker:/opt/iobroker$ nodejs -v
v10.20.1
daniel@iobroker:/opt/iobroker$ npm -v
6.14.4
In fact there seems to be an problem with newer versions of node/nodejs.

found this fyi:

radar2.0
2020-04-30 06:02:15.384
warn
(17084) Promise failed @ '_tickCallback in  internal/process/next_tick.js @68:7' error: { SyntaxError: Unexpected  token c in JSON at position 0 at JSON.parse () at  A.get.then.res (/opt/iobr

radar2.0
2020-04-30 06:02:14.472
warn
(17084) adapter.objects.getObjectList is deprecated, and will be  removed in the future. Please use adapter.getObjectList/Async. Report  this to Developer!

I am not sure which devices you screen but the first entry is because one of the devices return no or an invalid response. The second one is because you use latest js-controller but not latest (from git) radar2.

actually I just spent time getting this and another adapter up and running .. I didn't really use it .. so all must be default. But I will delete the object tree .. maybe there are some legacy objects from a former try.

My output after deleting the objects and restarting the adapter:

radar2.0
2020-05-01 06:16:35.387
info
(32753) radar2 set use of noble(true), doArp("-lgq --retry=5  --timeout=400" on ens18), btid(0) and doUwz(UWZDE14612,120,0,de,true).

radar2.0
2020-05-01 06:16:35.387
info
(32753) radar2 found 6 devices in config (Ich-,Fritzbox,G-Tags,HP-7520-,ECB-,Forum)

radar2.0
2020-05-01 06:16:35.178
info
(32753) will scan printers  [ 'HP-7520-' ]  every  720  minutes

radar2.0
2020-05-01 06:16:34.851
info
(32753) UWZ found the following (changed) warnings: Am  Freitagnachmittag und -abend besteht ein leichtes Risiko für teils  kräftige Schauer und örtliche Gewitter, die vereinzelt mit Starkregen um  10 L

radar2.0
2020-05-01 06:16:34.751
info
(32753) Will scan ECB for  [ 'USD,RUB,GBP' ]  every  60  minutes

radar2.0
2020-05-01 06:16:34.747
info
(32753) will scan UWZ with code UWZDE14612 every 120 minutes

radar2.0
2020-05-01 06:16:33.873
warn
(32753) adapter.objects.getObjectList is deprecated, and will be  removed in the future. Please use adapter.getObjectList/Async. Report  this to Developer!

radar2.0
2020-05-01 06:16:33.872
info
bts: (01:23:45:56:78:89:90,01:23:45:56:78:89:99)

radar2.0
2020-05-01 06:16:33.872
info
ips: (<IP_ADDRESS>,::1,<IP_ADDRESS>),

radar2.0
2020-05-01 06:16:33.872
info
(32753) Adapter identified macs: (12:34:56:78:90:12,44:4e:6d:29:c9:a8),

radar2.0
2020-05-01 06:16:33.853
info
(32753) New external IP address <IP_ADDRESS>

radar2.0
2020-05-01 06:16:33.671
info
(32753) Init item Forum with { name: 'Forum',ip:  'https://forum.iobroker.net',id: 'Forum',type: 'URL',lasthere:  '2020-05-01T06:14:33.550Z',anwesend: false }

radar2.0
2020-05-01 06:16:33.570
info
(32753) Init item ECB- with { name: 'ECB-', ip: 'USD,RUB,GBP', id: 'ECB', type: 'ECB' }

radar2.0
2020-05-01 06:16:33.543
info
(32753) Init item HP-7520- with { name: 'HP-7520-',ip: 'HPC56C03-PS7520',id: 'HP-7520',type: 'printer' }

radar2.0
2020-05-01 06:16:33.487
info
(32753) Init item G-Tags with { name: 'G-Tags',bluetooth: [  '01:23:45:56:78:89:90', '01:23:45:56:78:89:99' ],id: 'G-Tags',type:  'BT',btVendor: 'Vendor N/A',lasthere: '2020-05-01T06:14:33.367Z',anwese

radar2.0
2020-05-01 06:16:33.419
info
(32753) Init item Fritzbox with { name: 'Fritzbox',id: 'Fritzbox',type:  'IP',hasMAC: [ '12:34:56:78:90:12', '44:4e:6d:29:c9:a8' ],ipVendor:  'Vendor N/A',rip: [ '<IP_ADDRESS>', '<IP_ADDRESS>' ],last

radar2.0
2020-05-01 06:16:33.321
warn
(32753) ip address <IP_ADDRESS> in Fritzbox was used already for another device Fritzbox, this is forbidden!

radar2.0
2020-05-01 06:16:33.309
info
(32753) Init item Ich- with { name: 'Ich-',id: 'Ich',type: 'IP',rip: [  '<IP_ADDRESS>', '::1' ],lasthere: '2020-05-01T06:14:33.186Z',anwesend:  false }

radar2.0
2020-05-01 06:16:32.793
info
(32753) Will try to scan BT devices: true

radar2.0
2020-05-01 06:16:32.765
info
(32753) radar2 set to scan every 20 seconds and printers every 720 minutes.

radar2.0
2020-05-01 06:16:32.765
info
(32753) arp-scan will use the following interfaces: [ 'ens18' ]

radar2.0
2020-05-01 06:16:32.764
info
(32753) Remove name end for host names: .fritz.box

radar2.0
2020-05-01 06:16:32.764
info
(32753) use known IP list: [ '<IP_ADDRESS>' ]

radar2.0
2020-05-01 06:16:32.764
info
(32753) use known BT list: [ '01:12:23:34:45:56' ]

radar2.0
2020-05-01 06:16:32.763
info
(32753) radar2 set to flag items away if they are not seen for 2 minutes

radar2.0
2020-05-01 06:16:32.762
warn
(32753) node-bluetooth not found!

radar2.0
2020-05-01 06:16:32.751
info
(32753) found '@abandonware/noble'

radar2.0
2020-05-01 06:16:32.609
info
(32753) Connected with '<IP_ADDRESS>' for DHCP Scan

radar2.0
2020-05-01 06:16:32.532
info
(32753) net-ping not available! Will try to use normal ping!

radar2.0
2020-05-01 06:16:32.519
info
(32753) radar2 initialization started...

radar2.0
2020-05-01 06:16:32.435
warn
(32753) adapter.objects.getObjectList is deprecated, and will be  removed in the future. Please use adapter.getObjectList/Async. Report  this to Developer!

radar2.0
2020-05-01 06:16:32.375
info
(32753) starting. Version 1.0.9 in /opt/iobroker/node_modules/iobroker.radar2, node: v10.20.1, js-controller: 3.0.20

Can you load the latest adapter from git and check? The objlist warning shoul be gon, everything else is normal.

Yes .. that one is gone. I installed via git and the situation I have now is that the installation worked but I get an adapter update in the adapter list. Installed 1.2.0 Available 1.2.3 .. is there any variable possibly have forgotten to update?

Same issue here, always shows 1.2.3 is available even though it's already installed.

Updated to  1.2.5 on git and npm working on my old node v8 controller 2.x and node v12 controller 3.x now, changed also in text.  p.s. if you run it on Windows you cannot use hcitools!

don't know whom this Windows comment adresses .. I'm on Ubuntu VM in Proxmox

But you found an old screenshot on the forum without the hci-tool switch!

oh .. yes .. that was not mine :-)


Add WAAS status to webUI. Correct unit casting error on ownship alt.

Adds "DGPS (WAAS)" vs "3D GPS" status to webUI status page.
Change unit casting on ownship altitude such that negative pressure altitudes are properly displayed.

ForeFlight 7.4.1 still bugs out and thinks ownship is at FL1013 if I pass 0xFFF.


Add trait to return a models last activity as a relation

This adds a new trait that can be added to models that already use the activity log. The trait allows the model to have the last activity as a relation of the model or models.
This trait is inspired by this article by Jonathan Reinink.
$newsItem = NewsItem::withLastActivity()->first();

$newsItem->lastActivity // Activity model

Or multiple models.
$newsItems = NewsItem::withLastActivity()->get();

$newsItems[0]->lastActivity // Activity model

You can also specify the event type to return, such as 'created' or 'updated'.
$newsItem = NewsItem::withLastActivity('updated')->first();

There's a special Laravel has one of many relationship which doesn't need any subquery or scopes.

Thanks, I wasn't aware of the has one of many relationship. I updated the PR with this relationship but the tests are now failing. I think I'll just make this a trait in my own app.


Feat: Suggest CW20 Token

Hello, as described in issue #177 ,I am working on an implementation for CW20 token suggestion, if you have any feedback or suggestions I am open to any discussion, thanks!

awesome work @DavideSegullo !!! thinking to make this more flexible in the future, we should either rename the function, or add a parameter. Perhaps the parameter option is more flexible/generic.

awesome work @DavideSegullo !!! thinking to make this more flexible in the future, we should either rename the function, or add a parameter. Perhaps the parameter option is more flexible/generic.

Yes, I'll also add some examples

@pyramation It seems fine, I also added an example


Add labels for meters

To introduce a label to the meter to describe what figure shows

Works for me

changed style of text meters (request by @evshvarov) in 3.1.14


Fatal error: Uncaught exception

Hi,
we have this Fatal Error when we create a Product for onappuser
Fatal error: Uncaught exception 'Exception' with message 'The wrapper class 'OnApp_Role' does not support OnApp version '0'' in /var/www/includes/wrapper/OnApp.php:751 Stack trace: #0 /var/www/includes/wrapper/Role.php(115): OnApp->initFields(0, 'OnApp_Role') #1 /var/www/includes/wrapper/OnApp.php(672): OnApp_Role->initFields(0) #2 /var/www/modules/servers/onappusers/onappusers.php(663): OnApp->auth('https://185.76....', 'admin', 'changeme') #3 /var/www/modules/servers/onappusers/onappusers.php(638): OnApp_UserModule->getOnAppObject('OnApp_Role') #4 /var/www/modules/servers/onappusers/onappusers.php(91): OnApp_UserModule->getRoles() #5 /var/www/admin/configproducts.php(0): onappusers_ConfigOptions(Array) #6 {main} Next exception 'Exception' with message 'The wrapper class 'OnApp_Role' does not support OnApp version '0'' in /var/www/includes/classes/WHMCS/Terminus.php:0 Stack trace: #0 [internal function]: WHMCS_Terminus->whmcsExceptionHandler(Object(Exception)) #1 {main} thrown in /var/www/includes/classes/WHMCS/Terminus.php on line 0

Something wrong with getting OnApp version.
Does user 'admin' has permission to get OnApp version?
What is response for https://185.76..../version.json with user 'admin'?

Thanks Lev,
that helped me find the problem, it was a problem in our httpd.conf file
thanks a lot

You are welcome)


DNS server not reachable

Bug description
iOS: 17.2
When I try to connect to a server, I get an error message: IP address could not be retrieved from DNS server.
I have blocked all DNS queries on port 53 for all computers, except for my gateway.
It seems that webssh wants to make dns queries to servers that are not running through my gateway. Could it be that in the iOS version of webssh the dns servers are hard coded?
On MacOS everything works as it should and there are no problems.
Steps to reproduce

Open WebSSH
Click on a server
Error is thrown

Hey @MedicDok 👋
Could you tell me the exact WebSSH version you are running?

iOS version 24.09. (the "about" information shows: 24.8.1244 @ Jan 14 2024 13:02:52)
I have no idea why different information is displayed.
Settings -> About WebSSH (24.8.1244 @ Jan 14 2024 13:02:52)
and
Settings -> About WebSSH -> click on the field (24.09. - Dragon)

I rarely use test flight apps. But I can test a WebSSH beta version if required.

Screenshot:

@MedicDok Are you using IP or domain name for the hostname?
If you are using IP you shouldn't receive a such error and I need to Check what's wrong within WebSSH

That is a good point. I have added all servers with an IP address but it still makes DNS queries

Definitely a bug on my side 😓
I'm making a fix and will push it tonight for beta release
Sorry for the trouble
I'll come back to you shortly

A possible fix has been pushed to TestFlight. Waiting for approval.
I'll come back to you when available in a few hours

Hello @MedicDok 👋
Could you try this release please ?
https://testflight.apple.com/join/QSrBK59z
It contains fix about IP addresses

Still the same error message.

@MedicDok Please post your verbose logs :
https://webssh.net/documentation/help/howtos/enabling-verbose-logging/
They will contain some data to find the root cause

I have looked at the log file. The correct DNS server is being used. The IP address from where WebSSH wants to connect is also correct. But it is still unclear why it wants to make a DNS query for an IP address.
log-20240123.txt

@MedicDok Perfect!
Please confirm me that you have a trailing space on IP :
Resolving '45.xxx.xxx.xxx '...
If it's the case then I will be able to fix this issue on my side.
Sorry again

Original file: 9 '...
I can confirm, that there is a space after the IP.

🙏
A fix is on its way

Fix now available on WebSSH 24.9.1250 : https://testflight.apple.com/join/QSrBK59z

Bug is fixed!

@MedicDok Many thanks for your feedback 🙏
24.9 release will be pushed soon to the App Store
I wish you a nice day ☀


About web worker

Hi, do you know how to combine yuv-canvas with web-worker? It I want to use offscreen canvas, it seems that I have to rewrite yuv-canvas.

My project produces frames in a web worker, postMessages them to the main thread (transferring the buffers to avoid additional copies), and then the main thread uses yuv-canvas directly.
I don't know anything about offscreen canvas or what that entails.

I need to draw multiple videos on one page, but yuv-Canvas has a lot of calculation, which makes the page very slow.
I want to perform calculations in a Web worker. Can I do that

I need to draw multiple videos on one page, but yuv-Canvas has a lot of calculation, which makes the page very slow. I want to perform calculations in a Web worker. Can I do that

解决了吗兄弟？

Hello,
If anyone still needs an answer to this question: yes, it's possible to use yuv-canvas in a web worker with some small changes.
This function now crashes if you try to use it in a web worker:
https://github.com/brion/yuv-canvas/blob/main/src/WebGLFrameSink.js#L472

It crashes because it cannot find the document, this object is not available in the web worker.
So you can move the feature detection outside of the web worker in the main thread, attach the status to a window variable, example (if you want you can copy the feature detection from the original WebGLFrameSink.isAvailable function with small changes):
function webGLDetection() {
        // do the detection here...
	return true;
}

window.webGLAvailable = webGLDetection();

Then you can modify the WebGLFrameSink.isAvailable function by using the window variable:
	WebGLFrameSink.isAvailable = function() {
		return window.webGLAvailable;
	}

Then in the web worker where you include the bundle script you need to declare the window variable before you include the JS file.
window = globalThis;

importScripts('./js/bundle.js');

Hope this helps to give you an idea and that I didn't miss anything.
Cheers,
Mihail


cannot reproduce your results

It's really a great job, but I cannot reproduce the result, it sounds not good, here is some information

https://user-images.githubusercontent.com/24654967/223609715-001d551c-ef0f-4f73-9f58-28b8c2de37b3.mp4
https://user-images.githubusercontent.com/24654967/223609722-890dba1f-da34-45b4-bb1b-6c48e54350f2.mp4
so, what could be the problem?

your data contains many speakers? Not opencpop?

muti-speaker version is under development

your data contains many speakers? Not opencpop?

no, I found it is a any2one voice conversion, so my train data contains only one speaker(use biaobei-BZNSYP as train dataset), but my test data has many speakers to test the performance

voice conversion is so different from singing voice conversion; nsf is not very suitable for VC. VC should use quantized f0 or logf0 as input.

it is a good idear to use biaobei-BZNSYP for train. i will try it also @JeffC0628

voice conversion is so different from singing voice conversion; nsf is not very suitable for VC. VC should use quantized f0 or logf0 as input.

this is the key point, I will try the quantized f0 or logf0 as input, thanks for your reply,  appreciate it

voice conversion is so different from singing voice conversion; nsf is not very suitable for VC. VC should use quantized f0 or logf0 as input.

想问下，对于语音转换， 不用nsf-hifigan 用hifigan好些？所以是基于vits 输入ppg+加量化f0 ---> wav  波形？


OSSM-6731: added the 2.6 version for Somke test

@pbajjuri20 nice catch :+1: , I have forgot about that in https://github.com/maistra/maistra-test-tool/pull/692


Build testcentric.engine.core for .NET Core 3.1

This will allow us to use .NET Core 3.1 features for loading dependencies and pave the way for a .NET 6.0 implementation as well.

:tada: This issue has been resolved in version 2.0.0-alpha7 :tada:
The release is available on:

GitHub Release
NuGet Package


iOS Share sheet callback

We should have a callback from the share sheet for iOS as well as android. I need to be able to run additional code only after a successful share.

Hey @zanemcca - Just to give you an update, we're adding this feature in now and will submit a PR today or tomorrow. Thanks for the request!

Awesome thanks a lot @aaustin

Hey @zanemcca ,
Just have submitted PR #145 for the iOS share sheet callback.
Let me know if this resolves the issue. 👍

👍

Hey @renesansz ,
Thanks a lot for the quick response. I had a look and it is almost there except we need a corresponding success callback to go along with the dismiss. There is a completed flag that could be used to distinguish between the two.
Could it be possible to call onShareSheetDismissed for completed = False and then call onLinkShareResponse with the activityType passed as the result otherwise?

Or just match the functionality of Android.
I am not really sure why there are so many different callbacks in the first place. Why not just return a promise that is resolved if there is a sharedChannel/activityType and reject it otherwise?
This would also make it match the generateShortUrl syntax.

@zanemcca ,
I see, I have taken a look with iOS SDK but I'm not sure if its share sheet callbacks are consistent with Android SDK. Sure, I'll try to make some changes and update the PR 👍 .

@zanemcca , I've made some additional updates in the PR, however, the callbacks aren't complete as the Android (missing: onChannelSelected & onShareSheetLaunched).
Let me know of your thoughts 👌

@renesansz ,
Thanks again for the speedy reply. I took a look and everything seems to be functioning properly.
The last thing that would be great to have is if the format of the response was identical to androids.
{
  sharedLink: 'https://blahblah.com/1234/asdfjknasdkfjn',
  sharedChannel: 'com.google.Gmail.ShareExtension'
}

Having this would make handling the response identical for both platforms and it gives us access to the sharedLink and sharedChannel which are both nice things to save.
Sorry for being picky. I would do it myself but my Objective-C knowledge is basically non-existent.

@zanemcca ,
Sure, I'll update the response being returned from the callback.
No worries 👌

@zanemcca , Updated PR to return sharedLink & sharedChannel for the callback response.
Let me know if this will satisfy your needs.

Thanks a lot @renesansz!
That will definitely be enough to satisfy my needs 👍

Merged and deployed https://github.com/BranchMetrics/Cordova-Ionic-PhoneGap-Deferred-Deep-Linking-SDK/pull/145