Electron-forge unable to make for target Squirrel for arch x64

Preflight Checklist

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] I have searched the issue tracker for a bug that matches the one I want to file, without success.

Issue Details

Electron Forge Version:
6.0.0-beta.45
Electron Version:
11.4.1
Operating System:
Ubuntu 20.04.1 LTS x64

Expected Behavior
expected electron forge to make squrriel.windows application.
Actual Behavior
obtained error specifying that electron forge was unable to make target for squirrel.
✖ Making for target: squirrel - On platform: win32 - For arch: x64
An unhandled error has occurred inside Forge:
An error occured while making for target: squirrel
spawn mono ENOENT
Error: spawn mono ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19)
at onErrorNT (internal/child_process.js:415:16)
at process._tickCallback (internal/process/next_tick.js:63:19)
Additional Information
package.json
{
"name": "electron-chat-app",
"version": "1.0.0",
"description": "chat  application using electron,webrtc,react,socket.io",
"main": "./app/main.api.ws.js",
"scripts": {
"start": "electron-forge start",
"build": "electron-packager . --overwrite --arch x64 --platform win32",
"test": "echo "Error: no test specified" && exit 1",
"package": "electron-forge package",
"make": "electron-forge make . --overwrite --arch x64 --platform win32"
},
"author": "uncle-shaggy",
"license": "ISC",
"devDependencies": {
"@babel/core": "^7.12.16",
"@babel/preset-env": "^7.12.16",
"@babel/preset-stage-0": "^7.8.3",
"@electron-forge/cli": "^6.0.0-beta.54",
"@electron-forge/maker-appx": "^6.0.0-beta.54",
"@electron-forge/maker-deb": "^6.0.0-beta.54",
"@electron-forge/maker-rpm": "^6.0.0-beta.54",
"@electron-forge/maker-squirrel": "^6.0.0-beta.54",
"@electron-forge/plugin-compile": "^6.0.0-beta.54",
"@electron-forge/publisher-github": "^6.0.0-beta.54",
"babel-plugin-transform-async-to-generator": "^6.24.1",
"babel-preset-env": "^1.7.0",
"babel-preset-react": "^6.24.1",
"electron": "^11.4.1",
"webpack-cli": "^4.5.0"
},
"dependencies": {
"@babel/cli": "^7.12.10",
"@babel/preset-react": "^7.12.13",
"@babel/runtime": "^7.12.13",
"acorn": "^8.0.4",
"babel": "^6.23.0",
"babel-cli": "^6.26.0",
"babel-core": "^6.26.3",
"babel-loader": "^8.2.2",
"babel-plugin-object-rest-spread": "0.0.0",
"babel-plugin-transform-object-rest-spread": "^6.26.0",
"babel-preset-es2016-node5": "^1.1.2",
"babel-preset-stage-0": "^6.24.1",
"debug": "^4.3.1",
"electron-squirrel-startup": "^1.0.0",
"eslint": "^7.17.0",
"localforage": "^1.9.0",
"madge": "^4.0.0",
"moment": "^2.29.1",
"mongodb": "^3.6.4",
"prop-types": "^15.7.2",
"react": "^17.0.1",
"react-dom": "^17.0.1",
"redux": "^4.0.5",
"socket.io": "^3.1.0",
"socket.io-client": "^3.1.0",
"svg-url-loader": "^7.1.1",
"webpack": "^4.46.0",
"websocket": "^1.0.33",
"ws": "^7.4.3",
"wscat": "^4.0.1"
},
"config": {
"forge": {
"packagerConfig": {
"packageManager": "npm"
},
"makers": [
{
"name": "@electron-forge/maker-deb",
"config": {
"name": "electron_chat_app"
},
"platforms": [
"darwin",
"linux"
]
},
{
"name": "@electron-forge/maker-rpm",
"platforms": [
"linux"
],
"config": {}
},
{
"name": "@electron-forge/maker-squirrel",
"config": {
"name": "electron_chat_app"
},
"platforms": [
"win32"
]
},
{
"name": "@electron-forge/maker-appx",
"config": {
"packageName": "",
"name": "electronchatapp"
},
"platforms": []
}
],
"publishers": [
{
"config": {
"repository": {
"name": "",
"owner": ""
}
},
"name": "@electron-forge/publisher-github",
"platforms": []
}
]
}
}
}

Install mono if you're trying to create a Squirrel installer on non-Windows.

If you need more assistance, please use one of the community forums, including the Electron Discord server.


feat: port Data.Num.Lemmas

[ ] depends on: #2780
[ ] depends on: #2781
[ ] depends on: #2782
[ ] depends on: #2783

This PR/issue depends on:

leanprover-community/mathlib4#2780
leanprover-community/mathlib4#2781
leanprover-community/mathlib4#2782
leanprover-community/mathlib4#2783
By Dependent Issues (🤖). Happy coding!

bors merge


When in /r/all the sub specific removal reasons are ignored when removing from a sub you mod

I was in /r/all, found a post I wanted to remove from a sub I mod (/r/InternetIsBeautiful) and we have custom removal reasons. I clicked the Remove option and it came up with the empty removal reason box, and not the sub specific removal reasons.
I DO have the setting enabled to show a empty removal reason box if there are no removal reasons configured.
Image: https://i.gyazo.com/f5e00cce497e411f9569861f2a83d45c.png
Toolbox settings backup: http://pastebin.com/EXcCru91

Note to self and others, the fix for this likely lies here: https://github.com/creesch/reddit-moderator-toolbox/blob/master/tbutils.js#L10
Also, why do we do that on line 10 then this: https://github.com/creesch/reddit-moderator-toolbox/blob/master/tbutils.js#L118
I think we could clean those all into one big if.  Or maybe have and a array of invalid post_site vals and just do an indexOf.


set entity._template to true for template root

This PR adds a private boolean field on Entity called _template.
It can be used to differentiate between the entities of a template root instance,
used internally by the template instantiation mechanism, and the template instances
created by users at runtime (their entities have this flag set to false).
Template instances are created by cloning the root instance.
I confirm I have signed the Contributor License Agreement.

It is set on all entities of a template, I don’t think it can have other children at parse time


Data lake small refactors

Use Objects.require non null instead of ImplUtils in get FileSystemAsyncClient.getDirectoryClient

Add sample for creating a directory client and putting a file under it? That way we show all the basic client types.


Fix example for usage still not published uuid 2.0.0

IMHO There some inconsistency in https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#prepublishing-a-breaking-change
We have unpublished version 2.0.0 for uuid crate in branch with same name.
Now we can test it in my-library without waiting for publish as written in docs.
But if my-library changes committed to its master, for my-binary patch need be same as in library,
as uuid 2.0.0 still not published.

@bors: r+
Looks good to me, thanks!

:pushpin: Commit 45dea1431ec9a888e0d6e89c1c70d02ac82a4784 has been approved by alexcrichton

:hourglass: Testing commit 45dea1431ec9a888e0d6e89c1c70d02ac82a4784 with merge b0679d55afc25ad9f3084aa7204683f5f8b4fc15...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing b0679d55afc25ad9f3084aa7204683f5f8b4fc15 to master...


feat(elements): Add /sign-in export, remove hardcoded paths

Description

Moves sign-in components to a /sign-in export. Also refactors the machine to not rely on hardcoded sign in paths, instead deriving the base path from the Clerk router.

Checklist

[x] npm test runs as expected.
[x] npm run build runs as expected.
[x] (If applicable) JSDoc comments have been added or updated for any package exports
[x] (If applicable) Documentation has been updated

Type of change

[ ] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[x] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[ ] @clerk/backend
[ ] @clerk/chrome-extension
[ ] @clerk/clerk-js
[ ] @clerk/clerk-expo
[ ] @clerk/fastify
[ ] gatsby-plugin-clerk
[ ] @clerk/localizations
[ ] @clerk/nextjs
[ ] @clerk/clerk-react
[ ] @clerk/remix
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/themes
[ ] @clerk/types
[ ] build/tooling/chore

!snapshot

Hey @BRKalow - the snapshot version command generated the following package versions:

Package
Version

@clerk/backend
1.0.1-snapshot.vc65ad98

@clerk/chrome-extension
1.0.1-snapshot.vc65ad98

@clerk/clerk-js
5.0.1-snapshot.vc65ad98

@clerk/elements
0.0.2-snapshot.vc65ad98

@clerk/clerk-expo
1.0.1-snapshot.vc65ad98

@clerk/fastify
1.0.1-snapshot.vc65ad98

gatsby-plugin-clerk
5.0.1-snapshot.vc65ad98

@clerk/localizations
2.0.1-snapshot.vc65ad98

@clerk/nextjs
5.0.1-snapshot.vc65ad98

@clerk/clerk-react
5.0.1-snapshot.vc65ad98

@clerk/remix
4.0.1-snapshot.vc65ad98

@clerk/clerk-sdk-node
5.0.1-snapshot.vc65ad98

@clerk/shared
2.0.1-snapshot.vc65ad98

@clerk/themes
2.0.1-snapshot.vc65ad98

@clerk/types
4.0.1-snapshot.vc65ad98

Tip: Use the snippet copy button below to quickly install the required packages.
@clerk/backend
npm i<EMAIL_ADDRESS>--save-exact

@clerk/chrome-extension
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-js
npm i<EMAIL_ADDRESS>--save-exact

@clerk/elements
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-expo
npm i<EMAIL_ADDRESS>--save-exact

@clerk/fastify
npm i<EMAIL_ADDRESS>--save-exact

gatsby-plugin-clerk
npm i<EMAIL_ADDRESS>--save-exact

@clerk/localizations
npm i<EMAIL_ADDRESS>--save-exact

@clerk/nextjs
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-react
npm i<EMAIL_ADDRESS>--save-exact

@clerk/remix
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-sdk-node
npm i<EMAIL_ADDRESS>--save-exact

@clerk/shared
npm i<EMAIL_ADDRESS>--save-exact

@clerk/themes
npm i<EMAIL_ADDRESS>--save-exact

@clerk/types
npm i<EMAIL_ADDRESS>--save-exact

!snapshot

Hey @BRKalow - the snapshot version command generated the following package versions:

Package
Version

@clerk/backend
1.0.1-snapshot.v8b7e4f0

@clerk/chrome-extension
1.0.1-snapshot.v8b7e4f0

@clerk/clerk-js
5.0.1-snapshot.v8b7e4f0

@clerk/elements
0.0.2-snapshot.v8b7e4f0

@clerk/clerk-expo
1.0.1-snapshot.v8b7e4f0

@clerk/fastify
1.0.1-snapshot.v8b7e4f0

gatsby-plugin-clerk
5.0.1-snapshot.v8b7e4f0

@clerk/localizations
2.0.1-snapshot.v8b7e4f0

@clerk/nextjs
5.0.1-snapshot.v8b7e4f0

@clerk/clerk-react
5.0.1-snapshot.v8b7e4f0

@clerk/remix
4.0.1-snapshot.v8b7e4f0

@clerk/clerk-sdk-node
5.0.1-snapshot.v8b7e4f0

@clerk/shared
2.0.1-snapshot.v8b7e4f0

@clerk/themes
2.0.1-snapshot.v8b7e4f0

@clerk/types
4.0.1-snapshot.v8b7e4f0

Tip: Use the snippet copy button below to quickly install the required packages.
@clerk/backend
npm i<EMAIL_ADDRESS>--save-exact

@clerk/chrome-extension
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-js
npm i<EMAIL_ADDRESS>--save-exact

@clerk/elements
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-expo
npm i<EMAIL_ADDRESS>--save-exact

@clerk/fastify
npm i<EMAIL_ADDRESS>--save-exact

gatsby-plugin-clerk
npm i<EMAIL_ADDRESS>--save-exact

@clerk/localizations
npm i<EMAIL_ADDRESS>--save-exact

@clerk/nextjs
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-react
npm i<EMAIL_ADDRESS>--save-exact

@clerk/remix
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-sdk-node
npm i<EMAIL_ADDRESS>--save-exact

@clerk/shared
npm i<EMAIL_ADDRESS>--save-exact

@clerk/themes
npm i<EMAIL_ADDRESS>--save-exact

@clerk/types
npm i<EMAIL_ADDRESS>--save-exact

!snapshot

Hey @BRKalow - the snapshot version command generated the following package versions:

Package
Version

@clerk/backend
1.0.1-snapshot.vcaceed6

@clerk/chrome-extension
1.0.1-snapshot.vcaceed6

@clerk/clerk-js
5.0.1-snapshot.vcaceed6

@clerk/elements
0.0.2-snapshot.vcaceed6

@clerk/clerk-expo
1.0.1-snapshot.vcaceed6

@clerk/fastify
1.0.1-snapshot.vcaceed6

gatsby-plugin-clerk
5.0.1-snapshot.vcaceed6

@clerk/localizations
2.0.1-snapshot.vcaceed6

@clerk/nextjs
5.0.1-snapshot.vcaceed6

@clerk/clerk-react
5.0.1-snapshot.vcaceed6

@clerk/remix
4.0.1-snapshot.vcaceed6

@clerk/clerk-sdk-node
5.0.1-snapshot.vcaceed6

@clerk/shared
2.0.1-snapshot.vcaceed6

@clerk/themes
2.0.1-snapshot.vcaceed6

@clerk/types
4.0.1-snapshot.vcaceed6

Tip: Use the snippet copy button below to quickly install the required packages.
@clerk/backend
npm i<EMAIL_ADDRESS>--save-exact

@clerk/chrome-extension
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-js
npm i<EMAIL_ADDRESS>--save-exact

@clerk/elements
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-expo
npm i<EMAIL_ADDRESS>--save-exact

@clerk/fastify
npm i<EMAIL_ADDRESS>--save-exact

gatsby-plugin-clerk
npm i<EMAIL_ADDRESS>--save-exact

@clerk/localizations
npm i<EMAIL_ADDRESS>--save-exact

@clerk/nextjs
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-react
npm i<EMAIL_ADDRESS>--save-exact

@clerk/remix
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-sdk-node
npm i<EMAIL_ADDRESS>--save-exact

@clerk/shared
npm i<EMAIL_ADDRESS>--save-exact

@clerk/themes
npm i<EMAIL_ADDRESS>--save-exact

@clerk/types
npm i<EMAIL_ADDRESS>--save-exact

!snapshot

Hey @BRKalow - the snapshot version command generated the following package versions:

Package
Version

@clerk/backend
1.0.1-snapshot.v7e9c51b

@clerk/chrome-extension
1.0.1-snapshot.v7e9c51b

@clerk/clerk-js
5.0.1-snapshot.v7e9c51b

@clerk/elements
0.0.2-snapshot.v7e9c51b

@clerk/clerk-expo
1.0.1-snapshot.v7e9c51b

@clerk/fastify
1.0.1-snapshot.v7e9c51b

gatsby-plugin-clerk
5.0.1-snapshot.v7e9c51b

@clerk/localizations
2.0.1-snapshot.v7e9c51b

@clerk/nextjs
5.0.1-snapshot.v7e9c51b

@clerk/clerk-react
5.0.1-snapshot.v7e9c51b

@clerk/remix
4.0.1-snapshot.v7e9c51b

@clerk/clerk-sdk-node
5.0.1-snapshot.v7e9c51b

@clerk/shared
2.0.1-snapshot.v7e9c51b

@clerk/themes
2.0.1-snapshot.v7e9c51b

@clerk/types
4.0.1-snapshot.v7e9c51b

Tip: Use the snippet copy button below to quickly install the required packages.
@clerk/backend
npm i<EMAIL_ADDRESS>--save-exact

@clerk/chrome-extension
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-js
npm i<EMAIL_ADDRESS>--save-exact

@clerk/elements
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-expo
npm i<EMAIL_ADDRESS>--save-exact

@clerk/fastify
npm i<EMAIL_ADDRESS>--save-exact

gatsby-plugin-clerk
npm i<EMAIL_ADDRESS>--save-exact

@clerk/localizations
npm i<EMAIL_ADDRESS>--save-exact

@clerk/nextjs
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-react
npm i<EMAIL_ADDRESS>--save-exact

@clerk/remix
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-sdk-node
npm i<EMAIL_ADDRESS>--save-exact

@clerk/shared
npm i<EMAIL_ADDRESS>--save-exact

@clerk/themes
npm i<EMAIL_ADDRESS>--save-exact

@clerk/types
npm i<EMAIL_ADDRESS>--save-exact

This PR was superseded by https://github.com/clerk/javascript/pull/2725 and https://github.com/clerk/javascript/pull/2676


Build is not running on Debian derived distros

The import in Debian derived distros should be <crypto++/...> instead of <cryptopp/...>

The real problem is that the file rdrand.h is not present in cryptopp prior to the 5.6.3 version.

Created a docker build process using Crypto++ 5.6.5.


Add hook for data seralisation

What
Make it possible for operations to complete the operation with error when data serialisation fails
How
Added new serialise hook which is a throwing function which allows operations to error when attempting to transform the data to json.
Reviewers

+1


I want to see Character name, NOT steam name.

Hi, I want to see the character name of the players and not the steam name it keeps forcing me to show in the scoreboard.

I have the same problem. so I also want to have character names in game!

#5


Exception: HTTPError

Bug report
Your Environment

Netflix add-on version: plugin.video.netflix_1.3.1_20200519_t16.zip, but same with 1.3.1 from repo
Operating system version/name: OSMC 2020.03-1
Device model:  RPI3 b+

Used Operating system:

[ ] Android
[ ] iOS
[ ] Linux
[ ] OSX
[X] Raspberry-Pi
[ ] Windows

Describe the bug
When is want to start the netlix app i receive an error: Exception HTTPError
Expected behavior
Netflix start
Actual behavior
Netflix cannot start
Steps to reproduce the behavior
Start netflix app
Possible fix
I checked, i have internet access and the netflix is working from an other device.
Debug log
2020-05-19 23:33:16.619 T:1915647536   ERROR: Control 55 in window 10025 has been asked to focus, but it can't
2020-05-19 23:33:21.959 T:1669325536   ERROR: [plugin.video.netflix (0)] IPC callback raised exception: 500 Server Error: Internal Server Error for url: https://www.netflix.com/browse
2020-05-19 23:33:21.970 T:1669325536   ERROR: [plugin.video.netflix (0)] Traceback (most recent call last):
File "/home/osmc/.kodi/addons/plugin.video.netflix/resources/lib/common/ipc.py", line 178, in make_return_call
result = call(instance, func, data)
File "/home/osmc/.kodi/addons/plugin.video.netflix/resources/lib/common/ipc.py", line 202, in call
return func(instance)
File "/home/osmc/.kodi/addons/plugin.video.netflix/resources/lib/services/nfsession/nfsession_base.py", line 37, in ensure_login
return func(*args, **kwargs)
File "/home/osmc/.kodi/addons/plugin.video.netflix/resources/lib/services/nfsession/nfsession.py", line 82, in fetch_initial_page
response = self._get('browse')
File "/home/osmc/.kodi/addons/plugin.video.netflix/resources/lib/services/nfsession/nfsession_requests.py", line 45, in _get
**kwargs)
File "/home/osmc/.kodi/addons/plugin.video.netflix/resources/lib/common/logging.py", line 143, in timing_wrapper
return func(*args, **kwargs)
File "/home/osmc/.kodi/addons/plugin.video.netflix/resources/lib/services/nfsession/nfsession_requests.py", line 55, in _request_call
return self._request(method, endpoint, None, **kwargs)
File "/home/osmc/.kodi/addons/plugin.video.netflix/resources/lib/services/nfsession/nfsession_requests.py", line 92, in _request
response.raise_for_status()
File "/home/osmc/.kodi/addons/script.module.requests/lib/requests/models.py", line 940, in raise_for_status
raise HTTPError(http_error_msg, response=self)
HTTPError: 500 Server Error: Internal Server Error for url: https://www.netflix.com/browse
2020-05-19 23:33:22.002 T:1443881696   ERROR: [plugin.video.netflix (4)] IPC call fetch_initial_page returned HTTPError: 500 Server Error: Internal Server Error for url: https://www.netflix.com/browse
2020-05-19 23:33:22.012 T:1443881696   ERROR: [plugin.video.netflix (4)] Traceback (most recent call last):
File "/home/osmc/.kodi/addons/plugin.video.netflix/resources/lib/run_addon.py", line 207, in run
route([part for part in g.PATH.split('/') if part])
File "/home/osmc/.kodi/addons/plugin.video.netflix/resources/lib/run_addon.py", line 38, in lazy_login_wrapper
return func(*args, **kwargs)
File "/home/osmc/.kodi/addons/plugin.video.netflix/resources/lib/run_addon.py", line 72, in route
_execute(nav_handler, pathitems[1:], g.REQUEST_PARAMS)
File "/home/osmc/.kodi/addons/plugin.video.netflix/resources/lib/run_addon.py", line 100, in _execute
executor(pathitems=pathitems)
File "/home/osmc/.kodi/addons/plugin.video.netflix/resources/lib/navigation/directory.py", line 59, in root
common.make_call('fetch_initial_page')
File "/home/osmc/.kodi/addons/plugin.video.netflix/resources/lib/common/logging.py", line 143, in timing_wrapper
return func(*args, **kwargs)
File "/home/osmc/.kodi/addons/plugin.video.netflix/resources/lib/common/ipc.py", line 87, in make_call
return make_addonsignals_call(callname, data)
File "/home/osmc/.kodi/addons/plugin.video.netflix/resources/lib/common/ipc.py", line 155, in make_addonsignals_call
_raise_for_error(callname, result)
File "/home/osmc/.kodi/addons/plugin.video.netflix/resources/lib/common/ipc.py", line 168, in _raise_for_error
raise Exception(result['error'])
Exception: HTTPError
2020-05-19 23:33:24.138 T:1581232864   ERROR: GetDirectory - Error getting plugin://plugin.video.netflix/
2020-05-19 23:33:24.159 T:1915647536   ERROR: CGUIMediaWindow::GetDirectory(plugin://plugin.video.netflix/) failed
Additional context or screenshots (if appropriate)
Installation

[X] I'm using other Netflix Repo
[ ] I'm using a different source

Other information

Screenshots

http error 500 is not an addon error is a netflix server problem
if still persists in next days the only thing you can try is settings>Logout and relogin


Enable immediate reducer to return xtensor instead of xarray

Need to work some template magic to return xtensor's if possible.

fixed by #781


[Regression] Setting time manually will not re-render

Currently, while paused, the last result buffer will be drawn instead of re-running the command. I'm not sure how we want to handle this. Any suggestions, @luckyxxl ?

This also affects resizing it seems - when paused, the "history buffer" from accumulation is resized and reset to black it seems.
Also, what I was just thinking about: The accumulation effects are totally dependent on framerate right now, right? We should maybe try to fix this as well. Can we use different mixing factors depending on delta time?

Did you mean this as the fix for the accumulation? I don't like that you cannot see the accumulation effect at all now if paused. Another approach: If just paused draw the last result, if seeked while paused continue to draw the particles only until play is hit again is a huge hack in my opinion.
I still suggest just rendering the accumulation effect just as it is even while paused, the user should expect that such a time-based difference effect cannot be rendered correctly when paused.

First of all, the wording "huge hack" is not really a good basis for a constructive discussion. Please let me explain my reasoning why I think drawing only particles while paused is the better solution:
I have come to the conclusion, that rendering a frame that corresponds to a particular point in the timeline without context (i.e. a matching history buffer) is impossible when it comes to also getting the accumulation effects correctly. Therefore I don't believe that we should try to fake anything which we just cannot do right.
What you propose has the drawback that things will continue to change after the user has paused. This seems broken to me, i.e. because it's counterintuitive/unexpected to the user in my opinion.
So what would be intuitive? Accumulation effects are essentially blur, and blur happens when things are moving. While paused, nothing is moving. Maybe it would be the most intuitive thing if we never render any accumulation effect at all while paused? On the other hand, rendering the last result on pause is also nice somehow, because it gives you the possibility to view a frame-perfect result. But I'm not completely decided on this.
I also don't think this argument from you holds true at all:

the user should expect that such a time-based difference effect cannot be rendered correctly when paused.

Sorry for the "huge hack", just wanted to express that I don't like that the rendering pipeline now somehow has to check the clock and do state handling for "paused", "paused but seeked" and "render normal" (and detect those state changes).
Ok, our understanding of the accumulation effects differ. While you see a "blur" effect (which could also be implemented non-time based), I explicitly see an "echo" effect, which somehow combines the last rendered frames. During pause, something is rendered, too.
It is true that we can never render the "correct" frame, but I think that previewing the accumulation effect is beneficial and less confusing as a more complex logic like "you can see the current frame including accum effects, but only if you didn't seek before". It also depends whether we see out tool more as a movie editing tool (which should always lead the same results), or as a sequencing tool (which just sets parameters varying over time, yielding different results if you seek or start in the middle). The ladder is quite common for example in music, because it is also very hard/impossible to correctly render something in the middle of a track. And our "change image" and "flickr" effects already work this way, they override the default image and seeking back will not yield the same result.

(which could also be implemented non-time based)

I'm talking about motion blur. I would be interested to see, how one does it non-time-based.

"you can see the current frame including accum effects, but only if you didn't seek before"

Diefferent understanding here as well. As I said, this is a feature. which I am willing to give up if you find it too confusing.

It also depends whether we see out tool more as a movie editing tool [...] or as a sequencing tool

I don't think this matters at all. This is just about what feels the best for the user. And in my opinion, a user wants pause to stop things from happening.

Ok, so I would suggest not adding this feature :)

I don't think this matters at all.

This is exactly what we are discussing right here. Does pause stop/affect rendering or does it stop sequencing? As stated above, I always expected the latter and our "change image" effects already work this way.

As I said, I don't feel it's relevant to decide how we want to categorize our tool. The usability is all that matters. The user doesn't care if sequencing or rendering is stopped. All he cares about is, that stopping actually stops things from happening. The change image effects are just two examples where we fall short of achieving a movie maker, but I'm ok with that. I don't think this is a reason that we should stop trying to make it feel like a WYSIWYG editor.
I think we're at a point now where we discuss the usefulness of the seek feature. If we can't provide a "correct" (whatever that is) rendering on seek, we might as well remove it? But on the other hand, accumulation effects are so irrelevant, I would rather sacrifice those in the preview than the whole seek functionality.

I'm the optionion that a consistent user experience is better than a "good in any case" UE. For change image effects we fall schort, but for accumulation effects we try to minimize "incorrect" results, resulting in that the tool is neither a pure sequencer nor a consistent renderer.
But I don't really care. If it's better to disable accum effects on pause (not that it makes any sense for the user in my opinion), lets do this.

I'm talking about motion blur. I would be interested to see how one does it non-time-based.

I forgot to anwer that. Examples are screen-space per-object motion blur using motion vectors in the gbuffer, or more simple: motion blur based on camera linear velocity and/or angular velocity.


Banner with games playing currently

Banner at top of each page saying what pair is playing on each port, and linking to that port.

Well, it was a long time since Terje suggested that, so i order to bump this up a bit i`ll write alternative suggestion.
Currently main page ccrl*live just redirects to one of the ports. But maybe some auto-generated page with a links to all available ports (possibly with playing engines and/or event name) would be cool.
Too bad i have 0 experience in this so cant really help with coding part

I have no plans at this time to work on features for this project. It is always open to PRs.


Sending a int 0 presents a problem

Qt side
sendBinary("colorPicker", 0);

Qt Output
[SOCKET][BINARY][ "colorPicker" ] QVariant(int, 0)
Binary Data :  "\x81\xAB""colorPicker\x00"

ESP32 side
                if ( mIndata["colorPicker"] )
                {
                    Serial.print("Color Picker : ");
                    Serial.print((int)mIndata["colorPicker"]);
                    Serial.println(" ");

                    if (_isAllStripsSelected == true)
                    {
                        for (int i = 1; i < 9; i++)
                        {
                            Strips[i]->Color.Picker = (int)mIndata["colorPicker"];
                        }
                    }
                    else
                    {
                        Strips[_selectedStrip]->Color.Picker = (int)mIndata["colorPicker"];
                    }
                }

ESP32 Output
empty.........................................

im able to send any number (int) between 1 and<PHONE_NUMBER>8250125 but not 0

Thank you for reporting! Can you give me minimum full code which can reproduce it?

@MythicalForce

Try if my example above works correctly in your environment
Enable debug output and see the debug log

#define MSGPACK_DEBUGLOG_ENABLE
#include <MsgPack.h>

they are not the same notice at the end mine has 00 and yours has 0

What is the difference? Isn't it zero in integer?

@MythicalForce

Try if my example above works correctly in your environment
Enable debug output and see the debug log

#define MSGPACK_DEBUGLOG_ENABLE
#include <MsgPack.h>

they are not the same notice at the end mine has 00 and yours has 0

What is the difference? Isn't it zero in integer?

the difference is that i have a Null Termination at the end \0 and then my 0 so it terminates right after \0 so the 0 escapes


memory size/expectation mismatch, hash()/to_base64()

sdk release 0.3.0, problem general, but periodically manifests as SIGSTOP on azure pipelines CI mac runner, appears because of data that is allocated right up against end of mapped area with nothing mapped beyond
background...
hash.cpp/std::string hash(const std::string &to_sign, const std::vector &key)
defines
        unsigned int digest_length = SHA256_DIGEST_LENGTH;
        unsigned char digest[SHA256_DIGEST_LENGTH];

elsewhere with
include\hash.h:#define SHA256_DIGEST_LENGTH    32

and hash() makes call
        return to_base64(std::vector<unsigned char>(digest, digest + digest_length));

with base64.cpp containing
    std::string to_base64(const std::vector<unsigned char> &input)
    {
        return to_base64(input.data(), input.size());
    }

    std::string to_base64(const unsigned char* input, size_t size)
    {
        auto ptr = input;

        std::string result;
        result.reserve((size / 3 + 1) * 4);

        for (; size >= 3;)
...

Observe that SHA256_DIGEST_LENGTH used to define the memory size ('unsigned char digest[SHA256_DIGEST_LENGTH];') passed into to_base64() is NOT a multiple of 3, but that
the -inner- to_base64() with its for() loop incrementing by 3 expects and processes data as if the memory underLying 'input' will be a multiple of 3.
This leads to falling out of the loop with a length remainder of 2.
The generated code, on the mac at least, appears to be under some circumstances attempting to reference a 3rd byte from the beginning of that last entity.
When the data is not allocated right at the end of the segment, this is presumably referencing logically undefined memory, and hence logically wrong.
If the data of the vector happens to be allocated right at the end of a mapped memory area with NO memory mapped beyond that last address, a SIGSTOP is generated.
Following are debugger snippets from the SIGSTOP situation.
       r11 = 0xfffffff9a36d1c97
       r12 = 0x0000000108103983  "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/"
       r13 = 0x00007ff886cffffe
       r14 = 0x00007ffee8c4bcb8
...
   78  	        {
   79  	            const _triple_byte* record = reinterpret_cast<const _triple_byte*>(ptr);
** 80  	            unsigned char idx0 = record->_0;

    0x107dc825a <+330>: movzwl (%r13), %eax
->  0x107dc825f <+335>: movzbl 0x2(%r13), %ebx
    0x107dc8264 <+340>: shll   $0x10, %ebx
    0x107dc8267 <+343>: orl    %eax, %ebx
    0x107dc8269 <+345>: movl   %ebx, %eax
    0x107dc826b <+347>: shrl   $0x2, %eax
    0x107dc826e <+350>: andl   $0x3f, %eax
...
2022-01-10T12:52:09.2734350Z (lldb) bt all
2022-01-10T12:52:09.2738110Z tiledb_unit was compiled with optimization - stepping may behave oddly; variables may not be available.
2022-01-10T12:52:14.0292050Z * thread #1, stop reason = signal SIGSTOP
2022-01-10T12:52:14.0293960Z   * frame #0: 0x0000000107dc825f tiledb_unit`azure::storage_lite::to_base64(input=<unavailable>, size=2) at base64.cpp:80:42 [opt]
2022-01-10T12:52:14.0295040Z     frame #1: 0x0000000107dc80fb tiledb_unit`azure::storage_lite::to_base64(input=size=32) at base64.cpp:40:16 [opt]
2022-01-10T12:52:14.0295980Z     frame #2: 0x0000000107dc889d tiledb_unit`azure::storage_lite::hash(to_sign=<unavailable>, key=size=64) at hash.cpp:65:16 [opt]
2022-01-10T12:52:14.0297170Z     frame #3: 0x0000000107ddc48f tiledb_unit`azure::storage_lite::shared_key_credential::sign_request(this=<unavailable>, (null)=<unavailable>, h=0x00007ff88c30bdd0, url=0x00007ffee8c4be48, headers=<unavailable>) const at storage_credential.cpp:65:65 [opt]
2022-01-10T12:52:14.0298740Z     frame #4: 0x0000000107de18f7 tiledb_unit`azure::storage_lite::delete_blob_request_base::build_request(this=0x00007ff88c31ab28, a=<unavailable>, h=0x00007ff88c30bdd0) const at delete_blob_request_base.cpp:47:25 [opt]

Hi @dhoke4tdb , I can confirm there's a bug in to_base64 implementation. However, cpplite sdk has been deprecated, so I'm afraid we won't fix it. Please use our Track2 SDK instead.

Find attached a zip archive containing files involved in addressing this issue,
base64.cpp.patch - a patch gen'd against v0.3.0 of sdk (and applicable to several others that seem to have same exact base64.cpp)
verify.base64.cpp.both - a complete file containing both the broken and the fixed implementation that was used
attempting to validate that the fix actually did avoid the problem, having the _mod() version succeed followed by the _orig() version failing.
base64-patch-related.zip

Thanks @dhoke4tdb , I believe your patch can fix the bug!

One more file, a CI log from our verification attempt with backtrace indicating the _mod routine had succeeded before the _orig routine failed (in the same fashion we have been sporadically encountering.)
print-stack-raw.log


Break With Upcoming Version of Three

With Three r71dev this is broken, it has to do with the fog implementation. Removing the fog from the water shader solves the problem but unfortunately leaves us fogless. I took a stab at debugging the issue and failed. I have only dabbled with shader programming.
Here is the error from console:
 THREE.WebGLShader: Shader couldn't compile.
Three71dev.full.js:24669 THREE.WebGLShader: gl.getShaderInfoLog() ERROR: 0:119: 'square' : no matching overloaded function found
ERROR: 0:119: 'square' : no matching overloaded function found
ERROR: 0:119: 'LOG2' : undeclared identifier
ERROR: 0:120: 'whiteCompliment' : no matching overloaded function found

Removing THREE.ShaderChunk[ "fog_fragment" ], from the water shader allows it to compile.
Also the line number from the error will be different from stock three r71dev, mine is slightly different, though nothing related. I have just modified the skeletal AnimationHandler a little.

I fixed it (i think?) cause it implies only a minor modification, but it is mayby a regression. I hope it will not change and re-break :)

Awesome!
I will try it out later tonight.

Cool !
If you are interested, I work on an other way to render an ocean also on github: https://jbouny.github.io/fft-ocean/ (currently some issues depending the used browser, chrome seems fine)

WOW! Super awesome =]


Results of competition.

Hello Sir/Madam,
Let us know Results of competition
Thank you,
Regards,
Shiddu

Hello @shiddugmail we will be announcing it today :)
It took the judges some time to reach a verdict etc.
We are also in the process of sending out comms etc with the winners so stay tuned 📻 🎤 🎉


[HW] Jorge Ortiz

Name: Jorge Ortiz
Linkedin Profile: https://www.linkedin.com/in/jeortizquan/
Attach the homework screenshots below:

Congrats!

https://api.badgr.io/public/assertions/fzFXUolvRKSyqjDJuRhyqw?identity__url=https%3A%2F%2Fwww.linkedin.com%2Fin%2Fjeortizquan%2F


Minor Wording in 'Use Hex Code to Color Elements Red'

Challenge http://www.freecodecamp.com/challenges/waypoint-use-hex-code-to-color-elements-red has an issue.
In the sentence: "16 colors and 6 positions means we have 16 to the 6th power, or more than 16 million possible colors," it would be more accurate to say "16 values" instead of "16 colors."

@amyevans You're right. It should be "16 values".
And I guess in the first para,

You may be wondering why we use 6 digits to represent a color instead of just one or two. The answer is that using 6 digits gives us a huge variety.

It should be "6 characters" or "6 positions" instead of "6 digits".
cc: @QuincyLarson @benmcmahon100


Added config to enable opengl wireframe for debugging

Overview: What does this pull request change?

Motivation and Explanation: Why and how do your changes improve the library?

It is useful when debugging opengl to see the vertices and edges of objects, this adds a config option to enable wireframe mode in opengl
class Test(Scene):
    def construct(self):
        a = Dot(radius=2)
        self.add(a)
        self.interactive_embed()

Normal mode

wireframe mode

Links to added or changed documentation pages

Further Information and Comments

Reviewer Checklist

[ ] The PR title is descriptive enough for the changelog, and the PR is labeled correctly
[ ] If applicable: newly added non-private functions and classes have a docstring including a short summary and a PARAMETERS section
[ ] If applicable: newly added functions and classes are tested

maybe add a check that throws an error if you are not in opengl mode?

maybe add a check that throws an error if you are not in opengl mode?

I could add a check, thinking logging a warning to say it is an unsupported flag for cairo might be better than throwing an error though? Since the flag technically won't affect cairo's behaviour?

Both could work. Your right that a warning is probably better.


Feature Request - Default Device Type to Switch

I'd like to be able to update my config once to change the default device type from a light to a switch. At least for simple on/off devices. This would let me specify within HomeKit what kind of device it is. As it is I keep needing to go into the config and mark a new device as a switch...
Thoughts? Any direction on implementation?

That would add a more configuration complexity (as you would then need a "treatAsLight" option) without adding any additional functionality.  I don't think it is worth the complexity it causes.


Faker-based transformers by macro

A small experiment with the mass generation of transformers based on fake-rs fakers using macros.
Here is only a part of the transformers, the rest are easy to add in the same way.
✓ Checklist:

[ ] This PR has been added to CHANGELOG.md (at the top of the list);
[ ] Tests for the changes have been added (for bug fixes / features);
[ ] Docs have been added / updated (for bug fixes / features).

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@63c2879). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #23   +/-   ##
=======================================
  Coverage        ?   47.61%
=======================================
  Files           ?       40
  Lines           ?     1491
  Branches        ?        0
=======================================
  Hits            ?      710
  Misses          ?      781
  Partials        ?        0

Continue to review full report at Codecov.

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

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@63c2879). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #23   +/-   ##
=======================================
  Coverage        ?   47.61%
=======================================
  Files           ?       40
  Lines           ?     1491
  Branches        ?        0
=======================================
  Hits            ?      710
  Misses          ?      781
  Partials        ?        0

Continue to review full report at Codecov.

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


H6154 not responding to on/off commands

I just switched over from your older Govee LAN control integration (Thanks for all your hard work in this BTW !!!) as I was having issues with the H705A constantly disconnecting / reconnecting.
Using this integration the H705A is now working great but my H6154 is not responding to on / off requests.
Below is a copy of the log.  Appears as though the H6154 isn't returning a LAN API IP address.....
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
GOVEE_API_KEY=REDACTED
GOVEE_MQTT_HOST=core-mosquitto
GOVEE_EMAIL=REDACTED
GOVEE_PASSWORD=REDACTED
GOVEE_MQTT_PASSWORD=REDACTED
GOVEE_MQTT_USER=addons
GOVEE_MQTT_PORT=1883
++ cd /app
++ exec /app/govee serve
[2024-01-10T08:40:01 INFO  govee::commands::serve] Starting service. version 2024.01.09-c0925c04
[2024-01-10T08:40:01 INFO  govee::commands::serve] Querying platform API for device list
[2024-01-10T08:40:01 INFO  govee::commands::serve] Querying undocumented API for device + room list
[2024-01-10T08:40:01 INFO  govee::service::iot] Connected to IoT: CONNACK code 0: Connection Accepted.
[2024-01-10T08:40:01 INFO  govee::commands::serve] Starting LAN discovery
[2024-01-10T08:40:01 INFO  govee::service::iot] IoT (re)connected with status CONNACK code 0: Connection Accepted.
[2024-01-10T08:40:01 INFO  govee::commands::serve] Waiting 10 seconds for LAN API discovery
[2024-01-10T08:40:12 INFO  govee::commands::serve] Devices returned from Govee's APIs
[2024-01-10T08:40:12 INFO  govee::commands::serve] media room light strip (EE:E5:A4:C1:38:94:AB:8C) sku=H6154
[2024-01-10T08:40:12 INFO  govee::commands::serve]   Platform API: devices.types.light. supports_rgb=true supports_brightness=true
[2024-01-10T08:40:12 INFO  govee::commands::serve]                 color_temp=Some((2000, 9000)) segment_rgb=None
[2024-01-10T08:40:12 INFO  govee::commands::serve]   Undoc: room=None supports_iot=true ble_only=false
[2024-01-10T08:40:12 INFO  govee::commands::serve]
[2024-01-10T08:40:12 INFO  govee::commands::serve] Permanent Outdoor Lights (C2:DF:CD:38:32:30:06:66) sku=H705A
[2024-01-10T08:40:12 INFO  govee::commands::serve]   LAN API: ip=<IP_ADDRESS>
[2024-01-10T08:40:12 INFO  govee::commands::serve]   Platform API: devices.types.light. supports_rgb=true supports_brightness=true
[2024-01-10T08:40:12 INFO  govee::commands::serve]                 color_temp=Some((2000, 9000)) segment_rgb=Some(0..15)
[2024-01-10T08:40:12 INFO  govee::commands::serve]   Undoc: room=None supports_iot=true ble_only=false
[2024-01-10T08:40:12 INFO  govee::commands::serve]   Quirk: Quirk { sku: "H705A", icon: "mdi:outdoor-lamp", supports_rgb: true, supports_brightness: true, color_temp_range: Some((2000, 9000)), avoid_platform_api: false, ble_only: false, lan_api_capable: true, device_type: Light }
[2024-01-10T08:40:12 INFO  govee::commands::serve]
[2024-01-10T08:40:12 INFO  govee::service::http] http server addr is <IP_ADDRESS>:8056
[2024-01-10T08:40:18 INFO  govee::service::hass] Wait 1.1s for hass to settle on entity configs
[2024-01-10T08:40:19 INFO  govee::service::hass] MQTT connected with status=CONNACK code 0: Connection Accepted.
[2024-01-10T08:40:32 INFO  govee::service::state] requesting update via IoT MQTT media room light strip (EE:E5:A4:C1:38:94:AB:8C) None
[2024-01-10T08:40:37 INFO  govee::service::hass] Command for media room light strip (EE:E5:A4:C1:38:94:AB:8C): {"state":"ON"}
[2024-01-10T08:40:37 INFO  govee::service::state] Using IoT API to set media room light strip (EE:E5:A4:C1:38:94:AB:8C) power state
[2024-01-10T08:40:41 INFO  govee::service::hass] Command for media room light strip (EE:E5:A4:C1:38:94:AB:8C): {"state":"ON"}
[2024-01-10T08:40:41 INFO  govee::service::state] Using IoT API to set media room light strip (EE:E5:A4:C1:38:94:AB:8C) power state
[2024-01-10T08:40:47 INFO  govee::service::hass] powerSwitch for EEE5A4C13894AB8C: ON
[2024-01-10T08:40:47 INFO  govee::service::state] Using IoT API to set media room light strip (EE:E5:A4:C1:38:94:AB:8C) power state
[2024-01-10T08:40:52 INFO  govee::service::hass] powerSwitch for EEE5A4C13894AB8C: ON
[2024-01-10T08:40:52 INFO  govee::service::state] Using IoT API to set media room light strip (EE:E5:A4:C1:38:94:AB:8C) power state

Does the H6154 have LAN API support enabled in the Govee app?  That particular SKU isn't on the official list of LAN-API-supported devices from Govee, but that list isn't aggressively maintained by Govee.
If it does have LAN API support but doesn't show up in the probes, and isn't responding to the control request, then it may indicate a networking or device problem with that particular device; try power cycling it?
If it doesn't support LAN API then it is possible that is also doesn't respond to the same family of IoT commands that we're currently trying to use on it.
Can you try running this command to try turning on the device? You can also use off to try turning it off:
$ docker run --rm ghcr.io/wez/govee2mqtt /app/govee --api-key $GOVEE_API_KEY http-control --id EE:E5:A4:C1:38:94:AB:8C on

I'm running the integration through HASS.  The command is not recognized through the HASS SSH terminal :(
I checked the LAN API option in the Govee app and you are right... there is no option to enable the LAN API.
However, the H6154 worked w/o issue with your Govee LAN control integration.
I might have to go back to using your older integration for the H6154 and the newer for the H705A.
I will try to see if there is any way to execute the command you noted in HASS and will update once able to do so.
Thanks for your prompt reply and for trying to help :)

I have a similar issue with a different LED strip, but I believe the underlying issue is the same. It's H6121.
The status of the strip is always reflected correctly in HA, but control fails. When I tried your command above, the control works. It seems like IoT API is failing to control, while API key succeeds.

Please try the latest version and let me know how you get on with it!

H6154 now turns on and off via the integration. Sometimes it's not responsive and the color changing options don't work yet but it's a great step forward !
Thanks for continuing to look in to this...

Please share the logs from this updated version, especially around the commands that don't work

Here you go :
[2024-01-13T10:42:22 INFO  govee::commands::serve]
[2024-01-13T10:42:22 INFO  govee::service::http] http server addr is <IP_ADDRESS>:8056
[2024-01-13T10:42:27 INFO  govee::service::hass] Wait 1.3s for hass to settle on 26 entity configs
[2024-01-13T10:42:29 INFO  govee::service::hass] MQTT connected with status=CONNACK code 0: Connection Accepted.
[2024-01-13T10:42:42 INFO  govee::service::state] requesting update via Platform API media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) None
[2024-01-13T10:42:59 INFO  govee::service::hass] Command for media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154): {"state":"ON"}
[2024-01-13T10:42:59 INFO  govee::service::state] Using Platform API to set media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) power state
[2024-01-13T10:43:01 INFO  govee::service::state] Polling media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) to get latest state after control
[2024-01-13T10:43:01 INFO  govee::service::state] requesting update via Platform API media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) Some(DeviceState { on: false, online: Some(true), kelvin: 0, color: DeviceColor { r: 127, g: 172, b: 255 }, brightness: 197, scene: None, source: "PLATFORM API", updated: 2024-01-13T15:42:42.515743967Z })
[2024-01-13T10:43:13 INFO  govee::service::hass] Command for media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154): {"state":"ON","brightness":26}
[2024-01-13T10:43:13 INFO  govee::service::state] Using Platform API to set media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) brightness
[2024-01-13T10:43:13 INFO  govee::service::state] Polling media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) to get latest state after control
[2024-01-13T10:43:13 INFO  govee::service::state] requesting update via Platform API media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) Some(DeviceState { on: true, online: None, kelvin: 0, color: DeviceColor { r: 127, g: 172, b: 255 }, brightness: 197, scene: None, source: "AWS IoT API", updated: 2024-01-13T15:43:03.846981580Z })
[2024-01-13T10:43:18 INFO  govee::service::hass] Command for media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154): {"state":"ON","brightness":100}
[2024-01-13T10:43:18 INFO  govee::service::state] Using Platform API to set media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) brightness
[2024-01-13T10:43:18 INFO  govee::service::state] Polling media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) to get latest state after control
[2024-01-13T10:43:18 INFO  govee::service::state] requesting update via Platform API media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) Some(DeviceState { on: true, online: None, kelvin: 0, color: DeviceColor { r: 127, g: 172, b: 255 }, brightness: 69, scene: None, source: "AWS IoT API", updated: 2024-01-13T15:43:14.843679217Z })
[2024-01-13T10:43:20 INFO  govee::service::hass] Command for media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154): {"state":"ON","color_temp":500}
[2024-01-13T10:43:20 INFO  govee::service::state] Using Platform API to set media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) color temperature
[2024-01-13T10:43:21 INFO  govee::service::hass] Command for media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154): {"state":"ON","color_temp":500}
[2024-01-13T10:43:21 INFO  govee::service::state] Using Platform API to set media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) color temperature
[2024-01-13T10:43:21 INFO  govee::service::state] Polling media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) to get latest state after control
[2024-01-13T10:43:21 INFO  govee::service::state] requesting update via Platform API media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) Some(DeviceState { on: true, online: None, kelvin: 0, color: DeviceColor { r: 127, g: 172, b: 255 }, brightness: 254, scene: None, source: "AWS IoT API", updated: 2024-01-13T15:43:20.431487193Z })
[2024-01-13T10:43:22 INFO  govee::service::hass] Command for media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154): {"state":"ON","color_temp":230}
[2024-01-13T10:43:22 INFO  govee::service::state] Using Platform API to set media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) color temperature
[2024-01-13T10:43:22 INFO  govee::service::state] Polling media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) to get latest state after control
[2024-01-13T10:43:22 INFO  govee::service::state] requesting update via Platform API media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) Some(DeviceState { on: true, online: Some(true), kelvin: 0, color: DeviceColor { r: 127, g: 172, b: 255 }, brightness: 254, scene: None, source: "PLATFORM API", updated: 2024-01-13T15:43:22.120493552Z })
[2024-01-13T10:43:23 INFO  govee::service::hass] Command for media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154): {"state":"ON","color_temp":149}
[2024-01-13T10:43:23 INFO  govee::service::state] Using Platform API to set media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) color temperature
[2024-01-13T10:43:23 INFO  govee::service::state] Polling media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) to get latest state after control
[2024-01-13T10:43:23 INFO  govee::service::state] requesting update via Platform API media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) Some(DeviceState { on: true, online: Some(true), kelvin: 0, color: DeviceColor { r: 127, g: 172, b: 255 }, brightness: 254, scene: None, source: "PLATFORM API", updated: 2024-01-13T15:43:23.005203391Z })
[2024-01-13T10:43:23 INFO  govee::service::hass] Command for media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154): {"state":"ON","color_temp":111}
[2024-01-13T10:43:23 INFO  govee::service::state] Using Platform API to set media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) color temperature
[2024-01-13T10:43:24 INFO  govee::service::state] Polling media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) to get latest state after control
[2024-01-13T10:43:24 INFO  govee::service::state] requesting update via Platform API media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) Some(DeviceState { on: true, online: Some(true), kelvin: 0, color: DeviceColor { r: 127, g: 172, b: 255 }, brightness: 254, scene: None, source: "PLATFORM API", updated: 2024-01-13T15:43:23.680806721Z })
[2024-01-13T10:43:24 INFO  govee::service::hass] Command for media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154): {"state":"ON","color_temp":149}
[2024-01-13T10:43:24 INFO  govee::service::state] Using Platform API to set media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) color temperature
[2024-01-13T10:43:24 INFO  govee::service::hass] Command for media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154): {"state":"ON","color_temp":230}
[2024-01-13T10:43:24 INFO  govee::service::state] Using Platform API to set media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) color temperature
[2024-01-13T10:43:24 INFO  govee::service::state] Polling media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) to get latest state after control
[2024-01-13T10:43:24 INFO  govee::service::state] requesting update via Platform API media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) Some(DeviceState { on: true, online: Some(true), kelvin: 0, color: DeviceColor { r: 127, g: 172, b: 255 }, brightness: 254, scene: None, source: "PLATFORM API", updated: 2024-01-13T15:43:24.243685643Z })
[2024-01-13T10:43:26 INFO  govee::service::hass] Command for media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154): {"state":"ON","color":{"r":127,"g":172,"b":255}}
[2024-01-13T10:43:26 INFO  govee::service::state] Using Platform API to set media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) color
[2024-01-13T10:43:26 INFO  govee::service::state] Polling media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) to get latest state after control
[2024-01-13T10:43:26 INFO  govee::service::state] requesting update via Platform API media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) Some(DeviceState { on: true, online: Some(true), kelvin: 0, color: DeviceColor { r: 127, g: 172, b: 255 }, brightness: 254, scene: None, source: "PLATFORM API", updated: 2024-01-13T15:43:25.065819213Z })
[2024-01-13T10:43:28 INFO  govee::service::hass] Command for media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154): {"state":"ON","effect":"Care"}
[2024-01-13T10:43:28 INFO  govee::service::state] Using Platform API to set media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) to scene Care
[2024-01-13T10:43:31 INFO  govee::service::hass] Command for media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154): {"state":"ON","effect":"Active"}
[2024-01-13T10:43:31 INFO  govee::service::state] Using Platform API to set media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) to scene Active
[2024-01-13T10:43:33 INFO  govee::service::hass] Command for media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154): {"state":"ON","color_temp":149}
[2024-01-13T10:43:33 INFO  govee::service::state] Using Platform API to set media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) color temperature
[2024-01-13T10:43:33 INFO  govee::service::state] Polling media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) to get latest state after control
[2024-01-13T10:43:33 INFO  govee::service::state] requesting update via Platform API media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) Some(DeviceState { on: true, online: Some(true), kelvin: 0, color: DeviceColor { r: 127, g: 172, b: 255 }, brightness: 254, scene: None, source: "PLATFORM API", updated: 2024-01-13T15:43:26.960785880Z })
[2024-01-13T10:43:34 INFO  govee::service::hass] Command for media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154): {"state":"ON","color_temp":111}
[2024-01-13T10:43:34 INFO  govee::service::state] Using Platform API to set media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) color temperature
[2024-01-13T10:43:34 INFO  govee::service::state] Polling media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) to get latest state after control
[2024-01-13T10:43:34 INFO  govee::service::state] requesting update via Platform API media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) Some(DeviceState { on: true, online: Some(true), kelvin: 0, color: DeviceColor { r: 127, g: 172, b: 255 }, brightness: 254, scene: None, source: "PLATFORM API", updated: 2024-01-13T15:43:33.893453540Z })
[2024-01-13T10:43:35 INFO  govee::service::hass] Command for media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154): {"state":"ON","color_temp":500}
[2024-01-13T10:43:35 INFO  govee::service::state] Using Platform API to set media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) color temperature
[2024-01-13T10:43:35 INFO  govee::service::hass] Command for media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154): {"state":"ON","color_temp":230}
[2024-01-13T10:43:35 INFO  govee::service::state] Using Platform API to set media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) color temperature
[2024-01-13T10:43:35 INFO  govee::service::state] Polling media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) to get latest state after control
[2024-01-13T10:43:35 INFO  govee::service::state] requesting update via Platform API media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) Some(DeviceState { on: true, online: Some(true), kelvin: 0, color: DeviceColor { r: 127, g: 172, b: 255 }, brightness: 254, scene: None, source: "PLATFORM API", updated: 2024-01-13T15:43:35.142160152Z })
[2024-01-13T10:43:35 INFO  govee::service::hass] Command for media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154): {"state":"ON","color":{"r":255,"g":110,"b":84}}
[2024-01-13T10:43:35 INFO  govee::service::state] Using Platform API to set media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) color
[2024-01-13T10:43:35 INFO  govee::service::state] Polling media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) to get latest state after control
[2024-01-13T10:43:35 INFO  govee::service::state] requesting update via Platform API media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) Some(DeviceState { on: true, online: Some(true), kelvin: 0, color: DeviceColor { r: 127, g: 172, b: 255 }, brightness: 254, scene: None, source: "PLATFORM API", updated: 2024-01-13T15:43:35.142160152Z })
[2024-01-13T10:43:35 INFO  govee::service::hass] Command for media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154): {"state":"ON","color":{"r":127,"g":172,"b":255}}
[2024-01-13T10:43:35 INFO  govee::service::state] Using Platform API to set media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) color
[2024-01-13T10:43:35 INFO  govee::service::hass] Command for media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154): {"state":"ON","color":{"r":215,"g":150,"b":255}}
[2024-01-13T10:43:35 INFO  govee::service::state] Using Platform API to set media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) color
[2024-01-13T10:43:35 INFO  govee::service::state] Polling media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) to get latest state after control
[2024-01-13T10:43:35 INFO  govee::service::state] requesting update via Platform API media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) Some(DeviceState { on: true, online: Some(true), kelvin: 0, color: DeviceColor { r: 127, g: 172, b: 255 }, brightness: 254, scene: None, source: "PLATFORM API", updated: 2024-01-13T15:43:35.696353577Z })
[2024-01-13T10:43:40 INFO  govee::service::hass] Command for media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154): {"state":"OFF"}
[2024-01-13T10:43:40 INFO  govee::service::state] Using Platform API to set media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) power state
[2024-01-13T10:43:41 INFO  govee::service::state] Polling media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) to get latest state after control
[2024-01-13T10:43:41 INFO  govee::service::state] requesting update via Platform API media room light strip (EE:E5:A4:C1:38:94:AB:8C H6154) Some(DeviceState { on: true, online: None, kelvin: 0, color: DeviceColor { r: 127, g: 172, b: 255 }, brightness: 254, scene: None, source: "AWS IoT API", updated: 2024-01-13T15:43:41.522909832Z })

Those logs indicate no errors when asking Govee's platform API to carry out the actions you requested.
It seems as though the issue is on Govee's side and I suggest you reach out to their support folks to see if they are aware of issues controlling this device through their new platform API

Thanks for your prompt reply !
I'll try to reach out to Govee for assistance.
In closing, I'll just mention that these functions continue to work with your older Govee LAN control integration.

That's using the older REST API, while this one is using their newer Platform API. I may have to add the option of using the old API here in govee2mqtt as well.

H6121 working now, thanks!

Happy to raise a separate issue if appropriate, but this all looks similar to the issues I'm seeing with my H6159 . This used to work fine in the older integration but when I made the switch over to this one I'm not unable to control this device.
It reflects the state correctly but just doesn't respond to control requests.
I believe it needs to be over the IOT API as it doesn't seem to give me the option to enable LAN support for this device, but as I say it used to work with the old integration.
Thanks.


Octal literals and octal escape sequences are deprecated in build/npm/preinstall.js

The build/npm/preinstall.js is using octal escape sequences which is deprecated.
Use hexadecimal escape sequences instead.
\033 should be replaced with \x1b

Please tag good first issue


issue #52

Integer on 64Bit Architecture is BIGINT in POSTGRES.
Testing integers for containment in int8ranges for instance requires a cast to BIGINT. I do not want my keys restricted to 32bit.
My change to BIGINT may be the trigger for the problem but imho the cause would rather be a parser quirk that confuses a limit clause with a type cast in the context of not being aware of the BIGINT type. But, of course, the easiest cure is to retract that map of INTEGER to BIGINT and add an own clause for BIGINT

passes CI of my client package BitemporalPostgres

What about :binary => :BLOB,? Imho it should be :binary => :BYTEA,? Wrong PostgreSQL types in SearchLightPostgreSQL.TYPE_MAPPINGS #11
@UniqueTokens Maybe You create a PRQ for that? I feel resonsible for this, as it relates to a former PRQ of mine and I researched Date/Time data types for Julia and Postgres. I do not have the time to research BLOB types for now.
PS: This type mapping part of the package is a wee fragile imo. For instance Integer is abstract in Julia and 32bit in POSTGRES.
So to be safe we should use: Int16 => smallint, Int32 => integer, Int64 => bigint But I do not know how that might impact SearchLight.jl

PS: This type mapping part of the package is a wee fragile imo.

I agree with that. @essenciary It might make sense to discuss the timeline and all the pros and cons of the current SearchLight implementation in a team of contributors before a new PRQ for BYTEA? For my part, I'm currently thinking about whether and how the hardcoded SearchLightPostgreSQL.TYPE_MAPPINGS could be replaced by a dynamic assignment using the type conversions in the already used LibPQ.jl.

I agree - however, one of the goals is to provide as much compatibility between the various DB adapters so migrations can be ported between backends. So we should keep common mappings (shared with MySQL, SQLite, etc common types) and additional/specialised mappings for Postgres.

@michaelfliegner @UniqueTokens lmk if you agree that this is good to merge and I'll proceed.

Ok with me

LGTM

Thanks guys!


Timeseries with multi-column data

Hello. Thank you so much for the open-source implementation.
I have a custom dataset with cryptocurrency values for daily prediction which except from the target values,
includes also 3 columns of related features.
Those columns could be included in your implementation? Are features taken into account from the model or is just the target value?

(Not a dev). Lag llama doesn't support features mostly due to the nature of foundation models. They're trained on a large body of data sets and supposed to be able to do inference on any data. Both the training and use case data may or may not have varying number of features, including none, so features are not included on purpose.

Hi @eftymakr. Lag-Llama unfortunately does not support covariates (which are features apart from the target value, as you have). Currently, you can only use the historical values of the target variable to predict for future values of the target variable.
Thanks @smrnvdhy for  pointing out the difficulty of building a foundation model that can support arbitrary number of covariate features. It could in fact be possible to use features in a foundation model if it's trained to perform inference with and without features, and trained to work well with additional features specific to your own data. Building such a model is an open research question in my opinion.

Closing this issue. Feel free to open it if required :)


Some files needed do NOT exist

I have finished all the pre-processs for data, but when training, issues shown in the screen-shot occured.

It looks like you did not run pseudo label generation for CHAOS dataset.


fix(plugin/optimizer): 🐛 Enhance support for custom entry points in Vite config

Overview
This PR aims to enhance the support for custom entry points in the Vite configuration in library mode, enabling developers to specify custom entry points and facilitating the creation of libraries with custom submodules. By extending the capability of Vite configuration, this enhancement provides flexibility and empowers developers to tailor their projects more effectively.
What is it?

[X] Feature / enhancement
[X] Bug Fix
[ ] Docs / tests / types / typos

Description
This PR modifies the code to allow for custom entry points in the Vite configuration (library mode). It includes updates to handle custom entry points provided in the Vite config file. This enhancement aims to address the need for developers to create libraries with custom submodules by providing a more flexible configuration option.
Use cases and why
The primary use cases for this enhancement include:

Custom Entry Points: Developers can now specify custom entry points in the Vite config file, allowing for more granular control over project structure and module loading.
Library Creation: This enhancement facilitates the creation of libraries with custom submodules, enabling developers to structure their libraries in a way that best suits their needs.

Checklist:

[x] My code follows the developer guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] Added new tests to cover the fix / functionality

Issues Related:
This PR solve my own issue: #6177

On first glance everything looks good. It takes a custom path which is resolved, and allows for object inputs. If anyone else could review before merging.


Featured pictures: Show in recency or random order, rather than alphabetical order

Currently, featured pictures are shown in alphabetical order.
As a consequence, users will always see the same pictures.
In particular, nobody will ever see all of the featured pictures that do not start with a quote or digit character.
This is boring for users, they will not scroll featured pictures twice. Even in one year the pictures show will be the same, with 1 or 2 exceptions maybe among hundreds of pictures scrolled.
Solution: Rather than displaying in alphabetical order, show in either (only implement one):

Order of recent upload
Order of recent nomination
Or random

The order must be passed in the API request. Ordering results after receiving a result page is not a good solution.

I start working on this

@neoliteconsultant Thanks! :-)

Hey @nicolas-raoul
How do I get the featured images to show for the commons beta app? At the moment I am unable to test

The featured images category on the commons beta site has no images, that’s why the list is showing as empty. Am not sure how to get an image featured for testing. :(

Is there a need to test featured images on beta, though? Beta build variant is mostly only needed if you need to upload a lot of nonsensical pictures for testing, which doesn't appear to be necessary for this.

I does not seem to work, unfortunately.
The featured images are still listed in alphabetical order.

@nicolas-raoul did you check the upload times of the featured images?

@neoliteconsultant Yes, here are the upload times of the first images that appear, in order:

1 June 2016 https://commons.wikimedia.org/wiki/File:"Broke,_baby_sick,and_car_trouble!%22-_Dorothea_Lange%27s_photo_of_a_Missouri_family_of_five_in_the_vicinity_of_Tracy,_California.jpg
30 June 2016 https://commons.wikimedia.org/wiki/File:"Chuveirão"_na_Caverna_Timimina.jpg
27 January 2005 https://commons.wikimedia.org/wiki/File:"The_School_of_Athens"_by_Raffaello_Sanzio_da_Urbino.jpg
6 February 2015 https://commons.wikimedia.org/wiki/File:'One_of_the_wards_in_the_hospital_at_Scutari'.Wellcome_M0007724-_restoration,_cropped.jpg
1 December 2015 https://commons.wikimedia.org/wiki/File:0_A.D._Alpha_12_Loucetios.webm

As you can see, the upload dates do not impact how the images are ordered.

@nicolas-raoul ok I will resolve it ASAP

@neoliteconsultant Thanks a lot :-)

This works great now, thanks :-)


[Crash] Release 0.14.9

XCODE Version 8.3 (8E162)
IOS 10.3
Updated from 0.13.5 to 0.14.9:

I am releasing a fix for this now.  What platform are you running on?

This is fixed in release 0.14.10.
I still want to know what platform are you were running on and the kind of app distribution are you using.  I am curious because I didn't see this in my tests.

I tested with my iPhone 7 iOS 10.3
Running the app into debug mode and also with branch debug key.
Do you need more info?

Are you developing a special type of application?  Like an iMessage extension or iWatch app?

@E-B-Smith No, it's a default obj-c iOS application.

@E-B-Smith It's a default iOS application that also have an iMessage extension.
But the Branch SDK is only used in the main app.


Minor Fixes

Modified Location, Fixed Facebook Link, Added Github Link, Modified Join our community tagline, & removed phone no.

LGTM


Clarify palindrome product exercise requirements

REF #305
It's not clear from the current examples what the requirements of this exercise are.  In fact, a furtive glance is more likely to cause confusion than give clarity.
In my opinion, this is because for the first example the solution lies within the range of the list of factors, giving on a first impression that we are looking for products that lie within this range.
I think that by listing out the entire list of products (which is small in the case of the range of 1..9) we make it more clear that we are considering all the results.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (non-breaking change which adds functionality)
[ ] Breaking change (fix or enhancement that would cause existing functionality to change)
[x] Gardening (code and/or documentation cleanup)

References and Closures

Checklist:

[ ] I have read the CONTRIBUTING document.
[ ] My change relies on a pending issue/pull request
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

I like this. 👍
Would you be willing to make a PR against the common problem definition:
https://github.com/exercism/problem-specifications/blob/master/exercises/palindrome-products/description.md
From which this README is generated.
Thanks.

They've also fixed the It's there so we need to regenerate the readme anyway.
(we don't yet have an automated process for this.)

Closing in favor of exercism/problem-specifications#897

Great, thanks. :heart:

There are some more clues about regenerating READMEs here: https://github.com/exercism/ruby/pull/722


Pick full node

As a follow up for https://github.com/cosmos/voyager/issues/1291 we might allow the user to pick a node they trust.
Scope:

component: ability to enter an IP of a trusted node
logic: ability to connect to a full node based on an IP set in the view

a better ux might be to let the user pick from a list of full nodes including monikers and IPs.
but i'm not sure we need to do any of this before launch.

agreed

this will probably often be used by people how know the IP of their trusted node

even if you know the IP of the node, having a list would be nice / could help with verification etc...

Maybe make it a config setting.

Maybe make it a config setting.

what do you mean?

Make it configurable in the config.toml.

isn't it already with COSMOS_NODE? i thought the point of this was to let users (not developers) pick a node...?

Make it configurable in the config.toml.

This was an outcome of a discussion in the team meeting. We want to be able to define the set of trusted full nodes when shipping Voyager. A regular user will not use COSMOS_NODE as you pointed out. As we discussed that validators may ship a branded Voyager, validators may want to put in their preferred full node in the configuration easily.


Reflect.set in a Proxy object without set causes TypeError

In Node, it sets the property on Proxy object, while in GraalJS it throws:
TypeError: undefined is not a function
    at Reflect.set (native)

Code to reproduce:
var obj = {};
var handler = {
        get: (a,b)=>a[b]
}
var proxy = new Proxy(obj, handler);
Reflect.set(proxy, "key", "value");

Thank you for the report. I confirm that this is a bug in our implementation of Reflect.set.

This issue is fixed by https://github.com/graalvm/graaljs/commit/83d61752b79bf4978722d4e911069bf181e67ff1.


day 3 code does not run 'string index out of range'

When I run it it gives the following errors:
---------------------------------------------------------------------------
IndexError                                Traceback (most recent call last)
<timed exec> in <module>

[<ipython-input-203-bb6385a68880>](https://localhost:8080/#) in solve(input_data)
     13
     14     # get the locations of symbols, e.g. * ?, but not .
---> 15     symbol_locations = engine.get_symbol_locations()
     16     for point in symbol_locations:
     17         all_range_locations_for_symbol = set()

3 frames
[<ipython-input-199-e169fb26e460>](https://localhost:8080/#) in value_at_point(self, point)
    115     def value_at_point(self, point: Point):
    116         """ The value at this point """
--> 117         return self._array[point.y][point.x]
    118
    119     def set_value_at_point(self, point: Point, value):

IndexError: string index out of range

Thanks for flagging.  Unfortunately, I can't reproduce this with either the test input or my actual input.  I.e. it runs fine for me:
14:15:37.185:aoc2023 - INF: Part 1 soln: part_num_sum=559667
14:15:37.186:aoc2023 - INF: Part 2 soln: gear_ratios_sum=86841457
CPU times: total: 62.5 ms
Wall time: 70.3 ms

If you'd like me to try and debug, you could share your input with me?  Maybe with a GitHub gist that you can later delete?

Sure. Thanks. Really curious what caused this?
https://gist.github.com/TheBigBear/a7127fa52f8c2f40fcc2863aa997e4e9

I am simply opening it in google's open colab and it works fine for all other days, just not day 3 .
Thanks for taking the time to checking into it.
I have solved part 2 of day 3 (86879020), just can't solve it using your notebook for some strange reason.

Hey, no worries at all!  I'm just glad that people are using this and finding it useful.
And it's also good to know that the resolution "turn it off and on again" is still as valid now as it ever was!


Identify how to fix Frame_Overcurrent_Occurred

Good morning Aaron,
Thank you very much for the information.
Despite our existing assumption, this comes as a surprise since the unit in question was not sold with a protective case.
Please note that protective case cannot simply be installed on any scanners, as due to the additional weight on the scanner head, certain performance parameters must be adjusted for the frame motor if the scanner is mounted in a protective housing with a rotating hood.
This has never been done with this device, as we did not know that it is installed in a housing.
I uploaded the wizard to adjust the parameters on the scanner - after that the FRAME_OVERCURRENT error should disappear.
After that, please test the scanner and let us know if you run into this issue again.
As we begin to work on this support case kindly note the requests made at the end of this e-mail, thank you in advance for your cooperation.
Thank you and best regards,
Vitaly Pimkin
LiDAR Support

To run the .exe on the linux environment.... PlayOnLinux was used in cooperation with WINE.
Script provided by Riegl to "calibrate" the VZ400 to accomodate the housing, which it had not been set up for, initially.


2.0 Examples - Bad jQuery Link (404 / Not Found)

The new 2.0 examples have a bad link to jQuery:

GET http://twitter.github.com/bootstrap/assets/js/tests/vendor/jquery.js 404 (Not Found)

I get that on:

http://twitter.github.com/bootstrap/examples/hero.html
http://twitter.github.com/bootstrap/examples/fluid.html
http://twitter.github.com/bootstrap/examples/starter-template.html

(E.g., all three.)
Best,
--
T.J. Crowder
Independent Software Engineer
tj / crowder software / com
www / crowder software / com

See #1498 for a partial fix pull request.

Resolved in another thread. Thanks!


Fleet Manager: Error log access support

Let's separate the delete function in a separate PR and maintain this one for error log access support.

@AlexandreSato Can you please test and verify the changes?

LGTM. Thanks for the PR! 😊


Render SizePerPage component in searchPanel

Is it possible to render SizePerPage component in the searchPanel?

@hknCanaan sorry, it's impossible now, but I'll implement it on react-bootstrap-table2, this repo already stop implement new feature. thanks


Staging slow paths should work

Problem
staging env with op-roots V1 should work, both in slow-mode and op-mode
Impact
This is a must have before we can qualify V1 and deploy it to mainnet
Proposed Solution
Manually test and ensure each supported chain, works in both op-mode and slow-mode.
Deploy fixes to staging as necessary to resolve any errors.
Acceptance Criteria
These sub tasks need to be completed

[ ] https://github.com/connext/monorepo/issues/4969
[ ]  https://github.com/connext/monorepo/issues/4968
[ ]  https://github.com/connext/monorepo/issues/4970
[ ]  https://github.com/connext/monorepo/issues/4971
[ ]  https://github.com/connext/monorepo/issues/4972
[ ]  https://github.com/connext/monorepo/issues/4973
[ ]  https://github.com/connext/monorepo/issues/4974

This should be an epic @preethamr
cc: @alexwhte

Closing, the real goal is to launch optimistic roots so combining them


Fix typos

Found via codespell -S .mypy_cache -L aline

Thank you! I'll look into adding codespell to the pre-commit config :)

I suspect that aline is a typo too, so won't be excluding that one in the config.

:partying_face: :partying_face: :partying_face: :partying_face: :partying_face:


add wallet id support to new wallet commands

wallet send
wallet balance
wallet encrypt
wallet decrypt
wallet lock
wallet unlock
wallet status

This was completed


Support for adding instances of BinnedSpectrum

I really needed adding of the spectra, in the simplest case, to accumulate exposure.
I need two methods, average rate, and weighted average.
There were also some small changes here and there that were required.
I am not not too sure about the returning None errors in Poisson spectra, instead of assert. I just tried to minimize multiple "if self.is_poisson: x=None" statements.

Thanks!
However, what is the use case for this?
What do you need to achieve that cannot be achieved by simply loading one plugin instance per spectrum, and using them in a JointLikelihood object? Something like this:
sp1 = SpectrumLike(...)
sp2 = SpectrumLike(...)
data = DataList(sp1, sp2)

model = ...

jl = JointLikelihood(model, data)

I know that summing spectra has been a widely-used procedure in the X-ray community for years, but I don't like it: it is very error-prone because the handling of the background and especially of the response is tricky (the proper way of summing the response properly varies case by case).
If you only need to put together different spectra to gain statistic, using them in a joint likelihood achieves that already while maintaining each spectrum with its own background and response.

Indeed, I tried to use joint likelihood when possible.
I understand that this is the good way.
Summing kills information.
However, for us it's common to have up to ~100.000 spectra for a single source. I tried with a 100 and it's not quite as interactive, though still ok.
For response I put so far an assert that it is identical.
The spectra are already background(and other \source)-subtracted.
The summing could be limited to simple cases like this.
Potentially we could do the total joint likelihood fit of course, together with background, this would make 100.000 spectra and  200 x 100.000 sources (different parameters in each observation). Would it work with 20M sources?
Even if it will, it will take time, each attempt.
For exploration and a first look it is practical to see the merged spectrum.
Finally and related, it's nice for plotting purposes (though this could be achieved differently I guess)

It's an interesting question of course. I do not know a  better way right now than to stack spectra at least partially. A way which would be also be quite practical, for the reasons I listed.
Though really I made a pull request because J Michael mentioned it was in plans anyway.

ok, this is indeed a good use case for something like this. Yes, while astromodels is very lightweight, I never had in mind a use case with 20 million sources! So it would probably become unbearably slow.
I think having the assertion that the response is identical is the way to go, so we will not have in the future people shooting themselves in the foot by summing spectra which are not supposed to be summed.
So let's go ahead with this. I see that the tests are failing, but probably you are still working on it?

I left the tests that verify that accessing BinnedSpectrum.count_errors (and similar) for poisson spectra should raise an exception. This is related to the somewhat higher impact change I made (mentioned in the pull request).
replacing
assert self.is_poisson == False, "Cannot request errors on rates for a Poisson spectrum"
return self._errors * self.exposure

with
if self.is_poisson:
    return None
else:
    return self._errors * self.exposure

The exception would come up often when cloning or adding, leading to many repetitions of something like this:
if not self.is_poisson:
    function(...,self.count_errors)
else:
    function_alternative(...)

at many more technical stages there is no need to discriminate between poisson and gauss cases, so code repetition can be avoided by assuming that errors will be None in the poisson case.
If you prefer, I can add all those if's, not a big issue.


GH2861: Restore pre 1.0 error logging

Adds back support for aggregate exception and that diagnostic verbosity will print a full stack trace.

fixes #2861

@devlead your changes have been merged, thanks for your contribution 👍


just set bytes

@ArrantSquid if we just set bytes, then we can unmarshal to a model.

Seems legit to me. An opinionated lib. :)


Effect Rendering in Python3

Have I written custom code (as opposed to using a stock example script provided in MediaPipe)
No
OS Platform and Distribution
Linux Ubuntu 18.04
MediaPipe Tasks SDK version
No response
Task name (e.g. Image classification, Gesture recognition etc.)
Effect Rendering
Programming Language and version (e.g. C++, Python, Java)
Python
Describe the actual behavior

Describe the expected behaviour
I have looked at the face landmarker task guide which gives face blendshapes, but how do I use them for effect rendering in Python3? Is there any way to use effect_renderer_calculator.cc in Python3? I have looked at #1155 and other issues which perform rendering in Java, I'm guessing.
Is https://learnopencv.com/create-snapchat-instagram-filters-using-mediapipe the only way to do it in Python3?
I'm a bit new to this, so I'm sorry if this query sounds too basic.

We currently do not offer a high level API for effect rendering or graph customization. You can however run and create your own graphs via the underlying framework. This requires quite a bit of setup though: https://developers.google.com/mediapipe/framework
There are examples in our code base for how to run custom graphs: https://github.com/google/mediapipe/blob/master/mediapipe/python/solutions/face_mesh.py
It is probably easier to build your own rendering code. For that, you can also look at https://github.com/google/mediapipe/blob/master/mediapipe/tasks/web/vision/core/drawing_utils.ts
We hope that we can provide an easier way to customized graphs in the future.

@schmidt-sebastian, is it easier to do this in C++ (using the faceeffect graph) than in Python?


number of inputs and outputs when creating a block

Hi guys!
Сan I specify the number of inputs or outputs when I put the block on the Scene?
If this is possible, then there is an example?
Thank you.

I'm not sure what you mean...
You mean not at compile time?
If so, when registering models register different instances of the same model class, that has state to store how many inputs or outputs.

@russelltg
Not at compile time.
I need that when I put the block on the scene a window appears for inputting the number of inputs.
Now I solved the problem by passing the global variable to the class. When you register the model, the window does not appear. After registration, the value of the global variable is changed and when I put the block the window appears.

I also need this feature. Please add it. We are making an audio app and the user can put an audio block and configure later how many inputs/outputs it has.

I have done this for my own app. Eg: A node configures itself with the input and output ports of an incoming node. It has required some changes in the core code, namely that the number of ports and entries is assumed to be fixed when the node is first instanced... It would be nice if this came standard.

I think this was overlapping with the "dynamic ports" which is in master.


winpr: fix cache assertion before it's been created

Cache assertion fails because the call below (gdi_init_ex) creates the cache. I just changed the order and put the assertion after gdi_init_ex has been called.

@freerdp-bot test


New migration is necessary

Hi,
I just noticed a new migration file is necessary for the project.
Migrations for 'defender':
  usr/local/lib/python3.7/site-packages/defender/migrations/0002_alter_accessattempt_id.py
    - Alter field id on accessattempt

Hey @panosangelopoulos — this bug was fixed with PR https://github.com/jazzband/django-defender/pull/197


Update manager config to use postgresql-16-c9s image

Replaced the postgresql image with one that is publicly available in order to avoid requiring a pull secret in deployment automation being contributed to the ORAN-SC community.

/lgtm

/approve


Use Airlift's HTTP client in StorageClient for proxy support

The StorageClient class currently uses javax.net.ssl.HttpsURLConnection. If it were using Airlift's HTTP client, it would be possible to configure a proxy for it.

@nineinchnick @ebyhr : apologies for the basic question
how do we configure the connector properties to use the HTTP proxy setting? I do not want to have a global HTTP_PROXY variable
Thanks!

@metalshanked There's http-client.http-proxy config property. See
https://github.com/airlift/airlift/blob/master/http-client/src/main/java/io/airlift/http/client/HttpClientConfig.java for more details.

@metalshanked There's http-client.http-proxy config property. See https://github.com/airlift/airlift/blob/master/http-client/src/main/java/io/airlift/http/client/HttpClientConfig.java for more details.

Thanks!  Is there a way to set a "no-proxy" as well to bypass certain uri's from proxying ?

No.

No.

Sure no worries. Thanks again


TFKUBE-342: Make bamboo license optional when bamboo is not in products list

The changes LGTM. We need to fix unit tests before merging.
--- FAIL: TestBambooVariablesPopulatedWithValidValues (16.44s)


AttributeError: WEIGHTS_TS

Bug 💥
When I run Inference with deepdoctection-0.30 from exactly code in README, I got error message as below:
Traceback (most recent call last):
File "run.py", line 5, in
analyzer = dd.get_dd_analyzer()  # instantiate the built-in analyzer similar to the Hugging Face space demo
File "deepdoctection/analyzer/dd.py", line 458, in get_dd_analyzer
return build_analyzer(cfg)
File "deepdoctection/analyzer/dd.py", line 273, in build_analyzer
d_layout = build_detector(cfg, "LAYOUT")
File "deepdoctection/analyzer/dd.py", line 135, in build_detector
else (getattr(cfg.PT, mode).WEIGHTS if detectron2_available() else getattr(cfg.PT, mode).WEIGHTS_TS)
File "deepdoctection/utils/metacfg.py", line 46, in getattr
raise AttributeError(name)
AttributeError: WEIGHTS_TS

It looks that the .yaml file that is used to configure the analyzer does not align with the deepdoctection version.
Maybe forcing to reset the config file helps:
analyzer = dd.get_dd_analyzer(reset_config_file=True)


About training time and compute specifications

Hi, thanks for sharing the repo!
I was wondering what were the run time like for Mujoco tasks (HC and AntDir)? It looks like the paper uses number_of_layers=4 and number_of_attention_heads=16 with input size=512, which makes the transformer model huge.

Hello @SapanaChaudhary,
The input size is not 512. If you take a look at the hyperparameters from the README, the input size is 5 for most of the experiments. 512 is the dimension of the feedforward network that composes the transformer layer.
I don't remember exactly the runtime, but for HC is something like several hours (but less than a day). It is indeed more costly than RNN variants (since the transformer is more costly to run), but doable in a single-GPU setting.


crate = {} is accepted as a dependency constraint

[package]
authors = []
name = "test"
version = "0.1.0"

[dependencies]
crossbeam = {}

cargo build runs fine, downloading the latest crossbeam. (It seems to act somewhat like "*".)
cc @alexcrichton

Is this actually a misfeature? {} says "I don't care about this" just as well as "*" does.

I disagree with "just as well". "*" is at least an explicit version constraint, even if it is very loose, hence implies that it will be downloaded from crates.io (etc.), while {} isn't being explicit about anything.

Yeah this is a misfeature, Cargo should give an error about this.
This will probably have to be a warning for at least one cycle, however, to mitigate any breakage.

I've got a patch ready that emits a warning under these conditions, but I have two questions before I send a PR:

Is there a convention for the phrasing of a warning like this that indicates possible future breakage? At the moment I have "warning: Dependency (name-of-dep) specified without providing a local path, Git repository, or version to use.", but that doesn't really let the user know that this may break in a version or two.

Is there some marker or annotation I should leave in the code (or other such process) to indicate that this should be cleaned up and made into an error in the future? Or do we simply leave this bug open and hope that in a release or two someone gets around to looking at it and cleaning it up?

Actually, those seem like good questions to discuss in a PR :)
Sent #2270

Fixed in #2270

Woohoo!


Gradle Maven lib dependencies (AndroidAsync, etc.)

Currently not in feature/gradle-experimental:
https://github.com/readium/SDKLauncher-Android/blob/feature/gradle-experimental/SDKLauncher-Android/app/build.gradle#L9
...but in feature/lcp:
https://github.com/readium/SDKLauncher-Android/blob/feature/lcp/SDKLauncher-Android/app/build.gradle#L9
dependencies {
    compile 'com.android.support:support-v4:23.+'
    compile 'com.koushikdutta.ion:ion:2.+'
    compile 'commons-io:commons-io:2.4'
}

TODO:
https://github.com/koush/AndroidAsync
dependencies {
    compile 'com.koushikdutta.async:androidasync:2.+'
}

...to replace https://github.com/readium/SDKLauncher-Android/blob/develop/SDKLauncher-Android/libs/androidasync-2.0.1.jar

AndroidAsync is a dependency of ion. It's why I have omitted to mention it in the build.gradle

Great! Let's leave this issue open as the Gradle-Maven dependencies are not in the develop branch yet.

Also, let's make it clear in the Gradle script:
dependencies {
    compile 'com.android.support:support-v4:23.+'
    compile 'com.koushikdutta.ion:ion:2.+'
    // compile 'com.koushikdutta.async:androidasync:2.+' ALREADY INCLUDED AS DEP OF com.koushikdutta.ion
    compile 'commons-io:commons-io:2.4'
}

Fixed via https://github.com/readium/SDKLauncher-Android/commit/852704fa66a338b7365062024e3a064a551ba3bd


[Bug Report] Screen flicker with dialog and carousel

Element UI version
2.4.4
OS/Browsers version
Win10
Vue version
2.5.17-beta.0
Reproduction Link
https://jsfiddle.net/xya4k68r/15/
Steps to reproduce
I put a carousel in the dialog.
The carousel is controlled only by the buttons prepared in the dialog.
If the carousel is showing pages other than the first page, closing the dialog will return the first page of the carousel.
When you open the dialog again, the carousel can see the process of returning the page for a moment.
Once the carousel returns the page, you will see it every time you open a dialog regardless of the Carousel page.
What is Expected?
When opening a dialog, animation that returns carousel can not be inserted
What is actually happening?
When opening the dialog, the animation returning the carousel appears

I have the same problem!!!


Add slides for March 2023 (Crossplane & GitOps)

Thanks @KatharinaSick for the slides!

Of course :)


Gaussian mechanical keyboard

Gaussian 87 keyboard, Spaces and the Backspace doesn't work.A specialized disorder

i am sorry! i will go to check Macos SIP


[r112] Update reg. annotation statistics

Update Regulation annotation statistics for 112.
Sandbox URL: http://wp-np2-25.ebi.ac.uk:6020/info/genome/funcgen/data/statistics.html

@ilsley please could you review this before we branch for the new release? thanks


Complaints open the wrong correction round

Describe the bug
If I use the overview for complaints in an exam with two correction rounds (see picture), it opens the first correction round instead of the second one. (URL contains /submissions/XYZ/assessment?correction-round=0)

To Reproduce

Conduct exam with two correction rounds.
Create complaints.
Go to the complaint (using the steps in decsription)

Expected behavior
It shall open the second correction round.
Screenshots
No response
What browsers are you seeing the problem on?
Firefox
Additional context
No response
Relevant log output
No response

Since our gradings will start soon, I'll mark it as high prio now :) Feel free to change that

Was this fixed? Can't seem to reproduce it anymore

I'll check it again next week

@manuelmanso we encountered the issue again :)

(In Artemis 5.10.2)

@manuelmanso not sure why, but it again was a problem during exam reviews :( .. what information could we provide in addition?

Closing now. If the issue occurs again; I'll reopen it.


Upgrade for Terraform 0.12

Hi,
SecretHub TF provider needs to be upgraded for TF 0.12
Thanks in advance.

@SimonBarendse any idea when this task could be tackled ?

We're on it. You can expect to see a release this week.

Thanks for the update and great news !

Just released v0.2.0 which adds Terraform v0.12 support


Support for "cycles"?

Hi,
when scheduling or starting a cleaning job using the MiHome app you can set the number of cleaning cycles.
Is there a way to set this via Homekit?
Thank you,
Sascha

Hi @SaschaRH, do you mean zone cleaning?
If so, in the array defining the zone, you can add a fifth element to the array to specify the number of times to sweep that square.
AFAIK, general cleaning and room cleaning don't support that option. Do they?

Hi @afharo,
room cleaning supports this too, while general cleaning does not. In the Xiaomi Home app you just select the rooms and the number of cycles. I noticed, that this not just adds another cleaning cycle, it also changes the way it cleans on the second cycle, that's why I'd like to use it.


fix(gitex): Use pointer when decoding

Summary
use pointer when decoding
Does this close any open issues?
closes #3077
Screenshots

### Other Information
Any other information that is important to this PR.

Seems like @keon94 fix the issue in #2984