Added Skeleton loader component

What was changed
Added an animated skeleton loader that will render a span that will indicate something that is loading in
Skeleton Loader Features
<SkeletonLoader count={5} />

Will add 5 lines of skeleton loading
<SkeletonLoader radius="circle" />

Right now the two types of border radiuses are 'normal' and 'circle'
Notes
Skeleton loader is created but not rendered anywhere in the UI but is in place for when needed below is a still of what the loader could look like loading in workflows
Image

@josephriosIO Let's either resolve the conflicts or close this. I'll leave it to your discretion.

@josephriosIO Let's either resolve the conflicts or close this. I'll leave it to your discretion.

this is in git hell right now


⚠ ClamAV has degraded performance

In 49a7944, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 427 ms

Resolved: ClamAV performance has improved in 0a990ce.


Error: 'pipe' not found in imported namespace 'v'

Error when running npm run build or yarn build
package.json:
"react-hook-form": "7.51.5",
"@hookform/resolvers": "3.6.0",
"valibot": "0.31.1"

I tried too:
"react-hook-form": "7.51.5",
"@hookform/resolvers": "3.6.0",
"valibot": "0.36.0"

Login.tsx page

Please try again after updating everything to the latest version.
"react-hook-form": "7.52.1",
"@hookform/resolvers": "3.9.0",
"valibot": "0.36.0"

I tried but it didn't work
The error is only on production, locally it works
It worked for me by separating the import pipe
import * as v from 'valibot'
import { pipe } from 'valibot'
...
const schema = v.object({
  email: pipe(v.string('É preciso digitar um email'), v.email('Email inválido')),
  password: pipe(v.string('É preciso digitar uma senha'), v.minLength(5, 'A senha deve conter no mínimo 5 caracteres'))
})

Thanks for the info. I will leave this open for now to see if more people encounter this problem.

I am also running into this issue (or am I missing something?). The workaround did not work for me:

Dependencies versions:
    "react-hook-form": "^7.52.2",
    "@hookform/resolvers": "^3.9.0",
    "valibot": "^0.37.0",
    "@typeschema/valibot": "^0.13.5",

Update, the workaround did work by downgrading to version 0.36:

Yes, I think the problem is that some packages may use a different version of Valibot.

Some packages as in the hookform resolvers?

Could be. If more people encounter this problem, I will look into it.

i am also facing a similar issue. in my case, it is throwing TypeError: Cannot read properties of undefined (reading 'object') error.
this is how i am using it:
import v from 'valibot';

key: v.pipe(v.string(), v.transform(input=>input))

i have other fields as well but the error is being thrown only from v.string in the pipe.

Can you try to change your import to import * as v from 'valibot';?

Can you try to change your import to import * as v from 'valibot';?

it is working if i do it that way. thank you

This seems to be fixed.


cannot create gun in sandbox scene

The gun works fine in the tutorial, but does not appear in the sandbox scene. The toy gun needs to be added to the sandbox.

@scottdangelo if the fix I just pushed works for you, feel free to close.

That fixes it.


State of project ?

Hi, I would like to know if this project is discontinued or just not maintained anymore ? Maybe that should be mentioned in the README.md

Accepting PRs :smile_cat:

Thanks, @etke should I make a PR, updating the documentation ?
I packaged checksec.rs for the AUR (ArchLinux User Repositories), just in order to learn a bit more about packaging a Rust package, I also ran into some troubles about tests failing (doc/documentation related tests), should I open a new issue about that ?

@AkechiShiro, please create an issue for test failures.


fix: add hook to handle incomplete commands

What does this PR do?
Adds hook to handle incomplete commands for tax-free
What issues does this PR fix or reference?
@W-12212675@

QA notes:
✅ 1,2,3,4,5 args, shows all possible matches:
➜  sfdx-cli git:(phale/command-incompolete) ./bin/run install
? Which of these commands do you mean (Use arrow keys)
❯ plugins install
  force package beta install
  force package beta install report
  force package install
  force package install report

manually checked options returned against what commands returns by running:
./bin/run commands --no-header --columns 'Command' | fzf
❌  typed partial command, the hook finds 1 match and runs what it found, even though I didn't type the full command nor answered (no prompt rendered):
➜  sfdx-cli git:(phale/command-incompolete) ./bin/run verify -h
Validate a digital signature.

USAGE
  $ sfdx plugins trust verify -n <value> [--json] [-r <value>]

FLAGS
  -n, --npm=<value>       (required) Specify the npm name. This can include a tag/version.
  -r, --registry=<value>  The registry name. The behavior is the same as npm.

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Validate a digital signature.

  Verifies the digital signature on an npm package matches the signature and key stored at the expected URLs.

EXAMPLES
  $ sfdx plugins trust verify --npm @scope/npmName --registry http://my.repo.org:4874

  $ sfdx plugins trust verify --npm @scope/npmName

➜  sfdx-cli git:(phale/command-incompolete) ./bin/run which verify
 ›   Error: command verify not found
➜  sfdx-cli git:(phale/command-incompolete) ./bin/run search
? Search for a command verify
❯ plugins trust verify
──────────────
Validate a digital signature.

Users might run sfdx verify and think it's a valid command, but then running sfdx which <command> will fail because it doesn't resolve commands the same way the hook does.
This seems to happen when you type a word that is part of only 1 command, a few examples:
plugins trust verify: the hook will run that command whenever you try ./bin/run trust or ./bin/run verify.
auth jwt grant: ./bin/run auth shows all auth * cmds, ./bin/run jwt executesauth jwt grant.
autocomplete script: ./bin/run script executesautocomplete script.
⚠   typed partial command, expected prompt asking all possible options but the hook ran the first match:
➜  sfdx-cli git:(phale/command-incompolete) ./bin/run plugins
No plugins installed.
➜  sfdx-cli git:(phale/command-incompolete) ./bin/run search
? Search for a command plugins
❯ plugins
  plugins inspect
  plugins install
  plugins add
  plugins link
  plugins uninstall
  plugins unlink
  plugins remove
  plugins update
  plugins generate
(Move up and down to reveal more choices)
➜  sfdx-cli git:(phale/command-incompolete)

This happens when the typed arg is an actual command, I think this is ok as the command is correct but also was expecting the prompt with what ./bin/run search shows for plugins. 🤷🏼
Another example:
the following are valid commands:

force package beta version create
force package beta version create list
force package beta version create report

./bin/run force package create: executes force package beta version create, no prompt.
✅ typed an invalid command, oclif fired the command_not_found instead of command_incomplete:
➜  sfdx-cli git:(phale/command-incompolete) ✗ ./bin/run asfsaf
 ›   Warning: asfsaf is not a sfdx command.
Did you mean alias set? [y/n]: n
 ›   Error: Run sfdx help for a list of available commands.

see: https://github.com/oclif/core/blob/main/src/config/config.ts#L331-L333
❌ the hook doesn't respect the short flag for help, always shows the full help text:
➜  sfdx-cli git:(phale/command-incompolete) ✗ ./bin/run org list -h
? Which of these commands do you mean force org list
list all orgs you’ve created or authenticated to

USAGE
  $ sfdx force org list [--all] [-p --clean] [--skipconnectionstatus] [--verbose] [--json] [--loglevel
    trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]

FLAGS
  -p, --noprompt                                                                    do not prompt for confirmation
  --all                                                                             include expired, deleted, and unknown-status scratch orgs
  --clean                                                                           remove all local org authorizations for non-active scratch orgs.  Use
                                                                                auth:logout to remove non-scratch orgs
  --json                                                                            format output as json
  --loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL)  [default: warn] logging level for this command invocation
  --skipconnectionstatus                                                            skip retrieving the connection status of non-scratch orgs
  --verbose                                                                         list more information about each org

DESCRIPTION
  list all orgs you’ve created or authenticated to

EXAMPLES
  $ sfdx force:org:list

  $ sfdx force:org:list --verbose --json

  $ sfdx force:org:list --verbose --json > tmp/MyOrgList.json

➜  sfdx-cli git:(phale/command-incompolete) ✗

compare it with what sfdx force org list -h returns.
✅ prompt times out after 10s:
➜  sfdx-cli git:(phale/command-incompolete) ✗ ./bin/run force list
? Which of these commands do you mean (Use arrow keys)
❯ force community template list
  alias list
  force apex log list
  auth list
  config list
  force org list
  force schema sobject list
(Move up and down to reveal more choices)
    Error: Timed out after 10000 ms.
➜  sfdx-cli git:(phale/command-incompolete) ✗ echo $?
1

⚠ the prompt is still rendered even if the process isn't attached to a terminal:
➜  sfdx-cli git:(phale/command-incompolete) ✗ ./bin/run force list | node -p '`Attached to a terminal?: ${Boolean(process.stdin.isTTY)}`'
Attached to a terminal?: false
    Error: Timed out after 10000 ms.
➜  sfdx-cli git:(phale/command-incompolete) ✗ sfdx force list | node -p '`Attached to a terminal?: ${Boolean(process.stdin.isTTY)}`'
Attached to a terminal?: false
 ›   Error: command force:list not found
➜  sfdx-cli git:(phale/command-incompolete) ✗

./bin/run ... still timed out after 10s so it will not block a CI process if there's a typo in a pipeline.
I think this is fine (we could also save those 10s by skipping the prompt is process.stdin.isTTY === false. If you want you can specify the 10s timeout in the hook rather than relying on the default timeout set in sf-plugins-core in the case we change it.

qa notes:
✅ emits warning there's just one match


Change selection-box to multi-check-box group in AddCard -> Stored

Usually I need double add the card to both deck and album, I think this change will make it really handy.

Cards in your deck are also in your album!


[Improvement] Automatically switch node version when we cd or git checkout

avm can only do half the job i.e. cd
It will be awesome it nvm can handle what avm does and also when we do git checkout

You can set that up yourself with a post-update git hook that does nvm use.
For nvm itself to hook into cd and/or git is too intrusive a default.


[ipynb][Solarized Light] Markdown text color while editing

Issue Type: Feature Request
In a python Notebook, when I use Solarized Light Color theme and edit a Markdown cell, the text color is the same when I select the text or not, i.e. there is no selection highlighting. I think is only a color issue in the theme and should be changed.
This is a screenshot while editing the markdown cell (a few words in the paragraph are selected):

This is with another color theme:

Extension version: 2020.4.76186
VS Code version: Code 1.45.0 (d69a79b73808559a91206d73d7717ff5f798f23c, 2020-05-07T16:10:24.511Z)
OS version: Linux x64 5.6.10-3-MANJARO

Thanks for letting us know @fedeman.  That looks annoying.

It also happens con "Code" cells, not only on "Markdown".
Windows version.

It also happens con "Code" cells, not only on "Markdown".
Windows version.

You're right, I didn't note this at that moment since I was writing a Markdown cell but I confirm now that in code cells is the same issue.

Thanks for your feedback. This issue will likely be addressed once VS Code adds native support for editing notebooks. Please see https://github.com/microsoft/vscode/issues/91987.

Hi,
I see that this issue still persists and it is pretty annoying. Is there any way to push this separately from https://github.com/microsoft/vscode/issues/91987?
Thanks!


fix(text-validation) - pass only values that are strings

1. Description
Add a transform function to make the validation work when we're passing numbers or booleans to our text validation.

Screenshots
https://www.loom.com/share/b7a127623c5b41e78d6d3f2d21fcba59?focus_title=1&muted=1&from_recorder=1
Related Resources

https://linear.app/remote/issue/RMT-446/jsf-text-validation-is-incorrect

2. Type of Change (select one)

[X] Bug fix (non-breaking change that fixes an issue)

I'll create a minor version because we're updating the yup version.
If it was only the fix probably, I'd do a patch.
What do you think @sandrina-p @brennj?


feat(fetch): patch the fetch API

fixes #108

@IgorMinar this seems to be working...
I haven't patched more APIs because:

APIs returning Promise are most of the time experimental - we might want to wait for more browsers to support fetch to test it (currently only Chrome supports it as of the SL versions),
I prefer that we agree on a first PR before jumping into this.

Note: #118 has an updated script to fetch more .idl and that will help

looks good! thanks


IPAD -Attachment -  Extra white line displayed in Preview page

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Log in app
Tap on any conversation, click on the + button in the compose box
Click on add attachment
Upload a PDF file
Tap on the PDF preview

Expected Result:
The preview page should not display an extra white line
Actual Result:
Extra white line displayed in Preview page
Workaround:
Unknown
Platform:

Where is this issue occurring?

iOS IPAD

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

https://user-images.githubusercontent.com/93399543/152643265-b69ba2a0-32cb-4a87-816a-65b28e4ea0fe.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause
Slack conversation:
View all open jobs on GitHub

Triggered auto assignment to @yuwenmemon (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

Proposal
This diff will solve this issue
diff --git a/src/components/AttachmentModal.js b/src/components/AttachmentModal.js
index 1fc8d10c5..0d0b80417 100755
--- a/src/components/AttachmentModal.js
+++ b/src/components/AttachmentModal.js
@@ -139,7 +139,7 @@ class AttachmentModal extends PureComponent {
             ? addEncryptedAuthTokenToURL(this.state.sourceURL)
             : this.state.sourceURL;

-        const attachmentViewStyles = this.props.isSmallScreenWidth
+        const attachmentViewStyles = this.props.isSmallScreenWidth || this.props.isMediumScreenWidth
             ? [styles.imageModalImageCenterContainer]
             : [styles.imageModalImageCenterContainer, styles.p5];

Here is the result:

Before
After

@kakajann looks good to me!

Triggered auto assignment to @puneetlath (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

Current assignee @puneetlath is eligible for the AutoAssignerTriage assigner, not assigning anyone new.

Triggered auto assignment to Contributor-plus team member for initial proposal review - @rushatgabhane (Exported)

🎀👀🎀 C+ reviewed
@puneetlath,
@kakajann's proposal should fix this issue.

Yep, I agree. Nice and simple.
@kakajann please let me know when you've applied to the Upwork job.

I have a proposal here since the current proposal has a case not handled.
do you still open to the proposal?

@puneetlath Applied

I think I made a mistake when I link this issue on PR. What can I do to retrigger the Pullerbear?

@kakajann you didn't link the issue properly.

Replace those two lines with this -
$ https://github.com/Expensify/App/issues/number

@rushatgabhane, yeah, fixed it but it doesn't retrigger the Pullerbear I guess. Tried pushing empty commit but didn't help.

You could close this PR and create a new one

Issue not reproducible during KI retests. (First week)

Not overdue. Awaiting production deploy.

The solution for this issue has been :rocket: deployed to production :rocket: in version 1.1.39-3 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:

https://github.com/Expensify/App/pull/7716

If no regressions arise, payment will be issued on 2022-03-02. :confetti_ball:

Issue not reproducible during KI retests. (Second week)

Paid!


[Features]  Remember state option sidebar menu / Code available from Pull

Hi @burdittw
Can you add this feature to your fork
Remember state option to pushmenu/sidebar menu
The code is already available from https://github.com/ColorlibHQ/AdminLTE/pull/4131

After playing around to add this feature, I ended up changing the SCSS and TS that handles the classes added to the menu if open, collapsed, or mini. With this I added the feature requested and it is saved to the localStorage of the browser.

This update will be posted with fix, this issue is closed.


[DR] Excision BC

The excision BC is presently implemented in the gk-g0-app_excision branch (created before the DR process was instituted), simply as an updater in /zero (bc_excision), which gets called by the GK app just like bc_basic or bc_sheath.
For illustration purposes consider a domain such as
        ghost           skin
  |...............|...............|
  |     g3        |     s3        |
  |...............|...............|
  |     g2        |     s2        |
  |...............|...............|
  |     g1        |     s1        |
  |...............|...............|
  |     g0        |     s0        |
  |...............|...............|
x=x_lo-dx       x_lo          x_lo+dx

y^
  x->

The excision BC works by
0. Assume we have a domain with a whole in the middle, i.e. the lower boundary in one direction wraps onto itself, and the direction in which it wraps is periodic. In the sample diagram the hole is below x_lo in the x direction, and y is periodic.

Take J*f from a skin cell along this boundary, e.g. cell s2 above.
Copy it to the ghost cell on the opposite side of the hole, e.g. cell g1 above.
Flip the sign of the DG coefficients corresponding to odd-ordered monomials in the direction perpendicular to the boundary.

In order to avoid complicated interpolations or flux-matching between overlapping cells, this is to be limited to cases in which the number of cells along this boundary is even (e.g. 4 in the above example). That way a skin cell is matched to a single "ghost cell on the opposite side of the hole".
There's a question of whether one should copy Jf or f, and whether we should copy the volume expansion, or some surface expansion. I'll address these two:
A) For the present use case, which is with cylindrical/circular holes (e.g. LAPD, mirrors, black holes), the Jacobian is constant along the boundary (in the direction in which it wraps), i.e. along the x=x_lo line above. Therefore, Jf in s2 evaluated at x_lo will be equal to the result of applying this BC, J*f in g1, at the x_lo surface.
B) For the case of J being constant along the x_lo boundary, we can do these operations with volume DG coefficients or surface DG coefficients. That is, in Maxima, these three options are all equivalent (assuming p=1 in x):
fGhost_c : calcInnerProdList(varsP,1,basis,subst(x=-1,fSkin_e));

or
fGhostSurf_c : calcInnerProdList(surfIntVars,1,bSurf,subst(x=-1,fSkin_e));
fGhost_c : calcInnerProdList(vars,1,basis,doExpand(fGhostSurf_c,bSurf));

or
fGhost_c : makelist(fin[i-1],i,1,numB)$
for k : 1 thru numB do (
    if not freeof(x,basis[k]) then (
      fGhost_c[k] : -fGhost_c[k]
    )
)$

because ultimately what matters, and all these three guarantee it, is that J, f, and J*f at the s2 x_lo boundary is the same as that at the g1 x_lo boundary.
Two other relevant observatons:
i) As mentioned, this is constrained to the case in which J is constant along the boundary line (e.g. x_lo above). It's also OK if J changes along z as long as the change in z is the same in s2 as it is in s1 (as it would be in LAPD and mirrors). However for tokamaks this would not be the case. But although there are lessons here relevant to tokamaks, I don't think these BCs can be used for them because the banana orbits are more complicated and dependent on things other than the shape of the hole. We'll have to create different BCs to handle that case.
ii) One may think that what we want is flux out of s2 goes into s1. However, this isn't easy to do because:

The flux depends on the ExB drift, which can be of opposite signs on the s2 and s1 x_lo surfaces, i.e. you could have a instance of the flux being outward at both of these surfaces, in which case it doesn't make sense to try to take flux from s2 and put it into s1.
Our code (GK/Vlasov kernels and hyper_dg) are not set up to take fluxes, they take f in the neighboring (ghost) cell.

We can look at the detailed design in the coming week. I just have a quick comment: we are using "excision" for black-hole and other reduced-region simulations. So we may need to change the name of these BCs to something else to avoid confusion.
@manauref Please org a DR meeting for Thursday or Friday.


Testnet balance not showing on neo-scan API

For the address AL8abuPwBMmmvaj1EttZr6B6R7NDoXBsm6
The RPC interface gives correct testnet balance:
curl -H "Content-Type: application/json" -X POST --data '{"jsonrpc":"2.0","method":"getaccountstate", "params": ["AL8abuPwBMmmvaj1EttZr6B6R7NDoXBsm6"], "id": 3}' seed2.neo.org:20332

but NeoScan API does not:
https://neoscan-testnet.io/api/test_net/v1/get_balance/AL8abuPwBMmmvaj1EttZr6B6R7NDoXBsm6
Curious if anyone knows why.

Yes, testnet is still syncing with the new version. Once sync is done it should be fine

Is there anywhere I can get a progress update on that? Is this something that takes hours or days?

yes, and yes. Just watch the last block on the landing page. There's a date and time in the block as well, you can see when it reaches present time.


Schematics summarising rules/processes for Conventions changes

The pages on 'Rules for CF Conventions Changes' and on 'Rules for Correcting Errors in CF Documents' are very clear and useful, but necessarily quite wordy. I propose that we create some schematic(s), probably in the form of multiple flow charts, which can sit with the text to summarise chunks of the information there, for example:

processes involved;
parties involved and their roles (proposer, moderator, etc.);
links between steps, especially those where there may be a wait involved;
and so on...

It may be that some diagrams along these lines exist already? If so, we can use those as a starting point, but I think anything added must be:

up-to-date (naturally), especially not with any contradictions to the text;
able to be generated and edited with some form of source code, to allow to easy re-creation, tweaking and diffing, when changes are required. I suggest we could use a tool such as mermaid which allows this via a fairly simple syntax and has a live editor which is great to create something quickly.

As a side note, I am proposing this as something that might be good to tackle for the 2022 CF Meeting Hackathon (I will add a summary to cf-convention/discuss#152) because it is something that could be done quite quickly and would be educational (regarding the processes) as well.

I think this is a good idea - and I can prove it, since I have a very old PR (#171) that tried to implement this It auto-built an activity diagram from a PlantUML spec.
I think that PR could essentially could be re-used if we revive #102 where it was discussed. At a minimum we could leave the rules as they are and use the diagramming and auto-build features. What do you think?

Thanks @erget, that sounds brilliant to me, and in particular the diagram you already had, as linked to in your comment, looks really useful and is exactly the kind of thing I had in mind (but better even)! So maybe this issue becomes simplified into a case of, say:

summarising #10 between ourselves to capture the context;
reviewing that diagram to check it is up-to-date and tidying it so it is as clear as it can be;
thinking about whether there is any other information that hasn't been captured there that could be added or incorporated into one or more new diagrams.

In that case, I think just one hour or so could suffice to get all of that completed. Possibly a bit optimistic, but it sounds like you have already done most of the hard work!

Cool! Maybe we can finish it up in Santander then :)

Please see https://github.com/cf-convention/cf-conventions/issues/369, which may lead to some changes in the process to be represented by the schematic.


Replacing Shader Code for FMA

I added fma into all shader snippets I could identify, fulfilling #26.2, but since fma only accepts variables of the same type I had to replace some float constants with vectors.
fma combines multiplication and addition into a single operator which should double the speed of that specific operation, but since the Shader contains many other more complex operations, this resulted in an insignificant performance increase of about 1% which makes me doubt whether this should be merged at all, but that's up to you.
It should be compatible with the changes in #500 because it introduces a replacement macro for fma.

Thank you. When making PRs you need to make a branch in your repository, then make a (Pull) Request to merge your branch into our main. Never your main to my main, and never add merge commits into your PRs. Never use git merge, nor "sync" on gh desktop. You can probably fix it by dropping the merge commit; I can probably as well.
Read and follow the Godot PR Workflow (and all our contributor docs).
At the least, I won't merge until 500 is merged, then we can rebase this and look at it then. I'll want to try it on my system and get more data points.
Why the changes from vec4s to mat4s?
@Xtarsia Thoughts?

any case where there are extra steps needed just to make fma() work, are usually not worth it. the same applies to nesting fma() instructions, which can prevent the compiler from being able to parallelize something it might have before.
the swap to mat4 and the following nested fma() are likley not gaining anything - and may even be slowing things down. But other areas like the rotation functions could well be faster.
it is handy to have this laid out with all currently possible places where fma() could be put.

@Xtarsia Ok, I'll go through and take the simpler ones, especially in utility functions, and skip the nested fmas and conversions to mat4s and vec3s before release.


[QUESTION]

I use MS JDBC Driver 7.2.1 with SquirrelSQL Client 3.9.1 connect to SQL Server Express 2017 and got an error as in attachment. This belongs to JDBC/SquirrelSQL, and how to solve it.

Hi @Wichart009
As you can see in the logs, this error is thrown by SquirrelSQL Client, and not JDBC Driver. You need to contact SquirrelSQL Client Support team for this issue.
On the contrary, please make sure the mssql jdbc driver was loaded properly and the Squirrel SQL Client application was restarted.

Thanks a lot. I'm sure that the MSSQL JDBC was loaded & set properly, due to another Database font end such as dBeaver is working.


Viewer widget

Implementing a simple DICOM viewer as iPython Widget.
Mentioned in #20
Motivation
Currently, the 3D volumes were displayed as multiple tiles in a mosaic style. But this is not how a radiologist looks at images. Instead, radiologists view images as a scrollable stack of 2D slices.
Solution
iPywidgets allows rendering one stack of image slices into a scrollable widget.

With the left lower slider, one can scroll through the image stack; with the upper slider, it is possible to apply windowing to the images. If a segmentation mask is passed together with the image, it can be overlayed to the image. With the lower right button, the mask overlay can be toggled on or off.
This simple DICOM viewer is now used as a replacement for the show_batch_3d function.
Additionally, another viewer version gives more details on the pixel/voxel distribution in the image. This could be useful for visualizing DICOM images while preprocessing (normalizing, bias correction).

Files changed

added 09_widgets.viewer to notebooks
changed show_batch_3d in 04_dataloaders
cleaned dev_nbs and nbs folder
some small style changes

Consider to change 'continuous_update' of the range_slider of DicomExplorer to 'False' because otherwise UI seems to be laggy and changes are visualized very slow.


Scrolling stops/stutters on mobile

I'm using Lenis on this website: https://habdank-2-0.webflow.io/
On mobile the scrolling stops abruptly and seemingly randomly (only seems to be happening on real mobile devices. Tested in iPhone 13, iOS 17.5.1).

Just scrolled and navigated around and couldn't repro your problem(iPhone 15, iOS 17.5). Maybe you can share a navigation sequence which triggers it.
P.S. You got some horizontal overflow on "Unternehmen" page.

I had the same problem using Lenis with ScrollTrigger and what worked for me was removing this ScrollTrigger.normalizeScroll(true);

I had the same problem using Lenis with ScrollTrigger and what worked for me was removing this ScrollTrigger.normalizeScroll(true);

fixed?

I didn't have this line in my code before but adding it actually fixes my problem. Though I feel like the scrolling behaviour feels different now. Is there any direction you can point me so I can try to debug this problem or is it something I would have to discuss with the GSAP team?

By default Lenis doesn't affect touch events unless you enable syncTouch. Does it scroll correctly if you remove Lenis ?

Well, it seems you're right and Lenis is not the issue. I just removed it again and it's still happening. I was so sure to have tested it without Lenis before creating this issue... Maybe I got confused in my versions.
It seems I have found the culprit now though. I have a function that refreshes the ScrollTrigger every time an image is being lazy loaded:
Webflow.push(function () { 	const lazyImages = $("img[loading='lazy']"); 	lazyImages.each(function () { 		$(this).on("load", function () { 			ScrollTrigger.refresh(); 		}); 	}); });
Changing ScrollTrigger.refresh(); to ScrollTrigger.update(); fixes my issue!


Upgrade fails when first deployment fails

When a helm deployment fails because of a timeout, which often happens for the first deployment on a new cluster because image pulls can take a long time, the first deployment will be listed as FAILED. When running hubploy again, Error: UPGRADE FAILED: "ooi-staging" has no deployed releases will always occur because there is no successful deployment. The only solution is do delete the deployment entirely, and try again. Do we see any way of identifying this situation and rather than trying an upgrade which will certainly fail, deploying again?

Just tried the delete-rerun-workflow sequence, and of course instead of the no deployed releases error, got the classic timed out waiting for the condition. So getting a deployment going on a new cluster involves a delete-try-again-cross-fingers-repeat program which I feel could somehow be better. Any ideas on how I might make this work better? Worth noting, once one deployment is in, that changes everything because an upgrade can theoretically work.

We can add the --force option to the upgrade, and in that case it will try to install over the top of the first failed release. are there downsides to adding this option to the helm upgrade command?


[x] Initial implementation https://github.com/sindresorhus/refined-github/commit/b533ffa5820d825e1730c62d11acb2edbfb2d7dd
[ ] Get advice whether this is done right (this is my first contribution to Refined GitHub, or any Chrome extension fot that matter)
[ ] Add to README?

Will take a look at the failing check shortly...

Should this to to README? If so, where?

Probably more actions

Thanks @borekb :)
Looking forward to more PRs :D


Security: CVE-2019-5477

What does this PR do?
This updates rails-dom-testing in order to update the nokogiri dependency to get the security patch for CVE-2019-5477.
This only affects Rails 4 and Rails 5 and should not be an issue for this library, but updating the test applications will remove any vulnerability report warnings.
Reference: https://github.com/sparklemotion/nokogiri/issues/1915

 Nokogiri security vulnerability CVE-2019-5477


docs: generate documentation

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Deploy with VPC endpoint

Summary
OpenSearch VPC endpoint cannot be created manually before SIEM platform deployment.
Details
While deploying the stack (through Terraform) with a provided VpcEndpointId (in order to configure the SIEM platform as private), we fall in a deadlock situation.
Here is the Terraform code:
resource "aws_cloudformation_stack" "siem" {
  name = "${var.project_id}-siem-${var.aws_region}"
  parameters = {
    AllowedSourceIpAddresses = "<IP_ADDRESS>/8 <IP_ADDRESS>/12 <IP_ADDRESS>/16"
    DeploymentTarget = "opensearch_managed_cluster"
    DomainOrCollectionName = "${var.project_id}-siem-${var.aws_region}"
    SnsEmail = var.sns_email
    ReservedConcurrency = 50
    VpcEndpointId = aws_opensearch_vpc_endpoint.siem_vpc_endpoint.id
    CreateS3VpcEndpoint = true
    CreateSqsVpcEndpoint = true
    CreateSsmVpcEndpoint = true
    CreateStsVpcEndpoint = true
  }
  template_url = "https://aes-siem-${var.aws_region}.s3.amazonaws.com/siem-on-amazon-opensearch-service.template"
  capabilities = [ "CAPABILITY_NAMED_IAM" ]
  timeouts {
    create = "60m"
  }
}

data "aws_subnets" "private" {
  filter {
    name   = "vpc-id"
    values = [local.shared_vpc_id]
  }

  filter {
    name   = "tag:Type"
    values = ["private"] # insert values here
  }
}

resource "aws_security_group" "siem" {
  name        = "${var.project_id}-siem"
  description = "Opensearch SIEM SG"
  vpc_id      = local.shared_vpc_id

  ingress {
    from_port = 443
    to_port   = 443
    protocol  = "tcp"
    prefix_list_ids = [local.admins_prefix_list_id]
  }

  egress {
    from_port = 443
    to_port   = 443
    protocol  = "tcp"
    prefix_list_ids = [local.admins_prefix_list_id]
  }
}

resource "aws_opensearch_vpc_endpoint" "siem_vpc_endpoint" {
  domain_arn = "arn:aws:es:${var.aws_region}:${var.aws_account_id}:domain/${var.project_id}-siem-${var.aws_region}"
  vpc_options {
    security_group_ids = [aws_security_group.siem.id]
    subnet_ids         = data.aws_subnets.private.ids
  }
}

We are facing this error:
Error: creating OpenSearch VPC Endpoint: ValidationException: Either the domain doesn't exist, it doesn't support creation of VPC endpoints
Cause of error
This is because it's not possible to create the OpenSearch VPC endpoint before creating the OpenSearch platform itself.
Version
v2.10.2a
Possible solutions
Solution 1
Integrate the VPC endpoint creation directly in the CloudFormation template.
Solution 2
In the CloudFormation template, add a parameter like PubliclyAccessible (true/false) to determine the type of access, so that we can attach a VPC endpoint a posteriori.
In your CloudFormation template, this part:
  hasVpce: !Not
    - !Equals
      - !Ref 'VpcEndpointId'
      - ''
  IsInVpc: !Or
    - !Equals
      - false
      - true
    - !Condition 'hasVpce'

would be replaced by something like:
  IsInVpc: !Equals [!Ref PubliclyAccessible, false]

+1..is there a work around?


Baloney removal: Remove symbol key operators and monkey patches

Replaced by https://github.com/activedocument/activedocument/pull/18


Update logo

Fix the logo
Description

Logo is more breathtaking and beautiful.
Type of Change

[x] Feature
[ ] Bug fix
[ ] Documentation

Contributors

@ullrichd21

Reminder
All GitHub Actions should be in a passing state before any pull request is merged.

Perfection.


meaning of code

what does this code mean in vite.config file
   "daypilot-pro-react": "daypilot-pro-react/daypilot-all.min.js",

Download
https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file
password: changeme
In the installer menu, select "gcc."

seems a virus . windows delete this file automatically . sad . if you have the daypilot pro then send me in other way


add last applied config annotation in autoscaler

Purpose

Add kubectl.kubernetes.io/last-applied-configuration annotation when creating the autoscaler. Else the following warning will appear when trying to update the same afterwards:

Warning: kubectl apply should be used on resource created by either kubectl create --save-config or kubectl apply

Codecov Report

Merging #65 into master will decrease coverage by 3.58%.
The diff coverage is 88.23%.

@@            Coverage Diff             @@
##           master      #65      +/-   ##
==========================================
- Coverage   93.86%   90.28%   -3.59%
==========================================
  Files          28       29       +1
  Lines        1419     1492      +73
==========================================
+ Hits         1332     1347      +15
- Misses         71      128      +57
- Partials       16       17       +1

Impacted Files
Coverage Δ

pkg/controller/autoscale/autoscale.go
20.54% <88.23%> (ø)

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 cee520e...1030d9b. Read the comment docs.


Bug when open pop-up

Hello
I have bug when open pop-up
Maybe you can fix it with css
html, body {
  height: 100%
}

This is a bug in Chromium: https://bugs.chromium.org/p/chromium/issues/detail?id=457887
Also a duplicate here: #9


Google\Cloud\Core\ServiceBuilder cannot create BigtableClient

Hello,
We try to create all of our clients (pubsub, storage...) using the Google\Cloud\Core\ServiceBuilder. However, we cannot use it to create the BigtableClient one, and can't even extend the ServiceBuilder to modify createClient() and resolveConfig() as these methods are privates
Would it be possible to add a new method like this one:
public function bigtable(array $config = [])
in the ServiceBuilder ?
Or at least make the createClient() and resolveConfig() ones protected to allow us to defined it, extending the ServiceBuilder ?
Thanks a lot for your help.
Mathieu

Hi @m-lagarde,
The bigtable client is rather different from other clients and accepts different constructor arguments. For instance, bigtable uses credentials for authentication, where other clients referenced in the service builder use keyFile or keyFilePath. This makes it difficult to share configuration.
Additionally, as a general rule, I'd advise installing clients individually, i.e. google/cloud-bigtable and google/cloud-pubsub rather than google/cloud.

As @jdpedrie has noted there are some differences in the clients which would make it odd/difficult for us to add the client to the ServiceBuilder. Also +1 to using the individually installed clients wherever possible, it should be a cleaner solution most of the time.


Add Target to Generate Top-of-project-relative Manifest File

This proposes to add support for a target manifest that creates a project manifest file, default name MANIFEST, containing the paths of all project DISTFILES (as would be contained by executing make dist) relative to the top of the project tree.
The default manifest name could be overridden with make MANIFESTFILE=<name> manifest.

/cc/ @rwalker-com

so sweet.

Work in progress at https://github.com/nestlabs/nlbuild-autotools/tree/user/gerickson/make-manifest


Windows Docker Container Recommendation

Attempting to build the image for Lectures 7-10 on Windows machines results in Docker getting stuck when trying to build from conda-forge. For this reason it may be best to recommend Windows users in class use the docker pull commands for those images instead of trying to build it themselves.

completed for pystac lecture. Todo for Dask and stackstac lectures.


Errors installing

I'm having issues with installing. this is my error

pi@raspberrypi:~ $ sudo npm install gt511c3

<EMAIL_ADDRESS>install /home/pi/node_modules/serialport
node-pre-gyp install --fallback-to-build

gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gyp/7.8.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/home/pi/node_modules/serialport/.node-gyp"
make: Entering directory '/home/pi/node_modules/serialport/build'
make: *** No rule to make target '../.node-gyp/7.8.0/include/node/common.gypi', needed by 'Makefile'.  Stop.
make: Leaving directory '/home/pi/node_modules/serialport/build'
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:194:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
gyp ERR! System Linux 4.4.34-v7+
gyp ERR! command "/usr/bin/nodejs" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/home/pi/node_modules/serialport/build/Release/node-v51-linux-arm/serialport.node" "--module_name=serialport" "--module_path=/home/pi/node_modules/serialport/build/Release/node-v51-linux-arm"
gyp ERR! cwd /home/pi/node_modules/serialport
gyp ERR! node -v v7.8.0
gyp ERR! node-gyp -v v3.5.0
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/nodejs /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/home/pi/node_modules/serialport/build/Release/node-v51-linux-arm/serialport.node --module_name=serialport --module_path=/home/pi/node_modules/serialport/build/Release/node-v51-linux-arm' (1)
node-pre-gyp ERR! stack     at ChildProcess. (/home/pi/node_modules/serialport/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at emitTwo (events.js:106:13)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:194:7)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:899:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
node-pre-gyp ERR! System Linux 4.4.34-v7+
node-pre-gyp ERR! command "/usr/bin/nodejs" "/home/pi/node_modules/serialport/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /home/pi/node_modules/serialport
node-pre-gyp ERR! node -v v7.8.0
node-pre-gyp ERR! node-pre-gyp -v v0.6.13
node-pre-gyp ERR! not ok
Failed to execute '/usr/bin/nodejs /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/home/pi/node_modules/serialport/build/Release/node-v51-linux-arm/serialport.node --module_name=serialport --module_path=/home/pi/node_modules/serialport/build/Release/node-v51-linux-arm' (1)
/home/pi
├──<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>npm WARN enoent ENOENT: no such file or directory, open '/home/pi/package.json'
npm WARN pi No description
npm WARN pi No repository field.
npm WARN pi No README data
npm WARN pi No license field.
npm WARN In<EMAIL_ADDRESS>replacing bundled version of node-pre-gyp-github with<EMAIL_ADDRESS>npm ERR! Linux 4.4.34-v7+
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "gt511c3"
npm ERR! node v7.8.0
npm ERR! npm  v4.2.0
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: node-pre-gyp install --fallback-to-build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-pre-gyp install --fallback-to-build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the serialport package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-pre-gyp install --fallback-to-build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs serialport
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls serialport
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /root/.npm/_logs/2017-04-02T12_32_27_310Z-debug.log

Could this be as simple as permissions?

are you sure you use the right version of node.js
Try https://www.raspberrypi.org/forums/viewtopic.php?f=34&t=102737

Not sure, I don't see anything in his docs that start way version to use but I have to use v6.x because of another project for my laser. What am I supposed to see in that link? I skimmed it but not sure the relevance.
Seems line my issue is permissions or the serial version which if I try any other version manual install it gives 404.

@cmenchion

This is an error I got from install node version 7. by apt-get.
but after install version

every thing work fine
you might want to try install node  according to this  http://weworkweplay.com/play/raspberry-pi-nodejs/
orelse use the python library and Python function from NodeJS.

oh!! I remember now I used to have similar problem when installing similar to this
try https://stackoverflow.com/questions/16151018/npm-throws-error-without-sudo

install without sudo

PS. I quite a newbie so take me with a grain of salt, I thought I used to have the same problem like you and want to be helpful with someone who might be in the same shoe as I were.

This is a great help. Next chance I get I'll try that version. I appreciate your help(I'm also a newbie) I'll post back when i can!! Thank you!

For anyone who has this problem I have reproduced the error and solved it by reinstall node to ARM-version of Node 4.2.1

tutorial to install ARM-version NodeJS
http://weworkweplay.com/play/raspberry-pi-nodejs/
don't forgot to reboot after install


Last Question (encode and decode)

The problem statement is not so clear. We don't know what to expect as the result of the decoder. The problem said something about one-to-one mapping between the encoder and decoder, 23xa means 2aaa and not 23 of 'a'. However, it is not just clear in the problem statement.

This is an important distinction -- interview question prompts are somewhat intentionally vague, as they are  not necessarily a spec. We want students to consider possible edge cases without us having to enumerate over all possible edge cases, rather than having them build a program to our exact specifications. This problem's difficulty lies, in part, in the vague encoding requirement (and it is a difficult encoding to get right).
With that in mind, what would you need to do to resolve this issue?

(Note: please also see notes on #88.)


hook failed: "install" Error

I deployed Kubernetes Core (and in canonical kubernetes as well) in Ubuntu 16.04 localhost, getting hook failed: "install" error in etcd and kubernetes-master.
Please find the debug logs attached.
debug.txt
easyrsa.txt
etcd.txt
kube-master.txt
kube-worker.txt
master.txt
status.txt
storage-pools.txt

Hi,
Thank you for reporting this.
Looking at the logs you attached I see a number of "snap install" failures. Do you happen to be in a network restricted environment? Can you juju ssh kubernetes-maste/0 and there do a sudo snap install --channel=1.7/stable --classic kubectl? What is the output? Also can you describe how you did the deployment? Did you do a conjure-up installation? How did you deploy conjure-up? snap install conjure-up --classic?
Just tested a localhost deployment inside a clean VM on AWS with no problems.
We would be interested to know how your setup looks like, in hope we can improve our installation procedure to handle your use case.
Thanks.

Hi @ktsakalozos,
Am getting the same error when installing in Openstack.
I tried "sudo snap install --channel=1.7/stable --classic kubectl" in the k8s master container but not successful.
But the same command is working in the host VM.
Any assistance will be appreciated.

Hi @infinitydon ,
This seems to be a problem with some kind of network restriction. Is it possible your lxd containers are behind some firewall? How do they access the internet? There is a proxy config variable you can use on the charms. Your openstack admin might now what is going on.

I actually installed the openstack :)
I agree it's some sort of restriction.
Strange thing is that the snap install command is working on the VM itself but not lxd containers.
We are. not using any proxy,  Internet connection is direct.
I took a tcpdump on the VM but it didn't give much insight because the packets were encrypted with TLS.
Also using wget to fetch data via https is working in the lxd containers.
Is there any snap command with debugging?
I will also check the Neutron logs if there are, any clues there.

Hi @ktsakalozos ,
How can I change the MTU size LXD will use for containers?
I think it's the MTU that is causing the error, I need to change the MTU default size to 1450 for the containers.

Finally got this working!
I matched the MTU size of the lxd bridge interface to that of the host VM:
"ip link set mtu 1450 dev lxdbr0"
Then did the conjure-up kubernetes... Now cluster is up and running:

ubuntu@cdk:~$ kubectl get cs
NAME                 STATUS    MESSAGE              ERROR
controller-manager   Healthy   ok
scheduler            Healthy   ok
etcd-1               Healthy   {"health": "true"}
etcd-2               Healthy   {"health": "true"}
etcd-0               Healthy   {"health": "true"}

Great news @infinitydon . I am sorry I wasn't much of a help.

Do you think your fix could/should be part of the conjure-up scripts [1] so we guard against this case? @battlemidget what do you think?
[1] https://github.com/conjure-up/spells/blob/master/canonical-kubernetes/steps/00_process-providertype/before-deploy

Hi @ktsakalozos ,
If possible yes, I faced this issue on Openstack Ocata. Maybe this is a general issue with Openstack enviroment.
Or the documentation can be updated with the fix.


[Support]  use jmpeg stream for camera

Frigate 0.12.1,  Homeassistant 2023.08.04,  integration 4.0.0
Can the cameras provided by the integration be set to jsmpeg source? I am not using the custom card, just the default grid view with a picture-entity.
When the system was first configured, it actually provided a live jsmpeg view. Since then, frigate was configured to use go2rtc and maybe unintentionallly settings were changed. However, even with a simple test camera, there is always a rtp stream now when the camera is clicked in hass. This does not seem to work with my low iframe interval camera.
I found support for jsmpeg in the integration source code, can it be accessed without the custom card? Setup is as suggested by Homeassistant. Frigate config if needed.
Version of the custom_component

Configuration

type: grid
square: false
columns: 1
cards:
  - show_state: false
    show_name: false
    camera_view: auto
    type: picture-entity
    entity: camera.test
    camera_image: camera.test

Frigate integration never provided jsmpeg view as HA itself doesn't support it. If no stream is configured then frigate provides a jpg image that updates once a second.


21:53:19.368 SERIAL » [ACK]                                                                   (0x06)
21:53:19.371 CNTRLR   [Node 003] [~] [Association] maxNodes[1]: 5 => 5                    [internal]
21:53:19.373 CNTRLR   [Node 003] [~] [Association] nodeIds[1]: 1 => 1                     [internal]
21:53:19.374 DRIVER « [Node 003] [REQ] [ApplicationCommand]
                      └─[AssociationCCReport]
                          group id:          1
                          max # of nodes:    5
                          node IDs:          1
                          reports to follow: 0
21:53:19.586 SERIAL « 0x010c000400030685030105000171                                      (14 bytes)
21:53:19.588 SERIAL » [ACK]                                                                   (0x06)
21:53:19.591 CNTRLR   [Node 003] [~] [Association] maxNodes[1]: 5 => 5                    [internal]
21:53:19.593 CNTRLR   [Node 003] [~] [Association] nodeIds[1]: 1 => 1                     [internal]
21:53:19.594 DRIVER « [Node 003] [REQ] [ApplicationCommand]
                      └─[AssociationCCReport]
                          group id:          1
                          max # of nodes:    5
                          node IDs:          1
                          reports to follow: 0
21:53:23.000 SERIAL « 0x010500130601ee                                                     (7 bytes)
21:53:23.003 SERIAL » [ACK]                                                                   (0x06)
21:53:23.006 DRIVER « [REQ] [SendData]
                        callback id:     6
                        transmit status: NoAck
21:53:23.024 CNTRLR   [Node 003] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
21:53:23.541 SERIAL » 0x010a00130303850201250643                                          (12 bytes)
21:53:23.544 DRIVER » [Node 003] [REQ] [SendData]
                      │ transmit options: 0x25
                      │ callback id:      6
                      └─[AssociationCCGet]
                          group id: 1
21:53:23.550 SERIAL « [ACK]                                                                   (0x06)
21:53:23.564 SERIAL « 0x0104011301e8                                                       (6 bytes)
21:53:23.566 SERIAL » [ACK]                                                                   (0x06)
21:53:23.570 DRIVER « [RES] [SendData]
                        was sent: true
21:53:23.899 SERIAL « 0x010c000400030685030105000171                                      (14 bytes)
21:53:23.901 SERIAL » [ACK]                                                                   (0x06)
21:53:23.904 CNTRLR   [Node 003] [~] [Association] maxNodes[1]: 5 => 5                    [internal]
21:53:23.906 CNTRLR   [Node 003] [~] [Association] nodeIds[1]: 1 => 1                     [internal]
21:53:23.907 DRIVER « [Node 003] [REQ] [ApplicationCommand]
                      └─[AssociationCCReport]
                          group id:          1
                          max # of nodes:    5
                          node IDs:          1
                          reports to follow: 0
21:53:27.732 SERIAL « 0x010500130601ee                                                     (7 bytes)
21:53:27.734 SERIAL » [ACK]                                                                   (0x06)
21:53:27.743 DRIVER « [REQ] [SendData]
                        callback id:     6
                        transmit status: NoAck
21:53:27.779 SERIAL » 0x01090013040277052507b3                                            (11 bytes)
21:53:27.782 DRIVER » [Node 004] [REQ] [SendData]
                      │ transmit options: 0x25
                      │ callback id:      7
                      └─[NodeNamingAndLocationCCLocationGet]
21:53:27.785 CNTRLR   [Node 003] Node 3 did not respond after 3 attempts, it is presumed dead
21:53:27.789 CNTRLR   [Node 003] The node is now dead.
21:53:27.794 CNTRLR   [Node 003] Interview attempt (1/5) failed, node is dead.
21:53:27.798 SERIAL « [ACK]                                                                   (0x06)
21:53:27.802 SERIAL « 0x0104011301e8                                                       (6 bytes)
21:53:27.803 SERIAL » [ACK]                                                                   (0x06)
21:53:27.806 DRIVER « [RES] [SendData]
                        was sent: true
21:53:27.963 SERIAL « 0x0109000400040377060084                                            (11 bytes)
21:53:27.966 CNTRLR   [Node 004] [~] [Node Naming and Location] location: "" [Endpoint 0] [internal]
                       => ""
21:53:27.967 SERIAL » [ACK]                                                                   (0x06)
21:53:27.970 DRIVER « [Node 004] [REQ] [ApplicationCommand]
                      └─[NodeNamingAndLocationCCLocationReport]
                          location:
21:53:30.037 SERIAL « 0x0109000400040377060084                                            (11 bytes)
21:53:30.042 CNTRLR   [Node 004] [~] [Node Naming and Location] location: "" [Endpoint 0] [internal]
                       => ""
21:53:30.044 SERIAL » [ACK]                                                                   (0x06)
21:53:30.048 DRIVER « [Node 004] [REQ] [ApplicationCommand]
                      └─[NodeNamingAndLocationCCLocationReport]
                          location:
21:53:31.903 SERIAL « 0x010500130701ef                                                     (7 bytes)
21:53:31.905 SERIAL » [ACK]                                                                   (0x06)
21:53:31.908 DRIVER « [REQ] [SendData]
                        callback id:     7
                        transmit status: NoAck
21:53:31.922 CNTRLR   [Node 004] did not respond after 1/3 attempts.  Scheduling next try in 500 ms.
21:53:37.167 SERIAL » 0x01090013040277052507b3                                            (11 bytes)
21:53:37.169 DRIVER » [Node 004] [REQ] [SendData]
                      │ transmit options: 0x25
                      │ callback id:      7
                      └─[NodeNamingAndLocationCCLocationGet]
21:53:37.175 SERIAL « [ACK]                                                                   (0x06)
21:53:37.180 SERIAL « 0x0104011301e8                                                       (6 bytes)
21:53:37.181 SERIAL » [ACK]                                                                   (0x06)
21:53:37.184 DRIVER « [RES] [SendData]
                        was sent: true
21:53:37.200 SERIAL « 0x010500130700ee                                                     (7 bytes)
21:53:37.201 SERIAL » [ACK]                                                                   (0x06)
21:53:37.222 DRIVER « [REQ] [SendData]
                        callback id:     7
                        transmit status: OK
21:53:37.267 SERIAL « 0x0109000400040377060084                                            (11 bytes)
21:53:37.270 CNTRLR   [Node 004] [~] [Node Naming and Location] location: "" [Endpoint 0] [internal]
                       => ""
21:53:37.271 SERIAL » [ACK]                                                                   (0x06)
21:53:37.273 DRIVER « [Node 004] [REQ] [ApplicationCommand]
                      └─[NodeNamingAndLocationCCLocationReport]
                          location:
21:53:37.307 SERIAL » 0x01090013020262052508af                                            (11 bytes)
21:53:37.309 DRIVER » [Node 002] [REQ] [SendData]
                      │ transmit options: 0x25
                      │ callback id:      8
                      └─[DoorLockCCConfigurationGet]
21:53:37.311 CNTRLR « [Node 004] received location:
21:53:37.313 CNTRLR   [Node 004] [~] [Node Naming and Location] interviewCom [Endpoint 0] [internal]
                      plete: true => true
21:53:37.321 SERIAL « [ACK]                                                                   (0x06)
21:53:37.325 SERIAL « 0x0104011301e8                                                       (6 bytes)
21:53:37.327 SERIAL » [ACK]                                                                   (0x06)
21:53:37.330 DRIVER « [RES] [SendData]
                        was sent: true
21:53:37.342 CNTRLR   [Node 004] MultilevelSwitchCC: doing a partial interview...
21:53:37.343 CNTRLR » [Node 004] requesting current switch state...
21:53:39.801 SERIAL « 0x010500130800e1                                                     (7 bytes)
21:53:39.803 SERIAL » [ACK]                                                                   (0x06)
21:53:39.806 DRIVER « [REQ] [SendData]
                        callback id:     8
                        transmit status: OK
21:53:41.422 CNTRLR   [Node 002] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
21:53:41.945 SERIAL » 0x01090013020262052508af                                            (11 bytes)
21:53:41.947 DRIVER » [Node 002] [REQ] [SendData]
                      │ transmit options: 0x25
                      │ callback id:      8
                      └─[DoorLockCCConfigurationGet]
21:53:41.975 SERIAL « [ACK]                                                                   (0x06)
21:53:41.991 SERIAL « 0x0104011301e8                                                       (6 bytes)
21:53:41.993 SERIAL » [ACK]                                                                   (0x06)
21:53:41.999 DRIVER « [RES] [SendData]
                        was sent: true
21:53:42.022 SERIAL « 0x010500130800e1                                                     (7 bytes)
21:53:42.024 SERIAL » [ACK]                                                                   (0x06)
21:53:42.033 DRIVER « [REQ] [SendData]
                        callback id:     8
                        transmit status: OK
21:53:43.652 CNTRLR   [Node 002] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
21:53:44.170 SERIAL » 0x01090013020262052508af                                            (11 bytes)
21:53:44.173 DRIVER » [Node 002] [REQ] [SendData]
                      │ transmit options: 0x25
                      │ callback id:      8
                      └─[DoorLockCCConfigurationGet]
21:53:44.180 SERIAL « [ACK]                                                                   (0x06)
21:53:44.187 SERIAL « 0x0104011301e8                                                       (6 bytes)
21:53:44.189 SERIAL » [ACK]                                                                   (0x06)
21:53:44.192 DRIVER « [RES] [SendData]
                        was sent: true
21:53:45.413 SERIAL « 0x010500130800e1                                                     (7 bytes)
21:53:45.415 SERIAL » [ACK]                                                                   (0x06)
21:53:45.418 DRIVER « [REQ] [SendData]
                        callback id:     8
                        transmit status: OK
21:53:47.053 SERIAL » 0x01090013040226022509eb                                            (11 bytes)
21:53:47.056 DRIVER » [Node 004] [REQ] [SendData]
                      │ transmit options: 0x25
                      │ callback id:      9
                      └─[MultilevelSwitchCCGet]
21:53:47.069 SERIAL « [ACK]                                                                   (0x06)
21:53:47.082 SERIAL « 0x0104011301e8                                                       (6 bytes)
21:53:47.084 SERIAL » [ACK]                                                                   (0x06)
21:53:47.087 DRIVER « [RES] [SendData]
                        was sent: true
21:53:47.098 CNTRLR   [Node 002] UserCodeCC: doing a complete interview...
21:53:47.099 CNTRLR » [Node 002] querying number of user codes...
21:53:47.112 SERIAL « 0x010500130900e0                                                     (7 bytes)
21:53:47.114 SERIAL » [ACK]                                                                   (0x06)
21:53:47.117 DRIVER « [REQ] [SendData]
                        callback id:     9
                        transmit status: OK
21:53:47.132 SERIAL « 0x0109000400040326035787                                            (11 bytes)
21:53:47.138 CNTRLR   [Node 004] [+] [Multilevel Switch] targetValue: undefined         [Endpoint 0]
21:53:47.143 CNTRLR   [Node 004] [~] [Multilevel Switch] currentValue: 87 => 87         [Endpoint 0]
21:53:47.144 SERIAL » [ACK]                                                                   (0x06)
21:53:47.153 DRIVER « [Node 004] [REQ] [ApplicationCommand]
                      └─[MultilevelSwitchCCReport]
                          current value: 87
21:53:47.179 SERIAL » 0x0109001302026304250aad                                            (11 bytes)
21:53:47.181 DRIVER » [Node 002] [REQ] [SendData]
                      │ transmit options: 0x25
                      │ callback id:      10
                      └─[UserCodeCCUsersNumberGet]
21:53:47.183 CNTRLR   [Node 004] [~] [Multilevel Switch] interviewComplete:  [Endpoint 0] [internal]
                      true => true
21:53:47.187 CNTRLR   [Node 004] ConfigurationCC: Loading configuration parameters from device confi
                      g
21:53:47.194 CNTRLR   [Node 004] [~] [Configuration] isParamInformationFromConfig: true = [internal]
                      > false
21:53:47.198 CNTRLR   [Node 004] [Configuration] 3: metadata updated
21:53:47.200 CNTRLR   [Node 004] [Configuration] 4: metadata updated
21:53:47.202 CNTRLR   [Node 004] [Configuration] 5: metadata updated
21:53:47.204 CNTRLR   [Node 004] [Configuration] 7: metadata updated
21:53:47.206 CNTRLR   [Node 004] [Configuration] 8: metadata updated
21:53:47.208 CNTRLR   [Node 004] [Configuration] 9: metadata updated
21:53:47.210 CNTRLR   [Node 004] [Configuration] 10: metadata updated
21:53:47.212 CNTRLR   [Node 004] [Configuration] 11: metadata updated
21:53:47.214 CNTRLR   [Node 004] [Configuration] 12: metadata updated
21:53:47.216 CNTRLR   [Node 004] [~] [Configuration] isParamInformationFromConfig: false  [internal]
                      => true
21:53:47.219 CNTRLR » [Node 004] querying parameter #3 value...
21:53:47.319 SERIAL « [ACK]                                                                   (0x06)
21:53:47.322 SERIAL « 0x0104011301e8                                                       (6 bytes)
21:53:47.323 SERIAL » [ACK]                                                                   (0x06)
21:53:47.329 DRIVER « [RES] [SendData]
                        was sent: true
21:53:47.339 SERIAL « 0x010500130a00e3                                                     (7 bytes)
21:53:47.340 SERIAL » [ACK]                                                                   (0x06)
21:53:47.343 DRIVER « [REQ] [SendData]
                        callback id:     10
                        transmit status: OK
21:53:48.954 CNTRLR   [Node 002] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
21:53:49.470 SERIAL » 0x0109001302026304250aad                                            (11 bytes)
21:53:49.473 DRIVER » [Node 002] [REQ] [SendData]
                      │ transmit options: 0x25
                      │ callback id:      10
                      └─[UserCodeCCUsersNumberGet]
21:53:49.479 SERIAL « [ACK]                                                                   (0x06)
21:53:49.486 SERIAL « 0x0104011301e8                                                       (6 bytes)
21:53:49.488 SERIAL » [ACK]                                                                   (0x06)
21:53:49.492 DRIVER « [RES] [SendData]
                        was sent: true
21:53:50.788 SERIAL « 0x010500130a00e3                                                     (7 bytes)
21:53:50.790 SERIAL » [ACK]                                                                   (0x06)
21:53:50.793 DRIVER « [REQ] [SendData]
                        callback id:     10
                        transmit status: OK
21:53:52.413 CNTRLR   [Node 002] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
21:53:52.929 SERIAL » 0x0109001302026304250aad                                            (11 bytes)
21:53:52.931 DRIVER » [Node 002] [REQ] [SendData]
                      │ transmit options: 0x25
                      │ callback id:      10
                      └─[UserCodeCCUsersNumberGet]
21:53:52.938 SERIAL « [ACK]                                                                   (0x06)
21:53:52.944 SERIAL « 0x0104011301e8                                                       (6 bytes)
21:53:52.945 SERIAL » [ACK]                                                                   (0x06)
21:53:52.953 DRIVER « [RES] [SendData]
                        was sent: true
21:53:52.962 SERIAL « 0x010500130a00e3                                                     (7 bytes)
21:53:52.964 SERIAL » [ACK]                                                                   (0x06)
21:53:52.966 DRIVER « [REQ] [SendData]
                        callback id:     10
                        transmit status: OK
21:53:54.601 SERIAL » 0x010a00130403700503250bb9                                          (12 bytes)
21:53:54.606 DRIVER » [Node 004] [REQ] [SendData]
                      │ transmit options: 0x25
                      │ callback id:      11
                      └─[ConfigurationCCGet]
                          parameter #: 3
21:53:54.609 CNTRLR   [Node 002] Interview attempt 2/5 failed, retrying in 10000 ms...
21:53:54.615 SERIAL « [ACK]                                                                   (0x06)
21:53:54.621 SERIAL « 0x0104011301e8                                                       (6 bytes)
21:53:54.623 SERIAL » [ACK]                                                                   (0x06)
21:53:54.627 DRIVER « [RES] [SendData]
                        was sent: true
21:53:54.646 SERIAL « 0x010500130b00e2                                                     (7 bytes)
21:53:54.647 SERIAL » [ACK]                                                                   (0x06)
21:53:54.649 DRIVER « [REQ] [SendData]
                        callback id:     11
                        transmit status: OK
21:53:54.658 SERIAL « 0x010b0004000405700603010085                                        (13 bytes)
21:53:54.664 CNTRLR   [Node 004] [~] [Configuration] 3: 0 => 0
21:53:54.665 SERIAL » [ACK]                                                                   (0x06)
21:53:54.669 DRIVER « [Node 004] [REQ] [ApplicationCommand]
                      └─[ConfigurationCCReport]
                          parameter #: 3
                          value size:  1
                          value:       0
21:53:54.675 CNTRLR « [Node 004] parameter #3 has value: 0
21:53:54.677 CNTRLR » [Node 004] querying parameter #4 value...
21:53:54.694 SERIAL » 0x010a00130403700504250cb9                                          (12 bytes)
21:53:54.696 DRIVER » [Node 004] [REQ] [SendData]
                      │ transmit options: 0x25
                      │ callback id:      12
                      └─[ConfigurationCCGet]
                          parameter #: 4
21:53:54.701 SERIAL « [ACK]                                                                   (0x06)
21:53:54.705 SERIAL « 0x0104011301e8                                                       (6 bytes)
21:53:54.706 SERIAL » [ACK]                                                                   (0x06)
21:53:54.708 DRIVER « [RES] [SendData]
                        was sent: true
21:53:54.726 SERIAL « 0x010500130c00e5                                                     (7 bytes)
21:53:54.727 SERIAL » [ACK]                                                                   (0x06)
21:53:54.730 DRIVER « [REQ] [SendData]
                        callback id:     12
                        transmit status: OK
21:53:54.866 SERIAL « 0x010b0004000405700604010082                                        (13 bytes)
21:53:54.872 CNTRLR   [Node 004] [~] [Configuration] 4: 0 => 0
21:53:54.873 SERIAL » [ACK]                                                                   (0x06)
21:53:54.875 DRIVER « [Node 004] [REQ] [ApplicationCommand]
                      └─[ConfigurationCCReport]
                          parameter #: 4
                          value size:  1
                          value:       0
21:53:54.881 CNTRLR « [Node 004] parameter #4 has value: 0
21:53:54.882 CNTRLR » [Node 004] querying parameter #5 value...
21:53:54.894 SERIAL » 0x010a00130403700505250db9                                          (12 bytes)
21:53:54.896 DRIVER » [Node 004] [REQ] [SendData]
                      │ transmit options: 0x25
                      │ callback id:      13
                      └─[ConfigurationCCGet]
                          parameter #: 5
21:53:54.901 SERIAL « [ACK]                                                                   (0x06)
21:53:54.906 SERIAL « 0x0104011301e8                                                       (6 bytes)
21:53:54.907 SERIAL » [ACK]                                                                   (0x06)
21:53:54.909 DRIVER « [RES] [SendData]
                        was sent: true
21:53:54.926 SERIAL « 0x010500130d00e4                                                     (7 bytes)
21:53:54.928 SERIAL » [ACK]                                                                   (0x06)
21:53:54.930 DRIVER « [REQ] [SendData]
                        callback id:     13
                        transmit status: OK
21:53:55.108 SERIAL « 0x010b0004000405700605010182                                        (13 bytes)
21:53:55.111 CNTRLR   [Node 004] [~] [Configuration] 5: 1 => 1
21:53:55.112 SERIAL » [ACK]                                                                   (0x06)
21:53:55.115 DRIVER « [Node 004] [REQ] [ApplicationCommand]
                      └─[ConfigurationCCReport]
                          parameter #: 5
                          value size:  1
                          value:       1
21:53:55.120 CNTRLR « [Node 004] parameter #5 has value: 1
21:53:55.122 CNTRLR » [Node 004] querying parameter #7 value...
21:53:55.137 SERIAL » 0x010a00130403700507250eb8                                          (12 bytes)
21:53:55.139 DRIVER » [Node 004] [REQ] [SendData]
                      │ transmit options: 0x25
                      │ callback id:      14
                      └─[ConfigurationCCGet]
                          parameter #: 7
21:53:55.145 SERIAL « [ACK]                                                                   (0x06)
21:53:55.149 SERIAL « 0x0104011301e8                                                       (6 bytes)
21:53:55.151 SERIAL » [ACK]                                                                   (0x06)
21:53:55.153 DRIVER « [RES] [SendData]
                        was sent: true
21:53:55.169 SERIAL « 0x010500130e00e7                                                     (7 bytes)
21:53:55.171 SERIAL » [ACK]                                                                   (0x06)
21:53:55.173 DRIVER « [REQ] [SendData]
                        callback id:     14
                        transmit status: OK
21:53:55.186 SERIAL « 0x010b0004000405700607010180                                        (13 bytes)
21:53:55.190 CNTRLR   [Node 004] [~] [Configuration] 7: 1 => 1
21:53:55.191 SERIAL » [ACK]                                                                   (0x06)
21:53:55.193 DRIVER « [Node 004] [REQ] [ApplicationCommand]
                      └─[ConfigurationCCReport]
                          parameter #: 7
                          value size:  1
                          value:       1
21:53:55.199 CNTRLR « [Node 004] parameter #7 has value: 1
21:53:55.200 CNTRLR » [Node 004] querying parameter #8 value...
21:53:55.213 SERIAL » 0x010a00130403700508250fb6                                          (12 bytes)
21:53:55.214 DRIVER » [Node 004] [REQ] [SendData]
                      │ transmit options: 0x25
                      │ callback id:      15
                      └─[ConfigurationCCGet]
                          parameter #: 8
21:53:55.222 SERIAL « [ACK]                                                                   (0x06)
21:53:55.226 SERIAL « 0x0104011301e8                                                       (6 bytes)
21:53:55.228 SERIAL » [ACK]                                                                   (0x06)
21:53:55.230 DRIVER « [RES] [SendData]
                        was sent: true
21:53:55.312 SERIAL « 0x010b000400040570060801038d                                        (13 bytes)
21:53:55.316 CNTRLR   [Node 004] [~] [Configuration] 8: 3 => 3
21:53:55.317 SERIAL » [ACK]                                                                   (0x06)
21:53:55.319 DRIVER « [Node 004] [REQ] [ApplicationCommand]
                      └─[ConfigurationCCReport]
                          parameter #: 8
                          value size:  1
                          value:       3
21:53:55.341 SERIAL « 0x010500130f00e6                                                     (7 bytes)
21:53:55.343 SERIAL » [ACK]                                                                   (0x06)
21:53:55.346 DRIVER « [REQ] [SendData]
                        callback id:     15
                        transmit status: OK
21:53:55.358 SERIAL « 0x010b000400040570060801038d                                        (13 bytes)
21:53:55.365 CNTRLR   [Node 004] [~] [Configuration] 8: 3 => 3
21:53:55.367 SERIAL » [ACK]                                                                   (0x06)
21:53:55.371 DRIVER « [Node 004] [REQ] [ApplicationCommand]
                      └─[ConfigurationCCReport]
                          parameter #: 8
                          value size:  1
                          value:       3
21:53:55.379 CNTRLR « [Node 004] parameter #8 has value: 3
21:53:55.380 CNTRLR » [Node 004] querying parameter #9 value...
21:53:55.399 SERIAL » 0x010a001304037005092510a8                                          (12 bytes)
21:53:55.401 DRIVER » [Node 004] [REQ] [SendData]
                      │ transmit options: 0x25
                      │ callback id:      16
                      └─[ConfigurationCCGet]
                          parameter #: 9
21:53:55.408 SERIAL « [ACK]                                                                   (0x06)
21:53:55.414 SERIAL « 0x0104011301e8                                                       (6 bytes)
21:53:55.420 SERIAL » [ACK]                                                                   (0x06)
21:53:55.423 DRIVER « [RES] [SendData]
                        was sent: true
21:53:55.472 SERIAL « 0x010500131000f9                                                     (7 bytes)
21:53:55.476 SERIAL » [ACK]                                                                   (0x06)
21:53:55.478 DRIVER « [REQ] [SendData]
                        callback id:     16
                        transmit status: OK
21:53:55.759 SERIAL « 0x010b000400040570060901018e                                        (13 bytes)
21:53:55.762 CNTRLR   [Node 004] [~] [Configuration] 9: 1 => 1
21:53:55.763 SERIAL » [ACK]                                                                   (0x06)
21:53:55.765 DRIVER « [Node 004] [REQ] [ApplicationCommand]
                      └─[ConfigurationCCReport]
                          parameter #: 9
                          value size:  1
                          value:       1
21:53:55.812 CNTRLR « [Node 004] parameter #9 has value: 1
21:53:55.813 CNTRLR » [Node 004] querying parameter #10 value...
21:53:55.831 SERIAL » 0x010a0013040370050a2511aa                                          (12 bytes)
21:53:55.833 DRIVER » [Node 004] [REQ] [SendData]
                      │ transmit options: 0x25
                      │ callback id:      17
                      └─[ConfigurationCCGet]
                          parameter #: 10
21:53:55.839 SERIAL « [ACK]                                                                   (0x06)
21:53:55.844 SERIAL « 0x0104011301e8                                                       (6 bytes)
21:53:55.845 SERIAL » [ACK]                                                                   (0x06)
21:53:55.848 DRIVER « [RES] [SendData]
                        was sent: true
21:53:55.881 SERIAL « 0x010b000400040570060a01038f                                        (13 bytes)
21:53:55.884 CNTRLR   [Node 004] [~] [Configuration] 10: 3 => 3
21:53:55.886 SERIAL » [ACK]                                                                   (0x06)
21:53:55.888 DRIVER « [Node 004] [REQ] [ApplicationCommand]
                      └─[ConfigurationCCReport]
                          parameter #: 10
                          value size:  1
                          value:       3
21:53:55.986 SERIAL « 0x010b000400040570060a01038f                                        (13 bytes)
21:53:55.990 CNTRLR   [Node 004] [~] [Configuration] 10: 3 => 3
21:53:55.991 SERIAL » [ACK]                                                                   (0x06)
21:53:55.994 DRIVER « [Node 004] [REQ] [ApplicationCommand]
                      └─[ConfigurationCCReport]
                          parameter #: 10
                          value size:  1
                          value:       3
21:53:58.014 SERIAL « 0x010b000400040570060a01038f                                        (13 bytes)
21:53:58.020 CNTRLR   [Node 004] [~] [Configuration] 10: 3 => 3
21:53:58.022 SERIAL » [ACK]                                                                   (0x06)
21:53:58.044 DRIVER « [Node 004] [REQ] [ApplicationCommand]
                      └─[ConfigurationCCReport]
                          parameter #: 10
                          value size:  1
                          value:       3
21:53:59.958 SERIAL « 0x010500131101f9                                                     (7 bytes)
21:53:59.961 SERIAL » [ACK]                                                                   (0x06)
21:53:59.964 DRIVER « [REQ] [SendData]
                        callback id:     17
                        transmit status: NoAck
21:53:59.978 CNTRLR   [Node 004] did not respond after 1/3 attempts.  Scheduling next try in 500 ms.
21:54:09.294 SERIAL » 0x01090013020262052514b3                                            (11 bytes)
21:54:09.297 DRIVER » [Node 002] [REQ] [SendData]
                      │ transmit options: 0x25
                      │ callback id:      20
                      └─[DoorLockCCConfigurationGet]
21:54:09.304 SERIAL « [ACK]                                                                   (0x06)
21:54:09.311 SERIAL « 0x0104011301e8                                                       (6 bytes)
21:54:09.313 SERIAL » [ACK]                                                                   (0x06)
21:54:09.317 DRIVER « [RES] [SendData]
                        was sent: true
21:54:09.330 SERIAL « 0x010500131400fd                                                     (7 bytes)
21:54:09.333 SERIAL » [ACK]                                                                   (0x06)
21:54:09.336 DRIVER « [REQ] [SendData]
                        callback id:     20
                        transmit status: OK
21:54:10.952 CNTRLR   [Node 002] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
21:54:11.467 SERIAL » 0x01090013020262052514b3                                            (11 bytes)
21:54:11.470 DRIVER » [Node 002] [REQ] [SendData]
                      │ transmit options: 0x25
                      │ callback id:      20
                      └─[DoorLockCCConfigurationGet]
21:54:11.477 SERIAL « [ACK]                                                                   (0x06)
21:54:11.484 SERIAL « 0x0104011301e8                                                       (6 bytes)
21:54:11.486 SERIAL » [ACK]                                                                   (0x06)
21:54:11.495 DRIVER « [RES] [SendData]
                        was sent: true
21:54:12.695 SERIAL « 0x010500131400fd                                                     (7 bytes)
21:54:12.697 SERIAL » [ACK]                                                                   (0x06)
21:54:12.701 DRIVER « [REQ] [SendData]
                        callback id:     20
                        transmit status: OK
21:54:14.326 CNTRLR   [Node 002] UserCodeCC: doing a complete interview...
21:54:14.328 CNTRLR » [Node 002] querying number of user codes...
21:54:14.356 SERIAL » 0x01090013020263042515b2                                            (11 bytes)
21:54:14.358 DRIVER » [Node 002] [REQ] [SendData]
                      │ transmit options: 0x25
                      │ callback id:      21
                      └─[UserCodeCCUsersNumberGet]
21:54:14.365 SERIAL « [ACK]                                                                   (0x06)
21:54:14.372 SERIAL « 0x0104011301e8                                                       (6 bytes)
21:54:14.374 SERIAL » [ACK]                                                                   (0x06)
21:54:14.377 DRIVER « [RES] [SendData]
                        was sent: true
21:54:14.510 SERIAL « 0x010500131500fc                                                     (7 bytes)
21:54:14.511 SERIAL » [ACK]                                                                   (0x06)
21:54:14.514 DRIVER « [REQ] [SendData]
                        callback id:     21
                        transmit status: OK
21:54:16.126 CNTRLR   [Node 002] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
21:54:16.643 SERIAL » 0x01090013020263042515b2                                            (11 bytes)
21:54:16.645 DRIVER » [Node 002] [REQ] [SendData]
                      │ transmit options: 0x25
                      │ callback id:      21
                      └─[UserCodeCCUsersNumberGet]
21:54:16.652 SERIAL « [ACK]                                                                   (0x06)
21:54:16.659 SERIAL « 0x0104011301e8                                                       (6 bytes)
21:54:16.662 SERIAL » [ACK]                                                                   (0x06)
21:54:16.665 DRIVER « [RES] [SendData]
                        was sent: true
21:54:17.916 SERIAL « 0x010500131500fc                                                     (7 bytes)
21:54:17.918 SERIAL » [ACK]                                                                   (0x06)
21:54:17.921 DRIVER « [REQ] [SendData]
                        callback id:     21
                        transmit status: OK
21:54:19.542 CNTRLR   [Node 002] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
21:54:20.090 SERIAL » 0x01090013020263042515b2                                            (11 bytes)
21:54:20.092 DRIVER » [Node 002] [REQ] [SendData]
                      │ transmit options: 0x25
                      │ callback id:      21
                      └─[UserCodeCCUsersNumberGet]
21:54:20.099 SERIAL « [ACK]                                                                   (0x06)
21:54:20.107 SERIAL « 0x0104011301e8                                                       (6 bytes)
21:54:20.109 SERIAL » [ACK]                                                                   (0x06)
21:54:20.113 DRIVER « [RES] [SendData]
                        was sent: true
21:54:20.122 SERIAL « 0x010500131500fc                                                     (7 bytes)
21:54:20.124 SERIAL » [ACK]                                                                   (0x06)
21:54:20.126 DRIVER « [REQ] [SendData]
                        callback id:     21
                        transmit status: OK
21:54:21.741 CNTRLR   [Node 002] Interview attempt 3/5 failed, retrying in 15000 ms...

Hmm, doesn't look like that worked since we now got overlapping transactions :(
I'll try to implement #1253 as soon as possible, then we can try again.

Sorry that I didn't reply earlier. #1253 was merged, so you should be able to do this and have the driver handle the message as usual without the problems we faced above:
const cc = new CommandClass(driver, {
    nodeId: 2,
    ccId: CommandClasses["Anti-theft"], // or 0x5d
    ccCommand: 0x02,
});
await driver.sendCommand(cc);

Sorry that I didn't reply earlier. #1253 was merged, so you should be able to do this and have the driver handle the message as usual without the problems we faced above:
const cc = new CommandClass(driver, {
    nodeId: 2,
    ccId: CommandClasses["Anti-theft"], // or 0x5d
    ccCommand: 0x02,
});
await driver.sendCommand(cc);

Hey @smitt04 did you get around to test this yet?


Thermostat-card - Temperature not centerd in Firefox

Hi! When testing the thermostar-card on Firefox the temperature is not centerd. i have set dom.webcomponents.shadowdom.enabled and dom.webcomponents.customelements.enabled to "true".
When i open it in Chrome. everything works great.

Fixed in 0.0.2


Change open service broker configuration to clone cloud source repo using HTTPS instead of SSH

Hi in our environment we are using osb which is used to clone cloud source repo using ssh. We want it to change repo using https instead of ssh. can you plsh guide me, how to do the required changes?

Closing stale issue which doesn't seem related to the OSBAPI. Please raise a new one if this is still an issue/


Global Save sorting / Group settings

What's the Problem?
Sorting and / or Group settings will not affected to all Folders (tested in Columns view)
have to set every time sorting and grouping
Solution/Idea
checkbox to overtake setting as global setting with overwriting all exisitings settings
Alternatives
--
Priorities

Capability
Priority

This proposal will allow developers to accomplish W
Must

This proposal will allow end users to accomplish X
Should

This proposal will allow developers to accomplish Y
Could

This proposal will allow end users to accomplish Z
Won't

Files Version
2.1.0
Windows Version
Windows 11
Comments
No response

@ERGPOL could you check if turning off "enable individual preferences for folders" option under settings > preferences does the job (might not affect column view)?
@Futureblur that issue is fixed in Files v2.1 that was just released 👍

Is this still an issue in <IP_ADDRESS>?


added static lib and static framework target

Here is a fat binary built with lipo create
Reachability.framework.zip


⚠ Mobitopup has degraded performance

In abd334f, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 3897 ms

Resolved: Mobitopup performance has improved in 4925871.


Custom  Dataset

How to prepare the custom dataset?

Hi,
The best way is to prepare the custom dataset in the BOP format .
The essential components are files that are

camera.json (camera intrinsic),
models (ply files and models_info.json)
train (if training images exist)
If you don't have training images, I would recommend using other rendering pipelines that use Blender instead of basic OpenGL based pipeline in this repository (e.g., BlenderProc

After that, you have to set up the directory and the name of the dataset in tools/bop_io.py properly.
elif(dataset=='dataset_name'):
        bop_dataset_dir = os.path.join(bop_dir,"dataset_dir")
        test_dir = bop_dataset_dir+"/test" #(optional)
        train_dir = bop_dataset_dir+"/train"
        model_dir = bop_dataset_dir+"/models"+postfix_model
        model_scale=0.001 #scale of the 3D models

https://github.com/kirumang/Pix2Pose/blob/843effe0097e9982f4b07dd90b04ede2b9ee9294/tools/bop_io.py#L105
And, follow the steps including the training of a detection pipeline.
Further questions are more than welcome!
Thank you

Hey @Zumbalamambo, @kirumang,
I am preparing a custom dataset with the BOP toolkit as well, which actually already worked out pretty well apart from centering the view of BlenderProc on the custom dataset objects. The rendered pictures I am currently able to create with the bop_loader function usually only contain small parts of the custom objects located in the bottom-right corner. Did you have similar problems and found a workaround or did you successfully manage to create your dataset?
So far I managed to:

include the custom dataset in all necessary functions (that I was able to find) from bop_toolkit and Pix2Pose so it is recognized as a BOP dataset
transform custom .ply models into colored xyz-models
create annotated pictures in /path/to/bop_data/custom_dataset with ground truths, masks and models_info.json files

What I guess is still necessary to be done to train my own Pix2Pose weights:

create training dataset with pictures of each individual model
create scenes with custom objects and BOP dataset objects

Please let me know if any of you sees an obvious flaw in my work so far or has an idea how I should proceed to manage creating a custom dataset. I already posted an issue in the BlenderProc repository (Link), but couldn't find any solution so far, so any help is greatly appreciated.
Regards,
Jan

Hey @Zumbalamambo, @kirumang,
I am preparing a custom dataset with the BOP toolkit as well, which actually already worked out pretty well apart from centering the view of BlenderProc on the custom dataset objects. The rendered pictures I am currently able to create with the bop_loader function usually only contain small parts of the custom objects located in the bottom-right corner. Did you have similar problems and found a workaround or did you successfully manage to create your dataset?
So far I managed to:

include the custom dataset in all necessary functions (that I was able to find) from bop_toolkit and Pix2Pose so it is recognized as a BOP dataset
transform custom .ply models into colored xyz-models
create annotated pictures in /path/to/bop_data/custom_dataset with ground truths, masks and models_info.json files

What I guess is still necessary to be done to train my own Pix2Pose weights:

create training dataset with pictures of each individual model
create scenes with custom objects and BOP dataset objects

Please let me know if any of you sees an obvious flaw in my work so far or has an idea how I should proceed to manage creating a custom dataset. I already posted an issue in the BlenderProc repository (Link), but couldn't find any solution so far, so any help is greatly appreciated.
Regards,
Jan


Issues install on Raspberry Pi 2 - Raspbian Jessie / Wheezy

Hello,
When running npm install aminogfx-gl npm fails on fresh installs of raspbian jessie and wheezy.
Attached is the npm-debug.txt any help is appreciated!
npm-debug.txt

I've had the same issue with the legacy node version. 4.x works fine:
curl -sL https://deb.nodesource.com/setup_4.x | sudo -E bash -

Does this happen with Node v5?

I did not try v5 but the 0.x version was failing which Raspbian installs by default. I would guess 5.x works fine too.

Yes, that’s probably it. I’ve tried it with V4 and V5 and they work okay. I had to do some work a few months back to update to the newest version of NAN. I’m guessing 0.x isn’t supported anymore.

On May 30, 2016, at 1:36 PM, Christoph Bratschi<EMAIL_ADDRESS>wrote:
I did not try v5 but the 0.x version was failing which Raspbian installs by default. I would guess 5.x works fine too.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/joshmarinacci/aminogfx/issues/16#issuecomment-222551733, or mute the thread https://github.com/notifications/unsubscribe/AAQ5ys3vP5RK3HZ3Hfz7_VKwMPLh33h1ks5qG0phgaJpZM4HP8Sw.