Cluster setup still failing with 4 core nodes

@marcusbooyah: I'm still seeing cluster setup failures with nodes configured with 4 cores (the default).
I thought we needed 2 cores or even less now.  This needs to work.  You should probably reduce the number of nodes in your test clusters to 4 so you'll see this behavior.
Needing more than 4 cores is a problem for my DL360 because it has only 8 cores and XenServer appears to be kind of reserving 4 cores for itself, so I can't create a 8 core VM.

This was related to Istio needing too much CPU and is now fixed.


Arend sharedstatemodel

As far as I can see, I didn't ask for a pull request yet... It would be a waste if source is completely gone even when graduated

We are continuing the development in other branches before merging the distributed approach in the master branch.
https://github.com/TESTARtool/TESTAR_dev/tree/fernando_arend_shared_model


fix(Slideover): bind shadow class to panel

🔗 Linked issue

❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

📝 Checklist

[ ] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

Thanks for the fix! Never noticed it was missing 😅


feat(safari): use iframe for extension injection

Goal
The injected script should create an iframe to isolate the Save to Pocket UI and avoid collisions with JS and CSS.
Acceptance Criteria

[ ] Injected script should create an iframe
[ ] Prevent nested iFrames from being created
[ ] Messages dispatched from the Safari App Extension should reach the iframe
[ ] All Save To Pocket UI should live in the iFrame
[ ] The iFrame should resize according to the needs of the UI
[ ] Styles should be injected into the iFrame

Notes
This is the framer aspect of the chrome extension.  We will need to revisit and make sure any discrepancies with Safari are rectified

Closing this as it is not possible with Safari's API at this time.  Looks like support may be added in the future, in which case we can revisit.


Add French translation

Resolves #182, I took the liberty to make @Risengan the author of the 2nd commit in this PR since he created the translation.

Any update on this pull request @rsms? I'd love to provide a translation into german!


do not filter endpoints by procspied/ebpf in renderers

The filtering of endpoints causes some connections to get missed for non-eBPF-tracked connections. Furthermore, the filtering of endpoints is entirely pointless when the probes run eBPF since the filters just pass through eBPF-tracked endpoints (for good reason too; because otherwise some connections would be missed). So in that case it is just costing CPU and removing it actually improves performance.
Note that removing the filtering does not result in over-counting connections since that is done by source ip:port pairs.
Fixes #2551.
Fixes #2558.

Performance comparison using a recent eBPF-based Weave Cloud prod report, timing the http api calls to retrieve topologies:

topology
master
branch

processes
0.59
0.45

containers
1.6
1.3

pods
1.5
1.2

kube-controllers
1.5
1.3

services
1.5
1.3

hosts
2.0
1.6

(all times in seconds)

More accurate, cleaner code and it even improves performance: fantastic

and it even improves performance

For the eBPF case. It hurts performance for the non-eBPF case.


Bring TNA toolkit into the Wagtail repository

This decision follows a discussion between JC, MB, AB and GJ earliertoday during which we agreed that doing so will make it easier to both maintain Etna and identify candidate changes to the TNA Tookit that emerge from our work on Etna.

Hi @AshTNA @JamesWChan @matt-blair - this is the PR we discussed earlier. I've brought the Toolkit styles (and Bootstrap dependencies) into this repository and put a big comment into the etna.scss file.

Hi Gwyn,
I did some investigation and looks like the _card.scss we originally had doesn't actually exist in the toolkit, but was created from the design that Chris created, and therefore was in the toolkit-duplicates folder.
This is the card design that Chris made: https://github.com/nationalarchives/tna-frontend-design-toolkit/blob/main/components/cards/example.png
Therefore I think we need to integrate  our original _card.scss file with the toolkit one

Hi @AshTNA - thanks for identifying this issue. Would you be able to look into identifying a fix?


Auto Proficiency causing errors when adding Bard musical instruments

Specifically, I am using DDB-Importer by Mr. Primate and dnd5e-helpers, as well as DAE and SRD-DAE compendia. The issue comes about when importing a bard character with proficiency in musical instruments such as drums.
I get a pop-up telling me to manually check to proficiency but I also get some console errors. It's not clear to me what it means to check the proficiency manually?
Here is one of the errors from the console:
foundry.js:2499 ReferenceError: pass_type is not defined
    at AutoProfArmor_createOwnedItem (dnd5e-helpers.js:716)
    at dnd5e-helpers.js:1142
    at Function._call (foundry.js:2496)
    at Function.callAll (foundry.js:2456)
    at Function._handleCreateEmbeddedEntity (foundry.js:29908)
    at Actor5e.createEmbeddedEntity (foundry.js:29879)
    at async Actor5e.createEmbeddedEntity (foundry.js:31075)
    at async migrateActorDAESRD (main.js:15987)
    at async CharacterImport.parseCharacterData (main.js:18005)
    at async HTMLButtonElement.<anonymous> (main.js:17651)
_call @ foundry.js:2499
callAll @ foundry.js:2456
_handleCreateEmbeddedEntity @ foundry.js:29908
createEmbeddedEntity @ foundry.js:29879

This one is specifically happening during the creation of 1 of 3 instruments. It happens for all three.
foundry.js:2499 ReferenceError: pass_type is not defined
    at AutoProfArmor_createOwnedItem (dnd5e-helpers.js:716)
    at dnd5e-helpers.js:1142
    at Function._call (foundry.js:2496)
    at Function.callAll (foundry.js:2456)
    at Function._handleCreateEmbeddedEntity (foundry.js:29908)
    at Actor5e.createEmbeddedEntity (foundry.js:29879)
    at async Actor5e.createEmbeddedEntity (foundry.js:31075)
    at async CharacterImport.importCharacterItems (main.js:17783)
    at async CharacterImport.processCharacterItems (main.js:17944)
    at async CharacterImport.parseCharacterData (main.js:17983)
_call @ foundry.js:2499
callAll @ foundry.js:2456
_handleCreateEmbeddedEntity @ foundry.js:29908
createEmbeddedEntity @ foundry.js:29879
async function (async)
createEmbeddedEntity @ foundry.js:29869
createEmbeddedEntity @ foundry.js:31075
createEmbeddedEntity @ entity.js:541
(anonymous) @ main.js:17380
importItems @ main.js:17379
importCharacterItems @ main.js:17783
async function (async)
importCharacterItems @ main.js:17781
processCharacterItems @ main.js:17944
async function (async)
processCharacterItems @ main.js:17869
parseCharacterData @ main.js:17983
async function (async)
parseCharacterData @ main.js:17963
(anonymous) @ main.js:17651
async function (async)
(anonymous) @ main.js:17643
dispatch @ jquery.min.js:2
v.handle @ jquery.min.js:2

ReferenceError: pass_type is not defined
    at AutoProfArmor_createOwnedItem (dnd5e-helpers.js:716)
    at dnd5e-helpers.js:1142
    at Function._call (foundry.js:2496)
    at Function.callAll (foundry.js:2456)
    at Function._handleCreateEmbeddedEntity (foundry.js:29908)
    at Actor5e.createEmbeddedEntity (foundry.js:29879)
    at async Actor5e.createEmbeddedEntity (foundry.js:31075)
    at async migrateActorDAESRD (main.js:15987)
    at async CharacterImport.parseCharacterData (main.js:18005)
    at async HTMLButtonElement.<anonymous> (main.js:17651)
_call @ foundry.js:2499
callAll @ foundry.js:2456
_handleCreateEmbeddedEntity @ foundry.js:29908
createEmbeddedEntity @ foundry.js:29879
async function (async)
createEmbeddedEntity @ foundry.js:29869
createEmbeddedEntity @ foundry.js:31075
createEmbeddedEntity @ entity.js:541
createOwnedItem @ foundry.js:31211
migrateActorDAESRD @ main.js:15987
async function (async)
migrateActorDAESRD @ main.js:15985
parseCharacterData @ main.js:18005
async function (async)
parseCharacterData @ main.js:17963
(anonymous) @ main.js:17651
async function (async)
(anonymous) @ main.js:17643
dispatch @ jquery.min.js:2
v.handle @ jquery.min.js:2

There is a lingering error related to that symbol pass_type. Opening back up this ticket so that we can trace it. Thanks for the report and stack trace :)

There is a lingering error related to that symbol pass_type. Opening back up this ticket so that we can trace it. Thanks for the report and stack trace :)

Fixed in 1.8.8

Fixed in 1.8.8


fzf-lua does not work if set ambiwidth="double"

Info

Operating System: Ubuntu 22.04(WSL2)

Shell: fish

Terminal: wezterm 20230713-081419-f73f7180

nvim --version:

NVIM v0.10.0-dev-1f551e0
NVIM v0.9.2

fzf --version: 0.42.0 (d471067)

[ ] The issue is reproducible with mini.sh

fzf-lua configuration
require('fzf-lua').setup({})

Description
mini.sh can't work to my env.
using neovim's minimal reproduction template.
issue.lua
for name, url in pairs{
  -- ADD PLUGINS _NECESSARY_ TO REPRODUCE THE ISSUE, e.g:
  -- some_plugin = 'https://github.com/author/plugin.nvim'
  fzf_lua = 'https://github.com/ibhagwan/fzf-lua'
} do
  local install_path = vim.fn.fnamemodify('nvim_issue/'..name, ':p')
  if vim.fn.isdirectory(install_path) == 0 then
    vim.fn.system { 'git', 'clone', '--depth=1', url, install_path }
  end
  vim.opt.runtimepath:append(install_path)
end

-- ADD INIT.LUA SETTINGS THAT IS _NECESSARY_ FOR REPRODUCING THE ISSUE
require("fzf-lua").setup({})

vim.opt.ambiwidth = "double"

run
nvim --clean -u issue.lua

error message
E5108: Error executing lua ...hoge/nvim_issue/fzf_lua/lua/fzf-lua/providers/module.lua:38: /tmp/hoge/nvim_issue/fzf_lua/
lua/fzf-lua/utils.lua:751: border chars must be one cell
stack traceback:
        [C]: in function 'fzf_exec'
        ...hoge/nvim_issue/fzf_lua/lua/fzf-lua/providers/module.lua:38: in function <...hoge/nvim_issue/fzf_lua/lua/fzf-
lua/providers/module.lua:9>
        /tmp/hoge/nvim_issue/fzf_lua/lua/fzf-lua/cmd.lua:78: in function 'run_command'
        /tmp/hoge/nvim_issue/fzf_lua/lua/fzf-lua/cmd.lua:87: in function 'load_command'
        [string ":lua"]:1: in main chunk

Ty for this report @mimikun, TIL about ambiwidth.
The latest commit should make it work but the preview doesn't look normal since the border is manually drawn and the double width characters make it look spaced, working on a fix by using the native border instead. will update this post when done.

@mimikun, use the latest commit https://github.com/ibhagwan/fzf-lua/commit/ba449c6112a6bf694e740c1de79c054ad6d11be4, it should also fix the spaced preview border characters and title when ambiwidth="double".
Note that the default preview scrollbar is drawn by the border which is now not possible, I highly recommend switching to the float scrollbar which will still work with the new commit:
require("fzf-lua").setup({
  winopts = {
    preview = { scrollbar = "float" }
  }
})

Which should look like this:

note the floating scrollbar at the right side of the preview window

@ibhagwan
Thank you fix.
Is there a way to customize the part of the scrollbar indicated by the red circle?
It's thin and hard to see.

@ibhagwan
Thank you fix.
Is there a way to customize the part of the scrollbar indicated by the red circle?

Yes, this is the scroll bar controlled by fzf the binary, it has a few different customization options, see fzf’s man  page and use fzf_opts to pass the options to fzf, you’re most likely interested in:
--scrollbar=CHAR1[CHAR2]
  Use the given character to render scrollbar.
  (default: '│' or ':' depending on --no-unicode).
  The optional CHAR2 is used to render scrollbar of the preview window.

Thank you!


[SPARK-7330] [SQL] avoid NPE at jdbc rdd

Thank @nadavoosh point this out in #5590

Merged build triggered.

Merged build started.

Test build #31717 has started for   PR 5877 at commit 6f8f84b.

Test build #31717 has finished for   PR 5877 at commit 6f8f84b.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31717/
Test FAILed.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #31718 has started for   PR 5877 at commit 6daf277.

Test build #31718 has finished for   PR 5877 at commit 6daf277.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31718/
Test FAILed.

retest this please.

Merged build triggered.

Merged build started.

Test build #31720 has started for   PR 5877 at commit 6daf277.

Test build #31720 has finished for   PR 5877 at commit 6daf277.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31720/
Test PASSed.

Merged build triggered.

Merged build started.

Test build #31737 has started for   PR 5877 at commit 57fd03e.

Test build #31737 has finished for   PR 5877 at commit 57fd03e.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31737/
Test FAILed.

Merged build triggered.

Merged build started.

Test build #31741 has started for   PR 5877 at commit cd38347.

Test build #31741 has finished for   PR 5877 at commit cd38347.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31741/
Test FAILed.

retest this please.

Merged build triggered.

Merged build started.

Test build #31742 has started for   PR 5877 at commit cd38347.

Test build #31742 has finished for   PR 5877 at commit cd38347.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31742/
Test FAILed.

retest this please.

Merged build triggered.

Merged build started.

Test build #31745 has started for   PR 5877 at commit cd38347.

Test build #31745 has finished for   PR 5877 at commit cd38347.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31745/
Test PASSed.

Merged build triggered.

Merged build started.

Test build #31941 has started for   PR 5877 at commit 59b0e8c.

Test build #31941 has finished for   PR 5877 at commit 59b0e8c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31941/
Test PASSed.

Merged build finished. Test PASSed.

Merged build triggered.

Merged build started.

Test build #31953 has started for   PR 5877 at commit fe9b2c9.

Test build #31953 has finished for   PR 5877 at commit fe9b2c9.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31953/
Test PASSed.

Build triggered.

Build started.

Test build #32079 has started for   PR 5877 at commit a77f28e.

Can you resolve the conflict?

@yhuai sure, I will rebase that

Merged build triggered.

Merged build started.

Test build #32085 has started for   PR 5877 at commit cc11900.

Test build #32079 has finished for   PR 5877 at commit a77f28e.

This patch passes all tests.
This patch does not merge cleanly.
This patch adds no public classes.

Build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32079/
Test PASSed.

Test build #32085 has finished for   PR 5877 at commit cc11900.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32085/
Test FAILed.

Merged build finished. Test FAILed.

retest this please.

Merged build triggered.

Merged build started.

Test build #32111 has started for   PR 5877 at commit cc11900.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32111/
Test FAILed.

Merged build finished. Test FAILed.

i'll retrigger this build once jenkins is back up...

jenkins, test this please

Merged build triggered.

Merged build started.

Test build #32116 has started for   PR 5877 at commit cc11900.

Test build #32116 has finished for   PR 5877 at commit cc11900.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32116/
Test PASSed.

LGTM. I am merging it to master and branch-1.4.

Also branch-1.3.


Turn on automatically when the file opened is XML

This would be a great option, so I don't have to go to the plugins menu when I open a xml file.
Also, if for an active tab, the extension is not xml, it would be nice to turn off automatically.

Hi @SerGIlles ,
Sorry for the time taken to reply to the issue.
It is possible, but the feature needs design. To avoid impact the current behaviour, it is acceptable to have a configuration panel where you can enable/disable the features?
Cheers, João Rosa

Hi @SerGIlles ,
Any feedback on the previous question?

Hi @joaoasrosa,
Sorry for late response, also.
This works fine, thanks.
I identified two issues that make working with this extension a problem. I will add them separately.
Cheers

So, this feature has not been added to the plugin, right? It would be really useful!


pull request for e2e test at 12/25/2016 20:45:07

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


golang client sdk please :)

https://github.com/livekit/client-sdk-rust is a client and uses webgpu.
https://github.com/rajveermalviya/go-webgpu  works great for me as a golang webgpu across platforms.
Would be cool to make a  https://github.com/livekit/client-sdk-go repo with it.

Under the hood the golang client uses rust btw . The same rust package  your rust client uses.

Ah you rust client is designed with livekit-ffi.
So then this issue is a request for a golang client that leverages your livekit-ffi
As well as a rendering layer that utilises https://github.com/rajveermalviya/go-webgpu to that gui can built with it .
There is gioui and Fyne gui toolkits with significant users that could benefit from this.
https://github.com/rajveermalviya/go-webgpu does 2D and 3D and so thanks to its OpenGL and webgpu adapters could really prove a decent golang gui Engine for advanced projects

That certainly seems possible, but it's quite a significant lift and not planned by the team. If you are interested in hacking on one though, please do take it away!

Ok


Typings

It seems there are not any available typings for this library, which is quite a shame as it looks quite nice.

True, it's super nice. I'm not that fluent in TypeScript but if you could show some example on how other libs handled it, I could do the same with this one.

They have an entire article on it. https://typescript.codeplex.com/wikipage?title=Writing Definition (.d.ts) Files

Hey @Arc6180 , I tried to do it and here is the result so far : https://github.com/pauldijou/redux-act/commit/f0bb3f34ecfb290d82c9035e2e5811e339b0f875
The problem is that the lib is so "open" that it's really hard to fully type it. With the current typings, you can write valid TS code which will crash at runtime. One of the main issue is
export function createAction<P, M>(payloadReducer: (...args: any[]) => P, metaReducer?: (...args: any[]) => M): ActionCreator<P, M>;

Both functions should have the exact same arguments but I couldn't find a way to impose that with TS. The returned function should also have the same argument, but again, couldn't do it.
Here is another one:
export function createAction<P, M>(): ActionCreator<P, M>;

The action created can return any type. It will act as the identity. So if you give it a string, P will be string, but with a number, P will be a number. That's really problematic because it means you cannot know the action payload type when creating the reducer. So when creating the handler to reduce the payload, you don't know the actual type of the payload.
Not sure if I should stop here or rethink the full API just for TS.

@pauldijou, first of all, thank you so much for creating this sanity-preserving library.  About this issue, I have found your existing typings to be quite useful.  Could you publish them to DefinitelyTyped?  Or, I could do it for you.  Though, since it's a task I've never performed before, you might prefer to rely on yourself.  :)

Please do, I've never done it either.

After researching the matter further, it appears that what is most desired these days (according to the Summary paragraph on this Typings page is for the package author to include their typings file with their package.  Would you be willing to do this, so I wouldn't have to create a separate entry in Typings which would need to track changes to your package's API?

Oh right, I haven't done any release since I committed the types file. Otherwise, I was thinking the same, the package.json should already be configured for it.
I probably didn't feel like it because I wasn't fully satisfied with those typings. Did you encounter any problem when using them? Any improvements needed?

Great, thanks!   They give me some very useful type-checking in my reducers with respect to the state type involved.  For example, the payload type in a reducer's handler is checked against the type of the state field to which I'm assigning the payload.
As you described earlier, the handler doesn't currently know the actual payload type in the action.  What if, instead of
type Handler<S, P, M> = (state: S, payload: P, meta?: M) => S
you had
type Handler<S, P, M> = (state: S, action: Action<P, M>) => S
The only shortcoming I've found so far with respect to using the typings is that I now have to say [actionName.getType()] in the reducers' handlers, rather than just [actionName], but it's not a big deal.

That wouldn't help, the main problem is here:
interface Handlers<S> {
  [propertyName: string]: Handler<S, any, any>
}

I cannot put ActionCreator as the type of property because TS only allow string and number. First problem. And after that, all values must have the same type, so I'm forced to use the super generic any which does not help at all... Second problem.
The best way to use types is the following:
const reducer = createReducer({}, defaultState);

// This allow a typed action creator as first argument
// and will check that the handler is also correctly typed
reducer.on(increment, state => state + 1)

Thanks for that tip about using reducer.on().  I tried it, and it does indeed allow for more (or at least, more specific) type checking within my IDE.

@jeffmath Released in 1.1.1. Please tell me if it works out of the box now.

What is it that you are referring to?  The tip you gave me already worked in the previous version.

Yes but they were not released with the package so you had to add them manually, right? Now that they are bundled with it, TS should detect them automatically.

Oh, the typings!  I get it now.  I will give the new version a try.

The new version appears to work fine.  Thanks for the update!


Example running on IBM QC

Example running generated qasm on QC. By:

Running circuit.to_qasm()
Using the generated qasm with the IBM quantum computer.

Hi @teubert, Can you please little bit elaborate ?


Backup command

%backup on | off | force | info | count | restore | period
info is default
%backup on | off
Toggles autobackup
%backup period <minutes>
Set periof of automatic backups
%backup force <reason>
Make backup of currently selected world
%backup count [count]
If no count presented prints current maximum count of backups for selected world
else max count set to this number
support infinity value
%backup restore <date time>
Restore current world with selected backup
%backup info [all]
by default
Show current auto-backup state
Max backup count and latest backup info
output:
Automatic backup: off | on
Last backup: date time
Reason: Automatic backup | Custom text
Initiator: Mention

Example (auto)
Automatic backup: on
Last backup: 12.12.2012 22:22:08
Reason: Automatic backup

Example (caused by user)
Automatic backup: on
Last backup: 21.02.2021 16:04:01
Reason: We'll burn this world to ash
Initiator: ShadowMaster

%backup info all
Prints info about all backups available:
1. Date: 21.02.2021 16:04:01
    Reason: We'll burn this world to ash
    Initiator: ShadowMaster

2. Date: 21.02.2021 16:14:01
    Reason: Automatic backup

Separate servers have separate backup

Backup&restore https://github.com/Druzai/Bot_Mc_discord/issues/21#issue-954045333

%restore as alias to %backup restore
Also %backup size [max_size in MB]
%backup size => current size limitation
%backup size 10 => only 10 MB allowed
If size not set, it's equals to amount of free space available

Config option to select path to backups
(Never allow someone to explore your filesystem)
Maybe, size/count limitations also should be set via config?
To avoid spaming backups leading to leack of free space
Also maybe there should be some limitations in frequency of force backuping, to protect server disk from mass-overwrite

@MaxBQb I think it would be useful to let members decide what type of compression to use for archiving zip-file, like: store, deflated, bzip2, lzma.
And add subcommand %backup compression [algorithm] or %backup comp [algorithm]
What do you think?

%backup period <minutes>

About this, I know good parser that can parse to datetime object. Maybe you don't have to limit this command only to minutes?

Maybe, size/count limitations also should be set via config?

In config will be name of default folder that will store all backups and size limit for each server
For this name of default folder, it will be folder in server root dir
For now I think of 2 settings for backups in config, but you can suggest another settings :)

About compression:
When you don't know what kind of file you'll compress then it is a good idea to allow PRO users to choose most comprehensive algorithm (IMHO, auto detection better), BUT: you DO know the types of files.. because you create backups of server world, witch always have same inner structure, so I think, that you should compare all this methods and just choose proper algorithm by your own.
Anyway if you can't simply choose one, then you should add description for each method, to let user know, how to choose one in termins of fast compression and smaller size.
You can use parser to get the time, also check how discord.py handles datetime/timedelta by it's own, and never forget to use parses in command type hints (it's better then stupid str everywhere) Also give me a link to this parser, I'll want to use it later :)

About compression:

I think yes, I'll just write all the pros and cons of the algorithms/methods, users will choose a maximum of one or two times.
About parser: https://github.com/scrapinghub/dateparser. The result is datetime object, though. But it's interesting to experiment with it. :)

%backup size => current size limitation
%backup size 10 => only 10 MB allowed

Maybe it's not good to let server members change this value?

Maybe

Also maybe there should be some limitations in frequency of force backuping, to protect server disk from mass-overwrite

How much seconds must be between intervals? 1 minute? 10 minutes?

Added this feature in new release


Fix build on -git

This fixes a couple of things to work on the newest git revision. The only thing that has really changed is Hyprland's new custom shared pointers (named SP in the code), which the callback creation function now returns.
I also noticed that the activeWindow event sometimes passes a nullpointer, which would unload the plugin as it would try to work with that pointer. I honestly don't know where this nullptr is coming from, and haven't done any more investigation, but a simple if statement fixes it on our end.
I've split the whole into two separate commits, because the nullptr problem is already present in v0.40.0, but the SP were introduced afterwards. I have thus added a commit pin for that first commit and v0.40.0 in the second commit, so don't squash if you want to merge this.

Much thanks works perfectly, I kinda broke my setup so I didn't get the time to check it out until now..
(Also thanks for the merge hint, should probably learn git correctly one day)


"Encode and decode hex" is missing from intro.md

Should have been added in #132.

Since I was the submitter of #132, I will fix this issue. I should have another pull request submitted by tonight.

Crated pull request #150 to resolve this issue.

Fixed in #150.


ros2 support for turtlebot3_cartographer

ISSUE TEMPLATE ver. 0.2.0

Which TurtleBot3 you have?

[ ] Burger
[x ] Waffle
[ ] Waffle Pi

Which SBC(Single Board Computer) is working on TurtleBot3?

[ ] Raspberry Pi 3
[x ] Intel Joule 570x
[ ] etc (PLEASE, WRITE DOWN YOUR SBC HERE)

Which OS you installed in SBC?

[x ] Ubuntu MATE 16.04 or later
[ ] Raspbian
[ ] etc (PLEASE, WRITE DOWN YOUR OS)

Which OS you installed in Remote PC?

[ ] Ubuntu 16.04 LTS (Xenial Xerus)
[x ] Ubuntu 18.04 LTS (Bionic Beaver)
[ ] Linux Mint 18.x
[ ] etc (PLEASE, WRITE DOWN YOUR OS)

Write down software version and firmware version

Software version: [x.x.x]
Firmware version: [x.x.x]

Write down the commands you used in order

robot@NUC1804:~/turtlebot3_ws/src/turtlebot3/turtlebot3_cartographer$ ros2 launch `ros2 pkg prefix turtlebot3_cartographer`/share/turtlebot3_cartographer/launch/turtlebot3_cartographer.py

Copy and Paste your error message on terminal

[ERROR] [launch.LaunchService]: Caught exception in launch (see debug for traceback): executable 'occupancy_grid_node' not found on the libexec directory '/home/robot/cartographer_ws/install/cartographer_ros/lib/cartographer_ros'
[INFO] [launch]: process[cartographer_node-1]: started with pid [29031]
[INFO] [launch]: sending signal 'SIGINT' to process[cartographer_node-1]

Please, describe detailedly what difficulty you are in

I have teleop working on my turtlebot3 running ROS2 now. So now I want to run cartographer. I see you recently made commits to add occupancy_grid_node to the launch file. When I try to run I get errors. It looks like occupancy_grid_node is not yet ported. Is there any way to run turtlebot3_cartographer yet? If not, what is the status and when do you expect that to work?

@mkhansen-intel
I've tested cartographer and navigation2 on TurtleBot3 and Gazeob.
If you want to test this, please following attached link
http://emanual.robotis.com/docs/en/platform/turtlebot3/ros2/#ros2

@mkhansen-intel
I try to make map to run map_saver in nav2_map_server package.
However, when I ran that node, it couldn't make map.
$ ros2 run nav2_map_server map_saver -f /map
[INFO] [map_saver]: Waiting for the map

@routiful - I found the same issue. The problem was that cartographer is publishing with different QOS settings than map_saver is subscribing with (map_saver is using default). I manually changed the cartographer_ros code to use the default QOS settings and then I can save the map.

@mkhansen-intel
I've updated the node to modifed QOS settings
https://github.com/ROBOTIS-GIT/cartographer_ros/commit/87464b75115583885477b451b379f033642bbf68
Thank you for your review!

Looks OK to me, does map_saver work for you now?

@mkhansen-intel
Yes, it worked for my PC.
qos in which map subscriber in map_generator.cpp was set default. So I modified qos of map publisher to be set default.
https://github.com/ros-planning/navigation2/blob/3f65576a98330de0cb832d2c344474b2b604142d/nav2_map_server/src/map_generator.cpp#L55

Works now, thanks!


When effect: 'coverflow',onSlideChangeEnd doesn`t work

When effect: 'coverflow',onSlideChangeEnd doesn`t work

i have the same trouble!!

+1

I got the same issue but investigated a little more.
And in my case:
onSlideChangeStart, onSlideChangeEnd is not triggered when effect is set to something else then 'slide' and you grab slide and slowly slide mouse to change to next / previews slide. When swipe is performed this usually work and functions are triggered.
My workaround was to use onTransitionStart, onTransitionEnd instead but I don't think this is the way.
This will be fixed at some point ??

+1
Like @gsgenerator I use onTransitionEnd for my propose.

+1

Read the source code， Then found when effect: 'coverflow' , watchSlidesProgress is true,
when watchSlidesProgress:true ,  implement  updateActiveIndex   （s.previousIndex = s.activeIndex;s.activeIndex = newActiveIndex;） when finger away , perform (s.previousIndex = s.activeIndex;s.activeIndex = newActiveIndex;) again in function slideto . so my workaround is
in function 'slideto'
if (!s.params.freeMode && !s.params.watchSlidesProgress) {
s.previousIndex = s.activeIndex || 0;
s.activeIndex = slideIndex;
}

My workround was to  change the 2064th line of swiper.js   to the following：
if (s.activeIndex !== slideIndex) {
s.previousIndex = s.activeIndex || 0;
s.activeIndex = slideIndex;
}

@leiyu0932   thanks for your solution. It works and it should be merged to master. 👍

It works with the v4.0.1, so this issue may be closed?


Review warnings emitted during full-stack-tests and presentation-components test runs

Some test that tests Modal from itwinUI will continue to  show warnings until this issue is resolved https://github.com/iTwin/iTwinUI/issues/2199


Value gets selected while entering the last digit for the texts with  maxlength

Hello @RobinHerbots
Issue is with the text fields containing maxlength attribute
<input type="text" maxlength="12" class="MODE_ALPHANUMERIC" id="F_07_0020" name="F_07_0020" value="" data-inputmask="'alias': 'integer', 'integerDigits': '12', 'allowMinus':true, 'groupSeparator': ',', 'autoGroup': true, 'groupSize': '3'" >

When user enters the last character (say 12th Character in this case), all value gets selected. And if user tries to enter next (13th) character, all the value gets removed and only one (13th) character  displays.
But the behaviour should be :

It should not select the value while entering the last digit.
It should not allow to enter characters more than that of maxlength.

It works fine if I remove the plugin. Plugin should not change the DOMs default behaviour.

@laxmikantG ,
Is this issue still occuring?

@RobinHerbots  :- Sorry for delay in reply.
I did not check this with latest version. But I had fixed at our end by commenting following lines:
  ...}, $(npt).data("_inputmask", data), $(npt).is(":visible")) {
               var scrollCalc = $(npt).css("font-size").replace("px", "") * end;
               npt.scrollLeft = scrollCalc > npt.scrollWidth ? scrollCalc : 0, 0 == opts.insertMode && begin      == end && end++,
               npt.setSelectionRange ? (
			// Reason: Disable text selection after entering last digit
			/* npt.selectionStart = begin, npt.selectionEnd = end */
			// Reason : For normal TAB key behaviour (execute original code for TAB key event)
			event.keyCode == $.inputmask.keyCode.TAB ? (npt.selectionStart = begin, npt.selectionEnd = end /* END */) : true)  : npt.createTextRange && (range = npt.createTextRange(),
            range.collapse(!0), range.moveEnd("character", end), range.moveStart("character", begin),
            range.select());
        }...

We disabled the selection manually ;)
Thank you


Add Redux Logo

Designed by Matthew Johnston
Closes #151

Here's a preview, in case anyone doesn't want to sift through the diff :)

There’s also a page for it now:
https://github.com/reactjs/redux/blob/master/logo/README.md


The method '/' was called on null

my code :
          FlatButton(
          onPressed: () { },
          color: Colors.blue,
          child: Text(
              'My font size is 24px on the design draft and will change with the system.',
              style: TextStyle(
                color: Colors.black,
                fontSize: ScreenUtil(allowFontScaling: true).setSp(24),
              )),
        )

and the result !!!!
I/flutter (29201): The method '/' was called on null. I/flutter (29201): Receiver: null I/flutter (29201): Tried calling: /(1080.0)

看起来问题不是出在这里啊..
看看哪里使用了屏幕宽度

Did not reply for a while, so close first


Make backend for the blog.

Create backend/ directory with files to start a new nest.js application. The backend should use SQLite database, use Typeorm, and swagger.
go:

restart:


Replace bintray

use travis to run arm build and generate artifacts
update github release with arm artifact
remove bintray badge, flow tasks and docs

travis is now paid service, might go with drone, but as a separate issue.


v1.13 Backports 2023-05-22

[x] #25323 (@tommyp1ckles)
[x] #25461 (@tommyp1ckles)

:warning: merge conflict because the code after the added prepareHostPolicyEnforcement(kubectl) got changed in main vs. v1.13. Please check whether I've resolved it correctly.

[x] #25426 (@bleggett)

:warning: merge conflict because void *map is not present in v1.13 branch. Please check whether I've resolved it correctly.

[ ] #25465 (@LynneD)

Once this PR is merged, you can update the PR labels via:
for pr in 25323 25461 25426 25465; do contrib/backporting/set-labels.py $pr done 1.13; done

or with
make add-labels BRANCH=v1.13 ISSUES=25323,25461,25426,25465

@pchaigno could you please review the backport of https://github.com/cilium/cilium/pull/25426 given you've reviewed that PR?

/test-backport-1.13

/test-1.26-net-next

/test-1.26-net-next

net-next failure is https://github.com/cilium/cilium/issues/25524 which is going to be quarantined on main by https://github.com/cilium/cilium/pull/25670. I've added the needs-backport/1.13 there. Marking as ready-to-merge given that all other tests passed and reviews are in.


[GSoC] RadioButton & RadioGroup Component

As part of my proposal, I have added a RadioButton component with tests. Next goal is to work on RadioGroup component.
Output of tests:

Can one of the admins verify this patch?

@ellelili2025 It's ready for review. Code for Component and MockComponent for Horizontal and Vertical RadioGroup and RadioButton is complete along with appropriate test cases.

I think there are some design issues to be looked at here. The radio button is a user interface component, and the group is a layout, which makes sense at first glance. However, one important feature of a radio button group is that you can easily determine which item is selected in the group, and it doesn't look like the group has a block for that. It looks like the radio buttons are treated like checkboxes, and the only way to determine what is selected in a group is by checking the individual radio buttons.
It might make sense for a radio button group to be more like a listview, where the group itself is the user interface component, and the items are defined inside it.
I also triggered a browser error while working with the blocks.

It is no necessary to add a layout to group RadioButtons, add a grouping attribute is better.


[IP Security] ShowMyCode = false shows my code anyway

Describe the bug
When debugging or going to a definition for an app I am depending to, vscode shows me all the code in the object.dal.
Even local procedures or internal procedures.
To Reproduce
Create a First App with a codeunit that exposes a global procedure, and has a local and an internal procedure.
Create a second app with an action in a page that calls the global procedure in the codeunit of the First App.
Put a breakpoint on the call of the global procedure in the action of the page of the second app
or
Go to the definition of the procedure with F12
=> You can see all the object code
AL Code to reproduce the issue
First app (set showMyCode = false in app.json)
codeunit 51100 SomeCodeunit
{
    procedure MyGlobalProcedure()
    var
    begin
        DoMyLocalProcedure();
    end;

    local procedure DoMyLocalProcedure()
    var
    begin
        Message('This Should not be visible');
    end;

    internal procedure MyInternalProcedure()
    var
    begin
        Message('This should not be visible');
    end;
}

Second App (make a dependency with the first app)
page 50100 MyPage
{
    PageType = Card;
    ApplicationArea = All;
    UsageCategory = Administration;
    actions
    {
        area(Processing)
        {
            action(ActionName)
            {
                ApplicationArea = All;

                trigger OnAction()
                var
                    SomeCodeunit: Codeunit SomeCodeunit;
                begin
                    SomeCodeunit.MyGlobalProcedure();
                end;
            }
        }
    }
}

Expected behavior
I should not be able to see all the code, maybe only global procedures ?.
Also, (I think )I should be able to see internal procedure only if I give the right to Second App in app.json of my FirstApp by specifying "internalVisibleTo". Anyway, I though that just setting showMyCode = false must hide my code.
As said in MS Documentation:

Screenshots
Debug:

Go To Definition

5. Versions:

AL Language: 4.0.199169

Business Central: W1 15.1 (Platform 15.0.37865.38662 + Application 15.1.37881.38709)

Hi,
Have you been working in one workspace the application with Page 50100 has a dependency (a project reference) to the app with SomeCodeunit.
a. If you are in the same workspace, you own both projects. References for SomeCodeunit will be resolved from the referenced project and not the symbols, thus this is expected behaviour.
b. For debugging it is similar. Code that you have published from VSCode - these are called per tenant developer extensions -  even if marked as showmycode false should be able to be debugged.

Hi,
I'm working in two differents instances of vscode, so two workspaces, but both of these apps are deployed using vscode, not powershell.
So if I understood correctly, if I deploy my "motherapp" with Powershell. My 50100 page must not see the code inside the codeunit it depends on.
Thanks for your answsers!

Yes, it should be like that.

@JulienDecottignies can we close this issue?

I am closing this issue because it appears that it has been resolved. Please open a new issue if you believe this has not been resolved and reference the current issue.


better error tracing?

Hey Guys,
I'm having difficulty figuring out how to get a meaningful stack trace when I run into an error. The error messages seems to be related mostly to the rails app with a small message regarding the issue in the js which makes it difficult to figure out whats going on. Do you have any suggestions?
Thanks!

Hi @chrisdobler JavaScript is compiling here. You can try to make error handling similar to React::ServerRendering::PrerenderError class


Add touch event props

Hi!
I added the missing touch event props:

onPress
onPressIn
onPressOut
onLongPress
disabled
delayPressIn
delayPressOut
delayLongPress

https://github.com/react-native-svg/react-native-svg#touch-events

Hi @reck753, thanks for this contribution! Could you adjust the onPress* to add the argument received (event).
It seems it's not correctly typed in the source https://github.com/react-native-svg/react-native-svg/blob/fa9a25d36b6f863d3148bdd5dd1ac76e91339402/src/ReactNativeSVG.web.ts#L18 but I am sure we could have something like Event.pressEvent => unit seems more accurate.

Hi @reck753, thanks for this contribution!

I also adjusted the types for the delay* to int instead. I totally forgot that the value should be in milliseconds and that it doesn't make sense to be float. The type is int as well for RN pressables:
https://github.com/rescript-react-native/rescript-react-native/blob/e625be295df739f91f98b6e12855b4bcd7a6623d/src/components/TouchableOpacity.res#L23

Thanks!

Available in 12.1.8


remove repetitive code

Objective

Describe the objective or issue this PR addresses.
If you're fixing a specific issue, say "Fixes #X".

Solution

Describe the solution used to achieve the objective above.

Changelog

This section is optional. If this was a trivial fix, or has no externally-visible impact, you can delete this section.

What changed as a result of this PR?
If applicable, organize changes under "Added", "Changed", or "Fixed" sub-headings
Stick to one or two sentences. If more detail is needed for a particular change, consider adding it to the "Solution" section

If you can't summarize the work, your change may be unreasonably large / unrelated. Consider splitting your PR to make it easier to review and merge!

Migration Guide

This section is optional. If there are no breaking changes, you can delete this section.

If this PR is a breaking change (relative to the last release of Bevy), describe how a user might need to migrate their code to support these changes
Simply adding new functionality is not a breaking change.
Fixing behavior that was definitely a bug, rather than a questionable design choice is not a breaking change.

Can you please either clear out or fill out the PR description? The full text gets added to the commit when merged.

Can you please either clear out or fill out the PR description? The full text gets added to the commit when merged.
Also welcome to contributing to Bevy!

Thanks! Please review again.


Add minimum Python version requirement bump to changelog

This PR bumped the Python requirement from >=3.7 to >=3.9 and was then released as part of a minor version bump 7.30.2.
Originally posted by @tsibley in https://github.com/snakemake/snakemake/issues/2341#issuecomment-1648487223

Changelog should mention the Python version requirement bump (ideally ahead of time next time)

That version bump was my mistake. I forgot about the implications for scripts. I changed the implementation so that it is not necessary anymore. The next release will be python 3.7 again, with a corresponding note in the changelog.


Is it a bug when you click?

I have a question.
When I click the link on the tablet, it slides.
Can't you jump to the link when you click?

Thanks for reporting, this sounds like a bug in swiper.js. Can you please share a link to your swiper and which bS Swiper version do you use?

Thank you for your reply
The swiper link is https://bootscore.me/documentation/bs-swiper/
bS Swiper ver.<IP_ADDRESS>
Thank you

I can't reproduce this bug on bootscore.me site. However, there is a new release with updated swiper.js 8.3.2 https://github.com/bootscore/bs-swiper/releases/download/v<IP_ADDRESS>/bs-swiper-main.zip.
Please clear your browser cache or view in a private tab and let me know if that solved https://bootscore.me/documentation/bs-swiper/.
Thank you

I cached my browser but it doesn't improve. PCs and smartphones are okay, but only ipad and android tabred click the button and slide without jumping to the link and the card moves to the far left.

I triple checked this on different devices (even on iPad) but cannot reproduce this permanentely. It appears one time at Mac Safari but was gone when refreshing the page and never came back. The code itself looks good, so I guess there is something minor in swiper.js.
So, what you can do: Please downgrade to an earlier version and check if bug is still there
https://github.com/bootscore/bs-swiper/releases/download/<IP_ADDRESS>/bs-swiper-main.zip
Simply use the plugin-uploader for downgrade. This version doesn‘t crash something on your site, it‘s just an earlier version of swiper.js.
Thank you for reporting.


Layout Design Experiment

This is related to my comments here: https://github.com/gnosis/safe-react/issues/773#issuecomment-616203032
Curently, secondary content takes up around 20-30% of the screen right at the top. We should experiment with different layout(s) to in order to put the primary content more into the user's focus.

In some cases, the user has to scroll to even see the primary action of this screen such as this "Save" button

Example
One example could be to combine the Safe information with the Safelist dropdown option in the header

Also there might not be a need to have the Send / Receive buttons at their current positions

It is already possible to initiate a transaction from the assets and Address book tabs. We might consider removing these buttons and compensate it by

Adding a "+ Create Transaction" button in the Transaction tab, similar to for example the Remove Safe action button in the Settings tab.
Adding a QR code button to Safe information to open up the Receive modal

Would be good to come up with 2-3 different design proposals on how to optimize the layout so we can collect some feedback.

@alongoni let's plan on providing @lukasschor with a 2-3 proposals

Hi @lukasschor, I've been working in this 4 options. All options are focus in the secondary content, not changes at least for main content.
The options are from 1 to 4 progressively to less to more compact.
Option 1: The Safe Information and Send/Receive button joins in the header whith the Safe dropdown.
https://www.figma.com/proto/WQVRO14fPQQn47AaNha16M/Layout-Design-Experiment?node-id=1%3A2&scaling=min-zoom
Option 2: Based on Option 1, but Tabs menu adapts to a vertical collapsable menu. Even It's can keep open when resolutions is big (see option 3).
https://www.figma.com/proto/WQVRO14fPQQn47AaNha16M/Layout-Design-Experiment?node-id=25%3A147&scaling=min-zoom
Option 3: Based on options 1 and 2. The Send/Receive buttons go to the right, closer to the wallet connect information. In this prototype you can see how the setting section adapt to the new layout, keeping the save button more visible.
https://www.figma.com/proto/WQVRO14fPQQn47AaNha16M/Layout-Design-Experiment?node-id=125%3A1&scaling=min-zoom
Option 4: The safe information dropdown go to the right, and the wallet connection information is now in the same dropdown. This design looks a bit cleaner.
https://www.figma.com/proto/WQVRO14fPQQn47AaNha16M/Layout-Design-Experiment?node-id=43%3A198&scaling=min-zoom
Thanks!
cc: @nicosampler @fernandomg @pablofullana

Thanks. Interesting concepts!
Could you make one mockup that's a mix of these options?

Combined Safe list and Safe info in top-left corner from option 3

Expanding sidebar from option 4

Send/Receive buttons in the sidebar
Either below or above the tabs "Assets" etc.

Then i would try to gather some feedback on these.

Great!
This is the Option 5
https://www.figma.com/proto/WQVRO14fPQQn47AaNha16M/Layout-Design-Experiment?node-id=193%3A5&scaling=min-zoom

Ths sidebar very much reminds me of Zenhub. And in Zenhub you actually switch Workspaces from the sidebar, too.

So maybe we should bring this part also into the sidebar

What do you think?

I test the idea to put all together in the sidebar. The settings page have a diferent option to show the Safe Info.
https://www.figma.com/proto/WQVRO14fPQQn47AaNha16M/Layout-Design-Experiment?node-id=217%3A1&scaling=scale-down-width

Collected some initial feedback and looks like we are getting closer :). Could you make a version based on this option:

But with the following changes

Also expands on hover like with option 4, in non-expanded view show only blocky for the upper section

Also show Fiat balance (total amount on this Safe)

Remove this number as it was perceived as the number of pending transactions

Only show the Send button, no receive button

Instead of the etherscan icon, have a QR code icon next to the copy-paste icon (basically replaces the Receive button)

Hi, @lukasschor , I made the changes that suggested:
https://www.figma.com/proto/WQVRO14fPQQn47AaNha16M/Layout-Design-Experiment?node-id=278%3A1&scaling=min-zoom
Additionally, in this other prototype I add a (+) button offering to users pin up the expanded version of the menu. This option can coexist with the expand on hover version.
https://www.figma.com/proto/WQVRO14fPQQn47AaNha16M/Layout-Design-Experiment?node-id=282%3A1&scaling=min-zoom

Played around with it, too and tried out some ideas based on some initial feedback from other people. No particular strong opinion though.
@posthnikova
Could you maybe share your thoughts on these design experiments? Especially the last couple of mockups.

Nice prototypes!
I agree that the space could be a bit more optimized. Generally laptops have more horizontal space compared to their vertical screen real estate. Hence quite some dapp have side menus. This includes e.g. gmail, facebook, twitter, zenhub etc.
Here's my thoughts:

Maybe there's not even the needs to have the side bar collapsible. Do we really have that much info on the main part that it's necessary to collapse it?
If the side bar would be open all the time, switching safes becomes easier.

When we talk about saving precious vertical screen real estate, that empty white top bar seems like a waste of space.

This plus seems to be I can add something. If its purpose is to expand it, I would rather used chevrons or arrows e.g.

maybe that send button isn't even necessary anymore. Since I would expect to go to the balances page where there is a send button per assets anyway.

Other than those points I like it a lot actually.

Tried a more extreme experiment based on @tschubotz 's feedback on the header

I generally agree with Tobi's other comments. But there are a few things to consider.

Maybe there's not even the needs to have the side bar collapsible. Do we really have that much info on the main part that it's necessary to collapse it?
If the side bar would be open all the time, switching safes becomes easier.

Yes, there's is probably no need to collapse regarding the horizontal screen real estate. The feedback I got when showing around the designs, was that for the screens where there is an additional sidebar/tabbar in the main content (settings, apps), it looks a bit weird with the expanded version. But maybe the solution there is anyways to take these tabbar options as collapsable options in the main sidebar.

maybe that send button isn't even necessary anymore. Since I would expect to go to the balances page where there is a send button per assets anyway.

I think we should leave it because

There is currently no other way to open up the "Smart Contract Interaction" feature, so we would have to introduce this elsewhere in the interface
Creating transactions is most likely the main action of the Safe Multisig, so it's fine if it's omnipresent in the sidebar in my opinion, even if there is other ways to open up the send flows.

I generally like the side bar on desktop. Let's look at responsive layouts. On 1024 it looks good:

At 720 the sidebar takes a lot of space, we probably need to collapse it:

Please note there are no hovers on tablets/smartphones so the sidebar would collapse on tap. On mobile the whole content of the sidebar would move to the top. Therefore this duplication is unnecessary: https://prnt.sc/sj29we

I agree the sidebar can work. I'm unsure about removing the top white bar entirely, I think the way that the connected wallet is floating on its own makes it look a bit like a notification.
I wonder how clear it would be in this version how to switch between Safes. The side arrow/chevron seems to suggest expansion or moving towards something more than a drop-down style menu.
I also wonder how users would see their Safe's full address with this design. Only by copying it?

Hi! thanks to all for the feedback! it's so appreciated.
. Header (Top white bar): Agree with Tobias: it's a valuable space and we have to use it well.
. Side bar: Add a button (double chevron) at the bottom to collapse the sidebar. For large and medium resolutions the sidebar will be expanded by default. When the screens are small, the user can collapse it.
Here is the design:
https://www.figma.com/proto/WQVRO14fPQQn47AaNha16M/Layout-Design-Experiment?node-id=328%3A1&scaling=min-zoom

This is a quick prototype of my preferred behaviour: https://invis.io/T4XF6KSQX7M. Some thoughts:
Which view should be default: collapsed, expanded, or depending on the screen resolution? My preference is that it depends on the resolution: below 1024 collapsed view is default.
Should the sidebar expand on hover or on click, or both? I think both. There is 'fixed' state and 'hover' state. When the view is collapsed, hover opens 'hover' view which overlays the content. 'Fixed' view opens on click and condenses the content (grid should behave like this example: https://lh3.googleusercontent.com/aepyD62S5ymwEZPo_yWiDkdeQDkbXfvXyxuL0f3ldMVdrhCywcuN3_J0hlIc5dqZap8vtG05oaztns7G2wZBLVJsA0OLfRpZ4At2jw=w1064-v0).
Top bar: I think we should keep it. Currently it makes the landing page and the app look like it's the same service. When the content scrolls, connected wallet is always visible at the top. Plus we might need top bar in the future for dark mode switch.
Wallet dropdown: I modified proposed wallet info. I think we should keep the large identicon because it works nicely with other states: Connection error and Not connected https://prnt.sc/snbrts
Footer: I don't agree that footer should be part of the sidebar. It's not Safe-specific. And it's not visible in the collapsed state.
Some other ideas:
• Switch Safes inside sidebar (this was my second preferred version) https://invis.io/T4XF6KSQX7M#/418951901_Safe_List_Inside_Sidebar_1272px_
• Slider to browse through Safes https://invis.io/T4XF6KSQX7M#/418951948_Slider_1272px_
• Two levels sidebar https://invis.io/T4XF6KSQX7M#/418951946_Double_Sidebar_1272px_
• Switch Safes at the bottom https://invis.io/T4XF6KSQX7M#/418951950_Switch_Safes_Bottom_1272px_
• Switch Safes as a tab https://invis.io/T4XF6KSQX7M#/418951947_Safes_List_As_Tab_1272px_
• Collapse button at the top https://invis.io/T4XF6KSQX7M#/418951949_Switch_Button_At_The_Top_1272px_

@posthnikova Thanks a few thoughts:
Collapsable
I kind of agree with Tobi, not sure if we even need the sidebar to be collapsable. This would mean additional implementation effort, yet the actual value is unclear to me as we seem to have plenty of horizontal screen estate.
Wallet Dropdown
I would like to have more focus on the wallet type vs. the identicon, because it seems to confuse people to have two prominent identicons, especially as the difference between Safe address / connected Wallet has caused general confusion in the past. So the most important information there would be the Logo and type of the connected wallet, in my opinion. With secondary importance to the wallet address and identicon. And tertiary information being the network of the connected wallet (as we already show the notification if the network does not match the interface network)
Footer
Should we center the footer relative to the main content in the non-collapsed state? It looks off for me in this case
Double Sidebar
I really like the visual design of the double sidebar, and it would make switching Safes extremely fast. My concern would recognizability of the Safes, as I would assume barely anyone can decern their Safes just using the identicon. Would it show the name of the Safe on hover, is there another way to somehow show the name in the sidebar?
Other
I got pretty good feedback on calling the "Send" button "New transaction" instead. Do you feel strongly about calling it "Send" otherwise I would suggest to change it, at least for further feedback based on a clickable prototype.

not sure if we even need the sidebar to be collapsable.

@lukasschor Collapsing is only beneficial on small screens (below 1024). Expanded sidebar on such a screen wouldn't leave space for content at all https://prnt.sc/snd1rq. Collapsing should use this space https://prnt.sc/snd8g0

I would like to have more focus on the wallet type vs. the identicon, because
it seems to confuse people to have two prominent identicons

I wasn't aware of this. I don't have objections here.

Should we center the footer relative to the main content in the non-collapsed
state?

Yes, this is part of content grid.

Double Sidebar

I find this version not really viable, it's unclear how it would look with too many Safes.

Send

No strong opinion here, I will correct.

I made changes to wallet dropdown: https://invis.io/T4XF6KSQX7M. Other states:

I like the logos! Not sure about the identicons though, they are so small there one really needs to strain the eyes to look at them. Maybe it's better to just drop them.

I see you point @KristinaMayman. The main use-case is probably Metamask here, where a lot of people have multiple accounts and to quickly glanze if you are connected with the right account. I personally think this size would be sufficient for this, as it's usually enough to see if it's the "green one" or the "red one" :P
I would leave it in at least for the user test and see if there's some feedback on it.

I like this version with the big icon of the owner wallet type and the small identicon of the owner wallet address. That way the owner wallet identicon isn't competing with the Safe identicon and it's more clear that it "belong" to the owner wallet type.

I added all tabs (balances etc) and responsive layouts: https://invis.io/T4XF6KSQX7M. Starting to work on prototype for user tests.

Closing this for now. Will open a new implementation ticket, once we got back the results from the user tests.


feat(datepicker): add semantic classes

Add semantic classes to template to assist in styling

This addresses #2428.

Sounds good to me. But perhaps we should do the others as well.

Agreed


While running the d3net music seperation jupyter notebook in collab "AttributeError: module 'pynvml.nvml' has no attribute 'nvml_lib'" error is coming

2021-06-07 12:26:53,837 [nnabla][INFO]: Initializing CPU extension...
Traceback (most recent call last):
File "separate.py", line 96, in
ch_flip_average=True
File "separate.py", line 27, in run_separation
ctx = get_extension_context(args.context)
File "/usr/local/lib/python3.7/dist-packages/nnabla/ext_utils.py", line 97, in get_extension_context
mod = import_extension_module(ext_name)
File "/usr/local/lib/python3.7/dist-packages/nnabla/ext_utils.py", line 46, in import_extension_module
return importlib.import_module('.' + ext_name, 'nnabla_ext')
File "/usr/lib/python3.7/importlib/init.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1006, in _gcd_import
File "", line 983, in _find_and_load
File "", line 967, in _find_and_load_unlocked
File "", line 677, in _load_unlocked
File "", line 728, in exec_module
File "", line 219, in _call_with_frames_removed
File "/usr/local/lib/python3.7/dist-packages/nnabla_ext/cudnn/init.py", line 18, in
import nnabla_ext.cuda
File "/usr/local/lib/python3.7/dist-packages/nnabla_ext/cuda/init.py", line 114, in
check_gpu_compatibility()
File "/usr/local/lib/python3.7/dist-packages/nnabla_ext/cuda/init.py", line 71, in check_gpu_compatibility
from nnabla.utils.nvml import pynvml
File "/usr/local/lib/python3.7/dist-packages/nnabla/utils/nvml.py", line 39, in
load_nvml_for_win()
File "/usr/local/lib/python3.7/dist-packages/nnabla/utils/nvml.py", line 26, in load_nvml_for_win
if not (nvml.nvml_lib == None and sys.platform[:3] == "win"):
AttributeError: module 'pynvml.nvml' has no attribute 'nvml_lib'

Thanks for reporting the issue. It's been fixed in https://github.com/sony/nnabla/issues/892 (see also the workaround), and the fixed binary will be available in the next release of nnabla.

Closing this since this has been fixed in nnabla v1.20.0. Please reopen this issue if the problem still exists.


Striped tables.

Feature Description
Allow tables to display as striped.
Provide a brief summary of the feature you would like to see.
Have an option to display as striped, like mat-table-stripe.
Use Case
Makes reading the table much easier.
Describe the use case(s) that the proposed feature would enable.
Better viewing experience.

Why not just add a class to each even or add row?

We don't plan to add this directly; instead you can add a normal class binding to the row based on whether the index is even/odd

Cool thanks for the reply guys. Will do it that way then. Regards.

From: Jeremy Elbourn<EMAIL_ADDRESS>Sent: Wednesday, July 3, 2019 12:12 AM
To: angular/components
Cc: Jarrett Jordaan; Author
Subject: Re: [angular/components] Striped tables. (#16391)
Closed #16391https://github.com/angular/components/issues/16391.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/angular/components/issues/16391?email_source=notifications&email_token=AAF52S3ULT6A23K5WEIZUF3P5PHGNA5CNFSM4H3RBMM2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOSJQLNSQ#event-2455811786, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAF52S74EG4FKF2YMSEFFFDP5PHGNANCNFSM4H3RBMMQ.


Refactor command

This PR is to address #264 . Further detail of this PR will be added later.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 75.109%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
6044

Relevant Lines:
8047

💛  - Coveralls


Bar chart won't display when y-axis values are small (Chrome)

If the y-axis values in a bar chart are small, the chart won't display. This is because of a bug on line 331 of Chart.js. If num.toString() returns "5e-7", this code will throw a "TypeError: Cannot read property 'length' of undefined" in Chrome. Not tested in other browsers.
getDecimalPlaces = helpers.getDecimalPlaces = function(num){
if (num%1!==0 && isNumber(num)){
return num.toString().split(".")[1].length;
}
else {
return 0;
}
}

This has already been fixed in the master branch.


[test] Make swiftpm test robust against host triple differences

Hardcoding the triples was silly; the only interesting platform
difference is about which parts have a version number on macOS and which
do not.
This change is required for building on PPC64LE.

@benlangmuir can you please review & approve this cherry-pick?

@swift-ci please test


compatible with edge_type of src2dst and src2etype2dst

PR types

Bug fixes
PR changes

Others
Describe

compatible with edge_type of src2dst and src2etype2dst

lgtm


Adding  Software Version to Device Usage

During the review of the neuroimaging extension, MRIScannerUsage, we encountered a problem: most of the scanners have software associated with them. I created this issue to follow up on that discussion.
Luyba:

Question: MRI scanners are always used in connection to a software version (which is functioning as device control system and performs online image processing). I would suggest to link to the Software Version that was used during the Device Usage. Do we need this for all devices as option or is this something scanner specific?

Peyman

Completely agreed. I think adding it to the concept of device usage is more beneficial. There are cases where the device usage doesn't have any software associated with it, for example, the usage of a microtome. However, I think it is present in enough cases to consider it. Anyway, this seems like an important issue and needs more discussion, so I created an issue on OpenMinds-Core to discuss it further.

follow up question: I assume that the software version or even software could be changed using the same scanner / device (I know that his would be also true for blackrock acquisition systems for example).

What about the firmware and firmware version ?
We have the instrument (physical object), following some hardware specification, and running some firmware (code that is essential to the activity of the instrument and is loaded inside the instrument), and software (code running of the computer controlling the instrument and usually doing some data preprocessing.
In theory, each one can be versioned and get a PID (instrument /physical object, hardware type, firmware, software)

@jcolomb this is a good point. so far I would have categorized firmware as software to be honest (just not running on a users computer but directly as part of the hardware). we will discuss if a distinction in schema is required or if software just needs a specification (on where it can be run which I think we partially do already)


Add TwoPortHub (88009)

[ ] Rename existing SharpBrick.PoweredUp.Hub into BaseHub
[ ] Add TwoPortHub (88009) like TechnicMediumHub

Note: Note to everyone: I do not have the hardware and have in the foreseeable future no interest in purchasing them. If you want support for this hardware in this library, please contribute. I will guide you through the process and assist with everything needed.

Two methods how to do this:

Someone with the hardware is developing the missing hub and internal devices implementation.
A contributor with hardware is running the poweredup device list cli call and afterwards per listed port poweredup device dump-static-port -p <portId>. The information is then provided here in this ticket. This allows someone else to do the coding. Once completed, the contributor with the hardware can then run the examples to ensure it will still work.

Hi @tthiery ! Congrats... super structured library. I have two train hubs (2-port hubs), two remote hubs and a boost hub and maybe i can support you with the outputs of your CLI. If it is ok, i will open a new issue for the Boost Hub and PoweredUp Remote to not mix it up to much.
Cheers, Cornelius
Here the logs
Two Port Hub (Train Hub)
poweredup device list
Scan Started. Please select the Hub (using a number keys or 'q' to terminate):
1: Hub (with address<PHONE_NUMBER>26694)
1
Selected Hub with key 1
Discover Ports. Receiving Messages ...
.................................................
Discover Ports Function: 48 / 48
Hub: 0
  Port: 50
    IOTypeId: RgbLight
    HardwareRevision: <IP_ADDRESS>
    SoftwareRevision: <IP_ADDRESS>
    OutputCapability: True
    InputCapability: False
    LogicalCombinableCapability: False
    LogicalSynchronizableCapability: False
    ModeCombinations: []
    UsedCombinationIndex: 0
    MultiUpdateEnabled: False
    ConfiguredModeDataSetIndex: []
    Mode: 0
      Name: COL O
      IsInput: False
      IsOutput: True
      RawMin: 0
      RawMax: 10
      PctMin: 0
      PctMax: 100
      SIMin: 0
      SIMax: 10
      Symbol:
      InputSupportsNull: False
      InputSupportFunctionalMapping20: False
      InputAbsolute: False
      InputRelative: False
      InputDiscrete: False
      OutputSupportsNull: False
      OutputSupportFunctionalMapping20: True
      OutputAbsolute: False
      OutputRelative: False
      OutputDiscrete: True
      NumberOfDatasets: 1
      DatasetType: SByte
      TotalFigures: 1
      Decimals: 0
      DeltaInterval: 0
      NotificationEnabled: False
    Mode: 1
      Name: RGB O
      IsInput: False
      IsOutput: True
      RawMin: 0
      RawMax: 255
      PctMin: 0
      PctMax: 100
      SIMin: 0
      SIMax: 255
      Symbol:
      InputSupportsNull: False
      InputSupportFunctionalMapping20: False
      InputAbsolute: False
      InputRelative: False
      InputDiscrete: False
      OutputSupportsNull: False
      OutputSupportFunctionalMapping20: False
      OutputAbsolute: True
      OutputRelative: False
      OutputDiscrete: False
      NumberOfDatasets: 3
      DatasetType: SByte
      TotalFigures: 3
      Decimals: 0
      DeltaInterval: 0
      NotificationEnabled: False
  Port: 59
    IOTypeId: Current
    HardwareRevision: <IP_ADDRESS>
    SoftwareRevision: <IP_ADDRESS>
    OutputCapability: False
    InputCapability: True
    LogicalCombinableCapability: False
    LogicalSynchronizableCapability: False
    ModeCombinations: []
    UsedCombinationIndex: 0
    MultiUpdateEnabled: False
    ConfiguredModeDataSetIndex: []
    Mode: 0
      Name: CUR L
      IsInput: True
      IsOutput: False
      RawMin: 0
      RawMax: 4095
      PctMin: 0
      PctMax: 100
      SIMin: 0
      SIMax: 2444
      Symbol: mA
      InputSupportsNull: False
      InputSupportFunctionalMapping20: False
      InputAbsolute: True
      InputRelative: False
      InputDiscrete: False
      OutputSupportsNull: False
      OutputSupportFunctionalMapping20: False
      OutputAbsolute: False
      OutputRelative: False
      OutputDiscrete: False
      NumberOfDatasets: 1
      DatasetType: Int16
      TotalFigures: 4
      Decimals: 0
      DeltaInterval: 0
      NotificationEnabled: False
    Mode: 1
      Name: CUR S
      IsInput: True
      IsOutput: False
      RawMin: 0
      RawMax: 4095
      PctMin: 0
      PctMax: 100
      SIMin: 0
      SIMax: 2444
      Symbol: mA
      InputSupportsNull: False
      InputSupportFunctionalMapping20: False
      InputAbsolute: True
      InputRelative: False
      InputDiscrete: False
      OutputSupportsNull: False
      OutputSupportFunctionalMapping20: False
      OutputAbsolute: False
      OutputRelative: False
      OutputDiscrete: False
      NumberOfDatasets: 1
      DatasetType: Int16
      TotalFigures: 4
      Decimals: 0
      DeltaInterval: 0
      NotificationEnabled: False
  Port: 60
    IOTypeId: Voltage
    HardwareRevision: <IP_ADDRESS>
    SoftwareRevision: <IP_ADDRESS>
    OutputCapability: False
    InputCapability: True
    LogicalCombinableCapability: False
    LogicalSynchronizableCapability: False
    ModeCombinations: []
    UsedCombinationIndex: 0
    MultiUpdateEnabled: False
    ConfiguredModeDataSetIndex: []
    Mode: 0
      Name: VLT L
      IsInput: True
      IsOutput: False
      RawMin: 0
      RawMax: 3893
      PctMin: 0
      PctMax: 100
      SIMin: 0
      SIMax: 9600
      Symbol: mV
      InputSupportsNull: False
      InputSupportFunctionalMapping20: False
      InputAbsolute: True
      InputRelative: False
      InputDiscrete: False
      OutputSupportsNull: False
      OutputSupportFunctionalMapping20: False
      OutputAbsolute: False
      OutputRelative: False
      OutputDiscrete: False
      NumberOfDatasets: 1
      DatasetType: Int16
      TotalFigures: 4
      Decimals: 0
      DeltaInterval: 0
      NotificationEnabled: False
    Mode: 1
      Name: VLT S
      IsInput: True
      IsOutput: False
      RawMin: 0
      RawMax: 3893
      PctMin: 0
      PctMax: 100
      SIMin: 0
      SIMax: 9600
      Symbol: mV
      InputSupportsNull: False
      InputSupportFunctionalMapping20: False
      InputAbsolute: True
      InputRelative: False
      InputDiscrete: False
      OutputSupportsNull: False
      OutputSupportFunctionalMapping20: False
      OutputAbsolute: False
      OutputRelative: False
      OutputDiscrete: False
      NumberOfDatasets: 1
      DatasetType: Int16
      TotalFigures: 4
      Decimals: 0
      DeltaInterval: 0
      NotificationEnabled: False

poweredup device dump-static-port -p 50
Scan Started. Please select the Hub (using a number keys or 'q' to terminate):
1: Hub (with address<PHONE_NUMBER>26694)
1
Selected Hub with key 1
Discover Port 50. Receiving Messages ...
.................
Discover Ports Function: 16 / 16
##################################################
0B-00-43-32-01-01-02-00-00-03-00
05-00-43-32-02
12-00-44-32-00-00-43-4F-4C-20-4F-00-00-00-00-00-00-00
0E-00-44-32-00-01-00-00-00-00-00-00-20-41
0E-00-44-32-00-02-00-00-00-00-00-00-C8-42
0E-00-44-32-00-03-00-00-00-00-00-00-20-41
0B-00-44-32-00-04-00-00-00-00-00
08-00-44-32-00-05-00-44
0A-00-44-32-00-80-01-00-01-00
12-00-44-32-01-00-52-47-42-20-4F-00-00-00-00-00-00-00
0E-00-44-32-01-01-00-00-00-00-00-00-7F-43
0E-00-44-32-01-02-00-00-00-00-00-00-C8-42
0E-00-44-32-01-03-00-00-00-00-00-00-7F-43
0B-00-44-32-01-04-00-00-00-00-00
08-00-44-32-01-05-00-10
0A-00-44-32-01-80-03-00-03-00
##################################################

poweredup device dump-static-port -p 59
Scan Started. Please select the Hub (using a number keys or 'q' to terminate):
1: Hub (with address<PHONE_NUMBER>26694)
1
Selected Hub with key 1
Discover Port 59. Receiving Messages ...
.................
Discover Ports Function: 16 / 16
##################################################
0B-00-43-3B-01-02-02-03-00-00-00
05-00-43-3B-02
12-00-44-3B-00-00-43-55-52-20-4C-00-00-00-00-00-00-00
0E-00-44-3B-00-01-00-00-00-00-00-F0-7F-45
0E-00-44-3B-00-02-00-00-00-00-00-00-C8-42
0E-00-44-3B-00-03-00-00-00-00-00-C0-18-45
0B-00-44-3B-00-04-6D-41-00-00-00
08-00-44-3B-00-05-10-00
0A-00-44-3B-00-80-01-01-04-00
12-00-44-3B-01-00-43-55-52-20-53-00-00-00-00-00-00-00
0E-00-44-3B-01-01-00-00-00-00-00-F0-7F-45
0E-00-44-3B-01-02-00-00-00-00-00-00-C8-42
0E-00-44-3B-01-03-00-00-00-00-00-C0-18-45
0B-00-44-3B-01-04-6D-41-00-00-00
08-00-44-3B-01-05-10-00
0A-00-44-3B-01-80-01-01-04-00
##################################################

poweredup device dump-static-port -p 60
Scan Started. Please select the Hub (using a number keys or 'q' to terminate):
1: Hub (with address<PHONE_NUMBER>26694)
1
Selected Hub with key 1
Discover Port 60. Receiving Messages ...
.................
Discover Ports Function: 16 / 16
##################################################
0B-00-43-3C-01-02-02-03-00-00-00
05-00-43-3C-02
12-00-44-3C-00-00-56-4C-54-20-4C-00-00-00-00-00-00-00
0E-00-44-3C-00-01-00-00-00-00-00-50-73-45
0E-00-44-3C-00-02-00-00-00-00-00-00-C8-42
0E-00-44-3C-00-03-00-00-00-00-00-00-16-46
0B-00-44-3C-00-04-6D-56-00-00-00
08-00-44-3C-00-05-10-00
0A-00-44-3C-00-80-01-01-04-00
12-00-44-3C-01-00-56-4C-54-20-53-00-00-00-00-00-00-00
0E-00-44-3C-01-01-00-00-00-00-00-50-73-45
0E-00-44-3C-01-02-00-00-00-00-00-00-C8-42
0E-00-44-3C-01-03-00-00-00-00-00-00-16-46
0B-00-44-3C-01-04-6D-56-00-00-00
08-00-44-3C-01-05-10-00
0A-00-44-3C-01-80-01-01-04-00
##################################################

What is up today? First Mario now TwoPortHub 😁
Yes, do exactly like that. Add a new issue for the remote and the boost hub.

Maybe a rainy Sunday 😉

Just finished half of Mario today. Added TwoPortHub in a new pull request (#97). The implementation should already work for port A and B .. however, with technic devices I guess ;).
Missing

Voltage and Current have different values then for TechnicMediumHub / MarioHub. However, it is the same device type 0x14 / Voltage with now different static port info. Need to add some design. Too late for that 😀
Any LEGO System device (motors etc) you can drop me the information of above (dynamic devices should work).

Let me finish the Voltage situation and then we can perform a test run if you like.

Fixed the Voltage thing. The static port information messages in the code are now selected by the system type.
Test Script

Check Voltage and Current examples
Check RgbColor example
If you have a technic motor, modify and check a motor example

@corneliusmunz Have you had a chance to check this? Or are you similar stuck as with the MoveHub?

@tthiery Unfortunately today there was no rain 😉  But i was able to modify the RgbColor example (change hub type) and it works. If i find time i will connect a technic motor and maybe a train motor (Basic Motor) But for that i have to implement a concrete basic motor class. I will give you feedback as soon as possible

@tthiery I have tested it with the adapted ExampleMotorControl and a TechnicLargeLinearMotor. Additionally i have done the test with the adapted ExampleVoltage.  Both examples works as expected 👍 I also tried to implement a Device Class for the MediumLinearMotor (which is called in the DeviceType enum ExternalMotorWithTacho) but this was not successfull. But This is despite the Hub Implementation. I will try to experiment a littlebit more with that additional Device and send you a PR when it will work.
Output of the ExampleVoltage
info: Example[0]
      Finding Service
info: Example[0]
      Press RETURN to cancel Scanning
info: SharpBrick.PoweredUp.PoweredUpHost[0]
      Discovered log of type TwoPortHub with name 'myTrainHub' on Bluetooth Address '158897331706239'
info: Example[0]
      Connecting to Hub
info: Example[0]
      myTrainHub
info: Example[0]
      LegoSystem_TwoPortHub
info: Example[0]
      Press RETURN to continue to the action

warn: Example[0]
      Voltage L: 7210mV (75%)

So in my point of view, you can merge this into master.
Cheers, Cornelius

Awesome. Thanks a lot for your help!!!


Can't download Binary from S3

https://mapbox-node-binary.s3.amazonaws.com/sqlite3/v3.1.11/node-v48-linux-arm.tar.gz
Permission denied 403, any solutions?

We do not provide pre-compiled binaries for arm arch. We tried to do this for a while (#298) but it was unsustainable since we do not have a way to automatically create them. So your build will fall back to a source compile whenn the 403 happens (which is really a 404)


Chrome bug

It is not working in Chrome

Not working for me too.

This does nobody any good without steps to reproduce, example code, a detailed description of the issue, etc.

Not working for me too.
I am on Chrome 52 on OSX. Its only working when I enable experimental-web-platform-features in flags.

What I could notice is that Chrome doesn't support position:sticky; while Safari and Firefox does.
In Chrome it falls to position:fixed; breaking the layout when you use it as sidebar sticky.
The div class="fixedsticky-dummy" appears on Chrome's Inspector while in Safari and Firefox it doesn't.
Browsers tested:
Safari Mac 10.0.2
Firefox Mac 50.1.0
Chrome Mac 55.0.2883.95


Error when opening new model builder.

System Information (please complete the following information):

Model Builder Version (available in Manage Extensions dialog): <IP_ADDRESS>5601
Microsoft Visual Studio Enterprise 2019: 16.11.8

Describe the bug

On which step of the process did you run into an issue: opening new model builder
Clear description of the problem:
Error message:
"The model filename.mbconfig was created in an older version of Model Builder and cannot be opened with the current version. For compatibility, do you wish to update filename.mbconfig?
Note: Updating older.mbconfig files may result in loss of imformation."

To Reproduce
Steps to reproduce the behavior:

Select Create a new project from the Visual Studio 2019 start window;
Choose the C# Console App (.NET Core) project template with .Net 5.0;
Right click the project and click Add>Machine Learning Model...;
Click Add button to create the model builder;
Prompt Error dialog when opening the model builder.

Expected behavior
No error when opening new model builder
Screenshots
If applicable, add screenshots to help explain your problem.

Additional context

Can continue the next step after click Yes or No button.
Occurs on VS2019 and VS2022
new created mbconfig file:

not repro this issue on latest main: <IP_ADDRESS>6901


Use C++ functions to parse numeric literals and check bounds

What's going on with hexpr.lex.C? Was it up to date with hexpr.l?

Maybe different flex versions; this parser needs some renovation work at some point but it is good to have this fix in mind for any future work (so we don't silently accept and truncate any literal input).


Add Location of Configfile to README.md

I wanted to set some config settings permanently.
I had to search through the source code to find it.
Making this PR to help others

The Mac path is wrong. Should be ~/Library/Application Support/Zotify/config.json


Update project-calendar.md

Small edits on this one.

This was a leftover branch that was never turned into a PR - it needs updating or recreating with the new content structure


operator kiali (1.81.0)

/pipeline restart community-hosted-pipeline

This was the initial error:
[github-add-summary-comment : gather-info] 2024/03/04 16:45:14 warning: unsuccessful cred copy: ".docker" from "/tekton/creds" to "/home/nonroot": unable to create destination directory: mkdir /home/nonroot: permission denied
[github-add-summary-comment : gather-info] + PR_NAME=community-hosted-pipeline-runt2m8t
[github-add-summary-comment : gather-info] + mkdir community-hosted-pipeline-runt2m8t
[github-add-summary-comment : gather-info] + echo 'Getting pipeline logs'
[github-add-summary-comment : gather-info] Getting pipeline logs
[github-add-summary-comment : gather-info] + tkn pipelinerun logs community-hosted-pipeline-runt2m8t
[github-add-summary-comment : gather-info] task preflight-trigger has failed: TaskRun "community-hosted-pipeline-runt2m8t-preflight-trigger" failed to finish within "1h0m0s"
[github-add-summary-comment : gather-info] failed to get logs for task preflight-trigger : task preflight-trigger failed: pods "community-hosted-pipeline-runt2m8t-preflight-trigger-pod" not found. Run tkn tr desc community-hosted-pipeline-runt2m8t-preflight-trigger for more details


Use crc32c checksums in ImageLayer

We add a summary chapter to the ImageLayer file. This chapter includes a
Vec of checksums for each block in the file.
These checksums are stored in memory for as long as the file is loaded.
#427 #519

Hmm, now that I think about this some more, I think a per-page checksum is not the right approach, we should have just one checksum over the whole file. Reasons:

The point is to recognize if a file is corrupt for some reason. What should happen if you detect corruption? We want to reconstruct it from the original WAL, if we still have it, or download it from S3 if we have it there. I think it makes more sense to recover the whole file, rather than an individual block.

If there's something corrupt in a file, how much do you really trust the rest of the file? We have to be careful to have a checksum on each individual part of the file. You're doing that in this PR, and I don't see any obvious gaps, but still I'd rather have a more wholesale solution where you verify the checksum once, and after that you can trust the contents.

Cosmic ray is the classic example of corruption, but more likely, a bug in SSD or RAID controller firmware or something like that. A fairly common failure mode is that a page is written to wrong location, so you might see one block being replaced with a block from a completely unrelated file. That's a problem when the CRC is stored in the data block itself: the CRC will match because it's copied along with the data. That's less of a problem with this PR, because you're storing the CRCs separately from the data pages, but I'm still worried about that kind of problems. You could include the segment tag and block number in the CRC of each page to make that more robust, but it makes things slightly more complicated again.

4 Postgres actually already has checksums on data pages, in the page header. It's optional, I'm not sure if we are enabling them at the moment, but we probably should.
So all in all, I think a single per-file CRC makes more sense, after all. Perhaps you can make 'bookfile' to calculate it?

Sounds good, I'll take a look at adding this in bookfile


Bug when following the documentation.

https://docs.confident-ai.com/docs/getting-started#llm-evaluated-metrics
def test_summarization():
    input = "What if these shoes don't fit? I want a full refund."

    # Replace this with the actual output from your LLM application
    actual_output = "If the shoes don't fit, the customer wants a full refund."

    summarization_metric = LLMEvalMetric(
        name="Summarization",
        criteria="Summarization - determine if the actual output is an accurate and concise summarization of the input.",
        evaluation_params=[LLMTestCaseParams.INPUT, LLMTestCaseParams.ACTUAL_OUTPUT],
        minimum_score=0.5
    )
    test_case = LLMTestCase(input=input, actual_output=actual_output)
    assert_test(test_case, [summarization_metric])

The documentation does not say that OPENAI_API_KEY is required for this step. The test fails with
 pydantic.error_wrappers.ValidationError: 1 validation error for ChatOpenAI
E   __root__
E     Did not find openai_api_key, please add an environment variable `OPENAI_API_KEY` which contains it, or pass  `openai_api_key` as a named parameter. (type=value_error)

Please update the docs and include the instructions.

@rommik-nuvalence you can supply the openai api key by setting it as an env variable in the terminal like this:
export OPENAI_API_KEY="your openai api key"


fix: subscribe before getConfig

Codecov Report

Merging #186 into master will decrease coverage by 0.06%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #186      +/-   ##
==========================================
- Coverage   80.65%   80.59%   -0.07%
==========================================
  Files         190      190
  Lines        6332     6332
  Branches      850      850
==========================================
- Hits         5107     5103       -4
- Misses        842      846       +4
  Partials      383      383

Impacted Files
Coverage Δ

packages/hub/src/config-manager/ConfigClient.ts
90% <100%> (ø)
:arrow_up:

packages/metrics/src/collect/MetricsCollector.ts
73.52% <0%> (-11.77%)
:arrow_down:

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 47c901d...8644a54. Read the comment docs.


remote bme680

hi, this module looks beautiful and im trying to implement it in my mirror as well, however my set up is little different, since my raspberry pi is already fitted inside the frame. i have a pico attached to bme680 sensor, and the data is being pushed using mqtt and im visualising the data in homebridge. would you consider adding a feature which would make it possible to use remote bme680 sensor to this module. i have looked into mqtt module as well and decided to give yours a try.

Hi,
I'm OK to improve this module (and I would be pleased to have happy users of my modules), but in my opinion, your request doesn't deserve this module.
This module is essentially designed to retrieve sensor data (the hard part) and to provide this data to other modules specifically designed to display weather information (by sending notifications).
The fact that this module can display information by itself is more like a bonus.
Regarding the code, using external data (like events from mqtt) would be equivalent to only keep the njk and css files of this module (the easy part).
So, instead of modifying this module I will go on a fresh new and very simple module designed to listen to events and display them (using my njk/css files if you like the display).


Bump Marathon to 1.8.239

High-level description
Bump Marathon to 1.8.239
Corresponding DC/OS tickets (required)
JIRA Issues:

MARATHON-8721
MARATHON-8719

Related tickets (optional)

MARATHON-8725

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[x] Change log from the last version integrated (this should be a link to commits for easy verification and review): 4b02f3462..a6095a83d
[x] Included a test which will fail if code is reverted but test is not. If there is no test please explain.
[x] Test Results: Marathon release artifacts are only published if tests succeed

@mesosphere-mergebot label ready for review

@mesosphere-mergebot merge-it

@mesosphere-mergebot merge-it


Fixes Build status min rev documentation #90

This change is

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

Files
Coverage Δ

...lation/Controllers/TranslationEnginesController.cs
94.13% <ø> (ø)

:loudspeaker: Thoughts on this report? Let us know!.